Method for determining uplink transmission, method for determining power, communication node and medium

Abstract

The invention discloses a method for determining uplink transmission, a power determination method, a communication node and a medium. The method comprises the following steps: determining an effective time domain resource corresponding to uplink transmission based on a transmission mode; and determining processing related to uplink transmission according to the effective time domain resource and a predefined rule.

Description

Determine the uplink transmission method, power determination method, communication nodes, and medium. Technical Field

[0001] This application relates to the field of communication technology, such as a method for determining uplink transmission, a power determination method, a communication node, and a medium. Background Technology

[0002] To improve uplink (UL) coverage, reduce UL transmission latency, and increase UL transmission capacity in Time Division Duplexing (TDD) systems, Subband Full Duplex (SBFD) technology was developed.

[0003] In related technologies, UL subbands can be configured in some or all downlink (DL) symbols or flexible (F) symbols, but not in UL symbols. For example, a UL subband can be configured in a DL symbol, and simultaneously, a DL subband can also be configured in that DL symbol. That is, the UL subband and DL subband (also known as SBFD subband) are configured simultaneously in either a DL symbol or an F symbol. A symbol configured with SBFD subbands is called an SBFD symbol, and a symbol without SBFD subbands is called a non-SBFD symbol. However, the UL subband and DL subband are prohibited from being configured in UL symbols. In this case, the UL bandwidth part (BWP) in the UL symbol is used for UL transmission, and the UL subband in the SBFD symbol is used for uplink transmission. However, the interference conditions in the UL BWP and UL subband are different, so the corresponding UL transmission requires corresponding transmission parameters and configuration parameters to adapt to UL transmission in the UL BWP and UL subband respectively. This complicates the design of UL transmission in the system.

[0004] In related technologies, in scenarios where SBFD subbands are configured, no solution is provided for determining the effective time domain resources corresponding to uplink transmission, nor is a solution provided for determining the processing related to uplink transmission. Summary of the Invention

[0005] This application provides a method for determining uplink transmission, the method comprising:

[0006] Based on the transmission mode, determine the effective time domain resources corresponding to the uplink transmission;

[0007] Based on the available time-domain resources and predefined rules, determine the processing related to uplink transmission.

[0008] This application provides a power determination method, the method comprising:

[0009] For an uplink transmission of type PUSCH repetition type B, where a nominal repetition of the uplink transmission includes SBFD symbols and non-SBFD symbols, the power corresponding to the actual repetition when it is executed is determined based on the power parameters associated with the symbol type of the nominal repetition or the actual repetition obtained based on the nominal repetition, and the time-frequency resources of the nominal repetition or the actual repetition obtained based on the nominal repetition.

[0010] This application provides a communication node, including: a processor; the processor is used to implement the method for determining uplink transmission or the power determination method of any of the above embodiments when executing a computer program.

[0011] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the method for determining uplink transmission or the method for determining power in any of the above embodiments.

[0012] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description

[0013] Figure 1 is a schematic diagram of the structure of an SBFD sub-band according to an embodiment;

[0014] Figure 2 is a schematic diagram of another SBFD sub-band structure provided in an embodiment;

[0015] Figure 3 is a schematic diagram of the structure of an IBFD subband provided in an embodiment;

[0016] Figure 4 is a network diagram of a wireless communication system provided in an embodiment;

[0017] Figure 5 is a flowchart illustrating a method for determining uplink transmission according to an embodiment;

[0018] Figure 6 is a schematic diagram of nominal repetition provided in one embodiment;

[0019] Figure 7 is a flowchart illustrating a power determination method according to an embodiment;

[0020] Figure 8 is a schematic diagram of the structure of a UE provided in an embodiment;

[0021] Figure 9 is a schematic diagram of the structure of a base station provided in one embodiment. Detailed Implementation

[0022] It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application. The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0023] To improve UL coverage, reduce UL transmission latency, and increase UL transmission capacity in TDD systems, SBFD technology for Radio Resource Control (RRC) connected-mode User Equipment (UE) has emerged.

[0024] In related technologies, UL subbands can be configured in some or all downlink (DL) symbols or flexible (F) symbols, but cannot be configured in UL symbols. For example, if a UL subband is configured in a DL symbol, a DL subband will also be configured in that DL symbol.

[0025] The UL subband and the DL subband are also referred to as SBFD subbands, which means that an SBFD subband is configured in the DL symbol / slot of the DL BWP. The SBFD subband usually includes at least one DL subband and one UL subband.

[0026] For example, in a 100MHz TDD carrier, 20 consecutive resource blocks (RBs) are configured as UL subbands in the DL symbol / slot of the DL BWP. The remaining frequency domain resources of the DL BWP are the DL subbands (gap can be omitted). Alternatively, a DL subband can also be configured in the DL symbol / slot of the DL BWP. Thus, in the DL symbol / slot, the UL subband can be used for UL transmission, and the DL subband can be used for DL ​​transmission. Figure 1 is a schematic diagram of the structure of an SBFD subband provided in one embodiment. As shown in Figure 1, an SBFD subband includes one UL subband and two DL subbands. This frequency domain pattern is generally called "DUD" (based on frequency domain structure). Figure 2 is a schematic diagram of the structure of another SBFD subband provided in one embodiment. As shown in Figure 2, an SBFD subband includes one UL subband and one DL subband, with the UL subband located below the DL subband. This frequency domain pattern is generally called "DU" (based on frequency domain structure).

[0027] Currently, SBFD technology has the following characteristics: the base station has the ability to simultaneously perform reception in the UL subband and transmission in the DL subband within the same time domain. The UE does not have the ability to simultaneously perform reception in the UL subband and transmission in the DL subband within the same time domain. Here, the UL subband and DL subband are configured in the same Orthogonal Frequency-Division Multiplexing (OFDM) symbol / slot and are frequency-divided.

[0028] For ease of description, some technical terms are as follows: A symbol configured with an SBFD subband is called an SBFD symbol. A slot containing an SBFD symbol is called an SBFD slot. A symbol not configured with an SBFD subband is called a non-SBFD symbol, which is a regular symbol. A slot not containing an SBFD symbol is called a non-SBFD slot.

[0029] To further improve system efficiency, full-duplex technology has been studied, such as in-band full-duplex (IBFD) operation. This involves configuring a time-frequency resource within the carrier bandwidth of a carrier, allowing the base station to perform simultaneous transmission and reception on the same frequency. For example, consecutive red-band blocks (RBs) can be configured as IBDFD sub-bands within the carrier bandwidth, and these IBDFD sub-bands can be configured in all or some symbols to form a resource for IBDFD operation.

[0030] A portion or all of the carrier bandwidth of a carrier is configured as an IBFD subband, and the IBFD is configured in all or some symbols. Figure 3 is a schematic diagram of an IBFD subband structure provided in one embodiment. As shown in Figure 3, the left figure in Figure 3 shows a portion of the carrier bandwidth configured as an IBFD subband, and the IBFD is configured in all symbols. The right figure in Figure 3 shows a portion of the carrier bandwidth configured as an IBFD subband, and the IBFD is configured in some symbols. In the embodiments of this application, SBFD symbols or slots can be replaced by IBFD symbols or slots.

[0031] The aforementioned SBFD subband operation is performed within the DL BWP and UL BWP pair, which are center frequency aligned.

[0032] The intersection of the UL subband and the active UL BWP in the frequency domain is called the UL available physical resource block (PRB), and the intersection of the DL subband and the active DL BWP in the frequency domain is called the DL available PRB.

[0033] After the introduction of SBFD technology, DL transmission and UL transmission will occur simultaneously in an SBFD slot. These DL transmissions and UL transmissions may conflict in the time domain (i.e., overlap in the time domain). However, the UE cannot simultaneously perform DL transmission reception and UL transmission transmission. Therefore, some transmission conflict resolution mechanisms have been introduced.

[0034] UL transmission includes: UL transmissions scheduled through Downlink Control Information (DCI) in the Physical Downlink Control Channel (PDCCH), such as the Physical Uplink Control Channel (PUCCH), Sounding Reference Signal (SRS), Physical Uplink Shared Channel (PUSCH), Physical Random Access Channel (PRACH), etc. It also includes semi-static UL transmissions, such as those configured by RRC or Media Access Control-Control Element (MAC CE), including PUCCH, SRS, PUSCH, and PRACH. DL transmission includes: DL transmissions scheduled via DCI in PDCCH, such as Physical Downlink Shared Channel (PDSCH), PDCCH, Channel State Information Reference Signal (CSI-RS), etc. It also includes semi-static DL transmissions, such as PDSCH configured by RRC or MAC CE, Control Resource Set (CORESET) of PDCCH, CSI-RS, Synchronization Signal Block (SSB), etc.

[0035] DL or UL transmissions configured in MAC CE can also be classified as dynamic.

[0036] The transmission collision resolution mechanism in SBFD symbols is as follows:

[0037] 1. Regarding the conflict between dynamically scheduled DL transmissions and semi-statically configured UL transmissions in the SBFD symbol, if the cancellation timeline is met, the UL transmission is cancelled, meaning it is not sent. In other words, the DL transmission is received. Otherwise, the UL transmission is transmitted, but the DL transmission is not received. Although there is a cancellation timeline condition, in most cases, the cancellation timeline is met because the base station schedules the dynamic DL transmission because it wants the UE to receive it. Otherwise, the base station would not need to dynamically schedule the DL transmission to conflict with the semi-static UL transmission, because even if the dynamic DL transmission is scheduled, the UE will not receive it. In other words, the cancellation timeline decision here can be considered always true. Dynamic scheduling refers to transmissions scheduled based on DCI in the PDCCH.

[0038] 2. If there is a conflict between a dynamically scheduled UL transmission and a semi-statically configured DL transmission in the SBFD symbol, the DL transmission will not be received; that is, the UL transmission will be sent.

[0039] 3. If there is a conflict between a semi-static UL transmission and a semi-static DL transmission configured in the SBFD symbol, the UE will consider it an erroneous scheduling error and will neither receive nor send the semi-static DL transmission. The semi-static DL transmission includes UE-specific semi-static transmissions or cell-level semi-static DL transmissions. Cell-level semi-static DL transmissions include the PDCCH corresponding to the common search space. The semi-static common search space is a search space shared by multiple UEs at the cell level, configured by higher-layer signaling (such as RRC signaling). The semi-static UL transmission refers to the UE-level semi-static UL transmission configured by higher-layer signaling.

[0040] 4. If there is a conflict between a dynamically scheduled UL transmission and a dynamically scheduled DL transmission in the SBFD symbol, the DL transmission will not be received, that is, the UL transmission will not be sent either.

[0041] An SSB symbol configured with an SBFD subband is an SBFD symbol. Within this SBFD symbol, only DL transfers within the available DL PRBs are permitted. This SSB is located within this DL subband.

[0042] For a DL transmission with repetitions, such as a DL transmission with 4 repetitions, in the SBFD notation, each repetition follows the transmission collision resolution mechanism described above. For a UL transmission with multiplexing, such as a UL transmission with 4 repetitions, in the SBFD notation, each repetition follows the transmission collision resolution mechanism described above.

[0043] In related technologies, in scenarios where SBFD subbands are configured, no solution is provided for determining the effective time domain resources corresponding to uplink transmission, nor is a solution provided for determining the processing related to uplink transmission.

[0044] The method for determining uplink transmission provided in this application can be applied to various wireless communication systems, such as Long Term Evolution (LTE) systems, 4th-generation (4G) systems, 5th-generation (5G) systems, LTE and 5G hybrid architecture systems, 5G New Radio (NR) systems, and new communication systems emerging in future communication development, such as 6th-generation (6G) systems. Figure 4 is a network diagram of a wireless communication system provided in an embodiment. As shown in Figure 4, the wireless communication system includes a terminal device 110, an access network device 120, and a core network device 130.

[0045] Terminal device 110 can be a device with wireless transceiver capabilities, which can be deployed on land (such as indoors or outdoors, handheld, wearable or vehicle-mounted); on water (such as ships); or in the air (such as airplanes, balloons and satellites). Examples of terminal devices 110 include: wireless terminals, user equipment (UE), mobile phones, mobile stations, tablets, laptops, ultra-mobile personal computers (UMPCs), handheld computers, netbooks, personal digital assistants (PDAs), and other network-connected user devices; virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc.; IoT nodes in the Internet of Things (IoT); in-vehicle communication devices in the Internet of Vehicles (IoV); entertainment and gaming devices or systems; and GPS devices, etc. The embodiments of this application do not limit the specific technologies or device forms used in the terminal devices. Furthermore, the term "terminal device" can be abbreviated as "terminal."

[0046] Access network equipment 120 is the access device through which terminal equipment 110 wirelessly accesses the wireless communication system. It can be a reader / writer, a base station, an evolved NodeB (eNB or eNodeB) in Long Term Evolution Advanced (LTE), a transmission reception point (TRP), a base station in a 5G mobile communication system, a next-generation NodeB (gNB), a base station in a future mobile communication system, or an access node in a Wireless Fidelity (WiFi) system. Base stations can include various macro base stations, micro base stations, femtobase stations, wireless extensions, routers, WiFi devices, or various network-side devices such as primary cells and secondary cells, as well as location management function (LMF) devices. It can also be a module or unit that performs some of the functions of a base station; for example, it can be a central unit (CU) or a distributed unit (DU). The embodiments of this application do not limit the specific technology or equipment form used in the access network equipment. In addition, the access network equipment can be referred to as a base station.

[0047] Core network equipment 130 may include access and mobility management network elements and session management network elements. For example, terminal equipment 110 can access the core network through access network equipment 120 to achieve data transmission.

[0048] In this application embodiment, a method, communication node and medium for determining uplink transmission that can be run in the above-mentioned wireless communication system are provided to determine the effective time domain resources corresponding to the uplink transmission and to determine the processing related to the uplink transmission.

[0049] The method for determining uplink transmission, the communication node, and its technical effects are described below. All backgrounds, conditions, options, examples, and methods in the same or different embodiments of this application can be combined.

[0050] Figure 5 is a flowchart illustrating a method for determining uplink transmission according to an embodiment. As shown in Figure 5, the method for determining uplink transmission provided in this embodiment can be applied to a first communication node or a second communication node. In this embodiment, the first communication node can be the terminal device in Figure 4, and the second communication node can be the access network device in Figure 4. As shown in Figure 5, the method includes the following steps.

[0051] Step 501: Based on the transmission mode, determine the valid time domain resources corresponding to the uplink transmission.

[0052] The transmission mode in this embodiment is used to indicate the type of time-domain resources for uplink transmission. Furthermore, the transmission mode in this embodiment is used to indicate the symbol type of the uplink transmission time slot. The symbol types in this embodiment include SBFD symbols and / or non-SBFD symbols.

[0053] In one embodiment, the transmission mode includes a first mode for indicating uplink transmission to be performed in different time slots, wherein the symbols in the different time slots are SBFD symbols or non-subband full-duplex non-SBFD symbols.

[0054] In one embodiment, the transmission mode includes a second mode, which indicates that uplink transmission is performed in different time slots, and the symbols in the different time slots are SBFD symbols and non-SBFD symbols, and the symbols in the same time slot are either SBFD symbols or non-SBFD symbols.

[0055] The first and second modes are explained in detail below.

[0056] Mode 1: This refers to a UL transmit / DL receive operation that needs to be performed in different slots, but is restricted to using only SBFD symbols or only non-SBFD symbols in all different slots. For example, if a UL transmit / DL receive is determined to be in Mode 1 and needs to be performed in different slots, and if the valid symbol for the UL transmit / DL receive is determined to be an SBFD symbol, then the UL transmit / DL receive can only perform transmissions using SBFD symbols in different slots. That is, if the symbol provided for the UL transmit / DL receive in a slot is a non-SBFD symbol, then the UL transmit / DL transmission will not be performed in that slot. (This is repeated in the original text.)

