Conditional activation of radio resources for transport block repetition

Abstract

A user equipment (UE) is configured to: receive configuration information including allocation information for a downlink duplicate packet having a configuration number of repetitions and a condition resource associated with the downlink duplicate packet; determining whether the conditional resource associated with the downlink duplicate packet is to be activated; and decoding a transport block from a physical downlink shared channel (PDSCH), the physical downlink shared channel (PDSCH) being received on a plurality of resources from at least one of the downlink repetition packet and the conditional resource associated with the downlink repetition packet.

Description

Technical Field

[0001] The present patent application relates generally to wireless communications, and in particular to conditional activation of radio resources for transport block repetition. Background Art

[0002] Fifth generation (5G) New Radio (NR) networks may support transport block repetitions for uplink and / or downlink communications. Under normal circumstances, insufficient repetition issues may occur when the transmitting device is unable to perform a configured number of transport block repetitions within the radio resources allocated by the network. For example, in the uplink, due to delayed packet arrivals caused by jitter, the user equipment (UE) may miss some or all of the Physical Uplink Shared Channel (PUSCH) opportunities intended for transport block repetitions. Similarly, in the downlink, due to delayed packet arrivals caused by jitter, the base station may miss some or all of the Physical Downlink Control Channel (PDSCH) opportunities intended for transport block repetitions. It has been identified that a mechanism needs to be configured to address insufficient transport block repetitions. Summary of the invention

[0003] Some exemplary embodiments relate to a processor of a user equipment (UE) configured to perform the following operations: receiving configuration information including allocation information for a downlink repetition packet having a configured number of repetitions and a conditional resource associated with the downlink repetition packet; determining whether the conditional resource associated with the downlink repetition packet is to be activated; and decoding a transport block from a physical downlink shared channel (PDSCH) received on a plurality of resources from at least one of the downlink repetition packet and the conditional resource associated with the downlink repetition packet.

[0004] Other exemplary embodiments relate to a processor of a base station, the processor being configured to perform operations including: sending configuration information to a user equipment (UE), the configuration information including allocation information for a downlink repetition packet having a configured number of repetitions and a conditional resource associated with the downlink repetition packet; determining whether the conditional resource associated with the downlink repetition packet is to be activated; and sending a physical downlink shared channel (PDSCH) to the UE on a plurality of resources from at least one of the downlink repetition packet and the conditional resource associated with the downlink repetition packet, the PDSCH including a transport block repetition.

[0005] A further exemplary embodiment relates to a processor of a user equipment (UE) configured to perform the following operations: receiving configuration information including allocation information for an uplink repetition packet having a configured number of repetitions and a conditional resource associated with the uplink repetition packet; determining whether the conditional resource associated with the downlink repetition packet is to be activated; and sending a physical uplink shared channel (PUSCH) to the base station on a plurality of resources from at least one of the uplink repetition packet and the conditional resource associated with the downlink repetition packet, the PUSCH including a transport block repetition.

[0006] Additional exemplary embodiments include a processor of a base station configured to perform operations including: sending configuration information to a user equipment (UE), the configuration information including allocation information for an uplink repetition packet having a configured number of repetitions and a conditional resource associated with the uplink repetition packet; determining whether the conditional resource associated with the downlink repetition packet is to be activated; and receiving a physical uplink shared channel (PUSCH) from the UE on a plurality of resources from at least one of the uplink repetition packet and the conditional resource associated with the uplink repetition packet, the PUSCH including a transport block repetition. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 Exemplary network arrangements are shown according to various exemplary embodiments.

[0008] Figure 2 An exemplary user equipment (UE) is shown in accordance with various exemplary embodiments.

[0009] Figure 3 An exemplary base station according to various exemplary embodiments is shown.

[0010] Figure 4a Exemplary repeating packets are shown according to various exemplary embodiments.

[0011] Figure 4b Example scenarios in which under-replication occurs are shown according to various exemplary embodiments.

[0012] Figure 5 Exemplary repeating packets and associated conditional resources are shown according to various exemplary embodiments.

[0013] Figure 6 Several examples of one or more activated conditional resources are shown according to various exemplary embodiments.

[0014] Figure 7Methods for downlink conditional resource activation for transport block repetition according to various exemplary embodiments are shown.

[0015] Figure 8 Methods for downlink conditional resource activation for transport block repetition according to various exemplary embodiments are shown.

[0016] Fig. 9 Methods for uplink conditional resource activation for transport block repetition according to various exemplary embodiments are shown.

[0017] Fig.10 Methods for uplink conditional resource activation for transport block repetition according to various exemplary embodiments are shown.

[0018] Fig.11a An example of a single semi-persistent schedule (SPS) opportunity including a repetitive packet and a conditional packet is shown according to various exemplary embodiments.

[0019] FIG. 11 b shows an example of a single Configuration Grant (CG) opportunity including a repetition packet and a conditional packet according to various exemplary embodiments.

[0020] Fig.12 An example Abstract Syntax Notation One (ASN.1) for an SPS-Config IE including the condPdschAggregationFactor information element (IE) introduced herein is shown.

[0021] Fig.13 An example ASN.1 of a ConfiguredGrantConfig IE including the condRep IE introduced herein is shown.

[0022] Fig.14 An example of an exemplary medium access control (MAC) control element (CE) for conditional activation of resources for transport block repetition is shown in accordance with various exemplary embodiments. DETAILED DESCRIPTION

[0023] The exemplary embodiments may be further understood with reference to the following description and associated drawings, wherein like elements are provided with like reference numerals. The exemplary embodiments relate to conditional activation of radio resources for transport block repetition. As will be described in more detail below, insufficient repetition may occur in the event that a configured number of transport block repetitions cannot be performed within the corresponding network allocated radio resources. The exemplary embodiments introduce conditional activation of radio resources to ensure that a configured number of transport block repetitions are performed.

[0024] The exemplary embodiments are described with respect to user equipment (UE). However, reference to UE is provided for illustrative purposes only. The exemplary embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software and / or firmware for exchanging information and data with the network. Therefore, UE as described herein is used to represent any appropriate type of electronic component.

[0025] Exemplary embodiments are also described with reference to fifth generation (5G) new radio (NR) networks that support extended reality (XR). Those skilled in the art will understand that XR is an umbrella term for different types of reality, and may generally refer to real and virtual combined environments and associated human-computer interactions generated by computer technology and wearable devices. To provide some examples, the term XR may cover augmented reality (AR), mixed reality (MR), and virtual reality (VR). However, any reference to XR specific to a particular business use case or type is provided for illustrative purposes only. The exemplary embodiments are applicable to any currently implemented transmission block repetition mechanism, future specific implementations of the transmission block repetition mechanism, or independent of other transmission block repetition mechanisms.

[0026] During operation, XR services may utilize multiple data streams in the uplink and / or downlink. For example, in the downlink, there may be a video stream, an audio stream, and / or a data stream. In the uplink, there may be a control stream and / or a posture stream. From a physical channel perspective, there may be different control channels and shared channels for each stream, or multiple streams may share one control channel and / or shared channel. In some configurations, each stream may have different quality of service (QoS) requirements (e.g., block error rate (BLER) requirements, latency requirements, etc.).

[0027] For XR services, data payloads are typically periodic. For example, the video frame rate may be 60 frames per second, 90 frames per second, or 120 frames per second. The network may obtain auxiliary information about the characteristics of the XR service and utilize the auxiliary information to perform resource allocation for the XR service. Due to the periodic nature of the XR service, the network may use semi-persistent scheduling (SPS) and / or configuration grant (CG) methods for resource allocation.

[0028] To increase reliability (e.g., packet success, etc.), transport block repetition may be utilized in the uplink and / or downlink. For example, a transport block may be autonomously repeated (K) times during an SPS or CG opportunity. Typically, more repetitions are required for higher reliability.

[0029] Under-repetition issues may arise when a transmitting device (e.g., UE, gNB, etc.) is unable to achieve a configured number (K) of transport block repetitions due to any of a number of different reasons, including, but not limited to, delayed packet arrivals caused by jitter. For example, in the downlink, delayed packet arrivals at the physical layer (PHY) of the gNB due to jitter may cause the gNB to miss some or all of the physical downlink shared channel (PDSCH) opportunities configured for (K) transport block repetitions. Thus, under normal circumstances, the configured number (e.g., K) of repetitions are not achieved, which may reduce the reliability of the service. Similarly, in the uplink, delayed packet arrivals at the PHY layer of the UE due to jitter may cause the UE to miss some or all of the physical uplink shared channel (PUSCH) opportunities configured for (K) transport block repetitions. Thus, under normal circumstances, the configured number (e.g., K) of repetitions are not achieved, which may reduce the reliability of the service.

[0030] An exemplary embodiment is described with respect to a repetition packet. Throughout this specification, a repetition packet represents a set of time and frequency radio resources (e.g., resource blocks, resource elements, subcarriers, subframes, etc.) configured to carry a configured number of times (K times) of transmission block repetitions. In the uplink, a repetition packet may be mapped to a PUSCH opportunity. In addition, depending on the way the network allocates resources, the PUSCH opportunity may also be characterized as a CG opportunity. Therefore, in some examples, the terms repetition packet, PUSCH opportunity, and / or CG opportunity may be used interchangeably to refer to the same radio resource. In the downlink, a repetition packet may be mapped to a PDSCH opportunity. In addition, depending on the way the network allocates resources, the PDSCH opportunity may also be characterized as an SPS opportunity. Therefore, in some examples, the terms repetition packet, PDSCH opportunity, and / or SPS opportunity may be used interchangeably to refer to the same radio resource.

