Uplink transmission method and apparatus, uplink transmission configuration method and apparatus, and communication device

Abstract

The present application belongs to the technical field of communications. Disclosed are an uplink transmission method and apparatus, an uplink transmission configuration method and apparatus, and a communication device. The uplink transmission method in the embodiments of the present application comprises: a terminal determining a target time-domain type corresponding to a first uplink transmission, wherein the target time-domain type comprises a subband full-duplex (SBFD) time-domain type or a non-SBFD time-domain type; and the terminal determining transmission parameters of the first uplink transmission on the basis of the target time-domain type.

Description

Uplink transmission method, uplink transmission configuration method, device and communication equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202311678571.6 filed in China on December 7, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to an uplink transmission method, an uplink transmission configuration method, an apparatus, and a communication device. Background Art

[0004] Currently, uplink transmissions occur only on uplink (UL) symbols or flexible symbols. If an uplink transmission overlaps with a semi-static downlink (DL) symbol or a synchronization signal block (SSB) symbol, the user equipment (UE) cancels the uplink transmission. In related technologies, the New Radio (NR) system introduces full-duplex transmission technology, allowing UEs to be configured with subband full-duplex (SBFD) time-domain resources. However, how to perform uplink transmissions in this SBFD configuration remains a challenge. Summary of the Invention

[0005] The embodiments of the present application provide an uplink transmission method, an uplink transmission configuration method, an apparatus, and a communication device, which can solve the problem of how to perform uplink transmission under SBFD configuration.

[0006] In a first aspect, an uplink transmission method is provided, the method comprising:

[0007] The terminal determines a target time domain type corresponding to the first uplink transmission, where the target time domain type includes a sub-band full-duplex (SBFD) time domain type or a non-sub-band full-duplex (non-SBFD) time domain type;

[0008] The terminal determines, according to the target time domain type, a transmission parameter of the first uplink transmission.

[0009] In a second aspect, an uplink transmission device is provided, which is applied to a terminal, and the device includes:

[0010] A first processing module is configured to determine a target time domain type corresponding to a first uplink transmission, where the target time domain type includes a sub-band full-duplex (SBFD) time domain type or a non-sub-band full-duplex (non-SBFD) time domain type;

[0011] The second processing module is configured to determine a transmission parameter of the first uplink transmission according to the target time domain type.

[0012] In a third aspect, a method for configuring uplink transmission is provided, including:

[0013] The network side device sends configuration information or scheduling information to the terminal, where the configuration information or the scheduling information is used to determine a target time domain type for the first uplink transmission;

[0014] The target time domain type includes a sub-band full-duplex (SBFD) time domain type or a non-sub-band full-duplex (non-SBFD) time domain type.

[0015] In a fourth aspect, an uplink transmission configuration device is provided, which is applied to a network-side device, and includes:

[0016] A first sending module, configured to send configuration information or scheduling information to a terminal, where the configuration information or the scheduling information is used to determine a target time domain type for a first uplink transmission;

[0017] The target time domain type includes a sub-band full-duplex (SBFD) time domain type or a non-sub-band full-duplex (non-SBFD) time domain type.

[0018] In a fifth aspect, a communication device is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the steps of the method described in the first aspect, or implements the steps of the method described in the third aspect.

[0019] In the sixth aspect, a terminal is provided, which includes a processor and a communication interface, wherein the processor is used to: determine a target time domain type corresponding to a first uplink transmission, the target time domain type including a sub-band full-duplex SBFD time domain type or a non-sub-band full-duplex non-SBFD time domain type; and determine the transmission parameters of the first uplink transmission according to the target time domain type.

[0020] In the seventh aspect, a network side device is provided, which includes a processor and a communication interface, wherein the communication interface is used to: send configuration information or scheduling information to the terminal, and the configuration information or the scheduling information is used to determine the target time domain type of the first uplink transmission; wherein the target time domain type includes a sub-band full-duplex SBFD time domain type or a non-sub-band full-duplex non-SBFD time domain type.

[0021] In an eighth aspect, a communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the uplink transmission method as described in the first aspect, and the network side device can be used to execute the steps of the uplink transmission configuration method as described in the third aspect.

[0022] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0023] In the tenth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the third aspect.

[0024] In the eleventh aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect, or to implement the steps of the method described in the third aspect.

[0025] In an embodiment of the present application, a terminal determines a target time domain type corresponding to a first uplink transmission, where the target time domain type includes an SBFD time domain type or a non-SBFD time domain type; and the terminal determines transmission parameters for the first uplink transmission based on the target time domain type. This enables the terminal to more reasonably determine uplink transmission parameters under an SBFD configuration, thereby enabling the terminal to more reasonably perform uplink transmission under the SBFD configuration, thereby ensuring communication performance of the terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] FIG1 is a schematic diagram of a network structure applicable to an embodiment of the present application;

[0027] FIG2 is a schematic diagram of a flexible duplex mode;

[0028] FIG3 is a flow chart of an uplink transmission method provided in an embodiment of the present application;

[0029] FIG4 is a schematic diagram of a time unit where a PUSCH is provided in an embodiment of the present application;

[0030] FIG5 is a second schematic diagram of a time unit where a PUSCH is provided in an embodiment of the present application;

[0031] FIG6 is a structural diagram of an uplink transmission device provided in an embodiment of the present application;

[0032] FIG7 is a flowchart of an uplink transmission configuration method provided in an embodiment of the present application;

[0033] FIG8 is a structural diagram of an uplink transmission configuration device provided in an embodiment of the present application;

[0034] FIG9 is a structural diagram of a communication device provided in an embodiment of the present application;

[0035] FIG10 is a structural diagram of a terminal provided in an embodiment of the present application;

[0036] FIG11 is a structural diagram of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0037] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0038] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0039] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0040] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0041] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. In addition to the above-mentioned terminal devices, it can also be a chip in the terminal, such as a modem chip, a system-on-chip (SoC). It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device, wherein the access network device may also be called a radio access network (RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0042] Before describing the embodiments of the present application, the following briefly introduces the relevant technologies:

[0043] 1. Physical Uplink Control Channel (PUCCH) Resource Configuration and Determination in NR

[0044] In NR, PUCCH resources are configured under the information element (IE) PUCCH configuration (PUCCH-config). Up to 4 PUCCH resource sets can be configured in PUCCH-config. Each PUCCH resource set can contain one or more PUCCH resources. Each PUCCH resource set can carry a different number of uplink control information (UCI) bits. For example, the first PUCCH resource set can carry up to 2 bits of UCI and can contain up to 32 PUCCH resources. The second PUCCH resource set can carry more than 2 and less than or equal to N2 bits of UCI. Similarly, the third PUCCH resource set can carry more than N2 and less than or equal to N3 bits of UCI, and the fourth PUCCH resource set can carry more than N3 and less than or equal to 1706 bits of UCI. Both N2 and N3 can be configured by Radio Resource Control (RRC). PUCCH-config may also configure at least one of hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback timing, PUCCH transmission power parameters, and beam-related information.

[0045] For Channel State Information (CSI) or Scheduling Request (SR) transmission, the base station may configure an associated PUCCH resource identifier (resource ID) for each CSI / SR.

[0046] When the UE supports HARQ-ACK codebook transmission of different priorities, the base station can configure the PUCCH-config corresponding to the HARQ-ACK codebook transmission of different priorities. Specifically, the base station configures a PUCCH configuration list (PUCCH-configurationList), which can include two PUCCH-configs, one for high-priority and one for low-priority UCI transmission.

[0047] 2. Flexible duplex (SBFD)

[0048] When deploying traditional cellular networks, frequency division duplex (FDD) or time division duplex (TDD) can be used, depending on the available spectrum and service characteristics. In FDD, uplink and downlink transmissions occur on different frequencies, preventing interference and allowing simultaneous transmission. In TDD, uplink and downlink transmissions occur on the same frequency, interleaved using time division. Each duplex method has its own advantages and disadvantages.

[0049] To more flexibly utilize limited spectrum resources, dynamically match service needs, improve resource utilization efficiency, and enhance uplink coverage and reduce latency for data transmission, flexible duplexing methods have been proposed. This includes full-duplexing based on non-overlapping sub-bands in the frequency domain, referred to as sub-band full duplex (SBFD).

[0050] 1) Full-duplex on the network side

[0051] From the network's perspective, uplink and downlink transmissions can occur simultaneously within different frequency sub-bands. To prevent interference between uplink and downlink transmissions, a guard band (Guard Band) can be reserved between frequency sub-bands corresponding to different transmission directions (e.g., uplink and downlink sub-bands).

[0052] 2) Half-duplex or full-duplex on the terminal side

[0053] When the terminal side supports half-duplex, only uplink transmission or downlink transmission can be performed at the same time, and both cannot be performed at the same time. It is understandable that in this case, the uplink transmission and downlink transmission on the network side at the same time can only be directed to different terminals.

[0054] When the terminal side supports full-duplex, similar to the network side, at the same time, uplink transmission and downlink transmission can be performed simultaneously in different frequency domain sub-bands.

[0055] Figure 2 illustrates the flexible duplexing scheme described above. Within a subset of downlink symbols, the network semi-statically divides the frequency domain of a single carrier into three subbands: downlink subbands on either side of the carrier and uplink subbands in the middle. This reduces interference with adjacent carriers. In the third time slot, UE1 and UE2 perform uplink transmission and downlink reception, respectively. In Figure 2, D represents a downlink symbol, S represents a flexible symbol, and U represents an uplink symbol.

[0056] 3. SBFD Configuration or Instructions

[0057] In Release 18 (Rel-18) Duplex System Information (SI), SBFD based on full-duplex on the network side and half-duplex on the terminal side was studied. The focus was on semi-static SBFD, which involves only uplink transmission within the uplink subband configured on the network side, and only downlink transmission within the downlink subband configured on the network side. Dynamic SBFD was also studied extensively, including: for semi-static downlink (DL) symbols configured with a UL subband, downlink transmission is allowed outside the DL subband. For example, it is understood that the SBFD configuration of the symbol is disabled, falling back to the original DL symbol; and for semi-static flexible symbols configured with a UL subband, downlink transmission is allowed outside the DL subband, and uplink transmission is allowed outside the UL subband.

[0058] In addition, the signaling methods for implementing Dynamic SBFD are also discussed, including signaling indication methods based on scheduling downlink control information (DCI) / non-scheduling DCI / media access control (MAC) control element (CE).

[0059] In related technologies, when determining PUCCH resources, the terminal determines the corresponding resource set in the corresponding PUCCH-config based on the number of UCI bits, and determines the corresponding resource set based on the PUCCH Resource Indicator (PRI). The terminal then determines to transmit UCI, including HARQ-ACK, within the determined resource set. For SBFD operation, the UE may be configured with SBFD symbols. On these SBFD symbols, the bandwidth part (BWP) may be divided into a UL subband, a guard band, and a DL subband. Uplink transmission can only be performed within the UL subband.

[0060] In view of this, embodiments of the present application provide an uplink transmission method, an uplink transmission configuration method, and an apparatus to solve the problem of how to perform uplink transmission under SBFD configuration.

[0061] To facilitate the description of the following solution, the relevant concepts are first explained:

[0062] Based on the TDD pattern configuration information provided by the network side to the UE (for example, tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated provided for a serving cell of the UE), the following symbol types can be distinguished: downlink symbol (DL symbol), uplink symbol (UL symbol), and flexible symbol.

[0063] When tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is not provided for a certain Serving cell, it can be considered that the type of each Symbol is a Flexible symbol, or the rules corresponding to the Flexible symbol are followed.

[0064] Based on the above TDD pattern configuration information and the SBFD configuration information provided by the network side to the UE, the following Symbol types can be further distinguished: SBFD symbol and non-SBFD symbol.

[0065] The network side can configure certain symbols to perform SBFD operations through SBFD configuration information, that is, configure these symbols as SBFD symbols; a symbol that is not configured (or instructed) to perform SBFD operation can be considered a non-SBFD symbol. For example, some or all symbols within a single cycle determined based on the TDD pattern are configured as SBFD symbols. These symbols configured as SBFD symbols can be some or all types of symbol types distinguished based on the TDD pattern configuration information.

[0066] For a serving cell configured or activated for a UE, the symbol on the serving cell can be further divided into the following three symbol types:

[0067] 1) SBFD symbol for duplex mode 1

[0068] For Duplex mode 1, the network side supports full-duplex SBFD operation, while the UE side only supports half-duplex SBFD operation. That is, within a single SBFD symbol, the UE can only perform uplink transmission or downlink reception, but cannot simultaneously perform uplink transmission and downlink reception based on frequency division multiplexing (FDM).

[0069] 2) SBFD symbol for duplex mode 2

[0070] For Duplex mode 2, the network side supports full-duplex-based SBFD operation, and the UE side supports full-duplex-based SBFD operation, that is, the UE can simultaneously perform FDM-based uplink transmission and downlink reception within a single SBFD symbol.

[0071] It is understandable that a UE supporting full-duplex SBFD operation (ie, supporting Duplex mode 2 or SBFD symbol for duplex mode 2) must also support half-duplex SBFD operation (ie, supporting Duplex mode 1 or SBFD symbol for duplex mode 1).

[0072] 3) Non-SBFD symbol

[0073] A symbol that is not configured (or instructed) to perform an SBFD operation is considered a non-SBFD symbol.

[0074] In the relevant discussions of Rel-18 Duplex SI, it is proposed to distinguish Symbol types based on SBFD configuration information (for example, two Symbol types, SBFD symbol and non-SBFD symbol, or three Symbol types, SBFD symbol for duplex mode 1, SBFD symbol for duplex mode 2, and non-SBFD symbol). The corresponding uplink transmission parameters can be configured (directly) or derived (implicitly based on frequency domain offset (Offset), respective starting reference points, etc.) for different Symbol types to take into account / compensate for frequency domain resources, antenna and RF configurations, interference conditions and limitations corresponding to different Symbol types.

[0075] In the embodiment of the present application, SBFD type and non-SBFD type are mainly considered, and SBFD type may include at least one of SBFD symbol for duplex mode 1 and SBFD symbol for duplex mode 2.

[0076] The uplink transmission method, uplink transmission device, uplink transmission configuration method, and uplink transmission configuration device provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings through some embodiments and their application scenarios.

[0077] FIG3 shows a flow chart of an uplink transmission method provided by an embodiment of the present application. As shown in FIG3 , the uplink transmission method includes the following steps:

[0078] Step 301: The terminal determines a target time domain type corresponding to a first uplink transmission, where the target time domain type includes an SBFD time domain type or a non-SBFD time domain type.

[0079] Step 302: The terminal determines the transmission parameters of the first uplink transmission according to the target time domain type.

[0080] This embodiment of the present application defines two time domain types: an SBFD time domain type (hereinafter referred to as the SBFD type), and a non-SBFD time domain type (hereinafter referred to as the non-SBFD type). For example, SBFD symbols, SBFD time slots, or SBFD sub-time slots all belong to the SBFD time domain type, while uplink symbols, uplink time slots, uplink sub-time slots, downlink symbols, downlink time slots, downlink sub-time slots, flexible symbols, flexible time slots, or flexible sub-time slots all belong to the non-SBFD time domain type.

