WO2025020196A1

WO2025020196A1 - Devices and methods for communication

Info

Publication number: WO2025020196A1
Application number: PCT/CN2023/109666
Authority: WO
Inventors: Lin Liang; Gang Wang
Original assignee: NEC Corp
Current assignee: NEC Corp
Priority date: 2023-07-27
Filing date: 2023-07-27
Publication date: 2025-01-30
Anticipated expiration: 2026-01-27

Abstract

Embodiments of the present disclosure provide a solution for uplink transmission repetition configuration. In a solution, a terminal device receives, from a network device, a configuration of uplink transmission repetition scheduled by downlink control information (DCI), wherein the DCI is scrambled with a radio network temporary identity (RNTI) selected from C-RNTI or CS-RNTI. In accordance with a determination that the uplink transmission repetition is allowed, the terminal device transmits, to the network device, at least one repetition of an uplink transmission based on the configuration.

Description

DEVICES AND METHODS FOR COMMUNICATION

FIELDS

Example embodiments of the present disclosure generally relate to the field of communication techniques and in particular, to devices and methods for uplink (UL) transmission repetition configuration.

BACKGROUND

During the initial access procedure, UL repetition transmissions are used for some messages, such as, physical random access channel (PRACH) repetition, Msg3 repetition, Msg4 Hybrid Automatic Repeat Request (HARQ) feedback, to guarantee communication reliability.

Upon access to the network, UE may also need to transmit repetitions for some UL messages. Thus, UL transmission repetition configuration needs further improvement.

SUMMARY

In general, embodiments of the present disclosure provide a solution for UL transmission repetition configuration.

In a first aspect, there is provided a terminal device comprising: a processor configured to cause the terminal device to: receive, from a network device, a configuration of uplink transmission repetition scheduled by downlink control information (DCI) , wherein the DCI is scrambled with a radio network temporary identity (RNTI) selected from cell radio network temporary identity (C-RNTI) or configured scheduling radio network temporary identity (CS-RNTI) ; and in accordance with a determination that the uplink transmission repetition is allowed, transmit, to the network device, at least one repetition of an uplink transmission based on the configuration and the DCI.

In a second aspect, there is provided a network device comprising: a processor configured to cause the terminal device to: transmit, to a terminal device, a configuration of uplink transmission repetition scheduled by downlink control information (DCI) , wherein the DCI is scrambled with a radio network temporary identity (RNTI) selected from C-RNTI or CS-RNTI; and upon transmission of the DCI, receive, from the network device, an uplink transmission with at least one repetition based on the configuration.

In a third aspect, there is provided a communication method performed by a terminal device. The method comprises: receiving, from a network device, a configuration of uplink transmission repetition scheduled by downlink control information (DCI) , wherein the DCI is scrambled with a radio network temporary identity (RNTI) selected from C-RNTI or CS-RNTI; and in accordance with a determination that the uplink transmission repetition is allowed, transmitting, to the network device, at least one repetition of an uplink transmission based on the configuration and the DCI.

In a fourth aspect, there is provided a communication method performed by a network device. The method comprises: transmitting, to a terminal device, a configuration of uplink transmission repetition scheduled by downlink control information (DCI) , wherein the DCI is scrambled with a radio network temporary identity (RNTI) selected from C-RNTI or CS-RNTI; and upon transmission of the DCI, receiving, from the network device, an uplink transmission with at least one repetition based on the configuration.

In a fifth aspect, there is provided a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to carry out the method according to the third, or fourth aspect.

Other features of the present disclosure will become easily comprehensible through the following description.

BRIEF DESCRIPTION OF THE DRAWINGS

Through the more detailed description of some example embodiments of the present disclosure in the accompanying drawings, the above and other objects, features and advantages of the present disclosure will become more apparent, wherein:

FIG. 1 illustrates a schematic diagram of an example random access procedure;

FIG. 2 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;

FIG. 3 illustrates a signaling flow of UL transmission repetition configuration in accordance with some embodiments of the present disclosure;

FIG. 4 illustrates a schematic diagram of an example medium access control (MAC) control element (CE) according to some example embodiments of the present disclosure;

FIG. 5 illustrates a schematic diagram of an example MAC CE according to some example embodiments of the present disclosure;

FIG. 6 illustrates a schematic diagram of an example MAC CE according to some example embodiments of the present disclosure;

FIG. 7 illustrates a flowchart of a method implemented at a terminal device according to some example embodiments of the present disclosure;

FIG. 8 illustrates a flowchart of a method implemented at a network device according to some example embodiments of the present disclosure; and

FIG. 9 illustrates a simplified block diagram of an apparatus that is suitable for implementing example embodiments of the present disclosure.

Throughout the drawings, the same or similar reference numerals represent the same or similar element.

DETAILED DESCRIPTION

Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.

In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

As used herein, the term ‘terminal device’ refers to any device having wireless or wired communication capabilities. Examples of the terminal device include, but not limited to, user equipment (UE) , personal computers, desktops, mobile phones, cellular phones, smart phones, personal digital assistants (PDAs) , portable computers, tablets, wearable devices, internet of things (IoT) devices, Ultra-reliable and Low Latency Communications (URLLC) devices, Internet of Everything (IoE) devices, machine type communication (MTC) devices, devices on vehicle for V2X communication where X means pedestrian, vehicle, or infrastructure/network, devices for Integrated Access and Backhaul (IAB) , Space borne vehicles or Air borne vehicles in Non-terrestrial networks (NTN) including Satellites and High Altitude Platforms (HAPs) encompassing Unmanned Aircraft Systems (UAS) , eXtended Reality (XR) devices including different types of realities such as Augmented Reality (AR) , Mixed Reality (MR) and Virtual Reality (VR) , the unmanned aerial vehicle (UAV) commonly known as a drone which is an aircraft without any human pilot, devices on high speed train (HST) , or image capture devices such as digital cameras, sensors, gaming devices, music storage and playback appliances, or Internet appliances enabling wireless or wired Internet access and browsing and the like. The ‘terminal device’ can further has ‘multicast/broadcast’ feature, to support public safety and mission critical, V2X applications, transparent IPv4/IPv6 multicast delivery, IPTV, smart TV, radio services, software delivery over wireless, group communications and IoT applications. It may also incorporate one or multiple Subscriber Identity Module (SIM) as known as Multi-SIM. The term “terminal device” can be used interchangeably with a UE, a mobile station, a subscriber station, a mobile terminal, a user terminal or a wireless device.

The term “network device” refers to a device which is capable of providing or hosting a cell or coverage where terminal devices can communicate. Examples of a network device include, but not limited to, a Node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a next generation NodeB (gNB) , a transmission reception point (TRP) , a remote radio unit (RRU) , a radio head (RH) , a remote radio head (RRH) , an IAB node, a low power node such as a femto node, a pico node, a reconfigurable intelligent surface (RIS) , and the like.

The terminal device or the network device may have Artificial intelligence (AI) or Machine learning capability. It generally includes a model which has been trained from numerous collected data for a specific function, and can be used to predict some information.

The terminal or the network device may work on several frequency ranges, e.g., FR1 (e.g., 450 MHz to 6000 MHz) , FR2 (e.g., 24.25GHz to 71GHz) , frequency band larger than 100 GHz as well as Tera Hertz (THz) . It can further work on licensed/unlicensed/shared spectrum. The terminal device may have more than one connection with the network devices under Multi-Radio Dual Connectivity (MR-DC) application scenario. The terminal device or the network device can work on full duplex, flexible duplex and cross division duplex modes.

The embodiments of the present disclosure may be performed in test equipment, e.g., signal generator, signal analyzer, spectrum analyzer, network analyzer, test terminal device, test network device, channel emulator. In some embodiments, the terminal device may be connected with a first network device and a second network device. One of the first network device and the second network device may be a master node and the other one may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs) . In some embodiments, the first network device may be a first RAT device and the second network device may be a second RAT device. In some embodiments, the first RAT device is eNB and the second RAT device is gNB. Information related with different RATs may be transmitted to the terminal device from at least one of the first network device or the second network device. In some embodiments, first information may be transmitted to the terminal device from the first network device and second information may be transmitted to the terminal device from the second network device directly or via the first network device. In some embodiments, information related with configuration for the terminal device configured by the second network device may be transmitted from the second network device via the first network device. Information related with reconfiguration for the terminal device configured by the second network device may be transmitted to the terminal device from the second network device directly or via the first network device.