[0031] In order to distinguish between different resources of a repetition packet, the exemplary embodiment characterizes the repetition packet as comprising a set of (K) radio resources. For example, if the configured number of transport block repetitions is set to a value of four, the resources of the repetition packet may be indexed as resources 0-3. However, reference to the term repetition packet is provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0032] The exemplary embodiments introduce conditional activation of radio resources for transport block repetition. This may include performing transport block repetition on a repetition packet and associated conditional resources. The exemplary embodiments described herein may allow the network to avoid scenarios where the transmitting device (e.g., UE, gNB, etc.) cannot reach the configured number of transport block repetitions (e.g., K times). According to some aspects, the exemplary embodiments introduce techniques for activating conditional resources associated with repetition packets. On the other hand, the exemplary embodiments introduce techniques for determining which conditional resources will be activated. In addition, the exemplary embodiments introduce various messages and signaling mechanisms to implement the conditional activation of radio resources for transport block repetition introduced herein. The exemplary embodiments may be used independently of each other, in combination with currently implemented transport block repetition mechanisms, future specific implementations of transport block repetition mechanisms, or independently of other transport block repetition mechanisms.

[0033] Figure 1 An exemplary network arrangement 100 according to various exemplary embodiments is shown. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 may be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a tablet phone, an embedded device, a wearable device (e.g., a head mounted display (HMD), AR glasses, etc.), an Internet of Things (IoT) device, etc. It should also be understood that an actual network arrangement may include any number of UEs used by any number of users. Therefore, the example of a single UE 110 is provided for illustrative purposes only.

[0034] UE 110 may be configured to communicate with one or more networks. In the example of network configuration 100, the network with which UE 110 may wirelessly communicate is a 5G NR radio access network (RAN) 120. However, UE 110 may also communicate with other types of networks (e.g., 5G cloud RAN, next generation RAN (NG-RAN), long term evolution (LTE) RAN, traditional cellular network, wireless local area network (WLAN), etc.), and UE 110 may also communicate with the network via a wired connection. Referring to the exemplary embodiment, UE 110 may establish a connection with at least 5G NR RAN 120. Therefore, UE 110 may have a 5G NR chipset to communicate with NRRAN 120.

[0035] The 5G NR RAN 120 may be part of a cellular network that may be deployed by a network operator, such as Verizon, AT&T, T-Mobile, etc. The 5G NR RAN 120 may include, for example, cells or base stations (Node B, eNodeB, HeNB, eNB, gNB, gNodeB, macro cell, micro cell, small cell, femto cell, etc.) configured to transmit and receive traffic from UEs equipped with appropriate cellular chipsets.

[0036] In the network arrangement 100, the UE 110 may be connected to the 5G NR-RAN 120 via the gNB 120A. Those skilled in the art will appreciate that any association procedure may be performed for connecting the UE 110 to the 5G NR-RAN 120. For example, as described above, the 5G NR-RAN 120 may be associated with a particular cellular provider at which the UE 110 and / or its user has protocol and credential information (e.g., stored on a SIM card). Upon detecting the presence of the 5G NR-RAN 120, the UE 110 may send corresponding credential information to associate with the 5G NR-RAN 120. More specifically, the UE 110 may be associated with a particular base station (e.g., gNB 120A). However, as described above, reference to the 5G NR-RAN 120 is for illustrative purposes only, and any suitable type of RAN may be used.

[0037] The network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP multimedia subsystem (IMS) 150, and a network service backbone 160. The cellular core network 130 can be viewed as an interconnected collection of components that manage the operation and services of the cellular network. The cellular core network 130 also manages the services that flow between the cellular network and the Internet 140. The IMS 150 can generally be described as an architecture for delivering multimedia services to the UE 110 using the IP protocol. The IMS 150 can communicate with the cellular core network 130 and the Internet 140 to provide multimedia services to the UE 110. The network service backbone 160 communicates directly or indirectly with the Internet 140 and the cellular core network 130. The network service backbone 160 can generally be described as a collection of components (e.g., servers, network storage arrangements, etc.) that implement a set of services that can be used to extend the functionality of the UE 110 to communicate with various networks.

[0038] Figure 2 An exemplary UE 110 is shown according to various exemplary embodiments. The UE 110 sends Figure 1100. UE 110 may include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. Other components 230 may include, for example, an audio input device, an audio output device, a power supply, a data acquisition device, a port for electrically connecting UE 110 to other electronic devices, etc.

[0039] The processor 205 may be configured to execute a plurality of engines of the UE 110. For example, the engines may include a conditional resource activation engine 235. The conditional resource activation engine 235 may perform various operations related to utilizing conditional radio resources to ensure sufficient transport block repetitions. The operations may include, but are not limited to, receiving configuration information from a network, identifying empty resources within a repetition packet, activating conditional resources associated with the repetition packet, aggregating data received from the repetition packet and / or the conditional resources (e.g., downlink communications), and performing transport block repetitions on the repetition packet and / or the conditional resources (e.g., uplink communications).

[0040] The engine 235 referenced above is provided as an application (e.g., program) executed by the processor 205 for illustrative purposes only. The functionality associated with the engine 235 may also be represented as a separate combined component of the UE 110, or may be a modular component coupled to the UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit may include an input circuit system for receiving a signal and a processing circuit system for processing signals and other information. The engine may also be embodied as an application or multiple separate applications. In addition, in some UEs, the functionality described for the processor 205 is split between two or more processors (such as a baseband processor and an application processor). The exemplary embodiments may be implemented in any of these or other configurations of the UE.

[0041] The memory arrangement 210 may be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 may be a hardware component configured to display data to a user, and the I / O device 220 may be a hardware component that enables a user to enter input. The display device 215 and the I / O device 220 may be separate components or may be integrated together (such as a touch screen). The transceiver 225 may be a hardware component configured to establish a connection with the 5G NR-RAN 120 and / or any other suitable type of network. Thus, the transceiver 225 may operate on a variety of different frequencies or channels (e.g., a set of continuous frequencies).

[0042] Figure 3An exemplary base station 300 is shown in accordance with various exemplary embodiments. Base station 300 may represent any access node (e.g., gNB 120A, etc.) that UE 110 may use to establish a connection and manage network operations.

[0043] Base station 300 may include processor 305, memory arrangement 310, input / output (I / O) devices 315, transceiver 320, and other components 325. Other components 325 may include, for example, batteries, data acquisition devices, ports for electrically connecting base station 300 to other electronic devices, and the like.

[0044] The processor 305 may be configured to execute multiple engines of the base station 300. For example, the engine may include a conditional resource activation engine 330. The conditional resource activation engine 330 may perform various operations related to utilizing conditional radio resources to ensure sufficient transport block repetitions. The operations may include, but are not limited to, sending configuration information to one or more UEs, identifying empty resources within a repetition packet, activating conditional resources associated with repetitions, aggregating data received from repetition packets and / or conditional resources (e.g., uplink communications), and performing transport block repetitions on repetition packets and / or conditional resources (e.g., downlink communications).

[0045] The engine 330 described above as an application (e.g., a program) executed by the processor 305 is merely exemplary. The functionality associated with the engine 330 may also be represented as a separate combined component of the base station 300, or may be a modular component coupled to the base station 300, such as an integrated circuit with or without firmware. For example, the integrated circuit may include an input circuit system for receiving signals and a processing circuit system for processing signals and other information. In addition, in some base stations, the functionality described for the processor 305 is split between multiple processors (e.g., a baseband processor, an application processor, etc.). The exemplary embodiments may be implemented in any of these or other configurations of the base station.

[0046] The memory 310 may be a hardware component configured to store data related to operations performed by the base station 300. The I / O device 315 may be a hardware component or port that enables a user to interact with the base station 300. The transceiver 320 may be a hardware component configured to exchange data with the UE 110 and any other UE in the system 100. The transceiver 320 may operate on a variety of different frequencies or channels (e.g., a continuous set of frequencies). Therefore, the transceiver 320 may include one or more components (e.g., radio devices) to enable data exchange with various networks and UEs.

[0047] In 5G NR, a transport block may refer to data passed between the medium access control (MAC) and physical PHY layers. The transport block may then be processed at the PHY layer and mapped onto radio resources for transmission over the radio. In a downlink example, a transport block may be mapped to a PDSCH resource. In an uplink example, a transport block may be mapped to a PUSCH resource.

[0048] Figure 4a An exemplary repetition packet 400 according to various exemplary embodiments is shown. The repetition packet 400 represents a set of time and frequency radio resources (e.g., resource blocks, resource elements, subcarriers, subframes, etc.) configured to carry a configured number of (K) transport block repetitions. In this example, the transport block repetition is set to K=4. Each instance of a transport block is intended to be sent on a portion of the resources of the repetition packet. In this example, the repetition packet includes four resource sets indexed as 0-3. Resource 0 may include a first instance of a transport block, resource 1 may include a second instance of a transport block, resource 2 may include a third instance of a transport block, and resource 3 may include a fourth instance of a transport block. The resources of the repetition packet (e.g., resources 0-3) may be configured with the same HARQ ID, which enables a receiving entity (e.g., UE 110, gNB 120A, etc.) to appropriately aggregate these resources.

