Mapping uplink control information

Abstract

In one embodiment, a method is disclosed, the method comprising: receiving an indication indicating to map uplink control information on a physical uplink shared channel (PUSCH) at one or more slots, where the one or more slots are configured for subband full duplex (SBFD) operation; determining a number of resource blocks within a predefined distance in the frequency domain from one or more downlink subbands or one or more guard bands in the allocated resource blocks of the PUSCH; determining, based on the number of resource blocks, at least one frequency resource range to which at least one subset of uplink control information should not be mapped; mapping the at least one subset of uplink control information on the PUSCH such that the at least one subset of uplink control information is not mapped into the at least one frequency resource range; and transmitting the PUSCH.

Description

Technical Field

[0001] The following example embodiments relate to wireless communication. Background Technology

[0002] Cross-link interference refers to unwanted interference between two independent communication links in a wireless communication system. This interference can occur when a signal from one link (intended for a specific receiver) interferes with another link, leading to a degradation in communication quality or performance. Protecting these links against cross-link interference is essential. Summary of the Invention

[0003] The scope of protection claimed by the various exemplary embodiments is set forth in the independent claims. The exemplary embodiments and features described herein, where not falling within the scope of the independent claims (if any), should be construed as examples for understanding the various embodiments.

[0004] According to one aspect, an apparatus is provided, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least: receive an instruction to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; determine, based on at least one default number of resource blocks or at least one scaling factor, the number of resource blocks in the allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; determine, based on the number of resource blocks, at least one frequency resource range to which at least one subset of the uplink control information should not be mapped; map at least one subset of the uplink control information onto the physical uplink shared channel such that at least one subset of the uplink control information is not mapped to at least one frequency resource range; and transmit the physical uplink shared channel at one or more time slots according to the mapping.

[0005] According to another aspect, an apparatus is provided, comprising: means for receiving an instruction to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for subband full-duplex SBFD operation; means for determining, based on at least one default number of resource blocks or at least one scaling factor, the number of allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink subbands or one or more guard bands; means for determining, based on the number of resource blocks, at least one subset of the uplink control information should not be mapped to the at least one frequency resource range; means for mapping at least one subset of the uplink control information onto the physical uplink shared channel such that at least one subset of the uplink control information is not mapped to the at least one frequency resource range; and means for transmitting the physical uplink shared channel at the one or more time slots according to the mapping.

[0006] According to another aspect, a method is provided, comprising: receiving an indication to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; determining, based on at least one default number of resource blocks or at least one scaling factor, the number of resource blocks in the allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; determining, based on the number of resource blocks, at least one frequency resource range to which at least one subset of the uplink control information should not be mapped; mapping at least one subset of the uplink control information onto the physical uplink shared channel such that at least one subset of the uplink control information is not mapped to at least one frequency resource range; and transmitting the physical uplink shared channel at the one or more time slots according to the mapping.

[0007] According to another aspect, a computer program is provided, comprising instructions that, when executed by a device, cause the device to perform at least the following: receiving an instruction to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; determining, based on at least one default number of resource blocks or at least one scaling factor, the number of resource blocks in the allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; determining, based on the number of resource blocks, at least one frequency resource range to which at least one subset of the uplink control information should not be mapped; mapping at least one subset of the uplink control information onto the physical uplink shared channel such that at least one subset of the uplink control information is not mapped to at least one frequency resource range; and transmitting the physical uplink shared channel at one or more time slots according to the mapping.

[0008] According to another aspect, a computer-readable medium is provided, comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: receiving an instruction to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex (SBFD) operation; determining, based on at least one default number of resource blocks or at least one scaling factor, the number of resource blocks in the allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; determining, based on the number of resource blocks, at least one frequency resource range to which at least one subset of the uplink control information should not be mapped; mapping at least one subset of the uplink control information onto the physical uplink shared channel such that at least one subset of the uplink control information is not mapped to at least one frequency resource range; and transmitting the physical uplink shared channel at one or more time slots according to the mapping.

[0009] According to another aspect, a non-transitory computer-readable medium is provided, comprising program instructions that, when executed by a device, cause the device to perform at least the following: receiving an instruction to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; determining, based on at least one default number of resource blocks or at least one scaling factor, the number of resource blocks in the allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; determining, based on the number of resource blocks, at least one frequency resource range to which at least one subset of the uplink control information should not be mapped; mapping at least one subset of the uplink control information onto the physical uplink shared channel such that at least one subset of the uplink control information is not mapped to at least one frequency resource range; and transmitting the physical uplink shared channel at one or more time slots according to the mapping.

[0010] According to another aspect, an apparatus is provided, comprising at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: transmit to a user equipment an instruction to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; transmit to the user equipment an instruction indicating at least one default number of resource blocks or at least one scaling factor, the at least one default number of resource blocks or at least one scaling factor being used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; and receive from the user equipment a physical uplink shared channel, wherein at least one subset of the uplink control information is mapped onto the physical uplink shared channel, wherein at least one subset of the uplink control information is not mapped into the number of resource blocks.

[0011] According to another aspect, an apparatus is provided, comprising: means for transmitting to a user equipment an indication of mapping uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; means for transmitting to the user equipment an indication of at least one default number of resource blocks or at least one scaling factor, the at least one default number or at least one scaling factor being used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; and means for receiving the physical uplink shared channel from the user equipment, wherein at least one subset of the uplink control information is mapped onto the physical uplink shared channel, wherein at least one subset of the uplink control information is not mapped into the number of resource blocks.

[0012] According to another aspect, a method is provided, comprising: transmitting to a user equipment an indication to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; transmitting to the user equipment an indication of at least one default number of resource blocks or at least one scaling factor, the at least one default number or at least one scaling factor being used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; and receiving from the user equipment the physical uplink shared channel, wherein at least one subset of the uplink control information is mapped onto the physical uplink shared channel, wherein at least one subset of the uplink control information is not mapped into the number of resource blocks.

[0013] According to another aspect, a computer program is provided, comprising instructions that, when executed by a device, cause the device to perform at least the following: transmitting to a user equipment an instruction to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; transmitting to the user equipment an instruction to at least a default number of resource blocks or at least a scaling factor, the at least default number or at least a scaling factor being used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; and receiving from the user equipment a physical uplink shared channel, wherein at least a subset of the uplink control information is mapped onto the physical uplink shared channel, wherein at least a subset of the uplink control information is not mapped into the number of resource blocks.

[0014] According to another aspect, a computer-readable medium is provided, comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: transmitting to a user equipment an instruction to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; transmitting to the user equipment an instruction to at least a default number of resource blocks or at least a scaling factor, the at least a default number or at least a scaling factor being used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; and receiving from the user equipment a physical uplink shared channel, wherein at least a subset of the uplink control information is mapped onto the physical uplink shared channel, wherein at least a subset of the uplink control information is not mapped into the number of resource blocks.

[0015] According to another aspect, a non-transitory computer-readable medium is provided, comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least the following: transmitting to a user equipment an instruction to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; transmitting to the user equipment an instruction to at least one default number of resource blocks or at least one scaling factor, the at least one default number or at least one scaling factor being used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; and receiving from the user equipment a physical uplink shared channel, wherein at least one subset of the uplink control information is mapped onto the physical uplink shared channel, wherein at least one subset of the uplink control information is not mapped into the number of resource blocks.

[0016] List of Attachments In the following description, various exemplary embodiments will be described in more detail with reference to the accompanying drawings, wherein Figure 1 An example of a wireless communication network is shown; Figure 2 An example of physical uplink shared channel repetition type A is shown; Figure 3 An example of physical uplink shared channel repetition type A is shown; Figure 4 An example of power spectral density gain provided by transmission block processing over multiple time slots is shown; Figure 5A An example of consecutive time slot allocation for transport block processing over multiple time slots is shown; Figure 5B An example of non-contiguous timeslot allocation for transport block processing over multiple timeslots is shown; Figure 6 An example of repetition in transport block processing across multiple time slots is shown; Figure 7A An example of mapping hybrid automatic repeat request acknowledgment information on a physical uplink shared channel is shown; Figure 7B An example of mapping channel state information on a physical uplink shared channel is shown; Figure 7C An example of mapping uplink data over a physical uplink shared channel is shown; Figure 8 An example of using sub-band full-duplex frequency-time resource partitioning compared to frequency division duplex and time division duplex is shown; Figure 9 Examples of subband full-duplex time slots and non-subband full-duplex time slots are shown; Figure 10A An example of co-channel interference type is shown; Figure 10B An example of co-channel interference type is shown; Figure 11 The signal flow graph is shown; Figure 12 A flowchart is shown; Figure 13 A flowchart is shown; Figure 14 An example is shown for determining at least one frequency resource range, where uplink control information should not be mapped; Figure 15 An example of setting different sets of resource blocks in an uplink subband is shown; Figure 16 An example of the device is shown; and Figure 17 An example of the device is shown. Detailed Implementation

[0017] The following embodiments are exemplary. Although this specification may refer to "an," "a," or "some" embodiments in various places throughout the text, this does not necessarily mean that each reference refers to the same embodiment or that a particular feature applies only to a single embodiment. Individual features of different embodiments may also be combined with each other to provide other embodiments.

[0018] Some example embodiments described herein can be implemented in a wireless communication network including a radio access network based on one or more of the following radio access technologies: Global System for Mobile Communications (GSM) or any other second-generation radio access technology, Universal Mobile Telecommunications System (UMTS, 3G) based on Basic Wideband Code Division Multiple Access (W-CDMA), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), LTE-Advanced, Fourth Generation (4G), Fifth Generation (5G), 5G New Radio (NR), 5G-Advanced (i.e., 3GPP NR Release 18 and later), or Sixth Generation (6G). Some examples of radio access networks include Universal Mobile Telecommunications System (UMTS) Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRA), or Next Generation Radio Access Network (NG-RAN). The wireless communication network may also include a core network, and some example embodiments can also be applied to the network functions of this core network.

