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 receiving a first message, which is from a network-side device, wherein the first message is used for instructing to perform N instances of repeated transmission of a first uplink transmission, N being a positive integer; and on the basis of a second message from the network-side device, the terminal determining a target time-domain unit corresponding to the first uplink transmission, wherein the second message is used for configuring at least one time-domain unit, and the at least one time-domain unit includes a subband full-duplex (SBFD) time-domain unit.

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. 202311678513.3 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, communication systems support repeated transmission of uplink transmissions, that is, an uplink transmission can be repeatedly transmitted on multiple continuous or discontinuous uplink time domain resources. Currently, uplink transmissions are only transmitted on uplink (UL) symbols or flexible symbols. When an uplink transmission overlaps with a semi-static downlink (DL) symbol or a synchronization signal block (SSB) symbol, the user equipment (UE, also known as the terminal) cancels the uplink transmission. In related technologies, the New Radio (NR) system introduces full-duplex transmission technology, and the UE can be configured with subband full-duplex (SBFD) time domain resources. How to perform repeated transmission of uplink transmissions under the SBFD configuration is a problem that needs to be solved. 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 repeated uplink transmission under SBFD configuration.

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

[0007] The terminal receives a first message from the network-side device, where the first message is used to instruct repeated transmission of a first uplink transmission N times, where N is a positive integer;

[0008] The terminal determines a target time domain unit corresponding to the first uplink transmission according to a second message from a network-side device, where the second message is used to configure at least one time domain unit, and the at least one time domain unit includes a sub-band full-duplex (SBFD) time domain unit.

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

[0010] A receiving module, configured to receive a first message from a network-side device, wherein the first message is used to instruct repeated transmission of a first uplink transmission N times, where N is a positive integer;

[0011] The first processing module is used to determine the target time domain unit corresponding to the first uplink transmission according to a second message from the network side device, where the second message is used to configure at least one time domain unit, and the at least one time domain unit includes a sub-band full-duplex (SBFD) time domain unit.

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

[0013] The network side device sends a first message to the terminal, where the first message is used to instruct repeated transmission of the first uplink transmission N times, where N is a positive integer;

[0014] The network-side device sends a second message to the terminal, where the second message is used to configure at least one time domain unit, where the at least one time domain unit includes a sub-band full-duplex (SBFD) time domain unit.

[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 a first message to a terminal, where the first message is used to instruct repeated transmission of a first uplink transmission N times, where N is a positive integer;

[0017] The second sending module is configured to send a second message to the terminal, where the second message is used to configure at least one time domain unit, where the at least one time domain unit includes a sub-band full-duplex (SBFD) time domain unit.

[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, comprising a processor and a communication interface, wherein the communication interface is used to: receive a first message from a network side device, the first message being used to indicate repeated transmission of a first uplink transmission N times, where N is a positive integer; the processor being used to: determine a target time domain unit corresponding to the first uplink transmission based on a second message from the network side device, the second message being used to configure at least one time domain unit, the at least one time domain unit comprising a sub-band full-duplex SBFD time domain unit.

[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 a first message to the terminal, the first message is used to indicate repeated transmission of the first uplink transmission N times, where N is a positive integer; send a second message to the terminal, the second message is used to configure at least one time domain unit, and the at least one time domain unit includes a sub-band full-duplex SBFD time domain unit.

[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 receives a first message from a network-side device, the first message being used to instruct repeated transmission of a first uplink transmission N times; the terminal determines a target time domain unit corresponding to the first uplink transmission based on a second message from the network-side device, the second message being used to configure at least one time domain unit, the at least one time domain unit including an SBFD time domain unit. This enables the terminal to more reasonably determine the time domain resource location for uplink repeated transmission under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink repeated transmission under the SBFD configuration, thereby ensuring the terminal's communication performance. 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 PUCCH is provided in an embodiment of the present application;

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

[0031] FIG6 is a schematic diagram of PUCCH repeated transmission according to an embodiment of the present application;

[0032] FIG7 is a second schematic diagram of PUCCH repeated transmission provided in an embodiment of the present application;

[0033] FIG8 is a schematic diagram of PUSCH repeated transmission according to an embodiment of the present application;

[0034] FIG9 is a second schematic diagram of PUSCH repeated transmission provided in an embodiment of the present application;

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

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

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

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

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

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

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

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

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

[0044] 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. thGeneration, 6G) communication system.

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

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

[0047] 1. Physical Uplink Control Channel (PUCCH) repetition

[0048] In NR related technologies, the same PUCCH is supported to be transmitted in the same time-frequency resource position in multiple slots or sub-slots. The number of repeated transmissions of PUCCH is configured by Radio Resource Control (RRC) according to each (per) PUCCH format (e.g., nrofSlots in PUCCH-Format) or PUCCH resource. Specifically, the UE can be configured to use one PUCCH resource in slots transmit a PUCCH, where Indicates the number of repeated transmissions. If the PUCCH resource is indicated by downlink control information (DCI) and contains the parameter pucch-RepetitionNrofSlots, then is provided by pucch-RepetitionNrofSlots, otherwise it is provided by nrofSlots.

[0049] In related technologies, a UE may determine a time unit (or time domain unit, such as a time slot or a sub-time slot) for PUCCH transmission as follows:

[0050] First, for asymmetric spectrum, the UE determines the transmission frequency of the PUCCH. The slots / sub-slots are:

[0051] Starting from slot / sub-slot A, the following conditions must be met:

[0052] The first symbol corresponding to the PUCCH resource (e.g., configured by startingSymbolIndex) is not an uplink (UL) or flexible symbol of a synchronization signal (SS) or a physical broadcast channel (PBCH); and

[0053] Starting from the first symbol corresponding to the PUCCH resource, X consecutive UL / flexible symbols that are not SS / PBCH, where X is greater than or equal to the number of symbols corresponding to the PUCCH resource (e.g., configured by nrofsymbols) slots / sub-slots.

[0054] Second, for symmetrical spectrum or uplink supplementary band, the UE determines the transmission frequency of PUCCH. The slots are:

[0055] Continuous from slot A slots.

[0056] Slot / sub-slot A is defined as:

[0057] For Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK), slot / sub-slot A is the slot / sub-slot in which the UE is instructed to feedback HARQ-ACK, for example, the slot or sub-slot determined by the PDSCH to HARQ-ACK feedback timing;

[0058] For Scheduling Request (SR) or Channel State Information (CSI), slot A is the timeslot for sending SR / CSI based on the configured period and offset. If it is a sub-slot, sub-slot A also needs to be determined based on the PUCCH start symbol position and sub-slot length configuration.

[0059] In related technologies, parameters for PUCCH transmission, such as transmission power or beam information (e.g., represented by spatial configuration information PUCCH-SpatialRelationInfo), are configured by RRC (or configured by RRC and activated by a Medium Access Control (MAC) control element (CE)). If the PUCCH corresponds to only one set of power control or spatial configuration, the UE uses the same parameters for each repeated transmission of the PUCCH. If the PUCCH includes two sets of power control or spatial configuration, the UE determines the parameters for repeated PUCCH transmission according to the following method:

[0060] If the number of PUCCH repetitions is 2, the first transmission and the second transmission of the PUCCH use the first spatial configuration and the second spatial configuration, respectively, or use the first power control parameter and the second power control parameter, respectively;

[0061] During every X repetitions, the first spatial configuration and the second spatial configuration are used alternately, or the first power control parameter and the second power control parameter are used alternately, where X is the base station configuration. For example, when the base station configures mappingPattern='cyclicMapping', X=1, otherwise X=2.

[0062] 2. Physical Uplink Shared Channel (PUSCH) Repetition

[0063] In the related art, two types of PUSCH repetition transmissions, PUSCH repetition type A and PUSCH repetition type B, are supported, where PUSCH repetition type A is a slot-level PUSCH repetition, that is, PUSCH is repeatedly transmitted at the same position in consecutive time slots. PUSCH repetition type B is a back-to-back transmission mode, that is, PUSCH adopts back-to-back repeated transmission on consecutive symbol resources. For PUSCH repetition type B, the UE determines the nominal repetition position based on the start and length indication value (SLIV) indicated by the time domain resource allocation (TDRA) and the number of repetitions, and determines the actual repetition position based on the invalid symbol. The invalid symbol includes at least one of the following:

[0064] Symbols indicated as DL symbols by semi-static signaling, such as tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated;

[0065] For asymmetric spectrum, the symbols for receiving SS / PBCH are indicated by ssb-PositionsInBurst (or NonCellDefiningSSB) in ssb-PositionsInBurst (or ServingCellConfigCommon) in the System Information Block (SIB);

[0066] For UEs with reduced half-duplex capability in symmetrical spectrum, there is no N-bits after the last symbol of the first symbol. Rx-Tx ·T c Symbols starting after N symbols, or, there is no N symbols before the first symbol Tx-Rx ·T c The first symbol includes at least one of the following:

[0067] Symbols indicated by ssb-PositionsInBurst (or NonCellDefiningSSB) in ssb-PositionsInBurst (or ServingCellConfigCommon) in SIB for SS / PBCH;

[0068] Symbols associated with the ssb-PositionsInBurst indication in the SSB-MTC-AdditionalPCI for receiving the physical downlink control channel (PDCCH) for SS / PBCH;

[0069] Symbols for SS / PBCH associated with the ssb-PositionsInBurst indication in the SSB-MTC-AdditionalPCI of the physical cell ID receiving the Physical Downlink Shared Channel (PDSCH) active Transmission Configuration Indicator (TCI) state;

[0070] Symbols used for SS / PBCH, indicated by the symbol set for Layer 1 (L1) beam measurement / reporting;

[0071] For asymmetric spectrum, the symbols of the control resource set (CORESET) for the type 0-PDCCH common search space (CSS) are indicated by the pdcch-ConfigSIB1 in the Master Information Block (MIB);

[0072] For asymmetric spectrum, if the base station configures higher-level parameters such as numberOfInvalidSymbolsForDL-UL-Switching, tdd-UL-DL-ConfigurationCommon, or tdd-UL-DL-ConfigurationDedicated, the number of symbols following the DL symbol configured by these higher-level parameters is numberOfInvalidSymbolsForDL-UL-Switching. The number of symbols indicated by numberOfInvalidSymbolsForDL-UL-Switching is configured or defined by the reference subcarrier spacing (SCS) configured by referenceSubcarrierSpacing in tdd-UL-DL-ConfigurationCommon.

[0073] For a shared spectrum occupied by a semi-static channel, the symbols within the idle time occupied by the periodic channel.

[0074] The UE may be configured with the higher-layer parameter invalidSymbolPattern, where invalidSymbolPattern provides a symbol-level bitmap within one or two slots, where each bit indicates whether the symbol is an invalid symbol for PUSCH repetition type B. The UE may also be configured with an additional time domain pattern (such as the higher-layer parameter periodicityAndPattern given by invalidSymbolPattern), where 1 bit in periodicityAndPattern corresponds to a unit of symbol-level bitmap symbols, and a bit value equal to 1 indicates the presence of a unit of symbol-level bitmap symbols.

[0075] Some symbols following the DL symbols semi-statically configured by the above-mentioned base station through the high-level parameter numberOfInvalidSymbolsForDL-UL-Switching (i.e., symbols indicated as DL by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated) cannot be used for PUSCH repetition type B, which is mainly used for DL ​​to UL switching and to ensure use for other transmissions, such as DL, PUCCH or sounding reference signal (SRS) transmission.

[0076] 3. Flexible duplex (SBFD)

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

[0078] 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, including full-duplex based on non-overlapping sub-bands in the frequency domain (sub-band full duplex (SBFD) for short).

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

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

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

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

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

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

[0085] SBFD Configuration or Instructions

[0086] 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. Semi-static SBFD was studied specifically, where only uplink transmission is performed within the uplink subband configured on the network side, and only downlink transmission is performed 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, the SBFD configuration for this 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, as well as uplink transmission outside the UL subband.

[0087] In addition, the signaling method for implementing Dynamic SBFD is also discussed, including the signaling indication method based on scheduling (Scheduling) DCI / non-scheduling (Non-scheduling) DCI / MAC control element (CE).

[0088] In related technologies, PUCCH repetitions are transmitted using the same time-frequency resources in different time units. When determining the time slots for PUCCH repetitions, the terminal only needs to consider the semi-static TDD uplink and downlink configuration. However, when the UE is configured with SBFD symbols, consideration must be given to determining the transmission time slots for PUCCH repetitions or how to perform PUCCH repetitions under SBFD.

[0089] In related technologies, when PUSCH repetition type B is repeatedly transmitted, symbols configured or indicated as invalid symbols cannot be used for PUSCH repetition type B transmission. The terminal only needs to consider the semi-static TDD uplink and downlink configuration when determining invalid symbols. When the UE is configured with SBFD symbols, how to determine the transmission time slot of PUSCH repetition type B or how to perform PUSCH repetition type B repetition under SBFD configuration needs to be considered.

[0090] In view of this, the embodiments of the present application provide an uplink transmission method, an uplink transmission configuration method and an apparatus to solve the problem that repetition transmission schemes such as PUCCH repetition and PUSCH repetition type B in related technologies cannot be applied to full-duplex transmission.

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

[0092] 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: DL symbol, UL symbol, and Flexible symbol.

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

[0094] Based on the above TDD pattern configuration information and the SBFD configuration information (hereinafter referred to as SBFD configuration) provided by the network side to the UE, the following Symbol type can be further distinguished: SBFD symbol.

[0095] The network side can configure certain symbols to perform SBFD operations through SBFD configuration information, that is, configure these symbols as SBFD symbols. 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 of the symbol types distinguished based on the TDD pattern configuration information.

[0096] 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:

[0097] 1) SBFD symbol for duplex mode 1

[0098] 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).

