WO2022016552A1 - Procédés, dispositifs, et support lisible par ordinateur pour une communication - Google Patents

Procédés, dispositifs, et support lisible par ordinateur pour une communication Download PDF

Info

Publication number
WO2022016552A1
WO2022016552A1 PCT/CN2020/104603 CN2020104603W WO2022016552A1 WO 2022016552 A1 WO2022016552 A1 WO 2022016552A1 CN 2020104603 W CN2020104603 W CN 2020104603W WO 2022016552 A1 WO2022016552 A1 WO 2022016552A1
Authority
WO
WIPO (PCT)
Prior art keywords
repetitions
data transmission
downlink data
terminal device
transmitting
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.)
Ceased
Application number
PCT/CN2020/104603
Other languages
English (en)
Inventor
Gang Wang
Yukai GAO
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/CN2020/104603 priority Critical patent/WO2022016552A1/fr
Publication of WO2022016552A1 publication Critical patent/WO2022016552A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/08Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/1607Details of the supervisory signal
    • H04L1/1614Details of the supervisory signal using bitmaps
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829Arrangements specially adapted for the receiver end
    • H04L1/1854Scheduling and prioritising arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829Arrangements specially adapted for the receiver end
    • H04L1/1861Physical mapping arrangements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • H04L1/1896ARQ related signaling
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00Arrangements affording multiple use of the transmission path
    • H04L5/003Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053Allocation of signalling, i.e. of overhead other than pilot signals
    • H04L5/0055Physical resource allocation for ACK/NACK
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W72/00Local resource management
    • H04W72/20Control channels or signalling for resource management
    • H04W72/21Control 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 readable medium for communication.
  • Scheduling is a process of allocation resources for transmission.
  • There may be different types of scheduling for example, dynamic scheduling, semi-persistent scheduling (SPS) and the like.
  • SPS can be configured only in the uplink, or in the downlink (sps-ConfigDL) or in both directions.
  • Configuration of SPS doesn’t mean that the terminal device can start using SPS grants/assignments.
  • the network device has to explicitly activate SPS as explained in order for the UE to use SPS grants/assignments.
  • the terminal device can transmit a feedback for the downlink data transmission. A position for transmitting the feedback is a key aspect for the SPS scheduling.
  • example embodiments of the present disclosure provide a solution for communication.
  • a method for communication comprises: receiving, at a terminal device and from a network device, downlink data transmission which is semi-persistent configured, the downlink data transmission having a plurality of repetitions; determining the number of repetitions for the downlink data transmission; and transmitting, to the network device, a feedback for the repetitions for the downlink data transmission based on the number of the repetitions.
  • the communication method comprises transmitting, at a network device and to a terminal device, downlink data transmission which is semi-persistent configured, the downlink data transmission having a plurality of repetitions; and receiving, from the terminal device, a feedback for the repetitions for the downlink data transmission based on the number of repetitions.
  • a terminal device comprising a processing unit; and a memory coupled to the processing unit and storing instructions thereon, the instructions, when executed by the processing unit, causing the terminal device to perform acts comprising: receiving, from a network device, downlink data transmission which is semi-persistent configured, the downlink data transmission having a plurality of repetitions; determining the number of repetitions for the downlink data transmission; and transmitting, to the network device, a feedback for the repetitions for the downlink data transmission based on the number of the repetitions.
  • a network device comprising a processing unit; and a memory coupled to the processing unit and storing instructions thereon, the instructions, when executed by the processing unit, causing the network device to perform acts comprising: transmitting, to a terminal device, downlink data transmission which is semi-persistent configured, the downlink data transmission having a plurality of repetitions; and receiving, from the terminal device, a feedback for the repetitions for the downlink data transmission based on the number of repetitions.
  • a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to any one of the first aspect or second aspect.
  • Fig. 1 is a schematic diagram of a communication environment in which embodiments of the present disclosure can be implemented
  • Fig. 2 illustrates a signaling flow for preventing frequent handover and/or cell re-selection according to some embodiments of the present disclosure
  • Fig. 3 illustrates a simplified block diagram of position determination according to some embodiments of the present disclosure
  • Figs. 4A-4D illustrate simplified block diagrams of position determination according to some embodiments of the present disclosure
  • Figs. 5A-5B illustrate simplified block diagrams of TCI determination according to some embodiments of the present disclosure
  • Fig. 6 is a flowchart of an example method in accordance with an embodiment of the present disclosure.
  • Fig. 7 is a flowchart of an example method in accordance with an embodiment of the present disclosure.
  • Fig. 8 is a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • 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 NodeB in new radio access (gNB) 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, a satellite network device, an aircraft network device, and the like.
  • NodeB Node B
  • eNodeB or eNB Evolved NodeB
  • gNB NodeB in new radio access
  • RRU Remote Radio Unit
  • RH radio head
  • RRH remote radio head
  • a low power node such as a femto node, a pico node, a satellite network
  • terminal device refers to any device having wireless or wired communication capabilities.
  • Examples of 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
  • Communications discussed herein may use conform to any suitable standards including, but not limited to, New Radio Access (NR) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , cdma2000, and Global System for Mobile Communications (GSM) and the like.
  • NR New Radio Access
  • LTE Long Term Evolution
  • LTE-A LTE-Evolution
  • WCDMA Wideband Code Division Multiple Access
  • CDMA Code Division Multiple Access
  • GSM Global System for Mobile Communications
  • the communications 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.85G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols.
  • the techniques described herein may be used for the
  • 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.
  • the minimum period for SPS is 10ms.
  • multiple SPS configurations are allowed per BWP per serving cell.
  • the minimum period for SPS is 1 slot.
  • only slot-based hybrid automatic repeat request acknowledgment (HARQ-ACK) feedback is allowed.
  • HARQ-ACK hybrid automatic repeat request acknowledgment
  • Both slot-based Type-1 HARQ-ACK codebook construction and slot-based Type-2 HARQ-ACK codebook construction are supported.
  • sub-slot based HARQ-ACK feedback is supported to reduce the feedback latency.
  • the sub-slot length may be configured as 2-symbol or 7-symbol by radio resource control signaling.
  • For HARQ-ACK codebook construction only sub-slot based Type-2 HARQ-ACK codebook is supported.
  • PDSCH physical downlink shared channel
  • the repetition number is semi-statically configured in RRC by pdsch-AggregationFactor in PDSCH-Config/SPS-config.
  • MIMO multi-input-multi-output
  • URLLC ultra-reliable low-latency communication
  • Scheme 3 repetition for PDSCH based on multi-TRP is supported, which allows two PDSCH repetitions are transmitted within a slot. Whether scheme 3 repetition based on multi-TRP is applied is indicated by scheduling DCI.
  • Scheme 4 repetition for PDSCH based on multi-TRP is supported, which allows N PDSCH repetitions are transmitted in N consecutive slots.
  • the repetition number of N is configured in a time domain resource allocation (TDRA) table and indicated by scheduling DCI.
  • TDRA time domain resource allocation
  • scheme 3/4 repetitions based on multi-TRP for SPS configuration is supported or not is less discussed and not clear. If not supported, it is not clear whether scheme 3/4 repetition based on multi-TRP for the first SPS PDSCH with activation DCI and SPS PDSCH retransmission scheduled by DCI is supported or not. If supported, for SPS configuration with short periodicity, for example, 2 slots, the collision between SPS PDSCH reception occasion and uplink (UL) symbols configured by time divisional duplex (TDD) configuration is hard to avoid by gNB implementation. If the collision happens, the HARQ-ACK feedback for SPS PDSCH scheme 3 repetition should be studied.
  • TDD time divisional duplex
  • the UE is expected to receive two PDSCH transmission occasions, where the first TCI state is applied to the first PDSCH transmission occasion.
  • the second TCI state is applied to the second PDSCH transmission occasion, and the second PDSCH transmission occasion shall have the same number of symbols as the first PDSCH transmission occasion.
  • the UE is configured by the higher layers with a value in StartingSymbolOffsetK, it shall determine that the first symbol of the second PDSCH transmission occasion starts after symbols from the last symbol of the first PDSCH transmission occasion. If the value is not configured via the higher layer parameter StartingSymbolOffsetK, shall be assumed by the UE. The UE is not expected to receive more than two PDSCH transmission layers for each PDSCH transmission occasion.
  • the UE is expected to receive a single PDSCH transmission occasion.
  • the second TCI state is applied to the second PDSCH transmission occasion.
  • the UE may be further configured to enable CycMapping or SeqMapping in RepTCIMapping.
  • the first and second TCI states are applied to the first and second PDSCH transmission occasions, respectively, and the same TCI mapping pattern continues to the remaining PDSCH transmission occasions.
  • the first TCI state is applied to the first and second PDSCH transmissions
  • the second TCI state is applied to the third and fourth PDSCH transmissions, and the same TCI mapping pattern continues to the remaining PDSCH transmission occasions.
  • the UE may expect that each PDSCH transmission occasion is limited to two transmission layers.
  • the redundancy version to be applied is derived according to a predetermined table (for example, to Table 5.1.2.1-2) .
  • the redundancy version for PDSCH transmission occasions associated with the second TCI state is derived a further predetermined table (for example, Table 5.1.2.1-3) , where additional shifting operation for each redundancy version rv s is configured by higher layer parameter RVSeqOffset and n is counted only considering PDSCH transmission occasions associated with the second TCI state.
  • the Type-1 HARQ-ACK codebook is determined based on the following factors: (1) PDSCH-to-HARQ_feedback timing values K1; (2) PDSCH time domain resource allocation (TDRA) table; (3) The ratio between the downlink SCS configuration ⁇ DL and the uplink SCS configuration ⁇ UL if different numerology between DL and UL is configured; (4) TDD configuration by TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigDedicated.
  • a UE reports HARQ-ACK information for a corresponding PDSCH reception or SPS PDSCH release only in a HARQ-ACK codebook that the UE transmits in a slot indicated by a value of a PDSCH-to-HARQ_feedback timing indicator field in a corresponding DCI format 1_0 or DCI format 1_1.
  • the UE reports NACK value (s) for HARQ-ACK information bit (s) in a HARQ-ACK codebook that the UE transmits in a slot not indicated by a value of a PDSCH-to-HARQ_feedback timing indicator field in a corresponding DCI format 1_0 or DCI format 1_1.
  • pdsch-AggregationFactor If the UE is provided pdsch-AggregationFactor and no entry in pdsch-TimeDomainAllocationList includes RepNumR16 in PDSCH-TimeDomainResourceAllocation, is a value of pdsch-AggregationFactor; otherwise The UE reports HARQ-ACK information for a PDSCH reception
  • Time domain resource assignment field in the DCI format scheduling the PDSCH reception indicates an entry in pdsch-TimeDomainAllocationList containing RepNumR16, or
  • k is a number of slots indicated by the PDSCH-to-HARQ_feedback timing indicator field in a corresponding DCI format or provided by dl-DataToUL-ACK if the PDSCH-to-HARQ_feedback timing indicator field is not present in the DCI format. If the UE reports HARQ-ACK information for the PDSCH reception in a slot other than slot n+k, the UE sets a value for each corresponding HARQ-ACK information bit to NACK.
  • enhancement on SPS PDSCH has been achieved.
  • the terminal device receives downlink data transmission which is semi-persistent configured, the downlink data transmission having a plurality of repetitions.
  • the terminal device determines the number of repetitions for the downlink data transmission.
  • the network device transmits a feedback for the repetitions for the downlink data transmission based on the number of the repetitions. In this way, a position for transmitting a feedback is properly determined by the terminal device.
  • 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 network terminal device 120-1, a network device 120-2, ..., a network device 120-M, which can be collectively referred to as “network device (s) 120. ”
  • the network device may be gNB.
  • the network device may be IAB.
  • the number M can be any suitable integer number.
  • the network devices 120 and the terminal devices 110 can communicate data and control information to each other. Only for the purpose of illustrations, the network device 120-1 can be regarded as a source network device and the network device 120-2 can be regarded as a target network device.
  • 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
  • downlink (DL) sub-slot may refer to a virtual sub-slot constructed based on uplink (UL) sub-slot.
  • the DL sub-slot may comprise fewer symbols than one DL slot.
  • 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 2010 a configuration associated with the plurality of repetitions for downlink data transmission.
  • the configuration may indicate that the repetitions are intra-slot repetitions.
  • the configuration may indicate that a plurality of repetitions are transmitted in one slot.
  • the configuration may indicate that two repetitions are transmitted in one slot.
  • the configuration may indicate that the repetitions are inter-slot repetitions.
  • the configuration may indicate that the plurality of repetitions are transmitted in a plurality of slots.
  • the configuration may indicate that there are N repetitions are transmitted in N consecutive slots.
  • the network device 120 may transmit 2020 control information to the terminal device 110-1.
  • the control information may comprise an indication for activating the configuration.
  • the configuration may also comprise a TDRA table.
  • at least one entry in the TDRA table may comprise an indication of the number of repetitions. Examples of the TDRA tables will be described later.
  • the control information may also indicate a set of HARQ-ACK timing values, for example, 1, 2, and 4. It should be noted that the HARQ-ACK timing values can be any proper values.
  • the control information may also indicate a time domain position of an uplink control channel.
  • the network device 120 transmits 2030 downlink data transmission to the terminal device 110-1.
  • the downlink data transmission is semi-persistent configured.
  • the downlink data transmission has the plurality of repetitions. As mentioned above, the plurality of repetitions may be transmitted in the same slot. Alternatively, the plurality of repetitions may be transmitted in different slots.
  • the terminal device 110-1 determines 2040 the number of repetitions for the downlink data transmission. For example, if the number of repetitions is 2, the terminal device 110-1 may determine that scheme 3 is configured. Alternatively, if the terminal device 110-1 determines the number of repetitions based on the TDRA table, the terminal device 110-1 may understand that scheme 4 is configured.
  • the terminal device 110-1 may determine the number of repetitions which are received. For example, as shown in Fig. 3, in this scenario where scheme 3 is configured, there are two downlink data transmission repetitions, 3010-1 and 3010-2. The first repetition 3010-1 may colloid with the uplink transmission. In some embodiments, when the scheme 3 repetition is configured for SPS configuration, at least one SPS repetition colloids with UL symbol within one slot, the terminal device 110-1 may not transmit the feedback for the two SPS PDSCH transmission occasions for a transport block (TB) .
  • TB transport block
  • the terminal device 110-1 may transmit the feedback for the SPS PDSCH transmission occasion (s) for a transport block (TB) .
  • the terminal device 110-1 may determine 2050 a position for transmitting a feedback. In some embodiments, if the first repetition 3010-1 is received, the terminal device 110-1 may determine a position in a codebook for HARQ-ACK corresponding to the first repetition. For example, for slot based Type-1 HARQ-ACK codebook, the terminal device 110-1 may only report a valid HARQ-ACK value for the two transmission occasions for a TB with OR operation in the HARQ-ACK position, which is determined based on the configured SLIV for the first SPS PDSCH transmission 3010-1.
  • the terminal device 110-1 may determine a set of SLIVs which are overlapping with at least one of the plurality of repetitions but non-overlapping with uplink symbols within the slot.
  • the terminal device 110-1 may determine a target SLIV from the set of SLIVs.
  • the target SLIV may have the earliest ending symbol in the TDRA table associated with the slot.
  • the terminal device 110-1 may determine the position for HARQ-ACK in the Type-1 codebook based on the target SLIV. As shown in Fig.
  • the RI 3 overlaps with the first repetition 4010-1 but also overlaps with uplink symbols
  • the RI 1 overlaps with the second repetition 4010-2 and does not overlap with the uplink symbols.
  • the terminal device 110-1 may determine the position based on the SLIV associated with the RI 1.
  • the RI0 overlaps with the first repetition 4020-1 and does not overlap with the uplink symbols.
  • the RI 3 overlaps with the first repetition 4020-1 but also overlaps with uplink symbols.
  • the RI 1 overlaps with the second repetition 4020-2 and does not overlap with the uplink symbols. Since the SLIV associated with the RI 0 has the earliest ending symbol in the slot 420, the position can be determined based on the SLIV associated with the RI 0.
  • the terminal device 110-1 may determine a set of SLIVs which are overlapping with the second repetition but non-overlapping with uplink symbols within the slot.
  • the terminal device 110-1 may determine a position in a codebook for HARQ-ACK based on the set of SLIVs.
  • the RI0 overlaps with the first repetition 4030-1 and does not overlap with the uplink symbols.
  • the RI 3 overlaps with the first repetition 4030-1 but also overlaps with uplink symbols.
  • the RI 1 overlaps with the second repetition 4030-2 and does not overlap with the uplink symbols. Since the SLIV associated with the RI 1 overlaps with the second repetition 4030-2, the position can be determined based on the SLIV associated with the RI 1.
  • the terminal device 110-1 may determine a first SLIV of the first repetition based on the configuration.
  • the terminal device 110-1 may determine an offset between the first repetition and the second repetition based on the configuration.
  • a second SLIV of the second repetition may be determined based on the first SLIV and the offset.
  • the terminal device 110-1 may update a time domain resource allocation table with adding the second SLIV into the time domain resource allocation table.
  • the position in a codebook for HARQ-ACK may be determined based on the second SLIV in the updated time domain resource allocation table.
  • the terminal device 110-1 is configured with scheme 3 repetition, there is one “virtual” SLIV added in the TDRA table for Type-1 HARQ-ACK codebook generation.
  • the SLIV configuration for the first repetition 4040-1 is starting symbol index S, symbol length L, and the offset between the first repetition 4040-1and the second repetition 4040-2 is X.
  • the starting symbol index for the second SLIV 4140 of the second repetition 4040-2 is S+L+X, and length of the second SLIV 4140 is L.
  • the terminal device 110-1 may determine the position based on the second SLIV 4140.
  • the terminal device 110-1 can determine the position properly and still can report valid HARQ-ACK value for the SPS PDSCH transmission occasion (s) for the TB.
  • the terminal device 110-1 may obtain from the control information, a TDRA table, a set of HARQ-ACK timing values, and a time domain position of an uplink control channel. At least one entry in the time domain resource allocation table may comprise a repetition number indication. The terminal device 110-1 may determine the number of repetitions and a SLIV of each entry based on the TDRA table. The terminal device 110-1 may determine a set of positions based on the number of repetitions and the SLIV of each entry in the TDRA table, the set of HARQ-ACK timing values, and the time domain position of the uplink control channel.
  • the HARQ-ACK timing values may be any suitable number, for example, 1, 3, or 4.
  • the terminal device 110-1 when the terminal device 110-1 is configured by the higher layer parameter PDSCH-config that indicates at least one entry in pdsch-TimeDomainAllocationList contain RepNumR16 in PDSCH-TimeDomainResourceAllocation, for each SLIV, the terminal device 110-1 may use the maximum value of RepNumR16 configured in the pdsch-TimeDomainAllocationList to construct the HARQ-ACK codebook.
  • Table 1 below shows an example TDRA table.
  • maximum Repetition Number R16 for the SLIV of RI #1 and RI #2 is 4, maximum Repetition Number R16 for the SLIV of RI #0 is 2.
  • Table 2 shows specifications of Type-1 HARQ-ACK codebook determination.
  • Table 3 shows pseudo codes for Type-1 HARQ-ACK codebook determination.
  • the terminal device 110-1 may obtain from the control information, a TDRA table, a set of HARQ-ACK timing values, and a time domain position of an uplink control channel.
  • the terminal device 110-1 may determine a SLIV of one entry based on the TDAR table.
  • the terminal device 110-1 may determine a maximum number of repetitions based on the TDAR table.
  • the terminal device 110-1 may determine a set of positions based on the maximum number of repetitions, the SLIV of each entry in the TDRA table, the set of HARQ-ACK timing values, and the time domain position of the uplink control channel.
  • the terminal device 110-1 when the terminal device 110-1 is configured by the higher layer parameter PDSCH-config that indicates at least one entry in pdsch-TimeDomainAllocationList containing RepNumR16 in PDSCH-TimeDomainResourceAllocation, for all SLIVs in the pdsch-TimeDomainAllocationList, the terminal device 110-1 may use the maximum value of RepNumR16 configured in the pdsch-TimeDomainAllocationList to construct the HARQ-ACK codebook.
  • Table 4 shows an example TDRA table. As shown in Table 4, the maximum repetition number is 4.
  • Table 5 shows specifications of Type-1 HARQ-ACK codebook determination.
  • Table 6 shows pseudo codes for Type-1 HARQ-ACK codebook determination.
  • the terminal device 110-1 transmits 2060 the feedback to the network device 120 on the determined position.
  • the terminal device 110-1 may receive from the network device 120 further control information which indicates a plurality of TCI states.
  • the terminal device 110-1 may receive from the network device 120 a further configuration indicating a predetermined TCI state used for further downlink data transmission without repetitions.
  • the predetermined TCI state may be the first TCI in the further control information.
  • the predetermined TCI state may be the last TCI in the further control information. It should be noted that the predetermined TCI state may be any suitable TCI selected by the network device 120.
  • the terminal device 110-1 may receive, based on the predetermined TCI sates, the further downlink data transmission without repetitions from the network device.
  • the terminal device may determine the beam direction based on the TCI states.
  • the number of PDSCH transmission occasions is derived by the number of TCI states indicated by the DCI field 'Transmission Configuration Indication' of the scheduling DCI.
  • the terminal device doesn’t expect to be indicated more than one TCI states by the DCI field 'Transmission Configuration Indication' of the scheduling DCI scrambled with a CS-RNTI.
  • the terminal device when a UE configured by the higher layer parameter PDSCH-config that indicates at least one entry in pdsch-TimeDomainAllocationList contain RepNumR16 in PDSCH-TimeDomainResourceAllocation, the terminal device doesn’t expect one entry in pdsch-TimeDomainAllocationList contain RepNumR16 in PDSCH-TimeDomainResourceAllocation is indicated for SPS PDSCH by the scheduling DCI scrambled with a CS-RNTI.
  • the DCI 5110 may be used to activate the SPS PDSCH 5120 during the slot 510-1.
  • the SPS PDSCH 5130 in the slot 510-2 and the SPS PDSCH 5140 in the slot 510-3 may not have repetitions.
  • the DCI may only have one TCI state.
  • the DCI 5210 may be used to activate the SPS PDSCH during the slot 520-1. There are two repetitions in the slot 520-1, for example, the first SPS PDSCH repetition 5220-1 and the second SPS PDSCH repetition 5220-2. The SPS PDSCH 5230 in the slot 520-2 and the SPS PDSCH 5240 in the slot 520-3 may not have repetitions.
  • the DCI 5210 may have more than one TCI state. The first/last TCI state in the DCI 5210 may be used for SPS PDSCH without corresponding PDCCH.
  • Fig. 6 shows a flowchart of an example method 600 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 1400 can be implemented at a terminal device 110-1 as shown in Fig. 1.
  • the terminal device 110-1 may receive a configuration associated with the plurality of repetitions for downlink data transmission.
  • the configuration may indicate that the repetitions are intra-slot repetitions.
  • the configuration may indicate that a plurality of repetitions are transmitted in one slot.
  • the configuration may indicate that two repetitions are transmitted in one slot.
  • the configuration may indicate that the repetitions are inter-slot repetitions.
  • the configuration may indicate that the plurality of repetitions are transmitted in a plurality of slots.
  • the configuration may indicate that there are N repetitions are transmitted in N consecutive slots.
  • the terminal device 110-1 may receive control information from the network device 120.
  • the control information may comprise an indication for activating the configuration.
  • the configuration may also comprise a TDRA table.
  • at least one entry in the TDRA table may comprise an indication of the number of repetitions. Examples of the TDRA tables will be described later.
  • the control information may also indicate a set of HARQ-ACK timing values, for example, 1, 2, and 4. It should be noted that the HARQ-ACK timing values can be any proper values.
  • the control information may also indicate a time domain position of an uplink control channel.
  • the terminal device 110-1 receives downlink data transmission from the network device 120.
  • the downlink data transmission is semi-persistent configured.
  • the downlink data transmission has the plurality of repetitions. As mentioned above, the plurality of repetitions may be transmitted in the same slot. Alternatively, the plurality of repetitions may be transmitted in different slots.
  • the terminal device 110-1 determines the number of repetitions for the downlink data transmission. For example, if the number of repetitions is 2, the terminal device 110-1 may determine that scheme 3 is configured. Alternatively, if the terminal device 110-1 determines the number of repetitions based on the TDRA table, the terminal device 110-1 may understand that scheme 4 is configured.
  • the terminal device 110-1 may the number of repetitions which are received. In some embodiments, when the scheme 3 repetition is configured for SPS configuration, at least one SPS repetition colloids with UL symbol within one slot, the terminal device 110-1 may not transmit the feedback for the two SPS PDSCH transmission occasions for a transport block (TB) . Alternatively, when scheme 3 repetition is configured for SPS configuration, at least one repetition within one slot is received (i.e., available) , the terminal device 110-1 may transmit the feedback for the SPS PDSCH transmission occasion (s) for a TB.
  • TB transport block
  • the terminal device 110-1 may determine a position for transmitting a feedback. In some embodiments, if the first repetition 3010-1 is received, the terminal device 110-1 may determine a position in a codebook for HARQ-ACK corresponding to the first repetition. For example, for slot based Type-1 HARQ-ACK codebook, the terminal device 110-1 may only report a valid HARQ-ACK value for the two transmission occasions for a TB with OR operation in the HARQ-ACK position, which is determined based on the defined SLIV for the first repetition 3010-1.
  • the terminal device 110-1 may determine a set of SLIVs which are overlapping with at least one of the plurality of repetitions but non-overlapping with uplink symbols within the slot.
  • the terminal device 110-1 may determine a target SLIV from the set of SLIVs.
  • the target SLIV may have the earliest ending symbol in the TDRA table associated with the slot.
  • the terminal device 110-1 may determine the position for HARQ-ACK based on the target SLIV.
  • the terminal device 110-1 may determine the position based on the SLIV associated with the RI 1.
  • the terminal device 110-1 may determine a set of SLIVs which are overlapping with the second repetition but non-overlapping with uplink symbols within the slot.
  • the terminal device 110-1 may determine a position in a codebook for HARQ-ACK based on the set of SLIVs.
  • the terminal device 110-1 may determine a first SLIV of the first repetition based on the configuration.
  • the terminal device 110-1 may determine an offset between the first repetition and the second repetition based on the configuration.
  • a second SLIV of the second repetition may be determined based on the first SLIV and the offset.
  • the terminal device 110-1 may update a time domain resource allocation table with adding the second SLIV into the time domain resource allocation table.
  • the position in a codebook for HARQ-ACK may be determined based on the second SLIV in the updated time domain resource allocation table. If the terminal device 110-1 is configured with scheme 3 repetition, there is one “virtual” SLIV added in the TDRA table for type 1 HARQ-ACK codebook generation.
  • the terminal device 110-1 can determine the position properly and still can report valid HARQ-ACK value for the SPS PDSCH transmission occasion (s) for the TB.
  • the terminal device 110-1 may obtain from the control information, a TDRA table, a set of HARQ-ACK timing values, and a time domain position of an uplink control channel. At least one entry in the time domain resource allocation table may comprise a repetition number indication. The terminal device 110-1 may determine the number of repetitions and a SLIV of one entry based on the TDRA table. The terminal device 110-1 may determine a set of positions based on the number of repetitions and the SLIV of each entry in the TDRA table, the set of HARQ-ACK timing values, and the time domain position of the uplink control channel.
  • the HARQ-ACK timing values may be any suitable number, for example, 1, 3, or 4.
  • the terminal device 110-1 may obtain from the control information, a TDRA table, a set of HARQ-ACK timing values, and a time domain position of an uplink control channel.
  • the terminal device 110-1 may determine a SLIV of one entry based on the TDAR table.
  • the terminal device 110-1 may determine a maximum number of repetitions based on the TDAR table.
  • the terminal device 110-1 may determine a set of positions based on the maximum number of repetitions, the SLIV of each entry in the TDRA table, the set of HARQ-ACK timing values, and the time domain position of the uplink control channel.
  • the terminal device 110-1 transmits the feedback to the network device 120 on the determined position.
  • the terminal device 110-1 may receive from the network device 120 further control information which indicates a plurality of TCI states.
  • the terminal device 110-1 may receive from the network device 120 a further configuration indicating a predetermined TCI states used for further downlink data transmission without repetitions.
  • the terminal device 110-1 may receive, based on the predetermined TCI sates, the further downlink data transmission without repetitions from the network device. For example, the terminal device may determine the beam direction based on the TCI states.
  • Fig. 7 shows a flowchart of an example method 700 in accordance with an embodiment of the present disclosure. Only for the purpose of illustrations, the method 700 can be implemented at a first network device 120 as shown in Fig. 1.
  • the network device 120 may transmit a configuration associated with the plurality of repetitions for downlink data transmission.
  • the configuration may indicate that the repetitions are intra-slot repetitions.
  • the configuration may indicate that a plurality of repetitions are transmitted in one slot.
  • the configuration may indicate that two repetitions are transmitted in one slot.
  • the configuration may indicate that the repetitions are inter-slot repetitions.
  • the configuration may indicate that the plurality of repetitions are transmitted in a plurality of slots.
  • the configuration may indicate that there are N repetitions are transmitted in N consecutive slots.
  • the network device 120 may transmit control information to the terminal device 110-1.
  • the control information may comprise an indication for activating the configuration.
  • the configuration may also comprise a TDRA table.
  • at least one entry in the TDRA table may comprise an indication of the number of repetitions. Examples of the TDRA tables will be described later.
  • the control information may also indicate a set of HARQ-ACK timing values, for example, 1, 2, and 4. It should be noted that the HARQ-ACK timing values can be any proper values.
  • the control information may also indicate a time domain position of an uplink control channel.
  • the network device 120 transmits downlink data transmission to the terminal device 110-1.
  • the downlink data transmission is semi-persistent configured.
  • the downlink data transmission has the plurality of repetitions. As mentioned above, the plurality of repetitions may be transmitted in the same slot. Alternatively, the plurality of repetitions may be transmitted in different slots.
  • the network device 120 receives, from the terminal device 110-1, a feedback for the repetitions for the downlink data transmission based on the number of repetitions.
  • the network device 120 may transmit to the terminal device 110-1 further control information indicating a plurality of transmission configuration indicator (TCI) states.
  • TCI transmission configuration indicator
  • the network device 120 may transmit to the terminal device 110-1 a further configuration indicating a predetermined TCI states used for further downlink data transmission without repetitions.
  • the network device 120 may transmit to the terminal device 110-1 based on the predetermined TCI sates the further downlink data transmission without repetitions to the terminal device.
  • Fig. 8 is a simplified block diagram of a device 800 that is suitable for implementing embodiments of the present disclosure.
  • the device 800 can be considered as a further example implementation of the terminal device 110 and the network device 120 as shown in Fig. 1. Accordingly, the device 800 can be implemented at or as at least a part of the terminal device 110 or the network device 120.
  • the device 800 includes a processor 810, a memory 820 coupled to the processor 810, a suitable transmitter (TX) and receiver (RX) 840 coupled to the processor 810, and a communication interface coupled to the TX/RX 840.
  • the memory 820 stores at least a part of a program 830.
  • the TX/RX 840 is for bidirectional communications.
  • the TX/RX 840 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 830 is assumed to include program instructions that, when executed by the associated processor 810, enable the device 800 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to Fig. 2 to 6.
  • the embodiments herein may be implemented by computer software executable by the processor 810 of the device 800, or by hardware, or by a combination of software and hardware.
  • the processor 810 may be configured to implement various embodiments of the present disclosure.
  • a combination of the processor 810 and memory 820 may form processing means 850 adapted to implement various embodiments of the present disclosure.
  • the memory 820 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 820 is shown in the device 800, there may be several physically distinct memory modules in the device 800.
  • the processor 810 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 800 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • 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 any of Figs. 4-10.
  • 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)
  • Mobile Radio Communication Systems (AREA)