[0081] The first uplink transmission includes, for example, uplink transmissions such as PUCCH, Sounding Reference Signal (SRS) or PUSCH, which is not limited in the embodiment of the present application.

[0082] The terminal determines the target time domain type corresponding to the first uplink transmission, which can be understood as the terminal determining whether the first uplink transmission is SBFD uplink transmission or non-SBFD uplink transmission, where SBFD uplink transmission represents uplink transmission of SBFD time domain type, and non-SBFD uplink transmission represents uplink transmission of non-SBFD time domain type.

[0083] The terminal determines the transmission parameters of the first uplink transmission according to the target time domain type, which can make the transmission parameters of the first uplink transmission more reasonable and help ensure the communication performance of the terminal. Taking the target time domain type as the SBFD time domain type as an example, since the terminal can perform uplink transmission and downlink reception at the same time in the same time domain unit, the uplink transmission may interfere with the downlink reception. Therefore, when the target time domain type corresponding to the first uplink transmission is the SBFD time domain type, the terminal can use a lower transmission power to perform the first uplink transmission to reduce the interference caused by the first uplink transmission to the downlink reception, thereby ensuring the communication performance of the terminal. When the target time domain type corresponding to the first uplink transmission is the non-SBFD time domain type, the terminal can use a higher transmission power to perform the first uplink transmission to improve the reliability of the first uplink transmission, thereby ensuring the communication performance of the terminal.

[0084] For example, the base station can separately configure PUCCH-config / PUSCH-config / SRS-config for transmission in SBFD time domain resources, and PUCCH-config / PUSCH-config / SRS-config for transmission in non-SBFD time domain resources. SBFD configuration may be at the slot / subslot or symbol level. In an SBFD configuration, the UE needs to determine the time domain type corresponding to the uplink transmission, as well as the transmission resources and transmission parameters for the uplink transmission to ensure the validity of the uplink transmission.

[0085] In an embodiment of the present application, a terminal determines a target time domain type corresponding to a first uplink transmission, where the target time domain type includes an SBFD time domain type or a non-SBFD time domain type; and the terminal determines transmission parameters for the first uplink transmission based on the target time domain type. This enables the terminal to more reasonably determine uplink transmission parameters under an SBFD configuration, thereby enabling the terminal to more reasonably perform uplink transmission under the SBFD configuration, thereby ensuring communication performance of the terminal.

[0086] In some embodiments, the terminal determines the target time domain type corresponding to the first uplink transmission, including at least one of the following:

[0087] The terminal determines the target time domain type according to configuration information or scheduling information;

[0088] The terminal determines the target time domain type according to a time domain unit in which the downlink transmission corresponding to the first uplink transmission is located;

[0089] The terminal determines the target time domain type according to a target time domain unit corresponding to the first uplink transmission.

[0090] That is, the time domain type of uplink transmission may be determined according to configuration information or scheduling information, or may be determined according to a specific time domain unit.

[0091] In the embodiment of the present application, the time domain unit can be understood as a specific time domain position. For example, time slot (slot) i can be regarded as a time domain unit, and the j-th symbol in slot i can also be regarded as a time domain unit.

[0092] The time domain granularities corresponding to different time domain units may be the same or different. For example, the time domain unit corresponding to the downlink transmission of the first uplink transmission and the target time domain unit corresponding to the first uplink transmission may have the same or different time domain unit granularities.

[0093] The target time domain unit corresponding to the first uplink transmission may include one or more time domain units, for example, the time domain unit corresponding to the actual transmission of the first uplink transmission, or the time domain unit corresponding to the nominal transmission of the first uplink transmission, both of which can be understood as the target time domain unit corresponding to the first uplink transmission, and the granularity of the time domain units of the two may be the same or different.

[0094] Exemplarily, the time domain granularity of the target time domain unit may include a symbol, a time slot, or a sub-time slot, etc.

[0095] Exemplarily, the time domain unit where the downlink transmission corresponding to the first uplink transmission is located may include a symbol, a time slot, or a sub-time slot, etc.

[0096] In some embodiments, the terminal determines the target time domain type according to configuration information or scheduling information, including at least one of the following:

[0097] The terminal determines, according to a time domain type associated with first configuration information, the target time domain type, where the first configuration information is used to pre-configure a transmission configuration of M uplink transmissions, where the M uplink transmissions include the first uplink transmission, and M is a positive integer;

[0098] The terminal determines, according to the time domain type associated with second configuration information, the target time domain type, where the second configuration information is used to pre-configure the first uplink transmission;

[0099] The terminal determines, according to a time domain type associated with third configuration information, the target time domain type, where the third configuration information is used to pre-configure a resource set of K uplink transmissions, where the K uplink transmissions include the first uplink transmission, and K is a positive integer;

[0100] Determining, by the terminal, the target time domain type according to fourth configuration information, where the fourth configuration information is used to pre-configure the time domain type of the first uplink transmission;

[0101] The terminal determines the target time domain type according to first scheduling information, where the first scheduling information is used to dynamically schedule the first uplink transmission;

[0102] The terminal determines the target time domain type according to second scheduling information, where the second scheduling information is used to activate the first uplink transmission.

[0103] Exemplarily, the first uplink transmission is PUCCH, and the first configuration information is PUCCH-config; the first uplink transmission is PUSCH, and the first configuration information is the PUSCH-config configuration list; the first uplink transmission is configured grant PUSCH (Configured Grant PUSCH, CG-PUSCH) or SRS, and the first configuration information is the CG-PUSCH or SRS configuration list.

[0104] Exemplarily, the second configuration information is configuration information used to configure resources for each PUCCH / SRS / CG-PUSCH (per PUCCH / SRS / CG-PUSCH resource configured).

[0105] Exemplarily, the first uplink transmission is PUCCH, and the third configuration information is PUCCH resource set / List; the first uplink transmission is SRS or CG-PUSCH, and the third configuration information is a configuration list.

[0106] The fourth configuration information can be understood as configuration information used to configure the time domain type, which can be existing configuration information or new configuration information.

[0107] The first scheduling information can be understood as dynamic scheduling information. For example, for dynamically scheduled uplink transmission, such as PUCCH carrying HARQ-ACK, dynamic grant PUCSH (Dynamic Grant PUCSH, DG-PUCSH) or type 2CG-PUSCH, the first scheduling information includes scheduling DCI or activation DCI.

[0108] The second scheduling information can be understood as semi-persistent scheduling information, semi-static configuration information or high-level signaling. For example, for semi-statically configured uplink transmission, such as SPS HARQ-ACK / CSI / SR / SRS / CG-PUSCH (especially type1CG-PUSCH), the transmission time domain type corresponding to the uplink transmission is configured through high-level signaling (such as per CSI report / SR / SRS / CG-PUSCH configuration).

[0109] In some embodiments, the terminal determines the target time domain type according to the first scheduling information, including at least one of the following:

[0110] Determining, by the terminal, the target time domain type according to the time domain type information indicated by the first scheduling information;

[0111] Determining, by the terminal, the target time domain type according to the time domain type corresponding to the time domain unit indicated by the first scheduling information;

[0112] Determining, by the terminal, the target time domain type according to the time domain type associated with the codebook indicated by the first scheduling information;

[0113] The terminal determines the target time domain type according to the time domain type associated with the transmission configuration indicated by the first scheduling information.

[0114] In some embodiments, the time domain unit in which the downlink transmission corresponding to the first uplink transmission is located includes at least one of the following:

[0115] a downlink time domain symbol corresponding to an end symbol of the downlink transmission corresponding to the first uplink transmission;

[0116] an uplink time domain symbol corresponding to an end symbol of the downlink transmission corresponding to the first uplink transmission;

[0117] a downlink time domain unit corresponding to an end position of the downlink transmission corresponding to the first uplink transmission;

[0118] The uplink time domain unit corresponds to the downlink time domain unit corresponding to the end position of the downlink transmission corresponding to the first uplink transmission.

[0119] Exemplarily, for the uplink transmission of HARQ-ACK PUCCH, the time domain type corresponding to the symbol where the end position of the last DL transmission corresponding to HARQ-ACK (such as its corresponding PDSCH or PDCCH) is located can be used, wherein the time domain type corresponding to the symbol where the end position of the last DL transmission is located can be the time domain type of the DL symbol corresponding to the end position of the DL transmission, or the time domain type of the UL symbol corresponding to the end position of the DL transmission. If the DL transmission and the UL transmission correspond to different service cells or different subcarrier intervals, and the time domain type of the UL symbol corresponding to the end position of the DL transmission is different, that is, according to the end position of the DL transmission, it is mapped to the service cell corresponding to the UL transmission or the UL symbol corresponding to the subcarrier interval. For example, the first uplink transmission corresponds to service cell A, and the corresponding downlink transmission corresponds to service cell B. The time domain unit where the downlink transmission corresponding to the first uplink transmission is located includes: the uplink time domain unit on service cell A corresponding to the end symbol of the downlink transmission on service cell B.

[0120] In some embodiments, the terminal determines the target time domain type according to the target time domain unit corresponding to the first uplink transmission, including at least one of the following:

[0121] In a case where the target time domain unit is configured or indicated as an SBFD time domain unit, the terminal determines that the target time domain type is the SBFD time domain type;

[0122] In a case where the target time domain unit is configured or indicated as a non-SBFD time domain unit, the terminal determines that the target time domain type is the non-SBFD time domain type;

[0123] In a case where all symbols of the target time domain unit are SBFD symbols, the terminal determines that the target time domain type is the SBFD time domain type;

[0124] In a case where all symbols of the target time domain unit are non-SBFD symbols, the terminal determines that the target time domain type is the non-SBFD time domain type;

[0125] In a case where the target time domain unit includes both SBFD symbols and non-SBFD symbols, the terminal determines the target time domain type according to a target mode;

[0126] The target method includes at least one of the following:

[0127] Determining the target time domain type according to the number of SBFD symbols and the number of non-SBFD symbols included in the target time domain unit;

[0128] Determining the target time domain type according to the time domain type of the symbol located at a predefined position in the target time domain unit;

[0129] The target time domain type is determined according to a predefined or default time domain type of the target time domain unit.

[0130] Exemplarily, if the target time domain unit is semi-statically configured as (or configured by dynamic signaling as) an SBFD time domain unit, or the target time domain unit only includes SBFD symbols, then the target time domain unit is of SBFD type.

[0131] That is, the target time domain unit is configured as an SBFD time domain unit. It can be understood that the target time domain unit is configured as an SBFD time domain unit by higher layer signaling and / or dynamic signaling. Preferably, the target time domain unit is configured as an SBFD time domain unit by higher layer signaling.

[0132] Exemplarily, if the target time domain unit is not semi-statically configured as a non-SBFD time domain unit (or configured by dynamic signaling), or the target time domain unit only contains non-SBFD symbols, then the target time domain unit is of non-SBFD type.

[0133] Exemplarily, if the target time domain unit includes both an SBFD symbol and a non-SBFD symbol, the time domain type of the target time domain unit is determined according to the following method:

[0134] The number of SBFD symbols and non-SBFD symbols in the time domain unit is determined according to the time domain type with a larger number of symbols;

[0135] Determined according to a predefined position within the time domain unit, such as the time domain type corresponding to the first symbol or the last symbol;

[0136] Predefined / default as SBFD or non-SBFD type;

[0137] It is determined according to the time domain type of the symbol where the uplink transmission in the time domain unit is located.

[0138] In some embodiments, the target time domain unit includes at least one of the following:

[0139] a first time domain unit, where the first time domain unit is a time domain unit corresponding to actual transmission of the first uplink transmission;

[0140] a second time domain unit, where the second time domain unit is a time domain unit corresponding to the nominal transmission of the first uplink transmission;

[0141] The time domain granularities of the first time domain unit and the second time domain unit are the same or different.

[0142] In some embodiments, the first time domain unit comprises a symbol, a time slot, or a sub-time slot.

[0143] In some embodiments, the second time domain unit comprises a time slot or a sub-time slot.

[0144] In some embodiments, the second time domain unit includes at least one of the following:

[0145] A time domain unit determined by the terminal according to the configured period and offset of the first uplink transmission;

[0146] The terminal is instructed to use a time domain unit for transmitting a hybrid automatic repeat request answering HARQ-ACK.

[0147] Exemplarily, the second time domain unit includes the following two cases:

[0148] For HARQ-ACK PUCCH, it is the time domain unit where the UE is instructed to transmit HARQ-ACK, for example, the time domain unit (such as time slot or sub-time slot) used to feedback HARQ-ACK determined according to the timing indication from PDSCH to HARQ-ACK feedback;

[0149] For SR / CSI / SRS / CG-PUSCH, the time domain unit determined by the UE based on the SR / CSI / SRS / CG-PUSCH period and offset within the period (as well as the starting symbol position and subslot configuration). For example: the transmission slot determined based on the SR / CSI / SRS / CG-PUSCH period and offset within the period, or the transmission slot and subslot configuration determined based on the SR / CSI / SRS period and offset within the period, or the subslot determined based on the starting symbol of the PUCCH transmitting SR / CSI.

[0150] In some embodiments, the terminal determines the target time domain type according to the time domain unit in which the downlink transmission corresponding to the first uplink transmission is located, including at least one of the following:

[0151] When the time domain unit where the downlink transmission corresponding to the first uplink transmission is located is configured or indicated as an SBFD time domain unit, the terminal determines that the target time domain type is the SBFD time domain type;

[0152] When the time domain unit where the downlink transmission corresponding to the first uplink transmission is located is configured or indicated as a non-SBFD time domain unit, the terminal determines that the target time domain type is the non-SBFD time domain type;

[0153] When all symbols of a time domain unit in which a downlink transmission corresponding to the first uplink transmission is located are SBFD symbols, the terminal determines that the target time domain type is the SBFD time domain type;

[0154] When all symbols of a time domain unit in which a downlink transmission corresponding to the first uplink transmission is located are non-SBFD symbols, the terminal determines that the target time domain type is the non-SBFD time domain type;

[0155] When the time domain unit where the downlink transmission corresponding to the first uplink transmission is located includes both SBFD symbols and non-SBFD symbols, the terminal determines the target time domain type according to a target mode;

[0156] The target method includes at least one of the following:

[0157] Determining the target time domain type according to the number of SBFD symbols and the number of non-SBFD symbols included in the time domain unit where the downlink transmission corresponding to the first uplink transmission is located;

[0158] Determining the target time domain type according to the time domain type of a symbol located at a predefined position in the time domain unit where the downlink transmission corresponding to the first uplink transmission is located;

[0159] The target time domain type is determined according to a predefined or default time domain type of a time domain unit where the downlink transmission corresponding to the first uplink transmission is located.

[0160] In some embodiments, the terminal determines, according to the target time domain type, a transmission parameter of the first uplink transmission, including:

[0161] The terminal receives a first message from a network-side device, where the first message includes a first transmission configuration item and a second transmission configuration item, where the first transmission configuration item is mapped to the SBFD time domain type, and the second transmission configuration item is mapped to the non-SBFD time domain type.

[0162] Determining, by the terminal, a target transmission configuration item from the first transmission configuration item and the second transmission configuration item according to the target time domain type;

[0163] The terminal determines the transmission parameter associated with the target transmission configuration item as the transmission parameter of the first uplink transmission.

