Patent Description:
In some cases, a configured grant (CG) may refer to a mode where some resources in an uplink are pre-configured for a user equipment (UE). As such, the UE may use the CG for autonomous uplink data transmission when the UE has data, without the UE having to transmit a scheduling request and receive an explicit uplink grant on a physical downlink control channel (PDCCH) for the specific resource. In some cases, semi-persistent scheduling (SPS) may provide for the scheduling of a periodic uplink or downlink communication for a UE. For example, a base station, such as a gNodeB (gNB), may configure and activate downlink SPS to schedule a UE to receive a periodic physical downlink shared channel (PDSCH) without a PDCCH for every transmission. Similarly, the gNB may configure and activate uplink SPS to schedule a UE to transmit on a periodic physical uplink shared channel (PUSCH) without a physical uplink control channel (PUCCH) for every transmission. Document <CIT> discloses different procedures for updating parameters related to SPS scheduling.

Some present aspects relate to simultaneously updating semi-persistent scheduling (SPS) or configured grant (CG) parameters for multiple user equipments (UEs), for example, by configuring a common target action time, such as an absolute time, for updated SPS or CG parameters to take effect for multiple UEs. As used herein, the term "simultaneous updating" means that an update takes effect at a common or same time, such as in a synchronized manner. For example, the common or same time may be the common target action time across multiple UEs. It should be understood that the actual transmission of the updated SPS or CG parameters, or reception of such parameters at each UE, may occur at different times.

In some implementations, for example, in order to have synchronized updates across multiple UEs, a UE-specific action time for updated parameters to take effect may be signaled to each UE. Accordingly, different UEs may have a common update time even if updated parameters are signaled at different times.

In an aspect, for example, for each SPS/CG reactivation DCI, the RRC configuration may specify an absolute time for the updated parameters to take effect. For example, the absolute time may be after the end of the DCI, e.g., the next boundary within a set of periodic time boundaries. In an aspect, for example, the set of periodic time boundaries may start from an absolute time, e.g., the start of the frame with system frame number (SFN) = <NUM>. In an aspect, the period may be expressed in terms of frames, slots, symbols, etc..

In an alternative or additional aspect, the action time for updated parameters to take effect may be different for different parameters or sets. For example, in one non-limiting aspect, beam update may take effect <NUM> slots later after the DCI, while time-domain resource allocation update may take effect <NUM> slots later after the DCI. In an aspect, different action times may be signaled in the DCI, MAC-CE, or RRC message.

In an alternative or additional aspect, the action time may be applied to parameters other than DL/UL scheduling offset from the (re)activation DCI to the first scheduled PDSCH/PUSCH in terms of slots, e.g., K0/K2 as signaled in DCI. For example, in an aspect, the scheduled PDSCH/PUSCH after the DCI but before the action time may use previous parameters, except for K0/K2. In an aspect, the action time may be signaled as K0/K2 plus a certain delta.

In an aspect, for example, there may be a duration between the reactivation DCI and the first updated scheduled PDSCH/PUSCH based on the updated scheduling offset indicated in the DCI, e.g. K0/K2. Such a duration is hereinafter referred to as a transient duration. In some aspects, in the transient duration, there may be PDSCH/PUSCH occasions based on the previous SPS/CG configuration. Whether transmission is allowed on such PDSCH/PUSCH occasions may be according to one of the following optional aspects: (<NUM>) No PDSCH/PUSCH transmission is allowed in the transient duration. That is, the first PDSCH/PUSCH transmission after the DCI is indicated by the K0/K2 in the DCI; (<NUM>) PDSCH/PUSCH transmission based on the previous SPS/CG configuration is still allowed in the transient duration (however, the uplink feedback resource (e.g., PUCCH) of the last PDSCH in the transient duration should be before the first updated scheduled PDSCH indicated by K0 in the DCI, at least when the last PDSCH in the transient duration and the first updated scheduled PDSCH have the same HARQ ID); (<NUM>) PDSCH/PUSCH transmission based on previous SPS/CG configuration is still allowed in the transient duration, and the last transmission in the transient duration may be on the occasion before the first updated scheduled PDSCH/PUSCH but should have no overlap with the first updated scheduled PDSCH/PUSCH.

Software may be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Accordingly, in one or more example aspects, the functions described may be implemented in hardware, software, or any combination thereof. By way of example, and not limitation, such computer-readable media can include a random-access memory (RAM), a read-only memory (ROM), an electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the aforementioned types of computer-readable media, or any other medium that can be used to store computer executable code in the form of instructions or data structures that can be accessed by a computer.

<FIG> is a diagram illustrating an example of a wireless communications system and an access network <NUM> including UEs <NUM> that may be configured and activated by a base station <NUM> (e.g., a gNB) for SPS functionality. More specifically, for example, a UE <NUM> may include a modem <NUM> and an SPS component <NUM> configured to receive a physical downlink shared channel (PDSCH) from a base station <NUM> according to an SPS configuration, and/or to receive and implement updated SPS or CG parameters. The UE <NUM>, modem <NUM>, and/or SPS component <NUM> may be correspondingly configured to transmit a physical uplink shared channel (PUSCH) to the base station <NUM>. The base station <NUM> may include a modem <NUM> and an SPS component <NUM> configured to transmit the PDSCH to one or more of the UEs <NUM>. The base station <NUM>, modem <NUM>, and/or SPS component <NUM> may be correspondingly configured to receive the PUSCH from the UE <NUM>. In an aspect, the base station <NUM> and SPS component <NUM> may generate and transmit SPS or configured grant (CG) parameters for multiple UEs <NUM> served by the base station <NUM> that may be updated to take effect across the multiple UEs <NUM> in a synchronized manner, for example, by configuring a common target action time for the updated SPS or CG parameters to take effect for the multiple UEs <NUM>.

Further details of the present aspects are described below.

The base stations <NUM> configured for <NUM> LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC <NUM> through backhaul links <NUM> (e.g., S1 interface). The base stations <NUM> configured for <NUM> NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network <NUM> through backhaul links <NUM>. The base stations <NUM> may communicate directly or indirectly (e.g., through the EPC <NUM> or core network <NUM>) with each other over backhaul links <NUM> (e.g., X2 interface). The backhaul links <NUM>, <NUM>, and <NUM> may be wired or wireless.

