Terminal device, network device, and communication method

Abstract

The embodiments of the present disclosure relate to a method, an apparatus, and a computer-readable medium for communication. According to one embodiment of the present disclosure, a terminal device receives from a network device a radio resource control (RRC) configuration including a repetition number for a physical uplink shared channel (PUSCH) transmission occasion associated with a first sounding reference signal (SRS) resource indicator (SRI) and a PUSCH transmission occasion associated with a second SRI, the RRC configuration further including a redundancy version (RV) offset for an RV sequence associated with the first SRI. The terminal device receives a DCI indicating an RV identity. If the first RV sequence determined based on the repetition number, the identity, and the RV offset satisfies a condition, the terminal device does not apply the first RV sequence. Thus, reliability is improved.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and more particularly, to methods, apparatus, and computer storage media for communication.

Background Art

[0002] Multiple-input multiple-output (MIMO) technology is widely used in conventional wireless communication systems in which a network device uses a large number of antenna elements to communicate with a terminal device. Also, multi-transmission and reception point (multi-TRP) (and multi-panel reception) technology has recently been proposed and discussed to improve the reliability and robustness of communication between a network device and a terminal device. Generally speaking, downlink control information (DCI) may be used by a network device to indicate scheduling information to a terminal device. Several proposals regarding DCI for enabling multi-TRP and / or multi-panel have been discussed and some agreements have already been obtained.

Summary of the Invention

Problems to be Solved by the Invention

[0003] Overall, embodiments of the present disclosure provide a method, apparatus, and computer storage medium for redundant version determination.

Means for Solving the Problems

[0004] In a first aspect, a communication method is provided. The method includes, at a terminal device, receiving, from a network device, a radio resource control (RRC) configuration including a number of repetitions for a physical uplink shared channel (PUSCH) transmission occasion associated with a first sounding reference signal (SRS) resource indicator (SRI) and a PUSCH transmission occasion associated with a second SRI, the RRC configuration further including a redundancy version (RV) offset for an RV sequence associated with the first SRI; receiving, from the network device, downlink control information (DCI) indicating an identity of an RV; determining whether a first RV sequence for the PUSCH transmission occasion associated with the second SRI, determined based on the number of repetitions, the identity, and the RV offset, satisfies a condition for iterative transmission for the PUSCH transmission occasion associated with the second SRI; and transmitting uplink data to the network device in the PUSCH transmission occasion associated with the second SRI without applying the first RV sequence according to a determination that the first RV sequence satisfies the condition.

[0005] In a second aspect, a communication method is provided. The method includes, at a terminal device, receiving, from a network device, a radio resource control (RRC) configuration including a number of repetitions for iterative transmission for a PUSCH transmission occasion associated with a first SRS resource indicator (SRI) and a PUSCH transmission occasion associated with a second SRI, a set of permitted parameters, and an indication to activate a first transmission associated with the second SRI; and transmitting the first transmission to the network device according to a determination that the PUSCH transmission occasion satisfies a condition.

[0006] In a third aspect, a communication method is provided. The method includes, in a network device, transmitting to a terminal device a radio resource control (RRC) configuration including a number of repetitions for a physical uplink shared channel (PUSCH) transmission occasion associated with a first sounding reference signal (SRS) resource indicator (SRI) and a PUSCH transmission occasion associated with a second SRI, the RRC configuration further including a redundancy version (RV) offset for an RV sequence associated with the first SRI and a redundancy version (RV) offset for the RV sequence associated with the first SRI; transmitting to the terminal device a downlink control information (DCI) indicating an identity of an RV; and receiving uplink data from the terminal device in a PUSCH transmission occasion associated with the second SRI without applying the first RV sequence according to a determination that the first RV sequence determined based on the number of repetitions and the identity satisfies a condition for iterative transmission for the PUSCH transmission occasion associated with the second SRI.

[0007] In a fourth aspect, a communication method is provided. The method includes, in a network device, transmitting to a terminal device a radio resource control (RRC) configuration including a number of repetitions for a physical uplink shared channel (PUSCH) transmission occasion associated with a first sounding reference signal (SRS) resource indicator (SRI) and a PUSCH transmission occasion associated with a second SRI, a set of configured grant parameters, and an indication to activate a first transmission associated with the second SRI; and receiving the first transmission from the terminal device according to a determination that the PUSCH transmission occasion satisfies a condition.

[0008] In a fifth aspect, a terminal device is provided. The terminal device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the terminal device to execute the method according to the first aspect of the present disclosure.

[0009] In a sixth aspect, a terminal device is provided. The terminal device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the terminal device to execute the method according to the second aspect of the present disclosure.

[0010] In a seventh aspect, a network device is provided. The network device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the network device to execute the method according to the third aspect of the present disclosure.

[0011] In an eighth aspect, a network device is provided. The network device includes a processor and a memory coupled to the processor. The memory stores instructions that, when executed by the processor, cause the network device to execute the method according to the fourth aspect of the present disclosure.

[0012] In a ninth aspect, a computer-readable medium storing instructions is provided. The instructions, when executed on at least one processor, cause the at least one processor to execute the method according to the first, second, third, or fourth aspect of the present disclosure.

[0013] Other features of the present disclosure should be easily understood from the following description.

Brief Description of the Drawings

[0014] Some embodiments of the present disclosure will be described in more detail in the accompanying drawings to further clarify the above and other objects, features, and advantages of the present disclosure.

[0015]

Figure 1A

Figure 1B

[0016]

Figure 2A

Figure 2B

[0017]

Figure 3

[0018]

Figure 4

[0019]

Figure 5

[0020]

Figure 6

[0021]

Figure 7

[0022]

Figure 8

[0023]

Figure 9

[0024]

Figure 10

[0025] In the figure, the same or similar reference numerals represent the same or similar elements.

Embodiments for Carrying Out the Invention

[0026] Here, the principles of the present disclosure will be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and are intended to assist those skilled in the art in understanding and implementing the present disclosure, without suggesting any limitation on the scope of the present disclosure. The disclosure content described herein can be implemented in various ways different from the methods described below.

[0027] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art of the present disclosure.

[0028] As used herein, the term "terminal device" means any device having wireless or wired communication capabilities. Examples of terminal devices include, but are not limited to, user equipment (UE), personal computers, desktop computers, mobile phones, cellular phones, smartphones, personal digital assistants (PDAs), portable computers, tablets, wearable devices, Internet of Things (IoT) devices, any Internet of Everything (IoE) devices, machine type communication (MTC) devices, in-vehicle devices for vehicle-to-everything (V2X) communication, etc. Here, "X" in V2X represents pedestrians, vehicles or infrastructure / network, or image acquisition devices such as digital cameras, gaming devices, music storage and playback devices, or Internet appliances that enable wireless or wired Internet access and browsing. The term "terminal device" may be used interchangeably with UE, mobile station, subscriber station, mobile terminal, user terminal, or wireless device. Also, the term "network device" means a device that can provide or host a cell or coverage with which a terminal device can communicate. Examples of network devices include, but are not limited to, Node B (NodeB or NB), evolved Node B (eNodeB or eNB), next-generation Node B (gNB), transmission and reception point (TRP), remote radio unit (RRU), radio head (RH), remote radio head (RRH), femto node, pico node, and other low-power nodes.

[0029] In one embodiment, the terminal device can be connected to 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 may be a secondary node. The first network device and the second network device may use different radio access technologies (RATs). In one embodiment, the first network device may be a first RAT device, and the second network device may be a second RAT device. In one embodiment, the first RAT device is an eNB, and the second RAT device is a gNB. Information regarding different RATs may be transmitted from at least one of the first network device and the second network device to the terminal device. In one embodiment, the first information may be transmitted from the first network device to the terminal device, and the second information may be transmitted from the second network device directly or via the first network device to the terminal device. In one embodiment, information regarding the settings of the terminal device set by the second network device may be transmitted from the second network device via the first network device. Information regarding the re - settings of the terminal device set by the second network device may be transmitted from the second network device directly or via the first network device to the terminal device.

[0030] As used herein, the singular forms "a", "an", and "the" include the plural forms as well, unless the context clearly dictates otherwise. The terms "comprising" and its variants should be understood as open - ended terms meaning "including, but not limited to". The term "based on" should be understood as "at least partially based on". The terms "one embodiment" and "an embodiment" should be understood as "at least one embodiment". The term "another embodiment" should be understood as "at least one other embodiment". Terms such as "first", "second", etc. may refer to different or the same objects. There may be other explicit and implicit definitions hereinafter.

