WO2022205451A1 - Procédé, dispositif et support lisible par ordinateur pour la communication - Google Patents

Procédé, dispositif et support lisible par ordinateur pour la communication Download PDF

Info

Publication number
WO2022205451A1
WO2022205451A1 PCT/CN2021/085384 CN2021085384W WO2022205451A1 WO 2022205451 A1 WO2022205451 A1 WO 2022205451A1 CN 2021085384 W CN2021085384 W CN 2021085384W WO 2022205451 A1 WO2022205451 A1 WO 2022205451A1
Authority
WO
WIPO (PCT)
Prior art keywords
pucch
uplink control
network device
terminal device
repetitions
Prior art date
Application number
PCT/CN2021/085384
Other languages
English (en)
Inventor
Lin Liang
Gang Wang
Original Assignee
Nec Corporation
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 Corporation filed Critical Nec Corporation
Priority to PCT/CN2021/085384 priority Critical patent/WO2022205451A1/fr
Priority to JP2023560830A priority patent/JP2024513419A/ja
Publication of WO2022205451A1 publication Critical patent/WO2022205451A1/fr

Links

Images

Classifications

    • 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 signaling, i.e. of overhead other than pilot signals
    • 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/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0009—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding
    • H04L1/001—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the channel coding applied to control information
    • 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/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • 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/1864—ARQ related signaling
    • 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 signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • 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—Signaling for the administration of the divided path
    • 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
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0072—Error control for data other than payload data, e.g. control data
    • H04L1/0073—Special arrangements for feedback channel
    • 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/004—Arrangements for detecting or preventing errors in the information received by using forward error control
    • H04L1/0075—Transmission of coding parameters to receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunication, and in particular, to methods, devices and computer storage media for adaptive reference signal configuration.
  • repetitions for a single uplink transmission has been proposed.
  • the number of repetitions for the single uplink data transmissions may be semi-static configured. Alternatively, the number of repetitions may be indicated dynamically.
  • a position for transmitting the uplink information is also a key aspect.
  • embodiments of the present disclosure provide methods, devices and computer storage media for physical uplink control channel (PUCCH) repetitions.
  • PUCCH physical uplink control channel
  • a method of communication comprises: receiving, at a terminal device and from a network device, first configuration information of physical uplink control channel (PUCCH) , the first configuration information at least indicating PUCCH repetitions; receiving, from the network device, second configuration information of the PUCCH, the second configuration at least indicating the PUCCH repetitions; and transmitting, to the network device, uplink control information based on the number of the PUCCH repetitions which is determined based on the first configuration information and the second configuration information.
  • PUCCH physical uplink control channel
  • a method of communication comprises: transmitting, at a network device and to a terminal device, first configuration information of physical uplink control channel (PUCCH) , the first configuration information at least indicating PUCCH repetitions; transmitting, to the terminal device, second configuration information of PUCCH, the second configuration information at least indicating the PUCCH repetitions; and receiving, from the terminal device, uplink control information based on the number of the PUCCH repetitions which is determined based on the first configuration information and the second configuration information.
  • PUCCH physical uplink control channel
  • a terminal device comprising a processor and a memory coupled to the processor.
  • the memory stores instructions that when executed by the processor, cause the terminal device to perform: receiving, from a network device, first configuration information of physical uplink control channel (PUCCH) , the first configuration information at least indicating PUCCH repetitions; receiving, from the network device, second configuration information of the PUCCH, the second configuration at least indicating the PUCCH repetitions; and transmitting, to the network device, uplink control information based on the number of the PUCCH repetitions which is determined based on the first configuration information and the second configuration information.
  • PUCCH physical uplink control channel
  • a network device comprising a processor and a memory coupled to the processor.
  • the memory stores instructions that when executed by the processor, cause the network device to perform: transmitting, to a terminal device, first configuration information of physical uplink control channel (PUCCH) , the first configuration information at least indicating PUCCH repetitions; transmitting, to the terminal device, second configuration information of PUCCH, the second configuration information at least indicating the PUCCH repetitions; and receiving, from the terminal device, uplink control information based on the number of the PUCCH repetitions which is determined based on the first configuration information and the second configuration information.
  • PUCCH physical uplink control channel
  • a method of communication comprises: receiving, at a terminal device and from a network device, a radio resource control (RRC) configuration associated with physical uplink control channel (PUCCH) ; and in accordance with a determination that both a PUCCH resource information element and a PUCCH format information element are absent in the RRC configuration, transmitting, to the network device, uplink control information without repetition.
  • RRC radio resource control
  • a method of communication comprises: receiving, at a terminal device and from a network device, a radio resource control (RRC) configuration associated with physical uplink control channel (PUCCH) ; and in accordance with a determination that a PUCCH resource information element is absent but a PUCCH format information element is present in the RRC configuration, transmitting, to the network device, uplink control information based on the number of the PUCCH repetition which is determined based on the PUCCH format information element.
  • RRC radio resource control
  • a method of communication comprises: receiving, at a terminal device and from a network device, a radio resource control (RRC) configuration associated with physical uplink control channel (PUCCH) ; and in accordance with a determination that a PUCCH resource information element is present in the RRC configuration, transmitting, to the network device, uplink control information based on the number of the PUCCH repetition which is determined based on the PUCCH resource information element regardless of a presence or absence of a PUCCH format information element in the RRC configuration.
  • RRC radio resource control
  • a computer readable medium having instructions stored thereon.
  • the instructions when executed on at least one processor, cause the at least one processor to perform the method according to the first aspect, or fifth, or sixth, or seventh of the present disclosure.
  • a computer readable medium having instructions stored thereon.
  • the instructions when executed on at least one processor, cause the at least one processor to perform the method according to the second aspect of the present disclosure.
  • Fig. 1 is a schematic diagram of a communication environment in which embodiments of the present disclosure can be implemented
  • Fig. 2 illustrates a schematic diagram illustrating a process for PUCCH repetitions according to embodiments of the present disclosure
  • Fig. 3 illustrates a schematic diagram illustrating receptions according to embodiments of the present disclosure
  • Fig. 4 illustrates a flow chart of an example method of communication implemented at a terminal device in accordance with some embodiments of the present disclosure
  • Fig. 5 illustrates a flow chart of an example method of communication implemented at a network device in accordance with some embodiments of the present disclosure.
  • Fig. 6 is a simplified block diagram of a device that is suitable for implementing 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, Internet of Everything (IoE) devices, machine type communication (MTC) devices, device on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, or image capture devices such as digital cameras, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like.
  • UE user equipment
  • PDAs personal digital assistants
  • IoT internet of things
  • IoE Internet of Everything
  • MTC machine type communication
  • X means pedestrian, vehicle, or infrastructure/network
  • image capture devices such as digital cameras, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like.
  • terminal device can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.
  • network device refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate.
  • Examples of 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) , a low power node such as a femto node, a pico node, 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
  • a low power node such as a femto node, a pico node, and the like.
  • 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.
  • a first information may be transmitted to the terminal device from the first network device and a 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.
  • resources allocated to PUCCH can be based on a PUCCH resource indicator field in a last downlink control information (DCI) format among multiple DCI formats.
  • the multiple DCI formats can comprise at least one of:a value of a physical downlink shared channel (PDSCH) -to-hybrid automatic repeat request HARQ_feedback timing indicator field, a value of dl-DataToUL-ACK, dl-DataToUL-ACK-r16, or dl-DataToUL-ACKForDCIFormat1_2, which indicate a same slot for the PUCCH transmission that the UE detects and for which the UE transmits corresponding HARQ-ACK information in the PUCCH.
  • detected DCI formats are first indexed in an ascending order across serving cells indexes for a same PDCCH monitoring occasion and are then indexed in an ascending order across PDCCH monitoring occasion indexes.
  • a UE can be configured a number of slots, K , for repetitions of a PUCCH transmission by respective number of slots which is represented as “nrofSlots. ” If a UE is provided a PUCCH configuration that includes a parameter subslotLengthForPUCCH, the UE does not expect the PUCCH configuration to include the parameter nrofSlots.
  • the PUCCH transmission would overlap with the PUSCH transmission in one or more slots.
  • the conditions for multiplexing the UCI in the PUSCH are satisfied in the overlapping slots and the UE transmits the PUCCH and does not transmit the PUSCH in the overlapping slots.
  • a UE does not multiplex different UCI types in a PUCCH transmission with repetitions over K >1 slots. If a UE would transmit a first PUCCH over more than one slot and at least a second PUCCH over one or more slots, the transmissions of the first PUCCH and the second PUCCH would overlap in a number of slots then. For each slot of the number of slots, the UCI type priority of HARQ-ACK is higher than the priority of scheduling request (SR) . The priority of the SR is higher than the priority of CSI with higher priority that is higher than CSI with lower priority.
  • SR scheduling request
  • the UE does not expect the first PUCCH and any of the second PUCCHs to start at a same slot and include a UCI type with same priority. If the first PUCCH and any of the second PUCCHs include a UCI type with same priority, the UE transmits the PUCCH starting at an earlier slot and does not transmit the PUCCH starting at a later slot. If the first PUCCH and any of the second PUCCHs do not include a UCI type with same priority, the UE transmits the PUCCH that includes the UCI type with higher priority and does not transmit the PUCCH that include the UCI type with lower priority.
  • the UE can support to configure static PUCCH repetition and dynamic PUCCH repetition simultaneously.
  • IE PUCCH resource information element
  • nrofSlots in PUCCH format IE are configured.
  • the later DCI overwrites former DCI with different PUCCH repetition factor, the current priority rule for PUCCH repetition seems not to work well.
  • a former DCI in slot m indicates PUCCH feedback on slot n with repetition factor 2
  • a later DCI in slot m+1 indicates PUCCH on the same slot n but change repetition factor into 1
  • another DCI in slot m+2 indicates PUCCH feedback on slot n+1
  • the network expects PUCCH in slot n containing HARQ codebook in slot n and PUCCH in slot n+1 containing HARQ codebook in slot n+1 as PUCCH repetition factor in slot n is 1.
  • the UE miss detects DCI in slot m+1 the UE transmits HARQ codebook in slot n in both PUCCH slot n and n+1 as UE regards PUCCH repetition factor is 2 and drop HARQ codebook in slot n+1 in PUCCH slot n+1 due to current priority rule which is earlier first for same UCI priority.
  • a terminal device receives first configuration information of PUCCH from a network device.
  • the first configuration information at least indicates PUCCH repetitions.
  • the terminal device transmits uplink control information based on the number of PUCCH repetitions which is determined based on the first configuration information. In this way, it can give flexibility of repetition transmission and reduce radio resource signaling (RRC) configuration overhead.
  • RRC radio resource signaling
  • Fig. 1 illustrates a schematic diagram of a communication system in which embodiments of the present disclosure can be implemented.
  • the communication system 100 which is a part of a communication network, comprises a terminal device 110-1, a terminal device 110-2, ..., a terminal device 110-N, which can be collectively referred to as “terminal device (s) 110. ”
  • the number N can be any suitable integer number.
  • the communication system 100 further comprises a network terminal device 120.
  • the network device may be gNB.
  • the network devices 120 and the terminal devices 110 can communicate data and control information to each other.
  • the numbers of terminal devices and network devices shown in Fig. 1 are given for the purpose of illustration without suggesting any limitations.
  • Communications in the communication system 100 may be implemented according to any proper communication protocol (s) , comprising, but not limited to, cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • s cellular communication protocols of the first generation (1G) , the second generation (2G) , the third generation (3G) , the fourth generation (4G) and the fifth generation (5G) and on the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and/or any other protocols currently known or to be developed in the future.
  • IEEE Institute for Electrical and Electronics Engineers
  • the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Divided Multiple Address (CDMA) , Frequency Divided Multiple Address (FDMA) , Time Divided Multiple Address (TDMA) , Frequency Divided Duplexer (FDD) , Time Divided Duplexer (TDD) , Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Divided Multiple Access (OFDMA) and/or any other technologies currently known or to be developed in the future.
  • CDMA Code Divided Multiple Address
  • FDMA Frequency Divided Multiple Address
  • TDMA Time Divided Multiple Address
  • FDD Frequency Divided Duplexer
  • TDD Time Divided Duplexer
  • MIMO Multiple-Input Multiple-Output
  • OFDMA Orthogonal Frequency Divided Multiple Access
  • Embodiments of the present disclosure can be applied to any suitable scenarios.
  • embodiments of the present disclosure can be implemented at reduced capability NR devices.
  • embodiments of the present disclosure can be implemented in one of the followings: NR multiple-input and multiple-output (MIMO) , NR sidelink enhancements, NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz, narrow band-Internet of Thing (NB-IOT) /enhanced Machine Type Communication (eMTC) over non-terrestrial networks (NTN) , NTN, UE power saving enhancements, NR coverage enhancement, NB-IoT and LTE-MTC, Integrated Access and Backhaul (IAB) , NR Multicast and Broadcast Services, or enhancements on Multi-Radio Dual-Connectivity.
  • MIMO multiple-input and multiple-output
  • NR sidelink enhancements NR systems with frequency above 52.6GHz, an extending NR operation up to 71GHz
  • NB-IOT narrow band-Internet of
  • Fig. 2 shows a signaling chart illustrating process 200 among network devices according to some example embodiments of the present disclosure. Only for the purpose of discussion, the process 200 will be described with reference to Fig. 1.
  • the process 200 may involve the terminal device 110-1 and the network device 120 in Fig. 1.
  • the network device 120 may transmit a radio resource control (RRC) configuration associated with physical uplink control channel (PUCCH) to the terminal device 110-1.
  • RRC radio resource control
  • the network device 120 can transmit 2005 a PUCCH format information element in the RRC configuration to the terminal device 110-1.
  • the PUCCH format can indicate a first number of PUCCH repetition slots.
  • the PUCCH format information IE can comprise the parameter subslotLengthForPUCCH. Only as an example, if the subslotLengthForPUCCH indicates the number k, the terminal device 110-1 can transmit the PUCCH over k consecutive subslots. For example, as shown in Fig.
  • the terminal device 110-1 can transmit the PUCCH over the subslots 3010-1, 3010-2, 3010-3 and 3010-4.
  • the terminal device 110-1 can transmit the PUCCH over the subslots 3010-1, 3010-3 and 3010-4.
  • the terminal device 110-1 can transmit over 4 consecutive subslots instead of 4 available subslots. In this way, it can reduce latency of PUCCH repetitions and consistent understanding of an ending position between the network device 120 and the terminal device 110-1 when the terminal device 110-1 misses some signaling.
  • the network device 120 can transmit 2010 a PUCCH resource IE in the RRC configuration to the terminal device 110-1.
  • the PUCCH resource IE can indicate PUCCH repetitions.
  • the repFactor field can be introduced in the PUCCH resource IE to indicate the number of PUCCH repetitions of PUCCH resources.
  • the network device 120 can configure a plurality of PUCCH resources and each of the PUCCH resources can correspond to a number of PUCCH repetitions.
  • the PUCCH resource IE and the PUCCH format IE can be transmitted together or separately.
  • Table 1 below shows an example of RRC IE. It should be noted that table 1 is only an example not limitations.
  • the network device 120 can transmit 2015 downlink control information (DCI) to the terminal device 110-1.
  • DCI downlink control information
  • the DCI can comprise an identity of a resource allocated to the uplink transmission.
  • the terminal device 110-1 can determine 2020 the number of PUCCH repetitions. In an example embodiment, if the PUCCH format IE is present in the RRC configuration and the PUCCH resource IE is absent in the RRC configuration, the terminal device 110-1 can determine the number of PUCCH repetitions based on the PUCCH format IE. In some embodiments, if the PUCCH resource IE element is present in the RRC configuration, the terminal device 110-1 can determine the number of PUCCH repetitions based on the PUCCH resource IE regardless whether the PUCCH format IE is present or not. For example, , the terminal device 110-1 can determine the number of PUCCH repetitions based on the PUCCH resource IE and the identity of the resource indicated in the DCI. In this situation, the terminal device 110-1 can transmit 2025 uplink control information based on the determined number of PUCCH repetitions.
  • r_pucch calculation for PUCCH resource set can be reused other than the first PUCCH resource set to get r_pucch’ .
  • the value r_pucch can be obtained by r_pucch’ %8 and n can be obtained based on FLOOR (r_pucch’ /8) .
  • the terminal device 110-1 can transmit PUCCH repetition using the n-th repetition factor configured by higher layer.
  • the UE determines a PUCCH resource with index r PUCCH , 0 ⁇ r PUCCH ⁇ R PUCCH -1, as
  • N CCE a number of control channel elements (CCEs) in control resource set (CORESET) p of the PDCCH reception for the DCI format
  • n CCE the index of a first CCE for the PDCCH reception
  • the terminal device 110-1 can determine the number of PUCCH repetitions based on the PUCCH format IE.
  • the PUCCH format IE may indicate the number of slots.
  • the terminal device 110-1 can transmit the uplink control formation based on the number of PUCCH repetitions indicated in the PUCCH format IE.
  • the number of PUCCH repetitions in the PUCCH resource IE may have a different priority from the number of PUCCH repetitions in the PUCCH format IE. For example, if the priority of the number of PUCCH repetitions in the PUCCH resource IE is higher, the terminal device 110-1 can transmit the uplink control information based on the number of PUCCH repetitions in the PUCCH resource IE. Alternatively, if the priority of the number of PUCCH repetitions in the PUCCH format IE is higher, the terminal device 110-1 can transmit the uplink control information based on the number of PUCCH repetitions in the PUCCH format IE.
  • the priorities of the PUCCH resource IE and the PUCCH format IE can be pre-configured by the network device 120.
  • the terminal device can transmit the uplink control information without PUCCH repetitions. If the number of PUCCH repetitions is not configured in the PUCCH resource IE or in the PUCCH format IE, the terminal device can transmit the uplink control information without PUCCH repetitions. Alternatively, if the PUCCH resource IE and the PUCCH format IE are absent in the RRC configuration, the terminal device can transmit the uplink control information without PUCCH repetitions.
  • the terminal device 110-1 transmits PUCCH repetition based on this factor; else if network device 120 configures nrofSlots in PUCCH format IE, the terminal device 110-1 transmits PUCCH repetition based on nrofSlots; else, the terminal device 110-1 transmits PUCCH without repetition.
  • the terminal device 110-1 can ignore the number of PUCCH repetitions which is configured in the PUCCH format IE. In some embodiments, if the PUCCH resource IE does not indicate the number of PUCCH repetition, the terminal device 110-1 can determine the number of PUCCH repetitions to be a predetermined number, for example, one. It should be noted that the predetermined number can be any suitable value.
  • the terminal device 110-1 can receive first DCI which indicates a first starting PUCCH slot and second DCI which indicates the first starting PUCCH slot, the terminal device 110-1 can determine that the number of PUCCH repetitions is the same for the first DCI and the second DCI. For example, for dynamic HARQ-ACK PUCCH resource with dynamic PUCCH repetition factor indication in DCI, the terminal device 110-1 can expect the same PUCCH repetition factor for multiple DCIs indicating the same first PUCCH slot.
  • the first PUCCH and any of the second PUCCHs can comprise a UCI type with a same priority.
  • the terminal device 110-1 may not transmit the PUCCH starting at an earlier slot and may transmit the PUCCH starting at a later slot.
  • the terminal device 110-1 may transmit the PUCCH starting at an earlier slot and may not transmit the PUCCH starting at a later slot. In this way, the terminal device can also transmit the right HARQ-ACK codebook on PUCCH slot even the last DIC is missed. Therefore, in case the terminal device misses the last DCI that change/reduce the PUCCH repetition factor, the terminal device could also transmit the right HARQ-ACK codebook on PUCCH slot due to enhanced priority rule.
  • Fig. 4 shows a flowchart of an example method 400 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 400 can be implemented at a terminal device 110-1 as shown in Fig. 1.
  • the terminal device 110-1 receives first configuration information of PUCCH from the network device 120.
  • the first configuration information can be a PUCCH format information element.
  • the PUCCH format can indicate a first number of PUCCH repetition slots.
  • the PUCCH format information IE can comprise the parameter subslotLengthForPUCCH. Only as an example, if the subslotLengthForPUCCH indicates the number k, the terminal device 110-1 can transmit the PUCCH over k consecutive subslots.
  • the first configuration information of PUCCH can be any suitable configuration information associated with the PUCCH.
  • the terminal device 110-1 receives second configuration information of PUCCH from the network device 120.
  • the first configuration information can be a PUCCH resource information element.
  • the PUCCH resource IE can indicate PUCCH repetitions.
  • the repFactor field can be introduced in the PUCCH resource IE to indicate the number of PUCCH repetitions of PUCCH resources.
  • the network device 120 can configure a plurality of PUCCH resources and each of the PUCCH resources can correspond to a number of PUCCH repetitions.
  • the second configuration information of PUCCH can be any suitable configuration information associated with the PUCCH.
  • the terminal device 110-1 can receive DCI from the network device 120.
  • the DCI can comprise an identity of a resource allocated to the uplink transmission.
  • the terminal device 110-1 transmits uplink control information based on the number of PUCCH repetitions which is determined based on the first. In some embodiments, the terminal device 110-1 determines the number of PUCCH repetitions. In some embodiments, the terminal device 110-1 can determine the number of PUCCH repetitions based on the PUCCH resource IE and the identity of the resource indicated in the DCI.
  • the terminal device 110-1 can determine the number of PUCCH repetitions based on the PUCCH format IE.
  • the PUCCH format IE may indicate the number of slots.
  • the terminal device 110-1 can transmit the uplink control formation based on the number of PUCCH repetitions indicated in the PUCCH format IE.
  • the number of PUCCH repetitions in the PUCCH resource IE may have a different priority from the number of PUCCH repetitions in the PUCCH format IE. For example, if the priority of the number of PUCCH repetitions in the PUCCH resource IE is higher, the terminal device 110-1 can transmit the uplink control information based on the number of PUCCH repetitions in the PUCCH resource IE. Alternatively, if the priority of the number of PUCCH repetitions in the PUCCH format IE is higher, the terminal device 110-1 can transmit the uplink control information based on the number of PUCCH repetitions in the PUCCH format IE.
  • the priorities of the PUCCH resource IE and the PUCCH format IE can be pre-configured by the network device 120.
  • the terminal device 110-1 can transmit the uplink control information without PUCCH repetitions. For example, if the number PUCCH repetitions is not configured in the PUCCH resource IE or in the PUCCH format IE, the terminal device 110-1 can transmit the uplink control information without PUCCH repetitions.
  • the terminal device 110-1 can ignore the number of PUCCH repetitions which is configured in the PUCCH format IE. In some embodiments, if the PUCCH resource IE does not indicate the number of PUCCH repetition, the terminal device 110-1 can determine the number of PUCCH repetitions to be a predetermined number, for example, one. It should be noted that the predetermined number can be any suitable value.
  • the terminal device 110-1 can receive first DCI which indicates a first starting PUCCH slot and second DCI which indicates the first starting PUCCH slot, the terminal device 110-1 can determine that the number of PUCCH repetitions is the same for the first DCI and the second DCI. For example, for dynamic HARQ-ACK PUCCH resource with dynamic PUCCH repetition factor indication in DCI, the terminal device 110-1 can expect the same PUCCH repetition factor for multiple DCIs indicating the same first PUCCH slot.
  • the first PUCCH and any of the second PUCCHs can comprise a UCI type with a same priority.
  • the terminal device 110-1 may not transmit the PUCCH starting at an earlier slot and may transmit the PUCCH starting at a later slot.
  • the terminal device 110-1 may transmit the PUCCH starting at an earlier slot and may not transmit the PUCCH starting at a later slot.
  • Fig. 5 shows a flowchart of an example method 500 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 500 can be implemented at a network device 120 as shown in Fig. 1.
  • the network device 120 transmits first configuration information of PUCCH to the terminal device 110-1.
  • the first configuration information can be a PUCCH format information element.
  • the PUCCH format can indicate a first number of PUCCH repetition slots.
  • the PUCCH format information IE can comprise the parameter subslotLengthForPUCCH. Only as an example, if the subslotLengthForPUCCH indicates the number k, the terminal device 110-1 can transmit the PUCCH over k consecutive subslots.
  • the first configuration information of PUCCH can be any suitable configuration information associated with the PUCCH.
  • the network device 120 transmits second configuration information of PUCCH to the terminal device 110-1.
  • the first configuration information can be a PUCCH resource information element.
  • the PUCCH resource IE can indicate PUCCH repetitions.
  • the repFactor field can be introduced in the PUCCH resource IE to indicate the number of PUCCH repetitions of PUCCH resources.
  • the network device 120 can configure a plurality of PUCCH resources and each of the PUCCH resources can correspond to a number of PUCCH repetitions.
  • the second configuration information of PUCCH can be any suitable configuration information associated with the PUCCH.
  • the network device 120 can transmit DCI to the terminal device 110-1.
  • the DCI can comprise an identity of a resource allocated to the uplink transmission.
  • the network device 120 receives uplink control information from the terminal device 110-1 based on the number of PUCCH repetitions which is determined based on the first configuration information. In some embodiments, the terminal device 110-1 determines the number of PUCCH repetitions. In some embodiments, the terminal device 110-1 can determine the number of PUCCH repetitions based on the PUCCH resource IE and the identity of the resource indicated in the DCI.
  • the terminal device 110-1 can determine the number of PUCCH repetitions based on the PUCCH format IE.
  • the PUCCH format IE may indicate the number of slots.
  • the network device 120 can receive the uplink control formation based on the number of PUCCH repetitions indicated in the PUCCH format IE.
  • the number of PUCCH repetitions in the PUCCH resource IE may have a different priority from the number of PUCCH repetitions in the PUCCH format IE. For example, if the priority of the number of PUCCH repetitions in the PUCCH resource IE is higher, the network device 120 can receive the uplink control information based on the number of PUCCH repetitions in the PUCCH resource IE. Alternatively, if the priority of the number of PUCCH repetitions in the PUCCH format IE is higher, the network device 120 can receive the uplink control information based on the number of PUCCH repetitions in the PUCCH format IE.
  • the priorities of the PUCCH resource IE and the PUCCH format IE can be pre-configured by the network device 120.
  • the terminal device 110-2 can transmit the uplink control information without PUCCH repetitions. For example, if the number PUCCH repetitions is not configured in the PUCCH resource IE or in the PUCCH format IE, the network device 120 can receive t the uplink control information without PUCCH repetitions.
  • the first PUCCH and any of the second PUCCHs can comprise a UCI type with a same priority.
  • the network device 120 may not receive the PUCCH starting at an earlier slot and may receive the PUCCH starting at a later slot.
  • the network device 120 may receive the PUCCH starting at an earlier slot and may not receive the PUCCH starting at a later slot.
  • a terminal device comprises circuitry configured to receive, from a network device, first configuration information of physical uplink control channel (PUCCH) , the first configuration information at least indicating PUCCH repetitions; receive, from the network device, second configuration information of the PUCCH, the second configuration at least indicating the PUCCH repetitions and transmit, to the network device, uplink control information based on the number of the PUCCH repetitions which is determined based on the first configuration information and the second configuration information.
  • PUCCH physical uplink control channel
  • the terminal device comprises circuitry configured to receive the first configuration information of PUCCH by: receiving a PUCCH format information element from the network device, the PUCCH format information element indicating the first number of PUCCH repetition slots.
  • the terminal device comprises circuitry configured to receive the second configuration information of PUCCH by receiving a PUCCH resource information element from the network device, the PUCCH resource information element indicating: a plurality of numbers of PUCCH repetitions corresponding to a plurality resources allocated to the PUCCH.
  • the terminal device comprises circuitry configured to receive, from the network device, downlink control information indicating an identity of a resource; and determine the resource from the plurality resources allocated to the PUCCH based on the identity; and wherein the terminal device comprises circuitry configured to transmit the uplink control information by: determining the second number of PUCCH repetitions corresponding to the resource based on the PUCCH resource information element; and transmitting the uplink control information for the second number of PUCCH repetitions.
  • the terminal device comprises circuitry configured to in accordance with a determination that the second number of PUCCH repetitions is determined, ignore the first number of PUCCH repetitions.
  • the terminal device comprises circuitry configured to receive, from the network device, a PUCCH resource information element from the network device; and wherein the terminal device comprises circuitry configured to transmit the uplink control information by: in accordance with a determination that the number of PUCCH repetitions is absent in the PUCCH resource information element, determining the number of PUCCH repetitions to be a predetermined number; and transmitting the uplink control information for the predetermined number.
  • the terminal device comprises circuitry configured to transmit the uplink control information by: transmitting, to the network device, the uplink control information over a number of consecutive subslots, the number of consecutive subslots being same as the number of the PUCCH repetitions.
  • the terminal device comprises circuitry configured to receive, from the network device, first downlink control information indicating a first starting PUCCH slot; and receive, from the network device, second downlink control information indicating the first starting PUCCH slot; and determine the number of PUCCH repetitions being the same for the first downlink control information and the second downlink control information.
  • the terminal device comprises circuitry configured to transmit the uplink control information by: in accordance with a determination that a first starting slot is a dynamic PUCCH repetition including a hybrid automatic repeat request-acknowledgment and a second starting slot is a PUCCH repetition including a hybrid automatic repeat request-acknowledgment and the first starting slot is earlier than the second starting slot, transmitting, to the network device, the uplink control information at the second starting slot; or transmitting, to the network device, the uplink control information at the first starting slot.
  • a terminal device comprises circuitry configured to receive, from a network device, a radio resource control (RRC) configuration associated with physical uplink control channel (PUCCH) ; and in accordance with a determination that both a PUCCH resource information element and a PUCCH format information element are absent in the RRC configuration, transmit, to the network device, uplink control information without repetition.
  • RRC radio resource control
  • a terminal device comprises circuitry configured to receive, at a terminal device and from a network device, a radio resource control (RRC) configuration associated with physical uplink control channel (PUCCH) ; and in accordance with a determination that a PUCCH resource information element is absent but a PUCCH format information element is present in the RRC configuration, transmit, to the network device, uplink control information based on the number of the PUCCH repetition which is determined based on the PUCCH format information element.
  • RRC radio resource control
  • a terminal device comprises circuitry configured to receive, from a network device, a radio resource control (RRC) configuration associated with physical uplink control channel (PUCCH) ; and in accordance with a determination that a PUCCH resource information element is present in the RRC configuration, transmit, to the network device, uplink control information based on the number of the PUCCH repetition which is determined based on the PUCCH resource information element regardless of a presence or absence of a PUCCH format information element in the RRC configuration.
  • RRC radio resource control
  • a network device comprises circuitry configured to transmit, to a terminal device, first configuration information of physical uplink control channel (PUCCH) , the first configuration information at least indicating PUCCH repetitions; transmit, to the terminal device, second configuration information of PUCCH, the second configuration information at least indicating the PUCCH repetitions; and receive, from the terminal device, uplink control information based on the number of the PUCCH repetitions which is determined based at least in part on the configuration information.
  • PUCCH physical uplink control channel
  • the network device comprises circuitry configured to transmit the first configuration information of PUCCH by: transmitting, to the terminal device, a PUCCH format information element, the PUCCH format information element indicating the first number of PUCCH repetition slots.
  • the network device comprises circuitry configured to transmit the second configuration information of PUCCH by transmitting, to the terminal device, a PUCCH resource information element, the PUCCH resource information element indicating: a plurality of numbers of PUCCH repetitions corresponding to a plurality resources allocated to the PUCCH.
  • the network device comprises circuitry configured to transmit, to the terminal device, downlink control information indicating an identity of a resource; and wherein the network device comprises circuitry configured to receive the uplink control information by receiving the uplink control information for a second number of PUCCH repetitions corresponding to the resource which is determined based on the PUCCH resource information element.
  • the network device comprises circuitry configured to transmit, to the terminal device, a PUCCH resource information element; and the network device comprises circuitry configured to receive the uplink control information by in accordance with a determination that the number of PUCCH repetitions is absent in the PUCCH resource information element, receiving the uplink control information for a predetermined number.
  • the network device comprises circuitry configured to receive the uplink control information by receiving, from the terminal device, the uplink control information over a number of consecutive subslots, the number of consecutive subslots being same as the number of the PUCCH repetitions.
  • the network device comprises circuitry configured to transmit the uplink control information by in accordance with a determination that a first starting slot is a dynamic PUCCH repetition including a hybrid automatic repeat request-acknowledgment and a second starting slot is a PUCCH repetition including a hybrid automatic repeat request-acknowledgment and the first starting slot is earlier than the second starting slot, receiving, from the terminal device, the uplink control information at the second starting slot; or receiving, from the terminal device, the uplink control information at the first starting slot.
  • Fig. 6 is a simplified block diagram of a device 600 that is suitable for implementing embodiments of the present disclosure.
  • the device 600 can be considered as a further example implementation of the network device 120 or the terminal device 110 as shown in Fig. 1. Accordingly, the device 600 can be implemented at or as at least a part of the terminal device 110 or the network device 120.
  • the device 600 includes a processor 610, a memory 620 coupled to the processor 610, a suitable transmitter (TX) and receiver (RX) 640 coupled to the processor 610, and a communication interface coupled to the TX/RX 640.
  • the memory 610 stores at least a part of a program 630.
  • the TX/RX 640 is for bidirectional communications.
  • the TX/RX 640 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 interface for bidirectional communications between eNBs, S1 interface for communication between a Mobility Management Entity (MME) /Serving Gateway (S-GW) and the eNB, Un interface for communication between the eNB and a relay node (RN) , or Uu interface for communication between the eNB and a terminal device.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • Un interface for communication between the eNB and a relay node (RN)
  • Uu interface for communication between the eNB and a terminal device.
  • the program 630 is assumed to include program instructions that, when executed by the associated processor 610, enable the device 600 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to Figs. 2-5.
  • the embodiments herein may be implemented by computer software executable by the processor 610 of the device 600, or by hardware, or by a combination of software and hardware.
  • the processor 610 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 610 and memory 620 may form processing means adapted to implement various embodiments of the present disclosure.
  • the memory 620 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 620 is shown in the device 600, there may be several physically distinct memory modules in the device 600.
  • the processor 610 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 600 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.
  • 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, techniques 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 Figs. 1 to 6.
  • 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.