[0019] It should be noted that these embodiments are not limited to the wireless communication networks given as examples, and those skilled in the art can apply the scheme to other wireless communication networks or systems with the necessary characteristics. For example, some example embodiments can also be applied to communication systems based on the IEEE 802.11 standard or communication systems based on the IEEE 802.15 standard.

[0020] Figure 1 An example of a simplified wireless communication network is depicted, showing some physical and logical entities. Figure 1 The connection shown can be a physical connection or a logical connection. It will be apparent to those skilled in the art that the wireless communication network may also include, in addition to... Figure 1 Other physical and logical entities besides those shown.

[0021] However, the exemplary embodiments described herein are not limited to the wireless communication networks given as examples, but those skilled in the art can apply the embodiments described herein to other wireless communication networks with the necessary properties.

[0022] Figure 1 The example wireless communication network shown includes an access network, such as a radio access network (RAN), and a core network 110.

[0023] Figure 1User equipment (UE) 100 and 102 are illustrated, configured to have a radio connection with an access node (AN) 104 of an access network on one or more communication channels in a radio cell. The AN 104 may be an evolved Node B (eNB or eNodeB) or a next-generation Node B (gNB or gNodeB) providing the radio cell. A radio connection from the UE to the access node 104 (e.g., a radio link) may be referred to as an uplink (UL) or a reverse link, and a radio connection from the access node to the UE (e.g., a radio link) may be referred to as a downlink (DL) or a forward link. UE 100 may also communicate directly with UE 102 via a radio connection commonly referred to as a side link (SL), and vice versa. It should be understood that the access node 104, or its functionality, can be implemented using any entity suitable for providing such functionality, such as a node, host, server, or access point.

[0024] The access network may include more than one access node, which may be configured to communicate with each other via wired or wireless links. These links between access nodes may be used to send and receive control plane signaling and to route data from one access node to another.

[0025] The access node may include a computing device configured to control the radio resources of the access node. The access node may also be referred to as a base station, base transceiver station (BTS), access point, cell site, radio access node, or any other type of node capable of having a wireless connection with a UE (e.g., UE 100, 102). The access node may include a transceiver, or be coupled to a transceiver. From the transceiver of the access node, a connection can be provided to an antenna element that establishes a bidirectional radio link with UE 100, 102. The antenna element may include an antenna or antenna element, or multiple antennas or multiple antenna elements.

[0026] The access node 104 can also connect to the core network (CN) 110. The core network 110 may include an evolved packet core (EPC) and / or a fifth-generation core network (5GC). The EPC may include network entities such as a serving gateway (S-GW) for routing and forwarding data packets, a packet data network gateway (P-GW) for providing UE connectivity to external packet data networks, and a mobility management entity (MME). The 5GC may include network functions such as user plane functions (UPF), access and mobility management functions (AMF), and location management functions (LMF).

[0027] The core network 110 can also communicate with one or more external networks 113, such as the public switched telephone network or the Internet, or utilize the services they provide. For example, in a 5G wireless communication network, the UPF of the core network 110 can be configured to communicate with an external data network via the N6 interface. In an LTE wireless communication network, the P-GW of the core network 110 can be configured to communicate with an external data network.

[0028] The UEs 100 and 102 shown are a type of device that can allocate and assign resources on the air interface. UEs 100 and 102 may also be referred to as wireless communication devices, user units, mobile stations, remote terminals, access terminals, user terminals, terminal equipment, or user equipment (to name only). The UE may be a computing device with or without a Subscriber Identity Module (SIM), including but not limited to the following types of computing devices: mobile phones, smartphones, personal digital assistants (PDAs), handheld devices, computing devices including wireless modems (e.g., alarm or measuring devices), laptops, desktop computers, tablets, game consoles, notebooks, multimedia devices, redcap devices, wearable devices with radio components (e.g., watches, headphones, or glasses), sensors including wireless modems, or any computing device including a wireless modem integrated into a vehicle.

[0029] It should be understood that a UE can also be an almost entirely uplink-only device, an example of which could be a camera or camcorder that loads images or video clips onto the network. A UE can also be a device capable of operating in an Internet of Things (IoT) network, a scenario where objects can be provided with the ability to transmit data over a network without human-to-human or human-to-computer interaction. The UE can also leverage the cloud. In some applications, computation can be performed in the cloud or within another UE.

[0030] This wireless communication network can also support the use of cloud services; for example, at least a portion of the core network operations can be performed as cloud services (this is in...). Figure 1 (referred to as "Cloud" 114 in Chinese). The wireless communication network may also include a central control entity or similar entity that supports cooperation between wireless communication networks of different operators, such as in spectrum sharing.

[0031] 5G enables the use of multiple-input multiple-output (MIMO) antennas in access nodes 104 and / or UEs 100, 102, and allows for more base stations or access nodes than LTE networks (the so-called cell concept), including macro sites operating in conjunction with smaller base stations, and employs a variety of radio technologies depending on service requirements, use cases, and / or available spectrum. 5G wireless communication networks can support a wide range of use cases and related applications, including video streaming, augmented reality, various forms of data sharing, and various forms of machine-type applications, such as (massive) machine-type communication (mMTC), including vehicle safety, various sensors, and real-time control.

[0032] In 5G wireless communication networks, access nodes and / or UEs can have multiple radio interfaces, namely sub-6GHz, centimeter wave (cmWave), and millimeter wave (mmWave), and can also integrate with existing legacy radio access technologies (such as LTE). Integration with LTE can, for example, be implemented as a system where macro coverage can be provided by LTE, and 5G radio interface access can be provided through small cells that aggregate LTE. In other words, 5G wireless communication networks can support inter-RAT (such as LTE-5G) and inter-RI (such as sub-6GHz–cmWave–mmWave radio interface inter-operability). One concept to consider in 5G wireless communication networks is network slicing, in which multiple independent and dedicated virtual subnetworks (network instances) can be created within essentially the same infrastructure to run services with different requirements for latency, reliability, throughput, and mobility.

[0033] In some example embodiments, an access node (e.g., access node 104) may include: a radio unit (RU) comprising a radio transceiver (TRX), i.e., a transmitter (Tx) and a receiver (Rx); one or more distributed units (DUs) 105, which may be used for so-called Layer 1 (L1) processing and real-time Layer 2 (L2) processing; and a central unit (CU) 108 (also called a centralized unit), which may be used for non-real-time Layer 2 and Layer 3 (L3) processing. The CU 108 may, for example, be connected to one or more DUs 105 via an F1 interface. Such embodiments of the access node enable the centralization of the CU relative to the cell site and the DU, while the DU can be more distributed, or even retained at the cell site. The CU and DU together may also be referred to as a baseband or baseband unit (BBU). The CU and DU may also be included in a radio band access point (RAP).

[0034] CU 108 can be a logical node carrying Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), and / or Packet Data Convergence Protocol (PDCP) in the NR protocol stack of the access node. DU 105 can be a logical node carrying Radio Link Control (RLC), Medium Access Control (MAC), and / or Physical Layer (PHY) in the NR protocol stack of the access node. The operation of the DU can be at least partially controlled by the CU. It should also be understood that the functional allocation between DU 105 and CU 108 can vary depending on the implementation. CU may include a control plane (CU-CP), which can be a logical node carrying the control plane portion of the RRC and PDCP protocols in the NR protocol stack of the access node. CU may also include a user plane (CU-UP), which can be a logical node carrying the user plane portion of the PDCP protocol and the SDAP protocol in the CU of the access node.

[0035] Cloud computing systems can also be used to provide CU 108 and / or DU 105. CUs provided by cloud computing systems can be referred to as virtualized CUs (vCUs). In addition to vCUs, virtualized DUs (vDUs) can also be provided by cloud computing systems. Furthermore, there can be a combination where DUs can be implemented on so-called bare-metal solutions, such as application-specific integrated circuits (ASICs) or customer-specific standard product (CSSP) system-on-chips (SoCs).

[0036] Edge cloud can be introduced into the access network (e.g., RAN) by leveraging Network Functions Virtualization (NFV) and Software-Defined Networking (SDN). Using an edge cloud allows access node operations to be performed, at least partially, in a computing system operationally coupled to the remote radio head (RRH) or radio unit (RU) of the access node. It is also possible to perform access node operations on a distributed computing system or cloud computing system located at the access node. The application of cloud RAN architecture enables real-time RAN functions to be performed within the access network (e.g., in DU 105), while non-real-time functions can be performed centrally (e.g., in CU 108).

[0037] It should also be understood that in future wireless communication networks, the functional allocation between core network operations and access node operations may differ from, or even not exist at all, compared to LTE or 5G. Other technological advancements that can be used include big data and all-IP, which can transform how wireless communication networks are built and managed. 5G (or New Radio, NR) wireless communication networks can support multi-layered architectures, where multi-access edge computing (MEC) servers can be positioned between the core network 110 and access nodes 104. It should be understood that MEC can also be applied to LTE wireless communication networks.

[0038] 5G wireless communication networks (“5G networks”) can also include non-terrestrial communication networks, such as satellite communication networks, to enhance or supplement the coverage of 5G radio access networks. For example, satellite communications can support data transmission between the 5G radio access network and the core network, thereby enabling broader network coverage. Possible use cases could include providing business continuity for machine-to-machine (M2M) or Internet of Things (IoT) devices or vehicular passengers, or ensuring the operational availability of critical communications and future rail / maritime / aviation communications. Satellite communications can utilize geostationary orbit (GEO) satellite systems or low Earth orbit (LEO) satellite systems, especially large constellations (i.e., systems deploying hundreds of (nano) satellites). A given satellite 106 in a large constellation can cover multiple satellite-enabled network entities that create terrestrial cells. These terrestrial cells can be created by terrestrial relay access nodes or by access nodes 104 located on the ground or in satellites.