[0049] Figure 4b An example scenario in which under-repetition occurs according to various exemplary embodiments is shown. The example scenario is described with respect to sending duplicate packet 400 by gNB 120A to UE 110 in the downlink. Here, delayed packet arrival at gNB 120A due to jitter occurs after the corresponding PDSCH opportunity has begun and gNB 120A misses the first part of the corresponding PDSCH opportunity (e.g., resource 0). As a result, under-repetition may occur and gNB 120A may only send three transport blocks (e.g., resources 1-3) during the corresponding PDSCH opportunity.

[0050] According to some aspects, each repetition packet may be associated with a set of conditional resources. Similar to a repetition packet, a conditional resource may represent a set of time and frequency radio resources (e.g., resource blocks, resource elements, subcarriers, subframes, etc.) configured to carry a configured number of times (K times) of transport block repetitions. The network may pre-configure the conditional resources based on characteristic information related to the traffic flow intended to be sent on the repetition packet (e.g., expected jitter, etc.). The conditional resources may be allocated on the same serving cell as the repetition packet or on a different serving cell than the repetition packet. The repetition packet and the associated conditional resources may be configured with the same HARQ process ID to enable the receiving entity (e.g., UE 110, gNB 120A) to aggregate the data sent on the repetition packet and the conditional resources.

[0051] Figure 5 An exemplary repetition packet 400 and associated conditional resources 510 according to various exemplary embodiments are shown. Throughout this specification, in order to distinguish between different resources within a conditional resource set, the exemplary embodiment characterizes the conditional resource set as including (K) radio resource sets. For example, if the configured number of transport block repetitions is set to a value of four, the conditional resource set can be indexed as conditional resources 0-3. The number of conditional resources within the conditional resource set actually utilized can vary and depends on the number of transport block repetitions actually performed during the associated repetition packet. However, reference to the term conditional resource is provided for illustrative purposes only, and different entities may refer to similar concepts by different names.

[0052] In this example, conditional resource set 510 may include conditional resources indexed as 0-3. Conditional resource 0 may include a first instance of a transport block, conditional resource 1 may include a second instance of a transport block, resource condition 2 may include a third instance of a transport block, and resource condition 3 may include a fourth instance of a transport block. In some embodiments, all of the conditional resources may be used for transport block repetition. In other embodiments, only a subset of the conditional resources may be used for transport block repetition. In further embodiments, a conditional resource set may be associated with more than one repetition packet.

[0053] The conditional resources may be configured in an activated state or a deactivated state. When in a deactivated state, the UE 110 and the network may be aware of the configuration of the conditional resource set associated with the repetition package, but may not actually utilize any of the conditional resources for transport block repetition. When one or more conditional resources are in an activated state, transport block repetition may be performed on one or more conditional resources and one or more resources of the repetition package.

[0054] According to some aspects, when one or more resources of a repetition packet are perceived to be empty, at least a portion of the conditional resources may be activated. The subset of conditional resources to be activated may depend on which resource of the repetition packet is perceived to be empty. In some embodiments, in the uplink or downlink, UE 110 and gNB 120A independently determine whether one or more conditional resources are to be used for transport block repetition. Alternatively, in other embodiments, explicit signaling may be embedded in the repetition packet to indicate whether at least a subset of conditional resources should be activated. The explicit signaling may also indicate an allocation of conditional resources to be activated, which in some embodiments may override pre-configured associated conditional resources. hereinafter described in Figure 6 Additional details of exemplary embodiments of both types are provided following the description of FIG.

[0055] Figure 6Multiple examples of one or more activated conditional resources according to various exemplary embodiments are shown. In example 610, resource 0 of repetition packet 612 is empty. In a downlink scenario, gNB 120A may miss a portion of the corresponding PDSCH opportunity due to delayed packet arrival. Therefore, gNB 120A may perform only three transport block repetitions on repetition packet 612. UE 110 may monitor PDSCH on resource 0 of repetition packet 612, but not receive PDSCH thereon. However, UE 110 receives PDSCH on resources 1-3 of repetition packet 612. Since resource 0 of repetition packet 612 is empty, resource 0 of conditional resource set 614 may be activated. Therefore, in this example, UE 110 also receives PDSCH on resource 0 of conditional resource set 614. In an uplink scenario, UE 110 may miss a portion of the corresponding PUSCH opportunity due to delayed packet arrival. Therefore, UE 110 may perform only three transport block repetitions on repetition packet 612. gNB 120A may monitor PUSCH on resource 0 of repetition packet 612, but may not receive PUSCH thereon. However, gNB 120A may receive PUSCH on resources 1-3 of repetition packet 612. Since resource 0 of repetition packet 612 is empty, resource 0 of conditional resource set 614 may be activated. Therefore, in this example, gNB 120A may also receive PUSCH on resource 0 of conditional resource set 614.

[0056] In example 620, resources 0-1 of repetition packet 622 are empty. In a downlink scenario, gNB 120A may miss a portion of the corresponding PDSCH opportunity due to delayed packet arrival. Therefore, gNB 120A may perform only two transport block repetitions on repetition packet 622. UE 110 may monitor PDSCH on resources 0-1 of repetition packet 622, but not receive PDSCH thereon. However, UE 110 receives PDSCH on resources 2-3 of repetition packet 622. Since resources 0-1 of repetition packet 622 are empty, resources 0-1 of conditional resource set 624 may be activated. Therefore, in this example, UE 110 also receives PDSCH on resources 0-1 of conditional resource set 624. In an uplink scenario, UE 110 may miss a portion of the corresponding PUSCH opportunity due to delayed packet arrival. Therefore, UE 110 may perform only two transport block repetitions on repetition packet 622. gNB 120A may monitor PUSCH on resources 0-1 of repetition packet 622 but may not receive PUSCH thereon. However, gNB 120A may receive PUSCH on resources 2-3 of repetition packet 622. Since resources 0-1 of repetition packet 622 are empty, resources 0-1 of conditional resource set 624 may be activated. Therefore, in this example, gNB 120A may also receive PUSCH on resources 0-1 of conditional resource set 624.

[0057] In example 630, resources 0-2 of repetition packet 632 are empty. In a downlink scenario, gNB 120A may miss a portion of the corresponding PDSCH opportunity due to delayed packet arrival. Therefore, gNB 120A may perform only one transport block repetition on repetition packet 632. UE 110 may monitor PDSCH on resources 0-2 of repetition packet 632, but not receive PDSCH thereon. However, UE 110 receives PDSCH on resource 3 of repetition packet 632. Since resources 0-2 of repetition packet 632 are empty, resources 0-2 of conditional resource set 634 may be activated. Therefore, in this example, UE 110 also receives PDSCH on resources 0-2 of conditional resource set 634. In an uplink scenario, UE 110 may miss a portion of the corresponding PUSCH opportunity due to delayed packet arrival. Therefore, UE 110 may perform only one transport block repetition on repetition packet 632. gNB 120A may monitor PUSCH on resources 0-2 of repetition packet 632, but may not receive PUSCH thereon. However, gNB 120A may receive PUSCH on resource 3 of repetition packet 632. Since resources 0-2 of repetition packet 632 are empty, resources 0-2 of conditional resource set 634 may be activated. Therefore, in this example, gNB 120A may also receive PUSCH on resources 0-2 of conditional resource set 634.

[0058] In example 640, resources 0-3 of repetition packet 632 are empty. In a downlink scenario, gNB 120A may miss all of the corresponding PDSCH opportunities due to delayed packet arrival. Therefore, gNB 120A may not perform transport block repetition on repetition packet 642. UE 110 may monitor PDSCH on resources 0-3 of repetition packet 642, but not receive PDSCH thereon. Since resources 0-3 of repetition packet 642 are empty, resources 0-3 of conditional resource set 644 may be activated. Therefore, in this example, UE 110 receives PDSCH on resources 0-3 of conditional resource set 644. In an uplink scenario, UE 110 may miss all of the corresponding PUSCH opportunities due to delayed packet arrival. Therefore, UE 110 may not perform transport block repetition on repetition packet 642. gNB 120A may monitor PUSCH on resources 0-3 of repetition packet 642, but not receive PUSCH thereon. Since resources 0-3 of repetition packet 642 are empty, resources 0-3 of conditional resource set 644 may be activated. Therefore, in this example, gNB 120A receives PUSCH on resources 0-3 of conditional resource set 644.

[0059] Figure 7 A method 700 for downlink conditional resource activation for transport block repetition is shown according to various exemplary embodiments. Figure 2 Method 700 is described from the perspective of UE 110. Method 800, provided below following the description of method 700, provides an example of downlink conditional resource activation for transport block repetition from the perspective of a base station (e.g., gNB 120A).

[0060] Initially, consider a scenario where UE 110 is connected to gNB 120A of 5G NR RAN 120. gNB 120A is configured to perform transport block repetition in downlink, where the number of transport block repetitions is (K) and the repetition packets are arranged into (K) consecutive radio resource sets.

[0061] In 705, UE 110 receives one or more messages including configuration information for conditional activation of radio resources for downlink transport block repetition from gNB 120A. The configuration information may include, but is not limited to, allocation information of radio resources for at least one downlink repetition packet having (K times) repetitions and allocation information of conditional resources associated with the at least one downlink reception packet.