[0031] In some instances, a value, procedure, or device is referred to as "best," "lowest," "highest," "minimum," "maximum," etc. Such descriptions are intended to indicate that a selection can be made from among a number of available functional alternatives, and it should be understood that such a selection need not be better, smaller, higher, or otherwise preferable to other selections.

[0032] As used herein, the term "circuit" can mean a hardware circuit and / or a combination of a hardware circuit and software. For example, a circuit may be an analog and / or digital hardware circuit in combination with software / firmware. As yet another example, a circuit may be any portion of a hardware processor having software, including a digital signal processor, software, and one or more memories that cooperate to cause a device, such as a terminal device or a network device, to perform various functions. In yet another example, a circuit may be a hardware circuit and / or a processor, such as a microprocessor or a portion thereof, that requires software / firmware for operation, although the software need not be present if not required for operation. As used herein, the term "circuit" includes a hardware circuit or only one or more processors, or a portion of a hardware circuit or one or more processors, and the implementation of its (or their) accompanying software and / or firmware.

[0033] As used herein, the term "TRP" means an antenna array (having one or more antenna elements) that is available to a network device located at a particular geographical location. Although some embodiments of the present disclosure have been described with reference to multi-TRP as an example, these embodiments are for illustrative purposes only, to assist those skilled in the art in understanding and implementing the present disclosure, and do not imply any limitation on the scope of the present disclosure. It should be understood that the subject matter of the present disclosure described herein can be implemented in various ways different from the methods described below.

[0034] Generally speaking, one TRP usually corresponds to one SRS resource set. As used herein, the term "single TRP" means that a single SRS resource set is used to perform a related transmission (e.g., PUSCH transmission), and the term "multi-TRP" means that a plurality of SRS resource sets are used to perform a related transmission (e.g., PUSCH transmission).

[0035] Hereinafter, the terms "PUSCH transmission", "PUSCH transmission occasion", "uplink transmission", "PUSCH repetition", "PUSCH occasion", and "PUSCH reception" may be used interchangeably. The terms "DCI" and "DCI format" may be used interchangeably. The terms "transmission", "transmission occasion", and "repetition" may be used interchangeably. The terms "precoder", "precoding", "precoding matrix", "beam", "spatial relation information", "spatial relation info", "TPMI", "precoding information", "precoding information and number of layers", "precoding matrix indicator (PMI: precoding matrix indicator)", "precoding matrix indicator", "transmission precoding matrix support", "precoding matrix indication", "TCI state", "transmission configuration indicator", "quasi co-location (QCL)", "quasi-colocation", "QCL parameter", and "spatial relation" may be used interchangeably. The terms "SRI", "SRS resource set index", "UL TCI", "UL spatial region filter", "UL beam", "combined TCI" may be used interchangeably.

[0036] Recently, there has been a discussion on enhancing support for the introduction of multi-TRP. For example, it has been proposed to identify and specify characteristics that improve the reliability and robustness of physical channels other than the Physical Downlink Shared Channel (PDSCH), such as the Physical Downlink Control Channel (PDCCH), Physical Uplink Shared Channel (PUSCH), and / or Physical Uplink Control Channel (PUCCH), by using multi-TRP and / or multi-panel based on the reliability characteristics of Release 16 as a baseline. To improve the reliability and robustness of PUSCH, PUSCH transmission may be scheduled based on multi-TRP and / or multi-panel using single or single or multiple Downlink Control Information (DCI). The maximum number of Sounding Reference Signal (SRS) resource sets may be increased to two, and it has been agreed that two SRS resource indicator feeds corresponding to the two SRS resource sets may be introduced into the DCI that schedules PUSCH transmission. Additionally, two Transmit Precoding Matrix Indicator (TPMI) fields may be introduced into the DCI to schedule PUSCH transmission. It has also been proposed that dynamic switching between multi-TRP and / or multi-panel and single-TRP should be supported.

[0037] Since Release-16, for single DCI-based MTRP transmission, PDSCH retransmissions have been supported for better reliability. In Release-17, MTRP retransmissions have also been extended for both dynamic grant (DG) and configured grant (CG) transmissions for PUSCH. According to some techniques, the sequences for Release-16 may be reused for PUSCH transmission. However, reusing the new sequences implemented in Release-16 for PUSCH retransmissions may cause some performance problems. Furthermore, reusing the Release-16 downlink (DL) like a new redundancy version (RV) sequence or applying a cyclic shift version for PUSCH retransmissions may cause some performance problems. According to some techniques, an RV sequence shift may be added as a dynamic grant PUSCH retransmission. However, no solution for the first transmission is provided. According to other techniques, the first transmission also starts in the first transmission occasion of the second TRP, but the RV sequence shift applied to the second TRP is not considered, and the RV 0 may not be at the starting position in the RV sequence. Furthermore, in some other techniques, it is assumed that the RV sequence is always mapped to start from 0. However, the RV 0 preceding transmission occasion related to the transmission occasion may be wasted. Furthermore, there is no diversity or flexibility in using different RV sequences for transmissions to different TRPs.

[0038] In the uplink, configured grants are used to handle transmissions without a dynamic grant. Two types of configured grants are supported and differ in how they are enabled (see Figures 1A and 1B).

[0039] Figure 1A shows the configured grant type 1 in which uplink grants are provided by RRC including activation of the grant, and L1 / L2 control signaling is used to activate / deactivate transmissions. Type 1 sets all transmission parameters including period, time offset, and frequency resources, as well as the modulation and coding schemes for possible uplink transmissions, using RRC signaling. When receiving the RRC configuration in slot 111, the device may start transmission using the configured grant at the time given by the period and offset. The reason for the offset is to control at what time the device is permitted to transmit. Generally, there is no concept of activation time in RRC signaling, and the RRC configuration becomes effective as soon as it is correctly received. This point may vary depending on whether RLC retransmission is required to deliver the RRC command. To avoid this ambiguity, the time offset with respect to the SFN is included in the configuration. The CG configuration may be activated from slot 110-1. Slots 110-1, 110-2, and 110-3 may be possible uplink transmission occasions.

[0040] Figure 1B shows the configured grant type 2 in which the transmission period is provided by RRC. Type 2 is similar to downlink semi-persistent scheduling. RRC signaling is used to set the period, and the transmission parameters are provided as part of the activation using PDCCH. The RRC configuration may be received in slot 121. When receiving the PDCCH for the activation command within slot 122, if there is data in the buffer, the device transmits according to the preset period. If there is no data to transmit, the device does not transmit anything as in type 1. Note that since the activation time is better defined by the PDCCH transmission instant, in this case, no time offset is required. Slots 120-1, 120-2, and 120-3 may be possible uplink transmission occasions.

[0041] To solve at least a part of the above problems, a solution regarding redundant version determination of iterative transmission has been proposed. According to an embodiment of the present disclosure, a terminal device receives an RRC configuration from a network device, the RRC configuration including the number of repetitions for a physical uplink shared channel (PUSCH) transmission occasion associated with a first sounding reference signal (SRS) resource indicator (SRI) and a PUSCH transmission occasion associated with a second SRI, and further including a redundant version (RV) offset for an RV sequence associated with the first SRI. The terminal device receives a DCI indicating the identity of the RV. If a first RV sequence determined based on the number of repetitions, the identity, and the RV offset meets the conditions, the terminal device does not apply the first RV sequence. Thus, the reliability is improved.

[0042] FIG. 2A shows an exemplary communication network 200 in which an embodiment of the present disclosure can be implemented. A communication system 200, which is part of the communication network, includes terminal devices 210-1, 210-2, ···, 210-N, which can be collectively referred to as "terminal devices 210". The number N can be any suitable integer. The communication network 100 includes a network device 220 that serves the terminal devices 210. Further, the service area provided by the network device 220 is referred to as a serving cell 202. The network 200 may provide one or more serving cells 202 to serve the terminal devices 210. The terminal devices 210 can communicate with the network device 220 via one or more physical communication channels or links.

