Communication method and apparatus

Abstract

A communication method and apparatus, which can be applied to the field of satellite communications, such as an NTN. The method comprises: a terminal apparatus receives downlink control information, the downlink control information being used for indicating a scheduling delay parameter K, and K being a positive integer; and the terminal apparatus sends first data starting from a first time unit, the first time unit being the K-th, or the (K+Koffset)-th, or the (K+Koffset-G)-th uplink time unit after a time unit n. The time unit n is later than a time unit used for carrying downlink control information, Koffset is a predefined or preconfigured number of time units, n and Koffset are both positive integers, and G is the number of time units of a guard band within one frame period. By means of the technical solution provided in the present application, flexible scheduling can be achieved.

Description

A communication method and apparatus

[0001] This application claims priority to Chinese Patent Application No. 202411598623.3, filed on November 8, 2024, entitled “A Communication Method and Apparatus”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0003] With the development of information technology, there are more urgent requirements for the efficiency, mobility, and diversity of communications. Currently, in some important fields, such as space communications, aviation communications, maritime communications, and military communications, non-terrestrial networks (NTNs), such as satellite communications, play an irreplaceable role.

[0004] Compared to terrestrial networks, non-terrestrial networks utilize high, medium, and low Earth orbit satellites to achieve wide-area or even global coverage, providing seamless communication services to users worldwide. Non-terrestrial network communication systems can be integrated with terrestrial network communication systems, leveraging their respective strengths to create a globally seamless, integrated sea, land, air, and space communication network. This meets diverse user needs and represents a crucial direction for future communication development.

[0005] The frame structure involved in non-terrestrial networks differs from the frame structure used in existing standards. How to achieve flexible scheduling under the new frame structure is a technical problem to be solved. Summary of the Invention

[0006] This application provides a communication method and apparatus that enables flexible scheduling.

[0007] Firstly, this application provides a communication method that can be applied to a terminal device. The terminal device can be a terminal as a finished product, a component or module with terminal functions, a circuit or chip (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core), a chip system, or a processor that can be applied to the terminal to perform communication functions. Alternatively, it can be a logical node, logical module, or software capable of implementing all or part of the terminal functions. The method includes:

[0008] The terminal device receives downlink control information, which is used to indicate the scheduling delay parameter K, where K is a positive integer. The terminal device sends the first data starting from the first time unit. The first time unit is the Kth, or K+Koffset, or K+Koffset-G uplink time unit after time unit n. Here, time unit n is later than the time unit used to carry downlink control information, Koffset is the number of predefined or preconfigured time units, n and Koffset are both positive integers, and G is the number of time units in the guard band within one frame period.

[0009] The first time unit can be understood as the starting point of the time-domain resources used to transmit the first data. Taking uplink scheduling as an example, the first data can be uplink data, and the first time unit can also be understood as the starting point of the scheduled uplink data, or the starting position of the terminal device sending uplink data, or the starting position of the network device receiving uplink data.

[0010] Time unit n can also be called the scheduling delay start point. Time unit n is later than the time unit used to carry downlink control information; that is, time unit n is the time unit after the time unit used to carry downlink control information. The time unit used to carry downlink control information can be the last time unit of the time-domain resources used to carry downlink control information, or the end time unit of downlink control information. Downlink control information is transmitted through the physical downlink control channel (PDCCH). Optionally, the time unit used to carry downlink control information can also be the end time unit of the PDCCH.

[0011] The first time unit is the time unit following time unit n. The number of uplink time units between the first time unit and time unit n is related to the scheduling delay parameter K. The terminal device can determine the first time unit based on time unit n and the scheduling delay parameter K. Optionally, the first time unit is the Kth, K+Kth offset, or K+Kth offset-Gth uplink time unit immediately following time unit n.

[0012] Using the above method, with time unit n as the starting point of the scheduling delay, and the Kth, (K+K offset), or (K+K offset-G)th uplink time unit after time unit n as the starting point for scheduling uplink data, downlink resources and guard band resources within the frame period are not included in the scheduling delay parameter. In other words, the scheduling delay parameter does not need to cover the length of downlink resources and guard band resources. Thus, the scheduling delay parameter can be flexibly valued, allowing for flexible scheduling of the position where the terminal device sends uplink data in a new frame period, achieving flexible scheduling of uplink data.

[0013] In one possible implementation, time unit n is not earlier than the last downlink time unit in the current frame period, which is the frame period used to carry downlink control information.

[0014] The frame period includes downlink time domain resources, guard band time domain resources, and uplink time domain resources in sequence. That is, guard band time domain resources exist between downlink and uplink time domain resources. Optionally, the downlink time domain resources include consecutive downlink time units, the guard band time domain resources include consecutive guard band time units, and the uplink time domain resources include consecutive uplink time units.

[0015] The last downlink time unit within the current frame period can be the last downlink time unit in a series of consecutive downlink time units within the current frame period. In other words, time unit n is no earlier than the last downlink time unit in a series of consecutive downlink time units within the current frame period (or the end point of the consecutive downlink resources).

[0016] In the above implementation, the time unit n (i.e., the start point of the scheduling delay) is no earlier than the end point of the continuous downlink resources in the current frame period. Therefore, the downlink resources in the current frame period are not included in the scheduling delay parameter, meaning that the scheduling delay parameter does not need to cover the length of the downlink resources. Thus, the scheduling delay parameter can be flexibly set, allowing for flexible scheduling of the position where the terminal device sends uplink data in a new frame period, achieving flexible scheduling of uplink data.

[0017] In one possible implementation, time unit n is the first uplink time unit within the current frame period, and the first time unit is the Kth uplink time unit after time unit n.

[0018] The first uplink time unit within the current frame period can be the first uplink time unit in a series of consecutive uplink time units within the current frame period. In other words, time unit n can be the first uplink time unit (or the starting point of consecutive uplink resources) in a series of consecutive uplink time units within the current frame period.

[0019] The number of uplink time units between the first time unit and time unit n is K. Alternatively, the time interval between the first time unit and time unit n includes K uplink time units. Or, the first time unit is the Kth uplink time unit immediately following time unit n.

[0020] In the above implementation method, the starting point of continuous uplink resources within the current frame period is used as the scheduling delay starting point. That is, the scheduling delay parameter is calculated from the starting point of continuous uplink resources within the current frame period. Therefore, downlink resources and guard band resources within the current frame period are not included in the scheduling delay parameter, meaning the scheduling delay parameter does not need to cover the length of downlink resources and guard band resources. In this way, the scheduling delay parameter can be flexibly valued, allowing for flexible scheduling of the position where the terminal device transmits uplink data in a new frame period, thus achieving flexible scheduling of uplink data.

[0021] In one possible implementation, time unit n is the last guard band time unit in the current frame period, and the first time unit is the Kth uplink time unit after time unit n.

[0022] The last guard band time unit in the current frame period can be the last guard band time unit in a series of guard band time units within the current frame period. In other words, time unit n can be the last guard band time unit in a series of guard band time units within the current frame period (or the end point of the series of guard band resources).

[0023] It can be understood that the time unit following the last guard band time unit in the current frame period is the first uplink time unit in the current frame period.

[0024] In the above implementation method, the end point of the continuous guard band resources within the current frame period is used as the starting point of the scheduling delay. That is, the scheduling delay parameter is calculated from the end point of the continuous guard band resources within the current frame period. Therefore, the downlink resources and guard band resources within the current frame period are not included in the scheduling delay parameter, meaning the scheduling delay parameter does not need to cover the length of the downlink resources and guard band resources. In this way, the scheduling delay parameter can be flexibly valued, allowing for flexible scheduling of the position where the terminal device transmits uplink data in a new frame period, thus achieving flexible scheduling of uplink data.

[0025] In one possible implementation, time unit n is the first uplink time unit within the current frame period, and the first time unit is the K+K offset uplink time unit after time unit n.

[0026] The number of uplink time units between the first time unit and time unit n is K+Koffset. Alternatively, the time interval between the first time unit and time unit n includes K+Koffset uplink time units. Or, the first time unit is the K+Koffset-th uplink time unit immediately following time unit n.

[0027] In the above implementation, the scheduling delay starts from the beginning of the continuous uplink resources within the current frame period. This means the scheduling delay parameter is calculated from the starting point of the continuous uplink resources within the current frame period, excluding downlink resources and guard band resources within the current frame period. In other words, the scheduling delay parameter does not need to cover the length of downlink resources and guard band resources. This allows the scheduling delay parameter to be flexibly set, enabling flexible scheduling of the position where the terminal device transmits uplink data in a new frame period, thus achieving flexible uplink data scheduling. Furthermore, an additional parameter, Koffset, is added to extend the scheduling delay, further enhancing scheduling flexibility.

[0028] In one possible implementation, time unit n is the last guard band time unit in the current frame period, and the first time unit is the K+K offset uplink time unit after time unit n.

[0029] In the above implementation, the scheduling delay starts from the end point of the continuous guard band resources within the current frame period. This means the scheduling delay parameter is calculated from the end point of the continuous guard band resources within the current frame period. Therefore, downlink resources and guard band resources within the current frame period are not included in the scheduling delay parameter, meaning the scheduling delay parameter does not need to cover the length of downlink resources and guard band resources. This allows the scheduling delay parameter to be flexibly set, enabling flexible scheduling of the uplink data transmission position of the terminal device in a new frame period, thus achieving flexible uplink data scheduling. Furthermore, an additional parameter, Koffset, is added to extend the scheduling delay, further enhancing scheduling flexibility.

[0030] In one possible implementation, time unit n is the last downlink time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0031] The last downlink time unit within the current frame period can be the last downlink time unit in a series of consecutive downlink time units within the current frame period. In other words, time unit n can be the last downlink time unit in a series of consecutive downlink time units within the current frame period (or the end point of consecutive downlink resources).

[0032] The number of uplink time units between the first time unit and time unit n is K + Koffset - G. Alternatively, the time interval between the first time unit and time unit n includes K + Koffset - G uplink time units. Or, the first time unit is the K + Koffset - Gth uplink time unit immediately following time unit n.

[0033] The above implementation uses the end point of continuous downlink resources within the current frame period as the starting point for scheduling delay. In other words, the scheduling delay parameter is calculated from the end point of continuous downlink resources within the current frame period. Furthermore, an additional parameter, Koffset, is added to extend the scheduling delay. The length of Koffset can be used to cover the length of the guard band resources, thus the downlink resources and guard band resources within the current frame period are not included in the scheduling delay parameter. This means the scheduling delay parameter does not need to cover the lengths of downlink resources and guard band resources. Therefore, the scheduling delay parameter can be flexibly valued, allowing for flexible scheduling of the uplink data transmission position of the terminal device in a new frame period, achieving flexible uplink data scheduling. Moreover, it is more compatible with the scheduling delay methods in existing FDD communication.

[0034] In one possible implementation, time unit n is the first guard band time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0035] The first protection band time unit within the current frame period can be the first protection band time unit in a series of protection band time units within the current frame period. In other words, time unit n can be the first protection band time unit in a series of protection band time units within the current frame period (or the starting point of the series of protection band resources).

[0036] It can be understood that the time unit preceding the first guard band time unit in the continuous guard band time units within the current frame period is the last uplink time unit in the continuous downlink time units within the current frame period.

[0037] In the above implementation, the starting point of the continuous guard band resources within the current frame period is used as the starting point of the scheduling delay. That is, the scheduling delay parameter is calculated from the starting point of the continuous guard band resources within the current frame period. Furthermore, an additional parameter, Koffset, is added to extend the scheduling delay. The length of parameter Koffset can be used to cover the length of the guard band resources. Therefore, downlink resources and guard band resources within the current frame period are not included in the scheduling delay parameter; that is, the scheduling delay parameter does not need to cover the length of downlink resources and guard band resources. In this way, the scheduling delay parameter can be flexibly valued, allowing for flexible scheduling of the position where the terminal device sends uplink data in a new frame period, achieving flexible uplink data scheduling. Moreover, it is more compatible with the scheduling delay methods in existing FDD communication.

[0038] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0039] Secondly, this application provides a communication method that can be applied to a terminal device. The terminal device can be a terminal as a finished product, a component or module with terminal functions, a circuit or chip (such as a modem chip, also known as a baseband chip, or a system-on-chip (SoC) chip or system-in-package (SIP) chip containing a modem core), a chip system, or a processor that can be applied to the terminal to perform communication functions. Alternatively, it can be a logical node, logical module, or software capable of implementing all or part of the terminal functions. The method includes:

[0040] The terminal device receives downlink control information, which is used to indicate the scheduling delay parameter K, where K is a positive integer. The terminal device receives second data starting from the second time unit, which is the Kth or K+Koffset downlink time unit after time unit n. Here, time unit n is later than the time unit used to carry downlink control information, and Koffset is a predefined or preconfigured number of time units, where both n and Koffset are positive integers.

[0041] The second time unit can be understood as the starting point of the time-domain resources used to transmit the second data. Taking downlink scheduling as an example, the second data can be downlink data, and the second time unit can also be understood as the starting point of the downlink data scheduling, or the starting position of the network device sending downlink data, or the starting position of the terminal device receiving downlink data.

[0042] Time unit n can also be called the scheduling delay start point. Time unit n is later than the time unit used to carry downlink control information; that is, time unit n is the time unit after the time unit used to carry downlink control information. The time unit used to carry downlink control information can be the last time unit of the time-domain resources used to carry downlink control information, or the end time unit of downlink control information. Downlink control information is transmitted via PDCCH; optionally, the time unit used to carry downlink control information can also be the end time unit of PDCCH.

[0043] The second time unit is the time unit following time unit n. The number of downlink time units between the second time unit and time unit n is related to the scheduling delay parameter K. The terminal device can determine the second time unit based on time unit n and the scheduling delay parameter K. Optionally, the second time unit is the Kth or K+Kth offset downlink time unit immediately following time unit n.

[0044] Using the above method, with time unit n as the starting point of the scheduling delay, and the Kth or K+Koffset downlink time unit after time unit n as the starting point of the downlink data scheduling, the uplink resources and guard band resources within the frame period are not included in the scheduling delay parameter. In other words, the scheduling delay parameter does not need to cover the length of the uplink resources and guard band resources. Thus, the scheduling delay parameter can be flexibly valued, allowing for flexible scheduling of the terminal device's downlink data reception position in a new frame period, achieving flexible scheduling of downlink data.

[0045] In one possible implementation, the downlink control information is also used to indicate that the time unit used to carry the second data is not within the current frame period; wherein the current frame period is the frame period used to carry the downlink control information.

[0046] Through the above implementation method, the terminal device can determine that the downlink control information and the downlink data it schedules are not in the same frame period. In this case, time unit n is not earlier than the first downlink time unit in the next frame period of the current frame period, and the second time unit can be the Kth or K+Kth offset downlink time unit after time unit n.

[0047] In one possible implementation, the downlink control information is also used to indicate that: a portion of the time units used to carry the second data are within the current frame period, and another portion of the time units used to carry the second data are within a frame period after the current frame period; wherein, the current frame period is the frame period used to carry the downlink control information.

[0048] Through the above implementation method, the terminal device can determine that the downlink control information and a portion of the downlink data it schedules are in the same frame period, and the remaining downlink data are in frame periods following the current frame period. In this case, time unit n is not earlier than the first downlink time unit in the next frame period after the current frame period, and the second time unit can be the Kth or K+Koffset downlink time unit after time unit n.

[0049] In one possible implementation, time unit n is no earlier than the first downlink time unit in the next frame period of the current frame period. The current frame period is a frame period used to carry downlink control information, and the frame period includes, in sequence, a downlink time unit, a guard band time unit, and an uplink time unit.

[0050] The first downlink time unit in the next frame period can be the first downlink time unit in a series of downlink time units within the next frame period. In other words, time unit n is no earlier than the first downlink time unit (or the start point of the series of downlink resources) in a series of downlink time units within the next frame period.

[0051] In the above implementation, the time unit n (i.e., the scheduling delay start point) is no earlier than the start point of the continuous downlink resources in the next frame period. Therefore, the uplink resources and guard band resources in the current frame period are not included in the scheduling delay parameter. In other words, the scheduling delay parameter does not need to cover the length of the uplink resources and guard band resources. Thus, the scheduling delay parameter can be flexibly valued, allowing for flexible scheduling of the position where the terminal device receives downlink data in a new frame period, thereby achieving flexible scheduling of downlink data.

[0052] In one possible implementation, time unit n is the first downlink time unit in the next frame period of the current frame period, and the second time unit is the Kth downlink time unit after time unit n.

[0053] The number of downlink time units between the second time unit and time unit n is K. Alternatively, the time interval between the second time unit and time unit n comprises K downlink time units. Or, the second time unit is the Kth downlink time unit immediately following time unit n.

[0054] In the above implementation, the starting point of continuous downlink resources in the next frame period is used as the scheduling delay starting point. That is, the scheduling delay parameter is calculated from the starting point of continuous downlink resources in the next frame period. Therefore, uplink resources and guard band resources in the current frame period are not included in the scheduling delay parameter, meaning the scheduling delay parameter does not need to cover the length of uplink resources and guard band resources. In this way, the scheduling delay parameter can be flexibly valued, allowing for flexible scheduling of the terminal device's downlink data reception position in a new frame period, achieving flexible downlink data scheduling. Furthermore, considering the limited downlink resources within a frame period, in cases of high repetition frequency, it is necessary to delay to the next frame period to ensure data transmission performance.

[0055] In one possible implementation, time unit n is the first downlink time unit in the next frame period of the current frame period, and the second time unit is the K+K offset downlink time unit after time unit n.

[0056] The number of downlink time units between the second time unit and time unit n is K+Koffset. Alternatively, the time interval between the second time unit and time unit n includes K+Koffset downlink time units. Or, the second time unit is the K+Koffset-th downlink time unit immediately following time unit n.

[0057] In the above implementation, the starting point of continuous downlink resources in the next frame period is used as the scheduling delay starting point. That is, the scheduling delay parameter is calculated from the starting point of continuous downlink resources in the next frame period. Therefore, uplink resources and guard band resources in the current frame period are not included in the scheduling delay parameter, meaning the scheduling delay parameter does not need to cover the length of uplink resources and guard band resources. In this way, the scheduling delay parameter can be flexibly valued, allowing for flexible scheduling of the terminal device's downlink data reception position in a new frame period, achieving flexible downlink data scheduling. Furthermore, an additional parameter, Koffset, is added to extend the scheduling delay, further enhancing scheduling flexibility. Moreover, considering the limited downlink resources within a frame period, in cases of high repetition frequency, a delay to the next frame period is necessary to ensure data transmission performance.

[0058] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0059] Thirdly, this application provides a communication method that can be applied to a network device. The network device can be a network equipment as a final product, a component or module with network equipment functions, or a communication chip (e.g., a processor, baseband chip, or chip system) that can be used in a network device. The method includes:

[0060] The network device sends downlink control information, which is used to indicate the scheduling delay parameter K, where K is a positive integer. The network device receives the first data starting from the first time unit. The first time unit is the Kth, or K+Koffset, or K+Koffset-G uplink time unit after time unit n. Here, time unit n is later than the time unit used to carry downlink control information, Koffset is the number of predefined or preconfigured time units, n and Koffset are both positive integers, and G is the number of time units in the guard band within one frame period.

[0061] In one possible implementation, time unit n is not earlier than the last downlink time unit in the current frame period, and the current frame period is a frame period used to carry downlink control information; the frame period includes, in sequence: downlink time unit, guard band time unit and uplink time unit.

[0062] In one possible implementation, time unit n is the first uplink time unit in the current frame period, and the first time unit is the Kth or K+K offset uplink time unit after time unit n.

[0063] In one possible implementation, time unit n is the last guard band time unit in the current frame period, and the first time unit is the Kth or K+K offset uplink time unit after time unit n.

[0064] In one possible implementation, time unit n is the last downlink time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0065] In one possible implementation, time unit n is the first guard band time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0066] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0067] Fourthly, this application provides a communication method that can be applied to a network device. The network device can be a network equipment as a final product, a component or module with network equipment functions, or a communication chip (e.g., a processor, baseband chip, or chip system) that can be used in a network device. The method includes:

[0068] The network device receives downlink control information, which is used to indicate the scheduling delay parameter K, where K is a positive integer. The network device sends the second data starting from the second time unit, which is the Kth or K+Koffset downlink time unit after time unit n. Here, time unit n is later than the time unit used to carry downlink control information, and Koffset is a predefined or preconfigured number of time units, where both n and Koffset are positive integers.

[0069] In one possible implementation, the downlink control information is also used to indicate that the time unit used to carry the second data is not within the current frame period; wherein the current frame period is the frame period used to carry the downlink control information.

[0070] In one possible implementation, the downlink control information is also used to indicate that: a portion of the time units used to carry the second data are within the current frame period, and another portion of the time units used to carry the second data are within a frame period after the current frame period; wherein, the current frame period is the frame period used to carry the downlink control information.

[0071] In one possible implementation, time unit n is no earlier than the first downlink time unit in the next frame period of the current frame period. The current frame period is a frame period used to carry downlink control information, and the frame period includes, in sequence, a downlink time unit, a guard band time unit, and an uplink time unit.

[0072] In one possible implementation, time unit n is the first downlink time unit in the next frame period of the current frame period.

[0073] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0074] Fifthly, this application provides a communication device that includes modules, units, or means for performing methods as described in the first aspect or any possible implementation thereof. These modules, units, or means may be implemented in software, hardware, or a combination of software and hardware.

[0075] In one possible implementation, the device includes:

[0076] The transceiver unit is used to receive downlink control information, which is used to indicate the scheduling delay parameter K, where K is a positive integer. The transceiver unit is also used to send the first data starting from the first time unit. The first time unit is the Kth, K+Koffset, or K+Koffset-G uplink time unit after time unit n. Here, time unit n is later than the time unit used to carry downlink control information, Koffset is the number of predefined or preconfigured time units, n and Koffset are both positive integers, and G is the number of time units in the guard band within one frame period.

[0077] In one possible implementation, time unit n is not earlier than the last downlink time unit in the current frame period, and the current frame period is a frame period used to carry downlink control information; the frame period includes, in sequence: downlink time unit, guard band time unit and uplink time unit.

[0078] In one possible implementation, time unit n is the first uplink time unit in the current frame period, and the first time unit is the Kth or K+K offset uplink time unit after time unit n.

[0079] In one possible implementation, time unit n is the last guard band time unit in the current frame period, and the first time unit is the Kth or K+K offset uplink time unit after time unit n.

[0080] In one possible implementation, time unit n is the last downlink time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0081] In one possible implementation, time unit n is the first guard band time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0082] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0083] In a sixth aspect, this application provides a communication device comprising modules, units, or means for performing methods as described in the second aspect or any possible implementation thereof. These modules, units, or means may be implemented in software, hardware, or a combination of software and hardware.

[0084] In one possible implementation, the device includes:

[0085] The transceiver unit is used to receive downlink control information, which is used to indicate the scheduling delay parameter K, where K is a positive integer. The transceiver unit is also used to receive second data starting from the second time unit, which is the Kth or K+Koffset downlink time unit after time unit n. Here, time unit n is later than the time unit used to carry downlink control information, and Koffset is a predefined or preconfigured number of time units, where both n and Koffset are positive integers.

[0086] In one possible implementation, the downlink control information is also used to indicate that the time unit used to carry the second data is not within the current frame period; wherein the current frame period is the frame period used to carry the downlink control information.

[0087] In one possible implementation, the downlink control information is also used to indicate that: a portion of the time units used to carry the second data are within the current frame period, and another portion of the time units used to carry the second data are within a frame period after the current frame period; wherein, the current frame period is the frame period used to carry the downlink control information.

[0088] In one possible implementation, time unit n is no earlier than the first downlink time unit in the next frame period of the current frame period. The current frame period is a frame period used to carry downlink control information, and the frame period includes, in sequence, a downlink time unit, a guard band time unit, and an uplink time unit.

[0089] In one possible implementation, time unit n is the first downlink time unit in the next frame period of the current frame period.

[0090] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0091] In a seventh aspect, this application provides a communication device comprising modules, units, or means for performing methods as described in the third aspect or any possible implementation thereof. These modules, units, or means may be implemented in software, hardware, or a combination of software and hardware.

[0092] In one possible implementation, the device includes:

[0093] The transceiver unit is used to send downlink control information, which is used to indicate the scheduling delay parameter K, where K is a positive integer. The transceiver unit is also used to receive the first data starting from the first time unit. The first time unit is the Kth, K+Koffset, or K+Koffset-G uplink time unit after time unit n. Here, time unit n is later than the time unit used to carry downlink control information, Koffset is the number of predefined or preconfigured time units, n and Koffset are both positive integers, and G is the number of time units in the guard band within one frame period.

[0094] In one possible implementation, time unit n is not earlier than the last downlink time unit in the current frame period, and the current frame period is a frame period used to carry downlink control information; the frame period includes, in sequence: downlink time unit, guard band time unit and uplink time unit.

[0095] In one possible implementation, time unit n is the first uplink time unit in the current frame period, and the first time unit is the Kth or K+K offset uplink time unit after time unit n.

[0096] In one possible implementation, time unit n is the last guard band time unit in the current frame period, and the first time unit is the Kth or K+K offset uplink time unit after time unit n.

[0097] In one possible implementation, time unit n is the last downlink time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0098] In one possible implementation, time unit n is the first guard band time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0099] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0100] Eighthly, this application provides a communication device that includes modules, units, or means for performing methods as described in the fourth aspect or any possible implementation thereof. These modules, units, or means may be implemented in software, hardware, or a combination of software and hardware.

[0101] In one possible implementation, the device includes:

[0102] The transceiver unit is used to receive downlink control information, which is used to indicate the scheduling delay parameter K, where K is a positive integer. The transceiver unit is also used to send second data starting from the second time unit, which is the Kth or K+Koffset downlink time unit after time unit n. Here, time unit n is later than the time unit used to carry downlink control information, and Koffset is a predefined or preconfigured number of time units, where both n and Koffset are positive integers.

[0103] In one possible implementation, the downlink control information is also used to indicate that the time unit used to carry the second data is not within the current frame period; wherein the current frame period is the frame period used to carry the downlink control information.

[0104] In one possible implementation, the downlink control information is also used to indicate that: a portion of the time units used to carry the second data are within the current frame period, and another portion of the time units used to carry the second data are within a frame period after the current frame period; wherein, the current frame period is the frame period used to carry the downlink control information.

[0105] In one possible implementation, time unit n is no earlier than the first downlink time unit in the next frame period of the current frame period. The current frame period is a frame period used to carry downlink control information, and the frame period includes, in sequence, a downlink time unit, a guard band time unit, and an uplink time unit.

[0106] In one possible implementation, time unit n is the first downlink time unit in the next frame period of the current frame period.

[0107] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0108] Ninthly, this application provides a communication device including a processor for executing computer programs or instructions, which, when executed, cause the methods of any one of the first to fourth aspects or any possible implementations described above to be implemented. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, with the processor coupled to the communication interface.

[0109] In a tenth aspect, this application provides a computer-readable storage medium storing a computer program or instructions that, when executed, cause the method of any one of the first to fourth aspects or any possible implementation thereof to be implemented.

[0110] In one aspect, this application provides a computer program product comprising a computer program or instructions that, when executed, cause the method of any one of the first to fourth aspects or any possible implementation thereof to be implemented.

[0111] In a twelfth aspect, this application provides a chip including a processor for executing computer programs or instructions, which, when executed, cause the methods of any one of the first to fourth aspects or any possible implementations described above to be implemented. Optionally, the chip further includes a communication interface for receiving or transmitting signals.

[0112] In a thirteenth aspect, this application provides a chip including logic circuitry and an input / output interface. The logic circuitry is coupled to the input / output interface and transmits data through the input / output interface to perform the methods of any one of the first to fourth aspects or any possible implementation thereof.

[0113] In a fourteenth aspect, this application provides a communication system comprising a communication device as described in the fifth aspect or any possible implementation thereof, and / or a communication device as described in the sixth aspect or any possible implementation thereof, and / or a communication device as described in the seventh aspect or any possible implementation thereof, and / or a communication device as described in the eighth aspect or any possible implementation thereof.

[0114] In a fifteenth aspect, this application provides a communication system comprising a terminal device and a network device, wherein the terminal device is configured to perform the method of any one of the first to second aspects or any possible implementation thereof, and the network device is configured to perform the method of any one of the third to fourth aspects or any possible implementation thereof.

[0115] The beneficial effects of the third to fifteenth aspects mentioned above can be referred to the descriptions of the beneficial effects in the first and second aspects, and will not be repeated here.

[0116] Furthermore, in the process of executing any of the first to fourth aspects and any possible implementation of the method described above, the processes related to sending and / or receiving information can be understood as the process of the processor outputting information and / or the processor receiving input information. When outputting information, the processor can output the information to a transceiver (or communication interface, or transmitting module) for transmission. After the information is output by the processor, it may require further processing before reaching the transceiver. Similarly, when the processor receives input information, the transceiver (or communication interface, or transmitting module) receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, it may require further processing before being input to the processor.

[0117] Based on the above principles, for example, the information sent mentioned in the aforementioned method can be understood as information output by the processor. Similarly, the information received can be understood as information received by the processor from input.

[0118] Alternatively, unless otherwise specified, the operations of transmitting, sending, and receiving involved by the processor can be more generally understood as processor output and receiving, input, and other operations, unless they contradict their actual function or internal logic in the relevant description.

[0119] Optionally, in the process of executing the method of any of the first to fourth aspects and any possible implementation thereof, the processor may be a processor specifically designed to execute these methods, or it may be a processor that executes these methods by executing computer instructions stored in memory, such as a general-purpose processor. The memory may be a non-transitory memory, such as read-only memory (ROM), which may be integrated with the processor on the same chip or disposed on separate chips. This application does not limit the type of memory or the arrangement of the memory and processor. Attached Figure Description

[0120] The accompanying drawings used in the embodiments of this application are described below.

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

[0122] Figure 2 is a schematic diagram of the architecture of an NTN communication system provided in an embodiment of this application;

[0123] Figure 3 is a schematic diagram of the frame structure of the Iridium satellite;

[0124] Figure 4 is a schematic diagram of a frame structure #1 provided in an embodiment of this application;

[0125] Figure 5 is a flowchart illustrating a communication method provided in an embodiment of this application;

[0126] Figure 6 is a schematic diagram of an example A1 of an uplink scheduling delay provided in an embodiment of this application;

[0127] Figure 7 is another schematic diagram of an example A1 of an uplink scheduling delay provided in an embodiment of this application;

[0128] Figure 8 is a schematic diagram of an example A2 of uplink scheduling delay provided in an embodiment of this application;

[0129] Figure 9 is a schematic diagram of an example A3 of uplink scheduling delay provided in an embodiment of this application;

[0130] Figure 10 is a schematic diagram of an example A4 of an uplink scheduling delay provided in an embodiment of this application;

[0131] Figure 11 is a schematic diagram of an example A5 of uplink scheduling delay provided in an embodiment of this application;

[0132] Figure 12 is another schematic diagram of an example A5 of an uplink scheduling delay provided in an embodiment of this application;

[0133] Figure 13 is a schematic diagram of an example A6 of uplink scheduling delay provided in an embodiment of this application;

[0134] Figure 14 is a flowchart illustrating another communication method provided in an embodiment of this application;

[0135] Figure 15 is a schematic diagram of an example B1 of a downlink scheduling delay provided in an embodiment of this application;

[0136] Figure 16 is a schematic diagram of an example B2 of a downlink scheduling delay provided in an embodiment of this application;

[0137] Figure 17 is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0138] Figure 18 is a schematic diagram of another communication device provided in an embodiment of this application;

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

[0140] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0141] In this application, the words "exemplarily" or "for example" are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design that is described as "exemplarily" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design options. Rather, the use of the words "exemplarily" or "for example" is intended to present the relevant concepts in a specific manner.

[0142] The ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the order, sequence, priority, or importance of the multiple objects. Furthermore, "first" and "second" are not necessarily different. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0143] The term "embodiment" as used herein means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the various embodiments of this application are consistent and can be mutually referenced, and technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0144] It should be understood that in this application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0145] In the description of this application, "instruction" can include direct and indirect instructions, as well as explicit and implicit instructions. The information indicated by a certain piece of information is called the information to be instructed. In the specific implementation process, there are many ways to instruct the information to be instructed. For example, the information to be instructed can be directly instructed, such as by instructing the information itself or its index. Alternatively, the information to be instructed can be indirectly indicated by instructing other information, where there is a relationship between the indicated other information and the information to be instructed. Another example is that only a part of the information to be instructed can be indicated, while the other parts are known or pre-agreed upon. Furthermore, the instruction of specific information can be achieved by using a pre-agreed (such as an agreement) arrangement of various pieces of information, thereby reducing the instruction overhead to some extent.

[0146] It is understood that in the description of this application, "when," "if," and "if" all refer to the device making a corresponding action under certain objective circumstances, and are not limited to a specific time, nor do they require the device to make a judgment action when it is implemented, nor do they imply any other limitations.

[0147] The technical solutions of this application embodiment can be applied to various communication systems, such as long term evolution (LTE) communication systems, new radio (NR) communication systems, LTE-A advanced (LTE-A) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, machine-to-machine (M2M) communication systems, internet of things (IoT) communication systems, narrowband internet of things (NB-IoT) communication systems, integrated sensing and communication systems, frequency division duplex (FDD) communication systems, time division duplex (TDD) communication systems, non-terrestrial network (NTN) communication systems, wireless projection communication systems, integrated access and backhaul (IAB) communication systems, public land mobile network (PLMN) communication systems, and non-public networks. The network (NPN) communication system, as well as communication systems evolved from the fifth-generation (5G) communication system (e.g., the sixth-generation (6G) communication system), or non-3rd generation partnership project (3GPP) communication systems, are not restricted. The NTN can be a communication system integrated with other communication systems such as 4G, 5G mobile communication systems, or future communication systems, such as NR NTN, IoT NTN, etc.

[0148] For example, please refer to Figure 1, which is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. As shown in Figure 1, the communication system may include at least one terminal device and at least one network device. The terminal device can be connected to the network device wirelessly or via a wired connection, enabling uplink (UL) or downlink (DL) communication between the terminal device and the network device. Terminal devices can also be connected wirelessly or via a wired connection, enabling sidelink (SL) communication between them.

[0149] The terminal device in this application embodiment is a user-side entity used to receive or transmit signals, providing voice and / or data to the user. The terminal device may also be referred to as a terminal, terminal apparatus, access terminal, user terminal, subscriber unit, user equipment (UE), user station, mobile device, mobile station (MS), mobile station, mobile client, mobile unit, remote station, remote terminal, remote unit, wireless unit, wireless communication equipment, user agent, or user apparatus, etc. For example, the terminal device in this application embodiment may be a mobile phone, tablet computer, computer with wireless transceiver function, train, airplane, mobile internet device (MID), virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control (e.g., robot), wireless terminal in vehicle networking (e.g., in-vehicle equipment, vehicle equipment, in-vehicle module, vehicle), wireless terminal in self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, machine type communication (MTC) terminal, cellular phone, smartphone, cordless phone, session initiation protocol (SIP) phone, wireless data card, wireless local loop (WLL) station, personal digital assistant (PDA) PDA (Power Assistant), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, etc.

[0150] It should be noted that the terminal device described in the embodiments of this application can be a terminal as a final product, such as the various terminal devices mentioned above; it can also be a component or part with terminal functions; it can be a circuit or chip (such as a modem chip, also known as a baseband chip, or a system-on-a-chip (SoC) chip or system-in-package (SIP) chip containing a modem core), a chip system, or a processor that can be applied to the terminal to perform communication functions; or it can be a logic node, logic module, or software that can implement all or part of the terminal functions. In other words, the components, parts, or chips applied in the aforementioned terminal devices also belong to the category of terminal devices.

[0151] In Figure 1, network devices are exemplified using access network (AN) devices. Access network devices, also known as radio access network (RAN) devices, or simply access networks, are nodes or devices that connect terminal devices to a wireless network. In other words, the access network provides access services to terminal devices, enabling them to access (or connect to) the network. Access networks can support both wired and wireless access.

[0152] The network devices in this application embodiment may include, but are not limited to: base stations (or Node Bs, NBs), next-generation base stations (gNBs), evolved Node Bs (eNBs), radio network controllers (RNCs), base station controllers (BSCs), base transceiver stations (BTSs), home evolved Node Bs (HeNBs, or home Node Bs, HNBs), base band units (BBUs), access points (APs), wireless relay nodes, wireless backhaul nodes, transmission points (TPs), or transmission and reception points (TRPs), etc. They may also be one or a group of antenna panels of a base station in a 5G system, or network nodes constituting a gNB or TP, such as BBUs or distributed units (DUs), etc. The base station may be a macro base station, a micro base station, a pico base station, a small cell, a relay station, or a balloon station, etc.