[0039] It is obvious to those skilled in the art, Figure 1 The access node 104 shown is merely an example of a portion of an access network (e.g., a radio access network). In practice, this access network may include multiple access nodes, and UEs 100 and 102 may access multiple radio cells. Furthermore, the access network may include other devices, such as physical layer relay access nodes or other entities. At least one access node may be a home eNodeB or a home gNodeB. A home gNodeB or home eNodeB is a type of access node that can be used to provide indoor coverage in homes, offices, or other indoor environments.

[0040] Furthermore, within a geographic area of ​​an access network (such as a radio access network), various types of radio cells and multiple radio cells can be provided. A radio cell can be a macrocell (or umbrella cell), which can be a large cell with a diameter of tens of kilometers, or a smaller cell, such as a microcell, a femtocell, or a picocell. Figure 1 Multiple access nodes can provide any of these cells. A cellular radio network can be implemented as a multi-layered access network comprising various types of radio cells. In a multi-layered access network, one access node can provide one or more types of radio cells, thus requiring multiple access nodes to provide such a multi-layered access network.

[0041] To meet the demand for improved access network performance, the concept of "plug-and-play" access nodes can be introduced. Access networks capable of using "plug-and-play" access nodes, in addition to home eNodeBs or home gNodeBs, can also include home node B gateways (HNB-GW) (not listed in the original text). Figure 1(As shown in the diagram). The HNB-GW can be installed within an operator's access network and can aggregate services from a large number of home eNodeBs or home gNodeBs back to the operator's core network.

[0042] NR Release 15 (Rel-15) introduced a slot aggregation feature for Physical Uplink Shared Channels (PUSCH), also known as PUSCH Repetition Type A. In PUSCH Repetition Type A, the transmission of a Transport Block (TB) is repeated across multiple time slots. The same number of allocated resource blocks are applied across PUSCH repetitions. Each repetition resides in one time slot. A single start position and length for the PUSCH within a time slot can be indicated, i.e., a Single Start Position and Length Indication Value (SLIV). The same start position and length indicated by a single SLIV can be applied across PUSCH repetitions. In NR Release 15, the number of repetitions in PUSCH Repetition Type A is semi-statically configured in the RRC, and the number of repetitions is counted over consecutive physical time slots, such as... Figure 2 As shown. If the number of available symbols in a time slot is insufficient (i.e., less than the length of the PUSCH), then no PUSCH repetition will be transmitted in that time slot.

[0043] Figure 2 An example of PUSCH repetition type A with 4 repetitions in NR version 15 is shown, where PUSCH repetitions 201 and 202 in a given time slot start from symbol number 5, and the length of given PUSCH repetitions 201 and 202 is 7 symbols, assuming DDSUU (10D:2G:2U) time division duplex (TDD) mode. Here, a symbol refers to an orthogonal frequency division multiplexing (OFDM) symbol. Figure 2 In this context, "D" represents a downlink time slot, "S" represents a special time slot, and "U" represents an uplink time slot.

[0044] The DDSUU (10D:2G:2U) TDD mode represents a specific TDD configuration in which two downlink time slots, one special time slot (or protection period), and two uplink time slots are arranged sequentially. The special time slot consists of ten downlink symbols, two protection symbols, and two uplink symbols arranged sequentially. UEs 100 and 102 use these protection symbols as the handover time for switching from downlink reception to uplink transmission.

[0045] NR Release 16 (Rel-16) allows for dynamic indication of the number of repetitions for PUSCH repetition type A by associating the repetition number with each row of the Time Domain Resource Allocation (TDRA) table. Additionally, NR Release 16 introduces PUSCH repetition type B for Ultra Reliable Low Latency (URLLC) applications. In PUSCH repetition type B, a single SLIV is used to determine multiple back-to-back nominal repetitions of equal length, and each nominal repetition can span a slot boundary. Then, if a nominal repetition spans a slot boundary or is an invalid symbol, each nominal repetition is divided into multiple actual repetitions. PUSCH repetitions in PUSCH repetition type B also have the same number of allocated resource blocks in the frequency domain.

[0046] NR version 17 (Rel-17) allows counting repetitions on available time slots, i.e., counting on time slots that can be used for repeated transmissions, such as... Figure 3 As shown, this further improves PUSCH repeat type A. NR version 17 also increases the maximum number of repeats for PUSCH repeat type A from 16 to 32.

[0047] Figure 3 An example of PUSCH repetition type A with 4 repetitions in NR version 17 is shown, where PUSCH repetitions 301 and 302 in a given time slot start from symbol number 5, and the length of given PUSCH repetitions 301 and 302 is 7 symbols, assuming DDSUU (10D:2G:2U) TDD mode. Figure 3 In this context, "D" represents a downlink time slot, "S" represents a special time slot, and "U" represents an uplink time slot.

[0048] The Coverage Enhancement work item in NR Release 17 specifies a feature called Transport Block Processing on Multiple Time Slots (TBoMS). This feature allows a single transport block (TB) to be mapped onto multiple time slots, meaning that the resource allocation for a single PUSCH transport can span multiple time slots. This is different from PUSCH repetition.

[0049] Figure 4 An example of the power spectral density (PSD) gain provided by TBoMS compared to a single-slot PUSCH (shown in Figure 401) for the same transport block size is shown (shown in Figure 402).

[0050] like Figure 4 As shown, a key advantage of TBoMS is that it reduces the number of Physical Resource Blocks (PRBs) required to transmit the same Transport Block Size (TBS) compared to transmitting a TB in a single timeslot. This helps increase the Energy Per Resource Unit (EPRE), thereby improving coverage.

[0051] A new column can be added to the TDRA table to indicate the number of time slots allocated to TBoMS. . Counting can be done on available time slots. Therefore, non-contiguous time slots can be used for TBoMS in TDD. The same resource start symbol (S) and length (L) can be allocated to TBoMS in each time slot (similar to PUSCH repetition type A), as... Figure 5A and Figure 5B As shown.

[0052] Figure 5A It shows An example of continuous time slot allocation for TBoMS is shown below. Two portions of resources, 511 and 512, are allocated to a single TBoMS.

[0053] Figure 5B It shows An example of non-contiguous time slot allocation for TBoMS. Two portions of resources, 521 and 522, are allocated to a single TBoMS. Figure 5B In this context, "D" represents a downlink time slot, "S" represents a special time slot, and "U" represents an uplink time slot.

[0054] It supports repetitions of a single TBoMS. The column in the TDRA table that indicates the number of repetitions for PUSCH Repetition Type A (i.e., numberOfRepetitions-r17) in version 17 can also be used to indicate the number of repetitions of a single TBoMS. The UE can determine the repetition used for TBoMS. There are 10 available time slots, each with the same start symbol (S) and length (L), but TBS can be calculated from the resources of a single TBoMS (i.e., per TBoMS). (Scaling is performed). Redundant versions (RVs) can be cycled across TBoMS. RV sequences and RV index indicators from legacy versions 15 or 16 can be reused.

[0055] Figure 6 It shows in and Examples of TBoMS repetitions 611 and 612 in the following cases. Two portions of resources 621 and 622 are allocated for a single TBoMS repetition 611.

[0056] Uplink Control Information (UCI) messages may include at least one of the following: Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK), Channel State Information (CSI), and / or Scheduling Request (SR). The CSI may include CSI Part 1 and CSI Part 2, where CSI Part 1 has a fixed payload size and is used to identify the number of information bits in CSI Part 2. Therefore, CSI Part 1 should be fully transmitted before CSI Part 2 is transmitted.

[0057] UCI messages can be encoded and transmitted via the Physical Uplink Control Channel (PUCCH) or multiplexed on the PUSCH. At least HARQ-ACK and CSI can be multiplexed on the PUSCH. SRs may not need to be multiplexed on the PUSCH because the PUSCH can carry Buffer Status Reports (BSRs), which contain more detailed information about the UE's uplink buffer status than SRs.

[0058] UE can be called β A higher-level parameter (or beta offset) that determines the amount of resources dedicated to UCI within the PUSCH in the case of reuse. This parameter can vary for different types of UCI and their payload sizes.

[0059] For HARQ-ACK, if the payload is 1 bit or 2 bits, resource elements originally used for data scheduling in PUSCH can be punctured for HARQ-ACK, and β Can be via betaOffsetACK-Index1 Configure it. If the payload is 3 bits to 11 bits, HARQ-ACK can perform rate matching around the resource elements for data scheduling in the PUSCH, and β Can be via betaOffsetACK-Index2 Configure it. If the payload is greater than 11 bits, HARQ-ACK can perform rate matching around the resource elements for data scheduling in the PUSCH, and β Can be via betaOffsetACK-Index3 Configure it.

[0060] For CSI Part 1, if the payload is at most 11 bits, CSI Part 1 can perform rate matching around the resource elements for data scheduling in the PUSCH, and β Can be via betaOffsetCSI-Part1-Index1 Configure accordingly. If the payload is greater than 11 bits, CSI part 1 can perform rate matching around the resource elements for data scheduling in the PUSCH, and β Can be via betaOffsetCSI-Part1-Index2 Configure it.

[0061] For CSI Part 2, if the payload is at most 11 bits, CSI Part 2 can perform rate matching around the resource elements for data scheduling in the PUSCH, and β Can be via betaOffsetCSI-Part2-Index1 Configure accordingly. If the payload is greater than 11 bits, CSI part 2 can perform rate matching around the resource elements for data scheduling in the PUSCH, and β Can be via betaOffsetCSI-Part2-Index2 Configure it.

[0062] UCI mapping follows the principle of "frequency first, time second," starting with the lowest resource element at the smallest symbol index. In short, UCI mapping (i.e., multiplexing UCI on PUSCH) can include the following six steps.

[0063] The first step is to find the reserved HARQ-ACK position when the number of HARQ-ACK bits is less than or equal to 2.