As used herein, the singular forms ‘a’ , ‘an’ and ‘the’ are intended to include the plural forms as well, unless the context clearly indicates otherwise. The term ‘includes’ and its variants are to be read as open terms that mean ‘includes, but is not limited to. ’ The term ‘based on’ is to be read as ‘at least in part based on. ’ The term ‘one embodiment’ and ‘an embodiment’ are to be read as ‘at least one embodiment. ’ The term ‘another embodiment’ is to be read as ‘at least one other embodiment. ’ The terms ‘first, ’ ‘second, ’ and the like may refer to different or same objects. Other definitions, explicit and implicit, may be included below.

In some examples, values, procedures, or apparatus are referred to as ‘best, ’ ‘lowest, ’ ‘highest, ’ ‘minimum, ’ ‘maximum, ’ or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.

As used herein, the term “resource, ” “transmission resource, ” “uplink resource, ” or “downlink resource” may refer to any resource for performing a communication, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.

As used herein, the term “Msg3” and “HARQ-ACK for Msg4” may refer to UL transmission in PRACH, for example, RRCSetupRequest, HARQ-ACK for RRCSetup message. The term “Msg5” may refer to a RRCSetupcomplete message.

As used herein, the term “UL transmission repetitions” may refer to Physical Uplink Shared Channel (PUSCH) repetitions. PUSCH transmission may be scheduled by UL grant, or downlink control information (DCI) . For the latter case, the UE determines time-frequency resources for PUSCH, modulation and coding scheme (MCS) , redundancy version (RV) from the DCI. There are mainly two PUSCH repetition types, i.e., repetition type A and repetition B.

The definitions of PUSCH repetition type A in TS 38.214 is shown as below:

FIG. 1 illustrates a schematic diagram of an example random access procedure 100. As shown in FIG. 1, UE 102 in RRC_idle mode may access the network of gNB 104 through the initial access procedure. As previously mentioned, some UL message may use PUSCH repetitions, as those indicated by solid lines. Msg3 repetitions may be scheduled by UL grant or DCI. The RACH resources for Msg3 repetition may be indicated by FeatureCombination-r17 as below:

The configuration of Msg3 repetitions and the determination of MCS are specified in TS 38.321, TS 38.213 and TS 38.214 as blow:

Table 1 shows a configuration of a number of Msg3 repetition K as indicated in MCS information field.

Table 1. Number of repetition K as a function of 2 MSBs of MCS information field

Table 2 shows a configuration of Msg3 repetition in RAR UL grant.

Table 2. MCS index I_MCS as a function of 2 LSBs of MCS information field in RAR UL grant

Table 3 shows a configuration of Msg3 repetition in DCI format 0_0 with CRC scrambled by Temporary Cell Radio Network Temporary Identity (TC-RNTI) .

Table 3. MCS index I_MCS as a function of 3 LSBs of MCS information field in DCI format 0_0 with CRC scrambled by TC-RNTI.

After accessing the network, UE 102 in RRC_CONNECTED mode may transmit a RRCSetupComplete message on PUSCH, which is also called Msg5. Msg 5 may be scheduled by DCI format 0_0 with CRC scrambled by C-RNTI. Currently, DCI format 0_0 with CRC scrambled by C-RNTI or CS-RNTI does not support UL repetition yet. In addition to Msg 5, UL repetitions of UE capability information are also not supported, as indicated by dotted line in FIG. 1.

As more UEs may access the network by performing repetitions of PRACH, Msg3, HARQ-ACK for Msg4, the network may be congested during Msg5 PUSCH transmission, which would jeopardize the commercialization of existing CE features in both Terrestrial Network (TN) and Non-Terrestrial Network (NTN) scenarios.

However, retransmission is not a typical way at least for NTN scenario due to larger delay and significant performance gap (e.g., at least 10 dB) comparing with Msg3 repetition. Thus, there is a need for improving repetition configuration for PUSCH transmissions. Considering some of the PUSCH transmissions may need more network resources (e.g., Msg5 transmission that needs hundreds of bits) , a request mechanism for repetition transmission may be desirable.

Principles and implementations of the present disclosure will be described in detail below with reference to the figures.

FIG. 2 illustrates a schematic diagram of an example communication environment 100 in which example embodiments of the present disclosure can be implemented. In the communication environment 200, a plurality of communication devices, including a terminal device 210 and a network device 220, can communicate with each other.

In the example of FIG. 2, the terminal device 210 may be a UE and the network device 220 may be a base station serving the UE. The serving area of the network device 120 may be called a cell 202.

It is to be understood that the number of devices and their connections shown in FIG. 2 are only for the purpose of illustration without suggesting any limitation. The communication environment 200 may include any suitable number of devices configured to implementing example embodiments of the present disclosure. Although not shown, it would be appreciated that one or more additional devices may be located in the cell 202, and one or more additional cells may be deployed in the communication environment 200. It is noted that although illustrated as a network device, the network device 220 may be another device than a network device. Although illustrated as a terminal device, the terminal device 210 may be other device than a terminal device.

In the following, for the purpose of illustration, some example embodiments are described with the terminal device 210 operating as a UE and the network device 220 operating as a base station. However, in some example embodiments, operations described in connection with a terminal device may be implemented at a network device or other device, and operations described in connection with a network device may be implemented at a terminal device or other device.

In some example embodiments, if the terminal device 210 is a terminal device and the network device 220 is a network device, a link from the network device 220 to the terminal device 210 is referred to as a downlink (DL) , while a link from the terminal device 210 to the network device 220 is referred to as an uplink (UL) . In DL, the network device 220 is a transmitting (TX) device (or a transmitter) and the terminal device 210 is a receiving (RX) device (or a receiver) . In UL, the terminal device 210 is a TX device (or a transmitter) and the network device 220 is a RX device (or a receiver) .

The communications in the communication environment 200 may conform to any suitable standards including, but not limited to, Global System for Mobile Communications (GSM) , Long Term Evolution (LTE) , LTE-Evolution, LTE-Advanced (LTE-A) , New Radio (NR) , Wideband Code Division Multiple Access (WCDMA) , Code Division Multiple Access (CDMA) , GSM EDGE Radio Access Network (GERAN) , Machine Type Communication (MTC) and the like. The embodiments of the present disclosure may be performed according to any generation communication protocols either currently known or to be developed in the future. Examples of the communication protocols include, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) communication protocols, 5.5G, 5G-Advanced networks, or the sixth generation (6G) networks.

Reference is made to FIG. 3, which illustrates a signaling flow 300 of UL transmission repetition configuration in accordance with some embodiments of the present disclosure. For the purposes of discussion, the signaling flow 300 will be discussed with reference to FIG. 2, for example, by using the terminal device 210 and the network device 220.

It should be understood that in the following descriptions, Msg 5 scheduled by DCI format 0_0 with CRC scrambled by C-RNTI may be given as an example of UL transmission. However, the solution provided in the present disclosure is also applicable to other DCI formats or other UL transmissions during an initial access procedure, a reestablishment procedure, or a resume procedure. Thus, the present disclosure is not limited in this regard.

In the process 300, the terminal device 210 receives (305) , from the network device 220, a configuration of UL transmission repetition scheduled by DCI. The DCI is scrambled with RNTI selected from C-RNTI or CS-RNTI.

The network device 220 may then transmit DCI for scheduling UL transmission. The terminal device 210 determines (310) whether the UL transmission repetition is allowed.

If the UL transmission repetition is allowed, the terminal device 210 transmits (315) , to the network device 220, at least one repetition of an UL transmission based on the configuration.

It should be noted that, the determination of whether UL transmission repetition is allowed may not necessarily occur after the receipt of DCI. In some example embodiments, the determination may occur before or concurrently with the receipt of DCI. Thus, the present disclosure is not limited in this regard.

In some example embodiments, the terminal device 210 may request for UL transmission repetition. In these embodiments, the terminal device 210 may transmit, to the network device 220, a request for UL transmission repetition. The request may be associated with the initial access procedure, the reestablishment procedure, or the resume procedure.

In some example embodiments, the request for UL transmission repetition may be transmitted on random access resource, e.g., PRACH resource. To this end, an indication may be added in the feature combination as below. For example, the indication may use a spare bit in the feature combination.

