Method and apparatus for uplink transmission in full duplex system

By using PUCCH repetition features and signaling optimization in full-duplex systems, the problem of low uplink transmission efficiency in full-duplex systems is solved, and spectrum efficiency and radio resource management are improved.

CN118901263APending Publication Date: 2024-11-05SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 2 Cited by

Patent Information

Application Number
CN202380027527.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-02-28
Filing Date
2023-03-14
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

Uplink transmission in current full-duplex systems needs to be enhanced.

Method used

By using the PUCCH repetition feature in a full-duplex system, combined with public or UE-specific RRC signaling and DCI-based indications, the behavior of PUCCH transmission in SBFD and non-SBFD slots/symbols is controlled, optimizing uplink transmission.

Benefits of technology

It improves uplink transmission efficiency and coverage in full-duplex systems, reduces data transmission resource segmentation in normal UL time slots, and enhances spectrum efficiency and radio resource management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118901263A_ABST
    Figure CN118901263A_ABST
Patent Text Reader

Abstract

An apparatus and method for uplink transmission in a full duplex system. A method performed by a user equipment (UE) includes receiving first information for a first set of parameters of a physical uplink control channel (PUCCH) associated with a first subset of slots from a set of slots on a cell, and second information for a second set of parameters of the PUCCH associated with a second subset of slots from the set of slots on the cell. The method further includes determining a set of PUCCH parameters from the first set of parameters and the second set of parameters based on whether the slots are from the first subset of slots or from the second subset of slots, and transmitting the PUCCH in the slots on the cell based on the set of PUCCH parameters. The slots from the first subset of slots do not include time domain resources indicated for simultaneous transmission and reception on the cell. The slots from the second subset of slots include time domain resources indicated for simultaneous transmission and reception on the cell.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system (or a mobile communication system). More particularly, the present disclosure relates to uplink transmission in a full-duplex system. Background Art

[0002] 5G mobile communication technology defines a wide frequency band so that high transmission rates and new services are possible, and can be realized not only in "below 6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands called mmWave including 28 GHz and 39 GHz. In addition, 6G mobile communication technology (called a super 5G system) has been considered to be implemented in a terahertz (THz) frequency band (e.g., 95 GHz to 3 THz frequency band) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency one-tenth of that of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine type communication (mMTC), standardization is underway on beamforming and massive MIMO for mitigating radio wave path loss in millimeter waves and increasing millimeter wave transmission distances, parameter sets supporting dynamic operations for efficient utilization of millimeter wave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods (such as LDPC (low-density parity check) codes for large-volume data transmission and polar codes for highly reliable transmission of control information), L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services supported by 5G mobile communication technology, discussions are underway on improvements and performance enhancements of initial 5G mobile communication technology, and there is already physical layer standardization on technologies such as V2X (Vehicle to Everything) for assisting driving determination of autonomous vehicles based on information about the location and status of a vehicle transmitted by the vehicle and for enhancing user convenience, NR-U (New Radio Unlicensed) for system operation designed to comply with various regulatory-related requirements in unlicensed bands, NR UE power saving, non-terrestrial networks (NTN) (which is UE-satellite direct communication for providing coverage in areas where communication with terrestrial networks is unavailable), and positioning.

[0005] In addition, there has been standardization of technologies in air interface architecture / protocols, such as Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner, mobility enhancements including conditional switching and DAPS (Dual Active Protocol Stack) switching, and two-step random access (two-step RACH for NR) for simplifying the random access process. Standardization is also underway on the 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and the system architecture / service for mobile edge computing (MEC) for receiving services based on UE location.

[0006] As 5G mobile communication systems are commercialized, the number of connected devices, which has been growing exponentially, will be connected to the communication network, and it is therefore expected that enhanced functions and performance of the 5G mobile communication systems and integrated operations of the connected devices will be necessary. To this end, new research related to extended reality (XR) is arranged for effectively supporting AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, metaverse service support, and drone communication.

[0007] In addition, such development of 5G mobile communication systems will not only serve as a basis for developing new waveforms for providing terahertz band coverage for 6G mobile communication technology, multi-antenna transmission technologies (such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas), metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum) and RIS (reconfigurable smart surface), and full-duplex technology for improving frequency efficiency and improving system networks for 6G mobile communication technology, AI-based communication technology for achieving system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for achieving services with a complexity level that exceeds the limitations of UE operating capabilities by utilizing ultra-high performance communication and computing resources. Summary of the invention

[0008] Technical issues

[0009] Currently, there is a need to enhance uplink transmission in full-duplex systems.

[0010] Solution to the problem

[0011] The present disclosure relates to an apparatus and method for supporting uplink transmission in a full-duplex system.

[0012] In one embodiment, a method performed by a user equipment (UE) in a full-duplex system is provided. The method includes: receiving first information for a first parameter set of a physical uplink control channel (PUCCH) associated with a first time slot subset from a time slot set on a cell, and second information for a second parameter set of a PUCCH associated with a second time slot subset from a time slot set on the cell. The method further includes determining a PUCCH parameter set from the first parameter set and the second parameter set based on whether the time slot is from the first time slot subset or from the second time slot subset, and sending the PUCCH in the time slot on the cell based on the PUCCH parameter set. The time slot from the first time slot subset does not include time domain resources indicated for simultaneous transmission and reception on the cell. The time slot from the second time slot subset includes time domain resources indicated for simultaneous transmission and reception on the cell.

[0013] In another embodiment, a user equipment (UE) in a full-duplex system is provided. The UE includes a transceiver configured to receive first information of a first parameter set for a PUCCH associated with a first subset of time slots from a set of time slots on a cell, and second information of a second parameter set for a PUCCH associated with a second subset of time slots from a set of time slots on a cell. The UE includes a processor operably coupled to the transceiver, the processor being configured to determine a PUCCH parameter set from a first parameter set and a second parameter set based on whether the time slot is from a first subset of time slots or from a second subset of time slots. The transceiver is also configured to send a PUCCH in a time slot on the cell based on the PUCCH parameter set. The time slot from the first subset of time slots does not include time domain resources indicated for simultaneous transmission and reception on the cell. The time slot from the second subset of time slots includes time domain resources indicated for simultaneous transmission and reception on the cell.

[0014] In another embodiment, a base station (BS) is provided. The BS includes a transceiver configured to send first information for a first parameter set of PUCCH associated with a first subset of time slots from a set of time slots on a cell and second information for a second parameter set of PUCCH associated with a second subset of time slots from a set of time slots on the cell. A processor operably coupled to the transceiver is configured to determine a PUCCH parameter set from a first parameter set and a second parameter set based on whether the time slot is from the first subset of time slots or from the second subset of time slots. The transceiver is also configured to receive a PUCCH in a time slot on the cell based on the PUCCH parameter set. The time slot from the first subset of time slots does not include time domain resources indicated for simultaneous transmission and reception on the cell. The time slot from the second subset of time slots includes time domain resources indicated for simultaneous transmission and reception on the cell.

[0015] In another embodiment, a method performed by a base station (BS) in a full-duplex system is provided. The method includes: sending first information for a first parameter set of a physical uplink control channel (PUCCH) associated with a first subset of time slots from a set of time slots on a cell, and second information for a second parameter set of a PUCCH associated with a second subset of time slots from a set of time slots on the cell. And the method includes determining a PUCCH parameter set from a first parameter set and a second parameter set based on whether the time slot is from the first subset of time slots or from the second subset of time slots. And the method includes receiving a PUCCH in a time slot on the cell based on the PUCCH parameter set, wherein the time slot from the first subset of time slots does not include time domain resources indicated for simultaneous transmission and reception on the cell, and wherein the time slot from the second subset of time slots includes time domain resources indicated for simultaneous transmission and reception on the cell.

[0016] Other technical features may be apparent to those skilled in the art from the following drawings, descriptions and claims.

[0017] Beneficial Effects

[0018] According to various embodiments of the present disclosure, uplink transmission can be effectively enhanced. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:

[0020] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0021] Figure 2 An example gNB according to an embodiment of the present disclosure is shown;

[0022] Figure 3 An example UE according to an embodiment of the present disclosure is shown;

[0023] Figure 4 shows example wireless transmit and receive paths according to an embodiment of the present disclosure;

[0024] Figure 5 shows example wireless transmit and receive paths according to an embodiment of the present disclosure;

[0025] Figure 6 An example UL-DL frame configuration in a TDD communication system according to an embodiment of the present disclosure is shown;

[0026] Figure 7An example UL-DL frame configuration in a full-duplex communication system according to an embodiment of the present disclosure is shown;

[0027] Figure 8 An example PUCCH repetition with a configured allowed time slot set or a not allowed time slot set in a full-duplex communication system according to an embodiment of the present disclosure is shown;

[0028] Fig. 9 A flowchart showing an example method for a UE to determine available time slots for PUCCH repetition using common RRC according to an embodiment of the present disclosure;

[0029] Fig.10 A flowchart illustrating an example method for a UE to determine available time slots for PUCCH repetition using PUCCH configuration according to an embodiment of the present disclosure is shown;

[0030] Fig.11 An example is shown for a UE to determine available time slots for PUCCH repetition using UE-specific RRC according to an embodiment of the present disclosure;

[0031] Fig.12 A flow chart of an example method for a UE to determine available time slots for PUCCH repetition using DCI according to an embodiment of the present disclosure is shown.

[0032] Fig.13 A block diagram showing a user equipment (UE) according to an embodiment of the present disclosure; and

[0033] Fig.14 A block diagram of a base station (BS) according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0034] Before the following detailed description, it may be advantageous to set forth the definitions of certain words and phrases used throughout this patent document. The term "coupling" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not these elements are in physical contact with each other. The terms "send", "receive" and "communication" and their derivatives include direct and indirect communication. The terms "include" and "comprise" and their derivatives mean including but not limited to this. The term "or" is inclusive, meaning and / or. The phrase "associated with..." and its derivatives mean including, included in, interconnected with, included in, connected to or connected with, coupled to or coupled with, communicable with, collaborate with, interweave, juxtapose, close to, bound to or bound with, have, have the nature of, have a relationship with, etc. The term "controller" means any device, system or part thereof that controls at least one operation. Such a controller can be implemented in hardware or a combination of hardware and software and / or firmware. The functions associated with any particular controller can be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one of" means that different combinations of one or more of the listed items can be used, and only one of the items in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0035] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data or a portion thereof that are suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD) or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and rewrite data later, such as rewritable optical disks or erasable memory devices.

[0036] Definitions for certain other words and phrases are provided throughout this patent document. Those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0037] Discussed below Figures 1 to 14 The various embodiments used to describe the principles of the present disclosure in this patent document are for illustration only and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0038] The following documents and standard descriptions are hereby incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 38.211 v17.0.0, “NR, Physical Channels and Modulation” (hereinafter “REF 1”); 3GPP TS 38.212 v17.0.0, “NR, Multiplexing and Channel Coding” (hereinafter “REF 2”); 3GPP TS 38.213 v17.0.0, “NR, Physical Layer Procedures for Control” (hereinafter “REF 3”); 3GPP TS 38.214 v17.0.0, “NR, Physical Layer Procedures for Data” (hereinafter “REF 4”), 3GPP TS 38.321 v16.5.0, “NR, Medium Access Control (MAC) Protocol Specification” (hereinafter “REF 5”), 3GPP TS 3GPP TS 38.331v16.5.0, "NR, Radio Resource Control (RRC) Protocol Specification" (hereinafter "REF 6"), and 3GPP TS 38.133v16.8.0, "NR; Requirements for Support of Radio Resource Management" (hereinafter "REF 7").

[0039] Wireless communication is one of the most successful innovations in modern history. The number of users of wireless communication services recently exceeded 5 billion and continues to grow rapidly. Due to the increasing popularity of smartphones and other mobile data devices (such as tablets, "notepad" computers, netbooks, e-book readers and machine-type devices) among consumers and enterprises, the demand for wireless data services has increased rapidly. In order to meet the high growth of mobile data services and support new applications and deployments, improvements in radio interface efficiency and coverage are critical.

[0040] In order to meet the increased demand for wireless data services since the deployment of 4G communication systems and to realize various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. 5G / NR communication systems are considered to be implemented in higher frequency (mmWave) bands (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower frequency bands (e.g., 6 GHz) to achieve robust coverage and mobility support. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G / NR communication systems.

[0041] In addition, in 5G / NR communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RANs) ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), receiving-end interference cancellation, etc.

[0042] The discussion of 5G systems and frequency bands associated therewith is for reference, as certain embodiments of the present disclosure may be implemented in 5G systems. However, the present disclosure is not limited to 5G systems or frequency bands associated therewith, and embodiments of the present disclosure may be used in conjunction with any frequency band. For example, aspects of the present disclosure may also be applied to 5G communication systems, 6G, or even later deployments that may use terahertz (THz) frequency bands.

[0043] The following Figure 1-3 Various embodiments are described that are implemented in a wireless communication system and using Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques. Figure 1-3 The description is not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the present disclosure may be implemented in any suitably arranged communications system.

[0044] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown. Figure 1 The embodiment of the wireless network shown is for illustration only. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.

[0045] like Figure 1 As shown, the wireless network includes gNB 101 (e.g., base station, BS), gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130 (such as the Internet, a proprietary Internet Protocol (IP) network, or other data network).

[0046] gNB 102 provides wireless broadband access to network 130 for a first plurality of user equipment (UE) within coverage area 120 of gNB 102. The first plurality of UEs include: UE 111, which may be located in a small business; UE 112, which may be located in an enterprise; UE 113, which may be a WiFi hotspot; UE 114, which may be located in a first residence; UE 115, which may be located in a second residence; and UE 116, which may be a mobile device such as a cellular phone, a wireless laptop, a wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within coverage area 125 of gNB 103. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G / NR, Long Term Evolution (LTE), Long Term Evolution Advanced (LTE-A), WiMAX, WiFi, or other wireless communication technologies.

[0047] Depending on the network type, the term "base station" or "BS" may refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmission-reception point (TRP), an enhanced base station (eNodeB or eNB), a gNB, a macro cell, a femto cell, a WiFi access point (AP), or other wirelessly enabled devices. A base station may provide wireless access according to one or more wireless communication protocols (e.g., 5G 3GPP New Radio Interface / Access (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.). For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to a network infrastructure component that provides wireless access to a remote terminal. In addition, depending on the network type, the term "user equipment" or "UE" may refer to any component, such as a "mobile station", "subscriber station", "remote terminal", "wireless terminal", "reception point", or "user equipment". For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (such as a desktop computer or vending machine).

[0048] The dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation only. It should be clearly understood that coverage areas associated with a gNB, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0049] As described in more detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof for supporting uplink transmissions in a full-duplex system.In certain embodiments, one or more of BSs 101-103 include circuitry, programming, or a combination thereof for supporting uplink transmissions in a full-duplex system.

[0050] although Figure 1 An example of a wireless network is shown, but Figure 1 Various changes may be made. For example, the wireless network may include any number of gNBs and any number of UEs in any suitable arrangement. In addition, gNB 101 may communicate directly with any number of UEs and provide wireless broadband access to network 130 to these UEs. Similarly, each gNB 102-103 may communicate directly with network 130 and provide direct wireless broadband access to network 130 to the UEs. In addition, gNBs 101, 102, and / or 103 may provide access to other or additional external networks, such as an external telephone network or other type of data network.

[0051] Figure 2 An example gNB 102 is shown according to an embodiment of the present disclosure. Figure 2 The embodiment of the gNB 102 shown in FIG. is for illustration only, and Figure 1 gNBs 101 and 103 may have the same or similar configurations. However, gNBs have a variety of configurations, and Figure 2 The scope of the present disclosure is not limited to any particular implementation of the gNB.

[0052] like Figure 2 As shown, the gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0053] The transceivers 210a-210n receive incoming RF signals from the antennas 205a-205n, such as signals transmitted by UEs in the network 100. The transceivers 210a-210n downconvert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuits in the transceivers 210a-210n and / or the controller / processor 225, which generate processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. The controller / processor 225 may further process the baseband signals.

[0054] Transmit (TX) processing circuitry in the transceivers 210a-210n and / or the controller / processor 225 receives analog or digital data (such as voice data, network data, email, or interactive video game data) from the controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceivers 210a-210n up-convert the baseband or IF signal to an RF signal that is transmitted via the antennas 205a-205n.

[0055] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the reception of UL channel signals and the transmission of DL channel signals by the transceivers 210a-210n according to well-known principles. The controller / processor 225 may also support additional functionality, such as more advanced wireless communication functionality. For example, the controller / processor 225 may support beamforming or directional routing operations, in which output / input signals from / to multiple antennas 205a-205n are weighted differently to effectively direct the output signals in a desired direction. As another example, the controller / processor 225 may support methods for supporting uplink transmissions in a full-duplex system. The controller / processor 225 may support any of a variety of other functions in the gNB 102.

[0056] Controller / processor 225 is also capable of executing programs and other processes, such as an OS, that reside in memory 230. Controller / processor 225 may move data into or out of memory 230 as required by the executing process.

[0057] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or via a network. The interface 235 may support communication over any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (such as a system supporting 5G / NR, LTE, or LTE-A), the interface 235 may allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 235 may allow the gNB 102 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). The interface 235 includes any suitable structure that supports communication over a wired or wireless connection (such as Ethernet or a transceiver).

[0058] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, and another portion of memory 230 may include flash memory or other ROM.

[0059] although Figure 2 An example of a gNB 102 is shown, but the Figure 2 For example, gNB 102 may include Figure 2 Any number of each component shown in Figure 2 The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.

[0060] Figure 3 An example UE 116 is shown in accordance with an embodiment of the present disclosure. Figure 3 The embodiment of UE 116 shown in FIG. 1 is for illustration only, and Figure 1 UEs 111-115 may have the same or similar configurations. However, UEs have a variety of configurations, and Figure 3 The scope of the present disclosure is not limited to any particular implementation of the UE.

[0061] like Figure 3 As shown, UE 116 includes antenna 305, transceiver 310, and microphone 320. UE 116 also includes speaker 330, processor 340, input / output (I / O) interface (IF) 345, input 350, display 355, and memory 360. Memory 360 includes operating system (OS) 361 and one or more applications 362.

[0062] Transceiver 310 receives an incoming RF signal from antenna 305 transmitted by a gNB of network 100. Transceiver 310 downconverts the incoming RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry in transceiver 310 and / or processor 340, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. The RX processing circuitry transmits the processed baseband signal to speaker 330 (such as for voice data) or is processed by processor 340 (such as for web browsing data).

[0063] The TX processing circuit in the transceiver 310 and / or the processor 340 receives analog or digital voice data from the microphone 320, or receives other outgoing baseband data (such as network data, email, or interactive video game data) from the processor 340. The TX processing circuit encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceiver 310 up-converts the baseband or IF signal to an RF signal that is transmitted via the antenna 305.

[0064] The processor 340 may include one or more processors or other processing devices and execute the OS 361 stored in the memory 360 to control the overall operation of the UE 116. For example, the processor 340 may control the transceiver 310 to receive DL channel signals and transmit UL channel signals according to well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0065] The processor 340 is also capable of executing other processes and programs resident in the memory 360, such as processes for supporting uplink transmissions in a full-duplex system. The processor 340 can move data into or out of the memory 360 as needed for the executed process. In some embodiments, the processor 340 is configured to execute applications 362 based on the OS 361 or in response to signals received from the gNB or operator. The processor 340 is also coupled to the I / O interface 345, which provides the UE 116 with the ability to connect to other devices such as laptops and handheld computers. The I / O interface 345 is the communication path between these accessories and the processor 340.

