Communication method, communication device, communication system, storage medium and program product

Abstract

Disclosed in the present application are a communication method, a communication device, a communication system, a storage medium and a program product. The communication method comprises: determining at least one of a first parameter, a second parameter and a third parameter, wherein the first parameter is used for determining a first time interval, the first time interval is a time interval between an NPDCCH and an NPDSCH, and the NPDSCH is scheduled by DCI carried on the NPDCCH; the second parameter is used for determining a second time interval, and the second time interval is a time interval between the NPDSCH and an HARQ-ACK feedback corresponding to the NPDSCH; the third parameter is used for determining a third time interval, the third time interval is a time interval between the NPDCCH and an NPUSCH, and the NPUSCH is scheduled by the DCI carried on the NPDCCH; first information is sent by a network device; and the NPDCCH, the NPDSCH, the HARQ-ACK feedback and the NPUSCH are all located in a time-division duplexing (TDD) frame. Thus, uplink-downlink collisions can be avoided in a system, an HARQ process is optimized, the utilization rate of resources is effectively improved, and the overall performance of the system is also enhanced.

Description

Communication methods, communication equipment, communication systems, storage media and software products Technical Field

[0001] This application relates to the field of communication technology, and in particular to communication methods, communication equipment, communication systems, storage media, and program products. Background Technology

[0002] With the continuous development of communication technology, non-terrestrial networks (NTNs) have gradually become a research hotspot. NTNs can utilize airborne platforms or in-orbit satellites and other non-terrestrial infrastructure to build wireless communication systems. They can effectively enhance network coverage and can also be used for emergency communications. Furthermore, NTNs can play a role in the development of the Internet of Things (IoT) and possess scalability. Summary of the Invention

[0003] This application provides communication methods, communication devices, communication systems, storage media, and program products.

[0004] A first aspect of this application provides a communication method, which is executed by a terminal, and the method includes:

[0005] Based on the agreement or the first information, determine at least one of the first parameter, the second parameter, and the third parameter;

[0006] The first parameter is used to determine the first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH. The NPDSCH is scheduled by the downlink control information DCI carried on the NPDCCH.

[0007] The second parameter is used to determine the second time interval, which is the time interval between the NPDSCH and the HARQ-ACK feedback corresponding to the NPDSCH;

[0008] The third parameter is used to determine the third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, and the NPUSCH is scheduled by the DCI carried on the NPDCCH;

[0009] The first information is sent by the network device. The NPDCCH, NPDSCH, HARQ-ACK feedback, and NPUSCH are all located in the Time Division Duplex (TDD) frame.

[0010] A second aspect of this application provides a communication method, which is executed by a network device, and the method includes:

[0011] Send first information to the terminal, the first information being used to determine at least one of a first parameter, a second parameter, and a third parameter;

[0012] The first parameter is used to determine the first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH. The NPDSCH is scheduled by the downlink control information DCI carried on the NPDCCH.

[0013] The second parameter is used to determine the second time interval, which is the time interval between the NPDSCH and the HARQ-ACK feedback corresponding to the NPDSCH;

[0014] The third parameter is used to determine the third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, and the NPUSCH is scheduled by the DCI carried on the NPDCCH;

[0015] The NPDCCH, NPDSCH, HARQ-ACK feedback, and NPUSCH are all located in a Time Division Duplex (TDD) frame.

[0016] A third aspect of this application provides a terminal, the terminal comprising:

[0017] The processing module is used to determine at least one of the first parameter, the second parameter, and the third parameter based on the agreement of the protocol or the first information;

[0018] The first parameter is used to determine the first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH, wherein the NPDSCH is scheduled by the DCI carried on the NPDCCH.

[0019] The second parameter is used to determine the second time interval, which is the time interval between the NPDSCH and the HARQ-ACK feedback corresponding to the NPDSCH;

[0020] The third parameter is used to determine the third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, and the NPUSCH is scheduled by the DCI carried on the NPDCCH;

[0021] The first information is sent by the network device. The NPDCCH, NPDSCH, HARQ-ACK feedback, and NPUSCH are all located in the Time Division Duplex (TDD) frame.

[0022] A fourth aspect of this application provides a network device, which includes:

[0023] The transceiver module is used to send first information to the terminal, wherein the first information is used to determine at least one of a first parameter, a second parameter, and a third parameter;

[0024] The first parameter is used to determine the first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH, wherein the NPDSCH is scheduled by the DCI carried on the NPDCCH.

[0025] The second parameter is used to determine the second time interval, which is the time interval between the NPDSCH and the HARQ-ACK feedback corresponding to the NPDSCH;

[0026] The third parameter is used to determine the third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, and the NPUSCH is scheduled by the DCI carried on the NPDCCH;

[0027] The NPDCCH, NPDSCH, HARQ-ACK feedback, and NPUSCH are all located in a Time Division Duplex (TDD) frame.

[0028] The solution proposed in this application determines at least one of a first parameter, a second parameter, and a third parameter. The first parameter determines a first time interval, which is the time interval between NPDCCH and NPDSCH, where NPDSCH is scheduled by DCI carried on NPDCCH. The second parameter determines a second time interval, which is the time interval between NPDSCH and its corresponding HARQ-ACK feedback. The third parameter determines a third time interval, which is the time interval between NPDCCH and NPUSCH, where NPUSCH is scheduled by DCI carried on NPDCCH. The first information is sent by the network device. NPDCCH, NPDSCH, HARQ-ACK feedback, and NPUSCH are all located in a Time Division Duplex (TDD) frame, enabling the avoidance of uplink and downlink conflicts in the system, optimizing the HARQ process, effectively improving resource utilization, and enhancing overall system performance. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments or background art of this application, the following description of the accompanying drawings is provided. The following drawings are merely some embodiments of this application and do not impose specific limitations on the scope of protection of this application.

[0030] Figure 1A is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0031] Figure 1B is a schematic diagram of the TDD frame structure of a satellite system provided in an embodiment of this disclosure;

[0032] Figure 2A is an interactive schematic diagram of a communication method provided in an embodiment of this application;

[0033] Figure 3A is an interactive schematic diagram of a communication method provided in an embodiment of this application;

[0034] Figure 4A is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0035] Figure 4B is a schematic diagram of the structure of a network device provided in an embodiment of this application;

[0036] Figure 5A is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0037] Figure 5B is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0038] This application provides communication methods, communication devices, communication systems, storage media, and program products.

[0039] In a first aspect, embodiments of this application propose a communication method, the method comprising:

[0040] Based on the protocol agreement or the first information, at least one of the first parameter, the second parameter, and the third parameter is determined; wherein, the first parameter is used to determine the first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH, and the NPDSCH is scheduled by the downlink control information DCI carried on the NPDCCH; the second parameter is used to determine the second time interval, which is the time interval between the NPDSCH and the corresponding hybrid automatic repeat request acknowledgment (HARQ-ACK) feedback; the third parameter is used to determine the third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, and the NPUSCH is scheduled by the DCI carried on the NPDCCH; the first information is sent by the network device, and the NPDCCH, the NPDSCH, the HARQ-ACK feedback, and the NPUSCH are all located in a time division duplex (TDD) frame.

[0041] In the above embodiments, it is possible to avoid uplink and downlink conflicts in satellite systems using TDD mode, optimize the HARQ process, effectively improve resource utilization, enhance overall system performance, and improve the reliability of channel transmission.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the first parameter is used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the first subframe occupied by the NPDSCH.

[0043] In conjunction with some embodiments of the first aspect, in some embodiments, the NPDSCH and the NPDCCH are transmitted within a TDD frame; the maximum value among the candidate values ​​of the first parameter is determined based on the number of subframes included in a downlink time unit of the TDD frame and the number of subframes occupied by the NPDCCH.

