WO2025171664A1

WO2025171664A1 - Determination for uplink repetitions

Info

Publication number: WO2025171664A1
Application number: PCT/CN2024/077453
Authority: WO
Inventors: Nhat-Quang NHAN; Nikita Tafintsev; Youngsoo Yuk; Jing Yuan Sun; Guillermo POCOVI
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy; Nokia Technologies Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy; Nokia Technologies Oy
Priority date: 2024-02-18
Filing date: 2024-02-18
Publication date: 2025-08-21
Anticipated expiration: 2026-08-18

Abstract

Example embodiments of the present disclosure relate to a solution for determining uplink repetitions. In the solution, the first apparatus obtains, from a second apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain; and determines the number of uplink channel repetitions to be used at least based on the indication.

Description

DETERMINATION FOR UPLINK REPETITIONS

FIELDS

Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for determining uplink repetitions.

BACKGROUND

Currently, the new radio (NR) supports two duplexing modes: Frequency Division Duplex (FDD) for paired bands and Time Division Duplex (TDD) for unpaired bands. In TDD, the time domain resource is split between downlink (DL) and uplink (UL) . Allocation of a limited time duration for the uplink in TDD would result in reduced coverage, increased latency, and reduced capacity.

To address the challenges above, a study on the evolution of duplexing operation in NR has been initiated. Subband non-overlapping full duplex (SBFD) has been proposed as a scheme of an enhanced duplex operation. In the SBFD, simultaneous DL transmission and UL reception at a NR NodeB (also referred to as a gNB) on different physical resource blocks (PRBs) within an unpaired wideband NR cell is allowed. This duplexing scheme is also referred to as cross-division duplexing (xDD) or Flexible Duplexing (FDU) .

SUMMARY

In a first aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: obtain, from a second apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain; and determine the number of uplink channel repetitions to be used at least based on the indication.

In a second aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: transmit, to a first apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain.

In a third aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: obtain at least one pre-configured condition for a determination of a number of uplink channel repetitions; and determine the number of uplink channel repetitions to be used at least based on the at least one pre-configured condition.

In a fourth aspect of the present disclosure, there is provided a method. The method comprises: obtaining, from a second apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain; and determining the number of uplink channel repetitions to be used at least based on the indication.

In a fifth aspect of the present disclosure, there is provided a method. The method comprises: transmitting, to a first apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain.

In a sixth aspect of the present disclosure, there is provided a method. The method comprises: obtaining at least one pre-configured condition for a determination of a number of uplink channel repetitions; and determining the number of uplink channel repetitions to be used at least based on the at least one pre-configured condition.

In a seventh aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for obtaining, from a second apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain; and means for determining the number of uplink channel repetitions to be used at least based on the indication.

In an eighth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for transmitting, to a first apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain.

In a ninth aspect of the present disclosure, there is provided a first apparatus. The third apparatus comprises means for obtaining at least one pre-configured condition for a determination of a number of uplink channel repetitions; and means for determining the number of uplink channel repetitions to be used at least based on the at least one pre-configured condition.

In a tenth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourth aspect.

In an eleventh aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fifth aspect.

In a twelfth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the sixth aspect.

It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Some example embodiments will now be described with reference to the accompanying drawings, where:

FIG. 1A illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;

FIG. 1B illustrates a block of example duplexing modes;

FIG. 1C illustrates a block of SBFD resources and non-SBFD resources;

FIG. 1D illustrates associations among information elements related to number of repetitions according to some example embodiments of the present disclosure;

FIG. 2 illustrates an example of physical uplink control channel (PUCCH) repetitions in DDSUU format;

FIG. 3A and FIG. 3B illustrate signaling charts of communication according to some example embodiments of the present disclosure;

FIG. 4 illustrate an example of determinations of available slots for PUCCH repetitions according to some example embodiments of the present disclosure;

FIG. 5A and FIG. 5B illustrate signaling charts of communication according to some example embodiments of the present disclosure;

FIG. 6A illustrates a flowchart of a method implemented at a first apparatus according to some example embodiments of the present disclosure;

FIG. 6B illustrates a flowchart of a method implemented at a second apparatus according to some example embodiments of the present disclosure;

FIG. 7 illustrates a flowchart of a method implemented at a first apparatus according to some example embodiments of the present disclosure;

FIG. 8 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and

FIG. 9 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

References in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

It shall be understood that although the terms “first, ” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.

As used herein, “at least one of the following: <a list of two or more elements>” and “at least one of <a list of two or more elements>” and similar wording, where the list of two or more elements are joined by “and” or “or” , mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step is performed immediately after “A” occurs and one or more intervening steps may be included.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a” , “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” , “comprising” , “has” , “having” , “includes” and/or “including” , when used herein, specify the presence of stated features, elements, and/or components etc., but do not preclude the presence or addition of one or more other features, elements, components and/or combinations thereof.

As used in this application, the term “circuitry” may refer to one or more or all of the following:

(a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry) and

(b) combinations of hardware circuits and software, such as (as applicable) :

(i) a combination of analog and/or digital hardware circuit (s) with software/firmware and

(ii) any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and memory (ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions) and

(c) hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.

This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

As used herein, the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the next-hop IAB node.

The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) . The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (e.g., remote surgery) , an industrial device and applications (e.g., a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node) . In the following description, the terms “terminal device” , “communication device” , “terminal” , “user equipment” and “UE” may be used interchangeably.

As used herein, the term “resource, ” “transmission resource, ” “resource block, ” “physical resource block” (PRB) , “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like.

In the following, a resource in time domain will be used as an example of a resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains. In summary, the resource used herein includes but is not limited to a time resource or a frequency resource, for example, a subband non-overlapping full duplex time resource, a dynamic time division duplexing time resource, a full duplex evolution time resource, a sub-band, a sub-carrier, or a resource element (RE) .

As discussed above, the SBFD technology has been proposed to enhance the duplexing operation. One objective is to specify user equipment (UE) transmission, reception and measurement behavior and procedures in SBFD symbols and/or non-SBFD symbols for SBFD-aware UE:

- Transmission and reception behaviors on SBFD subbands configured in DL and/or flexible symbol indicated by TDD-UL-DL-ConfigCommon;

