Data transmission method and apparatus

Abstract

Provided in the embodiments of the present application are a data transmission method and apparatus. The method comprises: a terminal device receiving first information or second information; the terminal device receiving uplink downlink control information (DCI); and the terminal device sending a first physical uplink shared channel (PUSCH ) on the basis of the uplink DCI, wherein when the terminal device has received the first information, the first PUSCH is located only at a sub-band non-overlapping full duplex (SBFD) symbol, or is located only at a non-SBFD symbol; when the terminal device has received the second information, the first PUSCH is located only at the SBFD symbol, or is located only at the non-SBFD symbol, or is located at the SBFD symbol and the non-SBFD symbol; when the terminal device has received the first information, the uplink DCI comprises one SRI field and / or one PMI field; and when the terminal device has received the second information, the uplink DCI comprises two SRI fields and / or two PMI fields.

Description

Data transmission method and apparatus Technical Field

[0001] The embodiments of this application relate to the field of communication technology. Background Technology

[0002] As a research item (SI) of Rel-18, the application scenarios, simulation methods, and potential standardization impacts of Subband Non-overlapping Full Duplex (SBFD) were initially studied in Rel-18.

[0003] In the upcoming Rel-19, SBFD will be formally standardized as a Work Item (WI). With SBFD, terminal devices can be configured with non-overlapping downlink and uplink subbands within existing downlink time slots (or symbols) or flexible time slots (or symbols), thus making that time slot (or symbol) an SBFD time slot (or symbol). Within an SBFD time slot, the terminal device can transmit uplink information on the uplink subband, or receive downlink information on the downlink subband; that is, the terminal device operates in half-duplex mode (receive only or transmit only), while the network device can operate in full-duplex mode (receive and transmit simultaneously). Through SBFD, terminal devices can perform uplink transmission within existing downlink time slots or flexible time slots, effectively increasing the time-frequency resources available for uplink transmission, thereby improving uplink capacity and coverage, and reducing uplink latency.

[0004] Figure 1 is a schematic diagram of time-frequency domain resources configured with SBFD subbands. As shown in Figure 1, the terminal device is configured with SBFD subbands. SBFD subbands include downlink subbands and uplink subbands; for example, the uplink subband is located between two downlink subbands in the frequency domain. The time slot containing the SBFD subband is called an SBFD time slot, and the symbol containing the SBFD subband is called an SBFD symbol. Other time slots (or symbols) are called non-SBFD time slots (or symbols). By configuring SBFD subbands in some time slots, some additional time slots can be used for uplink transmission, which is beneficial for enhancing uplink coverage, increasing uplink capacity, and reducing uplink transmission latency.

[0005] The interference environments of SBFD and non-SBFD symbols differ. For example, SBFD symbols experience inter-subband interference (ISI) that leaks from the downlink subband to the uplink subband, and vice versa. In contrast, non-SBFD symbols do not experience this ISI. Therefore, transmission on SBFD symbols and transmission on non-SBFD symbols may require the use of separate beamforming or separate power control.

[0006] It should be noted that the above introduction to the technical background is only for the purpose of providing a clear and complete explanation of the technical solutions of this application and facilitating understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application.

[0007] Summary of the Invention

[0008] The inventors discovered that uplink or downlink transmissions may or may not span SBFD and non-SBFD symbols. For example, uplink or downlink transmissions may span multiple time slots in the time domain. Since a time slot may be an SBFD or non-SBFD time slot, uplink or downlink transmissions may or may not span SBFD and non-SBFD symbols. Because SBFD and non-SBFD symbols are located in different interference environments, transmissions on different symbol types may require the use of independent beamforming or power control, introducing additional complexity compared to transmissions only on the same symbol type. Considering factors such as implementation complexity or terminal device capabilities, it is beneficial for network devices to control whether the uplink and downlink transmissions of terminal devices can span different symbol types. For example, even if the uplink and downlink transmissions determined by resource allocation span SBFD and non-SBFD symbols, the network device can still instruct the terminal device to ignore transmissions on a certain symbol type during uplink and downlink transmissions, thereby ensuring that the actual transmissions occur only on SBFD symbols or only on non-SBFD symbols. In summary, the actual uplink and downlink transmissions performed by the terminal device may only be located on SBFD symbols, or only on non-SBFD symbols, or both on SBFD and non-SBFD symbols. How the terminal device determines whether the uplink and downlink transmissions are located on SBFD symbols and / or non-SBFD symbols, including the type of signaling used for determination, whether it is explicit or implicit, and the granularity of the signaling indication, are all issues that need to be addressed.

[0009] To address at least one of the above-mentioned problems or other similar issues, embodiments of this application provide a data transmission method and apparatus.

[0010] According to one aspect of the embodiments of this application, a data transmission method is provided, the method comprising:

[0011] The terminal device receives either the first information or the second information;

[0012] The terminal device receives uplink DCI (downlink control information);

[0013] The terminal device sends a first PUSCH (Physical Uplink Shared Channel) according to the uplink DCI;

[0014] in,

[0015] When the terminal device receives the first information, the first PUSCH is located only in an SBFD (Subband Full-Duplex) symbol, or only in a non-SBFD symbol;

[0016] When the terminal device receives the second information, the first PUSCH is located only in an SBFD symbol, or only in a non-SBFD symbol, or in both an SBFD symbol and a non-SBFD symbol.

[0017] When the terminal device receives the first information, the uplink DCI includes an SRI field and / or a PMI field;

[0018] When the terminal device receives the second information, the uplink DCI includes two SRI fields and / or two PMI fields.

[0019] According to another aspect of the embodiments of this application, a data transmission apparatus is provided, configured in a terminal device, the apparatus comprising:

[0020] The first receiving unit receives either the first information or the second information;

[0021] The second receiving unit receives uplink DCI (downlink control information);

[0022] The transmitting unit transmits the first PUSCH (Physical Uplink Shared Channel) according to the uplink DCI;

[0023] in,

[0024] When the first receiving unit receives the first information, the first PUSCH is located only in an SBFD (subband full-duplex) symbol, or only in a non-SBFD symbol;

[0025] When the first receiving unit receives the second information, the first PUSCH is located only in an SBFD symbol, or only in a non-SBFD symbol, or in both an SBFD symbol and a non-SBFD symbol.

[0026] When the first receiving unit receives the first information, the uplink DCI includes an SRI field and / or a PMI field;

[0027] When the first receiving unit receives the second information, the uplink DCI includes two SRI fields and / or two PMI fields.

[0028] According to another aspect of the embodiments of this application, a data transmission method is provided, the method comprising:

[0029] The terminal device receives an uplink DCI, which includes two SRI fields and / or two PMI fields, and the uplink DCI includes an indication field;

[0030] The terminal device sends a PUSCH according to the uplink DCI;

[0031] in,

[0032] The first codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, or only on non-SBFD symbols; the second codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols; or...

[0033] The first codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, the second codepoint of the indicator field indicates that the PUSCH is located only on non-SBFD symbols, and the third codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols.

[0034] According to another aspect of the embodiments of this application, a data transmission apparatus is provided, configured in a terminal device, the apparatus comprising:

[0035] A receiving unit receives an uplink DCI, the uplink DCI including two SRI fields and / or two PMI fields, and the uplink DCI including an indication field;

[0036] The transmitting unit transmits PUSCH according to the uplink DCI;

[0037] in,

[0038] The first codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, or only on non-SBFD symbols; the second codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols; or...

[0039] The first codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, the second codepoint of the indicator field indicates that the PUSCH is located only on non-SBFD symbols, and the third codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols.

[0040] According to another aspect of the embodiments of this application, a data transmission method is provided, the method comprising:

[0041] The terminal device receives the eleventh or twelfth message;

[0042] The terminal device receives downlink DCI;

[0043] The terminal device receives PDSCH according to the downlink DCI;

[0044] When the terminal device receives the eleventh information, the PDSCH is located only at the SBFD symbol, or only at a non-SBFD symbol;

[0045] When the terminal device receives the twelfth information, the PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0046] When the terminal device receives the twelfth information, the downlink DCI includes a first indication field, wherein a first codepoint of the first indication field indicates that the PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, and a second codepoint of the first indication field indicates that the PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols; or, the downlink DCI includes a second indication field, wherein a first codepoint of the second indication field indicates that the PDSCH is located only on SBFD symbols, a second codepoint of the second indication field indicates that the PDSCH is located only on non-SBFD symbols, and a third codepoint of the second indication field indicates that the PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols.

[0047] According to another aspect of the embodiments of this application, a data transmission apparatus is provided, configured in a terminal device, the apparatus comprising:

[0048] The first receiving unit receives either the eleventh or twelfth message;

[0049] The second receiving unit receives downlink DCI;

[0050] The third receiving unit receives the PDSCH according to the downlink DCI;

[0051] When the first receiving unit receives the eleventh information, the PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol;

[0052] When the first receiving unit receives the twelfth information, the PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0053] When the first receiving unit receives the twelfth information, the downlink DCI includes a first indication field, where a first codepoint of the first indication field indicates that the PDSCH is located only on SBFD symbols or only on non-SBFD symbols, and a second codepoint of the first indication field indicates that the PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols; or, the downlink DCI includes a second indication field, where a first codepoint of the second indication field indicates that the PDSCH is located only on SBFD symbols, a second codepoint of the second indication field indicates that the PDSCH is located only on non-SBFD symbols, and a third codepoint of the second indication field indicates that the PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols.

[0054] One of the beneficial effects of the embodiments of this application is that: through the embodiments of this application, it is possible to determine whether the uplink and downlink transmission data performed on the terminal device is located only on SBFD symbols, only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols. As a result, the terminal device can flexibly realize transmission on SBFD symbols and / or non-SBFD symbols, thereby achieving a good trade-off between complexity and performance.

[0055] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

[0056] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0057] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0058] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0059] Figure 1 is a schematic diagram of an SBFD subband;

[0060] Figure 2 is a schematic diagram of a communication system according to an embodiment of this application;

[0061] Figure 3 is a schematic diagram of a data transmission method according to an embodiment of this application;

[0062] Figure 4 is a schematic diagram of the DCI fields corresponding to the first information and the second information in an embodiment of this application.

[0063] Figure 5 is a schematic diagram of three cases of time-domain resources of PUSCH determined by the terminal device based on the resource allocation field of uplink DCI in the embodiments of this application.

[0064] Figure 6 is another schematic diagram of the DCI fields corresponding to the first information and the second information in an embodiment of this application;

[0065] Figure 7 is a schematic diagram of the PUSCH determined by the terminal device according to the resource allocation field of the uplink DCI in an embodiment of this application.

[0066] Figure 8 is another schematic diagram of the data transmission method according to an embodiment of this application;

[0067] Figure 9 is another schematic diagram of the data transmission method according to an embodiment of this application;

[0068] Figure 10 is a schematic diagram of configured grant PUSCH according to the data transmission method shown in Figure 9;

[0069] Figure 11 is another schematic diagram of the data transmission method according to an embodiment of this application;

[0070] Figure 12 is a schematic diagram of a data transmission method according to an embodiment of this application;

[0071] Figure 13 is another schematic diagram of the data transmission method according to an embodiment of this application;

[0072] Figure 14 is another schematic diagram of the data transmission method according to an embodiment of this application;

[0073] Figure 15 is another schematic diagram of the data transmission method according to an embodiment of this application;

[0074] Figure 16 is a schematic diagram of a data transmission device according to an embodiment of this application;