[0062] In one example, a PDSCH opportunity may be configured at UE 110 for receiving a downlink repetition packet using SPS (e.g., an SPS opportunity). Configuration information may directly or indirectly identify the time, frequency, and / or spatial position of a conditional resource set associated with a downlink repetition packet. In some embodiments, a single continuous PDSCH opportunity may include both a repetition packet and a conditional resource set. In other embodiments, a fixed offset or a dynamic offset may exist between a repetition packet and an associated conditional resource set. A repetition packet and its associated conditional resource set may be provided on the same serving cell or on different serving cells.

[0063] In 710, UE 110 monitors a PDSCH opportunity for receiving a downlink repetition packet from gNB 120A. For example, UE 110 may tune its transceiver 225 to gNB 120A during a scheduled PDSCH opportunity.

[0064] At 715, UE 110 processes one of the K resources from the downlink repetition packet. In other words, UE 110 monitors a portion of the PDSCH opportunity to determine whether the frequency resources of the PDSCH opportunity contain data (eg, one of the (K) transport blocks).

[0065] At 720, UE 110 determines whether one of the resources of the repetition packet contains data. If the resource does not contain data, method 700 continues to 725. At 725, UE 110 activates an associated conditional resource from the set of conditional resources. When in the activated state, UE 110 is configured to monitor at least one conditional resource. As will be described in more detail below, at least one activated conditional resource and zero or more resources from the repetition packet may be aggregated to decode the transport block.

[0066] In some embodiments, UE 110 may transmit an acknowledgment signal to gNB 120A indicating that at least one conditional resource has been activated by UE 110. In other embodiments, gNB 120A and UE 110 may not exchange any messages that explicitly identify that a conditional resource has been activated at UE 110. Instead, by performing method 700 on the UE 110 side and performing method 800 on the gNB 120A side, both UE 110 and gNB 120A may independently determine which repetition packet and / or conditional resource to use for transport block repetition.

[0067] Returning to 720, if the resource contains data, method 700 continues to 730. At 730, UE 110 receives data on the resource in the duplicate packet.

[0068] At 735, UE 110 determines whether K resources of the duplicate packet have been processed. If UE 110 has processed less than K resources of the duplicate packet (e.g., the PDSCH opportunity has not ended), method 700 returns to 715. If UE 110 has processed K resources of the duplicate packet, method 700 continues to 740.

[0069] At 740, UE 110 aggregates PDSCH on the repetition packet and / or the activated conditional resources to decode the transport block. For example, if each of the K resources of the repetition packet contains data, UE 110 may not activate any of the conditional resources. If at least one of the K resources of the repetition packet does not contain data, UE 110 may activate a corresponding at least one conditional resource in an associated set of conditional resources. If none of the K resources of the repetition packet contains data, UE 110 may activate an associated set of conditional resources.

[0070] Receiving the PDSCH of the associated conditional resource can be performed after the PDSCH opportunity for the repetition packet has ended. In other embodiments, the conditional resource set can overlap with the repetition packet part on time. However, these examples are provided only for illustrative purposes. Exemplary embodiments can utilize the conditional resources provided on any appropriate time, frequency and / or space resource.

[0071] Figure 8 A method 800 for downlink conditional resource activation for transport block repetition according to various exemplary embodiments is shown. The method 800 is described from the perspective of gNB 120A.

[0072] In 805, the gNB 120 sends one or more messages including configuration information for conditional activation of radio resources for downlink transport block repetition to the UE 110. The configuration information may include, but is not limited to, allocation information of radio resources for at least one downlink repetition packet having (K times) repetitions and allocation information of conditional resources associated with the at least one downlink reception packet. The configuration in 805 is the same as the configuration information in 705 of the above method 700.

[0073] At 810, gNB 120A processes one of the K resources for a downlink repetition packet. For example, as described above, gNB 120A may receive data from other network components (e.g., core network, edge server, etc.) to be delivered to UE 110. The data is provided from the MAC layer of gNB 120A to the PHY layer of gNB 120A, where it may be mapped to a PDSCH opportunity for transmission over the radio.

[0074] In 815, the gNB 120A determines whether the buffer corresponding to the downlink duplicate packet is empty (e.g., delayed packet arrival, no HARQ retransmission, etc.). In one embodiment, the buffer may be a logical channel (LCH) buffer, which is used to buffer data that is still in the radio link control (RLC) layer, e.g., data that has not yet been processed by the MAC. When the MAC has a transmit opportunity, the gNB 120A may check whether there is any data in the LCH buffer and determine how the transport block should be constructed for the transmit opportunity. However, the reference to the LCH buffer is provided for illustrative purposes only. Different entities may refer to similar concepts by different names. For example, the terms LCH buffer and RLC buffer may be used interchangeably to refer to the same type of buffer. In another embodiment, the buffer may be a HARQ buffer for buffering already constructed transport blocks. For example, if a HARQ retransmission is triggered, the gNB 120A may retrieve the transport block stored in the HARQ buffer and send the transport block again. However, the reference to the HARQ buffer is provided for illustrative purposes only. Different entities may refer to similar concepts by different names. In other embodiments, multiple buffers may be considered. Thus, reference to the term buffer in this example may refer to one of the multiple buffers corresponding to downlink repetition packets (e.g., an LCH buffer, a HARQ buffer, any other suitable buffer, etc.).

[0075] When the buffer is empty, gNB 120A does not have any data available to send to UE 110 during the resource period of the repeated packet. When the buffer contains data, the data may be mapped to the corresponding PDSCH resources.

[0076] If the buffer is empty, the method 800 continues to 820. At 820, the gNB 120A activates the associated conditional resource from the set of conditional resources. When in the activated state, the gNB 120A is configured to send data on at least one conditional resource. As will be described in more detail below, at least one activated conditional resource and zero or more resources from the repetition package may be used for transport block repetition.

[0077] In some embodiments, gNB 120A may transmit a signal to UE 110 in a repetition packet (or using any other suitable resource) indicating that at least one conditional resource has been activated. In other embodiments, gNB 120A and UE 110 may not exchange any messages that explicitly identify that a conditional resource has been activated. Instead, by performing method 700 on the UE 110 side and performing method 800 on the gNB 120A side, both UE 110 and gNB 120A independently determine which repetition packet and / or conditional resource to use for transport block repetition.

[0078] Returning to 815, if the buffer is not empty and contains sufficient data, method 800 continues to 825. At 825, gNB 120A sends the PDSCH (e.g., data, etc.) on the resources of the repetition packet.

[0079] At 830, gNB 120A determines whether K resources of the duplicate packet have been processed. If gNB 120A has processed less than K resources of the duplicate packet (e.g., the PDSCH opportunity has not ended), method 800 returns to 810. If gNB 120A has processed K resources of the duplicate packet, method 800 continues to 835.

[0080] At 835, gNB 120A performs transport block repetition on the repetition packet and / or the activated conditional resources. For example, if each of the K resources of the repetition packet contains data, gNB 120A may not activate any of the conditional resources. If at least one of the K resources of the repetition packet does not contain data, gNB 120A may activate a corresponding at least one conditional resource in an associated set of conditional resources. If none of the K resources of the repetition packet contains data, gNB 120A may activate an associated set of conditional resources.

[0081] The PDSCH of the conditional resource of sending association can be performed after the PDSCH opportunity for the repetition packet has ended. In other embodiments, the conditional resource set can overlap with the repetition packet part on time. However, these examples are provided only for illustrative purposes. Exemplary embodiments can utilize the conditional resources provided on any appropriate time, frequency and / or space resource.

[0082] Fig. 9 A method 900 for uplink conditional resource activation for transport block repetition is shown according to various exemplary embodiments. Figure 2 Method 900 is described from the perspective of UE 110. Method 1000, provided below following the description of method 900, will provide an example of uplink conditional resource activation for transport block repetition from the perspective of a base station (e.g., gNB 120A).

[0083] Initially, consider a scenario where UE 110 is connected to gNB 120A of 5G NR RAN 120. UE 110 is configured to perform transport block repetition in uplink, where the number of transport block repetitions is (K) and the repetition packets are arranged into (K) consecutive radio resource sets.

[0084] In 905, UE 110 receives one or more messages including configuration information for conditional activation of radio resources for uplink transport block repetition from gNB 120A. The configuration information may include, but is not limited to, allocation information of radio resources for at least one uplink repetition packet with (K) repetitions and allocation information of conditional resources associated with at least one uplink reception packet.

[0085] In one example, a PUSCH opportunity may be configured at UE 110 for sending an uplink repetition packet using a CG approach (e.g., a CG opportunity). The configuration information may directly or indirectly identify the time, frequency, and / or spatial position of a conditional resource set associated with an uplink repetition packet. In some embodiments, a single continuous PUSCH opportunity may include both a repetition packet and a conditional resource set. In other embodiments, there may be a fixed offset or a dynamic offset between a repetition packet and an associated conditional resource set. A repetition packet and its associated conditional resource set may be provided on the same serving cell or on different serving cells.

[0086] In 910, UE 110 processes one of the K resources for an uplink repetition packet. For example, as described above, UE 110 may receive data to be delivered to the network from other UE components and / or associated devices (e.g., applications running on UE 110, HMD, AR glasses, etc.). The data is provided from the MAC layer of UE 110 to the PHY layer of UE 110, where it may be mapped to a PUSCH opportunity for transmission over the radio.