[0164] The first transmission configuration item may include one or more transmission configurations, and the first transmission configuration item may also include one or more transmission configurations. When multiple transmission configurations are included, the multiple transmission configurations may be used for uplink transmissions of different priorities.

[0165] Exemplarily, for PUCCH transmission, the first transmission configuration item is PUCCH configuration list (configList) 1, and the second transmission configuration item is PUCCH-configList2. Specifically, the base station configures PUCCH-configList1 for SBFD symbol transmission and PUCCH-configList2 for non-SBFD symbol transmission. Among them, each PUCCH-configList can contain one or more PUCCH-configs, for example, for high and low priority UCI transmission respectively. Each PUCCH-config contains PUCCH resources, PUCCH transmission power control parameters or spatial information parameters (such as beam parameters), etc.

[0166] In this implementation, by configuring different transmission configuration items for different time domain types, the terminal can directly select the corresponding transmission configuration item according to the determined time domain type, thereby efficiently determining appropriate transmission parameters, which is conducive to ensuring the communication performance of the terminal.

[0167] In some embodiments, the transmission parameters include at least one of transmission configuration, feedback timing set, time domain resource allocation (TDRA), offset value (beta_offset), transmission code rate, power control parameters and beam parameters.

[0168] Among them, TDRA and offset value are PUSCH transmission parameters. TDRA is used for time domain resource allocation of PUSCH. TDRA includes the time slot offset K2 from PDCCH to PUSCH starting time slot, the starting symbol and number of symbols transmitted by PUSCH in the time slot, and other parameters. The offset value is a parameter used to control the number of REs occupied when UCI is transmitted on PUSCH.

[0169] In some embodiments, the method further comprises:

[0170] The terminal determines whether the first uplink transmission is valid, including at least one of the following:

[0171] In a case where the time domain unit of the first uplink transmission includes an SBFD symbol and a non-SBFD symbol, the terminal determines that the first uplink transmission is invalid;

[0172] In a case where the frequency domain resources of the first uplink transmission exceed the range of the SBFD uplink subband, the terminal determines that the first uplink transmission is invalid.

[0173] It can be understood that when the time domain unit of the first uplink transmission overlaps with both SBFD symbols and non-SBFD symbols, the terminal cannot perform the first uplink transmission.

[0174] Exemplarily, the UE can determine whether a certain uplink transmission is valid (or whether it can be transmitted) based on the SBFD configuration information from the network-side device. For example, if the uplink transmission is configured / indicated to be transmitted in the SBFD time domain, its transmission resources overlap with non-SBFD symbols, or its frequency domain resources exceed the frequency domain resource range available for UL (for example, for PUSCH transmission, the frequency domain resources allocated to PUSCH exceed the UL subband resource range configured by SBFD), then the UE determines that the uplink transmission is invalid.

[0175] It should be noted that, in the embodiments of the present application, the method of determining whether a certain uplink transmission is valid according to the SBFD configuration information can adopt the method of the above example.

[0176] It should be noted that the SBFD configuration information can be obtained by the UE receiving a second message from the network side device. For example, the network side device sends a second message to the terminal to configure at least one time domain unit for the terminal. If the time domain unit includes at least one SBFD time domain unit, the second message can be understood as SBFD configuration information.

[0177] In some embodiments, the method further comprises:

[0178] When determining that the first uplink transmission is invalid, the terminal performs a first operation, where the first operation includes at least one of the following:

[0179] postponing the first uplink transmission;

[0180] The first uplink transmission is canceled.

[0181] Postponing the first uplink transmission. This can be understood as the terminal selecting a resource location that meets the validity condition for the first uplink transmission to ensure the validity of the first uplink transmission.

[0182] Exemplarily, when selecting a time domain unit for the first uplink transmission, the terminal does not select a time domain unit including two types of symbols (ie, an SBFD symbol and a non-SBFD symbol).

[0183] Exemplarily, when selecting frequency domain resources for the first uplink transmission, the terminal does not select frequency domain resources that are beyond the range of the SBFD uplink subband.

[0184] During uplink transmission, the UE can ensure the validity of the uplink transmission by determining whether the uplink transmission is valid and transmitting the valid uplink transmission, thereby facilitating ensuring the communication performance of the terminal.

[0185] In some embodiments, the method further comprises:

[0186] In a case where the time domain type of the third time domain unit of the first uplink transmission does not match the target time domain type, the terminal performs a second operation, where the second operation includes at least one of the following:

[0187] postponing the first uplink transmission;

[0188] canceling the first uplink transmission;

[0189] Transmitting the first uplink transmission according to the transmission parameters corresponding to the time domain type of the third time domain unit;

[0190] The third time domain unit is a time domain unit corresponding to the actual transmission of the first uplink transmission.

[0191] Postponing the first uplink transmission may be understood as the terminal selecting a resource location that meets a validity condition for the first uplink transmission, so as to ensure the validity of the first uplink transmission.

[0192] Exemplarily, when selecting a time domain unit for the first uplink transmission, the terminal does not select (can be understood as skipping) a time domain unit whose time domain type does not match the target time domain type.

[0193] During uplink transmission, the UE compares the time domain type of the actual transmitted time domain unit with the target time domain type to see if it matches, and handles the mismatch by performing the second operation, thereby ensuring the validity of the uplink transmission and thus facilitating communication performance of the terminal.

[0194] In some embodiments, the method further comprises:

[0195] In a case where the first uplink transmission channel overlaps with the second uplink transmission channel, the terminal performs a third operation, where the third operation includes at least one of the following:

[0196] postponing the first uplink transmission;

[0197] canceling the first uplink transmission;

[0198] The first uplink transmission and the second uplink transmission are multiplexed for transmission.

[0199] It should be noted that the third operation may also include canceling the second uplink transmission.

[0200] The first uplink transmission and the second uplink transmission may be, for example, PUCCH and PUCCH, PUCCH and PUSCH, or PUSCH and PUSCH.

[0201] The above-mentioned third operation can be understood as overlapping processing or intra-UE overlapping processing. The overlapping processing methods include, for example, multiplexing (i.e., multiplexing the content carried by different channels on one channel for transmission), cancellation (i.e., canceling part of the channel transmission, cancellation can be understood as not transmitting, discarding) or priority processing (prioritization) (i.e., canceling part of the channel transmission according to priority, cancellation can be understood as not transmitting, discarding), etc.

[0202] In some embodiments, when the first uplink transmission channel overlaps with the second uplink transmission channel, the terminal performing a third operation includes:

[0203] In a case where a channel of the first uplink transmission overlaps with a channel of the second uplink transmission, the terminal determines whether the first uplink transmission and the second uplink transmission are valid according to SBFD configuration information from a network-side device;

[0204] The terminal performs the third operation when determining that the first uplink transmission and the second uplink transmission are valid.

[0205] In this implementation, when a first uplink transmission channel overlaps with a second uplink transmission channel, the terminal may first perform a validity check. If the channel is invalid, the UE may not perform overlap processing between uplink transmissions, or in other words, the invalid uplink transmission channel does not participate in overlap processing. If the channel is valid, the UE then performs overlap processing between uplink transmissions, or in other words, the aforementioned channel participates in overlap processing. This approach can avoid unnecessary discarding.

[0206] In some embodiments, the third operation includes multiplexing the first uplink transmission and the second uplink transmission;

[0207] After the terminal multiplexes and transmits the first uplink transmission and the second uplink transmission, the method further includes:

[0208] The terminal determines, according to the SBFD configuration information, whether a channel multiplexed by the first uplink transmission and the second uplink transmission is valid.

[0209] In this embodiment, when the channel of the first uplink transmission overlaps with the channel of the second uplink transmission, the terminal can first perform overlap processing between the uplink transmissions and then perform validity check after the overlap processing. This method can simplify the UE processing and avoid the UE from performing multiple validity checks.

[0210] In some embodiments, the time domain type of one of the first uplink transmission and the second uplink transmission is the SBFD time domain type, and the time domain type of the other is the non-SBFD time domain type;

[0211] The method further comprises:

[0212] The terminal determines a transmission parameter or a transmission resource of the multiplexing transmission.

[0213] In some embodiments, the terminal determines the transmission parameters or transmission resources of the multiplexing transmission, including at least one of the following:

[0214] The terminal determines, as the transmission parameters of the multiplexed transmission, the transmission parameters corresponding to the uplink transmission whose time domain type is the SBFD time domain type;

[0215] The terminal determines, as the transmission parameters of the multiplexed transmission, the transmission parameters corresponding to the uplink transmission whose time domain type is the non-SBFD time domain type;

[0216] The terminal determines the transmission parameters corresponding to the uplink transmission with a higher priority as the transmission parameters of the multiplexed transmission;

[0217] In a case where the overlapping channel includes a first HARQ-ACK PUCCH, the terminal determines, according to a transmission configuration item corresponding to the first HARQ-ACK PUCCH, a transmission parameter or transmission resource of the multiplexed transmission, where the first HARQ-ACK PUCCH is a HARQ-ACK PUCCH with corresponding DCI;

[0218] In a case where the overlapping channel includes a CSIPUCCH and a second HARQ-ACK PUCCH, the terminal determines the transmission parameters or transmission resources of the multiplexed transmission according to the transmission configuration item corresponding to the CSIPUCCH, and the second HARQ-ACK PUCCH is a HARQ-ACK PUCCH without corresponding DCI;

[0219] In a case where the overlapping channels include UCI and PUSCH, the terminal determines the transmission parameters or transmission resources of the multiplexing transmission according to the parameters corresponding to the PUSCH.

[0220] Exemplarily, the HARQ-ACK corresponding to the DCI may be understood as the HARQ-ACK corresponding to the DG-PDSCH or PDCCH;

[0221] Exemplarily, the HARQ-ACK without corresponding DCI can be understood as the HARQ-ACK corresponding to the SPS PDSCH.

[0222] For example, when the SBFD PUCCH and the non-SBFD PUCCH overlap, the UE may determine the PUCCH-config corresponding to the multiplexed PUCCH according to a predefined rule, for example:

[0223] The multiplexed PUCCH is determined from the PUCCH-config corresponding to the SBFD; or,

[0224] The multiplexed PUCCH is transmitted according to the transmission parameters corresponding to SBFD; or,

[0225] The multiplexed PUCCH is determined from the PUCCH-config corresponding to non-SBFD;

[0226] The multiplexed PUCCH is transmitted according to the transmission parameters corresponding to non-SBFD.

[0227] Alternatively, the PUCCH-config transmission parameter corresponding to the multiplexed PUCCH may be transmitted according to the multiplexing rules in the related art, for example:

[0228] If the overlapping channel contains HARQ-ACK corresponding to DCI, the multiplexed PUCCH resource is determined from the PUCCH-config corresponding to the HARQ-ACK;

[0229] If the overlapping channels are CSIPUCCH and SPS HARQ-ACK, the UE multiplexes the HARQ-ACK on the CSI resources and transmits the PUCCH using the PUCCH-config corresponding to the CSIPUCCH;

[0230] If the overlapping channels contain HARQ-ACKs corresponding to different priority levels, the multiplexed PUCCH resources are determined from the PUCCH-config corresponding to the high-priority HARQ-ACK (HP HARQ-ACK);

[0231] If UCI is multiplexed into PUSCH transmission, PUSCH and UCI are transmitted according to the parameters corresponding to PUSCH; for example, in non-SBFD PUSCH transmission, PUSCH is transmitted according to the parameters corresponding to the PUSCH-config corresponding to non-SBFD.

[0232] During the multiplexing process of uplink transmission, the UE can ensure the validity of uplink transmission by determining transmission parameters or transmission resources of the multiplexed transmission, thereby facilitating the communication performance of the terminal.

[0233] In order to better understand the technical solution of the present application, specific embodiments are provided below to exemplify the uplink transmission solution of the present application.

[0234] Example 1

[0235] 1. UE determines the time domain type of uplink transmission

[0236] The UE determines the time domain type of an uplink transmission, such as a PUCCH or other UL transmission (e.g., a physical uplink shared channel (PUSCH), a sounding reference signal (SRS), etc.) according to the following method. That is, the UE determines whether the uplink transmission is an SBFD transmission (i.e., the time domain type of the uplink transmission is an SBFD type) or a non-SBFD transmission (i.e., the time domain type of the uplink transmission is a non-SBFD type):

[0237] Here, the time domain unit corresponding to the SBFD type may include, for example, an SBFD symbol / time slot / sub-time slot.

[0238] Method 1: Determine the time domain type for uplink transmission based on pre-configured information, for example:

[0239] Method 1-1: For PUCCH, the time domain type of PUCCH transmission is determined based on the PUCCH-config / resourceList or resource set where the PUCCH resource is located. For example, the base station configures the PUCCH-config / resourceList or resource set for the UE to transmit in the SBFD time domain or the non-SBFD time domain, respectively. The UE determines the time domain type of its transmission based on the PUCCH-config / resourceList or resource set where the PUCCH is located.

[0240] For SRS or configured grant PUSCH (Configured Grant PUSCH, CG-PUSCH), the time domain type of its transmission is determined according to the configuration list in which it is located.

[0241] Method 1-2: Determine the time domain type of each uplink transmission based on the pre-configured time domain type corresponding to each uplink transmission resource. For example, the base station configures the time domain type for each uplink transmission resource (eg, per PUCCH / SRS / CG-PUSCH resource configured).

[0242] Method 1-3: Determine the time domain type of each uplink transmission according to the pre-configured information corresponding to the information or signal carried by each uplink resource.

[0243] For the PUCCH carrying HARQ-ACK, according to the PUCCH-config / resourceList or resource set where the HARQ-ACK codebook or PUCCH resource is located, for example, the scheduling DCI or RRC configuration HARQ-ACK codebook or PUCCH-config / resourceList or resource set information (such as an index).

[0244] For CSI / SR / SRS / CG-PUSCH, the higher layer configures the corresponding transmission time domain type (such as per CSI / SR / SRS / CG-PUSCH configuration). For example, for CG-PUSCH type-2, the UE can determine the corresponding time domain type based on the indication of activating DCI. For example, if power control parameters or spatial relationship parameters (such as SRS resource indicator (SRS resource indicator, SRI) or quasi co-location (Quasi co-location, QCL) parameters) are provided in the DCI or RRC configuration, and the SBFD type and non-SBFD type correspond to different power control parameters or spatial relationship parameters, respectively, the time domain type of the uplink transmission configured by the DCI or RRC can be determined by indicating the corresponding power control parameters or spatial relationship parameters.

[0245] Method 2: Determine the time domain type of uplink transmission according to predefined rules, for example:

[0246] Method 2-1: Determine the time domain type of the uplink transmission based on the time domain type of the time domain unit in which the nominal transmission (if an uplink transmission is contained in multiple locations, such as repetition, one transport block (TB) is transmitted on multiple PUSCHs (one TB over multiple PUSCHs) or multi-PUSCH scheduling) is located. Specifically:

[0247] For HARQ-ACK / DG-PUSCH / A-SRS, the time domain type for uplink transmission is the time domain type corresponding to the time unit in which the UE is instructed to transmit HARQ-ACK / PUSCH / SRS. As shown in Figure 4, PDSCH1 and PDSCH2 are instructed to feedback HARQ-ACK in time slots n+5 and n+7, respectively. Based on the SBFD configuration, time slot n+5 is an SBFD slot and time slot n+7 is a non-SBFD slot. The UE then determines the time domain types of PUCCH1 and PUCCH2 to be SBFD and non-SBFD, respectively.

[0248] For SR / CSI / CG-PUSCH / P-SRS / SP-SRS, the time domain type of uplink transmission is the time domain type corresponding to the time unit determined by the UE based on the SR / CSI / CG-PUSCH / SRS period and the offset within the period (as well as the starting symbol position and sub-slot configuration). As shown in Figure 5, the UE determines the time slots for CSI / SR transmission in period 1 and period 2 based on the CSI / SR period and offset, where in period 1, the time slot is configured as an SBFD time slot, and in period 2, the time slot is configured as a non-SBFD time slot. The UE then determines the time domain types of PUCCH1 and PUCCH2 as SBFD and non-SBFD, respectively.

[0249] Method 2-2: Determine the time domain type of the uplink transmission based on the time domain type of the time domain unit where the actual transmission (if an uplink transmission is contained in multiple locations, such as repetition, one TB over multiple PUSCHs) or multi-PUSCH scheduling, it can be the first transmission / repetition).

[0250] It is understandable that an uplink transmission is originally scheduled / configured for transmission in a certain time unit, but due to some reasons (for example, the time unit is DL, or the uplink transmission is cancelled by an uplink transmission with a higher priority), the uplink transmission cannot be transmitted. According to some predefined rules, the uplink transmission is postponed to another time unit for transmission. The other transmission unit is the time domain unit where the actual transmission occurs.

[0251] For example, for PUCCH, the time domain unit of actual transmission is the time slot for PUCCH transmission determined by the UE according to the defined rules. Alternatively, for PUSCH, the time unit of actual transmission is the time unit corresponding to the actual transmission. Exemplarily, the UE determines the time domain unit of actual transmission according to the following method:

[0252] Starting from time unit A, satisfy:

[0253] The first symbol corresponding to the PUCCH / PUSCH / SRS resource (e.g., provided by startingSymbolIndex) is a UL symbol, a flexible symbol, or a SBFD symbol that is not a synchronization signal (SS) / physical broadcast channel (PBCH) symbol;

[0254] Starting from the first symbol corresponding to the PUCCH / PUSCH / SRS resource, a number of consecutive X UL symbols, flexible symbols, or SBFD symbols that are not SS / PBCH symbols, where X is greater than or equal to the number of symbols corresponding to the PUCCH / PUSCH / SRS resource (for example, provided by nrofsymbols or TDRA).

[0255] Among them, time unit A includes the following situations:

[0256] Case 1: For HARQ-ACK / DG-PUSCH / A-SRS, time unit A is the time unit in which the UE is instructed to feedback HARQ-ACK (e.g., determined according to the timing of PDSCH to HARQ-ACK feedback) or transmit PUSCH / SRS;

[0257] Case 2: For SR / CSI / CG-PUSCH / P-SRS / SP-SRS, time unit A is the time unit for transmitting SR / CSI / CG-PUSCH / SRS determined by the UE based on the period configured for SR / CSI / CG-PUSCH / P-SRS / SP-SRS and the offset within the period. Time unit A can be slot A or sub-slot A. If it is sub-slot A, for SR / CSI, the UE also needs to determine sub-slot A based on the PUCCH start symbol position and sub-slot length configuration.

[0258] In this embodiment, the time unit can be replaced by the time domain unit, and the two have the same meaning.

[0259] In this embodiment, the time domain unit may be, for example, a time slot / sub-time slot.

[0260] For method 2-2, since the UE needs to determine the time domain type based on the time slot / sub-time slot in which the uplink transmission is located or the starting symbol and symbol position of the uplink transmission, this method is applicable to situations where the UE does not need to determine the time slot / sub-time slot or the starting symbol and symbol position of the uplink transmission according to the time domain type, for example: for SBFD type and non-SBFD type uplink transmission, the timing feedback timing set and time domain resource configuration of the PDSCH to HARQ-ACK feedback are common or the same, or for SBFD type and non-SBFD type uplink transmission, the time domain position corresponding to the same PRI / resource ID is the same, or the SBFD configuration mode is slot-level.

[0261] For a certain time domain unit (i.e., time unit), the UE may determine its time domain type using at least one of the following methods:

[0262] If the time domain unit is configured as an SBFD time domain unit, the time domain type of the time domain unit is the SBFD type;

[0263] If the time domain unit only contains SBFD symbols, the time domain type of the time domain unit is SBFD type;

[0264] If the time domain unit is not configured as an SBFD time domain unit, the time domain type of the time domain unit is non-SBFD type;

[0265] If the time domain unit contains only non-SBFD symbols, the time domain type of the time domain unit is a non-SBFD type.

[0266] When a UE is configured with SBFD, and the SBFD configuration is symbol-level, a time slot / subslot may contain both SBFD symbols and non-SBFD symbols. In other words, a time domain unit contains both SBFD symbols and non-SBFD symbols. In this case, the UE can determine the time domain type of the time domain unit according to at least one of the following methods:

[0267] Determined according to the number of SBFD symbols and the number of non-SBFD symbols in the time domain unit; specifically, if the number of SBFD symbols in the time domain unit is greater than the number of non-SBFD symbols, the time domain type of the time domain unit is the SBFD type; if the number of non-SBFD symbols in the time domain unit is greater than the number of SBFD symbols, the time domain type of the time domain unit is the non-SBFD type;

[0268] Determined according to the type of the symbol at the predefined position within the time domain unit; specifically, the symbol at the predefined position may be the first symbol or the last symbol; for example, if the first symbol in the time domain unit is an SBFD symbol, the time domain type of the time domain unit is an SBFD type, otherwise it is a non-SBFD type;

[0269] Determined by the time domain type corresponding to the symbol where the last DL transmission corresponding to the HARQ-ACK ends. Here, the symbol where the last DL transmission ends can be the DL symbol corresponding to the last DL transmission end, or the UL symbol corresponding to the last DL transmission end. The latter is mainly applicable when the DL and UL are on different carriers.

[0270] Determined according to the predefined / default time domain type of the time domain unit; for example, assuming that the time domain unit is predefined / defaulted as an SBFD type, the time domain type of the time domain unit is an SBFD type;

[0271] It is determined according to the symbol type corresponding to the symbol where the uplink transmission in the time domain unit is located; for example, for the PUCCH-config corresponding to SBFD and non-SBFD, the time domain resources (starting symbol and number of symbols) of the PUCCH resources corresponding to the same PRI are the same. The UE can determine the time domain type of the time domain unit according to the symbol type of the symbol where the PUCCH resources are located.

[0272] In this way, the UE determines the time domain type of the time domain unit in which the uplink transmission is actually transmitted, and the UE can use the determined time domain type as the time domain type of the uplink transmission. For simplicity of the following description, uplink transmission can be divided into two categories according to the time domain type: SBFD transmission and non-SBFD transmission.

[0273] It should be noted that the UL / flexible symbol in this embodiment refers to a symbol that is configured as a UL or flexible symbol by semi-static signaling, such as tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated, and is not configured as an SBFD symbol (for example, the symbol is not configured as an SBFD symbol by semi-static signaling). The SBFD symbol in this embodiment refers to an SBFD symbol determined according to high-level signaling or dynamic signaling. For example, the SBFD symbol is an SBFD symbol determined according to high-level signaling.

[0274] 2. UE determines transmission parameters for uplink transmission

[0275] The time domain type of the uplink transmission determined by the UE (e.g., SBFD symbol / time slot / sub-time slot) can be used to further determine the time domain resource location (e.g., the time domain unit in which the transmission is located) and transmission parameters (e.g., transmission configuration, feedback timing set, TDRA, offset value, transmission code rate, power control parameters, or beam parameters, etc.) of the uplink transmission. That is, the UE determines at least one of the time domain resource location and transmission parameters of the uplink transmission based on the determined time domain type of the uplink transmission.

[0276] When a UE is configured with SBFD, the base station can configure different transmission parameters for the UE, such as transmission configuration, feedback timing set, TDRA, offset value, transmission code rate, power control parameters or beam parameters, etc., for the UE to perform SBFD transmission and non-SBFD transmission respectively.

[0277] For dynamically scheduled transmissions, such as HARQ-ACK transmission, the UE can determine the time unit for feedback of HARQ-ACK based on the k1 indication field in its DCI, and determine the corresponding PUCCH-config based on the time domain type of the time unit, and determine the PUCCH resources for transmitting HARQ-ACK and the transmission parameters during PUCCH transmission in the PUCCH-config.

[0278] For semi-statically configured transmissions, such as CSI / SR / CG-PUSCH, the UE may determine its transmission time unit in each cycle based on the information configured by the higher layer, and determine its transmission parameters based on the time domain type of the time unit.

[0279] For example, assume that the UE is configured with PUCCH resources for transmitting UCI information in SBFD symbols and non-SBFD symbols, respectively, and the base station configures PUCCH-configList1 for SBFD symbol transmission and PUCCH-configList2 for non-SBFD symbol transmission. Each PUCCH-configList may contain one or more PUCCH-configs, for example, for high and low priority UCI transmissions, respectively. Each PUCCH-config includes PUCCH resources, PUCCH transmission power control parameters, spatial information parameters, etc. Then, for HARQ-ACK feedback, the UE may determine its PUCCH transmission resources and the transmission parameters corresponding to the transmission resources according to at least one of the following methods:

[0280] DCI indicates the time domain type / codebook type of HARQ-ACK feedback (the codebook type corresponds to the time domain type);

[0281] DCI directly indicates the PUCCH-config / PUCCH-configList used by the UE;

[0282] The DCI indicates the time unit of HARQ-ACK feedback, and the UE determines the corresponding PUCCH-config / PUCCH-configList according to the time domain type of the time unit.

[0283] After the UE determines the PUCCH-config according to the above method, it determines the PUCCH resources corresponding to the HARQ-ACK transmission in the PUCCH-config, and uses the transmission parameters corresponding to the PUCCH-config to transmit the PUCCH (if the PUCCH can be transmitted).

[0284] It can be understood that for dynamically scheduled transmissions, such as HARQ-ACK transmissions, the UE can determine the time domain type corresponding to its PUCCH transmission based on the indication in its DCI, thereby determining the corresponding PUCCH-config, and determining the PUCCH resources for transmitting HARQ-ACK in the PUCCH-config (which may include a PDSCH to HARQ-ACK feedback timing set), as well as the transmission parameters during PUCCH transmission.

[0285] Optionally, the UE does not expect the time domain type corresponding to the PUCCH transmission indicated by the DCI to be mismatched with the time domain type configured by the time domain unit for transmitting the PUCCH determined by the UE.

[0286] For CSI / SR transmission, the UE determines its PUCCH transmission resources and the corresponding transmission parameters according to at least one of the following methods:

[0287] For each CSI / SR, the base station configures its associated PUCCH resource ID. One PUCCH resource ID is uniquely associated with a PUCCH-config. The UE determines the time domain type corresponding to the CSI / SR transmission based on the mapping relationship between the PUCCH-config and the time domain type, and uses the transmission parameters configured in the PUCCH-config, such as the maximum code rate, power control parameters, beam parameters, etc. to transmit the PUCCH.

[0288] The base station configures the associated PUCCH resource ID for each CSI / SR. Each CSI / SR can be associated with two PUCCH resource IDs, one for UE transmission in the SBFD and the other for non-SBFD time domain resources. Within a certain period, the UE determines which PUCCH-config-based transmission resource and / or transmission parameters (such as maximum transmission rate, power control, beam, etc.) to use for PUCCH transmission based on the type of time unit in which the CSI / SR is located.

[0289] It is worth noting that when the transmission type is determined based on the time unit of the HARQ-ACK feedback indicated by the DCI, the UE needs to determine the time unit of the HARQ-ACK feedback based on the feedback timing indication from PDSCH to HARQ-ACK, and the value corresponding to the feedback timing indication can be configured by the timing set in the PUCCH-config, and the time granularity (time slot / sub-time slot) corresponding to the feedback timing can also be determined by the sub-slot configuration in the PUCCH-config. Therefore, this method is applicable to the case where the corresponding PDSCH to HARQ-ACK feedback timing set and timing granularity are the same for SBFD and non-SBFD types. For example, the corresponding DCI format is DCI 0_0, or the SBFD and non-SBFD types share a set / the same PDSCH to HARQ-ACK feedback timing set and timing granularity configuration.

[0290] For PUSCH / SRS transmission, the UE determines its transmission resources and transmission parameters corresponding to the transmission resources according to at least one of the following methods:

[0291] If it is a dynamically scheduled transmission, such as DG-PUSCH / type 2CG-PUSCH / A-SRS, the UE can determine its transmission time domain resource type / corresponding transmission parameters / parameter set (such as PUSCH-config) based on the DCI indication corresponding to PUSCH / SRS;

[0292] If it is a semi-statically configured transmission, such as type 1CG-PUSCH / P-SRS / SP-SRS, the UE can determine the type of time unit corresponding to the PUSCH / SRS transmission in the current period based on the high-level configuration (similar to CSI / SR) or the indication corresponding to the activated DCI, and use the corresponding transmission parameters / parameter set.

[0293] 3. UE determines whether uplink transmission can be transmitted

[0294] If the time domain unit for uplink transmission determined by the UE (assuming that the time domain type of the time domain unit is type A) overlaps with a time domain unit that is not type A (such as type B), the UE may perform at least one of the following operations:

[0295] Postponing the uplink transmission;

[0296] cancel the uplink transmission;

[0297] The uplink transmission is transmitted using the transmission parameters in the configuration corresponding to type B (eg, PUCCH-config).

[0298] For example, for CSI / SR transmission, assuming that its time domain type is determined to be type A according to high-level configuration information, when the resource location of CSI / SR in a certain period overlaps with different types of time domain units, the UE postpones the transmission in that period (such as postponing it to the next available time domain unit), or cancels the transmission in that period, or uses the transmission parameters corresponding to another type to transmit the PUCCH (such as power, beam information and other related parameters).

[0299] For example, for CG-PUSCH / P-SRS / SP-SRS transmission, if in a certain period / transmission timing, the time unit type of the uplink transmission is different from the type it is configured / indicated (for example, for high-level configuration or activation of DCI indication), the UE postpones the transmission within the period, or cancels the transmission within the period, or uses transmission parameters corresponding to another type to transmit the uplink transmission.

[0300] For example, for HARQ-ACK PUCCH, assuming that the UE has determined the time domain type of its transmission (assuming it is type A) and has determined the PUCCH resources in the corresponding PUCCH-config, then the UE can determine whether the PUCCH can be transmitted based on the SBFD configuration information, or whether the PUCCH can be transmitted using the transmission parameters corresponding to the PUCCH-config (for the convenience of the following description, this determination step may be referred to as the first step). If the time domain type corresponding to the PUCCH resource is different from the above-mentioned type A (assuming that the time domain type corresponding to the PUCCH resource is type B), the UE may cancel the PUCCH transmission, or postpone the PUCCH transmission, or transmit the PUCCH according to the transmission parameters corresponding to type B. If the time domain unit of the PUCCH resource overlaps with both the SBFD symbol and the non-SBFD symbol, the UE may cancel the PUCCH transmission, or postpone the PUCCH transmission, or transmit the PUCCH according to the transmission parameters corresponding to the specific type (type A or type B).