[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the NPDSCH and the NPDCCH are transmitted in different TDD frames; the maximum value among the candidate values ​​of the first parameter is determined based on the number of subframes included in a downlink time unit of the TDD frame, the number of subframes occupied by the NPDCCH, the number of subframes occupied by the TDD frame, the number of TDD frames between the NPDSCH and the NPDCCH, and the number of subframes between the frame header of the TDD frame and the starting point of the downlink time unit occupied by the NPDSCH.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the first parameter is determined based on the fourth parameter and the first offset; the NPDSCH is located within the downlink time unit 3 of the TDD frame; wherein, the fourth parameter is used to indicate the number of subframes between the first reference subframe and the last subframe occupied by the NPDSCH; the first offset is used to indicate the number of subframes between the first reference subframe and the first subframe occupied by the NPDSCH; the first offset is configured by the network device, or the first offset is agreed upon by the protocol.

[0046] In some embodiments of the first aspect, the first offset is equal to a terminal-specific first offset; or, the first offset is equal to a cell-specific first offset; or, the first offset is equal to the sum of the terminal-specific first offset and the cell-specific first offset; wherein the terminal-specific first offset corresponds to the terminal, and the cell-specific first offset corresponds to the serving cell where the terminal is located.

[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the first parameter is determined based on a first time domain resource and a second offset; the NPDSCH is located within downlink time unit 3 of a TDD frame; wherein, the first time domain resource is the first available time domain resource whose interval with the NPDSCH meets the requirements; the second offset is used to indicate the number of subframes between the first time domain resource and the first subframe occupied by the NPDSCH; the second offset is configured by the network device or is agreed upon by the protocol.

[0048] In some embodiments of the first aspect, the second offset is equal to a terminal-specific second offset; or, the second offset is equal to a cell-specific second offset; or, the second offset is equal to the sum of the terminal-specific second offset and the cell-specific second offset; wherein the terminal-specific second offset corresponds to the terminal, and the cell-specific second offset corresponds to the serving cell where the terminal is located.

[0049] In conjunction with some embodiments of the first aspect, in some embodiments, the second parameter is used to indicate the number of subframes between the last subframe occupied by the NPDSCH and the first subframe occupied by the HARQ-ACK feedback.

[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the HARQ-ACK feedback and the NPDSC are sent in different TDD frames; the maximum value among the candidate values ​​of the second parameter is determined based on the uplink time unit occupied by the HARQ-ACK feedback and the number of subframes occupied by the HARQ-ACK feedback.

[0051] In conjunction with some embodiments of the first aspect, in some embodiments, the second parameter is determined based on the fifth parameter and the third offset; the HARQ-ACK feedback is located within the uplink time unit 3 of the TDD frame; wherein, the fifth parameter is used to indicate the number of subframes between the second reference subframe and the last subframe occupied by the NPDSCH; the third offset is used to indicate the number of subframes between the second reference subframe and the first subframe occupied by the HARQ-ACK feedback; the third offset is configured by the network device, or the third offset is agreed upon by the protocol.

[0052] In conjunction with some embodiments of the first aspect, in some embodiments, the third offset is equal to a terminal-specific third offset; or, the third offset is equal to a cell-specific third offset; or, the third offset is equal to the sum of the terminal-specific third offset and the cell-specific third offset; wherein, the terminal-specific third offset corresponds to the terminal, and the cell-specific third offset corresponds to the serving cell where the terminal is located.

[0053] In conjunction with some embodiments of the first aspect, in some embodiments, the second parameter is determined based on a second time-domain resource and a fourth offset; the HARQ-ACK feedback is located within uplink time unit 3 of a TDD frame; wherein the second time-domain resource is the first available time-domain resource whose interval with the NPDSCH meets the requirements; the fourth offset is used to indicate the number of subframes between the second time-domain resource and the first subframe occupied by the HARQ-ACK feedback; the fourth offset is configured by the network device or is agreed upon by the protocol.

[0054] In conjunction with some embodiments of the first aspect, in some embodiments, the fourth offset is equal to a terminal-specific fourth offset; or, the fourth offset is equal to a cell-specific fourth offset; or, the fourth offset is equal to the sum of the terminal-specific fourth offset and the cell-specific fourth offset; wherein, the terminal-specific fourth offset corresponds to the terminal, and the cell-specific fourth offset corresponds to the serving cell where the terminal is located.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the third parameter is used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the first subframe occupied by the NPUSCH.

[0056] In conjunction with some embodiments of the first aspect, in some embodiments, the NPUSCH and the NPDCCH are transmitted in different TDD frames; the maximum value among the candidate values ​​of the third parameter is determined based on the uplink time unit occupied by the NPUSCH and the number of subframes occupied by the NPUSCH.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, the third parameter is determined based on the sixth parameter and the fifth offset; the NPUSCH is located within the uplink time unit 3 of the TDD frame; wherein, the sixth parameter is used to indicate the number of subframes between the third reference subframe and the last subframe occupied by the NPDCCH; the fifth offset is used to indicate the number of subframes between the third reference subframe and the first subframe occupied by the NPUSCH; the fifth offset is configured by the network device, or the fifth offset is agreed upon by the protocol.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the fifth offset is equal to a terminal-specific fifth offset; or, the fifth offset is equal to a cell-specific fifth offset; or, the fifth offset is equal to the sum of the terminal-specific fifth offset and the cell-specific fifth offset; wherein, the terminal-specific fifth offset corresponds to the terminal, and the cell-specific fifth offset corresponds to the serving cell where the terminal is located.

[0059] In conjunction with some embodiments of the first aspect, in some embodiments, the third parameter is determined based on a third time-domain resource and a sixth offset; the NPUSCH is located within the uplink time unit 3 of the TDD frame; wherein, the third time-domain resource is the first available time-domain resource whose interval with the NPDCCH meets the requirements; the sixth offset is used to indicate the number of subframes between the third time-domain resource and the first subframe occupied by the NPUSCH; the sixth offset is configured by the network device or is agreed upon by the protocol.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the sixth offset is equal to a terminal-specific sixth offset; or, the sixth offset is equal to a cell-specific sixth offset; or, the sixth offset is equal to the sum of the terminal-specific sixth offset and the cell-specific fourth offset; wherein, the terminal-specific sixth offset corresponds to the terminal, and the cell-specific fourth offset corresponds to the serving cell where the terminal is located.

[0061] In conjunction with some embodiments of the first aspect, in some embodiments, at least one of the following is satisfied: the temporal resources occupied by the NPDSCH are located in the first available downlink time unit after the first reference subframe, wherein the first parameter is used to indicate the number of subframes between the first reference subframe and the last subframe occupied by the NPDCCH; the temporal resources occupied by the HARQ-ACK feedback are located in the first available uplink time unit after the second reference subframe, wherein the second parameter is used to indicate the number of subframes between the second reference subframe and the last subframe occupied by the NPDSCH; the temporal resources occupied by the NPUSCH are located in the first available uplink time unit after the third reference subframe, wherein the third parameter is used to indicate the number of subframes between the third reference subframe and the last subframe occupied by the NPDCCH.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, at least one of the following is satisfied: the NPDSCH is repeatedly transmitted, wherein at least one of the repeatedly transmitted NPDSCH is located within downlink time unit 3 of the TDD frame; the NPUSCH is repeatedly transmitted, wherein at least one of the repeatedly transmitted NPUSCH is located within uplink time unit 3 of the TDD frame.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the NPDCCH carries downlink control information (DCI), the format type of the DCI is any one of N0, N1, and N2, and the length of each type of DCI is different; the method further includes: parsing the DCI based on a first number of bits; wherein the first number of bits is any one of the following: the length of any one of the multiple types of DCI; the length of the DCI with the smallest length among the multiple types of DCI; the length of the DCI with the largest length among the multiple types of DCI.

[0064] Secondly, embodiments of this application propose a communication method, the method comprising:

[0065] A first information is sent to the terminal, wherein the first information is used to determine at least one of a first parameter, a second parameter, and a third parameter; wherein the first parameter is used to determine a first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH, and the NPDSCH is scheduled by downlink control information DCI carried on the NPDCCH; the second parameter is used to determine a second time interval, which is the time interval between the NPDSCH and the corresponding hybrid automatic repeat request acknowledgment (HARQ-ACK) feedback; the third parameter is used to determine a third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, and the NPUSCH is scheduled by DCI carried on the NPDCCH; the NPDCCH, the NPDSCH, the HARQ-ACK feedback, and the NPUSCH are all located in a time division duplex (TDD) frame.

[0066] In the above embodiments, it is possible to avoid uplink and downlink conflicts in satellite systems using TDD mode, optimize the HARQ process, effectively improve resource utilization, enhance overall system performance, and improve the reliability of channel transmission.

[0067] In conjunction with some embodiments of the second aspect, in some embodiments, the first parameter is used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the first subframe occupied by the NPDSCH.

[0068] In conjunction with some embodiments of the second aspect, in some embodiments, the NPDSCH and the NPDCCH are transmitted within a TDD frame; the maximum value among the candidate values ​​of the first parameter is determined based on the number of subframes included in a downlink time unit of the TDD frame and the number of subframes occupied by the NPDCCH.

[0069] In conjunction with some embodiments of the second aspect, in some embodiments, the NPDSCH and the NPDCCH are transmitted in different TDD frames; the maximum value among the candidate values ​​of the first parameter is determined based on the number of subframes included in a downlink time unit of the TDD frame, the number of subframes occupied by the NPDCCH, the number of subframes occupied by the TDD frame, the number of TDD frames between the NPDSCH and the NPDCCH, and the number of subframes between the frame header of the TDD frame and the starting point of the downlink time unit occupied by the NPDSCH.

[0070] In conjunction with some embodiments of the second aspect, in some embodiments, the first parameter is determined based on the fourth parameter and the first offset; the NPDSCH is located within the downlink time unit 3 of the TDD frame; wherein, the fourth parameter is used to indicate the number of subframes between the first reference subframe and the last subframe occupied by the NPDSCH; the first offset is used to indicate the number of subframes between the first reference subframe and the first subframe occupied by the NPDSCH; the first offset is configured by the network device, or the first offset is agreed upon by the protocol.

[0071] In some embodiments, in conjunction with the second aspect, the first offset is equal to a terminal-specific first offset; or, the first offset is equal to a cell-specific first offset; or, the first offset is equal to the sum of the terminal-specific first offset and the cell-specific first offset; wherein the terminal-specific first offset corresponds to the terminal, and the cell-specific first offset corresponds to the serving cell where the terminal is located.

[0072] In conjunction with some embodiments of the second aspect, in some embodiments, the first parameter is determined based on a first time domain resource and a second offset; the NPDSCH is located within the downlink time unit 3 of the TDD frame; wherein, the first time domain resource is the first available time domain resource whose interval with the NPDSCH meets the requirements; the second offset is used to indicate the number of subframes between the first time domain resource and the first subframe occupied by the NPDSCH; the second offset is configured by the network device or is agreed upon by the protocol.

[0073] In some embodiments of the second aspect, the second offset is equal to a terminal-specific second offset; or, the second offset is equal to a cell-specific second offset; or, the second offset is equal to the sum of the terminal-specific second offset and the cell-specific second offset; wherein the terminal-specific second offset corresponds to the terminal, and the cell-specific second offset corresponds to the serving cell where the terminal is located.

[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the second parameter is used to indicate the number of subframes between the last subframe occupied by the NPDSCH and the first subframe occupied by the HARQ-ACK feedback.

[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the HARQ-ACK feedback and the NPDSC are sent in different TDD frames; the maximum value among the candidate values ​​of the second parameter is determined based on the uplink time unit occupied by the HARQ-ACK feedback and the number of subframes occupied by the HARQ-ACK feedback.

[0076] In some embodiments of the second aspect, the second parameter is determined based on the fifth parameter and the third offset; the HARQ-ACK feedback is located within the uplink time unit 3 of the TDD frame; wherein the fifth parameter is used to indicate the number of subframes between the second reference subframe and the last subframe occupied by the NPDSCH; the third offset is used to indicate the number of subframes between the second reference subframe and the first subframe occupied by the HARQ-ACK feedback; the third offset is configured by the network device or is agreed upon by the protocol.

[0077] In conjunction with some embodiments of the second aspect, in some embodiments, the third offset is equal to a terminal-specific third offset; or, the third offset is equal to a cell-specific third offset; or, the third offset is equal to the sum of the terminal-specific third offset and the cell-specific third offset; wherein, the terminal-specific third offset corresponds to the terminal, and the cell-specific third offset corresponds to the serving cell where the terminal is located.

[0078] In some embodiments of the second aspect, the second parameter is determined based on the second time-domain resource and the fourth offset; the HARQ-ACK feedback is located within the uplink time unit 3 of the TDD frame; wherein the second time-domain resource is the first available time-domain resource whose interval with the NPDSCH meets the requirements; the fourth offset is used to indicate the number of subframes between the second time-domain resource and the first subframe occupied by the HARQ-ACK feedback; the fourth offset is configured by the network device or is agreed upon by the protocol.

[0079] In conjunction with some embodiments of the second aspect, in some embodiments, the fourth offset is equal to a terminal-specific fourth offset; or, the fourth offset is equal to a cell-specific fourth offset; or, the fourth offset is equal to the sum of the terminal-specific fourth offset and the cell-specific fourth offset; wherein, the terminal-specific fourth offset corresponds to the terminal, and the cell-specific fourth offset corresponds to the serving cell where the terminal is located.

[0080] In conjunction with some embodiments of the second aspect, in some embodiments, the third parameter is used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the first subframe occupied by the NPUSCH.

[0081] In conjunction with some embodiments of the second aspect, in some embodiments, the NPUSCH and the NPDCCH are transmitted in different TDD frames; the maximum value among the candidate values ​​of the third parameter is determined based on the uplink time unit occupied by the NPUSCH and the number of subframes occupied by the NPUSCH.

[0082] In conjunction with some embodiments of the second aspect, in some embodiments, the third parameter is determined based on the sixth parameter and the fifth offset; the NPUSCH is located within the uplink time unit 3 of the TDD frame; wherein, the sixth parameter is used to indicate the number of subframes between the third reference subframe and the last subframe occupied by the NPDCCH; the fifth offset is used to indicate the number of subframes between the third reference subframe and the first subframe occupied by the NPUSCH; the fifth offset is configured by the network device, or the fifth offset is agreed upon by the protocol.

[0083] In conjunction with some embodiments of the second aspect, in some embodiments, the fifth offset is equal to a terminal-specific fifth offset; or, the fifth offset is equal to a cell-specific fifth offset; or, the fifth offset is equal to the sum of the terminal-specific fifth offset and the cell-specific fifth offset; wherein, the terminal-specific fifth offset corresponds to the terminal, and the cell-specific fifth offset corresponds to the serving cell where the terminal is located.

[0084] In conjunction with some embodiments of the second aspect, in some embodiments, the third parameter is determined based on the third time-domain resource and the sixth offset; the NPUSCH is located within the uplink time unit 3 of the TDD frame; wherein, the third time-domain resource is the first available time-domain resource whose interval with the NPDCCH meets the requirements; the sixth offset is used to indicate the number of subframes between the third time-domain resource and the first subframe occupied by the NPUSCH; the sixth offset is configured by the network device or is agreed upon by the protocol.

[0085] In conjunction with some embodiments of the second aspect, in some embodiments, the sixth offset is equal to a terminal-specific sixth offset; or, the sixth offset is equal to a cell-specific sixth offset; or, the sixth offset is equal to the sum of the terminal-specific sixth offset and the cell-specific fourth offset; wherein, the terminal-specific sixth offset corresponds to the terminal, and the cell-specific fourth offset corresponds to the serving cell where the terminal is located.

[0086] In conjunction with some embodiments of the second aspect, in some embodiments, at least one of the following is satisfied: the temporal resources occupied by the NPDSCH are located in the first available downlink time unit after the first reference subframe, wherein the first parameter is used to indicate the number of subframes between the first reference subframe and the last subframe occupied by the NPDCCH; the temporal resources occupied by the HARQ-ACK feedback are located in the first available uplink time unit after the second reference subframe, wherein the second parameter is used to indicate the number of subframes between the second reference subframe and the last subframe occupied by the NPDSCH; the temporal resources occupied by the NPUSCH are located in the first available uplink time unit after the third reference subframe, wherein the third parameter is used to indicate the number of subframes between the third reference subframe and the last subframe occupied by the NPDCCH.

[0087] In conjunction with some embodiments of the second aspect, in some embodiments, at least one of the following is satisfied: the NPDSCH is repeatedly transmitted, wherein at least one of the repeatedly transmitted NPDSCH is located within downlink time unit 3 of the TDD frame; the NPUSCH is repeatedly transmitted, wherein at least one of the repeatedly transmitted NPUSCH is located within uplink time unit 3 of the TDD frame.

[0088] In conjunction with some embodiments of the second aspect, in some embodiments, the NPDCCH carries downlink control information (DCI), the format type of the DCI is any one of N0, N1, and N2, and the length of each type of DCI is different; the terminal parses the DCI based on a first number of bits; wherein the first number of bits is any one of the following: the length of any one of the multiple types of DCI; the length of the DCI with the smallest length among the multiple types of DCI; the length of the DCI with the largest length among the multiple types of DCI.

[0089] Thirdly, embodiments of this application propose a communication method for use in a communication system, the communication system including a terminal and a network device, the method comprising:

[0090] The terminal determines at least one of a first parameter, a second parameter, and a third parameter based on the protocol agreement or first information. The first parameter determines a first time interval, which is the time interval between the Narrowband Physical Downlink Control Channel (NPDCCH) and the Narrowband Physical Downlink Shared Channel (NPDSCH), the NPDSCH being scheduled by Downlink Control Information (DCI) carried on the NPDCCH. The second parameter determines a second time interval, which is the time interval between the NPDSCH and the corresponding Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback. The third parameter determines a third time interval, which is the time interval between the NPDCCH and the Narrowband Physical Uplink Shared Channel (NPUSCH), the NPUSCH being scheduled by DCI carried on the NPDCCH. The first information is sent by the network device, and the NPDCCH, NPDSCH, HARQ-ACK feedback, and NPUSCH are all located within a Time Division Duplex (TDD) frame.

[0091] In the above embodiments, it is possible to avoid uplink and downlink conflicts in satellite systems using TDD mode, optimize the HARQ process, effectively improve resource utilization, enhance overall system performance, and improve the reliability of channel transmission.

[0092] Fourthly, embodiments of this application propose a terminal, which includes a transceiver module; wherein the terminal is used to execute the first aspect and optional implementations of the first aspect.

[0093] Fifthly, embodiments of this application propose a network device, which includes a transceiver module; wherein the first network element is used to execute the optional implementation of the second aspect and the second aspect.

[0094] In a sixth aspect, embodiments of this application provide a terminal, which includes one or more processors; wherein the terminal is used to execute the first aspect and optional implementations of the first aspect.

[0095] In a seventh aspect, embodiments of this application provide a network device comprising: one or more processors; wherein the network device is configured to execute the second aspect and optional implementations thereof.

[0096] Eighthly, embodiments of this application provide a communication device for executing the first aspect and optional implementations of the first aspect, as well as the second aspect and optional implementations of the second aspect.

[0097] Ninthly, embodiments of this application propose a communication system, which includes: a terminal and a network device; wherein the terminal is configured to perform the method described in the first aspect and the optional implementation of the first aspect, and the network device is configured to perform the method described in the second aspect and the optional implementation of the second aspect.

[0098] In a tenth aspect, embodiments of this application provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect and its optional implementation, as well as the second aspect and its optional implementation.

[0099] In the eleventh aspect, embodiments of this application provide a program product that, when executed by a communication device, causes the communication device to perform the method described in the first aspect and its optional implementation, as well as the second aspect and its optional implementation.

[0100] In a twelfth aspect, embodiments of this application provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect and its optional implementations, the second aspect and its optional implementations.

[0101] In a thirteenth aspect, embodiments of this application provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to the first aspect and its optional implementations, the second aspect, and its optional implementations.

[0102] It is understood that the aforementioned terminals, network devices, communication devices, communication systems, storage media, and program products are all used to execute the methods proposed in the embodiments of this application. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0103] This application provides communication methods, communication devices, communication systems, storage media, and program products. In some embodiments, the terms communication method, information processing method, data processing method, etc., can be used interchangeably.

[0104] The embodiments in this application are not exhaustive, but merely illustrative of some embodiments, and are not intended to limit the scope of protection of this application. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In the embodiments of this application, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0105] The terminology used in the embodiments of this application is for the purpose of describing specific embodiments only and is not intended to limit the scope of this application.

[0106] In the embodiments of this application, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the above," "described," "the foregoing," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0107] In the embodiments of this application, "multiple" refers to two or more.

[0108] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0109] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0110] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0111] The prefixes "first," "second," etc., used in the embodiments of this application are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0112] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0113] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0114] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0115] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0116] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0117] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0118] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0119] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.

[0120] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, various embodiments of this application can also be applied to structures that replace communication between access network devices, core network devices, or network devices and terminals with communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, uplink link, downlink link, etc., can be replaced with sidelink link.

[0121] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0122] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0123] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0124] Furthermore, each element, each row, or each column in the table of this application embodiment can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0125] Figure 1A is a schematic diagram of the architecture of a communication system according to an embodiment of this application.

[0126] As shown in Figure 1A, the communication system 100 includes a terminal 101 and a network device 102.

[0127] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things (IoT) device, narrowband Internet of Things (NB-IoT) device, satellite communication device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, wireless terminal device in smart home, and red-capped terminal, but is not limited thereto.

[0128] In some embodiments, network device 102 may be a node or device that connects a terminal to a wireless network. The network device may include, but is not limited to, nodes such as satellites or drones in non-terrestrial networks, evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), next-generation RAN node (NG-RAN node), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in Wi-Fi system.

[0129] In some embodiments, the technical solutions of this application can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this application can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0130] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0131] It is understood that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions proposed in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in the embodiments of this application are also applicable to similar technical problems.

[0132] The following embodiments of this application can be applied to the communication system 100 shown in FIG1A, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1A are illustrative. The communication system may include all or some of the main bodies in FIG1A, or it may include other main bodies outside of FIG1A. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is illustrative. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0133] The embodiments of this application can be applied to Non-terrestrial Network (NTN), Internet of Things (IoT) systems, Narrow Band-IoT (NB-IoT) systems, IoT-NTN systems, Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), 6th generation mobile communication system (6G), 6G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), and Global System for Mobile. Communications (GSM, CDMA2000), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi, IEEE 802.16), WiMAX (WiMAX, IEEE 802.20), Ultra-Wideband (UWB), Bluetooth, Public Land Mobile Network (PLMN), Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G / 6G).

[0134] In some embodiments, non-terrestrial networks (NTNs) are increasingly becoming a research hotspot. NTNs can utilize airborne platforms or on-orbit satellites and other non-terrestrial infrastructure to build wireless communication systems. They can effectively enhance network coverage and can also be used for emergency communications. Furthermore, NTNs can play a role in the development of the Internet of Things (IoT) and possess scalability.

[0135] In some embodiments, only Frequency Division Duplexing (FDD) operation is supported for IoT-NTN systems.

[0136] In some embodiments, it is considered to support Time Division Duplexing (TDD) operation on the dedicated spectrum (1616-1626.5 MHz) allocated to the satellite system.

[0137] In some embodiments, power consumption saving can also be achieved by introducing a certain period into the TDD band. For example, a period of 90ms can be defined.

[0138] Furthermore, one DL time unit (8.28ms) and one UL time unit (8.28ms) from a 90ms TDD mode on the satellite system's dedicated spectrum can be allocated to the 3GPP TDD mode, with the remaining resources used to maintain the operation of the original satellite system. This achieves compatibility between the 3GPP IoT-NTN TDD mode and the satellite system.

[0139] In some embodiments, the Time Division Multiple Access (TDMA) frame structure of the satellite system described above can be as shown in Figure 1B.

[0140] Since the current IoT-NTN system only supports FDD operation, the frame structure needs to be considered and redesigned for TDD mode.

[0141] In some embodiments, the following effects may also need to be considered when designing a TDD system:

[0142] For Low Earth Orbit (LEO) satellite systems, the Round Trip Time (RTT) varies depending on the satellite's altitude:

[0143] For example, LEO 600km: RTT is approximately 25.77ms; LEO 1200km: RTT is approximately 41.77ms.

[0144] In some embodiments of the IoT-NTN system in TDD mode, the time required for terminal 101 to decode control information and process data also needs to be considered when scheduling uplink and downlink transmissions. Therefore, it is necessary to redesign relevant parameters to provide sufficient processing time for the terminal, taking into account the frame structure of TDD mode.