Certain UEs <NUM> may communicate with each other using device-to-device (D2D) communication link <NUM>, e.g., including synchronization signals.

When operating in an unlicensed frequency spectrum, the small cell <NUM>' may employ NR and use the same (e.g., <NUM>, or the like) unlicensed frequency spectrum as may be used by the Wi-Fi AP <NUM>.

The electromagnetic spectrum is often subdivided, based on frequency/wavelength, into various classes, bands, channels, etc. In <NUM> NR two initial operating bands have been identified as frequency range designations FR1 (<NUM> - <NUM>) and FR2 (<NUM> - <NUM>).

Some base stations, such as gNB <NUM> may operate in a traditional sub-<NUM> spectrum, in millimeter wave frequencies, and/or near millimeter wave frequencies in communication with the UE <NUM>. The millimeter wave base station <NUM> may utilize beamforming <NUM> with the UE <NUM> to compensate for path loss and short range.

The base station <NUM> may also be referred to as a gNB, Node B, evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit reception point (TRP), or some other suitable terminology.

Referring to <FIG>, one or more example frame structures, channels, and resources may be used for communication between the base stations <NUM> and UEs <NUM> of <FIG>.

The subcarrier spacing is <NUM> and symbol duration is approximately <NUM>.

Referring to <FIG>, an example diagram <NUM> includes downlink (e.g., PDSCH) and uplink (e.g., PUSCH) resource timing before <NUM> and after <NUM> an SPS or CG parameter update or reconfiguration. For example, a group of UEs <NUM> (e.g., UE <NUM>, UE <NUM>,. , UE N) may be configured and activated by a base station such as a gNB <NUM> for SPS functionality. Generally, SPS may provide for the scheduling of a periodic communication (e.g., an uplink communication or a downlink communication) for a UE. For example, the gNB <NUM> may configure and activate downlink SPS to schedule the UEs <NUM> to receive a PDSCH without a PDCCH for every transmission. Similarly, the gNB <NUM> may configure and activate uplink SPS to schedule the UEs to transmit a PUSCH without a PUCCH for every transmission.

The base station <NUM> may configure and/or activate the UEs <NUM> for SPS using at least one of a downlink control information (DCI), a medium access control-control element (MAC-CE, e.g., MAC layer control signaling in the payload), or a radio resource control (RRC) signaling. SPS configuration may include parameters such as a periodicity, a hybrid automatic repeat request (HARQ) resource on PUCCH, a number of HARQ processes for SPS, beam configuration, transmission spacing (K0), transmission delay (K1), feedback spacing (K2), etc. The HARQ resource may carry an ACK or NACK indicating whether the PDSCH was correctly received. For example, in an aspect, SPS activation may be carried on a PDCCH DCI. A transmission spacing, which may be referred to as a K0 value, may be defined as a time gap between a downlink grant (e.g., a reactivation DCI) and corresponding downlink data (e.g., PDSCH) reception. A feedback spacing, which may be referred to as a K2 value, may be defined as a time gap between a downlink grant (e.g., a reactivation DCI) and a corresponding uplink feedback transmission. A transmission delay, which may be referred to as a K1 value, may be defined as a time gap between downlink data (e.g., PDSCH) reception and a corresponding uplink feedback transmission. Each of K0, K1, or K2 may be, for example, <NUM> slot, <NUM> slots, <NUM> slots, <NUM> slots, <NUM> millisecond (ms), <NUM>, <NUM>, <NUM>, or other durations.

The DCI may specify additional parameters of the SPS for the PDSCH, such as frequency domain resources, time domain resources, a modulation and coding scheme (MCS), a demodulation reference signal port (DMRS), a scrambling identifier for DMRS sequence generation, transmission configuration indicator (TCI) state, quasi co-location (QCL) type, beam to use and/or beam sweep, etc..

Still referring to <FIG>, for example, in an aspect, the gNB <NUM> may configure "UE <NUM>, UE <NUM>,. , UE N" in the group of UEs <NUM> for SPS, and may reconfigure the SPS for "UE <NUM>, UE <NUM>,. , UE N" at a later time by SPS reconfiguration/reactivation. For example, before SPS reconfiguration/reactivation, for each one of "UE <NUM>, UE <NUM>,. , UE N," the gNB <NUM> my configure downlink and uplink transmission using a particular beam. For example, on the downlink, the gNB <NUM> may transmit two symbols to each of "UE <NUM>, UE <NUM>,. , UE N" back to back on PDSCH using a respective beam. On the uplink, "UE <NUM>, UE <NUM>,. , UE N" may each be configured by the gNB <NUM> with an uplink grant to transmit two symbols to the gNB <NUM> back to back on PUSCH using a respective beam.

Subsequently, for example, in one non-limiting aspect, if the gNB <NUM> determines that transmissions of "UE <NUM>" have high block error rate (BLER), the gNB <NUM> may make the transmissions of "UE <NUM>" more robust, for example, by reconfiguring/reactivating SPS or CG configuration of "UE <NUM>" to enable replication by beam sweep. For example, the gNB <NUM> may reconfigure/reactivate "UE <NUM>" so that each uplink and/or downlink packet of "UE <NUM>" is sent by multiple beams (e.g., <NUM> different beams), either simultaneously, if the hardware allows this option, or sequentially in time. Accordingly, if one beam gets blocked, the packet of "UE <NUM>" may still be communicated via one of the other beams, thus improving reliability.

In an aspect, SPS/CG parameters per UE for the group of UEs <NUM> being served by the gNB <NUM> may need to be updated simultaneously, e.g., to take effect in a synchronized manner, for the group of UEs <NUM>. For example, if "UE <NUM>" is reconfigured/reactivated with beam sweep-based replication (e.g., receiving/transmitting each packet using three beams as in <FIG>), the resource location offsets for the other UEs in the group of UEs <NUM> may need to be updated at the same time, e.g., at a common starting point, that such a beam sweep is enabled for "UE <NUM>" in order to avoid errors or conflicts in the communications or to improve efficiency.