[0057] Mode 2: This refers to a UL transmit / DL receiver being executed in different slots, and being allowed to use both SBFD and non-SBFD symbols in different slots (the UL transmit / DL receiver can only use one type of symbol within a slot). For example, if a UL transmit / DL receiver is determined to be in Mode 2 and is executed in different slots, then the UL transmit / DL receiver can use different types of symbols in different slots, but can only use one type of symbol within a slot. For example, if the UL transmit / DL receiver is executed in slot n and slot m, and the symbols in slot n or slot m all contain either SBFD symbols or both non-SBFD symbols, then the UL transmit / DL receiver will be executed in slot n or slot m. That is, if the symbols in slot n or slot m contain both SBFD and non-SBFD symbols, then the UL transmit / DL receiver will not be executed in slot n or slot m.

[0058] The DL reception includes, but is not limited to, at least one of the following: a non-repeating PDSCH scheduled by the DCI, a repeating PDSCH scheduled by the DCI, a periodic non-repeating PDSCH (e.g., a semi-persistent Scheduling Physical Downlink Shared Channel (SPSPDSCH)), a periodic repeating PDSCH, multiple PDSCHs scheduled by a single DCI (non-repeating), multiple PDSCHs scheduled by a single DCI (repeating), a Channel State Information Reference Signal (CSI RS), and a Downlink Positioning Reference Signal (DLPRS).

[0059] The UL transmission includes, but is not limited to, at least one of the following: a DCI-scheduled PUSCH without repetition (including additional SP CSI PUSCH), a DCI-scheduled PUSCH with repetition (including additional Semi-Persistent Channel State Information Physical Uplink Shared Channel, SP CSI PUSCH), a periodic PUSCH without repetition (e.g., Type 2 Configured Grant Physical Uplink Shared Channel, type 2 CG PUSCH, type 1 CG PUSCH, SP CSI PUSCH, etc.), a periodic PUSCH with repetition (e.g., type 2 CG PUSCH, type 1 CG PUSCH, SP CSI PUSCH, etc.), a Transport Blockover Multiple Slots (TBoMS) (with or without repetition), and a PUCCH without repetition (including periodic (P) / SP CSI PUSCH). PUCCH, Scheduled Request Physical Uplink Control Channel (SR PUCCH), Hybrid Automatic Repeat Request Acknowledgement Physical Uplink Control Channel (HARQ-ACK PUCCH), PUCCH with repeats (including CSIPUCCH, SR PUCCH, HARQ-ACK PUCCH), and SRS.

[0060] TBoMS refers to the transmission of one TB across multiple slots. That is, the data corresponding to one TB is divided into n parts and transmitted in n slots respectively.

[0061] In this embodiment, the DL transmission in subsequent embodiments is the same as the DL reception described above, as observed from the base station side and the UE side, respectively.

[0062] In this embodiment, the effective time-domain resource refers to either a repeated time-domain resource that will be used for uplink transmission, or a time-domain resource that will be used for uplink transmission. For example, in this embodiment, the effective time-domain resource can be an effective timeslot.

[0063] It should be noted that when the method of this embodiment is applied to the first communication node, the uplink transmission in this embodiment refers to the first communication node performing uplink sending. When the method of this embodiment is applied to the second communication node, the uplink transmission in this embodiment refers to the second communication node performing uplink receiving.

[0064] Step 502: Determine the processing related to uplink transmission based on the available time domain resources and predefined rules.

[0065] In this embodiment, after determining the valid time domain resources, the processing related to uplink transmission can be determined based on the valid time domain resources and predefined rules.

[0066] The predefined rules in this embodiment are used to indicate at least one of the following: transmission rules related to uplink transmission, conflict handling rules related to uplink transmission, and processing rules for valid time domain resources related to uplink transmission.

[0067] In one embodiment, the uplink transmission is a PUCCH transmission with N PUCCH repetitions, the effective time domain resource is an effective time slot, and the transmission mode is a first mode. Step 501 includes: when the effective symbol type of the PUCCH transmission is SBFD symbol, the time slot satisfying the first condition is determined as one of the N effective time slots containing the N PUCCH repetitions. Here, N is an integer greater than or equal to 1. In this embodiment, the effective symbol type of the uplink transmission can be configured by the base station or determined based on predefined rules. In this implementation, the effective time domain resource corresponding to the uplink transmission is determined based on the transmission mode of the uplink transmission and the effective symbol type of the uplink transmission.

[0068] In one embodiment, the first condition includes: a time slot can provide a first SBFD symbol, and M1 consecutive symbols starting from the first SBFD symbol are SBFD symbols, the first SBFD symbol has the same symbol index as the starting symbol configured for the PUCCH resource corresponding to the PUCCH transmission, M1 is the number of symbols configured for the PUCCH resource, and M1 is an integer greater than or equal to 1. Subsequent first conditions and M1 can be implemented using the corresponding methods in this embodiment, and will not be elaborated further.

[0069] In one embodiment, the first condition includes: a time slot can provide a first SBFD symbol, and M1 consecutive symbols starting from the first SBFD symbol are SBFD symbols, and the M1 SBFD symbols do not contain symbols of downlink common channels or signals. Subsequent first conditions can all be implemented using this method, and will not be elaborated further.

[0070] In one embodiment, the uplink transmission is a PUCCH transmission with N PUCCH repetitions, the effective time domain resource is an effective time slot, the effective symbol type of the PUCCH transmission is SBFD symbol, and the transmission mode is the first mode. Step 502 includes: the uplink transmission will be transmitted in a time slot, and this time slot is the effective time slot. If, due to a preset first reason or transmission of first signaling, the effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, the time slot is still counted in the number of effective time slots. This implementation method can ensure that even if an effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, the effective time slot is still counted in the number of effective time slots, avoiding the communication system from entering a dead loop state in order to reach the number of effective time slots when an effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, thus improving the reliability of the communication system.

[0071] In one embodiment, the first signaling includes at least one of the following: signaling that dynamically changes the SBFD symbol to a non-SBFD symbol, and signaling that triggers an on-demand SSB within the SBFD symbol. Subsequent first signaling implementations can all adopt this method and will not be described further.

[0072] In one embodiment, the preset first reason includes at least one of the following: the PUCCH transmission is dynamically scheduled, and the PUCCH repetition overlaps with a dynamic downlink DL transmission in the time domain, causing the PUCCH repetition not to be sent; the PUCCH transmission is semi-statically configured, and the PUCCH repetition overlaps with a dynamic DL transmission in the time domain, causing the PUCCH repetition not to be sent; the PUCCH transmission is semi-statically configured, and the PUCCH repetition overlaps with a semi-static DL transmission in the time domain, causing the PUCCH repetition not to be sent; the PUCCH transmission is semi-statically configured or dynamically scheduled, and the PUCCH repetition overlaps with a high-priority uplink UL transmission or DL ​​transmission in the time domain, causing the PUCCH repetition not to be sent; the PUCCH repetition conflicts with a symbol whose attributes are dynamically changed in the time domain. Subsequent preset first reasons can all adopt this implementation method and will not be elaborated further.

[0073] In one embodiment, the uplink transmission is a PUCCH transmission with N PUCCH repetitions, the effective time domain resource is an effective time slot, and the transmission mode is a first mode. Step 501 includes the following implementation: when the effective symbol type of the PUCCH transmission is a non-SBFD symbol, the time slot that satisfies the second condition is determined as one of the N effective time slots containing the N PUCCH repetitions.

[0074] In one embodiment, the second condition includes: a time slot can provide a first UL symbol or a first F symbol without a configured SBFD subband, and M1 consecutive symbols starting from the first UL symbol or the first F symbol without a configured SBFD subband are UL symbols or flexible F symbols without a configured SBFD subband, wherein the first UL symbol or the first F symbol without a configured SBFD subband has the same symbol index as the starting symbol of the PUCCH resource configured for the PUCCH transmission. The implementation of M1 is the same as in the above embodiment and will not be repeated here. Subsequent second conditions can all adopt this implementation method and will not be repeated here.

[0075] In one embodiment, the second condition includes: a time slot can provide a first UL symbol or a first F symbol not configured with an SBFD subband, and M1 consecutive symbols starting from the first UL symbol or the first F symbol not configured with an SBFD subband are either UL symbols or F symbols not configured with an SBFD subband, and the M1 symbols do not contain symbols of downlink common channels or signals. Subsequent second conditions can all be implemented using this method, and will not be elaborated further.

[0076] In one embodiment, the uplink transmission is a PUCCH transmission with N PUCCH repetitions, the effective time domain resource is an effective time slot, the effective symbol type of the PUCCH transmission is a non-SBFD symbol, and the transmission mode is a first mode. Step 502 is implemented as follows: the uplink transmission is to be transmitted in a time slot, and this time slot is the effective time slot. If, due to a preset first reason or transmission of a second signaling, the effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, then the time slot is still counted in the number of effective time slots. This implementation ensures that even if an effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, the effective time slot is still counted in the number of effective time slots, avoiding the communication system from entering a dead loop in order to reach the number of effective time slots when an effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, thus improving the reliability of the communication system.

[0077] In one embodiment, the second signaling includes at least one of the following: signaling that dynamically changes a non-SBFD symbol to an SBFD symbol, and signaling that triggers an on-demand SSB within the non-SBFD symbol. Subsequent second signaling implementations can all adopt this method and will not be described further.

[0078] In one embodiment, the uplink transmission is a PUCCH transmission with N PUCCH repetitions, the effective time domain resource is an effective time slot, and the transmission mode is the second mode. Step 501 is implemented by determining a time slot that satisfies either the first or second condition as one of the N effective time slots containing the N PUCCH repetitions. Here, N is an integer greater than or equal to 1.

[0079] In one embodiment, the uplink transmission is a PUCCH transmission with N PUCCH repetitions, the effective time domain resource is an effective time slot, and the transmission mode is the second mode. Step 502 is implemented as follows: the uplink transmission is to be transmitted in a time slot, and this time slot is the effective time slot. If, due to a preset second reason, transmission of the first signaling, or transmission of the second signaling, the effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, then the time slot is still counted in the number of effective time slots. This implementation ensures that even if an effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, the effective time slot is still counted in the number of effective time slots, avoiding the communication system from entering a dead loop in order to reach the number of effective time slots when an effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, thus improving the reliability of the communication system.

[0080] In one embodiment, the preset second cause includes: the PUCCH repeat not being sent because it overlaps in the time domain with a downlink common channel or signal; the PUCCH repeat not being sent because the PUCCH transmission is dynamically scheduled and overlaps in the time domain with a dynamic DL transmission; the PUCCH repeat not being sent because the PUCCH transmission is semi-statically configured and overlaps in the time domain with a dynamic DL transmission; the PUCCH repeat not being sent because the PUCCH transmission is semi-statically configured and overlaps in the time domain with a semi-static DL transmission; the PUCCH repeat not being sent because the PUCCH transmission is semi-statically configured or dynamically scheduled and overlaps in the time domain with a high-priority UL transmission or DL ​​transmission; and the PUCCH repeat not being sent because it conflicts in the time domain with a symbol whose attributes are dynamically changed.

[0081] In one embodiment, the uplink transmission is a PUSCH transmission with N repetitions of the Physical Uplink Shared Channel (PUSCH) and carries a transport block spanning K time slots. The effective time domain resource is the effective time slot, and the transmission mode is the first mode. Step 501 includes the following steps: when the effective symbol type of the PUSCH transmission is SBFD symbol, the time slot satisfying the third condition is determined as one of the N*K effective time slots of the PUSCH transmission. Here, N is an integer greater than or equal to 1, and K is an integer greater than or equal to 1.

[0082] In one embodiment, the third condition includes: within a time slot, all symbols containing the PUSCH resources corresponding to the PUSCH transmission are SBFD symbols. Subsequent third conditions can all be implemented using this method, and will not be elaborated further.

[0083] In one embodiment, the third condition includes: within a time slot, all symbols containing the PUSCH resources corresponding to the PUSCH transmission are SBFD symbols, and the SBFD symbols do not contain symbols for downlink common channels or signals. Subsequent third conditions can all be implemented using this method, and will not be elaborated further.

[0084] In one embodiment, the uplink transmission is a PUSCH transmission with N PUSCH repetitions and carries a transport block spanning K time slots. The effective time domain resource is the effective time slot, the effective symbol type of the PUSCH transmission is SBFD symbol, and the transmission mode is the first mode. Step 502 includes the following steps: the uplink transmission will be transmitted in a time slot, and this time slot is the effective time slot. If, when the effective time slot counting is enabled, the effective time slot becomes an invalid time slot due to a preset third reason or the transmission of the first signaling, or the uplink transmission is not executed in the effective time slot, the time slot is still counted in the number of effective time slots. This implementation avoids the communication system from entering a dead loop state in order to reach the number of effective time slots when an effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, thus improving the reliability of the communication system.

[0085] In one embodiment, the preset third cause includes at least one of the following: the PUSCH transmission is dynamically scheduled, and the PUSCH repeat overlaps with a dynamic DL transmission in the time domain, causing the PUSCH repeat not to be sent; the PUSCH transmission is semi-statically configured, and the PUSCH repeat overlaps with a dynamic DL transmission in the time domain, causing the PUSCH repeat not to be sent; the PUSCH transmission is semi-statically configured, and the PUSCH repeat overlaps with a semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent; the PUSCH transmission is semi-statically configured or dynamically scheduled, and the PUSCH repeat overlaps with a high-priority UL transmission or DL ​​transmission in the time domain, causing the PUSCH repeat not to be sent; the PUSCH repeat conflicts with a symbol whose attributes are dynamically changed in the time domain.

[0086] In one embodiment, the uplink transmission is a PUSCH transmission with N repetitions of the Physical Uplink Shared Channel (PUSCH) and carries a transport block spanning K time slots. The effective time domain resource is the effective time slot, and the transmission mode is the first mode. Step 501 includes the following steps: when the effective symbol type of the PUSCH transmission is non-SBFD symbols, the time slot satisfying the fourth condition is determined as one of the N*K effective time slots of the PUSCH transmission.

[0087] In one embodiment, the fourth condition includes: within a time slot, all symbols containing the PUSCH resources corresponding to the PUSCH transmission are UL symbols or F symbols not configured with SBFD subbands. Subsequent fourth conditions can all be implemented using this method, and will not be elaborated further.

[0088] In one embodiment, the fourth condition includes: within a time slot, all symbols containing the PUSCH resources corresponding to the PUSCH transmission are UL symbols or F symbols that are not configured with SBFD subbands and do not contain downlink common channels or signals. Subsequent fourth conditions can all adopt this implementation method and will not be described in detail.

[0089] In one embodiment, the uplink transmission is a PUSCH transmission with N PUSCH repetitions and carries a transport block spanning K time slots. The effective time domain resource is the effective time slot, the effective symbol type of the PUSCH transmission is non-SBFD symbol, and the transmission mode is the first mode. Step 502 includes: the uplink transmission will be transmitted in a time slot, and this time slot is the effective time slot. If, when the effective time slot counting is enabled, the effective time slot becomes an invalid time slot due to a preset third reason or the transmission of second signaling, or the uplink transmission is not executed in the effective time slot, the time slot is still counted in the number of effective time slots. This implementation avoids the communication system from entering a dead loop state in order to reach the number of effective time slots when an effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, thus improving the reliability of the communication system.

[0090] In one embodiment, the uplink transmission is a PUSCH transmission with N PUSCH repetitions and carries a transport block spanning K time slots. The effective time domain resource is the effective time slot, and the transmission mode is the second mode. Step 501 includes: a time slot satisfying the third or fourth condition is determined as one of the N*K effective time slots for the PUSCH transmission. Here, N is an integer greater than or equal to 1, and K is an integer greater than or equal to 1.

[0091] In one embodiment, the uplink transmission is a PUSCH transmission with N PUSCH repetitions and carries a transport block spanning K time slots. The effective time domain resource is the effective time slot, and the transmission mode is the second mode. Step 502 includes the following steps: the uplink transmission will be transmitted in a time slot, and this time slot is the effective time slot. When the effective time slot counting is enabled, if the effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot due to a preset fourth reason, transmission of the first signaling, or transmission of the second signaling, the time slot is still counted in the number of effective time slots. This implementation avoids the communication system from entering a dead loop state in order to reach the number of effective time slots when an effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot, thus improving the reliability of the communication system.