Abstract

Les modes de réalisation de la présente divulgation se rapportent à la communication. Selon les modes de réalisation de la présente divulgation, une amélioration sur le PDSCH SPS a été obtenue. Le dispositif terminal reçoit une transmission de données de liaison descendante qui est configurée de façon semi-persistante, la transmission de données de liaison descendante ayant une pluralité de répétitions. Le dispositif terminal détermine le nombre de répétitions pour la transmission de données de liaison descendante. Le dispositif de réseau transmet une rétroaction pour les répétitions de la transmission de données de liaison descendante sur la base du nombre des répétitions. De cette façon, une position pour transmettre une rétroaction est correctement déterminée par le dispositif terminal.
PCT/CN2020/104603 2020-07-24 2020-07-24 Procédés, dispositifs, et support lisible par ordinateur pour une communication Ceased WO2022016552A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/104603 WO2022016552A1 (fr) 2020-07-24 2020-07-24 Procédés, dispositifs, et support lisible par ordinateur pour une communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/104603 WO2022016552A1 (fr) 2020-07-24 2020-07-24 Procédés, dispositifs, et support lisible par ordinateur pour une communication

Publications (1)

Publication Number Publication Date
WO2022016552A1 true WO2022016552A1 (fr) 2022-01-27

Family

ID=79729751

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/104603 Ceased WO2022016552A1 (fr) 2020-07-24 2020-07-24 Procédés, dispositifs, et support lisible par ordinateur pour une communication