[0145] The communication method, communication equipment, communication system, storage medium, and program products provided in this application will be described in detail below with reference to the accompanying drawings.

[0146] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of this application. As shown in Figure 2A, the embodiment of this application relates to a communication method, which includes:

[0147] In step S2101, network device 102 sends the first information.

[0148] In some embodiments, terminal 101 receives the first information sent by network device 102.

[0149] In some embodiments, terminal 101 may determine at least one of the first parameter, the second parameter, and the third parameter based on the first information described above.

[0150] In some embodiments, terminal 101 may also determine at least one of the first parameter, second parameter and third parameter mentioned above based on the agreement of the protocol.

[0151] Optionally, the first parameter is used to determine the first time interval, the second parameter is used to determine the second time interval, and the third parameter is used to determine the third time interval.

[0152] The first time interval mentioned above is the time interval between the Narrow Band Physical Downlink Control Channel (NPDCCH) and the Narrow Band Physical Downlink Shared Channel (NPDSCH), wherein the NPDSCH is scheduled by the downlink control information (DCI) carried on the NPDCCH.

[0153] The aforementioned second time interval is the time interval between the NPDSCH and the corresponding Hybrid Automatic Repeat Request-Acknowledge (HARQ-ACK) feedback.

[0154] The aforementioned third time interval is the time interval between the NPDCCH and the Narrow Band Physical Uplink Shared Channel (NPUSCH), wherein the NPUSCH is scheduled by the DCI carried on the NPDCCH.

[0155] For ease of description, in the embodiments of this application, K0 can be used to represent the first parameter, K1 can be used to represent the second parameter, and K2 can be used to represent the third parameter.

[0156] In the embodiments of this application, the aforementioned first information, NPDCCH, NPDSCH, NPUSCH, and HARQ-ACK feedback are all transmitted and received within the TDD frame.

[0157] In step S2102, terminal 101 determines the first parameter.

[0158] In some embodiments, the first parameter (represented by K0) is used to indicate the number of subframes between the last subframe occupied by NPDCCH and the first subframe occupied by NPDSCH.

[0159] Among them, the aforementioned NPDCCH carries a DCI, and the aforementioned NPDSCH is the NPDSCH scheduled by the DCI.

[0160] That is, the first time interval used to determine the first parameter mentioned above refers to the time interval between when terminal 101 ends receiving NPDCCH carrying downlink scheduling DCI and when terminal 101 begins receiving NPDSCH scheduled by the DCI.

[0161] As an example, when the terminal 101 detects, on a given serving cell, an NPDCCH ending at subframe n that is sent to the terminal, where DCI is carried on the NPDCCH, the terminal 101 shall start receiving the corresponding NPDSCH after subframe n+K0. The transmission of the corresponding NPDSCH is performed in N consecutive downlink subframes ni, where i=0,1,…,N-1, and decoding is performed according to the information in the NPDCCH. Wherein, subframe n is the last subframe of the NPDCCH transmission, which is determined by the starting subframe of the NPDCCH transmission and the DCI subframe repetition number field in the corresponding DCI; subframes ni (i=0,1,…,N-1) are N consecutive downlink subframes, excluding subframes used for System Information (SI) messages, scheduling gaps and processing gaps, and n0<n1<…,nN-1. Wherein, at least one of the scheduling gap(s) may be absent. Subframe n0 is the first available downlink subframe starting after the end of subframe n+K0. K0 is the number of subframes from subframe n (the last subframe of NPDCCH transmission) to the first subframe n0 of the NPDSCH.

[0162] In some embodiments, the value of the above first parameter may be redefined based on the frame structure of the TDD mode and the basic requirements between NPDCCH transmission and NPDSCH transmission.

[0163] Optionally, the above NPDCCH and NPDSCH may be sent within the same TDD frame. That is, the above NPDCCH and the above NPDSCH are sent within the same 90ms TDD frame. In this case, since one TDD frame includes four downlink (DL) time units, one downlink time unit includes 8 subframes, and it is also required to consider the basic requirement that at least 4 milliseconds shall be reserved between the end of the NPDCCH and the start of the NPDSCH, among the possible values of the above first parameter K0, the minimum value is 5, and the maximum value can be 8-x, where x is the number of subframes occupied by the above NPDCCH. For example, the candidate value of the first parameter K0 can be defined as k0 INTEGER(0...8-x), where INTEGER indicates that the value of K0 is an integer.

[0164] Optionally, the NPDCCH and NPDSCH may not be transmitted within the same TDD frame, meaning they can be transmitted across TDD frame periods. Specifically, the NPDSCH can be transmitted within a TDD frame following the TDD frame containing the NPDCCH, or within a TDD frame m TDD frames away from the TDD frame containing the NPDCCH. In this case, based on the TDD frame structure and considering the basic requirement of reserving at least 4 milliseconds between the end of the NPDCCH and the start of the NPDSCH, the minimum possible value of the first parameter K0 is 5, and the maximum value can be 8-x+90×m+T, where x is the number of subframes occupied by the NPDCCH, m is the number of TDD frames between the 90ms TDD frame containing the NPDCCH and the 90ms TDD frame containing the NPDSCH, m is a non-negative integer, and T is the number of subframes from the frame header of the 90ms TDD frame to the start point of the downlink time unit occupied by the NPDSCH.

[0165] Optionally, the downlink time unit occupied by the above-mentioned NPDSCH is downlink time unit 3 (DL3).

[0166] Optionally, the downlink time unit occupied by the above NPDCCH is downlink time unit 3 (DL3).

[0167] Optionally, the value of the first parameter mentioned above also needs to consider the maximum number of NPDCCH repetitions Rmax (i.e., the length of the search space Rmax, i.e., the number of downlink subframes contained in the search space), to adapt to different coverage levels. The larger the value of Rmax, the worse the coverage level (the worse the channel conditions) of terminal 101, and the more repetitions are needed to ensure reliable transmission of NPDCCH. Different search spaces can be configured with independent Rmax by the base station. It is understood that Rmax is not necessarily the actual number of NPDCCH repetitions; the actual number of NPDCCH repetitions R is less than or equal to Rmax.

[0168] The required scheduling delay for NPDSCH varies depending on the terminal's channel conditions. For example, a terminal in a good coverage level (good channel conditions) experiences fewer NPDCCH retransmissions and a shorter NPDCCH processing delay. Therefore, the NPDSCH scheduling delay can also be shorter to accommodate faster transmission demands. Conversely, a terminal in a poor coverage level (poor channel conditions) experiences more NPDCCH retransmissions and a longer NPDCCH processing delay. Therefore, the NPDSCH scheduling delay needs to be longer to accommodate the more frequent NPDCCH retransmissions and the poorer channel conditions.

[0169] As an example, based on the above considerations, a possible definition of the first parameter can be shown in Table 1 below.

[0170] Table 1 First parameter K0

[0171] In some embodiments, terminal 101 can base its actions on a scheduling delay information field: I Delay The value of K0 is obtained by querying the table specified in the protocol and then obtaining the corresponding value of the first parameter K0 mentioned above.

[0172] In some embodiments, a first offset (which can be represented by K0_offset) can be set to determine the first parameter based on the fourth parameter. Setting the first offset can ensure that the transmission time of the NPDSCH of terminal 101 is aligned with the 90ms TDD frame structure.

[0173] The fourth parameter mentioned above indicates the number of subframes between the first reference subframe and the last subframe occupied by the NPDCCH. The first offset mentioned above indicates the number of subframes between the first reference subframe and the first subframe occupied by the NPDCCH.

[0174] Optionally, the fourth parameter mentioned above can reuse the traditional settings, and the first reference subframe mentioned above is a subframe determined based on the existing parameter values.

[0175] Optionally, the first parameter can be expressed as: first parameter = 5 + fourth parameter + first offset.

[0176] For example, the value of the fourth parameter mentioned above and how it is determined can be as follows:

[0177] For DCI format N1, the fourth parameter is determined by the scheduling delay field (I) in Table 2 below. Delay )Sure;

[0178] For DCI format N2, the fourth parameter = 0.

[0179] Wherein, if the Cyclic Redundancy Check (CRC) of DCI format N1 is scrambled by the Group-Radio Network Temporary Identifier (G-RNTI), then the fourth parameter is based on the scheduling delay field (I) in Table 3. Delay) Determine; otherwise, the fourth parameter is determined according to the scheduling delay field (I) in Table 2. Delay The value of Rmax is determined according to the specifications of the corresponding DCI format N1.

[0180] Table 2. Fourth parameter of DCI format N1

[0181] Table 3. Fourth parameter of DCI format N1 with CRC scrambled by G-RNTI

[0182] Optionally, in the above embodiments, the NPDCCH and NPDSCH can be transmitted within the same TDD frame. That is, the NPDCCH and NPDSCH are transmitted within the same 90ms TDD frame.

[0183] Optionally, in the above embodiments, the NPDCCH and NPDSCH may not be transmitted within the same TDD frame, that is, they may be transmitted across the TDD frame period. Specifically, the NPDSCH may be transmitted in a TDD frame following the TDD frame containing the NPDCCH, or in a TDD frame m TDD frames away from the TDD frame containing the NPDCCH.

[0184] Optionally, the downlink time unit in the TDD frame occupied by the above NPDSCH is downlink time unit 3 (DL3).

[0185] Optionally, the aforementioned first offset may be configured or indicated by the network device 102, or it may be agreed upon by the protocol.

[0186] Optionally, the aforementioned first offset (K0_offset) can be equal to a terminal-specific first offset (represented by K0_UE_offset), that is, K0_offset = K0_UE_offset.

[0187] Optionally, the first offset (K0_offset) can be equal to the cell-specific first offset (represented by K0_cell_offset), that is, K0_offset = K0_cell_offset.

[0188] Optionally, the aforementioned first offset (K0_offset) can be equal to the sum of the terminal-specific first offset and the cell-specific first offset, that is, K0_offset = K0_cell_offset + K0_UE_offset.

[0189] Among them, the terminal-specific first offset (K0_UE_offset) corresponds to terminal 101, and the cell-specific first offset (K0_cell_offset) corresponds to the serving cell where terminal 101 is located.

[0190] Optionally, K0_cell_offset can be indicated by the higher-layer parameter k-Offset; K0_UE_offset can be indicated by the higher-layer parameter Differential Koffset. Alternatively, these two parameters can be determined jointly by the terminal and the network device through a protocol agreement. Alternatively, the first offset K0_offset can be set to a fixed value within a certain range.

[0191] The value range of K0_offset is (0...K0_offset_max), and K0_offset_max is the maximum value of K0_cell_offset + K0_UE_offset.

[0192] It should be noted that in the above embodiments, the first offset can be determined based on at least one of a cell-specific first offset and a terminal-specific first offset. The cell-specific first offset provides a cell-level reference time offset to distribute the uplink transmission times of different terminals and avoid conflicts. Furthermore, the terminal-specific first offset provides each terminal with an offset relative to the cell-specific first offset, enabling finer time adjustment. This setup can avoid uplink transmission conflicts and improve transmission efficiency.

[0193] In some embodiments, a new reference point (a first time-domain resource in this embodiment) and a new second offset (represented by K0_offset) can be set. Based on the first time-domain resource and the second offset, the aforementioned first parameter is determined. By setting the aforementioned first time-domain resource and the aforementioned second offset, the transmission time of the NPDSCH of terminal 101 can be ensured to be aligned with the 90ms TDD frame structure.

[0194] The first temporal resource mentioned above refers to the first available temporal resource whose interval with the NPDCCH meets the requirements (the granularity of this temporal resource can be a slot or a subframe, etc., without limitation). The second offset mentioned above is used to indicate the number of subframes between the first temporal resource and the first subframe occupied by the NPDCCH.

[0195] The requirement mentioned above can mean that at least a 4-millisecond transmission interval is reserved between the end of NPDCCH and the start of NPDSCH.

[0196] Optionally, in the above embodiments, the NPDCCH and NPDSCH can be transmitted within the same TDD frame. That is, the NPDCCH and NPDSCH are transmitted within the same 90ms TDD frame.

[0197] Optionally, in the above embodiments, the NPDCCH and NPDSCH may not be transmitted within the same TDD frame, that is, they may be transmitted across the TDD frame period. Specifically, the NPDSCH may be transmitted in a TDD frame following the TDD frame containing the NPDCCH, or in a TDD frame m TDD frames away from the TDD frame containing the NPDCCH.

[0198] Optionally, the downlink time unit in the TDD frame occupied by the above NPDSCH is downlink time unit 3 (DL3).

[0199] Optionally, the aforementioned second offset may be configured or indicated by the network device 102, or it may be agreed upon by the protocol.

[0200] Optionally, the aforementioned second offset (K0_offset) can be equal to a terminal-specific second offset (represented by K0_UE_offset), that is, K0_offset = K0_UE_offset.

[0201] Optionally, the aforementioned second offset (K0_offset) can be equal to a cell-specific second offset (represented by K0_cell_offset), that is, K0_offset = K0_cell_offset.

[0202] Optionally, the aforementioned second offset (K0_offset) can be equal to the sum of the terminal-specific second offset and the cell-specific second offset, that is, K0_offset = K0_cell_offset + K0_UE_offset.

[0203] Among them, the terminal-specific second offset (K0_UE_offset) corresponds to terminal 101, and the cell-specific second offset (K0_cell_offset) corresponds to the serving cell where terminal 101 is located.

[0204] Optionally, the cell-specific second offset (K0_cell_offset) can be indicated by the higher-layer parameter k-Offset; the terminal-specific second offset (K0_UE_offset) can be indicated by the higher-layer parameter Differential Koffset. Alternatively, these two parameters can be determined jointly by the terminal and network equipment through a protocol agreement. Alternatively, the second offset (K0_offset) can be set to a fixed value within a given range.

[0205] The second offset (K0_offset) has a value range of (0...K0_offset_max), where K0_offset_max is the maximum value of the cell-specific second offset plus the terminal-specific second offset.

[0206] In some embodiments, the value of the second offset can be 0, either by protocol preset or network configuration.

[0207] In some embodiments, the first parameter described above can also be used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the first reference subframe. Further, the temporal resources occupied by the NPDCCH are located in the first available downlink time unit after the first reference subframe. That is, terminal 101 can receive the NPDCCH within the first available downlink time unit after the first reference subframe.

[0208] That is, the aforementioned first parameter can reuse the traditional definition and determination method (as an example, it can be as shown in the value and determination method of the fourth parameter in the previous embodiment, which will not be repeated here), and the first reference subframe can be determined based on the aforementioned first parameter. Further, the terminal 101 performs NPDSC transmission in TDD mode on the first available downlink time unit after the first reference subframe.

[0209] As an example, the NPDCCH can be transmitted within the first available downlink time unit after subframe n+5 (i.e., the first reference subframe). Here, subframe n is the last subframe occupied by the NPDCCH.

[0210] In some embodiments, the NPDSCH described above may be sent repeatedly.

[0211] In some embodiments, for retransmitted NPDSCH, network device 102 can be configured such that at least one repetition of terminal 101 occurs within downlink time unit 3 (DL3) of a 90ms TDD frame. Alternatively, terminal 101 expects at least one repetition to occur within downlink time unit 3 (DL3) of a 90ms TDD frame.

[0212] In step S2103, terminal 101 determines the second parameter.

[0213] In some embodiments, the second parameter (represented by K1) is used to indicate the number of subframes between the last subframe occupied by NPDSCH and the first subframe occupied by HARQ-ACK feedback.

[0214] The HARQ-ACK feedback mentioned above is the feedback corresponding to the NPDSCH mentioned above, that is, the feedback in response to the NPDSCH mentioned above.

[0215] Optionally, the HARQ-ACK feedback mentioned above can be carried by uplink channels such as NPUSCH or Narrow Band Physical Uplink Control Channel (NPUCCH).

[0216] Optionally, the content of the HARQ-ACK feedback can be either acknowledgment (ACK) or non-acknowledgment (NACK).

[0217] That is, the second time interval used to determine the second parameter mentioned above refers to the time interval between when terminal 101 ends receiving NPDSCH and when terminal 101 begins sending the HARQ-ACK feedback.