[0075] Figure 17 is another schematic diagram of a data transmission device according to an embodiment of this application;

[0076] Figure 18 is a schematic diagram of a terminal device according to an embodiment of this application. Detailed Implementation

[0077] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0078] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0079] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.

[0080] In the embodiments of this application, the term "communication network" or "wireless communication network" may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0081] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), future 6G, etc., and / or other currently known or future communication protocols.

[0082] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a terminal device to a communication network and provides services to that terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0083] Base stations can include, but are not limited to: NodeBs (or NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), IAB hosts, etc. They can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femeto, pico, etc.). The term "base station" can include some or all of their functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0084] In the embodiments of this application, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer, for example, to a device that accesses a communication network and receives network services through a network device. A terminal device can be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc.

[0085] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptops, cordless phones, smartphones, smartwatches, digital cameras, etc.

[0086] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.

[0087] Furthermore, the terms "network side" or "network equipment side" refer to one side of the network, which can be a base station or include one or more network devices as described above. The terms "user side," "terminal side," or "terminal equipment side" refer to the side of the user or terminal, which can be a UE or include one or more terminal devices as described above. Unless otherwise specified, "equipment" can refer to either network equipment or terminal equipment.

[0088] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0089] Figure 2 is a schematic diagram of a communication system according to an embodiment of this application, illustrating the case of a terminal device and a network device as examples. As shown in Figure 2, the communication system 200 may include a network device 201 and terminal devices 202 and 203. For simplicity, Figure 2 only illustrates the case of two terminal devices and one network device, but the embodiments of this application are not limited to this.

[0090] In this embodiment of the application, network device 201 and terminal devices 202 and 203 can transmit existing services or services that can be implemented in the future. For example, these services may include, but are not limited to: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0091] It is worth noting that Figure 2 shows that both terminal devices 202 and 203 are within the coverage area of ​​network device 201, but this application is not limited to this. Both terminal devices 202 and 203 may be outside the coverage area of ​​network device 201, or one terminal device 202 may be within the coverage area of ​​network device 201 while the other terminal device 203 may be outside the coverage area of ​​network device 201.

[0092] In the embodiments of this application, the signaling may be, for example, Radio Resource Control (RRC) signaling; for example, referred to as an RRC message, including MIB, system information, dedicated RRC messages; or referred to as an RRC information element. The signaling may also be, for example, Medium Access Control (MAC) signaling; or referred to as a MAC control element. However, this application is not limited to these.

[0093] In the following explanation, without confusion, the terms "PUSCH" and "physical uplink data channel" or "uplink data" are used interchangeably. Furthermore, sending or receiving a PUSCH can be understood as sending or receiving uplink data carried by the PUSCH. Additionally, expressions such as "when," "if," and "under certain circumstances" have the same meaning and are interchangeable.

[0094] Furthermore, in the following descriptions, unless otherwise specified, Case 1 refers to uplink transmissions located only on SBFD symbols, Case 2 refers to uplink transmissions located only on non-SBFD symbols, and Case 3 refers to uplink transmissions located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols. Additionally, Case 1 restricts uplink transmissions to using only SBFD resources; Case 2 restricts uplink transmissions to using only non-SBFD resources; and Case 3 imposes no restrictions on the resources used by the uplink transmission. Furthermore, uplink DCI refers to the DCI used to schedule, activate, or indicate uplink transmissions, and downlink DCI refers to the DCI used to schedule, activate, or indicate downlink transmissions.

[0095] In this embodiment of the application, as shown in Figure 1, the SBFD subband includes an uplink subband and a downlink subband. Some time slots contain SBFD subbands; these time slots are SBFD time slots, and the symbols they include are SBFD symbols. Some time slots do not contain SBFD subbands; these time slots are non-SBFD time slots, and the symbols they include are non-SBFD symbols. It is also possible for a time slot to include both SBFD symbols and non-SBFD symbols, which are not listed here.

[0096] In the embodiments of this application, the terminal device may transmit PUSCH on SBFD symbols and / or non-SBFD symbols. For example, a PUSCH (i.e., a TB) may be located on both SBFD and non-SBFD symbols; or, for multiple PUSCH repetitions, some PUSCH repetitions may be located on SBFD symbols and some PUSCH repetitions may be located on non-SBFD symbols; or, for multiple PUSCHs, some PUSCHs may be located on SBFD symbols and some PUSCHs may be located on non-SBFD symbols.

[0097] In the embodiments of this application, "SBFD symbol" can be replaced with "SBFD time slot", and "non-SBFD symbol" can be replaced with "non-SBFD time slot".

[0098] The embodiments of this application will now be described with reference to the accompanying drawings.

[0099] First aspect of the embodiments

[0100] This application provides a data transmission method for uplink data transmission. Figure 3 is a schematic diagram of the data transmission method according to an embodiment of this application. As shown in Figure 3, the method includes:

[0101] 310, The terminal device receives the first information or the second information;

[0102] 320, The terminal device receives uplink DCI (downlink control information);

[0103] 330. The terminal device sends the first PUSCH (Physical Uplink Shared Channel) according to the above-mentioned uplink DCI;

[0104] Wherein, when the terminal device receives the first information, the first PUSCH is located only in the SBFD (subband full-duplex) symbol, or only in the non-SBFD symbol;

[0105] When the terminal device receives the second information, the first PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0106] Upon receiving the first information at the terminal device, the uplink DCI includes an SRI field and / or a PMI field;

[0107] When the terminal device receives the second information, the uplink DCI includes two SRI fields and / or two PMI fields.

[0108] It is worth noting that Figure 3 above is only an illustrative description of the embodiments of this application, but this application is not limited thereto. For example, the execution order between various operations can be appropriately adjusted, and other operations can be added or some operations can be removed. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description in Figure 3 above.

[0109] According to the above embodiments, it is possible to determine whether the uplink transmission data performed on the terminal device is located only on SBFD symbols, only on non-SBFD symbols, or on both SBFD and non-SBFD symbols. Thus, the terminal device can flexibly implement transmission on SBFD symbols and / or non-SBFD symbols, thereby achieving a good trade-off between complexity and performance.

[0110] In the embodiments of this application, the first PUSCH may be multiple PUSCH repetitions, multiple PUSCHs, or a transport block (TB) spanning multiple time slots.

[0111] For example, a PUSCH scheduled by DCI can be a repetition of multiple PUSCHs scheduled by DCI, or a TB over Multiple Slots scheduled by DCI.

[0112] In the above embodiments, the first information indicates that the uplink transmission (PUSCH) cannot span between SBFD and non-SBFD symbols, while the second information indicates that the uplink transmission can span between SBFD and non-SBFD symbols. In other words, the first information indicates that the uplink transmission must comply with a restriction condition, limiting the uplink transmission to only within the same symbol class. That is, the uplink transmission can be located only within SBFD symbols (Case 1) or only within non-SBFD symbols (Case 2). Which of Case 1 or Case 2 applies will be explained later. The second information indicates that there are no restrictions on the uplink transmission; that is, the uplink transmission can be located only within SBFD symbols, or only within non-SBFD symbols, or both (Case 3). If the terminal device receives the first information, the terminal device's uplink transmission is located only within SBFD symbols, or only within non-SBFD symbols, i.e., restricted to the same symbol class. If the terminal device receives the second information, the terminal device's uplink transmission is located only within SBFD symbols, or only within non-SBFD symbols, or both (both SBFD and non-SBFD symbols), i.e., without any restriction.

[0113] This application embodiment does not limit how the terminal device receives the first information or the second information. For example, the first information and / or the second information can be configured through RRC signaling. For example, when the terminal device is configured with Config1 (first information), it means that the terminal device has received the first information; when the terminal device is configured with Config2 (second information), it means that the terminal device has received the second information. For example, when the terminal device is configured with Child-Config, that is, when it receives Parent-Config (parent IE) including Child-Config (child IE), it means that the terminal device has received the first information; when the terminal device is not configured with Child-Config, that is, when it receives Parent-Config (parent IE) that does not include Child-Config (child IE), it means that the terminal device has received the second information. For example, when the terminal device is configured with Child-Config, it means that the terminal device has received the second information; when the terminal device is not configured with Child-Config, it means that the terminal device has received the first information.

[0114] In some embodiments, when the terminal device receives the first information, the uplink DCI includes an SRI field and / or a PMI field. For example, the first information is configured via RRC signaling. When the terminal device is configured with Config1 (first information), it indicates that the terminal device has received the first information. In this case, the uplink DCI received by the terminal device includes an SRI field (e.g., in the case where the uplink transmission is based on non-codebook transmission), or includes an SRI field and a PMI field (e.g., in the case where the uplink transmission is based on codebook transmission). In this case, an SRI field and / or a PMI field are applied to the uplink transmission performed by the terminal device according to the uplink DCI, wherein the uplink transmission is located only in the same type of symbol. For example, the uplink transmission spans multiple time slots, and the symbols in each time slot are either SBFD symbols or non-SBFD symbols.

[0115] In other embodiments, when the terminal device receives the second information, the uplink DCI includes two SRI fields and / or two PMI fields. For example, when the terminal device receives the second information, the uplink DCI received by the terminal device includes two SRI fields (e.g., in the case of uplink transmission based on non-codebook transmission), or includes two SRI fields and two PMI fields (e.g., in the case of uplink transmission based on codebook transmission). For example, when the uplink transmission performed by the terminal device according to the uplink DCI is only located in the same symbol class, the first SRI field and / or the first PMI field are applied to the uplink transmission, and the second SRI field and / or the second PMI field are reserved; when the uplink transmission performed by the terminal device according to the uplink DCI spans two symbol classes, the first SRI field and / or the first PMI field are applied to the uplink transmission located in SBFD symbols, and the second SRI field and / or the second PMI field are applied to the uplink transmission located in non-SBFD symbols.

[0116] Therefore, when the uplink transmission is located only in the same type of symbol, the uplink DCI has fewer fields (i.e., including one SRI field and / or one PMI field), which can effectively reduce signaling overhead.

[0117] In the above embodiments, "first field" means "first field" and "second field" means "second field," or "first field" means "second field" and "second field" means "first field." For example, the uplink DCI includes DCI format 0_1 ​​and / or DCI format 0_2 and / or DCI format 0_0, used to schedule or activate PUSCH transmission (e.g., activate configured grant Type 2 PUSCH). For example, the first PMI field can be called the Precoding information and number of layers field, the second PMI field can be called the Second Precoding information field, the first SRI field can be called the SRS resource indicator field, and the second SRI field can be called the Second SRS resource indicator field.

[0118] Figure 4 is a schematic diagram of the DCI fields corresponding to the first information and the second information in an embodiment of this application.

[0119] In some possible implementations, as shown in Figure 4, when the terminal device is configured with Config1 by RRC signaling (receiving the first information), DCI format 0_1 ​​and / or DCI format 0_2 include an SRI field (in the case of non-codebook transmission), or include an SRI field and a PMI field (in the case of codebook transmission). The PUSCH sent by the terminal device according to DCI format 0_1 ​​and / or DCI format 0_2 is located only on SBFD symbols, or only on non-SBFD symbols.