[0087] In 915, UE 110 determines whether the buffer corresponding to the uplink duplication packet is empty (e.g., delayed packet arrival). In one embodiment, the buffer may be an LCH buffer, which is used to buffer data still in the RLC layer, e.g., data not yet processed by the MAC. When the MAC has a transmission opportunity, the UE 110 may check whether there is any data in the LCH buffer, and determine how the transmission block should be constructed for the transmission opportunity. However, the reference to the LCH buffer is provided for illustrative purposes only. Different entities may refer to similar concepts by different names. For example, the terms LCH buffer and RLC buffer may be used interchangeably to refer to the same type of buffer. In another embodiment, the buffer may be a HARQ buffer for buffering already constructed transmission blocks. For example, if HARQ retransmission is triggered, the UE 110 may retrieve the transmission block stored in the HARQ buffer and transmit the transmission block again. However, the reference to the HARQ buffer is provided for illustrative purposes only. Different entities may refer to similar concepts by different names. In another embodiment, multiple buffers may be considered. Thus, reference to the term buffer in this example may refer to one of a plurality of buffers corresponding to downlink repetition packets (eg, an LCH buffer, a HARQ buffer, any other suitable buffer, etc.).

[0088] When the buffer is empty, UE 110 does not have any data available to send to the network during the resources of the repetition packet.When the buffer contains data, the data may be mapped to the corresponding PUSCH resources of the PUSCH opportunities of the repetition packet.

[0089] If the buffer is empty, the method 900 continues to 920. At 920, the UE 110 activates the associated conditional resource from the set of conditional resources. When in the activated state, the UE 110 is configured to send data on at least one conditional resource. As will be described in more detail below, at least one activated conditional resource and zero or more resources from the repetition package may be used for transmission block repetition.

[0090] In some embodiments, UE 110 may transmit a signal to gNB 120A in a repetition packet (or using any other suitable resource) indicating that at least one conditional resource has been activated. In other embodiments, UE 110 and gNB 120A do not exchange any messages that explicitly identify that a conditional resource has been activated. Instead, by performing method 900 on the UE 110 side and method 1000 on the gNB 120A side, both UE 110 and gNB 120A may independently determine which repetition packet and / or conditional resource to use for transport block repetition.

[0091] Returning to 915, if the buffer contains sufficient data, the method 900 proceeds to 925. At 925, the UE 110 sends a PUSCH (eg, data, etc.) on the resources of the duplicate packet.

[0092] At 930, UE 110 determines whether K resources of the duplicate packet have been processed. If UE 110 has processed less than K resources of the duplicate packet (e.g., the PUSCH opportunity has not ended), method 900 returns to 910. If UE 110 has processed K resources of the duplicate packet, method 900 continues to 935.

[0093] At 935, UE 110 performs transport block repetition on the repetition packet and / or the activated conditional resources. For example, if each of the K resources of the repetition packet contains data, UE 110 may not activate any of the conditional resources. If at least one of the K resources of the repetition packet does not contain data, UE 110 may activate a corresponding at least one conditional resource from an associated set of conditional resources. If none of the K resources of the repetition packet contains data, UE 110 may activate an associated set of conditional resources.

[0094] The PUSCH of the associated conditional resources can be performed after the PUSCH opportunity for the repetition packet has ended. In other embodiments, the conditional resource set can overlap with the repetition packet part on time. However, these examples are provided only for illustrative purposes. Exemplary embodiments can utilize the conditional resources provided on any appropriate time, frequency and / or space resources.

[0095] Fig.10 A method 1000 for uplink conditional resource activation for transport block repetition according to various exemplary embodiments is shown. The method 1000 is described from the perspective of gNB 120A.

[0096] In 1005, gNB 120 sends one or more messages including configuration information for conditional activation of radio resources for uplink transport block repetition to UE 110. The configuration information may include, but is not limited to, allocation information of radio resources for at least one downlink repetition packet with (K times) repetition and allocation information of conditional resources associated with the at least one downlink reception packet. The configuration in 1005 is the same as the configuration information in 905 of the above method 900.

[0097] At 1010, gNB 120A monitors a PUSCH opportunity for receiving an uplink repetition packet from gNB 120A. At 1015, gNB 120A processes one of the K resources from the uplink repetition packet. In other words, gNB 120A monitors a portion of the PUSCH opportunity to determine whether the frequency resource of the PDSCH opportunity contains data (e.g., one of the (K) transport blocks).

[0098] At 1020, the gNB 120A determines whether one of the resources of the repetition packet contains data. If the resource does not contain data, the method 1000 continues to 1025. At 1025, the gNB 120A activates an associated conditional resource from the set of conditional resources. While in the activated state, the gNB 120A is configured to monitor at least one conditional resource. As will be described in more detail below, at least one activated conditional resource and zero or more resources from the repetition packet may be aggregated to decode the transport block.

[0099] In some embodiments, gNB 120A may transmit an acknowledgment signal to UE 110 indicating that at least one conditional resource has been activated by gNB 120A. In other embodiments, gNB 120A and UE 110 do not exchange any messages that explicitly identify that a conditional resource has been activated. Instead, by performing method 900 on the UE 110 side and performing method 1000 on the gNB 120A side, both UE 110 and gNB 120A may independently determine which repetition packet and / or conditional resource to use for transport block repetition.

[0100] Returning to 1020, if the resource contains data, method 1000 continues to 1030. At 1030, gNB 120A receives the data on the resource in the duplicate packet.

[0101] At 1035, gNB 120A determines whether K resources of the duplicate packet have been processed. If gNB 120A has processed less than K resources of the duplicate packet (e.g., the PUSCH opportunity has not ended), method 1000 returns to 1015. If gNB 120A has processed K resources of the duplicate packet, method 1000 continues to 1040.

[0102] At 1040, gNB 120A aggregates PUSCH on the repetition packet and / or the activated conditional resources to decode the transport block. For example, if each of the K resources of the repetition packet contains data, gNB 120A may not activate any of the conditional resources. If at least one of the K resources of the repetition packet does not contain data, gNB 120A may activate a corresponding at least one conditional resource in an associated set of conditional resources. If none of the K resources of the repetition packet contains data, gNB 120A may activate an associated set of conditional resources.

[0103] Receiving the PUSCH of the associated conditional resources can be performed after the PUSCH opportunity for the repeated packet has ended. In other embodiments, the conditional resource set can overlap with the repeated packet part on time. However, these examples are provided only for illustrative purposes. Exemplary embodiments can utilize the conditional resources provided on any appropriate time, frequency and / or space resources.

[0104] According to some aspects, a PDSCH opportunity or a PUSCH opportunity may include a repetition packet and a conditional packet (e.g., a conditional resource set). For example, a single SPS opportunity may include a repetition packet and a conditional packet. In another example, a single CG opportunity may include a repetition packet and a conditional packet.

[0105] Fig.11a An example of a single SPS opportunity including a repetition packet and a conditional packet according to various exemplary embodiments is shown. In this example, the first SPS opportunity 1110 includes a repetition packet 1112 and a conditional packet 1114. Here, it may be considered that the number of times (K times) of transmission block repetitions is set to four. Therefore, the repetition packet 1112 includes resources indexed as 0-3, and the conditional packet 1114 also includes resources indexed as 0-3. The HARQ process ID of each resource on the repetition packet 1112 and the conditional packet 1114 may be the same.

[0106] In this example, the SPS opportunity is configured to occur with a configured SPS periodicity. The second SPS opportunity 1120 includes a repetition packet 1122 and a conditional packet 1124. Therefore, the repetition packet 1122 includes resources indexed as 0-3, and the conditional packet 1124 also includes resources indexed as 0-3. The HARQ process ID of each resource on the repetition packet 1122 and the conditional packet 1124 can be the same. The third SPS opportunity 1130 includes a repetition packet 1132 and a conditional packet 1134. Therefore, the repetition packet 1132 includes resources indexed as 0-3, and the conditional packet 1134 also includes resources indexed as 0-3. The HARQ process ID of each resource on the repetition packet 1132 and the conditional packet 1134 can be the same.

[0107] During operation, if the repeated packets in the same SPS opportunity do not meet the configured number (K) of transport block repetitions, at least one resource of the conditional packet may be activated. In another example, at least one resource of the conditional packet within the SPS opportunity may be activated at UE 110 based on an explicit signal from the network.

[0108] Figure 11b shows an example of a single CG opportunity including a repetition packet and a conditional packet according to various exemplary embodiments. In this example, the first CG opportunity 1150 includes a repetition packet 1152 and a conditional packet 1154. Here, it is considered that the number of times the transport block is repeated (K times) is set to four. Therefore, the repetition packet 1152 includes resources indexed as 0-3, and the conditional packet 1154 also includes resources indexed as 0-3. The HARQ process ID of each resource on the repetition packet 1152 and the conditional packet 1154 can be the same.

[0109] In this example, the CG opportunity is configured to occur with CG periodicity. The second SPS opportunity 1160 includes a repetition packet 1162 and a conditional packet 1164. Therefore, the repetition packet 1162 includes resources indexed as 0-3, and the conditional packet 1164 also includes resources indexed as 0-3. The HARQ process ID of each resource on the repetition packet 1162 and the conditional packet 1164 can be the same. The third CG opportunity 1170 includes a repetition packet 1172 and a conditional packet 1174. Therefore, the repetition packet 1172 includes resources indexed as 0-3, and the conditional packet 1174 also includes resources indexed as 0-3. The HARQ process ID of each resource on the repetition packet 1172 and the conditional packet 1174 can be the same.

