[go: up one dir, main page]

WO2024159403A1 - Relaxation de temps de traitement - Google Patents

Relaxation de temps de traitement Download PDF

Info

Publication number
WO2024159403A1
WO2024159403A1 PCT/CN2023/073997 CN2023073997W WO2024159403A1 WO 2024159403 A1 WO2024159403 A1 WO 2024159403A1 CN 2023073997 W CN2023073997 W CN 2023073997W WO 2024159403 A1 WO2024159403 A1 WO 2024159403A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
network device
processing time
transmission
uplink transmission
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/CN2023/073997
Other languages
English (en)
Inventor
Rapeepat Ratasuk
Jie Gao
Navin Hathiramani
Man Hung Ng
Nitin MANGALVEDHE
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.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
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 CN202380092788.0A priority Critical patent/CN120604480A/zh
Priority to PCT/CN2023/073997 priority patent/WO2024159403A1/fr
Publication of WO2024159403A1 publication Critical patent/WO2024159403A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1854—Scheduling and prioritising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1812—Hybrid protocols; Hybrid automatic repeat request [HARQ]
    • H04L1/1819—Hybrid protocols; Hybrid automatic repeat request [HARQ] with retransmission of additional or different redundancy

Definitions

  • Various example embodiments relate to the field of telecommunication and in particular, to methods, devices, apparatuses, and computer readable storage media for processing time relaxation.
  • RedCap reduced capability
  • eRedCap enhanced version
  • UE user equipment
  • MIMO downlink multiple input multiple output
  • the RedCap UE is configured with lower capabilities, for example, in terms of device bandwidth, an antenna configuration, a downlink multiple input multiple output (MIMO) support, a duplex operation, a maximum modulation, a peak data rate, etc.
  • MIMO downlink multiple input multiple output
  • example embodiments of the present disclosure provide a solution related to processing time relaxation.
  • a terminal device comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device at least to: determine that a processing time is insufficient to prepare an uplink transmission to a network device; and inform the network device that the processing time is insufficient.
  • a network device comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the network device at least to: determine, based on communicating with a terminal device, that a first processing time is insufficient for the terminal device to prepare an uplink transmission to the network device; and receive, from the terminal device, the uplink transmission based on a second processing time sufficient for the terminal device to prepare the uplink transmission.
  • a method implemented at a terminal device comprises determining that a processing time is insufficient to prepare an uplink transmission to a network device; and informing the network device that the processing time is insufficient.
  • an apparatus comprises means for determining, at a terminal device, that a processing time is insufficient to prepare an uplink transmission to a network device; and means for informing the network device that the processing time is insufficient.
  • an apparatus comprises means for determining, at a network device, based on communicating with a terminal device, that a first processing time is insufficient for the terminal device to prepare an uplink transmission to the network device; and means for receiving, from the terminal device, the uplink transmission based on a second processing time sufficient for the terminal device to prepare the uplink transmission.
  • a non-transitory computer readable medium comprising program instructions for causing an apparatus to perform at least the method according to any one of the above third to fourth aspect.
  • a computer program comprising instructions, which, when executed by an apparatus, cause the apparatus at least to perform at least the method according to any one of the above third to fourth aspect.
  • a terminal device comprising determining circuitry configured to determine that a processing time is insufficient to prepare an uplink transmission to a network device; and informing circuitry configured to inform the network device that the processing time is insufficient.
  • a network device comprising determining circuitry configured to determine, based on communicating with a terminal device, that a first processing time is insufficient for the terminal device to prepare an uplink transmission to the network device; and receiving circuitry configured to receive, from the terminal device, the uplink transmission based on a second processing time sufficient for the terminal device to prepare the uplink transmission.
  • FIG. 1A illustrates an example environment in which example embodiments of the present disclosure can be implemented
  • FIG. 1B and FIG. 1C shows UE processing times associated with scheduling for DL and UL transmission cases according to some example embodiments of the present disclosure respectively;
  • FIG. 2 illustrates a signaling flow between a terminal device and a network device according to some example embodiments of the present disclosure
  • FIG. 3 illustrates a first example communication process between a UE and a gNB according to some example embodiments of the present disclosure
  • FIG. 4 illustrates a second example communication process between a UE and a gNB according to some example embodiments of the present disclosure
  • FIG. 5 illustrates a third example communication process between a UE and a gNB according to some example embodiments of the present disclosure
  • FIG. 6 illustrates a fourth example communication process between a UE and a gNB according to some example embodiments of the present disclosure
  • FIG. 7 illustrates a fifth example communication process between a UE and a gNB according to some example embodiments of the present disclosure
  • FIG. 8 illustrates a flowchart of a method implemented at a terminal device according to some embodiments of the present disclosure
  • FIG. 9 illustrates a flowchart of a method implemented at a network device according to some embodiments of the present disclosure
  • FIG. 10 illustrates a simplified block diagram of a device that is suitable for implementing some example embodiments of the present disclosure.
  • FIG. 11 illustrates a block diagram of an example of a computer readable medium in accordance with some example embodiments of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an embodiment, ” “an example embodiment, ” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • circuitry may refer to one or more or all of the following:
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of 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 or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR) , Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on.
  • NR New Radio
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
  • the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a New Radio (NR) NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, a low power node such as a femto, a pico, and so forth, depending on the applied terminology and technology.
  • BS base station
  • AP access point
  • NodeB or NB node B
  • eNodeB or eNB evolved NodeB
  • NR New Radio
  • RRU Remote Radio Unit
  • RH radio header
  • RRH remote radio head
  • terminal device refers to any end device that may be capable of wireless communication.
  • a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • UE user equipment
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • FIG. 1A illustrates an example environment 100 in which example embodiments of the present disclosure can be implemented.
  • the environment 100 which may be a part of a communication network, comprises a terminal device 110 and a network device 120 communicating with each other or with other devices via each other.
  • the communication environment 100 may comprise any suitable number of devices and cells.
  • the terminal device 110 and the network device 120 can communicate data and control information with each other.
  • a link from the network device 120 to the terminal device 110 is referred to as a downlink (DL)
  • a link from the terminal device 110 to the network device 120 is referred to as an uplink (UL) .
  • the environment 100 may comprise a further device to communicate with the terminal device 110 and network device 120.
  • the communications in the environment 100 may follow any suitable communication standards or protocols, which are already in existence or to be developed in the future, such as Universal Mobile Telecommunications System (UMTS) , long term evolution (LTE) , LTE-Advanced (LTE-A) , the fifth generation (5G) New Radio (NR) , Wireless Fidelity (Wi-Fi) and Worldwide Interoperability for Microwave Access (WiMAX) standards, and employs any suitable communication technologies, including, for example, Multiple-Input Multiple-Output (MIMO) , Orthogonal Frequency Division Multiplexing (OFDM) , time division multiplexing (TDM) , frequency division multiplexing (FDM) , code division multiplexing (CDM) , Bluetooth, ZigBee, and machine type communication (MTC) , enhanced mobile broadband (eMBB) , massive machine type communication (mMTC) , ultra-reliable low latency communication (URLLC) , Carrier Aggregation (CA) , Dual Connectivity (DC) ,
  • the RedCap UE As described above, to facilitate complexity reduction and thus save power consumption, the RedCap UE has been proposed.
  • release 17 (Rel-17)
  • the third generation partnership project (3GPP) has specified the RedCap UE with the following capabilities as shown in Table 1.
  • Table 1 Reduced capability NR devices.
  • the 3GPP is specifying further device complexity reduction in Frequency range 1 (FR1) .
  • the goal is to introduce lower-tier devices between massive internet of things (IoT) and Rel-17 RedCap devices.
  • the supported peak data rate for the new Rel-18 devices is expected to be around 10 Mbps.
  • the work item description RP-223544 contains the following objective:
  • FIG. 1B and FIG. 1C shows UE processing times associated with scheduling for DL and UL transmission cases according to some example embodiments of the present disclosure respectively. These two UE processing times associated with scheduling are described in technical specification (TS) 38.214.
  • the UE processing time associated with scheduling for DL transmission is used to prepare hybrid automatic repeat request (HARQ) feedback for a physical downlink shared channel (PDSCH) .
  • the UE processing time associated with scheduling for DL transmission is associated with the PDSCH-to-HARQ-feedback timing indicator field.
  • the UE processing time associated with scheduling for DL transmission is associated with the parameter K1 as described in section 5.3 of TS 38.214.
  • the UE processing time associated with scheduling for UL transmission is used to prepare a transmission on a physical uplink shared channel (PUSCH) .
  • the UE processing time associated with scheduling for UL transmission is associated with time domain resource assignment.
  • the UE processing time associated with scheduling for UL transmission is associated with the slot offset parameter K2 as described in section 6.1.2.1 of TS 38.214.
  • the parameters K1 and K2 are dependent on parameter N1 (see Tables 5.3-1 and 5.3.2 in section 5.3 of TS 38.214) and parameter N2 (see Section 6.4 of TS 38.214) .
  • the parameters K1 and K2 and their relationship to parameters N1 and N2 are illustrated in FIG. 1B and FIG. 1C respectively.
  • the UE processing time associated with scheduling for DL transmission, T proc, 1 which is dependent on the parameter N 1 , is denoted as:
  • T proc, 1 (N 1 +d 1, 1 +d 2 ) (2048+144) ⁇ 2 - ⁇ ⁇ T C +T ext
  • - N 1 is based on ⁇ of table 5.3-1 and table 5.3-2 for UE processing capability 1 and 2 respectively, where ⁇ corresponds to the one of ( ⁇ PDCCH , ⁇ PDSCH , ⁇ UL ) resulting with the largest T proc, 1 , where the ⁇ PDCCH corresponds to the subcarrier spacing of the PDCCH scheduling the PDSCH, the ⁇ PDSCH corresponds to the subcarrier spacing of the scheduled PDSCH, and ⁇ UL corresponds to the subcarrier spacing of the uplink channel with which the HARQ-ACK is assumed to be transmitted regardless of whether or not the PDSCH reception provides a transport block for a HARQ process with disabled HARQ-ACK information as indicated by HARQ-feedbackEnabling-disablingperHARQprocess, if provided, and ⁇ is defined in clause 4.1 of [4, TS 38.211] .
  • the first uplink symbol which carries the HARQ-ACK information further includes the effect of timing difference between the component carriers as given in [11, TS 38.133] .
  • mapping type B as given in clause 7.4.1.1 of [4, TS 38.211] .
  • d 1, 1 3+min (d, 1) , where d is the number of overlapping symbols of the scheduling PDCCH and the scheduled PDSCH.
  • d 1, 1 3+d, where d is the number of overlapping symbols of the scheduling PDCCH and the scheduled PDSCH.
  • d 1, 1 is the number of overlapping symbols of the scheduling PDCCH and the scheduled PDSCH
  • d 1, 1 is the number of overlapping symbols of the scheduling PDCCH and the scheduled PDSCH.
  • the UE processing time associated with scheduling for UL transmission, T proc, 2 which is dependent on the parameter N 2 , is denoted as:
  • T proc, 2 max ( (N 2 +d 2, 1 +d 2 ) (2048+144) ⁇ 2 - ⁇ ⁇ T C +T ext +T switch , d 2, 2 )
  • - N 2 is based on ⁇ of Table 6.4-1 and Table 6.4-2 for UE processing capability 1 and 2 respectively, where ⁇ corresponds to the one of ( ⁇ UL , ⁇ DL ) resulting with the largest T proc, 2 , where the ⁇ DL corresponds to the subcarrier spacing of the downlink with which the PDCCH carrying the downlink control information (DCI) scheduling the PUSCH was transmitted and ⁇ UL corresponds to the subcarrier spacing of the uplink channel with which the PUSCH is to be transmitted, and ⁇ is defined in clause 4.1 of [4, TS 38.211] .
  • the first uplink symbol in the PUSCH allocation further includes the effect of timing difference between component carriers as given in [11, TS 38.133] .
  • the gNB uses always relaxed parameter K1/K2 until the UE capability is known (for example, the gNB can obtain UE capability in message 5 (Msg5) of the random access procedure) .
  • the gNB uses longer processing time (i.e. use larger parameter K1/K2) when scheduling the PDSCH/PUSCH.
  • this solution causes an additional latency problem for the non-eRedCap UEs (i.e. legacy Rel-17 UEs) .
  • an additional access delay of 3-6 ms could be incurred during initial access for the non-eRedCap UEs, which could be significant for delay-sensitive applications.
  • the gNB handles this situation via implementation.
  • the gNB may define separate random access resources for the RedCap UEs or use message 1 (Msg1) to identify all RedCap UEs, then only the RedCap UEs will have longer access time.
  • Msg1 message 1
  • additional overhead random access resource overhead
  • a terminal device determines that a processing time is insufficient to prepare an uplink transmission to a network device. Moreover, the terminal device informs the network device that the processing time is insufficient.
  • This scheme allows processing time relaxation to be implemented in the eRedCap terminal devices without impact on system access latency for the non-eRedCap terminal devices. In this way, it is possible to avoid system overhead, enable additional cost savings, and improve transmission efficiency.
  • This scheme can work without having to first identify the RedCap UE in Msg1.
  • FIG. 2 illustrates a signaling flow 200 between the terminal device 110 and the network device 120 according to some example embodiments of the present disclosure.
  • the signaling flow 200 will be described with reference to FIG. 1A.
  • the terminal device 110 determines (205) that a processing time (also referred to as a first processing time) is insufficient to prepare an uplink transmission to the network device 120.
  • a processing time also referred to as a first processing time
  • the terminal device 110 may be a RedCap UE with a relaxed processing capability.
  • the processing time may be associated with scheduling.
  • the processing time may be a legacy processing time, i.e. a shorter processing time compared to a relaxed processing time defined for eRedCap UEs, i.e. a longer processing time, associated with the relaxed processing capability.
  • the uplink transmission may comprise a transmission of HARQ feedback for a PDSCH (for example, HARQ feedback for a Msg4 transmission) from the network device 120, and in this case, the processing time may be used by the terminal device 110 to prepare the HARQ feedback.
  • the uplink transmission may comprise a transmission of a PUSCH (for example, a Msg3/5 transmission) , and in this case, the processing time may be used by the terminal device 110 to prepare the transmission on the PUSCH.
  • the terminal device 110 informs (210) the network device 120 that the processing time is insufficient. Accordingly, the network device 120 determines (215) , based on communicating with the terminal device 110, that the processing time is insufficient for the terminal device 110 to prepare an uplink transmission to the network device 120.
  • the terminal device 110 may transmit, to the network device 120, an indication that the processing time is insufficient, such that the network device 120 may be informed of the insufficient processing time. Then, upon receiving the indication from the terminal device 110, the network device 120 may determine that the processing time is insufficient for the terminal device 110 to prepare the uplink transmission. For example, the terminal device 110 may transmit, to the network device 120, an indication that the processing time configured in the DCI is too short.
  • the terminal device 110 may indicate to the network device 120 via a PUCCH that it is not able to meet the processing time (for example, using the PDSCH-to-HARQ_feedback timing indicator) requested by the network device 120.
  • the indication may be transmitted on a PUCCH on which the HARQ feedback is scheduled or configured.
  • the terminal device 110 may use the allocated PUCCH to transmit a message indicating the insufficient processing time.
  • the indication may be transmitted on a semi-persistently configured PUCCH for the terminal device 110 to transmit the indication.
  • the terminal device 110 may employ a semi-statically configured PUCCH configuration to indicate the need for additional processing time.
  • the terminal device 110 may indicate to the network device 120 via the PUSCH or PUCCH that it cannot meet the processing time (for example, the slot offset parameter for PUSCH) requested by the network device 120.
  • the indication may be transmitted on a media access control (MAC) message mapped to the PUSCH.
  • the indication may be transmitted in a short MAC message to indicate the insufficient PUSCH preparation time.
  • the indication may be transmitted on a PUCCH in an existing format with a configuration defined for the indication using a transmission resource on which the PUSCH is scheduled or configured. In this case, the PUCCH may use an existing format with a different configuration.
  • the indication may be transmitted on a PUCCH in a new format defined for the indication using a transmission resource on which the PUSCH is scheduled or configured.
  • the indication may be transmitted on a special PUCCH in Msg3 resource block location to indicate the additional processing time required by the terminal device 110 in order to allow the network device 120 to allocate UL resources for the PUSCH transmission.
  • the special PUCCH may be energy feedback in the last few symbols of the Msg3 for the indication of the insufficient processing time.
  • the terminal device transmits (220) , to the network device 120, the uplink transmission based on another processing time (also referred to as a second processing time) , which is sufficient for the terminal device 110 to prepare the uplink transmission.
  • the network device 120 receives (225) , from the terminal device 110, the uplink transmission based on the second processing time.
  • the second processing time may be a relaxed processing time defined for eRedCap UEs associated with the relaxed processing capability.
  • the terminal device 110 may determine a second transmission resource available for the uplink transmission, for example, based on the second processing time. The terminal device 110 may further transmit, to the network device 120, the uplink transmission on the second transmission resource. Accordingly, after determining that the first processing time is insufficient, the network device 120 may determine the second transmission resource and then receive the uplink transmission on the second transmission resource from the terminal device 110.
  • the second transmission resource may be pre-reserved or pre-configured for the uplink transmission.
  • an additional resource for the uplink transmission may be pre-reserved or pre-configured (for example, implicitly determined based on the current resource for the uplink transmission) for the purpose that the terminal device 110 can transmit the uplink transmission after preparing the uplink transmission.
  • the network device 120 may transmit a new PDCCH grant with a retransmission for the PDSCH to meet the second processing time for the terminal device 110.
  • the network device 120 may reschedule the second transmission resource for the uplink transmission using a parameter for transmitting the uplink transmission based on the second processing time, for example, a longer parameter compared with a legacy parameter.
  • the network device 120 may transmit the parameter to the terminal device 110.
  • the network device 120 may transmit the parameter to the terminal device 110 if it determines that the first processing time is insufficient.
  • the terminal device 110 may then determine the second transmission resource.
  • the parameter may comprise a first parameter for determining a transmission timing of the HARQ feedback for the PDSCH.
  • the first parameter may be the parameter K1 as described above.
  • the network device 120 may perform the rescheduling using a longer parameter K1 for the Msg4.
  • the parameter may comprise a second parameter for determining a transmission timing of transmitting the PUSCH.
  • the second parameter may be the parameter K2 as described above. In this case, the network device 120 may perform the rescheduling using a longer parameter K2 for the PUSCH.
  • the pre-reserved or pre-configured second transmission resource may be used to transmit the HARQ feedback.
  • the network device 120 may reschedule the second transmission resource for the uplink transmission using a longer parameter K1.
  • the network device 120 may either reschedule the downlink transmission for the PDSCH (for example, the Msg4) or listen for the PUCCH in an occasion which is aligned with the second processing time, i.e., the relaxed processing time.
  • the terminal device 110 may provide NACK feedback to the network device 120.
  • the network device 120 may not reschedule the downlink transmission for the PDSCH (for example, the Msg4) , but the terminal device 110 and the network device 120 may determine a new transmission resource (for example, new timing and location) for the uplink transmission for the PDSCH based on a relaxed processing capability, for example, the relaxed transmission timing of the eRedCap UE.
  • the network device 120 may transmit, to the terminal device 110, an indication of a retransmission of the PDSCH, and then retransmit the PDSCH to the terminal device 110.
  • the terminal device 110 may first determine whether the processing of an initial transmission (for example, initial Msg4 transmission) of the PDSCH is successful. If it is determined that the processing of an initial transmission is successful, the terminal device 110 may ignore the retransmission of the PDSCH. In other words, if the terminal device 110 is able to successfully decode the original transmission, it may discard or ignore the processing of the retransmission of the PDSCH.
  • the terminal device 110 may determine the HARQ feedback based on a result of the processing of the initial transmission. Otherwise, if it is determined that the processing of an initial transmission is unsuccessful, the terminal device 110 may perform HARQ combining of the initial transmission and the retransmission of the PDSCH, and then determine the HARQ feedback based on a result of the HARQ combining.
  • the network device 120 may request the terminal device 110 to process the retransmission via the DCI (implicitly or explicitly) and allow for additional processing time for this.
  • an explicit indication via the DCI may be transmitted when the value of the parameter K1 is sufficiently large to process the original transmission and retransmission of the PDSCH considering the timing of the PDCCH grant for the PDSCH.
  • the network device 120 may detect this and assume that the terminal device 110 does not have enough processing time. Then, as an example, the network device 120 may reschedule the uplink transmission for a longer preparation time, using, for example, the longer parameter K1/K2. As another example, after omitting to transmit the uplink transmission on a transmission resource, the terminal device 110 may postpone the uplink transmission to a next available transmission resource. The network device 120 may receive the uplink transmission on the next available transmission resource. For the DL transmission cases, the terminal device 110 may delay the HARQ feedback until the next PUCCH, and in this case, the network device 120 may then need to check 2 HARQ feedback regions.
  • this proposed scheme can work without having to first identify the terminal device 110 as the RedCap UE in Msg1.
  • FIG. 3 illustrates a first example communication process 300 between a UE 301 and a gNB 303 according to some example embodiments of the present disclosure.
  • FIG. 3 shows an example signaling diagram for downlink processing time indication.
  • the process flow 300 may be considered as an example of the signaling flow 200 as shown in FIG. 2.
  • the UE 301 may be an example of the terminal device 110
  • the gNB 303 may be an example of the network device 120.
  • the gNB 303 transmits a synchronization signal block (SSB) with a master information block (MIB) to the UE 301.
  • the gNB 303 transmits a system information block (SIB) to the UE 301.
  • the UE 301 transmits a Msg1 on a physical random access channel (PRACH) to the gNB 303.
  • the UE 301 transmits a Msg3 on a PUSCH to the gNB 303.
  • the gNB 303 transmits a PDCCH with a parameter K1, for example, a legacy parameter K1 (i.e. a shorter parameter K1) to the UE 301.
  • the gNB 303 transmits a Msg4 on a PDSCH to the UE 301.
  • the UE 301 determines that it cannot meet the assigned K1 processing time which is determined based on the parameter K1.
  • the UE 301 transmits, to the gNB 303, a PUCCH indicating that the assigned K1 processing time is insufficient, using a K1 timing which is determined based on the parameter K1.
  • the gNB 303 determines a new K1 timing, i.e., a new parameter K1, for example, a longer parameter K1.
  • the gNB 303 transmits, to the UE 301, a PDCCH with the longer parameter K1 and indicating a Msg4 retransmission.
  • the gNB 303 retransmits the PDSCH with the Msg4 to the UE 301.
  • the UE 301 transmits a PUCCH with the HARQ feedback, i.e. ACK or NACK feedback, to the gNB 303 based on the relaxed transmission timing determined based on the longer parameter K1.
  • FIG. 4 illustrates a second example communication process 300 between a UE 401 and a gNB 403 according to some example embodiments of the present disclosure.
  • FIG. 4 shows another example signaling diagram for downlink processing time indication.
  • the process flow 400 may be considered as an example of the signaling flow 200 as shown in FIG. 2.
  • the UE 401 may be an example of the terminal device 110
  • the gNB 403 may be an example of the network device 120.
  • the gNB 403 transmits a SSB with a MIB to the UE 401.
  • the gNB 403 transmits a SIB1 to the UE 401.
  • the UE 401 transmits a Msg1 on a PRACH to the gNB 403.
  • the UE 401 transmits a Msg3 on a PUSCH to the gNB 403.
  • the gNB 403 transmits a PDCCH with a parameter K1, for example, a legacy parameter K1 (i.e. a shorter parameter K1) to the UE 401.
  • a parameter K1 for example, a legacy parameter K1 (i.e. a shorter parameter K1)
  • the gNB 403 transmits a Msg4 on a PDSCH to the UE 401.
  • the UE 401 determines that it cannot meet the assigned K1 processing time which is determined based on the parameter K1.
  • the UE 401 transmits, to the gNB 403, a PUCCH indicating that the assigned K1 processing time is insufficient, using a K1 timing which is determined based on the parameter K1.
  • the UE 401 determines a new PUCCH resource for transmitting the HARQ feedback, i.e. ACK or NACK feedback.
  • the new PUCCH resource may be pre-reserved or pre-configured for the HARQ feedback.
  • the UE 401 transmits a PUCCH with the HARQ feedback, i.e. ACK or NACK feedback, to the gNB 403 using the new resource.
  • FIG. 5 illustrates a third example communication process 500 between a UE 501 and a gNB 503 according to some example embodiments of the present disclosure.
  • FIG. 5 shows a further example signaling diagram for downlink processing time indication.
  • the process flow 500 may be considered as an example of the signaling flow 200 as shown in FIG. 2.
  • the UE 501 may be an example of the terminal device 110
  • the gNB 503 may be an example of the network device 120.
  • the gNB 503 transmits a SSB with a MIB to the UE 501.
  • the gNB 503 transmits a SIB1 to the UE 501.
  • the UE 501 transmits a Msg1 on a PRACH to the gNB 503.
  • the UE 501 transmits a Msg3 on a PUSCH to the gNB 503.
  • the gNB 503 transmits a PDCCH with a parameter K1, for example, a legacy parameter K1 (i.e. a shorter parameter K1) to the UE 501.
  • a parameter K1 for example, a legacy parameter K1 (i.e. a shorter parameter K1)
  • the gNB 503 transmits a Msg4 on a PDSCH to the UE 501.
  • the UE 501 determines that it cannot meet the assigned K1 processing time which is determined based on the parameter K1.
  • the UE 501 transmits, to the gNB 503, a PUCCH indicating that the assigned K1 processing time is insufficient, using a K1 timing which is determined based on the parameter K1.
  • the UE 501 completes the processing of the PDSCH.
  • the gNB 503 determines a new K1 timing, i.e., a new parameter K1, for example, a longer parameter K1.
  • the gNB 503 transmits, to the UE 501, a PDCCH with the longer parameter K1 and indicating a Msg4 retransmission. Then, the gNB 503 retransmits the PDSCH with the Msg4 to the UE 501.
  • the UE 501 determines whether the processing of the PDSCH is successful.
  • the UE 501 may ignore the retransmission. In this case, the UE 501 may determine the HARQ feedback based on a result of the first PDSCH transmission, i.e., the initial PDSCH transmission. Otherwise, if the UE 501 receives the first PDSCH incorrectly, it may then perform HARQ combining of the first PDSCH transmission and the retransmission of the PDSCH and determine the HARQ feedback based on a result of the HARQ combining.
  • the UE 501 transmits a PUCCH with the HARQ feedback, i.e. ACK or NACK feedback to the gNB 503 based on the relaxed transmission timing determined based on the longer parameter K1.
  • FIG. 6 illustrates a fourth example communication process 600 between a UE 601 and a gNB 603 according to some example embodiments of the present disclosure.
  • FIG. 6 shows an example signaling diagram for uplink processing time indication using a PUSCH.
  • the process flow 600 may be considered as an example of the signaling flow 200 as shown in FIG. 2.
  • the UE 601 may be an example of the terminal device 110
  • the gNB 603 may be an example of the network device 120.
  • the gNB 603 transmits a SSB with a MIB to the UE 601.
  • the gNB 603 transmits a SIB1 to the UE 601.
  • the UE 601 transmits a Msg1 on a PRACH to the gNB 603.
  • the gNB 603 transmits a PDCCH with a parameter K2, for example, a legacy parameter K2 (i.e. a shorter parameter K2) .
  • the gNB 603 transmits, to the UE 601, a PDSCH with a Msg2 comprising a random access response (RAR) uplink grant.
  • the UE 601 determines that it cannot meet the assigned Msg3 preparation time which is determined based on the parameter K2.
  • the UE 601 transmits, to the gNB 603, a PUSCH indicating that the assigned Msg3 preparation time is insufficient, using a K2 timing which is determined based on the parameter K2.
  • the gNB 603 determines a relaxed parameter K2, i.e., a relaxed timing.
  • the gNB 603 transmits, to the UE 601, a PDCCH with the relaxed parameter K2 and indicating a Msg3 retransmission.
  • the UE 601 retransmits the PUSCH with the Msg3 to the gNB 603 based on the relaxed timing determined based on the relaxed parameter K2.
  • FIG. 7 illustrates a fifth example communication process 700 between a UE 701 and a gNB 703 according to some example embodiments of the present disclosure.
  • FIG. 7 shows an example signaling diagram for uplink processing time indication using a PUCCH.
  • the process flow 700 may be considered as an example of the signaling flow 200 as shown in FIG. 2.
  • the UE 701 may be an example of the terminal device 110
  • the gNB 703 may be an example of the network device 120.
  • the gNB 703 transmits a SSB with a MIB to the UE 701.
  • the gNB 703 transmits a SIB1 to the UE 701.
  • the UE 701 transmits a Msg1 on a PRACH to the gNB 703.
  • the gNB 703 transmits a PDCCH with a parameter K2, for example, a legacy parameter K2 (i.e. a shorter parameter K2) .
  • the gNB 703 transmits, to the UE 701, a PDSCH with a Msg2 comprising a RAR uplink grant.
  • the UE 701 determines that it cannot meet the assigned Msg3 preparation time which is determined based on the parameter K2.
  • the UE 701 transmits, to the gNB 703, a PUCCH (using, for example, format F0 or F1) indicating that the assigned Msg3 preparation time is insufficient.
  • the gNB 703 determines a relaxed parameter K2, i.e., a relaxed timing.
  • the gNB 703 transmits, to the UE 701, a PDCCH with the relaxed parameter K2 and indicating a Msg3 retransmission.
  • the UE 701 retransmits the PUSCH with the Msg3 to the gNB 703 based on the relaxed timing determined based on the relaxed parameter K2.
  • FIG. 8 illustrates a flowchart 800 of a method implemented at a terminal device according to some embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the terminal device 110 with reference to FIG. 1A.
  • the terminal device 110 determines that a processing time is insufficient to prepare an uplink transmission to a network device 120.
  • the terminal device 110 informs the network device 120 that the processing time is insufficient.
  • the terminal device 110 may transmit, to the network device 120, an indication that the processing time is insufficient.
  • the uplink transmission may comprise a transmission of HARQ feedback for a physical downlink shared channel (PDSCH) .
  • the indication may be transmitted on a physical uplink control channel (PUCCH) on which the HARQ feedback is scheduled or configured, a semi-persistently configured PUCCH for the terminal device 110 to transmit the indication, or any combination of the above-listed items.
  • PUCCH physical uplink control channel
  • the uplink transmission may comprise a transmission of a physical uplink shared channel (PUSCH) .
  • the indication may be transmitted in a media access control (MAC) message mapped to the PUSCH, a PUCCH in an existing format with a configuration defined for the indication using a transmission resource on which the PUSCH is scheduled or configured, a PUCCH in a new format defined for the indication using a transmission resource on which the PUSCH is scheduled or configured, or any combination of the above-listed items.
  • MAC media access control
  • the terminal device 110 may omit to transmit the uplink transmission on a transmission resource on which the uplink transmission is scheduled or configured.
  • the uplink transmission may be scheduled or configured on a first transmission resource, and in this case, the terminal device 110 may further, subsequent to determining that the processing time is insufficient, determine a second transmission resource available for the uplink transmission; and then transmit, to the network device 120, the uplink transmission on the second transmission resource.
  • the second transmission resource may be pre-reserved or pre-configured for the uplink transmission.
  • the terminal device 110 may further receive, from the network device 120, a parameter for transmitting the uplink transmission based on a second processing time sufficient to prepare the uplink transmission; and then determine the second transmission resource based on the parameter.
  • the parameter may comprise a first parameter for determining a transmission timing of hybrid automatic repeat request (HARQ) feedback for a PDSCH, or a second parameter for determining a transmission timing of transmitting a PUSCH.
  • HARQ hybrid automatic repeat request
  • the terminal device 110 may further receive, from the network device 120, an indication of a retransmission of the PDSCH.
  • the terminal device 110 may ignore the retransmission of the PDSCH based on successful processing of an initial transmission of the PDSCH, and then determine the HARQ feedback based on a result of the processing of the initial transmission.
  • the terminal device 110 may further perform HARQ combining of the initial transmission and the retransmission of the PDSCH based on unsuccessful processing of the initial transmission of the PDSCH, and then determine the HARQ feedback based on a result of the HARQ combining.
  • the terminal device 110 may further postpone the uplink transmission to a next available transmission resource.
  • the processing time may be used during a random access procedure for the terminal device 110 or in the event that the terminal device 110 is in a radio resource control, RRC, inactive mode or an RRC idle mode.
  • RRC radio resource control
  • FIG. 9 illustrates a flowchart 900 of a method implemented at a network device according to some embodiments of the present disclosure.
  • the method 900 will be described from the perspective of the network device 120 with reference to FIG. 1A.
  • the network device 120 determines, based on communicating with a terminal device 110, that a first processing time is insufficient for the terminal device 110 to prepare an uplink transmission to the network device 120.
  • the network device 120 receives, from the terminal device 110, the uplink transmission based on a second processing time sufficient for the terminal device 110 to prepare the uplink transmission.
  • the network device 120 may receive, from the terminal device 110, an indication that the first processing time is insufficient.
  • the uplink transmission may comprise a transmission of HARQ feedback for a physical downlink shared channel (PDSCH) .
  • the indication may be received on a physical uplink control channel (PUCCH) on which the HARQ feedback is scheduled or configured, a semi-persistently configured PUCCH for the terminal device 110 to transmit the indication, or any combination of the above-listed items.
  • PUCCH physical uplink control channel
  • the uplink transmission may comprise a transmission of a physical uplink shared channel (PUSCH) .
  • the indication may be received in a media access control (MAC) message mapped to the PUSCH, a PUCCH in an existing format with a configuration defined for the indication using a transmission resource on which the PUSCH is scheduled or configured, a PUCCH in a new format defined for the indication using a transmission resource on which the PUSCH is scheduled or configured, or any combination of the above-listed items.
  • MAC media access control
  • the network device 120 may determine that the first processing time is insufficient based on not receiving the uplink transmission on a transmission resource on which the uplink transmission is scheduled or configured.
  • the network device 120 may, subsequent to determining that the first processing time is insufficient, determine a second transmission resource based on the second processing time, and then receive, from the terminal device 110, the uplink transmission on the second transmission resource.
  • the second transmission resource may be pre-reserved or pre-configured for the uplink transmission.
  • the network device 120 may further transmit, to the terminal device 110, a parameter for transmitting the uplink transmission based on the second processing time, prior to receiving the uplink transmission from the terminal device 110.
  • the parameter may comprise a first parameter for determining a transmission timing of hybrid automatic repeat request, HARQ, feedback for a physical downlink shared channel (PDSCH) , or a second parameter for determining a transmission timing of transmitting a physical uplink shared channel (PUSCH) .
  • the network device 120 may transmit the parameter to the terminal device 110 based on determining that the first processing time is insufficient. In the example embodiments where the parameter comprises the first parameter, the network device 120 may further transmit, to the terminal device 110, an indication of a retransmission of the PDSCH, and then retransmit the PDSCH to the terminal device 110.
  • the network device 120 may receive the uplink transmission on a next available transmission resource.
  • the first processing time may be used during a random access procedure for the terminal device 110 or in the event that the terminal device 110 is in a radio resource control (RRC) inactive mode or an RRC idle mode.
  • RRC radio resource control
  • an apparatus capable of performing the method 800 may comprise means for performing the respective steps of the method 800.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for determining that a processing time is insufficient to prepare an uplink transmission to a network device; and means for informing the network device that the processing time is insufficient.
  • the means for informing the network device comprises: means for transmitting, to the network device, an indication that the processing time is insufficient.
  • the uplink transmission comprises a transmission of HARQ feedback for a physical downlink shared channel, PDSCH.
  • the indication is transmitted on at least one of: a physical uplink control channel, PUCCH, on which the HARQ feedback is scheduled or configured, or a semi-persistently configured PUCCH for the terminal device to transmit the indication.
  • the uplink transmission comprises a transmission of a physical uplink shared channel, PUSCH.
  • the indication is transmitted in at least one of: a media access control, MAC, message mapped to the PUSCH, a PUCCH in an existing format with a configuration defined for the indication using a transmission resource on which the PUSCH is scheduled or configured, or a PUCCH in a new format defined for the indication using a transmission resource on which the PUSCH is scheduled or configured.
  • the means for informing the network device comprises: means for omitting to transmit the uplink transmission on a transmission resource on which the uplink transmission is scheduled or configured.
  • the uplink transmission is scheduled or configured on a first transmission resource
  • the apparatus further comprises: means for, subsequent to determining that the processing time is insufficient, determining a second transmission resource available for the uplink transmission; and means for transmitting, to the network device, the uplink transmission on the second transmission resource.
  • the second transmission resource is pre-reserved or pre-configured for the uplink transmission.
  • the processing time is a first processing time and the apparatus further comprises: means for receiving, from the network device, a parameter for transmitting the uplink transmission based on a second processing time sufficient to prepare the uplink transmission; and means for determining the second transmission resource based on the parameter.
  • the parameter comprises one of: a first parameter for determining a transmission timing of hybrid automatic repeat request, HARQ, feedback for a PDSCH; or a second parameter for determining a transmission timing of transmitting a PUSCH.
  • the parameter comprises the first parameter
  • apparatus further comprises: means for receiving, from the network device, an indication of a retransmission of the PDSCH; means for, based on successful processing of an initial transmission of the PDSCH, ignoring the retransmission of the PDSCH; and means for determining the HARQ feedback based on a result of the processing of the initial transmission.
  • the apparatus further comprises: means for, based on unsuccessful processing of the initial transmission of the PDSCH, performing HARQ combining of the initial transmission and the retransmission of the PDSCH; and means for determining the HARQ feedback based on a result of the HARQ combining.
  • the apparatus further comprises: means for postponing the uplink transmission to a next available transmission resource.
  • the processing time is used during a random access procedure for the terminal device or in the event that the terminal device is in a radio resource control, RRC, inactive mode or an RRC idle mode.
  • the apparatus further comprises means for performing other steps in some embodiments of the method 800.
  • the means comprises at least one processor and at least one memory including computer program code. The at least one memory and computer program code are configured to, with the at least one processor, cause the performance of the apparatus.
  • an apparatus capable of performing the method 900 may comprise means for performing the respective steps of the method 900.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the apparatus comprises means for determining, based on communicating with a terminal device, that a first processing time is insufficient for the terminal device to prepare an uplink transmission to the network device; and means for receiving, from the terminal device, the uplink transmission based on a second processing time sufficient for the terminal device to prepare the uplink transmission.
  • the means for determining that the first processing time is insufficient comprises: means for receiving, from the terminal device, an indication that the first processing time is insufficient.
  • the uplink transmission comprises a transmission of HARQ feedback for a physical downlink shared channel, PDSCH.
  • the indication is received on at least one of: a physical uplink control channel, PUCCH, on which the HARQ feedback is scheduled or configured, or a semi-persistently configured PUCCH for the terminal device to transmit the indication.
  • the uplink transmission comprises a transmission of a physical uplink shared channel, PUSCH.
  • the indication is received in at least one of: a media access control, MAC, message mapped to the PUSCH, a PUCCH in an existing format with a configuration defined for the indication using a transmission resource on which the PUSCH is scheduled or configured, or a PUCCH in a new format defined for the indication using a transmission resource on which the PUSCH is scheduled or configured.
  • the means for determining that the first processing time is insufficient comprises: means for, based on not receiving the uplink transmission on a transmission resource on which the uplink transmission is scheduled or configured, determining that the first processing time is insufficient.
  • the uplink transmission is scheduled or configured on a first transmission resource
  • the means for receiving the uplink transmission comprises: mean for, subsequent to determining that the first processing time is insufficient, determining a second transmission resource based on the second processing time; and means for receiving, from the terminal device, the uplink transmission on the second transmission resource.
  • the second transmission resource is pre-reserved or pre-configured for the uplink transmission.
  • the apparatus further comprises: means for, prior to receiving the uplink transmission from the terminal device, transmitting, to the terminal device, a parameter for transmitting the uplink transmission based on the second processing time.
  • the parameter comprises one of: a first parameter for determining a transmission timing of hybrid automatic repeat request, HARQ, feedback for a physical downlink shared channel, PDSCH; or a second parameter for determining a transmission timing of transmitting a physical uplink shared channel, PUSCH.
  • the means for transmitting the parameter comprises: means for, based on determining that the first processing time is insufficient, transmitting the parameter to the terminal device.
  • the parameter comprises the first parameter
  • the apparatus further comprises: means for transmitting, to the terminal device, an indication of a retransmission of the PDSCH; and means for retransmitting the PDSCH to the terminal device.
  • the means for receiving the uplink transmission comprises: means for receiving the uplink transmission on a next available transmission resource.
  • the first processing time is used during a random access procedure for the terminal device or in the event that the terminal device is in a radio resource control, RRC, inactive mode or an RRC idle mode.
  • the apparatus further comprises means for performing other steps in some embodiments of the method 900.
  • the means comprises at least one processor and at least one memory including computer program code. The at least one memory and computer program code are configured to, with the at least one processor, cause the performance of the apparatus.
  • FIG. 10 illustrates a simplified block diagram of a device 1000 that is suitable for implementing some example embodiments of the present disclosure.
  • the device 1000 may be provided to implement the communication device, for example, the terminal device 110, or the network device 120 as shown in FIG. 1A.
  • the device 1000 includes one or more processors 1010, one or more memories 1020 coupled to the processor 1010, and one or more communication modules 1040 coupled to the processor 1010.
  • the communication module 1040 is for bidirectional communications.
  • the communication module 1040 has at least one antenna to facilitate communication.
  • the communication interface may represent any interface that is necessary for communication with other network elements.
  • the processor 1010 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 1000 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.
  • the memory 1020 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1024, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage.
  • ROM Read Only Memory
  • EPROM electrically programmable read only memory
  • flash memory a hard disk
  • CD compact disc
  • DVD digital video disk
  • RAM random access memory
  • a computer program 1030 includes computer executable instructions that are executed by the associated processor 1010.
  • the program 1030 may be stored in the ROM 1024.
  • the processor 1010 may perform any suitable actions and processing by loading the program 1030 into the RAM 1022.
  • the embodiments of the present disclosure may be implemented by means of the program 1030 so that the device 1000 may perform any process of the disclosure as discussed with reference to FIGS. 2 to 7.
  • the embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the program 1030 may be tangibly contained in a computer readable medium which may be included in the device 1000 (such as in the memory 1020) or other storage devices that are accessible by the device 1000.
  • the device 1000 may load the program 1030 from the computer readable medium to the RAM 1022 for execution.
  • the computer readable medium may include any types of tangible non-volatile storage, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • FIG. 11 illustrates a block diagram of an example of a computer readable medium 1100 in accordance with some example embodiments of the present disclosure.
  • the computer readable medium 1100 has the program 1030 stored thereon. It is noted that although the computer readable medium 1100 is depicted in form of CD or DVD in FIG. 11, the computer readable medium 1100 may be in any other form suitable for carry or hold the program 1030.
  • 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 representations, it is to be understood that the block, apparatus, system, technique or method 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 method as described above with reference to any of FIGS. 8-9.
  • 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 computer program codes or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable medium, and the like.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer 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. More specific examples of the computer 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.
  • non-transitory is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .

Landscapes

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

Abstract

Des modes de réalisation de la présente invention concernent la relaxation du temps de traitement. Un dispositif terminal détermine qu'un temps de traitement est insuffisant pour préparer une transmission de liaison montante à un dispositif de réseau. Ensuite, le dispositif terminal informe le dispositif de réseau que le temps de traitement est insuffisant. Par conséquent, il est possible d'éviter un surdébit de système, de permettre des économies de coût supplémentaires, et d'améliorer l'efficacité de transmission.
PCT/CN2023/073997 2023-01-31 2023-01-31 Relaxation de temps de traitement Ceased WO2024159403A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202380092788.0A CN120604480A (zh) 2023-01-31 2023-01-31 处理时间放松
PCT/CN2023/073997 WO2024159403A1 (fr) 2023-01-31 2023-01-31 Relaxation de temps de traitement

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/073997 WO2024159403A1 (fr) 2023-01-31 2023-01-31 Relaxation de temps de traitement

Publications (1)

Publication Number Publication Date
WO2024159403A1 true WO2024159403A1 (fr) 2024-08-08

Family

ID=92145747

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/073997 Ceased WO2024159403A1 (fr) 2023-01-31 2023-01-31 Relaxation de temps de traitement

Country Status (2)

Country Link
CN (1) CN120604480A (fr)
WO (1) WO2024159403A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108282286A (zh) * 2017-01-05 2018-07-13 华为技术有限公司 请求资源的方法和装置
US20210351876A1 (en) * 2020-05-08 2021-11-11 Qualcomm Incorporated Selective bundling techniques for harq-ack feedback
WO2021230701A1 (fr) * 2020-05-14 2021-11-18 엘지전자 주식회사 Procédé pour la transmission ou la réception d'un signal pour une communication sans fil, et dispositif associé
CN114641077A (zh) * 2022-05-05 2022-06-17 深圳传音控股股份有限公司 数据传输方法、通信设备及存储介质
WO2022154577A1 (fr) * 2021-01-18 2022-07-21 엘지전자 주식회사 Procédé de transmission/réception de pucch dans un système de communication sans fil et dispositif associé
CN114793365A (zh) * 2021-01-25 2022-07-26 北京紫光展锐通信技术有限公司 随机接入方法、装置、用户设备、网络设备及介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108282286A (zh) * 2017-01-05 2018-07-13 华为技术有限公司 请求资源的方法和装置
US20210351876A1 (en) * 2020-05-08 2021-11-11 Qualcomm Incorporated Selective bundling techniques for harq-ack feedback
WO2021230701A1 (fr) * 2020-05-14 2021-11-18 엘지전자 주식회사 Procédé pour la transmission ou la réception d'un signal pour une communication sans fil, et dispositif associé
WO2022154577A1 (fr) * 2021-01-18 2022-07-21 엘지전자 주식회사 Procédé de transmission/réception de pucch dans un système de communication sans fil et dispositif associé
CN114793365A (zh) * 2021-01-25 2022-07-26 北京紫光展锐通信技术有限公司 随机接入方法、装置、用户设备、网络设备及介质
CN114641077A (zh) * 2022-05-05 2022-06-17 深圳传音控股股份有限公司 数据传输方法、通信设备及存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ASUSTEK, ERICSSON, SAMSUNG, NOKIA: "Correction on DRX with bundle transmission of configured uplink grant", 3GPP TSG-RAN2 #112E, R2-2011045, 16 November 2020 (2020-11-16), XP052255616 *
ERICSSON: "Potential UE complexity reduction features for Redcap", 3GPP TSG-RAN WG1 MEETING #101-E, R1-2003289, 16 May 2020 (2020-05-16), XP051885083 *