[0064] In the second step, when the number of HARQ-ACK bits is greater than 2, the encoded and decoded HARQ-ACK bits are mapped (if any).

[0065] In the third step, the encoded and decoded CSI part 1 and CSI part 2 bits are mapped (if any).

[0066] In the fourth step, the encoded and decoded uplink shared channel (UL-SCH) bits are mapped (if any).

[0067] In the fifth step, when the number of HARQ-ACK bits is less than or equal to 2, the encoded and decoded HARQ-ACK bits are mapped (if any).

[0068] In the sixth step, code words are formed.

[0069] Figure 7A An example of mapping HARQ-ACK onto PUSCH is shown (corresponding to step 2 above).

[0070] Figure 7B An example of mapping CSI onto PUSCH is shown (corresponding to step 3 above).

[0071] Figure 7C An example of mapping UL data onto PUSCH is shown (corresponding to step 4 above).

[0072] Figure 7A , Figure 7B and Figure 7C The given element 700 represents a resource element (RE). Figure 7A , Figure 7B and Figure 7C The example considers a single resource block, a single layer, a pi / 2-BPSK modulation scheme (therefore, for illustrative purposes, 1 RE corresponds to 1 bit), and demodulation reference signal (DM-RS) symbols 711, 712, and 713 are located on OFDM symbol numbers 2, 7, and 11, respectively (symbol indices start from 0). BPSK is an abbreviation for binary phase shift keying. In DM-RS symbols 711, 712, and 713, REs other than DM-RS RE 701 are used for data signal transmission (comb type). This example assumes 6 HARQ-ACK bits 702, 19 CSI parts (1 bit 703), 19 CSI parts (2 bits 704), and 106 bits for data. In this example, the UCI mapping following the above six steps is as follows.

[0073] In the first step, since the number of HARQ-ACK bits in this example is 6 (>2), this step of finding the reserved RE is skipped.

[0074] In the second step, the encoded and decoded HARQ-ACK bits 702 are as follows: Figure 7A The mapping is shown below. HARQ-ACK is mapped to REs in the OFDM symbols available after the first DM-RS OFDM symbol 711. In this example, the number of REs required for HARQ-ACK is 6. Since this value is no greater than half the number of REs available for UCI transmission, the mapping of HARQ-ACK is as follows. Figure 7A The distribution is shown.

[0075] In the third step, the encoded / decoded CSI part 1 bit 703 and the encoded / decoded CSI part 2 bits 704 are as follows: Figure 7B The mapping is shown below. CSI mapping begins with the first non-DM-RS OFDM symbol available in the PUSCH allocation. In this example, CSI mapping begins with OFDM symbol 0. The mapping position is determined based on the number of available REs and the number of REs required for CSI Part 1 transmission. In this example, CSI Part 1 transmission requires 19 REs. Since only 12 REs are available for transmission in a given symbol, each RE in OFDM symbol 0 is used for CSI Part 1 in this example. For the transmission of the remaining CSI Part 1 bits, the mapping continues to the next OFDM symbol not used for DM-RS (i.e., OFDM symbol 1 in this example). In OFDM symbol 1, 12 REs are available, but CSI Part 1 only requires 7 more REs.

[0076] In the fourth step, the encoded / decoded UL data bit 705 is mapped onto the remaining REs, such as... Figure 7C As shown.

[0077] In step 5, since the number of HARQ-ACK bits in this example is 6 (>2), this step of mapping the encoded and decoded HARQ-ACK bits is skipped.

[0078] In the sixth step, code words are formed.

[0079] As can be seen from the above, UCI mainly reuses the first few symbols of PUSCH in the time slot.

[0080] The following discussion concerns UCI multiplexing in cases where PUSCH is repeatedly transmitted. If the UE transmits PUSCH on multiple time slots, or transmits multiple PUSCHs scheduled by DCI on multiple time slots (e.g., using DCI format 0_1 ​​or format 0_2), and the UE transmits a PUCCH with HARQ-ACK and / or CSI information in a single time slot that overlaps with PUSCH transmissions in one or more of the multiple time slots, and the PUSCH transmissions in one or more time slots satisfy specific conditions for multiplexing HARQ-ACK and / or CSI information, the UE multiplexes the HARQ-ACK and / or CSI information in the PUSCH transmissions in one or more time slots.

[0081] As can be seen from the above, when multiplexing occurs due to overlap with PUCCH, UCI performs multiplexing on the overlapping time slots (multiple slots).

[0082] However, there are cases where aperiodic channel state information (A-CSI) is requested and carried via the PUSCH (i.e., A-CSI is on the PUSCH). In this case, the following can be applied.

[0083] For PUSCH repetition type B, when the UE is scheduled to transmit transport blocks and (multiple) aperiodic CSI reports on the PUSCH via the "CSI request" field in the downlink control information (DCI), the (multiple) CSI reports may be transmitted only on the first actual repetition. The UE does not expect the first actual repetition to have only a single symbol duration.

[0084] For PUSCH repetition type A, when DCI format 0_1 ​​and DCI format 0_2 are Measurement Reference Signal (SRS) Resource Set Indicator indicator code points "10" or "11", and when (multiple) aperiodic CSI reports are scheduled on a PUSCH with a transport block via the "CSI request" field on the DCI, the multiplexing of the (multiple) CSI reports can be determined as follows.

[0085] If the high-level parameter AP-CSI-MultiplexingMode in CSI-AssociatedReportConfigInfo is enabled, and UCIs other than (multiple) CSI reports are not multiplexed on the PUSCH, then (multiple) CSI reports can be transmitted separately only on the first transmission timing associated with the first SRS resource set and on the first transmission timing associated with the second SRS resource set.

[0086] Otherwise, (multiple) CSI reports can be transmitted only on the first transmission occasion.

[0087] For PUSCH transmissions with Transport Block Processing on Multiple Slots (TBoMS), when DCI format 0_1 ​​and DCI format 0_2 schedule (multiple) aperiodic CSI reports on a PUSCH with a transport block via the “CSI request” field on the DCI, (multiple) CSI reports can be transmitted only on the first of the 𝑁∙𝐾 slots determined for the PUSCH transmission.

[0088] As can be seen from the above, for PUSCH repetition type A, type B or TBoMS, A-CSI can be multiplexed only on the first PUSCH repetition or transmission.

[0089] 5G NR currently supports two duplex modes: Frequency Division Duplex (FDD) for paired frequency bands and Time Division Duplex (TDD) for unpaired frequency bands. In TDD, time-domain resources are divided between the downlink and uplink. Allocating a limited duration for the uplink in TDD will result in reduced coverage, increased latency, and reduced capacity.

[0090] For the reasons mentioned above, 3GPP has agreed to launch Study 18 (RP-213591) on the evolution of duplex operation in NR to address the aforementioned challenges. One of the goals of this study is to allow simultaneous DL and UL transmissions on different Physical Resource Blocks (PRBs) or subbands within unpaired broadband NR cells, such as... Figure 8 As shown. Here, this duplex scheme is referred to as Subband Full-Duplex (SBFD) or Subband Non-Overlapping Full-Duplex. SBFD can also be called Cross-Dual-Duplex (xDD) or Flexible Duplex (FDU).

[0091] Figure 8 An example of frequency-time resource partitioning using SBFD 803 is shown, compared to FDD 801 and TDD 802.

[0092] Some of the goals of this research project include: studying non-overlapping sub-band full-duplex, identifying possible schemes and evaluating their feasibility and performance, and studying the handling of cross-link interference (CLI) between gNBs and UEs, and identifying solutions for managing these interferences by considering intra-sub-band CLI and inter-sub-band CLI in the case of non-overlapping sub-band full-duplex.

[0093] As can be seen from the above description of SBFD operation, there are two time slot types for DL ​​and UL transmissions (e.g., Figure 9 As shown), namely: 1) SBFD time slot, during which non-overlapping DL subbands and UL subbands coexist; and 2) non-SBFD time slot, during which the entire frequency band is used for UL or DL ​​(i.e., conventional / full DL / UL time slot).

[0094] Several SBFD operation modes have been investigated, including whether the SBFD-aware UE knows the time and frequency positions of the sub-bands used for SBFD operation. However, it has been agreed that operation modes in which the SBFD-aware UE knows the time and frequency positions of the sub-bands used for SBFD operation should be given priority. This means that the SBFD slots should be known to the (SBFD-aware) UE in some way.

[0095] Figure 9 Examples of SBFD slot 902 and non-SBFD slots 901 and 903 are shown.

[0096] SBFD introduces a new CLI type, namely, intra-channel sub-band CLI. This interference can be classified as follows: 1) gNB self-interference; 2) intra-cell UE-UE intra-channel CLI; 3) inter-cell UE-UE intra-channel CLI; and 4) gNB-to-gNB intra-channel CLI.

[0097] In addition to these new CLI types, in the case of different frequency domain divisions in neighboring cells, the system may also suffer from intra-channel CLI, that is, CLI transmitted on overlapping frequency resources: 5) intra-channel CLI between gNB and gNB; and 6) intra-channel CLI between UE and UE.

[0098] Figure 10A An example of co-channel interference type is shown in an SBFD deployment that utilizes the same frequency domain partitioning. Figure 10A The system shown includes two gNBs 1011 and 1012 and four UEs 1021, 1022, 1023 and 1024.

[0099] Reference Figure 10A1001 shows gNB self-interference, 1002 shows intra-cell UE-UE co-channel sub-band CLI, 1003 shows inter-cell UE-UE co-channel sub-band CLI, and 1004 shows gNB-to-gNB co-channel sub-band CLI.

[0100] Figure 10B An example of co-channel interference types is shown in SBFD deployments utilizing different frequency domain partitions. Figure 10B The system shown includes two gNBs 1011 and 1012 and four UEs 1021, 1022, 1023 and 1024.

[0101] Reference Figure 10B 1005 shows the intra-channel CLI between gNB and gNB, and 1006 shows the intra-channel CLI between UE and UE.

