[go: up one dir, main page]

WO2025030515A1 - Dispositif, procédé et support lisible par ordinateur pour les communications - Google Patents

Dispositif, procédé et support lisible par ordinateur pour les communications Download PDF

Info

Publication number
WO2025030515A1
WO2025030515A1 PCT/CN2023/112324 CN2023112324W WO2025030515A1 WO 2025030515 A1 WO2025030515 A1 WO 2025030515A1 CN 2023112324 W CN2023112324 W CN 2023112324W WO 2025030515 A1 WO2025030515 A1 WO 2025030515A1
Authority
WO
WIPO (PCT)
Prior art keywords
sbfd
time unit
uci
uplink
uplink channel
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2023/112324
Other languages
English (en)
Inventor
Xincai LI
Gang Wang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Corp filed Critical NEC Corp
Priority to PCT/CN2023/112324 priority Critical patent/WO2025030515A1/fr
Publication of WO2025030515A1 publication Critical patent/WO2025030515A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1861—Physical mapping arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex

Definitions

  • Embodiments of the present disclosure generally relate to the field of communication, and in particular, to devices, methods and computer readable medium for transmission enhancement.
  • a time unit (for example, a symbol, slot, sub-frame, frame, and so on) can be divided into a plurality of frequency subbands in the frequency domain.
  • the plurality of frequency subbands may be respectively used for different link directions, for example, uplink (UL) or downlink (DL) .
  • This time unit may be also referred to as subband non-overlapping full duplex (SBFD) time unit.
  • SBFD subband non-overlapping full duplex
  • a device for communication for example, a network device or a terminal device
  • UE would transmit multiple overlapping physical uplink control channels (PUCCH) in a slot or overlapping PUCCH (s) and physical uplink shared channels (PUSCH) in a slot.
  • PUCCH physical uplink control channels
  • PUSCH physical uplink shared channels
  • the UE may be configured to multiplex different UCI types in one PUCCH (or one PUSCH) .
  • the UE can multiplex all corresponding UCI types in one uplink channel if certain timing requirements are fulfilled.
  • the SBFD time unit is introduced, the UCI multiplexing procedure can be adapted accordingly.
  • example embodiments of the present disclosure relate to devices, methods, and computer readable medium for transmission enhancement.
  • a terminal device comprising a processor.
  • the processor is configured to cause the terminal device to transmit, to a network device, a first uplink channel within an uplink subband of a first subband non-overlapping full duplex (SBFD) time unit.
  • An SBFD time unit is configured with frequency subbands for different link directions.
  • the terminal device is further caused to transmit a second uplink channel in a first non-SBFD time unit to the network device.
  • a first set of uplink control information (UCI) associated with one of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel.
  • a second set of UCIs associated with the other one of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • UCI uplink control information
  • a network device comprising a processor.
  • the processor is configured to cause the network device to receive, from a terminal device, a first uplink channel within an uplink subband of a first SBFD time unit.
  • An SBFD time unit is configured with frequency subbands for different link directions.
  • the network device is further caused to receive a second uplink channel in a first non-SBFD time unit from a terminal device.
  • a first set of UCIs associated with one of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel.
  • a second set of UCIs associated with the other one of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • a terminal device comprising a processor.
  • the processor is configured to cause the terminal device to determine that one or more UCIs are scheduled to transmit across an SBFD time unit and a non-SBFD time unit.
  • the SBFD time unit is configured with frequency subbands for different link directions.
  • the terminal device is further caused to determine, from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit.
  • the terminal device is further caused to transmit, to a network device, an uplink channel based on the frequency resources.
  • the at least one UCI is multiplexed into the uplink channel.
  • a network device comprising a processor.
  • the processor is configured to cause the network device to determine that one or more UCIs are scheduled to transmit across an SBFD time unit and a non-SBFD time unit.
  • the SBFD time unit is configured with frequency subbands for different link directions.
  • the network device is further caused to determine, from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit.
  • the network device is further caused to receive, from a terminal device, an uplink channel based on the frequency resources.
  • the at least one UCI is multiplexed into the uplink channel.
  • a method implemented at a terminal device transmits, to a network device, a first uplink channel within an uplink subband of a first SBFD time unit.
  • An SBFD time unit is configured with frequency subbands for different link directions.
  • the terminal device further transmits a second uplink channel in a first non-SBFD time unit to the network device.
  • a first set of UCIs associated with one of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel.
  • a second set of UCIs associated with the other one of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • a method implemented at a network device receives, from a terminal device, a first uplink channel within an uplink subband of a first SBFD time unit.
  • An SBFD time unit is configured with frequency subbands for different link directions.
  • the network device further receives a second uplink channel in a first non-SBFD time unit from a terminal device.
  • a first set of UCIs associated with one of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel.
  • a second set of UCIs associated with the other one of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • a method implemented at a terminal device determines that one or more UCIs are scheduled to transmit across an SBFD time unit and a non-SBFD time unit.
  • the SBFD time unit is configured with frequency subbands for different link directions.
  • the terminal device further determines, from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit.
  • the terminal device further transmits, to a network device, an uplink channel based on the frequency resources.
  • the at least one UCI is multiplexed into the uplink channel.
  • the network device determines that one or more UCIs are scheduled to transmit across an SBFD time unit and a non-SBFD time unit.
  • the SBFD time unit is configured with frequency subbands for different link directions.
  • the network device further determines, from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit.
  • the network device further receives, from a terminal device, an uplink channel based on the frequency resources.
  • the at least one UCI is multiplexed into the uplink channel.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method of any of the fifth aspect to the eighth aspect.
  • Fig. 1 illustrates an example environment in which some embodiments of the present disclosure can be implemented
  • Fig. 2 illustrates an example signaling process for UCI multiplexing enhancement according to some embodiments of the present disclosure
  • Fig. 3 illustrates an example of individual UCI multiplexing procedures for the SBFD or non-SBFD time unit according to some embodiments of the present disclosure
  • Fig. 4 illustrates example of UCI multiplexing procedure specific to the SBFD or non-SBFD time unit according to some embodiments of the present disclosure
  • Fig. 5A illustrates an example of an UCI deferment according to some embodiments of the present disclosure
  • Fig. 5B illustrates another example of an UCI adjustment according to some embodiments of the present disclosure
  • Fig. 5C illustrates a further example of an UCI deferment according to some embodiments of the present disclosure
  • Fig. 6 illustrates an example of mapping UCI to an uplink subband of an SBFD time unit according to some embodiments of the present disclosure
  • Fig. 7 illustrates an example of mapping UCI across the SBFD time unit and the non-SBFD time unit according to some embodiments of the present disclosure
  • Fig. 8 illustrates an example of semi-persistent scheduling (SPS) hybrid automatic repeat request (HARQ) -acknowledge (ACK) deferment;
  • SPS semi-persistent scheduling
  • HARQ hybrid automatic repeat request
  • ACK acknowledgenowledge
  • Fig. 9 illustrates an example of SPS HARQ-ACK deferment according to some embodiments of the present disclosure
  • Fig. 10 illustrates another example of SPS HARQ-ACK deferment according to some embodiments of the present disclosure
  • Fig. 11 illustrates a further example of SPS HARQ-ACK deferment according to some embodiments of the present disclosure
  • Fig. 12 illustrates another example signaling process for UCI multiplexing enhancement according to some embodiments of the present disclosure
  • Fig. 13 illustrates an example of a UCI multiplexing procedure crossing the SBFD time unit and the non-SBFD time unit according to some embodiments of the present disclosure
  • Fig. 14 illustrates a flowchart of an example method implemented at a terminal device according to some embodiments of the present disclosure
  • Fig. 15 illustrates a flowchart of an example method implemented at a network device according to some embodiments of the present disclosure
  • Fig. 16 illustrates a flowchart of an example method implemented at a terminal device according to some embodiments of the present disclosure.
  • Fig. 17 illustrates a flowchart of an example method implemented at a network device according to some embodiments of the present disclosure
  • Fig. 18 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure.
  • terminal device refers to any device having wireless or wired communication capabilities.
  • the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Small Data Transmission (SDT) , mobility, Multicast and Broadcast Services (MBS) , positioning, dynamic/flexible duplex in commercial networks, reduced capability (RedCap) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eX
  • UE user equipment
  • the ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may be also incorporated one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM.
  • SIM Subscriber Identity Module
  • the term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal, a wireless device or a reduced capability terminal device.
  • the term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , Network-controlled Repeaters, and the like.
  • NodeB Node B
  • eNodeB or eNB evolved NodeB
  • gNB next generation NodeB
  • TRP transmission reception point
  • RRU remote radio unit
  • RH radio head
  • RRH remote radio head
  • IAB node a
  • the terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.
  • the terminal or the network device may work on several frequency ranges, e.g. FR1 (410 MHz –7125 MHz) , FR2 (24.25 GHz to 71 GHz) , 71 GHz to 114 GHz, and frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum.
  • the terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario.
  • MR-DC Multi-Radio Dual Connectivity
  • the terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.
  • the network device may have the function of network energy saving, Self-Organizing Networks (SON) /Minimization of Drive Tests (MDT) .
  • the terminal may have the function of power saving.
  • test equipment e.g. signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator.
  • the embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future.
  • Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.
  • the terminal device may be connected with a first network device and a second network device.
  • One of the first network device and the second network device may be a master node and the other one may be a secondary node.
  • the first network device and the second network device may use different radio access technologies (RATs) .
  • the first network device may be a first RAT device and the second network device may be a second RAT device.
  • the first RAT device is eNB and the second RAT device is gNB.
  • Information related with different RATs may be transmitted to the terminal device from at least one of the first network device and the second network device.
  • first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device.
  • information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device.
  • Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.
  • the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise.
  • the term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’
  • the term ‘based on’ is to be read as ‘at least in part based on. ’
  • the term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’
  • the term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’
  • the terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.
  • values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • circuitry used herein may refer to hardware circuits and/or combinations of hardware circuits and software.
  • the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware.
  • the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions.
  • the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation.
  • circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.
  • the subband and the frequency subband may be used interchangeable without any limitation.
  • the group size of a RBG may be also referred to as the RBG size without any limitation.
  • the control channel may be interchangeably used with the physical downlink control channel (PDCCH) without any limitation.
  • PDCCH physical downlink control channel
  • the time unit configured with SBFD communication or configuration may be also referred to as SBFD time unit, and the time unit not configured with SBFD communication may be also referred to as non-SBFD time unit.
  • the non-SBFD time unit may comprise UL time unit and/or DL time unit.
  • the time unit may be any time duration, for example, symbol, slot, subframe and frame and so on. Without any limitation, only for illustration purposes, these time scales can be used interchangeably.
  • resource Physical Resource Block (PRB) or resource block” used herein may refer to a resource base unit in the frequency domain.
  • PRB Physical Resource Block
  • SBFD aware UE used herein may refer to the terminal device which obtains the SBFD configuration for time units, for example, the subband division or location of the time units, and supports the SBFD operations with the network device.
  • frequency subband and “subband” can be used interchangeably without any limitation.
  • the frequency subband configured for the uplink communication in the SBFD time unit may be also referred to be as “uplink (UL) subband” .
  • the frequency subband configured for the downlink communication in the SBFD time unit may be also referred to be as “downlink (DL) subband” .
  • the time unit may be any metric of the time domain.
  • the time unit may be a frame, a subframe, a slot, or a symbol.
  • the time unit may be any other time duration.
  • the expression “frequency resources within a subband of the SBFD time unit” only refers that the resources are located within the subband with respect to the frequency domain, however, the time duration of the resources is unnecessary to be limited in the SBFD time unit.
  • the network device may indicate to the terminal devices that some time units are configured as SBFD time units, for example, configuring some DL time units as the SBFD time units.
  • the occasions for transmitting the uplink channel may be increased.
  • the uplink control information (UCI) multiplexing procedure can be adapted to the configured SBFD time units for enhancing the UCI transmission.
  • the example embodiments of the disclosure propose a mechanism for the UCI multiplexing enhancement with respect to the SBFD time unit.
  • a terminal device transmits, within an uplink subband of a first SBFD time unit, a first uplink channel to a network device.
  • the terminal device further transmits a second uplink channel in a first non-SBFD time unit to the network device.
  • a first set of UCIs associated with one (for example, SBFD time units or non-SBFD time units other than the first SBFD time unit) of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel.
  • a second set of UCIs associated with the other one (for example, non-SBFD time units or SBFD time units other than the first non-SBFD time unit) of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • the example embodiments of the disclosure propose a mechanism for the UCI multiplexing enhancement with respect to the SBFD time unit.
  • a terminal device determines that one or more UCIs are scheduled to transmit across an SBFD time unit and a non-SBFD time unit.
  • the SBFD time unit is configured with frequency subbands for different link directions.
  • the terminal device further determines, from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit.
  • the terminal device further transmits, to a network device, an uplink channel based on the frequency resources.
  • the at least one UCI is multiplexed into the uplink channel.
  • the UCI multiplexing procedure can be enhanced with respect to the introduced SBFD time units.
  • the transmission occasions for the UCI may be increased, so that the UCI may be transmitted timely.
  • Fig. 1 illustrates an example environment 100 in which example embodiments of the present disclosure can be implemented.
  • the environment 100 which may be a part of a communication network, comprises a terminal device 110, a network device 120.
  • the communication network may include NTN, NB-IoT and/or eMTC.
  • the communication network may include any other possible communication network. It is to be understood that the number of network devices and terminal devices is given only for the purpose of illustration without suggesting any limitations.
  • the communication network may include any suitable number of network devices and/or terminal devices adapted for implementing embodiments of the present disclosure. Although not shown, it would be appreciated that one or more terminal devices may be located in the environment 100. Without any limitation, the network device 120 supports the SBFD communication.
  • the network device 120 may transmit downlink (DL) channel to the terminal device 110 and receive UL channel from another terminal device 130 in the SBFD time unit, simultaneously.
  • the non-SBFD time unit may be UL only time unit or DL only time unit.
  • Fig. 1 the number of units and other objects in Fig. 1 is provided merely for the purpose of illustration without implying any limitations to the device environment 100.
  • the device environment 100 may include any suitable number of functionality units configured to implement example embodiments of the subject disclosure.
  • one or more terminal devices may be located in the device environment 100.
  • the coordination between the UCI multiplexing procedure and the introduced SBFD time unit can be achieved, and the UCI transmission can be enhanced.
  • Fig. 2 illustrates an example signaling process 200 for UCI multiplexing enhancement according to some embodiments of the present disclosure.
  • the process 200 will be described with reference to Fig. 1.
  • the terminal device 110 transmits (210) a first uplink channel 215 within in an uplink subband of a first subband non-overlapping full duplex (SBFD) time unit to the network device 120.
  • a first set of UCIs associated with one of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel.
  • the first set of UCIs may comprise only one UCI or more than one UCIs.
  • the second SBFD time unit may be any SBFD time unit that the UCI associated with is to be transmitted, and the second non-SBFD time unit may comprise any non-SBFD time unit that the UCI associated with is to be transmitted.
  • one or more UCIs associated with one type of the other SBFD time units or the other non-SBFD time units may be multiplexed into the first uplink channel within the uplink subband of the first SBFD time unit.
  • the first set of UCIs associated with SBFD time units may be multiplexed into the first uplink channel within the uplink subband of the first SBFD time unit.
  • the first set of UCIs associated with non-SBFD time units may be multiplexed into the first uplink channel within the uplink subband of the first SBFD time unit.
  • the first uplink channel 215 may be a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) , for example, a semi-static scheduled PUSCH.
  • the terminal device may multiplex multiple UCIs associated with one type of the SBFD time unit or the non-SBFD time unit into one channel within the uplink subband of the SBFD time unit.
  • the network device 120 receives (220) the first uplink channel 215 from the terminal device 110 accordingly.
  • the terminal device 110 transmits (230) a second uplink channel 235 in a first non-SBFD time unit to the network device 120.
  • a second set of UCIs associated with the other one of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • the set of UCIs may comprise only one UCI type or more than one UCI types.
  • one or more UCIs associated with the other type of the other SBFD time units or the other non-SBFD time units may be multiplexed into the second uplink channel in the second SBFD time unit.
  • the second set of UCIs associated with non-SBFD time units may be multiplexed into the second uplink channel in the first non-SBFD time unit.
  • the first set of UCIs associated with non-SBFD time unit are multiplexed into the first uplink channel
  • the second set of UCIs associated with SBFD time units may be multiplexed into the second uplink channel in the first non-SBFD time unit.
  • the second uplink channel 215 may be also a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH) .
  • the terminal device may multiplex multiple UCIs associated with the other type of the SBFD time unit or the non-SBFD time unit into one channel within the uplink subband of the SBFD time unit.
  • the network device 120 receives (240) the first uplink channel 235 from the terminal device 110 accordingly.
  • the first set of resources for the uplink transmission in the SBFD time unit and the second set of resources for the uplink transmission in the non-SBFD time unit may be individually configured.
  • the network device 120 may transmit a first resource configuration 202 indicating a first set of resources for an uplink channel transmission in the SBFD time unit to the terminal device 110. Then, the terminal device 110 may receive (203) the first resource configuration 202 accordingly.
  • the network device 120 may transmit (204) a second resource configuration 205 indicating a second set of resources for an uplink channel transmission in a non-SBFD time unit. Then, the terminal device 110 may receive (206) the second resource configuration 205 accordingly.
  • the first resource configuration 202 is independent from the second resource configuration 205, and the first set of resources is within an uplink subband of the SBFD time unit for an uplink channel transmission in the SBFD time unit.
  • Fig. 2 shows that the first resource configuration 202 and the second resource configuration 205 are transmitted/received individually, it is to be understood that the first resource configuration 202 and the second resource configuration 205 may be also transmitted/received in the same message or signaling.
  • the terminal device 110 may multiplex (208) one or more UCIs into (or on) the first uplink channel 215 within the uplink subband of the first SBFD time unit or the second uplink channel 235 in the first non-SBFD time unit, as mentioned above. Only for discussion purposes, the multiplexing procedures on the first uplink channel and the second uplink channel are further discussed with reference to Figs. 3 to 11.
  • Fig. 3 illustrates an example of individual UCI multiplexing procedures for the SBFD or non-SBFD time unit according to some embodiments of the present disclosure.
  • the uplink channel resources for the SBFD time unit and the non-SBFD time unit are configured separately.
  • the first set of resources indicated by the first resource configuration 215 may include the resources in the block 330
  • the second set of resources indicated by the second resource configuration 235 may include resources in block 360. It is to be understood that the resources indicated by the first or second resource configuration may be also applied to other SBFD symbols or non-SBFD symbols which are not shown in Fig. 3.
  • PUCCH resource (set) is separately configured for SBFD symbols
  • two PUCCHs can be transmitted in one slot.
  • the PUCCH/PUSCH transmitted on SBFD symbols may only carry the P-CSI report or HARQ-ACK for the scheduled/SPS PDSCH or AP-CSI report transmitted on the SBFD symbols.
  • the PUCCH/PUSCH transmitted on UL only symbols may at least carry the P-CSI report or HARQ-ACK for the scheduled/SPS PDSCH or AP-CSI report transmitted on the DL only symbols. As shown in Fig.
  • the HARQ-ACK feedback for PDSCH 310 and the DCI triggered AP-CSI report 320 transmitted on the SBFD symbols will be transmitted on the PUCCH1 resource 330 on the SBFD UL subband.
  • the HARQ-ACK feedback for PDSCH 340 and DCI triggered AP-CSI report 350 transmitted on the DL only symbols will be transmitted on the PUCCH2 resource 360 in UL only symbols.
  • one or more UCIs associated with non-SBFD time unit may be multiplexed into the second uplink channel in the first non-SBFD time unit.
  • PUCCH resource (set) is separately configured for SBFD symbols
  • two PUCCHs can be transmitted in one slot.
  • the PUCCH/PUSCH transmitted on SBFD symbols may carry the P-CSI report or HARQ-ACK for the scheduled/SPS PDSCH or AP-CSI report transmitted on the DL only symbol.
  • the PUCCH/PUSCH transmitted on UL only symbols may carry the P-CSI report or HARQ-ACK for the scheduled/SPS PDSCH or AP-CSI report transmitted on the SBFD symbols.
  • the HARQ-ACK feedback for PDSCH 310 and the DCI triggered AP-CSI report 320 transmitted on the SBFD symbols will be transmitted on the PUCCH 2 resource 360 on the UL symbols.
  • the HARQ-ACK feedback for PDSCH 340 and DCI triggered AP-CSI report 350 transmitted on the DL only symbols may be transmitted on the PUCCH1 resource 330 within the uplink subband of SBFD symbols. That is, the association between the trigger DCI/PDSCH symbols and the feedback/report symbols and the SBFD time units (or non-SBFD time unit) is not limited.
  • the terminal device 110 may perform (208) , with respect to the UCIs, the multiplexing procedure on the first uplink channel and the second uplink channel.
  • the terminal device 110 may perform a first multiplexing procedure of the first set of UCIs independently from a second multiplexing procedure of the second set of UCIs. Only for discussion clarity, the multiplexing procedure is discussed with reference to Fig. 4.
  • Fig. 4 illustrates example of UCI multiplexing procedure specific to the SBFD or non-SBFD time unit according to some embodiments of the present disclosure.
  • the PUCCH multiplexing procedure may be separately operated for the SBFD symbols and non-SBFD symbols in one slot.
  • the PUCCH 1 410, PUCCH 2 420, PUCCH 3 430, PUCCH 4 430 may be independently multiplexed into one PUCCH (i.e., the first uplink channel) within a UL subband of the SBFD symbols.
  • the PUCCH 5 450, PUCCH 6 460 and PUCCH 7 470 may be independent multiplexed into one PUCCH (i.e., the second uplink channel) in the UL symbols.
  • the transmitted one PUCCH may be determined according to the existing rule.
  • the above embodiment may be also expressed as below.
  • the UCI resource configured in a SBFD time unit may overlap with guardband or downlink subband of this SBFD time unit.
  • the uplink channel for the UCI transmission should be adjusted.
  • the UCI may be multiplexed into an uplink channel in a non-SBFD time unit after this SBFD time unit. Only for discussion purposes, the UCI deferment is further discussed with reference to Fig. 5A.
  • Fig. 5A illustrates an example of an UCI deferment according to some embodiments of the present disclosure.
  • the terminal device 110 may determine that a first UCI 520 to be transmitted in an SBFD time unit (for example, the first SBFD time unit as mentioned above) overlaps with a frequency subband other than one or more uplink subbands of the first SBFD time unit (or is not within the UL subband in the SBFD symbols) . In this case, the terminal device 110 may refrain a transmission of the first UCI in the first SBFD time unit, and multiplex the first UCI on the second uplink channel or on another uplink channel in another non-SBFD time unit.
  • an SBFD time unit for example, the first SBFD time unit as mentioned above
  • the terminal device 110 may refrain a transmission of the first UCI in the first SBFD time unit, and multiplex the first UCI on the second uplink channel or on another uplink channel in another non-SBFD time unit.
  • the UCI carried by this PUCCH 520 may be multiplexed on a PUCCH/PUSCH 530 in the UL only symbols.
  • the PUCCH resources for UCI of the SBFD symbols are not within UL subband, then this UCI can be multiplexed with the HARQ-ACK feedback on one PUCCH/PUSCH in the UL only symbols.
  • the UL only UCI 530 may be dropped if the priority of the type of the UCI 520 is higher than the UL only UCI 530 in UL symbols. Alternatively, if the priority of the type of the UCI 520 is lower than UL only UCI 530 in UL symbols, then the UCI 520 may be dropped. In addition, if the priorities of the UCIs 520 and 530 are the same, then the UCI 520 may be transmitted and the UCI 530 may be dropped.
  • the transmission of UCI may be also adjusted in the SBFD time units themselves.
  • the terminal device 110 may also transmit the above first UCI using frequency resources within the uplink subband of the first SBFD time unit. Only for discussion purposes, this embodiment is further discussed with reference to FIG. 5B.
  • Fig. 5B illustrates another example of an UCI adjustment according to some embodiments of the present disclosure.
  • the PUCCH resources 540 for UCI of the SBFD symbols are not within UL subband of the SBFD symbols.
  • this PUCCH may be transferred to the UL-subband transmission of this SBFD symbols if the UL-subband is configured with PUCCH resource. That is, this PUCCH 540 may transferred to the UL-subband transmission of this SBFD symbols.
  • the priority of the type of the UCI 540 is higher than a UCI in the UL subband, then UCI in the UL subband may be dropped.
  • the priority of the type of the UCI 540 is lower than the UCI in the UL subband, then the UCI 540 may be dropped.
  • the priorities of the UCI 540 and the UCI in the UL subband are the same, then the UCI 540 may be transmitted and the UCI in the UL subband may be dropped.
  • the transmission of UCI may be deferred to the other UL time unit which is not scheduled with uplink channel transmission.
  • the terminal device 110 may transmit the above first UCI in a third non-SBFD time unit which is not scheduled for an uplink transmission. Only for discussion clarity, this embodiment is further discussed with reference to FIG. 5C.
  • Fig. 5C illustrates a further example of an UCI deferment according to some embodiments of the present disclosure.
  • this PUCCH transmission can be deferred to another UL symbols/slot in the case that the other UL symbols/slot is not configured with PUCCH resource.
  • the position of PUCCH resource may be the same with respect to the SBFD symbols/slot and the UL symbols/slot.
  • this PUCCH 550 since the PUCCH resource 550 is not within the UL subband in the SBFD symbols, then this PUCCH 550 may be deferred to the UL only slot/symbols.
  • this embodiment may be also represented as below.
  • the UCI ought to be transmitted on SBFD symbols may be deferred or multiplexed on the PUCCH/PUSCH on UL only symbols. As such, UCI transmission successful probability may be improved.
  • the cross link interference may be occurred since the downlink transmission may be performed simultaneously.
  • the UCI multiplexing procedure on PUSCH may be changed to ensure the UCI transmission robustness.
  • the terminal device 110 may refrain from mapping the UCI into a predefined or configured number of resource blocks adjacent to a boundary of the uplink subband. Only for discussion clarity, the mapping of UCI is further discussed with reference to Fig. 6.
  • Fig. 6 illustrates an example of mapping UCI to an uplink subband of an SBFD time unit according to some embodiments of the present disclosure.
  • the approach of avoiding mapping control bits in the PRBs that are close to DL subbands can help to isolate inter-subband CLI for SBFD aware UE.
  • the frequency widths 610 and 620 may represent the predefined or configured number of resource blocks. That is, the UCI may be mapped to the resources other than frequency widths 610 and 620 within the uplink subband.
  • an example mapping restriction rule for UCI multiplexed on the PUSCH may be as below. If UE is scheduled with PUSCH transmission in SBFD symbols and the UCI is piggybacked on this PUSCH, the UCI may be not mapped to the N PRBs that close to the DL subband/guardband boundary. N is configured by RRC or dynamically indicated in the scheduling DCI, and the candidate value of N may be for example, 1, 2, 3, or 4. Furthermore, N may be related to the size of the inter-subband CLI. In addition or alternatively, if the guardband in the SBFD time unit is small, the candidate value may be configured/indicated larger value. Alternatively, the above embodiment may be also expressed as below.
  • the CLI may be also avoided by adjusting the position of the UCI in the uplink channel in the time domain.
  • a second UCI may be carried by a PUSCH that crosses an SBFD time unit and a non-SBFD time unit.
  • the terminal device 110 may map the UCI to a portion of the PUSCH, and the portion of the PUSCH is in the non-SBFD time unit. Only for discussion purposes, this embodiment is further discussed with reference to Fig. 7.
  • Fig. 7 illustrates an example of mapping UCI across the SBFD time unit and the non-SBFD time unit according to some embodiments of the present disclosure.
  • the UCI may be multiplexed on the portion (which experiences low CLI) of the PUSCH 710 that is not in the SBFD time unit if the PUSCH across the SBFD symbols and non-SBFD symbols transmission.
  • the portion of the PUSCH 710 that is in SBFD symbols may only carry the data.
  • the portion the PUSCH 710 that is in non-SBFD symbols may carry the UCI.
  • the UCI multiplexing method on the non-SBFD symbols may be the same as the existing rule, such as HARQ-ACK piggyback on the nearest symbol of the DMRS, then mapped the CSI part1, and then CSI part2. Only the non-SBFD symbols are considered when calculate UCI occupied RE.
  • the above embodiment may be also expressed as below.
  • mapping criterion for the UCI may be adjusted as below.
  • the UCI may be multiplexed on the non-SBFD symbols with lower interference if one slot includes SBFD symbols and non-SBFD symbols. As such inter-subband CLI for UCI transmission can be reduced and the UCI can be protected.
  • the initial scheduled PUCCH (for example, the second uplink channel 235) may collide with a downlink time unit.
  • the PUCCH may be deferred to UL slot (which may be also referred to be as target PUCCH slot) .
  • UL slot which may be also referred to be as target PUCCH slot
  • the deferment regarding the PUCCH is further discussed with reference to Fig. 8.
  • Fig. 8 illustrates an example of semi-persistent scheduling (SPS) hybrid automatic repeat request (HARQ) -acknowledge (ACK) deferment.
  • SPS semi-persistent scheduling
  • HARQ hybrid automatic repeat request
  • ACK acknowledgenowledge
  • HARQ-ACK deferment has been introduced for SPS PDSCH.
  • UE When a PUCCH for SPS HARQ-ACK overlaps with a semi-static DL symbol, UE will defer the PUCCH until this PUCCH does not overlap with the semi-static DL symbol, as shown in Fig. 8.
  • the PUCCH in the initial PUCCH slot may be deferred to the target PUCCH slot.
  • the SBFD time unit for example, configuring a semi-static DL symbol as the SBFD symbol
  • a UL subband in this semi-static DL symbol can be configured for UL transmission. Therefore, SPS HARQ-ACK deferment can be enhanced.
  • the terminal device 110 may determine that an uplink channel for semi-persistent scheduling (SPS) hybrid automatic request-acknowledge (HARQ-ACK) overlaps with a semi-static downlink time unit. In this case, the terminal device 110 may defer a transmission of the uplink channel for the SPS HARQ-ACK, and transmit the uplink channel for the SPS HARQ-ACK within an uplink subband of a third SBFD time unit after the semi-static downlink symbol. In addition, an interval between the third SBFD time unit and the semi-static downlink symbol may be the shortest among a plurality of SBFD time units or UL time units after the semi-static downlink symbol. Only for discussion purposes, this embodiment is further discussed with reference to Fig. 9.
  • SPS semi-persistent scheduling
  • HARQ-ACK hybrid automatic request-acknowledge
  • Fig. 9 illustrates an example of SPS HARQ-ACK deferment according to some embodiments of the present disclosure.
  • this HARQ-ACK for SPS PDSCH may be transmitted on available SBFD symbols if the PUCCH/PUSCH resource is within the UL subband on this SBFD slot/symbols. In this case, the deferment may be not needed.
  • the HARQ-ACK feedback for SPS PDSCH may be configured to transmit on slot n+3.
  • the slot n+2 is configured as an SBFD slot
  • the PUCCH/PUSCH resource is indicated within the UL subband of the SBFD slot n+2.
  • the HARQ-ACK for this SPS PDSCH may be feedback in the uplink channel within the UL subband of the SBFD slot n+2, in advance.
  • the above embodiment may be also expressed as below.
  • the HARQ-ACK for SPS PDSCH deferred to the third SBFD time unit may collide with some system signaling.
  • the terminal device 110 may determine that the above third SBFD time unit is configured for a synchronization signal block (SSB) transmission or a common search space (CSS) transmission.
  • the terminal device 110 may transmit the uplink channel for the SPS HARQ-ACK in another time unit after the third SBFD time unit. Only for discussion purposes, this embodiment is further discussed with reference to Figs. 10 and 11.
  • Fig. 10 illustrates another example of SPS HARQ-ACK deferment according to some embodiments of the present disclosure.
  • this HARQ-ACK transmission may be deferred to the next available SBFD symbols in the case that the PUCCH/PUSCH resource is within the UL subband of the available SBFD symbols. Without any limitation, this HARQ-ACK transmission may be also deferred to another UL symbol.
  • the HARQ-ACK for SPS PDSCH transmitted in slot n may be deferred to slot n+4.
  • the terminal device 110 may transmit, in slot n+3, the HARQ-ACK initially configured in slot n. This embodiment may be also expressed as below.
  • Fig. 11 illustrates a further example of SPS HARQ-ACK deferment according to some embodiments of the present disclosure.
  • the SPS HARQ-ACK may be deferred to the next available UL slot/flexible slot in the case that the nearest SBFD symbols is not available.
  • the SBFD symbol is less than the number of symbols required for PUCCH.
  • the CORESET/CSS collides with the HARQ-ACK feedback on UL subband in SBFD slot.
  • the terminal device 110 may perform common PDCCH monitoring on slot n+2.
  • the terminal device 110 may defer the HARQ-ACK feedback for SPS PDSCH to slot n+3 which is a flexible slot or UL only slot.
  • UL subband in semi-static DL symbol with SBFD operation can be used for SPS HARQ-ACK transmission.
  • SPS HARQ-ACK feedback delay can be reduced.
  • the multiplexing procedure on the SBFD time unit and non-SBFD time unit may be performed individually.
  • the multiplexing procedure may be also performed across the SBFD time unit and the non-SBFD time unit.
  • the embodiments related to the multiplexing procedure crossing the SBFD time unit and the non-SBFD time unit is further discussed with reference to Figs. 12 and 13.
  • Fig. 12 illustrates another example signaling process 1200 for UCI multiplexing enhancement according to some embodiments of the present disclosure.
  • the process 200 will be described with reference to Fig. 1.
  • the terminal device 110 determines (1210) that one or more UCIs are scheduled to transmit across a SBFD time unit and a non-SBFD time unit. Then, the terminal device 110 determines (1220) , from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit. Similarly, the network device 120 performs the corresponding operations (1240 and 1250) . Then, the terminal device 110 transmits (1230) an uplink channel 1235 to the network device 120. The above determined at least one UCI is multiplexed into the uplink channel 1235. The network device 120 receives (1260) the uplink channel 1235 accordingly.
  • a first set resources an uplink channel transmission in the SBFD time unit and a second set of resources for an uplink channel transmission in a non-SBFD time unit may be configured or indicated commonly.
  • the terminal device 110 may receive a resource configuration comprising a set of common parameters from the network device 120.
  • the set of common parameters indicates a second set of resources for an uplink channel transmission in a non-SBFD time unit.
  • the first set of resources for an uplink channel transmission in the SBFD time unit may be indicated based on the set of common parameters and at least one additional parameter.
  • the at least one additional parameter may be transmitted in the resource configuration.
  • the at least one additional parameter may be also preconfigured or predefined at the terminal device 110. For discussion clarity, the multiplexing procedure is further discussed with reference to Fig. 13.
  • Fig. 13 illustrates an example of a UCI multiplexing procedure crossing the SBFD time unit and the non-SBFD time unit according to some embodiments of the present disclosure.
  • PUCCH or PUSCH transmissions multiplexed with UCIs may cross SBFD symbols and non-SBFD symbols.
  • the SBFD symbols is less than the number of symbols required for PUCCH and the next symbols are UL symbols.
  • the PUCCH or PUSCH transmissions multiplexed with one or more UCIs may cross SBFD symbols and non-SBFD symbols.
  • the PUCCH 1310 for scheduling request and the PUCCH 1320 for HARQ-ACK feedback may be multiplexed into one uplink channel crossing the SBFD symbols and non-SBFD symbols.
  • the multiplexing procedure for PUCCH/PUSCH carrying the UCIs may be performed in the whole slot including the SBFD symbols and UL symbols.
  • the terminal device 110 may drop this PUCCH transmission.
  • the terminal device 110 may also defer this PUCCH transmission.
  • PUCCH resource (set) is separately configured for SBFD symbols, the PUCCH will be cancelled if the SBFD symbols less than the PUCCH symbols number or the PUCCH is not within the UL subband.
  • the above embodiment may be also expressed as below.
  • the terminal device 110 and the second device 120 may also perform the similar operations as discussed with reference to Figs. 2 to 11.
  • the PUCCH transmission may cross SBFD and non-SBFD symbols in one slot. As such, UCI transmission successful probability can be improved.
  • Fig. 14 illustrates a flowchart of a method 1400 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.
  • the method 1400 can be implemented at the terminal device 110 shown in Fig. 1.
  • the method 1400 will be described with reference to Fig. 1. It is to be understood that the method 1400 may include additional acts not shown and/or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
  • the terminal device 110 transmits, to a network device, a first uplink channel within an uplink subband of a first SBFD time unit.
  • An SBFD time unit is configured with frequency subbands for different link directions.
  • the terminal device 110 further transmits a second uplink channel in a first non-SBFD time unit to the network device.
  • a first set of UCIs associated with one of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel.
  • a second set of UCIs associated with the other one of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • the terminal device may further receive, from the network device, a first resource configuration indicating a first set of resources for an uplink channel transmission in the SBFD time unit and a second resource configuration indicating a second set of resources for an uplink channel transmission in a non-SBFD time unit, wherein the first resource configuration is independent from the second resource configuration, and the first set of resources is within an uplink subband of the SBFD time unit for an uplink channel transmission in the SBFD time unit.
  • a first multiplexing procedure of the first set of UCIs is performed independently from a second multiplexing procedure of the second set of UCIs.
  • the terminal device may further determine that a first UCI to be transmitted in the first SBFD time unit overlaps with a frequency subband other than one or more uplink subbands of the first SBFD time unit.
  • the terminal device may further refrain a transmission of the first UCI in the first SBFD time unit; and multiplex the first UCI on the second uplink channel or on another uplink channel in another non-SBFD time unit.
  • the terminal device may further transmit the first UCI using frequency resources within the uplink subband of the first SBFD time unit; and/or transmit the first UCI in a third non-SBFD time unit which is not scheduled for an uplink transmission.
  • the terminal device may further determine that a UCI is to be transmitted within an uplink subband of the SBFD time unit; and refrain from mapping the UCI into a predefined or configured number of resource blocks adjacent to a boundary of the uplink subband.
  • a second UCI is carried by a physical uplink shared channel (PUSCH) that crosses an SBFD time unit and a non-SBFD time unit, and wherein the terminal device may further map the UCI to a portion of the PUSCH, wherein the portion of the PUSCH is in the non-SBFD time unit.
  • PUSCH physical uplink shared channel
  • the terminal device may further determine that an uplink channel for semi-persistent scheduling (SPS) hybrid automatic request-acknowledge (HARQ-ACK) overlaps with a semi-static downlink time unit; defer a transmission of the uplink channel for the SPS HARQ-ACK; and transmit the uplink channel for the SPS HARQ-ACK within an uplink subband of a third SBFD time unit after the semi-static downlink symbol.
  • SPS semi-persistent scheduling
  • HARQ-ACK hybrid automatic request-acknowledge
  • an interval between the third SBFD time unit and the semi-static downlink symbol is shortest among a plurality of SBFD time units or UL time units after the semi-static downlink symbol.
  • the terminal device may further determine that the third SBFD time unit is configured for a synchronization signal block (SSB) transmission or a common search space (CSS) transmission; and transmit the uplink channel for the SPS HARQ-ACK in another time unit after the third SBFD time unit.
  • SSB synchronization signal block
  • CSS common search space
  • Fig. 15 illustrates a flowchart of a method 1500 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 1500 can be implemented at the network device 120 shown in Fig. 1.
  • the method 1500 will be described with reference to Fig. 1. It is to be understood that the method 1500 may include additional acts not shown and/or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
  • the network device 120 receives, from a terminal device, a first uplink channel within an uplink subband of a first SBFD time unit.
  • An SBFD time unit is configured with frequency subbands for different link directions.
  • the network device 120 further receives a second uplink channel in a first non-SBFD time unit from a terminal device.
  • a first set of UCIs associated with one of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel.
  • a second set of UCIs associated with the other one of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • the network device may further transmit, to the terminal device, a first resource configuration for an uplink channel transmission in an SBFD time unit and a second resource configuration for an uplink channel transmission in a non-SBFD time unit, wherein the first resource configuration is independent from the second resource configuration, and wherein the first resource configuration indicates a set of resources within an uplink subband of the SBFD time unit.
  • a first multiplexing procedure of the first set of UCIs is performed independently from a second multiplexing procedure of the second set of UCIs.
  • the network device may further determine that a first UCI to be transmitted in the first SBFD time unit overlaps with a frequency subband other than one or more uplink subbands of the first SBFD time unit.
  • the network device may further refrain a reception of the first UCI in the first SBFD time unit; and receive the first UCI multiplexed on the second uplink channel or on another uplink channel in another non-SBFD time unit.
  • the network device may further receive the first UCI using frequency resources within the uplink subband of the first SBFD time unit; or receive the first UCI in a third non-SBFD time unit which is not scheduled for an uplink transmission.
  • a second UCI is carried by a physical uplink shared channel (PUSCH) that crosses an SBFD time unit and a non-SBFD time unit, and wherein the network device may further receive the UCI mapped to a portion of the PUSCH, wherein the portion of the PUSCH is in the non-SBFD time unit.
  • PUSCH physical uplink shared channel
  • the network device may further determine that an uplink channel for semi-persistent scheduling (SPS) hybrid automatic request-acknowledge (HARQ-ACK) overlaps with a semi-static downlink time unit; defer a reception of the uplink channel for the SPS HARQ-ACK; and receive the uplink channel for the SPS HARQ-ACK within an uplink subband of a third SBFD time unit after the semi-static downlink symbol.
  • SPS semi-persistent scheduling
  • HARQ-ACK hybrid automatic request-acknowledge
  • an interval between the third SBFD time unit and the semi-static downlink symbol is shortest among a plurality of SBFD time units or UL time units after the semi-static downlink symbol.
  • the network device may further determine that the third SBFD time unit is configured for a synchronization signal block (SSB) transmission or a common search space (CSS) transmission; and receive the uplink channel for the SPS HARQ-ACK in another time unit after the third SBFD time unit.
  • SSB synchronization signal block
  • CSS common search space
  • Fig. 16 illustrates a flowchart of a method 1600 of communication implemented at a terminal device in accordance with some embodiments of the present disclosure.
  • the method 1600 can be implemented at the terminal device 110 shown in Fig. 1.
  • the method 1600 will be described with reference to Fig. 1. It is to be understood that the method 1600 may include additional acts not shown and/or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
  • the terminal device 110 determines that one or more UCIs are scheduled to transmit across an SBFD time unit and a non-SBFD time unit.
  • the SBFD time unit is configured with frequency subbands for different link directions.
  • the terminal device 110 further determines, from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit.
  • the terminal device further transmits, to a network device, an uplink channel based on the frequency resources. The at least one UCI is multiplexed into the uplink channel.
  • the terminal device may further receive, from the network device, a resource configuration comprising a set of common parameters, wherein the set of common parameters indicates a second set of resources for an uplink channel transmission in a non-SBFD time unit, and wherein a first set of resources for an uplink channel transmission in the SBFD time unit is indicated based on the set of common parameters and at least one additional parameter.
  • the terminal device may further determine that a first UCI to be transmitted in the SBFD time unit overlaps with a frequency subband other than one or more uplink subbands of the SBFD time unit.
  • the non-SBFD time unit is a first non-SBFD time unit, wherein the terminal device may further refrain a transmission of the first UCI in the SBFD time unit; and multiplex the first UCI on another uplink channel in the first non-SBFD time unit or a second non-SBFD time unit.
  • the non-SBFD time unit is a first non-SBFD time unit, wherein the terminal device may further transmit the first UCI using frequency resources within the uplink subband of the SBFD time unit; or transmit the first UCI in a third non-SBFD time unit which is not scheduled for an uplink transmission.
  • the terminal may further determine that a UCI is to be transmitted within an uplink subband of the SBFD time unit; and refrain from mapping the UCI into a predefined or configured number of resource blocks adjacent to a boundary of the uplink subband.
  • a second UCI is carried by a physical uplink shared channel (PUSCH) that crosses an SBFD time unit and a non-SBFD time unit, and wherein the terminal device may further map the UCI to a portion of the PUSCH, wherein the portion of the PUSCH is in the non-SBFD time unit.
  • PUSCH physical uplink shared channel
  • the terminal device may further determine that an uplink channel for semi-persistent scheduling (SPS) hybrid automatic request-acknowledge (HARQ-ACK) overlaps with a semi-static downlink time unit; defer a transmission of the uplink channel for the SPS HARQ-ACK; and transmit the uplink channel for the SPS HARQ-ACK within an uplink subband of a third SBFD time unit after the semi-static downlink symbol.
  • SPS semi-persistent scheduling
  • HARQ-ACK hybrid automatic request-acknowledge
  • an interval between the further SBFD time unit and the semi-static downlink symbol is shortest among a plurality of SBFD time units or UL time units after the semi-static downlink symbol.
  • the terminal device may further determine that the third SBFD time unit is configured for a synchronization signal block (SSB) transmission or a common search space (CSS) transmission; and transmit the uplink channel for the SPS HARQ-ACK in another time unit after the third SBFD time unit.
  • SSB synchronization signal block
  • CSS common search space
  • Fig. 17 illustrates a flowchart of a method 1700 of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • the method 1700 can be implemented at the network device 120 shown in Fig. 1.
  • the method 1700 will be described with reference to Fig. 1. It is to be understood that the method 1700 may include additional acts not shown and/or may omit some shown acts, and the scope of the present disclosure is not limited in this regard.
  • the network device 120 determines that one or more UCIs are scheduled to transmit across an SBFD time unit and a non-SBFD time unit.
  • the SBFD time unit is configured with frequency subbands for different link directions.
  • the network device 120 further determines, from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit.
  • the network device 120 further receives, from a terminal device, an uplink channel based on the frequency resources. The at least one UCI is multiplexed into the uplink channel.
  • the network device may further transmit, to the terminal device, a resource configuration comprising a set of common parameters, wherein the set of common parameters indicates a second set of resources for an uplink channel transmission in a non-SBFD time unit, and wherein a first set of resources for an uplink channel transmission in the SBFD time unit is indicated based on the set of common parameters and at least one additional parameter.
  • the network device may further determine that a first UCI to be transmitted in the SBFD time unit overlaps with a frequency subband other than one or more uplink subbands of the SBFD time unit.
  • the non-SBFD time unit is a first non-SBFD time unit, wherein the network device may further refrain a transmission of the first UCI in the SBFD time unit; and receive the first UCI multiplexed on another uplink channel in the first non-SBFD time unit or a second non-SBFD time unit.
  • the non-SBFD time unit is a first non-SBFD time unit, wherein the network device may further transmit the first UCI using frequency resources within the uplink subband of the SBFD time unit; or transmit the first UCI in a third non-SBFD time unit which is not scheduled for an uplink transmission.
  • a second UCI is carried by a physical uplink shared channel (PUSCH) that crosses with an SBFD time unit and a non-SBFD time unit, and wherein the network device may further receive the UCI mapped to a portion of the PUSCH, wherein the portion of the PUSCH is in the non-SBFD time unit.
  • PUSCH physical uplink shared channel
  • the network device may further determine that an uplink channel for semi-persistent scheduling (SPS) hybrid automatic request-acknowledge (HARQ-ACK) overlaps with a semi-static downlink time unit; defer a reception of the uplink channel for the SPS HARQ-ACK; and receive the uplink channel for the SPS HARQ-ACK within an uplink subband of a third SBFD time unit after the semi-static downlink symbol.
  • SPS semi-persistent scheduling
  • HARQ-ACK hybrid automatic request-acknowledge
  • an interval between the further SBFD time unit and the semi-static downlink symbol is shortest among a plurality of SBFD time units or UL time units after the semi-static downlink symbol.
  • the network device may further determine that the third SBFD time unit is configured for a synchronization signal block (SSB) transmission or a common search space (CSS) transmission; and receive the uplink channel for the SPS HARQ-ACK in another time unit after the third SBFD time unit.
  • SSB synchronization signal block
  • CSS common search space
  • Fig. 18 is a simplified block diagram of a device 1800 that is suitable for implementing some embodiments of the present disclosure.
  • the device 1800 can be considered as a further example embodiment of the terminal device 110 or network device 120 as shown in Fig. 1. Accordingly, the device 1800 can be implemented at or as at least a part of the above network devices or terminal devices.
  • the device 1800 includes a processor 1810, a memory 1820 coupled to the processor 1810, a suitable transceiver 1840 coupled to the processor 1810, and a communication interface coupled to the transceiver 1840.
  • the memory 1810 stores at least a part of a program 1830.
  • the transceiver 1840 may be for bidirectional communications or a unidirectional communication based on requirements.
  • the transceiver 1840 may include at least one of a transmitter 1842 and a receiver 1844.
  • the transmitter 1842 and the receiver 1844 may be functional modules or physical entities.
  • the transceiver 1840 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones.
  • the communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • RN relay node
  • Uu interface for communication between the eNB/gNB and a terminal device.
  • the program 1830 is assumed to include program instructions that, when executed by the associated processor 1810, enable the device 1800 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to Figs. 1-17.
  • the embodiments herein may be implemented by computer software executable by the processor 1810 of the device 1800, or by hardware, or by a combination of software and hardware.
  • the processor 1810 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 1810 and memory 1820 may form processing means 1850 adapted to implement various embodiments of the present disclosure.
  • the memory 1820 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 1820 is shown in the device 1800, there may be several physically distinct memory modules in the device 1800.
  • the processor 1810 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 1800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • a terminal device comprises circuitry configured to perform a method 1400 or 1600.
  • a network device comprises circuitry configured to perform a method 1500 or 1700.
  • the components included in the apparatuses and/or devices of the present disclosure may be implemented in various manners, including software, hardware, firmware, or any combination thereof.
  • one or more units may be implemented using software and/or firmware, for example, machine-executable instructions stored on the storage medium.
  • parts or all of the units in the apparatuses and/or devices may be implemented, at least in part, by one or more hardware logic components.
  • FPGAs Field-programmable Gate Arrays
  • ASICs Application-specific Integrated Circuits
  • ASSPs Application-specific Standard Products
  • SOCs System-on-a-chip systems
  • CPLDs Complex Programmable Logic Devices
  • various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, technique terminal devices or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to any of Figs. 2 to 17.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types.
  • the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
  • Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.
  • Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
  • the machine readable medium may be a machine readable signal medium or a machine readable storage medium.
  • a machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • machine readable storage medium More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • CD-ROM portable compact disc read-only memory
  • magnetic storage device or any suitable combination of the foregoing.
  • embodiments of the present disclosure may provide the following solutions.
  • a terminal device comprising: a processor, and the processor is configured to cause the terminal device to: transmit, to a network device, a first uplink channel within an uplink subband of a first subband non-overlapping full duplex (SBFD) time unit, wherein an SBFD time unit is configured with frequency subbands for different link directions; and transmit, to the network device, a second uplink channel in a first non-SBFD time unit, wherein a first set of uplink control information (UCI) associated with one of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel, and wherein a second set of UCIs associated with the other one of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • UCI uplink control information
  • the terminal device is further caused to: receive, from the network device, a first resource configuration indicating a first set of resources for an uplink channel transmission in the SBFD time unit and a second resource configuration indicating a second set of resources for an uplink channel transmission in a non-SBFD time unit, wherein the first resource configuration is independent from the second resource configuration, and the first set of resources is within an uplink subband of the SBFD time unit for an uplink channel transmission in the SBFD time unit.
  • a first multiplexing procedure of the first set of UCIs is performed independently from a second multiplexing procedure of the second set of UCIs.
  • the terminal device is further caused to: determine that a first UCI to be transmitted in the first SBFD time unit overlaps with a frequency subband other than one or more uplink subbands of the first SBFD time unit.
  • the terminal device is further caused to: refrain a transmission of the first UCI in the first SBFD time unit; and multiplex the first UCI on the second uplink channel or on another uplink channel in another non-SBFD time unit.
  • the terminal device is further caused to at least one of:transmit the first UCI using frequency resources within the uplink subband of the first SBFD time unit; or transmit the first UCI in a third non-SBFD time unit which is not scheduled for an uplink transmission.
  • the terminal device is further caused to: determine that a UCI is to be transmitted within an uplink subband of the SBFD time unit; and refrain from mapping the UCI into a predefined or configured number of resource blocks adjacent to a boundary of the uplink subband.
  • a second UCI is carried by a physical uplink shared channel (PUSCH) that crosses an SBFD time unit and a non-SBFD time unit
  • PUSCH physical uplink shared channel
  • the terminal device is further caused to: map the UCI to a portion of the PUSCH, wherein the portion of the PUSCH is in the non-SBFD time unit.
  • the terminal device is further caused to: determine that an uplink channel for semi-persistent scheduling (SPS) hybrid automatic request-acknowledge (HARQ-ACK) overlaps with a semi-static downlink time unit; defer a transmission of the uplink channel for the SPS HARQ-ACK; and transmit the uplink channel for the SPS HARQ-ACK within an uplink subband of a third SBFD time unit after the semi-static downlink symbol.
  • SPS semi-persistent scheduling
  • HARQ-ACK hybrid automatic request-acknowledge
  • an interval between the third SBFD time unit and the semi-static downlink symbol is shortest among a plurality of SBFD time units or UL time units after the semi-static downlink symbol.
  • the terminal device is further caused to: determine that the third SBFD time unit is configured for a synchronization signal block (SSB) transmission or a common search space (CSS) transmission; and transmit the uplink channel for the SPS HARQ-ACK in another time unit after the third SBFD time unit.
  • SSB synchronization signal block
  • CSS common search space
  • a network device comprising: a processor, and the processor is configured to cause the network device to: receive, from a terminal device, a first uplink channel within an uplink subband of a first subband non-overlapping full duplex (SBFD) time unit, wherein an SBFD time unit is configured with frequency subbands for different link directions; and receive, from a terminal device, a second uplink channel in a first non-SBFD time unit, wherein a first set of uplink control information (UCI) associated with one of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel, and wherein a second set of UCIs associated with the other one of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • UCI uplink control information
  • the network device is further caused to: transmit, to the terminal device, a first resource configuration for an uplink channel transmission in an SBFD time unit and a second resource configuration for an uplink channel transmission in a non-SBFD time unit, wherein the first resource configuration is independent from the second resource configuration, and wherein the first resource configuration indicates a set of resources within an uplink subband of the SBFD time unit.
  • a first multiplexing procedure of the first set of UCIs is performed independently from a second multiplexing procedure of the second set of UCIs.
  • the network device is further caused to: determine that a first UCI to be transmitted in the first SBFD time unit overlaps with a frequency subband other than one or more uplink subbands of the first SBFD time unit.
  • the network device is further caused to: refrain a reception of the first UCI in the first SBFD time unit; and receive the first UCI multiplexed on the second uplink channel or on another uplink channel in another non-SBFD time unit.
  • the network device is further caused to: receive the first UCI using frequency resources within the uplink subband of the first SBFD time unit; or receive the first UCI in a third non-SBFD time unit which is not scheduled for an uplink transmission.
  • a second UCI is carried by a physical uplink shared channel (PUSCH) that crosses an SBFD time unit and a non-SBFD time unit
  • PUSCH physical uplink shared channel
  • the network device is further caused to: receive the UCI mapped to a portion of the PUSCH, wherein the portion of the PUSCH is in the non-SBFD time unit.
  • the network device is further caused to: determine that an uplink channel for semi-persistent scheduling (SPS) hybrid automatic request-acknowledge (HARQ-ACK) overlaps with a semi-static downlink time unit; defer a reception of the uplink channel for the SPS HARQ-ACK; and receive the uplink channel for the SPS HARQ-ACK within an uplink subband of a third SBFD time unit after the semi-static downlink symbol.
  • SPS semi-persistent scheduling
  • HARQ-ACK hybrid automatic request-acknowledge
  • an interval between the third SBFD time unit and the semi-static downlink symbol is shortest among a plurality of SBFD time units or UL time units after the semi-static downlink symbol.
  • the network device is further caused to: determine that the third SBFD time unit is configured for a synchronization signal block (SSB) transmission or a common search space (CSS) transmission; and receive the uplink channel for the SPS HARQ-ACK in another time unit after the third SBFD time unit.
  • SSB synchronization signal block
  • CSS common search space
  • a terminal device comprising: a processor, and the processor is configured to cause the terminal device to: determine that one or more uplink control information (UCI) are scheduled to transmit across a subband non-overlapping full duplex (SBFD) time unit and a non-SBFD time unit, wherein the SBFD time unit is configured with frequency subbands for different link directions; determine, from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit; and transmit, to a network device, an uplink channel based on the frequency resources, wherein the at least one UCI is multiplexed into the uplink channel.
  • UCI uplink control information
  • the terminal device is further caused to: receive, from the network device, a resource configuration comprising a set of common parameters, wherein the set of common parameters indicates a second set of resources for an uplink channel transmission in a non-SBFD time unit, and wherein a first set of resources for an uplink channel transmission in the SBFD time unit is indicated based on the set of common parameters and at least one additional parameter.
  • the terminal device is further caused to: determine that a first UCI to be transmitted in the SBFD time unit overlaps with a frequency subband other than one or more uplink subbands of the SBFD time unit.
  • non-SBFD time unit is a first non-SBFD time unit
  • the terminal device is further caused to: refrain a transmission of the first UCI in the SBFD time unit; and multiplex the first UCI on another uplink channel in the first non-SBFD time unit or a second non-SBFD time unit.
  • non-SBFD time unit is a first non-SBFD time unit
  • the terminal device is further caused to: transmit the first UCI using frequency resources within the uplink subband of the SBFD time unit; or transmit the first UCI in a third non-SBFD time unit which is not scheduled for an uplink transmission.
  • the terminal is further caused to: determine that a UCI is to be transmitted within an uplink subband of the SBFD time unit; and refrain from mapping the UCI into a predefined or configured number of resource blocks adjacent to a boundary of the uplink subband.
  • a second UCI is carried by a physical uplink shared channel (PUSCH) that crosses an SBFD time unit and a non-SBFD time unit
  • PUSCH physical uplink shared channel
  • the terminal device is further caused to: map the UCI to a portion of the PUSCH, wherein the portion of the PUSCH is in the non-SBFD time unit.
  • the terminal device is further caused to: determine that an uplink channel for semi-persistent scheduling (SPS) hybrid automatic request-acknowledge (HARQ-ACK) overlaps with a semi-static downlink time unit; defer a transmission of the uplink channel for the SPS HARQ-ACK; and transmit the uplink channel for the SPS HARQ-ACK within an uplink subband of a third SBFD time unit after the semi-static downlink symbol.
  • SPS semi-persistent scheduling
  • HARQ-ACK hybrid automatic request-acknowledge
  • an interval between the further SBFD time unit and the semi-static downlink symbol is shortest among a plurality of SBFD time units or UL time units after the semi-static downlink symbol.
  • the terminal device is further caused to: determine that the third SBFD time unit is configured for a synchronization signal block (SSB) transmission or a common search space (CSS) transmission; and transmit the uplink channel for the SPS HARQ-ACK in another time unit after the third SBFD time unit.
  • SSB synchronization signal block
  • CSS common search space
  • a network device comprising: a processor, and the processor is configured to cause the network device to: determine that one or more uplink control information (UCI) are scheduled to transmit across a subband non-overlapping full duplex (SBFD) time unit and a non-SBFD time unit, wherein the SBFD time unit is configured with frequency subbands for different link directions; determine, from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit; and receive, from a terminal device, an uplink channel based on the frequency resources, wherein the at least one UCI is multiplexed into the uplink channel.
  • UCI uplink control information
  • the network device is further caused to: transmit, to the terminal device, a resource configuration comprising a set of common parameters, wherein the set of common parameters indicates a second set of resources for an uplink channel transmission in a non-SBFD time unit, and wherein a first set of resources for an uplink channel transmission in the SBFD time unit is indicated based on the set of common parameters and at least one additional parameter.
  • the network device is further caused to: determine that a first UCI to be transmitted in the SBFD time unit overlaps with a frequency subband other than one or more uplink subbands of the SBFD time unit.
  • non-SBFD time unit is a first non-SBFD time unit
  • the network device is further caused to: refrain a transmission of the first UCI in the SBFD time unit; and receive the first UCI multiplexed on another uplink channel in the first non-SBFD time unit or a second non-SBFD time unit.
  • non-SBFD time unit is a first non-SBFD time unit
  • the network device is further caused to: transmit the first UCI using frequency resources within the uplink subband of the SBFD time unit; or transmit the first UCI in a third non-SBFD time unit which is not scheduled for an uplink transmission.
  • a second UCI is carried by a physical uplink shared channel (PUSCH) that crosses with an SBFD time unit and a non-SBFD time unit
  • PUSCH physical uplink shared channel
  • the network device is further caused to: receive the UCI mapped to a portion of the PUSCH, wherein the portion of the PUSCH is in the non-SBFD time unit.
  • the network device is further caused to: determine that an uplink channel for semi-persistent scheduling (SPS) hybrid automatic request-acknowledge (HARQ-ACK) overlaps with a semi-static downlink time unit; defer a reception of the uplink channel for the SPS HARQ-ACK; and receive the uplink channel for the SPS HARQ-ACK within an uplink subband of a third SBFD time unit after the semi-static downlink symbol.
  • SPS semi-persistent scheduling
  • HARQ-ACK hybrid automatic request-acknowledge
  • an interval between the further SBFD time unit and the semi-static downlink symbol is shortest among a plurality of SBFD time units or UL time units after the semi-static downlink symbol.
  • the network device is further caused to: determine that the third SBFD time unit is configured for a synchronization signal block (SSB) transmission or a common search space (CSS) transmission; and receive the uplink channel for the SPS HARQ-ACK in another time unit after the third SBFD time unit.
  • SSB synchronization signal block
  • CSS common search space
  • a method of communication comprising: transmitting, at a terminal device and to a network device, a first uplink channel within an uplink subband of a first subband non-overlapping full duplex (SBFD) time unit, wherein an SBFD time unit is configured with frequency subbands for different link directions; and transmitting, to the network device, a second uplink channel in a first non-SBFD time unit, wherein a first set of uplink control information (UCI) associated with one of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel, and wherein a second set of UCIs associated with the other one of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • UCI uplink control information
  • a method of communication comprising: receiving, at a network device and from a terminal device, a first uplink channel within an uplink subband of a first subband non-overlapping full duplex (SBFD) time unit, wherein an SBFD time unit is configured with frequency subbands for different link directions; and receiving, from a terminal device, a second uplink channel in a first non-SBFD time unit, wherein a first set of uplink control information (UCI) associated with one of a second SBFD time unit or a second non-SBFD time unit is multiplexed into the first uplink channel, and wherein a second set of UCIs associated with the other one of the second SBFD time unit or the second non-SBFD time unit is multiplexed into the second uplink channel.
  • UCI uplink control information
  • a method of communication comprising: determining, at a terminal device, that one or more uplink control information (UCI) are scheduled to transmit across a subband non-overlapping full duplex (SBFD) time unit and a non-SBFD time unit, wherein the SBFD time unit is configured with frequency subbands for different link directions; determining, from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit; and transmitting, to a network device, an uplink channel based on the frequency resources, wherein the at least one UCI is multiplexed into the uplink channel.
  • UCI uplink control information
  • a method of communication comprising: determining, at a network device, that one or more uplink control information (UCI) are scheduled to transmit across a subband non-overlapping full duplex (SBFD) time unit and a non-SBFD time unit, wherein the SBFD time unit is configured with frequency subbands for different link directions; determining, from the one or more UCIs, at least one UCI that is scheduled on frequency resources within an uplink subband of the SBFD time unit; and receiving, from a terminal device, an uplink channel based on the frequency resources, wherein the at least one UCI is multiplexed into the uplink channel.
  • UCI uplink control information
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method according to any of the above methods.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation concernent des dispositifs, des procédés et un support lisible par ordinateur pour une amélioration de transmission. Selon des modes de réalisation de la présente divulgation, un dispositif terminal transmet, à un dispositif réseau, un premier canal de liaison montante dans une sous-bande de liaison montante d'une première unité de temps SBFD. Une unité de temps SBFD est configurée avec des sous-bandes de fréquence pour différentes directions de liaison. Le dispositif terminal transmet également un second canal de liaison montante dans une première unité de temps non SBFD au dispositif réseau. Un premier ensemble d'UCI associées à l'une de la seconde unité de temps SBFD et de la seconde unité de temps non SBFD est multiplexé dans le premier canal de liaison montante. Un second ensemble d'UCI associées à l'autre de la seconde unité de temps SBFD et de la seconde unité de temps non SBFD est multiplexé dans le second canal de liaison montante. De cette manière, le multiplexage des UCI peut être adaptée ou coordonné avec le mécanisme SBFD.
PCT/CN2023/112324 2023-08-10 2023-08-10 Dispositif, procédé et support lisible par ordinateur pour les communications Pending WO2025030515A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/112324 WO2025030515A1 (fr) 2023-08-10 2023-08-10 Dispositif, procédé et support lisible par ordinateur pour les communications

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/112324 WO2025030515A1 (fr) 2023-08-10 2023-08-10 Dispositif, procédé et support lisible par ordinateur pour les communications