[0153] In some deployments, a gNB may include a centralized unit (CU) and a dedicated unit (DU). The gNB may also include an active antenna unit (AAU). The CU implements some of the gNB's functions, and the DU implements others. For example, the CU handles non-real-time protocols and services, implementing radio resource control (RRC) and packet data convergence protocol (PDCP) layer functions. The DU handles physical layer protocols and real-time services, implementing radio link control (RLC), media access control (MAC), and physical (PHY) layer functions. The AAU implements some physical layer processing functions, radio frequency processing, and active antenna-related functions. RRC layer information is generated by the CU and is ultimately encapsulated by the DU's PHY layer to become PHY layer information, or it may be derived from PHY layer information. Therefore, in this architecture, higher-layer signaling, such as RRC layer signaling, can be considered as being sent by the DU, or by the DU+AAU. It is understood that network devices can be one or more of the following: CU nodes, DU nodes, and AAU nodes. Furthermore, a CU can be classified as a network device in the radio access network (RAN) or a network device in the core network (CN); this application does not limit this classification.

[0154] Furthermore, the solution provided in this application can be applied to satellite communication systems, such as 5G systems or NTN integrated into future evolved communication systems. In this case, the network equipment can be a satellite with access network equipment functionality, or an access network device deployed on a satellite. In some satellite communication scenarios, the network equipment can also be a satellite communication terminal, such as a portable station, a fixed station, a vehicle-mounted or airborne satellite communication terminal. It should be understood that in these scenarios, the satellite communication terminal communicates with the satellite and can act as a micro base station or satellite data station to further provide data interfaces to user equipment accessing the satellite communication terminal.

[0155] It should be noted that the network device described in the embodiments of this application can be a network device as a final product, such as the various network devices mentioned above, or it can be a component or part with network device functions, or it can be a communication chip (such as a processor, baseband chip, or chip system, etc.) that can be applied in a network device. That is to say, the components, parts, or chips applied in the above-mentioned network devices also belong to network devices.

[0156] It should be noted that although the network architecture shown in Figure 1 illustrates the access network and terminal devices, the application scenario may not be limited to the access network and terminal devices. For example, it may also include devices for carrying virtualized network functions, which are obvious to those skilled in the art and will not be elaborated here.

[0157] Furthermore, the number and types of network devices and terminal devices included in the network architecture shown in Figure 1 are merely examples, and the embodiments of this application are not limited thereto. For example, it may also include more or fewer terminal devices communicating with the network devices. As another example, it may also include more or fewer network devices communicating with the terminal devices. For the sake of brevity, they are not described one by one in the accompanying drawings.

[0158] Optionally, the communication system may also include network devices not shown in Figure 1, such as core network (CN) devices, data network devices, etc.

[0159] In some embodiments, the network device and the terminal device may also be referred to as communication devices, which may be general-purpose devices or special-purpose devices. This application does not specifically limit this.

[0160] This application does not limit the location of the terminal equipment and network equipment; the terminal equipment and network equipment can be in a fixed state or in a mobile state. The terminal equipment and network equipment can be deployed on land, or on water, in the air, etc.

[0161] In this embodiment, network devices deployed in the air can be referred to as non-terrestrial network devices, and network devices deployed on the ground can be referred to as terrestrial network devices. An NTN communication system includes at least one non-terrestrial network device, while network devices in a terrestrial communication system are all terrestrial network devices. Terrestrial network devices, relative to non-terrestrial network devices, are stationary or move at a relatively slow speed. In other words, non-terrestrial network devices, relative to terrestrial network devices, can be high-speed mobile network devices.

[0162] Non-terrestrial network equipment may include satellites, high-altitude platforms (HAPs), drones, hot air balloons, low-Earth orbit satellites, medium-Earth orbit satellites, high-Earth orbit satellites, etc., without limitation. The term "satellite" in this application can refer to a collection of satellites and other network equipment related to satellite communication; therefore, in this application, the descriptions "satellite" and "satellite network equipment" are equivalent.

[0163] Please refer to Figure 2, which is a schematic diagram of the architecture of an NTN communication system provided in an embodiment of this application. Figure 2 uses an NTN communication system integrated with a 5G communication system as an example. It should be understood that the solution provided in this embodiment can also be applied to NTN systems integrated with future evolving communication systems. The access network can be a next-generation radio access network (NG-RAN), and the core network can be a 5G core network (5G CN). This architecture can be understood as an NTN-based NG-RAN architecture.

[0164] The interface between the terminal equipment and the access network is called the air interface, such as the NR Uu interface. The NG interface, as the interface between the access network and the core network, is mainly used for exchanging non-access stratum (NAS) signaling in the core network, as well as user service data. The Xn interface is the interface between access networks, mainly used for exchanging handover signaling. The N6 interface can be the interface between the core network and the data network.

[0165] It should be noted that the above interfaces are exemplified using a 5G communication system. Different communication systems may use different names. For instance, in a fourth-generation (4G) communication system, the interface between access networks can be an X2 interface, and the interface between the access network and the core network can be an S1 interface, etc. Of course, in future communications, the names of these interfaces may remain unchanged or be replaced with other names; this application does not limit this.

[0166] An NTN communication system may include at least one terminal device, at least one non-terrestrial network device, and at least one terrestrial network device. For example, as shown in Figure 2, an NTN system includes two terminal devices, two non-terrestrial network devices, and multiple terrestrial network devices. The non-terrestrial network devices are 5G base stations (deployed on satellites), and the terrestrial network devices include ground stations, 5G user plane functions (UPFs), 5G control plane functions (UPFs), and data network devices.

[0167] 5G core network equipment consists of multiple functional units, which can be divided into control plane and data plane functional entities, as shown in Figure 2, namely the 5G control plane processing unit and the 5G user plane processing unit. The 5G control plane processing unit may include the access and mobility management function (AMF) network element and the session management function (SMF) network element shown in Figure 2, and may also include policy control function (PCF) network elements, unified data management (UDM) network elements, application function (AF) network elements, location management function (LMF) network elements, etc., not shown in Figure 2. The ground station is responsible for forwarding signaling and service data between the satellite (access network equipment) and the core network equipment. The functions of terminal equipment and various network devices are as described above and will not be repeated here.

[0168] Taking the integration of satellite and 5G networks as an example, the integration of satellite and 5G will give full play to their respective advantages and provide users with more comprehensive and high-quality services, mainly reflected in the following aspects:

[0169] (1) In remote areas, on airplanes or on ocean-going ships where terrestrial 5G networks cannot cover, satellites can provide economical and reliable network services, extending the network to places where terrestrial networks cannot reach.

[0170] (2) Satellites can provide continuous and uninterrupted network connections for IoT devices and mobile carriers such as airplanes, ships, trains and cars. After satellites are integrated with 5G, the service capabilities of 5G systems in this regard can be greatly enhanced.

[0171] (3) The superior broadcast / multicast capabilities of satellites can provide efficient data distribution services for network edge and user terminals.

[0172] Compared to earlier satellite mobile communication systems, the current development of satellite mobile communication exhibits the following characteristics:

[0173] (1) Miniaturization of mobile terminals: Supports a variety of mobile communication terminals, including handheld devices.

[0174] (2) Broadband communication services: In addition to traditional narrowband voice services, high-speed data services and network multimedia communication services are also provided.

[0175] One project within the 3GPP standard aims to apply existing 3GPP standard technologies to the Iridium satellite constellation for commercial applications. By appropriately adapting to the existing 3GPP standard for narrowband Internet of Things (NB-IoT), the protocol can operate based on the frame structure characteristics of Iridium.

[0176] Please refer to Figure 3, which is a schematic diagram of the Iridium satellite frame structure. As shown in Figure 3, the Iridium satellite frame structure period (or frame period) is 90ms, of which each uplink (UL) and downlink (DL) time slot occupies a duration of 8.28ms, and also includes a 20.32ms simplex time slot for broadcasting.

[0177] The 3GPP NB IoT standard uses a 1ms subframe as a basic scheduling time unit. One subframe includes two time slots, and the frame structure period is 10ms. Therefore, it is quite different from the frame structure and period of Iridium.

[0178] The 3GPP standard includes two scheduling tables, Table 1 and Table 2, which correspond to FDD and TDD, respectively.

[0179] Table 1

[0180] Table 2

[0181] Among them, I Delay This represents the scheduling delay index, and k0 represents the scheduling delay parameter.

[0182] The terminal indicates the scheduling delay index I via control signals. Delay The starting point of the time-domain transmission resources for uplink or downlink data scheduled by control signals can be determined. The starting point of the scheduling delay parameter (or the scheduling delay start point) is generally the ending point of the control signal transmission.

[0183] In addition to the scheduling delay parameter, other extended parameters may be added to increase the scheduling delay. These extended parameters may be protocol-defined processing delays, which are fixed parameters, or they may be extended parameters indicated by higher-layer signaling, which are relatively fixed. Therefore, this is mainly achieved through the I / O control signals. Delay This allows for greater flexibility in scheduling.

[0184] For example, in TDD communication, assuming the control signal transmission ends in the nth subframe, the terminal starts transmitting the uplink data scheduled by the control signal at the end of the k0th subframe after n+8 subframes.

[0185] For example, in FDD communication, assuming the control signal transmission ends in the nth subframe, then the terminal will transmit the signal in the (n+k)th subframe. offset At the end of each subframe, uplink data scheduled by control signals begins to be transmitted. Where k offset It is a delay parameter in the higher-level signaling configuration and is updated relatively infrequently.

[0186] Because the frame period in the 3GPP standard is 10ms, and each 10ms segment has both uplink and downlink resources, the uplink and downlink intervals are relatively small, allowing for smaller values ​​for the scheduling delay parameter. However, Iridium's frame structure has a period of 90ms, with each time slot lasting 8.28ms, resulting in larger uplink and downlink intervals. If the existing scheduling delay from the 3GPP standard were directly applied to Iridium's frame structure, the values ​​for the scheduling delay parameter would be limited (e.g., only larger values ​​could be obtained), thus restricting scheduling flexibility.

[0187] Therefore, how to achieve flexible scheduling under the new frame structure is a technical problem to be solved.

[0188] Based on this, embodiments of this application provide a communication method and apparatus that, by redefining the starting point of the scheduling delay parameter (hereinafter referred to as the scheduling delay starting point), enables flexible scheduling of uplink and downlink data under the new frame structure.

[0189] The following section uses the application to frame structure #1 as an example to introduce the technical solution of this application in detail.

[0190] Please refer to Figure 4, which is a schematic diagram of a frame structure #1 provided in an embodiment of this application. Figure 4 shows a frame period of frame structure #1, which sequentially includes downlink time domain resources (DL), guard time (GT) resources, and uplink time domain resources (UL). That is, there are guard time domain resources between downlink time domain resources and uplink time domain resources.

[0191] Optionally, the downlink time domain resources include continuous downlink time units, the protection band time domain resources include continuous protection band time units, and the uplink time domain resources include continuous uplink time units.

[0192] For example, the frame period is 90ms, the downlink time domain resource is 40ms, the guard band time domain resource is 30ms, and the uplink time domain resource is 20ms. That is, the frame period includes 90 subframes, the downlink time domain resource includes 40 downlink subframes, the guard band time domain resource includes 30 guard band subframes, and the uplink time domain resource includes 20 uplink subframes. Each downlink subframe (denoted by D in the figure) is 1ms, and each uplink subframe (denoted by U in the figure) is 1ms.

[0193] It should be understood that in other examples, the frame period, downlink time domain resource, guard band time domain resource, or uplink time domain resource may be of other lengths, and the embodiments of this application do not limit this.

[0194] The communication method provided in the embodiments of this application will be described in detail below.

[0195] The communication devices involved in this communication method may include terminal devices and network devices. Its system architecture can be seen in the description of Figure 1 or Figure 2, and will not be repeated here. Optionally, this communication method is applicable to NTN communication scenarios, that is, the network devices in the communication system can be non-terrestrial network devices.

