WO2024077639A1 - Rétroaction de demande automatique hybride (harq) - Google Patents

Rétroaction de demande automatique hybride (harq) Download PDF

Info

Publication number
WO2024077639A1
WO2024077639A1 PCT/CN2022/125531 CN2022125531W WO2024077639A1 WO 2024077639 A1 WO2024077639 A1 WO 2024077639A1 CN 2022125531 W CN2022125531 W CN 2022125531W WO 2024077639 A1 WO2024077639 A1 WO 2024077639A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
contention
harq
downlink
capability
Prior art date
Application number
PCT/CN2022/125531
Other languages
English (en)
Inventor
Pingping Wen
Ping Yuan
Srinivasan Selvaganapathy
Mads LAURIDSEN
Jing Yuan Sun
Original Assignee
Nokia Shanghai Bell Co., Ltd.
Nokia Solutions And Networks Oy
Nokia Technologies Oy
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 Nokia Shanghai Bell Co., Ltd., Nokia Solutions And Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co., Ltd.
Priority to PCT/CN2022/125531 priority Critical patent/WO2024077639A1/fr
Publication of WO2024077639A1 publication Critical patent/WO2024077639A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/006—Transmission of channel access control information in the downlink, i.e. towards the terminal
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/008—Transmission of channel access control information with additional processing of random access related information at receiving side
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access