[0301] Similarly, for CG-PUSCH transmission, the UE can determine whether a certain CG-PUSCH transmission can be transmitted (for example, the frequency domain resources corresponding to the CG-PUSCH exceed the UL subband range corresponding to the SBFD) based on the SBFD configuration information, or whether a certain CG-PUSCH transmission can overlap with different symbol types, or whether the time domain type of the CG-PUSCH matches the type it is configured / indicated for (for the convenience of subsequent description, this determination step can be referred to as the first step).

[0302] 4. Overlapping Processing of Uplink Transmission

[0303] Optionally, the UE first performs the above first step, and then performs intra-UE multiplexing (eg, overlapping processing of PUCCH and PUCCH, overlapping processing of PUCCH and PUSCH).

[0304] Optionally, the UE performs intra-UE multiplexing first, and then performs the first step.

[0305] Optionally, the UE performs the first step before intra-UE multiplexing, at each step of the multiplexing process, and after multiplexing.

[0306] Method 1: The UE first determines uplink transmission and then performs intra-UE multiplexing. After intra-UE multiplexing is completed, the UE determines whether the multiplexed PUCCH can be transmitted based on the SBFD configuration information.

[0307] Method 2: The UE first determines the time domain type corresponding to the uplink transmission and determines whether the PUCCH can be transmitted based on the SBFD configuration information, and then performs intra-UE multiplexing. After the intra-UE multiplexing is completed, the UE determines whether the PUCCH can be transmitted based on the SBFD configuration information.

[0308] Method 3: The UE first performs intra-UE multiplexing. After the intra-UE multiplexing is completed, the UE determines the time domain type corresponding to the uplink transmission according to the SBFD configuration information and determines whether the PUCCH can be transmitted.

[0309] For example, assuming that the time domain resources of the PUCCH resources corresponding to the SBFD PUCCH and the non-SBFD PUCCH are the same, the UE does not need to determine which set of PUCCH resources the PUCCH belongs to based on the SBFD configuration information before intra-UE multiplexing. After completing intra-UE multiplexing, the UE determines which set of PUCCH resources the PUCCH belongs to based on the SBFD configuration information and determines whether this PUCCH can be transmitted. If the PUCCH and PUSCH overlap, the UE determines the UCI transmission parameters based on the PUSCH configuration after completing PUCCH and PUSCH multiplexing. For example, based on the configured offset value corresponding to SBFD (i.e., beta_offset, a parameter used to control the number of resource elements (RE) occupied by UCI transmission on PUSCH) or the beta_offset corresponding to non-SBFD, it determines whether the PUSCH is transmitted in SBFD symbols or non-SBFD symbols.

[0310] Method 4: The UE first determines whether the PUCCH can be transmitted based on the SBFD configuration information, and then performs intra-UE multiplexing. After intra-UE multiplexing is completed, the UE determines the corresponding uplink transmission type based on the SBFD configuration information and determines whether the PUCCH can be transmitted.

[0311] Optionally, the UE does not wish / expect that two PUCCH resources corresponding to different time domain types (SBFD or non-SBFD) overlap.

[0312] Optionally, two PUCCH resources corresponding to different time domain types (SBFD or non-SBFD) can overlap. When the SBFD PUCCH resources overlap with the non-SBFD PUCCH resources, the UE determines the transmission type of the multiplexed PUCCH (e.g., the PUCCH-config) according to at least one of the following predefined rules:

[0313] The multiplexed PUCCH is determined from the PUCCH-config corresponding to SBFD, or is transmitted according to the transmission parameters corresponding to SBFD;

[0314] The multiplexed PUCCH is determined from the PUCCH-config corresponding to non-SBFD, or is transmitted according to the transmission parameters corresponding to non-SBFD;

[0315] Multiplex according to specific multiplexing rules and transmit according to the transmission parameters of the PUCCH-config corresponding to the multiplexed PUCCH, for example:

[0316] If the overlapping channel contains HARQ-ACK corresponding to DCI, the multiplexed PUCCH resource is determined from the PUCCH-config corresponding to the HARQ-ACK;

[0317] If the overlapping channels are CSIPUCCH and SPS HARQ-ACK, the UE multiplexes the HARQ-ACK on the CSI resources and transmits the PUCCH using the PUCCH-config corresponding to the CSIPUCCH;

[0318] If the overlapping channels contain HARQ-ACKs corresponding to different priority levels, the multiplexed PUCCH resources are determined from the PUCCH-config corresponding to the high-priority HARQ-ACK (ie, HP HARQ-ACK).

[0319] Optionally, the UE does not wish / expect the overlap of two PUCCH resources and PUSCH resources corresponding to different time domain types (SBFD or non-SBFD).

[0320] Optionally, two PUCCH resources and PUSCH resources corresponding to different time domain types (SBFD or non-SBFD) can overlap. When PUCCH resources and PUSCH resources corresponding to different time domain types overlap, if the UCI of the PUCCH is multiplexed into this PUSCH, the UE determines the transmission type (UCI parameter) of the multiplexed PUCCH according to at least one of the following predefined rules:

[0321] PUSCH and UCI are transmitted according to the corresponding PUSCH parameters (corresponding PUSCH-config), where the UCI beta_offset is determined by the uplink transmission type corresponding to the PUSCH;

[0322] PUSCH is transmitted according to the parameters corresponding to PUSCH (corresponding PUSCH-config), and UCI is transmitted according to the uplink transmission type corresponding to PUCCH, where the beta_offset of UCI is determined by the uplink transmission type corresponding to PUCCH;

[0323] If the PUSCH is a non-SBFD PUSCH, the PUSCH is transmitted according to the parameters corresponding to the PUSCH-config corresponding to the non-SBFD.

[0324] It should be noted that in related technologies, after the UE determines the PUCCH / PUSCH transmission according to the base station configuration or scheduling, it will perform intra-UE multiplexing, including overlapping processing between PUCCH and PUCCH, PUSCH and PUCCH. After the multiplexing is completed, the UE can determine whether the multiplexed PUCCH / PUSCH can be transmitted based on the TDD uplink and downlink configuration. For example, if the time domain unit of the multiplexed PUCCH / PUSCH overlaps with the DL symbol configured or indicated by the base station, the PUCCH / PUSCH cannot be transmitted.

[0325] Example 2

[0326] In related technologies, when a UE is configured to transmit multiple CSI PUCCHs in a time slot, the UE determines a maximum of two PUCCHs for transmitting CSI reports according to the following rules, for example:

[0327] If the UE is not configured with a PUCCH resource list for transmitting multiple CSI reports, such as multi-CSI-PUCCH-ResourceList, or the CSIPUCCHs in a time slot do not overlap, the UE can select the PUCCH corresponding to the CSI with the highest priority (such as PUCCH A). If PUCCH A is in short PUCCH format, that is, PUCCH format 2, the UE selects a PUCCH corresponding to the CSI with the highest priority from the remaining CSIPUCCHs that do not overlap with PUCCH A; if PUCCH A is in long PUCCH format, the UE selects a PUCCH corresponding to the CSI with the highest priority from the CSIPUCCHs that do not overlap with PUCCH A and whose corresponding PUCCH format is PUCCH format 2.

[0328] If the UE is configured with a PUCCH resource list multi-CSI-PUCCH-ResourceList for transmitting multiple CSI reports, and there are CSI PUCCHs with time domain overlap in a time slot, the UE multiplexes all CSI reports in the time slot on a PUCCH resource configured in a multi-CSI-PUCCH-ResourceList (if the transmission code rate corresponding to the PUCCH is exceeded after multiplexing, some CSI reports may be discarded).

[0329] When the UE is configured with SBFD time units, for multiple CSIPUCCHs in a time slot, some CSIPUCCHs may not be transmitted due to the SBFD configuration. The UE can first determine whether each CSIPUCCH can be transmitted based on the SBFD configuration, and then determine the CSI PUCCH to be transmitted among the CSIPUCCHs that can be transmitted according to the above rules.

[0330] In addition, in related art, when uplink channels of different priorities overlap, if the UE is not enabled for multiplexing between different priorities, the UE will cancel the low-priority channel and transmit the high-priority channel.

[0331] When the UE is configured with SBFD time units, a high-priority channel may not be transmitted due to the SBFD configuration. Therefore, the UE can first determine whether the high-priority channel can be transmitted based on the SBFD configuration. If the channel can be transmitted, the UE can cancel the overlapping low-priority channel. If the high-priority channel cannot be transmitted due to the SBFD configuration, the UE does not cancel the overlapping low-priority channel (that is, when processing overlapping channels, the channel that cannot be transmitted due to the SBFD configuration is not considered).

[0332] In summary, the embodiments of the present application enable the terminal to more reasonably determine uplink transmission parameters under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink transmission under the SBFD configuration, thereby ensuring the communication performance of the terminal.

[0333] The uplink transmission method provided in the embodiment of the present application may be performed by an uplink transmission device. In the embodiment of the present application, the uplink transmission device provided in the embodiment of the present application is described by taking the uplink transmission device performing the uplink transmission method as an example.

[0334] 6 , an embodiment of the present application further provides an uplink transmission device that can be applied to a terminal. As shown in FIG6 , the uplink transmission device 600 includes:

[0335] The first processing module 601 is configured to determine a target time domain type corresponding to a first uplink transmission, where the target time domain type includes a sub-band full-duplex (SBFD) time domain type or a non-sub-band full-duplex (non-SBFD) time domain type.

[0336] The second processing module 602 is configured to determine transmission parameters of the first uplink transmission according to the target time domain type.

[0337] Optionally, the first processing module is specifically configured to perform at least one of the following:

[0338] Determining the target time domain type according to the configuration information or the scheduling information;

[0339] Determining the target time domain type according to a time domain unit where the downlink transmission corresponding to the first uplink transmission is located;

[0340] The target time domain type is determined according to a target time domain unit corresponding to the first uplink transmission.

[0341] Optionally, the first processing module is specifically configured to perform at least one of the following:

[0342] Determining the target time domain type according to a time domain type associated with first configuration information, where the first configuration information is used to pre-configure a transmission configuration of M uplink transmissions, where the M uplink transmissions include the first uplink transmission, and M is a positive integer;

[0343] Determining the target time domain type according to the time domain type associated with second configuration information, where the second configuration information is used to pre-configure the first uplink transmission;

[0344] Determining the target time domain type according to a time domain type associated with third configuration information, where the third configuration information is used to pre-configure resource sets for K uplink transmissions, where the K uplink transmissions include the first uplink transmission, and K is a positive integer;

[0345] Determine the target time domain type according to fourth configuration information, where the fourth configuration information is used to pre-configure the time domain type of the first uplink transmission;

[0346] determining the target time domain type according to first scheduling information, where the first scheduling information is used to dynamically schedule the first uplink transmission;

[0347] The target time domain type is determined according to second scheduling information, where the second scheduling information is used to activate the first uplink transmission.

[0348] Optionally, the first processing module is specifically configured to perform at least one of the following:

[0349] Determining the target time domain type according to the time domain type information indicated by the first scheduling information;

[0350] Determining the target time domain type according to the time domain type corresponding to the time domain unit indicated by the first scheduling information;

[0351] Determining the target time domain type according to the time domain type associated with the codebook indicated by the first scheduling information;

[0352] The target time domain type is determined according to the time domain type associated with the transmission configuration indicated by the first scheduling information.

[0353] Optionally, the time domain unit in which the downlink transmission corresponding to the first uplink transmission is located includes at least one of the following:

[0354] a downlink time domain symbol corresponding to an end symbol of the downlink transmission corresponding to the first uplink transmission;

[0355] an uplink time domain symbol corresponding to an end symbol of the downlink transmission corresponding to the first uplink transmission;

[0356] a downlink time domain unit corresponding to an end position of the downlink transmission corresponding to the first uplink transmission;

[0357] The uplink time domain unit corresponds to the downlink time domain unit corresponding to the end position of the downlink transmission corresponding to the first uplink transmission.

[0358] Optionally, the first processing module is specifically configured to perform at least one of the following:

[0359] In a case where the target time domain unit is configured or indicated as an SBFD time domain unit, determining that the target time domain type is the SBFD time domain type;

[0360] In a case where the target time domain unit is configured or indicated as a non-SBFD time domain unit, determining the target time domain type to be the non-SBFD time domain type;

[0361] When all symbols of the target time domain unit are SBFD symbols, determining the target time domain type to be the SBFD time domain type;

[0362] When all symbols of the target time domain unit are non-SBFD symbols, determining the target time domain type to be the non-SBFD time domain type;

[0363] In a case where the target time domain unit includes both SBFD symbols and non-SBFD symbols, determining the target time domain type according to a target mode;

[0364] The target method includes at least one of the following:

[0365] Determining the target time domain type according to the number of SBFD symbols and the number of non-SBFD symbols included in the target time domain unit;

[0366] Determining the target time domain type according to the time domain type of the symbol located at a predefined position in the target time domain unit;

[0367] The target time domain type is determined according to a predefined or default time domain type of the target time domain unit.

[0368] Optionally, the target time domain unit includes at least one of the following:

[0369] a first time domain unit, where the first time domain unit is a time domain unit corresponding to actual transmission of the first uplink transmission;

[0370] a second time domain unit, where the second time domain unit is a time domain unit corresponding to the nominal transmission of the first uplink transmission;

[0371] The time domain granularities of the first time domain unit and the second time domain unit are the same or different.

[0372] Optionally, the first time domain unit includes a symbol, a time slot or a sub-time slot;

[0373] or,

[0374] The second time domain unit includes a time slot or a sub-time slot.

[0375] Optionally, the second time domain unit includes at least one of the following:

[0376] A time domain unit determined by the terminal according to the configured period and offset of the first uplink transmission;

[0377] The terminal is instructed to use a time domain unit for transmitting a hybrid automatic repeat request answering HARQ-ACK.

[0378] Optionally, the first processing module is specifically configured to perform at least one of the following:

[0379] When the time domain unit where the downlink transmission corresponding to the first uplink transmission is located is configured or indicated as an SBFD time domain unit, determining that the target time domain type is the SBFD time domain type;

[0380] When a time domain unit in which a downlink transmission corresponding to the first uplink transmission is located is configured or indicated as a non-SBFD time domain unit, determining that the target time domain type is the non-SBFD time domain type;

[0381] When all symbols of a time domain unit in which a downlink transmission corresponding to the first uplink transmission is located are SBFD symbols, determining that the target time domain type is the SBFD time domain type;

[0382] When all symbols of a time domain unit in which a downlink transmission corresponding to the first uplink transmission is located are non-SBFD symbols, determining that the target time domain type is the non-SBFD time domain type;

[0383] When the time domain unit where the downlink transmission corresponding to the first uplink transmission is located includes both SBFD symbols and non-SBFD symbols, determining the target time domain type according to a target mode;

[0384] The target method includes at least one of the following:

[0385] Determining the target time domain type according to the number of SBFD symbols and the number of non-SBFD symbols included in the time domain unit where the downlink transmission corresponding to the first uplink transmission is located;