[0196] Please refer to Figure 5, which is a flowchart illustrating a communication method provided in an embodiment of this application. The embodiment shown in Figure 5 uses a terminal device and a network device as the main entities performing the interaction to illustrate the method.

[0197] As shown in Figure 5, the communication method may include, but is not limited to, the following steps S501 to S502.

[0198] S501, the network device sends downlink control information to the terminal device, and correspondingly, the terminal device receives the downlink control information from the network device.

[0199] The downlink control information is used to indicate the scheduling delay parameter K, where K is a positive integer. For example, the downlink control information can directly indicate the scheduling delay parameter K. Alternatively, the downlink control information can indicate the index of the scheduling delay parameter K, thereby indirectly indicating K. After receiving the downlink control information, the terminal device can determine the scheduling delay parameter K based on this information.

[0200] S502, the terminal device starts sending first data from the first time unit, and correspondingly, the network device starts receiving first data from the first time unit.

[0201] The first time unit can be understood as the starting point of the time-domain resources used to transmit the first data. Taking uplink scheduling as an example, the first data can be uplink data, and the first time unit can also be understood as the starting point of the scheduled uplink data, or the starting position of the terminal device sending uplink data, or the starting position of the network device receiving uplink data.

[0202] Specifically, the first time unit is the time unit after the start of the scheduling delay. Let the start of the scheduling delay be denoted as time unit n, then the first time unit is the time unit after time unit n. Here, n is a positive integer.

[0203] The number of uplink time units between the first time unit and time unit n is related to the scheduling delay parameter K. The terminal device can determine the first time unit based on time unit n and the scheduling delay parameter K. For example, the number of uplink time units between the first time unit and time unit n can be determined based solely on the scheduling delay parameter K. Alternatively, the number of uplink time units between the first time unit and time unit n can be determined based on the scheduling delay parameter K and other information (such as other predefined or preconfigured parameters).

[0204] Time unit n is later than the time unit used to carry downlink control information; that is, time unit n is the time unit following the time unit used to carry downlink control information. The time unit used to carry downlink control information can be the last time unit of the time-domain resources used to carry downlink control information, or the end time unit of downlink control information. Downlink control information is transmitted through the physical downlink control channel (PDCCH). Optionally, the time unit used to carry downlink control information can also be the end time unit of the PDCCH.

[0205] Optionally, time unit n is not earlier than the last downlink time unit in the current frame period. Here, the current frame period is the frame period used to carry downlink control information, that is, the frame period in which the time-domain resources used to carry downlink control information reside.

[0206] The time unit in this application may be, but is not limited to, a subframe, a time slot, a micro-time slot, or a symbol. For ease of description, the embodiments of this application are illustrated using a subframe as the time unit.

[0207] Below are some examples of uplink scheduling delays.

[0208] Example A1: Time unit n is the first uplink time unit within the current frame period, and the first time unit is the Kth uplink time unit after time unit n.

[0209] It can be understood that in Example A1, the number of uplink time units between the first time unit and time unit n is K. Alternatively, the time interval between the first time unit and time unit n includes K uplink time units. Or, the first time unit is the Kth uplink time unit immediately following time unit n.

[0210] Therefore, the terminal device starts sending uplink data from the Kth uplink time unit immediately following time unit n, and correspondingly, the network device starts receiving uplink data from the Kth uplink time unit immediately following time unit n.

[0211] Please refer to Figure 6, which is a schematic diagram of an example A1 of an uplink scheduling delay provided in an embodiment of this application. As shown in Figure 6, time unit m represents the end time unit of downlink control information, time unit n represents the start point of scheduling delay, and time unit n+K represents the start point of uplink data scheduling, i.e., the first time unit.

[0212] Here, time unit m is contained in the continuous downlink time units within the current frame period, time unit n is the first uplink time unit in the continuous uplink time units within the current frame period, and time unit n+K is the Kth uplink time unit after time unit n.

[0213] The above scheme uses the first uplink time unit (or the starting point of continuous uplink resources) within the current frame period as the starting point of the scheduling delay. In other words, the scheduling delay parameter is calculated from the starting point of continuous uplink resources within the current frame period. Therefore, downlink resources and guard band resources within the current frame period are not included in the scheduling delay parameter, meaning the scheduling delay parameter does not need to cover the length of downlink resources and guard band resources. This allows the scheduling delay parameter to be flexibly set, enabling flexible scheduling of uplink data transmission positions by the terminal device in new frame periods, thus achieving flexible uplink data scheduling.

[0214] As an example, in Figure 6, the continuous uplink time unit is 20ms, comprising 20 uplink subframes. Time unit n (i.e., the starting point of scheduling delay) is the first uplink subframe, K=8, thus the first time unit (i.e., the starting point of scheduled uplink data) is the Kth uplink subframe after time unit n, i.e., the 9th uplink subframe. In this example, the downlink control information and its scheduled uplink data are within the same frame period, and the downlink control information of the current frame period schedules the uplink resources of the current frame period.

[0215] When the downlink control information of the current frame period schedules the uplink resources of the current frame period, and time unit n is the first uplink time unit in the current frame period, the first time unit being the Kth uplink time unit after time unit n can be equivalent to the first time unit being the Kth time unit after time unit n.

[0216] In other examples, the network side can also perform cross-frame period scheduling, meaning that the downlink control information of the current frame period can schedule uplink resources in the frame period following the current frame period. For example, the downlink control information of the current frame period can schedule uplink resources in the first frame period (or the next frame period) immediately following the current frame period. Another example is that the downlink control information of the current frame period can schedule uplink resources in the T-th frame period immediately following the current frame period, where T is an integer greater than 1. In other words, cross-frame period scheduling can span one or more frame periods, and this application embodiment does not impose any limitations on this.

[0217] Please refer to Figure 7, which is another schematic diagram of an example A1 of an uplink scheduling delay provided in an embodiment of this application. In Figure 7, the continuous uplink time unit is 20ms, including 20 uplink subframes. Time unit n (i.e., the starting point of the scheduling delay) is the first uplink subframe, and the first time unit (i.e., the starting point of the scheduled uplink data) is the Kth uplink subframe after time unit n. It can be understood that when K is greater than or equal to 20, the starting point of the scheduled uplink data falls into the next frame period.

[0218] For example, as shown in Figure 7, K = 32, so the starting point of the scheduled uplink data is the 33rd uplink subframe after time unit n. In this example, the downlink control information and its scheduled uplink data are not in the same frame period; the downlink control information of the current frame period schedules the uplink resources of the next frame period.

[0219] When downlink control information in the current frame period schedules uplink resources for the next frame period, the scheduling delay is very large because there are two consecutive guard band resources and one consecutive downlink resource between the downlink resources in the current frame period and the uplink resources in the next frame period. The corresponding scheduling delay parameters cannot cover a large scheduling delay range. To solve the problem of cross-frame period scheduling, the terminal device does not include the consecutive downlink resources and guard band resources in the next frame period in the scheduling delay parameters. This further enhances the flexibility of scheduling, supports cross-frame period scheduling, and eliminates the need to extend the existing scheduling delay. Furthermore, considering the limited uplink resources within a frame period, in cases with a high repetition rate, it is necessary to delay to the next frame period to ensure data transmission performance.

[0220] Example A2: Time unit n is the last guard band time unit in the current frame period, and the first time unit is the Kth uplink time unit after time unit n.

[0221] It can be understood that in Example A2, the number of uplink time units between the first time unit and time unit n is K. Alternatively, the time interval between the first time unit and time unit n includes K uplink time units. Or, the first time unit is the Kth uplink time unit immediately following time unit n.

[0222] Therefore, the terminal device starts sending uplink data from the Kth uplink time unit immediately following time unit n, and correspondingly, the network device starts receiving uplink data from the Kth uplink time unit immediately following time unit n.

[0223] Please refer to Figure 8, which is a schematic diagram of an example A2 of uplink scheduling delay provided in an embodiment of this application. As shown in Figure 8, time unit m represents the end time unit of downlink control information, time unit n represents the start point of scheduling delay, and time unit n+K represents the start point of uplink data scheduling, i.e., the first time unit.

[0224] Here, time unit m is contained in the continuous downlink time units within the current frame period, time unit n is the last guard band time unit in the continuous guard band time units within the current frame period, and time unit n+K is the Kth uplink time unit after time unit n.

[0225] It can be understood that the time unit following the last guard band time unit in the current frame period is the first uplink time unit in the current frame period.

[0226] The above scheme uses the last protection band time unit (or the end point of the continuous protection band resource) in the current frame period as the starting point for scheduling delay. In other words, the scheduling delay parameter is calculated from the end point of the continuous protection band resource in the current frame period. Therefore, downlink resources and protection band resources in the current frame period are not included in the scheduling delay parameter, meaning the scheduling delay parameter does not need to cover the length of downlink resources and protection band resources. This allows the scheduling delay parameter to be flexibly set, enabling flexible scheduling of the uplink data transmission position of the terminal device in a new frame period, thus achieving flexible uplink data scheduling.

[0227] As an example, in Figure 8, the continuous uplink time unit is 20ms, comprising 20 uplink subframes. Time unit n (i.e., the starting point of the scheduling delay) is the last guard band subframe (i.e., the subframe preceding the first uplink subframe), and K=8. Therefore, the first time unit (i.e., the starting point of the scheduled uplink data) is the Kth uplink subframe after time unit n, i.e., the 8th uplink subframe. In this example, the downlink control information and its scheduled uplink data are within the same frame period, and the downlink control information of the current frame period schedules the uplink resources of the current frame period.

[0228] When the downlink control information of the current frame period schedules the uplink resources of the current frame period, and time unit n is the last guard band time unit in the current frame period, the first time unit being the Kth uplink time unit after time unit n can be equivalent to the first time unit being the Kth time unit after time unit n.

[0229] In other examples, the network side can also perform cross-frame period scheduling. For a description of cross-frame period scheduling, please refer to the relevant descriptions in the preceding embodiments; they will not be repeated here. For example, in the cross-frame period scheduling shown in Figure 7, time unit n (i.e., the scheduling delay start point) can be replaced by the last guard band subframe (i.e., the subframe preceding the first uplink subframe), and correspondingly, the first time unit (i.e., the scheduling uplink data start point) can be replaced by the 32nd uplink subframe after time unit n.

[0230] Example A3: Time unit n is the first uplink time unit within the current frame period, and the first time unit is the K+K offset uplink time unit after time unit n.

[0231] Where Koffset is the number of predefined or preconfigured time units, and Koffset is a positive integer.

[0232] Optionally, Koffset is a fixed parameter agreed upon by the protocol. For example, Koffset is 8.

[0233] Alternatively, Koffset is an offset parameter configured by the network device via higher-layer signaling. For example, the network device can send configuration information to the terminal device, and the terminal device receives the configuration information from the network device, which includes an indication of Koffset, and the terminal device can obtain Koffset based on the configuration information.

[0234] It can be understood that in Example A3, the number of uplink time units between the first time unit and time unit n is K+Koffset. Alternatively, the time interval between the first time unit and time unit n includes K+Koffset uplink time units. Or, the first time unit is the K+Koffset-th uplink time unit immediately following time unit n.

[0235] Therefore, the terminal device starts sending uplink data from the K+K offset uplink time unit immediately following time unit n, and correspondingly, the network device starts receiving uplink data from the K+K offset uplink time unit immediately following time unit n.

[0236] Please refer to Figure 9, which is a schematic diagram of an example A3 of uplink scheduling delay provided in an embodiment of this application. As shown in Figure 9, time unit m represents the end time unit of downlink control information, time unit n represents the start point of scheduling delay, and time unit n+K+Koffset represents the start point of uplink data scheduling, i.e., the first time unit.

[0237] Here, time unit m is contained in the continuous downlink time units within the current frame period, time unit n is the first uplink time unit in the continuous uplink time units within the current frame period, and time unit n+K+Koffset is the K+Koffset-th uplink time unit after time unit n.

[0238] The above scheme uses the first uplink time unit (or the starting point of continuous uplink resources) within the current frame period as the starting point of the scheduling delay. This means the scheduling delay parameter is calculated from the starting point of continuous uplink resources within the current frame period. Therefore, downlink resources and guard band resources within the current frame period are not included in the scheduling delay parameter, meaning the scheduling delay parameter does not need to cover the length of downlink resources and guard band resources. This allows the scheduling delay parameter to have flexible values, enabling flexible scheduling of the position where the terminal device transmits uplink data in a new frame period, achieving flexible uplink data scheduling. Furthermore, an additional parameter, Koffset, is added to extend the scheduling delay, further enhancing scheduling flexibility.