[0099] 2) SBFD symbol for duplex mode 2

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

[0101] 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).

[0102] 3) Non-SBFD symbol

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

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

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

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

[0107] 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:

[0108] Step 301: The terminal receives a first message from a network-side device, where the first message is used to instruct to repeat N times a first uplink transmission, where N is a positive integer.

[0109] Step 302: The terminal determines a target time domain unit corresponding to the first uplink transmission according to a second message from a network-side device, where the second message is used to configure at least one time domain unit, and the at least one time domain unit includes an SBFD time domain unit.

[0110] In the embodiments of the present application, a time domain unit can be understood as a specific time domain location. For example, slot i can be considered a time domain unit, and the jth symbol in slot i can also be considered a time domain unit. An SBFD time domain unit can be understood as a time domain unit whose time domain type is SBFD. The time domain granularity corresponding to the time domain unit can include a system frame, subframe, time slot, sub-time slot, symbol set, or symbol. For example, an SBFD symbol, an SBFD time slot, or an SBFD sub-time slot all belong to an SBFD time domain unit.

[0111] The first uplink transmission may include, for example, uplink transmissions such as PUCCH, SRS, or PUSCH, which is not limited in the embodiments of the present application.

[0112] The at least one time domain unit configured in the second message includes an SBFD time domain unit. Therefore, the second message can be understood as a message carrying SBFD configuration information, or as information used for configuring an SBFD time domain unit.

[0113] The terminal determines the target time domain unit corresponding to the first uplink transmission based on the second message from the network-side device. This can be understood as the terminal determining the target time domain unit corresponding to the first uplink transmission based on the SBFD configuration information. Specific determination methods may include the following two:

[0114] First, a direct determination method, that is, the terminal directly determines the target time domain unit for the first uplink transmission; illustratively, this method can be applied to PUCCH repetition;

[0115] Second, an indirect determination method, that is, the terminal indirectly determines the target time domain unit for the first uplink transmission by determining whether certain time domain units are invalid time domain units; illustratively, this method can be applied to PUSCH repetition type B.

[0116] The above two determination methods will be presented later through specific implementation methods.

[0117] It should be noted that, for N first uplink transmissions, the target time domain unit determined by the UE may include N time domain units.

[0118] In an embodiment of the present application, a terminal receives a first message from a network-side device, the first message being used to instruct repeated transmission of a first uplink transmission N times; the terminal determines a target time domain unit corresponding to the first uplink transmission based on a second message from the network-side device, the second message being used to configure at least one time domain unit, the at least one time domain unit including an SBFD time domain unit. This enables the terminal to more reasonably determine the time domain resource location for uplink repeated transmission under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink repeated transmission under the SBFD configuration, thereby ensuring the terminal's communication performance.

[0119] The following describes an implementation method for determining the target time domain unit corresponding to the first uplink transmission by directly determining the target time domain unit.

[0120] In some embodiments, the terminal determines, according to the second message from the network-side device, a target time domain unit corresponding to the first uplink transmission, including:

[0121] The terminal determines, starting from a first time domain unit among the at least one time domain unit, N time domain units that meet a first preset condition as the target time domain units;

[0122] The first preset condition includes at least one of the following:

[0123] The target symbol is a symbol not used for SS or PBCH;

[0124] The target symbol is a UL symbol, a flexible symbol, or a SBFD symbol;

[0125] The X consecutive symbols starting from the target symbol are symbols not used for SS or PBCH;

[0126] X consecutive symbols starting from the target symbol are UL symbols, flexible symbols or SBFD symbols;

[0127] Wherein, X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission;

[0128] The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

[0129] Exemplarily, the target symbol is the first symbol (or starting symbol) corresponding to the PUCCH resource, for example, configured by the parameter startingSymbolIndex.

[0130] This implementation manner is that the terminal starts from the first time domain unit of at least one time domain unit configured by the network side device, and searches for a target symbol (or X consecutive symbols starting from the target symbol) of any time domain type not used for SS / PBCH and containing uplink available resources as the target time domain unit.

[0131] Optionally, the first time domain unit includes at least one of the following:

[0132] a time domain unit indicated for feeding back first information, where the first information includes HARQ-ACK;

[0133] A time domain unit for sending second information determined according to a period and an offset of second information, where the second information includes at least one of SR and CSI.

[0134] In this implementation, the UE does not need to consider the time domain resource type on which the first uplink transmission is to be transmitted. The target time domain units thus determined may include time domain units of different time domain types. For example, some of the target time domain units are SBFD time domain units, while others are non-SBFD time domain units.

[0135] It should be noted that when sub-slot PUCCH repetition is configured, the first time domain unit (the first time domain unit is a sub-slot) needs to be determined based on the starting symbol of the PUCCH corresponding to the CSI / SR and the sub-slot length configuration.