[0120] In some other possible implementations, when the terminal device is configured with Config2 by RRC signaling (receiving the second information), DCI format 0_1 ​​and / or DCI format 0_2 include two SRI fields (in the case of non-codebook transmission), or, include two SRI fields and two PMI fields (in the case of codebook transmission). The PUSCH sent by the terminal device according to DCI format 0_1 ​​and / or DCI format 0_2 is only located on SBFD symbols (SRI 1 and / or PMI 1 fields are applied to PUSCH), or only located on non-SBFD symbols (SRI 1 and / or PMI 1 fields are applied to PUSCH), or located on both SBFD and non-SBFD symbols (SRI 1 and / or PMI 1 fields are applied to PUSCH located on SBFD symbols, SRI 2 and / or PMI 2 fields are applied to PUSCH located on non-SBFD symbols), or SRI 1 and / or PMI 1 fields are applied to PUSCH located on non-SBFD symbols, SRI 2 and / or PMI 1 fields are applied to PUSCH located on non-SBFD symbols, SRI 2 and / or PMI 1 fields are applied to PUSCH located on non-SBFD symbols). Field 2 applies to the PUSCH located on the SBFD symbol.

[0121] For example, DCI format 0_1 ​​and / or DCI format 0_2 schedule or activate multiple PUSCH repetitions or multiple PUSCHs or TBs (TBoMS, TB over Multiple Slots). For example, the bit width of the SRI 1 field is greater than or equal to the bit width of the SRI 2 field, and / or the bit width of the PMI 1 field is greater than or equal to the bit width of the PMI 2 field, wherein the number of layers (or rank) is indicated only by the SRI 1 or PMI 1 field, and the SRI 2 or PMI 2 field does not need to indicate the number of layers (or rank).

[0122] In the above embodiments, the terminal device sends PUSCH according to the uplink DCI. For example, it may include: the PUSCH determined by the terminal device according to the resource allocation field of the uplink DCI is located in the SBFD symbol and the non-SBFD symbol, but the PUSCH actually sent by the terminal device may be located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0123] Figure 5 is a schematic diagram illustrating three scenarios of the time-domain resources of the PUSCH determined by the terminal device based on the resource allocation field of the uplink DCI in an embodiment of this application. As shown in Figure 5, although the terminal device determines that the PUSCH spans multiple different types of time slots based on the resource allocation field of the uplink DCI, i.e., spans SBFD symbols (time slots) and non-SBFD symbols (time slots), the PUSCH actually transmitted by the terminal device may be located only in SBFD symbols (Scenario 1), or only in non-SBFD symbols (Scenario 2), or in both SBFD symbols and non-SBFD symbols (Scenario 3). For example, when the terminal device receives the first information, the PUSCH actually transmitted by the terminal device may be located only in SBFD symbols (Scenario 1) or only in non-SBFD symbols (Scenario 2), i.e., the PUSCH is transmitted only in a portion of the time slots. Which scenario (Scenario 1 or Scenario 2) is specifically described later. This means that when the terminal device receives the first information, the time-domain resources of the PUSCH determined based on the resource allocation field are not necessarily consistent with the time-domain resources of the actually transmitted PUSCH. For example, when the terminal device receives the second information, the PUSCH actually sent by the terminal device is located on both SBFD and non-SBFD symbols (Case 3). In other words, the terminal device can determine the time domain resources of the actually sent PUSCH based on the resource allocation field of the uplink DCI. This means that when the terminal device receives the second information, the time domain resources of the PUSCH determined according to the resource allocation field are consistent with the time domain resources of the actually sent PUSCH.

[0124] In some embodiments, the terminal device sending a PUSCH according to the uplink DCI includes: the PUSCH determined by the terminal device based on the resource allocation field of the uplink DCI is located only on SBFD symbols, and the PUSCH actually sent by the terminal device is also located only on SBFD symbols, and the time domain resources of the PUSCH determined based on the resource allocation field are consistent with the time domain resources of the actually sent PUSCH. As another example, the terminal device sending a PUSCH according to the uplink DCI includes: the PUSCH determined by the terminal device based on the resource allocation field of the uplink DCI is located only on non-SBFD symbols, and the PUSCH actually sent by the terminal device is also located only on non-SBFD symbols, and the time domain resources of the PUSCH determined based on the resource allocation field are consistent with the time domain resources of the actually sent PUSCH.

[0125] In the above embodiments, Config1 (first information) and Config2 (second information) can be configured independently for PUSCHs scheduled or activated by DCI format 0_1 ​​and PUSCHs scheduled or activated by DCI format 0_2. For example, for PUSCHs scheduled or activated by DCI format 0_1, the terminal device is configured with Config1, and for PUSCHs scheduled or activated by DCI format 0_2, the terminal device is configured with Config2, that is, Config1 or Config2 is configured on a DCI format basis.

[0126] In some embodiments, for a PUSCH scheduled or activated by DCI format 0_3, or a PUSCH scheduled or activated by DCI format 0_0, or a sounding reference signal (SRS), the terminal device can be restricted to being configured only with Config1 (first information) and not with Config2 (second information). For example, for DCI format 0_0, this DCI format 0_0 is a DCI format 0_0 with CRC scrambled by C-RNTI. For example, for SRS, the SRS and PUSCH have separate or independent closed-loop power control states. One reason for this is that for the aforementioned PUSCH or SRS transmissions, the DCI used to indicate its closed-loop power control state has only one TPC command field, thus restricting the terminal device to be configured only with Config1, so that the TPC command field is applied to a single type of symbol, i.e., SBFD symbols or non-SBFD symbols.

[0127] In some embodiments, the uplink DCI may include DCI format 0_0, which is used to activate configured grant Type 2PUSCH.

[0128] In some embodiments, when the terminal device receives the second information, the uplink DCI includes a first indication field; the first codepoint of the first indication field indicates that the first PUSCH is located only on SBFD symbols, or only on non-SBFD symbols; the second codepoint of the first indication field indicates that the first PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols.

[0129] For example, when the terminal device receives the second information, the time-domain resources of the PUSCH determined by the terminal device based on the resource allocation field of the uplink DCI may only be located on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols. An indication field in the uplink DCI can dynamically indicate whether the actually transmitted PUSCH can span between SBFD and non-SBFD symbols. For example, by indicating through a first codepoint that it cannot span between SBFD and non-SBFD symbols, the terminal device is instructed to further ensure that the actually transmitted PUSCH does not span between SBFD and non-SBFD symbols (e.g., not transmitting a portion of the symbols) based on the time-domain resources determined by the resource allocation field. Therefore, the actually transmitted PUSCH is only located on SBFD symbols, or only on non-SBFD symbols. By indicating the first codepoint, when the terminal device receives the second information, the time-domain resources of the actually transmitted PUSCH may be inconsistent with the time-domain resources of the PUSCH determined by the resource allocation field. The second codepoint indication allows for transmission across SBFD and non-SBFD symbols. Specifically, it instructs the terminal device to determine the temporal resources of the actually transmitted PUSCH based on the resource allocation field. Therefore, the actually transmitted PUSCH can be located only on SBFD symbols, only on non-SBFD symbols, or on both SBFD and non-SBFD symbols. By indicating the second codepoint, when the terminal device receives the second information, the temporal resources of the actually transmitted PUSCH are consistent with the temporal resources of the PUSCH determined according to the resource allocation field.

[0130] For example, as shown in Figure 5, when the terminal device receives the second information, for the PUSCH scheduled or activated by the uplink DCI, the time-domain resources determined by the resource allocation field of the uplink DCI span both SBFD and non-SBFD symbols. In this case, an indication field in the uplink DCI can further indicate whether the PUSCH actually sent by the terminal device can span both SBFD and non-SBFD symbols. More specifically, one codepoint (first codepoint) of this indication field instructs the terminal device to send only the PUSCH located on SBFD symbols (Case 1), or only the PUSCH located on non-SBFD symbols (Case 2). The other codepoint (second codepoint) of this indication field instructs the terminal device to determine the time-domain resources of the PUSCH actually sent based on the resource allocation field. Therefore, the terminal device sends a PUSCH spanning both SBFD and non-SBFD symbols (Case 3). Here, the first codepoint only instructs the terminal device to send the PUSCH according to Case 1 or Case 2, but does not specifically indicate (does not distinguish) which of Case 1 and Case 2 it is. How to determine which of Case 1 and Case 2 it is will be explained later.

[0131] Figure 6 is another schematic diagram of the DCI fields corresponding to the first information and the second information in an embodiment of this application.

[0132] Unlike the example in Figure 4, in the example in Figure 6, when the terminal device is configured with Config2 (receiving the second information) by RRC signaling, the uplink DCI also includes an Indicator field. Codepoint 1 of the Indicator field indicates that the actually transmitted PUSCH is located only within the same symbol class, while codepoint 2 indicates that the actually transmitted PUSCH may or may not span different symbol classes. When the terminal device receives the second information, if the Indicator field indicates codepoint 1, the time-domain resources of the PUSCH determined by the resource allocation field are not necessarily consistent with the time-domain resources of the actually transmitted PUSCH. If the Indicator field indicates codepoint 2, the time-domain resources of the PUSCH determined by the resource allocation field are consistent with the time-domain resources of the actually transmitted PUSCH. For example, the Indicator field has a bit width of 1 bit, codepoint 1 is '0' (or '1'), and codepoint 2 is '1' (or '0'). For example, the Indicator field has a bit width of 2 bits, codepoint 1 is '00' (or '01'), codepoint 2 is '01' (or '00'), and the remaining codepoints ('10' and '11') are reserved. Only the values ​​of codepoint 1 and codepoint 2 need to be different; all possible values ​​are not listed.

[0133] For example, when the Indicator field is codepoint 2, it means that the terminal device can determine the actual PUSCH to be sent based on the resource allocation field of the uplink DCI.

[0134] In the above embodiments, in some possible implementations, when the first codepoint of the first indication field indicates that the first PUSCH is located only in an SBFD symbol or only in a non-SBFD symbol, the terminal device determines whether the first PUSCH is located only in an SBFD symbol or only in a non-SBFD symbol based on whether the first symbol indicated by the uplink DCI is located in an SBFD symbol or only in a non-SBFD symbol.

[0135] For example, as shown in Figure 5, when the terminal device receives the second information, the time domain resources of the PUSCH determined by the resource allocation field of the uplink DCI span both SBFD symbols (or time slots) and non-SBFD symbols (or time slots); as shown in Figure 6, the Indicator field of the uplink DCI indicates codepoint 1. At this time, the PUSCH actually sent by the terminal device is located only in SBFD symbols (case 1) or only in non-SBFD symbols (case 2); the terminal device determines which case of case 1 or case 2 the sent PUSCH belongs to based on the first symbol of the time domain resources, that is, the first symbol indicated by the uplink DCI is the first symbol of the time domain resources indicated by the resource allocation field of the uplink DCI. More specifically, since the first symbol (or time slot) of the time-domain resource indicated by the uplink DCI in Figure 5 is an SBFD symbol (or time slot), the PUSCH actually transmitted by the terminal device is only located in the SBFD symbol (Case 1); conversely (not shown in Figure 5), if the first symbol (or time slot) of the time-domain resource indicated by the uplink DCI is a non-SBFD symbol (or time slot), then the PUSCH actually transmitted by the terminal device is only located in the non-SBFD symbol (Case 2). Therefore, the terminal device can determine whether the transmitted PUSCH belongs to Case 1 or Case 2.

[0136] In simple terms, when the terminal device receives the second information, the Indicator field of the uplink DCI indicates the first set, i.e., {case 1, case 2}, or indicates the second set, i.e., {case 3}. When the Indicator field of the uplink DCI indicates {case 1, case 2}, the terminal device determines which case, case 1 or case 2, is it based on the first symbol of the time-domain resource indicated by the resource allocation field of the uplink DCI.