- UL transmissions within UL subband only;

- DL receptions within DL subband (s) only, except for cross-link interference (CLI) measurement by the UE outside of the DL subbands;

Note: When flexible symbols are used, it is not expected that any legacy Uplink symbol is converted to Downlink/SBFD symbols;

- Enhancement on resource allocation in frequency domain in SBFD symbols, including:

Resource allocation in frequency domain for physical downlink shared channel (PDSCH) /channel status information (CSI) -reference signal (RS) across two DL subbands in SBFD symbols;

Handling of unaligned boundaries between SBFD subband (s) and Resource block group (RBG) , CSI reporting subband, CSI-RS resource, Precoding Resource Block Group (PRG) ;

- Enhancements on physical channels/signals and procedure across SBFD symbols and non-SBFD symbols in different slots, where each transmission/reception within a slot has either all SBFD or all non-SBFD symbols, including:

resource allocation in frequency domain for transmission or reception in SBFD symbols and non-SBFD symbols with different available frequency resource in different slots;

CSI report of which associated CSI-RS instances occur in both SBFD symbols and non-SBFD symbols in different slots;

Configurations for SRS, PUCCH and physical uplink shared channel (PUSCH) on SBFD symbols and non-SBFD symbols, e.g., resources, frequency hopping parameters, UL power control parameters and/or beam/spatial relation;

- Collision handling between DL reception in DL subband (s) and UL transmission in UL subband in a SBFD symbol.

As used herein, term “SBFD-aware UE” refers to a UE which is capable of understanding/applying a SBFD-related configuration.

It is to be understood that the PUCCH is used as an example uplink transmission for describing some specific example embodiments of the present disclosure. However, it does not mean that the example embodiments of the present disclosure may be implemented only for PUCCH. Actually, the example embodiments of the present disclosure may be applicable to both PUCCH and PUSCH. That is, all the embodiments discussed about PUCCH may be applicable to PUSCH unless there is a clear exclusion.

Example Environment

FIG. 1A illustrates an example communication environment 100A in which example embodiments of the present disclosure can be implemented. The communication environment 100A includes a first apparatus 110 and a second apparatus 120. A serving area provided by the second apparatus 120 is called a cell. The second apparatus 120 can provide one or more cells, for example, a cell 102 as illustrated in FIG. 1A.

In some example embodiments, the first apparatus 110 may be comprised in a terminal device and the second apparatus 120 may be comprised in a network device serving the terminal apparatus.

In the following, for the purpose of illustration, some example embodiments are described with the first apparatus 110 operating as a terminal apparatus and the second apparatus 120 operating as a network apparatus. However, in some example embodiments, operations described in connection with a terminal apparatus may be implemented at a network apparatus or other apparatus, and operations described in connection with a network apparatus may be implemented at a terminal apparatus or other apparatus.

In some example embodiments, if the first apparatus 110 is a terminal apparatus and the second apparatus 120 is a network apparatus, a link from the second apparatus 120 to the first apparatus 110 is referred to as a downlink (DL) , while a link from the first apparatus 110 to the second apparatus 120 is referred to as an uplink (UL) . In DL, the second apparatus 120 is a transmitting (TX) apparatus (or a transmitter) and the first apparatus 110 is a receiving (RX) apparatus (or a receiver) . In UL, the first apparatus 110 is a TX apparatus (or a transmitter) and the second apparatus 120 is a RX apparatus (or a receiver) .