[0136] The embodiment of the present application defines two time domain types, one of which is the SBFD time domain type (which may be referred to as the SBFD type), and the other is the non-SBFD time domain type (which may be 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, and 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. In other words, the target time domain unit determined by this embodiment may include time domain units of the SBFD time domain type, and may also include time domain units of the non-SBFD time domain type.

[0137] When the time domain resources corresponding to a certain repeated transmission of the first uplink transmission fall into different types of time domain units (ie, overlap with different types of time domain units), the UE may cancel the repeated transmission.

[0138] For example, assuming that PUCCH repetition is only transmitted in time domain units of the same time domain type (such as SBFD time domain units or non-SBFD time domain units), when the time domain resources of a PUCCH repetition fall in time domain units of different types, the UE cancels the PUCCH repetition.

[0139] In some embodiments, the target time domain unit further satisfies at least one of the following:

[0140] The symbols used for the first uplink transmission in the target time domain unit are all SBFD symbols or all non-SBFD symbols;

[0141] The SBFD uplink subband of the target time domain unit covers the frequency domain resources of the first uplink transmission.

[0142] For example, if the target time domain unit satisfies that all symbol positions corresponding to PUCCH repetition are SBFD symbols, the target time domain unit also needs to satisfy that the frequency domain resources corresponding to PUCCH repetition when the SBFD time domain unit is transmitted are within the UL subband.

[0143] Exemplarily, when the corresponding frequency domain resources when PUCCH repetition is transmitted in the SBFD time domain unit meet the conditions in the UL subband, the target time domain unit can be a time domain unit where the time domain resources where the PUCCH is located are SBFD symbols; otherwise, the target time domain unit is a time domain unit where the time domain resources where the PUCCH is located are UL / Flexible symbols.

[0144] As mentioned above, since the UE determines the target time domain unit without considering the time domain type of time domain resources on which the first uplink transmission needs to be transmitted, in this implementation, the above conditions are used to assist the UE in determining the target time domain unit, so that the determined target time domain unit can meet the requirements of the first uplink transmission as much as possible.

[0145] In some embodiments, the first uplink transmission is determined to be transmitted on a time domain resource of a target time domain type, and the target time domain type includes an SBFD time domain type or a non-SBFD time domain type;

[0146] The method further comprises:

[0147] When the time domain type of the second time domain unit of the first uplink transmission does not match the target time domain type, the terminal cancels transmission of the first uplink transmission in the second time domain unit;

[0148] The second time domain unit is at least one time domain unit in the target time domain unit corresponding to the first uplink transmission.

[0149] As previously described, since the UE determines the target time domain unit without considering the time domain resource of the time domain type on which the first uplink transmission needs to be transmitted, the determined target time domain unit may not match the target time domain type determined for the first uplink transmission. In this embodiment, when the time domain type of the second time domain unit in the target time domain unit does not match the target time domain type, the terminal may cancel the transmission of the first uplink transmission in the second time domain unit.

[0150] Optionally, the method further includes:

[0151] The terminal counts the number of the second time domain units into the total number of the target time domain units.

[0152] In some embodiments, the first uplink transmission is determined to be transmitted on a time domain resource of an SBFD time domain type;

[0153] The terminal determines, according to the second message from the network-side device, a target time domain unit corresponding to the first uplink transmission, including:

[0154] The terminal determines, starting from a first time domain unit among the at least one time domain unit, N time domain units that meet a second preset condition as the target time domain units;

[0155] The second preset condition includes at least one of the following:

[0156] The target symbol is the SBFD symbol not used for SS or PBCH;

[0157] The target symbol is the SBFD symbol;

[0158] The consecutive X symbols starting from the target symbol are SBFD symbols not used for SS or PBCH;

[0159] The X consecutive symbols starting from the target symbol are SBFD symbols;

[0160] Wherein, X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission;

[0161] The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

[0162] This implementation is that the terminal starts from the first time domain unit of at least one time domain unit configured by the network side device, and searches for a target symbol (or X consecutive symbols starting from the target symbol) as an SBFD time domain unit not used for SS / PBCH as the target time domain unit.

[0163] Optionally, the first time domain unit includes at least one of the following:

[0164] a time domain unit indicated for feeding back first information, where the first information includes HARQ-ACK;

[0165] A time domain unit for sending second information determined according to a period and an offset of second information, where the second information includes at least one of SR and CSI.

[0166] Exemplarily, the target symbol is the first symbol (or starting symbol) corresponding to the PUCCH resource, for example, configured by startingSymbolIndex.

[0167] In this implementation, the UE needs to consider the time domain resource of the time domain type on which the first uplink transmission needs to be transmitted, so that the target time domain units determined all belong to the same time domain type. This approach can be understood as follows: when the UE is determining the target time domain unit corresponding to the first uplink transmission, if it encounters a time domain unit of a different time domain type, the UE skips the time domain unit and selects a time domain unit of the same time domain type later, which is equivalent to the UE postponing a repeated transmission of the first uplink transmission.

[0168] In some embodiments, the first uplink transmission is determined to be transmitted on a time domain resource of a non-SBFD time domain type;

[0169] The terminal determines, according to the second message from the network-side device, a target time domain unit corresponding to the first uplink transmission, including:

[0170] The terminal determines, starting from the first time domain unit among the at least one time domain unit, N time domain units that meet a third preset condition as the target time domain units;

[0171] The third preset condition includes at least one of the following:

[0172] The target symbol is an uplink symbol or a flexible symbol not used for SS or PBCH;

[0173] X consecutive symbols starting from the target symbol are uplink symbols or flexible symbols not used for SS or PBCH, where X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission;

[0174] The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

[0175] This implementation is that the terminal starts from the first time domain unit of at least one time domain unit configured by the network side device, and searches for a target symbol (or X consecutive symbols starting from the target symbol) as a non-SBFD time domain unit not used for SS / PBCH as the target time domain unit.

[0176] Optionally, the first time domain unit includes at least one of the following:

[0177] a time domain unit indicated for feeding back first information, where the first information includes HARQ-ACK;

[0178] A time domain unit for sending second information determined according to a period and an offset of second information, where the second information includes at least one of SR and CSI.

[0179] Exemplarily, the target symbol is the first symbol (or starting symbol) corresponding to the PUCCH resource, for example, the first symbol (or starting symbol) corresponding to the first uplink transmission configured by startingSymbolIndex.

[0180] In this implementation, the UE needs to consider the time domain resource of the time domain type on which the first uplink transmission needs to be transmitted, so that the target time domain units determined all belong to the same time domain type. This approach can be understood as follows: when the UE is determining the target time domain unit corresponding to the first uplink transmission, if it encounters a time domain unit of a different time domain type, the UE skips the time domain unit and selects a time domain unit of the same time domain type later, which is equivalent to the UE postponing a repeated transmission of the first uplink transmission.

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

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

[0183] canceling the first uplink transmission;

[0184] canceling the second uplink transmission;

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

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

[0187] The above-mentioned first 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.

[0188] In some embodiments, when the first uplink transmission channel overlaps with the second uplink transmission channel, the terminal performs a first operation, including:

[0189] In a case where a channel of the first uplink transmission overlaps with a channel of the second uplink transmission, the terminal determines, according to at least one time domain unit configured in the second message, whether the first uplink transmission and the second uplink transmission are valid;

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

[0191] It should be noted that the network-side device sends a second message to the terminal to configure at least one time domain unit for the terminal. Since the at least one time domain unit includes an SBFD time domain unit, the second message can be understood as SBFD configuration information. In other words, the terminal determines whether the first uplink transmission and the second uplink transmission are valid based on the at least one time domain unit configured in the second message. This can be understood as the terminal determining whether the first uplink transmission and the second uplink transmission are valid based on the SBFD configuration information.

[0192] It is understood that the SBFD configuration information includes time domain configuration information, such as which time domain units are SBFD time domain units and which are non-SBFD time domain units. The SBFD configuration information may also include the frequency domain configuration corresponding to SBFD. The SBFD UL subband can be determined based on the SBFD frequency domain configuration. In this way, the validity of the uplink transmission can be determined based on whether the frequency domain resources of the uplink transmission fall within the SBFD UL subband range.

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

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

[0195] The terminal determines a target time domain type corresponding to an S-th repeated transmission of the first uplink transmission, where the time domain type includes an SBFD time domain type or a non-SBFD time domain type, and S is a positive integer less than or equal to N;

[0196] The terminal determines, according to the target time domain type, a transmission parameter for the S-th repeated transmission.

[0197] The terminal determines the target time domain type corresponding to the S-th repeated transmission of the first uplink transmission. It can be understood that the terminal determines whether the S-th repeated transmission of the first uplink transmission is an SBFD uplink transmission or a non-SBFD uplink transmission, where the SBFD uplink transmission represents an uplink transmission of the SBFD time domain type, and the non-SBFD uplink transmission represents an uplink transmission of the non-SBFD time domain type.

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

[0199] In some embodiments, the terminal determines, according to the target time domain type, the transmission parameters for the S-th repeated transmission, including:

[0200] The terminal receives a third message from the network-side device, where the third 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.

[0201] 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;

[0202] The terminal determines the transmission parameter associated with the target transmission configuration item as the transmission parameter for the S-th repeated transmission.

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

[0204] Exemplarily, for PUCCH transmission, the first transmission configuration item is PUCCH-configList1, 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.

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

[0206] It should be noted that, in addition to employing the scheme of "the terminal determining the target transmission configuration item from the first transmission configuration item and the second transmission configuration item based on the target time domain type" to determine the transmission parameters for the Sth repeated transmission, the terminal may also directly determine the transmission parameters for the Sth repeated transmission to reduce intermediate processes. For example, when the time domain unit in which the Sth repeated transmission occurs is configured as an SBFD time domain unit, the terminal determines that the target time domain type is the SBFD time domain type, and the terminal determines to use the transmission parameters in the first transmission configuration item for the Sth repeated transmission.

[0207] Optionally, the transmission parameter includes at least one of a power control parameter and spatial information (such as a beam parameter).

[0208] In addition, the transmission parameters may also include parameters such as transmission configuration, feedback timing set or transmission code rate.

[0209] In some embodiments, the terminal determines the target time domain type in a manner that includes at least one of the following:

[0210] In a case where the time domain unit where the S-th repeated transmission is located is configured as an SBFD time domain unit, the terminal determines that the target time domain type is the SBFD time domain type;

[0211] In a case where the time domain unit where the S-th repeated transmission is located is configured as a non-SBFD time domain unit, the terminal determines that the target time domain type is the non-SBFD time domain type;

[0212] In a case where all symbols in the S-th repeated transmission are SBFD symbols, the terminal determines that the target time domain type is the SBFD time domain type;

[0213] In a case where all symbols in the S-th repeated transmission are non-SBFD symbols, the terminal determines that the target time domain type is the non-SBFD time domain type;

[0214] In a case where the time domain unit where the S-th repetition transmission is located includes both SBFD symbols and non-SBFD symbols, the terminal determines the target time domain type according to a target mode;

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

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

[0217] Determining the target time domain type according to the time domain type of the symbol located at a predefined position in the time domain unit where the S-th repeated transmission is located;

[0218] The target time domain type is determined according to a predefined or default time domain type of the time domain unit where the S-th repeated transmission is located.

[0219] Exemplarily, if the time domain unit where the S-th repetition transmission is located is configured as an SBFD time domain unit, or the time domain unit where the S-th repetition transmission is located only contains SBFD symbols, the target time domain type is the SBFD type.

[0220] Exemplarily, if the time domain unit where the Sth repetition transmission is located is not configured as an SBFD time domain unit, or the time domain unit where the Sth repetition transmission is located only contains non-SBFD symbols, the target time domain type is a non-SBFD type.

[0221] For example, if the time domain unit in which the S-th repetition transmission occurs contains both SBFD symbols and non-SBFD symbols, the target time domain type is determined according to the following method:

[0222] 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;

[0223] 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;

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

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

[0226] The above is a related implementation method of determining the target time domain unit corresponding to the first uplink transmission by adopting a direct determination method. The above implementation method is applicable to PUCCH repetition transmission.

[0227] The following describes an implementation method for determining the target time domain unit corresponding to the first uplink transmission using an indirect determination method.

[0228] In some embodiments, the terminal determines, according to the second message from the network-side device, a target time domain unit corresponding to the first uplink transmission, including:

[0229] The terminal determines, based on the second message, whether the L time domain units after the third time domain unit are invalid time domain units, where the value of L is configured by a higher layer, and the third time domain unit is a downlink time domain unit semi-statically configured through higher layer signaling, and the invalid time domain unit is not used to transmit the first uplink transmission.

[0230] Exemplarily, if the higher layer configures numberOfInvalidSymbolsForDL-UL-Switching, the value of L is the value of numberOfInvalidSymbolsForDL-UL-Switching.

[0231] As mentioned above, the second message can be understood as a message carrying SBFD configuration information. Therefore, this implementation method is that the UE determines whether the L time domain units after the third time domain unit are invalid time domain units based on the SBFD configuration information, thereby indirectly determining the target time domain unit (or available time unit, available time domain unit) corresponding to the first uplink transmission.

[0232] Exemplarily, the UE may determine a time domain unit that is located after the third time domain unit and is not determined to be an invalid time domain unit as a target time domain unit of PUSCH repetition type B.

[0233] In this implementation, the UE can determine the available time unit for uplink repeated transmission according to the SBFD configuration information, which can improve the effectiveness of the uplink repeated transmission, thereby improving the effectiveness of the communication system.

[0234] In some embodiments, the terminal determines, according to the second message, whether L time domain units following the third time domain unit are invalid time domain units, including at least one of the following:

[0235] If the L time domain units following the third time domain unit are non-SBFD time domain units, the terminal determines that the L time domain units following the third time domain unit are invalid time domain units;

[0236] If the L time domain units following the third time domain unit are SBFD time domain units, the terminal determines that the L time domain units following the third time domain unit are not invalid time domain units;

[0237] If the L time domain units after the third time domain unit include non-SBFD time domain units and SBFD time domain units, the terminal determines that the non-SBFD time domain units are invalid time domain units and determines that the SBFD time domain units are not invalid time domain units.

[0238] For example, for a UE configured with SBFD, the invalid symbol definition for PUSCH repetition type B may be:

[0239] When the UE is configured with numberOfInvalidSymbolsForDL-UL-Switching, it determines whether the numberOfInvalidSymbolsForDL-UL-Switching symbols following the semi-statically configured DL symbol (that is, the DL symbol not configured as an SBFD symbol) are invalid symbols, based on whether the symbol following the semi-statically configured DL symbol (that is, the DL symbol not configured as an SBFD symbol) is a non-SBFD symbol or an SBFD symbol, where:

[0240] If the numberOfInvalidSymbolsForDL-UL-Switching symbols following the semi-statically configured DL symbol are non-SBFD symbols, then according to the relevant protocol, the corresponding numberOfInvalidSymbolsForDL-UL-Switching symbols are invalid symbols, that is, the UE cannot transmit PUSCH repetition type B on these symbols;

[0241] If the numberOfInvalidSymbolsForDL-UL-Switching symbols following the semi-statically configured DL symbol are SBFD symbols, the corresponding numberOfInvalidSymbolsForDL-UL-Switching symbols are not invalid symbols. That is, the UE can transmit PUSCH repetition type B on these symbols;

[0242] If the numberOfInvalidSymbolsForDL-UL-Switching symbols after the semi-statically configured DL symbol include non-SBFD symbols and SBFD symbols, the non-SBFD symbols in the corresponding numberOfInvalidSymbolsForDL-UL-Switching symbols are invalid symbols, and the SBFD symbols in the corresponding numberOfInvalidSymbolsForDL-UL-Switching symbols are not invalid symbols, that is, the UE can transmit PUSCH repetition type B on the SBFD symbols in the numberOfInvalidSymbolsForDL-UL-Switching symbols.

[0243] The above is a related implementation method of determining the target time domain unit corresponding to the first uplink transmission by adopting an indirect determination method. The above implementation method is applicable to PUSCH repetition type B transmission.

[0244] In order to better understand the technical solutions of the present application, specific embodiments are provided below to exemplify the PUCCH repetition transmission solution and the PUSCH repetition type B transmission solution of the present application.

[0245] Example 1: PUCCH repetition transmission scheme

[0246] In the related art, when PUCCH is not configured for repeated transmission, the UE determines the time slot / sub-time slot for PUCCH transmission according to the following method. For example, for HARQ-ACK, the time slot / sub-time slot for PUCCH transmission is determined according to the k1 field in the scheduling / activation DCI (or the higher-level configuration (when the DCI does not contain the k1 field)). For example, the k1 field indicates "PDSCH-to-HARQ-ACK feedback timing" and the UL time slot / sub-time slot n corresponding to the end position (or end DL time slot) of the PDSCH is determined to be n+k1. For CSI / SR, the UE determines the transmission time slot within each period based on the period and offset corresponding to the CSI / SR. For example, for SR, if its period is greater than one time slot, the UE determines the time slot where an SR PUCCH transmission opportunity is located. satisfy where n f is the frame number, is the number of slots contained in a frame (when SCS is μ), SR OFFSET is the offset of SR, SRPERIODICITY is the SR period.

[0247] In related technologies, when PUCCH is configured for repeated transmission, the base station can configure the per PUCCH format or per PUCCH resource, such as the parameter pucch-RepetitionNrofSlots or nrofSlots. The UE can determine the PUCCH transmission time slot based on the semi-static uplink and downlink configuration.

[0248] This embodiment provides a method for the UE to determine the time domain resource type (which may be referred to as the time domain type) for PUCCH transmission and the time unit for repeated PUCCH transmission when the UE is also configured with SBFD time domain resources.

[0249] 1. The UE determines the time domain type of the PUCCH transmission, that is, the UE determines whether the PUCCH transmission is SBFD transmission (that is, the time domain type of the PUCCH transmission is SBFD type) or non-SBFD transmission (that is, the time domain type of the PUCCH transmission is non-SBFD type)

[0250] Here, the time domain resources corresponding to the SBFD type may include, for example, SBFD symbols / time slots / sub-time slots.

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

[0252] Method 1-1: Determine the time domain type of PUCCH transmission 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.

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

[0254] Methods 1-3: Determine the time domain type for PUCCH transmission based on the information or pre-configured information corresponding to the signal carried by the PUCCH resource. For PUCCH carrying HARQ-ACK, the time domain type is determined based on the codebook in which the HARQ-ACK is located, such as the codebook in which the DCI is scheduled or the RRC configuration is configured. For CSI / SR, the higher layers configure the transmission time domain type corresponding to the CSI / SR (e.g., per CSI / SR configuration).

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

[0256] Method 2-1: Determine the time domain type of PUCCH transmission based on the type of time domain resource where the nominal first transmission is located. Specifically:

[0257] For HARQ-ACK / PUSCH, the time domain type of PUCCH transmission is the type corresponding to the time unit in which the UE is instructed to transmit HARQ-ACK / PUSCH. As shown in Figure 4, PDSCH1 and PDSCH2 are instructed to feedback HARQ-ACK in time slot n+5 and time slot n+7, respectively. According to the SBFD configuration, time slot n+5 is an SBFD slot and time slot n+7 is a non-SBFD slot. Therefore, the UE determines the time domain types of PUCCH1 and PUCCH2 to be SBFD and non-SBFD, respectively.

[0258] For SR / CSI / CG-PUSCH / SRS, the time domain type of PUCCH transmission is the type of time unit determined by the UE based on the SR / CSI / CG-PUSCH / SRS period and 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. 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.

[0259] Method 2-2: Determine the time domain type of PUCCH transmission based on the type of time domain resources where the first actual transmission occurs.

[0260] For example, the UE determines the time domain resources for the first actual transmission according to the following method:

[0261] Starting from time unit A, at least one of the following conditions must be met:

[0262] The first symbol corresponding to the PUCCH / PUSCH / SRS resource (e.g., configured by startingSymbolIndex) is not an SS / PBCH symbol (the symbol may be a UL symbol, a flexible symbol, or an SBFD symbol);

[0263] X consecutive symbols that are not SS / PBCH, starting from the first symbol corresponding to the PUCCH / PUSCH / SRS resource (these X symbols can be UL symbols, flexible symbols, or SBFD symbols), where X is greater than or equal to the number of symbols corresponding to the PUCCH / PUSCH / SRS resource (for example, configured by nrofsymbols or indicated by TDRA)

[0264] time unit.

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

[0266] Case 1: For HARQ-ACK, time unit A is the time unit in which the UE is instructed to feedback HARQ-ACK;

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

[0268] For method 2-2, since the UE needs to determine the time domain type based on the starting symbol and symbol position of the PUCCH, this method is applicable to situations where the UE does not need to determine the starting symbol and symbol position of a PUCCH resource based on the time domain type, for example, for SBFD type and non-SBFD type PUCCH transmissions, the time domain resource configuration is common / the same, or for SBFD type and non-SBFD type PUCCH transmissions, the time domain position corresponding to the same PUCCH resource indicator (PUCCH Resource Indicator, PRI) / resource ID is the same, or the SBFD configuration method is slot-level.

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

[0270] 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 at least one of the time domain resource location (e.g., the time domain resource where the transmission occurs) and transmission parameters (e.g., power, beamforming) for the uplink transmission. That is, the UE determines at least one of the time domain resource location and transmission parameters for the uplink transmission based on the determined time domain type of the uplink transmission.

[0271] 2. The UE determines the time to transmit the PUCCH according to the SBFD time domain configuration. Time units

[0272] Solution 1: PUCCH repetition is only transmitted in time units of the same time domain type (such as SBFD time units (SBFD time units for short) and non-SBFD time units (non-SBFD time units for short)). When the time domain resources of a PUCCH repetition fall into time units of different time domain types, the UE cancels the PUCCH repetition.

[0273] In this solution, the UE determines the transmission of the PUCCH The time units are:

[0274] Starting from time unit A, at least one of the following conditions must be met:

[0275] The first symbol corresponding to the PUCCH resource (e.g., configured by startingSymbolIndex) is not an SS / PBCH symbol (the symbol may be a UL symbol, a flexible symbol, or an SBFD symbol);

[0276] Starting from the first symbol corresponding to the PUCCH resource, X consecutive symbols that are not SS / PBCH (the X symbols can be UL symbols, flexible symbols, or SBFD symbols), where X is greater than or equal to the number of symbols corresponding to the PUCCH resource (e.g., configured by nrofsymbols) time unit.

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

[0278] Case 1: For HARQ-ACK, time unit A is the time unit that the UE is instructed / triggered to feedback HARQ-ACK, for example, slot / sub-slot n+k, where n is the UL slot / sub-slot corresponding to the PDSCH end position / time slot, and k is the PDSCH-to-HARQ-ACK feedback timing configured by higher layers or indicated by DCI;

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

[0280] Optionally, if the UE determines to transmit the above PUCCH in the SBFD time unit (for example, the UE determines that the PUCCH is the PUCCH transmitted in the SBFD time unit according to a certain indication / configuration / rule, see the relevant method provided in the first part of this embodiment for details), then for the above time units. If a certain time unit is a non-SBFD time unit, that is, the time unit of the PUCCH overlaps with the non-SBFD time unit, the UE does not transmit the PUCCH in the time unit.

[0281] Optionally, the UE counts this time unit into 's count.

[0282] Optionally, if the UE determines to transmit the above PUCCH in a non-SBFD time unit (for example, the UE determines that the PUCCH is a PUCCH transmitted in a non-SBFD time unit according to a certain indication / configuration / rule, see the relevant method provided in the first part of this embodiment for details), then for the above time units. If a certain time unit is an SBFD time unit, that is, the time unit of the PUCCH overlaps with the SBFD time unit, the UE does not transmit the PUCCH in the time unit.

[0283] Optionally, the UE counts this time unit into 's count.

[0284] For example, as shown in FIG6 , the UE is instructed to feedback the HARQ-ACK of PDSCH 1 in slot n+5. The UE determines that the PUCCH resource for its feedback HARQ-ACK is configured with repeated transmission. Assuming that the number of repeated transmissions is If the value is 4, as shown in Figure 6, the UE determines that the time slots for repeated PUCCH transmission are slot n+5, slot n+6, slot n+7, and slot n+10. Since slots n+6 and n+7 are non-SBFD slots, the UE determines that the PUCCH can only be transmitted in SBFD time domain resources. Therefore, the UE cancels the repeated transmission of the PUCCH in slots n+6 and slot n+7 and only repeats the PUCCH in slots n+5 and slot n+10. In other words, the UE only transmits rep1 and rep4, and does not transmit rep2 and rep3.

[0285] It should be noted that when the above-mentioned PUCCH is repeatedly transmitted, there may be channel overlap between the PUCCH transmission and other uplink transmissions, for example, there is channel overlap between the PUCCH transmission and other PUCCH transmissions, or there is channel overlap between the PUCCH transmission and PUSCH transmission.

[0286] In the related art, when a PUCCH configured for repeated transmission overlaps with the time domain resources of other PUCCHs or PUSCHs (especially, here refers to the PUSCH that cannot be transmitted simultaneously with the PUCCH), the UE handles the transmission overlap on a per-repetition basis. Specifically, the UE determines which channel to transmit based on the priority of the PUCCH (such as the priority index, with priority indices 0 and 1 representing low priority and high priority, respectively) or the priority of the content carried by the PUCCH (such as CSI). For example, when channels with different priority indices overlap, the UE discards the transmission with a priority index of 0; when channels with the same priority index overlap, if PUCCH and PUCCH overlap, the UE determines the channel to transmit based on the order of HARQ-ACK priority being higher than SR, SR priority being higher than CSI with high priority (CSI with high priority), and CSI with high priority being higher than CSI with low priority (CSI with low priority) (i.e., the order of HARQ-ACK>SR>CSI with high priority>CSI with low priority). When PUCCH overlaps with PUSCH, the UE drops PUSCH transmission.

[0287] In this embodiment, the UE may first perform the steps in the above-described solution 1, and then perform overlap processing (such as intra-UE multiplexing, prioritization, cancellation, etc.). In other words, the UE first determines the time unit for PUCCH retransmission based on the SBFD configuration, and then performs overlap processing. The UE may also first perform overlap processing and then perform the steps in the above-described solution 1.

[0288] As an implementation method, for PUCCH transmission, the UE first determines whether a repetition can be transmitted based on the time domain type of the time domain resource in which it is located, and then performs overlapping processing between transmissions. For example, in Figure 6, because the time domain type of the time domain resource in which rep2 and rep3 are located is different from the time domain type configured / indicated / specified by the PUCCH, the UE cannot transmit rep2 and rep3. In this case, the UE first cancels rep2 and rep3 and then performs overlapping processing between transmissions. Since rep2 and rep3 are canceled, in the subsequent overlapping processing, it is equivalent to rep2 and rep3 not existing, and the problem of rep2 and rep3 overlapping with other uplink transmissions does not exist accordingly. This method can avoid unnecessary discarding.

[0289] As another embodiment, for PUCCH transmission, the UE determines the time unit for transmitting PUCCH Afterwards, overlap processing (such as intra-UE multiplexing) is performed. After processing, if the time domain resources of a PUCCH repetition do not meet the requirements, the UE cancels the repetition. In this method, the UE finally determines whether the uplink channel can be transmitted, which is relatively simple to implement.

[0290] Solution 2: PUCCH retransmission is performed only in time units of the same time domain type (such as SBFD time units and non-SBFD time units). When encountering time units of different types, the UE postpones PUCCH transmission.

[0291] Solution 2-1: If the UE determines to transmit the above PUCCH in the SBFD time unit (for example, the UE determines that the PUCCH is the PUCCH transmitted in the SBFD time unit according to certain instructions / configurations / rules, see the relevant methods provided in the first part of this embodiment for details), the UE determines the PUCCH transmission according to the following method: Time units:

[0292] Starting from time unit A, at least one of the following conditions must be met:

[0293] The first symbol corresponding to the PUCCH resource (e.g., configured by startingSymbolIndex) is not an SS / PBCH symbol (the symbol is an SBFD symbol);

[0294] Starting from the first symbol corresponding to the PUCCH resource, X consecutive symbols that are not SS / PBCH (the X symbols are all SBFD symbols), where X is greater than or equal to the number of symbols corresponding to the PUCCH resource (for example, configured by nrofsymbols) time unit.

[0295] The meaning of the time unit A here is the same as that of the time unit A in scheme 1.

[0296] Solution 2-2: If the UE determines to transmit the above PUCCH in a non-SBFD time unit (for example, the UE determines that the PUCCH is transmitted in a non-SBFD time unit according to certain instructions / configurations / rules, see the relevant methods provided in the first part of this embodiment for details), the UE determines the PUCCH transmission time according to the following method: Time units:

[0297] Starting from time unit A, at least one of the following conditions must be met:

[0298] The first symbol corresponding to the PUCCH resource (e.g., configured by startingSymbolIndex) is not an SS / PBCH symbol (the symbol is a UL symbol or a flexible symbol);

[0299] Starting from the first symbol corresponding to the PUCCH resource, X consecutive symbols that are not SS / PBCH (the X symbols are UL symbols or flexible symbols), where X is greater than or equal to the number of symbols corresponding to the PUCCH resource (e.g., configured by nrofsymbols) time unit.

[0300] The meaning of the time unit A here is the same as that of the time unit A in scheme 1.

[0301] For example, as shown in FIG7 , the UE is instructed to feedback the HARQ-ACK of PDSCH 1 in slot n+5. The UE determines that the PUCCH resource for its feedback HARQ-ACK is configured with repeated transmission. Assuming that the number of repeated transmissions is 7 , the UE determines that the time domain type for repeated PUCCH transmission is the SBFD type, and the UE determines that the time slots for transmitting the PUCCH are slot n+5, slot n+10, slot n+11, and slot n+12.

[0302] It should be noted that, in this embodiment, the term "non-SS / PBCH symbols" can be understood as: (1) non-SS / PBCH UL symbols or flexible symbols, which refer to symbols configured as UL / flexible and not configured for SS / PBCH transmission; (2) non-SS / PBCH SBFD symbols, which refer to symbols configured as SBFD and not configured for SS / PBCH transmission. If SBFD symbols can only be configured as non-SS / PBCH symbols, then when a symbol is configured as an SS / PBCH symbol, the symbol satisfies the requirement of being a non-SS / PBCH SBFD symbol.

[0303] Optionally, this embodiment is applicable to an asymmetric spectrum.

[0304] 3. Method for UE to determine power control parameters or spatial information during PUCCH repetition

[0305] The base station configures or activates two sets of power control parameters or spatial information for the UE's PUCCH transmission (for example, the base station activates two sets of spatial information, such as PUCCH-SpatialRelationInfo, for one PUCCH resource through MAC CE), and sets two sets of power control parameters (or spatial information) for the UE to transmit PUCCH in SBFD and non-SBFD, respectively. For each PUCCH repetition, the first set of power control parameters (or spatial information) and the second set of power control parameters (or spatial information) are used respectively according to whether the time domain type of the time domain resource where each repetition is located is SBFD or non-SBFD. For example, the base station configures multiple PUCCH-SpatialRelationInfo for UE PUCCH transmission through PUCCH-config, and activates two PUCCH-SpatialRelationInfo for one PUCCH resource (per resource ID) through MAC CE, respectively for the UE to transmit PUCCH in SBFD and non-SBFD. Optionally, the base station configures the mapping relationship between the PUCCH power control parameter (such as p0-PUCCH-Value) and PUCCH-SpatialRelationInfo through higher-layer parameters. The UE determines the corresponding power control parameter based on the PUCCH-SpatialRelationInfo used in each repetition.

[0306] Specifically, when a UE repeatedly transmits a PUCCH in multiple time units, if the PUCCH includes two sets of power control parameters or two sets of spatial information, the UE determines the parameters for repeated PUCCH transmission according to the following method:

[0307] If the time unit in which the PUCCH is repeated is an SBFD time unit, the first set of parameters is used;

[0308] If the time unit in which the PUCCH is repeated is a non-SBFD time unit, the second set of parameters is used.

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

[0310] In this embodiment, the UE can determine the time unit and transmission parameters of the PUCCH repetition transmission according to the SBFD configuration, which can improve the effectiveness of the PUCCH repetition transmission, thereby improving the effectiveness of the communication system.

[0311] Example 2: PUSCH repetition type B transmission solution

[0312] In this embodiment, when the UE is configured with numberOfInvalidSymbolsForDL-UL-Switching, the UE may determine, based on whether the semi-statically configured DL symbol is followed by an SBFD symbol or a non-SBFD symbol, whether the numberOfInvalidSymbolsForDL-UL-Switching symbols following the semi-statically configured DL symbol can be used for PUCH repetition type B transmission. Specifically, if the numberOfInvalidSymbolsForDL-UL-Switching symbols following the semi-statically configured DL symbol are SBFD symbols, then these numberOfInvalidSymbolsForDL-UL-Switching symbols can be used for PUCH repetition type B transmission; if the numberOfInvalidSymbolsForDL-UL-Switching symbols following the semi-statically configured DL symbol are non-SBFD symbols, then these numberOfInvalidSymbolsForDL-UL-Switching symbols cannot be used for PUCH repetition type B transmission.

[0313] As shown in Figure 8, assuming that the UE is configured with PUSCH repetition type B, where PUSCH is scheduled to transmit PUSCH in slot n-1, its TDRA indicates that the starting symbol of a PUSCH is the 10th symbol in slot n-1, the length is 4 symbols, and the number of repetitions is 4, then according to the time domain resource determination rule of PUSCH repetition type B, the UE determines the positions of the first to fourth nominal repetitions as shown in Figure 8 (rep1 represents the first, and so on), wherein the first and fourth nominal repetitions do not overlap with any invalid symbols and can be transmitted directly, the second nominal repetition overlaps with the semi-statically configured DL symbol (i.e., the symbol represented by D in the figure). In the related art, if the UE does not configure numberOfInvalidSymbolsForDL-UL-Switching, the second nominal repetition is divided into two parts, the first three symbols cannot be transmitted, and the last symbol is discarded. The third nominal repetition overlaps with the flexible symbol (i.e., the symbol represented by F in the figure) and the UL symbol (i.e., the symbol represented by U in the figure). If the UE is not configured with numberOfInvalidSymbolsForDL-UL-Switching, it can be transmitted directly. If the UE is configured with numberOfInvalidSymbolsForDL-UL-Switching, the UE does not transmit the nominal repetition because the symbol where the third nominal repetition is located is indicated as an invalid symbol.

[0314] As shown in Figure 9, if the UE is configured with SBFD symbols, assuming that the four symbols after the semi-static DL symbol are configured as SBFD symbols by semi-static signaling, when the UE determines the invalid symbols for PUSCH repetition type B, the numberOfInvalidSymbolsForDL-UL-Switching symbols after the semi-static DL symbol in Figure 9 can still be used to transmit PUSCH repetition type B. Therefore, the third nominal repetition can be transmitted.

[0315] In this embodiment, the UE can determine the available time unit for PUSCH repetition type B transmission according to the SBFD configuration, which can improve the effectiveness of PUSCH repetition type B transmission, thereby improving the effectiveness of the communication system.

[0316] In summary, the embodiments of the present application enable the terminal to more reasonably determine the time domain resource location of uplink repeated transmission under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink repeated transmission under the SBFD configuration, thereby ensuring the communication performance of the terminal.

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

[0318] 10 , an embodiment of the present application further provides an uplink transmission device that can be applied to a terminal. As shown in FIG10 , the uplink transmission device 1000 includes:

[0319] A receiving module 1001 is configured to receive a first message from a network-side device, where the first message is used to instruct to repeat N times a first uplink transmission, where N is a positive integer;

[0320] The first processing module 1002 is used to determine the target time domain unit corresponding to the first uplink transmission according to a second message from the network side device, where the second message is used to configure at least one time domain unit, and the at least one time domain unit includes a sub-band full-duplex (SBFD) time domain unit.

[0321] Optionally, the first processing module is specifically configured to:

[0322] Starting from a first time domain unit among the at least one time domain unit, determining N time domain units that meet a first preset condition as the target time domain units;

[0323] The first preset condition includes at least one of the following:

[0324] The target symbol is a symbol not used for the synchronization signal SS or the physical broadcast channel PBCH;

[0325] The target symbol is a UL symbol, a flexible symbol, or a SBFD symbol;

[0326] The X consecutive symbols starting from the target symbol are symbols not used for SS or PBCH;

[0327] X consecutive symbols starting from the target symbol are UL symbols, flexible symbols or SBFD symbols;

[0328] Wherein, X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission;

[0329] The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

[0330] Optionally, the first uplink transmission is determined to be transmitted on a time domain resource of an SBFD time domain type;

[0331] The first processing module is specifically configured to:

[0332] Starting from a first time domain unit in the at least one time domain unit, determining N time domain units that meet a second preset condition as the target time domain units;

[0333] The second preset condition includes at least one of the following:

[0334] The target symbol is the SBFD symbol not used for SS or PBCH;

[0335] The target symbol is the SBFD symbol;

[0336] The consecutive X symbols starting from the target symbol are SBFD symbols not used for SS or PBCH;

[0337] The X consecutive symbols starting from the target symbol are SBFD symbols;

[0338] Wherein, X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission;

[0339] The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

[0340] Optionally, the first uplink transmission is determined to be transmitted on a time domain resource of a non-SBFD time domain type;

[0341] The first processing module is specifically configured to:

[0342] Starting from a first time domain unit in the at least one time domain unit, determining N time domain units that meet a third preset condition as the target time domain units;

[0343] The third preset condition includes at least one of the following:

[0344] The target symbol is an uplink symbol or a flexible symbol not used for SS or PBCH;

[0345] X consecutive symbols starting from the target symbol are uplink symbols or flexible symbols not used for SS or PBCH, where X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission;

[0346] The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

[0347] Optionally, the first time domain unit includes at least one of the following:

[0348] a time domain unit indicated for feeding back first information, where the first information includes a hybrid automatic repeat request acknowledgement HARQ-ACK;

[0349] A time domain unit for sending second information is determined according to a period and an offset of second information, where the second information includes at least one of a scheduling request SR and channel state information CSI.

[0350] Optionally, the target time domain unit further satisfies at least one of the following:

[0351] The symbols used for the first uplink transmission in the target time domain unit are all SBFD symbols or all non-SBFD symbols;

[0352] The SBFD uplink subband of the target time domain unit covers the frequency domain resources of the first uplink transmission.

[0353] Optionally, the first uplink transmission is determined to be transmitted on a time domain resource of a target time domain type, and the target time domain type includes an SBFD time domain type or a non-SBFD time domain type;

[0354] The device further comprises:

[0355] a second processing module, configured to cancel transmission of the first uplink transmission in the second time domain unit if the time domain type of the second time domain unit of the first uplink transmission does not match the target time domain type;

[0356] The second time domain unit is at least one time domain unit in the target time domain unit corresponding to the first uplink transmission.

[0357] Optionally, the device further comprises:

[0358] The third processing module is configured to count the number of the second time domain units into the total number of the target time domain units.

[0359] Optionally, the device further comprises:

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

[0361] canceling the first uplink transmission;

[0362] canceling the second uplink transmission;

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

[0364] Optionally, the fourth processing module is specifically configured to:

[0365] 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 at least one time domain unit configured by the second message;

[0366] In a case where it is determined that the first uplink transmission and the second uplink transmission are valid, the first operation is performed.

[0367] Optionally, the device further comprises:

[0368] A fifth processing module, configured to determine a target time domain type corresponding to an S-th repeated transmission of the first uplink transmission, where the time domain type includes an SBFD time domain type or a non-SBFD time domain type, and S is a positive integer less than or equal to N;

[0369] The sixth processing module is used to determine the transmission parameters of the S-th repeated transmission according to the target time domain type.

[0370] Optionally, the sixth processing module includes:

[0371] a receiving unit, configured to receive a third message from the network-side device, the third message including a first transmission configuration item and a second transmission configuration item, the first transmission configuration item being mapped to the SBFD time domain type, and the second transmission configuration item being mapped to the non-SBFD time domain type;

[0372] 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;

[0373] The second processing unit is configured to determine the transmission parameter associated with the target transmission configuration item as the transmission parameter for the S-th repeated transmission.

[0374] Optionally, the transmission parameter includes at least one of a power control parameter and space information.

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

[0376] When the time domain unit where the S-th repeated transmission is located is configured as an SBFD time domain unit, determining the target time domain type to be the SBFD time domain type;

[0377] When the time domain unit where the S-th repeated transmission is located is configured as a non-SBFD time domain unit, determining the target time domain type to be the non-SBFD time domain type;

[0378] When all symbols in the S-th repeated transmission are SBFD symbols, determining the target time domain type to be the SBFD time domain type;

[0379] When all symbols in the S-th repeated transmission are non-SBFD symbols, determining the target time domain type to be the non-SBFD time domain type;

[0380] When the time domain unit where the S-th repetition transmission is located includes both SBFD symbols and non-SBFD symbols, determining the target time domain type according to a target mode;

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

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

[0383] Determining the target time domain type according to the time domain type of the symbol located at a predefined position in the time domain unit where the S-th repeated transmission is located;

[0384] The target time domain type is determined according to a predefined or default time domain type of the time domain unit where the S-th repeated transmission is located.

[0385] Optionally, the first processing module is specifically configured to:

[0386] According to the second message, determine whether the L time domain units located after the third time domain unit are invalid time domain units, the value of L is configured by the upper layer, the third time domain unit is a downlink time domain unit semi-statically configured through high-layer signaling, and the invalid time domain unit is not used to transmit the first uplink transmission.

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

[0388] If the L time domain units following the third time domain unit are non-SBFD time domain units, determining that the L time domain units following the third time domain unit are invalid time domain units;

[0389] If the L time domain units following the third time domain unit are SBFD time domain units, determining that the L time domain units following the third time domain unit are not invalid time domain units;

[0390] If the L time domain units after the third time domain unit include non-SBFD time domain units and SBFD time domain units, the non-SBFD time domain units are determined to be invalid time domain units, and the SBFD time domain units are determined not to be invalid time domain units.

[0391] In summary, the embodiments of the present application enable the terminal to more reasonably determine the time domain resource location of uplink repeated transmission under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink repeated transmission under the SBFD configuration, thereby ensuring the communication performance of the terminal.

[0392] The uplink transmission device 1000 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.

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

[0394] FIG11 is a flowchart of an uplink transmission configuration method provided in an embodiment of the present application. As shown in FIG11 , the uplink transmission configuration method includes the following steps:

[0395] Step 1101: The network-side device sends a first message to the terminal, where the first message is used to instruct the terminal to repeat N times of the first uplink transmission, where N is a positive integer.

[0396] Step 1102: The network-side device sends a second message to the terminal, where the second message is used to configure at least one time domain unit, where the at least one time domain unit includes a sub-band full-duplex (SBFD) time domain unit.

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

[0398] In summary, the embodiments of the present application enable the terminal to more reasonably determine the time domain resource location of uplink repeated transmission under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink repeated transmission under the SBFD configuration, thereby ensuring the communication performance of the terminal.

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

[0400] 12, 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 FIG12, the uplink transmission configuration device 1200 includes:

[0401] A first sending module 1201 is configured to send a first message to a terminal, where the first message is used to instruct repeated transmission of a first uplink transmission N times, where N is a positive integer;

[0402] The second sending module 1202 is configured to send a second message to the terminal, where the second message is used to configure at least one time domain unit, where the at least one time domain unit includes a sub-band full-duplex (SBFD) time domain unit.

[0403] In summary, the embodiments of the present application enable the terminal to more reasonably determine the time domain resource location of uplink repeated transmission under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink repeated transmission under the SBFD configuration, thereby ensuring the communication performance of the terminal.

[0404] The uplink transmission configuration device 1200 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.

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

[0406] Optionally, as shown in Figure 13, an embodiment of the present application further provides a communication device 1300, including a processor 1301 and a memory 1302, wherein the memory 1302 stores a program or instruction that can be run on the processor 1301. For example, when the communication device 1300 is a terminal, the program or instruction is executed by the processor 1301 to implement the various steps of the method embodiments of Figures 3 to 9, and can achieve the same technical effects. When the communication device 1300 is a network-side device, the program or instruction is executed by the processor 1301 to implement the various steps of the method embodiment of Figure 11 above, and can achieve the same technical effects. To avoid repetition, they are not described here.

[0407] The present application also provides a terminal embodiment, 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 embodiments shown in Figures 3 to 9. This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, Figure 14 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0408] The terminal 1400 includes but is not limited to: a radio frequency unit 1401, a network module 1402, an audio output unit 1403, an input unit 1404, a sensor 1405, a display unit 1406, a user input unit 1407, an interface unit 1408, a memory 1409 and at least some of the components of the processor 1410.