[0137] In the above embodiments, "the first symbol of the uplink DCI indication" can also be replaced with "the first PUSCH repetition of the uplink DCI indication" (i.e., the case of uplink DCI scheduling PUSCH repetition); "the first symbol of the uplink DCI indication" can also be replaced with "the first PUSCH of the uplink DCI indication" (i.e., the case of uplink DCI scheduling multiple PUSCHs); "the first symbol of the uplink DCI indication" can also be replaced with "the first time slot of the uplink DCI indication" (i.e., the case of uplink DCI scheduling TBoMS), and this application does not limit this.

[0138] In some embodiments, when the terminal device receives the first information, the terminal device determines whether the first PUSCH is located only in an SBFD symbol or only in a non-SBFD symbol based on whether the first symbol indicated by the uplink DCI is located in an SBFD symbol or in a non-SBFD symbol.

[0139] For example, as shown in Figure 5, when the terminal device receives the first information, the PUSCH sent by the terminal device is located only on an SBFD symbol (Case 1) or only on a non-SBFD symbol (Case 2). The terminal device determines whether it is Case 1 or Case 2 based on the first symbol of the time-domain resource indicated by the resource allocation field of the uplink DCI. In Figure 5, the terminal device determines it to be Case 1.

[0140] In the above embodiments, in some possible implementations, when the first symbol indicated by the uplink DCI is a non-SBFD symbol, the terminal device determines whether the first PUSCH is located only in an SBFD symbol or only in a non-SBFD symbol based on whether the first reference symbol is located in an SBFD symbol or a non-SBFD symbol.

[0141] The first reference symbol is the first symbol of the first PUSCH that does not overlap with the downlink symbol as indicated by the uplink DCI, or the first symbol of the first PUSCH repetition that does not overlap with the downlink symbol as indicated by the uplink DCI, or the first symbol of the first time slot that does not overlap with the downlink symbol as indicated by the uplink DCI, or the first symbol of the first time slot that does not overlap with the downlink symbol as indicated by the uplink DCI.

[0142] Figure 7 is a schematic diagram of the PUSCH determined by the terminal device according to the resource allocation field of the uplink DCI in an embodiment of this application.

[0143] As shown in Figure 7, the first symbol of the time-domain resource indicated by the uplink DCI is a non-SBFD symbol and overlaps with the downlink symbol in the time domain. The uplink DCI can schedule multiple PUSCH repetitions (PUSCH 1 to PUSCH 5 represent multiple PUSCH repetitions). Figure 7 shows the time-domain resources of the PUSCH repetition indicated by the uplink DCI. The first PUSCH repetition is located on a non-SBFD symbol but overlaps with the downlink symbol. In this scenario, for example, the terminal device determines case 1 or case 2 based on the first symbol of the first PUSCH repetition (i.e., PUSCH 2) that does not overlap with the downlink symbol in the time domain resources. Since PUSCH 1 overlaps with the downlink symbol, the first symbol is the first symbol of PUSCH 2, which is located in the SBFD symbol. Thus, the terminal device determines to send PUSCH 2 and PUSCH 4 (case 1). As another example, the terminal device determines case 1 or case 2 based on the first symbol that does not overlap with the downlink symbol in the time domain resources. Since the first symbol that does not overlap with the downlink symbol is still a symbol of PUSCH 1 and is a non-SBFD symbol, the terminal device determines to send PUSCH 3 and PUSCH 5 (case 2).

[0144] When all symbols in a PUSCH repetition (e.g., PUSCH 1) are either SBFD symbols or non-SBFD symbols, the terminal device determining Case 1 or Case 2 based on the first symbol of a PUSCH repetition is equivalent to the terminal device determining Case 1 or Case 2 based on the PUSCH repetition itself. In other words, if the PUSCH repetition is located on an SBFD symbol, it is determined to be Case 1; if the PUSCH repetition is located on a non-SBFD symbol, it is determined to be Case 2. Simply put, "the first symbol of the first PUSCH repetition that does not overlap with a downlink symbol" can be replaced with "the first PUSCH repetition that does not overlap with a downlink symbol".

[0145] Figure 7 illustrates this using the example of uplink DCI scheduling multiple PUSCH repetitions. Similarly, this can be extended to the case of uplink DCI scheduling multiple PUSCHs, where PUSCH 1 to PUSCH 5 represent multiple PUSCHs, which will not be elaborated further here. Figure 7 can also be extended to the case of TBoMS. The time-domain resources of the TBoMS indicated by the uplink DCI include time slots 1 to 5, i.e., replacing PUSCH 1 to PUSCH 5 with time slots 1 to 5. The time-domain resources are used to carry one PUSCH (TB) and span different symbol types. For example, the terminal device can determine case 1 or case 2 based on the first symbol of the first time slot that does not overlap with the downlink symbol in the time-domain resources. Since the first symbol of the first time slot that does not overlap with the downlink symbol (i.e., time slot 2) is an SBFD symbol, the terminal device determines case 1.

[0146] For example, downlink symbols refer to downlink symbols configured by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and / or SSB symbols configured by ssb-PositionsInBurst.

[0147] For example, when a PUSCH repetition overlaps with a downlink symbol, the terminal device does not send the PUSCH repetition; here, "PUSCH repetition" can also be replaced with "PUSCH" (i.e., the case where an uplink DCI schedules multiple PUSCHs), or replaced with "time slot" (i.e., the case where an uplink DCI schedules TBoMS).

[0148] In other embodiments, when the terminal device receives the second information, the uplink DCI includes a second indication field; the first codepoint of the second indication field indicates that the first PUSCH is located only on SBFD symbols; the second codepoint of the second indication field indicates that the first PUSCH is located only on non-SBFD symbols; the third codepoint of the second indication field indicates that the first PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols.

[0149] For example, uplink DCI also includes an Indicator field. Codepoint 1 of the Indicator field indicates that the PUSCH actually transmitted is located only on SBFD symbols, codepoint 2 of the Indicator field indicates that the PUSCH actually transmitted is located only on non-SBFD symbols, and codepoint 3 of the Indicator field indicates that the PUSCH actually transmitted may or may not cross different types of symbols.

[0150] For example, when the Indicator field is codepoint 3, it means that the terminal device can determine the actual PUSCH to be sent based on the resource allocation field of the uplink DCI.

[0151] In some embodiments, the terminal device is configured with two SRS resource sets, the first SRS resource set being applied to PUSCH located on SBFD symbols, and the second SRS resource set being applied to PUSCH located on non-SBFD symbols.

[0152] For example, the terminal device is configured with two SRS resource sets, applied to SBFD symbols and non-SBFD symbols respectively. When the PUSCH is only located on SBFD symbols, the SRI field indicates the SRS resource in the first SRS resource set; when the PUSCH is only located on non-SBFD symbols, the SRI field indicates the SRS resource in the second SRS resource set; when the PUSCH is located on both SBFD symbols and non-SBFD symbols, the first SRI field indicates the SRS resource in the first SRS resource set, and the second SRI field indicates the SRS resource in the second SRS resource set.

[0153] In some embodiments, when the terminal device is configured with Msg3 repetition, the terminal device may also receive third or fourth information. Furthermore, the terminal device may receive a RAR UL grant or CRC scrambled by TC-RNTI in DCI format 0_0, and send a second PUSCH according to the RAR UL grant or CRC scrambled by TC-RNTI in DCI format 0_0. When the terminal device receives the third information, the second PUSCH may be located only on SBFD symbols, or only on non-SBFD symbols; when the terminal device receives the fourth information, the second PUSCH may be located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols.

[0154] The above embodiments can also be implemented individually, as detailed below.

[0155] Figure 8 is another schematic diagram of the data transmission method according to an embodiment of this application. As shown in Figure 8, the method includes:

[0156] 810, The terminal device receives the third or fourth information, and the terminal device is configured with Msg3 repetition;

[0157] 820, The terminal device receives DCI format 0_0 with RAR UL grant or CRC scrambled by TC-RNTI;

[0158] 830, The terminal device sends the second PUSCH according to the DCI format 0_0 scrambled by TC-RNTI based on the RAR UL grant or CRC;

[0159] Wherein, when the terminal device receives the third information, the second PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol;

[0160] When the terminal device receives the fourth information, the second PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0161] For example, a PUSCH scheduled by RAR UL grant can be called Msg3, and a PUSCH scheduled by DCI format 0_0 with CRC scrambled by TC-RNTI can be called Msg3 retransmission; the terminal device is configured with Msg3 repetition, so both Msg3 and Msg3 retransmission can span multiple time slots, and thus may span SBFD symbols and non-SBFD symbols.

[0162] In the above embodiments, when the terminal device is configured with Config3, both Msg3 and Msg3 retransmissions are restricted to not crossing SBFD symbols and non-SBFD symbols, that is, only located on SBFD symbols (Case 1), or only located on non-SBFD symbols (Case 2); when the terminal device is configured with Config4, both Msg3 and Msg3 retransmissions can cross SBFD symbols and non-SBFD symbols, that is, only located on SBFD symbols (Case 1), or only located on non-SBFD symbols (Case 2), or located on both SBFD symbols and non-SBFD symbols (Case 3).

[0163] This application does not limit the signaling format of the third and fourth information in its embodiments. For example, the third information may be the same as or different from the first information, and the fourth information may be the same as or different from the second information. For example, the third and fourth information are configured in an SIB (e.g., SIB1). For example, the third and fourth information are configured in BWP-UplinkCommon. For example, the third and fourth information are configured under the same parent IE as msg3-Repetitions. For example, the third and fourth information are configured in FeatureCombination. For example, the third and fourth information are configured in RACH-ConfigCommon. For example, the third and fourth information are configured in RACH-ConfigDedicated. Furthermore, the indication methods for the first and second information described above are also applicable to the third and fourth information. As for how the terminal device further determines which of the three scenarios (Scenario 1, Scenario 2, and Scenario 3) it is, any of the methods described above can be used, and will not be repeated here. For example, if the terminal device receives the third information, it determines Scenario 1 or Scenario 2 based on the first symbol indicated by the DCI format 0_0 scrambled by TC-RNTI for RAR UL grant or CRC. If the terminal device receives the fourth information, it performs the actual transmission on the time domain resources indicated by the DCI format 0_0 scrambled by TC-RNTI for RAR UL grant or CRC.

[0164] For example, for PUSCH scheduled or activated by DCI format 0_1 ​​and / or DCI format 0_2, the terminal device is configured with Config1 or Config2; for PUSCH scheduled by DCI format 0_0 with RAR UL grant or CRC scrambled by TC-RNTI, the terminal device is configured with Config3 or Config4.

[0165] In some embodiments, the terminal device may also receive a fifth message, a sixth message, or a seventh message, and send a first configured grant PUSCH. When the terminal device receives the fifth message, the first configured grant PUSCH is located only on SBFD symbols; when the terminal device receives the sixth message, the first configured grant PUSCH is located only on non-SBFD symbols; when the terminal device receives the seventh message, the first configured grant PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols.

[0166] The above embodiments can also be implemented individually, as detailed below.

[0167] Figure 9 is another schematic diagram of the data transmission method according to an embodiment of this application. As shown in Figure 9, the method includes:

[0168] 910, The terminal device receives the fifth, sixth, or seventh message;

[0169] 920, the terminal device sends the first configured grant PUSCH;

[0170] Among them, when the terminal device receives the fifth information, the aforementioned first configured grant PUSCH is only located in the SBFD symbol;

[0171] If the terminal device receives the sixth message, the aforementioned first configured grant PUSCH is only located on a non-SBFD symbol;