The feature combination field description in the above example is shown as below:

In some example embodiments, the request for UL transmission repetition may be identified by a logical channel identity (LCID) . In particular, the reserved bits in LCID values may be used for this purpose. Accordingly, the network device 220 may determine whether UL repetition is available for this terminal device 210 via the LCID. Table 4 shows an example definition of LCID, where indexes 39 and 40 is used for indicating the Msg5 repetition.

Table 4. An example definition of LCID

In some example embodiments, a new MAC CE may be introduced to indicate that UL repetition is needed. In this case, the request for UL transmission repetition may be transmitted via a MAC CE. The MAC CE is identified by a MAC subheader with a LCID/eLCID indication of the request for the UL transmission repetition. The reserved bits in LCID values may be used for this purpose.

Table 5 shows an example definition of LCID, where index 47 of LCID value may be set to “Msg5 Repetition Request” .

Table 5. An example definition of LCID

An example definition of MAC CE for Msg5 repetition request is given as blow, which may apply to relevant standards.

Additionally, in the above embodiments, as new MAC CE is introduced, the priority order of various MAC CEs needs to be defined. For example, in order to transmit the request for UL transmission repetition as much as possible, a higher priority shall be considered. In this case, the priority of the MAC CE for requesting the UL repetition may not be higher than a priority of a MAC CE or data with C-RNTI from UL-CCCH, and not be lower than a priority of buffer status reporting (BSR) .

An example priority order for various MAC CEs is given as below:

In some example embodiments, the request for UL transmission repetition may be transmitted via a MAC CE for power headroom report (PHR) . The PHR may be triggered at least for initial access procedure, reestablishment procedure, or resume procedure. In this case, if there is UL resource available for accommodating PHR MAC CE as well as the MAC CE header in an UL transmission preceding the one requesting UL repetitions (e.g., Msg 3 is preceding Msg 5) , the request for UL transmission repetition may be placed in the PHR MAC CE header. For example, a new LCID for PHR MAC CE may be defined for this purpose. The reserved bits in LCID values may be used for this purpose.

Table 6 shows an example definition of LCID, where index 47 of LCID value may be set to “Single Entry PHR for Msg5 Repetition Request” .

Table 6. An example definition of LCID

In case of requesting UL repetition for Msg5, considering UL grant for Msg3 is limited, a truncated MAC CE for PHR may be used. In some other cases, a normal MAC CE for PHR may be used.

In some example embodiments, the request for UL transmission repetition may be transmitted via a common control channel (CCCH) message in a random access procedure, such as, RRCSetupRequest, RRCResumeRequest, RRCResumeRequest1, RRCReestablishmentRequest, and the like. In particular, the request may be indicated by an indication of whether UL transmission repetitions are needed, a first value of the indication may indicate requesting the UL transmission repetition, and a second value of the indication may indicate not requesting the UL transmission repetition.

For example, the indication may use a spare bit in the CCCH message. Taking RRCSetupRequest as an example, the request may be defined as below.

In the above example, the RRCSetupRequest-IE field description is shown as below:

In some example embodiments, the request for UL transmission repetition may be transmitted via MAC CE. FIG. 4 illustrates a schematic diagram of an example MAC CE 400 according to some example embodiments of the present disclosure. As shown in FIG. 4, a MAC subheader 400 except for fixed sized MAC CE, padding and a MAC SDU containing UL CCCH may consist of header fields, i.e., RI field 410, R field 420 and (e) LCID field 430, which means that there are two reserved bits in the MAC CE header. In this case, a repetition indication of UL transmission may use one or both of the reserved bits.

As shown in FIG. 4, RI 410 represents a format field indicating a size of the request for UL transmission repetition (e.g., Msg5 repetition request) . For example, a first value (e.g., the value 1) of the repetition indication may indicate requesting the UL transmission repetition. In this case, the terminal device 210 requests the DCI format 0_0 for scheduling UL transmission repetitions. A second value (e.g., the value 0) indicates not requesting the UL transmission repetition.

In some example embodiments, no request for UL transmission repetition is signaled. In this case, a new time domain resource allocation (TDRA) list may be configured by the network device 220 via a system information block (e.g., SIB1) and/or a RRC message (e.g., RRCSetup message, RRCResume message, and so on) . For example, the configuration of the UL transmission repetition from the network device 220 may comprise the TDRA list.

In the above example embodiments, the terminal device 210 may determine to use which TDRA list based on UE capability and a condition for transmitting the UL transmission repetition. The condition for transmitting the UL transmission repetition may be associated with a predetermined threshold.

In particular, if the terminal device 210 supports UL transmission repetition, and the condition for transmitting the UL transmission repetition is met, in other words, the UL transmission repetition is allowed, the terminal device 210 may transmit the UL transmission with the at least one repetition. If the terminal device 210 supports UL transmission repetition, while the condition for transmitting the UL transmission repetition is not met, the terminal device 210 may transmit the UL transmission without repetition. Otherwise, if the terminal device 210 does not support UL transmission repetition, in this case, the UL transmission repetition is not allowed, the terminal device 210 may transmit the UL transmission without repetition.

In some example embodiments, the condition for transmitting the UL transmission repetition may configured for a bandwidth part (BWP) associated with the terminal device 210. In this case, the terminal device 210 may determine whether to use the UL transmission repetition based on the configured condition. If the condition for transmitting the UL transmission repetition is met, the terminal device 210 may determine that the UL transmission repetition is allowed, and transmit the UL transmission with the at least one repetition. otherwise, if the condition for transmitting the UL transmission repetition is not met, the terminal device 210 may determine that the UL transmission repetition is not allowed, and transmit the UL transmission without repetition.

By way of example, a reference signal receiving power (RSRP) threshold may be introduced for requesting UL transmission repetition. In this example, if a RSRP of a DL pathloss reference is below the RSRP threshold, the terminal device 210 may determine that the condition for transmitting the UL transmission repetition is met. Otherwise, if the RSRP of the DL pathloss reference is not below the RSRP threshold, the terminal device 210 may determine that the condition for transmitting the UL transmission repetition is not met.

In some example embodiments, a separate RSRP threshold may be configured for requesting Msg5 repetition. A configuration of the threshold for Msg5 repetition may be specified as below, which may apply to TS 38.321:

An example BWP-UplinkCommon field description may be shown as below:

In some example embodiments, a RSRP threshold for Msg3 repetition may be reused for requesting 5 Msg repetition. A configuration of the threshold for Msg3 repetition that is reused for Msg5 repetition may be specified as below, which may apply to TS 38.321:

In some example embodiments, after receiving the request for UL transmission repetition, the network device 220 may not transmit any indication or response to the terminal device 210. In this case, the terminal device 210 determines whether to perform UL transmission repetition based on UE capability and the condition for transmitting the UL transmission repetition.

By way of example, the UL transmission is a transmission of Msg5 and the configuration of UL transmission repetition is a configuration of Msg3 repetition. In this example, if the terminal device 210 supports Msg5 repetition and the condition for Msg5 repetition is met, or alternatively, if the terminal device 210 requests for Msg5 repetition (e.g., via the request for UL transmission repetition) , once the terminal device 210 receives DCI format 0_0, the terminal device 210 may use Msg3 repetition or TDRA list with repetition. If the terminal device 210 supports Msg5 repetition and the condition for Msg5 repetition is not met, the terminal device 210 may not use Msg3 repetition or TDRA list with repetition, and in this case, the terminal device 210 may use a legacy TDRA list. If the terminal device 210 does not support Msg5 repetition, the terminal device 210 may not use Msg3 repetition or TDRA list with repetition, and in this case, the terminal device 210 may use a legacy TDRA list.

Alternatively, in some other embodiments, after receiving the request for UL transmission repetition, the network device 220 may indicate that DCI format 0_0 is to be used for scheduling UL transmission repetition.

In this case, the network device 220 may transmit an activation indication of UL transmission repetition scheduled by the DCI. In this way, the terminal device 210 may be aware that the UL transmission repetition is allowed.