[0386] Determining the target time domain type according to the time domain type of a symbol located at a predefined position in the time domain unit where the downlink transmission corresponding to the first uplink transmission is located;

[0387] The target time domain type is determined according to a predefined or default time domain type of a time domain unit where the downlink transmission corresponding to the first uplink transmission is located.

[0388] Optionally, the second processing module includes:

[0389] a receiving unit, configured to receive a first message from a network-side device, where the first message includes a first transmission configuration item and a second transmission configuration item, where the first transmission configuration item is mapped to the SBFD time domain type, and the second transmission configuration item is mapped to the non-SBFD time domain type;

[0390] a first processing unit, configured to determine, according to the target time domain type, a target transmission configuration item from the first transmission configuration item and the second transmission configuration item;

[0391] The second processing unit is configured to determine the transmission parameter associated with the target transmission configuration item as the transmission parameter of the first uplink transmission.

[0392] Optionally, the transmission parameters include at least one of transmission configuration, feedback timing set, time domain resource allocation TDRA, offset value, transmission code rate, power control parameter and beam parameter.

[0393] Optionally, the device further comprises:

[0394] A third processing module is configured to determine whether the first uplink transmission is valid, including at least one of the following:

[0395] In a case where the time domain unit of the first uplink transmission includes an SBFD symbol and a non-SBFD symbol, determining that the first uplink transmission is invalid;

[0396] In a case where the frequency domain resources of the first uplink transmission exceed the range of the SBFD uplink subband, it is determined that the first uplink transmission is invalid.

[0397] Optionally, the device further comprises:

[0398] a fourth processing module, configured to, if it is determined that the first uplink transmission is invalid, perform a first operation, where the first operation includes at least one of the following:

[0399] postponing the first uplink transmission;

[0400] The first uplink transmission is canceled.

[0401] Optionally, the device further comprises:

[0402] a fifth processing module, configured to, when a time domain type of the third time domain unit of the first uplink transmission does not match the target time domain type, perform a second operation, where the second operation includes at least one of the following:

[0403] postponing the first uplink transmission;

[0404] canceling the first uplink transmission;

[0405] Transmitting the first uplink transmission according to the transmission parameters corresponding to the time domain type of the third time domain unit;

[0406] The third time domain unit is a time domain unit corresponding to the actual transmission of the first uplink transmission.

[0407] Optionally, the device further comprises:

[0408] a sixth processing module, configured to, when the first uplink transmission channel overlaps with the second uplink transmission channel, perform a third operation, where the third operation includes at least one of the following:

[0409] postponing the first uplink transmission;

[0410] canceling the first uplink transmission;

[0411] The first uplink transmission and the second uplink transmission are multiplexed for transmission.

[0412] Optionally, the sixth processing module is specifically configured to:

[0413] In a case where a channel of the first uplink transmission overlaps with a channel of the second uplink transmission, determining whether the first uplink transmission and the second uplink transmission are valid according to SBFD configuration information from a network-side device;

[0414] If it is determined that the first uplink transmission and the second uplink transmission are valid, the third operation is performed.

[0415] Optionally, the third operation includes multiplexing the first uplink transmission and the second uplink transmission;

[0416] The device further comprises:

[0417] A seventh processing module is configured to determine, according to the SBFD configuration information, whether a channel multiplexed by the first uplink transmission and the second uplink transmission is valid.

[0418] Optionally, the time domain type of one of the first uplink transmission and the second uplink transmission is the SBFD time domain type, and the time domain type of the other is the non-SBFD time domain type;

[0419] The device further comprises:

[0420] An eighth processing module is used to determine the transmission parameters or transmission resources of the multiplexing transmission.

[0421] Optionally, the eighth processing module is specifically configured to perform at least one of the following:

[0422] Determining the transmission parameters corresponding to the uplink transmission whose time domain type is the SBFD time domain type as the transmission parameters of the multiplexed transmission;

[0423] Determining the transmission parameters corresponding to the uplink transmission whose time domain type is the non-SBFD time domain type as the transmission parameters of the multiplexed transmission;

[0424] Determining the transmission parameters corresponding to the uplink transmission with a higher priority as the transmission parameters of the multiplexed transmission;

[0425] In a case where the overlapping channel includes a first HARQ-ACK PUCCH, determining, according to a transmission configuration item corresponding to the first HARQ-ACK PUCCH, a transmission parameter or transmission resource of the multiplexed transmission, where the first HARQ-ACK PUCCH is a HARQ-ACK PUCCH with corresponding downlink control information DCI;

[0426] In a case where the overlapping channel includes a CSI PUCCH and a second HARQ-ACK PUCCH, determining the transmission parameters or transmission resources of the multiplexed transmission according to the transmission configuration item corresponding to the CSI PUCCH, and the second HARQ-ACK PUCCH is a HARQ-ACK PUCCH without corresponding DCI;

[0427] In the case where the overlapping channels include uplink control information UCI and a physical uplink shared channel PUSCH, the transmission parameters or transmission resources of the multiplexing transmission are determined according to parameters corresponding to the PUSCH.

[0428] In summary, the embodiments of the present application enable the terminal to more reasonably determine uplink transmission parameters under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink transmission under the SBFD configuration, thereby ensuring the communication performance of the terminal.

[0429] The uplink transmission device 600 in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component of an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can include servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0430] The uplink transmission device 600 provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 3 to 5 and achieve the same technical effects. To avoid repetition, they will not be described here.

[0431] FIG7 shows a flowchart of an uplink transmission configuration method provided by an embodiment of the present application. As shown in FIG7 , the uplink transmission configuration method includes the following steps:

[0432] Step 701: The network side device sends configuration information or scheduling information to the terminal, where the configuration information or the scheduling information is used to determine a target time domain type for a first uplink transmission; wherein the target time domain type includes an SBFD time domain type or a non-SBFD time domain type.

[0433] Optionally, the network-side device sends configuration information or scheduling information to the terminal, including at least one of the following:

[0434] The network-side device sends first configuration information to the terminal, where the first configuration information is associated with a corresponding time domain type, and the first configuration information is used to pre-configure transmission configurations of M uplink transmissions, where the M uplink transmissions include the first uplink transmission, and M is a positive integer;

[0435] The network-side device sends second configuration information to the terminal, where the second configuration information is associated with a corresponding time domain type, and the second configuration information is used to pre-configure the first uplink transmission;

[0436] The network-side device sends third configuration information to the terminal, where the third configuration information is associated with a corresponding time domain type, and the third configuration information is used to pre-configure K uplink transmission resource sets, where the K uplink transmissions include the first uplink transmission, and K is a positive integer;

[0437] The network-side device sends fourth configuration information to the terminal, where the fourth configuration information is used to pre-configure a time domain type of the first uplink transmission.

[0438] Optionally, the method further includes:

[0439] The network side device sends a first message to the terminal, where the first message includes a first transmission configuration item and a second transmission configuration item;

[0440] There is a mapping relationship between the first transmission configuration item and the sub-band full-duplex SBFD time domain type, and there is a mapping relationship between the second transmission configuration item and the non-sub-band full-duplex non-SBFD time domain type;

[0441] The first transmission configuration item and the second transmission configuration item both include transmission parameters.

[0442] Optionally, the transmission parameters include at least one of transmission configuration, feedback timing set, time domain resource allocation TDRA, offset value, transmission code rate, power control parameter and beam parameter.

[0443] For the relevant description of the embodiments of the present application, please refer to the relevant description of the method embodiments in Figures 3 to 5, and the same technical effects can be achieved. To avoid repetition, they will not be described in detail.

[0444] In summary, the embodiments of the present application enable the terminal to more reasonably determine uplink transmission parameters under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink transmission under the SBFD configuration, thereby ensuring the communication performance of the terminal.

[0445] The uplink transmission configuration method provided in the embodiment of the present application may be executed by an uplink transmission configuration device. In the embodiment of the present application, the uplink transmission configuration device performing the uplink transmission configuration method is taken as an example to illustrate the uplink transmission configuration device provided in the embodiment of the present application.

[0446] 8, the embodiment of the present application further provides an uplink transmission configuration device, which can be applied to a network side device. As shown in FIG8, the uplink transmission configuration device 800 includes:

[0447] A first sending module 801 is configured to send configuration information or scheduling information to a terminal, where the configuration information or the scheduling information is used to determine a target time domain type for a first uplink transmission;

[0448] The target time domain type includes a sub-band full-duplex (SBFD) time domain type or a non-sub-band full-duplex (non-SBFD) time domain type.

[0449] Optionally, the first sending module is specifically configured to perform at least one of the following:

[0450] Sending first configuration information to the terminal, where the first configuration information is associated with a corresponding time domain type, the first configuration information being used to pre-configure transmission configurations of M uplink transmissions, where the M uplink transmissions include the first uplink transmission, and M is a positive integer;

[0451] Sending second configuration information to the terminal, where the second configuration information is associated with a corresponding time domain type, and the second configuration information is used to pre-configure the first uplink transmission;

[0452] Sending third configuration information to the terminal, where the third configuration information is associated with a corresponding time domain type, and the third configuration information is used to pre-configure resource sets for K uplink transmissions, where the K uplink transmissions include the first uplink transmission, and K is a positive integer;

[0453] Sending fourth configuration information to the terminal, where the fourth configuration information is used to pre-configure a time domain type of the first uplink transmission.

[0454] Optionally, the device further comprises:

[0455] A second sending module, configured to send a first message to the terminal, where the first message includes a first transmission configuration item and a second transmission configuration item;

[0456] There is a mapping relationship between the first transmission configuration item and the sub-band full-duplex SBFD time domain type, and there is a mapping relationship between the second transmission configuration item and the non-sub-band full-duplex non-SBFD time domain type;

[0457] The first transmission configuration item and the second transmission configuration item both include transmission parameters.

[0458] Optionally, the transmission parameters include at least one of transmission configuration, feedback timing set, time domain resource allocation TDRA, offset value, transmission code rate, power control parameter and beam parameter.

[0459] In summary, the embodiments of the present application enable the terminal to more reasonably determine uplink transmission parameters under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink transmission under the SBFD configuration, thereby ensuring the communication performance of the terminal.

[0460] The uplink transmission configuration device 800 in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component of an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can include servers, network attached storage (NAS), etc., which are not specifically limited in the embodiment of the present application.

[0461] The uplink transmission configuration device 800 provided in the embodiment of the present application can implement the various processes implemented in the method embodiment of Figure 7 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0462] Optionally, as shown in Figure 9, an embodiment of the present application further provides a communication device 900, including a processor 901 and a memory 902, wherein the memory 902 stores a program or instruction that can be run on the processor 901. For example, when the communication device 900 is a terminal, the program or instruction is executed by the processor 901 to implement the various steps of the method embodiments of Figures 3 to 5, and can achieve the same technical effect. When the communication device 900 is a network-side device, the program or instruction is executed by the processor 901 to implement the various steps of the method embodiment of Figure 7 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0463] The present application also provides a terminal embodiment, wherein the communication interface and the processor are coupled, and the processor is configured to execute a program or instruction to implement the steps of the method embodiments shown in Figures 3 to 5. This terminal embodiment corresponds to the above-mentioned terminal-side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 10 is a schematic diagram of the hardware structure of a terminal implementing the embodiment of the present application.

[0464] The terminal 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009 and at least some of the components of the processor 1010.

[0465] Those skilled in the art will appreciate that the terminal 1000 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1010 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG10 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0466] It should be understood that in an embodiment of the present application, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0467] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1001 may transmit the data to the processor 1010 for processing. Furthermore, the RF unit 1001 may send uplink data to the network-side device. Typically, the RF unit 1001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0468] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1009 may include a volatile memory or a non-volatile memory, or the memory 1009 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 1009 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0469] Processor 1010 may include one or more processing units. Optionally, processor 1010 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1010.

[0470] The processor 1010 is configured to:

[0471] Determine a target time domain type corresponding to the first uplink transmission, where the target time domain type includes a sub-band full-duplex (SBFD) time domain type or a non-sub-band full-duplex (non-SBFD) time domain type;

[0472] Determine, according to the target time domain type, a transmission parameter of the first uplink transmission.

[0473] Optionally, the processor 1010 is further configured to perform at least one of the following:

[0474] Determining the target time domain type according to the configuration information or the scheduling information;

[0475] Determining the target time domain type according to a time domain unit where the downlink transmission corresponding to the first uplink transmission is located;

[0476] The target time domain type is determined according to a target time domain unit corresponding to the first uplink transmission.

[0477] Optionally, the processor 1010 is further configured to perform at least one of the following:

[0478] Determining the target time domain type according to a time domain type associated with first configuration information, where the first configuration information is used to pre-configure a transmission configuration of M uplink transmissions, where the M uplink transmissions include the first uplink transmission, and M is a positive integer;

[0479] Determining the target time domain type according to the time domain type associated with second configuration information, where the second configuration information is used to pre-configure the first uplink transmission;

[0480] Determining the target time domain type according to a time domain type associated with third configuration information, where the third configuration information is used to pre-configure resource sets for K uplink transmissions, where the K uplink transmissions include the first uplink transmission, and K is a positive integer;

[0481] Determine the target time domain type according to fourth configuration information, where the fourth configuration information is used to pre-configure the time domain type of the first uplink transmission;

[0482] determining the target time domain type according to first scheduling information, where the first scheduling information is used to dynamically schedule the first uplink transmission;

[0483] The target time domain type is determined according to second scheduling information, where the second scheduling information is used to activate the first uplink transmission.

[0484] Optionally, the first processing module is specifically configured to perform at least one of the following:

[0485] Determining the target time domain type according to the time domain type information indicated by the first scheduling information;

[0486] Determining the target time domain type according to the time domain type corresponding to the time domain unit indicated by the first scheduling information;

[0487] Determining the target time domain type according to the time domain type associated with the codebook indicated by the first scheduling information;

[0488] The target time domain type is determined according to the time domain type associated with the transmission configuration indicated by the first scheduling information.

[0489] Optionally, the time domain unit in which the downlink transmission corresponding to the first uplink transmission is located includes at least one of the following:

[0490] a downlink time domain symbol corresponding to an end symbol of the downlink transmission corresponding to the first uplink transmission;

[0491] an uplink time domain symbol corresponding to an end symbol of the downlink transmission corresponding to the first uplink transmission;

[0492] a downlink time domain unit corresponding to an end position of the downlink transmission corresponding to the first uplink transmission;

[0493] The uplink time domain unit corresponds to the downlink time domain unit corresponding to the end position of the downlink transmission corresponding to the first uplink transmission.

[0494] Optionally, the processor 1010 is further configured to perform at least one of the following:

[0495] In a case where the target time domain unit is configured or indicated as an SBFD time domain unit, determining that the target time domain type is the SBFD time domain type;

[0496] In a case where the target time domain unit is configured or indicated as a non-SBFD time domain unit, determining the target time domain type to be the non-SBFD time domain type;

[0497] When all symbols of the target time domain unit are SBFD symbols, determining the target time domain type to be the SBFD time domain type;

[0498] When all symbols of the target time domain unit are non-SBFD symbols, determining the target time domain type to be the non-SBFD time domain type;