[0218] As an example, when the terminal 101 detects an NPDSCH ending at subframe n that is sent to the terminal on a given serving cell, and the NPDSCH requires an ACK / NACK response, the terminal 101 shall start transmitting an uplink channel carrying the ACK / NACK response after subframe n+K1. Corresponding HARQ-ACK feedback is transmitted in N consecutive downlink subframes ni, where i=0,1,...,N-1. Wherein, subframe n is the last subframe of the NPDSCH transmission; subframes ni (i=0,1,...,N-1) are N consecutive uplink subframes, and n0<n1<...,nN-1. Subframe n0 is the first available downlink subframe starting after the end of subframe n+K1. K1 is the number of subframes between subframe n (the last subframe of NPDSCH transmission) and the first subframe n0 for HARQ-ACK feedback transmission.

[0219] In some embodiments, the value of the above second parameter may be redefined based on the frame structure of the TDD mode and the basic requirements between NPDSCH transmission and HARQ-ACK feedback transmission.

[0220] Considering that in TDD frame structure design, an appropriate guard period needs to be reserved to ensure sufficient time delay between uplink and downlink switching and avoid signal overlap. Therefore, when designing the above second parameter, it is necessary to ensure that the time interval between the NPDSCH and its HARQ-ACK feedback meets the requirement of the guard period.

[0221] Understandably, due to the frame structure of TDD mode, the transmission of NPDSCH and HARQ-ACK feedback will not occur within the same TDD frame. That is, NPDSCH transmission and its HARQ-ACK feedback need to be transmitted across TDD frames. Specifically, the HARQ-ACK feedback can be sent in a TDD frame following the TDD frame containing the NPDSCH, or in a TDD frame m TDD frames away from the NPDSCH frame. In this case, based on the TDD frame structure and considering the guard slot requirements, the interval between the subframe ending at downlink time unit DL3 in the current TDD frame and the subframe starting at uplink time unit UL3 in the next TDD frame is approximately 54 subframes, while the maximum round-trip time for LEO is approximately 41 subframes. Therefore, among the possible values ​​of the second parameter K1, the minimum value is 54, and the maximum value can be 62-N+90m, where N is the number of subframes occupied by HARQ-ACK, m is the number of TDD frames between the 90ms TDD frame where NPDSCH is located and the 90ms TDD frame where HARQ-ACK feedback is located, and m is a non-negative integer. For example, the candidate value of the second parameter K1 can be defined as k1 INTEGER(54...62-N)+90m, where INTEGER indicates that the value of K1 is an integer.

[0222] Optionally, the downlink time unit occupied by the above-mentioned NPDSCH is downlink time unit 3 (DL3).

[0223] Optionally, the uplink time unit occupied by the above HARQ-ACK feedback is uplink time unit 3 (UL3).

[0224] Optionally, the value of the second parameter mentioned above should also take into account the subcarrier spacing (SCS).

[0225] As an example, based on the above considerations, the possible definitions of the second parameter for different subcarrier intervals can be shown in Tables 4 and 5 below.

[0226] Table 4 shows the second parameter K1 and ACK / NACK subcarriers corresponding to a subcarrier spacing of Δf = 3.75kHz.

[0227] Table 5 shows the second parameter K1 and ACK / NACK subcarriers corresponding to a subcarrier spacing of Δf = 15kHz.

[0228] In some embodiments, terminal 101 may query the table agreed in the protocol based on the ACK / NACK resource index to obtain the value of the second parameter K1 mentioned above, and determine the allocated subcarrier for ACK / NACK.

[0229] In some embodiments, a third offset (which can be represented by K1_offset) can be set to determine the second parameter based on the fifth parameter. The setting of the second offset can ensure that the transmission time of the HARQ-ACK feedback from terminal 101 is aligned with the 90ms TDD frame structure.

[0230] The fifth parameter mentioned above indicates the number of subframes between the second reference subframe and the last subframe occupied by NPDSCH. The third offset mentioned above indicates the number of subframes between the second reference subframe and the first subframe occupied by HARQ-ACK feedback.

[0231] Optionally, the fifth parameter mentioned above can reuse the traditional settings, and the second reference subframe mentioned above is a subframe determined based on the existing parameter values.

[0232] For example, the value of the fifth parameter mentioned above and the method of determining it can be as follows:

[0233] For FDD, the fifth parameter is k′0+K offset -1, meaning the second reference subframe is n+k′0+K offset -1;

[0234] For TDD, the fifth parameter is 12+k′0-1, which means the second reference subframe is k′0-1 uplink subframes after subframe n+12.

[0235] Among them, the above K offset The value is determined by the following rules:

[0236] If terminal 101 is configured with the higher-level parameter k-Offset, then K offset =K cell_offset -K UE_offset , where: K cell_offset Indicated by the high-level parameter k-Offset; K UE_offset The value is indicated by the higher-level parameter Differential Koffset; otherwise, Koffset = 0.

[0237] If terminal 101 is configured with the higher-layer parameter k-Offset, then for NPUSCH (repeated) transmissions associated with TC-RNTI, K... offset = k-Offset.

[0238] The subcarriers allocated for ACK / NACK and the value of k0 are determined by the ACK / NACK resource field in the DCI format of the corresponding NPDCCH according to Tables 6 and 7 below:

[0239] For FDD, k′0=k0; for TDD, k′0=k0-12.

[0240] Table 6 shows the k0 and ACK / NACK subcarriers corresponding to NPUSCH at a subcarrier spacing of Δf = 3.75kHz.

[0241] Table 7 shows the k0 and ACK / NACK subcarriers corresponding to NPUSCH with a subcarrier spacing of Δf = 15kHz.

[0242] Optionally, in the above embodiments, the NPDSCH and HARQ-ACK feedback are not sent within the same TDD frame, meaning they can be sent across the TDD frame period. Specifically, the HARQ-ACK feedback can be sent within a TDD frame following the TDD frame containing the NPDSCH, or within a TDD frame m TDD frames away from the TDD frame containing the NPDSCH.

[0243] Optionally, the uplink time unit in the TDD frame occupied by the HARQ-ACK mentioned above is uplink time unit 3 (UL3).

[0244] Optionally, the aforementioned third offset may be configured or indicated by the network device 102, or it may be agreed upon by the protocol.

[0245] Optionally, the aforementioned third offset (K1_offset) can be equal to the terminal-specific third offset (represented by K1_UE_offset), that is, K1_offset = K1_UE_offset.

[0246] Optionally, the aforementioned third offset (K1_offset) can be equal to the cell-specific third offset (represented by K1_cell_offset), that is, K1_offset = K1_cell_offset.

[0247] Optionally, the aforementioned third offset (K1_offset) can be equal to the sum of the terminal-specific third offset and the cell-specific third offset, that is, K1_offset = K1_cell_offset + K1_UE_offset.

[0248] Among them, the terminal-specific third offset (K1_UE_offset) corresponds to terminal 101, and the cell-specific third offset (K1_cell_offset) corresponds to the serving cell where terminal 101 is located.

[0249] Optionally, K1_cell_offset can be indicated by the higher-layer parameter k-Offset; K1_UE_offset can be indicated by the higher-layer parameter Differential Koffset. Alternatively, these two parameters can be determined jointly by the terminal and the network device through a protocol agreement. Alternatively, the third offset K1_offset can be set to a fixed value within a certain range.

[0250] The value range of K1_offset is (0...K1_offset_max), and K1_offset_max is the maximum value of K1_cell_offset + K1_UE_offset.

[0251] It should be noted that in the above embodiments, the third offset can be determined based on at least one of a cell-specific third offset and a terminal-specific third offset. The cell-specific third offset provides a cell-level reference time offset to distribute the uplink transmission times of different terminals and avoid conflicts. Furthermore, the terminal-specific third offset provides each terminal with an offset relative to the cell-specific third offset, enabling finer time adjustment. This configuration avoids uplink transmission conflicts and improves transmission efficiency.

[0252] In some embodiments, a new reference point (a fourth time-domain resource in this embodiment) and a new fourth offset (represented by K1_offset) can be set. Based on the second time-domain resource and the fourth offset, the second parameter mentioned above can be determined. By setting the second time-domain resource and the fourth offset, the transmission time of the HARQ-ACK feedback of terminal 101 can be ensured to be aligned with the 90ms TDD frame structure.

[0253] The second temporal resource mentioned above refers to the first available temporal resource whose interval with NPDSCH meets the requirements (the granularity of this temporal resource can be a slot or a subframe, etc., without limitation). The fourth offset mentioned above is used to indicate the number of subframes between the second temporal resource mentioned above and the first subframe occupied by the HARQ-ACK feedback mentioned above.

[0254] The requirement mentioned above can mean that sufficient protection time slots need to be reserved between the end of NPDSCH and the start of HARQ-ACK feedback.

[0255] Optionally, in the above embodiments, the NPDSCH and HARQ-ACK feedback are not sent within the same TDD frame, meaning they can be sent across the TDD frame period. Specifically, the HARQ-ACK feedback can be sent within a TDD frame following the TDD frame containing the NPDSCH, or within a TDD frame m TDD frames away from the TDD frame containing the NPDSCH.

[0256] Optionally, the uplink time unit in the TDD frame occupied by the HARQ-ACK mentioned above is uplink time unit 3 (UL3).

[0257] Optionally, the aforementioned fourth offset may be configured or indicated by the network device 102, or it may be agreed upon by the protocol.

[0258] Optionally, the aforementioned fourth offset (K1_offset) can be equal to the terminal-specific fourth offset (represented by K1_UE_offset), that is, K1_offset = K1_UE_offset.

[0259] Optionally, the aforementioned fourth offset (K1_offset) can be equal to the cell-specific fourth offset (represented by K1_cell_offset), that is, K1_offset = K1_cell_offset.

[0260] Optionally, the aforementioned fourth offset (K1_offset) can be equal to the sum of the terminal-specific fourth offset and the cell-specific fourth offset, that is, K1_offset = K1_cell_offset + K1_UE_offset.

[0261] Among them, the terminal-specific fourth offset (K1_UE_offset) corresponds to terminal 101, and the cell-specific fourth offset (K1_cell_offset) corresponds to the serving cell where terminal 101 is located.

[0262] Optionally, the cell-specific fourth offset (K1_cell_offset) can be indicated by the higher-layer parameter k-Offset; the terminal-specific fourth offset (K1_UE_offset) can be indicated by the higher-layer parameter Differential Koffset. Alternatively, these two parameters can be determined jointly by the terminal and network equipment through a protocol agreement. Alternatively, the fourth offset (K1_offset) can be set to a fixed value within a certain range.

[0263] The fourth offset (K1_offset) has a value range of (0...K1_offset_max), where K1_offset_max is the maximum value of the cell-specific fourth offset plus the terminal-specific fourth offset.

[0264] In some embodiments, the value of the fourth offset can be 0, either by protocol preset or network configuration.

[0265] In some embodiments, the second parameter can also be used to indicate the number of subframes between the last subframe occupied by NPDSCH and the second reference subframe. Further, the temporal resources occupied by the HARQ-ACK feedback are located in the first available uplink time unit after the second reference subframe. That is, terminal 101 can send the HARQ-ACK feedback within the first available uplink time unit after the second reference subframe.

[0266] That is, the aforementioned second parameter can reuse the traditional definition and determination method (as an example, it can be as shown in the value and determination method of the fifth parameter in the previous embodiment, which will not be repeated here), and the second reference subframe can be determined based on the aforementioned second parameter. Further, the terminal 101 performs HARQ-ACK feedback transmission in TDD mode on the first available uplink time unit after the second reference subframe.

[0267] In some embodiments, the NPUSCH carrying the HARQ-ACK described above may be repeatedly transmitted.

[0268] In some embodiments, for repetitive NPUSCH transmissions, network device 102 can be configured such that at least one repetition of terminal 101 occurs within uplink time unit 3 (UL3) of a 90ms TDD frame. Alternatively, terminal 101 may expect at least one repetition to occur within uplink time unit 3 (UL3) of a 90ms TDD frame.

[0269] In step S2104, terminal 101 determines the third parameter.

[0270] In some embodiments, the third parameter (represented by K2) is used to indicate the number of subframes between the last subframe occupied by NPDCCH and the first subframe occupied by NPUSCH.

[0271] Among them, the NPDCCH carries the DCI, and the NPUSCH is the NPUSCH scheduled by the DCI.

[0272] That is, the third time interval determined by the third parameter mentioned above refers to the time interval from when the terminal 101 finishes receiving the NPDCCH carrying uplink scheduling DCI to when the terminal 101 starts sending the NPUSCH scheduled by the DCI.

[0273] As an example, when the terminal 101 detects, on a given serving cell, the NPDCCH ending at subframe n that is sent to the terminal, the terminal 101 shall start sending the corresponding NPUSCH after subframe n+K2. The transmission of the corresponding NPUSCH is performed in N consecutive downlink subframes ni, where i=0,1,...,N-1. Wherein, subframe n is the last subframe of NPDCCH transmission, which is determined by the starting subframe of NPDCCH transmission and the DCI subframe repetition number field in the corresponding DCI; subframes ni (i=0,1,...,N-1) are N consecutive uplink subframes, and n0<n1<...,nN-1. Subframe n0 is the first available downlink subframe starting after the end of subframe n+K2. K2 is the number of subframes from subframe n (the last subframe of NPDCCH transmission) to the first subframe n0 of NPUSCH transmission.

[0274] In some embodiments, the value of the third parameter mentioned above can be redefined based on the frame structure of TDD mode and the basic requirements between NPDCCH transmission and NPUSCH transmission.

[0275] Considering that in the design of TDD frame structure, an appropriate guard period needs to be reserved to ensure sufficient time delay between uplink and downlink handover and avoid signal overlap. Therefore, when designing the third parameter mentioned above, it is necessary to ensure that the time interval between the NPDCCH and the corresponding NPUSCH meets the requirement of the guard period.

[0276] Understandably, due to the frame structure of TDD mode, the transmission of NPDCCH and NPUSCH will not occur within the same TDD frame; that is, NPDCCH transmission and its NPUSCH transmission need to cross TDD frames. Specifically, the aforementioned NPUSCH can be transmitted in a TDD frame following the TDD frame containing the aforementioned NPDCCH, or in a TDD frame separated from the TDD frame containing the NPDCCH by m TDD frames. In this case, based on the TDD frame structure and considering the requirements of guard slots, the interval between the subframe ending at downlink time unit DL3 in the current TDD frame and the subframe starting at uplink time unit UL3 in the next TDD frame is approximately 54 subframes, while the maximum round-trip delay for LEO is approximately 41 subframes. Therefore, among the possible values ​​of the third parameter K2, the minimum value is 54, and the maximum value can be 62-N+90m, where N is the number of subframes occupied by HARQ-ACK, m is the number of TDD frames between the 90ms TDD frame containing NPDCCH and the 90ms TDD frame containing NPUSCH, and m is a non-negative integer. For example, the candidate value of the third parameter K21 can be defined as k2 INTEGER(54...62-N)+90m, where INTEGER indicates that the value of K2 is an integer.

[0277] Optionally, the downlink time unit occupied by the NPDCCH is downlink time unit 3 (DL3).

[0278] Optionally, the uplink time unit occupied by the above NPUSCH is uplink time unit 3 (UL3).

[0279] Optionally, the value of the third parameter mentioned above should also take into account the subcarrier spacing (SCS).

[0280] As an example, based on the above considerations, a possible definition of the third parameter can be shown in Table 8 below.

[0281] Table 8. Third parameter K2 under TDD

[0282] In some embodiments, terminal 101 can base its actions on a scheduling delay information field: I Delay The value of K2 is obtained by querying the table specified in the protocol and then obtaining the corresponding value of the third parameter K2 mentioned above.

[0283] In some embodiments, a fifth offset (which can be represented by K2_offset) can be set to determine the third parameter based on the sixth parameter. Setting the fifth offset can ensure that the transmission time of the NPUSCH of terminal 101 is aligned with the 90ms TDD frame structure.

[0284] The sixth parameter indicates the number of subframes between the third reference subframe and the last subframe occupied by the NPDCCH. The fifth offset indicates the number of subframes between the third reference subframe and the first subframe occupied by the NPUSCH.