In an aspect, resource location offsets for the other UEs (UE <NUM>,. , UE N) may have to be updated such as to minimize the total duration of SPS/CG transmissions for the entire group of UEs <NUM>.

In some implementations, for example, in order to have synchronized updates across multiple UEs, a UE-specific action time for updated parameters to take effect may be signaled to each UE. Accordingly, different UEs may have a common update time (e.g., an absolute time) even if updated parameters are signaled to different UEs at different times.

In an aspect, for example, multiple DCIs may be transmitted at different points in time to update SPS/CG parameters of multiple UEs. However, the DCIs may indicate action times with absolute values so that the updates take effect simultaneously for all the UEs. Accordingly, in an aspect, for example, the transmissions to "UE <NUM>" do not necessarily have to immediately affect the timing of all the other UEs, and the configuration updates to the other UEs may be pushed at a later time if the other UEs are not immediately/directly affected by the updates of "UE <NUM>. " Such flexibility may improve communication reliability/stability, since a poor performance incident of "UE <NUM>" does not necessarily require/cause an immediate update to all UEs, e.g., changes to "UE <NUM>" may take effect after the transmissions of the other UEs have completed.

In an aspect, for example, for each SPS/CG reactivation DCI, the RRC configuration may specify an absolute time for the updated parameters to take effect. For example, the absolute time may be after the end of the transmission of the DCI, e.g., the next boundary within a set of periodic time boundaries. In an aspect, for example, the set of periodic time boundaries may start from an absolute time, e.g., the start of the frame with SFN = <NUM>. For example, in one non-limiting aspect, the reconfigured SPS/CG parameters for each UE may take effect at the start of the next frame, thus resulting in synchronized updates for all UEs. In an aspect, the period may be expressed in terms of frames, slots, symbols, etc..

In an alternative or additional aspect, the action time for updated parameters to take effect may be different for different parameters and/or different sets of parameters. For example, in one non-limiting aspect, beam update may take effect <NUM> slots later after the DCI, while time-domain resource allocation update may take effect <NUM> slots later after the DCI. In an aspect, different action times may be signaled in the DCI, MAC-CE, or RRC message.

In an aspect, for example, the parameters to be updated by a (re)activation DCI may include one or more downlink and/or uplink scheduling offsets such as K0 (e.g., transmission spacing from the (re)activation DCI to the corresponding PDSCH) or K2 (e.g., feedback spacing from the (re)activation DCI to the corresponding PUSCH). In this case, the action time may be applicable only to parameters other than the downlink/uplink scheduling offsets from the (re)activation DCI to the first scheduled PDSCH/PUSCH in terms of slots, e.g., K0/K2 as signaled in DCI. For example, in an aspect, a scheduled PDSCH/PUSCH located after the DCI but before the action time may use the updated K0/K2 as signaled by the DCI but may continue to use any other previous/old parameters even if such other parameters are also updated by the DCI. Accordingly, K0/K2 may be updated in a different timeline as compared to other SPS/CG parameters.

In an aspect, the action time may be signaled as K0/K2 plus certain delta. For example, in an aspect, the action time for parameters other than K0/K2 may be indicated in terms of a delay with respect to the K0/K2.

In an aspect, for example, there may be a duration between the (re)activation DCI and the first updated scheduled transmission (PDSCH/PUSCH) that is based on an updated scheduling offset indicated in the DCI, e.g., a K0/K2. Such a duration is hereinafter referred to as a transient duration. In some aspects, in the transient duration, there may be transmission occasions (e.g., PDSCH/PUSCH) based on a previous SPS/CG configuration. Whether transmission is allowed on such occasions may be according to one of the following optional/alternative aspects.

In one optional aspect, for example, no PDSCH/PUSCH transmission according to the previous SPS/CG configuration is allowed in the transient duration. That is, the first PDSCH/PUSCH transmission after the (re)activation DCI is according to the K0/K2 indicated in the (re)activation DCI.

In another optional aspect, for example, PDSCH/PUSCH transmission based on the previous SPS/CG configuration is still allowed in the transient duration. However, for such transmissions, the uplink feedback resource (e.g., PUCCH) of the last PDSCH according to the previous SPS/CG configuration should be before the first scheduled PDSCH according to the K0 indicated in the (re)activation DCI. For example, in an aspect, when the last PDSCH according to the previous SPS/CG configuration and the first scheduled PDSCH according to the K0 indicated in the (re)activation DCI have the same HARQ ID, the ACK for the last PDSCH according to the previous SPS/CG configuration should precede the first scheduled PDSCH according to the K0 indicated in the (re)activation DCI. Accordingly, the 3GPP requirement that the next data should follow the last acknowledgement is met.

In a further optional aspect, for example, the aforementioned 3GPP requirement may be removed. For example, in an aspect, PDSCH/PUSCH transmission based on previous SPS/CG configuration is still allowed in the transient duration, and the last transmission in the transient duration according to the previous SPS/CG configuration may be on the occasion before the first scheduled PDSCH/PUSCH according to the update in the (re)activation DCI. However, the last transmission in the transient duration according to the previous SPS/CG configuration should not overlap with the first scheduled PDSCH/PUSCH according to the update in the (re)activation DCI.

Referring to <FIG>, in one optional non-limiting aspect, for example, the SPS/CG communications of the group of UEs <NUM> may be configured to be repeated in periodic cycles, such as a first cycle <NUM>, a second cycle <NUM>, a third cycle <NUM>, etc. In an aspect, a single cycle may be too short to finish updating SPS/CG parameters for all of "UE <NUM>, UE <NUM>,. , UE N" so that the updates can be applied in a next/subsequent cycle.