[0172] When the terminal device receives the seventh information, the aforementioned first configured grant PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0173] Figure 10 is a schematic diagram of the configured grant PUSCH according to the data transmission method shown in Figure 9.

[0174] As shown in Figure 10, for a configured grant (e.g., configured grant Type 1), periodic configured grant PUSCH resources are configured, where some PUSCH occasions are located on SBFD symbols and some PUSCH occasions are located on non-SBFD symbols.

[0175] When the terminal device is configured with Config5, it can only send PUSCH at PUSCH times located at SBFD symbols; when the terminal device is configured with Config6, it can only send PUSCH at PUSCH times located at non-SBFD symbols; when the terminal device is configured with Config7, it can send PUSCH at all PUSCH times shown in the diagram. For example, when the terminal device is configured with Config7, it can determine the PUSCH time according to the configuration of the configured grant (i.e., according to the prior art), and all determined PUSCH times can be used to send PUSCH. For example, the fifth, sixth, or seventh information can be configured in ConfiguredGrantConfig, or in rrc-ConfiguredUplinkGrant.

[0176] For example, for a PUSCH scheduled or activated by DCI format 0_1 ​​and / or DCI format 0_2, the terminal device is configured with Config1 or Config2; for a configured grant PUSCH, the terminal device is configured with Config5, Config6 or Config7.

[0177] In some embodiments, the terminal device may also receive an eighth message or a ninth message and send a second configured grant PUSCH. When the terminal device receives the eighth message, the second configured grant PUSCH is located only on an SBFD symbol, or only on a non-SBFD symbol; when the terminal device receives the ninth message, the second configured grant PUSCH is located only on an SBFD symbol, or only on a non-SBFD symbol, or on both an SBFD symbol and a non-SBFD symbol.

[0178] The above embodiments can also be implemented individually, as detailed below.

[0179] Figure 11 is another schematic diagram of a data transmission method according to an embodiment of this application. As shown in Figure 11, the method includes:

[0180] 1110, The terminal device receives the eighth or ninth message;

[0181] 1120, the terminal device sends a second configured grant PUSCH;

[0182] Among them, when the terminal device receives the eighth information, the second configured grant PUSCH is located only at the SBFD symbol, or only at the non-SBFD symbol;

[0183] When the terminal device receives the ninth message, the second configured grant PUSCH is located only on the SBFD symbol, or only on the non-SBFD symbol, or on both the SBFD and non-SBFD symbols.

[0184] As shown in Figure 10, for a configured grant (e.g., configured grant Type 1), when the terminal device is configured with Config8, the terminal device sends a PUSCH only on PUSCH opportunities located on SBFD symbols (Case 1), or only on PUSCH opportunities located on non-SBFD symbols (Case 2). For example, the terminal device can determine Case 1 or Case 2 based on whether the first configured grant PUSCH (or the first symbol of the first configured grant PUSCH) is located on an SBFD symbol or a non-SBFD symbol. The first configured grant PUSCH can be determined based on the "Offset" parameter in Figure 10, which is configured by RRC signaling. When the terminal device is configured with Config9, the terminal device can send a PUSCH on all PUSCH opportunities shown in the figure. For example, the eighth or ninth message can be configured in ConfiguredGrantConfig, or in rrc-ConfiguredUplinkGrant. For example, the eighth message can be the same as or different from the first message, and the ninth message can be the same as or different from the second message.

[0185] For example, for PUSCH scheduled or activated by DCI format 0_1 ​​and / or DCI format 0_2, the terminal device is configured with Config1 or Config2; for configured grant PUSCH, the terminal device is configured with Config8 or Config9.

[0186] In the above embodiments, when the terminal device receives the eighth information, the terminal device may also receive the tenth information, and determine whether the second configured grant PUSCH is located only in SBFD symbols or only in non-SBFD symbols based on the tenth information.

[0187] For example, the terminal device is configured with Config8, which indicates that the configured grant PUSCH does not cross SBFD symbols and non-SBFD symbols. The terminal device is also configured with Config10, which further indicates whether the configured grant PUSCH is located only on SBFD symbols or only on non-SBFD symbols. For example, Config8 and Config1 can be the same, and the terminal device is configured with Config1, so that both dynamic grant PUSCH and configured grant PUSCH are restricted to being located only on SBFD symbols, or only on non-SBFD symbols. The terminal device is also configured with Config10 in the configured grant configuration, which further indicates whether the configured grant PUSCH is located only on SBFD symbols or only on non-SBFD symbols.

[0188] This application also provides a data transmission method. Figure 12 is another schematic diagram of the data transmission method according to an embodiment of this application. As shown in Figure 12, the method includes:

[0189] 1210, The terminal device receives an uplink DCI, which includes two SRI fields and / or two PMI fields, and the uplink DCI includes an indication field;

[0190] 1220, the terminal device sends PUSCH according to the above uplink DCI;

[0191] Wherein, the first codepoint of the aforementioned indication field indicates that PUSCH is located only on SBFD symbols, or only on non-SBFD symbols; the second codepoint of the aforementioned indication field indicates that PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols; or,

[0192] The first codepoint of the above indication field indicates that the PUSCH is located only on SBFD symbols, the second codepoint of the above indication field indicates that the PUSCH is located only on non-SBFD symbols, and the third codepoint of the above indication field indicates that the PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols.

[0193] In the above embodiments, the uplink DCI always includes two SRI fields and / or two PMI fields, and the uplink DCI always includes an Indicator field. The Indicator field is used to indicate whether PUSCH is allowed across SBFD symbols and non-SBFD symbols. For example, the first codepoint of the Indicator field indicates case 1 or case 2, and the second codepoint of the Indicator field indicates case 3. As mentioned above, the terminal device can further determine whether it is case 1 or case 2 based on the first symbol of the PUSCH. For example, the first codepoint of the Indicator field indicates case 1, the second codepoint of the Indicator field indicates case 2, and the third codepoint of the Indicator field indicates case 3. For example, for case 1 or case 2, the first SRI field and / or the first PMI field are applied to the PUSCH, and the second SRI field and / or the second PMI field are left unused; for case 3, the first SRI field and / or the first PMI field are applied to the PUSCH located on the SBFD symbol, and the second SRI field and / or the second PMI field are located on the PUSCH located on the non-SBFD symbol.

[0194] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0195] Through the embodiments of this application, it is possible to determine whether the uplink transmission data performed on the terminal device is located only on SBFD symbols, only on non-SBFD symbols, or on both SBFD and non-SBFD symbols. As a result, the terminal device can flexibly implement transmission on SBFD symbols and / or non-SBFD symbols, thereby achieving a good trade-off between complexity and performance.

[0196] Second aspect of the embodiments

[0197] This application provides a data transmission method for downlink data transmission. The specific implementation of this method is similar to the data transmission method for uplink data transmission described in the first aspect embodiment. The same or corresponding content can be referred to the description in the first aspect embodiment. The content that is the same as the first aspect embodiment will not be repeated.

[0198] Figure 13 is a schematic diagram of a data transmission method according to an embodiment of this application. As shown in Figure 13, the method includes:

[0199] 1310, The terminal device receives the eleventh or twelfth message;

[0200] 1320, Terminal equipment receives downlink DCI;

[0201] 1330, The terminal device receives the PDSCH according to the aforementioned downlink DCI;

[0202] When the terminal device receives the eleventh message, the PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol;

[0203] When the terminal device receives the twelfth message, the PDSCH may be located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0204] When the terminal device receives the twelfth information, the downlink DCI includes a first indication field, wherein the first codepoint of the first indication field indicates that the PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, and the second codepoint of the first indication field indicates that the PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols; or, when the terminal device receives the twelfth information, the downlink DCI includes a second indication field, wherein the first codepoint of the second indication field indicates that the PDSCH is located only on SBFD symbols, the second codepoint of the second indication field indicates that the PDSCH is located only on non-SBFD symbols, and the third codepoint of the second indication field indicates that the PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols.

[0205] In the above embodiments, the processing method for handling whether downlink transmission crosses SBFD symbols and non-SBFD symbols can be adopted to some extent as in the uplink transmission. For example, "uplink" can be replaced with "downlink", "PUSCH" can be replaced with "PDSCH", and "DCI format 0_1 / 0_2 / 0_3 / 0_0" can be replaced with "DCI format 1_1 / 1_2 / 1_3 / 1_0" respectively. This will not be elaborated further here.

[0206] In some possible implementations, uplink and downlink can be configured independently to cross SBFD symbols and non-SBFD symbols. For example, uplink can be configured not to cross SBFD symbols and non-SBFD symbols, while downlink can be configured to cross SBFD symbols and non-SBFD symbols. Alternatively, uplink and downlink can be configured uniformly to cross SBFD symbols and non-SBFD symbols. For instance, if the terminal device receives the first information (i.e., the eleventh information is the same as the first information), then both uplink and downlink cannot cross SBFD symbols and non-SBFD symbols; if the terminal device receives the second information (i.e., the twelfth information is the same as the second information), then both uplink and downlink can cross SBFD symbols and non-SBFD symbols.

[0207] In the embodiments of this application, PDSCH can be multiple PDSCH repetitions, multiple PDSCHs, or a transport block (TB) spanning multiple time slots.

[0208] In some embodiments, similar to uplink transmission, if the first codepoint of the indication field indicates that the PDSCH is located only on an SBFD symbol or only on a non-SBFD symbol, the terminal device determines whether the PDSCH is located only on an SBFD symbol or only on a non-SBFD symbol based on whether the first symbol indicated by the downlink DCI is located on an SBFD symbol or only on a non-SBFD symbol.

[0209] In some embodiments, similar to uplink transmission, when the terminal device receives the eleventh information, the terminal device determines whether the PDSCH is located only in the SBFD symbol or only in the non-SBFD symbol based on whether the first symbol indicated by the downlink DCI is located in the SBFD symbol or in the non-SBFD symbol.

[0210] In the above embodiments, similar to uplink transmission, when the first symbol indicated by the downlink DCI is a non-SBFD symbol, the terminal device determines whether the PDSCH is located only in an SBFD symbol or only in a non-SBFD symbol based on whether the second reference symbol is located in an SBFD symbol or a non-SBFD symbol.

[0211] The second reference symbol is either the first symbol of the first PDSCH that does not overlap with the uplink symbol as indicated by the downlink DCI, or the first symbol of the first PDSCH repetition that does not overlap with the uplink symbol as indicated by the downlink DCI, or the first symbol of the first time slot that does not overlap with the uplink symbol as indicated by the downlink DCI, or the first symbol of the first time slot that does not overlap with the uplink symbol as indicated by the downlink DCI.

[0212] In some embodiments, similar to uplink transmission, the terminal device receives fifteenth information, sixteenth information, or seventeenth information; the terminal device also receives a first SPS PDSCH; when the terminal device receives the fifteenth information, the first SPS PDSCH is located only on SBFD symbols; when the terminal device receives the sixteenth information, the first SPS PDSCH is located only on non-SBFD symbols; when the terminal device receives the seventeenth information, the first SPS PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols.

[0213] Similar to uplink transmission, the above embodiments can also be implemented independently.

[0214] Figure 14 is another schematic diagram of the data transmission method according to an embodiment of this application. As shown in Figure 14, the method includes:

[0215] 1410, The terminal device receives the fifteenth, sixteenth, or seventeenth message;

[0216] 1420, the terminal device receives the first SPS PDSCH;