[0239] As an example, in Figure 9, the continuous uplink time unit is 20ms, comprising 20 uplink subframes. Time unit n (i.e., the starting point of the scheduling delay) is the first uplink subframe, K=8, Koffset=8. Therefore, the first time unit (i.e., the starting point of the scheduled uplink data) is the K+Koffset-th uplink subframe after time unit n, i.e., the 17th uplink subframe. In this example, the downlink control information and its scheduled uplink data are within the same frame period. The downlink control information of the current frame period schedules the uplink resources of the current frame period.

[0240] When the downlink control information of the current frame period schedules the uplink resources of the current frame period, and time unit n is the first uplink time unit in the current frame period, the first time unit being the K+K offset uplink time unit after time unit n can be equivalent to the first time unit being the K+K offset time unit after time unit n.

[0241] In other examples, the network can also schedule across frame periods. For a description of cross-frame period scheduling, please refer to the relevant descriptions in the preceding embodiments; they will not be repeated here. For example, in the cross-frame period scheduling shown in Figure 7, K = 32 can be replaced with K + Koffset = 40, and correspondingly, the first time unit (i.e., the starting point of the scheduled uplink data) can be replaced with the 41st uplink subframe after time unit n.

[0242] Example A4: Time unit n is the last guard band time unit in the current frame period, and the first time unit is the K+K offset uplink time unit after time unit n.

[0243] For a description of Koffset, please refer to the relevant description in Example A3, which will not be repeated here.

[0244] It can be understood that in Example #4, the number of uplink time units between the first time unit and time unit n is K+Koffset. Alternatively, the time interval between the first time unit and time unit n includes K+Koffset uplink time units. Or, the first time unit is the K+Koffset-th uplink time unit immediately following time unit n.

[0245] Therefore, the terminal device starts sending uplink data from the K+K offset uplink time unit immediately following time unit n, and correspondingly, the network device starts receiving uplink data from the K+K offset uplink time unit immediately following time unit n.

[0246] Please refer to Figure 10, which is a schematic diagram of an example A4 of an uplink scheduling delay provided in an embodiment of this application. As shown in Figure 10, time unit m represents the end time unit of downlink control information, time unit n represents the start point of scheduling delay, and time unit n+K+Koffset represents the start point of the scheduled uplink data, that is, the first time unit.

[0247] Here, time unit m is contained in the continuous downlink time units within the current frame period, time unit n is the last guard band time unit in the continuous guard band time units within the current frame period, and time unit n+K+Koffset is the K+Koffset-th uplink time unit after time unit n.

[0248] The above scheme uses the last protection band time unit (or the end point of the continuous protection band resource) in the current frame period as the starting point for the scheduling delay. In other words, the scheduling delay parameter is calculated from the end point of the continuous protection band resource in the current frame period. Therefore, downlink resources and protection band resources in the current frame period are not included in the scheduling delay parameter, meaning the scheduling delay parameter does not need to cover the length of downlink resources and protection band resources. This allows the scheduling delay parameter to have flexible values, enabling flexible scheduling of the position where the terminal device sends uplink data in a new frame period, achieving flexible uplink data scheduling. Furthermore, an additional parameter, Koffset, is added to extend the scheduling delay, further enhancing scheduling flexibility.

[0249] As an example, in Figure 10, the continuous uplink time unit is 20ms, comprising 20 uplink subframes. Time unit n (i.e., the starting point of the scheduling delay) is the last guard band subframe (i.e., the subframe preceding the first uplink subframe), K=8, Koffset=8, thus the first time unit (i.e., the starting point of the scheduled uplink data) is the K+Koffset-th uplink subframe after time unit n, i.e., the 16th uplink subframe. In this example, the downlink control information and its scheduled uplink data are within the same frame period; the downlink control information of the current frame period schedules the uplink resources of the current frame period.

[0250] When the downlink control information of the current frame period schedules the uplink resources of the current frame period, and time unit n is the last guard band time unit in the current frame period, the first time unit being the K+K offset uplink time unit after time unit n can be equivalent to the first time unit being the K+K offset time unit after time unit n.

[0251] In other examples, the network side can also perform cross-frame period scheduling. For a description of cross-frame period scheduling, please refer to the relevant descriptions in the preceding embodiments; they will not be repeated here. For example, in the cross-frame period scheduling shown in Figure 7, time unit n (i.e., the starting point of the scheduling delay) can be replaced with the last guard band subframe (i.e., the subframe preceding the first uplink subframe), K = 32 can be replaced with K + Koffset = 40, and correspondingly, the first time unit (i.e., the starting point of the scheduled uplink data) can be replaced with the 40th uplink subframe after time unit n.

[0252] In Example A5, time unit n is the last downlink time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0253] The description of Koffset can be found in Example A3, and will not be repeated here. G represents the number of time units of the guard band within a frame period. Taking frame structure #1 shown in Figure 4 as an example, G = 30.

[0254] It can be understood that, in Example A5, the number of uplink time units between the first time unit and time unit n is K + Koffset - G. Alternatively, the time interval between the first time unit and time unit n includes K + Koffset - G uplink time units. Or, the first time unit is the K + Koffset - Gth uplink time unit immediately following time unit n.

[0255] Therefore, the terminal device starts sending uplink data from the K+Koffset-Gth uplink time unit immediately following time unit n, and correspondingly, the network device starts receiving uplink data from the K+Koffset-Gth uplink time unit immediately following time unit n.

[0256] Please refer to Figure 11, which is a schematic diagram of an example A5 of uplink scheduling delay provided in an embodiment of this application. As shown in Figure 11, time unit m represents the end time unit of downlink control information, time unit n represents the start point of scheduling delay, and time unit n+K+Koffset-G represents the start point of uplink data scheduling, that is, the first time unit.

[0257] Here, time unit m is contained in the continuous downlink time units within the current frame period, time unit n is the last downlink time unit in the continuous downlink time units within the current frame period, and time unit n+K+Koffset-G is the K+Koffset-Gth uplink time unit after time unit n.

[0258] The above scheme uses the last downlink time unit (or the end point of continuous downlink resources) in the current frame period as the starting point for scheduling delay. In other words, the scheduling delay parameter is calculated from the end point of continuous downlink resources in the current frame period. An additional parameter, Koffset, is added to extend the scheduling delay. The length of Koffset can be used to cover the length of the guard band resources, thus the downlink resources and guard band resources in the current frame period are not included in the scheduling delay parameter. This means the scheduling delay parameter does not need to cover the length of downlink resources and guard band resources. Therefore, the scheduling delay parameter can be flexibly valued, allowing for flexible scheduling of the uplink data transmission position of the terminal device in a new frame period, achieving flexible uplink data scheduling. Furthermore, it is more compatible with the scheduling delay methods in existing FDD communication.

[0259] As an example, in Figure 11, the continuous protection band time unit is 30ms, including 30 protection band subframes, G=30; the continuous uplink time unit is 20ms, including 20 uplink subframes; time unit n (i.e., the starting point of the scheduling delay) is the last downlink subframe, K=8, Koffset=30; therefore, the first time unit (i.e., the starting point of the scheduled uplink data) is the K+Koffset-G uplink subframe after time unit n, i.e., the 8th uplink subframe. In this example, the downlink control information and its scheduled uplink data are within the same frame period; the downlink control information of the current frame period schedules the uplink resources of the current frame period.

[0260] When the downlink control information of the current frame period schedules the uplink resources of the current frame period, and time unit n is the last downlink time unit in the current frame period, the first time unit being the K+Koffset-Gth uplink time unit after time unit n can be equivalent to the first time unit being the K+Koffsetth time unit after time unit n.

[0261] In other examples, the network can also schedule across frame periods. For a description of cross-frame period scheduling, please refer to the relevant descriptions in the preceding embodiments; they will not be repeated here.

[0262] Please refer to Figure 12, which is another schematic diagram of an example A5 of an uplink scheduling delay provided in an embodiment of this application. In Figure 12, the continuous guard band time unit is 30ms, including 30 guard band subframes, G=30; the continuous uplink time unit is 20ms, including 20 uplink subframes, S1=G+20; time unit n (i.e., the starting point of the scheduling delay) is the last downlink subframe; and the first time unit (i.e., the starting point of the scheduled uplink data) is the K+Koffset-Gth uplink subframe after time unit n. When K+Koffset-G is greater than or equal to 20, that is, when K+Koffset-G-20 is greater than or equal to 0, that is, when K+Koffset-S1 is greater than or equal to 0, that is, when S2 is greater than or equal to 0, the starting point of the scheduled uplink data falls into the next frame period. Wherein, S1+S2=K+Koffset.

[0263] For example, as shown in Figure 12, K = 32 and Koffset = 30, so the starting point of the scheduled uplink data is the 32nd uplink subframe after time unit n. In this example, the downlink control information and the scheduled uplink data are not in the same frame period; the downlink control information of the current frame period schedules the uplink resources of the next frame period.

[0264] Example A6: Time unit n is the first guard band time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0265] The description of Koffset can be found in Example #3, and will not be repeated here. G is the number of time units of the guard band within one frame period. Taking the frame structure #1 shown in Figure 4 as an example, G = 30.

[0266] It can be understood that, in Example A6, the number of uplink time units between the first time unit and time unit n is K + Koffset - G. Alternatively, the time interval between the first time unit and time unit n includes K + Koffset - G uplink time units. Or, the first time unit is the K + Koffset - Gth uplink time unit immediately following time unit n.

[0267] Therefore, the terminal device starts sending uplink data from the K+Koffset-Gth uplink time unit immediately following time unit n, and correspondingly, the network device starts receiving uplink data from the K+Koffset-Gth uplink time unit immediately following time unit n.

[0268] Please refer to Figure 13, which is a schematic diagram of an example A6 of uplink scheduling delay provided in an embodiment of this application. As shown in Figure 13, time unit m represents the end time unit of downlink control information, time unit n represents the start point of scheduling delay, and time unit n+K+Koffset-G represents the start point of uplink data scheduling, that is, the first time unit.

[0269] Here, time unit m is contained in the continuous downlink time units within the current frame period, time unit n is the first guard band time unit in the continuous guard band time units within the current frame period, and time unit n+K+Koffset-G is the K+Koffset-Gth uplink time unit after time unit n.

[0270] It can be understood that the time unit preceding the first guard band time unit in the continuous guard band time units within the current frame period is the last downlink time unit in the continuous downlink time units within the current frame period.

[0271] The above scheme uses the first protection band time unit (or the start point of the continuous protection band resource) within the current frame period as the starting point of the scheduling delay. In other words, the scheduling delay parameter is calculated from the start point of the continuous protection band resource within the current frame period. An additional parameter, Koffset, is added to extend the scheduling delay. The length of Koffset can be used to cover the length of the protection band resource, thus excluding downlink resources and protection band resources within the current frame period from the scheduling delay parameter. This means the scheduling delay parameter does not need to cover the length of downlink resources and protection band resources. Therefore, the scheduling delay parameter can be flexibly set, allowing for flexible scheduling of the uplink data transmission position of the terminal device in a new frame period, achieving flexible uplink data scheduling. Furthermore, it is more compatible with the scheduling delay methods in existing FDD communication.

[0272] As an example, in Figure 13, the continuous protection band time unit is 30ms, including 30 protection band subframes, G=30; the continuous uplink time unit is 20ms, including 20 uplink subframes; time unit n (i.e., the starting point of scheduling delay) is the first protection band subframe, K=8, Koffset=30; therefore, the first time unit (i.e., the starting point of scheduled uplink data) is the K+Koffset-G uplink subframe after time unit n, i.e., the 8th uplink subframe. In this example, the downlink control information and its scheduled uplink data are within the same frame period; the downlink control information of the current frame period schedules the uplink resources of the current frame period.

[0273] When the downlink control information of the current frame period schedules the uplink resources of the current frame period, and time unit n is the first guard band time unit in the current frame period, the first time unit being the K+Koffset-Gth uplink time unit after time unit n can be equivalent to the first time unit being the K+Koffsetth time unit after time unit n.