For example, for a subcarrier spacing (SCS) of <NUM>, each cycle is <NUM>. In this case, a <NUM> cycle duration includes <NUM> slots and may include at most <NUM> PDCCH symbols (<NUM> PDCCH symbols per slot), which may be used to update SPS/CG parameters for at most <NUM> UEs via DCI. In addition, sufficient time should be reserved for PDCCH decoding. For example, due to decoding latency, the last <NUM> slots of a cycle may not be used to send PDCCH for SPS/CG parameter updates that need to be applied at the start of the next cycle. More specifically, if PDCCH symbols are transmitted in the last <NUM> slots of a cycle, a UE may not finish decoding those PDCCH symbols before the start of the next cycle. Therefore, any SPS/CG parameter updates via PDCCH symbols transmitted in the last <NUM> slots of a cycle may not take effect at the start of the next cycle, and a UE may not be able to apply such parameters at the start of the next cycle. Accordingly, when a cycle includes <NUM> slots, only the first <NUM> slots of the cycle may be used for SPS/CG parameter update of at most <NUM> UEs. However, the group of UEs <NUM> may include more than <NUM> UEs (e.g., may include <NUM> or <NUM> UEs).

Accordingly, in some present aspects, to address the above, a common "action time" may be configured for synchronized updates for all UEs in the group of UEs <NUM> to take effect. For example, in an aspect, each activation/reactivation DCI or MAC-CE or RRC signaling for each UE may indicate a target action time for updated SPS/CG parameters to take effect for that UE, and such target action time may be common for multiple UEs <NUM>.

For example, in an aspect, due to the number of UEs in the group of UEs <NUM>, the group of UEs <NUM> may be split into two subgroups of UEs, and an activation/reactivation DCI in the first cycle <NUM> may indicate updated SPS/CG parameters for each UE in the first sub-group of UEs. Further, an activation/reactivation DCI in the second cycle <NUM> may indicate updated SPS/CG parameters for each UE in the second sub-group of UEs. In addition, in an aspect, each of the aforementioned activation/reactivation DCIs may also indicate a target action time common for the updated SPS/CG parameters to take effect for both sub-groups of UEs. For example, in an aspect, each of the aforementioned activation/reactivation DCIs may also indicate that for both sub-groups of UEs, the updated SPS/CG parameters should take effect at the start of the third cycle <NUM>. As such, SPS/CG parameters may be updated simultaneously for the entire group of UEs <NUM> to take effect at the beginning of the third cycle <NUM>.

In an aspect, for example, the action time used to align SPS/CG parameter update time across multiple UEs may be indicated in the activation/reactivation DCI or MAC-CE or RRC signaling transmitted by the gNB <NUM> to update such SPS/CG parameters.

In an aspect, the absolute time may be expressed, for example, in an absolute unit of time such as a frame index, subframe index, slot index, symbol index, etc..

In a further aspect, the action time may be a relative time offset from the activation/reactivation DCI or MAC-CE or RRC signaling transmitted by the gNB <NUM> to update the SPS/CG parameters.

In some alternative and/or additional aspects, the gNB may dynamically indicate which type of action time to use for SPS/CG parameter update in DCI, MAC-CE, or RRC signaling.

<FIG> illustrate flow charts of example methods <NUM> and <NUM> for wireless communications for a UE. In an example, UE <NUM> may perform the functions described in any of methods <NUM> or <NUM> using one or more of the components described in <FIG> above (e.g., modem <NUM> and/or SPS component <NUM>) or in <FIG> or <FIG> below (e.g., the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> in <FIG>).

Referring to <FIG>, at <NUM>, the method <NUM> of wireless communication for a UE includes receiving, by the UE, an activation/reactivation DCI from a base station, the activation/reactivation DCI including an update to a periodically-occurring scheduling, where an absolute time for the update to take effect is specified in an RRC configuration of the activation/reactivation DCI. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may receive an activation/reactivation DCI from the base station <NUM>, the activation/reactivation DCI including an update to a periodically-occurring scheduling, where an absolute time for the update to take effect is specified in an RRC configuration of the activation/reactivation DCI, as described herein. In an aspect, for example, the periodically-occurring scheduling may relate to longer time scale allocations repeated periodically in time, such as SPS or CG. In an aspect, for example, the DCI may be carried by a wireless signal that is received and processed by the UE <NUM>, and the DCI indicates an absolute time for the update to take effect, as describe herein. For example, in an aspect, the DCI may indicate an absolute time for the SPS or CG parameter update to take effect, where the absolute time is common to a group of UEs <NUM> served by the base station <NUM> and including the UE <NUM>. Accordingly, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may provide means for receiving, by the UE, an activation/reactivation DCI from a base station, the activation/reactivation DCI including an update to a periodically-occurring scheduling, where an absolute time for the update to take effect is specified in an RRC configuration of the activation/reactivation DCI.

At <NUM>, the method <NUM> further includes applying the update to the periodically-occurring scheduling for communications of the UE beginning at and following the absolute time. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may apply the update to the periodically-occurring scheduling for communications of the UE <NUM> beginning at and following the absolute time, as described above. For instance, the UE <NUM> may determine the absolute time by decoding an indication in the downlink communication. In an aspect, for example, the update is applied to a persistent scheduling occurring periodically, such as a SPS or CG. Accordingly, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may provide means for applying the update to the periodically-occurring scheduling for communications of the UE beginning at and following the absolute time.

Optionally or in addition, the periodically-occurring scheduling includes a SPS or CG parameter, the absolute time is common to a group of UEs <NUM> including the UE <NUM>, and updates to one or more SPS or CG parameters of the group of UEs <NUM> take effect simultaneously at the absolute time.

Optionally or in addition, the absolute time is after an end of the activation/reactivation DCI.

Optionally or in addition, the absolute time is a next boundary within a set of periodic time boundaries.

Optionally or in addition, the absolute time is expressed in a frame index, a subframe index, a slot index, or a symbol index.

Referring to <FIG>, at <NUM>, the method <NUM> of wireless communication for a UE includes receiving, by the UE, at least one downlink communication from a base station, the at least one downlink communication including an update to a plurality of SPS or CG parameters. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may receive at least one downlink communication from a base station <NUM>, the at least one downlink communication including an update to a plurality of SPS or CG parameters, as described above. Accordingly, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may provide means for receiving, by the UE, at least one downlink communication from a base station, the at least one downlink communication including an update to a plurality of SPS or CG parameters.