[0092] In one embodiment, the preset fourth reason includes: the PUSCH repetition not being sent because it overlaps with a common downlink channel or signal in the time domain; the PUSCH repetition not being sent because the PUSCH transmission is dynamically scheduled and overlaps with a dynamic DL transmission in the time domain; the PUSCH repetition not being sent because the PUSCH transmission is semi-statically configured and overlaps with a dynamic DL transmission in the time domain; the PUSCH repetition not being sent because the PUSCH transmission is semi-statically configured and overlaps with a semi-static DL transmission in the time domain; the PUSCH repetition not being sent because the PUSCH transmission is semi-statically configured or dynamically scheduled and overlaps with a high-priority UL transmission or DL ​​transmission in the time domain; and the PUSCH repetition not being sent because it conflicts with a symbol whose attributes are dynamically changed in the time domain. Subsequent fourth reasons can all be implemented using this method and will not be elaborated further.

[0093] In one embodiment, the uplink transmission is an aperiodic sounding reference signal (A-SRS) transmission, the effective time domain resource is an effective time slot, and the transmission mode is a first mode. Step 501 includes: when the effective symbol type of the A-SRS transmission is SBFD symbols, the time slot satisfying the fifth condition is determined as the effective time slot.

[0094] In one embodiment, the fifth condition includes: within a time slot, the symbols of all SRS resources in the SRS resource set corresponding to the A-SRS transmission are SBFD symbols in the time domain, and the UE capability satisfies the minimum timing requirement between the PDCCH that triggers the A-SRS transmission and all the SRS resources. Subsequent fifth conditions can all adopt this implementation method and will not be elaborated further. The minimum timing requirement of the UE refers to: a timing domain interval needs to be maintained between the PDCCH (end) that triggers the A-SRS transmission and all the SRS resources of the A-SRS (beginning of the earliest SRS resource). The size of this interval is related to the UE's capability (different UEs may require different sizes of this interval). If the interval is less than the minimum timing requirement of the UE, it means that the UE does not have enough time to decode the PDCCH and prepare for the A-SRS transmission. Subsequent fifth conditions can all adopt this implementation method and will not be elaborated further.

[0095] In one embodiment, the fifth condition includes: in a time slot, all SRS resources in the SRS resource set corresponding to the A-SRS transmission have SBFD symbols in the time domain and the SBFD symbols do not contain symbols of downlink common channels or signals, and satisfy the UE capability of the minimum timing requirement between the PDCCH that triggers the A-SRS transmission and all the SRS resources.

[0096] In one embodiment, the uplink transmission is A-SRS transmission, the effective time domain resource is an effective time slot, the effective symbol type of the A-SRS transmission is SBFD symbol, and the transmission mode is the first mode. Step 502 is implemented by ensuring that during uplink transmission, the effective time slot does not become an ineffective time slot or the uplink transmission is not performed within the effective time slot due to a preset fifth reason or transmission of the first signaling. This implementation can ensure that the A-SRS transmission is successfully transmitted within the effective time slot as much as possible, improving the reliability of the communication system.

[0097] In one embodiment, the preset fifth reason includes at least one of the following: the A-SRS transmission is not sent because it is dynamically scheduled and overlaps with a dynamic DL transmission in the time domain; the A-SRS transmission is not sent because it is semi-statically configured and overlaps with a dynamic DL transmission in the time domain; the A-SRS transmission is not sent because it is semi-statically configured and overlaps with a semi-static DL transmission in the time domain; the A-SRS transmission is not sent because it is semi-statically configured or dynamically scheduled and overlaps with a high-priority UL transmission or DL ​​transmission in the time domain; the A-SRS transmission is not sent because it overlaps with an SSB in the time domain; or the A-SRS transmission conflicts with a symbol whose attributes are dynamically changed in the time domain. The same implementation method can be used for all the subsequent pre-defined fifth reasons, so I will not go into details again.

[0098] In one embodiment, the uplink transmission is A-SRS transmission, the effective time domain resource is an effective time slot, and the transmission mode is the first mode. The implementation process of step 501 includes: when the effective symbol type of the A-SRS transmission is non-SBFD symbol, the time slot that satisfies the sixth condition is determined as the effective time slot.

[0099] In one embodiment, the sixth condition includes: within a time slot, the symbols of all SRS resources in the SRS resource set corresponding to the A-SRS transmission are non-SBFD symbols in the time domain, and the UE capability satisfies the minimum timing requirement of the UE between the PDCCH that triggers the A-SRS transmission and all the SRS resources. Subsequent sixth conditions can all be implemented using this method and will not be elaborated further.

[0100] In one embodiment, the sixth condition includes: within a time slot, all SRS resources in the SRS resource set corresponding to the A-SRS transmission have symbols that are non-SBFD symbols in the time domain, and the non-SBFD symbols do not contain symbols of downlink common channels or signals, and satisfy the UE capability of meeting the minimum timing requirement of the UE between the PDCCH that triggers the A-SRS transmission and all the SRS resources. Subsequent sixth conditions can all be implemented using this method and will not be elaborated further.

[0101] In one embodiment, the uplink transmission is A-SRS transmission, the effective time domain resource is an effective time slot, the effective symbol type of the A-SRS transmission is non-SBFD symbols, and the transmission mode is the first mode. Step 502 includes the following implementation process: during uplink transmission, it is not desirable for the effective time slot to become an ineffective time slot or for the uplink transmission to not be performed within the effective time slot due to a preset fifth reason or transmission of second signaling. This implementation method can ensure that the A-SRS transmission is successfully transmitted within the effective time slot as much as possible, improving the reliability of the communication system.

[0102] In one embodiment, the symbols of the downlink common channel or signal include at least one of the following: SSB symbol, control resource set CORESET#0 symbol, semi-statically configured sensing channel or signal symbol, and semi-statically configured symbol for adjusting automatic gain control (AGC).

[0103] The method for determining uplink transmission provided in this embodiment determines the effective time domain resources corresponding to the uplink transmission based on the transmission mode, and determines the processing related to the uplink transmission according to the effective time domain resources and predefined rules, so as to realize the determination of the effective time domain resources corresponding to the uplink transmission and the determination of the processing related to the uplink transmission.

[0104] The following examples illustrate the method for determining uplink transmission provided in this embodiment, taking into account scenarios where the uplink transmission is a PUCCH transmission with N PUCCH repetitions, a PUSCH transmission with N PUSCH repetitions carrying a transport block spanning K time slots, and A-SRS transmission, with the effective time domain resource being the effective time slot. In the following examples, the first communication node is the UE and the second communication node is the base station.

[0105] Example 1: PUCCH transmission with N PUCCH repetitions

[0106] For a PUCCH transmission with N PUCCH repetitions, the base station and UE agree on the following rules (Alts) to determine the N slots as the valid time slots corresponding to the PUCCH transmission with N repetitions.

[0107] Rule 1 (ALT1)

[0108] Based on different implementation methods of transmission modes, ALT1 has the following three implementation methods.

[0109] In the first implementation of ALT1, if the first mode is determined to be a PUCCH transmission with N repetitions, and the valid symbol type of this PUCCH transmission is determined to be SBFD symbols, then N slots are determined starting from the initial slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of these N slots need to be determined based on predefined conditions (due to differences in symbol configuration between slots, not all slots can be used for this PUCCH transmission). That is, slots that satisfy the following conditions are determined as the slots containing the N repetitions. For ease of description, the N time slots determined here are called valid time slots.

[0110] Condition: A slot can provide a first SBFD symbol, and M consecutive symbols starting from (and including) this first SBFD symbol are SBFD symbols, and the first M1 symbols of these M symbols do not contain SSB symbols (M1 is less than or equal to M). Alternatively, it can be described as: A slot can provide a first SBFD symbol, and M1 consecutive symbols starting from (and including) this first SBFD symbol are SBFD symbols and do not contain SSB symbols. A slot satisfying this condition is determined as one of the N slots. Here, the first SBFD symbol has the same symbol index as the starting symbol configured in the PUCCH resource corresponding to the PUCCH transmission (e.g., the symbol index refers to the symbol index within the slot), and M1 is the number of symbols configured in the PUCCH resource. Here, the SSB symbol can also be replaced with the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbols here include semi-statically configured SSB symbols, but do not include on-demand triggered SSB symbols.

[0111] The base station and UE agree that the symbol positions for the PUCCH transmission in the determined N slots are: starting from the first SBFD symbol mentioned above, for M1 consecutive SBFD symbols.

[0112] If, within the N slots determined based on the above conditions, the UE intends to perform the aforementioned PUCCH transmission with N repetitions using the PUCCH Resource, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUCCH transmission in one or more slots within the N slots, or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of the N slots.

[0113] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for PUCCH transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for PUCCH transmission to transmit an SSB.

[0114] The preset reasons include at least one of the following:

[0115] 1. In response to the fact that the PUCCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUCCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUCCH repetition not being sent.

[0116] 2. In response to the fact that the PUCCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUCCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0117] 3. In response to the fact that the PUCCH transmission is semi-statically configured, and in the SBFD symbol of the slot, the PUCCH repeat conflicts with the semi-static DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0118] 4. If the PUCCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUCCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUCCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0119] 5. In response to a PUCCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes have been dynamically changed in the time domain conflicting within the slot. For example, the attribute of a symbol is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0120] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0121] In the second implementation of ALT1, if the first mode is determined to be a PUCCH transmission with N repetitions, and the valid symbol type of the PUCCH transmission is determined to be non-SBFD symbol, then N slots are determined starting from the starting slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of the N slots need to be determined based on predefined conditions (due to the differences in symbol configuration between slots, not all slots can be used for this PUCCH transmission). That is, the slots that meet the following conditions are determined to be the slots where the N repetitions are located.

[0122] Conditions: A slot can provide a first UL symbol or a first F (flexible) symbol not configured with an SBFD subband, and the M consecutive symbols starting from this first symbol are either UL symbols or F symbols not configured with an SBFD subband, and the first M1 symbols of these M symbols do not contain any SSB symbols (M1 is less than or equal to M). Alternatively, it can be described as: A slot can provide a first UL symbol or a first F symbol not configured with an SBFD subband, and the M1 consecutive symbols starting from this first symbol are either UL symbols or F symbols not configured with an SBFD subband and do not contain any SSB symbols. A slot satisfying these conditions is determined as one of the N slots. Wherein, the first symbol has the same symbol index as the starting symbol configured for the PUCCH Resource corresponding to the PUCCH transmission (e.g., the symbol index refers to the symbol index within the slot), and M1 is the number of symbols configured for the PUCCH Resource. Here, the SSB symbol can also be replaced with the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbol here includes semi-statically configured SSB symbols but excludes on-demand triggered SSB symbols.

[0123] The base station and UE agree that the symbol positions for performing the PUCCH transmission in the determined N slots are: starting from the first symbol mentioned above, the symbols are M1 consecutive UL symbols or F symbols that are not configured with SBFD subbands.

[0124] If, within the N slots determined based on the above conditions, the UE intends to perform the aforementioned PUCCH transmission with N repetitions using the PUCCH Resource, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUCCH transmission in one or more slots within the N slots, or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of the N slots.

[0125] This signaling includes, but is not limited to: signaling that dynamically changes non-SBFD symbols to SBFD symbols. For example, this signaling, based on the DCI transmitted in the PDCCH, triggers at least one non-SBFD symbol used for PUCCH transmission to be changed to an SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within a non-SBFD symbol. For example, this signaling triggers at least one non-SBFD symbol used for PUCCH transmission to transmit an SSB.

[0126] The preset reason includes at least one of the following:

[0127] 1. In response to the fact that the PUCCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUCCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUCCH repetition not being sent.

[0128] 2. In response to the fact that the PUCCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUCCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0129] 3. In response to the fact that the PUCCH transmission is semi-statically configured, and in the SBFD symbol of the slot, the PUCCH repeat conflicts with the semi-static DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0130] 4. If the PUCCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUCCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUCCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0131] 5. In response to a PUCCH repetition (whether semi-statically configured or dynamically scheduled) and a symbol with dynamically changed attributes in the time domain conflict within the slot. For example, a symbol's attribute is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0132] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0133] In the third implementation of ALT1, when the second mode is determined to be a PUCCH transmission with N repetitions, N slots are determined starting from the initial slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of the N slots need to be determined based on predefined conditions (due to the differences in symbol configuration between slots, not all slots can be used for this PUCCH transmission). That is, the slots that satisfy one of the following conditions 1 and 2 are determined to be the slots where the N repetitions are located.

[0134] Condition 1: A slot can provide a first SBFD symbol, and M consecutive symbols starting from (and including) this first SBFD symbol are SBFD symbols, and the first M1 symbols of these M symbols do not contain SSB symbols (M1 is less than or equal to M). This can also be described as: A slot can provide a first SBFD symbol, and M1 consecutive symbols starting from (and including) this first SBFD symbol are SBFD symbols and do not contain SSB symbols. A slot satisfying this condition is determined as one of the N slots. The first SBFD symbol has the same symbol index as the starting symbol configured in the PUCCH Resource corresponding to the PUCCH transmission (e.g., the symbol index refers to the symbol index within the slot), and M1 is the number of symbols configured in the PUCCH Resource. Here, the SSB symbols can also be replaced with CORESET#0 symbols, semi-statically configured sensing channel / signal symbols, semi-statically configured symbols for adjusting AGC, or downlink common channel / signal symbols. Here, the SSB symbols can also include semi-statically configured SSB symbols, but do not include on-demand triggered SSB symbols.

[0135] The base station and UE agree that the symbol positions for the PUCCH transmission in the determined N slots are: starting from the first SBFD symbol mentioned above, for M1 consecutive SBFD symbols.

[0136] If, within the N slots determined based on the above conditions, the UE intends to perform the aforementioned PUCCH transmission with N repetitions using the PUCCH Resource, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUCCH transmission in one or more slots within the N slots, or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of the N slots.

[0137] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for PUCCH transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for PUCCH transmission to transmit an SSB.

[0138] The preset reasons include at least one of the following:

[0139] 1. In response to the fact that the PUCCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUCCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUCCH repetition not being sent.

[0140] 2. In response to the fact that the PUCCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUCCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0141] 3. In response to the fact that the PUCCH transmission is semi-statically configured, and in the SBFD symbol of the slot, the PUCCH repeat conflicts with the semi-static DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0142] 4. If the PUCCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUCCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUCCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0143] 5. In response to a PUCCH repetition (whether semi-statically configured or dynamically scheduled) and a symbol with dynamically changed attributes in the time domain conflict within the slot. For example, a symbol's attribute is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0144] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0145] Condition 2: A slot can provide a first UL symbol or a first F symbol not configured with an SBFD subband, and starting from this first symbol (inclusive), the M consecutive symbols are either UL symbols or F symbols not configured with an SBFD subband, and the first M1 symbols among these M symbols do not contain any SSB symbols (M1 is less than or equal to M). This can also be described as: A slot can provide a first UL symbol or a first F symbol not configured with an SBFD subband, and starting from this first symbol (inclusive), the M1 consecutive symbols are either UL symbols or F symbols not configured with an SBFD subband and do not contain any SSB symbols. A slot satisfying this condition is determined as one of the N slots. Wherein, the first symbol has the same symbol index as the starting symbol configured for the PUCCH Resource corresponding to the PUCCH transmission (e.g., the symbol index refers to the symbol index within the slot), and M1 is the number of symbols configured for the PUCCH Resource. Here, the SSB symbol can also be replaced with the CORESET#0 symbol, the semi-statically configured sensing channel / signal symbol, the semi-statically configured symbol for adjusting AGC, or the downlink common channel / signal symbol. The SSB symbol here can include semi-statically configured SSB symbols but excludes on-demand triggered SSB symbols.

[0146] The base station and UE agree that the symbol positions for performing the PUCCH transmission in the determined N slots are: starting from the first symbol mentioned above, the symbols are M1 consecutive UL symbols or F symbols that are not configured with SBFD subbands.