[0043] In communication network 200, the link from terminal device 210 to network device 220 is referred to as an uplink (UL), and the link from network device 220 to terminal device 210 is referred to as a downlink (DL). In the UL, terminal device 210 is a TX device (or transmitter), and network device 220 is an RX device (or receiver). In the DL, network device 220 is a transmitting (TX) device (or transmitter), and terminal device 210 is a receiving (RX) device (or receiver).

[0044] In a specific example of FIG. 2A, network device 220 may schedule UL transmissions such as DCI (e.g., PUSCH transmissions). Below, exemplary messages used to schedule PUSCH transmissions will be discussed together with DCI. It should be understood that radio resource control (RRC) messages / signaling and media access control (MAC) control element (CE) messages / signaling may also be used to schedule PUSCH transmissions.

[0045] Communication in communication network 200 may comply with any suitable standard including, but not limited to, New Radio access (NR), Long Term Evolution (LTE), LTE-Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA (Registered Trademark) ), Code Division Multiple Access (CDMA), and Global System for Mobile Communications (GSM), etc. Further, the communication may be performed according to any generation of communication protocol known currently or developed in the future. Examples of communication protocols include, but are not limited to, the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocols.

[0046] It should be understood that the number of network devices, terminal devices, and / or serving cells is for illustrative purposes only and does not imply any limitation to the present disclosure. The communication network 200 may include any suitable number of network devices, terminal devices, and / or serving cells suitable for implementing the embodiments of the present disclosure. Also, in some examples, it should be understood that only a homogeneous network arrangement or only a heterogeneous network arrangement may be included in the communication network 200.

[0047] Furthermore, to support multi-TRP and / or multi-panel, the network device 220 may include one or more TRPs. For example, the network device 220 may be coupled to multi-TRPs at different geographical locations to achieve better coverage. One or more of the multi-TRPs may be included in the same serving cell or different serving cells. It should be understood that a TRP may be a panel, and a panel may refer to an antenna array (having one or more antenna elements).

[0048] FIG. 2B shows an exemplary scenario of the communication network 200 shown in FIG. 2A. As shown in FIG. 2B, the network device 220 may communicate with the terminal device 210 via TRPs 230-1 and 230-2 (collectively referred to as TRP 230). In the following text, TRP 230-1 may be referred to as the first TRP, and TRP 230-2 may be referred to as the second TRP. The first and second TRPs 230-1 and 230-2 may be included in the same serving cell (e.g., serving cell 202 shown in FIG. 2A) or different serving cells provided by the network device 220.

[0049] It should be understood that the number of network devices, terminal devices, and / or TRPs is for illustrative purposes only and does not imply any limitation to the present disclosure. The communication network 200 may include any suitable number of network devices, terminal devices, and / or TRPs suitable for implementing the embodiments of the present disclosure.

[0050] In the following, some embodiments of the present disclosure are described with reference to two TRPs, a first TRP 230-1 and a second TRP 230-2, within the same serving cell provided by the network device 220. However, these embodiments are for illustrative purposes only, and are intended to assist those skilled in the art in understanding and implementing the present disclosure, and do not imply any limitation on the scope of the present disclosure. It should be understood that the content of the present disclosure described herein can be implemented in various ways different from the methods described below.

[0051] FIG. 3 shows a signaling diagram illustrating a process 300 between devices according to some exemplary embodiments of the present disclosure. For illustrative purposes only, process 300 will be described with reference to FIG. 2B. Process 300 may involve the terminal device 210-1, the TRP 230-1, and the TRP 230-2. It should be noted that process 300 is merely an example and not a limitation.

[0052] The terminal device 210-1 may be configured to have a condition or a set of conditions for repeated PUSCH transmission to the TRP 230-2. For example, the condition may indicate that the first RV sequence is not applied when the RV sequence does not include RV at the first position of the RV sequence. Alternatively or additionally, the condition may indicate that the RV sequence is not applied when the RV sequence does not include RV at the first and second positions of the RV sequence. In other embodiments, the condition may indicate that the RV sequence is not applied when neither RV 0 nor RV 3 exists at the first and second positions of the RV sequence. FIG. 5 is a schematic diagram showing an example of a cyclic buffer for incremental redundancy. As shown in FIG. 5, the uplink data 500 may include systematic bits 510 and a set of check bits. The RV of the uplink data 500 may include a bit set 5010, and the RV of the uplink data 500 0 including RV at the first and second positions of the RV sequence may also be applicable. FIG. 5 is a schematic diagram showing an example of a cyclic buffer for incremental redundancy. As shown in FIG. 5, the uplink data 500 may include systematic bits 510 and a set of check bits. The RV of the uplink data 500 may include a bit set 5010, and the RV of the uplink data 500 0 including RV at the first and second positions of the RV sequence may also be applicable. FIG. 5 is a schematic diagram showing an example of a cyclic buffer for incremental redundancy. As shown in FIG. 5, the uplink data 500 may include systematic bits 510 and a set of check bits. The RV of the uplink data 500 may include a bit set 5010, and the RV of the uplink data 500 0 also RV 3 also does not exist, the condition may indicate that the RV sequence is not applied. FIG. 5 is a schematic diagram showing an example of a cyclic buffer for incremental redundancy. As shown in FIG. 5, the uplink data 500 may include systematic bits 510 and a set of check bits. The RV of the uplink data 500 may include a bit set 5010, and the RV of the uplink data 500 0 may include a bit set 5010, and the RV of the uplink data 5001 may include a bit set 5020 and the RV of the uplink data 500 2 may include a bit set 5030 and the RV of the uplink data 500 3 may include a bit set 5040. The RV 0 and the RV 3 both include more systematic bits and are thus self - decodable. Therefore, by applying conditions, the reliability of PUSCH transmission is improved.

[0053] The network device 220 transmits radio resource control (RRC) configuration to the terminal device 210 - 1. The RRC configuration includes the number of repetitions for the PUSCH transmission occasion associated with the first sounding reference signal indicator (SRI) and the PUSCH transmission occasion associated with the second SRI. The PUSCH transmission occasion associated with the first SRI may be used for the TRP 230 - 1, and the PUSCH transmission occasion associated with the second SRI may be used for the TRP 230 - 2. As an example only, when the number of repetitions indicates 4, it means that the total transmission repetitions for the TRP 230 - 1 and the TRP 230 - 2 are 4.

[0054] The RRC configuration further includes an RV offset for the RV sequence associated with the first SRI. The RV offset is "rv sIt may be expressed as "」. The terminal device 210-1 may transmit a UE capability report to the network device 220 in order to notify the network of its capabilities. The RRC configuration may be determined based on the UE capability report. In some embodiments, when the UE capability report indicates that the terminal device 210-1 can enable the condition for retransmission for the PUSCH transmission occasion associated with the second SRI, the RRC configuration may include a first indication for enabling the condition for retransmission for the PUSCH transmission occasion associated with the second SRI. For example, the RRC configuration may include the parameter "RVRestrictions-secondTRP". Alternatively or additionally, when the UE capability report indicates that the terminal device 210-1 can shift the RV sequence, the RRC configuration may include a second indication for shifting the RV sequence for the PUSCH transmission associated with the TRP 130-2. For example, the RRC configuration may include the parameter "shiftedToRV0_secondTRP". Details of shifting the first sequence will be described later.

[0055] The network device 220 transmits downlink control information (DCI) (2010). The DCI may be used to schedule the PUSCH. The DCI includes the identity of the RV. The identity of the RV may be expressed as "rv id 」.

[0056] The terminal device 210-1 may determine a first RV sequence based on the number of repetitions, the identity, and the RV offset (2015). For example, the first RV sequence may be determined based on Table 1 below. TIFF0007691004000001.tif83163

[0057] For all PUSCH transmission occasions associated with the first TRP 130-1, the applicable redundancy version is derived according to Table 2 (shown below), where n is associated with the first TRP PUSCHIt is counted considering only the transmission occasions. The redundant version for the PUSCH transmission occasion associated with the second TRP 130-2 is derived according to Table 1, where the additional shift operation for each redundant version rv s is set by the upper layer parameter sequenceOffsetforRV-PUSCH, and n is counted considering only the PUSCH transmission occasions associated with the second TRP. In other words, the RV sequence associated with the second SRI may be determined by the RV offset from the selected RV sequence associated with the first SRI. n starts from 0 and is up to 1144 for TIFF0007691004000002.tif, where K represents the number of repetitions, and 717 for TIFF0007691004000003.tif represents the sealing operation. TIFF0007691004000004.tif73160