In some example embodiments, the activation indication may be transmitted via a MAC CE. FIG. 5 illustrates a schematic diagram of an example MAC CE 500 according to some example embodiments of the present disclosure. As shown in FIG. 5, a MAC subheader except for fixed sized MAC CE, padding, and a MAC SDU containing UL CCCH may consist of the header fields, i.e., RepInd field 510, F field 520 and (e) LCID field 530. Thus, there is a reserved bit in the MAC CE header, which may be used for the activation indication. For example, for downlink (DL) Physical Downlink Shared Channel (PDSCH) , such as Msg4, the reserved bit in the MAC CE header may be used by the network device 220 to indicate to use PUSCH repetition for DCI format 0_0.

In the example of FIG. 5, RepInd field 510 may indicate that the terminal device 210 shall use UL transmission repetition for DCI format 0_0. For example, a first value (e.g., the value 1) of the activation indication may indicate that DCI is used for scheduling UL transmission repetition, and a second value (e.g., the value 0) of the activation indication may indicate that DCI is not used for scheduling UL transmission repetition.

In some example embodiments, a new MAC CE may be defined for the activation indication of UL transmission repetition scheduled by DCI format 0_0. The new MAC CE may be identified by a MAC CE subheader with a (e) LCID. An example definition of MAC CE for UL repetition activation is given as blow, which may apply to relevant standards. The reserved bits in LCID values may be used for this purpose.

Table 7 shows an example definition of LCID, where index 35 of LCID value may be set to “PUSCH repetition activation for DCI format 0_0” .

Table 7. An example definition of LCID

Additionally, in some embodiments, the network device 220 may also indicate termination of UL repetitions scheduled by DCI format 0_0. For example, once entering RRC_CONNECTED mode, if the terminal device 210 may expect to perform PUSCH repetition transmission, DCI format 0_1 or 0_2 may be used. In this case, UL repetition scheduled by DCI format 0_0 (e.g., Msg5 repetition) may be terminated due to it’s limitation, such as, the repetition number.

In some example embodiments, a new MAC CE may be defined to indicate UL repetition scheduled by DCI format 0_0 is deactivated. Such a MAC CE may be carried in DCI. The MAC CE may be identified by a MAC subheader with (e) LCID. An example definition of MAC CE for UL repetition deactivation is given as blow, which may apply to relevant standards. For example, the reserved bits in LCID values may be used for this purpose. For example, index 35 of LCID value as shown in Table 7 above may be set to “PUSCH repetition deactivation for DCI format 0_0” .

In some example embodiments, the network device 220 may transmit the deactivation indication via a RRC message. Once the deactivation indication is received, the terminal device 210 may terminate the UL repetition.

In some example embodiments, a dedicated TDRA list may be configured via SIB (e.g., SIB1) and/or RRC message. If the dedicated TDRA list is configured, the UL repetition may be considered as terminated.

In some example embodiments, a dedicated TDRA list may be configured for UL repetition scheduled by DCI format 0_0. The configuration of the dedicated TDRA list may be via SIB (e.g., SIB1) and/or a RRC message. The dedicated TDRA list may comprise at least the repetition number which is up to 16 entries.

An example configuration of the dedicated TDRA only for repetition type A used for Msg5 repetition is shown as blow:

An example configuration of the dedicated TDRA for repetition type A and repetition type B used for Msg5 repetition is shown as blow:

In the above embodiments, as the dedicated TDRA list is defined for UL repetition scheduled by DCI format 0_0, it needs to define applying which PUSCH TDRA configuration for DCI format 0_0.

In some example embodiments, a common TDRA list with repetition and a common TDRA list without repetition may be configured for the terminal device 210. For example, a common TDRA list for Msg5 repetition is configured in PUSCH-ConfigCommon, and there will be two common TDRA lists. The network device 220 may indicate which of the two common TDRA lists to be used via an indication which may be carried in a MAC CE. The priority order of these TDRA lists in descending order may be: the dedicated TDRA list, the common TDRA list with repetition, the common TDRA list without repetition which is the legacy TDRA list, and a default TDRA list.

Additionally, or alternatively, in some example embodiments, the dedicated TDRA list with repetition and the dedicated TDRA list without repetition may be configured for the terminal device 210. For example, the dedicated TDRA list for Msg5 repetition is configured in PUSCH-Config. The priority order of these TDRA lists in descending order may be: the dedicated TDRA list with repetition, the dedicated TDRA list without repetition, the common TDRA list, and the default TDRA list.

Table 8 shows example applicable PUSCH TDRA for common search space and DCI format 0_0 in UE specific search space.

Table 8. Applicable PUSCH TDRA for common search space and DCI format 0_0 in UE specific search space

With the activation and deactivation mechanism, the terminal device 210 may be aware of when to use UL transmission repetition via DCI format 0_0 and when not to use.

Instead of reusing the configuration of Msg3 repetition and introducing a new TDRA list, a separate message may be used to indicate the repetition number of UL transmission repetition. This can support more repetition number, and the DCI format 0_0 may keep unchanged.

In some example embodiments, the configuration of UL transmission repetition may comprise the repetition number and an indication indicating whether the UL transmission repetition scheduled by DCI format 0_0 is activated. the configuration of UL transmission repetition may be contained in a first message, including but not limited to, a MAC CE, a RRC message, or a SIB. Furthermore, a repetition number list may be defined in SIB and/or RRC message to support more repetition number.

An example definition of PUSCH repetition for DCI format 0_0 activation/deactivation MAC CE is given as blow, which may apply to relevant standards.

FIG. 6 illustrates a schematic diagram of an example MAC CE 600 according to some example embodiments of the present disclosure. The MAC CE 600 may be used for Msg5 repetition activation/deactivation MAC CE of one octet that is identified by a MAC subheader with LCID. As shown in FIG. 6, the MAC CE 600 may include one AI field 610, three R bits 620 to 640 and one repetition number field 650.

An example definition of Msg5 repetition activation/deactivation MAC CE is given as blow:

In some example embodiments where the UL transmission repetition is Msg 5 repetition, a Msg3 repetition mechanism may be reused for Msg5 repetition. In particular, a repetition factor for Msg5 repetition number is introduced, and in this case, the configuration of UL transmission repetition may be the repetition factor for Msg 5 repetition. The repetition factor may be configured via SIB or a RRC message. The candidate values for the repetition factor may be a positive integer, such as, 1, 2, 3, 4 and so on.

For example, the repetition number for Msg5 may be determined as N_msg5=N_msg3 *M, where N_msg5 denotes the repetition number for Msg5, N_msg3 denotes the repetition number for Msg3, and M denotes the repetition factor.

Additionally, a repetition list {1, 2, 4, 8} may be configured for Msg3 repetition. In this case, the terminal device 210 may determine the repetition number of Msg5 repetition by applying the repetition factor to the repetition list configured for Msg3 repetition.

In some example embodiments, UE capability for UL transmission repetition may be supported. The terminal device 210 may transmit, to the network device 220, a capability indication of the terminal device 210 indicating support of the UL transmission repetition.

An example definition and parameters of UE capability are given as below:

FIG. 7 illustrates a flowchart of a communication method 700 implemented at a terminal device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the terminal device 210 in FIG. 2.

At block 710, the terminal device 210 receives, from a network device, a configuration of UL transmission repetition scheduled by DCI, wherein the DCI is scrambled with a RNTI selected from C-RNTI or CS-RNTI.

At block 720, the terminal device 210 determines if the UL transmission repetition is allowed.

At block 730, in accordance with a determination that the UL transmission repetition is allowed, the terminal device 210 transmits, to the network device, at least one repetition of an UL transmission based on the configuration and the DCI.

In some example embodiments, the processor is further configured to cause the terminal device to: transmit, to the network device, a request for the UL transmission repetition.

In some example embodiments, the request is transmitted on a random access resource.

In some example embodiments, the request is identified by a LCID, wherein the request is associated with one of the following: an initial access procedure, a reestablishment procedure, or a resume procedure.

In some example embodiments, the request is transmitted via a MAC CE, and wherein the MAC CE comprises a MAC subheader with a LCID indication of the request for the UL transmission repetition.

In some example embodiments, a priority of the MAC CE for requesting the at least one repetition of the UL transmission is not lower than a priority of a MAC CE for buffer status reporting, and not higher than a priority of a MAC CE with C-RNTI.

In some example embodiments, the request is transmitted via a MAC CE for PHR, wherein the MAC CE for PHR comprises a MAC CE header with a LCID indication of the request for the UL transmission repetition, and the MAC CE for PHR comprises a normal MAC CE or a truncated MAC CE.