[0102] There is an issue of uneven distribution of CLI levels among the resource blocks (RBs) allocated for UL transmission in the UL subband. This can be seen from... Figure 10A and Figure 10B It has been observed that UL transmission in SBFD slots or symbols is affected not only by intra-channel CLI but also by inter-channel CLI. The level of inter-channel CLI across UL subbands allocated to RBs for UL transmission is uneven. In fact, RBs closer to (multiple) DL subbands will be more affected by inter-channel CLI than those farther away. Therefore, to better protect UCI, it is beneficial to avoid mapping UCI onto RBs closer to (multiple) DL subbands. However, there is currently no solution available to avoid mapping UCI onto RBs closer to (multiple) DL subbands.

[0103] Some example embodiments can address the aforementioned problems by providing a method for mapping encoded / decoded UCI bits onto uplink transmissions during SBFD operations. The example embodiments described below can help protect UCIs against CLI in cases where UCIs are multiplexed during SBFD operations on uplink transmissions.

[0104] The following will use the principles and terminology of 5G radio access technology to describe some example embodiments, but these example embodiments are not limited to 5G radio access technology.

[0105] Figure 11A signal flow diagram according to an example embodiment is shown. This example embodiment is designed to avoid mapping UCI to resource blocks close to (multiple) DL subbands that have more inter-subband interference. This example embodiment can be applied to any uplink transmission (e.g., PUSCH) in an SBFD slot and does not require the transmission to span different symbol types.

[0106] Reference Figure 11 At 1101, network node (NW node) 104 transmits information to UE 100, which includes at least the following: frequency band; a certain number of SBFD time slots and / or symbols (i.e., where the frequency band is divided into multiple sub-bands, and at least one sub-band is used for DL ​​transmission, and at least one sub-band is used for UL transmission), and the location of the certain number of SBFD time slots and / or symbols in the radio frame; a certain number of non-SBFD time slots and / or symbols (i.e., where the entire frequency band is used for DL ​​transmission or UL transmission), and the location of the certain number of non-SBFD time slots and / or symbols in the radio frame; and the number and location of (if any) gap symbols in a particular time slot.

[0107] The UE is configured with one or more time slots operating in SBFD mode by receiving this information. The network node can be, for example, a radio access network node, such as a gNB.

[0108] At 1102, the network node can determine the cross-link interference (CLI) level associated with the physical uplink shared channel from the UE. The CLI level can be measured by the network node and / or reported by the UE. If the CLI level is reported by the UE, the network node can determine the CLI level based on at least one of the following: the report from the UE and the CLI level measured by the network node itself.

[0109] At 1103, the network node transmits to the UE an indication that, if uplink control information is to be multiplexed on the PUSCH, the uplink control information will be mapped onto the Physical Uplink Shared Channel at one or more time slots, wherein the one or more time slots are configured for Subband Full-Duplex (SBFD) operation. For example, this indication may be transmitted via RRC. The UE receives this indication.

[0110] Network nodes can determine to transmit this indication based on cross-link interference levels exceeding a threshold. Otherwise, conventional mappings (e.g., such as...) can be applied. Figure 7A , Figure 7B and Figure 7C (As shown).

[0111] It should be noted that step 1103 can be performed alternatively before step 1101, or steps 1101 and 1103 can be combined into a single step.

[0112] At 1104, the network node transmits an indication to the UE, which indicates at least one default number of resource blocks. Or at least one scaling factor, the at least one default number or at least one scaling factor being used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel that are within a predefined distance in the frequency domain from one or more downlink subbands or one or more guard bands.

[0113] The indications in 1104 can be transmitted together with the indications in 1103 via higher-layer signaling (such as RRC or MAC layer signaling) or physical layer signaling, or these indications can be transmitted separately.

[0114] In 1105, network nodes schedule (e.g., via scheduling DCI) PUSCH in one or more time slots, which include SBFD symbols, or both SBFD and non-SBFD symbols, which can lead to UCI multiplexing on the PUSCH in case of conflict. For example, if the PUSCH overlaps in time with the Physical Uplink Control Channel (PUCCH) carrying the UCI, the UCI can be multiplexed on the PUSCH and the PUCCH can be discarded. Alternatively or additionally, network nodes can schedule PUSCH with duplicates or TBoMS spanning SBFD and non-SBFD time slots.

[0115] As an alternative to 1103 and 1104, the network node can transmit indications for 1103 and 1104 to the UE via the scheduling DCI at 1105. As mentioned above, this indication can depend on the CLI level measured by the network node and / or reported by the UE. For example, this mapping can be applied if the CLI is above a threshold (i.e., in a high CLI case); otherwise, a conventional mapping (e.g., such as...) can be applied. Figure 7A , Figure 7B and Figure 7C (As shown).

[0116] In 1106, the UE determines, at least based on the indication in 1103, whether to map uplink control information onto the PUSCH during SBFD operation.

[0117] For example, in the event of a conflict, the UE can determine whether UCI should be multiplexed on the PUSCH. The UE can also determine (multiple) SBFD time slots, (multiple) special time slots, and (multiple) non-SBFD time slots, and / or SBFD symbols, gap symbols, and non-SBFD symbols in a given time slot.

[0118] The one or more gap symbols are gaps used by the UE to switch from downlink reception to uplink transmission when it receives downlink transmission in at least one downlink subband. In other words, the one or more gap symbols refer to symbols reserved as guard periods between downlink transmission and uplink transmission in the same or different subbands of the same frequency band.

[0119] Uplink control information may include at least one of the following: HARQ-ACK information, CSI part 1, and / or CSI part 2.

[0120] In 1107, the UE is based on at least one default number of resource blocks. Or at least one scaling factor to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel that are within a predefined distance in the frequency domain from one or more downlink subbands or one or more guard bands. In other words, the UE determines the number of RBs located near (multiple) DL subbands or (multiple) guard bands in the frequency domain. .

[0121] For example, if the PUSCH is assigned to one or more specific RB sets within the UL subband (e.g., those RBs close to (multiple) DL subbands), the UE can decide to determine In other words, the UE can determine whether the physical uplink shared channel is allocated on one or more predefined resource block sets within the uplink subband, and the number of resource blocks can be determined based on the determination that the physical uplink shared channel is allocated on at least one of the one or more predefined resource block sets within the uplink subband. Figure 15 As shown in the example, one or more predefined resource block sets may include multiple resource block sets 1501, 1502, 1503, 1504, 1505, 1506, and 1507, which at least partially overlap. For example, if PUSCH spans two RB sets 1504 and 1505, it can be considered to be scheduled in a superset 1502 of the two sets 1504 and 1505.

[0122] Alternatively, the UE may determine whether the distance, in units of resource blocks, between one or more downlink subbands and at least one of the following is below a threshold: the resource block with the highest resource block index and / or the resource block with the lowest resource block index among the resource blocks allocated for the physical uplink shared channel. In this case, the number of resource blocks can be determined based on determining that the distance is below the threshold.

[0123] In one example, the number of resource blocks can be determined based on at least one default number of resource blocks, the allocated resource blocks of the physical uplink shared channel, and the bandwidth of the uplink subbands allocated to the physical uplink shared channel. In this case, at least one default number of resource blocks may include a single default number of resource blocks. For example, if a unique (i.e., single) default number is indicated from a network node (e.g., via RRC). The UE determines the number of resource blocks in the following way. :

[0124] In another example, at least one default number of resource blocks may include multiple different default numbers for different sets of resource blocks in the uplink subband. In this case, the UE can determine (or select) the default number of resource blocks from multiple different default numbers based on the allocated resource blocks in the uplink subband of the physical uplink shared channel (i.e., the set of RBs in the UL subband allocated based on the PUSCH). In this scenario, the number of resource blocks can be determined based on the default number of resource blocks, the allocated resource blocks of the physical uplink shared channel, and the bandwidth of the uplink subband. For example, the UE can determine the number of resource blocks in the following ways. :

[0125] In another example, the number of resource blocks can be determined by multiplying the number of allocated resource blocks of the physical uplink shared channel by at least one scaling factor. In this case, the at least one scaling factor may include a single scaling factor (i.e., a unique scaling factor). For example, the UE can determine the number of resource blocks in the following way: :

[0126] In another example, at least one scaling factor may include multiple different scaling factors for different sets of resource blocks in the uplink subband. In this case, the UE determines (or selects) a scaling factor from multiple different scaling factors based on the allocated resource blocks of the physical uplink shared channel in the uplink subband (i.e., the set of RBs in the UL subband allocated based on the PUSCH). In this case, the number of resource blocks can be determined by multiplying the number of allocated resource blocks of the physical uplink shared channel by the scaling factor. For example, the UE can determine the number of resource blocks in the following manner. :

[0127] In 1108, the UE is based on the determined number of resource blocks. Determine at least one frequency resource range among the allocated frequency resources of the PUSCH, and at least one subset of uplink control information should not be mapped to that at least one frequency resource range.

[0128] In one example, the at least one frequency resource range may include a frequency resource range that corresponds to the bottom or top resource block of the allocated resource block of the physical uplink shared channel in the frequency domain.

[0129] In another example, the at least one frequency resource range may include two frequency resource ranges. One of the two frequency resource ranges may correspond to the bottom resource block of the allocated resource block of the physical uplink shared channel in the frequency domain. The other frequency resource range may correspond to the top resource block of the allocated resource block of the physical uplink shared channel in the frequency domain.

[0130] In other words, the UE can obtain the top RB and / or bottom RB from the allocated RB for PUSCH. To determine at least one frequency resource range, depending on the set of RBs to which the PUSCH is allocated.

[0131] Examples of RB sets 1501, 1502, 1503, 1504, 1505, 1506, and 1507 are as follows: Figure 15 As shown. For example, if the UE determines that PUSCH is allocated in Figure 15 In RB set 1501 (i.e., PUSCH is almost entirely allocated the UL subband bandwidth), the two frequency resource ranges 1401 and 1402 at the top and bottom can be determined, such as Figure 14 As shown.