[0058] Alternatively, the terminal device 210-1 may determine the first RV sequence based on the following formula. X=(mod(mod(n,4)+rv s , 4)+1) th (1) Here, X represents the x-th value of the RV sequence applied to the first SRI, and the rv s represents the RV offset for the RV sequence associated with the first SRI, and n represents the n-th transmission associated with the second SRI. The value of X may start from 1. In other words, X may be a positive integer. As only one example, when rv s is equal to 1 and RV id is equal to 2, the RV sequence associated with the first SRI may be {RV 2 ,RV 3 ,RV 1 ,RV 0}. In this case, when n is equal to 0 and x is equal to 2, according to formula (1), RV 3corresponds. Similarly, when n is equal to 1 and x is equal to 3, RV 1 corresponds. When n is equal to 2 and x is equal to 4, RV 0 corresponds. When n is equal to 3 and x is equal to 1, RV 2 corresponds. Therefore, the first RV sequence may be {RV 3 , RV 1 , RV 0 , RV 2}. Equation (1) may be expressed as "(mod(n + rv s , 4)+1) th ". It should be noted that Equation (1) is merely an example and is not limiting.

[0059] In other embodiments, the terminal device 210-1 may determine the first RV sequence based on Table 3-5 below. Note that the numbers and values shown in Table 3-5 are merely examples and are not limiting. TIFF0007691004000005.tif80162 TIFF0007691004000006.tif80162TIFF0007691004000007.tif80162

[0060] The terminal device 210-1 may determine whether a set of conditions for PUSCH retransmission to the TRP 230-2 is applicable (2020). For example, when the number of repetitions associated with the second SRI is less than a predetermined number, the set of conditions may be applied. For example, the predetermined number may be 4. Note that the predetermined number may be any appropriate number. Alternatively, when there is a negative acknowledgment (NACK) associated with the TRP 230-2 implied by the DCI, the terminal device 210-1 may apply the set of conditions. In other embodiments, when there is a non-ideal backhaul between the TRP 230-1 and the TRP 230-2, the set of conditions may be applied. In one embodiment, the term "non-ideal backhaul" means that there are delays and losses between the TRPs or that there is an indication indicating dynamic switching (e.g., via DCI). As another exemplary embodiment, when there is a dynamic switch from a single TRP to multiple TRPs, the terminal device 210-1 may apply the set of conditions.

[0061] The terminal device 210-1 determines whether the first RV sequence meets the conditions (2025). For example, the terminal device 210-1 may determine whether the first RV sequence does not include an RV at the first position of the RV sequence. Alternatively or additionally, the terminal device 210-1 may determine whether the first RV sequence does not include an RV at the first and second positions of the RV sequence and whether the RV sequence is not applicable. In other embodiments, the terminal device 210-1 may determine whether the first RV sequence does not include an RV at the first and second positions of the RV sequence and also does not include an RV at the first and second positions of the RV sequence and whether the RV sequence is not applicable. 0 As an alternative or in addition, the terminal device 210-1 may determine whether the first RV sequence does not include an RV at the first and second positions of the RV sequence and whether the RV sequence is not applicable. 0 In other embodiments, the terminal device 210-1 may determine whether the first RV sequence does not include an RV at the first and second positions of the RV sequence and whether the RV sequence is not applicable. 0 also RV 3 also does not include and whether the RV sequence is not applicable.

[0062] As an example only, when the RV offset is equal to 3 (i.e., rv s ), the first RV sequence may be determined based on Table 8 below. Similarly, when the RV offset is 1 (i.e., rv sIf it is equal to (), the first RV sequence may be determined based on Table 6 below. When the RV offset is 2 (i.e., rv s If it is equal to (), the first RV sequence may be determined based on Table 7 below. Note that the numbers and values shown in Tables 6 to 8 are merely examples and are not limiting. TIFF0007691004000008.tif82166 TIFF0007691004000009.tif80162 TIFF0007691004000010.tif82166 table 8 According to, when rv id is 2, the first RV sequence is {RV 1 , RV 2 , RV 0 , RV 3}}. In this case, the first RV sequence satisfies the condition. Similarly, according to Table 6 , when rv id is 1, the first RV sequence is {RV 2 , RV 1 , RV 3 , RV 0}}. In this case, the first RV satisfies the condition. The terminal device 210-1 does not expect the first RV sequence to satisfy the condition. In other words, when rv s is set to be equal to 3, the terminal device does not expect to receive rv id equal to 2. When rv s is set to be equal to 1, the terminal device does not expect to receive rv id equal to 1. In this case, when rv s is set to be equal to 3, the network device 220 should avoid transmitting rv id equal to 2, or when rv s is set to be equal to 1, avoid transmitting rv id equal to 1. In other words, when set to have the upper layer parameter RVRestrictions-secondTRP, the UE, when rv sWhen set to =y, it does not expect to receive rvid=x.

[0063] When the first RV sequence meets the condition, the terminal device 210-1 transmits uplink data to the network device 220 without applying the first RV sequence (2030). For example, when there is only one PUSCH transmission occasion associated with the second TRP 230-2, the terminal device 210-1 should always transmit the RV of the uplink data. 0

[0064] Alternatively, as described above, the RRC configuration may include a second instruction to shift the RV sequence for PUSCH transmission associated with the TRP 130-2. When set to have the upper layer parameter shiftedToRV0_secondTRP, when the terminal device 210-1 receives rv s =x when set to =y, the terminal device 210-1 autonomously determines the RV sequence as if it were within the row starting with RV0. In this case, when the first RV sequence meets the condition, the terminal device 210-1 may shift the first RV sequence to a second sequence that does not meet the condition. For example, according to the table id 8 According to, the first RV sequence is {RV 1 , RV 2 , RV 0 , RV 3}. In this case, the terminal device 210-1 may shift the first RV sequence to a second RV sequence {RV 8 0 , RV 3 , RV 1 , RV 2} based on the table. Similarly, as another embodiment, according to Table 8, the first RV sequence is {RV 2 , RV 1 , RV 3 , RV 0}. In this case, the terminal device 210-1 may shift the first RV sequence to {RV 6 0 ​​​​,RV 2 ,RV 1 ,RV 3} may be shifted to a second RV sequence which is. In some embodiments, the terminal device 210-1 may transmit uplink data to the network device 220 based on the second RV sequence. Alternatively, the terminal device 210-1 may transmit the RV 0 of the uplink data to the network device 220.

[0065] In some embodiments, as described above, the terminal device 210-1 may transmit a UE capability report to the network device 220 to notify the network of its capabilities. For example, the terminal device 210-1 may notify the network that it can determine the RV sequence based on the cyclic shift of the sequence. As only one example, the above equations (1) and Tables 3 to 5 show examples of cyclic shifts. The terminal device 210-1 may also notify the network that it can determine the RV sequence based on the sequential shift of the sequence. As only one example, the above Tables 1, 6 to 8 show examples of sequential shifts. In some embodiments, new upper layer signaling may be added to clarify the ambiguity. For example, the RRC parameter SequenceOffsetforRV-v16x0 may be used to indicate that the cyclic shift RV sequence is adopted, and the candidate value may be the same as that for sequenceOffsetforRV. Alternatively, an upper layer parameter, such as shiftOperationRVSequence with a candidate value, may be added to indicate whether to use the offset for each RV or to cyclically shift the RV sequence using the offset. For example, the offset may be 1. Note that the offset may be any appropriate number.

[0066] In other embodiments, the redundant version for the PUSCH transmission occasion associated with the second TRP is (mod(mod(n,4)+rv within the RV sequence applied for the first TRP s,4)+1)th value, where each redundant version rv s The additional shift operation for is set by the upper layer parameter sequenceOffsetforRV-PUSCH, and n is counted considering only the PUSCH transmission occasions associated with the second TRP. When set to have the upper layer parameter RVRestrictions-secondTRP, if there is only one PUSCH transmission occasion associated with the second TRP, the UE should always transmit RV 0 .

[0067] Figure 4 shows a signaling diagram illustrating process 400 between devices according to some exemplary embodiments of the present disclosure. For illustrative purposes only, process 400 will be described with reference to Figure 2B. Process 400 may involve terminal device 210-1, TRP 230-1, and TRP 230-2. It should be noted that process 400 is merely an example and not a limitation.