[0274] In other examples, the network side can also perform cross-frame period scheduling. For a description of cross-frame period scheduling, please refer to the relevant descriptions in the preceding embodiments; they will not be repeated here. For example, in the cross-frame period scheduling shown in Figure 12, time unit n (i.e., the starting point of the scheduling delay) can be replaced by the first guard band subframe (i.e., the subframe following the last downlink subframe).

[0275] The above describes an example of uplink scheduling delay. The following describes an example of downlink scheduling delay.

[0276] Please refer to Figure 14, which is a flowchart illustrating another communication method provided in an embodiment of this application. The embodiment shown in Figure 14 uses a terminal device and a network device as the main entities performing the interaction to illustrate the method.

[0277] As shown in Figure 14, the communication method may include, but is not limited to, the following steps S1401 to S1402.

[0278] S1401, the network device sends downlink control information to the terminal device, and correspondingly, the terminal device receives the downlink control information from the network device.

[0279] The downlink control information is used to indicate the scheduling delay parameter K, where K is a positive integer. For example, the downlink control information can directly indicate the scheduling delay parameter K. Alternatively, the downlink control information can indicate the index of the scheduling delay parameter K, thereby indirectly indicating K. After receiving the downlink control information, the terminal device can determine the scheduling delay parameter K based on this information.

[0280] S1402, the network device starts sending second data from the second time unit, and correspondingly, the terminal device starts receiving second data from the second time unit.

[0281] The second time unit can be understood as the starting point of the time-domain resources used to transmit the second data. Taking downlink scheduling as an example, the second data can be downlink data, and the second time unit can also be understood as the starting point of the downlink data scheduling, or the starting position of the network device sending downlink data, or the starting position of the terminal device receiving downlink data.

[0282] Specifically, the second time unit is the time unit following the start of the scheduling delay. Let the start of the scheduling delay be denoted as time unit n, then the second time unit is the time unit following time unit n. Here, n is a positive integer.

[0283] The number of downlink time units between the second time unit and time unit n is related to the scheduling delay parameter K. For example, the number of downlink time units between the second time unit and time unit n can be determined based solely on the scheduling delay parameter K. Alternatively, the number of downlink time units between the second time unit and time unit n can be determined based on the scheduling delay parameter K and other information (such as other predefined or preconfigured parameters).

[0284] Due to the limited downlink resources within a frame period, the following situations may occur:

[0285] Scenario 1: The downlink control information and its scheduled downlink data are within the same frame period. In other words, the time unit used to carry the second data is within the current frame period. That is, the downlink control information of the current frame period schedules the downlink resources of the current frame period.

[0286] In this case, time unit n can be the end time unit of downlink control information, and the second time unit can be the Kth or K+Kth offset downlink time unit after time unit n.

[0287] Scenario 2: The downlink control information and the downlink data it schedules are not within the same frame period. In other words, the time unit used to carry the second data is not within the current frame period. Alternatively, the time unit used to carry the second data is within a frame period following the current frame period. That is, the downlink control information of the current frame period schedules downlink resources for a frame period following the current frame period.

[0288] For example, downlink control information for the current frame period can schedule downlink resources for the first frame period (or the next frame period) immediately following the current frame period. As another example, downlink control information for the current frame period can schedule downlink resources for the T-th frame period immediately following the current frame period, where T is an integer greater than 1.

[0289] In this case, time unit n is not earlier than the first downlink time unit in the next frame period, and the second time unit can be the Kth or K+Kth downlink time unit after time unit n.

[0290] Scenario 3: The downlink control information and a portion of the downlink data it schedules are within the same frame period, while the remaining downlink data is in the next frame period. In other words, a portion of the time units used to carry the second data are within the current frame period, while another portion of the time units used to carry the second data is in a frame period following the current one. That is, the downlink control information in the current frame period schedules downlink resources for both the current and next frame periods.

[0291] In this case, for downlink data in the current frame period, time unit n can be the end time unit of downlink control information, and the second time unit can be the Kth or K+Kth offset downlink time unit after time unit n. For downlink data in the next frame period, time unit n is not earlier than the first downlink time unit in the next frame period, and the second time unit can be the Kth or K+Kth offset downlink time unit after time unit n.

[0292] Optionally, the downlink control information may also be used to indicate the above-mentioned situation one, situation two, or situation three. For example, the downlink control information may indicate that the downlink data it schedules is in the same frame period; or indicate that the downlink data it schedules is not in the same frame period; or indicate that part of the downlink data it schedules is in the current frame period, and another part of the downlink data is in a frame period after the current frame period. Thus, the terminal device can determine the corresponding time unit n and the second time unit according to the above indications.

[0293] Below are some examples of downlink scheduling delays.

[0294] Example B1: Time unit n is the first downlink time unit in the next frame period of the current frame period, and the second time unit is the Kth downlink time unit after time unit n.

[0295] It can be understood that in Example B1, the number of downlink time units between the second time unit and time unit n is K. Alternatively, the time interval between the second time unit and time unit n includes K downlink time units. Or, the second time unit is the Kth downlink time unit immediately following time unit n.

[0296] Thus, the network device begins sending downlink data from the Kth downlink time unit immediately following time unit n, and correspondingly, the terminal device begins receiving downlink data from the Kth downlink time unit immediately following time unit n.

[0297] Please refer to Figure 15, which is a schematic diagram of an example B1 of a downlink scheduling delay provided in an embodiment of this application. As shown in Figure 15, time unit m represents the end time unit of downlink control information, time unit n represents the start point of scheduling delay, and time unit n+K represents the start point of the downlink data scheduling, that is, the second time unit.

[0298] Here, time unit m is contained in the continuous downlink time units within the current frame period, time unit n is the first downlink time unit in the continuous downlink time units within the next frame period within the current frame period, and time unit n+K is the Kth downlink time unit after time unit n.

[0299] The above scheme uses the first downlink time unit (or the start point of continuous downlink resources) in the next frame period as the starting point of the scheduling delay. This means the scheduling delay parameter is calculated from the start of the continuous downlink resources in the next frame period. Therefore, uplink resources and guard band resources in the current frame period are not included in the scheduling delay parameter, meaning the scheduling delay parameter does not need to cover the length of uplink and guard band resources. This allows the scheduling delay parameter to be flexibly set, enabling flexible scheduling of the terminal device's downlink data reception position in the new frame period, achieving flexible downlink data scheduling. Furthermore, considering the limited downlink resources within a frame period, in cases of high repetition frequency, a delay to the next frame period is necessary to ensure data transmission performance.

[0300] Example B2: Time unit n is the first downlink time unit in the next frame period after the current frame period, and the second time unit is the K+K offset downlink time unit after time unit n.

[0301] Where Koffset is the number of predefined or preconfigured time units, and Koffset is a positive integer.

[0302] Optionally, Koffset is a fixed parameter agreed upon by the protocol. For example, Koffset is 8.

[0303] Alternatively, Koffset is an offset parameter configured by the network device via higher-layer signaling. For example, the network device can send configuration information to the terminal device, and the terminal device receives the configuration information from the network device, which includes an indication of Koffset, and the terminal device can obtain Koffset based on the configuration information.

[0304] It can be understood that, in Example B2, the number of downlink time units between the second time unit and time unit n is K+Koffset. Alternatively, the time interval between the second time unit and time unit n includes K+Koffset downlink time units. Or, the second time unit is the K+Koffset-th downlink time unit immediately following time unit n.

[0305] Therefore, the network device starts sending downlink data from the K+K offset downlink time unit immediately following time unit n, and correspondingly, the terminal device starts receiving downlink data from the K+K offset downlink time unit immediately following time unit n.

[0306] Please refer to Figure 16, which is a schematic diagram of an example B2 of a downlink scheduling delay provided in an embodiment of this application. As shown in Figure 16, time unit m represents the end time unit of downlink control information, time unit n represents the start point of scheduling delay, and time unit n+K+Koffset represents the start point of the scheduled downlink data, that is, the second time unit.

[0307] Here, time unit m is contained in the continuous downlink time units within the current frame period, time unit n is the first downlink time unit in the continuous downlink time units within the next frame period within the current frame period, and time unit n+K+Koffset is the K+Koffset-th downlink time unit after time unit n.

[0308] The above scheme uses the first downlink time unit (or the start point of continuous downlink resources) in the next frame period as the starting point of the scheduling delay. This means the scheduling delay parameter is calculated from the start of the continuous downlink resources in the next frame period, excluding uplink and guard band resources in the current frame period. Therefore, the scheduling delay parameter does not need to cover the length of uplink and guard band resources. This allows for flexible values ​​for the scheduling delay parameter, enabling flexible scheduling of the terminal device's downlink data reception position in the new frame period, achieving flexible downlink data scheduling. Furthermore, an additional parameter, Koffset, is added to extend the scheduling delay, further enhancing scheduling flexibility. Moreover, considering the limited downlink resources within a frame period, in cases of high repetition frequency, a delay to the next frame period is necessary to ensure data transmission performance.

[0309] The methods of the embodiments of this application have been described in detail above. The apparatus embodiments related to the embodiments of this application will be described below.

[0310] Please refer to Figure 17, which is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0311] As shown in Figure 17, the communication device 1700 may include a transceiver unit 1701. The transceiver unit 1701 may be software, hardware, or a combination of both.

[0312] The transceiver unit 1701 can implement sending and / or receiving functions, and can also be described as a communication unit. The transceiver unit 1701 can also be a unit integrating an acquisition unit and a sending unit, wherein the acquisition unit is used to implement the receiving function, and the sending unit is used to implement the sending function. Optionally, the transceiver unit 1701 can be used to receive information sent by other devices, and can also be used to send information to other devices.

[0313] In one possible design, the communication device 1700 may correspond to the terminal device in the above method embodiments. For example, the communication device 1700 may be the terminal device in the method embodiments shown in FIG. 5 or FIG. 14, or it may be a processor, circuit, chip, or chip system in the terminal device. The communication device 1700 may include units for performing the operations performed by the terminal device in the above method embodiments, and each unit in the communication device 1700 is for implementing the operations performed by the terminal device in the above method embodiments. The descriptions of each unit are as follows:

[0314] In one possible embodiment, the transceiver unit 1701 is configured to receive downlink control information, which is used to indicate a scheduling delay parameter K, where K is a positive integer; the transceiver unit 1701 is also configured to transmit first data starting from a first time unit, where the first time unit is the Kth, K+Koffset, or K+Koffset-Gth uplink time unit after time unit n; wherein time unit n is later than the time unit used to carry downlink control information, Koffset is a predefined or preconfigured number of time units, n and Koffset are both positive integers, and G is the number of time units in the guard band within one frame period.

[0315] In one possible implementation, time unit n is not earlier than the last downlink time unit in the current frame period, and the current frame period is a frame period used to carry downlink control information; the frame period includes, in sequence: downlink time unit, guard band time unit and uplink time unit.

[0316] In one possible implementation, time unit n is the first uplink time unit in the current frame period, and the first time unit is the Kth or K+K offset uplink time unit after time unit n.

[0317] In one possible implementation, time unit n is the last guard band time unit in the current frame period, and the first time unit is the Kth or K+K offset uplink time unit after time unit n.

[0318] In one possible implementation, time unit n is the last downlink time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0319] In one possible implementation, time unit n is the first guard band time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0320] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0321] In another possible embodiment, the transceiver unit 1701 is configured to receive downlink control information, which is used to indicate a scheduling delay parameter K, where K is a positive integer; the transceiver unit 1701 is also configured to receive second data starting from a second time unit, where the second time unit is the Kth or K+Koffset downlink time unit after time unit n; wherein, time unit n is later than the time unit used to carry downlink control information, Koffset is a predefined or preconfigured number of time units, and both n and Koffset are positive integers.

[0322] In one possible implementation, the downlink control information is also used to indicate that the time unit used to carry the second data is not within the current frame period; wherein the current frame period is the frame period used to carry the downlink control information.

[0323] In one possible implementation, the downlink control information is also used to indicate that: a portion of the time units used to carry the second data are within the current frame period, and another portion of the time units used to carry the second data are within a frame period after the current frame period; wherein, the current frame period is the frame period used to carry the downlink control information.

[0324] In one possible implementation, time unit n is no earlier than the first downlink time unit in the next frame period of the current frame period. The current frame period is a frame period used to carry downlink control information, and the frame period includes, in sequence, a downlink time unit, a guard band time unit, and an uplink time unit.

[0325] In one possible implementation, time unit n is the first downlink time unit in the next frame period of the current frame period.