[0285] Optionally, the sixth parameter mentioned above can reuse the traditional settings, and the third reference subframe mentioned above is a subframe determined based on the existing parameter values.

[0286] For example, the value of the sixth parameter mentioned above and the method of determining it can be as follows:

[0287] When terminal 101 detects an NPDCCH with DCI format N0 ending in subframe n on a given serving cell, and this NPDCCH schedules an NPUSCH to be sent to terminal 101, terminal 101 should perform the corresponding NPUSCH transmission after the following times:

[0288] For FDD, the sixth parameter is k0+K offset That is, the third reference subframe is n+k0+K offset ;

[0289] For TDD, the sixth parameter is 8+k′0, which means the k0 uplink subframes after the third reference subframe n+8.

[0290] Terminal 101 should use NPUSCH format 1 to transmit information based on NPDCCH in N consecutive uplink time slots ni (i = 0, 1, ..., N-1), where:

[0291] Subframe n is the last subframe of the NPDCCH transmission, determined by the starting subframe of the NPDCCH transmission and the repeated digital segment of the DCI subframe in the corresponding DCI.

[0292] For FDD, n0 is the subframe n+k0+K. offset The first uplink time slot that begins after the end;

[0293] For TDD, n0 is the first uplink slot after k0 uplink subframes after subframe n+8 ends.

[0294] Among them, the above K offset The value is determined by the following rules:

[0295] If terminal 101 is configured with the higher-level parameter k-Offset, then K offset =K cell_offset -K UE_offset , where: K cell_offset Indicated by the high-level parameter k-Offset; K UE_offset The value is indicated by the higher-level parameter Differential Koffset; otherwise, Koffset = 0.

[0296] If terminal 101 is configured with the higher-layer parameter k-Offset, then for NPUSCH (repeated) transmissions associated with TC-RNTI, K... offset = k-Offset.

[0297] The value of k0 is determined by the scheduling delay field (I) in the corresponding DCI. Delay Determine based on Table 9 (for FDD) and Table 10 (for TDD):

[0298] Table 9 shows the k0 corresponding to DCI format N0 under FDD.

[0299] Table 10. k0 corresponding to DCI format N0 under TDD

[0300] Optionally, in the above embodiments, the NPDCCH and NPUSCH are not transmitted within the same TDD frame, meaning they can be transmitted across the TDD frame period. Specifically, the NPUSCH can be transmitted in a TDD frame following the TDD frame containing the NPDCCH, or in a TDD frame m TDD frames away from the TDD frame containing the NPDCCH.

[0301] Optionally, the uplink time unit in the TDD frame occupied by the above NPUSCH is uplink time unit 3 (UL3).

[0302] Optionally, the aforementioned fifth offset may be configured or indicated by the network device 102, or it may be agreed upon by the protocol.

[0303] Optionally, the aforementioned fifth offset (K2_offset) can be equal to the terminal-specific fifth offset (represented by K2_UE_offset), that is, K2_offset = K2_UE_offset.

[0304] Optionally, the aforementioned fifth offset (K2_offset) can be equal to the cell-specific fifth offset (represented by K2_cell_offset), that is, K2_offset = K2_cell_offset.

[0305] Optionally, the aforementioned fifth offset (K2_offset) can be equal to the sum of the terminal-specific fifth offset and the cell-specific fifth offset, that is, K2_offset = K2_cell_offset + K2_UE_offset.

[0306] Among them, the terminal-specific fifth offset (K2_UE_offset) corresponds to terminal 101, and the cell-specific fifth offset (K2_cell_offset) corresponds to the serving cell where terminal 101 is located.

[0307] Optionally, K2_cell_offset can be indicated by the higher-layer parameter k-Offset; K2_UE_offset can be indicated by the higher-layer parameter Differential Koffset. Alternatively, these two parameters can be determined jointly by the terminal and network device through a protocol agreement. Alternatively, the fifth offset K2_offset can be set to a fixed value within a certain range.

[0308] The value range of K2_offset is (0...K2_offset_max), and K2_offset_max is the maximum value of K2_cell_offset + K2_UE_offset.

[0309] It should be noted that in the above embodiments, the fifth offset can be determined based on at least one of a cell-specific fifth offset and a terminal-specific fifth offset. The cell-specific fifth offset provides a cell-level reference time offset to distribute the uplink transmission times of different terminals and avoid conflicts. Furthermore, the terminal-specific fifth offset provides each terminal with an offset relative to the cell-specific fifth offset, enabling finer time adjustment. This configuration avoids uplink transmission conflicts and improves transmission efficiency.

[0310] In some embodiments, a new reference point (a fourth time-domain resource in this embodiment) and a new sixth offset (represented by K2_offset) can be set. Based on the third time-domain resource and the sixth offset, the aforementioned third parameter is determined. By setting the aforementioned third time-domain resource and the aforementioned sixth offset, the transmission time of the NPUSCH of terminal 101 can be ensured to be aligned with the 90ms TDD frame structure.

[0311] The aforementioned third temporal resource refers to the first available temporal resource whose interval with the NPDCCH meets the requirements (the granularity of this temporal resource can be a slot or a subframe, etc., without limitation). The aforementioned sixth offset is used to indicate the number of subframes between the aforementioned third temporal resource and the first subframe occupied by the aforementioned NPUSCH.

[0312] The requirement mentioned above can mean that sufficient protection time slots need to be reserved between the end of NPDCCH and the start of NPUSCH.

[0313] Optionally, in the above embodiments, the NPDCCH and NPUSCH are not transmitted within the same TDD frame, meaning they can be transmitted across the TDD frame period. Specifically, the NPUSCH can be transmitted in a TDD frame following the TDD frame containing the NPDCCH, or in a TDD frame m TDD frames away from the TDD frame containing the NPDCCH.

[0314] Optionally, the uplink time unit in the TDD frame occupied by the HARQ-ACK mentioned above is uplink time unit 3 (UL3).

[0315] Optionally, the aforementioned sixth offset may be configured or indicated by the network device 102, or it may be agreed upon by the protocol.

[0316] Optionally, the aforementioned sixth offset (K2_offset) can be equal to the terminal-specific sixth offset (represented by K2_UE_offset), that is, K2_offset = K2_UE_offset.

[0317] Optionally, the aforementioned sixth offset (K2_offset) can be equal to the cell-specific sixth offset (represented by K2_cell_offset), that is, K2_offset = K2_cell_offset.

[0318] Optionally, the aforementioned sixth offset (K2_offset) can be equal to the sum of the terminal-specific sixth offset and the cell-specific sixth offset, that is, K2_offset = K2_cell_offset + K2_UE_offset.

[0319] Among them, the terminal-specific sixth offset (K2_UE_offset) corresponds to terminal 101, and the cell-specific sixth offset (K2_cell_offset) corresponds to the serving cell where terminal 101 is located.

[0320] Optionally, the cell-specific sixth offset (K2_cell_offset) can be indicated by the higher-layer parameter k-Offset; the terminal-specific sixth offset (K2_UE_offset) can be indicated by the higher-layer parameter Differential Koffset. Alternatively, these two parameters can be determined jointly by the terminal and network equipment through a protocol agreement. Alternatively, the sixth offset (K2_offset) can be set to a fixed value within a given range.

[0321] The sixth offset (K2_offset) has a value range of (0...K2_offset_max), where K2_offset_max is the maximum value of the cell-specific sixth offset plus the terminal-specific sixth offset.

[0322] In some embodiments, the value of the sixth offset can be 0, either by protocol preset or network configuration.

[0323] In some embodiments, the third parameter can also be used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the third reference subframe. Further, the temporal resources occupied by the NPUSCH are located in the first available uplink time unit after the third reference subframe. That is, terminal 101 can transmit the NPUSCH within the first available uplink time unit after the third reference subframe.

[0324] That is, the aforementioned third parameter can reuse the traditional definition and determination method (as an example, it can be as shown in the value and determination method of the sixth parameter in the aforementioned embodiment, which will not be repeated here), and the third reference subframe can be determined based on the aforementioned third parameter. Further, the terminal 101 performs NPUSCH transmission in TDD mode on the first available uplink time unit after the third reference subframe.

[0325] In some embodiments, the NPUSCH described above may be sent repeatedly.

[0326] In some embodiments, for repetitive NPUSCH transmissions, network device 102 can be configured such that at least one repetition of terminal 101 occurs within uplink time unit 3 (UL3) of a 90ms TDD frame. Alternatively, terminal 101 may expect at least one repetition to occur within uplink time unit 3 (UL3) of a 90ms TDD frame.

[0327] In some embodiments, the format of the DCI carried in the NPDCCH can be any one of N0, N1, and N2, wherein different types of DCI have different lengths.

[0328] Optionally, the types of DCIs scheduled for different channels can be the same or different.

[0329] In some embodiments, terminal 101 may parse the received DCI based on a first number of bits.

[0330] Optionally, the first number of bits can be the length of any one of the multiple types of DCIs mentioned above.

[0331] Optionally, the first number of bits can be the length of the DCI with the smallest length among the multiple types of DCIs.

[0332] Optionally, the first number of bits can be the length of the longest DCI among the multiple types of DCIs mentioned above.

[0333] As an example, a new scheduling delay / HARQ-ACK resource field is added to DCI format N2 to indicate K0 / K1 / K2, and bits are allocated to this new field. Allocating bits will change the DCI length (or size) of DCI format N2. To avoid excessive DCI blind detection (the number of blind detections is doubled due to inconsistent DCI sizes), bit length alignment needs to be considered. Several DCI length alignment schemes can be considered, but are not limited to:

[0334] 1) Align the DCI length to a specific DCI format:

[0335] If the length of DCI format N2 is less than the length of DCI format N0 / N1, several zero padding bits need to be added to the end of DCI format N2 during parsing until they are equal. If the length of DCI format N2 is greater than the length of DCI format N0 / N1, several MSB bits of the "scheduling delay / HARQ-ACK resource" field of DCI format N2 need to be truncated until they are equal.

[0336] 2) Align with the longer DCI length:

[0337] If the lengths of DCI formats N0 / 1 / 2 are not equal, then the shorter DCI needs to be padded with several zero bits at the end until their lengths are equal.

[0338] 3) Align with shorter DCI lengths:

[0339] If the lengths of DCI format N0 / 1 / 2 are not equal, the MSB bits of the "scheduling delay / HARQ-ACK resource" field in several long DCIs need to be truncated until their lengths are equal.

[0340] In some embodiments, the terms “eNB”, “gNB”, “base station”, and “NG-RAN node” can be used interchangeably.

[0341] In some embodiments, the terms "carrier," "band," and "frequency" can be used interchangeably.

[0342] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0343] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0344] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0345] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0346] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0347] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.

[0348] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angular degree", "antenna", "antenna element", and "panel" can be used interchangeably.

[0349] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0350] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0351] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.

[0352] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0353] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0354] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0355] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0356] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0357] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0358] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.

[0359] The communication method involved in the embodiments of this application may include at least one of steps S2101 to S2104. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, step S2103 can be implemented as an independent embodiment, step S2104 can be implemented as an independent embodiment, steps S2101+S2102 can be implemented as an independent embodiment, steps S2101+S2103 can be implemented as an independent embodiment, steps S2101+S2104 can be implemented as an independent embodiment, steps S2102+S2103 can be implemented as an independent embodiment, and steps S2102+S2104 can be implemented as an independent embodiment. The implementation can be carried out in the following embodiments. Steps S2103+S2104 can be implemented as independent embodiments, as can steps S2102+S2103+S2104, S2101+S2102+S2103, S2101+S2102+S2104, S2101+S2103+S2104, and so on, but are not limited thereto.

[0360] In some embodiments, steps S2102, S2103, and S2104 may be performed in an interchangeable order or simultaneously.

[0361] In some embodiments, steps S2101, S2103, and S2104 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0362] In some embodiments, steps S2101, S2102, and S2104 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0363] In some embodiments, steps S2101, S2102, and S2103 are optional, and one or more of these steps may be omitted or substituted in different embodiments.

[0364] In some embodiments, other alternative implementations may be described before or after the specification corresponding to FIG2A.

[0365] Figure 3A is an interactive schematic diagram of a communication method according to an embodiment of this application. As shown in Figure 3A, the embodiment of this application relates to a communication method, which includes:

[0366] In step S3101, terminal 101 determines at least one of the first parameter, the second parameter, and the third parameter.

[0367] In some embodiments, at least one of a first parameter, a second parameter, and a third parameter is determined based on protocol conventions or first information; wherein, the first parameter is used to determine a first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH, the NPDSCH being scheduled by downlink control information DCI carried on the NPDCCH; the second parameter is used to determine a second time interval, which is the time interval between the NPDSCH and the corresponding hybrid automatic repeat request acknowledgment (HARQ-ACK) feedback; the third parameter is used to determine a third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, the NPUSCH being scheduled by DCI carried on the NPDCCH; the first information is sent by the network device, and the NPDCCH, the NPDSCH, the HARQ-ACK feedback, and the NPUSCH are all located in a time division duplex (TDD) frame.

[0368] In some embodiments, the first parameter is used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the first subframe occupied by the NPDSCH.

[0369] Optionally, the NPDSCH and NPDCCH are transmitted within a single TDD frame; the maximum value among the candidate values ​​of the first parameter is determined based on the number of subframes included in a downlink time unit of the TDD frame and the number of subframes occupied by the NPDCCH.

[0370] Optionally, the NPDSCH and NPDCCH are transmitted in different TDD frames; the maximum value among the candidate values ​​of the first parameter is determined based on the number of subframes included in a downlink time unit of the TDD frame, the number of subframes occupied by the NPDCCH, the number of subframes occupied by the TDD frame, the number of TDD frames between the NPDSCH and the NPDCCH, and the number of subframes between the frame header of the TDD frame and the start point of the downlink time unit occupied by the NPDSCH.

[0371] Optionally, the first parameter is determined based on the fourth parameter and the first offset; the NPDSCH is located within the downlink time unit 3 of the TDD frame; wherein, the fourth parameter is used to indicate the number of subframes between the first reference subframe and the last subframe occupied by the NPDSCH; the first offset is used to indicate the number of subframes between the first reference subframe and the first subframe occupied by the NPDSCH; the first offset is configured by the network device or is agreed upon by the protocol.

[0372] Optionally, the first offset is equal to a terminal-specific first offset; or, the first offset is equal to a cell-specific first offset; or, the first offset is equal to the sum of the terminal-specific first offset and the cell-specific first offset; wherein the terminal-specific first offset corresponds to the terminal, and the cell-specific first offset corresponds to the serving cell where the terminal is located.

[0373] Optionally, the first parameter is determined based on the first time domain resource and the second offset; the NPDSCH is located within the downlink time unit 3 of the TDD frame; wherein, the first time domain resource is the first available time domain resource whose interval with the NPDSCH meets the requirements; the second offset is used to indicate the number of subframes between the first time domain resource and the first subframe occupied by the NPDSCH; the second offset is configured by the network device or is agreed upon by the protocol.

[0374] Optionally, the second offset is equal to a terminal-specific second offset; or, the second offset is equal to a cell-specific second offset; or, the second offset is equal to the sum of the terminal-specific second offset and the cell-specific second offset; wherein the terminal-specific second offset corresponds to the terminal, and the cell-specific second offset corresponds to the serving cell where the terminal is located.

[0375] In some embodiments, the second parameter is used to indicate the number of subframes between the last subframe occupied by the NPDSCH and the first subframe occupied by the HARQ-ACK feedback.

[0376] Optionally, the HARQ-ACK feedback and the NPDSCH are sent in different TDD frames; the maximum value among the candidate values ​​of the second parameter is determined based on the uplink time unit occupied by the HARQ-ACK feedback and the number of subframes occupied by the HARQ-ACK feedback.

[0377] Optionally, the second parameter is determined based on the fifth parameter and the third offset; the HARQ-ACK feedback is located within the uplink time unit 3 of the TDD frame; wherein, the fifth parameter is used to indicate the number of subframes between the second reference subframe and the last subframe occupied by the NPDSCH; the third offset is used to indicate the number of subframes between the second reference subframe and the first subframe occupied by the HARQ-ACK feedback; the third offset is configured by the network device or is agreed upon by the protocol.