[0066] Processor 340 is also coupled to input 350 including, for example, a touch screen, a keypad, etc., and display 355. An operator of UE 116 may use input 350 to enter data into UE 116. Display 355 may be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and / or at least limited graphics, such as from a website.

[0067] Memory 360 is coupled to processor 340. A portion of memory 360 may include random access memory (RAM), and another portion of memory 360 may include flash memory or other read-only memory (ROM).

[0068] although Figure 3 An example of UE 116 is shown, but the Figure 3 Make various changes. For example, Figure 3 The various components in may be combined, further subdivided, or omitted, and additional components may be added as required. As a specific example, processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, transceiver 310 may include any number of transceivers and signal processing chains, and may be connected to any number of antennas. In addition, although Figure 3 The UE 116 is shown configured as a mobile phone or smart phone, but the UE may be configured to operate as other types of mobile or stationary devices.

[0069] The communication system includes downlink (DL) and uplink (UL), where downlink (DL) refers to transmission from a base station or one or more transmission points to a UE, and uplink (UL) refers to transmission from a UE to a base station or to one or more reception points.

[0070] The time unit for DL ​​signaling or UL signaling on a cell is called a time slot and may include one or more symbols. A symbol may also be used as an additional time unit. A frequency (or bandwidth (BW)) unit is called a resource block (RB). An RB includes multiple subcarriers (SC). For example, a time slot may have a duration of 1 millisecond or 0.5 milliseconds, include 14 symbols, and an RB may include 12 SCs with an inter-SC spacing of 15kHz or 30kHz, and so on.

[0071] DL signals include data signals conveying information content, control signals conveying DL control information (DCI), and reference signals (RS) also known as pilot signals. The gNB sends data information or DCI through the corresponding physical DL shared channel (PDSCH) or physical DL control channel (PDCCH). PDSCH or PDCCH can be sent on a variable number of time slot symbols including one time slot symbol. For simplicity, the DCI format that schedules PDSCH reception of the UE is called the DL DCI format, and the DCI format that schedules PUSCH transmission from the UE is called the UL DCI format.

[0072] The gNB transmits one or more of multiple types of RS including Channel State Information RS (CSI-RS) and Demodulation RS (DMRS). CSI-RS is primarily intended for UEs to perform measurements and provide Channel State Information (CSI) to the gNB. For channel measurements, non-zero power CSI-RS (NZP CSI-RS) resources are used. For interference measurement reporting, CSI Interference Measurement (CSI-IM) resources associated with a Zero Power CSI-RS (ZPCSI-RS) configuration are used. The CSI process consists of NZP CSI-RS and CSI-IM resources.

[0073] The UE can determine the CSI-RS transmission parameters through DL control signaling or higher layer signaling (such as radio resource control (RRC) signaling) from the gNB. The transmission instance of CSI-RS can be indicated by DL control signaling or configured by higher layer signaling. DMRS is only transmitted in the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data or control information.

[0074] Figure 4 and Figure 5 An example wireless transmission and reception path according to the present disclosure is shown. In the following description, Figure 4 The transmission path 400 of can be described as being implemented in a BS (such as BS 102), while Figure 5 The receiving path 500 may be described as being implemented in a UE, such as UE 116. However, it is understood that the receiving path 500 may be implemented in a BS and the transmitting path 400 may be implemented in a UE. In some embodiments, the receiving path 500 is configured to support uplink transmission in a full-duplex system as described in embodiments of the present disclosure.

[0075] like Figure 4 The transmit path 400 shown includes a channel coding and modulation block 405, a serial to parallel (S to P) block 410, an inverse fast Fourier transform (IFFT) block of size N 415, a parallel to serial (P to S) block 420, an add cyclic prefix block 425, and an upconverter (UC) 430. Figure 5 The receive path 500 shown includes a downconverter (DC) 555, a remove cyclic prefix block 560, a serial to parallel (S to P) block 565, a size N fast Fourier transform (FFT) block 570, a parallel to serial (P to S) block 575, and a channel decoding and demodulation block 580.

[0076] like Figure 4As shown, the channel coding and modulation block 405 receives a set of information bits, applies coding (such as low-density parity check (LDPC) coding), and modulates the input bits (such as using orthogonal phase shift keying (QPSK) or orthogonal amplitude modulation (QAM)) to generate a frequency-domain modulation symbol sequence.

[0077] The serial to parallel block 410 converts (such as demultiplexes) the serial modulation symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in the BS 102 and the UE 116. The size N IFFT block 415 performs an IFFT operation on the N parallel symbol streams to generate a time domain output signal. The parallel to serial block 420 converts (such as multiplexes) the parallel time domain output symbols from the size N IFFT block 415 to generate a serial time domain signal. The add cyclic prefix block 425 inserts a cyclic prefix into the time domain signal. The up-converter 430 modulates (such as up-converts) the output of the add cyclic prefix block 425 to an RF frequency for transmission via a wireless channel. The signal may also be filtered at the baseband before conversion to the RF frequency.

[0078] The RF signal transmitted from the BS 102 reaches the UE 116 after passing through the wireless channel, and an operation opposite to that at the BS 102 is performed at the UE 116 .

[0079] like Figure 5 As shown, the down converter 555 down-converts the received signal to the baseband frequency, and the cyclic prefix removal block 560 removes the cyclic prefix to generate a serial time domain baseband signal. The serial to parallel block 565 converts the time domain baseband signal into a parallel time domain signal. The size N FFT block 570 performs an FFT algorithm to generate N parallel frequency domain signals. The parallel to serial block 575 converts the parallel frequency domain signals into a sequence of modulated data symbols. The channel decoding and demodulation block 580 demodulates and decodes the modulation symbols to recover the original input data stream.

[0080] Each of BS101-103 can be implemented as follows Figure 4 The transmission path 400 shown is similar to the transmission to UE 111-116 in the downlink and can be implemented as follows Figure 5 Receive path 500 is shown, which is similar to receiving in the uplink from UE 111-116. Similarly, each of UE 111-116 may implement transmit path 400 for transmitting in the uplink to BS 101-103, and may implement receive path 500 for receiving in the downlink from BS 101-103.

[0081] Figure 4 and Figure 5Each component in may be implemented using hardware or a combination of hardware and software / firmware. As a specific example, Figure 4 and Figure 5 At least some components in can be implemented in software, while other components can be implemented by configurable hardware or a mixture of software and configurable hardware. For example, FFT block 570 and IFFT block 415 can be implemented as configurable software algorithms, in which the value of size N can be modified according to the implementation.

[0082] In addition, although described as using FFT and IFFT, this is illustrative only and should not be construed as limiting the scope of the present disclosure. Other types of transforms may be used, such as discrete Fourier transform (DFT) and inverse discrete Fourier transform (IDFT) functions. It will be appreciated that for DFT and IDFT functions, the value of variable N may be any integer (e.g., 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of variable N may be any integer that is a power of 2 (e.g., 1, 2, 4, 8, 16, etc.).

[0083] although Figure 4 and Figure 5 An example of a wireless transmit and receive path is shown, but the Figure 4 and Figure 5 Make various changes. For example, Figure 4 and Figure 5 The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs. Figure 4 and Figure 5 It is intended to illustrate examples of the types of transmit and receive paths that may be used in a wireless network.Any other suitable architecture may be used to support wireless communications in a wireless network.

[0084] The UL signal also includes a data signal conveying information content, a control signal conveying UL control information (UCI), a DMRS associated with data or UCI demodulation, a sounding RS (SRS) enabling the gNB to perform UL channel measurements, and a random access (RA) preamble enabling the UE to perform random access (see also NR specifications). The UE sends data information or UCI through the corresponding physical UL shared channel (PUSCH) or physical UL control channel (PUCCH). PUSCH or PUCCH can be sent on a variable number of time slot symbols including one time slot symbol. The gNB can configure the UE to send signals on cells within the active UL BWP of the cell UL BW.

[0085] UCI includes Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) information indicating correct or incorrect detection of a data transport block (TB) in the PDSCH, a Scheduling Request (SR) indicating whether the UE has data in the buffer, and a CSI report that enables the gNB to select appropriate parameters for PDSCH or PDCCH transmission to the UE. The HARQ-ACK information can be configured with a smaller granularity than each TB and can be each data code block (CB) or each data CB group, where a data TB includes multiple data CBs.

[0086] The CSI report from the UE may include a channel quality indicator (CQI), which informs the gNB of the maximum modulation and coding scheme (MCS) for the UE to detect a data TB at a predetermined block error rate (BLER), such as 10% BLER (see NR specification), a precoding matrix indicator (PMI), and a rank indicator (RI), which indicates the transmission rank of the PDSCH.

[0087] UL RS includes DMRS and SRS. DMRS is transmitted only in the BW of the corresponding PUSCH or PUCCH transmission. The gNB can use DMRS to demodulate the information in the corresponding PUSCH or PUCCH. SRS is sent by the UE to provide UL CSI to the gNB, and for TDD systems, SRS transmission can also provide PMI for DL ​​transmission. In addition, in order to establish synchronization or initial high-layer connection with the gNB, the UE can send a physical random access channel (such as PRACH as shown in the NR specification).

[0088] Antenna ports are defined so that the channel on which a symbol on the antenna port is sent can be inferred from the channel on which another symbol on the same antenna port is sent.

[0089] For a DM-RS associated with a PDSCH, the channel on which a PDSCH symbol on one antenna port is sent can be inferred from the channel on which a DM-RS symbol on the same antenna port is sent only if the two symbols are within the same resources as the scheduled PDSCH, in the same time slot, and in the same PRG.

[0090] For a DM-RS associated with a PDCCH, the channel on which a PDCCH symbol on one antenna port is sent can be inferred from the channel on which a DM-RS symbol on the same antenna port is sent only if the two symbols are within resources that the UE can assume use the same precoding.

[0091] For DM-RS associated with PBCH, the channel on which a PBCH symbol on one antenna port is sent can be inferred from the channel on which the DM-RS symbol on the same antenna port is sent only if the two symbols are within an SS / PBCH block sent in the same time slot and have the same block index.

[0092] Two antenna ports are considered to be quasi co-located if large-scale properties of the channel over which symbols on one antenna port are transmitted can be inferred from the channel over which symbols on the other antenna port are transmitted. Large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters.

[0093] The UE may assume that SSBs transmitted at the same center frequency position with the same block index are quasi-co-located with respect to Doppler spread, Doppler shift, average gain, average delay, delay spread, and spatial Rx parameters (when applicable). For any other SS / PBCH block transmission, the UE may not assume quasi-co-location.

[0094] In the absence of CSI-RS configuration, and unless otherwise configured, the UE may assume that the PDSCH DM-RS and SSB are quasi-co-located with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx parameters (when applicable). The UE may assume that the PDSCH DM-RS within the same CDM group are quasi-co-located with respect to Doppler shift, Doppler spread, average delay, delay spread, and spatial Rx. The UE may also assume that the DMRS ports associated with the PDSCH are QCL with QCL type A, type D (when applicable), and average gain. The UE may also assume that no DM-RS conflicts with SS / PBCH blocks.

[0095] The UE may be configured with a list of up to M TCI state configurations within the higher layer parameter PDSCH-Config to decode the PDSCH based on a detected PDCCH with DCI for the UE and a given serving cell, where M depends on the UE capability maxNumberConfiguredTCIstatesPerCC. Each TCI state contains parameters for configuring the quasi co-location (QCL) relationship between one or two downlink reference signals and the DMRS ports of the PDSCH, the DMRS ports of the PDCCH, or the CSI-RS ports of the CSI-RS resources.