[0110] During operation, if the repeated packets in the same CG opportunity do not meet the configured number (K) of transmission block repetitions, at least one resource of the conditional packet may be activated. In another example, at least one resource of the conditional packet within the CG opportunity may be activated at UE 110 based on an explicit signal from the network.

[0111] According to some aspects, exemplary embodiments introduce an information element (IE) that may be provided in an SPS configuration IE (SPS-Config). This new IE may be called condPdschAggregationFactor and indicates the number of repetitions of a conditional packet (e.g., a repetition packet) that will follow the default PDSCH resource for each SPS opportunity. Fig.12 An example Abstract Syntax Notation One (ASN.1) of an SPS-Config IE including the condPdschAggregationFactor IE introduced herein is shown in FIG.

[0112] According to some aspects, an exemplary embodiment introduces an IE that can be provided in a CG configuration IE (ConfiguredGrantConfig). This new IE can be called condRep and indicates the number of repetitions of a conditional packet (e.g., a repeated packet) that will follow the default PUSCH resource for each CG opportunity. Fig.13 An example ASN.1 of a ConfiguredGrantConfig IE including the condRep IE introduced herein is shown in FIG.

[0113] As described above, the exemplary embodiment also introduces explicit signaling that can be used to activate conditional resources associated with the repetition packet. In some embodiments, downlink control information (DCI) can be used to activate conditional resources. In one example, the DCI can be addressed to the configured scheduling (CS)-radio network temporary identifier (RNTI) of UE 110. Those skilled in the art will appreciate that CS-RNTI is a unique UE identifier for SPS in the downlink and type 2CG in the uplink. Therefore, this existing mechanism for SPS and type 2CG activation can be used to activate conditional resources as configured scheduling resources. In another example, for the purpose of activating conditional resources for transport block repetition, DCI can be addressed to the new RNTI introduced herein.

[0114] In one embodiment, an exemplary DCI may be provided on a physical downlink control channel (PDCCH) after the first orthogonal frequency division multiplexing (OFDM) symbol of a repetition packet. In another embodiment, the DCI may be transmitted on the PDCCH before the first OFDM symbol of the repetition packet. In this example, upon receiving a DCI indicating one or more activated conditional resources on the PDCCH, the UE 110 may skip at least one resource of the repetition packet. This may enable the UE 110 to save energy instead of using energy to monitor an empty PDSCH.

[0115] In another embodiment, the DCI includes the HARQ process ID, and the UE 110 can determine whether the conditional resources are activated for repetition. That is, if (e.g., within a predefined time interval) the HARQ process ID is indicated as being the same as the most recent repetition packet, the UE 110 can assume that the conditional resources are activated to complete the required repetition.

[0116] The exemplary DCI described herein may include a purpose indicator field. The purpose indicator field indicates the purpose of activation of the conditional resource, which can be used for new transmissions (e.g., conventional SPS activation, conventional CG activation) or for transport block repetitions. UE 110 can determine the HARQ process of the activated conditional resource based on the indicator, and then UE 110 can automatically set the HARQ process of the conditional resource to the HARQ process of the original repeated packet. Otherwise, any other appropriate mechanism can be used to determine the HARQ process. In some embodiments, the purpose indicator field can be a one-bit flag, where a first value indicates that the DCI is used for conditional resource activation, and a second different value indicates that the DCI is used for normal operation.

[0117] In addition, the exemplary DCI described herein may also include a resource set as an activated field. If the purpose of the DCI is conditional resource activation for transport block repetition, the DCI may also indicate a subset of conditional resources to be activated. If this field is not present, the resources may be considered activated until another deactivation command is received from the gNB 120A.

[0118] The exemplary embodiment also introduces conditional resource activation based on MAC control element (CE). The network can also activate conditional resources associated with the repetition packet via explicit signaling based on MAC CE. The MAC CE can be transmitted in a MAC CE packet data unit (PDU) for one of the PDSCH resources within the target repetition packet or an independent PDSCH within the target repetition packet.

[0119] In some embodiments, if one of the PDSCH resources within the target repetition packet transmits an exemplary MAC CE, UE 110 may decode the repetition packet. Assuming that a MAC CE may be included in a repetition packet, the PHY should later provide a transport block to the MAC layer to identify the presence of a MAC CE.

[0120] Fig.14 An example of an exemplary MAC CE 1400 for conditional activation of resources for transport block repetition according to various exemplary embodiments is shown. The exemplary MAC CE includes a first field 1410 configured to include one or more IDs of a target repetition packet. The ID may be an ID of an SPS configuration or a CG configuration. The exemplary MAC CE includes a second field 1420 configured to include one or more IDs of conditional resources associated with the target repetition packet. The exemplary MAC CE 1400 may also include a third field 1430 configured to include an indication of the conditional resources to be activated. For example, a set or subset of conditional resources associated with the target repetition packet to be activated.

[0121] For the uplink case, when jitter occurs and UE 110 is unable to perform the configured number of repetitions within a repetition packet, UE 110 may transmit uplink control information (UCI) to the network. The UCI may be transmitted based on UCI multiplexing in the PUSCH resourced within the repetition packet. Alternatively, assuming the original repetition packet is a CG or transmitted on the PUCCH, the UCI may be transmitted on the CG-UCI.

[0122] In one example, the UCI may inform gNB 120A that jitter exists. In this example, upon receiving the UCI, gNB 120A may further determine whether the associated conditional resources should be activated for repetition. If so, explicit signaling (e.g., DCI, MAC CE, etc.) may be transmitted to gNB 120A to activate the conditional resources.

[0123] In another example, the UCI may notify gNB 120A that jitter is present and recommend that at least a portion of the associated conditional resources should be activated. In this example, UE 110 may recommend which pre-configured conditional resources may be activated. However, in some embodiments, gNB 120A may have the final decision on whether to permit UE 110 to use the conditional resources for uplink transmissions.

[0124] In another example, the UCI may inform gNB 120A of at least a portion of the associated conditional resources and which subset of the conditional resources are to be activated. In this example, UE 110 may autonomously activate the conditional resources without permission from gNB 120A.

[0125] As described above, one of the repetitions may be performed on the conditional resources. For each resource within the conditional resource set for sending repetitions, UE 110 may determine its repetition index. In some embodiments, the repetition index may be determined based on mod(Total_Resource, Required_Repetition), where Total_Resource represents the number of activated resources within the conditional resource set plus the number of resources in the repetition packet, and Required_Repetition represents the number of repetitions required for the associated PUSCH. However, this example is provided for illustrative purposes only. An exemplary embodiment may utilize any appropriate technique to determine the repetition index. In addition, a rule may be defined so that the HARQ process ID for the conditional resource is the same as the HARQ process ID derived from the first resource of the repetition packet using the activated conditional resource.

[0126] According to some aspects, in the uplink, the conditional resource may be a configured and activated CG. In the following example, the original repetition packet may be represented as CG#1, and the associated conditional resource may be represented as CG#2. Initially, consider a scenario in which the default CG#1 is associated with service flow #A and CG#2 is associated with service flow #B. In this scenario, CG#2 can be used for new data transmission of service flow #B. However, when the packets in service flow #A experience jitter and the problem of insufficient repetition occurs, CG#2 can be used to perform some or all of the transmission block repetitions of service flow #A. To provide an example, data transmission from service flow #B may be temporarily stopped. If service flow #B does not have data available for transmission, packets from service flow #A may use the resources of CG#2, or if service flow #B has a lower priority than service flow #A, packets from service flow #A may use the resources of CG#2. In this scenario, the HARQ process ID of CG#2 used by service flow #A can be derived by directly following the HARQ process ID of the associated CG#1.

[0127] Example

[0128] In a first embodiment, a user equipment (UE) includes: a transceiver configured to communicate with a network; and a processor communicatively coupled to the transceiver and configured to perform the following operations, the operations including: receiving configuration information, the configuration information including allocation information for a downlink repetition packet having a configured number of repetitions and conditional resources associated with the downlink repetition packet; determining whether the conditional resources associated with the downlink repetition packet are to be activated; and decoding a transport block from a physical downlink shared channel (PDSCH), the physical downlink shared channel (PDSCH) being received on multiple resources from at least one of the downlink repetition packet and the conditional resources associated with the downlink repetition packet.

[0129] In a second embodiment, the UE according to the first embodiment, wherein a single semi-persistent scheduling (SPS) opportunity includes both the downlink repetition packet and the conditional resources associated with the downlink repetition packet.

[0130] In a third embodiment, according to the UE of the second embodiment, the same Hybrid Automatic Repeat Request (HARQ) process ID is configured on all resources of both the downlink repetition packet and the conditional resources associated with the downlink repetition packet.

[0131] In a fourth embodiment, according to the UE of the second embodiment, the operation further comprises: receiving an information element (IE) indicating a number of repetitions of the conditional resource associated with the downlink repetition packet.

[0132] In a fifth embodiment, according to the UE described in the first embodiment, the operation also includes: activating one or more conditional resources associated with the downlink repetition packet; and aggregating the PDSCH from the downlink repetition packet and the activated one or more conditional resources, wherein decoding the transmission block is based on the aggregated PDSCH.

[0133] In a sixth embodiment, the UE according to the fifth embodiment, wherein activating the one or more conditional resources associated with the downlink repetition packet is based on determining that the downlink repetition packet does not include data in one or more of the repetitions of the downlink repetition packet.