[0409] Those skilled in the art will appreciate that the terminal 1400 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1410 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG14 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.

[0410] It should be understood that in an embodiment of the present application, the input unit 1404 may include a graphics processing unit (GPU) 14041 and a microphone 14042, and the graphics processor 14041 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 1406 may include a display panel 14061, and the display panel 14061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1407 includes a touch panel 14071 and at least one of other input devices 14072. The touch panel 14071 is also called a touch screen. The touch panel 14071 may include two parts: a touch detection device and a touch controller. Other input devices 14072 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.

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

[0412] The memory 1409 can be used to store software programs or instructions and various data. The memory 1409 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 1409 may include a volatile memory or a non-volatile memory, or the memory 1409 may include both volatile and non-volatile memory. 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. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1409 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0413] Processor 1410 may include one or more processing units. Optionally, processor 1410 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 1410.

[0414] The radio frequency unit 1401 is used for:

[0415] receiving a first message from a network-side device, where the first message is used to instruct repeated transmission of a first uplink transmission N times, where N is a positive integer;

[0416] The processor 1410 is configured to:

[0417] A target time domain unit corresponding to the first uplink transmission is determined according to a second message from a network-side device, where the second message is used to configure at least one time domain unit, and the at least one time domain unit includes a sub-band full-duplex (SBFD) time domain unit.