[0378] Optionally, the aforementioned third offset is equal to a terminal-specific third offset; or, the aforementioned third offset is equal to a cell-specific third offset; or, the aforementioned third offset is equal to the sum of the aforementioned terminal-specific third offset and the aforementioned cell-specific third offset; wherein, the aforementioned terminal-specific third offset corresponds to the aforementioned terminal, and the aforementioned cell-specific third offset corresponds to the serving cell where the aforementioned terminal is located.

[0379] Optionally, the second parameter is determined based on the second time-domain resource and the fourth offset; the HARQ-ACK feedback is located within the uplink time unit 3 of the TDD frame; wherein, the second time-domain resource is the first available time-domain resource whose interval with the NPDSCH meets the requirements; the fourth offset is used to indicate the number of subframes between the second time-domain resource and the first subframe occupied by the HARQ-ACK feedback; the fourth offset is configured by the network device or is agreed upon by the protocol.

[0380] Optionally, the aforementioned fourth offset is equal to the terminal-specific fourth offset; or, the aforementioned fourth offset is equal to the cell-specific fourth offset; or, the aforementioned fourth offset is equal to the sum of the aforementioned terminal-specific fourth offset and the aforementioned cell-specific fourth offset; wherein, the aforementioned terminal-specific fourth offset corresponds to the aforementioned terminal, and the aforementioned cell-specific fourth offset corresponds to the serving cell where the aforementioned terminal is located.

[0381] In some embodiments, the third parameter is used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the first subframe occupied by the NPUSCH.

[0382] Optionally, the NPUSCH and NPDCCH are transmitted in different TDD frames; the maximum value among the candidate values ​​of the third parameter is determined based on the uplink time unit occupied by the NPUSCH and the number of subframes occupied by the NPUSCH.

[0383] Optionally, the third parameter is determined based on the sixth parameter and the fifth offset; the NPUSCH is located within the uplink time unit 3 of the TDD frame; wherein, the sixth parameter is used to indicate the number of subframes between the third reference subframe and the last subframe occupied by the NPDCCH; the fifth offset is used to indicate the number of subframes between the third reference subframe and the first subframe occupied by the NPUSCH; the fifth offset is configured by the network device or is agreed upon by the protocol.

[0384] Optionally, the aforementioned fifth offset is equal to the terminal-specific fifth offset; or, the aforementioned fifth offset is equal to the cell-specific fifth offset; or, the aforementioned fifth offset is equal to the sum of the aforementioned terminal-specific fifth offset and the aforementioned cell-specific fifth offset; wherein, the aforementioned terminal-specific fifth offset corresponds to the aforementioned terminal, and the aforementioned cell-specific fifth offset corresponds to the serving cell where the aforementioned terminal is located.

[0385] Optionally, the third parameter is determined based on the third time-domain resource and the sixth offset; the NPUSCH is located within the uplink time unit 3 of the TDD frame; wherein, the third time-domain resource is the first available time-domain resource whose interval with the NPDCCH meets the requirements; the sixth offset is used to indicate the number of subframes between the third time-domain resource and the first subframe occupied by the NPUSCH; the sixth offset is configured by the network device or is agreed upon by the protocol.

[0386] Optionally, the sixth offset is equal to the terminal-specific sixth offset; or, the sixth offset is equal to the cell-specific sixth offset; or, the sixth offset is equal to the sum of the terminal-specific sixth offset and the cell-specific fourth offset; wherein, the terminal-specific sixth offset corresponds to the terminal, and the cell-specific fourth offset corresponds to the serving cell where the terminal is located.

[0387] In some embodiments, at least one of the following is satisfied: the temporal resources occupied by the NPDSCH are located in the first available downlink time unit after the first reference subframe, wherein the first parameter is used to indicate the number of subframes between the first reference subframe and the last subframe occupied by the NPDCCH; the temporal resources occupied by the HARQ-ACK feedback are located in the first available uplink time unit after the second reference subframe, wherein the second parameter is used to indicate the number of subframes between the second reference subframe and the last subframe occupied by the NPDSCH; the temporal resources occupied by the NPUSCH are located in the first available uplink time unit after the third reference subframe, wherein the third parameter is used to indicate the number of subframes between the third reference subframe and the last subframe occupied by the NPDCCH.

[0388] In some embodiments, at least one of the following conditions is met: the NPDSCH is repeatedly transmitted, wherein at least one of the repeatedly transmitted NPDSCHs is located within downlink time unit 3 of the TDD frame; the NPUSCH is repeatedly transmitted, wherein at least one of the repeatedly transmitted NPUSCHs is located within uplink time unit 3 of the TDD frame.

[0389] In some embodiments, the NPDCCH carries downlink control information (DCI), the format type of the DCI is any one of N0, N1, and N2, and the length of each type of DCI is different; the method further includes: parsing the DCI based on a first number of bits; wherein the first number of bits is any one of the following: the length of any one of the multiple types of DCI; the length of the DCI with the smallest length among the multiple types of DCI; the length of the DCI with the largest length among the multiple types of DCI.

[0390] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0391] The following is an exemplary description of the methods described in the above embodiments.

[0392] In some embodiments, in NR, K0 refers to the slot interval between the downlink scheduling DCI and its scheduled PDSCH; K1 refers to the slot interval between the PDSCH and its HARQ-ACK feedback; and K2 refers to the slot interval between the uplink scheduling DCI and its scheduled PUSCH. The UE needs time to decode control information (PDCCH) and process data (PDSCH / PUSCH), and K0, K1, and K2 provide the UE with sufficient processing time.

[0393] In the embodiments of the present application, in the TDD frame structure of a satellite system, it is necessary to redesign and define K0, K1 and K2 to align with the TDD frame structure, thereby avoiding resource conflicts between uplink and downlink transmissions, and optimizing the HARQ process, resource utilization and overall system performance.

[0394] For the above problem, at least one of the following design schemes can be considered:

[0395] Key point 1: For K0, K1 and K2, it is considered to redefine the values of K0, K1 and K2.

[0396] 1-1: For K0, it is considered to redefine the value of K0, where K0 is the time interval between NPDCCH and NPDSCH.

[0397] When a UE detects, on a given serving cell, an NPDCCH with DCI format N1 and DCI format N2 that is sent to the UE and ends at subframe n, the UE shall start the corresponding NPDSCH transmission after subframe n+K0:

[0398] The corresponding NPDSCH transmission will be carried out in N consecutive NB-IoT downlink subframes ni, where i=0,1,…,N-1, and is decoded according to the information in the NPDCCH. Wherein: subframe n is the last subframe of NPDCCH transmission, which is determined by the starting subframe of NPDCCH transmission and the DCI subframe repetition number field in the corresponding DCI; subframe ni (i=0,1,…,N-1) are N consecutive NB-IoT downlink subframes, excluding subframes used for system information (SI) messages, scheduling gap (if any) or processing gap (if any), and n0<n1<…,nN-1. Subframe n0 is the first NB-IoT downlink subframe started after the end of subframe n+K0; K0 is the number of subframes between subframe n (the last subframe of NPDCCH transmission) and the first subframe n0 of NPDSCH.

[0399] The design of K0 needs to be aligned with the 90ms TDD frame structure to ensure that the transmission of NPDSCH is completed within the downlink transmission window. Meanwhile, it needs to be considered that at least a 4-millisecond transmission interval shall be reserved between the end of NPDCCH and the start of NPDSCH (NPDSCH processing starts after n+5 subframes), then the redefinition of the value of K0 can be determined by the following two ways (without limitation):

[0400] Scheme 1: Complete the reception of DCI and NPDSCH within one 90ms TDD frame.

[0401] In this manner, it is ensured that the receiving processes of DCI (NPDCCH) and PDSCH (NPDSCH) are completed within the same 90ms TDD frame. Considering that one time unit of the downlink time slot in a satellite system includes 8 subframes, and a 90ms TDD frame includes 4 downlink time units; and further considering the transmission interval of at least 4 milliseconds between the end of NPDCCH and the start of NPDSCH, therefore: the candidate values of K0 can be defined as: k0 INTEGER (5...8-x), where x is the total number of subframes for NPDCCH transmission.

[0402] Mode 2: After receiving DCI, the receiving of the scheduled NPDSCH is completed across the period of the 90ms TDD frame.

[0403] The candidate values of K0 can be defined as: K0 INTEGER (5...8-x+90×m+T), where x is the total number of subframes for NPDCCH transmission, m is an integer, and T refers to the number of frames occupied by the 90ms TDD frame from the frame header to the starting point of the downlink time unit DL3.

[0404] Therefore, redefinition of the value range of k0 can be considered, and an example of a redefined value implementation is shown in the aforementioned Table 1.

[0405] 1-2: For K1, redefining the value range of K1 is considered, wherein K1 is the time interval between NPDSCH and its HARQ-ACK feedback.

[0406] When a UE detects an NPDSCH transmission ending at NB-IoT subframe n that requires an ACK / NACK response, the UE shall start transmitting NPUSCH carrying the ACK / NACK response in subframe n+K1:

[0407] The transmission of NPUSCH carrying the ACK / NACK response will be carried out in N consecutive NB-IoT uplink subframes ni, where i=0,1,...,N-1, wherein: subframe n is the last subframe of NPDSCH transmission; subframes ni (i=0,1,...,N-1) are N consecutive NB-IoT uplink subframes, and n0<n1<...,nN-1. n0 is the first NB-IoT uplink subframe after K1 subframes following the end of subframe n; K1 is the number of NB-IoT subframes from subframe n to uplink subframe n0.

[0408] Considering that in the TDD frame structure design, an appropriate guard period needs to be reserved to ensure sufficient time delay between uplink and downlink switching and avoid signal overlap.

[0409] For a low earth orbit (LEO) satellite system, RTT (Round-Trip Time) varies according to satellite altitude: for LEO at 600km, RTT is approximately 25.77ms; for LEO at 1200km, RTT is approximately 41.77ms.

[0410] To ensure that the time interval between NPDSCH and its HARQ-ACK feedback meets the guard period requirement, and NPDSCH can only be transmitted in the downlink time unit DL3 within a 90ms TDD frame, and HARQ-ACK feedback needs to be transmitted in the uplink time unit UL3 within a 90ms TDD frame. Meanwhile, considering the 90ms TDD frame structure of the satellite system, NPDSCH transmission and its HARQ-ACK feedback are transmitted across TDD frames, that is, the HARQ-ACK feedback is transmitted on the uplink time unit UL3 in one or more TDD frames after the corresponding NPDSCH transmission. The interval between the last subframe where the downlink time domain resource DL3 ends in the current TDD frame and the starting subframe of the uplink time domain resource UL3 in the next TDD frame is approximately 54 subframes, and the maximum round-trip delay for LEO is approximately 41 subframes. Therefore:

[0411] The candidate values of K1 can be defined as: K1 INTEGER (54...62-N)+90m, where N is the number of consecutive NB-IoT uplink subframes, and m is an integer. As one of the embodiments of redefining the value, it can be as shown in Table 4 and Table 5 above.

[0412] 1-3: For K2, redefinition of the value of K2 is considered, where K2 is the time interval between the NPDCCH for scheduling uplink DCI and the PUSCH scheduled thereby.

[0413] When a UE detects an NPDCCH of DCI format N0 ending at subframe n and sent to the UE on a given serving cell, the UE shall start corresponding NPUSCH transmission from subframe n+K2:

[0414] Corresponding NPDSCH transmission will be carried out in N consecutive NB-IoT downlink subframes ni, where i=0,1,…,N-1, and decoding is performed according to the information in the NPDCCH. Wherein: subframe n is the last subframe of NPDCCH transmission, which is determined by the starting subframe of NPDCCH transmission and the DCI subframe repetition number field in the corresponding DCI; subframes ni (i=0,1,…,N-1) are N consecutive NB-IoT uplink subframes, and n0<n1<…,nN-1. n0 is the first NB-IoT uplink subframe after K2 subframes after the end of subframe n; K2 is the number of subframes from subframe n to the first subframe n0 of NPUSCH.

[0415] In the TDD frame structure design, it is necessary to reserve an appropriate guard period to ensure sufficient time delay between uplink and downlink switching and avoid signal overlap.

[0416] For low Earth orbit (LEO) satellite systems, the round-trip time (RTT) varies depending on the satellite altitude: LEO 600km: RTT is approximately 25.77ms; LEO 1200km: RTT is approximately 41.77ms.

[0417] The design of K2 needs to be aligned with the 90ms TDD frame structure. To ensure that the time interval between the NPDCCH and its scheduled NPUSCH transmissions meets the guard period requirement, and since the NPDCCH can only be transmitted in downlink time unit DL3 within a 90ms TDD frame, its scheduled NPUSCH transmission needs to be transmitted in uplink time unit UL3 within a 90ms TDD frame. Considering the 90ms TDD frame structure of the satellite system, the NPDCCH transmission and its scheduled NPUSCH transmission span across TDD frames. That is, the scheduled NPUSCH transmission will be transmitted in uplink time unit UL3 within one or more TDD frames following its NPDCCH transmission. The interval between the subframe where the downlink time domain resource DL3 ends in the current TDD frame and the subframe where the uplink time domain resource UL3 begins in the next TDD frame is approximately 54 subframes. The maximum round-trip time for LEO is approximately 41 subframes. Therefore:

[0418] The candidate value of K2 can be defined as: K2 INTEGER(54...62-N)+90m, where N is the number of consecutive NPUSCH uplink subframes, and m is an integer. One example of this redefinition is shown in Table 8 above.

[0419] Key Point 2: Consider introducing bias values ​​for K0, K1, and K2.

[0420] 2-1: For K0, consider introducing a bias value K0_offset.

[0421] The calculation formula for K0 is redefined as K0 = 5 + k0 + K0_offset. A new K0_offset is introduced to ensure that the transmission time of NPDSCH is aligned with the 90ms TDD frame structure, so that NPDSCH can be performed in the downlink transmission window DL3 (the downlink transmission window DL3 can be in the same 90ms TDD frame as the DCI receiving that schedules the NPDSCH transmission, or delayed to the m frames after the 90ms TDD frame where the DCI receiving that schedules the NPDSCH transmission is located).

[0422] The value of K0_offset can be determined by the following parameters:

[0423] 1) K0_offset = K0_cell_offset; or,

[0424] 2) K0_offset = K0_UE_offset; or,

[0425] 3) K0_offset=K0_cell_offset+K0_UE_offset.

[0426] The parameter values ​​are determined in the following ways (not limited to): K0_cell_offset is indicated by the higher layer parameter k-Offset; K0_UE_offset is indicated by the higher layer parameter Differential Koffset; or these two parameters are determined by the terminal and the base station through a protocol agreement; or K0_offset is set to a fixed value within the range of values.

[0427] Among them, the maximum value of K0_cell_offset+K0_UE_offset is K0_offset_max, so the value range of K0_offset is (0...K0_offset_max).

[0428] 2-2: For K1, consider introducing a bias value K1_offset.

[0429] Redefine the formula for calculating K1, i.e., K1=n+k′0+K offset -1+K1_offset introduces a new K1_offset to ensure that the transmission time of HARQ-CK feedback in NPDSCH transmission is aligned with the 90ms TDD frame structure, so that HARQ-CK feedback can be performed in the uplink transmission window UL3.

[0430] The value of K1_offset can be determined by the following parameters:

[0431] 1) K1_offset = K1_cell_offset; or,

[0432] 2) K1_offset = K1_UE_offset; or,

[0433] 3) K1_offset=K1_cell_offset+K1_UE_offset.

[0434] The parameter values ​​are determined in the following ways (not limited to): K1_cell_offset is indicated by the higher layer parameter k-Offset; K1_UE_offset is indicated by the higher layer parameter Differential Koffset; or these two parameters are determined by the terminal and the base station through a protocol agreement; or K1_offset is set to a fixed value within the range of values.

[0435] Among them, the maximum value of K1_cell_offset+K1_UE_offset is K1_offset_max, so the value range of K1_offset is (0...K1_offset_max).

[0436] 2-3: For K2, consider introducing a bias value K2_offset.