[0147] If, within the N slots determined based on the above conditions, the UE intends to perform the aforementioned PUCCH transmission with N repetitions using the PUCCH Resource, and due to the following preset reasons or the receipt of some signaling, the UE ultimately fails to perform the PUCCH transmission in one or more slots within the N slots, or causes the valid slot to become an invalid slot, then the UE counts that slot in the total number of the N slots.

[0148] This signaling includes, but is not limited to: signaling that dynamically changes non-SBFD symbols to SBFD symbols. For example, this signaling, based on the DCI transmitted in the PDCCH, triggers at least one non-SBFD symbol used for PUCCH transmission to be changed to an SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within a non-SBFD symbol. For example, this signaling triggers at least one non-SBFD symbol used for PUCCH transmission to transmit an SSB.

[0149] The preset reason includes at least one of the following:

[0150] 1. In response to the fact that the PUCCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUCCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUCCH repetition not being sent.

[0151] 2. In response to the fact that the PUCCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUCCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0152] 3. In response to the fact that the PUCCH transmission is semi-statically configured, and in the SBFD symbol of the slot, the PUCCH repeat conflicts with the semi-static DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0153] 4. If the PUCCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUCCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUCCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0154] 5. In response to a PUCCH repetition (whether semi-statically configured or dynamically scheduled) and a symbol with dynamically changed attributes in the time domain conflict within the slot. For example, a symbol's attribute is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0155] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0156] Rule 2 (ALT2)

[0157] Based on different implementation methods of the transmission mode, ALT2 has the following three implementation methods.

[0158] In the first implementation of ALT2, if the first mode is determined to be a PUCCH transmission with N repetitions, and the valid symbol type of the PUCCH transmission is determined to be SBFD symbol, then N slots are determined starting from the starting slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of the N slots need to be determined based on predefined conditions (due to the differences in symbol configuration between slots, not all slots can be used for this PUCCH transmission). That is, the slots that meet the following conditions are determined to be the slots where the N repetitions are located.

[0159] Condition: A slot can provide a first SBFD symbol, and M consecutive symbols starting from (and including) that first SBFD symbol are SBFD symbols. Alternatively, it can be described as: A slot can provide a first SBFD symbol, and M1 consecutive symbols starting from (and including) that first SBFD symbol are SBFD symbols. A slot satisfying this condition is determined as one of the N slots. Wherein, the first SBFD symbol has the same symbol index as the starting symbol configured in the PUCCH Resource corresponding to the PUCCH transmission (e.g., the symbol index refers to the symbol index within the slot), and M1 is the number of symbols configured in the PUCCH Resource.

[0160] The base station and UE agree that the symbol positions for the PUCCH transmission in the determined N slots are: starting from the first SBFD symbol mentioned above, for M1 consecutive SBFD symbols.

[0161] If, within the N slots determined based on the above conditions, the UE intends to perform the aforementioned PUCCH transmission with N repetitions using the PUCCH Resource, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUCCH transmission in one or more slots within the N slots, or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of the N slots.

[0162] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for PUCCH transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for PUCCH transmission to transmit an SSB.

[0163] The preset reasons include at least one of the following:

[0164] 1. In response to the fact that the PUCCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUCCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUCCH repetition not being sent.

[0165] 2. In response to the fact that the PUCCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUCCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0166] 3. In response to the fact that the PUCCH transmission is semi-statically configured, and in the SBFD symbol of the slot, the PUCCH repeat conflicts with the semi-static DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0167] 4. If the PUCCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUCCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUCCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0168] 5. In response to a PUCCH repetition (whether semi-statically configured or dynamically scheduled) and an SSB time-domain conflict within the slot and SBFD symbol, the PUCCH repetition is not transmitted. Here, the SSB symbol can also be replaced by the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbol here can include semi-statically configured SSB symbols, but does not include on-demand triggered SSB symbols.

[0169] 6. In response to a PUCCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes have been dynamically changed in the time domain conflicting within the slot. For example, the attribute of a symbol is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0170] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0171] In the second implementation of ALT2, if the first mode is determined to be a PUCCH transmission with N repetitions, and the valid symbol type of the PUCCH transmission is determined to be non-SBFD symbol, then N slots are determined starting from the starting slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of the N slots need to be determined based on predefined conditions (due to the differences in symbol configuration between slots, not all slots can be used for this PUCCH transmission). That is, the slots that meet the following conditions are determined to be the slots where the N repetitions are located.

[0172] Condition: A slot can provide a first UL symbol or a first F symbol without a configured SBFD subband, and M consecutive symbols starting from (inclusive) this first symbol are either UL symbols or F symbols without a configured SBFD subband. Alternatively, it can be described as: A slot can provide a first UL symbol or a first F symbol without a configured SBFD subband, and M1 consecutive symbols starting from (inclusive) this first symbol are either UL symbols or F symbols without a configured SBFD subband. A slot satisfying this condition is determined as one of the N slots. Wherein, the first symbol has the same symbol index as the starting symbol configured for the PUCCH Resource corresponding to the PUCCH transmission (e.g., the symbol index refers to the symbol index within the slot), and M1 is the number of symbols configured for the PUCCH Resource.

[0173] The base station and UE agree that the symbol positions for performing the PUCCH transmission in the determined N slots are: starting from the first symbol mentioned above, the symbols are M1 consecutive UL symbols or F symbols that are not configured with SBFD subbands.

[0174] If, within the N slots determined based on the above conditions, the UE intends to perform the aforementioned PUCCH transmission with N repetitions using the PUCCH Resource, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUCCH transmission in one or more slots within the N slots, or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of the N slots.

[0175] This signaling includes, but is not limited to: signaling that dynamically changes non-SBFD symbols to SBFD symbols. For example, this signaling, based on the DCI transmitted in the PDCCH, triggers at least one non-SBFD symbol used for PUCCH transmission to be changed to an SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within a non-SBFD symbol. For example, this signaling triggers at least one non-SBFD symbol used for PUCCH transmission to transmit an SSB.

[0176] The preset reasons include at least one of the following:

[0177] 1. In response to the fact that the PUCCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUCCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUCCH repetition not being sent.

[0178] 2. In response to the fact that the PUCCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUCCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0179] 3. In response to the fact that the PUCCH transmission is semi-statically configured, and in the SBFD symbol of the slot, the PUCCH repeat conflicts with the semi-static DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0180] 4. If the PUCCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUCCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUCCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0181] 5. In response to a PUCCH repetition (whether semi-statically configured or dynamically scheduled) and a symbol with dynamically changed attributes in the time domain conflict within the slot. For example, a symbol's attribute is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0182] 6. In response to a PUCCH repetition (whether semi-statically configured or dynamically scheduled) conflicting with an SSB in the time domain within the slot and SBFD symbol, the PUCCH repetition is not transmitted. Here, the SSB symbol can also be replaced by the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbol here can include semi-statically configured SSB symbols, but does not include on-demand triggered SSB symbols.

[0183] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0184] In the third implementation of ALT2, when the second mode is determined to be a PUCCH transmission with N repetitions, N slots are determined starting from the initial slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of the N slots need to be determined based on predefined conditions (due to the differences in symbol configuration between slots, not all slots can be used for this PUCCH transmission). That is, the slots that satisfy one of the following conditions 3 and 4 are determined to be the slots where the N repetitions are located.

[0185] Condition 3: A slot can provide a first SBFD symbol, and M consecutive symbols starting from (and including) that first SBFD symbol are SBFD symbols. This can also be described as: A slot can provide a first SBFD symbol, and M1 consecutive symbols starting from (and including) that first SBFD symbol are SBFD symbols. The slot satisfying this condition is determined as one of the N slots. Wherein, the first SBFD symbol has the same symbol index as the starting symbol configured in the PUCCH Resource corresponding to the PUCCH transmission (e.g., the symbol index refers to the symbol index within the slot), and M1 is the number of symbols configured in the PUCCH Resource.

[0186] The base station and UE agree that the symbol positions for the PUCCH transmission in the determined N slots are: starting from the first SBFD symbol mentioned above, for M1 consecutive SBFD symbols.

[0187] If, within the N slots determined based on the above conditions, the UE intends to perform the aforementioned PUCCH transmission with N repetitions using the PUCCH Resource, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUCCH transmission in one or more slots within the N slots, or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of the N slots.

[0188] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for PUCCH transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for PUCCH transmission to transmit an SSB.

[0189] The preset reasons include at least one of the following:

[0190] 1. In response to the fact that the PUCCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUCCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUCCH repetition not being sent.

[0191] 2. In response to the fact that the PUCCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUCCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0192] 3. In response to the fact that the PUCCH transmission is semi-statically configured, and in the SBFD symbol of the slot, the PUCCH repeat conflicts with the semi-static DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0193] 4. If the PUCCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUCCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUCCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0194] 5. In response to a PUCCH repetition (whether semi-statically configured or dynamically scheduled) and an SSB time-domain conflict within the slot and SBFD symbol, the PUCCH repetition is not transmitted. Here, the SSB symbol can also be replaced by the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbol here can include semi-statically configured SSB symbols but excludes on-demand triggered SSB symbols.

[0195] 6. In response to a PUCCH repetition (whether semi-statically configured or dynamically scheduled) and a symbol with dynamically changed attributes in the time domain conflict within the slot. For example, a symbol's attribute is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0196] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0197] Condition 4: A slot can provide a first UL symbol or a first F symbol without a configured SBFD subband, and M consecutive symbols starting from (inclusive) this first symbol are either UL symbols or F symbols without a configured SBFD subband. This can also be described as: A slot can provide a first UL symbol or a first F symbol without a configured SBFD subband, and M1 consecutive symbols starting from (inclusive) this first symbol are either UL symbols or F symbols without a configured SBFD subband. A slot satisfying this condition is determined as one of the N slots. Wherein, the first symbol has the same symbol index as the starting symbol configured for the PUCCH Resource corresponding to the PUCCH transmission (e.g., the symbol index refers to the symbol index within the slot), and M1 is the number of symbols configured for the PUCCH Resource.

[0198] The base station and UE agree that the symbol positions for performing the PUCCH transmission in the determined N slots are: starting from the first symbol mentioned above, the symbols are M1 consecutive UL symbols or F symbols that are not configured with SBFD subbands.

[0199] If, within the N slots determined based on the above conditions, the UE intends to perform the aforementioned PUCCH transmission with N repetitions using the PUCCH Resource, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUCCH transmission in one or more slots within the N slots, or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of the N slots.

[0200] This signaling includes, but is not limited to: signaling that dynamically changes non-SBFD symbols to SBFD symbols. For example, this signaling, based on the DCI transmitted in the PDCCH, triggers at least one non-SBFD symbol used for PUCCH transmission to be changed to an SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within a non-SBFD symbol. For example, this signaling triggers at least one non-SBFD symbol used for PUCCH transmission to transmit an SSB.

[0201] The preset reasons include at least one of the following:

[0202] 1. In response to the fact that the PUCCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUCCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUCCH repetition not being sent.

[0203] 2. In response to the fact that the PUCCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUCCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0204] 3. In response to the fact that the PUCCH transmission is semi-statically configured, and in the SBFD symbol of the slot, the PUCCH repeat conflicts with the semi-static DL transmission in the time domain, resulting in the PUCCH repeat not being sent.

[0205] 4. If the PUCCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUCCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUCCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0206] 5. In response to a PUCCH repetition (whether semi-statically configured or dynamically scheduled) and an SSB time-domain conflict within the slot and SBFD symbol, the PUCCH repetition is not transmitted. Here, the SSB symbol can also be replaced by the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbol here can include semi-statically configured SSB symbols, but does not include on-demand triggered SSB symbols.

[0207] 6. In response to a PUCCH repetition (whether semi-statically configured or dynamically scheduled) and a symbol with dynamically changed attributes in the time domain conflict within the slot. For example, a symbol's attribute is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0208] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0209] Example 2: PUSCH transmission with N PUSCH repetitions

[0210] For a PUSCH transmission carrying a transport block TB, it belongs to PUSCH (repetition type A) repetitiontype A, has N repetitions, and is configured with a valid slot count, meaning a PUSCH transmission needs to be repeated N times. The size of the TB must meet at least one of the following requirements: the TB can be transmitted in only one slot, or the TB needs to be transmitted in K slots. In other words, if a PUSCH transmission repeated N times carries a TB that requires K slots to complete, then one repetition of the PUSCH transmission requires K slots. If the PUSCH transmission is repeated N times, then it requires N*K slots. Here, we assume K is an integer greater than or equal to 1. This covers both cases of TB size. For this PUSCH transmission, the base station and UE agree on the following rules (Alts) to determine the N*K slots corresponding to the valid time slots of this PUSCH transmission. K corresponds to the number of slots required for one TB to be transmitted. N is the number of repetitions. Assuming a TB requires 2 slots to complete the transmission, and the PUSCH transmission carrying this TB is configured to repeat 4 times, then 8 slots are needed to complete the PUSCH transmission. For example, the first two slots complete the first transmission of the TB, which is also the first repetition of the PUSCH. In other words, one repetition of the PUSCH transmission requires 2 slots. If K equals 1, then a TB typically requires 1 slot to complete the transmission. If N equals 1, the PUSCH does not need to be repeated. If N equals 1 and K is greater than 1, then to allow the TB to span K slots, the PUSCH transmission still needs to span K slots.

[0211] Rule 3 (ALT3)

[0212] Based on different implementation methods of transmission modes, ALT3 has the following three implementation methods.

[0213] In the first implementation of ALT3, the first mode is determined to be a PUSCH transmission with N repetitions, and the PUSCH carries a TB (which includes transmissions across multiple slots). The valid symbol type for the PUSCH transmission is determined to be SBFD symbols. Then, N*K slots are determined starting from the initial slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of the N slots need to be determined based on predefined conditions (due to differences in symbol configuration between slots, not all slots can be used for this PUSCH transmission). A slot that meets the following conditions is determined as one of the N*K slots.

[0214] Condition: If, within a slot, all symbols containing the PUSCH resource corresponding to the PUSCH transmission are SBFD symbols and these SBFD symbols do not contain SSB symbols, then that slot is determined to be one of the N*K slots. Alternatively, it can be described as follows: If, within a slot, at least one symbol among the symbols containing the PUSCH resource corresponding to the PUSCH transmission is a non-SBFD symbol, or at least one symbol is an SBFD symbol and contains an SSB symbol, then that slot is not determined to be one of the N*K slots; otherwise, that slot is determined to be one of the N*K slots. The symbols containing the PUSCH resource are configured or determined based on configuration signaling. Here, the SSB symbols can also be replaced with CORESET#0 symbols, semi-statically configured sensing channel / signal symbols, semi-statically configured symbols for adjusting AGC, or downlink common channel / signal symbols. Here, the SSB symbols also include semi-statically configured SSB symbols or exclude on-demand triggered SSB symbols.

[0215] The base station and the UE agree that the PUSCH resource will be used for all PUSCH transmissions within the determined N*K slots. That is, the PUSCH transmission will be performed at the same symbol position within the determined N*K slots.

[0216] If, when valid slot counting is enabled, within the N*K slots determined based on the above conditions, the UE attempts to perform a PUSCH repetition type A PUSCH transmission (N is greater than 1 or the TB carried by the PUSCH spans K slots) using the PUSCH resources, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUSCH transmission in one or more slots within the N*K slots, or causes the valid slot to become an invalid slot, then the UE will still count the slot in the number of N*K slots.

[0217] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for PUSCH transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for PUSCH transmission to transmit an SSB.

[0218] The preset reasons include at least one of the following:

[0219] 1. In response to the fact that the PUSCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUSCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUSCH repetition not being sent.

[0220] 2. In response to the fact that the PUSCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUSCH repeat not being sent.

[0221] 3. In response to the fact that the PUSCH transmission is semi-statically configured, and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent.