[0217] Specifically, when the terminal device receives the fifteenth information, the first SPS PDSCH is located only in the SBFD symbol; when the terminal device receives the sixteenth information, the first SPS PDSCH is located only in the non-SBFD symbol; when the terminal device receives the seventeenth information, the first SPS PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0218] In some embodiments, similar to uplink transmission, the terminal device receives the eighteenth or nineteenth information; the terminal device also receives the second SPS PDSCH; when the terminal device receives the eighteenth information, the second SPS PDSCH is located only on SBFD symbols, or only on non-SBFD symbols; when the terminal device receives the nineteenth information, the second SPS PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols.

[0219] Similar to uplink transmission, the above embodiments can also be implemented independently.

[0220] Figure 15 is another schematic diagram of the data transmission method according to an embodiment of this application. As shown in Figure 15, the method further includes:

[0221] 1510, The terminal device receives the eighteenth or nineteenth message;

[0222] 1520, the terminal device receives the second SPS PDSCH;

[0223] Specifically, when the terminal device receives the eighteenth information, the second SPS PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol; when the terminal device receives the nineteenth information, the second SPS PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0224] In the above embodiments, when the terminal device receives the eighteenth information, the terminal device can also receive the twentieth information and determine, based on the twentieth information, whether the second SPS PDSCH is located only in the SBFD symbol or only in the non-SBFD symbol.

[0225] The above embodiments are merely illustrative examples of embodiments of this application, but this application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0226] Through the embodiments of this application, it is possible to determine whether the downlink transmission data performed on the terminal device is located only on SBFD symbols, only on non-SBFD symbols, or on both SBFD and non-SBFD symbols. Thus, the terminal device can flexibly implement transmission on SBFD symbols and / or non-SBFD symbols, thereby achieving a good trade-off between complexity and performance.

[0227] Third aspect of the embodiments

[0228] This application provides a data transmission device installed on a terminal device. Since the principle by which this device solves the problem is similar to the method in the first aspect embodiment, its specific implementation can refer to the implementation of the method described in the first aspect embodiment; the same or related parts will not be repeated.

[0229] Figure 16 is a schematic diagram of a data transmission apparatus according to an embodiment of this application. As shown in Figure 16, the apparatus 1600 includes:

[0230] The first receiving unit 1610 receives first information or second information;

[0231] The second receiving unit 1620 receives uplink DCI (downlink control information);

[0232] Transmitting unit 1630 transmits the first PUSCH (Physical Uplink Shared Channel) according to the uplink DCI;

[0233] Specifically, when the first receiving unit 1610 receives the first information, the first PUSCH is located only in an SBFD (Subband Full-Duplex) symbol, or only in a non-SBFD symbol; when the first receiving unit 1610 receives the second information, the first PUSCH is located only in an SBFD symbol, or only in a non-SBFD symbol, or in both an SBFD symbol and a non-SBFD symbol; when the first receiving unit 1610 receives the first information, the uplink DCI includes one SRI field and / or one PMI field; when the first receiving unit 1610 receives the second information, the uplink DCI includes two SRI fields and / or two PMI fields.

[0234] In the embodiments of this application, the first PUSCH is a plurality of PUSCH repetitions, or a plurality of PUSCHs, or a transport block (TB) spanning multiple time slots.

[0235] In some embodiments, when the first receiving unit 1610 receives the second information, the uplink DCI includes a first indication field; the first codepoint of the first indication field indicates that the first PUSCH is located only in SBFD symbols, or only in non-SBFD symbols; the second codepoint of the first indication field indicates that the first PUSCH is located only in SBFD symbols, or only in non-SBFD symbols, or in both SBFD symbols and non-SBFD symbols.

[0236] In some embodiments, if the first codepoint in the first indication field indicates that the first PUSCH is located only on an SBFD symbol or only on a non-SBFD symbol, the location of the first PUSCH is determined based on whether the first symbol indicated by the uplink DCI is located on an SBFD symbol or only on a non-SBFD symbol.

[0237] In some embodiments, when the first receiving unit 1610 receives the first information, it determines whether the first PUSCH is located only in an SBFD symbol or only in a non-SBFD symbol based on whether the first symbol indicated by the uplink DCI is located in an SBFD symbol or in a non-SBFD symbol.

[0238] In some embodiments, if the first symbol indicated by the uplink DCI is a non-SBFD symbol, the first PUSCH is determined to be located only in an SBFD symbol or only in a non-SBFD symbol based on whether the first reference symbol is located in an SBFD symbol or a non-SBFD symbol.

[0239] In the above embodiments, the first reference symbol is the first symbol of the first PUSCH that does not overlap with the downlink symbol as indicated by the uplink DCI, or the first symbol of the first PUSCH repetition that does not overlap with the downlink symbol as indicated by the uplink DCI, or the first symbol of the first time slot that does not overlap with the downlink symbol as indicated by the uplink DCI, or the first symbol that does not overlap with the downlink symbol as indicated by the uplink DCI.

[0240] In some embodiments, when the terminal device receives the second information, the uplink DCI includes a second indication field; the first codepoint of the second indication field indicates that the first PUSCH is located only on SBFD symbols; the second codepoint of the second indication field indicates that the first PUSCH is located only on non-SBFD symbols; the third codepoint of the second indication field indicates that the first PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols.

[0241] In some embodiments, the terminal device is configured with two SRS resource sets, the first SRS resource set being applied to PUSCH located on SBFD symbols, and the second SRS resource set being applied to PUSCH located on non-SBFD symbols.

[0242] In some embodiments, the first receiving unit 1610 receives third information or fourth information; and the second receiving unit 1620 receives DCI format 0_0 scrambled by RAR UL grant or CRC by TC-RNTI, and the sending unit 1630 sends a second PUSCH according to DCI format 0_0 scrambled by RAR UL grant or CRC by TC-RNTI.

[0243] Specifically, when the first receiving unit 1610 receives the third information, the second PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol; when the first receiving unit 1610 receives the fourth information, the second PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0244] In some embodiments, the first receiving unit 1610 receives the fifth, sixth, or seventh information; the sending unit 1630 sends the first configured grant PUSCH.

[0245] Specifically, when the first receiving unit 1610 receives the fifth information, the first configured grant PUSCH is located only on the SBFD symbol; when the first receiving unit 1610 receives the sixth information, the first configured grant PUSCH is located only on the non-SBFD symbol; when the first receiving unit 1610 receives the seventh information, the first configured grant PUSCH is located only on the SBFD symbol, or only on the non-SBFD symbol, or on both the SBFD symbol and the non-SBFD symbol.

[0246] In some embodiments, the first receiving unit 1610 receives the eighth or ninth information; the sending unit 1630 sends the second configured grant PUSCH.

[0247] Specifically, when the first receiving unit 1610 receives the eighth information, the second configured grant PUSCH is located only on the SBFD symbol, or only on the non-SBFD symbol; when the first receiving unit 1610 receives the ninth information, the second configured grant PUSCH is located only on the SBFD symbol, or only on the non-SBFD symbol, or on both the SBFD symbol and the non-SBFD symbol.

[0248] In some embodiments, when the first receiving unit 1610 receives the eighth information, the first receiving unit 1610 also receives the tenth information; thereby, the terminal device determines, based on the tenth information, whether the second configured grant PUSCH is located only on SBFD symbols or only on non-SBFD symbols.

[0249] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The data transmission device 1600 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0250] Furthermore, for simplicity, Figure 16 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0251] Through the embodiments of this application, it is possible to determine whether the uplink transmission data performed on the terminal device is located only on SBFD symbols, only on non-SBFD symbols, or on both SBFD and non-SBFD symbols. As a result, the terminal device can flexibly implement transmission on SBFD symbols and / or non-SBFD symbols, thereby achieving a good trade-off between complexity and performance.

[0252] Fourth aspect of the embodiment

[0253] This application provides a data transmission device installed on a terminal device. Since the principle by which this device solves the problem is similar to the method in the second aspect of the embodiment, its specific implementation can refer to the implementation of the method described in the second aspect of the embodiment; the same or related parts will not be repeated.

[0254] Figure 17 is another schematic diagram of a data transmission apparatus according to an embodiment of this application. As shown in Figure 17, the apparatus 1700 includes:

[0255] The first receiving unit 1710 receives either the eleventh or twelfth information;

[0256] The second receiving unit 1720 receives downlink DCI;

[0257] The third receiving unit 1730 receives PDSCH according to the downlink DCI;

[0258] When the first receiving unit 1710 receives the eleventh information, the PDSCH is located only in SBFD symbols, or only in non-SBFD symbols; when the first receiving unit 1710 receives the twelfth information, the PDSCH is located only in SBFD symbols, or only in non-SBFD symbols, or in both SBFD and non-SBFD symbols; when the first receiving unit 1710 receives the twelfth information, the downlink DCI includes a first indication field, the first codepoint of the first indication field indicates that the PDSCH is located only in SBFD symbols, or only in non-SBFD symbols, and the second codepoint of the first indication field indicates that the PDSCH is located only in SBFD symbols, or only in non-SBFD symbols, or in both SBFD and non-SBFD symbols; or, when the first receiving unit 1710 receives the twelfth information, the downlink DCI includes a second indication field, the first codepoint of the second indication field indicates that the PDSCH is located only in SBFD symbols, the second codepoint of the second indication field indicates that the PDSCH is located only in non-SBFD symbols, and the third codepoint of the second indication field indicates that the PDSCH is located only in SBFD symbols, or only in non-SBFD symbols, or in both SBFD and non-SBFD symbols.

[0259] In the embodiments of this application, PDSCH is a multiple PDSCH repetition, or multiple PDSCHs, or a transport block (TB) spanning multiple time slots.

[0260] In some embodiments, if the first codepoint of the indication field indicates that the PDSCH is located only on an SBFD symbol or only on a non-SBFD symbol, the terminal device determines whether the PDSCH is located only on an SBFD symbol or only on a non-SBFD symbol based on whether the first symbol indicated by the downlink DCI is located on an SBFD symbol or on a non-SBFD symbol.

[0261] In some embodiments, when the first receiving unit 1710 receives the eleventh information, the terminal device determines whether the PDSCH is located only in the SBFD symbol or only in the non-SBFD symbol based on whether the first symbol indicated by the downlink DCI is located in the SBFD symbol or in the non-SBFD symbol.

[0262] In some embodiments, if the first symbol indicated by the downlink DCI is a non-SBFD symbol, the terminal device determines whether the PDSCH is located only in an SBFD symbol or only in a non-SBFD symbol based on whether the second reference symbol is located in an SBFD symbol or a non-SBFD symbol.

[0263] The second reference symbol is either the first symbol of the first PDSCH that does not overlap with the uplink symbol as indicated by the downlink DCI, or the first symbol of the first PDSCH repetition that does not overlap with the uplink symbol as indicated by the downlink DCI, or the first symbol of the first time slot that does not overlap with the uplink symbol as indicated by the downlink DCI, or the first symbol of the first time slot that does not overlap with the uplink symbol as indicated by the downlink DCI.

[0264] In some embodiments, the first receiving unit 1710 further receives the fifteenth, sixteenth, or seventeenth information; the third receiving unit 1730 further receives the first SPS PDSCH; when the first receiving unit 1710 receives the fifteenth information, the first SPS PDSCH is located only on SBFD symbols; when the first receiving unit 1710 receives the sixteenth information, the first SPS PDSCH is located only on non-SBFD symbols; when the first receiving unit 1710 receives the seventeenth information, the first SPS PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols.