[0437] Redefine the formula for calculating K2, i.e., K1 = n + k0 + K offset +K2_offset introduces a new K2_offset to ensure that the transmission time of NPUSCH is aligned with the 90ms TDD frame structure, so that the scheduled NPUSCH transmission is transmitted in the uplink time unit UL3 within a 90ms TDD frame.

[0438] The value of K2_offset can be determined by the following parameters:

[0439] 1) K2_offset = K2_cell_offset; or,

[0440] 2) K2_offset = K2_UE_offset; or,

[0441] 3) K2_offset=K2_cell_offset+K2_UE_offset.

[0442] The parameter values ​​are determined in the following ways (not limited to): K2_cell_offset is indicated by the higher-layer parameter k-Offset; K2_UE_offset is indicated by the higher-layer parameter Differential Koffset; or these two parameters are determined by the terminal and the base station through a protocol agreement; or K2_offset is set to a fixed value within the range of values.

[0443] Among them, the maximum value of K2_cell_offset+K2_UE_offset is K2_offset_max, so the value range of K2_offset is (0...K2_offset_max).

[0444] Key Point 3: For K0, K1 and K2, consider introducing new reference points and offset values.

[0445] 3-1: For K0, define a new reference point and K0_offset to ensure a transmission interval of at least 4 milliseconds between the end of NPDCCH and the start of NPDSCH, while simplifying the current 36.213 protocol design. This reference point is defined as the first available downlink time-domain resource (in units of subframes or slots) reserved to guarantee the 4-millisecond transmission interval. In this case, the reference point can be determined as subframe n+5 (the 5th subframe after the end of NPDCCH transmission).

[0446] At the same time, the terminal expects at least one repetition of NPDSCH to be scheduled in downlink time unit DL3, or the base station to schedule at least one NPDSCH repetition in downlink time unit DL3.

[0447] K0_offset is defined as the number of subframes between the reference point and the first subframe n0 of NPDSCH.

[0448] The value of K0_offset can be determined by the following parameters:

[0449] 1) K0_offset = K0_cell_offset; or,

[0450] 2) K0_offset = K0_UE_offset; or,

[0451] 3) K0_offset=K0_cell_offset+K0_UE_offset.

[0452] The parameter values ​​are determined in the following ways (not limited to): K0_cell_offset is indicated by the higher layer parameter k-Offset; K0_UE_offset is indicated by the higher layer parameter Differential Koffset; or these two parameters are determined by the terminal and the base station through a protocol agreement; or K0_offset is set to a fixed value within the range of values.

[0453] Among them, the maximum value of K0_cell_offset+K0_UE_offset is K0_offset_max, so the value range of K0_offset is (0...K0_offset_max).

[0454] 3-2: Cancel the original value of K1, redefine a new reference point and K1_offset to ensure alignment with the 90ms TDD frame structure. At the same time, the terminal expects the HARQ-ACK feedback of NPDSCH to be scheduled for transmission on the uplink time unit UL3 of the 90ms TDD frame structure, or the base station to schedule the HARQ-ACK feedback of NPDSCH on the uplink time unit UL3 of the 90ms TDD frame structure.

[0455] The reference point is defined as the starting subframe of uplink time unit UL3 within the 90ms TDD frame where the HARQ-ACK feedback is located after the NPDSCH transmission.

[0456] K1_offset is defined as the number of subframes between the reference point and the first subframe n0 of the HARQ-ACK feedback.

[0457] The value of K1_offset can be determined by the following parameters:

[0458] 1) K1_offset = K1_cell_offset; or,

[0459] 2) K1_offset = K1_UE_offset; or,

[0460] 3) K1_offset=K1_cell_offset+K1_UE_offset.

[0461] The parameter values ​​are determined in the following ways (not limited to): K1_cell_offset is indicated by the higher layer parameter k-Offset; K1_UE_offset is indicated by the higher layer parameter Differential Koffset; or these two parameters are determined by the terminal and the base station through a protocol agreement; or K1_offset is set to a fixed value within the range of values.

[0462] Among them, the maximum value of K1_cell_offset+K1_UE_offset is K1_offset_max, so the value range of K1_offset is (0...K1_offset_max).

[0463] 3-3: Cancel the original value of K2, redefine a new reference point and K2_offset to ensure alignment with the 90ms TDD frame structure. At the same time, the terminal expects the NPUSCH scheduled by the NPDCCH to be scheduled for transmission on the uplink time unit UL3 of the 90ms TDD frame structure, or the base station to configure the NPUSCH scheduled by the NPDCCH on the uplink time unit UL3 of the 90ms TDD frame structure.

[0464] The reference point is defined as the starting subframe of uplink time unit UL3 within the 90ms TDD frame where the scheduled NPUSCH transmission occurs after the NPDCCH transmission.

[0465] K2_offset is defined as the number of subframes between the reference point and the first subframe n0 of its scheduled NPUSCH transmission.

[0466] The value of K2_offset can be determined by the following parameters:

[0467] 1) K2_offset = K2_cell_offset; or,

[0468] 2) K2_offset = K2_UE_offset; or,

[0469] 3) K2_offset=K2_cell_offset+K2_UE_offset.

[0470] The parameter values ​​are determined in the following ways (not limited to): K2_cell_offset is indicated by the higher-layer parameter k-Offset; K2_UE_offset is indicated by the higher-layer parameter Differential Koffset; or these two parameters are determined by the terminal and the base station through a protocol agreement; or K2_offset is set to a fixed value within the range of values.

[0471] Among them, the maximum value of K2_cell_offset+K2_UE_offset is K2_offset_max, so the value range of K2_offset is (0...K2_offset_max).

[0472] Optionally, for each embodiment in point 3 above, the values ​​of K0_offset, K1_offset, and K2_offset can all be equal to 0, either preset by the protocol or configured by the base station.

[0473] Key Point 4: For K0, K1 and K2, the legacy mode is considered. NPDSCH transmission, HARQ-ACK feedback and NPUSCH transmission are carried out on the first available downlink or uplink transmission unit after the legacy reference point. For example, NPDSCH transmission is carried out on the first available downlink transmission unit DL3 after the legacy reference point (n+5).

[0474] Key Point 5: For repetitive NPDSCH / NPUSCH transmissions, the base station configuration determines that the terminal has at least one repetition transmission in a 90ms TDD Frame downlink time unit DL3 / uplink time unit UL3, or the terminal expects at least one repetition transmission in a 90ms TDD Frame downlink time unit DL3 / uplink time unit UL3.

[0475] Point 6: Consider DCI enhancements after introducing k0 and k_offset in DCI format N2.

[0476] In DCI format N2, a new scheduling delay / HARQ-ACK resource field is added to indicate K0 / 1 / 2, and bits are allocated to this new field. Allocating bits will change the DCI size of DCI format N2. To avoid excessive DCI blind detection (doubled DCI blind detection count due to inconsistent DCI size), bit length alignment needs to be considered. Several DCI length alignment schemes can be considered, but are not limited to:

[0477] 1) Align the DCI length to a specific DCI format:

[0478] If the length of DCI format N2 is less than the length of DCI format N0 / N1, several zero padding bits need to be added to the end of DCI format N2 during parsing until they are equal. If the length of DCI format N2 is greater than the length of DCI format N0 / N1, several MSB bits of the "scheduling delay / HARQ-ACK resource" field of DCI format N2 need to be truncated until they are equal.

[0479] 2) Align with the longer DCI length:

[0480] If the lengths of DCI formats N0 / 1 / 2 are not equal, then the shorter DCI needs to be padded with several zero bits at the end until their lengths are equal.

[0481] 3) Align with shorter DCI lengths:

[0482] If the lengths of DCI format N0 / 1 / 2 are not equal, the MSB bits of the "scheduling delay / HARQ-ACK resource" field in several long DCIs need to be truncated until their lengths are equal.

[0483] In some embodiments, unless contradictory, the optional implementations in this embodiment can be implemented as independent embodiments, and the optional implementations in this embodiment can also be combined arbitrarily. The technical features of different feasible implementations in this embodiment can be combined to form new optional implementations based on their inherent logical relationships.

[0484] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0485] This application also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed, which includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed, which includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0486] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0487] In this application embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0488] Figure 4A is a schematic diagram of the structure of a terminal according to an embodiment of this application. The terminal 4100 is used to execute any of the above methods. In some embodiments, as shown in Figure 4A, the terminal 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the processing module 4102 is configured to determine at least one of a first parameter, a second parameter, and a third parameter based on protocol conventions or first information; wherein the first parameter is used to determine a first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH, the NPDSCH being scheduled by the DCI carried on the NPDCCH; the second parameter is used to determine a second time interval, which is the time interval between the NPDSCH and the HARQ-ACK feedback corresponding to the NPDSCH; the third parameter is used to determine a third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, the NPUSCH being scheduled by the DCI carried on the NPDCCH; the first information is sent by the network device, and the NPDCCH, the NPDSCH, the HARQ-ACK feedback, and the NPUSCH are all located in a time division duplex (TDD) frame. Optionally, the transceiver module is used to perform at least one of the communication steps (such as step S2101, but not limited thereto) performed by terminal 101 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps (such as steps S2102, S2103, S2104, S3101, but not limited thereto) performed by terminal 101 in any of the above methods, which will not be elaborated here.

[0489] Figure 4B is a schematic diagram of the structure of a network device according to an embodiment of this application. The network device 4200 is used to perform any of the above methods. In some embodiments, as shown in Figure 4B, the network device 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module 4201 is configured to send first information to the terminal, the first information being used to determine at least one of a first parameter, a second parameter, and a third parameter; wherein, the first parameter is used to determine a first time interval, the first time interval being the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH, the NPDSCH being scheduled by the DCI carried on the NPDCCH; the second parameter is used to determine a second time interval, the second time interval being the time interval between the NPDSCH and the HARQ-ACK feedback corresponding to the NPDSCH; the third parameter is used to determine a third time interval, the third time interval being the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, the NPUSCH being scheduled by the DCI carried on the NPDCCH; the NPDCCH, the NPDSCH, the HARQ-ACK feedback, and the NPUSCH are all located in a time division duplex (TDD) frame. Optionally, the transceiver module is used to perform at least one of the communication steps (such as step S2101, but not limited thereto) performed by the network device 102 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by the network device 102 in any of the above methods, which will not be elaborated here.

[0490] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0491] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0492] In some embodiments, the processing module can be replaced by the processor, and the transceiver module can be replaced by the transceiver.

[0493] Figure 5A is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this application. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0494] As shown in Figure 5A, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0495] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., step S2101, but not limited thereto), and the processor 5101 performs at least one of other steps (e.g., step S2102, step S2103, step S2104, step S3101, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0496] In some embodiments, the communication device 5100 further includes one or more memories 5102 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5102 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5102 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5102 and can be used to receive data and / or instructions from the memory 5102 or other devices, and can be used to send data and / or instructions to the memory 5102 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5102 and send the data and / or instructions to the processor 5101.

[0497] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this application is not limited thereto, and the structure of the communication device 5100 may not be limited by FIG. 5A. The communication device may be a standalone device or a part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0498] Figure 5B is a schematic diagram of the structure of chip 5200 according to an embodiment of this application. For cases where the communication device 5100 can be a chip or a chip system, please refer to the schematic diagram of chip 5200 shown in Figure 5B, but it is not limited thereto.

[0499] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0500] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0501] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., step S2101, but not limited thereto). The interface circuit 5202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 5202 performing data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of other steps (e.g., steps S2102, S2103, S2104, S3101, but not limited thereto).

[0502] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0503] This application also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0504] This application also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0505] This application also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method, characterized in that, The method is executed by a terminal, and the method includes: Based on the agreement or the first information, determine at least one of the first parameter, the second parameter, and the third parameter; The first parameter is used to determine the first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH. The NPDSCH is scheduled by the downlink control information DCI carried on the NPDCCH. The second parameter is used to determine the second time interval, which is the time interval between the NPDSCH and the HARQ-ACK feedback corresponding to the NPDSCH; The third parameter is used to determine the third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, and the NPUSCH is scheduled by the DCI carried on the NPDCCH; The first information is sent by the network device. The NPDCCH, NPDSCH, HARQ-ACK feedback, and NPUSCH are all located in the Time Division Duplex (TDD) frame.

2. The method according to claim 1, characterized in that, The first parameter is used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the first subframe occupied by the NPDSCH.

3. The method according to claim 2, characterized in that, The NPDSCH and NPDCCH are transmitted within a single TDD frame; The maximum value among the candidate values ​​of the first parameter is determined based on the number of subframes included in a downlink time unit of the TDD frame and the number of subframes occupied by the NPDCCH.

4. The method according to claim 2, characterized in that, The NPDSCH and the NPDCCH are sent within different TDD frames; The maximum value among the candidate values ​​of the first parameter is determined based on the number of subframes included in a downlink time unit of the TDD frame, the number of subframes occupied by the NPDCCH, the number of subframes occupied by the TDD frame, the number of TDD frames between the NPDSCH and the NPDCCH, and the number of subframes between the frame header of the TDD frame and the start point of the downlink time unit occupied by the NPDSCH.

5. The method according to claim 2, characterized in that, The first parameter is determined based on the fourth parameter and the first offset; The NPDSCH is located within downlink time unit 3 of the TDD frame; The fourth parameter is used to indicate the number of subframes between the first reference subframe and the last subframe occupied by the NPDCCH; the first offset is used to indicate the number of subframes between the first reference subframe and the first subframe occupied by the NPDCCH. The first offset is configured by the network device, or the first offset is agreed upon by the protocol.

6. The method according to claim 5, characterized in that, The first offset is equal to a terminal-specific first offset; or... The first offset is equal to a cell-specific first offset; or, The first offset is equal to the sum of the terminal-specific first offset and the cell-specific first offset; Wherein, the terminal-specific first offset corresponds to the terminal, and the cell-specific first offset corresponds to the serving cell where the terminal is located.

7. The method according to claim 2, characterized in that, The first parameter is determined based on the first time-domain resource and the second offset; The NPDSCH is located within downlink time unit 3 of the TDD frame; Wherein, the first temporal resource is the first available temporal resource whose interval with the NPDCCH meets the requirements; the second offset is used to indicate the number of subframes between the first temporal resource and the first subframe occupied by the NPDCCH; The second offset is configured by the network device, or the second offset is agreed upon by the protocol.

8. The method according to claim 6, characterized in that, The second offset is equal to the terminal-specific second offset; or, The second offset is equal to a cell-specific second offset; or, The second offset is equal to the sum of the terminal-specific second offset and the cell-specific second offset; The terminal-specific second offset corresponds to the terminal, and the cell-specific second offset corresponds to the serving cell where the terminal is located.

9. The method according to claim 1, characterized in that, The second parameter is used to indicate the number of subframes between the last subframe occupied by the NPDSCH and the first subframe occupied by the HARQ-ACK feedback.

10. The method according to claim 9, characterized in that, The HARQ-ACK feedback and the NPDSCH are sent in different TDD frames; The maximum value among the candidate values ​​of the second parameter is determined based on the uplink time unit occupied by the HARQ-ACK feedback and the number of subframes occupied by the HARQ-ACK feedback.

11. The method according to claim 9, characterized in that, The second parameter is determined based on the fifth parameter and the third offset; The HARQ-ACK feedback is located within the uplink time unit 3 of the TDD frame; The fifth parameter is used to indicate the number of subframes between the second reference subframe and the last subframe occupied by the NPDSCH; the third offset is used to indicate the number of subframes between the second reference subframe and the first subframe occupied by the HARQ-ACK feedback. The third offset is configured by the network device, or the third offset is agreed upon by the protocol.

12. The method according to claim 11, characterized in that, The third offset is equal to a terminal-specific third offset; or... The third offset is equal to a cell-specific third offset; or... The third offset is equal to the sum of the terminal-specific third offset and the cell-specific third offset; The terminal-specific third offset corresponds to the terminal, and the cell-specific third offset corresponds to the serving cell where the terminal is located.