[0134] In a seventh embodiment, according to the UE of the fifth embodiment, the operations further include: receiving downlink control information (DCI), wherein activating the one or more conditional resources associated with the repetition packet is based on the DCI.

[0135] In an eighth embodiment, according to the UE of the seventh embodiment, the DCI includes a configured scheduling (CS)-radio network temporary identifier (RNTI).

[0136] In a ninth embodiment, the UE according to the seventh embodiment, wherein the DCI includes a radio network temporary identifier (RNTI) specific to activating conditional resources for downlink transport block repetition.

[0137] In a tenth embodiment, according to the UE of the seventh embodiment, the DCI is provided on a physical downlink control channel (PDCCH) after a first orthogonal frequency division multiplexing (OFDM) symbol of the repeated packet.

[0138] In an eleventh embodiment, according to the UE of the seventh embodiment, the DCI is provided on a physical downlink control channel (PDCCH) before a first orthogonal frequency division multiplexing (OFDM) symbol of the repeated packet.

[0139] In a twelfth embodiment, according to the UE of the seventh embodiment, the DCI includes a field indicating a hybrid automatic repeat request (HARQ) process ID of the downlink repetition packet.

[0140] In a thirteenth embodiment, according to the UE of the seventh embodiment, the DCI includes a field indicating a purpose of activating the one or more conditional resources.

[0141] In a fourteenth embodiment, according to the UE of the seventh embodiment, the DCI includes a field identifying the one or more conditional resources to be activated.

[0142] In a fifteenth embodiment, according to the UE of the fifth embodiment, the operation further comprises: receiving a medium access control (MAC) control element (CE), wherein activating the one or more conditional resources associated with the repeated packet is based on the MAC CE.

[0143] In a sixteenth embodiment, according to the UE of the fifteenth embodiment, the MAC CE is provided in one of the PDSCH resources in the downlink repetition packet.

[0144] In a seventeenth embodiment, according to the UE of the fifteenth embodiment, the MAC CE is provided in a PDSCH resource outside the downlink repetition packet.

[0145] In an eighteenth embodiment, a method for performing any one of the operations described in accordance with the first to seventeenth embodiments is provided.

[0146] In a nineteenth embodiment, a base station includes: a transceiver, which is configured to communicate with a user equipment (UE); and a processor, which is communicatively coupled to the transceiver and configured to perform the following operations, the operations including: sending configuration information to the UE, the configuration information including allocation information for a downlink repetition packet with a configured number of repetitions and conditional resources associated with the downlink repetition packet; determining whether the conditional resources associated with the downlink repetition packet are to be activated; and sending a physical downlink shared channel (PDSCH) to the UE on multiple resources from at least one of the downlink repetition packet and the conditional resources associated with the downlink repetition packet, the PDSCH including transport block repetitions.

[0147] In a twentieth embodiment, according to the base station of the nineteenth embodiment, a single SPS opportunity includes both the downlink repetition packet and the conditional resources associated with the downlink repetition packet.

[0148] In a twenty-first embodiment, according to the base station of the twentieth embodiment, the same hybrid automatic repeat request (HARQ) process ID is configured on all resources of both the downlink repetition packet and the conditional resources associated with the downlink repetition packet.

[0149] In a twenty-second embodiment, according to the base station of the twentieth embodiment, the operation further comprises: sending an information element (IE) to the UE, wherein the IE indicates a number of repetitions of the conditional resources associated with the downlink repetition packet.

[0150] In a twenty-third embodiment, according to the base station of the nineteenth embodiment, the operation further includes: activating one or more conditional resources associated with the downlink repetition packet; and sending PDSCH on the downlink repetition packet and the activated one or more conditional resources.

[0151] In a twenty-fourth embodiment, the base station according to the twenty-third embodiment, wherein activating the one or more conditional resources associated with the downlink repetition packet is based on determining that a buffer is empty.

[0152] In a twenty-fifth embodiment, the base station according to the twenty-fourth embodiment, wherein the buffer is one of a logical channel (LCH) buffer, a radio link control (RLC) buffer, or a HARQ buffer.

[0153] In a twenty-sixth embodiment, according to the base station of the twenty-third embodiment, the operation further includes: sending downlink control information (DCI) to the UE, wherein the UE activates the one or more conditional resources associated with the repeated packet based on the DCI.

[0154] In a twenty-seventh embodiment, the base station according to the twenty-sixth embodiment, wherein the DCI includes a configured scheduling (CS)-radio network temporary identifier (RNTI).

[0155] In a twenty-eighth embodiment, the base station according to the twenty-sixth embodiment, wherein the DCI includes a radio network temporary identifier (RNTI) specific to activating conditional resources for downlink transport block repetition.

[0156] In a twenty-ninth embodiment, according to the base station of the twenty-sixth embodiment, the DCI is sent on a physical downlink control channel (PDCCH) after a first orthogonal frequency division multiplexing (OFDM) symbol of the repeated packet.

[0157] In a thirtieth embodiment, according to the base station of the twenty-sixth embodiment, the DCI is sent on a physical downlink control channel (PDCCH) before the first orthogonal frequency division multiplexing (OFDM) symbol of the repeated packet.

[0158] In a thirty-first embodiment, the base station according to the twenty-sixth embodiment, wherein the DCI includes a field indicating a hybrid automatic repeat request (HARQ) process ID of the downlink repetition packet.

[0159] In a thirty-second embodiment, the base station according to the twenty-sixth embodiment, wherein the DCI includes a field indicating the purpose of activating the one or more conditional resources.

[0160] In a thirty-third embodiment, the base station according to the twenty-sixth embodiment, wherein the DCI includes a field identifying the one or more conditional resources to be activated.

[0161] In a thirty-fourth embodiment, according to the base station of the twenty-third embodiment, the operation also includes: sending a medium access control (MAC) control element (CE) to the UE, wherein the UE activates the one or more conditional resources associated with the repeated packet based on the MAC CE.

[0162] In a thirty-fifth embodiment, according to the base station of the thirty-fourth embodiment, the MAC CE is sent on one of the PDSCH resources in the downlink repetition packet.

[0163] In a thirty-sixth embodiment, according to the base station of the thirty-fourth embodiment, the MAC CE is sent on a PDSCH resource outside the downlink repetition packet.

[0164] In a thirty-seventh embodiment, a method for performing any of the operations described in accordance with the nineteenth to thirty-sixth embodiments.

[0165] In a thirty-eighth embodiment, a processor of a user equipment (UE), the processor being configured to perform the following operations, the operations comprising: receiving configuration information, the configuration information comprising allocation information for an uplink repetition packet having a configured number of repetitions and conditional resources associated with the uplink repetition packet; determining whether the conditional resources associated with the downlink repetition packet are to be activated; and sending a physical uplink shared channel (PUSCH) to the base station on multiple resources from at least one of the uplink repetition packet and the conditional resources associated with the downlink repetition packet, the PUSCH comprising transport block repetitions.

[0166] In a thirty-ninth embodiment, a processor according to the thirty-eighth embodiment, wherein a single configuration grant (CG) opportunity includes both the uplink repetition packet and the conditional resources associated with the uplink repetition packet.

[0167] In a 40th embodiment, the processor according to the 39th embodiment, wherein the same hybrid automatic repeat request (HARQ) process ID is configured on all resources of both the uplink repetition packet and the conditional resources associated with the uplink repetition packet.

[0168] In a forty-first embodiment, according to the processor of the thirty-ninth embodiment, the operation further comprises: receiving an information element (IE) indicating a number of repetitions of the conditional resources associated with the uplink repetition packet.

[0169] In a forty-second embodiment, according to the processor of the thirty-ninth embodiment, the operation further includes: activating one or more conditional resources associated with the uplink repetition packet; and sending PUSCH on the uplink repetition packet and the activated one or more conditional resources.

[0170] In a forty-third embodiment, the processor of embodiment forty-second, wherein activating the one or more conditional resources associated with the uplink repetition packet is based on determining that a buffer is empty.

[0171] In a forty-fourth embodiment, the processor of the forty-second embodiment, wherein the buffer is one of a logical channel (LCH) buffer, a radio link control (RLC) buffer, or a HARQ buffer.

[0172] In a forty-fifth embodiment, according to the processor of the thirty-eighth embodiment, the operation further comprises: sending uplink control information (UCI), wherein the UCI indicates to the base station that there is jitter associated with transport block repetition.

[0173] In a forty-sixth embodiment, according to the processor of the forty-fifth embodiment, the operation further comprises: receiving a signal from the base station in response to the UCI, wherein the signal is configured to activate one or more of the conditional resources.

[0174] In a forty-seventh embodiment, according to the processor of the forty-fifth embodiment, the UCI further recommends to the base station that one or more of the conditional resources will be activated.

[0175] In a 48th embodiment, the processor according to the 45th embodiment, wherein the UCI is multiplexed in PUSCH resources within the uplink repetition packet.

[0176] In a forty-ninth embodiment, according to the processor of the thirty-eighth embodiment, the operation further comprises: sending uplink control information (UCI), wherein the UCI indicates that the UE has activated one or more of the conditional resources for transmission block repetition.

[0177] In a fiftieth embodiment, the processor according to the forty-ninth embodiment, wherein the UCI is multiplexed in PUSCH resources within the uplink repetition packet.