[0068] Network device 220 transmits RRC configuration to terminal device 210-1 (4005). The RRC configuration includes the number of repetitions for the PUSCH transmission occasion associated with the first SRS indicator (SRI) and the number of repetitions for the PUSCH transmission occasion associated with the second SRI. The PUSCH transmission occasion associated with the first SRI may be used for TRP 230-1, and the PUSCH transmission occasion associated with the second SRI may be used for TRP 230-2. As an example only, if the number of repetitions indicates 4, it means that the total transmission repetitions for TRP 230-1 and TRP 230-2 are 4.

[0069] If the configured permission setting is set such that startingFromTRP2 is set to "off", the first transmission of the transport block may start only in the first transmission occasion of the K repetitions associated with the first TRP if the configured RV sequence is {0, 2, 3, 1}. Otherwise, if the configured RV sequence is {0, 2, 3, 1}, in addition to the first transmission occasion of the K repetitions associated with the first TRP 230-1, the first transmission of the transport block may start in (1) the first transmission occasion of the K repetitions associated with the second TRP, and (2) any transmission occasion of the K repetitions where RV = 0 and associated with the second TRP if the configured RV sequence is {0, 2, 3, 1}. When the first transmission of the transport block starts in a transmission occasion associated with the first TRP, the UE does not transmit the PUSCH in the transmission occasion associated with the first TRP. In other embodiments, if the configured permission setting is set such that startingFromTRP2 is set to "on", the first transmission of the transport block may start in (1) the first transmission occasion of the K repetitions if the configured RV sequence is {0, 2, 3, 1}, and (2) any transmission occasion of the K repetitions associated with RV = 0 if the configured RV sequence is {0, 2, 3, 1}. In other embodiments, if the configured permission setting is set such that startingFromTRP2 is set to "on", the first transmission of the transport block may start only in any transmission occasion of the K repetitions before the transmission occasion associated with RV = 0 if the configured RV sequence is {0, 2, 3, 1}.

[0070] The RRC configuration indicates a set of configured permission parameters. The set of configured permission parameters can indicate which slots are permitted. The RRC configuration also includes an indication to enable the first transmission associated with the second SRI.

[0071] In the CG mode, more sequences, such as {RV 0 ,RV 3 ,RV 0 ,RV 3 ,} and {RV 0 ,RV 0 ,RV 0 ,RV 0 ,} can be set. Therefore, when different RV sequences are set, different limitations may also be applied to the RV sequence offset. For example, if the RV sequence for TRP 230-1 is {RV 0 ,RV 3 ,RV 0 ,RV 3}, the offset for TRP 230-2 may be 0 or 1. Additionally, for the CG PUSCH repetition, the first transmission may also start from the first transmission occasion and / or any transmission occasion associated with RV = 0 for the second TRP. Regarding the CG PUSCH, the term "PUSCH transmission" as used herein may refer to the nominal transmission or the actual transmission.

[0072] Tables 9 to 12 show examples of CG resources for TRP 230-1 and TRP 230-2. As shown in Table 9, the RV sequence for TRP 230-1 is {RV 0 ,RV 2 ,RV 3 ,RV 1}, and the RV sequence for TRP 230-2 is a cyclic shift of the RV sequence for TRP 230-1. As shown in Table 10, the RV sequence for TRP 230-1 is {RV 0 ,RV 2 ,RV 3 ,RV 1}, and the RV sequence for TRP 230-2 is a cyclic shift of the RV sequence for TRP 230-1. As shown in Table 11, the RV sequence for TRP 230-1 is {RV 0 ,RV 3 ,RV 0 ,RV3}, and the RV sequence of TRP 230-2 is a cyclic shift of the RV sequence for TRP 230-1. As shown in Table 12, the RV sequence for TRP 230-1 is {RV 0 , RV 3 , RV 0 , RV 3}, and the RV sequence of TRP 230-2 is a cyclic shift of the RV sequence for TRP 230-1. TIFF0007691004000011.tif224154 TIFF0007691004000012.tif236162 TIFF0007691004000013.tif236162 TIFF0007691004000014.tif236162

[0073] When the PUSCH transmission opportunity satisfies the conditions, the terminal device 210-1 transmits the first transmission to the network device 220 (4010). In some embodiments, a PUSCH transmission opportunity having a second SRI is associated with RV 0 , and the terminal device 210-1 may transmit the first transmission to TRP 230-2. Alternatively, when the PUSCH transmission opportunity having a second SRI is the first transmission opportunity of the retransmission, the terminal device 210-1 may transmit the first transmission to TRP 230-2. In other embodiments, when the PUSCH transmission opportunity having a first SRI is the first transmission opportunity of the retransmission, the terminal device 210-1 may transmit the first transmission to TRP 230-1.

[0074] In some embodiments, when the terminal device 210-1 starts the first transmission in the n-th transmission occasion associated with the TRP 230-2, the terminal device 210-1 may end the transmission after n+K transmission occasions. n is counted considering both the first TRP and the second TRP, and n = 0, 1, 2,..., K-1. The number K represents the number of repetitions.

[0075] In other embodiments, when the terminal device 210-1 starts the first transmission in the n-th transmission occasion, the terminal device 210-1 may end the transmission after K repetitions. n is counted considering both the first TRP and the second TRP, and n = 0, 1, 2,..., K-1. The number K represents the number of repetitions.

[0076] Alternatively, when the terminal device 210-1 starts the first transmission in the n-th transmission occasion, the terminal device 210-1 may end the transmission after K-n+1 repetitions. n is counted considering both the first TRP and the second TRP, and n = 0, 1, 2,..., K-1. The number K represents the number of repetitions.

[0077] In some embodiments, for the CG PUSCH repetition, the first transmission may also start from any transmission occasion associated with RV = 0 for the first transmission occasion and / or the second TRP. In some embodiments, the number of repetitions may be greater than 8. Alternatively, for the non-ideal backhaul and frequency range 2 (FR2), when the first transmission starts in the PUSCH occasion associated with the TRP 230-2, the PUSCH transmission to the TRP 230-1 may be omitted. In this case, the terminal device 210-1 may skip the PUSCH transmission to the TRP 230-1. Thus, the delay can be reduced.

[0078] In some embodiments, for all PDSCH transmission occasions associated with the first TCI state, the applied redundancy version is derived according to Table 13 (below), where n is counted considering only the PDSCH transmission occasions associated with the first TCI state. For the PDSCH transmission occasions associated with the second TCI state, the redundancy version No. is derived according to the (mod(mod(n,4)+rvs,4)+1)-th value in the RV sequence applied for the 1 TCI state, where the additional shift operation for each redundancy version rvs is set by the upper layer parameter sequenceOffsetforRV, and n is counted considering only the PDSCH transmission occasions associated with the second TCI state.

[0079] Similarly, in some embodiments, for all PUSCH transmission occasions associated with the first SRI 130-1, the applied redundancy version is derived according to Table 2 (below), where n is counted considering only the PUSCH transmission occasions associated with the first SRI. For the PUSCH transmission occasions associated with the second SRI state, the redundancy version is the (mod(mod(n,4)+rv s , 4)+1)-th value in the RV sequence applied for the first SRI state in Table 2, where the additional shift operation for each redundancy version rv s is set by the upper layer parameter sequenceOffsetforRV, and n is counted considering only the PUSCH transmission occasions associated with the second SRI.

[0080] Alternatively, for all PDSCH transmission occasions associated with the first TCI 130-1, the applicable redundancy version is derived according to Table 13 (shown below), where n is counted considering only the PDSCH transmission occasions associated with the first TCI. The redundancy version for PDSCH transmission associated with the second TCI state is derived according to Table 14 (shown below), where the additional shift operation for each redundancy version rv s is set by the upper layer parameter sequenceOffsetforRV, and n is counted considering only the PDSCH transmission occasions associated with the second TCI state. The terminal device 210-1 may also transmit a UE capability report to the network. The UE capability report may indicate that the terminal device 210-1 can support a cyclic shift operation for each redundancy version for PDSCH transmission. When the upper layer parameter SequenceOffsetforRV-v16x0 is set, the redundancy version for PDSCH transmission occasions associated with the second TCI state is based on the (mod(mod(n,4)+rv s ,4)+1)-th value within the RV sequence applied for the first TCI state. TIFF0007691004000015.tif82162 TIFF0007691004000016.tif82162