At <NUM>, the method <NUM> further includes determining an action time for the update to take effect for each of the plurality of SPS or CG parameters, where the action time is a function of a type of each of the plurality of SPS or CG parameters, where the action time is selected from a group including at least a first action time associated with a first type of parameter and a second action time associated with a second type of parameter, the second action time being different than the first action time. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may determine an action time for the update to take effect for each of the plurality of SPS or CG parameters, where the action time is a function of a type of each of the plurality of SPS or CG parameters, where the action time is selected from a group including at least a first action time associated with a first type of parameter and a second action time associated with a second type of parameter, the second action time being different than the first action time, as described above. Accordingly, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may provide means for determining an action time for the update to take effect for each of the plurality of SPS or CG parameters, where the action time is a function of a type of each of the plurality of SPS or CG parameters, where the action time is selected from a group including at least a first action time associated with a first type of parameter and a second action time associated with a second type of parameter, the second action time being different than the first action time.

At <NUM>, the method <NUM> further includes applying the update to respective ones of the plurality of SPS or CG parameters for communications of the UE beginning at and following each respective action time for the respective ones of the plurality SPS or CG parameters. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may apply the update to respective ones of the plurality of SPS or CG parameters for communications of the UE <NUM> beginning at and following each respective action time for the respective ones of the plurality SPS or CG parameters, as described above. Accordingly, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may provide means for applying the update to respective ones of the plurality of SPS or CG parameters for communications of the UE beginning at and following each respective action time for the respective ones of the plurality SPS or CG parameters.

Optionally or in addition, the first action time is a first periodic time boundary after the downlink communication and the second action time is a second periodic time boundary after the downlink communication, the first periodic time boundary being different than the second periodic time boundary.

Optionally or in addition, each action time is specified in the downlink communication.

Optionally or in addition, receiving the at least one downlink communication includes receiving at least one of an activation/reactivation DCI or a MAC CE or an RRC signaling that includes each action time that updates the plurality of SPS or CG parameters. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may receive at least one of an activation/reactivation DCI or a MAC CE or an RRC signaling that includes each action time that updates the plurality of SPS or CG parameters, as described herein.

Optionally or in addition, the at least one downlink communication includes an activation/reactivation DCI indicating an updated scheduling offset.

Optionally or in addition, the method <NUM> further includes applying the updated scheduling offset for the communications of the UE beginning at and following the first action time, where the first action time coincides with an end of a transmission of the activation/reactivation DCI. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may apply the updated scheduling offset for the communications of the UE beginning at and following the first action time, where the first action time coincides with an end of a transmission of the activation/reactivation DCI, as described herein.

Optionally or in addition, the activation/reactivation DCI further indicates an updated non-scheduling parameter.

Optionally or in addition, the method <NUM> further includes applying the updated non-scheduling parameter for the communications of the UE beginning at and following the second action time, where the second action time coincides with an amount of time after the end of the transmission of the activation/reactivation DCI. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may apply the updated non-scheduling parameter for the communications of the UE <NUM> beginning at and following the second action time, where the second action time coincides with an amount of time after the end of the transmission of the activation/reactivation DCI, as described herein.

Optionally or in addition, the communications of the UE <NUM> include a PDSCH or a PUSCH, and the updated scheduling offset includes a K0 or a K2.

Optionally or in addition, the second action time is specified as a K0 or a K2 plus a time delay.

Optionally or in addition, the method <NUM> further includes identifying a transient period that starts with the activation/reactivation DCI and ends with a first updated scheduled transmission according to the updated scheduling parameter indicated in the activation/reactivation DCI. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may identify a transient period that starts with the activation/reactivation DCI and ends with a first updated scheduled transmission according to the updated scheduling parameter indicated in the activation/reactivation DCI, as described herein.

Optionally or in addition, the method <NUM> further includes skipping communication of scheduled transmissions that are according to a previous SPS or CG configuration in the transient period. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may skip communication of scheduled transmissions that are according to a previous SPS or CG configuration in the transient period, as described herein.

Optionally or in addition, the method <NUM> further includes determining whether to allow communication of a scheduled transmission that is according to a previous SPS or CG configuration in the transient period. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may determine whether to allow communication of a scheduled transmission that is according to a previous SPS or CG configuration in the transient period, as described herein.

Optionally or in addition, the determining whether to allow the communication of the scheduled transmission includes skipping the communication of the scheduled communication in response to the scheduled communication including a PDSCH with an uplink feedback resource that is after the first updated scheduled transmission; and allowing the communication of the scheduled communication otherwise. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may skip the communication of the scheduled communication in response to the scheduled communication including a PDSCH with an uplink feedback resource that is after the first updated scheduled transmission, and allow the communication of the scheduled communication otherwise, as described herein.

Optionally or in addition, the determining whether to allow the communication of the scheduled transmission includes skipping the communication of the scheduled communication in response to the scheduled communication including a PDSCH with a same HARQ ID as the first updated scheduled transmission and an uplink feedback resource that is after the first updated scheduled transmission, and allowing communication of the scheduled communication otherwise. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may skip the communication of the scheduled communication in response to the scheduled communication including a PDSCH with a same HARQ ID as the first updated scheduled transmission and an uplink feedback resource that is after the first updated scheduled transmission, and allow communication of the scheduled communication otherwise, as described herein.

Optionally or in addition, the determining whether to allow the communication of the scheduled transmission includes skipping the communication of the scheduled communication in response to the scheduled communication overlapping with the first updated scheduled transmission, and allowing the communication of the scheduled communication otherwise. For example, in an aspect, the UE <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may skip the communication of the scheduled communication in response to the scheduled communication overlapping with the first updated scheduled transmission, and allow the communication of the scheduled communication otherwise, as described herein.

<FIG> illustrate flow charts of example methods <NUM> and <NUM> for wireless communications for a base station. In an example, the base station <NUM> may perform the functions described in any of methods <NUM> or <NUM> using one or more of the components described in <FIG> (e.g., SPS component <NUM>) above or in <FIG> or <FIG> below (e.g., the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> in <FIG>).