[0499] In a case where the target time domain unit includes both SBFD symbols and non-SBFD symbols, determining the target time domain type according to a target mode;

[0500] The target method includes at least one of the following:

[0501] Determining the target time domain type according to the number of SBFD symbols and the number of non-SBFD symbols included in the target time domain unit;

[0502] Determining the target time domain type according to the time domain type of the symbol located at a predefined position in the target time domain unit;

[0503] The target time domain type is determined according to a predefined or default time domain type of the target time domain unit.

[0504] Optionally, the target time domain unit includes at least one of the following:

[0505] a first time domain unit, where the first time domain unit is a time domain unit corresponding to actual transmission of the first uplink transmission;

[0506] a second time domain unit, where the second time domain unit is a time domain unit corresponding to the nominal transmission of the first uplink transmission;

[0507] The time domain granularities of the first time domain unit and the second time domain unit are the same or different.

[0508] Optionally, the first time domain unit includes a symbol, a time slot or a sub-time slot;

[0509] or,

[0510] The second time domain unit includes a time slot or a sub-time slot.

[0511] Optionally, the second time domain unit includes at least one of the following:

[0512] A time domain unit determined by the terminal according to the configured period and offset of the first uplink transmission;

[0513] The terminal is instructed to use a time domain unit for transmitting a hybrid automatic repeat request answering HARQ-ACK.

[0514] Optionally, the processor 1010 is further configured to perform at least one of the following:

[0515] When the time domain unit where the downlink transmission corresponding to the first uplink transmission is located is configured or indicated as an SBFD time domain unit, determining that the target time domain type is the SBFD time domain type;

[0516] When a time domain unit in which a downlink transmission corresponding to the first uplink transmission is located is configured or indicated as a non-SBFD time domain unit, determining that the target time domain type is the non-SBFD time domain type;

[0517] When all symbols of a time domain unit in which a downlink transmission corresponding to the first uplink transmission is located are SBFD symbols, determining that the target time domain type is the SBFD time domain type;

[0518] When all symbols of a time domain unit in which a downlink transmission corresponding to the first uplink transmission is located are non-SBFD symbols, determining that the target time domain type is the non-SBFD time domain type;

[0519] When the time domain unit where the downlink transmission corresponding to the first uplink transmission is located includes both SBFD symbols and non-SBFD symbols, determining the target time domain type according to a target mode;

[0520] The target method includes at least one of the following:

[0521] Determining the target time domain type according to the number of SBFD symbols and the number of non-SBFD symbols included in the time domain unit where the downlink transmission corresponding to the first uplink transmission is located;

[0522] Determining the target time domain type according to the time domain type of a symbol located at a predefined position in the time domain unit where the downlink transmission corresponding to the first uplink transmission is located;

[0523] The target time domain type is determined according to a predefined or default time domain type of a time domain unit where the downlink transmission corresponding to the first uplink transmission is located.

[0524] Optionally, the radio frequency unit 1001 is configured to:

[0525] receiving a first message from a network-side device, where the first message includes a first transmission configuration item and a second transmission configuration item, where the first transmission configuration item is mapped to the SBFD time domain type, and the second transmission configuration item is mapped to the non-SBFD time domain type;

[0526] The processor 1010 is further configured to:

[0527] determining, according to the target time domain type, a target transmission configuration item from the first transmission configuration item and the second transmission configuration item;

[0528] The transmission parameter associated with the target transmission configuration item is determined as the transmission parameter of the first uplink transmission.

[0529] Optionally, the transmission parameters include at least one of transmission configuration, feedback timing set, time domain resource allocation TDRA, offset value, transmission code rate, power control parameter and beam parameter.

[0530] Optionally, the processor 1010 is further configured to:

[0531] Determining whether the first uplink transmission is valid includes at least one of the following:

[0532] In a case where the time domain unit of the first uplink transmission includes an SBFD symbol and a non-SBFD symbol, determining that the first uplink transmission is invalid;

[0533] In a case where the frequency domain resources of the first uplink transmission exceed the range of the SBFD uplink subband, it is determined that the first uplink transmission is invalid.

[0534] Optionally, the processor 1010 is further configured to:

[0535] If it is determined that the first uplink transmission is invalid, performing a first operation, where the first operation includes at least one of the following:

[0536] postponing the first uplink transmission;

[0537] The first uplink transmission is canceled.

[0538] Optionally, the processor 1010 is further configured to:

[0539] When the time domain type of the third time domain unit of the first uplink transmission does not match the target time domain type, performing a second operation, where the second operation includes at least one of the following:

[0540] postponing the first uplink transmission;

[0541] canceling the first uplink transmission;

[0542] Transmitting the first uplink transmission according to the transmission parameters corresponding to the time domain type of the third time domain unit;

[0543] The third time domain unit is a time domain unit corresponding to the actual transmission of the first uplink transmission.

[0544] Optionally, the processor 1010 is further configured to:

[0545] In a case where the channel of the first uplink transmission overlaps with the channel of the second uplink transmission, performing a third operation, where the third operation includes at least one of the following:

[0546] postponing the first uplink transmission;

[0547] canceling the first uplink transmission;

[0548] The first uplink transmission and the second uplink transmission are multiplexed for transmission.

[0549] Optionally, the processor 1010 is further configured to:

[0550] In a case where a channel of the first uplink transmission overlaps with a channel of the second uplink transmission, determining whether the first uplink transmission and the second uplink transmission are valid according to SBFD configuration information from a network-side device;

[0551] If it is determined that the first uplink transmission and the second uplink transmission are valid, the third operation is performed.

[0552] Optionally, the third operation includes multiplexing the first uplink transmission and the second uplink transmission;

[0553] The processor 1010 is further configured to:

[0554] Determine whether a channel multiplexed by the first uplink transmission and the second uplink transmission is valid according to the SBFD configuration information.

[0555] Optionally, the time domain type of one of the first uplink transmission and the second uplink transmission is the SBFD time domain type, and the time domain type of the other is the non-SBFD time domain type;

[0556] The processor 1010 is further configured to:

[0557] Determine transmission parameters or transmission resources of the multiplexed transmission.

[0558] Optionally, the processor 1010 is further configured to perform at least one of the following:

[0559] Determining the transmission parameters corresponding to the uplink transmission whose time domain type is the SBFD time domain type as the transmission parameters of the multiplexed transmission;

[0560] Determining the transmission parameters corresponding to the uplink transmission whose time domain type is the non-SBFD time domain type as the transmission parameters of the multiplexed transmission;

[0561] Determining the transmission parameters corresponding to the uplink transmission with a higher priority as the transmission parameters of the multiplexed transmission;

[0562] In a case where the overlapping channel includes a first HARQ-ACK PUCCH, determining, according to a transmission configuration item corresponding to the first HARQ-ACK PUCCH, a transmission parameter or transmission resource of the multiplexed transmission, where the first HARQ-ACK PUCCH is a HARQ-ACK PUCCH with corresponding downlink control information DCI;

[0563] In a case where the overlapping channel includes a CSI PUCCH and a second HARQ-ACK PUCCH, determining the transmission parameters or transmission resources of the multiplexed transmission according to the transmission configuration item corresponding to the CSI PUCCH, and the second HARQ-ACK PUCCH is a HARQ-ACK PUCCH without corresponding DCI;

[0564] In the case where the overlapping channels include uplink control information UCI and a physical uplink shared channel PUSCH, the transmission parameters or transmission resources of the multiplexing transmission are determined according to parameters corresponding to the PUSCH.

[0565] In summary, the embodiments of the present application enable the terminal to more reasonably determine uplink transmission parameters under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink transmission under the SBFD configuration, thereby ensuring the communication performance of the terminal.

[0566] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiments of Figures 3 to 5, and achieve the same or corresponding technical effects. To avoid repetition, they will not be repeated here.

[0567] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG7 . This network-side device embodiment corresponds to the aforementioned network-side device method embodiment, and each implementation process and implementation method of the aforementioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0568] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 11, the network-side device 1100 includes an antenna 111, a radio frequency device 112, a baseband device 113, a processor 114, and a memory 115. Antenna 111 is connected to radio frequency device 112. In the uplink direction, radio frequency device 112 receives information via antenna 111 and sends the received information to baseband device 113 for processing. In the downlink direction, baseband device 113 processes the information to be transmitted and sends it to radio frequency device 112. Radio frequency device 112 processes the received information and then sends it through antenna 111.

[0569] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 113 , which includes a baseband processor.

[0570] The baseband device 113 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 11, one of the chips is, for example, a baseband processor, which is connected to the memory 115 through a bus interface to call the program in the memory 115 and execute the operations performed by the terminal or network side device shown in the above method embodiment.

[0571] The network side device may further include a network interface 116, which is, for example, a common public radio interface (CPRI).

[0572] Specifically, the network side device 110 of the embodiment of the present application also includes: instructions or programs stored in the memory 115 and executable on the processor 114. The processor 114 calls the instructions or programs in the memory 115 to execute the methods of execution of each module shown in Figure 8 and achieve the same technical effect. To avoid repetition, it will not be described here.

[0573] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the method embodiments of Figures 3 to 5 above, or the various processes of the method embodiment of Figure 7 above, are implemented, and the same technical effect can be achieved. To avoid repetition, they are not repeated here.

[0574] The processor is the processor in the terminal described in the above embodiment, or the processor of the network-side device described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0575] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the method embodiments of Figures 3 to 5 above, or to implement the various processes of the method embodiment of Figure 7 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0576] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0577] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the embodiment of the uplink transmission method of the above-mentioned terminal, or to implement the various processes of the embodiment of the uplink transmission configuration method of the above-mentioned network side device. To avoid repetition, they are not repeated here.

[0578] An embodiment of the present application also provides a communication system, including: a terminal and a network side device, wherein the terminal can be used to execute the steps of the uplink transmission method on the terminal side, and the network side device can be used to execute the steps of the uplink transmission configuration method of the network side device.

[0579] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0580] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network-side device, etc.) to execute the methods described in each embodiment of the present application.

[0581] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. An uplink transmission method, comprising: The terminal determines a target time domain type corresponding to the first uplink transmission, where the target time domain type includes a sub-band full-duplex SBFD time domain type or a non-sub-band full-duplex non-SBFD time domain type; The terminal determines, according to the target time domain type, a transmission parameter of the first uplink transmission.

2. The method according to claim 1, wherein: The terminal determines a target time domain type corresponding to the first uplink transmission, including at least one of the following: The terminal determines the target time domain type according to configuration information or scheduling information; The terminal determines the target time domain type according to a time domain unit where the downlink transmission corresponding to the first uplink transmission is located; The terminal determines the target time domain type according to a target time domain unit corresponding to the first uplink transmission.

3. The method according to claim 2, wherein: The terminal determines the target time domain type according to the configuration information or the scheduling information, including at least one of the following: The terminal determines the target time domain type according to the time domain type associated with first configuration information, where the first configuration information is used to pre-configure transmission configurations of M uplink transmissions, where the M uplink transmissions include the first uplink transmission, and M is a positive integer; The terminal determines, according to the time domain type associated with second configuration information, the target time domain type, where the second configuration information is used to pre-configure the first uplink transmission; The terminal determines the target time domain type according to the time domain type associated with third configuration information, where the third configuration information is used to pre-configure resource sets for K uplink transmissions, where the K uplink transmissions include the first uplink transmission, and K is a positive integer; The terminal determines, according to fourth configuration information, the target time domain type, where the fourth configuration information is used to pre-configure the time domain type of the first uplink transmission; The terminal determines the target time domain type according to first scheduling information, where the first scheduling information is used to dynamically schedule the first uplink transmission; The terminal determines the target time domain type according to second scheduling information, where the second scheduling information is used to activate the first uplink transmission.

4. The method according to claim 3, wherein: The terminal determines, according to the first scheduling information, the target time domain type, including at least one of the following: The terminal determines the target time domain type according to the time domain type information indicated by the first scheduling information; The terminal determines the target time domain type according to the time domain type corresponding to the time domain unit indicated by the first scheduling information; Determining, by the terminal, the target time domain type according to the time domain type associated with the codebook indicated by the first scheduling information; The terminal determines the target time domain type according to the time domain type associated with the transmission configuration indicated by the first scheduling information.

5. The method according to claim 2, wherein: The time domain unit where the downlink transmission corresponding to the first uplink transmission is located includes at least one of the following: a downlink time domain symbol corresponding to an end symbol of the downlink transmission corresponding to the first uplink transmission; An uplink time domain symbol corresponding to an end symbol of a downlink transmission corresponding to the first uplink transmission; A downlink time domain unit corresponding to an end position of the downlink transmission corresponding to the first uplink transmission; The uplink time domain unit corresponds to the downlink time domain unit corresponding to the end position of the downlink transmission corresponding to the first uplink transmission.

6. The method according to claim 2, wherein: The terminal determines, according to the target time domain unit corresponding to the first uplink transmission, the target time domain type, including at least one of the following: In a case where the target time domain unit is configured or indicated as a SBFD time domain unit, the terminal determines that the target time domain type is the SBFD time domain type; In a case where the target time domain unit is configured or indicated as a non-SBFD time domain unit, the terminal determines that the target time domain type is the non-SBFD time domain type; In a case where all symbols of the target time domain unit are SBFD symbols, the terminal determines that the target time domain type is the SBFD time domain type; In a case where all symbols of the target time domain unit are non-SBFD symbols, the terminal determines that the target time domain type is the non-SBFD time domain type; In a case where the target time domain unit includes both SBFD symbols and non-SBFD symbols, the terminal determines the target time domain type according to a target mode; The target method includes at least one of the following: Determining the target time domain type according to the number of SBFD symbols and the number of non-SBFD symbols included in the target time domain unit; Determining the target time domain type according to the time domain type of the symbol located at a predefined position in the target time domain unit; The target time domain type is determined according to a predefined or default time domain type of the target time domain unit.

7. The method according to claim 2 or 6, wherein: The target time domain unit includes at least one of the following: A first time domain unit, where the first time domain unit is a time domain unit corresponding to actual transmission of the first uplink transmission; a second time domain unit, where the second time domain unit is a time domain unit corresponding to the nominal transmission of the first uplink transmission; The time domain granularities of the first time domain unit and the second time domain unit are the same or different.

8. The method according to claim 7, wherein: The first time domain unit includes a symbol, a time slot or a sub-time slot; or, The second time domain unit includes a time slot or a sub-time slot.

9. The method according to claim 7 or 8, wherein: The second time domain unit includes at least one of the following: The time domain unit determined by the terminal according to the configured period and offset of the first uplink transmission; The terminal is instructed to use a time domain unit for transmitting a hybrid automatic repeat request answer HARQ-ACK.

10. The method according to any one of claims 1 to 9, wherein: The terminal determines, according to the target time domain type, a transmission parameter of the first uplink transmission, including: The terminal receives a first message from a network-side device, where the first message includes a first transmission configuration item and a second transmission configuration item, where a mapping relationship exists between the first transmission configuration item and the SBFD time domain type, and where a mapping relationship exists between the second transmission configuration item and the non-SBFD time domain type; Determining, by the terminal, a target transmission configuration item from the first transmission configuration item and the second transmission configuration item according to the target time domain type; The terminal determines the transmission parameter associated with the target transmission configuration item as the transmission parameter of the first uplink transmission.