[0132] As another example, if the UE determines that the PUSCH is allocated in RB sets 1502, 1504, or 1505, then only one frequency resource range 1401 at the top can be determined (see [link]). Figure 14 ).

[0133] As another example, if the UE determines that PUSCH is allocated in Figure 15 If the RB set is 1503, 1506, or 1507, then only one frequency resource range 1402 at the bottom can be determined (see [link]). Figure 14 ).

[0134] At 1109, the UE maps at least one subset of the uplink control information onto the Physical Uplink Shared Channel (PUSCH) such that at least one subset of the uplink control information is not mapped to at least one frequency resource range. Here, mapping the uplink control information may mean that the UE maps encoded / decoded uplink control information bits onto the PUSCH.

[0135] In one example, the UE may map low-priority uplink control information onto at least one frequency resource range. For example, the low-priority uplink control information may include channel state information portion 2. In this case, at least one subset of uplink control information not mapped to at least one frequency resource range may include high-priority uplink control information, such as at least one of the following: HARQ-ACK information and / or channel state information portion 1.

[0136] In other words, the UE may not map any UCI on at least one determined frequency resource range, or may only map low-priority UCIs (e.g., CSI Part 2) on at least one determined frequency resource range.

[0137] At 1110, the UE, based on the SBFD operation and the mapping result, transmits the PUSCH to the network node in one or more time slots. The network node receives the PUSCH.

[0138] Figure 12 A method flowchart according to an example embodiment is shown, the method being performed by apparatus 1600. For example, apparatus 1600 may be, include, or be contained within a user equipment. The user equipment may also be referred to as a wireless communication device, user unit, mobile station, remote terminal, access terminal, user terminal, terminal equipment, or user equipment (UE). The user equipment may correspond to... Figure 1 One of UE 100 or 102, or Figure 11 UE in the middle.

[0139] Reference Figure 12 In block 1201, the device receives an indication to map uplink control information onto the physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation. This indication may be received from network node 104.

[0140] In block 1202, the device determines, based on at least one default number of resource blocks or at least one scaling factor, the number of resource blocks in the allocated resource blocks of the physical uplink shared channel that are within a predefined distance in the frequency domain from one or more downlink subbands or one or more guard bands.

[0141] At least one default number or the at least one scaling factor may be indicated by the network node, or may be predefined (e.g., hard-coded in the standard).

[0142] In block 1203, the device determines at least one frequency resource range based on the number of resource blocks, at least one subset of the uplink control information should not be mapped to the at least one frequency resource range.

[0143] In block 1204, the device maps at least one subset of uplink control information onto the physical uplink shared channel such that at least one subset of the uplink control information is not mapped to at least one frequency resource range.

[0144] In box 1205, the device transmits the Physical Uplink Shared Channel (PUSCH) at one or more time slots according to a mapping. The PUSCH can be transmitted to network nodes.

[0145] In one example, the number of resource blocks can be determined based on at least one default number of resource blocks, the allocated resource blocks of the physical uplink shared channel, and the bandwidth of the uplink subband allocated to the physical uplink shared channel, wherein at least one default number of resource blocks may include a default number of resource blocks.

[0146] In another example, at least one default number of resource blocks may include multiple different default numbers for different sets of resource blocks in the uplink subband. In this case, the apparatus may determine the default number of resource blocks from multiple different default numbers based on the allocated resource blocks of the physical uplink shared channel in the uplink subband. The number of resource blocks may be determined based on the default number of resource blocks, the allocated resource blocks of the physical uplink shared channel, and the bandwidth of the uplink subband.

[0147] In another example, the number of resource blocks can be determined by multiplying the number of allocated resource blocks of the physical uplink shared channel by at least one scaling factor, wherein the at least one scaling factor may include a scaling factor.

[0148] In another example, at least one scaling factor may include multiple different scaling factors for different sets of resource blocks in the uplink subband. In this case, the device may determine a scaling factor from multiple different scaling factors based on the allocated resource blocks of the physical uplink shared channel in the uplink subband. The number of resource blocks can be determined by multiplying the number of allocated resource blocks of the physical uplink shared channel by the scaling factor.

[0149] The apparatus can determine whether the physical uplink shared channel is allocated on one or more predefined resource block sets within an uplink subband. The number of resource blocks can be determined based on the determination that the physical uplink shared channel is allocated on at least one of the one or more predefined resource block sets within the uplink subband. For example, the one or more predefined resource block sets include multiple resource block sets that at least partially overlap.

[0150] Alternatively, the apparatus may determine whether the distance, in units of resource blocks, between one or more downlink subbands and at least one of the following is less than a threshold: the resource block with the highest resource block index among the resource blocks allocated to the physical uplink shared channel, or the resource block with the lowest resource block index. The number of resource blocks may be determined based on determining that the distance is less than the threshold.

[0151] In one example, at least one frequency resource range may include a frequency resource range that corresponds to the bottom or top resource block of the allocated resource block of the physical uplink shared channel in the frequency domain.

[0152] In another example, at least one frequency resource range may include two frequency resource ranges, wherein one of the two frequency resource ranges corresponds to the bottom resource block of the allocated resource block of the physical uplink shared channel in the frequency domain, and the other frequency resource range of the two frequency resource blocks corresponds to the top resource block of the allocated resource block of the physical uplink shared channel in the frequency domain.

[0153] In one example, the device can map low-priority uplink control information to at least one frequency resource range. For example, the low-priority uplink control information may include channel state information portion 2.

[0154] Figure 13 A method flowchart according to an example embodiment is shown, the method being performed by device 1700. For example, device 1700 may be, include, or be contained in a network node of a wireless access network. This network node may correspond to... Figure 1 Access node 104 in the middle, or Figure 11 Network nodes in the network.

[0155] Reference Figure 13 In block 1301, the apparatus transmits to user equipment 100 an indication to map uplink control information onto the physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for subband full-duplex SBFD operation.

[0156] The device can determine the cross-link interference level associated with the physical uplink shared channel. In this case, the device can determine an indication that the transmission indication maps uplink control information onto the physical uplink shared channel based on the cross-link interference level being higher than a threshold.

[0157] In block 1302, the apparatus transmits to the user equipment an indication of at least one default number of resource blocks or at least one scaling factor, the at least one default number of resource blocks or at least one scaling factor being used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel that are within a predefined distance in the frequency domain from one or more downlink subbands or one or more guard bands.

[0158] In block 1303, the apparatus receives a physical uplink shared channel from a user equipment, wherein at least a subset of uplink control information is mapped onto the physical uplink shared channel, and wherein at least a subset of the uplink control information is not mapped into the number of resource blocks.

[0159] In one example, the number of resource blocks can be determined based on at least one default number of resource blocks, the allocated resource blocks of the physical uplink shared channel, and the bandwidth of the uplink subband allocated to the physical uplink shared channel, wherein at least one default number of resource blocks may include a default number of resource blocks.

[0160] In another example, at least one default number of resource blocks may include multiple different default numbers for different sets of resource blocks in the uplink subband. In this case, the user equipment can determine the default number of resource blocks from multiple different default numbers based on the allocated resource blocks of the physical uplink shared channel in the uplink subband. The number of resource blocks can be determined based on the default number of resource blocks, the allocated resource blocks of the physical uplink shared channel, and the bandwidth of the uplink subband.

[0161] In another example, the number of resource blocks can be determined by multiplying the number of allocated resource blocks of the physical uplink shared channel by at least one scaling factor, wherein the at least one scaling factor may include a scaling factor.

[0162] In another example, at least one scaling factor may include multiple different scaling factors for different sets of resource blocks in the uplink subband. In this case, the user equipment can determine a scaling factor from multiple different scaling factors based on the allocated resource blocks of the physical uplink shared channel in the uplink subband. The number of resource blocks can be determined by multiplying the number of allocated resource blocks of the physical uplink shared channel by the scaling factor.

[0163] The user equipment can determine whether the physical uplink shared channel is allocated on one or more predefined resource block sets within the uplink subband. The number of resource blocks can be determined based on the determination that the physical uplink shared channel is allocated on at least one of the one or more predefined resource block sets within the uplink subband. For example, the one or more predefined resource block sets may include multiple resource block sets that at least partially overlap.

[0164] Alternatively, the user equipment may determine whether the distance, in units of resource blocks, between one or more downlink subbands and at least one of the following is below a threshold: the resource block with the highest resource block index among the resource blocks allocated to the physical uplink shared channel, or the resource block with the lowest resource block index. The number of resource blocks may be determined based on determining that the distance is below the threshold.

[0165] User equipment can determine at least one frequency resource range based on the number of resource blocks, and at least one subset of the uplink control information should not be mapped to the at least one frequency resource range.

[0166] In one example, the at least one frequency resource range may include a frequency resource range that corresponds to the bottom or top resource block of the allocated resource block of the physical uplink shared channel in the frequency domain.

[0167] In another example, the at least one frequency resource range may include two frequency resource ranges, wherein one of the two frequency resource ranges corresponds to the bottom resource block of the allocated resource block of the physical uplink shared channel in the frequency domain, and the other frequency resource range corresponds to the top resource block of the allocated resource block of the physical uplink shared channel in the frequency domain.

[0168] In one example, a user equipment may map low-priority uplink control information to at least one frequency resource range. For example, the low-priority uplink control information may include channel state information portion 2.

[0169] pass Figures 11 to 13 The described steps, related functions, and information interactions (messages) do not have an absolute temporal order. Some steps may be performed simultaneously or in a manner different from the described order. Other functions may be performed, other information sent, and / or other rules applied between or within them. Some steps, parts of steps, or one or more messages may be omitted or replaced by corresponding steps, parts of steps, or one or more messages.