In some example embodiments, the request is transmitted via a CCCH message in a random access procedure, and a first value of an indication in the CCCH message indicates requesting the UL transmission repetition, and a second value of the indication indicates not requesting the UL transmission repetition.

In some example embodiments, the request is transmitted via a MAC CE, and wherein a MAC CE header of the MAC CE comprises a repetition indication, a first value of the repetition indication indicates requesting the uplink transmission repetition, and a second value of the repetition indication indicates not requesting the uplink transmission repetition.

In some example embodiments, the configuration of the uplink transmission repetition comprises a TDRA list.

In some example embodiments, the processor is further configured to cause the terminal device to: in accordance with a determination that a capability of the terminal device supports uplink transmission repetition, and a condition for transmitting the uplink transmission repetition is met, determine that the uplink transmission repetition is allowed; and transmit the uplink transmission with the at least one repetition; in accordance with a determination that the capability of the terminal device supports the uplink transmission repetition, and the condition for transmitting the uplink transmission repetition is not met, determine that the uplink transmission repetition is not allowed; and transmit the uplink transmission without repetition; in accordance with a determination that the capability of the terminal device does not support the uplink transmission repetition, determine that the uplink transmission repetition is not allowed; and transmit the uplink transmission without repetition.

In some example embodiments, a condition for transmitting the uplink transmission repetition is configured for a bandwidth part associated with the terminal device, and wherein the processor is further configured to cause the terminal device to: in accordance with a determination that the condition for transmitting the uplink transmission repetition is met, determine that the uplink transmission repetition is allowed; and transmit the uplink transmission with the at least one repetition; in accordance with a determination that the condition for transmitting the uplink transmission repetition is not met, determine that the uplink transmission repetition is not allowed; and transmit the uplink transmission without repetition.

In some example embodiments, the condition for transmitting the uplink transmission repetition is associated with a RSRP threshold, and wherein the processor is further configured to cause the terminal device to: in accordance with a determination that a RSRP of a downlink pathloss reference is below the RSRP threshold, determine that the condition for transmitting the uplink transmission repetition is met; and in accordance with a determination that the RSRP of the downlink pathloss reference is not below the RSRP threshold, determine that the condition for transmitting the uplink transmission repetition is not met.

In some example embodiments, the RSRP threshold comprises at least one of the following: a first RSRP threshold for message 5 repetition, or a second RSRP threshold for message 3 repetition in a random access procedure.

In some example embodiments, the uplink transmission comprises a transmission of message 5, and the configuration of the uplink transmission repetition comprises a configuration of message 3 repetition, and wherein the processor is further configured to cause the terminal device to: in accordance with a determination that the uplink transmission repetition is allowed, determine that the configuration of the message 3 repetition is used for transmitting the at least one repetition of the uplink transmission after receiving the DCI; and in accordance with a determination that the uplink transmission repetition is not allowed, determine that the configuration of the message 3 repetition is not used for transmitting the at least one repetition of the uplink transmission.

In some example embodiments, the processor is further configured to cause the terminal device to: receive, from the network device, an activation indication of the uplink transmission repetition scheduled by the DCI; and determine, based on at least the activation indication, that the uplink transmission repetition is allowed.

In some example embodiments, the activation indication is received via a MAC CE, and wherein the MAC CE comprises an activation indication, a first value of the activation indication indicates that the DCI is used for scheduling the uplink transmission repetition, and a second value of the activation indication indicates that the DCI is not used for scheduling the uplink transmission repetition.

In some example embodiments, the activation indication is carried in a reserved bit in the MAC CE or in a MAC CE header.

In some example embodiments, the activation indication is received via a MAC CE, and the MAC CE comprises a MAC CE subheader with a LCID indicative of an activation of the uplink transmission repetition.

In some example embodiments, the processor is further configured to cause the terminal device to: upon receipt of a dedicated TDRA list for uplink transmission repetition scheduled by a different DCI format from the network device, terminate the transmission of the at least one repetition.

In some example embodiments, the processor is further configured to cause the terminal device to: receive, from the network device, a termination indication of the uplink transmission repetition; and terminate the transmission of the at least one repetition.

In some example embodiments, the termination indication is received via one of the following: a RRC message, a MAC CE, or a DCI.

In some example embodiments, the configuration of the uplink transmission repetition comprises a dedicated TDRA list for the uplink transmission repetition scheduled by the DCI, and the dedicated TDRA list comprises at least a repetition number.

In some example embodiments, a common TDRA list with repetition and a common TDRA list without repetition are configured for the terminal device, and priorities of the following in descending order comprise: the dedicated TDRA list, the common TDRA list with repetition, the common TDRA list without repetition, a default TDRA list.

In some example embodiments, the dedicated TDRA list with repetition and the dedicated TDRA list without repetition are configured for the terminal device, and priorities of the following in descending order comprise: the dedicated TDRA list with repetition, the dedicated TDRA list without repetition, a common TDRA list, a default TDRA list.

In some example embodiments, the configuration of the uplink transmission repetition is received via a first message, and wherein the first message comprises a repetition number and an indication indicating whether the uplink transmission repetition scheduled by the DCI is activated, and the first message comprises one of the following: a MAC CE, a RRC message, or a system information block.

In some example embodiments, the uplink transmission repetition comprises a message 5 repetition, and the configuration of the uplink transmission repetition comprises a repetition factor for message 5 repetition, and wherein the processor is further configured to cause the terminal device to: determine a repetition number of message 5 repetition by applying the repetition factor to a repetition list configured for message 3 repetition.

In some example embodiments, the processor is further configured to cause the terminal device to: transmit, to the network device, a capability indication of the terminal device indicating support of the uplink transmission repetition.

In some example embodiments, the DCI comprises a DCI format 0_0, and the uplink transmission repetition comprises a message 5 repetition.

FIG. 8 illustrates a flowchart of a communication method 800 implemented at a network device in accordance with some embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the network device 220 in FIG. 2.

At block 810, the network device 220 transmits, to a terminal device, a configuration of uplink transmission repetition scheduled by DCI, wherein the DCI is scrambled with a RNTI selected from C-RNTI or CS-RNTI.

At block 820, upon transmission of the DCI, the network device 220 receives, from the network device, an UL transmission with at least one repetition based on the configuration.

In some example embodiments, the processor is further configured to cause the network device to: receive, from the terminal device, a request for the uplink transmission repetition.

In some example embodiments, the request is received on a random access resource.

In some example embodiments, the request is received via a MAC CE, and wherein the MAC CE comprises a MAC subheader with a LCID indication of the request for the uplink transmission repetition.

In some example embodiments, the request is received via a MAC CE for PHR, wherein the MAC CE for PHR comprises a MAC CE header with a LCID indicative of the request for the uplink transmission repetition, and the MAC CE for PHR comprises a normal MAC CE or a truncated MAC CE.

In some example embodiments, the request is received via a CCCH message in a random access procedure, and a first value of an indication in the CCCH message indicates requesting the uplink transmission repetition, and a second value of the indication indicates not requesting the uplink transmission repetition.

In some example embodiments, the request is received via a MAC CE, and wherein a MAC CE header of the MAC CE comprises a repetition indication, a first value of the repetition indication indicates requesting the uplink transmission repetition, and a second value of the repetition indication indicates not requesting the uplink transmission repetition.

In some example embodiments, the configuration of the uplink transmission repetition comprises a condition for transmitting the uplink transmission repetition.

In some example embodiments, the condition for transmitting the uplink transmission repetition is associated with a RSRP threshold.

In some example embodiments, the uplink transmission comprises a transmission of message 5, and the configuration of the uplink transmission repetition comprises a configuration of message 3 repetition.

In some example embodiments, the processor is further configured to cause the network device to: transmit, to the terminal device, an activation indication of the uplink transmission repetition scheduled by the DCI.

In some example embodiments, the activation indication is transmitted via a MAC CE, and wherein the MAC CE comprises an activation indication, a first value of the activation indication indicates that the DCI is used for scheduling the uplink transmission repetition, and a second value of the activation indication indicates that the DCI is not used for scheduling the uplink transmission repetition.

In some example embodiments, the activation indication is transmitted via a MAC CE, and the MAC CE comprises a MAC CE subheader with a LCID indicative of an activation of the uplink transmission repetition.