Referring to <FIG>, at <NUM>, the method <NUM> of wireless communication for a base station includes transmitting, by the base station, an activation/reactivation DCI to a UE, the activation/reactivation DCI including an update to a periodically-occurring scheduling, where an absolute time for the update to take effect is specified in an RRC configuration of the activation/reactivation DCI. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may transmit an activation/reactivation DCI to the UE <NUM>, the activation/reactivation DCI including an update to a periodically-occurring scheduling, where an absolute time for the update to take effect is specified in an RRC configuration of the activation/reactivation DCI, as described herein. In an aspect, for example, the periodically-occurring scheduling may relate to longer time scale allocations repeated periodically in time, such as SPS or CG. In an aspect, for example, the DCI may be carried by a wireless signal that is received and processed by the UE <NUM>, and the DCI indicates an absolute time for the update to take effect, as describe herein. For example, in an aspect, the DCI may indicate an absolute time for the SPS or CG parameter update to take effect, where the absolute time is common to a group of UEs <NUM> served by the base station <NUM> and including the UE <NUM>. Accordingly, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may provide means for transmitting an activation/reactivation DCI to the UE <NUM>, the activation/reactivation DCI including an update to a periodically-occurring scheduling, where an absolute time for the update to take effect is specified in an RRC configuration of the activation/reactivation DCI.

At <NUM>, the method <NUM> further includes applying the update to the periodically-occurring scheduling for communications with the UE beginning at and following the absolute time. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may apply the update to the periodically-occurring scheduling for communications with the UE <NUM> beginning at and following the absolute time, as described above. In an aspect, for example, the update is applied to a persistent scheduling occurring periodically, such as a SPS or CG. Accordingly, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may provide means for applying the update to the periodically-occurring scheduling for communications with the UE <NUM> beginning at and following the absolute time.

Optionally or in addition, the periodically-occurring scheduling include a SPS or CG parameter, the absolute time is common to a group of UEs <NUM> including the UE <NUM>, and updates to one or more SPS or CG parameters of the group of UEs <NUM> take effect simultaneously at the absolute time.

Referring to <FIG>, at <NUM>, the method <NUM> of wireless communication for a base station includes transmitting, by the base station, at least one downlink communication to a UE, the at least one downlink communication including an update to a plurality of SPS or CG parameters. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may transmit at least one downlink communication to a UE <NUM>, the at least one downlink communication including an update to a plurality of SPS or CG parameters, as described above. Accordingly, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may provide means for transmitting at least one downlink communication to a UE <NUM>, the at least one downlink communication including an update to a plurality of SPS or CG parameters.

At <NUM>, the method <NUM> further includes determining an action time for the update to take effect for each of the plurality of SPS or CG parameters, where the action time is a function of a type of each of the plurality of SPS or CG parameters, where the action time is selected from a group including at least a first action time associated with a first type of parameter and a second action time associated with a second type of parameter, the second action time being different than the first action time. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may determine an action time for the update to take effect for each of the plurality of SPS or CG parameters, where the action time is a function of a type of each of the plurality of SPS or CG parameters, where the action time is selected from a group including at least a first action time associated with a first type of parameter and a second action time associated with a second type of parameter, the second action time being different than the first action time, as described above. Accordingly, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may provide means for determining an action time for the update to take effect for each of the plurality of SPS or CG parameters, where the action time is a function of a type of each of the plurality of SPS or CG parameters, where the action time is selected from a group including at least a first action time associated with a first type of parameter and a second action time associated with a second type of parameter, the second action time being different than the first action time.

At <NUM>, the method <NUM> further includes applying the update to respective ones of the plurality of SPS or CG parameters for communications with the UE beginning at and following each respective action time for the respective ones of the plurality SPS or CG parameters. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may apply the update to respective ones of the plurality of SPS or CG parameters for communications with the UE <NUM> beginning at and following each respective action time for the respective ones of the plurality SPS or CG parameters, as described above. Accordingly, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may provide means for applying the update to respective ones of the plurality of SPS or CG parameters for communications with the UE <NUM> beginning at and following each respective action time for the respective ones of the plurality SPS or CG parameters.

Optionally or in addition, transmitting the at least one downlink communication includes transmitting at least one of an activation/reactivation DCI or a MAC CE or an RRC signaling that includes each action time that updates the plurality of SPS or CG parameters. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may transmit at least one of an activation/reactivation DCI or a MAC CE or an RRC signaling that includes each action time that updates the plurality of SPS or CG parameters, as described herein.

Optionally or in addition, the method <NUM> further includes applying the updated scheduling offset for the communications with the UE beginning at and following the first action time, where the first action time coincides with an end of a transmission of the activation/reactivation DCI. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may apply the updated scheduling offset for the communications with the UE <NUM> beginning at and following the first action time, where the first action time coincides with an end of a transmission of the activation/reactivation DCI, as described herein.

Optionally or in addition, the method <NUM> further includes applying the updated non-scheduling parameter for the communications with the UE beginning at and following the second action time, where the second action time coincides with an amount of time after the end of the transmission of the activation/reactivation DCI. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may apply the updated non-scheduling parameter for the communications with the UE <NUM> beginning at and following the second action time, where the second action time coincides with an amount of time after the end of the transmission of the activation/reactivation DCI, as described herein.

Optionally or in addition, the communications with the UE <NUM> include a PDSCH or a PUSCH, and the updated scheduling offset includes a K0 or a K2.

Optionally or in addition, the method <NUM> further includes identifying a transient period that starts with the activation/reactivation DCI and ends with a first updated scheduled transmission according to the updated scheduling parameter indicated in the activation/reactivation DCI. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may identify a transient period that starts with the activation/reactivation DCI and ends with a first updated scheduled transmission according to the updated scheduling parameter indicated in the activation/reactivation DCI, as described herein.

Optionally or in addition, the method <NUM> further includes skipping communication of scheduled transmissions that are according to a previous SPS or CG configuration in the transient period. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may skip communication of scheduled transmissions that are according to a previous SPS or CG configuration in the transient period, as described herein.