[0418] Optionally, the processor 1410 is further configured to:

[0419] Starting from a first time domain unit among the at least one time domain unit, determining N time domain units that meet a first preset condition as the target time domain units;

[0420] The first preset condition includes at least one of the following:

[0421] The target symbol is a symbol not used for the synchronization signal SS or the physical broadcast channel PBCH;

[0422] The target symbol is a UL symbol, a flexible symbol, or a SBFD symbol;

[0423] The X consecutive symbols starting from the target symbol are symbols not used for SS or PBCH;

[0424] X consecutive symbols starting from the target symbol are UL symbols, flexible symbols or SBFD symbols;

[0425] Wherein, X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission;

[0426] The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

[0427] Optionally, the first uplink transmission is determined to be transmitted on a time domain resource of an SBFD time domain type;

[0428] The processor 1410 is further configured to:

[0429] Starting from a first time domain unit in the at least one time domain unit, determining N time domain units that meet a second preset condition as the target time domain units;

[0430] The second preset condition includes at least one of the following:

[0431] The target symbol is the SBFD symbol not used for SS or PBCH;

[0432] The target symbol is the SBFD symbol;

[0433] The consecutive X symbols starting from the target symbol are SBFD symbols not used for SS or PBCH;

[0434] The X consecutive symbols starting from the target symbol are SBFD symbols;