Country Status (1)

Country Link
WO (1) WO2022016552A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116633494A (zh) * 2022-02-09 2023-08-22 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
WO2023201483A1 (fr) * 2022-04-18 2023-10-26 Oppo广东移动通信有限公司 Procédé de communication sans fil, dispositif terminal et dispositif de réseau

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014110785A1 (fr) * 2013-01-18 2014-07-24 Broadcom Corporation Transmission de données destinée à des dispositifs de communication de type machine peu coûteux
WO2017078784A1 (fr) * 2015-11-05 2017-05-11 Intel Corporation Systèmes de retransmission adaptative de paquet
CN111226408A (zh) * 2018-09-25 2020-06-02 联发科技(新加坡)私人有限公司 用于移动通信中的上行链路传输的混合自动重传请求反馈过程

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014110785A1 (fr) * 2013-01-18 2014-07-24 Broadcom Corporation Transmission de données destinée à des dispositifs de communication de type machine peu coûteux
WO2017078784A1 (fr) * 2015-11-05 2017-05-11 Intel Corporation Systèmes de retransmission adaptative de paquet
CN111226408A (zh) * 2018-09-25 2020-06-02 联发科技(新加坡)私人有限公司 用于移动通信中的上行链路传输的混合自动重传请求反馈过程

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CMCC: "Repetitions Transmission for SPS configurations", 3GPP TSG-RAN WG2 MEETING#108 R2-1915995, 22 November 2019 (2019-11-22), XP051817550 *
ERICSSON: "Repetition enhancements for UL SPS operation", 3GPP TSG-RAN WG2 #102 R2-1807219, 25 May 2018 (2018-05-25), XP051464070 *
HUAWEI ET AL.: "Corrections on other aspects for URLLC/IIOT enhancements", 3GPP TSG RAN WG1 MEETING #101-E R1-2004611, 5 June 2020 (2020-06-05), XP051886327 *
HUAWEI ET AL.: "Corrections on other aspects for URLLC/IIOT enhancements", 3GPP TSG RAN WG1 MEETING#100BIS-E R1-2002584, 30 April 2020 (2020-04-30), XP051875698 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116633494A (zh) * 2022-02-09 2023-08-22 上海朗帛通信技术有限公司 一种被用于无线通信的节点中的方法和装置
WO2023201483A1 (fr) * 2022-04-18 2023-10-26 Oppo广东移动通信有限公司 Procédé de communication sans fil, dispositif terminal et dispositif de réseau