Publications (1)

Publication Number Publication Date
WO2025030515A1 true WO2025030515A1 (fr) 2025-02-13

Family

ID=94533336

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/112324 Pending WO2025030515A1 (fr) 2023-08-10 2023-08-10 Dispositif, procédé et support lisible par ordinateur pour les communications

Country Status (1)

Country Link
WO (1) WO2025030515A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230007641A1 (en) * 2021-06-30 2023-01-05 Electronics And Telecommunications Research Institute Method and apparatus for subband duplex operation
US20230180166A1 (en) * 2021-12-08 2023-06-08 Samsung Electronics Co., Ltd. Method and apparatus for transmission timing using timing advance in full-duplex systems

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230007641A1 (en) * 2021-06-30 2023-01-05 Electronics And Telecommunications Research Institute Method and apparatus for subband duplex operation
US20230180166A1 (en) * 2021-12-08 2023-06-08 Samsung Electronics Co., Ltd. Method and apparatus for transmission timing using timing advance in full-duplex systems

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Discussion on potential enhancement on subband non-overlapping full duplex", 3GPP DRAFT; R1-2302348, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 7 April 2023 (2023-04-07), XP052351832 *
PRAVJYOT SINGH DEOGUN, NEC: "Discussion on subband non-overlapping full duplex", 3GPP DRAFT; R1-2302746; TYPE DISCUSSION; FS_NR_DUPLEX_EVO, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), 6 April 2023 (2023-04-06), XP052293322 *