Definitions

  • Examples of the disclosure relate to Hybrid automatic request (HARQ) feedback.
  • Some relate to hybrid automatic request (HARQ) feedback used to acknowledge the proper reception of the downlink content resolution message (Msg4) in the contention-based random-access (CBRA) procedure.
  • Msg4 downlink content resolution message
  • CBRA contention-based random-access
  • Hybrid automatic request (HARQ) feedback is used to acknowledge the proper reception of the downlink content resolution message (Msg4) in the contention-based random-access (CBRA) procedure.
  • Msg4 downlink content resolution message
  • CBRA contention-based random-access
  • a user equipment comprising means for:
  • HARQ hybrid automatic request
  • HARQ hybrid automatic request
  • the indication instructs disablement or provides conditions for UE determination of disablement.
  • the indication comprises received broadcast system information.
  • the broadcast system information defines one or more coverage enhancement levels, wherein at least one coverage enhancement level is associated with disablement.
  • the broadcast system information defines one or more thresholds for assessing a downlink signal at the user equipment.
  • the indication is a modified downlink random access response in the contention-based random-access procedure.
  • the indication is a downlink control information comprising a modified HARQ-ACK resource field.
  • a modification of a downlink control information field is indicated in broadcast system information or predefined in a specification.
  • the user equipment comprises means for disabling, in dependence upon the received indication, hybrid automatic request (HARQ) feedback for a downlink data message subsequent to the contention resolution message.
  • HARQ hybrid automatic request
  • the user equipment comprises means for: indicating, to a network node, a capability for disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure.
  • HARQ hybrid automatic request
  • the user equipment comprises means for: indicating, to a network node, a capability for disablement using an uplink message of the contention-based random-access (CBRA) procedure.
  • CBRA contention-based random-access
  • the means for indicating, to the network, a capability for disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access (CBRA) procedure comprises: means for implicit indication of the capability by constraining detectable features of a random access request in the contention-based random-access procedure.
  • HARQ hybrid automatic request
  • CBRA contention-based random-access
  • the means for indicating, to the network, a capability for disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access (CBRA) procedure comprises: means for implicit indication of the capability by selecting between different configurations for the random access request in the contention-based random-access procedure, wherein a first set of configurations indicates a capability and a second a second set of configurations indicates a lack of capability.
  • HARQ hybrid automatic request
  • the means for implicit indication of the capability comprises means for selecting for use a preamble for the random access request from a first predefined sub-set to indicate a first capability and means for selecting a preamble for the random access request from a second predefined sub-set to indicate a second capability and/or means for implicit indication of the capability comprises means for selecting for use subcarriers for the random access request from a first predefined sub-set to indicate a first capability and means for selecting subcarriers for the random access request from a second predefined sub-set to indicate a second capability and/or means for implicit indication of the capability comprises means for selecting for use time-domain resources for the random access request from a first predefined sub-set to indicate a first capability and means for selecting time-domain resources for the random access request from a second predefined sub-set to indicate a second capability.
  • the means for indicating, to the network, a capability for disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access (CBRA) procedure comprises: means for explicit indication of the capability by adapting Scheduled UL Transmission in the contention-based random-access (CBRA) procedure.
  • HARQ hybrid automatic request
  • the user equipment comprises means for performing contention-based random-access (CBRA) procedure comprising: transmitting a random access request; receiving a random access response; transmitting a scheduled UL Transmission; receiving a contention resolution message; and comprising means for determining from downlink control information, that the next transmitted contention resolution message is a last transmitted contention resolution message and there is no subsequent re-transmission of the contention resolution message.
  • CBRA contention-based random-access
  • the user equipment comprises means for stopping a contention resolution timer in dependence upon determining from the downlink control information, that the next transmitted contention resolution message is a last transmitted contention resolution message.
  • a method comprising: receiving from a network node an indication to disable hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure; and disabling, in dependence upon the received indication, hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure.
  • HARQ hybrid automatic request
  • a computer program comprising instructions that when run on an apparatus enable the apparatus to control: receiving an indication to disable hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure; and disabling, in dependence upon the received indication, hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure.
  • HARQ hybrid automatic request
  • a network node comprising means for:
  • HARQ hybrid automatic request
  • the means for indicating disablement at the user equipment of hybrid automatic request (HARQ) feedback for a downlink contention resolution message in a contention-based random-access procedure comprises means for: instructing disablement or providing conditions for UE determination of disablement.
  • HARQ hybrid automatic request
  • the means for indicating disablement at the user equipment of hybrid automatic request (HARQ) feedback for a downlink contention resolution message in a contention-based random-access procedure comprises means for: broadcasting system information to indicate disablement.
  • HARQ hybrid automatic request
  • system information is comprised in a broadcast system information block.
  • the system information defines one or more coverage enhancement levels, wherein at least one coverage enhancement level is associated with disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure.
  • HARQ hybrid automatic request
  • the system information defines one or more thresholds for assessing signal quality at the user equipment.
  • the means for indicating disablement at the user equipment of hybrid automatic request (HARQ) feedback for a downlink contention resolution message in a contention-based random-access procedure comprises means for: modifying a downlink random access response in the contention-based random-access procedure to indicate disablement.
  • HARQ hybrid automatic request
  • the means for indicating disablement at the user equipment of hybrid automatic request (HARQ) feedback for a downlink contention resolution message in a contention-based random-access procedure comprises means for: using a downlink control information to indicate disablement.
  • HARQ hybrid automatic request
  • the network node comprises means for modifying HARQ-ACK resource field in a downlink control information to indicate disablement.
  • the network node comprises means for performing contention-based random-access procedure for the user equipment comprising: receiving from the user equipment a random access request; transmitting to the user equipment a random access response; receiving from the user equipment a scheduled uplink transmission; transmitting to the user equipment a contention resolution; and comprises means for informing the user equipment, in downlink control information, that the next contention resolution message is a last contention resolution message and there is no subsequent re-transmission of the contention resolution message.
  • an indication, to at least a user equipment, of disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure additionally indicates disablement at the user equipment of hybrid automatic request (HARQ) feedback for downlink messages transferred after the downlink contention resolution message.
  • the network node is a transmission-reception point.
  • the network node comprises means for receiving from user equipment an indication of capability for disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access (CBRA) procedure.
  • HARQ hybrid automatic request
  • CBRA contention-based random-access
  • the network node comprises means for receiving the indication of capability in an uplink message of the contention-based random-access procedure.
  • the network node comprises means for receiving the indication of capability implicitly via a constrained random access request in the contention-based random-access procedure.
  • the network node comprises means for receiving the indication of capability via a preamble for the random access request, wherein the preamble is selected from a first predefined sub-set to indicate a first capability and selected from a second predefined sub-set to indicate a lack of capability and/or indication of the capability received using subcarriers for the random access request from a first predefined sub-set to indicate a first capability and from a second predefined sub-set to indicate a lack of capability.
  • the network node comprises means for receiving the indication of capability via a scheduled uplink transmission in the contention-based random-access procedure.
  • a method comprising: indicating, to at least a user equipment, disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure.
  • HARQ hybrid automatic request
  • a computer program comprising instructions that when run on an apparatus enable the apparatus to control: indicating, to at least a user equipment, disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure.
  • HARQ hybrid automatic request
  • a user equipment comprising means for: indicating, to a network node, a capability for disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure.
  • HARQ hybrid automatic request
  • a user equipment comprising means for: receiving from a network node an indication of non-occurrence of retransmission of a downlink contention resolution message in a contention-based random-access procedure; and in dependence upon the received indication, contention resolution timer is stopped in a contention-based random-access procedure.
  • the means for indicating non-occurrence of retransmission of a downlink contention resolution message in a contention-based random-access (CBRA) procedure comprises means for: using a downlink control information to non-occurrence of retransmission.
  • the user equipment comprises means for modifying HARQ-ACK resource field in a downlink control information to indicate non-occurrence of retransmission.
  • a network node comprising means for: indicating, to at least a user equipment, non-occurrence of retransmission of a downlink contention resolution message in a contention-based random-access procedure.
  • the means for indicating non-occurrence of retransmission of a downlink contention resolution message in a contention-based random-access (CBRA) procedure comprises means for: using a downlink control information to non-occurrence of retransmission.
  • the network node comprises means for modifying HARQ-ACK resource field in a downlink control information to indicate non-occurrence of retransmission.
  • FIG. 1 shows an example of the subject matter described herein
  • FIG. 2 shows another example of the subject matter described herein
  • FIG. 3 shows another example of the subject matter described herein
  • FIG. 4 shows another example of the subject matter described herein
  • FIG. 5 shows another example of the subject matter described herein
  • FIG. 6 shows another example of the subject matter described herein
  • FIG. 7 shows another example of the subject matter described herein
  • FIG. 8 shows another example of the subject matter described herein
  • FIG. 9 shows another example of the subject matter described herein.
  • FIG. 10 shows another example of the subject matter described herein
  • FIG. 11 shows another example of the subject matter described herein
  • FIG. 12 shows another example of the subject matter described herein
  • FIG. 13 shows another example of the subject matter described herein
  • FIG. 14 shows another example of the subject matter described herein
  • FIG 1 illustrates an example of a network 100 comprising a plurality of network nodes including terminal nodes 110, access nodes 120 and one or more core nodes 129.
  • the terminal nodes 110 and access nodes 120 communicate with each other.
  • the one or more core nodes 129 communicate with the access nodes 120.
  • the network 100 is in this example a radio telecommunications network, in which at least some of the terminal nodes 110 and access nodes 120 communicate with each other using transmission/reception of radio waves.
  • the one or more core nodes 129 may, in some examples, communicate with each other.
  • the one or more access nodes 120 may, in some examples, communicate with each other.
  • the network 100 may be a cellular network comprising a plurality of cells 122 each served by an access node 120.
  • the interface between the terminal nodes 110 and an access node 120 defining a cell 122 is a wireless interface 124.
  • the access node 120 is a cellular radio transceiver.
  • the terminal nodes 110 are cellular radio transceivers.
  • the cellular network 100 is a third generation Partnership Project (3GPP) network in which the terminal nodes 110 are user equipment (UE) and the access nodes 120 are base stations.
  • 3GPP third generation Partnership Project
  • the network 100 is an Evolved Universal Terrestrial Radio Access network (E-UTRAN) .
  • the E-UTRAN consists of E-UTRAN NodeBs (eNBs) 120, providing the E-UTRA user plane and control plane (RRC) protocol terminations towards the UE 110.
  • the eNBs 120 are interconnected with each other by means of an X2 interface 126.
  • the eNBs are also connected by means of the S1 interface 128 to the Mobility Management Entity (MME) 129.
  • MME Mobility Management Entity
  • the network 100 is a Next Generation (or New Radio, NR) Radio Access network (NG-RAN) .
  • the NG-RAN consists of gNodeBs (gNBs) 120, providing the user plane and control plane (RRC) protocol terminations towards the UE 110.
  • the gNBs 120 are interconnected with each other by means of an X2/Xn interface 126.
  • the gNBs are also connected by means of the N2 interface 128 to the Access and Mobility management Function (AMF) .
  • AMF Access and Mobility management Function
  • a user equipment comprises a mobile equipment. Where reference is made to user equipment that reference includes and encompasses, wherever possible, a reference to mobile equipment.
  • FIG 2 illustrates a process of communication between a network node 120 and a user equipment.
  • the network node 120 is configured to indicate, to the user equipment 110, disablement 52 at the user equipment 110 of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access (CBRA) procedure.
  • HARQ hybrid automatic request
  • the network node 120 is illustrated as in communication with one user equipment 110, the network node 120 is configured to contemporaneously communication with multiple user equipment 110 in parallel.
  • the network node 120 is configured to indicate, to each of multiple user equipment 110, disablement 52 at the respective user equipment 110 of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access (CBRA) procedure for that user equipment 110.
  • HARQ hybrid automatic request
  • CBRA contention-based random-access
  • the user equipment 110 is configured to receive from the network node 120 an indication 50 to disable 52 hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message in a contention-based random-access (CBRA) procedure for the user equipment 110.
  • the user equipment 110 is additionally configured to disable 52, in dependence upon the received indication 50, hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in the contention-based random-access (CBRA) procedure.
  • HARQ hybrid automatic request
  • FIG 3 illustrates an example of a contention-based random-access (CBRA) procedure 60 with HARQ feedback (without HARQ feedback disablement) .
  • FIG 4 illustrates an example of a contention-based random-access (CBRA) procedure 60 with HARQ feedback disablement 52.
  • the contention-based random-access (CBRA) procedure 60 comprises from the user equipment 110 perspective:
  • the user equipment 110 transmits a HARQ feedback message 20 acknowledging reception of the contention resolution message (Msg 4) 14.
  • the contention-based random-access (CBRA) procedure 60 comprises from the network node 120 perspective:
  • the network node 120 receives a HARQ feedback message 20 from the user equipment 110 acknowledging reception of the contention resolution message (Msg 4) 14 by the user equipment 110.
  • FIG 4 illustrates an example of a contention-based random-access (CBRA) procedure 60 with HARQ feedback disablement 52.
  • the user equipment 110 does not transmit a HARQ feedback message 20 acknowledging reception of the contention resolution message (Msg 4) 14.
  • the network node 120 does not receive and does not expect to receive a HARQ feedback message 20 from the user equipment 110 acknowledging reception of the contention resolution message (Msg 4) 14 by the user equipment 110.
  • the network node 120 is configured to indicate, to the user equipment 110, disablement at the user equipment 110 of hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message 14 in a contention-based random-access (CBRA) procedure 60.
  • HARQ hybrid automatic request
  • CBRA contention-based random-access
  • the user equipment 110 is configured to receive from the network node 120 an indication 50 to disable 52 hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message 14 in a contention-based random-access (CBRA) procedure 60 for the user equipment 110.
  • the user equipment 110 is additionally configured to disable 52, in dependence upon the received indication 50, hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message 14 in the contention-based random-access (CBRA) procedure 60.
  • HARQ hybrid automatic request
  • FIG 5 illustrates an example of a contention-based random-access (CBRA) procedure 60 without HARQ feedback disablement.
  • the procedure 60 is similar to that illustrated in FIG 3, however, in FIG 5 there is data communication associated with the CBRA procedure 60.
  • the network node 120 After the network node 120 transmits the downlink contention resolution message 14 to the user equipment 110, the network node 120 can subsequently transmit a downlink data message 30 to the user equipment 110.
  • the first HARQ feedback message 20 is illustrated as transmitted in a time interval between the network node 120 transmitting the downlink contention resolution message 14 and transmitting the downlink data message 40, in some examples the first HARQ feedback message 20 is not transmitted in a time interval between the user equipment 110 transmitting the downlink contention resolution message 14 and transmitting the downlink data message 40, but is transmitted after the network node transmits the downlink data message 40.
  • This timing order is, for example, dependent upon a communication distance (communication delay) between the network node 120 and the user equipment 110.
  • HARQ feedback messages 20 can be delayed relative to the timings illustrated in FIG 5.
  • the downlink contention resolution message 14 can be retransmitted by the network node 120 if the HARQ feedback message 20 is not received in time.
  • the network node 120 transmits the downlink contention resolution message 14 to the user equipment 110, and the user equipment 110 can subsequently transmit an uplink data message (not illustrated) to the network equipment. There is not normally a HARQ process associated with uplink transmissions.
  • the disablement of HARQ feedback messages 30, therefore refers to disablement of HARQ feedback messages 30 transmitted in the uplink direction in respect of a preceding message received in the downlink direction.
  • FIG 6 illustrates an example of a contention-based random-access (CBRA) procedure 60, as previously described with reference to FIG 5, with HARQ feedback disablement.
  • CBRA contention-based random-access
  • the first HARQ process for the downlink contention resolution message 14 is disabled 52. Therefore when the user equipment successfully receives the downlink contention resolution message 14 it does not transmit, in reply, a first HARQ feedback message 20 to the network node 120.
  • the second HARQ process for the downlink data message 30 is disabled 52.
  • the user equipment 110 When the user equipment 110 successfully receives the downlink data message 40 it does not transmit, in reply, a second HARQ feedback message 20 to the network node 120.
  • the procedure 60 illustrated in FIG 6 is similar to that illustrated in FIG 4, however, in FIG 6 there is data communication associated with the CBRA procedure 60. After the network node 120 transmits the downlink contention resolution message 14 to the user equipment 110, the network node 120 subsequently transmits the downlink data message 30 to the user equipment 110.
  • the user equipment 110 is additionally configured to disable, in dependence upon the received indication 50, hybrid automatic request (HARQ) feedback 20 for a downlink data message 30 subsequent to the contention resolution message (Msg 4) .
  • HARQ hybrid automatic request
  • the user equipment 110 is configured to respond to receiving the indication 50 from the network node 120 and disable the hybrid automatic request (HARQ) feedback 20 for the contention resolution message (Msg 4) 14 and also disable the hybrid automatic request (HARQ) feedback 20 for the downlink data message 30, received subsequent to the contention resolution message (Msg 4) but in association with the CBRA procedure 60.
  • HARQ hybrid automatic request
  • the downlink data message 30 transferred after the downlink (DL) contention resolution message 14 can, for example, be a DLInformationTransfer message in a control plane of a NB-IoT UE.
  • the downlink data message 30 transferred after the downlink (DL) contention resolution message 14 can, for example, be a DL early data transmission.
  • the indication 50 indicates disablement 52 at the user equipment 110 of hybrid automatic request (HARQ) feedback 20 for downlink messages, for example downlink data messages 30, transferred after the downlink contention resolution message 14.
  • HARQ hybrid automatic request
  • FIGs 7 and 8 illustrate examples of the indication 50, where the indication 50 instructs disablement 52 at the user equipment. That is the indication 50 is an unconditional command to disable 52 uplink HARQ feedback messages 20.
  • FIG 9 illustrates an example of the indication 50, where the indication 50 provides conditions for user equipment 110 to determine whether or not to disable 52 uplink HARQ feedback messages 20.
  • the indication 50 is provided by the downlink control information (DCI) 40.
  • the downlink control information is a message sent, for example based on the scheduling of the network, from the network node 120 to a specific user equipment 110 for configuring operation of the specific user equipment 110.
  • the DCI is transmitted on the Physical Downlink Control Channel (PDCCH) in 3GPP.
  • PDCCH Physical Downlink Control Channel
  • the indication 50 can, for example, be a repurposed downlink control information (DCI) field.
  • DCI downlink control information
  • the indication 50 can, for example, use downlink control information (DCI) fields associated with the CBRA procedure 60.
  • the indication 50 can, for example, use downlink control information (DCI) fields associated with scheduling the contention resolution message (Msg 4) 14.
  • the indication 50 is a downlink control information (DCI) 40 for scheduling the downlink contention resolution message 14, repurposed for indicating disablement 52 of hybrid automatic request (HARQ) feedback 20 for at least the downlink contention resolution message (Msg 4) 14 in a contention-based random-access (CBRA) procedure 60.
  • DCI downlink control information
  • HARQ hybrid automatic request
  • Msg downlink contention resolution message
  • the indication 50 is a downlink control information (DCI) 40 comprising a modified HARQ-ACK resource field.
  • DCI downlink control information
  • the modification of the downlink control information (DCI) field, for use as an indicator 50 for disablement 42 of HARQ feedback, can, for example, be indicated in broadcast system information (SIB) or predefined in a specification.
  • SIB broadcast system information
  • which value of “HARQ-ACK resource” field is defined to indicate HARQ feedback disabling can be indicated through SIB signaling or defined in the specification.
  • the DCI 40 has Format N1.
  • the indication 50 is provided by the random access response message 12 in the CBRA procedure 60.
  • the random access response message 12 used as the indication is Msg2 in the CBRA procedure 60 and disables 52 HARQ feedback 20 for at least the contention resolution message 14 which is Msg4 in the same CBRA procedure 60.
  • the indication 50 is a modified downlink random access response 12 in the contention-based random-access (CBRA) procedure 60.
  • the indication 50 can, for example, be provided as a flag or bit field in a modified downlink random access response 12.
  • the indication 50 comprises received broadcast system information 42.
  • the system information 42 is broadcast to multiple user equipment 110.
  • the broadcast system information 42 is comprised in a broadcast system information block (SIB) .
  • SIBs are transmitted using Broadcast Control Channel (BCCH) mapped on Downlink Share Channel (DL-SCH) which in turn mapped on Physical Downlink Shared Channel (PDSCH) .
  • BCCH Broadcast Control Channel
  • DL-SCH Downlink Share Channel
  • PDSCH Physical Downlink Shared Channel
  • the broadcast system information 42 provides conditions for user equipment determination of disablement.
  • the broadcast system information 42 defines one or more thresholds 54 for assessing 56 a downlink signal 42 at the user equipment 110.
  • the assessment 56 of the downlink signal 42 can, for example, be a measurement of a received power, for example, reference signal received power (RSRP) .
  • RSRP reference signal received power
  • the downlink signal 42 is a reference signal, for example the secondary synchronization signal (SSS) .
  • SSS secondary synchronization signal
  • other assessments of a reference signal can be used or other downlink signal can be assessed.
  • the measured RSRP at the user equipment 110 is low (below the threshold) , there are likely to be more repetitions in a HARQ process.
  • the network is likely to remain busy and HARQ stalling is less likely to happen. There is therefore no requirement for disablement 52 of the HARQ process.
  • the network may be stalled waiting for a HARQ feedback message 20. There is therefore a requirement for disablement 52 of the HARQ process.
  • the user equipment assesses the downlink channel to be reliable, for example, the user equipment measures the RSRP to be above the threshold, it disables 52 the HARQ process 20.
  • the user equipment can re-use thresholds provided for other purposes.
  • the user equipment can re-use thresholds provided for determining a coverage enhancement (CE) level.
  • CE coverage enhancement
  • the broadcast system information 42 defines one or more coverage enhancement (CE) levels, and at least one coverage enhancement (CE) level is associated with disablement 52 of the HARQ feedback 20.
  • CE coverage enhancement
  • a low CE level can cause disablement 52 of the HARQ process 20 whereas a high CE level (worse RSRP) can prevent disablement 52 of the HARQ process 20.
  • a shorter transmission time per packet results in stalling being more likely. Therefore, transmissions with limited number of repetitions are more likely to have HARQ feedback disabled.
  • FIG 10 illustrates a contention-based random-access (CBRA) procedure 60, for example as previously described.
  • CBRA contention-based random-access
  • the network node 120 repeats the contention resolution message (Msg 4) 14 multiple times and stops when the HARQ feedback message 20 is received.
  • the network node 120 repeats blindly the contention resolution message (Msg 4) 14 multiple times without waiting for the HARQ feedback message.
  • the user equipment 110 after transmitting the scheduled UL Transmission (Msg3) 13 waits to receive the downlink contention resolution message (Msg 4) 14. It waits for the original contention resolution message (Msg 4) 14 or a re-transmission of the contention resolution message (Msg 4) 14.
  • the user equipment 110 starts a contention resolution timer, for example, after transmitting the scheduled UL Transmission (Msg3) 13 and waits to receive a contention resolution message (Msg 4) 14 until the contention resolution timer expires or a contention resolution message (Msg4) 14 is received.
  • the wait to receive a contention resolution message (Msg 4) 14 is terminated either when the contention resolution timer expires or a contention resolution message (Msg4) 14 is received.
  • the network node 120 informs 92 the user equipment 110 to use an alternate condition for terminating the wait to receive a contention resolution message (Msg 4) 14. For example, the network node 120 can inform 92 the user equipment 110 that the next (or a specified) contention resolution message (Msg 4) 14 will be the last contention resolution message (Msg 4) 14 and there will be no further re-transmissions of the contention resolution message (Msg 4) 14.
  • the user equipment 110 is configured to determine 90 from downlink control information 40, that the next transmitted contention resolution message 14 is a last transmitted contention resolution message 14 and there is no subsequent re-transmission of the contention resolution message 14. As a consequence the user equipment can stop its contention resolution timer (e.g. mac-ContentionResolutionTimer in 3GPP)
  • the contention resolution timer e.g. mac-ContentionResolutionTimer in 3GPP
  • the next transmitted contention resolution message 14 can be the original, first-transmitted contention resolution message 14 or can be a re-transmission of the contention resolution message 14.
  • the user equipment 110 is configured to determine from the downlink control information 40, that the contention resolution message 14 is transmitted without subsequent re-transmission.
  • DCI 40 can be modified to inform the user equipment 110 that the next transmitted contention resolution message 14 is a last transmitted contention resolution message 14 and there is no subsequent re-transmission of the contention resolution message 14.
  • a HARQ-ACK resource field in a downlink control information (DCI) 40 can be modified to indicate non-occurrence of retransmission.
  • DCI downlink control information
  • Which value of “HARQ-ACK resource” field is defined to indicate this can be indicated through SIB signaling or defined in a specification.
  • the user equipment 110 determines from downlink control information 40, that the contention resolution message 14 is transmitted without subsequent re-transmission.
  • DCI format N1 which is used to indicate both the NPDSCH (e.g. Msg4) transmission related parameter and NPUSCH format2 related parameter
  • the network node 120 can inform 92, via DCI 40, the user equipment 110 that the current grant is the last attempt for Msg4 (re) transmissions. The user equipment therefore knows whether to expect a future re-transmission. If not subsequent re-transmission is expected, the contention resolution timer can be stopped early to save user equipment power consumption.
  • the user equipment 110 is therefore configured to receive from a network node 120 an indication 92 of non-occurrence of retransmission of a downlink contention resolution message (Msg 4) 14 in a contention-based random-access (CBRA) procedure 60; and in dependence upon the received indication 92, the contention resolution timer is stopped in a contention-based random-access (CBRA) procedure 60.
  • Msg 4 downlink contention resolution message
  • CBRA contention-based random-access
  • a downlink control information 40 can be used as the indication 92.
  • the HARQ-ACK resource field in a downlink control information 40 can be modified to provide the indication 92.
  • the value of “HARQ-ACK resource” field defined as the indication 92 can be indicated through system information (SIB) signaling or defined in specification.
  • FIG 11 illustrates an example in which the user equipment 110 is configured to indicating, to a network node 120, a capability 70 for disablement at the user equipment 110 of hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message (Msg 4) 14 in a contention-based random-access (CBRA) procedure 60.
  • HARQ hybrid automatic request
  • Msg 4 downlink contention resolution message
  • the indication of capability 70 can, for example, occur as part of the CBRA procedure 60 for which hybrid automatic request (HARQ) feedback 20 is to be disabled.
  • the user equipment 110 is configured to indicate capability 70 for disablement 52 of HARQ feedback 20 at the user equipment 110 using an uplink message of the contention-based random-access (CBRA) procedure. For example, using the Random Access Request (Msg1) 11 and/or the Scheduled Uplink Transmission (Msg3) 13.
  • Msg1 Random Access Request
  • Msg3 Scheduled Uplink Transmission
  • the user equipment 110 is configured to indicate the capability 70 for disablement 52 of HARQ feedback 20 at the user equipment 110 by constraining detectable features of a random access request (Msg1) 11 in the contention-based random-access (CBRA) procedure 60.
  • Msg1 random access request
  • CBRA contention-based random-access
  • the user equipment 110 is configured to provide an implicit indication of the capability 70.
  • the user equipment 110 is configured to indicate the capability 70 for disablement 52 of HARQ feedback 20 at the user equipment 110 by selecting between different configurations for the random access request 11 in the contention-based random-access (CBRA) procedure 60, wherein a first set of configurations indicates a capability for disablement 52 and a second a second set of configurations indicates a lack of capability for disablement 52.
  • CBRA contention-based random-access
  • the different configurations for the random access request 11 can comprise one or more of:
  • this first subcarrier defines the remaining subcarriers used for frequency hopping during preamble transmission.
  • the random access is performed according to a configuration, which defines periodic occasions in the time domain, where the user equipment 110 can select between a certain number of subcarriers.
  • the user equipment 110 is configured to provide implicit indication of the capability 70 by selecting for use a preamble for the random access request 11 from a first predefined sub-set to indicate a first capability and selecting a preamble for the random access request (Msg1) from a second predefined sub-set to indicate a second capability (e.g. non-capability) and/or provide implicit indication of the capability 70 by selecting for use subcarriers for the random access request 11 from a first predefined sub-set to indicate a first capability and selecting subcarriers for the random access request (Msg1) 11 from a second predefined sub-set to indicate a second capability (e.g.
  • non-capability an/or provide implicit indication of the capability 70 by selecting for use time-domain resources for the random access request from a first predefined sub-set to indicate a first capability and means for selecting time-domain resources for the random access request from a second predefined sub-set to indicate a second capability (e.g. non-capability) .
  • the second predefined subsets are different (exclusive to) the respective first predefined sub-sets.
  • the user equipment 110 is configured to provide implicit indication of the capability 70 by:
  • a combination of characteristics for the random access request 11 e.g. preamble and/or subcarriers and/or time-domain resources
  • a second predefined sub-set different to the first sub-set
  • a second capability e.g. non-capability
  • the user equipment 110 is configured to provide explicit indication of the capability 70.
  • the user equipment 110 is configured to indicate, to the network, a capability for disablement 52 at the user equipment 110 of hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message 14 in a contention-based random-access (CBRA) procedure 60 using an explicit indication of the capability 70 by adapting scheduled uplink transmission 13 in the contention-based random-access (CBRA) procedure 60.
  • HARQ hybrid automatic request
  • the adapting scheduled uplink transmission 13 can, for example, provide an indication as a flag or modified bit field.
  • a bit can be dedicated to a HARQ feedback disabling flag.
  • the user equipment 110 positively indicates to the network a capability for disablement 52 at the user equipment 110 of hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message 14 in a contention-based random-access (CBRA) procedure 60.
  • the network node is enabled to provide an indication 50, to the user equipment 110, to indicate disablement 52 at the user equipment 110 of hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message in a contention-based random-access (CBRA) procedure 60.
  • the user equipment 110 negatively indicates to the network a capability for disablement 52 at the user equipment 110 of hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message 14 in a contention-based random-access (CBRA) procedure 60.
  • the user equipment 110 indicates a lack of capability.
  • the network node is not enabled to provide an indication 50, to the user equipment 110, to indicate disablement 52 at the user equipment 110 of hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message in a contention-based random-access (CBRA) procedure 60.
  • the user equipment 110 negatively indicates to the network a capability for disablement 52 at the user equipment 110 of hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message 14 in a contention-based random-access (CBRA) procedure 60.
  • the network node is nevertheless enabled to provide an indication 50, to the user equipment 110, to indicate disablement 52 at the user equipment 110 of hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message in a contention-based random-access (CBRA) procedure 60.
  • the user equipment 110 is unresponsive to the indication 50 and does not disable 52 the HARQ process.
  • the user equipment 110 shall follow its own capability and still attempt HARQ feedback transmission 20.
  • the network node 120 is configured to mitigate the effects of HARQ stalling.
  • HARQ stalling occurs when the network is waiting for completion of a HARQ process (waiting to receive the HARQ feedback message 20) but the wait is inefficient because, for example, there are long periods of waiting when there is unlikely to be a HARQ feedback message 20 received. This may, for example, be because of long transmission delays (large distance) between the user equipment 110 and the network node 120.
  • the network or network node 120 can be configured to determine HARQ stalling or a likelihood of HARQ stalling. Where the likelihood exceeds a threshold then the network nodes can transmit an indication 50, to the user equipment 110, to indicate disablement 52 at the user equipment 110 of hybrid automatic request (HARQ) feedback 20 for at least a downlink contention resolution message 14 in a contention-based random-access (CBRA) procedure 60.
  • the indication is sent in dependence on determining HARQ stalling or a likelihood of HARQ stalling.
  • the indication is sent in dependence on a measured or expected transmission delay between the network node 120 and the user equipment 110.
  • the user equipment 110/network node 120 can, for example, be user equipment/network node 120 conforming to the narrowband internet of things (NB-IoT) standardization requirements.
  • NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services.
  • NB-IoT significantly improves the power consumption of user equipment, system capacity and spectrum efficiency.
  • the user equipment 110/network node 120 can, for example, be user equipment/network node 120 conforming to 5G New Radio Reduced Capability user equipment (5G NR RedCap or 5G NR Lite) .
  • 5G New Radio Reduced Capability user equipment 5G NR RedCap or 5G NR Lite
  • the user equipment 110 can, for example, be user equipment (network node 120) conforming to the enhanced Machine-Type Communication (eMTC) standardization requirements.
  • eMTC enhanced Machine-Type Communication
  • the user equipment 110 can, for example, be user equipment (network node 120) conforming to Internet of Things Non-Terrestrial Network (IoT NTN) standardization requirements.
  • IoT NTN Internet of Things Non-Terrestrial Network
  • NB-IoT Narrow-Band Internet of Things
  • eMTC Enhanced Machine Type Communication
  • the network node 120 and the user equipment can, for example, be part of a very large scale network, with distances between them of over 100km.
  • the network node 120 can, for example, be node of a Non-Terrestrial Network (NTN) .
  • NTN Non-Terrestrial Network
  • the network node 120 can, for example, be node of a satellite network.
  • the base station is on Earth and satellite acts as a relay. In some satellite networks, the base station is on a satellite.
  • the network node 120 can therefore be on Earth or on a satellite.
  • the satellites can, for example, be low-earth orbit (LEO) satellites (altitude of 300 km –1500 km) .
  • the satellites can, for example, be geostationary earth orbit (GEO) satellites (altitude of about 36000 km) .
  • the network node 120 can, for example, be any transmission-reception point such as user equipment, a relay, or a base-station.
  • the user equipment 110 can be an Internet of Things (IoT) device.
  • IoT Internet of Things
  • Such devices have low complexity, low cost, low power consumption and low throughput, and key requirements of IoT services are extended coverage, delay-tolerant and infrequent data transmissions, and support of massive communications.
  • Disabling uplink HARQ feedback 20 in reply to downlink transmission benefits user equipment power consumption and latency. It also improves uplink throughput in an NTN as more resource would be available in uplink.
  • Disabling HARQ feedback 20 for downlink transmission can mitigate HARQ stalling which is due to the large round trip time (RTT) in NTN and will benefit UE power consumption and latency.
  • RTT round trip time
  • FIG 12 illustrates an example as previously described.
  • the network node 120 and the user equipment (UE) 110 support the HARQ feedback disabling for Msg4 14 in CBRA 60 and following signal radio bearer (SRB) scheduling.
  • SRB signal radio bearer
  • HARQ feedback disabling can be supported in a control plane (CP) solution, a user plane solution and early data transmission (EDT) . It enables quick scheduling for following SRB/RRC to transmit data in time, to both reduce the data transmission time and save UE energy consumption and uplink resources.
  • CP control plane
  • EDT early data transmission
  • the CP solution i.e., Control Plane CIoT EPS/5GS optimization
  • NB-IoT which enables support of user data (IP, non-IP) or SMS messages over control plane via the Mobility Management Entity (MME) without triggering data radio bearer establishment.
  • the control plane CIoT EPS optimization for NB-IoT UEs is characterized by: RRC connection reconfiguration is not supported; data radio bearer (DRB) is not used; AS security is not used; a non-anchor carrier can be configured for all unicast transmissions during RRC connection establishment or re-establishment.
  • the UL/DL NAS message carrying small data can be transmitted by a UL/DL RRC container message (e.g. RRCConnectionSetupComplete and/or following ULinformationTransfer/DLInformationTransfer in SRB1) and DRB is not used. Hence it can reduce the overall time for data transmission for small data.
  • NB-IoT/eMTC supports early data transmission (EDT) feature where single user packet is transmitted during RACH procedure 60. Since no RRC connection is established for EDT (i.e. no transition to RRC CONNECTED) , it is a further energy efficient procedure for small data transmission.
  • EDT early data transmission
  • MT-EDT is initiated by the MME and there is a single downlink data transmission during the random access procedure 60.
  • MO-EDT is triggered when the upper layers have requested the establishment or resumption of the RRC Connection for Mobile Originated data (i.e., not signaling or SMS) and allows one uplink data transmission optionally followed by one downlink data transmission during the random access procedure 60.
  • the RAN will trigger paging message for EDT, then the UE will initiate MO EDT procedure and sends paging response.
  • NB-IoT CP solution and EDT enable efficient data transmission between IoT devices and IoT applications/service to save UE’s energy consumption.
  • HARQ stalling may happen due to the long RTT (up to 540ms in GEO) and small HARQ process number (1 or 2 HARQ processes for category NB1 and NB2, respectively) in the case the required channel transmission time is less than the RTT. Due to high RTT, it may also cause scheduling delay after Msg4 (e.g. NW has to wait for HARQ feedback from UE for Msg4) which will delay the successive UL/DL RRC container message scheduling and transmission at least one RTT in the CP solution.
  • Msg4 e.g. NW has to wait for HARQ feedback from UE for Msg4
  • introducing HARQ feedback disabling for Msg4 will be beneficial since it enables quick scheduling for the following SRB/RRC to transmit data in time, thus to both reduce the data transmission time and save UE energy consumption.
  • the disabling of HARQ feedback is also beneficial since it will further reduce the UE energy consumption as UE will not transmit HARQ feedback repetitions.
  • the user equipment 110 and the network node 120 are communicating in accordance with NB-IoT.
  • Narrowband Primary Synchronization Signal (NPSS) 71, Narrowband Secondary Synchronization Signal (NSSS) 72, Narrowband Physical Broadcast Channel signal (NPBCH) 73 are transmitted from the network node 120 to the user equipment 110 to enable initial synchronization and master system information acquisition.
  • NPSS and NSSS are used by an NB-IoT UE to perform cell search, which includes time and frequency synchronization, and cell identity detection.
  • NPBCH carries the master information block (MIB) and is transmitted in subframe #0 in every frame.
  • the CBRA procedure 60 is performed with data downlink 30 but without uplink HARQ feedback messages for downlink Msg4 14 or downlink data message 30.
  • the CBRA procedure 60 has already been described.
  • An UL NAS message carrying small data is transmitted by the user equipment 110 in a UL container message 74 (e.g. RRCConnectionSetupComplete) and DRB is not used.
  • a UL container message 74 e.g. RRCConnectionSetupComplete
  • a DL NAS message (DL data message 30) carrying small data is transmitted by the network node 120 in DL RRC container message 75 (e.g. ULinformationTransfer/DLInformationTransfer in SRB1) and DRB is not used.
  • DL RRC container message 75 e.g. ULinformationTransfer/DLInformationTransfer in SRB1
  • the UE 110 indicates its HARQ feedback disabling capability 50 to the network before Msg4 14.
  • the UE 110 indicates the support of HARQ feedback disabling in Msg3 13 or Msg1 11.
  • the UE 110 will select the preamble from the dedicated preamble set if the UE supports HARQ feedback disabling for Msg4, while the UE will select another preamble if it does not support the HARQ feedback disabling.
  • the network Based on the UE’s transmission of the preamble in Msg1 11, the network (NW) will implicitly know the UE capability for HARQ feedback disabling for Msg4 based on the received preamble from the UE.
  • the implicit indication via a preamble set can also be based on selecting specific RACH resources in time and/or frequency domain in addition to/instead of the preamble sequence.
  • a dedicated preamble set can be configured by the network for each coverage enhancement (CE) level for UE to indicate UE can support the HARQ feedback disabling.
  • NW can configure a dedicated preamble set per coverage enhancement (CE) level to enable the UE to indicate the UE can support the HARQ feedback disabling.
  • UE 110 may indicate the support of HARQ feedback in Msg3 13, e.g. via a bit flag.
  • a bit can be dedicated to a HARQ feedback disabling flag.
  • NW 120 indicates HARQ feedback disabling for Msg4 and following SRB scheduling
  • the network can indicate HARQ feedback disabling in DCI/SIB/Msg4.
  • CE Coverage Enhancement
  • BS Base Station
  • PDCCH Physical Downlink Control
  • PDSCH Physical Downlink Control
  • PUSCH Physical Uplink Control
  • Coverage enhancement level 1 (robust) ⁇ +10dB for coverage enhancement, 144dB ⁇ MCL ⁇ 154dB
  • Coverage enhancement level 2 (extreme) ⁇ +20dB for coverage enhancement, MCL>154dB
  • HARQ feedback disabling can depend on the coverage enhancement (CE) level of the IoT UE and only apply for a certain coverage enhancement level. For example, for the high coverage enhancement level with lower RSRP/larger MCL and large repetition number, the HARQ stalling is less likely to happen and HARQ feedback enabling can be applied. For the low coverage enhancement level with higher RSRP/smaller maximum coupling loss (MCL) and small repetition number, the HARQ stalling is more likely to happen and HARQ feedback disabling can be applied.
  • the network is aware of the UE’s CE level based on the RA preamble transmission.
  • HARQ feedback disabling/enabling per CE level can be indicated through SIB signaling (i.e., in each of the CE level configurations) . It can be defined in specification that HARQ feedback disabling/enabling only applies to one or two coverage enhancement levels.
  • HARQ feedback disabling can depend on the coverage enhancement (CE) level of the IoT UE 110 and only apply for a certain coverage enhancement level. For example, for CE level 0 with higher RSRP/smaller MCL (e.g., MCL ⁇ 144dB) , the HARQ stalling is more likely to happen due to the small repetition number, thus HARQ feedback disabling can be applied. For CE level 2 with lower RSRP/larger MCL (e.g., MCL>154dB) , the HARQ stalling is less likely to happen due to the large repetition number, thus HARQ feedback enabling can be applied.
  • CE coverage enhancement
  • the network node 120 is configured to control HARQ feedback disabling /enabling per coverage level in SIB signaling together with the current signaling of two thresholds in rsrp-ThresholdsPrachInfoList.
  • the UE will determine the CE level based on the measured RSRP and the two signaled RSRP thresholds, then get the HARQ feedback disabling or enabling based on the CE level.
  • each coverage level is applied with HARQ feedback disabling or enabling is defined in the specification.
  • Coverage level 0 and coverage level 1 are defined with HARQ feedback disabling and Coverage level 2 is defined with HARQ feedback enabled in the specification.
  • HARQ feedback disabling/enabling is indicated in the Msg2 12.
  • DCI based HARQ feedback disabling/enabling signaling solutions can be used to indicate HARQ feedback disabling/enabling for Msg4 since the solution doesn’t need RRC configuration/reconfiguration.
  • “HARQ-ACK resource” in DCI format N1 can be re-defined to indicate HARQ feedback disabling/enabling.
  • DL HARQ feedback i.e., ACK/NACK
  • NPUSCH Narrowband Physical Uplink Shared Channel
  • One value of the current “HARQ-ACK resource” field can be re-defined to indicate HARQ feedback disabling. Both the feature that field “HARQ-ACK resource” is redefined to indicate HARQ feedback disabling/enabling and which value of “HARQ-ACK resource” field is defined to indicate HARQ feedback disabling can be indicated through SIB signaling or defined in specification.
  • the network node 120 can indicate 92 the non-occurrence of Msg4 retransmissions in DCI 40.
  • DCI format N1 which is used to indicate both the Narrowband Physical Downlink Shared Channel (NPDSCH) transmission related parameter and NPUSCH format2 related parameter
  • NPDSCH Narrowband Physical Downlink Shared Channel
  • the medium access control (MAC) entity in the user equipment 110 shall start /restart mac-ContentionResolutionTimer at each HARQ retransmission of the bundle in the subframe corresponding to the last subframe of a PUSCH transmission corresponding to the largest TBS indicated by the UL grant plus UE-eNB RTT subframes.
  • the UE will monitor the PDCCH until mac-ContentionResolutionTimer expires or is stopped. With this information, the UE can stop the contention resolution timer earlier to save UE power consumption.
  • NW Since it is NW’s scheduling decision on whether more Msg4 retransmission will be scheduled, if NW decides to stop Msg4 scheduling after current grant, NW can inform UE the current grant is the last attempt for Msg4 (re) transmissions. With this information, after decoding the corresponding NPDSCH and if the contention resolution is not successful, the UE can stop the contention resolution timer earlier to save UE power consumption.
  • the described examples enable the efficient data transmission between IoT devices and IoT applications/service for both CP solution and EDT, to save UE’s energy consumption in IoT NTN with high RTT.
  • the described example introduces the solution to support the HARQ feedback disabling for Msg4 and following SRB scheduling including both how UE indicate the HARQ feedback disabling UE capability to the network before Msg4 14 and the signaling solution to indicate the HARQ feedback disabling.
  • HARQ feedback disabling can be supported in CP solution and EDT and enable quick scheduling for following SRB/RRC to transmit data in time.
  • NW will not allocate the uplink resources for HARQ feedback when HARQ feedback is disabled for Msg4, NW can schedule UL grant (e.g., for Msg5) to implicitly feedback Msg4 is successfully decoded, which is beneficial to save both power consumption and UL resources.
  • UL grant e.g., for Msg5
  • HARQ hybrid automatic request
  • HARQ hybrid automatic request
  • a network node comprising means for: indicating, to at least a user equipment, disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure.
  • HARQ hybrid automatic request
  • Independent claims may be filed for user equipment comprising means for: indicating, to a network node, a capability for disablement at the user equipment of hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure.
  • HARQ hybrid automatic request
  • a network node comprising means for:
  • contention resolution timer is stopped in a contention-based random-access procedure.
  • Fig 13 illustrates an example of a controller 400 suitable for use in an apparatus 110, 120.
  • Implementation of a controller 400 may be as controller circuitry.
  • the controller 400 may be implemented in hardware alone, have certain aspects in software including firmware alone or can be a combination of hardware and software (including firmware) .
  • controller 400 may be implemented using instructions that enable hardware functionality, for example, by using executable instructions of a computer program 406 in a general-purpose or special-purpose processor 402 that may be stored on a computer readable storage medium (disk, memory etc) to be executed by such a processor 402.
  • a general-purpose or special-purpose processor 402 may be stored on a computer readable storage medium (disk, memory etc) to be executed by such a processor 402.
  • the processor 402 is configured to read from and write to the memory 404.
  • the processor 402 may also comprise an output interface via which data and/or commands are output by the processor 402 and an input interface via which data and/or commands are input to the processor 402.
  • the memory 404 stores a computer program 406 comprising computer program instructions (computer program code) that controls the operation of the apparatus 110, 120 when loaded into the processor 402.
  • the computer program instructions, of the computer program 406, provide the logic and routines that enables the apparatus to perform the methods illustrated in the accompanying Figs.
  • the processor 402 by reading the memory 404 is able to load and execute the computer program 406.
  • the apparatus 120 comprises:
  • processor 402 At least one processor 402;
  • At least one memory 404 including computer program code the at least one memory 404 and the computer program code configured to, with the at least one processor 402, cause the apparatus 120 at least to perform:
  • HARQ hybrid automatic request
  • the apparatus 110 comprises:
  • processor 402 At least one processor 402;
  • At least one memory 404 including computer program code the at least one memory 404 and the computer program code configured to, with the at least one processor 402, cause the apparatus 110 at least to perform: receiving from a network node an indication to disable hybrid automatic request (HARQ) feedback for at least a downlink contention resolution message in a contention-based random-access procedure; and
  • HARQ hybrid automatic request
  • HARQ hybrid automatic request
  • the apparatus 110 comprises:
  • processor 402 At least one processor 402;
  • At least one memory 404 including computer program code the at least one memory 404 and the computer program code configured to, with the at least one processor 402, cause the apparatus 110 at least to perform:
  • HARQ hybrid automatic request
  • the computer program 406 may arrive at the apparatus 110, 120 via any suitable delivery mechanism 408.
  • the delivery mechanism 408 may be, for example, a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a record medium such as a Compact Disc Read-Only Memory (CD-ROM) or a Digital Versatile Disc (DVD) or a solid-state memory, an article of manufacture that comprises or tangibly embodies the computer program 406.
  • the delivery mechanism may be a signal configured to reliably transfer the computer program 406.
  • the apparatus 110, 120 may propagate or transmit the computer program 406 as a computer data signal.
  • HARQ hybrid automatic request
  • HARQ hybrid automatic request
  • HARQ hybrid automatic request
  • HARQ hybrid automatic request
  • the computer program instructions may be comprised in a computer program, a non-transitory computer readable medium, a computer program product, a machine-readable medium. In some but not necessarily all examples, the computer program instructions may be distributed over more than one computer program.
  • memory 404 is illustrated as a single component/circuitry it may be implemented as one or more separate components/circuitry some or all of which may be integrated/removable and/or may provide permanent/semi-permanent/dynamic/cached storage.
  • processor 402 is illustrated as a single component/circuitry it may be implemented as one or more separate components/circuitry some or all of which may be integrated/removable.
  • the processor 402 may be a single core or multi-core processor.
  • references to ‘computer-readable storage medium’ , ‘computer program product’ , ‘tangibly embodied computer program’ etc. or a ‘controller’ , ‘computer’ , ‘processor’ etc. should be understood to encompass not only computers having different architectures such as single /multi-processor architectures and sequential (Von Neumann) /parallel architectures but also specialized circuits such as field-programmable gate arrays (FPGA) , application specific circuits (ASIC) , signal processing devices and other processing circuitry.
  • References to computer program, instructions, code etc. should be understood to encompass software for a programmable processor or firmware such as, for example, the programmable content of a hardware device whether instructions for a processor, or configuration settings for a fixed-function device, gate array or programmable logic device etc.
  • circuitry may refer to one or more or all of the following:
  • circuitry also covers an implementation of merely a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or other computing or network device.
  • the blocks illustrated in the accompanying Figs may represent steps in a method and/or sections of code in the computer program 406.
  • the illustration of a particular order to the blocks does not necessarily imply that there is a required or preferred order for the blocks and the order and arrangement of the block may be varied. Furthermore, it may be possible for some blocks to be omitted.
  • module refers to a unit or apparatus that excludes certain parts/components that would be added by an end manufacturer or a user.
  • the controller can be a module.
  • the above-described examples find application as enabling components of: automotive systems; telecommunication systems; electronic systems including consumer electronic products; distributed computing systems; media systems for generating or rendering media content including audio, visual and audio visual content and mixed, mediated, virtual and/or augmented reality; personal systems including personal health systems or personal fitness systems; navigation systems; user interfaces also known as human machine interfaces; networks including cellular, non-cellular, and optical networks; ad-hoc networks; the internet; the internet of things; virtualized networks; and related software and services.
  • the apparatus can be provided in an electronic device, for example, a mobile terminal, according to an example of the present disclosure. It should be understood, however, that a mobile terminal is merely illustrative of an electronic device that would benefit from examples of implementations of the present disclosure and, therefore, should not be taken to limit the scope of the present disclosure to the same. While in certain implementation examples, the apparatus can be provided in a mobile terminal, other types of electronic devices, such as, but not limited to: mobile communication devices, hand portable electronic devices, wearable computing devices, portable digital assistants (PDAs) , pagers, mobile computers, desktop computers, televisions, gaming devices, laptop computers, cameras, video recorders, GPS devices and other types of electronic systems, can readily employ examples of the present disclosure. Furthermore, devices can readily employ examples of the present disclosure regardless of their intent to provide mobility.
  • PDAs portable digital assistants
  • connection means operationally connected/coupled/in communication.
  • intervening components can exist (including no intervening components) , i.e., so as to provide direct or indirect connection/coupling/communication. Any such intervening components can include hardware and/or software components.
  • the term "determine/determining” can include, not least: calculating, computing, processing, deriving, measuring, investigating, identifying, looking up (for example, looking up in a table, a database or another data structure) , ascertaining and the like. Also, “determining” can include receiving (for example, receiving information) , accessing (for example, accessing data in a memory) , obtaining and the like. Also, “determine/determining” can include resolving, selecting, choosing, establishing, and the like.
  • a property of the instance can be a property of only that instance or a property of the class or a property of a sub-class of the class that includes some but not all of the instances in the class. It is therefore implicitly disclosed that a feature described with reference to one example but not with reference to another example, can where possible be used in that other example as part of a working combination but does not necessarily have to be used in that other example.
  • any reference to X comprising a/an/the Y indicates that X may comprise only one Y or may comprise more than one Y unless the context clearly indicates the contrary. If it is intended to use ‘a’ , ‘an’ or ‘the’ with an exclusive meaning then it will be made clear in the context. In some circumstances the use of ‘at least one’ or ‘one or more’ may be used to emphasis an inclusive meaning but the absence of these terms should not be taken to infer any exclusive meaning.
  • the presence of a feature (or combination of features) in a claim is a reference to that feature or (combination of features) itself and also to features that achieve substantially the same technical effect (equivalent features) .
  • the equivalent features include, for example, features that are variants and achieve substantially the same result in substantially the same way.
  • the equivalent features include, for example, features that perform substantially the same function, in substantially the same way to achieve substantially the same result.

Landscapes

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

Abstract

L'invention concerne un équipement utilisateur comprenant des moyens pour : recevoir d'un nœud de réseau une indication de désactivation d'une rétroaction de demande automatique hybride (HARQ) pour au moins un message de résolution de contention de liaison descendante dans une procédure d'accès aléatoire basée sur la contention ; et un moyen de désactivation, en fonction de l'indication reçue, d'une rétroaction de demande automatique hybride (HARQ) pour au moins un message de résolution de contention de liaison descendante dans une procédure d'accès aléatoire basée sur la contention.
PCT/CN2022/125531 2022-10-14 2022-10-14 Rétroaction de demande automatique hybride (harq) WO2024077639A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/125531 WO2024077639A1 (fr) 2022-10-14 2022-10-14 Rétroaction de demande automatique hybride (harq)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/125531 WO2024077639A1 (fr) 2022-10-14 2022-10-14 Rétroaction de demande automatique hybride (harq)

Publications (1)

Publication Number Publication Date
WO2024077639A1 true WO2024077639A1 (fr) 2024-04-18

Family

ID=90668612

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/125531 WO2024077639A1 (fr) 2022-10-14 2022-10-14 Rétroaction de demande automatique hybride (harq)

Country Status (1)

Country Link
WO (1) WO2024077639A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022025369A1 (fr) * 2020-07-28 2022-02-03 Lg Electronics Inc. Procédé et appareil de transmission d'une demande de planification de liaison montante dans un système de communication sans fil
US20220046677A1 (en) * 2020-10-22 2022-02-10 Intel Corporation Hybrid automatic repeat request (harq) enhancements for ultra-reliable low latency communication (urllc)
US20220095366A1 (en) * 2019-11-07 2022-03-24 Lg Electronics Inc. Method and apparatus for channel state reporting in wireless communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220095366A1 (en) * 2019-11-07 2022-03-24 Lg Electronics Inc. Method and apparatus for channel state reporting in wireless communication system
WO2022025369A1 (fr) * 2020-07-28 2022-02-03 Lg Electronics Inc. Procédé et appareil de transmission d'une demande de planification de liaison montante dans un système de communication sans fil
US20220046677A1 (en) * 2020-10-22 2022-02-10 Intel Corporation Hybrid automatic repeat request (harq) enhancements for ultra-reliable low latency communication (urllc)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
MCC SUPPORT: "Final Report of 3GPP TSG RAN WG1 #96b v1.0.0", 3GPP TSG RAN WG1 MEETING #97, R1-1905921, 9 May 2019 (2019-05-09), XP051739857 *
MEDIATEK INC.: "LCP impact of disabling HARQ uplink retransmission", 3GPP TSG RAN WG2 MEETING #112-E, R2-2008970, 23 October 2020 (2020-10-23), XP051942020 *

Similar Documents

Publication Publication Date Title
CN110945957B (zh) 执行随机接入过程的方法和装置
US20230189078A1 (en) Use of wait period to obtain on-demand system information for wireless networks
EP2869655B1 (fr) Procédés de gestion d'un accès aléatoire dans un système de communication sans fil, dispositif correspondant et serveur
KR20190135060A (ko) 랜덤 액세스 절차를 수행하는 방법 및 장치
KR20190052696A (ko) 향상된 경쟁 기반 랜덤 액세스 절차를 위한 방법 및 장치
KR20190029643A (ko) 차세대 통신 시스템에서 유연한 ue 대역폭을 지원하는 방법 및 장치
EP3611943B1 (fr) Procédé et appareil d'acquisition d'informations de système
US11178680B2 (en) Method, apparatus, and system for acquiring system information
CN113767677B (zh) 非许可频带中的随机接入消息重传
EP3282800A1 (fr) Procédé et appareil de renvoi de signalisation d'accès aléatoire
WO2013107036A1 (fr) Gestion d'un échec d'accès aléatoire
US20220022265A1 (en) Communicating between a terminal and a wireless network node
CN109587766B (zh) 按需系统信息请求响应、接收方法及装置、基站
WO2022022488A1 (fr) Procédé de transmission d'informations auxiliaires, dispositif terminal et dispositif réseau
US10143035B2 (en) Device and method of handling communication with communication device
CN110447275B (zh) 一种传输系统信息的方法、基站及终端
WO2024077639A1 (fr) Rétroaction de demande automatique hybride (harq)
CN113439467B (zh) 在终端和无线网络节点之间的通信
CN114503771B (zh) 在随机接入过程中监控窗口的终止
WO2020252633A1 (fr) Procédé, dispositif, et système de temporisation destinés à un préambule d'accès aléatoire
CN111132360B (zh) 消息发送、消息配置方法及装置、存储介质
WO2019158096A1 (fr) Procédé et dispositif de transmission de données lors d'un accès aléatoire
US20190158232A1 (en) Mobile apparatus and random access method therof
WO2023155998A1 (fr) Attribution de ressources radio sensible à l'état de rrc et économe en énergie

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

Country of ref document: EP

Kind code of ref document: A1