In some example embodiments, the processor is further configured to cause the network device to: transmit, to the terminal device, a termination indication of the uplink transmission repetition.

In some example embodiments, the termination indication comprises a configuration of a dedicated TDRA list.

In some example embodiments, the termination indication is transmitted via one of the following: a RRC message, a MAC CE, or a DCI.

In some example embodiments, the processor is further configured to cause the network device to: transmit, to the terminal device, a configuration of a common TDRA list with repetition and a common TDRA list without repetition, wherein priorities of the following in descending order comprise: the dedicated TDRA list, the common TDRA list with repetition, the common TDRA list without repetition, a default TDRA list.

In some example embodiments, the processor is further configured to cause the network device to: transmit, to the terminal device, a configuration of the dedicated TDRA list with repetition and the dedicated TDRA list without repetition, wherein priorities of the following in descending order comprise: the dedicated TDRA list with repetition, the dedicated TDRA list without repetition, a common TDRA list, a default TDRA list.

In some example embodiments, the configuration of the uplink transmission repetition is transmitted via a first message, and wherein the first message comprises a repetition number and an indication indicating whether the uplink transmission repetition scheduled by the DCI is activated, and the first message comprises one of the following: a MAC CE, a RRC message, or a system information block.

In some example embodiments, the uplink transmission repetition comprises a message 5 repetition, and the configuration of the uplink transmission repetition comprises a repetition factor for message 5 repetition, and a repetition number of message 5 repetition is determined by applying the repetition factor to a repetition list configured for message 3 repetition.

In some example embodiments, the processor is further configured to cause the network device to: receive, from the terminal device, a capability indication of the terminal device indicating support of the uplink transmission repetition.

FIG. 9 is a simplified block diagram of a device 900 that is suitable for implementing embodiments of the present disclosure. The device 900 can be considered as a further example implementation of any of the devices as shown in FIG. 2. Accordingly, the device 900 can be implemented at or as at least a part of the terminal device 210 or the network device 220.

As shown, the device 900 includes a processor 910, a memory 920 coupled to the processor 910, a suitable transceiver 940 coupled to the processor 910, and a communication interface coupled to the transceiver 940. The memory 920 stores at least a part of a program 930. The transceiver 940 may be for bidirectional communications or a unidirectional communication based on requirements. The transceiver 940 may include at least one of a transmitter 942 and a receiver 944. The transmitter 942 and the receiver 944 may be functional modules or physical entities. The transceiver 940 has at least one antenna to facilitate communication, though in practice an Access Node mentioned in this application may have several ones. The communication interface may represent any interface that is necessary for communication with other network elements, such as X2/Xn interface for bidirectional communications between eNBs/gNBs, S1/NG interface for communication between a Mobility Management Entity (MME) /Access and Mobility Management Function (AMF) /SGW/UPF and the eNB/gNB, Un interface for communication between the eNB/gNB and a relay node (RN) , or Uu interface for communication between the eNB/gNB and a terminal device.

The program 930 is assumed to include program instructions that, when executed by the associated processor 910, enable the device 900 to operate in accordance with the embodiments of the present disclosure, as discussed herein with reference to FIGs. 1 to 9. The embodiments herein may be implemented by computer software executable by the processor 910 of the device 900, or by hardware, or by a combination of software and hardware. The processor 910 may be configured to implement various embodiments of the present disclosure. Furthermore, a combination of the processor 910 and memory 920 may form processing means 950 adapted to implement various embodiments of the present disclosure.

The memory 920 may be of any type suitable to the local technical network and may be implemented using any suitable data storage technology, such as a non-transitory computer readable storage medium, semiconductor based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory, as non-limiting examples. While only one memory 920 is shown in the device 900, there may be several physically distinct memory modules in the device 900. The processor 910 may be of any type suitable to the local technical network, and may include one or more of general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 900 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.

According to embodiments of the present disclosure, a terminal device comprising a circuitry is provided. The circuitry is configured to: receive, from a network device, a configuration of uplink transmission repetition scheduled by downlink control information, DCI, wherein the DCI is scrambled with a radio network temporary identity, RNTI selected from C-RNTI or CS-RNTI; and in accordance with a determination that the uplink transmission repetition is allowed, transmit, to the network device, at least one repetition of an uplink transmission based on the configuration and the DCI. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the terminal device as discussed above.

According to embodiments of the present disclosure, a network device comprising a circuitry is provided. The circuitry is configured to: transmit, to a terminal device, a configuration of uplink transmission repetition scheduled by downlink control information, DCI, wherein the DCI is scrambled with a radio network temporary identity, RNTI selected from C-RNTI or CS-RNTI; and upon transmission of the DCI, receive, from the network device, an uplink transmission with at least one repetition based on the configuration. According to embodiments of the present disclosure, the circuitry may be configured to perform any method implemented by the network device as discussed above.

The term “circuitry” used herein may refer to hardware circuits and/or combinations of hardware circuits and software. For example, the circuitry may be a combination of analog and/or digital hardware circuits with software/firmware. As a further example, the circuitry may be any portions of hardware processors with software including digital signal processor (s) , software, and memory (ies) that work together to cause an apparatus, such as a terminal device or a network device, to perform various functions. In a still further example, the circuitry may be hardware circuits and or processors, such as a microprocessor or a portion of a microprocessor, that requires software/firmware for operation, but the software may not be present when it is not needed for operation. As used herein, the term circuitry also covers an implementation of merely a hardware circuit or processor (s) or a portion of a hardware circuit or processor (s) and its (or their) accompanying software and/or firmware.

According to embodiments of the present disclosure, a terminal apparatus is provided. The terminal apparatus comprises means for receiving, from a network device, a configuration of uplink transmission repetition scheduled by downlink control information, DCI, wherein the DCI is scrambled with a radio network temporary identity, RNTI selected from C-RNTI or CS-RNTI; and means for in accordance with a determination that the uplink transmission repetition is allowed, transmitting, to the network device, at least one repetition of an uplink transmission based on the configuration and the DCI. In some embodiments, the first apparatus may comprise means for performing the respective operations of the method 700. In some example embodiments, the first apparatus may further comprise means for performing other operations in some example embodiments of the method 700. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

According to embodiments of the present disclosure, a network apparatus is provided. The network apparatus comprises means for transmitting, to a terminal device, a configuration of uplink transmission repetition scheduled by downlink control information, DCI, wherein the DCI is scrambled with a radio network temporary identity, RNTI selected from C-RNTI or CS-RNTI; and means for upon transmission of the DCI, receiving, from the network device, an uplink transmission with at least one repetition based on the configuration. In some embodiments, the second apparatus may comprise means for performing the respective operations of the method 800. In some example embodiments, the second apparatus may further comprise means for performing other operations in some example embodiments of the method 800. The means may be implemented in any suitable form. For example, the means may be implemented in a circuitry or software module.

In summary, embodiments of the present disclosure provide the following aspects.

In an aspect, it is proposed a terminal device comprising: a processor configured to cause the terminal device to: receive, from a network device, a configuration of uplink transmission repetition scheduled by downlink control information, DCI, wherein the DCI is scrambled with a radio network temporary identity, RNTI selected from C-RNTI or CS-RNTI; and in accordance with a determination that the uplink transmission repetition is allowed, transmit, to the network device, at least one repetition of an uplink transmission based on the configuration and the DCI.

In some embodiments, the processor is further configured to cause the terminal device to: transmit, to the network device, a request for the uplink transmission repetition.

In some embodiments, the request is transmitted on a random access resource.

In some embodiments, the request is identified by a logical channel identity, LCID, wherein the request is associated with one of the following: an initial access procedure, a reestablishment procedure, or a resume procedure.

In some embodiments, the request is transmitted via a medium access control, MAC, control element, CE, and wherein the MAC CE comprises a MAC subheader with a LCID indication of the request for the uplink transmission repetition.

In some embodiments, a priority of the MAC CE for requesting the at least one repetition of the uplink transmission is not lower than a priority of a MAC CE for buffer status reporting, and not higher than a priority of a MAC CE with C-RNTI.

In some embodiments, the request is transmitted via a MAC CE for power headroom report, PHR, wherein the MAC CE for PHR comprises a MAC CE header with a LCID indication of the request for the uplink transmission repetition, and the MAC CE for PHR comprises a normal MAC CE or a truncated MAC CE.