[0222] 4. If the PUSCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUSCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUSCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0223] 5. In response to a PUSCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes are dynamically changed in the time domain conflicting within the slot. For example, a symbol's attributes are changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0224] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0225] In the second implementation of ALT3, the first mode is determined to be a PUSCH transmission with N repetitions, and the PUSCH carries a TB (which includes the execution of transmissions across multiple slots). The valid symbol type of the PUSCH transmission is determined to be non-SBFD symbols. Then, N*K slots are determined starting from the initial slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of the N slots need to be determined based on predefined conditions (due to the differences in symbol configuration between slots, not all slots can be used for this PUSCH transmission). The slot that satisfies the following conditions is determined as one of the N*K slots.

[0226] Condition: If, within a slot, all symbols containing the PUSCH resource corresponding to the PUSCH transmission are UL symbols or F symbols without SSBs and not configured with SBFD subbands, then that slot is determined as one of the N*K slots. The symbols containing the PUSCH resource are configured or determined based on configuration signaling. Here, the SSB symbols can also be replaced with CORESET#0 symbols, semi-statically configured sensing channel / signal symbols, semi-statically configured symbols for adjusting AGC, or downlink common channel / signal symbols. The SSB symbols here also include semi-statically configured SSB symbols, but do not include on-demand triggered SSB symbols.

[0227] The base station and the UE agree that the PUSCH resource will be used for all PUSCH transmissions within the determined N*K slots. That is, the PUSCH transmission will be performed at the same symbol position within the determined N*K slots.

[0228] If, when valid slot counting is enabled, within the N*K slots determined based on the above conditions, the UE attempts to perform a PUSCH repetition type A PUSCH transmission (N is greater than 1 or the TB carried by the PUSCH spans K slots) using the PUSCH resources, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUSCH transmission in one or more slots within the N*K slots or causes the valid slot to become an invalid slot, then the UE will still count the slot in the number of N*K slots.

[0229] This signaling includes, but is not limited to: signaling that dynamically changes non-SBFD symbols to SBFD symbols. For example, this signaling, based on the DCI in the PDCCH, triggers at least one non-SBFD symbol used for PUSCH transmission to be changed to an SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within a non-SBFD symbol. For example, this signaling triggers at least one non-SBFD symbol used for PUSCH transmission to transmit an SSB.

[0230] The preset reasons include at least one of the following:

[0231] 1. In response to the fact that the PUSCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUSCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUSCH repetition not being sent.

[0232] 2. In response to the fact that the PUSCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUSCH repeat not being sent.

[0233] 3. In response to the fact that the PUSCH transmission is semi-statically configured, and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent.

[0234] 4. If the PUSCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUSCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUSCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0235] 5. In response to a PUSCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol with dynamically changed attributes in the time domain conflict within the slot. For example, a symbol's attribute is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0236] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0237] In the third implementation of ALT3, in the second mode, a PUSCH transmission with N repetitions is determined, and the PUSCH carries a TB (which includes the execution of transmissions across multiple slots). Then, N*K slots are determined starting from the initial slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of the N slots need to be determined based on predefined conditions (due to the differences in symbol configuration between slots, not all slots can be used for this PUSCH transmission). The slot that satisfies one of the following conditions 5 and 6 is determined as one of the N*K slots.

[0238] Condition 5: If, within a slot, all symbols containing the PUSCH resource corresponding to the PUSCH transmission are SBFD symbols and these SBFD symbols do not contain SSB symbols, then the slot is determined to be one of the N*K slots. Alternatively, it can be described as follows: If, within a slot, at least one symbol among the symbols containing the PUSCH resource corresponding to the PUSCH transmission is a non-SBFD symbol, or at least one symbol is an SBFD symbol and contains an SSB symbol, then the slot is not determined to be one of the N*K slots; otherwise, the slot is determined to be one of the N*K slots. The symbols containing the PUSCH resource are configured or determined based on configuration signaling. Here, the SSB symbols can also be replaced with CORESET#0 symbols, semi-statically configured sensing channel / signal symbols, semi-statically configured symbols for adjusting AGC, or downlink common channel / signal symbols. Here, the SSB symbols can include semi-statically configured SSB symbols but exclude on-demand triggered SSB symbols.

[0239] The base station and the UE agree that the PUSCH resource will be used for all PUSCH transmissions within the determined N*K slots. That is, the PUSCH transmission will be performed at the same symbol position within the determined N*K slots.

[0240] If, when valid slot counting is enabled, within the N*K slots determined based on the above conditions, the UE attempts to perform a PUSCH repetition type A PUSCH transmission (N is greater than 1 or the TB carried by the PUSCH spans K slots) using the PUSCH resources, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUSCH transmission in one or more slots within the N*K slots, or causes the valid slot to become an invalid slot, then the UE will still count the slot in the number of N*K slots.

[0241] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for PUSCH transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for PUSCH transmission to transmit an SSB.

[0242] The preset reasons include at least one of the following:

[0243] 1. In response to the fact that the PUSCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUSCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUSCH repetition not being sent.

[0244] 2. In response to the fact that the PUSCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUSCH repeat not being sent.

[0245] 3. In response to the fact that the PUSCH transmission is semi-statically configured, and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent.

[0246] 4. If the PUSCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUSCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUSCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0247] 5. In response to a PUSCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol with dynamically changed attributes in the time domain conflict within the slot. For example, a symbol's attribute is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0248] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0249] Condition 6: If, within a slot, all symbols containing the PUSCH resource corresponding to the PUSCH transmission are UL symbols or F symbols without SSBs and not configured with SBFD subbands, then that slot is determined as one of the N*K slots. The symbols containing the PUSCH resource are configured or determined based on configuration signaling. Here, the SSB symbols can also be replaced with CORESET#0 symbols, semi-statically configured sensing channel / signal symbols, semi-statically configured symbols for adjusting AGC, or downlink common channel / signal symbols. The SSB symbols here also include semi-statically configured SSB symbols, but do not include on-demand triggered SSB symbols.

[0250] The base station and the UE agree that the PUSCH resource will be used for all PUSCH transmissions within the determined N*K slots. That is, the PUSCH transmission will be performed at the same symbol position within the determined N*K slots.

[0251] If, when valid slot counting is enabled, within the N*K slots determined based on the above conditions, the UE attempts to perform a PUSCH repetition type A PUSCH transmission (N is greater than 1 or the TB carried by the PUSCH spans K slots) using the PUSCH resources, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUSCH transmission in one or more slots within the N*K slots or causes the valid slot to become an invalid slot, then the UE will still count the slot in the number of N*K slots.

[0252] This signaling includes, but is not limited to: signaling that dynamically changes non-SBFD symbols to SBFD symbols. For example, this signaling, based on the DCI in the PDCCH, triggers at least one non-SBFD symbol used for PUSCH transmission to be changed to an SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within a non-SBFD symbol. For example, this signaling triggers at least one non-SBFD symbol used for PUSCH transmission to transmit an SSB.

[0253] The preset reasons include at least one of the following:

[0254] 1. In response to the fact that the PUSCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUSCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUSCH repetition not being sent.

[0255] 2. In response to the fact that the PUSCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUSCH repeat not being sent.

[0256] 3. In response to the fact that the PUSCH transmission is semi-statically configured, and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent.

[0257] 4. If the PUSCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUSCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUSCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0258] 5. In response to a PUSCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol with dynamically changed attributes in the time domain conflict within the slot. For example, a symbol's attribute is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0259] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0260] Rule 4 (ALT4)

[0261] Based on different implementation methods of transmission modes, ALT4 has the following three implementation methods.

[0262] In the first implementation of ALT4, the first mode is determined to be a PUSCH transmission with N repetitions, and the PUSCH carries a TB (which includes the execution of transmissions across multiple slots). The valid symbol type of the PUSCH transmission is determined to be SBFD symbols. Then, N*K slots are determined starting from the initial slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of the N slots need to be determined based on predefined conditions (due to the differences in symbol configuration between slots, not all slots can be used for this PUSCH transmission). The slot that satisfies the following conditions is determined as one of the N*K slots.

[0263] Condition: If, within a slot, all symbols containing the PUSCH resource corresponding to the PUSCH transmission are SBFD symbols, then that slot is determined to be one of the N*K slots. The symbol containing the PUSCH resource is configured or determined based on configuration signaling.

[0264] The base station and the UE agree that the PUSCH resource will be used for all PUSCH transmissions within the determined N*K slots. That is, the PUSCH transmission will be performed at the same symbol position within the determined N*K slots.

[0265] If, when valid slot counting is enabled, within the N*K slots determined based on the above conditions, the UE attempts to perform a PUSCH repetition type A PUSCH transmission (N is greater than 1 or the TB carried by the PUSCH spans K slots) using the PUSCH resources, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUSCH transmission in one of the N*K slots or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of N*K slots.

[0266] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for PUSCH transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for PUSCH transmission to transmit an SSB.

[0267] The preset reasons include at least one of the following:

[0268] 1. In response to the fact that the PUSCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUSCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUSCH repetition not being sent.

[0269] 2. In response to the fact that the PUSCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUSCH repeat not being sent.

[0270] 3. In response to the fact that the PUSCH transmission is semi-statically configured, and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent.

[0271] 4. If the PUSCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUSCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUSCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0272] 5. A PUSCH repetition (whether semi-statically configured or dynamically scheduled) conflicts with an SSB in the time domain within the slot and SBFD symbol, causing the PUSCH repetition to not be transmitted. Here, the SSB symbol can also be replaced by the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbol here can include semi-statically configured SSB symbols but excludes on-demand triggered SSB symbols.

[0273] 6. In response to a PUSCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes have been dynamically changed in the time domain conflicting within the slot. For example, the attribute of a symbol is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0274] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0275] In the second implementation of ALT4, the first mode is determined to be a PUSCH transmission with N repetitions, and the PUSCH carries a TB (which includes the execution of transmissions across multiple slots). The valid symbol type of the PUSCH transmission is determined to be non-SBFD symbols. Then, N*K slots are determined starting from the initial slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of the N slots need to be determined based on predefined conditions (due to the differences in symbol configuration between slots, not all slots can be used for this PUSCH transmission). The slot that satisfies the following conditions is determined as one of the N*K slots.

[0276] Condition: If, within a slot, all symbols containing the PUSCH resource corresponding to the PUSCH transmission are UL symbols or F symbols not configured with SBFD subbands, then that slot is determined to be one of the N*K slots. The symbols containing the PUSCH resource are configured or determined based on configuration signaling. Here, the SSB symbols can also be replaced with CORESET#0 symbols, semi-statically configured sensing channel / signal symbols, semi-statically configured symbols for adjusting AGC, or downlink common channel / signal symbols. The SSB symbols here also include semi-statically configured SSB symbols, but do not include on-demand triggered SSB symbols.

[0277] The base station and the UE agree that the PUSCH resource will be used for all PUSCH transmissions within the determined N*K slots. That is, the PUSCH transmission will be performed at the same symbol position within the determined N*K slots.

[0278] If, when valid slot counting is enabled, within the N*K slots determined based on the above conditions, the UE attempts to perform a PUSCH repetition type A PUSCH transmission (N is greater than 1 or the TB carried by the PUSCH spans K slots) using the PUSCH resources, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUSCH transmission in one or more slots within the N*K slots or causes the valid slot to become an invalid slot, then the UE will still count the slot in the number of N*K slots.

[0279] This signaling includes, but is not limited to: signaling that dynamically changes non-SBFD symbols to SBFD symbols. For example, this signaling, based on the DCI in the PDCCH, triggers at least one non-SBFD symbol used for PUSCH transmission to be changed to an SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within a non-SBFD symbol. For example, this signaling triggers at least one non-SBFD symbol used for PUSCH transmission to transmit an SSB.

[0280] The preset reasons include at least one of the following:

[0281] 1. In response to the fact that the PUSCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUSCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUSCH repetition not being sent.

[0282] 2. In response to the fact that the PUSCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUSCH repeat not being sent.

[0283] 3. In response to the fact that the PUSCH transmission is semi-statically configured, and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent.

[0284] 4. If the PUSCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUSCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUSCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0285] 5. In response to a PUSCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol with dynamically changed attributes in the time domain conflict within the slot. For example, a symbol's attribute is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0286] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0287] In the third implementation of ALT4, the second mode is determined to be a PUSCH transmission with N repetitions, and the PUSCH carries a TB (which includes the execution of transmissions across multiple slots). Then, N*K slots are determined starting from the initial slot configured by RRC signaling or indicated by dynamic signaling. The specific positions of the N slots need to be determined based on predefined conditions (due to the differences in symbol configuration between slots, not all slots can be used for this PUSCH transmission). The slot that satisfies one of the following conditions 7 and 8 is determined as one of the N*K slots.

[0288] Condition 7: If, within a slot, all symbols containing the PUSCH resource corresponding to the PUSCH transmission are SBFD symbols, then that slot is determined to be one of the N*K slots. The symbol containing the PUSCH resource is configured or determined based on configuration signaling.

[0289] The base station and the UE agree that the PUSCH resource will be used for all PUSCH transmissions within the determined N*K slots. That is, the PUSCH transmission will be performed at the same symbol position within the determined N*K slots.

[0290] If, when valid slot counting is enabled, within the N*K slots determined based on the above conditions, the UE attempts to perform a PUSCH repetition type A PUSCH transmission (N is greater than 1 or the TB carried by the PUSCH spans K slots) using the PUSCH resources, and due to at least one of the following preset reasons or the receipt of some signaling, the UE ultimately fails to perform the PUSCH transmission in one of the N*K slots or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of N*K slots.

[0291] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for PUSCH transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for PUSCH transmission to transmit an SSB.

[0292] The preset reasons include at least one of the following:

[0293] 1. In response to the fact that the PUSCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUSCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUSCH repetition not being sent.

[0294] 2. In response to the fact that the PUSCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUSCH repeat not being sent.

[0295] 3. In response to the fact that the PUSCH transmission is semi-statically configured, and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent.

[0296] 4. If the PUSCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUSCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUSCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0297] 5. A PUSCH repetition (whether semi-statically configured or dynamically scheduled) conflicts with an SSB in the time domain within the slot and SBFD symbol, causing the PUSCH repetition to not be transmitted. Here, the SSB symbol can also be replaced by the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbol here can include semi-statically configured SSB symbols but excludes on-demand triggered SSB symbols.

[0298] 6. In response to a PUSCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes have been dynamically changed in the time domain conflicting within the slot. For example, the attribute of a symbol is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0299] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0300] Condition 8: If, within a slot, all symbols containing the PUSCH resource corresponding to the PUSCH transmission are UL symbols or F symbols not configured with SBFD subbands, then that slot is determined to be one of the N*K slots. The symbols containing the PUSCH resource are configured or determined based on configuration signaling.

[0301] The base station and the UE agree that the PUSCH resource will be used for all PUSCH transmissions within the determined N*K slots. That is, the PUSCH transmission will be performed at the same symbol position within the determined N*K slots.

[0302] If, when valid slot counting is enabled, within the N*K slots determined based on the above conditions, the UE attempts to perform a PUSCH repetition type A PUSCH transmission (N is greater than 1 or the TB carried by the PUSCH spans K slots) using the PUSCH resources, and due to the following preset reasons or receiving some signaling, the UE ultimately fails to perform the PUSCH transmission in one of the N*K slots or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of N*K slots.

[0303] This signaling includes, but is not limited to: signaling that dynamically changes non-SBFD symbols to SBFD symbols. For example, this signaling, based on the DCI in the PDCCH, triggers at least one non-SBFD symbol used for PUSCH transmission to be changed to an SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within a non-SBFD symbol. For example, this signaling triggers at least one non-SBFD symbol used for PUSCH transmission to transmit an SSB.

[0304] The preset reason includes at least one of the following:

[0305] 1. In response to the fact that the PUSCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUSCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUSCH repetition not being sent.

[0306] 2. In response to the fact that the PUSCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUSCH repeat not being sent.

[0307] 3. In response to the fact that the PUSCH transmission is semi-statically configured, and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent.

[0308] 4. If the PUSCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUSCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUSCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0309] 5. A PUSCH repetition (whether semi-statically configured or dynamically scheduled) conflicts with an SSB in the time domain within the slot and SBFD symbol, causing the PUSCH repetition to not be transmitted. Here, the SSB symbol can also be replaced by the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbol here can include semi-statically configured SSB symbols but excludes on-demand triggered SSB symbols.