Landscapes

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

Abstract

Des modes de réalisation de la présente divulgation concernent des procédés, des dispositifs et des supports lisibles par ordinateur pour la communication. Selon des modes de réalisation de la présente divulgation, un dispositif terminal reçoit des premières informations de configuration de PUCCH en provenance d'un dispositif de réseau. Les premières informations de configuration Indiquent au moins des répétitions de PUCCH. Le dispositif terminal reçoit, en provenance du dispositif de réseau, des secondes informations de configuration du PUCCH. La seconde configuration indique au moins les répétitions de PUCCH. Le dispositif terminal transmet des informations de commande de liaison montante sur la base du nombre de répétitions de PUCCH qui est déterminé sur la base des premières informations de configuration et des secondes informations de configuration. Il est ainsi possible d'obtenir une flexibilité de la transmission de répétitions et de réduire le surdébit de configuration de signalisation des ressources radio (RRC).
PCT/CN2021/085384 2021-04-02 2021-04-02 Procédé, dispositif et support lisible par ordinateur pour la communication WO2022205451A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2021/085384 WO2022205451A1 (fr) 2021-04-02 2021-04-02 Procédé, dispositif et support lisible par ordinateur pour la communication
JP2023560830A JP2024513419A (ja) 2021-04-02 2021-04-02 通信の方法

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/085384 WO2022205451A1 (fr) 2021-04-02 2021-04-02 Procédé, dispositif et support lisible par ordinateur pour la communication