[0170] As used in this specification, expressions such as "at least one of the following: " and "at least one " indicate that the list of elements, when connected by "and" or "or", includes at least one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0171] Figure 14 This illustrates defining at least one frequency resource range (e.g., within the allocated frequency resources for PUSCH transmissions) Figure 11 box 1108 or Figure 12 In the example of box 1203, at least one subset of UCI should not be mapped within that frequency resource range. In this example, at least one subset of UCI is not mapped to resource blocks 1401 and 1402, but may be mapped to resource blocks between 1401 and 1402.

[0172] Figure 15 Examples are shown of setting different resource block sets 1501, 1502, 1503, 1504, 1505, 1506, and 1507 in the uplink subband.

[0173] Figure 16 An example of apparatus 1600 is shown, which includes components for performing one or more of the example embodiments described above. For example, apparatus 1600 may be an apparatus included in or incorporated within a user equipment. The user equipment may also be referred to as a wireless communication device, user unit, mobile station, remote terminal, access terminal, user terminal, terminal equipment, or user equipment (UE). The user equipment may correspond to... Figure 1 One of UE 100 or UE 102, or Figure 11 UE in the middle.

[0174] Apparatus 1600 may include circuitry or chipsets for implementing one or more of the exemplary embodiments described above. For example, apparatus 1600 may include at least one processor 1610. The at least one processor 1610 is used to interpret instructions (e.g., computer program instructions) and process data. The at least one processor 1610 may include one or more programmable processors. The at least one processor 1610 may include programmable hardware with embedded firmware and may alternatively or additionally include one or more application-specific integrated circuits (ASICs).

[0175] The at least one processor 1610 is connected to at least one memory 1620. The at least one processor is configured to read and write data to the at least one memory 1620. The at least one memory 1620 may include one or more memory cells. These memory cells may be volatile or non-volatile. It should be noted that it may include one or more non-volatile memory cells and one or more volatile memory cells, or alternatively, it may include only one or more non-volatile memory cells, or only one or more volatile memory cells. Volatile memory may be, for example, random access memory (RAM), dynamic random access memory (DRAM), or synchronous dynamic random access memory (SDRAM). Non-volatile memory may be, for example, read-only memory (ROM), programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), flash memory, optical storage, or magnetic storage. In general, memory may be referred to as a non-transitory computer-readable medium. The term "non-transitory" as used herein is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., the difference between RAM and ROM). The at least one memory 1620 stores computer-readable instructions that are executed by the at least one processor 1610 to perform one or more of the exemplary embodiments described above. For example, non-volatile memory stores computer-readable instructions, while the at least one processor 1610 uses volatile memory to execute instructions for temporarily storing data and / or instructions. Computer-readable instructions may refer to computer program code.

[0176] Computer-readable instructions may be pre-stored in at least one memory 1620, or alternatively or additionally, these instructions may be received by the device via an electromagnetic carrier signal and / or copied from a physical entity such as a computer program product. Execution of these computer-readable instructions by at least one processor 1610 causes the device 1600 to perform one or more of the exemplary embodiments described above. That is, at least one processor and at least one memory storing these instructions can provide components for performing or causing the performance of any of the methods and / or steps described above.

[0177] In the context of this document, "memory," "computer-readable medium," or "computer-readable device" can refer to any non-transitory medium or apparatus capable of containing, storing, transmitting, propagating, or carrying instructions for use by or in conjunction with an instruction execution system, apparatus, or device (e.g., a computer). The term "non-transitory" as used herein is a limitation on the medium itself (i.e., tangible, not tactile) and not on the persistence of data storage (e.g., the difference between RAM and ROM).

[0178] The device 1600 may also include or be connected to the input unit 1630. The input unit 1630 may include one or more interfaces for receiving input. These interfaces may include, for example, one or more temperature, motion, and / or orientation sensors, one or more cameras, one or more accelerometers, one or more microphones, one or more buttons, and / or one or more touch detection units. Additionally, the input unit 1630 may include an interface for connecting external devices.

[0179] The device 1600 may also include an output unit 1640. The output unit may include or be connected to one or more displays capable of displaying visual content, such as a light-emitting diode (LED) display, a liquid crystal display (LCD), and / or a liquid crystal display on silicon (LCoS). The output unit 1640 may also include one or more audio outputs. For example, the one or more audio outputs may be speakers.

[0180] The device 1600 also includes a connection unit 1650. The connection unit 1650 is used to establish a wireless connection with one or more external devices. The connection unit 1650 includes at least one transmitter and at least one receiver, which may be integrated into or connected to the device 1600. The at least one transmitter includes at least one transmitting antenna, and the at least one receiver includes at least one receiving antenna. The connection unit 1650 may include one or more integrated circuits for providing wireless communication capabilities to the device 1600. Alternatively, the wireless connection may be implemented using an application-specific integrated circuit (ASIC). The connection unit 1650 may also provide means for performing at least some of the steps or functions in one or more of the exemplary embodiments described above. The connection unit 1650 may include one or more components, such as a power amplifier, a digital front-end (DFE), an analog-to-digital converter (ADC), a digital-to-analog converter (DAC), a frequency converter, a (de)modulator, and / or encoding / decoding circuitry, which are controlled by corresponding control units.

[0181] It should be noted that device 1600 may also include Figure 16 Various components not shown. These components may be hardware components and / or software components.

[0182] Figure 17 An example of apparatus 1700 is shown, which includes components for performing one or more exemplary embodiments described above. For example, apparatus 1700 may be an apparatus included in or incorporated within a network node of a wireless access network. This network node may correspond to... Figure 1 Access node 104 in the middle, or Figure 11 Network nodes in the network.

[0183] This network node can also be referred to as, for example, a network element, a radio access network (RAN) node, a next-generation radio access network (NG-RAN) node, a NodeB, an eNB, a gNB, a base transceiver unit (BTS), a base station, an NR base station, a 5G base station, an access node, an access point (AP), a cell site, a relay node, a repeater, an integrated access and backhaul (IAB) node, an IAB provisioning node, a distributed unit (DU), a centralized unit (CU), a baseband unit (BBU), a radio unit (RU), a radio head, a remote radio head (RRH), or a transmit and receive point (TRP).

[0184] Apparatus 1700 may include, for example, circuitry or chipsets for implementing one or more exemplary embodiments described above. Apparatus 1700 may be an electronic device comprising one or more electronic circuits. Apparatus 1700 may include communication control circuitry 1710, such as at least one processor, and at least one memory 1720 storing instructions 1722 that, when executed by the at least one processor, cause apparatus 1700 to perform one or more exemplary embodiments described above. These instructions 1722 may, for example, include computer program code (software). The at least one processor and the at least one memory storing the instructions may provide components for performing or causing the performance of any of the methods and / or steps described above.

[0185] The processor is connected to memory 1720. The processor is configured to read and write data to memory 1720. Memory 1720 may include one or more memory cells. These memory cells may be volatile or non-volatile. It should be noted that it may include one or more non-volatile memory cells and one or more volatile memory cells, or only one or more non-volatile memory cells, or only one or more volatile memory cells. Volatile memory may be, for example, random access memory (RAM), dynamic random access memory (DRAM), or synchronous dynamic random access memory (SDRAM). Non-volatile memory may be, for example, read-only memory (ROM), programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), flash memory, optical storage, or magnetic storage. Generally, memory may be referred to as a non-transitory computer-readable medium. The term "non-transitory" as used herein is a limitation on the medium itself (i.e., tangible, not tactile), not a limitation on the persistence of data storage (e.g., the difference between RAM and ROM). Memory 1720 stores computer-readable instructions that are executed by the processor. For example, non-volatile memory stores computer-readable instructions, while the processor uses volatile memory to execute those instructions, or to temporarily store data and / or instructions.

[0186] Computer-readable instructions may be pre-stored in memory 1720, or alternatively or additionally, these instructions may be received by the device via electromagnetic carrier signals and / or copied from a physical entity such as a computer program product. Executing these computer-readable instructions will cause device 1700 to perform one or more of the functions described above.

[0187] The memory 1720 can be implemented using any applicable data storage technology, such as semiconductor-based storage devices, flash memory, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and / or removable memory. The memory may include a configuration database for storing configuration information, such as a current list of neighboring cells, and in some exemplary embodiments, may also include the frame structure used by detected neighboring cells.

[0188] The device 1700 may also include or be connected to a communication interface 1730, such as a radio unit, which includes hardware and / or software for establishing a communication connection with one or more wireless communication devices according to one or more communication protocols. The communication interface 1730 includes at least one transmitter (Tx) and at least one receiver (Rx), which may be integrated into or connected to the device 1700. The communication interface 1730 may provide means for performing some of the steps in one or more of the exemplary embodiments described above. The communication interface 1730 may include one or more components, such as a power amplifier, a digital front-end (DFE), an analog-to-digital converter (ADC), a digital-to-analog converter (DAC), a frequency converter, a (de)modulator, and / or encoding / decoding circuitry, which are controlled by corresponding control units.

[0189] Communication interface 1730 provides the device with the ability to conduct wireless communication in a wireless communication network. For example, the communication interface can provide a radio interface for one or more wireless communication devices. Device 1700 may also include or be connected to another interface facing the core network, such as a network coordination device or Access and Mobility Management Function (AMF), and / or be connected to an access node of the wireless communication network.

[0190] The device 1700 may also include a scheduler 1740 configured to allocate radio resources. The scheduler 1740 may be configured together with the communication control circuitry 1710 or separately.

[0191] It should be noted that device 1700 may also include Figure 17 Various components not shown. These components may be hardware components and / or software components.

[0192] The term "circuit" as used in this application may refer to one or all of the following: a) a circuit implementation consisting solely of hardware (e.g., an implementation solely in analog and / or digital circuitry); and b) a combination of hardware circuitry and software, such as (as applicable): i) a combination of analog and / or digital hardware circuitry and software / firmware; and ii) any part of a hardware processor working in conjunction with software (including digital signal processors, software, and memory) to enable a device (e.g., a mobile phone) to perform various functions; and c) hardware circuitry and / or processors (e.g., one or more microprocessors or a portion thereof) that require software (e.g., firmware) to function during operation, but may not be present when not in operation.