[0310] 6. In response to a PUSCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes have been dynamically changed in the time domain conflicting within the slot. For example, the attribute of a symbol is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0311] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0312] For non-DCI activated type 1 and type 2 PUSCH transfers with configuration authorization, where the PUSCH also has N repetitions, the same method as PUSCH repetition type A can be used (e.g., N greater than 1 but K = 1). For example, the method in the first mode or the method in the second mode of Alt3 above, or the method in the first mode or the method in the second mode of Alt4 above. Some examples are provided below; the remaining examples are based on the same principle.

[0313] If the method in the first mode of Alt3 is used, then:

[0314] If, within the N*K slots determined based on the above conditions, the UE attempts to perform the aforementioned type 1 and type 2 PUSCH transmissions in one of the slots by using the PUSCH transmission corresponding to the PUSCH resource, but due to the following preset reasons or receiving some signaling, the UE (ultimately) omits the execution of the PUSCH transmission in that slot or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of N*K slots.

[0315] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for PUSCH transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for PUSCH transmission to transmit an SSB.

[0316] The preset reasons include at least one of the following:

[0317] 1. In response to the fact that the PUSCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUSCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUSCH repetition not being sent.

[0318] 2. In response to the fact that the PUSCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUSCH repeat not being sent.

[0319] 3. In response to the fact that the PUSCH transmission is semi-statically configured, and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent.

[0320] 4. If the PUSCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUSCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUSCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0321] 5. In response to a PUSCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes are dynamically changed in the time domain conflicting within the slot. For example, a symbol's attributes are changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0322] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0323] For a DCI-activated type 2 PUSCH transport with configuration authorization carrying a TB spanning K slots, and the PUSCH also having N repetitions, the same method as PUSCH repetition type A can be used (e.g., N equals / greater than 1 and K is greater than 1). For example, the methods in the first or second mode of Alt3 above, or the methods in the first or second mode of Alt4 above. Some examples are provided below; the remaining examples are based on the same principle.

[0324] If the method in the first mode of Alt3 is used, then:

[0325] If, within the N*K slots determined based on the above conditions, the UE attempts to perform a type 2 PUSCH transmission in one of the slots by using the PUSCH transmission corresponding to the PUSCH resource, but due to the following preset reasons or receiving some signaling, the UE (ultimately) omits the PUSCH transmission in that slot or causes the valid slot to become an invalid slot, then the UE will still count that slot in the total number of N*K slots.

[0326] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for PUSCH transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for PUSCH transmission to transmit an SSB.

[0327] The preset reasons include at least one of the following:

[0328] 1. In response to the fact that the PUSCH transmission is dynamically scheduled, and in the SBFD symbol in the slot, the PUSCH repetition conflicts with the dynamic DL transmission in the time domain (i.e., overlaps in the time domain, the same below), resulting in the PUSCH repetition not being sent.

[0329] 2. In response to the fact that the PUSCH transmission is semi-statically configured and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the dynamic DL transmission in the time domain, resulting in the PUSCH repeat not being sent.

[0330] 3. In response to the fact that the PUSCH transmission is semi-statically configured, and in the SBFD symbol in the slot, the PUSCH repeat conflicts with the semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent.

[0331] 4. If the PUSCH transmission is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the PUSCH duplicate conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the PUSCH duplicate to not be transmitted. Here, "high priority" refers to the highest priority when the base station is configured with both high-priority and low-priority transmissions; in this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0332] 5. In response to a PUSCH recurrence (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes are dynamically changed in the time domain conflicting within the slot. For example, a symbol's attributes are changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0333] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0334] Example 3: Aperiodic SRS

[0335] For an aperiodic SRS (A-SRS) transmission with a valid slot count (hereinafter referred to as A-SRS), the base station and UE agree on the following rules (Alts) to determine the valid slots of the A-SRS.

[0336] Rule 5 (ALT5)

[0337] In the first implementation of ALT5, if the first mode is determined to be an A-SRS transmission with a valid slot count, and the valid symbol type of the A-SRS transmission is determined to be SBFD symbol, then the slot that satisfies the following conditions is determined to be the valid slot of the A-SRS, and the A-SRS is transmitted in the determined valid slot.

[0338] Condition: In a slot, if all SRS resources in the SRS resource set corresponding to the A-SRS are SBFD symbols in the time domain and do not contain SSB symbols, and the UE capability satisfies the minimum timing requirement between the PDCCH that triggers the A-SRS and all the SRS resources, then the slot is determined to be a valid slot. The symbol positions of all SRS resources within the slot are configured by signaling.

[0339] Here, the SSB symbol can also be replaced with the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbol here includes semi-statically configured SSB symbols but excludes on-demand triggered SSB symbols.

[0340] The base station and UE agree that within the determined valid slot, A-SRS transmission will be performed based on the symbols configured for that A-SRS. From the first symbol of the PDCCH containing the DCI that triggered the A-SRS to the last symbol of the SRS-ResourceSet (containing all symbols of SRS resources) corresponding to the A-SRS, the UE does not expect the valid slot to become invalid due to the following preset reasons or the receipt of some signaling (e.g., the valid slot no longer meets the above conditions, causing A-SRS to ultimately not be transmitted in the valid slot).

[0341] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for the A-SRS transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for the A-SRS transmission to transmit an SSB.

[0342] The preset reasons include at least one of the following:

[0343] 1. In response to the fact that the A-SRS is dynamically scheduled and that the A-SRS and the dynamic DL transmission in the SBFD symbol in the slot conflict in the time domain (i.e. overlap in the time domain, the same below), the A-SRS is not sent.

[0344] 2. In response to the fact that the A-SRS is semi-statically configured and in the SBFD symbol in the slot, the A-SRS conflicts with the dynamic DL transmission in the time domain, resulting in the A-SRS not being sent.

[0345] 3. In response to the fact that the A-SRS is semi-statically configured and in the SBFD symbol in the slot, the A-SRS conflicts with the semi-static DL transmission in the time domain, resulting in the A-SRS not being sent.

[0346] 4. If the A-SRS is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the A-SRS conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the A-SRS not to be transmitted. Here, "high priority" refers to the highest priority transmission configured when both high and low priority transmissions are available at the base station. In this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0347] 5. In response to a temporal conflict in the slot between the A-SRS (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes are dynamically changed. For example, the attribute of a symbol is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0348] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0349] In the second implementation of ALT5, if the first mode is determined to be an A-SRS with a valid slot count, and the valid symbol type of the A-SRS transmission is determined to be a non-SBFD symbol, then the slot that satisfies the following conditions is determined to be the valid slot of the A-SRS, and the A-SRS is transmitted in the determined valid slot.

[0350] Conditions: In a slot, if all SRS resources in the SRS-ResourceSet corresponding to the A-SRS are non-SBFD symbols in the time domain and do not contain SSB symbols, and the UE capability satisfies the minimum timing requirement between the PDCCH that triggers the A-SRS and all the SRS resources, then the slot is determined to be a valid slot. The symbol positions of all SRS resources in the slot are configured by signaling. Non-SBFD symbols include UL symbols and F symbols that are not configured with SBFD subbands.

[0351] Here, the SSB symbol can also be replaced with the CORESET#0 symbol, the semi-statically configured sensing channel / signal symbol, the semi-statically configured symbol for adjusting AGC, or the downlink common channel / signal symbol. The SSB symbol here can include semi-statically configured SSB symbols but excludes on-demand triggered SSB symbols.

[0352] The base station and UE agree that within the determined valid slot, A-SRS transmission will be performed based on the symbols configured for that A-SRS. From the first symbol of the PDCCH containing the DCI that triggered the A-SRS to the last symbol of the SRS-ResourceSet (containing all symbols of SRS resources) corresponding to the A-SRS, the UE does not expect the valid slot to become invalid due to the following preset reasons or the receipt of some signaling (e.g., the valid slot no longer meets the above conditions, causing A-SRS to ultimately not be transmitted in the valid slot).

[0353] This signaling includes, but is not limited to: signaling that dynamically changes non-SBFD symbols to SBFD symbols. For example, this signaling is transmitted based on DCI in PDCCH, triggering at least one non-SBFD symbol used for the A-SRS transmission to be changed to an SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within a non-SBFD symbol. For example, this signaling triggers at least one non-SBFD symbol used for the A-SRS transmission to transmit an SSB.

[0354] The preset reasons include at least one of the following:

[0355] 1. In response to the fact that the A-SRS is dynamically scheduled and that the A-SRS and the dynamic DL transmission in the SBFD symbol in the slot conflict in the time domain (i.e. overlap in the time domain, the same below), the A-SRS is not sent.

[0356] 2. In response to the fact that the A-SRS is semi-statically configured and in the SBFD symbol in the slot, the A-SRS conflicts with the dynamic DL transmission in the time domain, resulting in the A-SRS not being sent.

[0357] 3. In response to the fact that the A-SRS is semi-statically configured and in the SBFD symbol in the slot, the A-SRS conflicts with the semi-static DL transmission in the time domain, resulting in the A-SRS not being sent.

[0358] 4. If the A-SRS is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the A-SRS conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the A-SRS not to be transmitted. Here, "high priority" refers to the highest priority transmission configured when both high and low priority transmissions are available at the base station. In this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0359] 5. In response to a temporal conflict in the slot between the A-SRS (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes are dynamically changed. For example, the attribute of a symbol is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0360] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0361] Rule 6 (ALT6)

[0362] In the first implementation of ALT6, if the first mode is determined to be an A-SRS with a valid slot count, and the valid symbol type of the A-SRS transmission is determined to be SBFD symbol, then the slot that satisfies the following conditions is determined to be the valid slot of the A-SRS, and the A-SRS is transmitted in the determined valid slot.

[0363] Condition: In a slot, if all SRS resources in the SRS-ResourceSet corresponding to the A-SRS are SBFD symbols in the time domain, and the UE capability satisfies the minimum timing requirement between the PDCCH that triggers the A-SRS and all the SRS resources, then the slot is determined to be a valid slot. The symbol positions of all SRS resources within the slot are configured by signaling.

[0364] The base station and UE agree that within the determined valid slot, A-SRS transmission will be performed based on the symbols configured for that A-SRS. From the first symbol of the PDCCH containing the DCI that triggered the A-SRS to the last symbol of the SRS-ResourceSet (containing all symbols of SRS resources) corresponding to the A-SRS, the UE does not expect the valid slot to become invalid due to the following preset reasons or the receipt of some signaling (e.g., the valid slot no longer meets the above conditions, causing A-SRS to ultimately not be transmitted in the valid slot).

[0365] This signaling includes, but is not limited to: signaling that dynamically changes SBFD symbols to non-SBFD symbols, for example, this signaling is transmitted based on DCI in PDCCH, triggering at least one SBFD symbol used for the A-SRS transmission to be changed to a non-SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within an SBFD symbol, for example, this signaling triggers at least one SBFD symbol used for the A-SRS transmission to transmit an SSB.

[0366] At least one of the preset reasons includes:

[0367] 1. In response to the fact that the A-SRS is dynamically scheduled and that the A-SRS and the dynamic DL transmission in the SBFD symbol in the slot conflict in the time domain (i.e. overlap in the time domain, the same below), the A-SRS is not sent.

[0368] 2. In response to the fact that the A-SRS is semi-statically configured and in the SBFD symbol in the slot, the A-SRS conflicts with the dynamic DL transmission in the time domain, resulting in the A-SRS not being sent.

[0369] 3. In response to the fact that the A-SRS is semi-statically configured and in the SBFD symbol in the slot, the A-SRS conflicts with the semi-static DL transmission in the time domain, resulting in the A-SRS not being sent.

[0370] 4. If the A-SRS is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the A-SRS conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the A-SRS not to be transmitted. Here, "high priority" refers to the highest priority transmission configured when both high and low priority transmissions are available at the base station. In this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0371] 5. The A-SRS (whether semi-statically configured or dynamically scheduled) and SSB conflict in the time domain within the slot and SBFD symbol, causing the A-SRS to not be transmitted. Here, the SSB symbol can also be replaced by the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbol here can include semi-statically configured SSB symbols but excludes on-demand triggered SSB symbols.

[0372] 6. In response to a temporal conflict in the slot between the A-SRS (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes are dynamically changed. For example, the attribute of a symbol is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0373] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0374] In the second implementation of ALT6, if the first mode is determined to be an A-SRS with a valid slot count, and the valid symbol type of the A-SRS transmission is determined to be a non-SBFD symbol, then the slot that satisfies the following conditions is determined to be the valid slot of the A-SRS, and the A-SRS is transmitted in the determined valid slot.

[0375] Condition: In a slot, if all SRS resources in the SRS-ResourceSet corresponding to the A-SRS are non-SBFD symbols in the time domain, and the UE capability satisfies the minimum timing requirement between the PDCCH that triggers the A-SRS and all the SRS resources, then the slot is determined to be a valid slot. The symbol positions of all SRS resources within the slot are configured by signaling. Here, SSB symbols can include semi-statically configured SSB symbols but excludes on-demand triggered SSB symbols.

[0376] The base station and UE agree that within the determined valid slot, the A-SRS transmission will be performed based on the symbols configured for the A-SRS. From the first symbol of the PDCCH where the DCI triggering the A-SRS resides to the last symbol of the SRS-ResourceSet (containing all symbols of SRS resources) corresponding to the A-SRS, the UE does not expect the valid slot to become invalid due to the following pre-existing reasons or the receipt of some signaling (e.g., the valid slot no longer meets the above conditions, causing the A-SRS to ultimately not be transmitted within the valid slot).

[0377] This signaling includes, but is not limited to: signaling that dynamically changes non-SBFD symbols to SBFD symbols. For example, this signaling is transmitted based on DCI in PDCCH, triggering at least one non-SBFD symbol used for the A-SRS transmission to be changed to an SBFD symbol. This signaling also includes, but is not limited to: signaling that triggers an on-demand SSB transmission within a non-SBFD symbol. For example, this signaling triggers at least one non-SBFD symbol used for the A-SRS transmission to transmit an SSB.

[0378] The preset reasons include at least one of the following:

[0379] 1. In response to the fact that the A-SRS is dynamically scheduled and that the A-SRS and the dynamic DL transmission in the SBFD symbol in the slot conflict in the time domain (i.e. overlap in the time domain, the same below), the A-SRS is not sent.

[0380] 2. In response to the fact that the A-SRS is semi-statically configured and in the SBFD symbol in the slot, the A-SRS conflicts with the dynamic DL transmission in the time domain, resulting in the A-SRS not being sent.

[0381] 3. In response to the fact that the A-SRS is semi-statically configured and in the SBFD symbol in the slot, the A-SRS conflicts with the semi-static DL transmission in the time domain, resulting in the A-SRS not being sent.

[0382] 4. If the A-SRS is semi-statically configured or dynamically scheduled, and within the SBFD symbol of that slot, the A-SRS conflicts with a high-priority UL or DL ​​transmission in the time domain, causing the A-SRS not to be transmitted. Here, "high priority" refers to the highest priority transmission configured when both high and low priority transmissions are available at the base station. In this case, the high-priority transmission can cancel the low-priority transmission in the event of a conflict.

[0383] 5. The A-SRS (whether semi-statically configured or dynamically scheduled) and SSB conflict in the time domain within the slot and SBFD symbol, causing the A-SRS to not be transmitted. Here, the SSB symbol can also be replaced by the CORESET#0 symbol, a semi-statically configured sensing channel / signal symbol, a semi-statically configured symbol for adjusting AGC, or a downlink common channel / signal symbol. The SSB symbol here can include semi-statically configured SSB symbols but excludes on-demand triggered SSB symbols.

[0384] 6. In response to a temporal conflict in the slot between the A-SRS (whether semi-statically configured or dynamically scheduled) and a symbol whose attributes are dynamically changed. For example, the attribute of a symbol is changed from an SBFD symbol to a non-SBFD symbol, or vice versa.