13. The method according to claim 9, characterized in that, The second parameter is determined based on the second time-domain resource and the fourth offset; The HARQ-ACK feedback is located within the uplink time unit 3 of the TDD frame; Wherein, the second temporal resource is the first available temporal resource whose interval with the NPDSCH meets the requirements; the fourth offset is used to indicate the number of subframes between the second temporal resource and the first subframe occupied by the HARQ-ACK feedback; The fourth offset is configured by the network device, or the fourth offset is agreed upon by the protocol.

14. The method according to claim 13, characterized in that, The fourth offset is equal to the terminal-specific fourth offset; or... The fourth offset is equal to the cell-specific fourth offset; or... The fourth offset is equal to the sum of the terminal-specific fourth offset and the cell-specific fourth offset; The terminal-specific fourth offset corresponds to the terminal, and the cell-specific fourth offset corresponds to the serving cell where the terminal is located.

15. The method according to claim 1, characterized in that, The third parameter is used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the first subframe occupied by the NPUSCH.

16. The method according to claim 15, characterized in that, The NPUSCH and the NPDCCH are sent in different TDD frames; The maximum value among the candidate values ​​of the third parameter is determined based on the uplink time unit occupied by the NPUSCH and the number of subframes occupied by the NPUSCH.

17. The method according to claim 15, characterized in that, The third parameter is determined based on the sixth parameter and the fifth offset; The NPUSCH is located within the uplink time unit 3 of the TDD frame; The sixth parameter is used to indicate the number of subframes between the third reference subframe and the last subframe occupied by the NPDCCH; the fifth offset is used to indicate the number of subframes between the third reference subframe and the first subframe occupied by the NPUSCH. The fifth offset is configured by the network device, or the fifth offset is agreed upon by the protocol.

18. The method according to claim 17, characterized in that, The fifth offset is equal to the terminal-specific fifth offset; or... The fifth offset is equal to the cell-specific fifth offset; or... The fifth offset is equal to the sum of the terminal-specific fifth offset and the cell-specific fifth offset; The terminal-specific fifth offset corresponds to the terminal, and the cell-specific fifth offset corresponds to the serving cell where the terminal is located.

19. The method according to claim 15, characterized in that, The third parameter is determined based on the third time-domain resource and the sixth offset; The NPUSCH is located within the uplink time unit 3 of the TDD frame; Wherein, the third temporal resource is the first available temporal resource whose interval with the NPDCCH meets the requirements; the sixth offset is used to indicate the number of subframes between the third temporal resource and the first subframe occupied by the NPUSCH; The sixth offset is configured by the network device, or the sixth offset is agreed upon by the protocol.

20. The method according to claim 19, characterized in that, The sixth offset is equal to the terminal-specific sixth offset; or... The sixth offset is equal to the cell-specific sixth offset; or... The sixth offset is equal to the sum of the terminal-specific sixth offset and the cell-specific fourth offset; The terminal-specific sixth offset corresponds to the terminal, and the cell-specific fourth offset corresponds to the serving cell where the terminal is located.

21. The method according to claim 1, characterized in that, Meet at least one of the following: The temporal resources occupied by the NPDCCH are located in the first available downlink time unit after the first reference subframe, wherein the first parameter is used to indicate the number of subframes between the first reference subframe and the last subframe occupied by the NPDCCH. The temporal resources occupied by the HARQ-ACK feedback are located in the first available uplink time unit after the second reference subframe, wherein the second parameter is used to indicate the number of subframes between the second reference subframe and the last subframe occupied by the NPDSCH. The temporal resources occupied by the NPUSCH are located in the first available uplink time unit after the third reference subframe, wherein the third parameter is used to indicate the number of subframes between the third reference subframe and the last subframe occupied by the NPDCCH.

22. The method according to any one of claims 1-21, characterized in that, Meet at least one of the following: The NPDSCH is repeatedly transmitted, wherein at least one of the repeatedly transmitted NPDSCHs is located within downlink time unit 3 in the TDD frame; The NPUSCH is transmitted repeatedly, wherein at least one repeated NPUSCH is located within uplink time unit 3 of the TDD frame.

23. The method according to any one of claims 1-22, characterized in that, The NPDCCH carries downlink control information (DCI), the DCI format type being any one of N0, N1, and N2, and the length of each type of DCI is different; the method further includes: Based on the first number of bits, the DCI is parsed; Wherein, the first number of bits is any of the following: The length of any one of the multiple types of DCIs; The length of the DCI with the smallest length among the multiple types of DCI; The length of the longest DCI among the various types of DCIs.

24. A communication method, characterized in that, The method is performed by a network device, and the method includes: Send first information to the terminal, the first information being used to determine at least one of a first parameter, a second parameter, and a third parameter; The first parameter is used to determine the first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH. The NPDSCH is scheduled by the downlink control information DCI carried on the NPDCCH. The second parameter is used to determine the second time interval, which is the time interval between the NPDSCH and the HARQ-ACK feedback corresponding to the NPDSCH; The third parameter is used to determine the third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, and the NPUSCH is scheduled by the DCI carried on the NPDCCH; The NPDCCH, NPDSCH, HARQ-ACK feedback, and NPUSCH are all located in a Time Division Duplex (TDD) frame.

25. The method according to claim 24, characterized in that, The first parameter is used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the first subframe occupied by the NPDSCH.

26. The method according to claim 25, characterized in that, The NPDSCH and NPDCCH are transmitted within a single TDD frame; The maximum value among the candidate values ​​of the first parameter is determined based on the number of subframes included in a downlink time unit of the TDD frame and the number of subframes occupied by the NPDCCH.

27. The method according to claim 25, characterized in that, The NPDSCH and the NPDCCH are sent within different TDD frames; The maximum value among the candidate values ​​of the first parameter is determined based on the number of subframes included in a downlink time unit of the TDD frame, the number of subframes occupied by the NPDCCH, the number of subframes occupied by the TDD frame, the number of TDD frames between the NPDSCH and the NPDCCH, and the number of subframes between the frame header of the TDD frame and the start point of the downlink time unit occupied by the NPDSCH.

28. The method according to claim 25, characterized in that, The first parameter is determined based on the fourth parameter and the first offset; The NPDSCH is located within downlink time unit 3 of the TDD frame; The fourth parameter is used to indicate the number of subframes between the first reference subframe and the last subframe occupied by the NPDCCH; the first offset is used to indicate the number of subframes between the first reference subframe and the first subframe occupied by the NPDCCH. The first offset is configured by the network device, or the first offset is agreed upon by the protocol.

29. The method according to claim 28, characterized in that, The first offset is equal to a terminal-specific first offset; or... The first offset is equal to a cell-specific first offset; or, The first offset is equal to the sum of the terminal-specific first offset and the cell-specific first offset; Wherein, the terminal-specific first offset corresponds to the terminal, and the cell-specific first offset corresponds to the serving cell where the terminal is located.

30. The method according to claim 25, characterized in that, The first parameter is determined based on the first time-domain resource and the second offset; The NPDSCH is located within downlink time unit 3 of the TDD frame; Wherein, the first temporal resource is the first available temporal resource whose interval with the NPDCCH meets the requirements; the second offset is used to indicate the number of subframes between the first temporal resource and the first subframe occupied by the NPDCCH; The second offset is configured by the network device, or the second offset is agreed upon by the protocol.

31. The method according to claim 30, characterized in that, The second offset is equal to the terminal-specific second offset; or, The second offset is equal to a cell-specific second offset; or, The second offset is equal to the sum of the terminal-specific second offset and the cell-specific second offset; The terminal-specific second offset corresponds to the terminal, and the cell-specific second offset corresponds to the serving cell where the terminal is located.

32. The method according to claim 24, characterized in that, The second parameter is used to indicate the number of subframes between the last subframe occupied by the NPDSCH and the first subframe occupied by the HARQ-ACK feedback.

33. The method according to claim 32, characterized in that, The HARQ-ACK feedback and the NPDSCH are sent in different TDD frames; The maximum value among the candidate values ​​of the second parameter is determined based on the uplink time unit occupied by the HARQ-ACK feedback and the number of subframes occupied by the HARQ-ACK feedback.

34. The method according to claim 32, characterized in that, The second parameter is determined based on the fifth parameter and the third offset; The HARQ-ACK feedback is located within the uplink time unit 3 of the TDD frame; The fifth parameter is used to indicate the number of subframes between the second reference subframe and the last subframe occupied by the NPDSCH; the third offset is used to indicate the number of subframes between the second reference subframe and the first subframe occupied by the HARQ-ACK feedback. The third offset is configured by the network device, or the third offset is agreed upon by the protocol.

35. The method according to claim 34, characterized in that, The third offset is equal to a terminal-specific third offset; or... The third offset is equal to a cell-specific third offset; or... The third offset is equal to the sum of the terminal-specific third offset and the cell-specific third offset; The terminal-specific third offset corresponds to the terminal, and the cell-specific third offset corresponds to the serving cell where the terminal is located.

36. The method according to claim 32, characterized in that, The second parameter is determined based on the second time-domain resource and the fourth offset; The HARQ-ACK feedback is located within the uplink time unit 3 of the TDD frame; Wherein, the second temporal resource is the first available temporal resource whose interval with the NPDSCH meets the requirements; the fourth offset is used to indicate the number of subframes between the second temporal resource and the first subframe occupied by the HARQ-ACK feedback; The fourth offset is configured by the network device, or the fourth offset is agreed upon by the protocol.

37. The method according to claim 36, characterized in that, The fourth offset is equal to the terminal-specific fourth offset; or... The fourth offset is equal to the cell-specific fourth offset; or... The fourth offset is equal to the sum of the terminal-specific fourth offset and the cell-specific fourth offset; The terminal-specific fourth offset corresponds to the terminal, and the cell-specific fourth offset corresponds to the serving cell where the terminal is located.

38. The method according to claim 24, characterized in that, The third parameter is used to indicate the number of subframes between the last subframe occupied by the NPDCCH and the first subframe occupied by the NPUSCH.

39. The method according to claim 38, characterized in that, The NPUSCH and the NPDCCH are sent in different TDD frames; The maximum value among the candidate values ​​of the third parameter is determined based on the uplink time unit occupied by the NPUSCH and the number of subframes occupied by the NPUSCH.

40. The method according to claim 38, characterized in that, The third parameter is determined based on the sixth parameter and the fifth offset; The NPUSCH is located within the uplink time unit 3 of the TDD frame; The sixth parameter is used to indicate the number of subframes between the third reference subframe and the last subframe occupied by the NPDCCH; the fifth offset is used to indicate the number of subframes between the third reference subframe and the first subframe occupied by the NPUSCH. The fifth offset is configured by the network device, or the fifth offset is agreed upon by the protocol.

41. The method according to claim 40, characterized in that, The fifth offset is equal to the terminal-specific fifth offset; or... The fifth offset is equal to the cell-specific fifth offset; or... The fifth offset is equal to the sum of the terminal-specific fifth offset and the cell-specific fifth offset; The terminal-specific fifth offset corresponds to the terminal, and the cell-specific fifth offset corresponds to the serving cell where the terminal is located.

42. The method according to claim 38, characterized in that, The third parameter is determined based on the third time-domain resource and the sixth offset; The NPUSCH is located within the uplink time unit 3 of the TDD frame; Wherein, the third temporal resource is the first available temporal resource whose interval with the NPDCCH meets the requirements; the sixth offset is used to indicate the number of subframes between the third temporal resource and the first subframe occupied by the NPUSCH; The sixth offset is configured by the network device, or the sixth offset is agreed upon by the protocol.

43. The method according to claim 42, characterized in that, The sixth offset is equal to the terminal-specific sixth offset; or... The sixth offset is equal to the cell-specific sixth offset; or... The sixth offset is equal to the sum of the terminal-specific sixth offset and the cell-specific fourth offset; The terminal-specific sixth offset corresponds to the terminal, and the cell-specific fourth offset corresponds to the serving cell where the terminal is located.

44. The method according to claim 24, characterized in that, Meet at least one of the following: The temporal resources occupied by the NPDCCH are located in the first available downlink time unit after the first reference subframe, wherein the first parameter is used to indicate the number of subframes between the first reference subframe and the last subframe occupied by the NPDCCH. The temporal resources occupied by the HARQ-ACK feedback are located in the first available uplink time unit after the second reference subframe, wherein the second parameter is used to indicate the number of subframes between the second reference subframe and the last subframe occupied by the NPDSCH. The temporal resources occupied by the NPUSCH are located in the first available uplink time unit after the third reference subframe, wherein the third parameter is used to indicate the number of subframes between the third reference subframe and the last subframe occupied by the NPDCCH.

45. The method according to any one of claims 24-44, characterized in that, Meet at least one of the following: The NPDSCH is repeatedly transmitted, wherein at least one of the repeatedly transmitted NPDSCHs is located within downlink time unit 3 in the TDD frame; The NPUSCH is transmitted repeatedly, wherein at least one repeated NPUSCH is located within uplink time unit 3 of the TDD frame.

46. ​​The method according to any one of claims 24-45, characterized in that, The NPDCCH carries downlink control information (DCI), and the format type of the DCI is any one of N0, N1, and N2, and the length of the DCI of each type is different. The terminal parses the DCI based on the first number of bits; Wherein, the first number of bits is any of the following: The length of any one of the multiple types of DCIs; The length of the DCI with the smallest length among the multiple types of DCI; The length of the longest DCI among the various types of DCIs.

47. A communication method, the method being used in a communication system, the communication system comprising a terminal and a network device, characterized in that, The method includes: The terminal determines at least one of the first parameter, the second parameter, and the third parameter based on the agreement of the protocol or the first information. The first parameter is used to determine the first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH, wherein the NPDSCH is scheduled by the DCI carried on the NPDCCH. The second parameter is used to determine the second time interval, which is the time interval between the NPDSCH and the HARQ-ACK feedback corresponding to the NPDSCH; The third parameter is used to determine the third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, and the NPUSCH is scheduled by the DCI carried on the NPDCCH; The first information is sent by the network device. The NPDCCH, NPDSCH, HARQ-ACK feedback, and NPUSCH are all located in the Time Division Duplex (TDD) frame.

48. A terminal, characterized in that, The terminal includes: The processing module is used to determine at least one of the first parameter, the second parameter, and the third parameter based on the agreement of the protocol or the first information: The first parameter is used to determine the first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH, wherein the NPDSCH is scheduled by the DCI carried on the NPDCCH. The second parameter is used to determine the second time interval, which is the time interval between the NPDSCH and the HARQ-ACK feedback corresponding to the NPDSCH; The third parameter is used to determine the third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, and the NPUSCH is scheduled by the DCI carried on the NPDCCH; The first information is sent by the network device. The NPDCCH, NPDSCH, HARQ-ACK feedback, and NPUSCH are all located in the Time Division Duplex (TDD) frame.

49. A network device, characterized in that, The network device includes: The transceiver module is used to send first information to the terminal, wherein the first information is used to determine at least one of a first parameter, a second parameter, and a third parameter; The first parameter is used to determine the first time interval, which is the time interval between the narrowband physical downlink control channel NPDCCH and the narrowband physical downlink shared channel NPDSCH, wherein the NPDSCH is scheduled by the DCI carried on the NPDCCH. The second parameter is used to determine the second time interval, which is the time interval between the NPDSCH and the HARQ-ACK feedback corresponding to the NPDSCH; The third parameter is used to determine the third time interval, which is the time interval between the NPDCCH and the narrowband physical uplink shared channel NPUSCH, and the NPUSCH is scheduled by the DCI carried on the NPDCCH; The NPDCCH, NPDSCH, HARQ-ACK feedback, and NPUSCH are all located in a Time Division Duplex (TDD) frame.

50. A terminal, characterized in that, The terminal includes: One or more processors; The terminal is used to execute the communication method according to any one of claims 1-23.

51. A network device, characterized in that, The network device includes: One or more processors; The first network device is used to perform the communication method according to any one of claims 24-46.

52. A communication device, characterized in that, The communication device is used to perform the communication method according to any one of claims 1-23 and 24-46.

53. A communication system, characterized in that, The device includes a terminal and a network device, wherein the terminal is configured to implement the communication method of any one of claims 1-23, and the network device is configured to implement the communication method of any one of claims 24-46.

54. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-23 and 24-46.

55. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the communication method according to any one of claims 1-23 and 24-46.

Images