Similar Documents

Publication Publication Date Title
US12537630B2 (en) Methods for communications, terminal device, network device and computer readable media
CN115918193B (zh) 通信方法、终端设备和计算机可读介质
WO2022205467A1 (fr) Procédé, dispositif et support de stockage informatique de communication
US9986557B2 (en) Communication method in wireless communication system on basis of carrier aggregation
US20240048279A1 (en) Methods, devices, and computer readable medium for communication
JP2023065547A (ja) 端末装置、ネットワークデバイス、及び方法
WO2021189320A1 (fr) Procédé, dispositif et support de stockage informatique de communication
US12464530B2 (en) Methods for communication, terminal device, network device, and computer readable media
JP2026016740A (ja) 端末装置、ネットワーク装置、及びそれらにより実行される方法
WO2022027645A1 (fr) Support lisible par ordinateur, procédés, et dispositifs de communication
WO2022016552A1 (fr) Procédés, dispositifs, et support lisible par ordinateur pour une communication
WO2021196246A1 (fr) Procédés, dispositifs et support de communication
WO2021248283A1 (fr) Procédés de communication, équipement terminal et support lisible par ordinateur
US20240072976A1 (en) Determination of Feedback Timing
AU2019426286B2 (en) Method, device, and computer readable medium for communication
US20240323953A1 (en) Method, device and computer readable medium for communication
AU2016417122B2 (en) Determination of feedback timing
WO2025160922A1 (fr) Configuration de modes de fonctionnement pour duplex intégral sans chevauchement de sous-bande
US12621087B2 (en) Method, device and computer storage medium of communication
WO2024168740A1 (fr) Indication de rétroaction de demande de répétition automatique hybride dynamique
WO2022000498A1 (fr) Procédés, dispositifs et support lisible par ordinateur relatifs aux communications
WO2022011674A1 (fr) Procédé, dispositif et support de stockage d'ordinateur destinés à des communications
WO2023272723A1 (fr) Procédé, dispositif et support de stockage informatique de communication
US20240048292A1 (en) Method, device and computer storage medium of 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: 20946082

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20946082

Country of ref document: EP

Kind code of ref document: A1