[0326] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0327] In another possible design, the communication device 1700 may correspond to the network device in the above method embodiments. For example, the communication device 1700 may be the network device in the method embodiments shown in FIG. 5 or FIG. 14, or it may be a processor, circuit, chip, or chip system in the network device. The communication device 1700 may include units for performing the operations performed by the network device in the above method embodiments, and each unit in the communication device 1700 is for implementing the operations performed by the network device in the above method embodiments. The descriptions of each unit are as follows:

[0328] In one possible embodiment, the transceiver unit 1701 is configured to transmit downlink control information, which is used to indicate a scheduling delay parameter K, where K is a positive integer; the transceiver unit 1701 is also configured to receive first data starting from a first time unit, where the first time unit is the Kth, or K+Koffset, or K+Koffset-Gth uplink time unit after time unit n; wherein time unit n is later than the time unit used to carry downlink control information, Koffset is a predefined or preconfigured number of time units, n and Koffset are both positive integers, and G is the number of time units in the guard band within one frame period.

[0329] In one possible implementation, time unit n is not earlier than the last downlink time unit in the current frame period, and the current frame period is a frame period used to carry downlink control information; the frame period includes, in sequence: downlink time unit, guard band time unit and uplink time unit.

[0330] In one possible implementation, time unit n is the first uplink time unit in the current frame period, and the first time unit is the Kth or K+K offset uplink time unit after time unit n.

[0331] In one possible implementation, time unit n is the last guard band time unit in the current frame period, and the first time unit is the Kth or K+K offset uplink time unit after time unit n.

[0332] In one possible implementation, time unit n is the last downlink time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0333] In one possible implementation, time unit n is the first guard band time unit in the current frame period, and the first time unit is the K+Koffset-Gth uplink time unit after time unit n.

[0334] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0335] In another possible embodiment, the transceiver unit 1701 is configured to receive downlink control information, which is used to indicate a scheduling delay parameter K, where K is a positive integer; the transceiver unit 1701 is also configured to send second data starting from a second time unit, where the second time unit is the Kth or K+Koffset downlink time unit after time unit n; wherein time unit n is later than the time unit used to carry downlink control information, Koffset is a predefined or preconfigured number of time units, and both n and Koffset are positive integers.

[0336] In one possible implementation, the downlink control information is also used to indicate that the time unit used to carry the second data is not within the current frame period; wherein the current frame period is the frame period used to carry the downlink control information.

[0337] In one possible implementation, the downlink control information is also used to indicate that: a portion of the time units used to carry the second data are within the current frame period, and another portion of the time units used to carry the second data are within a frame period after the current frame period; wherein, the current frame period is the frame period used to carry the downlink control information.

[0338] In one possible implementation, time unit n is no earlier than the first downlink time unit in the next frame period of the current frame period. The current frame period is a frame period used to carry downlink control information, and the frame period includes, in sequence, a downlink time unit, a guard band time unit, and an uplink time unit.

[0339] In one possible implementation, time unit n is the first downlink time unit in the next frame period of the current frame period.

[0340] In one possible implementation, the time unit is any one of a subframe, a time slot, a micro-time slot, or a symbol.

[0341] According to embodiments of this application, the various units in the device shown in FIG17 can be individually or entirely merged into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effect of the embodiments of this application. The above units are based on logical function division. In practical applications, the function of one unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the above device may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0342] It should be noted that the implementation of each unit can also refer to the corresponding description in the above method embodiments.

[0343] Please refer to Figure 18, which is a schematic diagram of another communication device provided in an embodiment of this application. The communication device 1800 may include a processor 1801. Optionally, the communication device 1800 may also include a memory 1802. Further optionally, the communication device 1800 may also include a communication interface 1803 and a bus 1804. The processor 1801, memory 1802, and communication interface 1803 are interconnected via the bus 1804. The communication interface 1803 is used for data interaction with other devices.

[0344] The processor 1801 is a module that performs arithmetic and logical operations. It can be one or a combination of processing modules such as a central processing unit (CPU), a graphics processing unit (GPU), or a microprocessor unit (MPU). The processor 1801 can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0345] The memory 1802 is used to provide storage space, in which data such as the operating system and computer programs can be stored. The memory 1802 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0346] In one possible design, the communication device 1800 may correspond to the terminal device in the above method embodiments. For example, the communication device 1800 may be the terminal device in the above method embodiments, or it may be a processor, circuit, chip, or chip system in the terminal device. The communication device 1800 may include components for performing the operations performed by the terminal device in the above method embodiments. Furthermore, each component in the communication device 1800 is configured to implement the operations performed by the terminal device in the above method embodiments. The processor 1801 calls a computer program stored in the memory 1802 to execute the method shown in the above method embodiments.

[0347] In another possible design, the communication device 1800 may correspond to the network device in the above method embodiments. For example, the communication device 1800 may be the network device in the above method embodiments, or it may be a processor, circuit, chip, or chip system in the network device. The communication device 1800 may include components for performing the operations performed by the network device in the above method embodiments, and each component in the communication device 1800 is for implementing the operations performed by the network device in the above method embodiments. The processor 1801 calls the computer program stored in the memory 1802 to execute the method shown in the above method embodiments.

[0348] Alternatively, the communication device 1800 may be a chip or a chip system. For the case where the communication device 1800 is a chip or a chip system, refer to the schematic diagram of the chip structure shown in Figure 19.

[0349] As shown in Figure 19, chip 1900 includes processor 1901 and interface 1902. The number of processors 1901 can be one or more, and the number of interfaces 1902 can be multiple. It should be noted that the functions of processor 1901 and interface 1902 can be implemented through hardware design, software design, or a combination of both; no restrictions are placed here.

[0350] Optionally, the chip 1900 may also include a memory 1903 for storing necessary program instructions and data.

[0351] In this application, processor 1901 can be used to call an implementation program of the communication method in an electronic device provided by one or more embodiments of this application from memory 1903, and execute the instructions contained in the program. Interface 1902 can be used to output the execution result of processor 1901. In this application, interface 1902 can be specifically used to output various messages or information from processor 1901.

[0352] The communication methods provided by one or more embodiments of this application can be referred to the above-described method embodiments, and will not be repeated here.

[0353] According to the method provided in the embodiments of this application, the embodiments of this application also provide a computer-readable storage medium storing a computer program or instructions, which can implement the method shown in the above-described method embodiments when the computer program or instructions are run on a processor.

[0354] According to the method provided in the embodiments of this application, the embodiments of this application also provide a computer program product, which includes a computer program or instructions. When the computer program or instructions are run on a processor, they can implement the method shown in the above-described method embodiments.

[0355] According to the method provided in the embodiments of this application, the embodiments of this application also provide a communication system, which includes at least one of the above-mentioned communication devices 1700, or communication devices 1800, or chip 1900.

[0356] According to the method provided in the embodiments of this application, the embodiments of this application also provide a communication system, which includes a terminal device and a network device, wherein the terminal device is used to perform the steps performed by the terminal device in the above method embodiments, and the network device is used to perform the steps performed by the network device in the above method embodiments.

[0357] It should be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be a hard disk drive (HDD), a solid-state drive (SSD), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memory.

[0358] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. This computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, the processes or functions shown in the embodiments of this application are performed entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, a computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium that a computer can access, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; it can also be an optical medium, such as a digital video optical disc; or it can be a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or non-volatile storage medium, or may include both types of storage media.

[0359] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments provided herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0360] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0361] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0362] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0363] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0364] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the technology, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods shown in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0365] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A communication method, characterized in that, include: The terminal device receives downlink control information, which is used to indicate a scheduling delay parameter K, where K is a positive integer. The terminal device sends first data starting from the first time unit, where the first time unit is the Kth, or K+Koffset, or K+Koffset-Gth uplink time unit after time unit n; Wherein, the time unit n is later than the time unit used to carry the downlink control information, the Koffset is a predefined or preconfigured number of time units, both n and Koffset are positive integers, and G is the number of time units of the guard band in one frame period.

2. A communication method, characterized in that, include: The network device sends downlink control information, which is used to indicate a scheduling delay parameter K, where K is a positive integer. The network device receives first data starting from a first time unit, where the first time unit is the Kth, or K+Koffset, or K+Koffset-Gth uplink time unit after time unit n; Wherein, the time unit n is later than the time unit used to carry the downlink control information, the Koffset is a predefined or preconfigured number of time units, both n and Koffset are positive integers, and G is the number of time units of the guard band in one frame period.

3. The method according to claim 1 or 2, characterized in that, The time unit n is later than the time unit used to carry the downlink control information, including: The time unit n is not earlier than the last downlink time unit in the current frame period, and the current frame period is the frame period used to carry the downlink control information; The frame period includes, in sequence, a downlink time unit, a guard band time unit, and an uplink time unit.

4. The method according to claim 3, characterized in that, The time unit n is not earlier than the last downlink time unit in the current frame period, including: The time unit n is the first uplink time unit within the current frame period.

5. The method according to claim 3, characterized in that, The time unit n is not earlier than the last downlink time unit in the current frame period, including: The time unit n is the last guard band time unit in the current frame period.

6. The method according to claim 3, characterized in that, The time unit n is not earlier than the last downlink time unit in the current frame period, including: The time unit n is the last downlink time unit in the current frame period.

7. The method according to claim 3, characterized in that, The time unit n is not earlier than the last downlink time unit in the current frame period, including: The time unit n is the first guard band time unit within the current frame period.

8. The method according to any one of claims 1 to 7, characterized in that, The time unit can be any one of a subframe, a time slot, a micro-time slot, or a symbol.

9. A communication device, characterized in that, include: A transceiver unit is used to receive downlink control information, wherein the downlink control information is used to indicate a scheduling delay parameter K, and K is a positive integer. The transceiver unit is further configured to send first data starting from a first time unit, wherein the first time unit is the Kth, or K+Koffset, or K+Koffset-Gth uplink time unit after time unit n; Wherein, the time unit n is later than the time unit used to carry the downlink control information, the Koffset is a predefined or preconfigured number of time units, both n and Koffset are positive integers, and G is the number of time units of the guard band in one frame period.

10. A communication device, characterized in that, include: A transceiver unit is used to send downlink control information, wherein the downlink control information is used to indicate a scheduling delay parameter K, where K is a positive integer. The transceiver unit is further configured to receive first data starting from a first time unit, wherein the first time unit is the Kth, or K+Koffset, or K+Koffset-Gth uplink time unit after time unit n; Wherein, the time unit n is later than the time unit used to carry the downlink control information, the Koffset is a predefined or preconfigured number of time units, both n and Koffset are positive integers, and G is the number of time units of the guard band in one frame period.

11. The apparatus according to claim 9 or 10, characterized in that, The time unit n is later than the time unit used to carry the downlink control information, including: The time unit n is not earlier than the last downlink time unit in the current frame period, and the current frame period is the frame period used to carry the downlink control information; The frame period includes, in sequence, a downlink time unit, a guard band time unit, and an uplink time unit.

12. The apparatus according to claim 11, characterized in that, The time unit n is not earlier than the last downlink time unit in the current frame period, including: The time unit n is the first uplink time unit within the current frame period.

13. The apparatus according to claim 11, characterized in that, The time unit n is not earlier than the last downlink time unit in the current frame period, including: The time unit n is the last guard band time unit in the current frame period.

14. The apparatus according to claim 11, characterized in that, The time unit n is not earlier than the last downlink time unit in the current frame period, including: The time unit n is the last downlink time unit in the current frame period.

15. The apparatus according to claim 11, characterized in that, The time unit n is not earlier than the last downlink time unit in the current frame period, including: The time unit n is the first guard band time unit within the current frame period.

16. The apparatus according to any one of claims 9 to 15, characterized in that, The time unit can be any one of a subframe, a time slot, a micro-time slot, or a symbol.

17. A communication device, characterized in that, Includes a processor for executing a computer program or instructions, which, when executed, cause the method of any one of claims 1 to 8 to be implemented.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed, cause the method of any one of claims 1 to 8 to be implemented.

19. A computer program product, characterized in that, It includes a computer program or instructions that, when executed, cause the method of any one of claims 1 to 8 to be implemented.

20. A chip, characterized in that, The method includes a processor for retrieving and executing a computer program or instructions stored in a memory, such that the method of any one of claims 1 to 8 is implemented.

Images