Publications (1)

Publication Number Publication Date
WO2022205451A1 true WO2022205451A1 (fr) 2022-10-06

Family

ID=83455538

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/085384 WO2022205451A1 (fr) 2021-04-02 2021-04-02 Procédé, dispositif et support lisible par ordinateur pour la communication

Country Status (2)

Country Link
JP (1) JP2024513419A (fr)
WO (1) WO2022205451A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110224796A (zh) * 2018-03-02 2019-09-10 华为技术有限公司 上行控制信息的发送、接收方法和装置
CN111263448A (zh) * 2018-12-29 2020-06-09 维沃移动通信有限公司 信息传输的方法和设备
WO2020145610A1 (fr) * 2019-01-09 2020-07-16 주식회사 케이티 Procédé et dispositif de transmission et de réception d'informations de commande de liaison montante

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110224796A (zh) * 2018-03-02 2019-09-10 华为技术有限公司 上行控制信息的发送、接收方法和装置
CN111263448A (zh) * 2018-12-29 2020-06-09 维沃移动通信有限公司 信息传输的方法和设备
WO2020145610A1 (fr) * 2019-01-09 2020-07-16 주식회사 케이티 Procédé et dispositif de transmission et de réception d'informations de commande de liaison montante

Also Published As

Publication number Publication date
JP2024513419A (ja) 2024-03-25