[0265] In some embodiments, the first receiving unit 1710 also receives the eighteenth or nineteenth information; the third receiving unit 1730 also receives the second SPS PDSCH; when the first receiving unit 1710 receives the eighteenth information, the second SPS PDSCH is located only on SBFD symbols, or only on non-SBFD symbols; when the first receiving unit 1710 receives the nineteenth information, the second SPS PDSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD symbols and non-SBFD symbols.

[0266] In some embodiments, when the first receiving unit 1710 receives the eighteenth information, the first receiving unit 1710 also receives the twentieth information; the terminal device determines, based on the twentieth information, whether the second SPS PDSCH is located only in SBFD symbols or only in non-SBFD symbols.

[0267] It is worth noting that the above description only covers the components or modules relevant to this application, but this application is not limited thereto. The data transmission device 1700 may also include other components or modules, and for details regarding these components or modules, please refer to related technologies.

[0268] Furthermore, for simplicity, Figure 17 only illustrates the connection relationships or signal flow between the various components or modules, but those skilled in the art should understand that various related technologies such as bus connections can be used. The aforementioned components or modules can be implemented using hardware facilities such as processors, memory, transmitters, and receivers; this application does not limit this implementation.

[0269] Through the embodiments of this application, it is possible to determine whether the downlink transmission data performed on the terminal device is located only on SBFD symbols, only on non-SBFD symbols, or on both SBFD and non-SBFD symbols. Thus, the terminal device can flexibly implement transmission on SBFD symbols and / or non-SBFD symbols, thereby achieving a good trade-off between complexity and performance.

[0270] Fifth aspect of the embodiment

[0271] This application also provides a communication system, which includes a terminal device and a network device. Referring to FIG1, the contents that are the same as those in the embodiments of the first and second aspects will not be repeated.

[0272] In some embodiments, the terminal device is configured to:

[0273] Receive the first or second information and the uplink DCI (downlink control information), and send the first PUSCH (physical uplink shared channel) according to the uplink DCI.

[0274] Specifically, when the terminal device receives the first information, the first PUSCH is located only on an SBFD (Subband Full-Duplex) symbol, or only on a non-SBFD symbol; when the terminal device receives the second information, the first PUSCH is located only on an SBFD symbol, or only on a non-SBFD symbol, or on both an SBFD symbol and a non-SBFD symbol; when the terminal device receives the first information, the uplink DCI includes one SRI field and / or one PMI field; when the terminal device receives the second information, the uplink DCI includes two SRI fields and / or two PMI fields.

[0275] In some embodiments, the terminal device is configured with Msg3 repetition, and the terminal device is configured as follows:

[0276] Receive the third or fourth information, and receive the DCI format 0_0 scrambled by TC-RNTI for RAR UL grant or CRC, and send the second PUSCH according to the DCI format 0_0 scrambled by TC-RNTI for RAR UL grant or CRC.

[0277] Specifically, when the terminal device receives the third information, the second PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol; when the terminal device receives the fourth information, the second PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0278] In some embodiments, the terminal device is configured to:

[0279] Receive the fifth, sixth, or seventh message; send the first configured grant PUSCH.

[0280] Specifically, when the terminal device receives the fifth information, the first configured grant PUSCH is located only on the SBFD symbol; when the terminal device receives the sixth information, the first configured grant PUSCH is located only on the non-SBFD symbol; when the terminal device receives the seventh information, the first configured grant PUSCH is located only on the SBFD symbol, or only on the non-SBFD symbol, or on both the SBFD symbol and the non-SBFD symbol.

[0281] In some embodiments, the terminal device is configured to:

[0282] Receive the eighth or ninth message; send the second configured grant PUSCH.

[0283] Specifically, when the terminal device receives the eighth message, the second configured grant PUSCH is located only on the SBFD symbol, or only on the non-SBFD symbol; when the terminal device receives the ninth message, the second configured grant PUSCH is located only on the SBFD symbol, or only on the non-SBFD symbol, or on both the SBFD symbol and the non-SBFD symbol.

[0284] In some embodiments, the terminal device is configured to:

[0285] Receive the uplink DCI and send the PUSCH based on the uplink DCI.

[0286] The uplink DCI includes two SRI fields and / or two PMI fields, and the uplink DCI includes an indicator field.

[0287] Specifically, the first codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, or only on non-SBFD symbols; the second codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols; or, the first codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, the second codepoint of the indicator field indicates that the PUSCH is located only on non-SBFD symbols, and the third codepoint of the indicator field indicates that the PUSCH is located only on SBFD symbols, or only on non-SBFD symbols, or on both SBFD and non-SBFD symbols.

[0288] In some embodiments, the terminal device is configured to:

[0289] Receive the eleventh or twelfth message; and receive the downlink DCI; receive the PDSCH based on the downlink DCI.

[0290] Specifically, when the terminal device receives the eleventh message, the PDSCH is located only on the SBFD symbol, or only on the non-SBFD symbol; when the terminal device receives the twelfth message, the PDSCH is located only on the SBFD symbol, or only on the non-SBFD symbol, or on both the SBFD symbol and the non-SBFD symbol.

[0291] When the terminal device receives the twelfth information, the downlink DCI includes a first indication field, wherein the first codepoint of the first indication field indicates that the PDSCH is located only in SBFD symbols, or only in non-SBFD symbols, and the second codepoint of the first indication field indicates that the PDSCH is located only in SBFD symbols, or only in non-SBFD symbols, or in both SBFD symbols and non-SBFD symbols; or, when the terminal device receives the twelfth information, the downlink DCI includes a second indication field, wherein the first codepoint of the second indication field indicates that the PDSCH is located only in SBFD symbols, the second codepoint of the second indication field indicates that the PDSCH is located only in non-SBFD symbols, and the third codepoint of the second indication field indicates that the PDSCH is located only in SBFD symbols, or only in non-SBFD symbols, or in both SBFD symbols and non-SBFD symbols.

[0292] In some embodiments, the terminal device is configured to:

[0293] Receive the fifteenth, sixteenth, or seventeenth message; and receive the first SPS PDSCH.

[0294] Specifically, when the terminal device receives the fifteenth information, the first SPS PDSCH is located only in the SBFD symbol; when the terminal device receives the sixteenth information, the first SPS PDSCH is located only in the non-SBFD symbol; when the terminal device receives the seventeenth information, the first SPS PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0295] In some embodiments, the terminal device is configured to:

[0296] Receive the eighteenth or nineteenth message; and receive the second SPS PDSCH.

[0297] Specifically, when the terminal device receives the eighteenth information, the second SPS PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol; when the terminal device receives the nineteenth information, the second SPS PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0298] This application also provides a terminal device, which can be any of the aforementioned devices, but this application is not limited to these and can also be other devices.

[0299] Figure 18 is a schematic diagram of a terminal device according to an embodiment of this application. As shown in Figure 18, the terminal device 1800 may include a processor 1810 and a memory 1820; the memory 1820 stores data and programs and is coupled to the processor 1810. It is worth noting that this figure is exemplary; other types of structures may also be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0300] As shown in Figure 18, the terminal device 1800 may further include: a communication module 1830, an input unit 1840, a display 1850, and a power supply 1860. The functions of these components are similar to those in the prior art and will not be described again here. It is worth noting that the terminal device 1800 does not necessarily include all the components shown in Figure 18; these components are not essential. Furthermore, the terminal device 1800 may also include components not shown in Figure 18, which can be referred to in the prior art.

[0301] For example, processor 1810 and communication module 1830 can be configured to execute programs to implement the methods described in the embodiments of the first and second aspects.

[0302] This application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to perform the methods described in the embodiments of the first and second aspects.

[0303] This application also provides a storage medium storing a computer program, wherein the computer program causes a terminal device to execute the methods described in the embodiments of the first and second aspects.

[0304] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, etc.

[0305] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, one or more and / or combinations of one or more functional block diagrams shown in the figures can correspond to various software modules in a computer program flow, or to various hardware modules. These software modules can correspond to the various steps shown in the figures, respectively. These hardware modules can be implemented, for example, using a field-programmable gate array (FPGA) to embed these software modules.

[0306] The software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. A storage medium can be coupled to the processor, enabling the processor to read information from and write information to the storage medium; or the storage medium can be an integral part of the processor. The processor and storage medium can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

[0307] One or more and / or one or more combinations of functional blocks described in the accompanying drawings can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. One or more and / or one or more combinations of functional blocks described in the accompanying drawings can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0308] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0309] Regarding the implementation methods including the above embodiments, the following notes are also disclosed:

[0310] 1. A data transmission method, wherein the method comprises:

[0311] The terminal device receives third or fourth information, and the terminal device is configured with Msg3 repetition;

[0312] The terminal device receives RAR UL grant or CRC scrambled by TC-RNTI in DCI format 0_0;

[0313] The terminal device sends a second PUSCH according to the DCI format 0_0 scrambled by TC-RNTI according to the RAR UL grant or CRC.

[0314] in,

[0315] When the terminal device receives the third information, the second PUSCH is located only at an SBFD symbol, or only at a non-SBFD symbol;

[0316] When the terminal device receives the fourth information, the second PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0317] 2. A data transmission method, wherein the method includes:

[0318] The terminal device receives the fifth, sixth, or seventh information;

[0319] The terminal device sends the first configured grant PUSCH.

[0320] in,

[0321] When the terminal device receives the fifth information, the first configured grant PUSCH is located only in the SBFD symbol;

[0322] When the terminal device receives the sixth information, the first configured grant PUSCH is located only in a non-SBFD symbol;

[0323] When the terminal device receives the seventh information, the first configured grant PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0324] 3. A data transmission method, wherein the method includes:

[0325] The terminal device receives the eighth or ninth message;

[0326] The terminal device sends a second configured grant PUSCH;

[0327] When the terminal device receives the eighth information, the second configured grant PUSCH is located only on an SBFD symbol, or only on a non-SBFD symbol;

[0328] When the terminal device receives the ninth information, the second configured grant PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0329] 4. The method according to Appendix 3, wherein, when the terminal device receives the eighth information, the method further includes:

[0330] The terminal device receives the tenth information;

[0331] The terminal device determines, based on the tenth information, whether the second configured grant PUSCH is located only on SBFD symbols or only on non-SBFD symbols.

[0332] 5. A data transmission method, wherein the method includes:

[0333] The terminal device receives the fifteenth, sixteenth, or seventeenth message;

[0334] The terminal device receives the first SPS PDSCH;

[0335] When the terminal device receives the fifteenth information, the first SPS PDSCH is located only at the SBFD symbol;

[0336] When the terminal device receives the sixteenth information, the first SPS PDSCH is located only in a non-SBFD symbol;

[0337] When the terminal device receives the seventeenth information, the first SPS PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0338] 6. A data transmission method, wherein the method comprises:

[0339] The terminal device receives the eighteenth or nineteenth message;

[0340] The terminal device receives the second SPS PDSCH;

[0341] When the terminal device receives the eighteenth information, the second SPS PDSCH is located only at the SBFD symbol, or only at a non-SBFD symbol;

[0342] When the terminal device receives the nineteenth information, the second SPS PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0343] 7. The method according to Appendix 6, wherein, when the terminal device receives the eighteenth information, the method further includes:

[0344] The terminal device receives the twentieth message;

[0345] The terminal device determines, based on the twentieth information, whether the second SPS PDSCH is located only at SBFD symbols or only at non-SBFD symbols.

[0346] 8. A data transmission method, wherein the method comprises:

[0347] The terminal device receives either the first information or the second information;

[0348] The terminal device receives the uplink DCI;