[0081] Similarly, for all PUSCH transmission occasions associated with the first SRI, the applicable redundancy version is derived according to Table 2, where n is counted considering only the PUSCH transmission occasions associated with the first SRI. The redundancy version for PUSCH transmission occasions associated with the second SRI is derived according to Table 1, where the additional shift operation for each redundancy version rv sThe additional shift operation for s is set by the upper layer parameter sequenceOffsetforRV, and n is counted considering only the PUSCH transmission occasions associated with the second SRI. The terminal device 210-1 may also send a UE capability report to the network. The UE capability report may indicate that the terminal device 210-1 can support the cyclic shift operation for each redundancy version for PUSCH transmission. When the upper layer parameter SequenceOffsetforRV-v16x0 is set, the redundancy version for the PUSCH transmission occasion associated with the second SRI is derived based on the (mod(mod(n,4)+rv

[0082] Also, there is no test case for the RV sequence introduced in Table 13, and the conventional test cases (e.g., Table 15 below) can be replaced as follows. Note that the test cases for PDSCH repetition may be replaced below.

[0083] The redundancy version coding sequence {0,2,3,1} may be updated to one of {0,2,3,1}, {0,2,1,3}, {0,1,3,2}, {0,3,1,2}. In particular, for PDSCH repetition, the redundancy version coding sequence {0,2,3,1} may be updated to one of the first TCI state {0,2,3,1}, the second TCI state {0,2,3,1}, the first TCI state {0,2,3,1}, the second TCI state {1,3,0,2}, the first TCI state {0,2,3,1}, the second TCI state {2,0,1,3}, the first TCI state {0,2,3,1}, the second TCI state {3,1,2,0}.

[0084] Specifically for PUSCH repetitions, the redundant version coding sequence {0, 2, 3, 1} may be updated to one of the first SRI {0, 2, 3, 1}, the second SRI {0, 2, 3, 1}, the first SRI {0, 2, 3, 1}, the second SRI {1, 3, 0, 2}, the first SRI {0, 2, 3, 1}, the second SRI {2, 0, 1, 3}, the first SRI {0, 2, 3, 1}, the second SRI {3, 1, 2, 0}. The terminal device 210-1 may perform uplink transmission based on the above RV sequence.

[0085] The performance requirements for PUSCH are determined by the maximum block error rate (BLER) for a given SNR. BLER is defined as the probability that PUSCH information is decoded incorrectly when it is transmitted. The performance requirements assume HARQ retransmission. Table 15 below shows the test parameters for testing PUSCH repetition type A. TIFF0007691004000017.tif211162

[0086] FIG. 6 is a flowchart of an exemplary method 600 according to an embodiment of the present disclosure. For illustrative purposes only, method 600 may be implemented in the terminal device 210-1 as shown in FIGS. 2A and 2B.

[0087] In block 610, the terminal device 210-1 receives a radio resource control (RRC) configuration from the network device 220. The RRC configuration includes the number of repetitions for a physical uplink shared channel (PUSCH) transmission occasion associated with a first sounding reference signal (SRS) resource indicator (SRI) and a PUSCH transmission occasion associated with a second SRI. The RRC configuration further includes an RV offset for a redundant version (RV) sequence associated with the first SRI. In some embodiments, the RRC configuration may include a first indication to enable a condition. Alternatively, the RRC configuration may further include a second indication to enable a shift of the first RV sequence.

[0088] In block 620, the terminal device 210-1 receives downlink control information (DCI) indicating the identity of the RV from the network device 220.

[0089] In block 630, the terminal device 210-1 determines whether a first RV sequence for a PUSCH transmission occasion associated with a second SRI, which is determined based on the number of repetitions, the identity, and the RV offset, satisfies the conditions for iterative transmission for the PUSCH transmission occasion associated with the second SRI.

[0090] In some embodiments, the condition indicates that the first RV sequence is not applicable according to a determination that one of the following is satisfied: the first RV sequence does not include RV0 at the first position of the first RV sequence; the first RV sequence does not include RV0 at the first and second positions of the first RV sequence; or the first RV sequence does not include either RV0 or RV3 at the first and second positions of the first RV sequence.

[0091] In some embodiments, the terminal device 210-1 may apply the condition if at least one of the following is satisfied: the number of repetitions associated with the second SRI is less than a predetermined number, e.g., less than 4; a negative acknowledgment implied in the DCI; a non-ideal backhaul between a first transmission point associated with the first SRI and a second transmission point associated with the second SRI; or a dynamic switch from a single transmission point to multiple transmission points. The predetermined number may be any suitable number.

[0092] In other embodiments, the terminal device 210-1 may determine the first RV sequence based on the number of repetitions, the identity, and a predetermined table. Alternatively, the terminal device 210-1 may determine the first RV sequence based on the number of repetitions, the identity, and an equation (shown in Equation 1 above).

[0093] In block 640, according to the determination that the first RV sequence meets the conditions, the terminal device 210-1 transmits uplink data to the network device 220 in the PUSCH transmission occasion associated with the second SRI without applying the first RV sequence. In some embodiments, if there is only one PUSCH transmission occasion associated with the second SRI, the terminal device 210-1 may transmit RV0 of the uplink data in the PUSCH transmission associated with the second SRI. Alternatively, the terminal device 210-1 may transmit RV0 of the uplink data in the PUSCH transmission associated with the second SRI.

[0094] FIG. 7 is a flowchart of an exemplary method 700 according to an embodiment of the present disclosure. For illustrative purposes only, the method 700 may be implemented in the terminal device 210-1 as shown in FIGS. 2A and 2B.

[0095] In block 710, the terminal device 210-1 receives a radio resource control (RRC) configuration from the network device 220. The RRC configuration includes the number of repetitions of the iterative transmission for the physical uplink shared channel (PUSCH) transmission occasion associated with the first sounding reference signal (SRS) resource indicator (SRI) and the PUSCH transmission occasion associated with the second SRI, a set of configured grant parameters, and an instruction to enable the first transmission associated with the second SRI.

[0096] In block 720, if the PUSCH transmission occasion meets the conditions, the terminal device 210-1 transmits the first transmission. The conditions may include one of the following: the PUSCH transmission occasion having the second SRI is associated with RV 0 , the PUSCH transmission occasion having the second SRI is the first transmission occasion of the iterative transmission, or the PUSCH transmission occasion having the first SRI is the first transmission occasion of the iterative transmission.

[0097] In another embodiment, if the first transmission is associated with the second SRI, the terminal device 210-1 may skip the PUSCH transmission associated with the first SRI.

[0098] FIG. 8 is a flowchart of an exemplary method 800 according to an embodiment of the present disclosure. For illustrative purposes only, method 800 may be implemented in the network device 220 as shown in FIGS. 2A and 2B.

[0099] In block 810, the network device 220 transmits radio resource control (RRC) configuration to the terminal device 210-1. The RRC configuration includes the number of repetitions for the physical uplink shared channel (PUSCH) transmission occasion associated with the first sounding reference signal (SRS) resource indicator (SRI) and the PUSCH transmission occasion associated with the second SRI. The RRC configuration further includes the redundancy version (RV) offset for the RV sequence associated with the first SRI and the redundancy version (RV) offset for the RV sequence associated with the first SRI. In some embodiments, the RRC configuration may include a first indication to enable a condition. Alternatively, the RRC configuration may further include a second indication to enable a shift of the first RV sequence.

[0100] In block 820, the network device 220 transmits downlink control information (DCI) indicating the identity of the RV to the terminal device 210-1.

[0101] In block 830, according to the determination that the first RV sequence determined based on the number of repetitions and the identity satisfies the condition for the repeated transmission of the PUSCH transmission occasion associated with the second SRI, the network device 220 receives uplink data from the terminal device 210-1 in the PUSCH transmission occasion associated with the second SRI without applying the first RV sequence.

[0102] In some embodiments, the condition indicates that the first RV sequence is not applied according to a determination that one of the following is satisfied: the first RV sequence does not include RV0 at the first position of the first RV sequence; the first RV sequence does not include RV0 at the first and second positions of the first RV sequence; or the first RV sequence does not include either RV0 or RV3 at the first and second positions of the first RV sequence.

[0103] In some embodiments, when there is only one PUSCH transmission occasion associated with the second SRI, the network device 220 may receive RV0 of uplink data in the PUSCH transmission occasion associated with the second SRI. In other embodiments, the network device 220 may receive uplink data in the PUSCH transmission associated with the second SRI based on a second RV sequence determined by shifting the first RV sequence.

[0104] FIG. 9 is a flowchart of an exemplary method 900 according to an embodiment of the present disclosure. For illustrative purposes only, method 900 may be implemented in the network device 220 as shown in FIGS. 2A and 2B.

[0105] In block 910, the network device 220 transmits a radio resource control (RRC) configuration to the terminal device 210-1. The RRC configuration includes the number of repetitions of the iterative transmission for the physical uplink shared channel (PUSCH) transmission occasion associated with the first sounding reference signal (SRS) resource indicator (SRI) and the PUSCH transmission occasion associated with the second SRI, a set of configured grant parameters, and an indication to enable the first transmission associated with the second SRI.

[0106] In block 720, when the PUSCH transmission occasion satisfies the condition, the network device 220 receives the first transmission. The condition is that the PUSCH transmission occasion having the second SRI is RV 0being associated therewith, the PUSCH transmission occasion having the second SRI being the first transmission occasion of the iterative transmission, or the PUSCH transmission occasion having the first SRI being the first transmission occasion of the iterative transmission, may be included.

[0107] In some embodiments, the terminal device includes a circuit, and the circuit receives, in the terminal device, from a network device, an RRC configuration including the number of repetitions for a physical uplink shared channel (PUSCH) transmission occasion associated with a first sounding reference signal (SRS) resource indicator (SRI) and a PUSCH transmission occasion associated with a second SRI, the RRC configuration further including a redundancy version (RV) offset for an RV sequence associated with the first SRI, receives from the network device downlink control information (DCI) indicating an identity of the RV, determines whether a first RV sequence for the PUSCH transmission occasion associated with the second SRI, determined based on the number of repetitions, the identity, and the RV offset, satisfies a condition for iterative transmission for the PUSCH transmission occasion associated with the second SRI, and is configured to transmit uplink data to the network device in the PUSCH transmission occasion associated with the second SRI without applying the first RV sequence according to a determination that the first RV sequence satisfies the condition.

[0108] In some embodiments, the condition is that the first RV sequence does not include an RV at a first position of the first RV sequence, the first RV sequence does not include an RV at first and second positions of the first RV sequence, or the first RV sequence does not include either RV0 or RV3 at first and second positions of the first RV sequence, and according to a determination that one of them is satisfied, it indicates that the first RV sequence is not applied. 0 being included, the first RV sequence does not include an RV at first and second positions of the first RV sequence 0 being included, or the first RV sequence does not include either RV0 or RV3 at first and second positions of the first RV sequence, and according to a determination that one of them is satisfied, it indicates that the first RV sequence is not applied.

[0109] In some embodiments, the RRC configuration further includes a first indication for enabling a condition.

[0110] In some embodiments, the terminal device includes a circuit, and the circuit is configured to transmit the uplink data in a PUSCH transmission associated with the second SRI by transmitting RV0 of the uplink data in the PUSCH transmission associated with the second SRI according to a determination that there is only one PUSCH transmission opportunity associated with the second SRI, without applying the first RV sequence.

[0111] In some embodiments, the RRC configuration further includes a second indication for enabling a shift of the first RV sequence.

[0112] In some embodiments, the terminal device includes a circuit, and the circuit is configured to transmit the uplink data in a PUSCH transmission associated with the second SRI by transmitting RV0 of the uplink data in the PUSCH transmission associated with the second SRI.

[0113] In some embodiments, the terminal device includes a circuit, and the circuit determines the first RV sequence based on the number of repetitions, the identity, and a predetermined table, or based on the number of repetitions, the identity, Equation X = (mod(mod(n,4)+rv s , 4)+1) th and is configured to determine the first RV sequence, where X represents the x-th value of the RV sequence applied to the first SRI, and the rv s represents an RV offset for the RV sequence associated with the first SRI, and n represents the n-th transmission associated with the second SRI.

[0114] In some embodiments, the terminal device comprises a circuit, and the circuit is configured to apply the condition according to a determination that at least one of the following is satisfied: the number of repetitions associated with the second SRI is less than 4; a negative response implied in the DCI; a non-ideal backhaul between a first transmission point associated with the first SRI and a second transmission point associated with the second SRI; or a dynamic switch from a single transmission point to multiple transmission points.

[0115] In some embodiments, the terminal device comprises a circuit, and the circuit is configured to receive, from a network device, in the terminal device, a radio resource control (RRC) configuration including a set of permitted parameters and an indication to activate a first transmission associated with the second SRI, for a physical uplink shared channel (PUSCH) transmission occasion associated with a first sounding reference signal (SRS) resource indicator (SRI) and a PUSCH transmission occasion associated with a second SRI, and to transmit the first transmission to the network device according to a determination that the PUSCH transmission occasion satisfies a condition.

[0116] In some embodiments, the condition indicates that the first RV sequence is not applied according to a determination that one of the following is satisfied: the first RV sequence does not include an RV at a first position of the first RV sequence; the first RV sequence does not include an RV at first and second positions of the first RV sequence; or the first RV sequence does not include RV0 or RV3 at first and second positions of the first RV sequence. 0 the first RV sequence does not include an RV at first and second positions of the first RV sequence; 0 or the first RV sequence does not include RV0 or RV3 at first and second positions of the first RV sequence.

[0117] In some embodiments, the terminal device comprises a circuit, and the circuit is configured to skip a PUSCH transmission associated with the first SRI according to a determination that the first transmission is associated with the second SRI.

[0118] In some embodiments, the network device includes a circuit, and the circuit transmits to the terminal device an RRC configuration including the number of repetitions for a physical uplink shared channel (PUSCH) transmission occasion associated with a first sounding reference signal (SRS) resource indicator (SRI) and a PUSCH transmission occasion associated with a second SRI, and further includes a redundancy version (RV) offset for the RV sequence associated with the first SRI and a redundancy version (RV) offset for the RV sequence associated with the first SRI. The network device transmits to the terminal device downlink control information (DCI) indicating the identity of the RV, and is configured to receive uplink data from the terminal device in the PUSCH transmission occasion associated with the second SRI without applying the first RV sequence according to a determination that the first RV sequence determined based on the number of repetitions and the identity satisfies the condition for iterative transmission for the PUSCH transmission occasion associated with the second SRI.

[0119] In some embodiments, the condition is that the first RV sequence does not include an RV at a first position of the first RV sequence, the first RV sequence does not include an RV at first and second positions of the first RV sequence, or the first RV sequence does not include either RV0 or RV3 at first and second positions of the first RV sequence. According to a determination that one of these is satisfied, it is indicated that the first RV sequence is not applied. 0 the first RV sequence does not include an RV at a first position of the first RV sequence, the first RV sequence does not include an RV at first and second positions of the first RV sequence, or the first RV sequence does not include either RV0 or RV3 at first and second positions of the first RV sequence. According to a determination that one of these is satisfied, it is indicated that the first RV sequence is not applied. 0 the first RV sequence does not include an RV at a first position of the first RV sequence, the first RV sequence does not include an RV at first and second positions of the first RV sequence, or the first RV sequence does not include either RV0 or RV3 at first and second positions of the first RV sequence. According to a determination that one of these is satisfied, it is indicated that the first RV sequence is not applied.

[0120] In some embodiments, the RRC configuration further includes a first indication for enabling the condition.

[0121] In some embodiments, the network device comprises a circuit, and the circuit is configured to receive the uplink data in the PUSCH transmission occasion associated with the second SRI without applying the first RV sequence by receiving the RV0 of the uplink data in the PUSCH transmission occasion associated with the second SRI according to the determination that there is only one PUSCH transmission occasion associated with the second SRI.

[0122] In some embodiments, the RRC configuration further includes a second indication for enabling a shift of the first RV sequence.

[0123] In some embodiments, the network device comprises a circuit, and the circuit is configured to receive the uplink data in the PUSCH transmission associated with the second SRI without applying the first RV sequence by receiving the uplink data in the PUSCH transmission associated with the second SRI based on a second RV sequence determined by shifting the first RV sequence.

[0124] In some embodiments, the network device comprises a circuit, and the circuit is configured to transmit, in the network device, to the terminal device, a radio resource control (RRC) configuration including a number of repetitions, a set of permitted parameters to be set, and an indication for enabling the first transmission associated with the second SRI, for the physical uplink shared channel (PUSCH) transmission occasion associated with the first sounding reference signal (SRS) resource indicator (SRI) and the PUSCH transmission occasion associated with the second SRI, and to receive, from the terminal device, the first transmission according to the determination that the PUSCH transmission occasion meets the condition.

[0125] In some embodiments, the condition is that the first RV sequence has RV at the first position of the first RV sequence 0not including, and the first RV sequence not including RV at the first and second positions of the first RV sequence 0 not including, or the first RV sequence including neither RV0 nor RV3 at the first and second positions of the first RV sequence, indicates that the first RV sequence is not applicable according to the determination that one of these is satisfied.

[0126] FIG. 10 is a schematic block diagram of an apparatus 1000 suitable for implementing an embodiment of the present disclosure. The apparatus 1000 can be considered as another exemplary embodiment of the network apparatus 220 or the terminal apparatus 210 shown in FIGS. 2A and 2B. Accordingly, the apparatus 1000 can be implemented in the terminal apparatus 210 or the network apparatus 220, or at least partially as thereof.

[0127] As shown, the apparatus 1000 includes a processor 1010, a memory 1020 coupled to the processor 1010, a suitable transmitter (TX) and receiver (RX) 1040 coupled to the processor 1010, and a communication interface coupled to the TX / RX 1040. The memory 1010 stores at least a part of the program 1030. The TX / RX 1040 is used for two-way communication. The TX / RX 1040 has at least one antenna to facilitate communication, although the access nodes referred to herein may actually have a plurality of antennas. The communication interface may represent any interface necessary for communication with other network elements, such as an X2 interface for two-way communication between eNBs, an S1 interface for communication between a mobility management entity (MME) / serving gateway (S-GW) and an eNB, a Un interface for communication between an eNB and a relay node (RN), or a Uu interface for communication between an eNB and a terminal apparatus.

[0128] Program 1030 is assumed to include program instructions that, when executed by the associated processor 1010 as described herein with reference to FIGS. 3-9, enable the apparatus 1000 to operate in accordance with the embodiments of the present disclosure. The embodiments of the present text may be implemented by computer software executable by the processor 1010 of the apparatus 1000, or by hardware, or by a combination of software and hardware. The processor 1010 may be configured to implement various embodiments of the present disclosure. Further, the combination of the processor 1010 and the memory 1020 may form processing means suitable for realizing various embodiments of the present disclosure.

[0129] The memory 1020 may be of any type suitable for a local technology network and may be implemented using any suitable data storage technology, such as, by way of non-limiting example, a non-transitory computer-readable storage medium, a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, a fixed memory, and a removable memory. Although only one memory 1020 is shown within the apparatus 1000, there may be several physically different memory modules within the apparatus 1000. The processor 1010 may be of any type suitable for a local technology network and may include, by way of non-limiting example, one or more of a general-purpose computer, a dedicated computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. The apparatus 1000 may have a specific application integrated circuit chip that is temporally dependent on a clock that synchronizes a plurality of processors, e.g., a main processor.

[0130] As a whole, various embodiments of the present disclosure may be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software that can be executed by a controller, a microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described using block diagrams, flowcharts, or other pictorial representations, the blocks, devices, systems, techniques, or methods described herein are, by way of non-limiting example, hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or a controller or other computing device, or any combination thereof.

[0131] 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 instructions included in program modules, that are executed within a device on a target physical processor or a virtual processor to perform the processes or methods described above with reference to FIGS. 2 to 10. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In various embodiments, the functions of the program modules may be combined or divided among the program modules as needed. The machine-executable instructions of the program modules may be executed within a local or distributed device. In a distributed device, the program modules may be located in both local and remote storage media.

[0132] The program code for executing the method of the present disclosure may be described in any combination of one or more programming languages. These program codes are provided to a processor or a controller of a general-purpose computer, a dedicated computer, or other programmable data processing devices, and when executed by the processor or the controller, the program codes implement the functions / operations specified in the flowchart and / or block diagram. The program code may be executed entirely on the machine, partially on the machine, as an independent software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0133] The above program code may be implemented on a machine-readable medium, and the machine-readable medium may be any tangible medium that can be used by or include or store a program related to an instruction execution system, device, or apparatus. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. The machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing media. More specific examples of the machine-readable storage medium may include an electrical connection having one or more wires, a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0134] Although the operations have been described in a particular order, it should be understood that in order to obtain the desired results, these operations are not necessarily required to be executed in the particular order shown or in a sequential order, or to execute all of the operations described. In some cases, multitasking or parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, 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 a particular embodiment. Some features described in the context of individual embodiments may be combined and implemented in a single embodiment. Conversely, various features described in the context of a single embodiment may be implemented separately in multiple embodiments or in any suitable sub-combination.

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