[0193] This definition of "circuit" applies to all uses of the term in this application, including its use in the claims. As a further example, the term "circuit" as used in this application also includes implementations consisting solely of hardware circuitry or a processor (or multiple processors), or a portion thereof, and its accompanying software and / or firmware. Furthermore, the term "circuit" also includes (for example, and where applicable, baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits for servers, cellular network devices, or other computing or network devices.

[0194] The techniques and methods described herein can be implemented in various ways. For example, these techniques can be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or a combination thereof. For hardware implementation, the devices in the exemplary embodiments can be implemented in one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), graphics processing units (GPUs), processors, controllers, microcontrollers, microprocessors, or other electronic units designed to perform the functions described herein, or a combination thereof. For firmware or software implementation, these functions can be implemented through modules (e.g., procedures, functions, etc.) in at least one chipset. Software code can be stored in a storage unit and executed by a processor. The storage unit can be integrated inside the processor or located outside the processor. In the latter case, the storage unit can communicate with the processor in a variety of known ways. Furthermore, to achieve the objectives of the various aspects described herein, the system components described herein can be rearranged and / or supplemented by additional components, which are not limited to the specific structures shown, as will be understood by those skilled in the art.

[0195] It will be apparent to those skilled in the art that the concept of the present invention can be implemented in various ways as technology advances. The embodiments are not limited to the exemplary embodiments described above, but can be modified within the scope of the claims. Therefore, all terms and expressions should be interpreted broadly, and are intended to be illustrative rather than limiting of the embodiments.

Claims

1. An apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by said at least one processor, causing the apparatus to at least: The receiving indication maps uplink control information onto the physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for subband full-duplex SBFD operation; Based on at least one default number of resource blocks or at least one scaling factor, determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel that are within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands. At least one frequency resource range is determined based on the number of resource blocks, and at least one subset of the uplink control information should not be mapped to the at least one frequency resource range; Mapping at least one subset of the uplink control information onto the physical uplink shared channel, such that at least one subset of the uplink control information is not mapped to the at least one frequency resource range; and According to the mapping, the physical uplink shared channel is transmitted in one or more time slots.

2. The apparatus of claim 1, wherein the number of resource blocks is determined based on the at least one default number of resource blocks, the allocated resource blocks of the physical uplink shared channel, and the bandwidth of the uplink subbands allocated to the physical uplink shared channel. The at least one default number of resource blocks includes a default number of resource blocks.

3. The apparatus of claim 1, wherein the at least one default number of resource blocks comprises a plurality of different default numbers for different sets of resource blocks in the uplink subband; The device is further configured to: Based on the allocated resource blocks in the uplink subband of the physical uplink shared channel, a default number of resource blocks is determined from the plurality of different default numbers. The number of resource blocks is determined based on the default number of resource blocks, the allocated resource blocks of the physical uplink shared channel, and the bandwidth of the uplink subband.

4. The apparatus of claim 1, wherein the number of resource blocks is determined by multiplying the number of allocated resource blocks of the physical uplink shared channel by the at least one scaling factor. The at least one scaling factor includes a scaling factor.

5. The apparatus of claim 1, wherein the at least one scaling factor comprises a plurality of different scaling factors for different sets of resource blocks in the uplink subband; The device is further configured to: Based on the allocated resource blocks of the physical uplink shared channel in the uplink subband, a scaling factor is determined from the plurality of different scaling factors. The number of resource blocks is determined by multiplying the number of allocated resource blocks of the physical uplink shared channel by the scaling factor.

6. The apparatus according to any one of claims 2 to 4, further comprising: Determine whether the physical uplink shared channel is allocated on one or more predefined resource block sets within the uplink subband. The number of resource blocks is determined based on the determination that the physical uplink shared channel is allocated on at least one of the one or more predefined resource block sets within the uplink subband.

7. The apparatus of claim 6, wherein the one or more predefined resource block sets comprise at least partially overlapping sets of resource blocks.

8. The apparatus according to any one of claims 2 to 4, further comprising: Determine whether the distance, in units of resource blocks, between the one or more downlink subbands and at least one of the following is less than a threshold: the resource block with the highest resource block index among the resource blocks allocated to the physical uplink shared channel, or the resource block with the lowest resource block index. The number of resource blocks is determined based on the determination that the distance is below the threshold.

9. The apparatus according to any one of the preceding claims, wherein the at least one frequency resource range comprises a frequency resource range corresponding to the bottom or top resource block in the frequency domain of the allocated resource blocks of the physical uplink shared channel.

10. The apparatus according to any one of claims 1 to 8, wherein the at least one frequency resource range comprises two frequency resource ranges. One of the two frequency resource ranges corresponds to the bottom resource block of the allocated resource block in the frequency domain of the physical uplink shared channel. The other of the two frequency resource ranges corresponds to the top resource block in the frequency domain of the allocated resource block of the physical uplink shared channel.

11. The apparatus according to any one of the preceding claims is further configured such that: Map low-priority uplink control information to at least one frequency resource range.

12. The apparatus of claim 11, wherein the low-priority uplink control information includes channel state information portion 2.

13. An apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by said at least one processor, causing the apparatus to at least: Transmit to the user equipment an indication to map uplink control information onto the physical uplink shared channel at one or more timeslots, wherein the one or more timeslots are configured for subband full-duplex SBFD operation; The user equipment is transmitted an indication of at least one default number of resource blocks or at least one scaling factor, wherein the at least one default number of resource blocks or the at least one scaling factor is used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel that are within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands. as well as The user equipment receives the physical uplink shared channel, wherein at least a subset of the uplink control information is mapped onto the physical uplink shared channel. The at least one subset of the uplink control information is not mapped in the number of resource blocks.

14. The apparatus according to claim 13, further comprising: Determine the cross-link interference level associated with the physical uplink shared channel; and Based on the fact that the cross-link interference level is higher than a threshold, a transmission indication is determined to map the uplink control information onto the physical uplink shared channel.

15. An apparatus comprising: A component for receiving an indication to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; A component for determining, based on at least one default number of resource blocks or at least one scaling factor, the number of allocated resource blocks in the physical uplink shared channel within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands; A component for determining at least one frequency resource range based on the number of resource blocks, wherein at least one subset of the uplink control information should not be mapped to the at least one frequency resource range; Components for mapping at least one subset of the uplink control information onto the physical uplink shared channel so that at least one subset of the uplink control information is not mapped to the at least one frequency resource range; as well as A component for transmitting the physical uplink shared channel in one or more time slots according to the mapping.

16. An apparatus comprising: Components for transmitting to a user equipment an indication to map uplink control information onto a physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for sub-band full-duplex SBFD operation; A component for transmitting to the user equipment an indication of at least one default number of resource blocks or at least one scaling factor, wherein the at least one default number of resource blocks or the at least one scaling factor is used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel that are within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands. as well as A component for receiving the physical uplink shared channel from the user equipment, wherein at least a subset of the uplink control information is mapped onto the physical uplink shared channel. The at least one subset of said resources is not mapped in said number of resource blocks.

17. A method comprising: The receiving indication maps uplink control information onto the physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for subband full-duplex SBFD operation; Based on at least one default number of resource blocks or at least one scaling factor, determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel that are within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands. At least one frequency resource range is determined based on the number of resource blocks, and at least one subset of the uplink control information should not be mapped to the at least one frequency resource range; Mapping at least one subset of the uplink control information onto the physical uplink shared channel, such that at least one subset of the uplink control information is not mapped to the at least one frequency resource range; and According to the mapping, the physical uplink shared channel is transmitted in one or more time slots.

18. A method comprising: Transmit to the user equipment an indication to map uplink control information onto the physical uplink shared channel at one or more timeslots, wherein the one or more timeslots are configured for subband full-duplex SBFD operation; The user equipment is transmitted an indication of at least one default number of resource blocks or at least one scaling factor, wherein the at least one default number of resource blocks or the at least one scaling factor is used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel that are within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands. as well as The user equipment receives the physical uplink shared channel, wherein at least a subset of the uplink control information is mapped onto the physical uplink shared channel. The at least one subset of the uplink control information is not mapped in the number of resource blocks.

19. A non-transitory computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the following: The receiving indication maps uplink control information onto the physical uplink shared channel at one or more time slots, wherein the one or more time slots are configured for subband full-duplex SBFD operation; Based on at least one default number of resource blocks or at least one scaling factor, determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel that are within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands. At least one frequency resource range is determined based on the number of resource blocks, and at least one subset of the uplink control information should not be mapped to the at least one frequency resource range; Mapping at least one subset of the uplink control information onto the physical uplink shared channel, such that at least one subset of the uplink control information is not mapped to the at least one frequency resource range; and According to the mapping, the physical uplink shared channel is transmitted in one or more time slots.

20. A non-transitory computer-readable medium comprising program instructions that, when executed by a device, cause the device to perform at least the following: Transmit to the user equipment an indication to map uplink control information onto the physical uplink shared channel at one or more timeslots, wherein the one or more timeslots are configured for subband full-duplex SBFD operation; The user equipment is transmitted an indication of at least one default number of resource blocks or at least one scaling factor, wherein the at least one default number of resource blocks or the at least one scaling factor is used to determine the number of resource blocks in the allocated resource blocks of the physical uplink shared channel that are within a predefined distance in the frequency domain from one or more downlink sub-bands or one or more guard bands. as well as The user equipment receives the physical uplink shared channel, wherein at least a subset of the uplink control information is mapped onto the physical uplink shared channel. The at least one subset of the uplink control information is not mapped in the number of resource blocks.

Images