In some embodiments, the request is transmitted via a common control channel, CCCH, message in a random access procedure, and a first value of an indication in the CCCH message indicates requesting the uplink transmission repetition, and a second value of the indication indicates not requesting the uplink transmission repetition.

In some embodiments, the request is transmitted via a MAC CE, and wherein a MAC CE header of the MAC CE comprises a repetition indication, a first value of the repetition indication indicates requesting the uplink transmission repetition, and a second value of the repetition indication indicates not requesting the uplink transmission repetition.

In some embodiments, the configuration of the uplink transmission repetition comprises a time domain resource allocation, TDRA, list.

In some embodiments, the processor is further configured to cause the terminal device to: in accordance with a determination that a capability of the terminal device supports uplink transmission repetition, and a condition for transmitting the uplink transmission repetition is met, determine that the uplink transmission repetition is allowed; and transmit the uplink transmission with the at least one repetition; in accordance with a determination that the capability of the terminal device supports the uplink transmission repetition, and the condition for transmitting the uplink transmission repetition is not met, determine that the uplink transmission repetition is not allowed; and transmit the uplink transmission without repetition; in accordance with a determination that the capability of the terminal device does not support the uplink transmission repetition, determine that the uplink transmission repetition is not allowed; and transmit the uplink transmission without repetition.

In some embodiments, a condition for transmitting the uplink transmission repetition is configured for a bandwidth part associated with the terminal device, and wherein the processor is further configured to cause the terminal device to: in accordance with a determination that the condition for transmitting the uplink transmission repetition is met, determine that the uplink transmission repetition is allowed; and transmit the uplink transmission with the at least one repetition; in accordance with a determination that the condition for transmitting the uplink transmission repetition is not met, determine that the uplink transmission repetition is not allowed; and transmit the uplink transmission without repetition.

In some embodiments, the condition for transmitting the uplink transmission repetition is associated with a reference signal receiving power, RSRP, threshold, and wherein the processor is further configured to cause the terminal device to: in accordance with a determination that a RSRP of a downlink pathloss reference is below the RSRP threshold, determine that the condition for transmitting the uplink transmission repetition is met; and in accordance with a determination that the RSRP of the downlink pathloss reference is not below the RSRP threshold, determine that the condition for transmitting the uplink transmission repetition is not met.

In some embodiments, the RSRP threshold comprises at least one of the following: a first RSRP threshold for message 5 repetition, or a second RSRP threshold for message 3 repetition in a random access procedure.

In some embodiments, the uplink transmission comprises a transmission of message 5, and the configuration of the uplink transmission repetition comprises a configuration of message 3 repetition, and wherein the processor is further configured to cause the terminal device to: in accordance with a determination that the uplink transmission repetition is allowed, determine that the configuration of the message 3 repetition is used for transmitting the at least one repetition of the uplink transmission after receiving the DCI; and in accordance with a determination that the uplink transmission repetition is not allowed, determine that the configuration of the message 3 repetition is not used for transmitting the at least one repetition of the uplink transmission.

In some embodiments, the processor is further configured to cause the terminal device to: receive, from the network device, an activation indication of the uplink transmission repetition scheduled by the DCI; and determine, based at least on the activation indication, that the uplink transmission repetition is allowed.

In some embodiments, the activation indication is received via a MAC CE, and wherein the MAC CE comprises an activation indication, a first value of the activation indication indicates that the DCI is used for scheduling the uplink transmission repetition, and a second value of the activation indication indicates that the DCI is not used for scheduling the uplink transmission repetition.

In some embodiments, the activation indication is carried in a reserved bit in the MAC CE or in a MAC CE header.

In some embodiments, the activation indication is received via a MAC CE, and the MAC CE comprises a MAC CE subheader with a LCID indicative of an activation of the uplink transmission repetition.

In some embodiments, the processor is further configured to cause the terminal device to: upon receipt of a dedicated TDRA list for uplink transmission repetition scheduled by a different DCI format from the network device, terminate the transmission of the at least one repetition.

In some embodiments, the processor is further configured to cause the terminal device to: receive, from the network device, a termination indication of the uplink transmission repetition; and terminate the transmission of the at least one repetition.

In some embodiments, the termination indication is received via one of the following: a RRC message, a MAC CE, or a DCI.

In some embodiments, the configuration of the uplink transmission repetition comprises a dedicated TDRA list for the uplink transmission repetition scheduled by the DCI, and the dedicated TDRA list comprises at least a repetition number.

In some embodiments, a common TDRA list with repetition and a common TDRA list without repetition are configured for the terminal device, and priorities of the following in descending order comprise: the dedicated TDRA list, the common TDRA list with repetition, the common TDRA list without repetition, a default TDRA list.

In some embodiments, the dedicated TDRA list with repetition and the dedicated TDRA list without repetition are configured for the terminal device, and priorities of the following in descending order comprise: the dedicated TDRA list with repetition, the dedicated TDRA list without repetition, a common TDRA list, a default TDRA list.

In some embodiments, the configuration of the uplink transmission repetition is received via a first message, and wherein the first message comprises a repetition number and an indication indicating whether the uplink transmission repetition scheduled by the DCI is activated, and the first message comprises one of the following: a MAC CE, a RRC message, or a system information block.

In some embodiments, the uplink transmission repetition comprises a message 5 repetition, and the configuration of the uplink transmission repetition comprises a repetition factor for message 5 repetition, and wherein the processor is further configured to cause the terminal device to: determine a repetition number of message 5 repetition by applying the repetition factor to a repetition list configured for message 3 repetition.

In some embodiments, the processor is further configured to cause the terminal device to: transmit, to the network device, a capability indication of the terminal device indicating support of the uplink transmission repetition.

In some embodiments, the DCI comprises a DCI format 0_0, and the uplink transmission repetition comprises a message 5 repetition.

In an aspect, it is proposed a network device comprising: a processor configured to cause the terminal device to: transmit, to a terminal device, a configuration of uplink transmission repetition scheduled by downlink control information, DCI, wherein the DCI is scrambled with a radio network temporary identity, RNTI selected from C-RNTI or CS-RNTI; and upon transmission of the DCI, receive, from the network device, an uplink transmission with at least one repetition based on the configuration.

In some embodiments, the processor is further configured to cause the network device to: receive, from the terminal device, a request for the uplink transmission repetition.

In some embodiments, the request is received on a random access resource.

In some embodiments, the request is received via a MAC CE, and wherein the MAC CE comprises a MAC subheader with a LCID indication of the request for the uplink transmission repetition.

In some embodiments, the request is received via a MAC CE for power headroom report, PHR, wherein the MAC CE for PHR comprises a MAC CE header with a LCID indicative of the request for the uplink transmission repetition, and the MAC CE for PHR comprises a normal MAC CE or a truncated MAC CE.

In some embodiments, the request is received via a CCCH message in a random access procedure, and a first value of an indication in the CCCH message indicates requesting the uplink transmission repetition, and a second value of the indication indicates not requesting the uplink transmission repetition.

In some embodiments, the request is received via a MAC CE, and wherein a MAC CE header of the MAC CE comprises a repetition indication, a first value of the repetition indication indicates requesting the uplink transmission repetition, and a second value of the repetition indication indicates not requesting the uplink transmission repetition.

In some embodiments, the configuration of the uplink transmission repetition comprises a condition for transmitting the uplink transmission repetition.

In some embodiments, the condition for transmitting the uplink transmission repetition is associated with a RSRP threshold.

In some embodiments, the uplink transmission comprises a transmission of message 5, and the configuration of the uplink transmission repetition comprises a configuration of message 3 repetition.

In some embodiments, the processor is further configured to cause the network device to: transmit, to the terminal device, an activation indication of the uplink transmission repetition scheduled by the DCI.

In some embodiments, the activation indication is transmitted via a MAC CE, and wherein the MAC CE comprises an activation indication, a first value of the activation indication indicates that the DCI is used for scheduling the uplink transmission repetition, and a second value of the activation indication indicates that the DCI is not used for scheduling the uplink transmission repetition.

In some embodiments, the activation indication is transmitted via a MAC CE, and the MAC CE comprises a MAC CE subheader with a LCID indicative of an activation of the uplink transmission repetition.