Claims

1. Means for receiving, from a network device, configuration information including, within a Radio Resource Control (RRC) message, the number of repetitions K for Physical Uplink Shared Channel (PUSCH) repetitions corresponding to transmission occasions associated with a first sounding reference signal (SRS) resource set and a second SRS resource set, an indication, wherein the transmission occasions include a first transmission occasion among the number of repetitions K and a last transmission occasion among the number of repetitions K, the first transmission occasion among the number of repetitions K is associated with the first SRS resource set, the indication set to “off” indicates that the first transmission of a transport block may start only at the first transmission occasion among the number of repetitions K, means for transmitting, based on the indication, the first transmission of the transport block to the network device, a terminal device comprising the above.

2. The indication set to “on” indicates that, when the RV sequence configured for the terminal device is {0, 2, 3, 1}, the first transmission of the transport block may start at a first transmission occasion associated with a value of RV = 0 corresponding to the second SRS resource set, The terminal device according to Claim 1.

3. Means further configured to have a parameter indicating an RV sequence The terminal device according to Claim 1 or 2, further comprising the above.

4. Means for transmitting, to a terminal device, configuration information including, within a Radio Resource Control (RRC) message, the number of repetitions K for Physical Uplink Shared Channel (PUSCH) repetitions corresponding to transmission occasions associated with a first sounding reference signal (SRS) resource set and a second SRS resource set, an indication, wherein the transmission occasions include a first transmission occasion among the number of repetitions K and a last transmission occasion among the number of repetitions K, the first transmission occasion among the number of repetitions K is associated with the first SRS resource set, the indication set to “off” indicates that the first transmission of a transport block may start only at the first transmission occasion among the number of repetitions K, ​ ​ Means for receiving, from the terminal device, the first transmission of the transport block based on the indication; A network device including the same. According to claim 5, when the RV sequence set for the terminal device is {0, 2, 3, 1}, the indication set to "on" indicates that the first transmission of the transport block may start in the first transmission occasion associated with the value of RV = 0 corresponding to the second SRS resource set. The network device according to claim 4. According to claim 6 Means for setting a parameter indicating an RV sequence The network device according to claim 4 or 5, further including the same. According to claim 7 A communication method executed by a terminal device, comprising: Receiving, from a network device, in a radio resource control (RRC) message, The number of repetitions K for physical uplink shared channel (PUSCH) repetitions corresponding to transmission occasions associated with a first sounding reference signal (SRS) resource set and a second SRS resource set, An indication, And setting information including the same, The transmission occasion includes a first transmission occasion among the number of repetitions K and a last transmission occasion among the number of repetitions K, The first transmission occasion among the number of repetitions K is associated with the first SRS resource set, The indication set to "off" indicates that the first transmission of the transport block may start only in the first transmission occasion among the number of repetitions K, Based on the indication, transmitting the first transmission of the transport block to the network device; A communication method including the same. According to claim 8, when the RV sequence set for the terminal device is {0, 2, 3, 1}, the indication set to "on" indicates that the first transmission of the transport block may start in the first transmission occasion associated with the value of RV = 0 corresponding to the second SRS resource set. The method according to claim 7. According to claim 9 Further including being set to have a parameter indicating an RV sequence The method according to claim 7 or 8, further including the same.

Images