SPS SCHEDULING

The PDCCH carries all allocation information for both the PDSCH and PUSCH respectively.Since the PDCCH
is limited size (generally, 3 OFDM symbol times), there is a limit as to how many DCIs can be carried in a
subframe (1 ms),which limit the number of UEs receiving allocation in 1ms. To support more allocations,
without increasing the size of the PDCCH, we can use semi-persistent scheduling (SPS).UE is pre-
configured by the eNB with an SPS-RNTI (allocation ID) and a periodicity. Once pre-configured, if the UE
were to receive an allocation (DL / UL) using the SPS-RNTI (instead of the typical C-RNTI).During SPS,
certain things remain fixed for each allocation : RB assignments, Modulation and Coding Scheme, etc.
Because of this, if the radio link conditions change, a new allocation will have to be sent.When a data
transfer is completed, there are several mechanisms for deactivating SPS (explicit, inactivity timer, etc.).
Procedures in SPS:• Configuration
• Activation • Transmission • Release

SPS CONFIGURATION

The eNB can configure the UE with SPS at any time but, typically
: dedicated bearer establishment for the VoIP service

SPS can be configured/re-configured by RRC at any time using SPS-Config. This SPS-Config includes the
configuration for semiPersistSchedC-RNTI (sps-CRNTI), sps-ConfigDL and sps-ConfigUL.SPS can be
configured in only uplink/downlink or both.

The eNB has to explicitly activate SPS as explained below, in order for the UE to use SPS
grants/assignments.eNB first configures the UE with SPS and then activates the same.

SPS ACTIVATION
Soon after the UE is configured with SPS C-RNTI, the UE is configured by higher layers to decode PDCCH
with CRC scrambled by the SPS C-RNTI.
A UE shall monitor PDCCH with CRC scrambled by the SPS C-RNTI in every subframe as the eNB can
activate/re-activate/release SPS at any time using Downlink control information .

DCI0 - activate/release SPS in UL

DCI Format 1/1A/2/2A/2B/2C - activate SPS in DL
DCI1A – release SPS in DL.

Received DCI format on SPS C-RNTI can be a grant/assignment for a retransmission or for
activation/re-activation/release of SPS.

A UE shall validate a SPS assignment PDCCH only if all the following conditions are met:
· the CRC parity bits obtained for the PDCCH payload are scrambled with the SPS C-RNTI
· the new data indicator field is set to ‘0’. In case of DCI formats 2, 2A, 2B and 2C, the new data indicator
field refers to the one for the enabled transport block
Validation is achieved if all the fields for the respective used DCI format are set according to Table 9.2-1
or Table 9.2-1A. If validation is achieved, the UE shall consider the received DCI information accordingly
as a valid SPS activation or release. If validation is not achieved, the received DCI format shall be
considered by the UE as having been received with a non-matching CR

Over-Riding SPS Resources:

When the resource allocation information masked by CRNTI is received in the subframe marked
for SPS data, The UE uses the radio resource indicated by dynamic scheduling at that subframe
and does not use the radio resource configured by SPS. The radio resource for SPS is over-ride by
dynamic scheduling.
5.10 Semi-Persistent Scheduling
When Semi-Persistent Scheduling is enabled by RRC, the following information is provided [8]:

ETSI
ETSI TS 136 321 V12.5.0 (2015-04)383GPP TS 36.321 version 12.5.0 Release 12
- Semi-Persistent Scheduling C-RNTI;
- Uplink Semi-Persistent Scheduling interval semiPersistSchedIntervalUL and number of empty
transmissions before implicit release implicitReleaseAfter, if Semi-Persistent Scheduling is enabled for the
uplink;
- Whether twoIntervalsConfig is enabled or disabled for uplink, only for TDD;
- Downlink Semi-Persistent Scheduling interval semiPersistSchedIntervalDL and number of configured
HARQ processes for Semi-Persistent Scheduling numberOfConfSPS-Processes, if Semi-Persistent
Scheduling is enabled for the downlink;
When Semi-Persistent Scheduling for uplink or downlink is disabled by RRC, the corresponding configured
grant or configured assignment shall be discarded.
Semi-Persistent Scheduling is supported on the SpCell only.
Semi-Persistent Scheduling is not supported for RN communication with the E-UTRAN in combination with
an RN subframe configuration.
NOTE: When eIMTA is configured for the SpCell, if a configured uplink grant or a configured downlink
assignment occurs on a subframe that can be reconfigured through eIMTA L1 signalling, then the UE
behaviour is left unspecified.
5.10.1 Downlink
After a Semi-Persistent downlink assignment is configured, the MAC entity shall consider sequentially that
the Nth assignment occurs in the subframe for which:
- (10 * SFN + subframe) = [(10 * SFNstart time + subframestart time) + N * semiPersistSchedIntervalDL]
modulo 10240.
Where SFNstart time and subframestart time are the SFN and subframe, respectively, at the time the
configured downlink assignment were (re-)initialised.
5.10.2 Uplink
After a Semi-Persistent Scheduling uplink grant is configured, the MAC entity shall:
- if twoIntervalsConfig is enabled by upper layer:
- set the Subframe_Offset according to Table 7.4-1.
- else:
- set Subframe_Offset to 0.
- consider sequentially that the Nth grant occurs in the subframe for which:
- (10 * SFN + subframe) = [(10 * SFNstart time + subframestart time) + N * semiPersistSchedIntervalUL +
Subframe_Offset * (N modulo 2)] modulo 10240.
Where SFNstart time and subframestart time are the SFN and subframe, respectively, at the time the
configured uplink grant were (re-)initialised.
The MAC entity shall clear the configured uplink grant immediately after implicitReleaseAfter [8] number
of consecutive new MAC PDUs each containing zero MAC SDUs have been provided by the Multiplexing
and Assembly entity, on the Semi-Persistent Scheduling resource.
NOTE: Retransmissions for Semi-Persistent Scheduling can continue after clearing the configured uplink
grant

FOR CONFIG REFER 36.331 …pg 248