Similar Documents

Publication Publication Date Title
EP3753327A1 (fr) Procédés et appareils de transmission d'informations de commande de liaison montante
WO2021007862A1 (fr) Rapport de rétroaction harq dans une transmission de liaison latérale
WO2019056164A1 (fr) Procédés et appareils destinés à la transmission d'informations de commande
WO2022021426A1 (fr) Procédé, dispositif et support de stockage informatique de communication
US20230388058A1 (en) Method, device and computer storage medium for communication
WO2021026909A1 (fr) Procédés de communication, dispositifs terminaux et support lisible par ordinateur
JP2023109997A (ja) 方法、端末デバイス、プログラム、及びネットワークデバイス
US20230370209A1 (en) Methods for communications, terminal device, network device and computer readable media
WO2021189320A1 (fr) Procédé, dispositif et support de stockage informatique de communication
AU2019474027B2 (en) Methods, devices and computer readable media for communication on unlicensed band
US20220321306A1 (en) Report of harq feedback in sidelink transmission
WO2022217606A1 (fr) Procédés de communication, dispositif terminal, dispositif réseau et supports lisibles par ordinateur
WO2022016552A1 (fr) Procédés, dispositifs, et support lisible par ordinateur pour une communication
WO2022027645A1 (fr) Support lisible par ordinateur, procédés, et dispositifs de communication
WO2022141647A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2022205451A1 (fr) Procédé, dispositif et support lisible par ordinateur pour la communication
WO2020220229A1 (fr) Rétroaction harq dans une transmission de liaison latérale
WO2023272723A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2022087850A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés à la communication
WO2022000498A1 (fr) Procédés, dispositifs et support lisible par ordinateur relatifs aux communications
WO2022052130A1 (fr) Procédé, dispositif et support lisible par ordinateur destinés à la communication
WO2022193252A1 (fr) Procédés de communication, dispositif terminal, dispositif de réseau et support lisible par ordinateur
WO2022095037A1 (fr) Procédé, dispositif et support de stockage informatique de communication
WO2022193256A1 (fr) Procédés de communication, dispositifs et support lisible par ordinateur
WO2022151096A1 (fr) Procédé, dispositif et support lisible par ordinateur pour des communications

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: 21934108

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023560830

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21934108

Country of ref document: EP

Kind code of ref document: A1