[0385] Semi-static DL transmission includes at least one of the following: UE-level semi-static DL transmission (including UE-dedicated search space of PDCCH, SSB triggered on demand), and cell-level semi-static DL transmission (including common search space of PDCCH, SSB triggered on demand).

[0386] In the scenario of configuring SBFD, the above examples implement the determination of valid time-domain resources corresponding to uplink transmissions and the determination of processing related to uplink transmissions. The examples provide valid slot determination rules for PUCCH repetitions, PUSCH repetition type A (including TBoMS), and Aperiodic SRS, respectively, and specify the corresponding specific conditions that cause a slot to still be counted as a valid slot even if the aforementioned transmission is not performed in one of the determined valid slots. These specific conditions include conflict resolution introduced in Release 19 (R19), as well as channel or signaling conflicts that may be introduced in R20 or 6G, such as sensing channels / signals, dynamic SBFD signaling, etc.

[0387] This application also provides a power determination method. In existing protocols, PUSCH (repetition type B) repetition type B includes nominal repetitions and actual repetitions. Based on predefined conditions, a nominal repetition can be divided into multiple actual repetitions. The actual repetitions are ultimately transmitted. Regarding power determination, for PUSCH / PUCCH / PRACH / SRS, it is based on the transmission timing.

[0388] In existing technology, a PUSCH transmission occasion *i* is defined as L consecutive symbols starting from the start symbol *S* within a time slot of time slot number *n*, within a frame with frame number *SFN*. Furthermore, the base station and the UE agree on certain rules to determine the transmission power for each PUSCH transmission occasion *i*. For PUSCH repetition type B, a transmission occasion is a nominal repetition of PUSCH repetition type B. Thus, the power determination for PUSCH repetition type B is based on the nominal repetition. That is, based on the nominal repetition, an actual repetition power is determined.

[0389] However, after SBFD subbands are supported, SBFD symbols and non-SBFD symbols are configured with independent power control parameters. That is, if a UE performs a UL transmission in different slots within the same symbol type, the power of that UL transmission in those different slots should be determined using the power parameters associated with the corresponding symbol type (SBFD symbol or non-SBFD symbol).

[0390] If the boundary between SBFD symbols and non-SBFD symbols is used as a trigger condition for dividing a nominal repetition into actual repetitions, that is, if a nominal repetition is divided into actual repetitions by the boundary between SBFD symbols and non-SBFD symbols, then the power of the resulting actual repetitions needs to be determined. Figure 6 is a schematic diagram of nominal repetition provided in an embodiment. As shown in Figure 6, in a slot, a nominal repetition is divided into two actual repetitions (denoted as repetition B and repetition A) by the boundary between SBFD symbols and non-SBFD symbols. The power determination method provided in this embodiment can determine the power of these actual repetitions.

[0391] Figure 7 is a flowchart illustrating a power determination method according to an embodiment. The power determination method provided in this embodiment is applicable to both a first communication node and a second communication node. In this embodiment, the first communication node can be the terminal device shown in Figure 4, and the second communication node can be the access network device shown in Figure 4. As shown in Figure 7, the method includes the following steps.

[0392] Step 701: For an uplink transmission of type PUSCH repetition type B, and a nominal repetition of the uplink transmission includes SBFD symbols and non-SBFD symbols, determine the power corresponding to the actual repetition when it is executed based on the power parameter associated with the symbol type of the nominal repetition or the actual repetition obtained based on the nominal repetition, and based on the time-frequency resources of the nominal repetition or the actual repetition obtained based on the nominal repetition.

[0393] The following sections will introduce the various implementation methods.

[0394] Implementation method 1 (Option 1)

[0395] In the above context, if a PUSCH transfer is a PUSCH repetition type B, then one of its transfer events is defined as an actual repetition of that PUSCH repetition type B transfer, rather than a nominal repetition.

[0396] Furthermore, if a nominal repetition in a slot is divided into multiple actual repetitions by the boundary between SBFD symbols and non-SBFD symbols, the transmission power of each of the multiple actual repetitions is determined separately based on each actual repetition. Specifically, this includes determining the power corresponding to the actual repetition when it is executed using the power parameter associated with the symbol type of the symbol in which each actual repetition is located and the time-frequency resources of the actual repetition.

[0397] Implementation Method 2 (Option 2)

[0398] In the above context, if a PUSCH transmission is a PUSCH repetition type B, then one of its transmission events is still defined as a nominal repetition of that PUSCH repetition type B transmission. If a nominal repetition in a slot is divided into multiple actual repetitions by SBFD symbol and non-SBFD symbol boundaries, then these multiple actual repetitions use the same power, and this same power is determined based on the power parameter associated with the symbol type of the first symbol of the nominal repetition and the time-frequency resources of the nominal repetition. That is, the power corresponding to the execution of the actual repetition is determined based on the power parameter associated with the symbol type of the first symbol of the nominal repetition and the time-frequency resources of the nominal repetition.

[0399] Implementation method 3 (Option 3)

[0400] In the above context, if a PUSCH transmission is a PUSCH repetition type B, then one of its transmission opportunities is still defined as a nominal repetition of that PUSCH repetition type B transmission. If a nominal repetition is divided into multiple actual repetitions by SBFD symbol and non-SBFD symbol boundaries, then these multiple actual repetitions still use the same power, and this same power is determined based on the first actual repetition among the multiple actual repetitions obtained from the nominal repetition. Specifically, this includes determining the power corresponding to the execution of the actual repetition based on the power parameters associated with the symbol type of the symbol in which the first actual repetition is located and the time-frequency resources of the first actual repetition.

[0401] Implementation method 4 (Option 4)

[0402] In the above context, if a PUSCH transmission is a PUSCH repetition type B, then one of its transmission opportunities is defined as a nominal repetition of that PUSCH repetition type B transmission. If a nominal repetition is divided into multiple actual repetitions by the boundary between SBFD symbols and non-SBFD symbols, then these multiple actual repetitions still use the same power, and this same power is determined as the larger of the transmission power obtained based on option 2 and option 3.

[0403] Implementation method 5 (Option 5)

[0404] In the above context, if a PUSCH transmission is a PUSCH repetition type B, and a nominal repetition of this PUSCH repetition type B includes a boundary between SBFD symbols and non-SBFD symbols (and the base station and UE agree that the nominal repetition will not be divided into multiple actual repetitions by this boundary), then the transmission power corresponding to the transmission timing of this nominal repetition is determined based on one of the following methods. In this case, the nominal repetition is determined based on existing conditions (see TS38.214) whether to be divided into multiple actual repetitions for transmission.

[0405] Specifically, one of the following methods is used:

[0406] A1: The power parameters associated with the symbol type of the first symbol of the nominal repetition and the time-frequency resources of the nominal transmission repetition;

[0407] A2: The power parameters of the symbol type of the first actual repetition among the multiple actual repetitions divided using the nominal repetition, and the time-frequency resources of that nominal repetition. Note: The multiple actual repetitions here are still obtained based on the boundary between SBFD symbols and non-SBFD symbols, but these multiple actual repetitions are only used to determine the transmission power mentioned above;

[0408] A3: A transmission power P1 is determined based on the power parameters associated with SBFD symbols and the time-frequency resources of the nominal repetition; a transmission power P2 is determined based on the power parameters associated with non-SBFD symbols and the time-frequency resources of the nominal repetition. The larger of P1 and P2 is used. This implementation method can guarantee transmission performance.

[0409] A4: Always use the power parameters associated with the SBFD symbol and the time-frequency resources of the nominal repetition.

[0410] For the power parameters in the above options, please refer to section 7.1.1 of TS38.213 for calculation of P. PUSCH,b,f,c,k (i,j,q d ,l) or P PUSCH,b,f,c (i,j,q d The required parameters are as follows: P is configured for SBFD symbols and non-SBFD symbols respectively. PUSCH,b,f,c,k (i,j,q d ,l) or P PUSCH,b,f,c (i,j,q d ,l), and respectively configured for calculating P PUSCH,b,f,c,k (i,j,q d ,l) or P PUSCH,b,f,c (i,j,q d (l) Required relevant parameters. For example, if a UL transmission is within an SBFD symbol, the power of that UL transmission is determined based on the P associated with the SBFD symbol. PUSCH,b,f,c,k (i,j,q d ,l) or P PUSCH,b,f,c (i,j,q d ,l), and associated with SBFD symbols to determine PPUSCH,b,f,c,k (i,j,q d ,l) or P PUSCH,b,f,c (i,j,q d The relevant parameters of l).

[0411] Regarding P PUSCH,b,f,c,k (i,j,q d ,l) or P PUSCH,b,f,c (i,j,q d The explanation of ,l) is as follows:

[0412] If the UE uses the parameter set configuration of index j and the PUSCH power control adjustment state of index l to transmit PUSCH on the active UL BWP b of carrier f in serving cell c:

[0413] If the UE is indicated to have a first Transmission Configuration Indicator State (TCI-State) or an Uplink Transmission Configuration Indicator State (TCI-UL-State) and a second TCI-State or TCI-UL-State, and a multipanel scheme is configured, and the UE determines that it will simultaneously apply the first TCI-State or TCI-UL-State and the second TCI-State or TCI-UL-State in PUSCH transmission timing i, then the UE determines the PUSCH transmission power P of the k-th indicated TCI-State or TCI-UL-State. PUSCH,b,f,c,k (i,j,q d Otherwise, the UE determines the PUSCH transmission power P in the PUSCH transmission timing i. PUSCH,b,f,c (i,j,q d ,l). Among them, q d It is the reference signal index used by the UE to calculate downlink path loss estimation.

[0414] This power determination method, for the case where the nominal repetition of PUSCH repetition type B includes SBFD symbols and non-SBFD symbols, provides a method for determining the corresponding transmission power based on various potential transmission modes.

[0415] This application also provides a communication node, including a processor, which is configured to implement, when executing a computer program, the method for determining uplink transmission or the power determination method provided in any embodiment of this application. Specifically, the communication node can be a first communication node or a second communication node. For example, the first communication node can be a terminal device, such as a UE, provided in any embodiment of this application; the second communication node can be an access network device, such as a base station, provided in any embodiment of this application, and this application does not impose specific limitations on this.

[0416] For example, the following embodiments provide structural diagrams of a communication node as a terminal and a base station, respectively.

[0417] Figure 8 is a schematic diagram of the structure of a UE provided in one embodiment. The UE can be implemented in various forms. The UE in this application can include, but is not limited to, mobile terminal devices such as mobile phones, smartphones, laptops, digital broadcast receivers, personal digital assistants (PDAs), portable devices (PADs), portable media players (PMPs), navigation devices, in-vehicle terminal devices, in-vehicle display terminals, in-vehicle electronic rearview mirrors, etc., as well as fixed terminal devices such as digital television (TV), desktop computers, etc.

[0418] As shown in Figure 8, UE 50 may include a wireless communication unit 51, an audio / video (A / V) input unit 52, a user input unit 53, a sensing unit 54, an output unit 55, a memory 56, an interface unit 57, a processor 58, and a power supply unit 59, etc. Figure 8 illustrates a UE including multiple components; however, it should be understood that it is not required to implement all of the components shown. More or fewer components may be implemented alternatively.

[0419] In this embodiment, the wireless communication unit 51 allows the UE 50 to communicate wirelessly with a base station or network. The A / V input unit 52 is configured to receive audio or video signals. The user input unit 53 can generate key input data to control various operations of the UE 50 based on user-input commands. The sensing unit 54 monitors the current state of the UE 50, the position of the UE 50, the presence or absence of user touch input to the UE 50, the orientation of the UE 50, the acceleration or deceleration of the UE 50, and its direction, etc., and generates commands or signals for controlling the operation of the UE 50. The interface unit 57 serves as an interface through which at least one external device can connect to the UE 50. The output unit 55 is configured to provide output signals in a visual, audio, and / or tactile manner. The memory 56 can store software programs, etc., that perform processing and control operations executed by the processor 58, or can temporarily store data that has been output or will be output. The memory 56 can include at least one type of storage medium. Moreover, the UE 50 can cooperate with a network storage device that performs the storage function of the memory 56 via a network connection. Processor 58 typically controls the overall operation of UE 50. Power supply unit 59, under the control of processor 58, receives external or internal power and provides the appropriate power required to operate various components and assemblies.

[0420] The processor 58 executes at least one functional application and data processing by running a program stored in the memory 56, such as implementing the method provided in the embodiments of this application.

[0421] Figure 9 is a schematic diagram of a base station structure according to an embodiment. As shown in Figure 9, the base station includes a processor 60, a memory 61, and a communication interface 62. The number of processors 60 in the base station can be one or more; Figure 9 shows one processor 60 as an example. The processor 60, memory 61, and communication interface 62 in the base station can be connected via a bus or other means; Figure 9 shows a connection via a bus as an example. The bus represents one or more types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local area bus using any of the various bus structures.

[0422] The memory 61, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the methods in the embodiments of this application. The processor 60 executes at least one functional application and data processing of the base station by running the software programs, instructions, and modules stored in the memory 61, thereby implementing the methods described above.

[0423] Memory 61 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created based on the UE's usage. Furthermore, memory 61 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, memory 61 may include memory remotely located relative to processor 60, which can be connected to a base station via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, networks, mobile communication networks, and combinations thereof.

[0424] Communication interface 62 can be configured to receive and send data.

[0425] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the methods provided in any embodiment of this application.

[0426] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. Computer-readable storage media include (a non-exhaustive list): electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), electrically erasable, programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0427] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, the data signals carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0428] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wire, optical fiber, radio frequency (RF), or any suitable combination thereof.

[0429] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination of programming languages, including object-oriented programming languages ​​(such as Java, Smalltalk, C++, Ruby, and Go) and conventional procedural programming languages ​​(such as the "C" language or similar programming languages). The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network (including a Local Area Network (LAN) or a Wide Area Network (WAN)), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0430] Those skilled in the art will understand that the term user terminal encompasses any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0431] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0432] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0433] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored in memory. The memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Multifunction Discs, DVDs, or CDs), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

Claims

1. A method for determining uplink transmission, characterized in that, The method includes: determining the effective time domain resources corresponding to the uplink transmission based on the transmission mode; and determining the processing related to the uplink transmission according to the effective time domain resources and predefined rules.

2. The method according to claim 1, characterized in that, The transmission mode includes a first mode, which is used to indicate uplink transmission in different time slots, wherein the symbols in the different time slots are sub-band full-duplex (SBFD) symbols or non-sub-band full-duplex (non-SBFD) symbols.

3. The method according to claim 1, characterized in that, The transmission mode includes a second mode, which is used to indicate uplink transmission in different time slots, wherein the symbols in the different time slots are SBFD symbols and non-SBFD symbols, and the symbols in the same time slot are either SBFD symbols or non-SBFD symbols.

4. The method according to claim 2, characterized in that, The uplink transmission is a PUCCH transmission with N repetitions of the Physical Uplink Control Channel (PUCCH), and the effective time domain resource is an effective time slot; the determination of the effective time domain resource corresponding to the uplink transmission based on the transmission mode includes: when the effective symbol type of the PUCCH transmission is SBFD symbol, the time slot that satisfies the first condition is determined as one of the N effective time slots in which the N PUCCH repetitions are located, where N is an integer greater than or equal to 1.

5. The method according to claim 4, characterized in that, The first condition includes: a time slot can provide a first SBFD symbol, and M1 consecutive symbols starting from the first SBFD symbol are SBFD symbols, the first SBFD symbol has the same symbol index as the starting symbol configured for the PUCCH resource corresponding to the PUCCH transmission, M1 is the number of symbols configured for the PUCCH resource, and M1 is an integer greater than or equal to 1.

6. The method according to claim 4, characterized in that, The first condition includes: a time slot can provide a first SBFD symbol, M1 consecutive symbols starting from the first SBFD symbol are SBFD symbols, and the M1 SBFD symbols do not contain symbols of downlink common channels or signals.