Similar Documents

Publication Publication Date Title
WO2023044912A1 (fr) Procédé, dispositif et support de stockage informatique pour la communication
WO2024192688A1 (fr) Dispositif, procédé et support lisible par ordinateur pour communication
WO2024060246A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2024007314A1 (fr) Procédés, dispositifs et support destinés aux communications
WO2023150981A1 (fr) Procédés, dispositifs, et support lisible par ordinateur pour des communications
WO2025010546A1 (fr) Dispositif, procédé et support lisible par ordinateur pour les communications
WO2024212117A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2023184273A1 (fr) Procédé, dispositif, et support de stockage informatique destinés à la communication
WO2025030515A1 (fr) Dispositif, procédé et support lisible par ordinateur pour les communications
WO2025091391A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2025118281A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2024130610A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés à des communications
WO2025030330A1 (fr) Dispositif, procédé et support lisible par ordinateur pour les communications
WO2025065189A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2024152214A1 (fr) Dispositif, procédé et support lisible par ordinateur pour configuration de ressources de liaison radio
WO2025260256A1 (fr) Dispositif, procédé et support lisible par ordinateur pour communication
WO2025152159A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2025199686A1 (fr) Dispositif, procédé et support lisible par ordinateur pour des communications
WO2024168736A1 (fr) Dispositifs et procédés de communication
WO2024065771A1 (fr) Procédés, dispositifs et support de communication
WO2023168610A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la gestion d'interférence de liaison croisée
WO2024098192A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés aux communications
WO2025156117A1 (fr) Dispositifs, procédés, et support de communication
WO2025208363A1 (fr) Dispositifs et procédés de communication
WO2023245510A1 (fr) Procédés, dispositifs et support de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23948087

Country of ref document: EP

Kind code of ref document: A1