Optionally or in addition, the method <NUM> further includes determining whether to allow communication of a scheduled transmission that is according to a previous SPS or CG configuration in the transient period. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may determine whether to allow communication of a scheduled transmission that is according to a previous SPS or CG configuration in the transient period, as described herein.

Optionally or in addition, the determining whether to allow the communication of the scheduled transmission includes skipping the communication of the scheduled communication in response to the scheduled communication including a PDSCH with an uplink feedback resource that is after the first updated scheduled transmission; and allowing the communication of the scheduled communication otherwise. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may skip the communication of the scheduled communication in response to the scheduled communication including a PDSCH with an uplink feedback resource that is after the first updated scheduled transmission; and allow the communication of the scheduled communication otherwise, as described herein.

Optionally or in addition, the determining whether to allow the communication of the scheduled transmission includes skipping the communication of the scheduled communication in response to the scheduled communication including a PDSCH with a same HARQ ID as the first updated scheduled transmission and an uplink feedback resource that is after the first updated scheduled transmission, and allowing communication of the scheduled communication otherwise. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may skip the communication of the scheduled communication in response to the scheduled communication including a PDSCH with a same HARQ ID as the first updated scheduled transmission and an uplink feedback resource that is after the first updated scheduled transmission, and allow communication of the scheduled communication otherwise, as described herein.

Optionally or in addition, the determining whether to allow the communication of the scheduled transmission includes skipping the communication of the scheduled communication in response to the scheduled communication overlapping with the first updated scheduled transmission, and allowing the communication of the scheduled communication otherwise. For example, in an aspect, the base station <NUM>, the antenna <NUM>, RF front end <NUM>, transceiver <NUM>, modem <NUM>, processor <NUM>, memory <NUM>, and/or SPS component <NUM> may skip the communication of the scheduled communication in response to the scheduled communication overlapping with the first updated scheduled transmission, and allow the communication of the scheduled communication otherwise, as described herein.

Referring to <FIG>, one example of an implementation of UE <NUM> may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM> and/or SPS component <NUM> to enable one or more of the functions described herein related to SPS.

In an aspect, the one or more processors <NUM> can include a modem <NUM> and/or can be part of the modem <NUM> that uses one or more modem processors. Thus, the various functions related to SPS component <NUM> may be included in modem <NUM> and/or processors <NUM> and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, the one or more processors <NUM> may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with transceiver <NUM>. In other aspects, some of the features of the one or more processors <NUM> and/or modem <NUM> associated with SPS component <NUM> may be performed by transceiver <NUM>.

Also, memory <NUM> may be configured to store data used herein and/or local versions of applications <NUM> or SPS component <NUM> and/or one or more of its subcomponents being executed by at least one processor <NUM>. Memory <NUM> can include any type of computer-readable medium usable by a computer or at least one processor <NUM>, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory <NUM> may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining SPS component <NUM> and/or one or more of its subcomponents, and/or data associated therewith, when UE <NUM> is operating at least one processor <NUM> to execute SPS component <NUM> and/or one or more of its subcomponents.

Receiver <NUM> may include hardware, firmware, and/or software code executable by a processor for receiving data, the code including instructions and being stored in a memory (e.g., computer-readable medium). Additionally, receiver <NUM> may process such received signals, and also may obtain measurements of the signals, such as, but not limited to, Ec/Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. Transmitter <NUM> may include hardware, firmware, and/or software code executable by a processor for transmitting data, the code including instructions and being stored in a memory (e.g., computer-readable medium).

Although illustrated as being associated with the processor <NUM>, it should be understood that the functionality of the SPS component <NUM> may alternatively be implemented by the modem <NUM>.

In an aspect, the processor(s) <NUM> may correspond to one or more of the processors described in connection with UE <NUM> in <FIG> below. Similarly, the memory <NUM> may correspond to the memory described in connection with UE <NUM> in <FIG> below.

In one configuration, UE <NUM> or UE <NUM> (<FIG>) may be an apparatus for wireless communication including means for performing any of the appended claims for wireless communication by a UE. The aforementioned means may be one or more of the aforementioned components of UE <NUM> and/or processor <NUM> of UE <NUM> configured to perform the functions recited by the aforementioned means. As described supra, processor <NUM> may include the TX Processor <NUM>, the RX Processor <NUM>, and the controller/processor <NUM> of UE <NUM> described below with reference to <FIG>.

Referring to <FIG>, one example of an implementation of base station <NUM> may include a variety of components, some of which have already been described above and are described further herein, including components such as one or more processors <NUM> and memory <NUM> and transceiver <NUM> in communication via one or more buses <NUM>, which may operate in conjunction with modem <NUM> and/or SPS component <NUM> to enable one or more of the functions described herein related to SPS.

Also, memory <NUM> may be configured to store data used herein and/or local versions of applications <NUM> or SPS component <NUM> and/or one or more of its subcomponents being executed by at least one processor <NUM>. Memory <NUM> can include any type of computer-readable medium usable by a computer or at least one processor <NUM>, such as random access memory (RAM), read only memory (ROM), tapes, magnetic discs, optical discs, volatile memory, non-volatile memory, and any combination thereof. In an aspect, for example, memory <NUM> may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining SPS component <NUM> and/or one or more of its subcomponents, and/or data associated therewith, when base station <NUM> is operating at least one processor <NUM> to execute SPS component <NUM> and/or one or more of its subcomponents.

Receiver <NUM> may include hardware, firmware, and/or software code executable by a processor for receiving data, the code including instructions and being stored in a memory (e.g., computer-readable medium). In an aspect, receiver <NUM> may receive signals transmitted by at least one UE <NUM>. Additionally, receiver <NUM> may process such received signals, and also may obtain measurements of the signals, such as, but not limited to, Ec/Io, signal-to-noise ratio (SNR), reference signal received power (RSRP), received signal strength indicator (RSSI), etc. Transmitter <NUM> may include hardware, firmware, and/or software code executable by a processor for transmitting data, the code including instructions and being stored in a memory (e.g., computer-readable medium).