In some embodiments, the processor is further configured to cause the network device to: transmit, to the terminal device, a termination indication of the uplink transmission repetition.

In some embodiments, the termination indication comprises a configuration of a dedicated TDRA list.

In some embodiments, the termination indication is transmitted via one of the following: a RRC message, a MAC CE, or a DCI.

In some embodiments, the processor is further configured to cause the network device to: transmit, to the terminal device, a configuration of a common TDRA list with repetition and a common TDRA list without repetition, wherein priorities of the following in descending order comprise: the dedicated TDRA list, the common TDRA list with repetition, the common TDRA list without repetition, a default TDRA list.

In some embodiments, the processor is further configured to cause the network device to: transmit, to the terminal device, a configuration of the dedicated TDRA list with repetition and the dedicated TDRA list without repetition, wherein priorities of the following in descending order comprise: the dedicated TDRA list with repetition, the dedicated TDRA list without repetition, a common TDRA list, a default TDRA list.

In some embodiments, the configuration of the uplink transmission repetition is transmitted via a first message, and wherein the first message comprises a repetition number and an indication indicating whether the uplink transmission repetition scheduled by the DCI is activated, and the first message comprises one of the following: a MAC CE, a RRC message, or a system information block.

In some embodiments, the uplink transmission repetition comprises a message 5 repetition, and the configuration of the uplink transmission repetition comprises a repetition factor for message 5 repetition, and a repetition number of message 5 repetition is determined by applying the repetition factor to a repetition list configured for message 3 repetition.

In some embodiments, the processor is further configured to cause the network device to: receive, from the terminal device, a capability indication of the terminal device indicating support of the uplink transmission repetition.

In an aspect, a terminal device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the terminal device discussed above.

In an aspect, a network device comprises: at least one processor; and at least one memory coupled to the at least one processor and storing instructions thereon, the instructions, when executed by the at least one processor, causing the device to perform the method implemented by the network device discussed above.

In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device discussed above.

In an aspect, a computer readable medium having instructions stored thereon, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device discussed above.

In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the terminal device discussed above.

In an aspect, a computer program comprising instructions, the instructions, when executed on at least one processor, causing the at least one processor to perform the method implemented by the network device discussed above.

Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representation, it will be appreciated that the blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the process or method as described above with reference to FIGS. 1 to 9. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program codes, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

The above program code may be embodied on a machine readable medium, which may be any tangible medium that may contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine readable medium may be a machine readable signal medium or a machine readable storage medium. A machine readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination.

Although the present disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the present disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

A terminal device comprising:

a processor configured to cause the terminal device to:

receive, from a network device, a configuration of uplink transmission repetition scheduled by downlink control information, DCI, wherein the DCI is scrambled with a radio network temporary identity, RNTI selected from cell radio network temporary identity, C-RNTI, or configured scheduling radio network temporary identity, CS-RNTI; and

in accordance with a determination that the uplink transmission repetition is allowed, transmit, to the network device, at least one repetition of an uplink transmission based on the configuration and the DCI.
The terminal device of claim 1, wherein the processor is further configured to cause the terminal device to:

transmit, to the network device, a request for the uplink transmission repetition.
The terminal device of claim 2, wherein the request is transmitted on a random access resource.
The terminal device of claim 2, wherein the request is identified by a logical channel identity, LCID,

wherein the request is associated with one of the following: an initial access procedure, a reestablishment procedure, or a resume procedure.
The terminal device of claim 2, wherein the request is transmitted via a medium access control, MAC, control element, CE, and

wherein the MAC CE comprises a MAC subheader with a LCID indication of the request for the uplink transmission repetition.
The terminal device of claim 5, wherein a priority of the MAC CE for requesting the at least one repetition of the uplink transmission is not lower than a priority of a MAC CE for buffer status reporting, and not higher than a priority of a MAC CE with C-RNTI.
The terminal device of claim 2, wherein the request is transmitted via a MAC CE for power headroom report, PHR,

wherein the MAC CE for PHR comprises a MAC CE header with a LCID indication of the request for the uplink transmission repetition, and the MAC CE for PHR comprises a normal MAC CE or a truncated MAC CE.
The terminal device of claim 2, wherein the request is transmitted via a common control channel, CCCH, message in a random access procedure, and a first value of an indication in the CCCH message indicates requesting the uplink transmission repetition, and a second value of the indication indicates not requesting the uplink transmission repetition.
The terminal device of claim 2, wherein the request is transmitted via a MAC CE, and

wherein a MAC CE header of the MAC CE comprises a repetition indication, a first value of the repetition indication indicates requesting the uplink transmission repetition, and a second value of the repetition indication indicates not requesting the uplink transmission repetition.
The terminal device of claim 1, wherein the configuration of the uplink transmission repetition comprises a time domain resource allocation, TDRA, list.
The terminal device of claim 10, wherein the processor is further configured to cause the terminal device to:

in accordance with a determination that a capability of the terminal device supports uplink transmission repetition, and a condition for transmitting the uplink transmission repetition is met,

determine that the uplink transmission repetition is allowed; and

transmit the uplink transmission with the at least one repetition;

in accordance with a determination that the capability of the terminal device supports the uplink transmission repetition, and the condition for transmitting the uplink transmission repetition is not met,

determine that the uplink transmission repetition is not allowed; and

transmit the uplink transmission without repetition;

in accordance with a determination that the capability of the terminal device does not support the uplink transmission repetition,

determine that the uplink transmission repetition is not allowed; and

transmit the uplink transmission without repetition.
The terminal device of claim 1, wherein a condition for transmitting the uplink transmission repetition is configured for a bandwidth part associated with the terminal device, and

wherein the processor is further configured to cause the terminal device to:

in accordance with a determination that the condition for transmitting the uplink transmission repetition is met,

determine that the uplink transmission repetition is allowed; and

transmit the uplink transmission with the at least one repetition;

in accordance with a determination that the condition for transmitting the uplink transmission repetition is not met,

determine that the uplink transmission repetition is not allowed; and

transmit the uplink transmission without repetition.
The terminal device of claim 12, wherein the condition for transmitting the uplink transmission repetition is associated with a reference signal receiving power, RSRP, threshold, and

wherein the processor is further configured to cause the terminal device to:

in accordance with a determination that a RSRP of a downlink pathloss reference is less than the RSRP threshold, determine that the condition for transmitting the uplink transmission repetition is met; and

in accordance with a determination that the RSRP of the downlink pathloss reference is not below the RSRP threshold, determine that the condition for transmitting the uplink transmission repetition is not met.
The terminal device of claim 13, wherein the RSRP threshold comprises at least one of the following:

a first RSRP threshold for message 5 repetition, or

a second RSRP threshold for message 3 repetition in a random access procedure.
The terminal device of claim 2, wherein the uplink transmission comprises a transmission of message 5, and the configuration of the uplink transmission repetition comprises a configuration of message 3 repetition, and

wherein the processor is further configured to cause the terminal device to:

in accordance with a determination that the uplink transmission repetition is allowed, determine that the configuration of the message 3 repetition is used for transmitting the at least one repetition of the uplink transmission after receiving the DCI; and

in accordance with a determination that the uplink transmission repetition is not allowed, determine that the configuration of the message 3 repetition is not used for transmitting the at least one repetition of the uplink transmission.
The terminal device of claim 2, wherein the processor is further configured to cause the terminal device to:

receive, from the network device, an activation indication of the uplink transmission repetition scheduled by the DCI; and

determine, based at least on the activation indication, that the uplink transmission repetition is allowed.
The terminal device of claim 16, wherein the activation indication is received via a MAC CE, and

wherein the MAC CE comprises an activation indication, a first value of the activation indication indicates that the DCI is used for scheduling the uplink transmission repetition, and a second value of the activation indication indicates that the DCI is not used for scheduling the uplink transmission repetition.
The terminal device of claim 17, wherein the activation indication is carried in a reserved bit in the MAC CE or in a MAC CE header.
The terminal device of claim 16, wherein the activation indication is received via a MAC CE, and the MAC CE comprises a MAC CE subheader with a LCID indicative of an activation of the uplink transmission repetition.
The terminal device of claim 1, wherein the processor is further configured to cause the terminal device to:

upon receipt of a dedicated TDRA list for uplink transmission repetition scheduled by a different DCI format from the network device, terminate the transmission of the at least one repetition.