11. The method according to any one of claims 1 to 10, wherein: The transmission parameters include at least one of transmission configuration, feedback timing set, time domain resource allocation TDRA, offset value, transmission code rate, power control parameter and beam parameter.

12. The method according to any one of claims 1 to 11, further comprising: The terminal determines whether the first uplink transmission is valid, including at least one of the following: In a case where the time domain unit of the first uplink transmission includes an SBFD symbol and a non-SBFD symbol, the terminal determines that the first uplink transmission is invalid; In a case where the frequency domain resources of the first uplink transmission exceed the range of the SBFD uplink subband, the terminal determines that the first uplink transmission is invalid.

13. The method according to claim 12, further comprising: When determining that the first uplink transmission is invalid, the terminal performs a first operation, where the first operation includes at least one of the following: postponing the first uplink transmission; The first uplink transmission is canceled.

14. The method according to any one of claims 1 to 13, further comprising: In a case where the time domain type of the third time domain unit of the first uplink transmission does not match the target time domain type, the terminal performs a second operation, where the second operation includes at least one of the following: postponing the first uplink transmission; canceling the first uplink transmission; Transmitting the first uplink transmission according to the transmission parameters corresponding to the time domain type of the third time domain unit; The third time domain unit is a time domain unit corresponding to actual transmission of the first uplink transmission.

15. The method according to any one of claims 1 to 14, further comprising: In a case where the first uplink transmission channel overlaps with the second uplink transmission channel, the terminal performs a third operation, where the third operation includes at least one of the following: postponing the first uplink transmission; canceling the first uplink transmission; The first uplink transmission and the second uplink transmission are multiplexed for transmission.

16. The method according to claim 15, wherein: In a case where the first uplink transmission channel overlaps with the second uplink transmission channel, the terminal performing a third operation, including: In a case where a channel of the first uplink transmission overlaps with a channel of the second uplink transmission, the terminal determines whether the first uplink transmission and the second uplink transmission are valid according to SBFD configuration information from a network-side device; When determining that the first uplink transmission and the second uplink transmission are valid, the terminal performs the third operation.

17. The method according to claim 15, wherein: The third operation includes multiplexing the first uplink transmission and the second uplink transmission for transmission; After the terminal multiplexes the first uplink transmission and the second uplink transmission, the method further includes: The terminal determines, according to the SBFD configuration information, whether a channel multiplexed by the first uplink transmission and the second uplink transmission is valid.

18. The method according to any one of claims 15 to 17, wherein: The time domain type of one of the first uplink transmission and the second uplink transmission is the SBFD time domain type, and the time domain type of the other is the non-SBFD time domain type; The method further comprises: The terminal determines a transmission parameter or a transmission resource of the multiplexed transmission.

19. The method according to claim 18, wherein: The terminal determines a transmission parameter or a transmission resource of the multiplexed transmission, including at least one of the following: The terminal determines, as the transmission parameter of the multiplexed transmission, the transmission parameter corresponding to the uplink transmission whose time domain type is the SBFD time domain type; The terminal determines, as the transmission parameters of the multiplexed transmission, the transmission parameters corresponding to the uplink transmission whose time domain type is the non-SBFD time domain type; The terminal determines the transmission parameters corresponding to the uplink transmission with a higher priority as the transmission parameters of the multiplexed transmission; In a case where the overlapping channel includes a first HARQ-ACK PUCCH, the terminal determines, according to a transmission configuration item corresponding to the first HARQ-ACK PUCCH, a transmission parameter or a transmission resource of the multiplexed transmission, where the first HARQ-ACK PUCCH is a HARQ-ACK PUCCH having corresponding downlink control information DCI; In a case where the overlapping channel includes a CSI PUCCH and a second HARQ-ACK PUCCH, the terminal determines, according to a transmission configuration item corresponding to the CSI PUCCH, a transmission parameter or a transmission resource for the multiplexed transmission, and the second HARQ-ACK PUCCH is a HARQ-ACK PUCCH without corresponding DCI; In the case where the overlapping channels include uplink control information UCI and a physical uplink shared channel PUSCH, the terminal determines the transmission parameters or transmission resources of the multiplexing transmission according to the parameters corresponding to the PUSCH.

20. A method for configuring uplink transmission, comprising: The network side device sends configuration information or scheduling information to the terminal, where the configuration information or the scheduling information is used to determine a target time domain type for the first uplink transmission; The target time domain type includes a sub-band full-duplex (SBFD) time domain type or a non-sub-band full-duplex (non-SBFD) time domain type.

21. The method according to claim 20, wherein: The network side device sends configuration information or scheduling information to the terminal, including at least one of the following: The network side device sends first configuration information to the terminal, where the first configuration information is associated with a corresponding time domain type, and the first configuration information is used to pre-configure transmission configurations of M uplink transmissions, where the M uplink transmissions include the first uplink transmission, and M is a positive integer; The network side device sends second configuration information to the terminal, where the second configuration information is associated with a corresponding time domain type, and the second configuration information is used to pre-configure the first uplink transmission; The network side device sends third configuration information to the terminal, where the third configuration information is associated with a corresponding time domain type, and the third configuration information is used to pre-configure a resource set of K uplink transmissions, where the K uplink transmissions include the first uplink transmission, and K is a positive integer; The network side device sends fourth configuration information to the terminal, where the fourth configuration information is used to pre-configure a time domain type of the first uplink transmission.

22. The method according to claim 20 or 21, further comprising: The network side device sends a first message to the terminal, where the first message includes a first transmission configuration item and a second transmission configuration item; There is a mapping relationship between the first transmission configuration item and the sub-band full-duplex SBFD time domain type, and there is a mapping relationship between the second transmission configuration item and the non-sub-band full-duplex non-SBFD time domain type; The first transmission configuration item and the second transmission configuration item both include transmission parameters.

23. The method according to claim 22, wherein: The transmission parameters include at least one of transmission configuration, feedback timing set, time domain resource allocation TDRA, offset value, transmission code rate, power control parameter and beam parameter.

24. An uplink transmission device, applied to a terminal, the device comprising: A first processing module is configured to determine a target time domain type corresponding to a first uplink transmission, where the target time domain type includes a sub-band full-duplex SBFD time domain type or a non-sub-band full-duplex non-SBFD time domain type; The second processing module is used to determine the transmission parameters of the first uplink transmission according to the target time domain type.

25. The device according to claim 24, wherein: The first processing module is specifically used for at least one of the following: Determining the target time domain type according to the configuration information or the scheduling information; Determine the target time domain type according to the time domain unit where the downlink transmission corresponding to the first uplink transmission is located; The target time domain type is determined according to a target time domain unit corresponding to the first uplink transmission.

26. The device according to claim 25, wherein The first processing module is specifically used for at least one of the following: Determining the target time domain type according to a time domain type associated with first configuration information, where the first configuration information is used to pre-configure transmission configurations of M uplink transmissions, where the M uplink transmissions include the first uplink transmission, and M is a positive integer; Determining the target time domain type according to the time domain type associated with second configuration information, where the second configuration information is used to pre-configure the first uplink transmission; Determine the target time domain type according to the time domain type associated with third configuration information, where the third configuration information is used to pre-configure resource sets for K uplink transmissions, where the K uplink transmissions include the first uplink transmission, and K is a positive integer; Determine the target time domain type according to fourth configuration information, where the fourth configuration information is used to pre-configure the time domain type of the first uplink transmission; Determining the target time domain type according to first scheduling information, where the first scheduling information is used to dynamically schedule the first uplink transmission; The target time domain type is determined according to second scheduling information, where the second scheduling information is used to activate the first uplink transmission.

27. The device according to claim 26, wherein: The first processing module is specifically used for at least one of the following: Determining the target time domain type according to the time domain type information indicated by the first scheduling information; Determining the target time domain type according to the time domain type corresponding to the time domain unit indicated by the first scheduling information; Determining the target time domain type according to the time domain type associated with the codebook indicated by the first scheduling information; The target time domain type is determined according to the time domain type associated with the transmission configuration indicated by the first scheduling information.

28. The device according to claim 25, wherein The first processing module is specifically used for at least one of the following: In a case where the target time domain unit is configured as a SBFD time domain unit, determining that the target time domain type is the SBFD time domain type; In a case where the target time domain unit is configured as a non-SBFD time domain unit, determining the target time domain type to be the non-SBFD time domain type; In a case where all symbols of the target time domain unit are SBFD symbols, determining that the target time domain type is the SBFD time domain type; In a case where all symbols of the target time domain unit are non-SBFD symbols, determining the target time domain type to be the non-SBFD time domain type; In the case where the target time domain unit includes both SBFD symbols and non-SBFD symbols, determining the target time domain type according to a target mode; The target method includes at least one of the following: Determining the target time domain type according to the number of SBFD symbols and the number of non-SBFD symbols included in the target time domain unit; Determining the target time domain type according to the time domain type of the symbol located at a predefined position in the target time domain unit; The target time domain type is determined according to a predefined or default time domain type of the target time domain unit.

29. The device according to any one of claims 24 to 28, wherein The second processing module comprises: A receiving unit, configured to receive a first message from a network side device, wherein the first message includes a first transmission configuration item and a second transmission configuration item, wherein a mapping relationship exists between the first transmission configuration item and the SBFD time domain type, and a mapping relationship exists between the second transmission configuration item and the non-SBFD time domain type; A first processing unit, configured to determine a target transmission configuration item from the first transmission configuration item and the second transmission configuration item according to the target time domain type; The second processing unit is used to determine the transmission parameter associated with the target transmission configuration item as the transmission parameter of the first uplink transmission.

30. The apparatus according to any one of claims 24 to 29, further comprising: A third processing module is configured to determine whether the first uplink transmission is valid, including at least one of the following: In a case where the time domain unit of the first uplink transmission includes an SBFD symbol and a non-SBFD symbol, determining that the first uplink transmission is invalid; In a case where the frequency domain resources of the first uplink transmission exceed the range of the SBFD uplink subband, it is determined that the first uplink transmission is invalid.

31. The apparatus of claim 30, further comprising: a fourth processing module, configured to, when determining that the first uplink transmission is invalid, perform a first operation, wherein the first operation includes at least one of the following: postponing the first uplink transmission; The first uplink transmission is canceled.

32. The apparatus according to any one of claims 24 to 31, further comprising: a fifth processing module, configured to perform a second operation when the time domain type of the third time domain unit of the first uplink transmission does not match the target time domain type, wherein the second operation includes at least one of the following: postponing the first uplink transmission; canceling the first uplink transmission; Transmitting the first uplink transmission according to the transmission parameters corresponding to the time domain type of the third time domain unit; The third time domain unit is a time domain unit corresponding to actual transmission of the first uplink transmission.

33. The apparatus according to any one of claims 24 to 32, further comprising: A sixth processing module is configured to perform a third operation when the first uplink transmission channel overlaps with the second uplink transmission channel, where the third operation includes at least one of the following: postponing the first uplink transmission; canceling the first uplink transmission; The first uplink transmission and the second uplink transmission are multiplexed for transmission.

34. The device according to claim 33, wherein The sixth processing module is specifically used for: In a case where a channel of the first uplink transmission overlaps with a channel of the second uplink transmission, determining whether the first uplink transmission and the second uplink transmission are valid according to SBFD configuration information from a network-side device; In a case where it is determined that the first uplink transmission and the second uplink transmission are valid, the third operation is performed.

35. The device according to claim 33, wherein The third operation includes multiplexing the first uplink transmission and the second uplink transmission for transmission; The device also includes: The seventh processing module is used to determine whether the channel multiplexed by the first uplink transmission and the second uplink transmission is valid according to the SBFD configuration information.

36. The device according to any one of claims 33 to 35, wherein: The time domain type of one of the first uplink transmission and the second uplink transmission is the SBFD time domain type, and the time domain type of the other is the non-SBFD time domain type; The device also includes: An eighth processing module is used to determine the transmission parameters or transmission resources of the multiplexed transmission.

37. The device according to claim 36, wherein The eighth processing module is specifically used for at least one of the following: Determine the transmission parameters corresponding to the uplink transmission whose time domain type is the SBFD time domain type as the transmission parameters of the multiplexed transmission; Determine the transmission parameters corresponding to the uplink transmission whose time domain type is the non-SBFD time domain type as the transmission parameters of the multiplexed transmission; Determine the transmission parameters corresponding to the uplink transmission with a higher priority as the transmission parameters of the multiplexed transmission; In a case where the overlapping channel includes a first HARQ-ACK PUCCH, determining a transmission parameter or a transmission resource of the multiplexed transmission according to a transmission configuration item corresponding to the first HARQ-ACK PUCCH, where the first HARQ-ACK PUCCH is a HARQ-ACK PUCCH having corresponding downlink control information DCI; In a case where the overlapping channel includes a CSI PUCCH and a second HARQ-ACK PUCCH, determining a transmission parameter or a transmission resource for the multiplexed transmission according to a transmission configuration item corresponding to the CSI PUCCH, and the second HARQ-ACK PUCCH is a HARQ-ACK PUCCH without corresponding DCI; In the case where the overlapping channels include uplink control information UCI and a physical uplink shared channel PUSCH, the transmission parameters or transmission resources of the multiplexing transmission are determined according to the parameters corresponding to the PUSCH.

38. An uplink transmission configuration device, applied to a network side device, the device comprising: A first sending module, used to send configuration information or scheduling information to a terminal, where the configuration information or the scheduling information is used to determine a target time domain type for a first uplink transmission; The target time domain type includes a sub-band full-duplex (SBFD) time domain type or a non-sub-band full-duplex (non-SBFD) time domain type.

39. The device according to claim 38, wherein The first sending module is specifically used for at least one of the following: Sending first configuration information to the terminal, where the first configuration information is associated with a corresponding time domain type, and the first configuration information is used to pre-configure transmission configurations of M uplink transmissions, where the M uplink transmissions include the first uplink transmission, and M is a positive integer; Sending second configuration information to the terminal, where the second configuration information is associated with a corresponding time domain type, and the second configuration information is used to pre-configure the first uplink transmission; Sending third configuration information to the terminal, where the third configuration information is associated with a corresponding time domain type, and the third configuration information is used to pre-configure resource sets for K uplink transmissions, where the K uplink transmissions include the first uplink transmission, and K is a positive integer; Sending fourth configuration information to the terminal, where the fourth configuration information is used to pre-configure a time domain type of the first uplink transmission.

40. The apparatus according to claim 38 or 39, further comprising: A second sending module, configured to send a first message to a terminal, wherein the first message includes a first transmission configuration item and a second transmission configuration item; There is a mapping relationship between the first transmission configuration item and the sub-band full-duplex SBFD time domain type, and there is a mapping relationship between the second transmission configuration item and the non-sub-band full-duplex non-SBFD time domain type; The first transmission configuration item and the second transmission configuration item both include transmission parameters.

41. A communication device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the uplink transmission method as described in any one of claims 1 to 19 are implemented, or the steps of the uplink transmission configuration method as described in any one of claims 20 to 23 are implemented.

42. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the uplink transmission method as described in any one of claims 1 to 19, or implements the steps of the uplink transmission configuration method as described in any one of claims 20 to 23.

Images