Moreover, in an aspect, base station <NUM> may include RF front end <NUM>, which may operate in communication with one or more antennas <NUM> and transceiver <NUM> for receiving and transmitting radio transmissions, for example, wireless communications transmitted by other base stations <NUM> or wireless transmissions transmitted by UE <NUM>.

In an aspect, transceiver may be tuned to operate at specified frequencies such that base station <NUM> can communicate with, for example, one or more UEs <NUM> or one or more cells associated with one or more other base stations <NUM>. In an aspect, for example, modem <NUM> can configure transceiver <NUM> to operate at a specified frequency and power level based on the base station configuration of the base station <NUM> and the communication protocol used by modem <NUM>.

In an aspect, modem <NUM> can control one or more components of base station <NUM> (e.g., RF front end <NUM>, transceiver <NUM>) to enable transmission and/or reception of signals from the network based on a specified modem configuration. In another aspect, the modem configuration can be based on base station configuration information associated with base station <NUM>.

In an aspect, the processor(s) <NUM> may correspond to one or more of the processors described in connection with base station <NUM> in <FIG> below. Similarly, the memory <NUM> may correspond to the memory described in connection with base station <NUM> in <FIG> below.

In one configuration, base station <NUM> or base station <NUM> may be an apparatus for wireless communication including means for performing any of the appended claims for wireless communication by a base station. The aforementioned means may be one or more of the aforementioned components of base station <NUM> and/or processor <NUM> of base station <NUM> configured to perform the functions recited by the aforementioned means. As described supra, processor <NUM> may include the TX Processor <NUM>, the RX Processor <NUM>, and the controller/processor <NUM> of base station <NUM> described below with reference to <FIG>.

In an aspect, one or more components of base station <NUM> may implement applications <NUM>, modem <NUM>, and/or SPS component <NUM> described above with reference to <FIG>. For example, in an aspect, one or more processors of base station <NUM> (e.g., TX processor <NUM>, RX processor <NUM>, controller/processor <NUM>, etc.) can include the modem <NUM> and/or can be part of modem <NUM> that uses one or more modem processors. In an aspect, the various functions related to SPS component <NUM> may be included in modem <NUM> and/or one or more processors of base station <NUM> and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, one or more processors of base station <NUM> may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with a transceiver. In other aspects, some of the features of modem <NUM> and/or SPS component <NUM> may be performed by a transceiver <NUM> of base station <NUM>. Also, memory <NUM> of base station <NUM> may be configured to store data used herein and/or local versions of applications <NUM> or SPS component <NUM> and/or one or more of its subcomponents being executed by one or more processors of base station <NUM>. In an aspect, for example, memory <NUM> may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining SPS component <NUM> and/or one or more of its subcomponents, and/or data associated therewith, when base station <NUM> is operating at least one processor to execute SPS component <NUM> and/or one or more of its subcomponents.

Further, in an aspect, one or more components of UE <NUM> may implement applications <NUM>, modem <NUM>, and/or SPS component <NUM> described above with reference to <FIG>. For example, in an aspect, one or more processors of UE <NUM> (e.g., TX processor <NUM>, RX processor <NUM>, controller/processor <NUM>, etc.) can include modem <NUM> and/or can be part of modem <NUM> that uses one or more modem processors. In an aspect, the various functions related to SPS component <NUM> may be included in modem <NUM> and/or one or more processors of UE <NUM> and, in an aspect, can be executed by a single processor, while in other aspects, different ones of the functions may be executed by a combination of two or more different processors. For example, in an aspect, one or more processors of UE <NUM> may include any one or any combination of a modem processor, or a baseband processor, or a digital signal processor, or a transmit processor, or a receiver processor, or a transceiver processor associated with a transceiver. In other aspects, some of the features of modem <NUM> and/or SPS component <NUM> may be performed by a transceiver <NUM> of UE <NUM>. Also, memory <NUM> of UE <NUM> may be configured to store data used herein and/or local versions of applications <NUM> or SPS component <NUM> and/or one or more of its subcomponents being executed by one or more processors of UE <NUM>. In an aspect, for example, memory <NUM> may be a non-transitory computer-readable storage medium that stores one or more computer-executable codes defining SPS component <NUM> and/or one or more of its subcomponents, and/or data associated therewith, when UE <NUM> is operating at least one processor to execute SPS component <NUM> and/or one or more of its subcomponents.

Each spatial stream may then be provided to a different antenna <NUM> via a separate transmitter 918TX. Each transmitter 918TX may modulate an RF carrier with a respective spatial stream for transmission.

At the UE <NUM>, each receiver 954RX receives a signal through its respective antenna <NUM>. Each receiver 954RX recovers information modulated onto an RF carrier and provides the information to the receive (RX) processor <NUM>. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal.

The spatial streams generated by the TX processor <NUM> may be provided to different antenna <NUM> via separate transmitters 954TX. Each transmitter 954TX may modulate an RF carrier with a respective spatial stream for transmission.

Each receiver 918RX receives a signal through its respective antenna <NUM>. Each receiver 918RX recovers information modulated onto an RF carrier and provides the information to a RX processor <NUM>.

At least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM> may be configured to perform aspects in connection with SPS component <NUM> of UE <NUM> in <FIG>.

At least one of the TX processor <NUM>, the RX processor <NUM>, and the controller/processor <NUM> may be configured to perform aspects in connection with SPS component <NUM> of base station <NUM> in <FIG>.

Claim 1:
A method of wireless communication for a user equipment, UE, comprising:
receiving (<NUM>), by the UE, an activation/reactivation downlink control information, DCI, from a base station, the activation/reactivation DCI including an update to a periodically-occurring scheduling, wherein an absolute time for the update to take effect is specified in a radio resource control, RRC, configuration of the activation/reactivation DCI; and
applying (<NUM>) the update to the periodically-occurring scheduling for communications of the UE beginning at and following the absolute time, wherein the periodically-occurring scheduling comprises a semi-persistent scheduling, SPS, or configured grant, CG, parameter, wherein the absolute time is common to a group of UEs including the UE, wherein updates to one or more SPS or CG parameters of the group of UEs take effect simultaneously at the absolute time.