[0435] Wherein, X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission;

[0436] The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

[0437] Optionally, the first uplink transmission is determined to be transmitted on a time domain resource of a non-SBFD time domain type;

[0438] The processor 1410 is further configured to:

[0439] Starting from a first time domain unit in the at least one time domain unit, determining N time domain units that meet a third preset condition as the target time domain units;

[0440] The third preset condition includes at least one of the following:

[0441] The target symbol is an uplink symbol or a flexible symbol not used for SS or PBCH;

[0442] X consecutive symbols starting from the target symbol are uplink symbols or flexible symbols not used for SS or PBCH, where X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission;

[0443] The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

[0444] Optionally, the first time domain unit includes at least one of the following:

[0445] a time domain unit indicated for feeding back first information, where the first information includes a hybrid automatic repeat request acknowledgement HARQ-ACK;

[0446] A time domain unit for sending second information is determined according to a period and an offset of second information, where the second information includes at least one of a scheduling request SR and channel state information CSI.

[0447] Optionally, the target time domain unit further satisfies at least one of the following:

[0448] The symbols used for the first uplink transmission in the target time domain unit are all SBFD symbols or all non-SBFD symbols;

[0449] The SBFD uplink subband of the target time domain unit covers the frequency domain resources of the first uplink transmission.