Communications in the communication environment 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) , the fifth generation (5G) , the sixth generation (6G) , and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , Frequency Division Duplex (FDD) , Time Division Duplex (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiple (OFDM) , Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and/or any other technologies currently known or to be developed in the future.

Multiple duplexing modes may be supported in communication environment 100A. Reference is now made to FIG. 1B, which illustrates a block 100B of three example duplexing modes, i.e., TDD, FDD and SBFD.

The FDD may be used for paired bands and TDD may be used for unpaired bands. In TDD, the time domain resource is split between downlink and uplink. Allocation of a limited time duration for the uplink in TDD would result in reduced coverage, increased latency, and reduced capacity. The SBFD may be considered as an evolution of duplexing operation in NR. In particular, the SBFD may allow simultaneous DL and UL transmission on different physical resource blocks (PRBs) /sub-bands within an unpaired wideband NR cell, as illustrated in FIG. 1B.

Further, different duplexing modes may be used interactively. For better understanding, reference is now made to FIG. 1C, which illustrates a block 100C of SBFD resources and non-SBFD resources. In the example of FIG. 1C, it may be observed that there are two slot/symbol types exist for both DL and UL transmissions as shown in Figure 2, namely,

SBFD slots/symbols, during which the non-overlapping DL sub-bands and UL sub-band (s) both exist, and

Non-SBFD slots/symbols, during which the entire band is used for DL or UL (i.e., legacy/full DL/UL slots) .

Several SBFD operation modes have been studied including whether time and frequency locations of sub-bands for SBFD operation are known to the SBFD-aware UE or not. It, however, has been agreed that at least the operation mode with time and frequency locations of sub-bands for SBFD operation being known to the SBFD-aware UE is prioritized and considered for normative works in release 19. This means that SBFD slots should be known by the (SBFD-aware) UE in one way or another. According to the release 19 work item description (WID) , the expected UE behavior of SBFD-aware UEs is that the SBFD-aware UEs may only receive DL in DL sub-bands and transmit UL in UL sub-bands, i.e., half-duplex operational mode.

Generally speaking, physical uplink control channel (PUCCH) is used for conveying uplink control information (UCI) . There are different types of UCI, including: Hybrid Automatic Repeat Request (HARQ) feedback (also referred to as HARQ-ACK feedback) , which is used for a UE to feedback to a network (NW) whether the corresponding physical downlink shared channel (PDSCH) has been well received by the UE (i.e., ACK) or not (i.e., NACK) .

Scheduling request (SR) , which is used for a UE to request a NW for scheduling UL resources for an UL transmission on physical uplink shared channel (PUSCH) .

Channel state information (CSI) feedback, which is used for a UE to feedback information about the channel measured through configured CSI reference signals (CSI-RS) .

UE may be configured with 4 PUCCH resource sets with different IDs (pucch-ResourceSetId) . The first set (i.e., pucch-ResourceSetId = 0) may include up to 32 resources, while the other sets can include up to 8 resources. Each PUCCH resource within a set is configured with an ID (PUCCH-ResourceId) , a first part of frequency domain resource allocation (startingPRB, secondHopPRB, intraSlotFrequencyHopping) , and a PUCCH format. All PUCCH resources across the sets have different IDs, i.e., each resource is unique.

Each PUCCH resource may be linked with a PUCCH format. There are 5 PUCCH formats, namely Formats 0, 1, 2, 3 and 4. Each PUCCH format will be separately configured with format-specific details including a second part of frequency domain resource allocation (nrofPRBs) and time domain allocation within a slot (nrofSymbols, startingSymbolIndex) . Formats 0 and 2 are short PUCCH formats, which occupy from 1 to 2 symbols in a slot. Formats 1, 3 and 4 are long PUCCH formats, which occupy from 4 to 14 symbols in a slot. Different PUCCH formats have different ways of conveying different UCI types. This aspect is out of the scope of this invention and will not be described here.

From the above information, UE only knows that there are multiple candidate PUCCH resources per slot. Therefore, UE needs additional information on which slot and which resource per slot to use for transmitting a UCI. This additional information will be informed to UE depending on UCI type as follows.

● For determining the slot:

○ For HARQ-ACK feedback, a ‘PDSCH-to-HARQ_feedback timing indicator’ field will be included in the scheduling downlink control information (DCI) , i.e., the DCI that schedules the PDSCH, or the activating DCI, i.e., the DCI that activates the subsequent semi-persistent transmissions of PDSCH without scheduling DCI. Depending on DCI format, the field may indicate a value in a predefined list or a row in a lookup table configured in dl-DataToUL-ACK. This value gives a delay between the end of the slot containing the PDSCH and the start of the slot where the HARQ-ACK feedback should be sent by the UE.

○ For SR and CSI feedback, UE will be configured in RRC a periodicity and an offset for determining which slot in time domain it will use to report the corresponding UCI type.

● For determining the resource per slot:

○ If the UCI include HARQ-ACK information bits, the UE firstly determines a resource set among the 4 resource sets based on different thresholds specified for the UCI payload (i.e., a range of payload size is associated with a set) . The UE then follows the ‘PUCCH Resource Indicator’ field for determining which resource within the set is used in the slot.

○ For SR and CSI feedback, UE will be configured with a resource ID for determining which resource the UE should use in the slot.

With the above information, the UE can determine a resource for conveying a UCI payload on a PUCCH transmission.

As for PUCCH repetitions, there exists a feature that allows PUCCH to be repeated in time for improving the reliability of PUCCH decoding thanks to time diversity, also referred to as PUCCH repetitions. For PUCCH repetitions, after the first PUCCH transmission (1st repetition) performed on the resource in the slot identified as described above, the PUCCH transmission is repeatedtimes in subsequent available slots, whereis the number of PUCCH repetitions. The repetitions use the same resource ID, and thus the same format. Therefore, before performing PUCCH repetitions, the UE should determine firstly the number of PUCCH repetitionsand secondly thesubsequent available slots for the repetitions. These procedures are described as follows.

For determining the number of PUCCH repetitionscan be configured for each PUCCH resource using pucch-RepetitionNrofSlots-r17 parameter and/or configured for each PUCCH format using nrofSlots parameter. If both parameters are configured, the former will overwrite the latter if the PUCCH resource is indicated by a DCI (meaning that if the PUCCH resource is for HARQ-ACK) . Otherwise, the latter is applied.

The pucch-RepetitionNrofSlots-r17 parameter was introduced in Rel-17 for UL coverage enhancements, for allowing a dynamic indication of number of PUCCH repetitions, given that the DCI also includes a ‘PUCCH resource indicator’ field for selecting a resource out of a resource set. Therefore, configuring number of repetitions per resource also means that the DCI can dynamically select a number of repetitions (by selecting a resource from the resource set) .

It is worth noting that, the nrofSlots parameter is configured in PUCCH-FormatConfig, which is a common configuration for all PUCCH formats (each format also has a format-specific configuration) . In addition, NW can configure whether the parameters configured in PUCCH-FormatConfig (including nrofSlots) are applied for a PUCCH format or not. In other words, NW can configure whether nrofSlots is applied for a PUCCH format or not. However, for the PUCCH formats that apply nrofSlots, the same value of nrofSlots is used across the formats (because it is configured once in the common PUCCH-FormatConfig parameter) .

In order to better understanding the associations among the above information, reference is now made to FIG. 1D, which illustrates associations 100D among information elements related to number of repetitions.

For counting the available slots: in TDD mode, UE determinessubsequent available slots for PUCCH repetitions, starting from the slot determined for the first repetitions. A slot is considered as available if it has an UL symbol at the starting symbol of the PUCCH format (provided by startingSymbolIndex) followed by a number of consecutive UL symbols that is equal to the length of the PUCCH format (provided by nrofsymbols) .

Refer to FIG. 2, which illustrates an example of physical uplink control channel (PUCCH) repetitions in DDSUU format. In the example of FIG. 2, it assumes DDSUU TDD pattern with the special slot S, which has 10, 2, and 2 symbols for downlink, gap, and uplink, respectively (see Figure 4) . Let’s assume two TDD patterns (DDSUU-DDSUU) in 10 slots which are indexed from #1 to #10, startingSymbolIndex = 4, nrofsymbols = 10, and the first repetition is in slot #4. Thesubsequent available slots in this example are slots #5, #9 and #10. Indeed, slots #6 and #7 are full downlink slots, thus the PUCCH resource would fully overlap with DL resource and the slots are not available. Slot #8 is a special slot, which has a part of UL resources. However, the UL resource is not enough for the considered PUCCH resource using the assumed format (the format starts from symbol #4, which is a DL symbol) , resulting in partial overlapping with DL resource and thus not available.

In general, the available time-domain resources for the PUCCH resources that overlap with UL sub-band is higher than for the PUCCH resources that do not overlap with UL sub-band. In other words, there are more repetitions for PUCCH in UL sub-band. Therefore, NW can configure a higher number of repetitions (pucch-RepetitionNrofSlots-r17) for the PUCCH resources that overlap with UL sub-band in frequency domain.

A higher number of repetitions for a same delay (or a shorter delay for a same number of repetitions) can be achieved if NW selects a PUCCH resource in UL sub-band, at least for HARQ-ACK feedback, whose PUCCH resource is indicated by a DCI. This, however, is not applicable for the PUCCH resources for SR or CSI feedback. Indeed, PUCCH resources for SR or CSI feedback are not indicated by a DCI (but RRC configured) . Therefore, as aforementioned, the number of repetitions for these PUCCHs is indicated by nrofSlots parameter, which is commonly configured for all PUCCH formats. However, one PUCCH format can be associated with different PUCCH resources, each of these resources may or may not be in UL sub-band. Therefore, means for configuring higher number of repetitions only for PUCCH in UL sub-band is needed.

In addition, for dynamically indicated PUCCH resource (via DCI, for HARQ-ACK) , whose number of repetitions is configured for each of the PUCCH resources, then if the UL sub-band is reconfigured (i.e., changed by NW) , NW should also reconfigure all of PUCCH resources for changing the number of repetitions per resource. This approach would require a high RRC overhead. Therefore, means for implicitly determining a number of PUCCH repetitions for PUCCH in UL sub-band is needed, which does not require an update (i.e., a reconfiguration) of all PUCCH resources when UL sub-band location is reconfigured.

Work Principle and Example Signaling for Communication

According to some example embodiments of the present disclosure, there is provided a solution relates to a determination for uplink repetitions. Specifically, the UE may determine a higher number of repetitions to be applied for PUCCH/PUSCH resources in UL sub-band.

In a nutshell, in order to determine a proper number of repetitions to be applied for PUCCH/PUSCH resources in UL sub-band, the present disclosure proposes two manners, i.e., an NW-configured manner and a rule-based manner. In the following, these two manners will be discussed separately.

For the purposes of discussion, following embodiments will be discussed with reference to FIG. 1A, for example, by using the first apparatus 110 and the second apparatus 120, where the first apparatus 110 may function as a terminal apparatus and the second apparatus 120 may function as a network apparatus. Further, the first apparatus 110 may be configured with SBFD resources in a time domain and a frequency domain.

It is to be understood that the operations at the first apparatus 110 and the second apparatus 120 should be coordinated. In other words, the second apparatus 120 and the first apparatus 110 should have common understanding about configurations, parameters and so on. Such common understanding may be implemented by any suitable interactions between the second apparatus 120 and the first apparatus 110 or both the second apparatus 120 and the first apparatus 110 applying the same rule/policy.

In the following, although some operations are described from a perspective of the first apparatus 110, it is to be understood that the corresponding operations should be performed by the second apparatus 120. Similarly, although some operations are described from a perspective of the second apparatus 120, it is to be understood that the corresponding operations should be performed by the first apparatus 110. Merely for brevity, some of the same or similar contents are omitted here.

Reference is made to FIG. 3A, which illustrates a signaling flow 300A of communication in accordance with some embodiments of the present disclosure. Example FIG. 3A relates to the NW-configured manner, where the network device may configure at least one new parameter for SBFD-aware UE to determine number of PUCCH repetitions.

In operation, the first apparatus 110 obtains 310-1 an indication for the first apparatus 110 to determine a number of uplink channel repetitions in an SBFD operation. In some embodiments, the second apparatus 120 trasnmits 310-2 the indication to the first apparatus 110. In some embodiments, the uplink channel repetitions may relate to physical uplink control channel (PUCCH) repetitions or physical uplink shared channel (PUSCH) repetitions.

Based on the indication, the first apparatus determines 320 the number of uplink channel repetitions to be used at least.

In some embodiments, the indication may comprise at least one parameter associated with the number of uplink channel repetitions dedicated for the SBFD operation. In some embodiments, the at least one parameter may be configured in PUCCH resource or in PUCCH format of a PUCCH configuration. As one example, the indication may be nrofSlots-SBFD parameter configured in PUCCH-FormatConfig, or pucch-RepetitionNrofSlots-SBFD parameter configured in PUCCH-Resource. Reference is made to FIG. 1D. In FIG. 1D, nrofSlots-SBFD 190 is configured explicitly in PUCCH format. Alternatibely, pucch-RepetitionNrofSlots-SBFD 191 is configured explicitly in PUCCH resource. It should be understood that the names of IE/parameter in FIG. 1D are only for the purpose of illustration without suggesting any limitations. That is, when new IEs are introduced to configure the uplink channel format/resource, the SBFD dedicated parameter discussed herein may be comprised in the new IEs. The present disclosure is not limited with regard to the specific name of IE/parameter.

In some embodiments, the first apparatus 110 may apply the at least one parameter for the number of uplink channel repetitions.

Additionally, the application of the at least one parameter is conditionally. In some embodiments, in a case that an uplink channel resource overlaps with an uplink sub-band in an SBFD slot, the first apparatus 110 may apply the at least one parameter for the number of uplink channel repetitions. Accordingly, in some embodiments, in a case that an uplink channel resource does not overlap with an uplink sub-band in an SBFD slot, the first apparatus 110 may ignore the at least one parameter for the number of uplink channel repetitions.

Alternatively, in some embodiments, in a case that an uplink channel resource is associated with a PUCCH format that is allowed to be repeated or transmitted in an SBFD slot, the first apparatus 110 may apply the at least one parameter for the number of uplink channel repetitions. Accordingly, in a case that an uplink channel resource is associated with a PUCCH format that is not allowed to be repeated or transmitted in an SBFD slot, the first apparatus 110 may ignore the at least one parameter for the number of uplink channel repetitions.

Except for the at least one parameter, the indication may alternatively comprise a value associated with the number of uplink channel repetitions. In this event, the first apparatus may determine the number of uplink channel repetitions by adding the value to a further number of uplink channel repetitions. For example, the indication indicates an offset number X. Then the first apparatus 110 may determine the number of repetitions for the PUCCH to bewhereis the repetition number determined as legacy manner.

Reference is made to FIG. 3B, which illustrates a signaling flow 300B of communication in accordance with some embodiments of the present disclosure. Example FIG. 3B relates to the rule-based manner, where new rule is specified for UE to determine number of repetitions for PUCCH in UL sub-band by leveraging the existing parameters.

As illustrated in FIG. 3B the first apparatus 110 may receive 340 SBFD configuration from the second apparatus 120. Thus, the first apparatus 110 may be configured with SBFD resources in a time domain and a frequency domain.

In operation, the first apparatus 110 obtains 350 at least one pre-configured condition for a determination of a number of uplink channel repetitions, i.e., specify one or more rules.

Then the first apparatus 110 determines 360 the number of uplink channel repetitions to be used at least based on the at least one pre-configured condition.

In some embodiments, in a case that an uplink channel resource is within an uplink sub-band in an SBFD slot and is indicated by an RRC configuration (or not indicated by DCI) , the first apparatus 110 may apply the number of uplink channel repetitions configured per uplink channel resource.

Alternatively, in some embodiments, in a case that an uplink channel resource is within an uplink sub-band in an SBFD slot, the first apparatus 110 may apply a maximum value or a minimum value from a plurality of configured uplink channel repetition numbers as the number of uplink channel repetitions. Additionally, the plurality of configured uplink channel repetition numbers may be at least one of the configured uplink channel repetition numbers per uplink channel resource, or per uplink channel format.

In some embodiments, in a case that an uplink channel resource is within an uplink sub-band in an SBFD slot, the first apparatus 110 may determine a value associated with the number of uplink channel repetitions, and may determine the number of uplink channel repetitions by adding the value to a further number of uplink channel repetitions.

Additionally, in some embodiments, in case that an uplink channel transmission over plurality of slots is to be stopped at an SBFD slot in a TDD pattern, the first apparatus 110 may determine the value based on a number of remaining SBFD slots after the SBFD slot in the TDD pattern.

Alternatively, in some embodiments, in a case that an uplink channel transmission over plurality of slots is to be stopped at a slot in a TDD pattern, the first apparatus 110 may determine the value based on a number of consecutive available slots after the slot in the TDD pattern.

Compared with the NW-configured manner, the rule-based manner may configure whether the new rule is applied or not. That is, the rule-based manner may simply configure or not the parameter for enabling/disabling the feature.

For a better understanding, reference is now made to FIG. 4, which illustrates an example 400 of determination of available slots for PUCCH repetitions according to some example embodiments of the present disclosure.

In the example of FIG. 4, Case 1 corresponds to the case of PUCCH repetitions being outside UL sub-band, and Case 2 corresponds to the case of PUCCH repetitions being inside UL sub-band.

Example of FIG. 4 considers two PUCCH resources with different resource IDs, namely ID#aand ID#b. The former is outside UL sub-band while the latter is inside.

Both resources are linked to a same PUCCH format, which is configured with nrofSlots = 4. Case 1 assumes that resource ID#ais semi-statically configured for SR or CSI feedback, while Case 2 assumes that resource ID#b is used for the same purpose. According to the embodiments discussed above, a higher number of repetitions may be achieved for Case 2 (8 repetitions) compared to Case 1 (4 repetitions) for a same considered time duration.

Embodiments

In order to better understand the above procedure, some example embodiments will be further discussed as below.

Embodiments about the NW-configured manner will be discussed first. In operation, the network device configures at least one new parameter for SBFD-aware UE to determine number of PUCCH repetitions.

In some embodiments, the network device may configure a new (second) parameter for the number of repetitions explicitly in PUCCH format (e.g., nrofSlots-SBFD 190 as illustrated in FIG. 1D) or PUCCH resource (e.g., pucch-RepetitionNrofSlots-SBFD 191 as illustrated in FIG. 1D) , which is dedicated for SBFD operation.

With the new parameter, in some embodiments, the SBFD-aware UE may apply the new parameter for determining the number of repetitions, if it is configured. Otherwise, UE applies the legacy parameter.

Alternatively, in some embodiments, the SBFD-aware UE may apply the new parameter for determining the number of repetitions, if it is configured and if the PUCCH resource overlaps with UL sub-band. Otherwise, UE applies the legacy parameter (i.e., either nrofSlots or pucch-RepetitionNrofSlots, following legacy rules) .

In some embodiments, in a case that the number of repetitions is configured per PUCCH format, the SBFD-aware UE may apply the new parameter for determining the number of repetitions, if it is configured and if the PUCCH resource is associated with a PUCCH format that is allowed to be repeated or transmitted on SBFD slot. Otherwise, UE applies the legacy parameter.

Alternatively, in some embodiments, the network device configures a new value (X) , and UE may apply the new value as an addition to the number of repetitionsdetermined by UE using legacy rules (i.e., configured for the UE in PUCCH format or PUCCH resource) , if the PUCCH resource overlaps with UL sub-band. The final number of repetitions for the PUCCH may be determined to be

Reference is now made to FIG. 5A, which illustrate a signaling chart 500A of communication according to some example embodiments of the present disclosure.

In some embodiments, at Step 1, an access node (gNB) may transmit, and UE may receive SBFD configuration (s) including the location of both SBFD and non-SBFD time slots and frequency sub-bands.

At Step 2, the gNB may configure at least one a new (second) parameter for SBFD-aware device to determine the number of PUCCH repetitions.

In some embodiments, the gNB may configure a new (second) parameter for number of repetitions in PUCCH format (e.g., nrofSlots-SBFD) or PUCCH resource (e.g., pucch-RepetitionNrofSlots-SBFD) , which is dedicated for SBFD operation.

Alternatively, the gNB may configure a new value (X) for the device to determine a number of PUCCH repetitions as an addition to the number of repetitions determined by the device using legacy rules, if the PUCCH resource overlaps with UL sub-band.

At Step 3, the gNB may transmit DCI to the device. At Step 4, UE may determine which resources to use for PUCCH transmissions in the SBFD slots.

Specifically, in some embodiments, at Step 4, UE may apply the new parameter for determining number of repetitions, if it is configured and if the PUCCH resource overlaps with UL sub-band. Otherwise, the device applies the legacy parameter. Alternatively, in some embodiments, UE apply the new parameter for determining number of repetitions, if it is configured. Otherwise, the device applies the legacy parameter. Alternatively, in some embodiments, UE may apply the new parameter for determining number of repetitions, if it is configured and if the PUCCH resource is associated with a PUCCH format that is allowed to be repeated or transmitted on SBFD slot. Otherwise, the device applies the legacy parameter.

Alternatively, in some embodiments, at Step 4, UE may apply the new value as an addition to the number of repetitions determined by using legacy rules.

Step 5, after determining which resources to use for PUCCH transmissions in the SBFD slots, at Step 5, UE may transmit UCI to the gNB.

In the following, embodiments about the rule-based manner will be discussed. Specifically, a new rule may be specified for UE to determine number of repetitions for PUCCH in UL sub-band by leveraging the existing parameters.

In some embodiments, UE may apply the number of repetitions configured per resource (i.e., pucch-RepetitionNrofSlots) only if the resource is within UL sub-band and if the PUCCH resource is not indicated by a DCI (but RRC configuration) . Otherwise, if the resource is not within UL sub-band, the UE applies the number of repetitions configured per format (i.e., nrofSlots) , as per legacy behavior.

Alternatibely, in some embodiments, the UE may apply the number of repetitions which is max (or min) of (nrofSlots and pucch-RepetitionNrofSlots) only if the resource is within UL sub-band.

Alternatibely, in some embodiments, UE may determine a new value (Y) and UE may apply the new value as an addition to the number of repetitionsdetermined by UE using legacy rules (i.e., configured for the UE in PUCCH format or PUCCH resource) , if the PUCCH resource overlaps with UL sub-band. The final number of repetitions for the PUCCH isAs one example, Y is a number of remaining SBFD slots after a SBFD slot in a TDD pattern, if a transmission of the PUCCH over slots would stop at the SBFD slot in the TDD pattern. As another example, Y is a number of remaining consecutive available slots after a slot in a TDD pattern, if a transmission of the PUCCH overslots would stop at the slot in the TDD pattern. In this way, the delay is minimized while also allow extra repetitions in UL sub-band.

Reference is now made to FIG. 5B, which illustrate a signaling chart 500B of communication according to some example embodiments of the present disclosure.

As illustrated in FIG. 5B, at Step 1, an access node (gNB) may transmit, and UE may receive SBFD configurations including the location of both SBFD and non-SBFD time slots and frequency sub-bands. At Step 2, a new rule may be specified for the device to determine number of repetitions for PUCCH in UL sub-band by leveraging the existing parameters.

Then, at Step 3, the gNB may transmit DCI to the device and at Step 4, the UE may apply the rule. In some embodiments, the UE may apply number of repetitions configured per resource only if the resource is within UL sub-band and if the PUCCH resource is not indicated by a DCI (but RRC configuration) . Otherwise, if the resource is not within UL sub-band, the UE may apply the number of repetitions configured per format, as per legacy behavior, Alternatively, in some embodiments, UE may apply a number of repetitions which may be max (or min) of (nrofSlots and pucch-RepetitionNrofSlots) only if the resource is within UL sub-band. Alternatively, in some embodiments, UE may determine a new value (Y) and applies it as an addition to the number of repetitions N determined by using legacy rules.

Additionally, in some embodiments, Y is a number of remaining SBFD slots after a SBFD slot in a TDD pattern, if a transmission of the PUCCH over N slots would stop at the SBFD slot in the TDD pattern. Alternatively, in some embodiments, Y is a number of remaining consecutive available slots after a slot in a TDD pattern, if a transmission of the PUCCH over N slots would stop at the slot in the TDD pattern.

At Step 5, the gNB may apply the rule for determining the number of repetitions transmitted by the device. Finally, after determining which PUCCH resources can be considered as available for PUCCH transmission, at Step 6, UE transmits UCI to the access node.

With the above processes, UE may determine a higher number of repetitions to be applied for PUCCH resources in UL sub-band, especially when the resource ID and the format (and thus the number of repetitions) is semi-statically configured and cannot be dynamically changed by NW.

Example Methods

FIG. 6 shows a flowchart of an example method 600A implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 600A will be described from the perspective of the first apparatus 110 in FIG. 1A.

At block 610, the first apparatus obtains, from a second apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain.

At block 620, the first apparatus determines the number of uplink channel repetitions to be used at least based on the indication.

In some example embodiments, the uplink channel repetitions relate to physical uplink control channel repetitions or physical uplink shared channel repetitions.

In some example embodiments, the indication comprises at least one parameter associated with the number of uplink channel repetitions dedicated for the SBFD operation.

In some example embodiments, the at least one parameter is configured in PUCCH resource or in PUCCH format of a PUCCH configuration.

In some example embodiments, the indication comprises a value associated with the number of uplink channel repetitions.

In some example embodiments, the first apparatus may apply the at least one parameter for the number of uplink channel repetitions.

In some example embodiments, in accordance with a determination that an uplink channel resource overlaps with an uplink sub-band in an SBFD slot, the first apparatus may apply the at least one parameter for the number of uplink channel repetitions; or in accordance with a determination that an uplink channel resource does not overlap with an uplink sub-band in an SBFD slot, the first apparatus may ignore the at least one parameter for the number of uplink channel repetitions.

In some example embodiments, in accordance with a determination that an uplink channel resource is associated with a PUCCH format that is allowed to be repeated or transmitted in an SBFD slot, the first apparatus may apply the at least one parameter for the number of uplink channel repetitions; or in accordance with a determination that an uplink channel resource is associated with a PUCCH format that is not allowed to be repeated or transmitted in an SBFD slot, the first apparatus may ignore the at least one parameter for the number of uplink channel repetitions.

In some example embodiments, the first apparatus may determine the number of uplink channel repetitions by adding the value to a further number of uplink channel repetitions.

FIG. 6B shows a flowchart of an example method 600B implemented at a second device in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 600B will be described from the perspective of the second apparatus 120 in FIG. 1A.

At block 650, the second apparatus transmits, to a first apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain.

FIG. 7 shows a flowchart of an example method 700 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the first apparatus 100 in FIG. 1A.

At block 710, the first apparatus obtains at least one pre-configured condition for a determination of a number of uplink channel repetitions.

At block 720, the first apparatus determines the number of uplink channel repetitions to be used at least based on the at least one pre-configured condition.

In some example embodiments, in accordance with a determination that an uplink channel resource is within an uplink sub-band in an SBFD slot and is indicated by a radio resource control, RRC, configuration, the first apparatus may apply the number of uplink channel repetitions configured per uplink channel resource.

In some example embodiments, in accordance with a determination that an uplink channel resource is within an uplink sub-band in an SBFD slot, the first apparatus may apply a maximum value or a minimum value from a plurality of configured uplink channel repetition numbers as the number of uplink channel repetitions.

In some example embodiments, the plurality of configured uplink channel repetition numbers are configured per at least one of the following: uplink channel resource, or uplink channel format.

In some example embodiments, in accordance with a determination that an uplink channel resource is within an uplink sub-band in an SBFD slot, the first apparatus may determine a value associated with the number of uplink channel repetitions; and determining the number of uplink channel repetitions by adding the value to a further number of uplink channel repetitions.

In some example embodiments, in accordance with a determination that an uplink channel transmission over plurality of slots is to be stopped at an SBFD slot in a Time Division Duplexing, TDD pattern, the first apparatus may determine the value based on a number of remaining SBFD slots after the SBFD slot in the TDD pattern.

In some example embodiments, in accordance with a determination that an uplink channel transmission over plurality of slots is to be stopped at a slot in a Time Division Duplexing, TDD pattern, the first apparatus may determine the value based on a number of consecutive available slots after the slot in the TDD pattern.

Example Apparatus, Device and Medium

In some example embodiments, a first apparatus capable of performing any of the method 600A (for example, the first apparatus 110 in FIG. 1A) may comprise means for performing the respective operations of the method 600A. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The first apparatus may be implemented as or included in the first apparatus 110 in FIG. 1A.

In some example embodiments, the first apparatus comprises means for obtaining, from a second apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain; and means for determining the number of uplink channel repetitions to be used at least based on the indication.

In some example embodiments, the first apparatus further comprises: means for applying the at least one parameter for the number of uplink channel repetitions.

In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that an uplink channel resource overlaps with an uplink sub-band in an SBFD slot, applying the at least one parameter for the number of uplink channel repetitions; or means for in accordance with a determination that an uplink channel resource does not overlap with an uplink sub-band in an SBFD slot, ignoring the at least one parameter for the number of uplink channel repetitions.

In some example embodiments, the first apparatus further comprises: means for in accordance with a determination that an uplink channel resource is associated with a PUCCH format that is allowed to be repeated or transmitted in an SBFD slot, applying the at least one parameter for the number of uplink channel repetitions; or means for in accordance with a determination that an uplink channel resource is associated with a PUCCH format that is not allowed to be repeated or transmitted in an SBFD slot, ignoring the at least one parameter for the number of uplink channel repetitions.

In some example embodiments, the first apparatus further comprises: means for determining the number of uplink channel repetitions by adding the value to a further number of uplink channel repetitions.

In some example embodiments, the first apparatus further comprises means for performing other operations in some example embodiments of the method 600 or the first apparatus 110. In some example embodiments, the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the first apparatus.

In some example embodiments, a second apparatus capable of performing any of the method 600B (for example, the second apparatus 120 in FIG. 1A) may comprise means for performing the respective operations of the method 600B. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The second apparatus may be implemented as or included in the second apparatus 120 in FIG. 1A.

In some example embodiments, the second apparatus comprises means for transmitting, to a first apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain.

In some example embodiments, the second apparatus further comprises means for performing other operations in some example embodiments of the method 600B or the second apparatus 120. In some example embodiments, the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the second apparatus.

In some example embodiments, a third apparatus capable of performing any of the method 700 (for example, the first apparatus 110 in FIG. 1A) may comprise means for performing the respective operations of the method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module. The third apparatus may be implemented as or included in the first apparatus 110 in FIG. 1A.

In some example embodiments, the third apparatus comprises means for obtaining at least one pre-configured condition for a determination of a number of uplink channel repetitions; and means for determining the number of uplink channel repetitions to be used at least based on the at least one pre-configured condition.

In some example embodiments, the third apparatus further comprises: means for in accordance with a determination that an uplink channel resource is within an uplink sub-band in an SBFD slot and is indicated by a radio resource control, RRC, configuration, applying the number of uplink channel repetitions configured per uplink channel resource.

In some example embodiments, the third apparatus further comprises: means for in accordance with a determination that an uplink channel resource is within an uplink sub-band in an SBFD slot, applying a maximum value or a minimum value from a plurality of configured uplink channel repetition numbers as the number of uplink channel repetitions.

In some example embodiments, the third apparatus further comprises: means for in accordance with a determination that an uplink channel resource is within an uplink sub-band in an SBFD slot, determining a value associated with the number of uplink channel repetitions; and means for determining the number of uplink channel repetitions by adding the value to a further number of uplink channel repetitions.

In some example embodiments, the third apparatus further comprises: means for in accordance with a determination that an uplink channel transmission over plurality of slots is to be stopped at an SBFD slot in a Time Division Duplexing, TDD pattern, determining the value based on a number of remaining SBFD slots after the SBFD slot in the TDD pattern.

In some example embodiments, the third apparatus further comprises: means for in accordance with a determination that an uplink channel transmission over plurality of slots is to be stopped at a slot in a Time Division Duplexing, TDD pattern, determining the value based on a number of consecutive available slots after the slot in the TDD pattern.

In some example embodiments, the third apparatus further comprises means for performing other operations in some example embodiments of the method 700 or the first apparatus 110. In some example embodiments, the means comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the performance of the third apparatus.

FIG. 8 is a simplified block diagram of a device 800 that is suitable for implementing example embodiments of the present disclosure. The device 800 may be provided to implement a communication device, for example, the first apparatus 110 or the second apparatus 120 as shown in FIG. 1A. As shown, the device 800 includes one or more processors 810, one or more memories 820 coupled to the processor 810, and one or more communication modules 840 coupled to the processor 810.

The communication module 840 is for bidirectional communications. The communication module 840 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 840 may include at least one antenna.

The processor 810 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

The memory 820 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 824, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , an optical disk, a laser disk, and other magnetic storage and/or optical storage. Examples of the volatile memories include, but are not limited to, a random access memory (RAM) 822 and other volatile memories that will not last in the power-down duration.

A computer program 830 includes computer executable instructions that are executed by the associated processor 810. The instructions of the program 830 may include instructions for performing operations/acts of some example embodiments of the present disclosure. The program 830 may be stored in the memory, e.g., the ROM 824. The processor 810 may perform any suitable actions and processing by loading the program 830 into the RAM 822.

The example embodiments of the present disclosure may be implemented by means of the program 830 so that the device 800 may perform any process of the disclosure as discussed with reference to FIG. 3A to FIG. 7. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

In some example embodiments, the program 830 may be tangibly contained in a computer readable medium which may be included in the device 800 (such as in the memory 820) or other storage devices that are accessible by the device 800. The device 800 may load the program 830 from the computer readable medium to the RAM 822 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .

FIG. 9 shows an example of the computer readable medium 900 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 900 has the program 830 stored thereon.

Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.

Although the present disclosure has been described in languages specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

A first apparatus comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to:

obtain, from a second apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain; and

determine the number of uplink channel repetitions to be used at least based on the indication.
The first apparatus of claim 1, wherein the uplink channel repetitions relate to physical uplink control channel repetitions or physical uplink shared channel repetitions.
The first apparatus of claim 1 or 2, wherein the indication comprises at least one parameter associated with the number of uplink channel repetitions dedicated for the SBFD operation.
The first apparatus of claim 3, wherein the at least one parameter is configured in PUCCH resource or in PUCCH format of a PUCCH configuration.
The first apparatus of claim 1 or 2, wherein the indication comprises a value associated with the number of uplink channel repetitions.
The first apparatus of claim 3 or 4, wherein the first apparatus is caused to:

apply the at least one parameter for the number of uplink channel repetitions.
The apparatus of claim 3 or 4, wherein the first apparatus is caused to:

in accordance with a determination that an uplink channel resource overlaps with an uplink sub-band in an SBFD slot, apply the at least one parameter for the number of uplink channel repetitions; or

in accordance with a determination that an uplink channel resource does not overlap with an uplink sub-band in an SBFD slot, ignore the at least one parameter for the number of uplink channel repetitions.
The first apparatus of claim 3 or 4, wherein the first apparatus is caused to:

in accordance with a determination that an uplink channel resource is associated with a PUCCH format that is allowed to be repeated or transmitted in an SBFD slot, apply the at least one parameter for the number of uplink channel repetitions; or

in accordance with a determination that an uplink channel resource is associated with a PUCCH format that is not allowed to be repeated or transmitted in an SBFD slot, ignore the at least one parameter for the number of uplink channel repetitions.
The first apparatus of claim 5, wherein the first apparatus is caused to:

determine the number of uplink channel repetitions by adding the value to a further number of uplink channel repetitions.
A second apparatus comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to:

transmit, to a first apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain.
The second apparatus of claim 10, wherein the uplink channel repetitions relate to physical uplink control channel repetitions or physical uplink shared channel repetitions.
The second apparatus of claim 10 or 11, wherein the indication comprises at least one parameter associated with the number of uplink channel repetitions dedicated for the SBFD operation.
The second apparatus of claim 12, wherein the at least one parameter is configured in PUCCH resource or in PUCCH format of a PUCCH configuration.
The second apparatus of claim 10 or 11, wherein the indication comprises a value associated with the number of uplink channel repetitions.
A first apparatus comprising:

at least one processor; and

at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to:

obtain at least one pre-configured condition for a determination of a number of uplink channel repetitions; and

determine the number of uplink channel repetitions to be used at least based on the at least one pre-configured condition.
The first apparatus of claim 15, wherein the first apparatus is caused to:

in accordance with a determination that an uplink channel resource is within an uplink sub-band in an SBFD slot and is indicated by a radio resource control, RRC, configuration, apply the number of uplink channel repetitions configured per uplink channel resource.
The first apparatus of claim 15, wherein the first apparatus is caused to:

in accordance with a determination that an uplink channel resource is within an uplink sub-band in an SBFD slot, apply a maximum value or a minimum value from a plurality of configured uplink channel repetition numbers as the number of uplink channel repetitions.
The first apparatus of claim 17, wherein the plurality of configured uplink channel repetition numbers are configured per at least one of the following:

uplink channel resource, or

uplink channel format.
The first apparatus of claim 15, wherein the first apparatus is caused to:

in accordance with a determination that an uplink channel resource is within an uplink sub-band in an SBFD slot,

determine a value associated with the number of uplink channel repetitions; and

determine the number of uplink channel repetitions by adding the value to a further number of uplink channel repetitions.
The first apparatus of claim 19, wherein the first apparatus is caused to:

in accordance with a determination that an uplink channel transmission over plurality of slots is to be stopped at an SBFD slot in a Time Division Duplexing, TDD, pattern, determine the value based on a number of remaining SBFD slots after the SBFD slot in the TDD pattern.
The first apparatus of claim 19, wherein the first apparatus is caused to:

in accordance with a determination that an uplink channel transmission over plurality of slots is to be stopped at a slot in a Time Division Duplexing, TDD, pattern, determine the value based on a number of consecutive available slots after the slot in the TDD pattern.
A method comprising:

obtaining, at a first apparatus and from a second apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain; and

determining the number of uplink channel repetitions to be used at least based on the indication.
A method comprising:

transmitting, at a second apparatus and to a first apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain.
A method comprising:

obtaining, at a first apparatus, at least one pre-configured condition for a determination of a number of uplink channel repetitions; and

determining the number of uplink channel repetitions to be used at least based on the at least one pre-configured condition.
A first apparatus comprising:

means for obtaining, from a second apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain; and

means for determining the number of uplink channel repetitions to be used at least based on the indication.
A second apparatus comprising:

means for transmitting, to a first apparatus, an indication for the first apparatus to determine a number of uplink channel repetitions in a sub-band non-overlapping full-duplex, SBFD, operation, wherein the first apparatus is configured with SBFD resources in a time domain and a frequency domain.
A first apparatus comprising:

means for obtaining at least one pre-configured condition for a determination of a number of uplink channel repetitions; and

means for determining the number of uplink channel repetitions to be used at least based on the at least one pre-configured condition.
A computer readable medium comprising instructions stored thereon for causing an apparatus at least to perform the method of any of claims 22 to 24.