[0178] In a fifty-first embodiment, a processor according to the thirty-ninth embodiment, wherein the uplink repetition packet is a first configuration grant (CG) opportunity, and the conditional resource is a second CG opportunity.

[0179] In a fifty-second embodiment, a processor according to the fifty-first embodiment, wherein the first CG opportunity and the second CG opportunity are associated with different business flows.

[0180] In a fifty-third embodiment, a user equipment (UE) comprises: a transceiver configured to communicate with a network; and a processor according to any one of the thirty-eighth to fifty-second embodiments.

[0181] In a fifty-fourth embodiment, a method for performing any of the operations described in accordance with the thirty-eighth to fifty-second embodiments.

[0182] In a fifty-fifth embodiment, a processor of a base station is configured to perform the following operations, the operations comprising: sending configuration information to a user equipment (UE), the configuration information comprising allocation information for an uplink repetition packet having a configured number of repetitions and conditional resources associated with the uplink repetition packet; determining whether the conditional resources associated with the downlink repetition packet are to be activated; and receiving a physical uplink shared channel (PUSCH) from the UE on multiple resources from at least one of the uplink repetition packet and the conditional resources associated with the uplink repetition packet, the PUSCH comprising transport block repetitions.

[0183] In a fifty-sixth embodiment, a processor according to the fifty-fifth embodiment, wherein a single configuration grant (CG) opportunity includes both the uplink repetition packet and the conditional resources associated with the uplink repetition packet.

[0184] In a fifty-seventh embodiment, the processor according to the fifty-sixth embodiment, wherein the same hybrid automatic repeat request (HARQ) process ID is configured on all resources of both the uplink repetition packet and the conditional resources associated with the uplink repetition packet.

[0185] In a fifty-eighth embodiment, according to the processor of the fifty-sixth embodiment, the operation further comprises: sending an information element (IE) to the UE, wherein the IE indicates the number of repetitions of the conditional resources associated with the uplink repetition packet.

[0186] In a fifty-ninth embodiment, according to the processor of the fifty-fifth embodiment, the operation also includes: activating one or more conditional resources associated with the uplink repetition packet; and aggregating the PUSCH from the uplink repetition packet and the activated one or more conditional resources, wherein decoding the transport block is based on the aggregated PUSCH.

[0187] In a sixtieth embodiment, the processor of the fifty-ninth embodiment, wherein activating the one or more conditional resources associated with the downlink repetition packet is based on determining that the downlink repetition packet does not include data in one or more of the repetitions of the downlink repetition packet.

[0188] In a sixty-first embodiment, according to the processor of the fifty-fifth embodiment, the operation further comprises: receiving uplink control information (UCI) from the UE, wherein the UCI indicates that jitter exists at the UE associated with uplink transport block repetition.

[0189] In a sixty-second embodiment, according to the processor of the sixty-first embodiment, the operation further comprises: sending a signal to the UE in response to the UCI, wherein the signal is configured to activate one or more of the conditional resources.

[0190] In a sixty-third embodiment, the processor according to the sixty-first embodiment, wherein the UCI further recommends that one or more of the conditional resources be activated.

[0191] In a sixty-fourth embodiment, the processor according to the sixty-first embodiment, wherein the UCI is multiplexed in PUSCH resources within the uplink repetition packet.

[0192] In a sixty-fifth embodiment, according to the processor of the fifty-fifth embodiment, the operation further comprises: receiving uplink control information (UCI), wherein the UCI indicates that the UE has activated one or more of the conditional resources for transport block repetition.

[0193] In a sixty-sixth embodiment, the processor according to the sixty-fifth embodiment, wherein the UCI is multiplexed in PUSCH resources within the uplink repetition packet.

[0194] In a sixty-seventh embodiment, a base station comprises: a transceiver configured to communicate with a user equipment (UE) network; and a processor according to any one of the fifty-fifth to sixty-sixth embodiments.

[0195] In a fifty-fourth embodiment, a method for performing any of the operations described in accordance with the fifty-fifth to sixty-sixth embodiments is provided.

[0196] Those skilled in the art will appreciate that the exemplary embodiments described above may be implemented with any suitable software configuration or hardware configuration or combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments may include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, etc. The exemplary embodiments of the above methods may be embodied as a program comprising lines of code stored on a non-transitory computer-readable storage medium, which, when compiled, may be executed on a processor or microprocessor.

[0197] Although this application describes various embodiments, each having different features in various combinations, those skilled in the art will understand that any feature of one embodiment may be combined with features of other embodiments in any manner that is not expressly negated or that is not functionally or logically inconsistent with the operation of the device or the prescribed function of the disclosed embodiment.

[0198] It is well known that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0199] It will be apparent to those skilled in the art that various modifications may be made to the present disclosure without departing from the spirit or scope of the present disclosure. Therefore, it is intended that the present disclosure covers modifications and variations of the present disclosure as long as they fall within the scope of the appended claims and their equivalents.

Claims

1. A processor of a user equipment (UE), the processor being configured to perform the following operations, the operations comprising: receiving configuration information including allocation information for a downlink repetition packet having a configured number of repetitions and conditional resources associated with the downlink repetition packet; determining whether the conditional resources associated with the downlink repetition packet are to be activated; as well as A transport block is decoded from a physical downlink shared channel (PDSCH) received on a plurality of resources from at least one of the downlink repetition packet and the conditional resources associated with the downlink repetition packet.

2. The processor of claim 1, wherein a single semi-persistent scheduling (SPS) opportunity includes both the downlink repetition packet and the conditional resources associated with the downlink repetition packet.

3. The processor of claim 2, wherein the same Hybrid Automatic Repeat Request (HARQ) process ID is configured across all resources of both the downlink repetition packet and the conditional resources associated with the downlink repetition packet.

4. The processor of claim 2, the operations further comprising: An information element (IE) indicating a number of repetitions of the conditional resources associated with the downlink repetition packet is received.

5. The processor of claim 1 , the operations further comprising: activating one or more conditional resources associated with the downlink repetition packet; as well as A PDSCH from the downlink repetition packet and the activated one or more conditional resources are aggregated, wherein decoding the transport block is based on the aggregated PDSCH.

6. The processor of claim 5, wherein activating the one or more conditional resources associated with the downlink repetition packet is based on determining that the downlink repetition packet does not include data in one or more of the repetitions of the downlink repetition packet.

7. The processor of claim 5, the operations further comprising: Downlink control information (DCI) is received, wherein activating the one or more conditional resources associated with the repetition packet is based on the DCI.

8. The processor of claim 7, wherein the DCI comprises a configured scheduling (CS)-radio network temporary identifier (RNTI).

9. The processor of claim 7, wherein the DCI comprises a radio network temporary identifier (RNTI) specific to activating conditional resources for downlink transport block repetition.

10. The processor of claim 7, wherein the DCI is provided on a physical downlink control channel (PDCCH) following a first orthogonal division multiplexing (OFDM) symbol of the repetitive packet.

11. The processor of claim 7, wherein the DCI is provided on a physical downlink control channel (PDCCH) preceding a first orthogonal division multiplexing (OFDM) symbol of the repeated packet.

12. The processor of claim 7, wherein the DCI comprises a field indicating a hybrid automatic repeat request (HARQ) process ID of the downlink repetition packet.

13. The processor of claim 7, wherein the DCI includes a field indicating a purpose for activating the one or more conditional resources.

14. The processor of claim 7, wherein the DCI includes a field identifying the one or more conditional resources to be activated.

15. The processor of claim 5, the operations further comprising: A medium access control (MAC) control element (CE) is received, wherein activating the one or more conditional resources associated with the repeated packet is based on the MAC CE.

16. The processor of claim 15, wherein the MAC CE is provided in one of the PDSCH resources within the downlink repetition packet.

17. The processor of claim 15, wherein the MAC CE is provided in a PDSCH resource outside the downlink repetition packet.

18. A processor of a base station, the processor being configured to perform the following operations, the operations comprising: sending configuration information to a user equipment (UE), the configuration information comprising allocation information for a downlink repetition packet having a configured number of repetitions and conditional resources associated with the downlink repetition packet; determining whether the conditional resources associated with the downlink repetition packet are to be activated; as well as A physical downlink shared channel (PDSCH) is transmitted to the UE on a plurality of resources from at least one of the downlink repetition packet and the conditional resources associated with the downlink repetition packet, the PDSCH including a transport block repetition.

19. The processor of claim 18, wherein a single SPS opportunity includes both the downlink repetition packet and the conditional resources associated with the downlink repetition packet.

20. The processor of claim 19, wherein a same Hybrid Automatic Repeat Request (HARQ) process ID is configured across all resources of both the downlink repetition packet and the conditional resources associated with the downlink repetition packet.

21. The processor of claim 19, the operations further comprising: An information element (IE) is sent to the UE, the IE indicating a number of repetitions of the conditional resources associated with the downlink repetition packet.

22. The processor of claim 18, the operations further comprising: activating one or more conditional resources associated with the downlink repetition packet; as well as A PDSCH is transmitted on the downlink repetition packet and the activated one or more conditional resources.

23. The processor of claim 22, the operations further comprising: Downlink control information (DCI) is sent to the UE, wherein the UE activates the one or more conditional resources associated with the repetition packet based on the DCI.

24. The processor of claim 22, the operations further comprising: A medium access control (MAC) control element (CE) is sent to the UE, wherein the UE activates the one or more conditional resources associated with the repeated packet based on the MAC CE.

Images