[0096] The quasi-co-location relationship is configured by the higher layer parameter qcl-Type1 for the first DL RS and qcl-Type2 (if configured) for the second DL RS. For the case of two DL RSs, the QCL type may be different, regardless of whether the reference is to the same DL RS or to different DL RSs. The quasi-co-location type corresponding to each DL RS is given by the higher layer parameter qcl-Type in QCL-Info, and can take one of the following values: QCL-TypeA: {Doppler shift, Doppler spread, average delay, delay spread}; QCL-TypeB: {Doppler shift, Doppler spread; QCL-TypeC: {Doppler shift, average delay}; and QCL-TypeD: {spatial Rx parameters}.

[0097] The UE receives a MAC-CE activation command to map up to [N] (e.g., N=8) TCI states to the code points of the DCI field "Transmission Configuration Indication". When a HARQ-ACK corresponding to the PDSCH carrying the activation command is sent in time slot n, it can be after the MAC-CE application time, e.g., from time slot Starting from the first timeslot thereafter, the indicated mapping between TCI states and code points of the DCI field "Transmission Configuration Indication" applies.

[0098] To improve UL coverage, Rel-15 NR UL supports the PUCCH repetition feature. Long PUCCH formats F1, F3 and F4 can be repeated over multiple time slots. The number of PUCCH repetitions is configured by RRC. In Rel-15 NR, each BWP provides UE-specific PUCCH parameters to the UE using RRC PUCCH-Config. The IE includes the parameter nrofSlots that indicates to the UE the number of time slots that the UE must repeat the PUCCH transmission. RRC signaling can enable or disable the use of PUCCH repetition for the UE. When configured by RRC to use PUCCH repetition, the UE can skip PUCCH transmissions with PUCCH repetition in time slots subject to certain conditions detailed below.

[0099] Rel-16 NR introduces subslot based HARQ-ACK feedback to support more than one PUCCH for HARQ-ACK transmission within a slot, which is mainly beneficial for achieving low latency. The UL slot consists of multiple subslots. No more than one PUCCH carrying HARQ-ACK starts in a subslot. The UE can indicate the supported subslot configuration in the candidate values ​​of {7-symbol*2, 2-symbol*7 and 7-symbol*2} for normal CP or the candidate values ​​of {6-symbol*2, 2-symbol*6 and 6-symbol*2} for extended CP. The UE cannot be configured with Rel-15 PUCCH repetition and Rel-16 NR subslot based HARQ-ACK feedback at the same time. If the RRC PUCCH-config including subslotLengthForPUCCH is provided to the UE, the UE does not expect the PUCCH configuration to include nrofSlots.

[0100] To improve NR UL coverage for FR1 and FR2, and TDD and FDD, Rel-17 NR introduces several enhancements to PUSCH and PUCCH repetition. For PUSCH repetition type A, the maximum number of repetitions is increased to 32, applicable to PUSCH transmissions with and without dynamic grant. In addition, available slot based counting is supported, with the increased maximum number of repetitions being 32 for both available slot based counting and physical slot based counting. TB handling over multiple slots (TBoMS) is supported for PUSCH transmissions with and without dynamic grant. For a single transmission with TB handling over multi-slot PUSCH, the TB size is based on all allocated REs across multiple slots, and the number of slots is counted based on the available slots for UL transmission. In addition, repeated TB handling over multi-slot PUSCH is supported. DMRS bundling is supported for PUSCH repetition type A scheduled by DCI format 0_1 ​​or 0_2, for PUSCH repetition type A with configured grant, for PUSCH repetition type B, and for TB handling on multi-slot PUSCH and for PUCCH repetition. Dynamic PUCCH repetition factor indication per PUCCH resource configuration is introduced, applicable to all PUCCH formats. PUSCH repetition type A for MSG3 transmission for 4-step CBRA is supported on both the normal UL carrier (NUL) and the supplementary UL carrier (SUL). If configured, the UE requests MSG3 repetition via a separate PRACH resource when the RSRP referenced by the DL path loss is below the configured threshold. In addition, repetition of CFRA PUSCH is also supported.

[0101] Referring to the Rel-17 NR enhancements for PUCCH repetition, in addition to dynamically indicating PUCCH repetition during PUCCH repetition via DCI and DM-RS bundling for PUCCH transmission, Rel-17 NR also introduces the possibility of using PUCCH repetition with Rel-16 NR subslot based HARQ-ACK feedback and the possibility of switching between the first and second set of provided spatial settings and / or power control parameters during PUCCH repetition.

[0102] The DCI-based indication of PUCCH repetition in Rel-17 NR reuses the Rel-16 PUCCH Resource Indicator (PRI) field in the DL scheduling DCI format. The PRI value is mapped to a set of PUCCH resource indices provided by the RRC parameter resourceList for PUCCH resources, which are from the set of PUCCH resources provided by the parameter PUCCH-ResourceSet. Note that the principle of selecting the set of PUCCH resources by the UE (e.g., based on the UCI payload size) remains unchanged. Rel-17 NR allows the parameter PUCCH-nrofSlots to be configured per PUCCH resource. PUCCH transmission is repeated when the PRI field value in the DL scheduling DCI results in the selection of a PUCCH resource for which the Rel-17 parameter PUCCH-nrofSlots is configured. If both the Rel-17 parameter PUCCH-nrofSlots and the Rel-15 parameter nrofSlots are provided to the UE for PUCCH resources, the Rel-17 parameter applies.

[0103] DM-RS bundling for PUCCH repetitions (e.g., Rel-17 NR Joint Channel Estimation (JCE)) allows for improved UL coverage of PUCCH through gNB-side multi-slot channel estimation. To be able to support multi-slot channel estimation at the gNB, the UE maintains power consistency and phase continuity within a time domain window (TDW) for its PUCCH transmissions across its PUCCH repetitions. Certain listed types of conditions (e.g., events such as a gap of more than 13 symbols between any two consecutive PUCCH transmissions or intermittent DL reception between any two PUCCH transmissions of a PUCCH repetition) result in the inability to maintain power consistency and phase continuity across PUCCH transmissions. The UE determines a nominal TDW and an actual TDW. The UE is required to maintain power consistency and phase continuity within an actual time domain window for PUCCH transmissions across PUCCH repetitions. If an event occurs that causes power consistency and phase continuity to not be maintained, the actual TDW ends in the last symbol of the PUCCH transmission before the event (e.g., possibly before the end of the determined nominal TDW). If the RRC parameter PUCCH-Window-Restart is enabled, a new actual TDW that provides power consistency and phase continuity for PUCCH transmissions for the remaining number of PUCCH repetitions may start in the first symbol of the PUCCH transmission after the event. Further procedural aspects of DMRS bundling operation during PUCCH repetitions are provided below.

[0104] Referring to the PUCCH repetition process, the UE can be instructed to use PUCCH resources in PUCCH is sent on time slots, where if the PUCCH resource is indicated by the DCI format and includes the parameter PUCCH-nrofSlots, Provided by PUCCH-nrofSlots, otherwise, Provided by the parameter nrofSlots. If the parameter subslotLengthForPUCCH is provided to the UE, it is used A slot with repeated PUCCH transmissions on a slot includes a number of symbols indicated by subslotLengthForPUCCH.

[0105] for UE PUCCH transmission with UCI is repeated on each time slot. The PUCCH transmission in each of the subslots has the same number of consecutive symbols as provided by nrofSymbols. If subslotLengthForPUCCH is not provided, The PUCCH transmission in each of the timeslots has the same first symbol as provided by the parameter startingSymbolIndex; otherwise mod(startingSymbolIndex, subslotLengthForPUCCH). Whether the UE performs frequency hopping for PUCCH transmissions in different timeslots is configured by the parameter interslotFrequencyHopping. If the UE is configured to perform frequency hopping for PUCCH transmissions across different timeslots, the UE performs frequency hopping per timeslot, and the UE sends PUCCH starting from the first PRB provided by the parameter startingPRB in timeslots with even numbers, and starts sending PUCCH starting from the second PRB provided by the parameter secondHopPRB in timeslots with odd numbers. The timeslot indicated to the UE for the first PUCCH transmission has the number 0, and the UE in Each subsequent time slot before the UE transmits PUCCH in a time slot is counted, regardless of whether the UE transmits PUCCH in the time slot. The UE is not expected to be configured to perform frequency hopping for PUCCH transmissions within a time slot. If the UE is not configured to perform frequency hopping for PUCCH transmissions across different time slots, and if the UE is configured to perform frequency hopping for PUCCH transmissions within a time slot, the frequency hopping pattern between the first PRB and the second PRB is the same within each time slot.

[0106] If the UE determines that for PUCCH transmission in a slot, the number of symbols available for PUCCH transmission is less than the value provided by nrofSymbols of the corresponding PUCCH format, the UE does not send PUCCH in the slot.

[0107] The SS / PBCH block symbol is the symbol of the SS / PBCH block with the candidate SS / PBCH block index, where the candidate SS / PBCH block index corresponds to the SS / PBCH block index indicated to the UE through the parameter ssb-PositionsInBurst in SIB1 or the parameter ssb-PositionsInBurst in RRC ServingCellConfigCommon, as described in REF3.

[0108] For unpaired spectrum, the UE determines the time slots, starting from the time slot indicated to the UE for HARQ-ACK reporting, or the time slot determined for SR reporting as described in REF3, or the time slot for CSI reporting as described in REF4, and having a UL symbol or flexible symbol that is not a SS / PBCH block symbol provided as the first symbol by startingSymbolIndex, and having consecutive UL symbols or flexible symbols that are not SS / PBCH block symbols equal to or greater than the number of symbols provided by nrofSymbols as described in REF3 starting from the first symbol.

[0109] For paired spectrum or supplementary uplink frequency bands, the UE determines the frequency bands to be used for PUCCH transmission. The time slot is consecutive time slots, which start from the time slot indicated to the UE for HARQ-ACK reporting, or the time slot used for SR reporting determination as described in REF3, or the time slot used for CSI reporting as described in REF4.

[0110] If the UE will be in the first number If the UE transmits PUCCH on the first number of slots and the UE transmits PUSCH with repetition type A on the second number of slots, and the PUCCH transmissions overlap with PUSCH in one or more slots, and the conditions for multiplexing UCI in PUSCH as described in RFE3 are met in the overlapping slots, the UE transmits PUCCH and does not transmit PUSCH in the overlapping slots. The UE shall send a PUCCH on a time slot of and a PUSCH with repetition type B on a second number of time slots, and the PUCCH transmission shall overlap with actual PUSCH repetitions in one or more time slots, and for the overlapped actual PUSCH repetitions the conditions for multiplexing UCI in PUSCH as described in REF3 are satisfied, the UE sends the PUCCH and does not send overlapping actual PUSCH repetitions.

[0111] The UE does not multiplex different UCI types in PUCCH transmissions, where the PUCCH transmission has repetition on time slots. If the UE will send a first PUCCH on more than one time slot and at least a second PUCCH on one or more time slots, and the transmissions of the first PUCCH and the second PUCCH will overlap in a number of time slots, then for each time slot in the number of time slots and with UCI type priority of HARQ-ACK>SR>CSI with higher priority>CSI with lower priority. The UE does not expect the first PUCCH and any second PUCCH to start at the same time slot and include UCI types with the same priority. If the first PUCCH and any second PUCCH include UCI types with the same priority, the UE sends the PUCCH starting at the earlier time slot and does not send the PUCCH starting at the later time slot. If the first PUCCH and any second PUCCH do not include UCI types with the same priority, the UE sends a PUCCH including the UCI type with the higher priority and does not send a PUCCH including the UCI type with the lower priority.

[0112] When the PUCCH resources for the repetition of the PUCCH transmission of the UE include the first spatial setting and the second spatial setting, or the first power control parameter set and the second power control parameter set, as described in REF5 and REF3, the UE uses the first spatial setting and the second spatial setting, or the first power control parameter set and the second power control parameter set for the first repetition and the second repetition of the PUCCH transmission, respectively, when Each PUCCH transmission repetitions, alternating between a first spatial setting and a second spatial setting, or alternating between the first power control parameter set and the second power control parameter set, wherein if the parameter mappingPattern='cyclicMapping', otherwise,

[0113] The UE does not expect the PUCCH detected in response to DCI format to overlap with any other PUCCH that does not meet the corresponding timing conditions described in REF3.

[0114] If the UE will PUCCH is sent in time slots, and due to If the PUCCH in a time slot of a time slot overlaps with another PUCCH transmission in the time slot, and the UE does not send PUCCH in the time slot, the UE counts the time slot as in a time slot.

[0115] For DAPS operation, if the UE will PUCCH is sent in time slots, and due to The PUCCH in a time slot overlaps with the UE transmission on the target MCG in the time slot. The UE does not send the PUCCH in the time slot, so the UE counts the time slot as in a time slot.

[0116] With reference to the joint channel estimation process, for PUCCH transmission with PUCCH repetition, Rel-17 DM-RS bundling for PUCCH can be enabled by the parameter PUCCH-DMRS-Bundling (per UL BWP). Note that PUCCH format 0 / 2 does not support DM-RS bundling for PUCCH. When the RRC-provided parameter PUCCH-DMRS-Bundling is enabled for the UE, the UE determines one or more nominal TDWs as follows. For PUCCH transmission with PUCCH repetition, the duration of each nominal TDW, except for the last nominal TDW in consecutive time slots, is given by the RRC parameter PUCCH-TimeDomainWindowLength (range 2-8) (if configured). Alternatively, when PUCCH-TimeDomainWindowLength is not configured, the duration is calculated as min([maxDMRS-BundlingDuration], M), where M is the duration in consecutive time slots from the first time slot determined for PUCCH transmission with PUCCH repetition to the last time slot determined for PUCCH transmission with PUCCH repetition, as described in REF3.

[0117] For PUCCH transmissions of PUCCH repetitions, the start of the first nominal TDW is the first time slot determined for the first PUCCH transmission. The end of the last nominal TDW is the last time slot determined for the last PUCCH transmission. The start of any other nominal TDW is the first time slot determined for PUCCH transmissions after the last time slot determined for PUCCH transmissions of the previous nominal TDW.

[0118] For PUCCH transmissions with PUCCH repetitions, the nominal TDW consists of one or more actual TDWs. The UE determines the actual TDW as follows. The start of the first actual TDW is the first symbol of the first PUCCH transmission in the time slot determined for the PUCCH transmission within the nominal TDW. If the actual TDW reaches the end of the last PUCCH transmission within the nominal TDW, the end of the actual TDW is the last symbol of the last PUCCH transmission in the time slot determined for the transmission of the PUCCH within the nominal TDW, if an event occurs that results in the inability to maintain power consistency and phase continuity across PUCCH transmissions with PUCCH repetitions within the nominal TDW, the last symbol of the PUCCH transmission before the event, and the PUCCH transmission is in the time slot determined for the transmission of the PUCCH, or when the parameter PUCCH-Window-Restart is enabled, the start of the new actual TDW is the first symbol of the PUCCH transmission after the event that results in the inability to maintain power consistency and phase continuity across PUCCH transmissions with PUCCH repetitions within the nominal TDW, and the PUCCH transmission is in the time slot determined for the transmission of the PUCCH.

[0119] Events that make it impossible to maintain power consistency and phase continuity for PUCCH transmissions across PUCCH repetitions within the nominal TDW are:

[0120] - DL timeslot or DL ​​reception or DL ​​monitoring based on tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated for unpaired spectrum,

[0121] - the gap between any two consecutive PUCCH transmissions exceeds 13 symbols,

[0122] - the gap between any two consecutive PUCCH transmissions does not exceed 13 symbols, but other UL transmissions are scheduled between the two consecutive PUCCH transmissions,

[0123] - For PUCCH transmissions with PUCCH repetition, discard or cancel PUCCH transmission according to REF3,

[0124] - according to REF3, for any two consecutive PUCCH transmissions of PUCCH repetition, and when the PUCCH resources used for the repetition of the PUCCH transmission of the UE include a first spatial relationship and a second spatial relationship, different spatial relationships are used for the two PUCCH transmissions of the PUCCH repetition,

[0125] - UL timing adjustment in response to a timing advance command according to REF3,

[0126] - Frequency Hopping

[0127] In the case where the actual TDW is created in response to frequency hopping or in response to any event not triggered by DCI or MAC-CE, the UE's PUCCH transmissions across PUCCH repetitions maintain power consistency and phase continuity within the actual TDW. In the case where the actual TDW is created in response to an event triggered by DCI or by MAC-CE other than frequency hopping, the UE's PUCCH transmissions across PUCCH repetitions maintain power consistency and phase continuity within the actual TDW, which is subject to the UE capabilities.

[0128] Note that PUCCH repetitions with different sets of power control parameters in multi-TRP operation are considered semi-static events, which results in the inability to maintain power consistency and phase continuity across PUCCH repetitions.

[0129] When PUCCH repetition is configured with DM-RS bundling, a higher layer parameter PUCCH-FrequencyHopping-Interval may be provided to the UE. For inter-slot hopping and DMRS bundling with PUCCH repetition in Rel-17 NR, the UE performs determination of the hopping interval, followed by determination of the configured TDW, and then determination of the actual TDW, in the order shown. DM-RS bundling is restarted by the UE at the start of each hop, and DM-RS bundling is per actual TDW. Relative slot index may be used to determine inter-slot hopping for PUCCH repetition with DMRS bundling. The RRC configuration provided to the UE for hopping interval determination and configured TDW determination are separate. If no hopping interval is configured, the default hopping interval is the same as the configured TDW length. Note that the UE determines the Rel-17 hopping interval for PUCCH repetition with DM-RS bundling only when the hopping interval is configured.

[0130] Figure 6 An example UL-DL frame configuration in a TDD communication system 600 according to an embodiment of the present disclosure is shown. Figure 6 The illustrated embodiment of the UL-DL frame configuration in the TDD communication system 600 is for illustration only. Figure 6 The scope of the present disclosure is not limited to any particular implementation of the UL-DL frame configuration in the TDD communication system 600 .

[0131] 5G NR radio supports both time division duplex (TDD) operation and frequency division duplex (FDD) operation. The use of FDD or TDD depends on the NR band and the allocation in each country. TDD is required in most frequency bands above 2.5GHz. Figure 6 An example structure of a time slot or a single-carrier TDD UL-DL frame configuration for a TDD communication system according to an embodiment of the present disclosure is shown.

[0132] A DDDSU UL-DL configuration is shown, where D denotes DL timeslot, U denotes UL timeslot, and S denotes a special or switching timeslot having a DL portion, a flexible portion G which may also be used as a guard period for DL ​​to UL switching, and optionally a UL portion.

[0133] TDD has several advantages over FDD. For example, using the same frequency band for DL ​​and UL transmissions results in a simpler UE implementation with TDD because no duplexer is required. Another advantage is that time resources can be flexibly allocated to UL and DL given the asymmetric ratio of traffic in both directions. DL is typically allocated most of the time resources in TDD to handle DL-heavy mobile traffic. Another advantage is that channel state information (CSI) can be more easily acquired via channel reciprocity. This reduces the overhead associated with CSI reporting, especially when there are many antennas or antenna elements.

[0134] Although TDD has advantages over FDD, it also has disadvantages. The first disadvantage is that TDD has a smaller coverage area due to the fact that usually a small part of the time resources can be used for UL transmission, while with FDD, all time resources can be used for UL transmission. Another disadvantage is the waiting time. In TDD, the timing gap between the DL reception and the UL transmission containing the hybrid automatic repeat request acknowledgment (HARQ-ACK) information associated with the DL reception is usually larger than the timing gap in FDD, such as several milliseconds. Therefore, the HARQ round-trip time in TDD is usually longer than that of FDD, especially when the DL traffic load is high. This leads to increased UL user plane delay in TDD, and when the PUCCH providing the HARQ-ACK information needs to be repeatedly transmitted to improve coverage, it may cause data throughput loss or even HARQ stalling (the alternative in this case is that the network abandons the HARQ-ACK information for at least some transmission blocks in the DL).

[0135] To address some of the shortcomings of TDD operation, dynamic adaptation of the link direction has been considered, where in addition to some symbols in some time slots supporting predetermined transmissions such as SSB, the symbols of the time slots can have a flexible transmission direction, such as DL or UL, which the UE can determine based on the scheduling information for transmission or reception. The PDCCH can also be used to provide a DCI format, such as DCI format 2_0 as described in REF2 and REF3, which can indicate the link direction of some flexible symbols in one or more time slots. However, in actual deployments, it is difficult for the gNB scheduler to adapt the transmission direction of the symbols without coordinating with other gNB schedulers in the network. This is due to cross-link interference (CLI), where, for example, DL reception by a UE in a cell may experience large interference from UL transmissions from other UEs in the same or adjacent cells.

[0136] Full-duplex (FD) communication offers the potential to increase spectral efficiency, improve capacity and reduce latency in wireless networks. When FD communication is used, UL and DL signals are received and transmitted simultaneously on fully or partially overlapping or adjacent frequency resources, thereby improving spectral efficiency and reducing latency in the user and / or control planes.

[0137] There are several options for operating a full-duplex wireless communication system. For example, a single carrier can be used so that transmission and reception are scheduled on the same time domain resource (such as a symbol or time slot). Transmission and reception on the same symbol or time slot can be separated in frequency, for example by being placed in non-overlapping subbands. The UL frequency subband in the time domain resource that also includes the DL frequency subband can be allocated at the center of the carrier, or at the edge of the carrier, or at a selected frequency domain position of the carrier. The allocation of DL subbands and UL subbands can overlap partially or completely. The gNB can use the same physical antenna, antenna port, antenna panel, and transmitter-receiver unit (TRX) to transmit and receive simultaneously in the time domain resources. Transmission and reception in FD can also occur using separate physical antennas, ports, panels, or TRXs. Antennas, ports, panels, or TRXs can also be partially reused, or when FD communication is enabled, only the corresponding subset can be active for transmission and reception.

[0138] When a UE receives a signal / channel from a gNB on a full-duplex time slot or symbol, reception may be scheduled in a DL subband of the full-duplex time slot or symbol. When full-duplex operation at the gNB uses a DL time slot or symbol to schedule transmissions from a UE using full-duplex transmission and reception at the gNB, one or more (such as two) DL subbands may be present on the full-duplex time slot or symbol. When a UE is scheduled to transmit on a full-duplex time slot or symbol, transmission may be scheduled in a UL subband of the full-duplex time slot or symbol. When full-duplex operation at the gNB uses an UL time slot or symbol for scheduling transmissions to a UE using full-duplex transmission and reception at the gNB, one or more (such as two) UL subbands may be present in the full-duplex time slot or symbol. Full-duplex operation using a UL subband or DL ​​subband may be referred to as sub-band full-duplex (SBFD).

[0139] Hereinafter, for brevity, full-duplex slots / symbols and SBFD slots / symbols may be collectively referred to as SBFD slots / symbols and non-full-duplex slots / symbols, and normal DL or UL slots / symbols may be referred to as non-SBFD slots / symbols.

[0140] Instead of using a single carrier, different component carriers (CCs) may be used for reception and transmission by the UE. For example, reception by the UE may occur on a first CC and transmission by the UE may occur on a second CC having a small (including zero) frequency separation from the first CC.

[0141] Furthermore, the gNB may operate in full-duplex mode even when the UE is still operating in half-duplex mode, such as when the UE can transmit and receive simultaneously, or the UE may also be capable of full-duplex operation.

[0142] Full-duplex transmission / reception is not limited to gNBs, TRPs or UEs, but can also be used for other types of wireless nodes, such as relays or repeater nodes.

[0143] Full-duplex operation needs to overcome several challenges that work in actual deployment. When using overlapping frequency resources, the received signal is affected by co-channel cross-link interference (CLI) and self-interference. CLI and self-interference elimination methods include passive methods that rely on isolation between transmit and receive antennas, active methods that utilize RF or digital signal processing, and hybrid methods that use a combination of active and passive methods. Filtering and interference elimination can be implemented in RF, baseband (BB), or both RF and BB. Although mitigating co-channel CLI may require a large complexity at the receiver, it is feasible within current technical limitations. Another aspect of FD operation is to mitigate adjacent channel CLI, because in several cellular band allocations, different operators have adjacent spectrum.

[0144] Throughout this disclosure, full duplex (FD) is used as a short form for full duplex operation in a wireless system. The terms "cross-division duplex (XDD)" and FD or SBFD may be used interchangeably in this disclosure.

[0145] FD operation in NR can improve spectral efficiency, link robustness, capacity and latency of UL transmissions. In NR TDD systems, UL transmissions are limited by fewer available transmission opportunities than DL receptions. For example, for NR TDD with SCS=30kHz, DDDU (2 ms), DDDSU (2.5 ms) or DDDDDDDSUU (5 ms), the UL-DL configuration allows DL:UL ratios from 3:1 to 4:1. Any UL transmission can only occur in a limited number of UL time slots, such as every 2, 2.5 or 5 ms, respectively.

[0146] Figure 7 An example UL-DL frame configuration in a full-duplex communication system 700 according to an embodiment of the present disclosure is shown. Figure 7 The illustrated embodiment of the UL-DL frame configuration in the full-duplex communication system 700 is for illustration only. Figure 7 The scope of the present disclosure is not limited to any particular implementation of the UL-DL frame configuration in the TDD communication system 700 .

[0147] Figure 7 Two example full-duplex configurations using single carrier and multi-carrier UL-DL frame configurations according to embodiments of the present disclosure are shown.

[0148] For a single-carrier TDD configuration with full-duplex enabled, the time slot indicated as X is a full-duplex or XDD time slot. Both DL and UL transmissions can be scheduled for at least one or more symbols in the FD time slot. The term FD time slot is used to refer to such a time slot, wherein if the radio resources are scheduled or allocated by the base station, the UE can simultaneously receive and transmit in at least one or more symbols of the time slot. A half-duplex UE cannot simultaneously transmit and receive in a FD time slot or on (multiple) symbols of a FD time slot. When a half-duplex UE is configured to transmit in a symbol of a FD time slot, another UE may be configured to receive in a symbol of the FD time slot. A full-duplex UE can simultaneously transmit and receive in a symbol of a FD time slot, possibly in the case of other UEs that schedule or allocate resources for DL ​​or UL in a symbol of a FD time slot. The transmission of a UE in a first FD time slot can use the same or different frequency domain resources as in a second FD time slot, wherein the resources may differ in bandwidth, the position of the first RB or the center carrier.

[0149] For carrier aggregation TDD configurations with FD enabled, the UE receives in a slot on CC#1 and transmits in at least one or more symbols of a slot on CC#2. In addition to the D slots used only for transmission / reception by the gNB / UE, the U slots used only for reception / transmission by the gNB / UE, and the S slots also used to support DL-UL switching, full-duplex slots with both transmission / reception by the gNB or UE occurring on the same time domain resources (such as slots or symbols) are marked by X. For the example of TDD with SCS=30kHz, single carrier, and UL-DL allocation DXXSU (2.5 ms), the second and third slots allow full-duplex or SBFD operation. UL transmissions may also occur in the last slot (U) where the full UL transmission bandwidth is available. The FD or SBFD slot or symbol allocation and / or multiple slots or symbols on a time period may be indicated by the DCI format in the PDCCH reception and may then vary per time period unit, or may be indicated by higher layer signaling (such as via MAC CE or RRC).

[0150] Various embodiments of the present disclosure recognize the issues when considering UL transmissions in a wireless communication system with full duplex capability. Therefore, various embodiments of the present disclosure provide mechanisms for supporting UL transmissions using the PUCCH repetition feature in a wireless communication system supporting full duplex operation.

[0151] Consider the following in TDD cells supporting gNB full-duplex operation: Figure 7 Example of a single carrier full duplex configuration DXXSU shown. Timeslots are numbered from #1 to #5. For legacy Rel-15 UEs, the gNB configures a common UL-DL frame configuration via SIB1 in this serving cell. The gNB does not provide UE-specific, e.g., UE-specific RRC UL-DL frame configuration to the UE. SFI, e.g., DCIF2_0 is not configured. Note that this example corresponds to a typical TDD configuration in Rel-15 NR, where FG 5-1 is mandatory to support the UE, but FG 5-1a (UE-specific RRC UL_DL frame configuration) and FG 3-6 (SFI) are optional UE features. Without loss of generality, this example assumes NR operation in n78 (3.5GHz) and SCS=30kHz. For simplicity, it is assumed that the UE DL and UL BWP are configured on the full NR channel BW (e.g., 100MHz). Any aspects related to guard RBs, transmit power, beamforming, or processing and timing requirements related to PUSCH transmission in a serving cell using full-duplex transmission and reception are ignored.

[0152] The gNB may configure SIB1 TDD-UL-DL-ConfigCommon with {dl-UL-TransmissionPeriodicity,nrofDownlinkSlots,nrofDownlinkSymbols,nrofUplinkSlots,nrofUplinkSymbols} = {P = 2.5ms, 3 DL slots, 12 DL symbols, 0 UL symbols, 1 UL slot} or DDDS(D)U. As a result, legacy NR UEs only consider the last 2 symbols in slot #4 as flexible symbols (F). This effectively prohibits the possibility of scheduling any UL transmission for legacy UEs using SBFD UL subbands in full-duplex slots #2 and #3.

[0153] When a legacy UE is configured with the Rel-15 NR PUCCH repetition feature on K = {2, 4 or 8} slots and L = 14 symbols, for PUCCH transmission in the slot. As determined by the PUCCH transmission process in REF3, no PUCCH transmission occurs in the DL slot. Similarly, no PUCCH transmission occurs on the flexible symbols in slot #4 because L ≥ 2. Therefore, the UE only sends PUCCH with PUCCH repetition in UL slot #5.

[0154] When the gNB configures SIB1TDD-UL-DL-ConfigCommon with {P=2.5ms, 1DL slot, 0DL symbol, 0UL symbol, 1UL slot} or DFFFU, UL transmissions with Rel-15 PUCCH repetition can be scheduled by the gNB using SBFD UL sub-bands in full-duplex slots #2 and #3 (assuming the gNB does not configure SSB in these slots).

[0155] For repeated PUCCH transmissions in SBFD UL subbands using full-duplex slots #2 and #3 and normal UL slot #5, then the same UL BWP configuration and the same PUCCH frequency domain allocation must be used. The same PUCCH frequency hopping behavior must be applied. For example, depending on the slot indicated to the UE for the first PUCCH transmission, the UE then determines the PRB index of the PUCCH transmission in the first hop, which is provided by the startingPRB in the slot with even numbering, but is provided by the secondHopPRB to determine the PRB index of the PUCCH transmission in the slot with odd numbering. If the first PUCCH transmission occurs in full-duplex slot #3, the UE will use the secondHopPRB to send the PUCCH of the PUCCH repetition in UL slot #4. If the first PUCCH transmission occurs in full-duplex slot #2, the UE will use the startingPRB to send the PUCCH of the PUCCH repetition in UL slot #4. For example, the gNB must select the configured startingPRB and secondHopPRB for the UE so that the UE uses both and additional provided parameters (such as PRB offset RB BWP offset ) The PUCCH allocation calculated by REF3 will not be mapped outside the SBFD UL subband in full-duplex time slots #2 and #3.

[0156] When the UE is configured with the Rel-17 NR PUCCH repetition feature, the number of repetitions may be indicated by DCI with the help of an index to the number of repetitions configured by RRC. The possible signaled PRI value indicated by the DCI is mapped to the set of PUCCH resource indices provided by the RRC parameter resourceList for PUCCH resources from the set of PUCCH resources provided by the parameter PUCCH-ResourceSet. The same considerations as described above for the case of Rel-15 NR PUCCH repetition apply.

[0157] One issue concerns PUCCH transmissions of PUCCH repetitions. When PUCCH repetitions are configured in a TDD serving cell with full-duplex support, PUCCH repetitions can only occur using normal UL slots only or both full-duplex slots and normal UL slots together. Except for a few limited cases (such as when 2 consecutive full-duplex slots are provided, K=2), it is not possible to configure PUCCH repetitions using only and exclusively full-duplex slots. Note that even in the case where the UE is provided with a configuration of SBFD UL subbands (e.g., slots / symbols and start / end RBs), the related art allows PUCCH repetitions to be scheduled using only UL or F slots / symbols, so PUCCH repetitions must still occur using normal UL slots alone, or must use both full-duplex slots and normal UL slots together. For PUCCH transmissions corresponding to PUCCH repetitions across full-duplex and normal UL slots, the PUCCH frequency domain allocation and / or frequency hopping behavior must also be the same. The SBFD UL subband is usually located in the center of the operator's channel BW to protect the first neighbor TDD channel from cross link interference (CLI). The PUCCH transmission corresponding to the PUCCH repetition using the SBFD UL subband in a full-duplex time slot must be allocated to the middle of the channel BW. Therefore, the PUCCH transmission including the PUCCH repetition of the full-duplex time slot must then also occur in the middle of the channel BW of the normal UL time slot.

[0158] Therefore, when PUCCH repetition using full-duplex timeslots results in PUCCH transmissions corresponding to PUCCH repetitions in normal UL timeslots, the schedulable UL BW in normal UL timeslots is divided. PUSCH transmissions in normal UL timeslots can no longer be allocated large continuous BW, which significantly reduces the achievable UL cell throughput and UL spectral efficiency. Rel-15 NR UEs are only forced to support UL resource allocation type 1 with (almost) frequency-contiguous PUSCH allocations. Therefore, PUSCH frequency allocations for UEs in good link conditions can only be completely below or above the center BW occupied by PUCCH transmissions using PUCCH repetitions using full-duplex timeslots from UEs in bad link conditions. When the SBFD UL subband includes approximately 20% of the channel BW, UEs with good SINR can then be scheduled with no more than 40% of the UL scheduling BW in a normal UL timeslot. Note that the need to schedule PUCCH repetitions in the middle of the channel BW corresponding to the SBFD UL subband is purely because the use of related techniques cannot avoid PUCCH repetitions that result in the use of full-duplex timeslots and normal UL timeslots together. When the PUCCH repetitions in the serving cell are intentionally configured to use only a small and limited repetition factor of K=2 instead of a maximum K of 8 to avoid the above disadvantages, this greatly reduces the achievable UL radio range of PUCCH transmissions from UEs under poor link conditions. The (theoretical) use of UL resource allocation type 0 using RBG-based allocation for PUSCH transmissions in UL timeslots will result in increased UE complexity. Even worse, the need for control of the resulting spectrum emissions results in an additional UL power back-off of up to several dB applied by the UE for the corresponding PUSCH transmission, which again greatly reduces the achievable UL radio range for a given UL data rate of the UE under good link conditions. This is because these UEs are no longer able to use their maximum UL transmission power. The full and undivided schedulable UL BW in normal UL timeslots for UEs in good link conditions is then available to the gNB only when there is no DL scheduling to UEs in bad link conditions (which would result in Ack / Nack type UCI using PUCCH repetition) or when CSI type UCI is not configured for transmissions from these UEs.

[0159] Various embodiments of the present disclosure provide methods for controlling UE time domain transmission behavior of PUCCH transmission in PUCCH repetition using common or UE-specific RRC signaling and DCI-based indication, methods for indicating and determining separate PUCCH configurations in SBFD or non-SBFD time slots / symbols, methods for counting available time slots and determining candidate time slots for UE to use for PUCCH repetition, and methods for controlling UE time domain transmission behavior of PUCCH repetition using one or more lists or sequences of PUCCH resource allocations in PUCCH repetition.

[0160] Hereinafter, unless explicitly stated otherwise, providing a parameter value by a higher layer includes providing the parameter value through a system information block (SIB) such as SIB1, or through common RRC signaling, or through UE-specific RRC signaling.

[0161] In the following, for the sake of brevity and simplicity of description, the TDD UL-DL frame configuration provided by the higher layer refers to tdd-UL-DL-ConfigurationCommon as an example of RRC common configuration and / or tdd-UL-DL-ConfigurationDedicated as an example of UE-specific configuration. The UE determines the common TDD UL-DL frame configuration of the serving cell by receiving a system information block (SIB) such as SIB1 when accessing the cell from RRC_IDLE, or determines the common TDD UL-DL frame configuration of the serving cell through public RRC signaling when the UE is configured with an Scell ​​or an additional SCG through IE ServingCellConfigCommon under RRC_CONNECTED. When the UE is configured with a serving cell (e.g., added or modified), the UE determines the dedicated TDD UL-DL frame configuration using IEServingCellConfig, where the serving cell can be a SpCell or SCell of an MCG or SCG. The TDD UL-DL frame configuration specifies a time slot or symbol as one of type 'D', 'U' or 'F' using at least one time domain mode with configurable periodicity.

[0162] In the following, for brevity and simplicity of description, SFI refers to the slot format indicator, which is configured using an IE provided by a higher layer such as slotFormatCombination or slotFormatCombinationsPerCell, as an example, and which is indicated to the UE by a group common DCI such as DCI F2_0, where slotFormats is defined in REF3.

[0163] In the following, for brevity and simplicity of description, the term xdd-config is used to describe the UE-determined configuration and parameterization for DL ​​reception and / or UL transmission in a serving cell supporting full-duplex operation. Note that the use of full-duplex operation by the gNB in ​​the serving cell does not have to be identifiable or known to the UE when scheduling DL reception and / or UL transmission in a slot or symbol. For example, the parameters associated with xdd-config may include: a set of time domain resources, such as symbols / slots, where DL reception or UL transmission is allowed, possible or not allowed; a range or set of frequency domain resources (e.g., serving cell, BWP, start and / or end or RB set) where DL reception or UL transmission is allowed, possible or not allowed; one or more guard intervals, such as guard SC or RB, guard symbol, for time domain and / or frequency domain radio resources during DL reception or UL transmission; one or more resource types, such as 'simultaneous Tx-Rx', 'Rx only' or 'Tx only' or 'D', 'U', 'F', 'N / A'; one or more scheduling behaviors, such as 'DG only', 'CG only', 'Any'. Parameters associated with xdd-config may include indications or values ​​for determining the (assumed) Tx power settings for DL ​​reception of the UE, for example, reference power, EPRE or power offset for specifying DL channel / or signal type; UL transmission power and / or spatial settings are determined by the UE. Configurations and / or parameters associated with xdd-config may be provided to the UE using higher layer signaling, DCI-based signaling and / or MAC CE-based signaling. For example, parameters associated with xdd-config may be provided to the UE via public RRC signaling using SIB. In another example, parameters associated with xdd-config may be provided to the UE via dedicated RRC signaling such as ServingCellConfig. For example, the TDRA table of the RRC configuration may be used or PUCCH configuration and / or DCI-based signaling may be used to indicate to the UE which configuration should be applied to provide parameters associated with xdd-config.

[0164] Various embodiments of the present disclosure provide the UE with separate PUCCH configurations associated with SBFD and non-SBFD time slots / symbols, respectively, to indicate UE-specific or cell-specific PUCCH parameters in a BWP or in a carrier of a cell carrier group. Separate PUCCH configurations associated with SBFD and non-SBFD time slots / symbols, respectively, may be provided to the UE to configure or indicate separate PUCCH format configurations or separate PUCCH resources or PUCCH resource sets for SBFD and non-SBFD time slots / symbols, respectively. Separate values ​​of the same parameter in a PUCCH configuration, in a PUCCH resource or resource set, or in a PUCCH format may be provided to the UE as information, wherein a first value indicating the parameter is for use by the UE in a non-SBFD time slot / symbol, and then a second value indicating the parameter is for use by the UE in a SBFD time slot / symbol. For example, the parameter may correspond to a configured or indicated PUCCH resource or PUCCH format, DL data to UL acknowledgement (ACK) timing or delay, number of repetitions, DMRS bundling indication, number of bits configured for PUCCH resource indication (PRI) in DCI, cyclic or sequential mapping pattern for PUCCH repetition associated with a spatial setting or power control set, frequency hopping (FH) enable or disable indication, FH start PRB or second hop or number of hops or hop width, maximum code rate or number of PRBs for a PUCCH format, or indication of simultaneous HARQ acknowledgement and CSI for PUCCH transmission.

[0165] Various embodiments of the present disclosure provide a UE with an RRC configuration using common and / or UE-specific RRC signaling, wherein the UE is configured with a set of allowed time slots or a set of disallowed time slots in which PUCCH repetition may or may not occur. The UE may be scheduled using a dynamic grant or using a configured grant. The UE uses the newly provided RRC configuration to determine the time slots in the PUCCH repetition that are potentially available for PUCCH transmission. The newly provided RRC configuration may enable or disable and / or parameterize the use of full-duplex or normal UL time slots for PUCCH repetition of the UE, respectively.

[0166] Figure 8 An example PUCCH repetition with a configured set of allowed slots or a set of not allowed slots 800 is shown according to an embodiment of the present disclosure. Figure 8 The embodiment of PUCCH repetition with a configured set of allowed time slots or a set of not allowed time slots 800 shown in FIG. 8 is for illustration only. Figure 8 The scope of the present disclosure is not limited to any particular implementation of PUCCH repetition with a configured set of allowed slots or set of disallowed slots 800 .

[0167] The gNB may configure the UE to use only normal UL timeslots (instead of full-duplex timeslots), or only full-duplex timeslots (instead of normal UL timeslots), or both full-duplex and normal UL timeslots for PUCCH repetition. Only a subset of full-duplex timeslots and / or a subset of normal UL timeslots may be configured as potentially available timeslots for PUCCH repetition. Figure 8 An example of the case where PUCCH repetition uses only full-duplex time slots is shown in . Note that the use of full-duplex operation by the gNB when scheduling DL reception and / or UL transmission in a time slot or symbol does not have to be identified or known to the UE. The allowed or disallowed time domain resources for PUCCH repetition may be configured and / or determined by the UE by several possible means, e.g. using a TDRA table, referring to the slot / symbol type, using absolute slot numbering relative to a common DL time reference (such as SFN) and / or using slot / symbol numbering in a (sub)frame, using relative slot / symbol numbering determined relative to a timing reference (such as slots / symbols associated with DCI reception or the like), or using parameter values ​​or settings.

[0168] When the PUCCH transmission in the PUCCH repetition uses a full-duplex time slot, the UE selects a first PUCCH configuration associated with the SBFD time slot / symbol to determine one or more PUCCH transmission settings for the SBFD time slot / symbol. For example, based on the first PUCCH configuration, the UE may select a value or list, or select a value from a list of DL data to UL acknowledgement (ACK) timing to determine the first PUCCH transmission of the PUCCH repetition in the SBFD time slot / symbol. For example and based on the first PUCCH configuration, the UE may determine the number of repetitions used in the SBFD time slot / symbol, or the setting for the DMRS bundling indication in the SBFD time slot / symbol, or the cyclic or sequential mapping pattern for the PUCCH repetition associated with the spatial setting or power control setting in the SBFD time slot / symbol, or the frequency hopping (FH) parameter (such as enabled or disabled) or the configuration of the FH start PRB or the second hopping PRB on the SBFD time slot / symbol, or the maximum code rate or number of PRBs for the PUCCH format when transmitting on the SBFD time slot / symbol. When a PUCCH transmission in a PUCCH repetition uses a non-full-duplex time slot (e.g., a UL time slot), the UE selects a second PUCCH configuration associated with a non-SBFD time slot / symbol to determine one or more PUCCH transmission settings for the non-SBFD time slot / symbol. For example, based on the second PUCCH configuration, the UE may select a value or list, or select a value from a list of DL data to UL acknowledgement (ACK) timing, to determine a first PUCCH transmission for a PUCCH repetition in a non-SBFD time slot / symbol. For example and based on the second PUCCH configuration, the UE may determine a number of repetitions in a non-SBFD time slot / symbol, or a setting for a DMRS bundling indication in a non-SBFD time slot / symbol, or a cyclic or sequential mapping pattern for a PUCCH repetition associated with a spatial setting or a power control setting in a non-SBFD time slot / symbol, or a frequency hopping (FH) parameter (such as enabled or disabled) or a configuration of an FH start PRB or a second frequency hopping PRB on a non-SBFD time slot / symbol, or a maximum code rate or number of PRBs for a PUCCH format when transmitted on a non-SBFD time slot / symbol.

[0169] For example, for PUCCH repetition using SBFD slots / symbols, the number of repetitions n may be provided or indicated to the UE. rep,SBFD =4, and for PUCCH repetitions using non-SBFD slots / symbols, the number of repetitions n may be provided or indicated to the UE. rep,non-SBFD=2. For example, the UE may be instructed and use a first list of DL data to UL acknowledgement (ACK) timing (such as [2, 3, 5, 7] slots) to determine the first slot in the PUCCH repetition to occur in a SBFD slot / symbol, and the UE may be instructed and use a second list of DL data to UL acknowledgement (ACK) timing (such as [5, 6, 8] slots) to determine the first slot in the PUCCH repetition to occur in a non-SBFD slot / symbol. For example, a first FH configuration for PUCCH repetition using SBFD slots / symbols may be provided to the UE, indicating that FH is enabled in the SBFD slot / symbol using the first PRB and the second hop PRB, but a second FH configuration for PUCCH repetition using non-SBFD slots / symbols indicates to the UE that FH is disabled on non-SBFD slots / symbols. For example, for PUCCH repetition using SBFD slots / symbols, a maximum code rate cr may be provided or indicated to the UE. SBFD = 'zerodot25', and for PUCCH repetitions using non-SBFD slots / symbols, the maximum code rate cr may be provided or indicated to the UE non-SBFD ='zerodot60'. For example, for PUCCH repetition using SBFD slots / symbols, the number of PRBs n may be provided or indicated to the UE. PRB,SBFD =4, and for PUCCH repetition using non-SBFD slots / symbols, the number of PRBs n may be provided or indicated to the UE. PRB,non-SBFD =8.

[0170] When the usage of only normal UL timeslots for PUCCH repetition is configured for the UE, the legacy UE behavior follows, e.g., the UE sends PUCCH for PUCCH repetition in timeslots of type U and / or F when scheduled by the gNB, unless the PUCCH transmission is omitted by REF3. When the usage of only full-duplex timeslots is configured for PUCCH repetition, the UE does not send PUCCH for PUCCH repetition in timeslots of type U after gNB scheduling. The UE determines the potentially available timeslots for PUCCH transmission in PUCCH repetition using the new RRC configuration. When the usage of both full-duplex UL timeslots and normal UL timeslots is configured for PUCCH repetition, the UE sends PUCCH in timeslots of type U and / or F subject to gNB scheduling, and wherein the UE determines the potentially available timeslots using the new RRC configuration.

[0171] One reason to configure allowed (or disallowed) time domain resources for PUCCH repetition is to preserve UL SE and UL data peak throughput for UEs in good link conditions without sacrificing achievable UL radio range for UL control signals for UEs in poor link conditions (and vice versa). When the gNB supports full-duplex operation, additional time slots for UL transmission can be made available to UEs in poor link conditions. These UEs can then use PUCCH repetition to increase their achievable UL radio range when a larger number of time slots are used to send UL control signals compared to a TDD cell without full-duplex operation (which (in effect) has fewer normal UL time slots). The segmentation of the UL scheduling BW for data transmission in normal UL time slots, which is caused by the need to place the full-duplex UL subband in the carrier center as in the related art, is eliminated, which is caused by PUCCH repetition across both full-duplex and normal UL time slots. A maximum number of PUCCH repetitions can be supported, for example up to 8.

[0172] Another reason is that the improved flexibility in configuring the allowed (or not allowed) time domain resources for PUCCH repetition when full-duplex slots are used allows to offset the losses caused by different required transmit UE transmit power settings and different UL beamforming gains. Due to the gNB antenna panel design, UL reception in a full (e.g. normal) UL slot will use a different number of TRXs and use a larger effective Rx area compared to the SBFD UL subband in a SBFD slot. Similar considerations apply to gNB DL transmissions in a full (e.g. normal) DL slot vs. SBFD slot. For example, gNB Rx in a normal UL slot uses a 12V×8H×2P panel of size 40×60cm to use all available 48TRXs. gNB Rx in a SBFD slot uses only 16 TRXs and 1 / 3 of the plane for Rx mode, while the remaining 32 TRXs and 2 / 3 of the plane are used for simultaneous DL transmissions. The gNB will collect less useful signal energy per received UL symbol in a SBFD slot compared to a UL transmission made by the UE in a normal UL slot. There is less link gain when comparing full duplex to UL reception in normal UL timeslots. Different antenna and panel designs exist to support full duplex operation on the gNB side. The design options may evolve over time as the technology matures. Common to existing and anticipated future design options for antennas and panels is that the number of TRXs and the available Tx or Rx aperture area for Tx and / or Rx in a normal DL or UL timeslot are typically not the same when compared to DL transmission or UL reception in a SBFD timeslot. Therefore, the increased flexibility of the gNB in ​​controlling the time domain allocation of PUCCH transmissions from UEs in a system supporting full duplex operation is beneficial to improve radio resource efficiency.

[0173] Fig. 9 An example UE determination of available time slots for PUCCH repetition using common RRC 900 according to an embodiment of the present disclosure is shown. Fig. 9 The embodiment shown in which a UE determines available time slots for PUCCH repetition using common RRC 900 is for illustration only. Fig. 9 The scope of the present disclosure is not limited to any particular implementation in which a UE uses the common RRC 900 to determine available time slots for PUCCH repetition.

[0174] In one embodiment, the UE is provided with an RRC configuration using common RRC signaling such as a system information block (SIB) (e.g., SIB1), where the UE is configured with an allowed time slot set or a disallowed time slot set where PUCCH transmission of PUCCH repetitions may or may not occur.

[0175] In a first step, the UE determines 'potentially available' time slots or symbols for PUCCH transmission in a PUCCH repetition using a provided common RRC configuration. In a second step, the UE determines 'available' time slots or symbols for PUCCH transmission in a PUCCH repetition using a configured or provided number of repetitions associated with DL reception using dynamic grant or associated with DL semi-persistent transmission or associated with periodic, semi-persistent or aperiodic UCI transmission (such as CSI) using PUCCH.

[0176] In order to determine by the UE the potentially available timeslots or symbols for PUCCH transmission in a PUCCH repetition using the common RRC configuration provided in the first step, there are several possibilities to provide an indication of allowed or not allowed timeslots to the UE.

[0177] In one example, the xdd-config provided by the SIB may designate a timeslot or symbol as one or a combination of types 'D', 'U', 'F' or 'N / A' using a time domain pattern with a configurable periodicity of a configured period. The UE considers symbols in timeslots indicated as 'D' by the xdd-config as potentially available for reception, e.g., no PUCCH transmission is possible, and considers symbols in timeslots indicated as 'U' by the xdd-config as potentially available for transmission, e.g., PUCCH transmission is possible. The UE considers symbols in timeslots indicated as 'F' by the xdd-config as potentially available for reception or transmission, where the gNB scheduling determines the UE transmit or receive behavior. The UE considers symbols in timeslots indicated as 'N / A' by the xdd-config as not available for reception or transmission. The xdd-config is provided separately from the tdd-UL-DL-ConfigurationCommon. When provided for the same time domain resources, the first slot or symbol type indicated by xdd-config can be independent of the second slot or symbol type 'D', 'U', 'F' indicated by tdd-UL-DL-ConfigurationCommon. In this case, the UE can rely on appropriate network configuration to ensure consistency between the first slot or symbol type and the second slot or symbol type (when both are provided). Alternatively, one of the slot or symbol types has priority, for example, the slot or symbol type provided by tdd-UL-DL-ConfigurationCommon determines the UE behavior when both types are provided. In addition, the slot or symbol configuration of the first type provided by xdd-config may only be applied to some slots or symbol configuration types of the second type, for example, the slot or symbol type provided by xdd-config may only be applied to symbols or slots that are not specified as 'D' by the tdd-UL-DL-ConfigurationCommon type provided for the same time domain resources. Note that the latter case is conceptually similar, but different from the case when tdd-UL-DL-ConfigurationDedicated is provided to the UE. One reason is that symbols or slots of type 'U' in tdd-UL-DL-ConfigurationCommon may still be specified by xdd-config as 'unusable' for PUCCH transmission, even though tdd-UL-DL-ConfigurationCommon may allow the use of the same time domain resources for other types of UL transmissions, such as PUSCH, SRS or RACH.Unlike tdd-UL-DL-ConfigurationDedicated which can only provide UE-specific configuration for symbols or slots specified as 'F' in tdd-UL-DL-ConfigurationCommon, the slot or type allocation provided by xdd-config is not restricted, for example, even 'D' slots or symbols in tdd-UL-DL-ConfigurationCommon can be used for PUCCH transmission of UEs supporting the enhanced support features of (gNB) full-duplex transmission.

[0178] consider Figure 7 Example of a single carrier full-duplex configuration as shown in . The gNB configures SIB1 tdd-UL-DL-ConfigurationCommon with {dl-UL-TransmissionPeriodicity,nrofDownlinkSlots,nrofDownlinkSymbols,nrofUplinkSlots,nrofUplinkSymbols} = {P = 2.5ms, 3DL slots, 12DL symbols, 0UL symbols, 1UL slot} or DDDS(D)U. Therefore, a legacy UE or a UE not supporting the feature for enhanced support of (gNB) full-duplex operation determines that any UL transmission can only occur in slot #5 when scheduled. When the gNB is configured with SIB1 xdd-config with N / AUUN / AU, the UE determines that UL transmissions including PUCCH transmissions with PUCCH repetitions can occur in slots #2, #3, and #5. When SIB1 xdd-config provides the configuration N / AUUN / AN / A to the UE, the UE determines that PUCCH transmissions with PUCCH repetitions may occur in slots #2 and #3, but not in slot #5. Note that other UL transmissions listed above, such as SRS, PUSCH, etc., may still be scheduled for the UE using 'U' slot #5. When SIB1 tdd-UL-DL-ConfigurationCommon provides DFFSU and xdd-config provides N / AUUN / AN / A, the UE also determines that PUCCH transmissions, when scheduled, may occur in slots #2 and #3, but not in slot #5. Note that using the 'U' slot #5 provided by Figure 7 The UE determination of the UL transmission for the provided example full-duplex time slots #2 and #3 may include additional transmit or receive parameters provided by the xdd-config, such as the frequency domain behavior of the transmission in the full-duplex time slots, e.g., the start, size and / or end of the SBFD UL subband in the time slot or symbol.

[0179] In one example, the xdd-config in the SIB provides a parameter, e.g., a bit flag, setting, or value, indicating whether PUCCH transmission is enabled or disabled for a time slot type (e.g., time slot type 'D', F', or 'U' indicated by tdd-UL-DL-ConfigurationCommon). The time slot type indicated by the common RRC configuration may be associated with a single parameter and / or multiple such parameters provided by the xdd-config, e.g., one parameter per time slot type may be provided. The parameters provided by the xdd-config may provide settings for more than one time slot or symbol type. When a first parameter provided by the xdd-config for PUCCH transmission is set to enabled for a first time slot or symbol type 'F', the UE determines the symbols potentially available for PUCCH transmission in the time slot indicated as 'F' by tdd-UL-DL-ConfigurationCommon, otherwise the UE determines that the corresponding time domain resources are not available for PUCCH transmission. The xdd-config may provide a second parameter to indicate whether PUCCH transmission is set to enabled for a second time slot or symbol type 'U' provided by tdd-UL-DL-ConfigurationCommon. When the second parameter provided by xdd-config for PUCCH transmission is set to enabled for timeslot type 'U', the UE determines symbols potentially available for PUCCH transmission in the timeslot indicated as 'U' by tdd-UL-DL-ConfigurationCommon, otherwise the UE determines that the corresponding time domain resources are not available for PUCCH transmission.

[0180] consider Figure 7 Example of a single carrier full duplex configuration in . The gNB configures SIB1 tdd-UL-DL-ConfigurationCommon to DFFSU. A legacy UE or a UE not supporting features for enhanced support (gNB) of full duplex operation determines that any UL transmission can only occur in slots #2, #3 and #5 when scheduled. The gNB configures SIB1xdd-config using a first parameter and a second parameter indicating 'enabled' or 'disabled' for a first slot type 'F' and a second slot type 'U', respectively. The first parameter is set to 'enabled' and the second parameter is set to 'disabled'. The UE determines that full duplex slots #2 and #3 are potentially available for PUCCH transmissions instead of slot #5, e.g. a normal UL slot. Note that other UL transmissions listed above, such as SRS, PUSCH, etc., may still be scheduled for the UE using 'U' slot #5. Note that the use of Figure 7The UE determination of UL transmissions for the provided example full-duplex slots #2 and #3 may include additional transmit or receive parameters provided by xdd-config, such as the frequency domain behavior of the transmissions in the full-duplex slots, for example, the start, size and / or end of the SBFD UL subband in the slot or symbol. One reason is the reduced signaling overhead when configuring the time domain transmission behavior in a TDD cell providing full-duplex support. The existing common RRC signaling providing the slot type indication is reused, but the existing UL transmission behavior for the slot or symbol type is modified by a bit flag.

[0181] In one example, xdd-config provides a bitmap that indicates whether PUCCH repetition is enabled or disabled for specified time domain resources (e.g., time slots or symbols) associated with full-duplex time slots and / or normal UL time slots. The bitmap can be defined using a fixed length, or the bitmap can have a variable length for a suitable configurable periodicity. For example, the length of the bitmap can correspond to the UL-DL frame configuration period or mode 1 period or a combined mode 1 and / or mode 2 period of the reference tdd-UL-DL-ConfigurationCommon. The UE considers symbols in time slots indicated as 'enabled' by xdd-config to be potentially available for PUCCH transmission. The UE considers symbols in time slots indicated as 'disabled' by xdd-config to be unavailable for PUCCH transmission. The bits in the bitmap can indicate transmission settings for a group of symbols or time slots. Multiple bitmaps may be provided, for example, different bitmaps may be applied to different types of UL channels or signals, such as PUCCH, PUSCH, SRS or PRACH, or different bitmaps may be applied to different types of the same UL channels or signals, for example, a first bitmap for PUCCH format 1 and a second bitmap for PUCCH format 3 transmission. xdd-config is provided separately from tdd-UL-DL-ConfigurationCommon. The first slot or symbol type 'enable' or 'disable' is provided by xdd-config, and the second slot or symbol type 'D', 'U', 'F' is provided by tdd-UL-DL-ConfigurationCommon. For the same time domain resource, there may be a first type and a second type of indication. Note that only one slot or symbol type may be provided for some time domain resources. In the case where only one of the slot or symbol types is provided for the time domain resource, the UE applies that slot or symbol type. For example, when only slot or symbol type 'Enabled' is provided for a slot or symbol, the UE assumes DL reception "as if" it is configured with 'U' (and / or 'F') by tdd-UL-DL-ConfigurationCommon. For example, when only slot or symbol type 'D' is provided for a slot or symbol, the UE assumes DL reception "as if" it is configured as 'Disabled' by xdd-config. In addition, the slot or symbol configuration of the first type provided by xdd-config may only be applied to some slot or symbol configuration types of the second type, for example, the slot or symbol type provided by xdd-config may only be applied to symbols or slots that are not specified as 'D' by the tdd-UL-DL-ConfigurationCommon type provided for the same time domain resources.

[0182] consider Figure 7Example of a single carrier full duplex configuration shown in . The gNB configures SIB1 TDD-UL-DL-ConfigurationCommon to DFFS(D)U. A legacy UE or a UE not supporting features for enhanced support of (gNB) full-duplex operation determines that any UL transmission can only occur in slots #2, #3 and #5 when scheduled. The gNB configures SIB1 xdd-config using a bitmap with a value of 'enabled' or 'disabled' per slot and is set to '01100' using a length of 5 for the DL-UL allocation period corresponding to the common TDD UL-DL frame configuration. The UE determines that full-duplex slots #2 and #3 are potentially available for PUCCH transmissions, but not slot #5, e.g. a normal UL slot. Note that other UL transmissions listed above, such as SRS, PUSCH, etc., may still be scheduled for the UE using 'U' slot #5. Note that the use of the bitmap defined by Figure 7 The UE determination of the UL transmission for the provided example full-duplex time slots #2 and #3 may include additional transmit or receive parameters provided by the xdd-config, such as the frequency domain behavior of the transmission in the full-duplex time slots, e.g., the start, size and / or end of the SBFD UL subband in the time slot or symbol.

[0183] In one example, the xdd-config in the SIB may specify a slot or symbol as one of the types 'simultaneous Tx-Rx', 'Rx only', or 'Tx only' using at least one time domain pattern with configurable periodicity for the configuration period. The UE considers symbols in slots indicated by the xdd-config as 'Rx only' as potentially available for reception, e.g., no PUCCH transmission is possible, and considers symbols in slots indicated by the xdd-config as 'Tx only' as potentially available for transmission, e.g., PUCCH (or other types of UL) transmissions are possible when scheduled. The UE considers symbols in slots indicated by the xdd-config as 'simultaneous Tx-Rx' as potentially available for reception or transmission, e.g., the gNB may schedule DL transmission or UL reception in that time domain resource. The xdd-config is provided separately from the tdd-UL-DL-ConfigurationCommon. A first slot or symbol type 'simultaneous Tx-Rx', 'Rx only' or 'Tx only' is indicated by xdd-config, and a second slot or symbol type 'D', 'U', 'F' is indicated by tdd-UL-DL-ConfigurationCommon. For the same time domain resource, there may be a first type and a second type of indication. Note that only one slot or symbol type may be provided for some time domain resources. In this case, when only one of the slot or symbol types is provided for the time domain resource, the UE applies that slot or symbol type. For example, when only the slot or symbol type 'Rx only' is provided for a slot or symbol, the UE assumes DL reception "as if" it was configured with 'D' (and / or 'F') by tdd-UL-DL-ConfigurationCommon. For example, when only the slot or symbol type 'D' is provided for a slot or symbol, the UE assumes DL reception "as if" it was configured with 'Rx only' by xdd-config. In addition, the first type of time slot or symbol configuration provided by xdd-config can be applied only to some time slot or symbol configuration types of the second type, for example, the time slot or symbol type provided by xdd-config can be applied only to symbols or time slots that are not specified as 'D' by the tdd-UL-DL-ConfigurationCommon type provided for the same time domain resources. xdd-config also provides parameters, such as a bit flag, a bitmap, or a value (set), indicating whether PUCCH transmission is enabled or disabled for full-duplex time slots and / or for normal UL time slots.For a time slot or symbol for which the UE determines the first time slot or symbol type as 'simultaneous Tx-Rx', such as a full-duplex time slot or symbol, if the first bit flag provided by the xdd-config indicates "PUCCH transmission in a full-duplex time slot or symbol", the UE determines the corresponding time domain resources as potentially available for PUCCH transmission, otherwise the UE only determines the 'Tx only' (or 'U') symbol or time slot as potentially available. For a time slot or symbol for which the UE determines the first time slot or symbol type as 'Tx only' (e.g., a normal UL time slot or symbol), if the second bit flag provided by the xdd-config indicates "PUCCH transmission in an UL time slot or symbol", the UE determines the corresponding time domain resources as potentially available for PUCCH transmission. When both the first bit flag and the second bit flag are set to enabled, the UE determines that time slots or symbols of both 'simultaneous Tx-Rx' and 'Tx only' types are potentially available for UL transmission of PUCCH. A default rule may be used, for example, when the first bit flag is set to enabled, the UE may determine that PUCCH transmissions in time domain resources indicated as 'simultaneous Tx-Rx' (or 'F') symbols or slots are also potentially available, but UL transmissions are possible in all 'U' slots unless otherwise configured.

[0184] consider Figure 7 Example of single carrier full duplex configuration in tdd-UL-DL. The gNB configures SIB1 tdd-UL-DL-ConfigurationCommon to {dl-UL-TransmissionPeriodicity,nrofDownlinkSlots,nrofDownlinkSymbols, nrofUplinkSlots,nrofUplinkSymbols} = {P = 2.5ms, 3DL slots, 12DL symbols, 0UL symbols, 1UL slot} or DDDSU. Legacy UEs or UEs that do not support the feature for enhanced support (gNB) for full duplex operation determine that any UL transmission can only occur in slot #5 when scheduled. When the gNB configures SIB1 xdd-config with 'Rx only' - 'simultaneous Tx-Rx' - 'simultaneous Tx-Rx', 'Rx only', 'Tx only', and the first bit flag enabling PUCCH transmission in full-duplex slots is set, but the second bit flag enabling PUCCH transmission in normal UL slots is not set, the UE determines that UL transmission of PUCCH in PUCCH repetition can occur in full-duplex slots #2 and #3. Note that other UL transmissions listed above, such as SRS, PUSCH, etc., can still be scheduled for the UE using 'U' slot #5. Note that the use of Figure 7The UE determination of the UL transmission for the provided example full-duplex time slots #2 and #3 may include additional transmit or receive parameters provided by the xdd-config, such as the frequency domain behavior of the transmission in the full-duplex time slots, e.g., the start, size and / or end of the SBFD UL subband in the time slot or symbol.

[0185] When the UE is provided with separate PUCCH configurations associated with different slot or symbol types (i.e., SBFD and non-SBFD slots / symbols or 'D' and 'F' and 'U' respectively) to indicate UE-specific PUCCH parameters or cell-specific PUCCH parameters in a BWP or in a carrier of a cell carrier group, the UE selects and determines the PUCCH configuration from the PUCCH configurations based on the slot or symbol type to determine the UL transmission parameters.

[0186] For example, separate PUCCH configurations, separate PUCCH format configurations, or separate PUCCH resources or PUCCH resource sets for SBFD and non-SBFD time slots / symbols, respectively, may be provided or indicated to the UE. Separate values ​​of the same parameter in a PUCCH configuration, a PUCCH resource or resource set, or a PUCCH format may be provided to the UE as information, wherein a first value of the parameter is indicated for use by the UE in a non-SBFD time slot / symbol, and then a second value of the parameter is indicated for use by the UE in a SBFD time slot / symbol.

[0187] After the UE determines potential available time slots or symbols for PUCCH transmission in a PUCCH transmission using the provided common RRC configuration, the UE determines available time slots for PUCCH transmission in a PUCCH repetition.

[0188] Consider the example where only tdd-UL-DL-ConfigurationCommon (but not tdd-UL-DL-ConfigurationDedicated) and xdd-config are provided by the SIB, the xdd-config uses a bitmap with 'enable' or 'disable' values ​​per timeslot or per timeslot type.

[0189] The UE first determines the number of repetitions K. The UE may be instructed to use PUCCH resources in PUCCH is sent on time slots, where if the PUCCH resource is indicated by the DCI format and includes the parameter PUCCH-nrofSlots, then Provided by PUCCH-nrofSlots, otherwise, Provided by parameter nrofSlots. If parameter subslotLengthForPUCCH is provided to the UE, it is used for The repeated PUCCH transmissions on each slot include a number of symbols indicated by subslotLengthForPUCCH.

[0190] for UE PUCCH transmission with UCI is repeated on each time slot. The PUCCH transmission in each of the subslots has the same number of consecutive symbols as provided by nrofSymbols. If subslotLengthForPUCCH is not provided, The PUCCH transmission in each of the subslots has the same first symbol as provided by the parameter startingSymbolIndex; otherwise mod(startingSymbolIndex, subslotLengthForPUCCH).

[0191] If the UE determines that for PUCCH transmission in a slot, the number of symbols available for PUCCH transmission is less than the value provided by nrofSymbols of the corresponding PUCCH format, the UE does not send PUCCH in that slot. If the parameter xdd-config, when provided for PUCCH transmission in a symbol or slot, indicates that the symbol or slot is not available for PUCCH transmission with PUCCH repetition, the UE does not send PUCCH in that symbol or slot.

[0192] The SS / PBCH block symbol is the symbol of the SS / PBCH block with the candidate SS / PBCH block index, where the candidate SS / PBCH block index corresponds to the SS / PBCH block index indicated to the UE through the parameter ssb-PositionsInBurst in SIB1 or the parameter ssb-PositionsInBurst in RRC ServingCellConfigCommon, as described in REF3.

[0193] For unpaired spectrum, the UE determines the time slots, starting from a time slot indicated to the UE for HARQ-ACK reporting, or a time slot determined for SR reporting as described in REF3, or a time slot for CSI reporting as described in REF4, and having a UL symbol or flexible symbol that is not a SS / PBCH block symbol provided as the first symbol by startingSymbolIndex, and having consecutive UL symbols or flexible symbols that are not SS / PBCH block symbols equal to or greater than the number of symbols provided by nrofSymbols as described in REF3 starting from the first symbol, and wherein the availability of the symbols or time slots is set to 'enabled' when indicated by xdd-config.

[0194] For paired spectrum or supplementary uplink frequency bands, the UE determines the frequency bands to be used for PUCCH transmission. The time slot is consecutive time slots, starting from the time slot indicated to the UE for HARQ-ACK reporting, or the time slot determined for SR reporting as described in REF3, or the time slot for CSI reporting as described in REF4. If the parameter xdd-config, when provided for PUCCH transmission in a symbol or time slot, indicates that the symbol or time slot is not available for PUCCH transmission with PUCCH repetition, the UE does not send PUCCH in that symbol or time slot.

[0195] In one embodiment, the UE is provided with an RRC configuration using UE-specific RRC signaling, wherein the UE is configured with an allowed set of time slots or a disallowed set of time slots in which PUCCH repetition can or cannot occur. For example, the UE-specific RRC signaling can be provided to the UE in an IE such as pucch-Config, pucch-ConfigCommon, BWP-UplinkCommon, BWP-UplinkDedicated, or ServingCellConfig and / or in an IE such as tdd-UL-DL-ConfigurationDedicated and / or slotFormatCombination. For example, UE-specific RRC signaling for the UE to determine an allowed set of time slots or a disallowed set of time slots in which PUCCH repetition can or cannot occur can be provided by the RRC as part of a PUCCH resource set configuration, a PUCCH resource configuration, and / or can be provided in a configuration associated with a PDSCH-to-HARQ_feedback or PDSCH-to-HARQ feedback (HARQ_feedback) timing indicator field of a DCI.

[0196] In a first step, the UE determines "potentially available" time slots or symbols for PUCCH transmission in a PUCCH repetition using a provided UE-specific RRC configuration. In a second step, the UE determines "available" time slots or symbols for PUCCH transmission in a PUCCH repetition using a configured or provided number of repetitions associated with DL reception using dynamic grants or associated with DL semi-persistent transmissions or associated with periodic, semi-persistent or aperiodic UCI transmissions (such as CSI) using PUCCH.

[0197] In one example, a PUCCH configuration (e.g., pucch-Config) provides a parameter (e.g., a bit flag, setting, or value) indicating whether PUCCH transmission is enabled or disabled for a time slot type (e.g., time slot type 'D', 'F', or 'U' indicated by a TDD UL-DL frame configuration and / or an SFI (e.g., tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, or slotFormat)). The time slot type indicated by the TDD UL-DL frame configuration and / or the SFI may be associated with a single parameter and / or multiple such parameters provided by the PUCCH configuration, for example, one parameter per time slot type may be provided. The parameters provided by the PUCCH configuration may provide settings for more than one time slot or symbol type. When a first parameter provided by the PUCCH configuration for PUCCH transmission is set to enabled for a first time slot or symbol type 'F', the UE determines symbols in the time slot indicated as 'F' that are potentially available for PUCCH transmission, otherwise the UE determines that the corresponding time domain resources are not available for PUCCH transmission. The PUCCH configuration may provide a second parameter to indicate whether PUCCH transmission is set to be enabled for a second time slot or symbol type 'U'. When the second parameter provided by the PUCCH configuration for PUCCH transmission is set to be enabled for time slot type 'U', the UE determines the symbols potentially available for PUCCH transmission in the time slot indicated as 'U', otherwise the UE determines that the corresponding time domain resources are not available for PUCCH transmission.

[0198] consider Figure 7An example of a single carrier full-duplex configuration shown in . The gNB configures SIB1 tdd-UL-DL-ConfigurationCommon to DFFSU. A legacy UE or a UE that does not support features for enhanced support (gNB) for full-duplex operation determines that any UL transmission can only occur in time slots #2, #3 and #5 when scheduled. The gNB provides the PUCCH configuration to the UE using a first parameter and a second parameter indicating 'enable' or 'disable' for a first time slot type 'F' and a second time slot type 'U', respectively. The first parameter is set to 'enable' and the second parameter is set to 'disable'. The UE determines that full-duplex time slots #2 and #3 are potentially available for PUCCH transmissions with PUCCH repetitions, but not time slot #5 (e.g., a normal UL time slot). Note that other types of UL transmissions such as SRS or PUSCH as described above may still be scheduled for the UE using 'U' time slot #5. Note that the use of the PUCCH configuration indicated by Figure 7 The UE determination of the UL transmission for the example full-duplex time slots #2 and #3 provided may include additional transmit or receive parameters provided by the PUCCH configuration, such as the frequency domain behavior of the transmission in the full-duplex time slot, e.g., the start, size and / or end of the SBFD UL subband in the time slot or symbol.

[0199] In one example, the PUCCH configuration provides a parameter indicating whether PUCCH transmission in PUCCH repetition is enabled or disabled for a specified time slot, for example, a bit flag, setting or value for each index row of a table. The PUCCH resource configuration indicates the configured number of repetitions of the selected PUCCH resource. A new parameter txType is provided for the selected PUCCH resource. txType indicates whether PUCCH transmission in PUCCH repetition is enabled or disabled in the specified time slot. One reason is that this method retains the related art RRC configuration signaling for PUCCH repetition, for example, the existing protocol design can be reused mainly by introducing additional control to selectively allow or not allow selected time domain resources.

[0200] For example, txType may specify a slot or symbol as one or a combination of types 'D', 'U', 'F', or 'N / A' with reference to a time domain mode having a configurable periodicity for a configuration period (e.g., with reference to slot types 'D', 'F', or 'U' determined using a TDD UL-DL frame configuration and / or using an SFI). In another example, txType may specify a slot or symbol type 'simultaneous Tx-Rx', 'Rx only', or 'Tx only' with reference to xdd-config. In another example, txType may specify a slot or symbol with reference to a bitmap or list of slots or symbols (or groups of slots or symbols) indicating whether PUCCH repetition is enabled or disabled in a time domain resource, wherein the bitmap or list of slots may be configured by RRC alone, e.g., using a PUCCH configuration.

[0201] The UE selects a PUCCH resource set. The UE selects a PUCCH resource in a PUCCH resource set using, for example, a PRI. The UE determines the number of repetitions of the selected PUCCH resource and a new parameter txType associated with the PUCCH resource. The txType may be configured differently for different PUCCH resources. No txType may be provided for a PUCCH resource, or a default behavior may be defined for a PUCCH resource. For example, a first PUCCH resource may allow PUCCH transmissions with PUCCH repetitions using only a time slot type 'Tx Only', while a second PUCCH resource of the PUCCH may allow PUCCH transmissions with PUCCH repetitions using a time slot type 'Tx-Rx Simultaneously'.

[0202] Using different txType settings for each PUCCH resource, the first PUCCH repetition (e.g., resulting in the number of PUCCH repetitions in K slots) can be assigned to a different slot type than the second (later) PUCCH repetition. Note that instead of configuring the parameter txType for a PUCCH resource, the txType can alternatively be configured for a PUCCH resource set or a PUCCH format.

[0203] consider Figure 7Example of a single carrier full-duplex configuration in . The gNB configures SIB1TDD-UL-DL-ConfigurationCommon to DDDSU. A legacy UE or a UE not supporting features for enhanced support of (gNB) full-duplex operation determines that any UL transmission can only occur in slot #5 when scheduled. The gNB provides the PUCCH configuration using the parameter txType associated with a list of not allowed slots for PUCCH resources. The list may be provided explicitly in the PUCCH configuration or may be provided separately using other RRC signaling messages or IEs. For illustration purposes, it is assumed that the slot numbering starts at 0 and is referenced relative to the slot numbering of the UL-DL frame configuration. A set of PUCCH resources is configured for the UE. The first PUCCH resource in the set is configured with 4 repetitions and txType = [4], indicating that the PUCCH transmission of the PUCCH repetitions may occur in normal UL slots, for example, in slot #5, but not in other slots. The second PUCCH resource in the set is configured with 8 repetitions and txType = [1, 2], indicating that PUCCH transmissions of PUCCH repetitions may occur in full-duplex time slots (e.g., time slots #2 and #3), but not in other time slots. The UE receives a first DL grant DCI, e.g., type 'D', in time slot #1, resulting in selection of the first PUCCH resource and the first PUCCH transmission of the PUCCH repetition determined in time slot #5. The UE determines that time slot #5 (e.g., a normal UL time slot) is potentially available, but all other time slots are not available. After the first PUCCH repetition is terminated, the UE receives a second (later) DL grant DCI in DL time slot #1, resulting in selection of the second PUCCH resource in the PUCCH resource set. The UE determines that full-duplex time slots #2 and #3 are available for PUCCH transmissions of PUCCH repetitions, but time slots #1, #4, #5 are not available, e.g., normal UL time slots are not available. Note that the use of Figure 7 The UE determination of the UL transmission for the example full-duplex time slots #2 and #3 provided may include additional transmit or receive parameters provided by the PUCCH configuration, such as the frequency domain behavior of the transmission in the full-duplex time slot, e.g., the start, size and / or end of the SBFD UL subband in the time slot or symbol.

[0204] Fig.10 An example UE determination of available time slots for PUCCH repetition using PUCCH configuration 1000 according to an embodiment of the present disclosure is shown. Fig.10 The illustrated embodiment in which a UE determines available time slots for PUCCH repetition using PUCCH configuration 1000 is for illustration only. Fig.10 The scope of the present disclosure is not limited to any particular implementation of a UE using the PUCCH configuration 1000 to determine available time slots for PUCCH repetition.

[0205] In one example, a PUCCH configuration (e.g., pucch-Config) provides a bitmap or list of time slots or symbols (or groups of time slots or symbols) indicating whether PUCCH repetition is enabled or disabled for a specified time domain resource (e.g., time slot or symbol) associated with a full-duplex time slot and / or a normal UL time slot. The bitmap may be defined using a fixed length, or the bitmap may have a variable length for a suitable configurable period. For example, the length of the bitmap may correspond to a UL-DL frame configuration period or a mode 1 period or a combined mode 1 and / or mode 2 period of the length of the reference tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated or the reference slotFormat. The UE considers symbols in time slots indicated as 'enabled' by the PUCCH configuration to be potentially available for PUCCH transmission. The UE considers symbols in time slots indicated as 'disabled' by the PUCCH configuration to be unavailable for PUCCH transmission. The bits in the bitmap may indicate transmission settings for a group of symbols or time slots. Multiple bitmaps may be provided, for example, different bitmaps may apply to different types of UL channels or signals, such as PUCCH, PUSCH, SRS or PRACH, or different bitmaps may apply to different types of the same UL channel or signal, for example, a first bitmap for PUCCH format 1 and a second bitmap for PUCCH format 3. When a list of slots or symbols (or slot or symbol groups) is used for indication in a PUCCH configuration, an absolute or relative slot or symbol number relative to a suitable timing reference number is used to identify the time domain resources allowed or not allowed for PUCCH transmission. Multiple lists may be provided, or multiple lists may apply to different types of UL channels or signals or UL transmission behaviors for the same UL channel or signal, such as a first list for PUCCH format 1 and a second list for PUCCH format 3. The UE considers symbols in slots listed as "allowed" or "included" by the PUCCH configuration as potentially available for PUCCH transmission. The UE considers symbols in slots not listed or "not allowed" as not available for PUCCH transmission.

[0206] consider Figure 7Example of a single carrier full duplex configuration shown in . The gNB configures SIB1 tdd-UL-DL-ConfigurationCommon to DFFSU. A legacy UE or a UE not supporting features for enhanced support (gNB) of full-duplex operation determines that any UL transmission can only occur in slots #2, #3 and #5 when scheduled. The gNB provides the PUCCH configuration using a bitmap with a value of 'enabled' or 'disabled' per slot and set to '01100' using the length 5 of the DL-UL allocation period corresponding to the common TDD UL-DL frame configuration. Alternatively, the gNB configures the list of allowed slots for PUCCH repetition as [1, 2] using the PUCCH configuration, where slots are numbered starting from 0. The UE determines that full-duplex slots #2 and #3 are potentially available for PUCCH transmission, but not slot #5, e.g. a normal UL slot. Note that other UL transmissions listed above, such as SRS, PUSCH, etc., may still be scheduled for the UE using 'U' slot #5. Note that the use of the bitmap specified by Figure 7 The UE determination of the UL transmission for the provided example full-duplex time slots #2 and #3 may include additional transmit or receive parameters provided by the xdd-config, such as the frequency domain behavior of the transmission in the full-duplex time slots, for example, the start, size and / or end of the UL subband in the time slot or symbol.

[0207] When the UE is provided with separate PUCCH configurations associated with different slot or symbol types (i.e., SBFD and non-SBFD slots / symbols or 'D' and 'F' and 'U' respectively) to indicate UE-specific PUCCH parameters or cell-specific PUCCH parameters in a BWP or in a carrier of a cell carrier group, the UE selects and determines the PUCCH configuration from the PUCCH configurations based on the slot or symbol type to determine the UL transmission parameters.

[0208] For example, separate PUCCH configurations, separate PUCCH format configurations, or separate PUCCH resources or PUCCH resource sets for SBFD and non-SBFD time slots / symbols, respectively, may be provided or indicated to the UE. Separate values ​​of the same parameter in a PUCCH configuration, a PUCCH resource or resource set, or a PUCCH format may be provided to the UE as information, wherein a first value of the parameter is indicated for use by the UE in a non-SBFD time slot / symbol, and then a second value of the parameter is indicated for use by the UE in a SBFD time slot / symbol.

[0209] After the UE determines potential available time slots or symbols for PUCCH transmission in a PUCCH transmission using the provided UE-specific RRC configuration, the UE determines available time slots for PUCCH transmission in a PUCCH repetition.

[0210] Consider the example where the PUCCH configuration provides only tdd-UL-DL-ConfigurationCommon (but not tdd-UL-DL-ConfigurationDedicated) and xdd-config using the bitmap pucchTdmMask (with a value of 'enabled' or 'disabled' per slot), e.g. as part of the RRC configuration associated with a PUCCH format or associated with a PUCCH resource or associated with a PUCCH resource set. Note that UE-specific signaling in Rel-15 NR and above may use one or a combination of UE-common IEs and UE-specific IEs in the RRC signaling messages sent to the UE.

[0211] The UE first determines the number of repetitions K. The UE may be instructed to use PUCCH resources in PUCCH is sent on time slots, where if the PUCCH resource is indicated by the DCI format and includes the parameter PUCCH-nrofSlots, then Provided by PUCCH-nrofSlots, otherwise, Provided by parameter nrofSlots. If parameter subslotLengthForPUCCH is provided to the UE, it is used for The repeated PUCCH transmissions on each slot include a number of symbols indicated by subslotLengthForPUCCH.

[0212] for UE PUCCH transmission with UCI is repeated on each time slot. The PUCCH transmission in each of the subslots has the same number of consecutive symbols as provided by nrofSymbols. If subslotLengthForPUCCH is not provided, The PUCCH transmission in each of the subslots has the same first symbol as provided by the parameter startingSymbolIndex; otherwise mod(startingSymbolIndex, subslotLengthForPUCCH).

[0213] If the UE determines that for PUCCH transmission in a time slot, the number of symbols available for PUCCH transmission is less than the value provided by nrofSymbols of the corresponding PUCCH format, the UE does not send PUCCH in this time slot. If the parameter pucchTdmMask provided by pucch-Config, when configured for PUCCH transmission in a time slot, indicates that the time slot is not available for PUCCH transmission with PUCCH repetition, the UE does not send PUCCH in this time slot.

[0214] The SS / PBCH block symbol is the symbol of the SS / PBCH block with the candidate SS / PBCH block index, which corresponds to the SS / PBCH block index indicated to the UE through the parameter ssb-PositionsInBurst in SIB1 or the parameter ssb-PositionsInBurst in RRC ServingCellConfigCommon, as described in REF3.

[0215] For unpaired spectrum, the UE determines the time slots, starting from the time slot indicated to the UE for HARQ-ACK reporting, or starting from the time slot determined for SR reporting as described in REF3, or starting from the time slot for CSI reporting as described in REF4, and having a UL symbol or flexible symbol that is not a SS / PBCH block symbol as the first symbol provided by startingSymbolIndex, and having consecutive UL symbols or flexible symbols that are not SS / PBCH block symbols equal to or greater than the number of symbols provided by nrofSymbols as described in REF3 starting from the first symbol, and wherein the availability of the time slot is set to 'enabled' when indicated by pucchTdmMask.

[0216] For paired spectrum or supplementary uplink frequency bands, the UE determines the frequency bands to be used for PUCCH transmission. Time slot is consecutive time slots, starting from the time slot indicated to the UE for HARQ-ACK reporting, or the time slot determined for SR reporting as described in REF3, or the time slot for CSI reporting as described in REF4. If the parameter pucchTdmMask provided by pucch-Config indicates that the time slot is not available for PUCCH transmission with PUCCH repetition when configured for PUCCH transmission in the time slot, the UE does not send PUCCH in the time slot.

[0217] Fig.11An example UE determination of available time slots for PUCCH repetition using UE-specific RRC 1100 according to an embodiment of the present disclosure is shown. Fig.11 The embodiment shown in which a UE determines available time slots for PUCCH repetition using UE-specific RRC 1100 is for illustration only. Fig.11 The scope of the present disclosure is not limited to any particular implementation in which the UE uses the UE-specific RRC 1100 to determine available time slots for PUCCH repetition.

[0218] In one embodiment, the UE is provided with an RRC configuration, wherein the UE is configured with a set of allowed time slots or a set of not allowed time slots in which PUCCH reuse can occur or cannot occur. When specifying time slots or symbols that are allowed or not allowed for PUCCH transmission, the list or sequence can be represented using a SLIV value, or a starting symbol and length pair, or any other suitable signaling. The list or sequence may have a fixed maximum length, for example, N=8. The list or sequence may have a length of 1, for example, only a single PUCCH transmission is subsequently performed. The list or sequence may have a configurable number or a default number of the number of PUCCH transmissions for PUCCH repetition. There may be only one or more lists or sequences of PUCCH resource allocations. For example, a list or sequence of PUCCH resource allocations may be provided by RRC as part of a PUCCH resource set configuration, a PUCCH resource configuration, and / or may be provided in a configuration associated with a PDSCH-to-HARQ_feedback (PDSCH to HARQ feedback) timing indicator field of a dl-DataToUL-ACK or DCI. For example, one or more lists or sequences of PUCCH resource allocations may be provided to the UE in the time domain using UE-specific RRC signaling in IEs such as pucch-Config, pucch-ConfigCommon, BWP-UplinkCommon, BWP-UplinkDedicated, or ServingCellConfig. Note that UE-specific signaling as in Rel-15 NR and above may use one or a combination of UE-common IEs and UE-specific IEs in the RRC signaling message sent to the UE. The PUCCH configuration provided by the RRC may enable or disable and / or parameterize the use of full-duplex or normal UL time slots for PUCCH repetitions, respectively, for the UE. A default list or sequence of PUCCH resource allocations in the time domain for PUCCH repetitions may be provided by a system specification. The use of a default list or sequence of PUCCH resource allocations for PUCCH repetitions may be configured by higher layers of the UE. Different lists or sequences of PUCCH resource allocations in the time domain of PUCCH repetition may be provided for different PUCCH types (eg, PUCCH format 1, format 3, or format 4) or for different PUCCH resources or for different PUCCH resource sets.

[0219] The UE may use a list or sequence of PUCCH resource allocations provided in the RRC configuration of the allowed or not allowed time slots for PUCCH repetition during PUCCH resource selection to determine whether PUCCH transmission in a time slot or symbol can or cannot occur, for example, the UE selects a list or sequence associated with the determined PUCCH resources, or a list or sequence associated with the PDSCH to HARQ feedback timing indicator field in the dl-DataToUL-ACK or DCI to determine in which time slots or symbols PUCCH transmission can or cannot occur. Alternatively, one of multiple lists or sequences of PUCCH resource allocations is configured for the UE by RRC, and then one of the configured lists or sequences of possible PUCCH resource allocations is indicated to the UE by DCI. The UE then uses the index provided by the DCI to determine the potential available time slots for PUCCH transmission for PUCCH repetition using the selected list or sequence of PUCCH resource allocations. The DCI that causes the UE to perform PUCCH transmission may be associated with DL reception using dynamic authorization, or associated with DL semi-persistent transmission. A UE's PUCCH transmission may be associated with a periodic, semi-persistent, or aperiodic UCI transmission (such as CSI).

[0220] In a first step, the UE determines "potentially available" time slots or symbols for PUCCH transmission in PUCCH repetition using a provided UE-specific RRC configuration with a list or sequence of PUCCH resource allocations. In a second step, the UE determines "available" time slots or symbols for PUCCH transmission in PUCCH repetition using a configured or indicated list of PUCCH resource allocations associated with DL reception using dynamic grants, or associated with DL semi-persistent transmissions, or associated with periodic, semi-persistent or aperiodic UCI transmissions (such as CSI) using PUCCH.

[0221] In one example, a list or sequence of PUCCH resource allocations providing an indication of whether PUCCH transmission of a PUCCH repetition is allowed or not allowed for a specified timeslot uses a SLIV value or a startingSymbolIndex and nrofSymbols value pair for each timeslot. Alternatively, another suitable signaling representation may be selected, such as a value of 0 when PUCCH transmission is 'disabled' in a timeslot, and a value of 1 when PUCCH transmission is 'disabled' in a timeslot. Note that the (same or different) PUCCH symbol allocations in the timeslots for PUCCH repetitions may then be provided separately. For simplicity and illustration purposes, the following examples use SLIV values.

[0222] Each symbol allocation in the provided list or sequence specifies a symbol allocation for PUCCH transmission for PUCCH transmission in a time slot. One possible setting or value for a symbol allocation in a time slot may be "invalid" or "skipped", for example, there is no symbol allocation for PUCCH transmission in the corresponding time slot. A sequence or list of symbol allocations for PUCCH resource allocation in the time domain is configured for PUCCH repetition, for example, one symbol allocation is provided for each time slot in a number of time slots. The length of the sequence or list of symbol allocations in the PUCCH repetition may correspond to the number of repetitions K of the PUCCH repetition for the selected PUCCH resource, resource set or for the PUCCH format. The length of the sequence or list of symbol allocations may be less than K, and the sequence or list is repeated completely and / or partially to match the desired number of repetitions that may be configured separately for the PUCCH resource, resource set or PUCCH format. The sequence of the symbol allocation list for PUCCH resource allocation may be defined with respect to continuous time domain resources, or with respect to non-continuous time domain resources, as defined by a suitable set of rules. The symbol allocation of type "Invalid" or "Skip" indicates whether PUCCH transmission in PUCCH repetition is enabled or disabled in the specified time slot. By configuring the symbol allocation in a suitable manner using the "Invalid" setting, for example, PUCCH transmission of PUCCH repetition can be scheduled using only full-duplex time slots, or only UL time slots, or both full-duplex time slots and normal UL time slots, or any desired subset of time domain resources.

[0223] One reason is that this approach reuses protocol design features that are already available in NR, e.g., PUSCH configuration for multi-T PUSCH operation, e.g., the existing protocol design can be largely reused for PUCCH repetition, with appropriate design changes to selectively allow or not allow selected time domain resources to be used for PUCCH repetition.

[0224] The UE selects a PUCCH resource set. The UE selects a PUCCH resource in a PUCCH resource set, for example, using a PRI. The UE determines the number of repetitions of the selected PUCCH resource. If symbol allocation and / or number of repetitions are provided for the selected PUCCH resource, the UE determines the symbol allocation and / or number of repetitions. Different sequences or lists of PUCCH symbol allocations may be configured for different PUCCH resources, resource sets, or for different PUCCH formats. Sequences or lists of different PUCCH resources, resource sets, or PUCH formats may have different lengths, including possible configurations using length = 0 (e.g., no valid allocation) or length = 1 (e.g., PUCCH transmission in a single time slot). Sequences or lists of different PUCCH resource allocations may use different values. Restrictions and / or constraints imposed on allowed symbol allocation values ​​may be defined. For example, when the UE is configured with PUCCH repetition, the UE expects only a single (valid) symbol allocation value other than the value "INVALID" or "SKIP" in the sequence or list of PUCCH resource allocations configured, e.g., the same PUCCH symbol allocation in a time slot must be used in all time slots of the PUCCH repetition except the time slots to be skipped (as indicated by the symbol allocation value "INVALID". Using different lists or sequences of PUCCH symbol allocations for PUCCH resource allocations in the time domain allows setting one or more symbol allocations in the sequence or list to "INVALID" or "SKIP". For example, a first PUCCH resource may allow PUCCH transmissions with PUCCH repetition using only time slot type 'Tx Only', while a second PUCCH resource of the PUCCH may allow PUCCH transmissions with PUCCH repetition using time slot type 'Simultaneous Tx-Rx'.

[0225] consider Figure 7Example of a single carrier full duplex configuration shown in . The gNB configures SIB1 tdd-UL-DL-ConfigurationCommon to DFFS(D)U. A legacy UE or a UE that does not support features for enhanced support of (gNB) full-duplex operation determines that any UL transmission can only occur in slots #2, #3, and #5 when scheduled. The gNB provides a PUCCH configuration with a list or sequence of SLIV values ​​associated with the PUCCH resources of the PUCCH resource set. The number of repetitions corresponding to the PUCCH resource is provided by the length of the sequence, e.g., nrofSlots is not used. The first PUCCH resource is configured with a list or sequence of SLIV=[67, N / A, 67, 67, 67, 67], where SLIV value=67 indicates a PUCCH symbol allocation starting on the 3rd symbol and 11 consecutive symbols of the slot, and where SLIV=N / A indicates an invalid symbol allocation value. PUCCH repetitions are configured for 6 consecutive slots (but 1 slot remains unallocated). The second PUCCH resource is configured with a list or sequence of SLIV=[67, N / A, N / A, N / A, N / A, 67]. PUCCH repetition is also configured for 6 consecutive time slots (but 5 time slots remain unallocated). For the purpose of illustration, it is assumed that dl-DataToUL-ACK is configured by RRC to a value of 4 for all PUCCH transmissions. Note that in general, different dl-DataToUL-ACK values ​​or PDSCH to HARQ feedback timing indicator fields in the DCI may be used. The UE receives a first DL grant DCI in time slot #1 (e.g., with type 'D'), resulting in selection of a first PUCCH resource and a first PUCCH transmission of a PUCCH repetition scheduled in time slot #5 (e.g., a normal UL time slot). The UE determines that time slot #5 (e.g., a normal UL time slot) is potentially available for PUCCH repetition, but the next time slot carrying SSB, for example, is not available, then the next 4 time slots including full-duplex time slots #2 and #3 are potentially available. The UE uses both normal UL time slot #5 and full-duplex time slots #2 and #3 (e.g., over 2 consecutive UL-DL frame configuration periods) to send the first PUCCH repetition. After the first PUCCH repetition terminates, the UE receives a second DL grant DCI in DL time slot #1, resulting in the selection of a second PUCCH resource. The UE determines that PUCCH transmission of the PUCCH repetition can only occur in normal UL time slots (e.g., time slot #5 of the current and next UL-DL configuration periods). Therefore, the UE sends the second PUCCH repetition using only normal UL time slots (e.g., time slot #5) and not in full-duplex time slots #2 and #3. Note that the use of the second PUCCH repetition by Figure 7The UE determination of the UL transmission for the example full-duplex time slots #2 and #3 provided may include additional transmit or receive parameters provided by the PUCCH configuration, such as the frequency domain behavior of the transmission in the full-duplex time slot, e.g., the start, size and / or end of the SBFD UL subband in the time slot or symbol.

[0226] When the UE is provided with separate PUCCH configurations associated with different slot or symbol types (i.e., SBFD and non-SBFD slots / symbols or 'D' and 'F' and 'U' respectively) to indicate UE-specific PUCCH parameters or cell-specific PUCCH parameters in a BWP or in a carrier of a cell carrier group, the UE selects and determines the PUCCH configuration from the PUCCH configurations based on the slot or symbol type to determine the UL transmission parameters.

[0227] For example, separate PUCCH configurations, separate PUCCH format configurations, or separate PUCCH resources or PUCCH resource sets for SBFD and non-SBFD time slots / symbols, respectively, may be provided or indicated to the UE. Separate values ​​of the same parameter in a PUCCH configuration, a PUCCH resource or resource set, or a PUCCH format may be provided to the UE as information, wherein a first value of the parameter is indicated for use by the UE in a non-SBFD time slot / symbol, and then a second value of the parameter is indicated for use by the UE in a SBFD time slot / symbol.

[0228] After the UE determines potential available time slots or symbols for PUCCH transmission in PUCCH transmission using the provided UE-specific RRC configuration with a list or sequence of PUCCH resource allocations in the time domain, the UE determines available time slots for PUCCH transmission in the PUCCH repetition.

[0229] Then, the PUCCH transmission procedure for the UE to determine the available time slots for PUCCH transmission in the PUCCH repetition may follow the other example procedures described herein.

[0230] Fig.12 An example UE determination 1200 of available time slots for PUCCH repetition using DCI according to an embodiment of the present disclosure is shown. Fig.12 The embodiment shown in FIG. 12 where the UE uses DCI 1200 to determine available time slots for PUCCH repetition is for illustration only. Fig.12 The scope of the present disclosure is not limited to any particular implementation of the UE using the DCI 1200 to determine available time slots for PUCCH repetition.

[0231] In one embodiment, an indication of an allowed time slot set or a disallowed time slot set for PUCCH repetition is provided to the UE through L1 control signaling such as DCI.

[0232] In one example, the (DL grant) DCI contains an (existing) PUCCH resource indicator (PRI) field, for example, for determining PUCCH resources. An additional new field txType is configured in the DCI. The UE uses the new field txType to determine an allowed set of time slots or an unallowed set of time slots for PUCCH transmission. For example, txType may specify a time slot or symbol as one or a combination of types 'D', 'U', 'F' or 'N / A' with reference to a time domain mode with configurable periodicity for a configuration period (e.g., with reference to a time slot type 'D', 'F' or 'U' determined using a TDD UL-DL frame configuration and / or using an SFI). In another example, txType may specify a time slot or symbol type 'simultaneous Tx-Rx', 'Rx only' or 'Tx only' with reference to xdd-config. In another example, txType may specify a time slot or symbol with reference to a bitmap or list of time slots or symbols (or groups of time slots or symbols) indicating whether PUCCH repetition is enabled or disabled in the time domain resources of the PUCCH resources, where the bitmap or list of time slots may be configured by RRC alone, for example, using PUCCH configuration. No settings for txType may be provided, or a default behavior may be defined. For example, a first type of PUCCH (e.g., PUCCH F1) may be assigned to a time slot type 'Tx only' or 'U only', while a second type of PUCCH (e.g., PUCCH F3) may be assigned to a time slot type 'simultaneous Tx-Rx' or 'Both F+U'. Similarly, the same or different txTypes may be configured with respect to a PUCCH resource set or a PUCCH resource.

[0233] A new field txType allows independent control of the time domain resource allocation associated with PUCCH transmissions in PUCCH repetitions. The UE may be configured by higher layer signaling to use an index into a (smaller) subset of allowed combinations when determining PUCCH transmission parameters for PUCCH repetitions. For example, a single bit may be used for txType, where a value of 0 is associated with PUCCH transmissions using PUCCH repetitions of normal UL timeslots, e.g. 'Tx only', while a value of 1 indicates PUCCH transmissions in PUCCH repetitions in timeslots of both types 'simultaneous Tx-Rx' and 'Tx only'.

[0234] consider Figure 7Example of single carrier full duplex configuration in tdd-UL-DL. The gNB configures SIB1 tdd-UL-DL-ConfigurationCommon as {dl-UL-TransmissionPeriodicity, nrofDownlinkSlots, nrofDownlinkSymbols, nrofUplinkSlots, nrofUplinkSymbols} = {P = 2.5ms, 3DL slots, 12DL symbols, 0UL symbols, 1UL slot} or DFFS(D)U. A legacy UE or a UE not supporting the feature for enhanced support (gNB) of full duplex operation determines that any UL transmission can only occur in slots #2, #3 and #5 when scheduled. The gNB configures xdd-config with 'Rx only' - 'simultaneous Tx-Rx' - 'simultaneous Tx-Rx', 'Rx only', 'Tx only' for UL-DL frame configuration. When the new txType field in the DCI indicates 'simultaneous Tx-Rx', the UE determines that UL transmission of PUCCH in PUCCH repetition can occur in full-duplex time slots #2 and #3. When the new txType field indicates 'Tx only', the UE determines that UL transmission of PUCCH can only occur in normal UL time slots (e.g., time slot #5). Note that the use of Figure 7 The UE determination of the UL transmission for the provided example full-duplex time slots #2 and #3 may include additional transmit or receive parameters provided by the xdd-config, such as the frequency domain behavior of the transmission in the full-duplex time slots, e.g., the start, size and / or end of the SBFD UL subband in the time slot or symbol.

[0235] consider Figure 7Example of a single carrier full-duplex configuration shown in . The gNB configures SIB1 tdd-UL-DL-ConfigurationCommon to DFFSU. A legacy UE or a UE that does not support features for enhanced support of (gNB) full-duplex operation determines that any UL transmission can occur in slots #2, #3, and #5 when scheduled. The gNB configures a txType field of length 1 in the DCI. A value of 0 indicates the default behavior, e.g., PUCCH transmissions using only PUCCH repetitions of ‘U’ slots. A value of 1 indicates PUCCH transmissions using only PUCCH repetitions of ‘F’ slots (e.g., full-duplex slots). When the new txType field in the DCI indicates ‘UL only’, e.g., a value of 0, the UE determines that UL transmissions of the PUCCH in the PUCCH repetitions can occur in a normal UL slot (e.g., slot #5), subject to the corresponding configuration or indication of the dl-DataToUL-ACK or PDSCH to HARQ Feedback Timing Indicator field of the DCI. When the new txType field indicates 'F Only', the UE determines that PUCCH transmission of PUCCH repetition can only occur in time slots #2 and #3, i.e., full-duplex time slots subject to the corresponding configuration or indication of the dl-DataToUL-ACK or PDSCH to HARQ Feedback Timing Indicator field of the DCI. Figure 7 The UE determination of the UL transmission for the provided example full-duplex time slots #2 and #3 may include additional transmit or receive parameters provided by the xdd-config, such as the frequency domain behavior of the transmission in the full-duplex time slots, e.g., the start, size and / or end of the SBFD UL subband in the time slot or symbol.

[0236] When the UE is provided with separate PUCCH configurations associated with different slot or symbol types (i.e., SBFD and non-SBFD slots / symbols or 'D' and 'F' and 'U' respectively) to indicate UE-specific PUCCH parameters or cell-specific PUCCH parameters in a BWP or in a carrier of a cell carrier group, the UE selects and determines the PUCCH configuration from the PUCCH configurations based on the slot or symbol type to determine the UL transmission parameters.

[0237] For example, separate PUCCH configurations, separate PUCCH format configurations, or separate PUCCH resources or PUCCH resource sets for SBFD and non-SBFD time slots / symbols, respectively, may be provided or indicated to the UE. Separate values ​​of the same parameter in a PUCCH configuration, a PUCCH resource or resource set, or a PUCCH format may be provided to the UE as information, wherein a first value of the parameter is indicated for use by the UE in a non-SBFD time slot / symbol, and then a second value of the parameter is indicated for use by the UE in a SBFD time slot / symbol.

[0238] After the UE determines potential available time slots or symbols for PUCCH transmission in a PUCCH transmission using the DCI, the UE determines available time slots for PUCCH transmission in a PUCCH repetition.

[0239] Then, the PUCCH transmission procedure for the UE to determine the available time slots for PUCCH transmission in the PUCCH repetition may follow other example procedures described herein.

[0240] When common or UE-specific RRC signaling, or a list or sequence of PUCCH resource allocations in the time domain, or a DCI-based indication is used to control the UE time domain transmission behavior of PUCCH transmissions in PUCCH repetition, the UE is configured or provided with an indication of a set of allowed time slots or a set of not allowed time slots where PUCCH repetition may or may not occur. The UE may, for example, support multiple concurrent PUCCH repetition processes in non-overlapping time domain resources.

[0241] In one embodiment, the UE provides a capability indication, for example using RRC signaling, thereby providing the network with an indication of support for multiple concurrent PUCCH repetition processes and / or the number of concurrent PUCCH repetition processes supported. When concurrent PUCCH repetition processes for the same UE are supported, the UE receives a signaling indication from the gNB using common or UE-specific RRC signaling if multiple concurrent PUCCH repetition processes are enabled or disabled. The capability indication provided by the UE to the gNB may indicate whether the UE supports separate PUCCH configurations for PUCCH transmissions using SBFD slots / symbols or non-SBFD slots / symbols, respectively. The UE capability indication provided to the gNB may include a maximum or minimum number or range of separate PUCCH configurations supported by the UE and associated with SBFD and non-SBFD slots / symbols, respectively. The UE may indicate to the gNB the supported settings, or the maximum or minimum number or range of separate PUCCH format configurations, or support for separate PUCCH resources or sets of PUCCH resources in SBFD and non-SBFD slots / symbols, respectively. The UE may indicate to the gNB when the UE supports separate values ​​for the same parameter in a PUCCH configuration, in a PUCCH resource or resource set, or in a PUCCH format.

[0242] For example, the UE may indicate to the gNB individual UE capabilities associated with UE support for individual value settings of the same parameter in a PUCCH configuration, in a PUCCH resource or resource set, or in a PUCCH format, wherein the UE indicates a first value supported by the parameter for a non-SBFD slot / symbol and the UE indicates a second value supported by the parameter for a SBFD slot / symbol. For example, the parameter may correspond to support for the number of PUCCH resources, or supported PUCCH formats, supported values ​​or ranges of DL data to UL acknowledgement (ACK) timing or delay, supported number of repetitions, support of DMRS bundling, supported mapping modes such as cyclic or sequential mapping of PUCCH repetitions associated with a spatial configuration or power control set, supported frequency hopping (FH) configurations such as a value or range of FH start PRB or a second hop or number of hops or hop width, supported maximum code rate or number of PRBs for a PUCCH format, or support for simultaneous HARQ acknowledgements and CSI for PUCCH transmissions in SBFD slots / symbols or non-SBFD slots / symbols, respectively.

[0243] The UE may be configured for a first PUCCH repetition using only normal UL timeslots (but not full-duplex timeslots), and a second PUCCH repetition using only full-duplex timeslots (but not normal UL timeslots). The first PUCCH repetition may be configured with a different or the same number of repetitions as the second PUCCH repetition. The first PUCCH repetition using symbols or timeslots that are not allocated for symbol or timeslot allocation in the second PUCCH repetition occurs simultaneously, for example in TDM. The first motivation is to increase the DL data rate due to the reduced delay in sending Ack / Nack corresponding to the DL TB in the PUCCH. It is not desirable to send PUCCH repetitions across both full-duplex and normal UL timeslots because the SBFD UL subband in the center splits the UL scheduling BW in the normal UL timeslot and greatly reduces the UL SE and peak rate in the normal UL timeslot. When the PUCCH repetition is configured to use only full-duplex timeslots, assuming DDDSU, the UE cannot use 20% of the (time domain) UL transmission resources for PUCCH repetitions. Using multiple concurrent PUCCH repetition processes allows using only full duplex time slots for the first PUCCH repetition process and then using only the second PUCCH repetition process in the UL time slot. The first and second PUCCH repetition processes can then use different frequency domain allocations, e.g., the first PUCCH repetition process in a full duplex time slot in a SBFD UL subband does not prevent the second PUCCH repetition process in a normal UL time slot from being configured at the band edge. Segmentation of the UL scheduling BW can be avoided and the PUCCH repetition has access to all time domain resources for use.

[0244] For example, the UE uses a (UL)UECapabilityInformation message to signal its support for concurrent PUCCH repetition procedures in non-overlapping time domain resources and / or the number of concurrent PUCCH repetition procedures supported. When the UE supports the concurrent PUCCH repetition procedure, the UE determines whether to enable the concurrent PUCCH repetition procedure and / or determines the maximum number of concurrent PUCCH repetition procedures based on the PUCCH configuration (e.g., using an IE such as pucch-Config or ServingCellConfig). The UE does not expect to be scheduled for a PUCCH transmission of a first PUCCH repetition in a symbol or time slot in which a PUCCH transmission of a second PUCCH repetition is configured.

[0245] As can be seen by those skilled in the art, the solutions and examples described for the case where the allowed time domain resource set or the disallowed time domain resource set for PUCCH repetition is configured based on tdd-UL-DL-ConfigurationCommon and xdd-config (e.g., determination of symbol or time slot type 'D', 'F', 'U') using common UE-specific RRC signaling, a list or sequence of PUCCH resource allocations in the time domain, or DCI-based indications are easily extended to the case where tdd-UL-DL-ConfigurationDedicated and / or SFI are provided to the UE. The UE determines the time slot and symbol type as described in REF3. For example, tdd-UL-DL-ConfigurationDedicated (if provided) only allows symbols or time slots of type 'F' to be allocated in mode 1 / mode 2 of tdd-UL-DL-ConfigurationCommon. The UE can determine the time slot and symbol type in various ways, but a single value 'D', 'F', 'U' is determined for any given time slot or symbol. Similarly, the configuration of slot or symbol types provided by xdd-config uses slots or symbols of type 'Tx only', 'Rx only', 'simultaneous Tx-Rx' for illustration purposes and to simplify the exemplary description. Other suitable symbol or slot designations may be used for the same purposes as described without loss of functionality.

[0246] The above flow charts illustrate example methods that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods shown in the flow charts herein. For example, although shown as a series of steps, the various steps in each figure can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, a step can be omitted or replaced by another step.

[0247] Fig.13 A block diagram of a terminal (or user equipment (UE)) according to an embodiment of the present disclosure is shown.

[0248] like Fig.13 As shown, the terminal according to the embodiment may include a transceiver 1310, a memory 1320 and a processor (or controller) 1130. The transceiver 1310, the memory 1320 and the processor (or controller) 1130 of the terminal may operate according to the communication method of the above-mentioned terminal. However, the components of the terminal are not limited thereto. For example, the terminal may include Fig.13 130. In addition, the processor (or controller) 1130, the transceiver 1310, and the memory 1320 may be implemented as a single chip. In addition, the processor (or controller) 1130 may include at least one processor.

[0249] The transceiver 1310 is collectively referred to as a terminal station receiver and a terminal transmitter, and can send a signal to a base station or another terminal / receive a signal from a base station or another terminal. The signal sent to the terminal or received from the terminal may include control information and data. The transceiver 1310 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for amplifying the frequency of the low noise and down-converting the received signal. However, this is only an example of the transceiver 1310, and the components of the transceiver 1310 are not limited to the RF transmitter and the RF receiver.

[0250] In addition, the transceiver 1310 may receive a signal through a wireless channel and output the signal to the processor (or controller) 1130 , and transmit a signal output from the processor (or controller) 1130 through a wireless channel.

[0251] The memory 1320 may store programs and data required for the operation of the terminal. In addition, the memory 1320 may store control information or data included in a signal obtained by the terminal. The memory 1320 may be a storage medium such as a read-only memory (ROM), a random access memory (RAM), a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

[0252] The processor (or controller) 1130 may control a series of processes so that the terminal operates as described above. For example, the processor (or controller) 1130 may receive a data signal and / or a control signal, and the processor (or controller) 1130 may determine a result of receiving a signal sent by a base station and / or another terminal.

[0253] Fig.14 A block diagram of a base station according to an embodiment of the present disclosure is shown. Fig.14 The base station may refer to the above-mentioned transmission and reception point (TRP).

[0254] like Fig.14As shown, the base station of the present disclosure may include a transceiver 1410, a memory 1420, and a processor (or controller) 1430. The transceiver base station 1410, the memory 1420, and the processor (or controller) 1430 may operate according to the communication method of the above-mentioned base station. However, the components of the base station are not limited thereto. For example, the base station may include Fig.14 14. In addition, the processor (or controller) 1430, the transceiver 1410, and the memory 1420 may be implemented as a single chip. In addition, the processor (or controller) 1430 may include at least one processor.

[0255] The transceiver 1410 is collectively referred to as a base station receiver and a base station transmitter, and can send / receive signals to / from a terminal, another base station, and / or a core network function (or entity). The signal sent to or received from the base station may include control information and data. The transceiver 1410 may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for amplifying the frequency of the low noise and down-converting the received signal. However, this is only an example of the transceiver 1410, and the components of the transceiver 1410 are not limited to the RF transmitter and the RF receiver.

[0256] In addition, the transceiver 1410 may receive a signal through a wireless channel and output the signal to the processor (or controller) 1430 , and transmit a signal output from the processor (or controller) 1430 through a wireless channel.

[0257] The memory 1420 may store programs and data required for the operation of the base station. In addition, the memory 1420 may store control information or data included in a signal obtained by the base station. The memory 1420 may be a storage medium such as a ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media.

[0258] The processor (or controller) 1430 may control a series of processes so that the base station operates as described above. For example, the processor (or controller) 1430 may receive a data signal and / or a control signal, and the processor (or controller) 1430 may determine the result of receiving a signal sent by a terminal and / or a core network function.

[0259] The methods according to the embodiments described in the claims or detailed description of the present disclosure may be implemented in hardware, software, or a combination of hardware and software.

[0260] When the electrical structure and method are implemented in software, a computer-readable recording medium having one or more programs (software modules) recorded thereon may be provided. The one or more programs recorded on the computer-readable recording medium are configured to be executable by one or more processors in an electronic device. The one or more programs include instructions for executing the methods of the embodiments described in the claims or the detailed description of the present disclosure.

[0261] Those skilled in the art will appreciate that the above illustrative embodiments are described herein and are not intended to be limiting. It should be understood that any two or more embodiments disclosed herein may be combined in any combination. In addition, other embodiments may be utilized and other changes may be made without departing from the spirit and scope of the subject matter presented herein. It is readily understood that the various aspects of the invention of the present disclosure as generally described herein and shown in the accompanying drawings may be arranged, replaced, combined, separated and designed in a variety of different configurations, all of which are considered herein.

[0262] It will be appreciated by those skilled in the art that the various illustrative logic blocks, modules, circuits, and steps described in this application may be implemented as hardware, software, or a combination of the two. In order to clearly illustrate this interchangeability between hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in the form of their function sets. Whether these function sets are implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. The technician can implement the described function set in different ways for each specific application, but this design decision should not be interpreted as causing a departure from the scope of this application.

[0263] The various illustrative logical blocks, modules, and circuits described in this application may be implemented or performed by a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in cooperation with a DSP core, or any other such configuration.

[0264] The steps of the method or algorithm described in this application can be directly embodied in hardware, in a software module executed by a processor, or in a combination thereof. The software module can reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium can be integrated into the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In an alternative, the processor and the storage medium can reside in a user terminal as discrete components.

[0265] In one or more exemplary designs, the functions may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, each function may be stored on or delivered by a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, the latter including any media that facilitates the sending of a computer program from one place to another. Storage media may be any available media that can be accessed by a general or special purpose computer.

[0266] The above description is merely an exemplary embodiment of the present invention and is not intended to limit the scope of protection of the present invention, which is determined by the appended claims.

[0267] Although the drawings show different examples of user equipment, various changes may be made to the drawings. For example, the user equipment may include any number of each component in any suitable arrangement. Generally, the drawings do not limit the scope of the present disclosure to any particular configuration. In addition, although the drawings show operating environments in which various user equipment features disclosed in this patent document may be used, these features may be used in any other suitable system.

[0268] Although the present disclosure has been described using exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. The present disclosure is intended to cover these changes and modifications that fall within the scope of the appended claims. The description in this application should not be interpreted as implying that any particular element, step or function is an essential element that must be included in the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A method performed by a user equipment (UE) in a full-duplex system, the method include: take over: first information for a first set of parameters for a physical uplink control channel (PUCCH) associated with a first subset of time slots from a set of time slots on a cell, and second information for a second set of parameters for the PUCCH associated with a second subset of time slots from the set of time slots on the cell; determining a PUCCH parameter set from the first set of parameters and the second set of parameters based on whether the time slot is from the first subset of time slots or from the second subset of time slots; as well as The PUCCH is sent in the timeslot on the cell based on the PUCCH parameter set, wherein: time slots from the first subset of time slots do not include time domain resources indicated for simultaneous transmission and reception on the cell, and Timeslots from the second subset of timeslots include time domain resources indicated for simultaneous transmission and reception on the cell.

2. The method according to claim 1, further comprising: include: A physical downlink shared channel (PDCCH) is received that provides a downlink control information (DCI) format, wherein the DCI format includes a field indicating one of: the first subset of time slots, or the first subset of time slots and the second subset of time slots; determining a number of repetitions of the PUCCH transmission; and Based on the indication of the field, the PUCCH of the repetition number is transmitted in a time slot of one of the following items: the first subset of time slots, or The first subset of time slots and the second subset of time slots.

3. The method according to claim 1, further comprising: include: Receiving a physical downlink shared channel (PDCCH) providing a downlink control information (DCI) format, wherein: The PDCCH is received in a first time slot from the set of time slots, and The DCI format includes fields; and The number of time slots is determined based on a mapping of the value of the field to the number of time slots, wherein: When the first time slot is from the first subset of time slots, the mapping is indicated based on the first set of parameters, When the first time slot is from the second subset of time slots, the mapping is indicated based on the second set of parameters, and The time slot follows the first time slot by the number of time slots.

4. The method according to claim 1, further comprising: include: Determining a number of repetitions of the PUCCH transmission; as well as sending a first repetition of the PUCCH in a first time slot from the first subset of time slots using a first PUCCH resource, and and sending a second repetition of the PUCCH in a second time slot from the second subset of time slots using a second PUCCH resource, wherein: The first parameter set indicates a first PUCCH resource set, The second parameter set indicates a second PUCCH resource set, The first PUCCH resource is from the first PUCCH resource set, The second PUCCH resource is from the second PUCCH resource set, and The first PUCCH resource and the second PUCCH resource have the same index.

5. A user equipment (UE) in a full-duplex system, the UE include: A transceiver configured to receive: first information for a first set of parameters for a physical uplink control channel (PUCCH) associated with a first subset of time slots from a set of time slots on a cell, and second information for a second set of parameters for the PUCCH associated with a second subset of time slots from the set of time slots on the cell; as well as a processor operably coupled to the transceiver, the processor configured to determine a set of PUCCH parameters from the first set of parameters and the second set of parameters based on whether a time slot is from the first subset of time slots or from the second subset of time slots, The transceiver is further configured to send the PUCCH in the time slot on the cell based on the PUCCH parameter set, wherein time slots from the first subset of time slots do not include time domain resources indicated for simultaneous transmission and reception on the cell, and The time slots from the second subset of time slots include time domain resources indicated for simultaneous transmission and reception on the cell.

6. The UE according to claim 5, in: The transceiver is further configured to receive a physical downlink shared channel (PDCCH) providing a downlink control information (DCI) format, wherein the DCI format includes a field indicating one of: the first subset of time slots, or the first subset of time slots and the second subset of time slots; The processor is further configured to determine a number of repetitions for a PUCCH transmission; and The transceiver is further configured to transmit the PUCCH of the repetition number in a time slot of one of the following based on the indication of the field: the first subset of time slots, or The first subset of time slots and the second subset of time slots.

7. The UE according to claim 5, in: The transceiver is further configured to receive a physical downlink shared channel (PDCCH) providing a downlink control information (DCI) format, The PDCCH is received in a first time slot from the set of time slots, The DCI format includes fields, The processor is further configured to determine the number of time slots based on a mapping of the value of the field to the number of time slots, When the first time slot is from the first subset of time slots, the mapping is indicated based on the first set of parameters, When the first time slot is from the second subset of time slots, the mapping is indicated based on the second set of parameters, and The time slot follows the first time slot by the number of time slots.

8. The UE according to claim 5, in: The processor is further configured to determine a number of repetitions of the PUCCH transmission, The transceiver is further configured to: sending a first repetition of the PUCCH in a first time slot from the first subset of time slots using a first PUCCH resource, and sending a second repetition of the PUCCH in a second time slot from the second subset of time slots using a second PUCCH resource, The first parameter set indicates a first PUCCH resource set, The second parameter set indicates a second PUCCH resource set, The first PUCCH resource is from the first PUCCH resource set, The second PUCCH resource is from the second PUCCH resource set, and The first PUCCH resource and the second PUCCH resource have the same index.

9. A base station (BS) in a full-duplex system, the BS include: The transceiver is configured to send: first information for a first set of parameters for a physical uplink control channel (PUCCH) associated with a first subset of time slots from a set of time slots on a cell, and second information for a second set of parameters for the PUCCH associated with a second subset of time slots from the set of time slots on the cell; as well as a processor operably coupled to the transceiver, the processor configured to determine a set of PUCCH parameters from the first set of parameters and the second set of parameters based on whether a time slot is from the first subset of time slots or from the second subset of time slots, The transceiver is further configured to receive the PUCCH in the time slot on the cell based on the PUCCH parameter set, wherein time slots from the first subset of time slots do not include time domain resources indicated for simultaneous transmission and reception on the cell, and The time slots from the second subset of time slots include time domain resources indicated for simultaneous transmission and reception on the cell.

10. The BS according to claim 9, in: The transceiver is further configured to transmit a physical downlink shared channel (PDCCH) providing a downlink control information (DCI) format, wherein the DCI format includes a field indicating one of: the first subset of time slots, or the first subset of time slots and the second subset of time slots; and The transceiver is further configured to receive the repeated number of PUCCHs in a time slot of one of the following: the first subset of time slots, or The first subset of time slots and the second subset of time slots.

11. The BS according to claim 9, in: The transceiver is further configured to transmit a physical downlink shared channel (PDCCH) providing a downlink control information (DCI) format, The PDCCH is sent in a first time slot from the set of time slots, The DCI format includes fields, The processor is further configured to determine the number of time slots based on a mapping of the value of the field to the number of time slots, When the first time slot is from the first subset of time slots, the mapping is indicated based on the first set of parameters, When the first time slot is from the second subset of time slots, the mapping is indicated based on the second set of parameters, and The time slot follows the first time slot by the number of time slots.

12. The BS according to claim 9, in: The transceiver is further configured to: receiving a first repetition of the PUCCH in a first slot from a first subset of slots on a first PUCCH resource, and receiving a second repetition of the PUCCH in a second slot from the second subset of slots on a second PUCCH resource, The first parameter set indicates a first PUCCH resource set, The second parameter set indicates a second PUCCH resource set, The first PUCCH resource is from the first PUCCH resource set, The second PUCCH resource is from the second PUCCH resource set, and The first PUCCH resource and the second PUCCH resource have the same index.

13. A method performed by a base station (BS) in a full-duplex system, the method include: send: first information for a first set of parameters for a physical uplink control channel (PUCCH) associated with a first subset of time slots from a set of time slots on a cell, and second information for a second set of parameters for the PUCCH associated with a second subset of time slots from the set of time slots on the cell; determining a PUCCH parameter set from the first set of parameters and the second set of parameters based on whether the time slot is from the first subset of time slots or from the second subset of time slots; as well as The PUCCH is received in the timeslot on the cell based on the PUCCH parameter set, wherein: time slots from the first subset of time slots do not include time domain resources indicated for simultaneous transmission and reception on the cell, and The time slots from the second subset of time slots include time domain resources indicated for simultaneous transmission and reception on the cell.

14. The method according to claim 13, further comprising: include: A physical downlink shared channel (PDCCH) is transmitted that provides a downlink control information (DCI) format, wherein the DCI format includes a field indicating one of: the first subset of time slots, or the first subset of time slots and the second subset of time slots; determining a number of repetitions of the PUCCH transmission; and Based on the indication of the field, receiving the PUCCH of the repetition number in a time slot of one of the following: the first subset of time slots, or The first subset of time slots and the second subset of time slots.

15. The method according to claim 13, further comprising: include: A physical downlink shared channel (PDCCH) is sent that provides a downlink control information (DCI) format, where: The PDCCH is received in a first time slot from the set of time slots, and The DCI format includes fields; and The number of time slots is determined based on a mapping of the value of the field to the number of time slots, wherein: When the first time slot is from the first subset of time slots, the mapping is indicated based on the first set of parameters, When the first time slot is from the second subset of time slots, the mapping is indicated based on the second set of parameters, and The time slot follows the first time slot by the number of time slots.

Citation Information

Cited By

  • Communication method, device, medium, program product, chip and system

    CN120264438A

  • Device, method and computer readable medium for communications

    WO2026213784A1