[0349] The terminal device sends a first PUSCH (Physical Uplink Shared Channel) according to the uplink DCI;

[0350] in,

[0351] When the terminal device receives the first information, the first PUSCH is located only in an SBFD (Subband Full-Duplex) symbol, or only in a non-SBFD symbol;

[0352] When the terminal device receives the second information, the first PUSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0353] 9. A data transmission method, wherein the method comprises:

[0354] The terminal device receives the eleventh or twelfth message;

[0355] The terminal device receives downlink DCI;

[0356] The terminal device receives PDSCH according to the downlink DCI;

[0357] When the terminal device receives the eleventh information, the PDSCH is located only at the SBFD symbol, or only at a non-SBFD symbol;

[0358] When the terminal device receives the twelfth information, the PDSCH is located only in the SBFD symbol, or only in the non-SBFD symbol, or in both the SBFD symbol and the non-SBFD symbol.

[0359] 10. A communication system comprising a terminal device and a network device, wherein the terminal device includes a memory and a processor, the memory storing a computer program, and the processor being configured to execute the computer program to implement the method as described in any one of Appendices 1 to 9.

Claims

1. A data transmission apparatus configured in a terminal device, wherein, The apparatus comprises: a first receiving unit receiving first information or second information; a second receiving unit receiving uplink DCI (downlink control information); a sending unit sending a first PUSCH (physical uplink shared channel) according to the uplink DCI; wherein, in a case where the first receiving unit receives the first information, the first PUSCH is located only in SBFD (sub-band full duplex) symbols or only in non-SBFD symbols; in a case where the first receiving unit receives the second information, the first PUSCH is located only in SBFD symbols or only in non-SBFD symbols or in SBFD symbols and non-SBFD symbols; in a case where the first receiving unit receives the first information, the uplink DCI comprises one SRI field and / or one PMI field; in a case where the first receiving unit receives the second information, the uplink DCI comprises two SRI fields and / or two PMI fields.

2. The apparatus according to claim 1, wherein, in a case where the first receiving unit receives the second information, the uplink DCI comprises a first indication field; a first codepoint (code point) of the first indication field indicates that the first PUSCH is located only in SBFD symbols or only in non-SBFD symbols; a second codepoint of the first indication field indicates that the first PUSCH is located only in SBFD symbols or only in non-SBFD symbols or in SBFD symbols and non-SBFD symbols.

3. The apparatus according to claim 2, wherein, in a case where the first codepoint of the first indication field indicates that the first PUSCH is located only in SBFD symbols or only in non-SBFD symbols, the terminal device determines whether the first PUSCH is located only in SBFD symbols or only in non-SBFD symbols according to whether a first symbol indicated by the uplink DCI is located in SBFD symbols or non-SBFD symbols.

4. The apparatus according to claim 1, wherein, in a case where the first receiving unit receives the first information, the terminal device determines whether the first PUSCH is located only in SBFD symbols or only in non-SBFD symbols according to whether a first symbol indicated by the uplink DCI is located in SBFD symbols or non-SBFD symbols.

5. The apparatus according to claim 4, wherein, in a case where the first symbol indicated by the uplink DCI is a non-SBFD symbol, the terminal device determines whether the first PUSCH is located only in SBFD symbols or only in non-SBFD symbols according to whether a first reference symbol is located in SBFD symbols or non-SBFD symbols, The first reference symbol is a first symbol of a first PUSCH indicated by the uplink DCI without overlapping with downlink symbols, or a first symbol of a first PUSCH repetition indicated by the uplink DCI without overlapping with downlink symbols, or a first symbol of a first slot indicated by the uplink DCI without overlapping with downlink symbols, or a first symbol indicated by the uplink DCI without overlapping with downlink symbols.

6. The apparatus of claim 1, wherein, in a case where the first receiving unit receives the second information, the uplink DCI comprises a second indication field; a first codepoint of the second indication field indicates that the first PUSCH is located only in SBFD symbols; a second codepoint of the second indication field indicates that the first PUSCH is located only in non-SBFD symbols; a third codepoint of the second indication field indicates that the first PUSCH is located only in SBFD symbols, or only in non-SBFD symbols, or in SBFD symbols and non-SBFD symbols.

7. The apparatus of claim 1, wherein, the first PUSCH is a plurality of PUSCH repetitions, or a plurality of PUSCHs, or a transport block (TB) across a plurality of slots.

8. The apparatus of claim 1, wherein, the terminal device is configured with two SRS resource sets, a first SRS resource set is applied to PUSCHs located in SBFD symbols, and a second SRS resource set is applied to PUSCHs located in non-SBFD symbols.

9. The apparatus of claim 1, wherein, the terminal device is configured with Msg3 repetition, the first receiving unit receives third information or fourth information; the second receiving unit receives a RAR UL grant or a DCI format 0_0 scrambled with a TC-RNTI; the sending unit sends a second PUSCH according to the RAR UL grant or the DCI format 0_0 scrambled with the TC-RNTI; wherein, in a case where the first receiving unit receives the third information, the second PUSCH is located only in SBFD symbols, or only in non-SBFD symbols; in a case where the first receiving unit receives the fourth information, the second PUSCH is located only in SBFD symbols, or only in non-SBFD symbols, or in SBFD symbols and non-SBFD symbols.

10. The apparatus of claim 1, wherein, the first receiving unit further receives fifth information, sixth information, or seventh information; the sending unit further sends a first configured grant PUSCH (CG-PUSCH); wherein, In a case that the first receiving unit receives the fifth information, the first configured grant PUSCH is only located in SBFD symbols; In a case that the first receiving unit receives the sixth information, the first configured grant PUSCH is only located in non-SBFD symbols; In a case that the first receiving unit receives the seventh information, the first configured grant PUSCH is only located in SBFD symbols, or only located in non-SBFD symbols, or located in SBFD symbols and non-SBFD symbols.

11. The apparatus of claim 1, wherein, the first receiving unit further receives eighth information or ninth information; the sending unit further sends a second configured grant PUSCH; In a case that the first receiving unit receives the eighth information, the second configured grant PUSCH is only located in SBFD symbols, or only located in non-SBFD symbols; In a case that the first receiving unit receives the ninth information, the second configured grant PUSCH is only located in SBFD symbols, or only located in non-SBFD symbols, or located in SBFD symbols and non-SBFD symbols.

12. The apparatus of claim 11, wherein, In a case that the first receiving unit receives the eighth information, the first receiving unit further receives tenth information; the terminal device determines, according to the tenth information, whether the second configured grant PUSCH is only located in SBFD symbols or only located in non-SBFD symbols. The apparatus comprises:

13. A data transmission apparatus configured in a terminal device, wherein, a receiving unit that receives uplink DCI, the uplink DCI comprising two SRI fields and / or two PMI fields, and the uplink DCI comprising an indication field; a sending unit that sends a PUSCH according to the uplink DCI; wherein, a first codepoint of the indication field indicates that the PUSCH is only located in SBFD symbols, or only located in non-SBFD symbols, and a second codepoint of the indication field indicates that the PUSCH is only located in SBFD symbols, or only located in non-SBFD symbols, or located in SBFD symbols and non-SBFD symbols; or a first codepoint of the indication field indicates that the PUSCH is only located in SBFD symbols, a second codepoint of the indication field indicates that the PUSCH is only located in non-SBFD symbols, and a third codepoint of the indication field indicates that the PUSCH is only located in SBFD symbols, or only located in non-SBFD symbols, or located in SBFD symbols and non-SBFD symbols. The apparatus comprises:

14. A data transmission apparatus configured to a terminal device, wherein, a first receiving unit that receives eleventh information or twelfth information; a second receiving unit that receives downlink DCI; a third receiving unit that receives a PDSCH according to the downlink DCI; ​ In a case that the first receiving unit receives the eleventh information, the PDSCH is located only in SBFD symbols or only in non-SBFD symbols; In a case that the first receiving unit receives the twelfth information, the PDSCH is located only in SBFD symbols or only in non-SBFD symbols, or in SBFD symbols and non-SBFD symbols; In a case that the first receiving unit receives the twelfth information, the downlink DCI includes a first indication field, a first codepoint of the first indication field indicates that the PDSCH is located only in SBFD symbols or only in non-SBFD symbols, a second codepoint of the first indication field indicates that the PDSCH is located only in SBFD symbols or only in non-SBFD symbols, or in SBFD symbols and non-SBFD symbols; or, the downlink DCI includes a second indication field, a first codepoint of the second indication field indicates that the PDSCH is located only in SBFD symbols, a second codepoint of the second indication field indicates that the PDSCH is located only in non-SBFD symbols, and a third codepoint of the second indication field indicates that the PDSCH is located only in SBFD symbols or only in non-SBFD symbols, or in SBFD symbols and non-SBFD symbols.

15. The apparatus of claim 14, wherein, In a case that the first codepoint of the indication field indicates that the PDSCH is located only in SBFD symbols or only in non-SBFD symbols, the terminal device determines whether the PDSCH is located only in SBFD symbols or only in non-SBFD symbols according to whether a first symbol indicated by the downlink DCI is located in SBFD symbols or non-SBFD symbols.

16. The apparatus of claim 14, wherein, In a case that the first receiving unit receives the eleventh information, the terminal device determines whether the PDSCH is located only in SBFD symbols or only in non-SBFD symbols according to whether a first symbol indicated by the downlink DCI is located in SBFD symbols or non-SBFD symbols.

17. The apparatus of claim 16, wherein, In a case that the first symbol indicated by the downlink DCI is a non-SBFD symbol, the terminal device determines whether the PDSCH is located only in SBFD symbols or only in non-SBFD symbols according to whether a second reference symbol is located in SBFD symbols or non-SBFD symbols, wherein the second reference symbol is a first symbol of a first PDSCH indicated by the downlink DCI which does not overlap with an uplink symbol, or a first symbol of a first PDSCH repetition indicated by the downlink DCI which does not overlap with an uplink symbol, or a first symbol of a first slot indicated by the downlink DCI which does not overlap with an uplink symbol, or a first symbol indicated by the downlink DCI which does not overlap with an uplink symbol.

18. The apparatus of claim 14, wherein, the PDSCH is a plurality of PDSCH repetitions, or a plurality of PDSCHs, or a transport block (TB) across multiple slots.

19. The apparatus of claim 14, wherein, the first receiving unit further receives fifteenth information, sixteenth information, or seventeenth information; the third receiving unit further receives a first SPS PDSCH; in a case where the first receiving unit receives the fifteenth information, the first SPS PDSCH is located only in SBFD symbols; in a case where the first receiving unit receives the sixteenth information, the first SPS PDSCH is located only in non-SBFD symbols; in a case where the first receiving unit receives the seventeenth information, the first SPS PDSCH is located only in SBFD symbols, or only in non-SBFD symbols, or in SBFD symbols and non-SBFD symbols.

20. The apparatus of claim 14, wherein, the first receiving unit further receives eighteenth information or nineteenth information; the third receiving unit further receives a second SPS PDSCH; in a case where the first receiving unit receives the eighteenth information, the second SPS PDSCH is located only in SBFD symbols, or only in non-SBFD symbols; in a case where the first receiving unit receives the nineteenth information, the second SPS PDSCH is located only in SBFD symbols, or only in non-SBFD symbols, or in SBFD symbols and non-SBFD symbols; wherein, in a case where the first receiving unit receives the eighteenth information, the first receiving unit further receives twentieth information; the terminal device determines, according to the twentieth information, whether the second SPS PDSCH is located only in SBFD symbols or only in non-SBFD symbols.

Images