[0450] Optionally, the first uplink transmission is determined to be transmitted on a time domain resource of a target time domain type, and the target time domain type includes an SBFD time domain type or a non-SBFD time domain type;

[0451] The processor 1410 is further configured to:

[0452] When the time domain type of the second time domain unit of the first uplink transmission does not match the target time domain type, canceling the transmission of the first uplink transmission in the second time domain unit;

[0453] The second time domain unit is at least one time domain unit in the target time domain unit corresponding to the first uplink transmission.

[0454] Optionally, the processor 1410 is further configured to:

[0455] The number of the second time domain units is counted into the total number of the target time domain units.

[0456] Optionally, the processor 1410 is further configured to:

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

[0458] canceling the first uplink transmission;

[0459] canceling the second uplink transmission;

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

[0461] Optionally, the processor 1410 is further configured to:

[0462] 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 at least one time domain unit configured by the second message;

[0463] In a case where it is determined that the first uplink transmission and the second uplink transmission are valid, the first operation is performed.

[0464] Optionally, the processor 1410 is further configured to:

[0465] Determine a target time domain type corresponding to an S-th repeated transmission of the first uplink transmission, where the time domain type includes an SBFD time domain type or a non-SBFD time domain type, and S is a positive integer less than or equal to N;

[0466] Determine, according to the target time domain type, a transmission parameter for the S-th repeated transmission.

[0467] Optionally, the radio frequency unit 1401 is further configured to:

[0468] receiving a third message from the network-side device, the third message including a first transmission configuration item and a second transmission configuration item, the first transmission configuration item being mapped to the SBFD time domain type, and the second transmission configuration item being mapped to the non-SBFD time domain type;

[0469] The processor 1410 is further configured to:

[0470] 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;

[0471] The transmission parameters associated with the target transmission configuration item are determined as the transmission parameters for the S-th repeated transmission.

[0472] Optionally, the transmission parameter includes at least one of a power control parameter and space information.

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

[0474] When the time domain unit where the S-th repeated transmission is located is configured as an SBFD time domain unit, determining the target time domain type to be the SBFD time domain type;

[0475] When the time domain unit where the S-th repeated transmission is located is configured as a non-SBFD time domain unit, determining the target time domain type to be the non-SBFD time domain type;

[0476] When all symbols in the S-th repeated transmission are SBFD symbols, determining the target time domain type to be the SBFD time domain type;

[0477] When all symbols in the S-th repeated transmission are non-SBFD symbols, determining the target time domain type to be the non-SBFD time domain type;

[0478] When the time domain unit where the S-th repetition transmission is located includes both SBFD symbols and non-SBFD symbols, determining the target time domain type according to a target mode;

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

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

[0481] Determining the target time domain type according to the time domain type of the symbol located at a predefined position in the time domain unit where the S-th repeated transmission is located;

[0482] The target time domain type is determined according to a predefined or default time domain type of the time domain unit where the S-th repeated transmission is located.

[0483] Optionally, the processor 1410 is further configured to:

[0484] According to the second message, determine whether the L time domain units located after the third time domain unit are invalid time domain units, the value of L is configured by the upper layer, the third time domain unit is a downlink time domain unit semi-statically configured through high-layer signaling, and the invalid time domain unit is not used to transmit the first uplink transmission.

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

[0486] If the L time domain units following the third time domain unit are non-SBFD time domain units, determining that the L time domain units following the third time domain unit are invalid time domain units;

[0487] If the L time domain units following the third time domain unit are SBFD time domain units, determining that the L time domain units following the third time domain unit are not invalid time domain units;

[0488] If the L time domain units after the third time domain unit include non-SBFD time domain units and SBFD time domain units, the non-SBFD time domain units are determined to be invalid time domain units, and the SBFD time domain units are determined not to be invalid time domain units.

[0489] In summary, the embodiments of the present application enable the terminal to more reasonably determine the time domain resource location of uplink repeated transmission under the SBFD configuration, thereby enabling the terminal to more reasonably perform uplink repeated transmission under the SBFD configuration, thereby ensuring the communication performance of the terminal.

[0490] 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 9, and achieve the same or corresponding technical effects. To avoid repetition, they will not be repeated here.

[0491] 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 FIG11 . 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.

[0492] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 15 , the network-side device 1500 includes an antenna 151, a radio frequency device 152, a baseband device 153, a processor 154, and a memory 155. The antenna 151 is connected to the radio frequency device 152. In the uplink direction, the radio frequency device 152 receives information via the antenna 151 and sends the received information to the baseband device 153 for processing. In the downlink direction, the baseband device 153 processes the information to be transmitted and sends it to the radio frequency device 152. The radio frequency device 152 processes the received information and then sends it through the antenna 151.

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

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

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

[0496] Specifically, the network side device 150 of the embodiment of the present application also includes: instructions or programs stored in the memory 155 and can be run on the processor 154. The processor 154 calls the instructions or programs in the memory 155 to execute the methods executed by each module shown in Figure 12 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0497] 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 9 above, or the various processes of the method embodiment of Figure 11 above, are implemented, and the same technical effect can be achieved. To avoid repetition, they are not repeated here.

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

[0499] 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 9 above, or to implement the various processes of the method embodiment of Figure 11 above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

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

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

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

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

[0505] In the embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

[0507] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0508] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the relevant technology, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0509] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by controlling the relevant hardware through a computer program. The program can be stored in a computer-readable storage medium, and when executed, the program can include the processes in the above-described method embodiments. The storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

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

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

[0512] 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 receives a first message from a network side device, where the first message is used to indicate repeated transmission of a first uplink transmission N times, where N is a positive integer; The terminal determines a target time domain unit corresponding to the first uplink transmission according to a second message from a network side device, where the second message is used to configure at least one time domain unit, and the at least one time domain unit includes a sub-band full-duplex SBFD time domain unit.

2. The method according to claim 1, wherein: The terminal determines, according to the second message from the network side device, a target time domain unit corresponding to the first uplink transmission, including: The terminal determines, starting from a first time domain unit among the at least one time domain unit, N time domain units that meet a first preset condition as the target time domain units; The first preset condition includes at least one of the following: The target symbol is a symbol not used for a synchronization signal SS or a physical broadcast channel PBCH; The target symbol is a UL symbol, a flexible symbol or a SBFD symbol; The continuous X symbols starting from the target symbol are symbols not used for SS or PBCH; X consecutive symbols starting from the target symbol are UL symbols, flexible symbols or SBFD symbols; Wherein, X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission; The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

3. The method according to claim 1, wherein: The first uplink transmission is determined to be transmitted on a time domain resource of a SBFD time domain type; The terminal determines, according to the second message from the network side device, a target time domain unit corresponding to the first uplink transmission, including: The terminal determines, starting from a first time domain unit in the at least one time domain unit, N time domain units that meet a second preset condition as the target time domain units; The second preset condition includes at least one of the following: The target symbol is a SBFD symbol not used for SS or PBCH; The target symbol is the SBFD symbol; The X consecutive symbols starting from the target symbol are SBFD symbols not used for SS or PBCH; The X consecutive symbols starting from the target symbol are SBFD symbols; Wherein, X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission; The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

4. The method according to claim 1, wherein: The first uplink transmission is determined to be transmitted on a time domain resource of a non-SBFD time domain type; The terminal determines, according to the second message from the network side device, a target time domain unit corresponding to the first uplink transmission, including: The terminal determines, starting from the first time domain unit in the at least one time domain unit, N time domain units that meet a third preset condition as the target time domain units; The third preset condition includes at least one of the following: The target symbol is an uplink symbol or a flexible symbol not used for SS or PBCH; X consecutive symbols starting from the target symbol are uplink symbols or flexible symbols not used for SS or PBCH, where X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission; The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