7. The method according to claim 2, characterized in that, The uplink transmission is a PUCCH transmission with N PUCCH repetitions, the effective time domain resource is an effective time slot, and the effective symbol type of the PUCCH transmission is SBFD symbol; the process of determining the uplink transmission-related processing according to the effective time domain resource and predefined rules includes: the uplink transmission will be transmitted in a time slot, and the time slot is the effective time slot; if the effective time slot becomes an ineffective time slot or the uplink transmission is not executed in the effective time slot due to a preset first reason or transmission of the first signaling, the time slot is still counted in the number of effective time slots.

8. The method according to claim 7, characterized in that, The first signaling includes at least one of the following: signaling to dynamically change an SBFD symbol to a non-SBFD symbol, and signaling to trigger an on-demand synchronization signal block (SSB) within the SBFD symbol; the preset first reason includes at least one of the following: in response to the PUCCH transmission being dynamically scheduled and the PUCCH repetition overlapping with a dynamic downlink DL transmission in the time domain, causing the PUCCH repetition not to be sent; in response to the PUCCH transmission being semi-statically configured and the PUCCH repetition overlapping with a dynamic DL transmission in the time domain, causing the PUCCH repetition not to be sent; in response to the PUCCH transmission being semi-statically configured and the PUCCH repetition overlapping with a semi-static DL transmission in the time domain, causing the PUCCH repetition not to be sent; in response to the PUCCH transmission being semi-statically configured or dynamically scheduled and the PUCCH repetition overlapping with a high-priority uplink UL transmission or DL ​​transmission in the time domain, causing the PUCCH repetition not to be sent; in response to the PUCCH repetition conflicting with a symbol whose attributes are dynamically changed in the time domain.

9. The method according to claim 2, characterized in that, The uplink transmission is a PUCCH transmission with N PUCCH repetitions, and the effective time domain resource is an effective time slot; the determination of the effective time domain resource corresponding to the uplink transmission based on the transmission mode includes: when the effective symbol type of the PUCCH transmission is a non-SBFD symbol, the time slot that satisfies the second condition is determined as one of the N effective time slots where the N PUCCH repetitions are located.

10. The method according to claim 9, characterized in that, The second condition includes: a time slot can provide a first UL symbol or a first F symbol without a configured SBFD subband, and M1 consecutive symbols starting from the first UL symbol or the first F symbol without a configured SBFD subband are UL symbols or flexible F symbols without a configured SBFD subband, and the first UL symbol or the first F symbol without a configured SBFD subband has the same symbol index as the starting symbol of the PUCCH resource configured for the PUCCH transmission.

11. The method according to claim 9, characterized in that, The second condition includes: a time slot can provide a first UL symbol or a first F symbol not configured with an SBFD subband, M1 consecutive symbols starting from the first UL symbol or the first F symbol not configured with an SBFD subband are UL symbols or F symbols not configured with an SBFD subband, and the M1 symbols do not contain symbols of downlink common channels or signals.

12. The method according to claim 2, characterized in that, The uplink transmission is a PUCCH transmission with N PUCCH repetitions, the effective time domain resource is an effective time slot, and the effective symbol type of the PUCCH transmission is a non-SBFD symbol; the process of determining the uplink transmission-related processing according to the effective time domain resource and predefined rules includes: the uplink transmission will be transmitted in a time slot, and the time slot is the effective time slot; if the effective time slot becomes an ineffective time slot or the uplink transmission is not executed in the effective time slot due to a preset first reason or transmission of a second signaling, the time slot is still counted in the number of effective time slots.

13. The method according to claim 12, characterized in that, The second signaling includes at least one of the following: signaling that dynamically changes a non-SBFD symbol to an SBFD symbol, and signaling that triggers an on-demand SSB within the non-SBFD symbol.

14. The method according to claim 3, characterized in that, The uplink transmission is a PUCCH transmission with N PUCCH repetitions, and the effective time domain resource is an effective time slot; the determination of the effective time domain resource corresponding to the uplink transmission based on the transmission mode includes: the time slot that satisfies the first condition or the second condition is determined as one of the N effective time slots in which the N PUCCH repetitions are located; where N is an integer greater than or equal to 1.

15. The method according to claim 3, characterized in that, The uplink transmission is a PUCCH transmission with N PUCCH repetitions, and the effective time domain resource is an effective time slot; the process of determining the uplink transmission-related processing according to the effective time domain resource and predefined rules includes: the uplink transmission will be transmitted in a time slot, and the time slot is the effective time slot; if the effective time slot becomes an invalid time slot or the uplink transmission is not executed in the effective time slot due to a preset second reason, transmission of the first signaling, or transmission of the second signaling, the time slot is still counted in the number of effective time slots.

16. The method according to claim 15, characterized in that, The preset second cause includes: the PUCCH repeat not being sent because it overlaps in the time domain with a common downlink channel or signal; the PUCCH repeat not being sent because the PUCCH transmission is dynamically scheduled and overlaps in the time domain with a dynamic DL transmission; the PUCCH repeat not being sent because the PUCCH transmission is semi-statically configured and overlaps in the time domain with a dynamic DL transmission; the PUCCH repeat not being sent because the PUCCH transmission is semi-statically configured and overlaps in the time domain with a semi-static DL transmission; the PUCCH repeat not being sent because the PUCCH transmission is semi-statically configured or dynamically scheduled and overlaps in the time domain with a high-priority UL transmission or DL ​​transmission; and the PUCCH repeat not being sent because it conflicts in the time domain with a symbol whose attributes are dynamically changed.

17. The method according to claim 2, characterized in that, The uplink transmission is a PUSCH transmission with N repetitions of the Physical Uplink Shared Channel (PUSCH) and carries a transport block that spans K time slots. The effective time domain resource is the effective time slot. The determination of the effective time domain resource corresponding to the uplink transmission based on the transmission mode includes: when the effective symbol type of the PUSCH transmission is SBFD symbol, the time slot that satisfies the third condition is determined as one of the N*K effective time slots of the PUSCH transmission; where N is an integer greater than or equal to 1 and K is an integer greater than or equal to 1.

18. The method according to claim 17, characterized in that, The third condition includes: within a time slot, all symbols containing the PUSCH resources corresponding to the PUSCH transmission are SBFD symbols.

19. The method according to claim 17, characterized in that, The third condition includes: within a time slot, all symbols of the PUSCH resource corresponding to the PUSCH transmission are SBFD symbols, and the SBFD symbols do not contain symbols of downlink common channels or signals.

20. The method according to claim 2, characterized in that, The uplink transmission is a PUSCH transmission with N PUSCH repetitions and carries a transport block that spans K time slots. The effective time domain resource is the effective time slot, and the effective symbol type of the PUSCH transmission is SBFD symbol. The process of determining the uplink transmission-related processing based on the effective time domain resource and predefined rules includes: the uplink transmission will be transmitted in a time slot, and the time slot is the effective time slot. If the effective time slot count is enabled, and the effective time slot becomes an ineffective time slot or the uplink transmission is not executed in the effective time slot due to a preset third reason or transmission of the first signaling, the time slot is still counted in the number of effective time slots.

21. The method according to claim 20, characterized in that, The preset third reason includes at least one of the following: the PUSCH transmission is dynamically scheduled, and the PUSCH repeat overlaps with a dynamic DL transmission in the time domain, causing the PUSCH repeat not to be sent; the PUSCH transmission is semi-statically configured, and the PUSCH repeat overlaps with a dynamic DL transmission in the time domain, causing the PUSCH repeat not to be sent; the PUSCH transmission is semi-statically configured, and the PUSCH repeat overlaps with a semi-static DL transmission in the time domain, causing the PUSCH repeat not to be sent; the PUSCH transmission is semi-statically configured or dynamically scheduled, and the PUSCH repeat overlaps with a high-priority UL transmission or DL ​​transmission in the time domain, causing the PUSCH repeat not to be sent; the PUSCH repeat conflicts with a symbol whose attributes are dynamically changed in the time domain.

22. The method according to claim 2, characterized in that, The uplink transmission is a PUSCH transmission with N repetitions of the Physical Uplink Shared Channel (PUSCH) and carries a transmission block spanning K time slots. The effective time domain resource is the effective time slot. The determination of the effective time domain resource corresponding to the uplink transmission based on the transmission mode includes: when the effective symbol type of the PUSCH transmission is non-SBFD symbol, the time slot that satisfies the fourth condition is determined as one of the N*K effective time slots of the PUSCH transmission.

23. The method according to claim 22, characterized in that, The fourth condition includes: within a time slot, all symbols of the PUSCH resource corresponding to the PUSCH transmission are UL symbols or F symbols that are not configured with SBFD subbands.

24. The method according to claim 22, characterized in that, The fourth condition includes: within a time slot, all symbols containing the PUSCH resources corresponding to the PUSCH transmission are UL symbols or F symbols that are not configured with SBFD subbands and do not contain downlink common channels or signals.

25. The method according to claim 2, characterized in that, The uplink transmission is a PUSCH transmission with N PUSCH repetitions and carries a transport block that spans K time slots. The effective time domain resource is the effective time slot, and the effective symbol type of the PUSCH transmission is non-SBFD symbol. The process of determining the uplink transmission-related processing based on the effective time domain resource and predefined rules includes: the uplink transmission will be transmitted in a time slot, and the time slot is the effective time slot. If the effective time slot count is enabled, and the effective time slot becomes an ineffective time slot or the uplink transmission is not executed in the effective time slot due to a preset third reason or transmission of second signaling, the time slot is still counted in the number of effective time slots.

26. The method according to claim 3, characterized in that, The uplink transmission is a PUSCH transmission with N PUSCH repetitions and carries a transport block that spans K time slots. The effective time domain resource is the effective time slot. The determination of the effective time domain resource corresponding to the uplink transmission based on the transmission mode includes: the time slot that satisfies the third condition or the fourth condition is determined as one of the N*K effective time slots of the PUSCH transmission; where N is an integer greater than or equal to 1 and K is an integer greater than or equal to 1.

27. The method according to claim 3, characterized in that, The uplink transmission is a PUSCH transmission with N PUSCH repetitions and carries a transmission block spanning K time slots. The effective time domain resource is the effective time slot. The process of determining the uplink transmission-related processing based on the effective time domain resource and predefined rules includes: the uplink transmission will be transmitted in a time slot, and the time slot is the effective time slot. If the effective time slot count is enabled, and the effective time slot becomes an ineffective time slot or the uplink transmission is not executed in the effective time slot due to a preset fourth reason, transmission of the first signaling, or transmission of the second signaling, the time slot is still counted in the number of effective time slots.

28. The method according to claim 27, characterized in that, The preset fourth reason includes: the PUSCH repeat not being sent because it overlaps with a downlink common channel or signal in the time domain; the PUSCH repeat not being sent because the PUSCH transmission is dynamically scheduled and overlaps with a dynamic DL transmission in the time domain; the PUSCH repeat not being sent because the PUSCH transmission is semi-statically configured and overlaps with a dynamic DL transmission in the time domain; the PUSCH repeat not being sent because the PUSCH transmission is semi-statically configured and overlaps with a semi-static DL transmission in the time domain; the PUSCH repeat not being sent because the PUSCH transmission is semi-statically configured or dynamically scheduled and overlaps with a high-priority UL transmission or DL ​​transmission in the time domain; and the PUSCH repeat not being sent because it conflicts with a symbol whose attributes are dynamically changed in the time domain.

29. The method according to claim 2, characterized in that, The uplink transmission is an aperiodic sounding reference signal (A-SRS) transmission, and the effective time domain resource is an effective time slot; the determination of the effective time domain resource corresponding to the uplink transmission based on the transmission mode includes: when the effective symbol type of the A-SRS transmission is SBFD symbol, the time slot that satisfies the fifth condition is determined as the effective time slot.

30. The method according to claim 29, characterized in that, The fifth condition includes: in a time slot, all SRS resources in the SRS resource set corresponding to the A-SRS transmission have SBFD symbols in the time domain, and meet the UE capability of the minimum timing requirement of the UE between the physical downlink control channel (PDCCH) that triggers the A-SRS transmission and all the SRS resources.

31. The method according to claim 29, characterized in that, The fifth condition includes: in a time slot, all SRS resources in the SRS resource set corresponding to the A-SRS transmission have SBFD symbols in the time domain and the SBFD symbols do not contain downlink common channel or signal symbols, and meet the UE capability of the minimum timing requirement between the PDCCH that triggers the A-SRS transmission and all the SRS resources.

32. The method according to claim 2, characterized in that, The uplink transmission is A-SRS transmission, the effective time domain resource is an effective time slot, and the effective symbol type of the A-SRS transmission is SBFD symbol; the process of determining the uplink transmission-related processing based on the effective time domain resource and predefined rules includes: during the uplink transmission, it is not expected that the effective time slot will become an ineffective time slot or the uplink transmission will not be executed in the effective time slot due to a preset fifth reason or transmission of the first signaling.

33. The method according to claim 32, characterized in that, The preset fifth reason includes at least one of the following: the A-SRS transmission is not sent because it is dynamically scheduled and overlaps with a dynamic DL transmission in the time domain; the A-SRS transmission is not sent because it is semi-statically configured and overlaps with a dynamic DL transmission in the time domain; the A-SRS transmission is not sent because it is semi-statically configured and overlaps with a semi-static DL transmission in the time domain; the A-SRS transmission is not sent because it is semi-statically configured or dynamically scheduled and overlaps with a high-priority UL transmission or DL ​​transmission in the time domain; the A-SRS transmission is not sent because it overlaps with an SSB in the time domain; or the A-SRS transmission conflicts with a symbol whose attributes are dynamically changed in the time domain.

34. The method according to claim 2, characterized in that, The uplink transmission is A-SRS transmission, and the effective time domain resource is an effective time slot; the determination of the effective time domain resource corresponding to the uplink transmission based on the transmission mode includes: when the effective symbol type of the A-SRS transmission is non-SBFD symbol, the time slot that satisfies the sixth condition is determined as the effective time slot.

35. The method according to claim 34, characterized in that, The sixth condition includes: within a time slot, all SRS resources in the SRS resource set corresponding to the A-SRS transmission have non-SBFD symbols in the time domain, and satisfy the UE capability of the minimum timing requirement between the PDCCH that triggers the A-SRS transmission and all the SRS resources.

36. The method according to claim 34, characterized in that, The sixth condition includes: in a time slot, all SRS resources in the SRS resource set corresponding to the A-SRS transmission have symbols that are non-SBFD symbols in the time domain, and the non-SBFD symbols do not contain symbols of downlink common channels or signals, and satisfy the UE capability of the minimum timing requirement between the PDCCH that triggers the A-SRS transmission and all the SRS resources.

37. The method according to claim 2, characterized in that, The uplink transmission is A-SRS transmission, the effective time domain resource is an effective time slot, and the effective symbol type of the A-SRS transmission is a non-SBFD symbol; the process of determining the uplink transmission-related processing based on the effective time domain resource and predefined rules includes: during the uplink transmission, it is not expected that the effective time slot will become an ineffective time slot or the uplink transmission will not be executed in the effective time slot due to a preset fifth reason or transmission of second signaling.

38. The method according to any one of claims 6, 11, 19, 31 or 36, characterized in that, The symbols of the downlink common channel or signal include at least one of the following: SSB symbol, control resource set CORESET#0 symbol, semi-statically configured sensing channel or signal symbol, and semi-statically configured symbol for adjusting automatic gain control (AGC).

39. A method for determining power, characterized in that, The method includes: for an uplink transmission of type PUSCH repetition type B, wherein a nominal repetition of the uplink transmission includes SBFD symbols and non-SBFD symbols, determining the power corresponding to the actual repetition when it is executed based on the power parameters associated with the symbol type of the nominal repetition or the actual repetition obtained based on the nominal repetition, and based on the time-frequency resources of the nominal repetition or the actual repetition obtained based on the nominal repetition.

40. A communication node, characterized in that, include: processor; The processor is configured to implement, when executing a computer program, the method for determining uplink transmission as described in any one of claims 1 to 38, or the power determination method as described in claim 39.

41. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the method for determining uplink transmission as described in any one of claims 1 to 38, or the power determination method as described in claim 39.

Images