Also Published As

Publication number Publication date
CN120604480A (zh) 2025-09-05

Similar Documents

Publication Publication Date Title
AU2023274127B2 (en) Sharing HARQ processes by multiple configured grants resources
US11051328B2 (en) Method and device for cross-numerology scheduling
EP2979385A1 (fr) Méthode et appareil de détermination de temporisation de harq dans des systèmes de communication
US9706532B2 (en) TDD and FDD joint carrier aggregation enhancements in LTE-advanced
WO2020191625A9 (fr) Mécanisme d'activation de harq basé sur un service
WO2020097775A1 (fr) Communications avec des ressources de liaison montante préconfigurées
CN117957894A (zh) 用于通信的方法、设备和计算机可读介质
WO2024159403A1 (fr) Relaxation de temps de traitement
WO2024159405A1 (fr) Relâchement de temps de traitement
WO2024178651A1 (fr) Appareils, procédés et support de communication à double connectivité
WO2024216521A1 (fr) Transfert de saut de pdcch après une transmission de nack
WO2024239335A1 (fr) Indication de mode harq rapide pour sps et autorisation configurée
WO2025050402A1 (fr) Gestion de ressources
WO2025030528A1 (fr) Indication associée à la surveillance de pdcch
WO2024229783A1 (fr) Format de préambule prach dans sbfd
WO2025065393A1 (fr) Rapport de retard pour activation de cellule
WO2025171609A1 (fr) Activation de cellule
WO2024168930A1 (fr) Évitement d'interruption de temps d'occupation de canal
WO2025160922A1 (fr) Configuration de modes de fonctionnement pour duplex intégral sans chevauchement de sous-bande
WO2024168620A1 (fr) Configuration de ressource dynamique pour rétroaction de liaison latérale
WO2024031482A1 (fr) Amélioration de transmission de rétroaction de liaison latérale
CN112868261A (zh) 服务小区的l1信令
KR20250170128A (ko) Nack 송신 후 pdcch 스킵 핸들링
CN121219989A (zh) 针对sps和配置授权的快速harq模式指示

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202547070132

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 202380092788.0

Country of ref document: CN

WWP Wipo information: published in national office

Ref document number: 202547070132

Country of ref document: IN

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 202380092788.0

Country of ref document: CN