5. The method according to any one of claims 2 to 4, wherein: The first time domain unit includes at least one of the following: A time domain unit indicated to be used to feed back first information, wherein the first information includes a hybrid automatic repeat request acknowledgement HARQ-ACK; A time domain unit for sending second information determined according to a period and an offset of second information, wherein the second information includes at least one of a scheduling request SR and a channel state information CSI.

6. The method according to claim 2, wherein: The target time domain unit also satisfies at least one of the following: The symbols used for the first uplink transmission in the target time domain unit are all SBFD symbols or all non-SBFD symbols; The SBFD uplink subband of the target time domain unit covers the frequency domain resources of the first uplink transmission.

7. The method according to claim 2 or 6, wherein: The first uplink transmission is determined to be transmitted on a time domain resource of a target time domain type, where the target time domain type includes a SBFD time domain type or a non-SBFD time domain type; The method further comprises: In a case where the time domain type of the second time domain unit of the first uplink transmission does not match the target time domain type, the terminal cancels transmission of the first uplink transmission in the second time domain unit; The second time domain unit is at least one time domain unit in the target time domain unit corresponding to the first uplink transmission.

8. The method according to claim 7, further comprising: The terminal counts the number of the second time domain units into the total number of the target time domain units.

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

10. The method according to claim 9, wherein: In a case where the first uplink transmission channel overlaps with the second uplink transmission channel, the terminal performs a first 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, according to at least one time domain unit configured by the second message, whether the first uplink transmission and the second uplink transmission are valid; The terminal performs the first operation when determining that the first uplink transmission and the second uplink transmission are valid.

11. The method according to any one of claims 1 to 10, further comprising: The terminal determines a target time domain type corresponding to an S-th repeated transmission of the first uplink transmission, where the time domain type includes an SBFD time domain type or a non-SBFD time domain type, and S is a positive integer less than or equal to N; The terminal determines, according to the target time domain type, a transmission parameter for the Sth repeated transmission.

12. The method according to claim 11, wherein: The terminal determines, according to the target time domain type, a transmission parameter for the S-th repeated transmission, including: The terminal receives a third message from the network side device, where the third message includes a first transmission configuration item and a second transmission configuration item, where the first transmission configuration item has a mapping relationship with the SBFD time domain type, and the second transmission configuration item has a mapping relationship with 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 for the Sth repeated transmission.

13. The method according to claim 11 or 12, wherein: The transmission parameter includes at least one of a power control parameter and space information.

14. The method according to any one of claims 11 to 13, wherein: The manner in which the terminal determines the target time domain type includes at least one of the following: In a case where the time domain unit where the S-th repeated transmission is located is configured as an SBFD time domain unit, the terminal determines that the target time domain type is the SBFD time domain type; In a case where the time domain unit where the S-th repeated transmission is located is configured 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 in which the S-th repetition transmission is performed are SBFD symbols, the terminal determines that the target time domain type is the SBFD time domain type; In a case where all symbols in which the S-th repeated transmission is performed 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 time domain unit where the S-th repetition transmission is located 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; 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 S-th repeated transmission is located; The target time domain type is determined according to a predefined or default time domain type of the time domain unit where the S-th repeated transmission is located.

15. The method according to claim 1, wherein: The terminal determines, according to the second message from the network side device, a target time domain unit corresponding to the first uplink transmission, including: The terminal determines, based on the second message, whether the L time domain units after the third time domain unit are invalid time domain units, the value of L is configured by the higher layer, the third time domain unit is a downlink time domain unit semi-statically configured through higher layer signaling, and the invalid time domain unit is not used to transmit the first uplink transmission.

16. The method according to claim 15, wherein: The terminal determines, according to the second message, whether L time domain units after the third time domain unit are invalid time domain units, including at least one of the following: If the L time domain units after the third time domain unit are non-SBFD time domain units, the terminal determines that the L time domain units after the third time domain unit are invalid time domain units; If the L time domain units after the third time domain unit are SBFD time domain units, the terminal determines that the L time domain units after the third time domain unit are not invalid time domain units; If the L time domain units after the third time domain unit include non-SBFD time domain units and SBFD time domain units, the terminal determines that the non-SBFD time domain units are invalid time domain units and determines that the SBFD time domain units are not invalid time domain units.

17. A method for configuring uplink transmission, comprising: The network side device sends a first message to the terminal, where the first message is used to indicate repeated transmission of a first uplink transmission N times, where N is a positive integer; The network side device sends a second message to the terminal, where the second message is used to configure at least one time domain unit, and the at least one time domain unit includes a sub-band full-duplex (SBFD) time domain unit.

18. An uplink transmission device, applied to a terminal, the device comprising: A receiving module, configured to receive a first message from a network side device, wherein the first message is used to indicate repeated transmission of a first uplink transmission N times, where N is a positive integer; The first processing module is used to determine the target time domain unit corresponding to the first uplink transmission according to a second message from a network side device, wherein the second message is used to configure at least one time domain unit, and the at least one time domain unit includes a sub-band full-duplex SBFD time domain unit.

19. The device according to claim 18, wherein: The first processing module is specifically used for: Starting from a first time domain unit in the at least one time domain unit, determining N time domain units that meet a first preset condition as the target time domain units; The first preset condition includes at least one of the following: The target symbol is a symbol not used for a synchronization signal SS or a physical broadcast channel PBCH; The target symbol is a UL symbol, a flexible symbol or a SBFD symbol; The continuous X symbols starting from the target symbol are symbols not used for SS or PBCH; X consecutive symbols starting from the target symbol are UL symbols, flexible symbols or SBFD symbols; Wherein, X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission; The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

20. The device according to claim 18, wherein The first uplink transmission is determined to be transmitted on a time domain resource of a SBFD time domain type; The first processing module is specifically used for: Starting from a first time domain unit in the at least one time domain unit, determining N time domain units that meet a second preset condition as the target time domain units; The second preset condition includes at least one of the following: The target symbol is a SBFD symbol not used for SS or PBCH; The target symbol is the SBFD symbol; The X consecutive symbols starting from the target symbol are SBFD symbols not used for SS or PBCH; The X consecutive symbols starting from the target symbol are SBFD symbols; Wherein, X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission; The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

21. The device according to claim 18, wherein The first uplink transmission is determined to be transmitted on a time domain resource of a non-SBFD time domain type; The first processing module is specifically used for: Starting from a first time domain unit in the at least one time domain unit, determining N time domain units that meet a third preset condition as the target time domain units; The third preset condition includes at least one of the following: The target symbol is an uplink symbol or a flexible symbol not used for SS or PBCH; X consecutive symbols starting from the target symbol are uplink symbols or flexible symbols not used for SS or PBCH, where X is an integer greater than or equal to the number of symbols corresponding to the first uplink transmission; The target symbol is configured by a starting symbol index corresponding to the first uplink transmission.

22. The device according to claim 19, wherein The first uplink transmission is determined to be transmitted on a time domain resource of a target time domain type, where the target time domain type includes a SBFD time domain type or a non-SBFD time domain type; The device also includes: A second processing module, configured to cancel the transmission of the first uplink transmission in the second time domain unit when the time domain type of the second time domain unit of the first uplink transmission does not match the target time domain type; The second time domain unit is at least one time domain unit in the target time domain unit corresponding to the first uplink transmission.

23. The apparatus according to claim 22, further comprising: The third processing module is configured to count the number of the second time domain units into the total number of the target time domain units.

24. The device according to any one of claims 18 to 23, further comprising: The fourth processing module is configured to perform a first operation when the first uplink transmission channel overlaps with the second uplink transmission channel, where the first operation includes at least one of the following: canceling the first uplink transmission; canceling the second uplink transmission; The first uplink transmission and the second uplink transmission are multiplexed for transmission.

25. The device according to claim 24, wherein: The fourth 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 at least one time domain unit configured by the second message; In a case where it is determined that the first uplink transmission and the second uplink transmission are valid, the first operation is performed.

26. The device according to any one of claims 18 to 25, further comprising: A fifth processing module, configured to determine a target time domain type corresponding to an S-th repeated transmission of the first uplink transmission, where the time domain type includes an SBFD time domain type or a non-SBFD time domain type, and S is a positive integer less than or equal to N; The sixth processing module is used to determine the transmission parameters of the S-th repeated transmission according to the target time domain type.

27. The device according to claim 26, wherein: The sixth processing module comprises: a receiving unit, configured to receive a third message from the network side device, wherein the third 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 Sth repeated transmission.

28. The device according to claim 26 or 27, wherein The fifth processing module is specifically used for at least one of the following: In a case where the time domain unit where the S-th repeated transmission is located is configured as an SBFD time domain unit, determining that the target time domain type is the SBFD time domain type; In a case where the time domain unit where the S-th repeated transmission is located is configured as a non-SBFD time domain unit, determining that the target time domain type is the non-SBFD time domain type; In a case where all symbols in which the S-th repeated transmission is performed are SBFD symbols, determining that the target time domain type is the SBFD time domain type; In a case where all symbols in the S-th repeated transmission are non-SBFD symbols, determining the target time domain type to be the non-SBFD time domain type; In a case where the time domain unit where the S-th repetition transmission is located 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; 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 S-th repeated transmission is located; The target time domain type is determined according to a predefined or default time domain type of the time domain unit where the S-th repeated transmission is located.

29. The device according to claim 18, wherein The first processing module is specifically used for: According to the second message, determine whether the L time domain units located after the third time domain unit are invalid time domain units, the value of L is configured by the high layer, the third time domain unit is a downlink time domain unit semi-statically configured through high layer signaling, and the invalid time domain unit is not used to transmit the first uplink transmission.

30. The device according to claim 29, wherein: The first processing module is specifically used for at least one of the following: If the L time domain units after the third time domain unit are non-SBFD time domain units, determining that the L time domain units after the third time domain unit are invalid time domain units; If the L time domain units after the third time domain unit are SBFD time domain units, determining that the L time domain units after the third time domain unit are not invalid time domain units; If the L time domain units after the third time domain unit include non-SBFD time domain units and SBFD time domain units, the non-SBFD time domain units are determined to be invalid time domain units, and the SBFD time domain units are determined not to be invalid time domain units.

31. An uplink transmission configuration device, applied to a network side device, the device comprising: A first sending module, used to send a first message to a terminal, where the first message is used to indicate repeated transmission of a first uplink transmission N times, where N is a positive integer; The second sending module is used to send a second message to the terminal, where the second message is used to configure at least one time domain unit, and the at least one time domain unit includes a sub-band full-duplex SBFD time domain unit.

32. A communication device, comprising 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, the steps of the uplink transmission method as described in any one of claims 1 to 16 are implemented, or the steps of the uplink transmission configuration method as described in claim 17 are implemented.

33. 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 16, or implements the steps of the uplink transmission configuration method as described in claim 17.

Images