You are on page 1of 38

LTE MAC Scheduler Interface

Specification v1.11
Femto Forum Technical Document

Document number:
Date issued:
Document status:

FF_Tech_001_v1.11
12-10-2010
Document for public distribution

Legal Notice
Permitted Use of this document
You are permitted to download, use and distribute copies of this document provided that:
(a) you must only use and distribute this document in its entirety without amendment, deletion or addition
of any legal notice, text, graphics or other content; and
(b) you must not make this document available for download on any publically accessible bulletin board,
website, ftp site or file sharing service.
Disclaimer
This document is provided on an as is basis without guarantees, representations, conditions or warranties
as to its accuracy or completeness or that it is free from error. To the extent permitted by law, the Femto
Forum Ltd and the contributors to this document exclude all representations, conditions, warranties and
other terms which might otherwise be implied by statute, common law or the law of equity.
Patents
It is possible that use of the technical matter published in this document may require the permission of the
proprietor of one or more patents. You are entirely response for identifying and where necessary obtaining
a licence under such patents should you choose to use any such technical matter. The Femto Forum Ltd has
no responsibility in this regard and shall not be liable for any loss or damage suffered in relation to an
infringement of any third party patent as a result of such use.
Copyright
This document is subject to copyright owned by the Femto Forum Ltd and/or licensed to the Femto Forum
Ltd by its contributing members. You may use and distribute this document free of charge provided that you
comply with the provisions set out in this notice. Other than this limited licence, you are not granted any
further right, interest or title in this document and the Femto Forum Ltd and/or its contributing members
shall at all times remain the sole owner(s) of the copyright in this document.
Trade Marks
The Femto Forum logo and other logo, trade and service marks contained in this document are the
property of the Femto Forum Ltd and, where applicable, other third parties. You are not permitted to use
or reproduce these marks without the prior written consent of the Femto Forum Ltd or where applicable
the third party owner.

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 2

Table of Contents

1
2
3
4

Table of Contents ........................................................................................................................... 3


Scope ............................................................................................................................................. 5
Interface Overview ......................................................................................................................... 5
Detailed interface description ........................................................................................................ 7
4.1 CSCHED MAC Scheduler Control SAP ........................................................................................ 7
4.1.1
CSCHED_CELL_CONFIG_REQ Parameters ................................................................................ 8
4.1.2
CSCHED_CELL_CONFIG_CNF Parameters .............................................................................. 10
4.1.3
CSCHED_UE_CONFIG_REQ Parameters ................................................................................. 10
4.1.4
CSCHED_UE_CONFIG_CNF Parameters ................................................................................. 11
4.1.5
CSCHED_LC_CONFIG_REQ Parameters.................................................................................. 11
4.1.6
CSCHED_LC_CONFIG_CNF Parameters .................................................................................. 12
4.1.7
CSCHED_LC_RELEASE_REQ Parameters................................................................................. 12
4.1.8
CSCHED_LC_RELEASE_CNF Parameters ................................................................................. 13
4.1.9
CSCHED_UE_RELEASE_REQ Parameters ................................................................................ 13
4.1.10
CSCHED_UE_RELEASE_CNF Parameters ............................................................................ 13
4.1.11
CSCHED_UE_CONFIG_UPDATE_IND Parameters ............................................................... 14
4.1.12
CSCHED_CELL_CONFIG_UPDATE_IND Parameters ............................................................ 14
4.2 SCHED - MAC Scheduler SAP ..................................................................................................... 15
4.2.1
SCHED_DL_RLC_BUFFER_REQ Parameters ............................................................................ 16
4.2.2
SCHED_DL_PAGING_BUFFER_REQ Parameters ..................................................................... 16
4.2.3
SCHED_DL_MAC_BUFFER_REQ Parameters .......................................................................... 17
4.2.4
SCHED_DL_TRIGGER_REQ Parameters .................................................................................. 18
4.2.5
SCHED_DL_RACH_INFO_REQ Parameters ............................................................................. 18
4.2.6
SCHED_DL_CQI_INFO_REQ Parameters ................................................................................ 18
4.2.7
SCHED_DL_CONFIG_IND Parameters .................................................................................... 20
4.2.8
SCHED_UL_TRIGGER_REQ Parameters .................................................................................. 21
4.2.9
SCHED_UL_NOISE_INTERFERENCE_REQ Parameters ............................................................. 21
4.2.10
SCHED_UL_SR_INFO_REQ Parameters .............................................................................. 21
4.2.11
SCHED_UL_MAC_CTRL_INFO_REQ Parameters ................................................................. 22
4.2.12
SCHED_UL_CQI_INFO_REQ Parameters ............................................................................ 22
4.2.13
SCHED_UL_CONFIG_IND Parameters ................................................................................ 22
4.3 Parameters ............................................................................................................................... 23
4.3.1
dlDciListElement ................................................................................................................... 23
4.3.2
ulDciListElement ................................................................................................................... 24
4.3.3
vendorSpecificListElement .................................................................................................... 24
4.3.4
logicalChannelConfigListElement .......................................................................................... 24
4.3.5
addBufferListElement ........................................................................................................... 25
4.3.6
rachListElement .................................................................................................................... 25
4.3.7
phichListElement .................................................................................................................. 25
4.3.8
buildDataListElement............................................................................................................ 25
4.3.9
rlcPDU_ListElement .............................................................................................................. 26
4.3.10
buildRAR_ListElement ....................................................................................................... 26
4.3.11
buildBroadcastListElement................................................................................................ 26
4.3.12
ulInfoListElement .............................................................................................................. 26
4.3.13
srListElement .................................................................................................................... 27
4.3.14
macCE_ListElement........................................................................................................... 27

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 3

4.3.15
macCE_Value .................................................................................................................... 27
4.3.16
drxConfig .......................................................................................................................... 27
4.3.17
spsConfig .......................................................................................................................... 28
4.3.18
srRequest.......................................................................................................................... 28
4.3.19
cqiRequest ........................................................................................................................ 28
4.3.20
ue_Capabilities ................................................................................................................. 29
4.3.21
siConfiguration ................................................................................................................. 29
4.3.22
siMessageListElement ....................................................................................................... 29
4.3.23
dlInfoListElement .............................................................................................................. 29
4.3.24
cqiListElement .................................................................................................................. 30
4.3.25
sbMeasResult ................................................................................................................... 30
4.3.26
ueSelected ........................................................................................................................ 30
4.3.27
higherLayerSelected ......................................................................................................... 30
4.3.28
bwPart .............................................................................................................................. 31
4.3.29
ulCQI................................................................................................................................. 31
4.3.30
pagingInfoListElement ...................................................................................................... 31
4.4 Constants ................................................................................................................................. 31
5
Scenarios ...................................................................................................................................... 32
5.1 Cell Setup ................................................................................................................................. 32
5.2 RACH procedure ....................................................................................................................... 34
5.3 UE configuration ....................................................................................................................... 35
5.4 Radio Bearer Setup ................................................................................................................... 35
5.5 Handling of logical channel buffer status .................................................................................. 35
5.6 DRB release .............................................................................................................................. 35
5.7 UE release ................................................................................................................................ 36
5.8 UE configuration update by MAC scheduler .............................................................................. 36
5.9 Scheduler Subframe flow .......................................................................................................... 37
6
References ................................................................................................................................... 37
7
Revision History............................................................................................................................ 37
8
Appendix A: Performance and Functional Requirements for the LTE Femtocell Scheduler API ..... 38

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 4

Scope

This document specifies the MAC Scheduler interface. The goal of this interface specification is to allow
the use of a wide range of schedulers which can be plugged into the eNodeB and to allow for standardized
interference coordination interface to the scheduler.

Interface Overview

The MAC scheduler is part of MAC from a logical view and the MAC scheduler should be independent
from the PHY interface.
The description in this interface does not foresee any specific implementation of the interface. What is
specified in this document is the structure of the parameters. In order to describe the interface in detail the
following model is used:
The interface is defined as a service access point offered by the MAC scheduler to the remaining MAC
functionality, as shown in Figure 1. A _REQ primitive is from MAC to the MAC scheduler. A _IND/_CNF
primitives are from the MAC scheduler to the MAC. The description using primitives does not foresee any
specific implementation and is used for illustration purposes. Therefore an implementation could be
message-based or function-based interface. Timing constrains applicable to the MAC scheduler are not yet
specified.
For the MAC scheduler interface specification a push-based concept is employed, that is all parameters
needed by the scheduler are passed to the scheduler at specific times rather than using a pull-based concept
(i.e. fetching the parameters from different places as needed). The parameters specified are as far as
possible aligned with the 3GPP specifications

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 5

Data flow
Control flow
RRC/RRM/OAM

RLC

CMAC SAP

MAC SAP

MAC

Control

CSCHED SAP
Scheduler
DL

Cell Cfg
UE Cfg
LC Cfg

PDCCH/
RACH
UL

HARQ
sched
cfg

Subframe

SCHED SAP

PHY SAP
PHY

Figure 1: MAC scheduler interface overview

Figure 1 shows the functionality split between the MAC scheduler and the remaining MAC. For the
purposes of describing the MAC scheduler interface the MAC consists of a control block and a subframe
block, which uses the CSCHED and SCHED SAP respectively. The subframe block triggers the MAC scheduler
every TTI and receives the scheduler results. The control block forwards control information to the MAC
scheduler as necessary. The scheduler consists of the following blocks:
UL
Is responsible for scheduling of the PUSCH resources.
DL
Is responsible for scheduling of the PDSCH resources.
PDCCH/RACH Is responsible for shared resources between UL and DL.
HARQ
Is responsible for handling HARQ retransmissions, keeping track of the number of
retransmissions and redundancy versions.
Cell Cfg
Stores the UE configuration needed by the MAC scheduler.

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 6

UE Cfg
LC Cfg
Sched Cfg

Stores the UE configuration needed by the MAC scheduler.


Stores the logical channel configuration needed by the MAC scheduler.
Stores the scheduler-specific configuration needed by the MAC scheduler.

Detailed interface description

In the following section the messages exchanged at the SAPs are specified.

4.1

CSCHED MAC Scheduler Control SAP

Table 1 specifies which configuration messages can be used to configure the scheduler.
There is no restriction on the timing of when these messages can be sent, except where otherwise noted in
the message description. The RNTI and, if available, the LCID are used to identity the UE/LC between the
MAC scheduler and the MAC. In case of a reconfiguration message all parameters previously configured in a
message have to be resend, otherwise parameters not present are removed in the scheduler (i.e. no delta
configuration is possible)
Primitive name

Reference

Description

CSCHED_CELL_CONFIG_REQ

4.1.1

(re-)configure MAC scheduler with cell


configuration and scheduler
configuration. The cell configuration will
also setup the BCH, BCCH, PCCH and
CCCH LC configuration.

CSCHED_CELL_CONFIG_CNF

4.1.2

Cell configuration and scheduler


configuration applied

CSCHED_UE_CONFIG_REQ

4.1.3

(re-)configure MAC scheduler with UE


specific parameters. A UE can only be
configured when a cell configuration has
been received.

CSCHED_UE_CONFIG_CNF

4.1.4

UE specific configuration applied

CSCHED_LC_CONFIG_REQ

4.1.5

(re-)configure MAC scheduler with logical


channel configuration. A logical channel
can only be configured when a UE
configuration has been received.

CSCHED_LC_CONFIG_CNF

4.1.6

Logical channel configuration applied

CSCHED_LC_RELEASE_REQ

4.1.7

release a logical channel in the MAC


scheduler. A logical channel can only be
released if it has been configured
previously.

CSCHED_LC_RELEASE_CNF

4.1.8

Logical Channel specific configuration


removed

CSCHED_UE_RELEASE_REQ

4.1.9

release a UE in the MAC scheduler. The


release of the UE configuration implies
the release of LCs, which are still active. A
UE can only be released if it has been
configured previously.

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 7

CSCHED_UE_RELEASE_CNF

4.1.10

UE specific configuration removed

CSCHED_UE_CONFIG_UPDATE_IND

4.1.11

update of UE specific parameters from


MAC scheduler to RRC

CSCHED_CELL_CONFIG_UPDATE_IND

4.1.12

update of ctrl channel configuration from


MAC scheduler to RRC

Table 1: CSCHED primitives

4.1.1 CSCHED_CELL_CONFIG_REQ Parameters

Elements

Value

Type

Description

pusch_HoppingOffset

0..98

uint8_t

PUSCH resources in
RBs. used for
hopping. see [2]
section 5.3.4

hoppingMode

inter, interintra

enum

see [2] section


5.3.4

n_SB

1,2,3,4

uint8_t

number of
subbands. see [2]
section 5.3.4

phichResource

PHICH_R_ONE_SIXTH,
PHICH_R_HALF,
PHICH_R_ONE,
PHICH_R_TWO

enum

The number of
resources element
groups used for
PHICH.

phichDuration

normal, extended

enum

initialNrOf_PDCCH_OFDM_Symbols

0..4

uint8_t

see [2] table 6.9.31


Nr of PDCCH OFDM
symbols. see [2]
section 6.9

siConfiguration

see section 4.3.21

struct

The SI
configuration

ul_Bandwidth

6,15,25,50,75,100

uint8_t

UL transmission
bandwidth in RBs

dl_Bandwidth

6,15,25,50,75,100

uint8_t

DL transmission
bandwidth in RBs

ul_CyclicPrefixLength

normal, extended

enum

dl_CyclicPrefixLength
antennaPortsCount

normal, extended
1,2,4

enum
uint8_t

see [2] section


5.2.1
DL cyclic prefix.
Number of cell
specific antenna
ports. see [2]
section 6.2.1

duplexMode

DM_TDD, DM_FDD

enum

Cell is configured in
TDD or FDD mode.

subframeAssignment

0..6

uint8_t

DL/UL subframe

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 8

assignment. Only
TDD. see [2] table
4.2.2
specialSubframePatterns

0..8

uint8_t

TDD configuration.
Only TDD. see [2]
table 4.2.1

mbsfn_SubframeConfigPresent

TRUE, FALSE

bool

Indicates if the
following mbsfn_
fields are valid or
not.

mbsfn_SubframeConfig_RFPeriod

1,2,4,8,16.32

uint8_t

The MBSFN radio


frame period

mbsfn_SubframeConfig_RFOffset
[MAX_MBSFN_CONFIG]

0..7

uint8_t

The radio frame


offset

mbsfn_SubframeConfig_SFallocation
[MAX_MBSFN_CONFIG]

bitmap 0..9

uint8_t

Indicates the
MBSFN subframes

prachConfigurationIndex

0..63

uint8_t

see [2] section


5.7.1

prach_FreqOffset

0..94

uint8_t

see [2] section


5.7.1

ra_ResponseWindowSize

2..8,10

uint8_t

Duration of RA
response window
in SF. see [1]

mac_ContentionResolutionTimer

8,16,24,32,40,48,56,64

uint8_t

Contention
resolution timer
used during
random access. see
[1].

maxHARQ_Msg3Tx

1..8

uint8_t

see [1]

n1PUCCH_AN
deltaPUCCH-Shift
nRB_CQI
nCS_AN
srsSubframeConfiguration

0..2047
1..3
0..98
0..7
0..15

uint16_t
uint8_t
uint8_t
uint8_t
uint8_t

see [4] section 10.1


see [2] section 5.4
see [2] section 5.4
see [2] section 5.4
see [2] table
5.5.3.3-1 and
5.5.3.3-2

srsSubframeOffset

0..9

uint8_t

see [2] section


5.5.3.2

srsBandwidthConfiguration

0..7

uint8_t

SRS bandwidth. see


[2] section 5.5.3.2

srsMaxUpPts

TRUE, FALSE

bool

see [2] section


5.5.3.2. Only TDD

enable64QAM

MOD_16QAM,
MOD_64QAM

enum

maximum UL
modulation
supported. see [4]
section 8.6.1.

[MAX_MBSFN_CONFIG]

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 9

nr_vendorSpecificList

0..MAX_SCHED_CFG_LIST

vendorSpecificList

uint8_t

The number of
elements in the
next array

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

Contains scheduler
specific
configuration
received from the
OAM subsystem
for use by a specific
scheduler.

4.1.2 CSCHED_CELL_CONFIG_CNF Parameters


Elements

Value

Type

Description

result
nr_vendorSpecificList

SUCCESS, FAILURE
0..MAX_SCHED_CFG_LIST

enum
uint8_t

The outcome of the request


The number of elements in the
next array
Contains scheduler specific
configuration received from the
OAM subsystem for use by a
specific scheduler.

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

4.1.3 CSCHED_UE_CONFIG_REQ Parameters


Elements

Value

Type

rnti
reconfigureFlag

1..65535
TRUE, FALSE

uint16_t
bool

drxConfigPresent

TRUE, FALSE

bool

drxConfig
timeAlignmentTimer

see 4.3.16
500,750,1280,1920,2560,5120
,10240,inf

struct
uint16_t

measGapConfigPattern

MGP_GP1, MGP_GP2, OFF

enum

measGapConfigSubframeOffs
et
spsConfigPresent

0..79

uint8_t

TRUE, FALSE

bool

spsConfig
srConfigPresent
srConfig
cqiConfigPresent
cqiConfig
transmissionMode

see 4.3.17
TRUE, FALSE
see 4.3.18
TRUE, FALSE
see 4.3.19
1..7

struct
bool
struct
bool
struct
uint8_t

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 10

Description
The RNTI identifying the UE.
Indicates if this is a reconfiguration for
an existing UE or if a new UE is added.
Indicates if the drx sub-structure is
valid or not.
The DRX configuration
in subframes. see[1]. Used for
controlling synchronization status of
the UE, not for the actual timing
advance procedure.
Specifies the measurement gap
configuration or that it is not
applicable. see 3GPP TS 36.133
Specifies the measurement gap offset,
if applicable. see 3GPP TS 36.133
Indicates if the next sub-structure is
valid or not
The SPS configuration
Inidicates if srConfig struct is present
The SR configuration request
Inidicates if cqiConfig struct is present
The CQI configuration request
The configured transmission mode. see

[4] section 7.1


aggregated bit rate of non-gbr bearer
per UE. see 3GPP TS 36.413
aggregated bit rate of non-gbr bearer
per UE. see 3GPP TS 36.413

ue_AggregatedMaximumBitr
ateUL
ue_AggregatedMaximumBitr
ateDL

0..10000000000

uint64_t

0..10000000000

uint64_t

ue_Capabilities
ue_TransmitAntennaSelectio
n
ttiBundling
maxHARQ_Tx

see 4.3.20
none, openLoop, closedLoop

struct
enum

The UE capabilities
see [4] section 8.7

TRUE, FALSE
1..8,10,12,16,20,24, 28

bool
uint8_t

betaOffset_ACK_Index
betaOffset_RI_Index
betaOffset_CQI_Index
ackNackSRS_SimultaneousTr
ansmission
simultaneousAckNackAndCQI
aperiodicCQI_RepMode

0..15
0..15
0..15
TRUE, FALSE

uint8_t
uint8_t
uint8_t
bool

see [1]
The maximum HARQ retransmission for
uplink HARQ. see [1].
see [4] table 8.6.3-1
see [4] table 8.6.3-2
see [4] table 8.6.3-3
see [4] section 8.2

TRUE, FALSE
rm12, rm20,rm22, rm30,
rm31, None

bool
enum

see [4] section 10.1


Reporting mode for aperiodic CQI. see
[4] section 7.2.1

tdd_AckNackFeedbackMode
ackNackRepetitionFactor

bundling,multiplexing
0,2,4,6

enum
uint8_t

nr_vendorSpecificList

0..MAX_SCHED_CFG_LIST

uint8_t

see [3] section 7.3. Only TDD


see [4] section 10.1. 0 means no
repetition
The number of elements in the next
array
Contains scheduler specific
configuration received from the OAM
subsystem for use by a specific
scheduler.

vendorSpecificList

A variablelength array
of variablelength
vendorSpecifi
cListElement
see 4.3.3

4.1.4 CSCHED_UE_CONFIG_CNF Parameters


Elements

Value

Type

Description

rnti
result
nr_vendorSpecificList

1..65535
SUCCESS, FAILURE
0..MAX_SCHED_CFG_LIST

uint16_t
Enum
uint8_t

The RNTI identifying the UE.


The outcome of the request
The number of elements in the
next array
Contains scheduler specific
configuration received from the
OAM subsystem for use by a
specific scheduler.

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

4.1.5 CSCHED_LC_CONFIG_REQ Parameters

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 11

Elements

Value

Type

Description

rnti

1..65535

uint16_t

reconfigureFlag

TRUE, FALSE

bool

nr_logicalChannelConfigList

1..MAX_LC_LIST

uint8_t

logicalChannelConfigList
[MAX_LC_LIST]

An array of
LogicalChannel
ConfigListElement see
4.3.4
0..MAX_SCHED_CFG_LIST

array of struct

The RNTI identifying the


UE.
Indicates if this is a
reconfiguration for an
existing UE or if a new
UE is added.
The number of array
elements.
The array of logical
channel configurations
to be configured.

nr_vendorSpecificList

uint8_t

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

The number of elements


in the next array
Contains scheduler
specific configuration
received from the OAM
subsystem for use by a
specific scheduler.

4.1.6 CSCHED_LC_CONFIG_CNF Parameters


Elements

Value

Type

Description

rnti

1..65535

uint16_t

result

SUCCESS, FAILURE

enum

nr_logicalChannelIdentity

1..MAX_LC_LIST

uint8_t

logicalChannelIdentity
[MAX_LC_LIST]

An array of integers with


range 1..10

array of uint8_t

nr_vendorSpecificList

0..MAX_SCHED_CFG_LIST

uint8_t

The RNTI identifying the


UE.
The outcome of the
request
The number of array
elements.
The array of logical
channel ID which have
been
configured/updated.
The number of elements
in the next array
Contains scheduler
specific configuration
received from the OAM
subsystem for use by a
specific scheduler.

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

4.1.7 CSCHED_LC_RELEASE_REQ Parameters


Elements

Value

Type

Description

rnti
nr_logicalChannelIdentity
logicalChannelIdentity

1..65535
1..MAX_LC_LIST
An array of integers with

uint16_t
uint8_t
array of uint8_t

The RNTI identifying the UE.


The number of array elements.
The array of logical channel ID

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 12

[MAX_LC_LIST]
nr_vendorSpecificList

range 1..10
0..MAX_SCHED_CFG_LIST

which shall be released.


The number of elements in the
next array
Contains scheduler specific
configuration received from the
OAM subsystem for use by a
specific scheduler.

uint8_t

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

4.1.8 CSCHED_LC_RELEASE_CNF Parameters


Elements

Value

Type

Description

rnti
result
nr_LogicalChannelIdentity
logicalChannelIdentity
[MAX_LC_LIST]
nr_vendorSpecificList

1..65535
SUCCESS, FAILURE
1..MAX_LC_LIST
An array of integers with
range 1..10
0..MAX_SCHED_CFG_LIST

uint16_t
enum
uint8_t
array of uint8_t

The RNTI identifying the UE.


The outcome of the request
The number of array elements.
The array of logical channel ID
which have been released.
The number of elements in the
next array
Contains scheduler specific
configuration received from the
OAM subsystem for use by a
specific scheduler.

vendorSpecificList

uint8_t
A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

4.1.9 CSCHED_UE_RELEASE_REQ Parameters


Elements

Value

Type

Description

rnti
nr_vendorSpecificList

1..65535
0..MAX_SCHED_CFG_LIST

uint16_t
uint8_t

The RNTI identifying the UE.


The number of elements in the next
array
Contains scheduler specific
configuration received from the
OAM subsystem for use by a
specific scheduler.

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see4.3.3

4.1.10 CSCHED_UE_RELEASE_CNF Parameters


Elements

Value

Type

Description

rnti
result
nr_vendorSpecificList

1..65535
SUCCESS, FAILURE
0..MAX_SCHED_CFG_LIST

uint16_t
enum
uint8_t

The RNTI identifying the UE.


The outcome of the request
The number of elements in the next
array
Contains scheduler specific
configuration received from the OAM
subsystem for use by a specific
scheduler.

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 13

4.1.11 CSCHED_UE_CONFIG_UPDATE_IND Parameters


Elements

Value

Type

Description

rnti
transmissionMode

1..65535
1..7

uint16_t
uint8_t

spsRequestPresent

TRUE, FALSE

bool

spsRequest
srRequestPresent

see 4.3.17
TRUE, FALSE

struct
bool

srRequest
cqiRequestPresent

see 4.3.18
TRUE, FALSE

struct
bool

cqiRequest
nr_vendorSpecificL
ist
vendorSpecificList

see 4.3.19
0..MAX_SCHED_CFG_LIST

struct
uint8_t

The RNTI identifying the UE.


The configured transmission mode.
see [4] section 7.1
Inidicates if spsRequest struct is
present
The SPS configuration request
Inidicates if srRequest struct is
present
The SR configuration request
Inidicates if cqiRequest struct is
present
The CQI configuration request
The number of elements in the next
array
Contains scheduler specific
configuration received from the
OAM subsystem for use by a specific
scheduler.

A
variablelength
array of
variablelength
vendorSp
ecificList
Element
see 4.3.3

4.1.12 CSCHED_CELL_CONFIG_UPDATE_IND Parameters


Elements

Value

Type

Description

prbUtilizationDL
prbUtilizationUL
nr_vendorSpecificList

0..100
0..100
0..MAX_SCHED_CFG_LIST

uint8_t
uint8_t
uint8_t

Percentage as defined in 36.314


Percentage as defined in 36.314
The number of elements in the next
array
Contains scheduler specific
configuration received from the OAM
subsystem for use by a specific
scheduler.

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 14

4.2

SCHED - MAC Scheduler SAP

Primitive name

Reference

Description

SCHED_DL_RLC_BUFFER_REQ

4.2.1

update buffer status of logical channel data in


RLC. The update rate with which the buffer status
is updated in the scheduler is outside of the scope
of the document.

SCHED_DL_PAGING_BUFFER_REQ

4.2.2

update buffer status of paging messages.

SCHED_DL_MAC_BUFFER_REQ

4.2.3

update buffer status of MAC control elements.


The update rate with which the buffer status is
updated in the scheduler is outside of the scope
of the document.

SCHED_DL_TRIGGER_REQ

4.2.4

Starts the DL MAC scheduler for this subframe

SCHED_DL_RACH_INFO_REQ

4.2.5

Provides RACH reception information to the


scheduler

SCHED_DL_CQI_INFO_REQ

4.2.6

Provides CQI measurement report information to


the scheduler

SCHED_DL_CONFIG_IND

4.2.5

triggers building of DL MAC PDUs and Subframe


Configuration in MAC

SCHED_UL_TRIGGER_REQ

4.2.8

Starts the UL MAC scheduler for this subframe

SCHED_UL_NOISE_INTERFERENCE_REQ 4.2.9

Provides Noise and interference measurement


information to the scheduler

SCHED_UL_SR_INFO_REQ

4.2.10

Provides scheduling request reception


information to the scheduler

SCHED_UL_MAC_CTRL_INFO_REQ

4.2.11

Provides mac control information (power


headroom, ul buffer status) to the scheduler

SCHED_UL_CQI_INFO_REQ

4.2.12

Provides UL CQI measurement information to the


scheduler

SCHED_UL_CONFIG_IND

4.2.9

passes the UL scheduling decision (Format 0 DCIs)


to MAC
Table 2 SCHED SAP

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 15

4.2.1 SCHED_DL_RLC_BUFFER_REQ Parameters


Elements

Value

Type

Description

rnti

1..65535

uint16_t

logicalChannelIdentity

0..10

uint8_t

rlc_TransmissionQueueSize

0..4294967295

uint32_t

rlc_TransmissionQueueHOL_Delay

0..65535

uint16_t

rlc_RetransmissionQueueSize

0..4294967295

uint32_t

rlc_RetransmissionHOL_Delay

0..65535

uint16_t

rlc_StatusPDU_Size

0..65535

uint16_t

nr_vendorSpecificList

0..MAX_SCHED_CFG_LIST

uint8_t

The RNTI identifying


the UE.
The logical channel ID.
see [1].
The current size of the
transmission queue in
byte
Head of line delay of
new transmissions in
ms
The current size of the
retransmission queue
in byte
Head of line delay of
retransmissions in ms
The current size of the
pending STATUS
message in byte
The number of
elements in the next
array
Contains scheduler
specific configuration
received from the OAM
subsystem for use by a
specific scheduler.

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see4.3.3

4.2.2 SCHED_DL_PAGING_BUFFER_REQ Parameters


Elements

Value

nr_pagingInfoList

0..MAX_PAGING_LIST

pagingInfoList[nr_pagingInfoList]

A variable-length array of
pagingInfoListElement
0..MAX_SCHED_CFG_LIST

nr_vendorSpecificList

vendorSpecificList

Type

Description

uint8_t

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 16

Valid only if rnti==PRNTI


Valid only if rnti==PRNTI
The number of
elements in the next
array
Contains scheduler
specific configuration
received from the OAM
subsystem for use by a
specific scheduler.

4.2.3 SCHED_DL_MAC_BUFFER_REQ Parameters


Elements

Value

Type

Description

rnti

1..65535

uint16_t

ceBitmap

TA, DRX, CR

uint8_t
bitmap

nr_vendorSpecificList

0..MAX_SCHED_CFG_LIST

uint8_t

The RNTI identifying the UE. TODO


add paging depends on CCPU
comment 15.
The CE element which is scheduled
to be sent by the MAC. Can be
Timing Advance CE, DRX Command
CE and Contention Resolution CE.
The number of elements in the next
array

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see4.3.3

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 17

Contains scheduler specific


configuration received from the
OAM subsystem for use by a
specific scheduler.

4.2.4 SCHED_DL_TRIGGER_REQ Parameters


Elements

Value

Type

Description

sfn_sf

0..16377
bit 0-3 SF
bit 4-13 SFN
0..MAX_DL_INFO_LIST

uint16_t

The SFN and SF for which the


scheduling is to be done.

uint8_t

An variable-length array
of dlInfoListElement. See
4.3.23
0..MAX_SCHED_CFG_LIST

array of struct

The number of elements in the UE


DL information list
The list of UE DL information.

nr_dlInfoList
dlInfoList
[nr_dlInfoList]
nr_vendorSpecificList
vendorSpecificList

uint8_t
A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

The number of elements in the


next array
Contains scheduler specific
configuration received from the
OAM subsystem for use by a
specific scheduler.

4.2.5 SCHED_DL_RACH_INFO_REQ Parameters


Elements

Value

Type

Description

sfn_sf

0..16377
bit 0-3 SF
bit 4-13 SFN
0..MAX_RACH_LIST

uint16_t

The SFN and SF in which the


information was received

uint8_t

A variable-length array of
rachListElement. See
4.3.6
0..MAX_SCHED_CFG_LIST

array of struct

The number of elements in the RACH


list
The list of detected RACHs

nr_rachList
rachList [nr_rachList]

nr_vendorSpecificList
vendorSpecificList

uint8_t
A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

The number of elements in the next


array
Contains scheduler specific
configuration received from the OAM
subsystem for use by a specific
scheduler.

4.2.6 SCHED_DL_CQI_INFO_REQ Parameters


Elements

Value

Type

Description

sfn_sf

0..16377
bit 0-3 SF
bit 4-13 SFN
0..MAX_CQI_LIST

uint16_t

The SFN and SF in which the


information was received

uint8_t

The number of CQI reports.

A variable-length array of
cqiListElement. See
4.3.24

array of struct

The list of DL CQI reports received in


one subframe.

nr_cqiList
cqiList[nr_cqiList]

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 18

nr_vendorSpecificList
vendorSpecificList

0..MAX_SCHED_CFG_LIST

uint8_t
A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 19

The number of elements in the next


array
Contains scheduler specific
configuration received from the OAM
subsystem for use by a specific
scheduler.

4.2.7 SCHED_DL_CONFIG_IND Parameters


Elements

Value

Type

Description

nr_buildDataList

0.. MAX_BUILD_DATA_LIST

uint8_t

nr_buildRAR_List

0.. MAX_BUILD_RAR_LIST

uint8_t

nr_buildBroadcastList

0.. MAX_BUILD_BC_LIST

uint8_t

buildDataList
[nr_buildDataList]

array of struct

nrOf_PDCCH_OFDM_Symbols

A variable-length array of
buildDataListElement. See
4.3.8
A variable-length array of
buildRAR_ListElement. See
4.3.10
A variable-length array of
buildBroadcastListElement.
See 4.3.11
0..4

The number of elements in the


buildData list
The number of elements in the
buildRAR list
The number of elements in the
buildBroadcastList.
Applicable for BCCH, PCCH
The list of resource allocation for
UEs and LCs.

nr_vendorSpecificList

0..MAX_SCHED_CFG_LIST

buildRAR_List
[nr_buildRAR_List]
buildBroadcastList
[nr_buildBroadcastList]

vendorSpecificList

array of struct

The list of resource allocation for


RAR

array of struct

The list of resource allocation for


BCCH, PCCH

uint8_t

current size of PDCCH

uint8_t

The number of elements in the


next array
Contains scheduler specific
configuration received from the
OAM subsystem for use by a
specific scheduler.

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 20

4.2.8 SCHED_UL_TRIGGER_REQ Parameters


Elements

Value

Type

Description

sfn_sf

0..16377
bit 0-3 SF
bit 4-13 SFN
0.. MAX_ULINFO_LIST
A variable-length array of
ulInfoListElement. See 4.3.12
0..MAX_SCHED_CFG_LIST

uint16_t

The SFN and SF for which the


scheduling is to be done.

uint8_t
array of
struct
uint8_t

number of UL information elements


The list of UL information for the
scheduler.
The number of elements in the next
array
Contains scheduler specific
configuration received from the OAM
subsystem for use by a specific
scheduler.

nr_ulInfoList
ulInfoList [nr_ulInfoList]
nr_vendorSpecificList
vendorSpecificList

A variablelength
array of
variablelength
vendorSpe
cificListEle
ment see
4.3.3

4.2.9 SCHED_UL_NOISE_INTERFERENCE_REQ Parameters


Elements

Value

Type

Description

sfn_sf

uint16_t

The SFN and SF in which the


information was received

rip

0..16377
bit 0-3 SF
bit 4-13 SFN
-126.0..-75.0

tnp

-146.0..-75

nr_vendorSpecificList

0..MAX_SCHED_CFG_LIST

uint16_t. fixed point


SXXXXXXX.XXXXXXXX
uint16_t fixed point
SXXXXXXX.XXXXXXXX
uint8_t

Received Interference Power. See


36.214. in dBm.
Thermal Noise Power. See 36.214. in
dBm
The number of elements in the next
array
Contains scheduler specific
configuration received from the
OAM subsystem for use by a specific
scheduler.

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

4.2.10 SCHED_UL_SR_INFO_REQ Parameters


Elements

Value

Type

Description

sfn_sf

0..16377
bit 0-3 SF
bit 4-13 SFN
0..MAX_SR_LIST
A variable-length array of
srListElement. see 4.3.13
0..MAX_SCHED_CFG_LIST

uint16_t

The SFN and SF in which the


information was received

uint8_t
array of struct

The number of SRs received.


The list of SRs received in one
subframe.
The number of elements in the next

nr_srList
srList[nr_srList]
nr_vendorSpecificList

uint8_t

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 21

vendorSpecificList

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

array
Contains scheduler specific
configuration received from the
OAM subsystem for use by a specific
scheduler.

4.2.11 SCHED_UL_MAC_CTRL_INFO_REQ Parameters


Elements

Value

Type

Description

sfn_sf

0..16377
bit 0-3 SF
bit 4-13 SFN
0..MAX_MAC_CE_LIST

uint16_t

The SFN and SF in which the


information was received

uint8_t

A variable-length array of
maCE_ListElement. see
4.3.14
0..MAX_SCHED_CFG_LIST

array of struct

Number of MAC control


elements
The list of MAC control
elements received in one
subframe.
The number of elements in the
next array
Contains scheduler specific
configuration received from
the OAM subsystem for use by
a specific scheduler.

nr_macCE_List
macCE_List[nr_macCE_List]

nr_vendorSpecificList
vendorSpecificList

uint8_t
A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

4.2.12 SCHED_UL_CQI_INFO_REQ Parameters


Elements

Value

Type

Description

sfn_sf

0..16377
bit 0-3 SF
bit 4-13 SFN
see 4.3.29
0..MAX_SCHED_CFG_LIST

uint16_t

The SFN and SF in which the


information was received

ulCqi
nr_vendorSpecificList
vendorSpecificList

Struct
uint8_t
A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

The number of elements in the


next array
Contains scheduler specific
configuration received from
the OAM subsystem for use by
a specific scheduler.

4.2.13 SCHED_UL_CONFIG_IND Parameters


Elements

Value

Type

Description

nr_dciList

0..MAX_DCI_LIST

uint8_t

nr_phichList

0..MAX_PHICH_LIST

uint8_t

dciList [nr_dciList]

A variable-length array of
ulDciListElement. See

array of struct

number of UL DCIs created by the


scheduler
number of PHICH information
created by the scheduler
the list of UL DCI (Format 0)
elements

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 22

phichList
[nr_phichList..
MAX_PHICH_LIST]
nr_vendorSpecificList

4.3.2
A variable-length array of
phichListElement. See
4.3.7
0..MAX_SCHED_CFG_LIST

vendorSpecificList

4.3

array of struct

the list of PHICH elements

uint8_t

The number of elements in the next


array
Contains scheduler specific
configuration received from the
OAM subsystem for use by a specific
scheduler.

A variable-length array of
variable-length
vendorSpecificListElement
see 4.3.3

Parameters
4.3.1 dlDciListElement

Elements

Value

Type

Description

rnti
rb_bitmap
rb_shift
res_alloc
nr_of_tbs
tbs_size [MAX_TB_LIST]

1..65535
32bit bitmap
0,1
0,1,2
1..2
0..

uint16_t
uint32_t
uint8_t
uint8_t
uint8_t
uint16_t

mcs[MAX_TB_LIST]

0..31

uint8_t

ndi[MAX_TB_LIST]
rv[MAX_TB_LIST]
cce_index
aggr_level
precoding_info

uint8_t
uint8_t
uint8_t
uint8_t
uint8_t
enum
int8_t
uint8_t
uint8_t
enum

format of the DCI


see [4] section 5.1.1.1
HARQ process number
only for TDD
see [4] section 7.1.6.3

tb_swap

0..1
0..3
0..88
1,2,4,8
2 antenna_ports: 0..6
4 antenna_ports: 0..50
1,1A,1B,1C,1D,2,2A,2B
-4,-1,0,1,3,4
0..7
1,2,3,4
VRB_DISTRIBUTED,
VRB_LOCALIZED
TRUE, FALSE

The RNTI identifying the UE.


The RBs allocated to the UE
see [4] section 7.1.6.2
type of resource allocation
The number of transport blocks
The size of the transport blocks in
byte
The modulation and coding
scheme of each TB. see[4] section
7.1.7
New data Indicator.
Redundancy version.
CCE index used to send the DCI.
The aggregation level.
Precoding information.

bool

TB to CW swap flag. see [3] section


5.3.3.1.5

sps_release
pdcch_order

TRUE, FALSE
TRUE, FALSE

bool

preamble_index

0..63

uint8_t

prach_mask_index

0..15

uint8_t

n_gap
tbs_idx
dl_power_offset

GAP1, GAP2
2,3
0,1

enum
uint8_t
uint8_t

Indicates if PDCCH is for PDCCH


order.
Preamble index. Only valid if
pdcch_order == TRUE.
PRACH Mask index. Only valid valid
if pdcch_order == TRUE.
The value for N_GAP
The TBS index for Format 1A
For Format 1D. see [4] section

format
tpc
harq_process
dai
vrb_format

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 23

pdcch_power_offset

-6..4

7.1.5
DL PDCCH power boosting in dB

int8_t

4.3.2 ulDciListElement
Elements

Value

Type

rnti
rb_start

1..65535
0..99

uint16_t
uint8_t

rb_len

1..100

uint8_t

tb_size
mcs

2..
0..32

uint16_t
uint8_t

ndi
cce_index
aggr_level
ue_tx_antenna_selection

0..1
0..88
1,2,4,8
0,1,3

uint8_t
uint8_t
uint8_t
uint8_t

hopping
n_2_dmrs
tpc

TRUE, FALSE
0..7
-4,-1,0,1,3,4

bool
uint8_t
int8_t

cqi_request
ul_index
dai
freq_hopping
pdcch_power_offset

TRUE, FALSE
0,1,2,3
1,2,3,4
0..4
-6..4

bool
uint8_t
uint8_t
uint8_t
int8_t

Description

The RNTI identifying the UE.


The start RB allocated to the UE. see [4]
section 8.1
The number of RBs allocated to the UE. see [4]
section 8.1
The size of the transport block in byte
The modulation and coding scheme of each
TB. see[4] section 8.6
New data Indicator.
CCE index used to send the DCI.
The aggregation level.
see [3] section 5.3.3.2. 3 means antenna
selection is off.
Hopping enabled flag. see [4] section 8.4
cyclic shift
Tx power control command. see [4] section
5.1.1.1
aperiodic CQI request flag. see [4] section 7.2.1
UL index. only for TDD
DL assignment index. only for TDD
The frequency hopping bits. see [4] section 8.4
DL PDCCH power boosting in dB

4.3.3 vendorSpecificListElement
Elements

Value

Type

Description

type

PF_WEIGHT1, PF_WEIGHT2,
CQI_AVG_FACTOR, etc.

enum

length
value

unsigned integer
depends on type

uint32_t
struct

Indicating the type of the value. This


types are examples, real types are
implementation specific, examples
are:
PF_WEIGHT1 The first weight used
by a proportional fair scheduler
PF_WEIGHT2 The second weight
used by a proportional fair scheduler
CQI_AVG_FACTOR The factor used
for averaging CQIs in the scheduler.
The length of the actual value
The actual value which will be set

4.3.4 logicalChannelConfigListElement

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 24

Elements

Value

Type

Description

logicalChannelIdentity

1..10

uint8_t

logicalChannelGroup

0..3, 4

uint8_t

direction

enum

qci

DIR_UL, DIR_DL,
DIR_BOTH
QBT_NON_GBR,
QBT_GBR
0..255

e_RAB_MaximumBitrateUL
e_RAB_MaximumBitrateDL
e_RAB_GuaranteedBitrateUL
e_RAB_GuaranteedBitrateDL

0..10000000000
0..10000000000
0..10000000000
0..10000000000

uint64_t
uint64_t
uint64_t
uint64_t

The logical channel id. See [1].


Note: CCCH is preconfigured.
The LC group the LC is mapped to. .
4 means no LCG is associated with
the logical channel.
The direction of the logical
channel.
Guaranteed or non-guaranteed bit
rate bearer
The QCI defined in 3GPP TS 23.203.
The QCI is coded as defined in
36.413, i.e the value indicates one
less than the actual QCI value.
in bit/s. For QBT_GBR only.
in bit/s. For QBT_GBR only.
in bit/s. For QBT_GBR only.
in bit/s. For QBT_GBR only.

qosBearerType

enum
uint8_t

4.3.5 addBufferListElement
Elements

Value

Type

Description

length
timestamp

1..65535
32bit

uint16_t
uint32_t

lengths in bytes
Time packet arrived in PDCP

4.3.6 rachListElement
Elements

Value

Type

Description

rnti
estimatedSize

1..65535
56,144,208,256

uint16_t
uint16_t

The newly allocated t-c-rntis


estimated minimum size of first UL
message in bits, based on received RACH
preamble

4.3.7 phichListElement
Elements

Value

Type

Description

rnti
phich

1..65535
ACK, NACK

uint16_t
enum

The RNTI identifying the UE.


ACK or NACK to be passed to the UE in the
PHICH

4.3.8 buildDataListElement
2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 25

Elements

Value

Type

Description

rnti
dci

1..65535
see section 4.3.1

uint16_t
struct

ceBitmap[MAX_TB_LIST]

TA, DRX, CE

nr_rlcPDU_List

1..MAX_RLC_PDU_LIST

uint8_t
bitmap
uint8_t

rlcPDU_List
[nr_rlcPDU_List][MAX_TB_LIST]

A variable array of
rlcPDU_ListElement. See 4.3.9

array of
struct

The RNTI identifying the UE.


The DL DCI configured for this
UE. This may also indicate
PDCCH order or SPS release or
format 3/3A, in which case there
is no associated PDSCH.
The CEs scheduled for
transmission for this TB
The number of RLC PDUs to be
built
List of parameters for RLC PDU
creation.

4.3.9 rlcPDU_ListElement
Elements

Value

Type

Description

logicalChannelIdentity
size

0..10
1..9420

uint8_t
uint16_t

The logical channel ID. see [1]


Maximum length of RLC PDU in bytes

4.3.10 buildRAR_ListElement
Elements

Value

Type

Description

rnti

1..65535

uint16_t

grant
dci

integer
see 4.3.1

uint32_t
struct

The RNTI identifying the UE (in this case it


is the Temporary C-RNTI).
20 bit UL grant. see [4] section 6.2
The DL DCI configured for this RAR.

4.3.11 buildBroadcastListElement
Elements

Value

Type

Description

type
index

BCCH, PCCH
0..63

enum
uint8_t

dci

see 4.3.1

struct

The type identifying the broadcast message.


The index of the broadcast message. This identifies
which broadcast message (either SIB1, SIx or PCCH)
should be transmitted.
0 SIB1
1..31 SIx
32..63 - PCCH
The DL DCI configured for BCCH and PCCH.

4.3.12 ulInfoListElement

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 26

Elements

Value

Type

Description

rnti
ulReception[MAX_LC_LIST+1]

1..65535
0..65535

uint16_t
uint16_t

receptionStatus

Ok, notOk, NotValid

enum

tpc

-4,-1,0,1,3,4

int8_t

The RNTI identifying the UE.


The amount of data in bytes in the MAC
SDU received in this subframe for the
given logical channel.
NotValid is used when no TB is
expected. Ok/notOk Indicates
successful/unsuccessful reception of UL
TB.
Tx power control command. see [4]
section 5.1.1.1

4.3.13 srListElement
Elements

Value

Type

Description

rnti

1..65535

uint16_t

The RNTI identifying the UE.

4.3.14 macCE_ListElement
Elements

Value

Type

Description

rnti
maCE_Type
maCE_Value

1..65535
BSR, PHR, CRNTI
see 4.3.15

uint16_t
enum
union

The RNTI identifying the UE.


Mac Control Element Type
Field discrimination is based on
maCE_Type

4.3.15 macCE_Value
Elements

Value

Type

Description

phr

0..63,64

uint8_t

The power headroom. see [1] section


6.1.3.6. 64 means no valid PHR is
available.
Indicates that a C-RNTI MAC CE was
received. The value is not used
The value 64 indicates that the buffer
status for this LCG should not to be
updated. Always all 4 LCGs are present.
see [1] 6.1.3.1

crnti

uint8_t

bufferStatus [MAX_NR_LCG]

0..63, 64

uint8_t

4.3.16 drxConfig
Elements

Value

Type

Description

onDurationTimer

1,2,3,4,5,6,8,10,20,30,40,50,60,80,1
00,200
1,2,3,4,5,6,8,10,20,30,40,50,60,80,1

uint8_t

Timer in subframes.
see [1]
Timer in subframes.

drx_InactivityTimer

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

uint16_t

page 27

00,200,300,500,750,1280,1920,256
0
1,2,4,6,8,16,24,33

drx_RetransmissionTimer
longDRX_Cycle
longDRX_CycleStartOffset
shortDRX_Cycle
drxShortCycleTimer

see [1]
uint8_t

10,20,32,40,64,80,128,160,256,320,
512,640,1024,1280,2048,2560
0..2559

uint16_t

2,5,8,10,16,10,21,40,64,80,128,160,
256,320,512,640,OFF
1..16

uint16_t

uint16_t

uint8_t

Timer in subframes.
see [1]
Long DRX cycle in
subframes. see [1]
Long DRX cycle offset.
see [1]
Short DRX cycle in
subframes. see [1]
Timer in subframes.
see [1]

4.3.17 spsConfig
Elements

Value

Type

Description

semiPersistSchedIntervalU
L
semiPersistSchedIntervalD
L
numberOfConfSPS_Proces
ses
n1_PUCCH_AN_Persistent
ListSize

10,20,32,40,64,80,128,160,320,6
40
10,20,32,40,64,80,128,160,320,6
40
1..8

uint16_t

0..4

uint8_t

n1_PUCCH_AN_Persistent
List[4]

0..2047

uint16_t

implicitReleaseAfter

2,3,4,8

uint8_t

SPS scheduling interval in UL in


subframes.
SPS scheduling interval in DL in
subframes.
number of SPS HARQ processes.
see [1]
The size of the list. When
spsConfig is included in
CSCHED_UE_CONFIG_IND this
parameters is ignored
see [4] section 10.1. When
spsConfig is included in
CSCHED_UE_CONFIG_IND this
parameters is ignored
number of empty transmission.
see [1] section 5.10.2. When
spsConfig is included in
CSCHED_UE_CONFIG_IND this
parameters is ignored

Elements

Value

Type

Description

action

setup,release

enum

schedInterval

5,10,20,40,80

uint8_t

dsr_TransMax

4,8,16,32,64

uint8_t

Indicates if SR config should be


released or changed
SR scheduling interval in
subframes.
see [1] section 5.4.4

Type

Description

uint16_t
uint8_t

4.3.18 srRequest

4.3.19 cqiRequest
Elements

Value

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 28

action

setup,release

enum

cqiSchedInterval

1,2,5,10,20,32,40,64,80,128,160

uint16_t

riSchedInterval

1,2,4,8,16,20

uint8_t

Indicates if SR config should be


released or changed
CQI scheduling interval in
subframes.
RI scheduling interval in
subframes.

4.3.20 ue_Capabilities
Elements

Value

Type

Description

halfDuplex
intraSF_hopping
type2_sb_1
ueCategory
resAllocType1

FALSE, TRUE
FALSE, TRUE
FALSE, TRUE
1..5
FALSE, TRUE

bool
bool
bool
uint8_t
bool

UE only supports half-duplex FDD operation


UE support of intra-subframe hopping
UE supports type 2 hopping with n_sb > 1
The UE category
UE support for resource allocation type 1.

4.3.21 siConfiguration
Elements

Value

Type

Description

sfn

0..1023

uint16_t

sib1Length

1..MAX_SI_MSG_SIZE

uint16_t

siWindowLength

1,2,5,10,15,20,40

uint8_t

nrSI_Message_List
siMessageList
[nrSI_Message_List]

0..MAX_SI_MSG_LIST
variable-length array of
siMessageListElement. see 4.3.22

uint8_t
array of struct

Frame number to apply this


configuration.
The length of the SIB 1 message. Unit in
bytes
Common SI scheduling window for all
SIs. Unit in subframes.
The number of SI messages.
List of SI messages to be sent. The index
will later be used to identify the
message in the
buildBroadcastListElement see 4.3.11

4.3.22 siMessageListElement
Elements

Value

Type

Description

periodicity

8, 16, 32, 64, 128, 256, 512

uint16_t

length

1..MAX_SI_MSG_SIZE

uint16_t

Periodicity of the SI-message Unit in


radio frames
The length of SI message. Unit in bytes

4.3.23 dlInfoListElement
Elements

Value

Type

Description

rnti
harqProcessId

1..65535
0..7,8

uint16_t
uint8_t

The RNTI identifying the UE.


HARQ process ID. 8 is not present

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 29

nr_harqStatus
harqStatus[MAX_T
B_LIST]

1.. MAX_TB_LIST
ACK, NACK, DTX

uint8_t
enum

The size if the HARQ status list.


HARQ status for the above process

4.3.24 cqiListElement
Elements

Value

Type

Description

rnti
ri
cqiType

1..65535
1..4
P10,P11,P20,P21, A12, A22, A20,
A30, A31
0..15

uint16_t
uint8_t
enum

The RNTI identifying the UE.


The last received rank indication.
The CQI format.

array of uint8_t

0..15

uint8_t

see 4.3.25

union

The reported wideband CQI value per


codeword.
The reported wideband precoding
matrix index.
field discrimination is based on cqiType.

wb_cqi[MAX_TB_LI
ST]
wb_pmi
sbMeasResult

4.3.25 sbMeasResult
Elements

Value

Type

Description

ueSelected

see 4.3.26

struct

higherLayerSelecte
d[MAX_HL_SB]

see 4.3.27

struct

bwPart

see 4.3.28

struct

The subband measurement results for


aperiodic UE selected subbands.
The subband measurement results for
aperiodic higher-layer selected
subbands.
The subband measurement results for
periodic UE selected subbands.
Indicates the current CQI for the best
subband in the current bandwidth part.

4.3.26 ueSelected
Elements

Value

Type

Description

sbList[MAX_UE_SEL
ECTED_SB]
sb_pmi

0..24

array of uint8_t

0..15

uint8_t

sb_cqi[MAX_TB_LIS
T]

0..15

uint8_t

The preferred-M subbands reported by


the UE.
The PMI conditioned on the preferred M subbands.
The CQI for up to two codewords
conditioned on the preferred -M
subbands.

4.3.27 higherLayerSelected
Elements

Value

Type

Description

sb_pmi

0..63

uint8_t

The PMI conditioned on the current

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 30

sb_cqi[MAX_TB_LIS
T]

0..15

uint8_t

subband.
The CQI for up to two codewords
conditioned on the current subband.

4.3.28 bwPart
Elements

Value

Type

Description

bwPartIndex

1..4

uint8_t

sb

0..11

uint8_t

cqi

0..15

uint8_t

The bandwidth part for which CQI is


being reported.
The preferred subband in the current
bandwidth part.
The CQI conditioned on the selected
subband

4.3.29 ulCQI
Elements

Value

Type

Description

sinr[MAX_SINR_RB
_LIST

-20.0..30.

fixed point
u_int16_t
Sxxxxxxxxxxx.xx
x

type

SRS, PUSCH, PUCCH_1, PUCCH_2,


PRACH

enum

The SINR measurement based on the


resource given in type.
In case of PUCCH only the first index is
used. For PRACH the first 6 indices are
used. For PUSCH and SRS each index
represents one RB. The SINR is given in
dB
SRS measurement on SRS
PUSCH measurement on PUSCH
PUCCH_1 measurement done on
Format 1 resource
PUCCH_2 measurement done on
Format 2 resource
PRACH measurement done on PRACH

4.3.30 pagingInfoListElement
pagingIndex

pagingMessageSize
pagingSubframe

4.4

32..63

uint8_t

0..9

uint16_t
uint8_t

The index used to identify the scheduled


message, will be retuned in
SCHED_DL_CONFIG_IND
The size of the paging message
The subframe during which the message shall
be sent

Constants
Elements

Value

MAX_SCHED_CFG_LIST

10

MAX_LC_LIST

10

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 31

5.1

MAX_CTRL_BUF_LIST

MAX_BUFF_ADD_LIST

30

MAX_RACH_LIST

30

MAX_DL_INFO_LIST

30

MAX_BUILD_DATA_LIST

30

MAX_BUILD_RAR_LIST

10

MAX_BUILD_BC_LIST

MAX_ULINFO_LIST

30

MAX_DCI_LIST

30

MAX_PHICH_LIST

30

MAX_TB_LIST

MAX_RLC_PDU_LIST

30

MAX_NR_LCG

MAX_MBSFN_CONFIG

MAX_SI_MSG_LIST

32

MAX_SI_MSG_SIZE

65535

MAX_CE_LIST

30

MAX_CQI_LIST

30

MAX_UE_SELECTED_SB

MAX_HL_SB

25

MAX_SINR_RB_LIST

100

MAX_SR_LIST

30

MAX_MAC_CE_LIST

30

Scenarios

Cell Setup

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 32

RRC

PDCP

RLC

MAC

PHY

Scheduler

Configure PHY
Configure MAC
CSCHED_CELL_CONFIG_REQ

Store cell and


scheduler configuration
CSCHED_CELL_CONFIG_CNF
MAC configuration complete

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 33

5.2

RACH procedure
MAC

PHY

Scheduler

RxCallback(RACH(preamble))

Check RACH type


Decide on UL-GRANT
Create T-C-RNTI
Create MAC_RAR PDU
SCHED_CTRL_BUFFER_REQ(rnti=RA_RNTI, count)

Scheduler Subframe flow

SubframeConfiguration(MAC_RAR(T-C-RNTI, UL-grant, TA) on PDSCH with RA-RNTI)

RxCallback(RRC_CONN_REQ) on PUSCH with T-C_RNTI

Detect T-C-RNTI and incomplete RACH


Create MAC_CONTENTION_RESOLUTION
Start timer for UE contention resultion
UE CONTENTION
SCHED_LC_BUFFER_REQ(rnti=T-C-RNTI, count)

Scheduler Subframe flow

SubframeConfiguration(MAC_CONRES(CONRES) on PDSCH with T-C-RNTI)


alt
RxCallback(HARQ ACK for MAC_CONRES)

RACH procedure completed


Turn T-C-RNTI into C-RNTI
Inform RRC about RACH compete
UE CONTENTION

UE CONTENTION
RACH procedure failed
Release T-C-RNTI
Inform RRC about RACH failure

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 34

5.3

UE configuration
MAC

RRC

Scheduler

Configure UE in MAC
CSCHED_UE_CONFIG_REQ

Store UE specific
configuration
CSCHED_UE_CONFIG_CNF
MAC configuration complete

5.4

Radio Bearer Setup


RRC

RLC

PDCP

MAC

PHY

Scheduler

Configure RB in PDCP
PDCP configuration complete
Configure LC in RLC
RLC configuration complete
Configure LC in MAC
CSCHED_LC_CONFIG_REQ

Store LC specific
configuration
CSCHED_LC_CONFIG_CNF
MAC configuration complete

5.5

Handling of logical channel buffer status


PDCP

RLC

MAC

PHY

Scheduler

Send RLC SDU


SCHED_LC_BUFFER_REQ(rnti=x, lcid, count)

Update buffer status


associated with the
RNTI and LCID

Discard SDU
SCHED_LC_BUFFER_REQ(rnti=x, lcid, timestamp)

Update buffer status


associated with the
RNTI and LCID

5.6

DRB release

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 35

RRC

RLC

PDCP

MAC

Scheduler

PHY

Release LC in MAC
CSCHED_LC_RELEASE_REQ

Remove LC specific
configuration
CSCHED_LC_RELEASE_CNF
MAC LC release complete

Release LC in RLC

RLC LC release complete

Release RB in PDCP

PDCP RB release complete

5.7

UE release
RRC

MAC

PHY

Scheduler

Release UE in MAC
CSCHED_UE_RELEASE_REQ

Remove UE specific
configuration
CSCHED_UE_RELEASE_CNF
MAC UE release complete

5.8

UE configuration update by MAC scheduler


RRC

MAC

PHY

Scheduler

CSCHED_UE_CONFIG_UPDATE_IND
Configuration update indication
Change in configuration
requested by scheduler
is checked and turned
into RRC Reestablishment
Configure UE in MAC
CSCHED_UE_CONFIG_REQ(update)

Store UE specific
configuration
CSCHED_UE_CONFIG_CNF
MAC UE configuration complete

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 36

5.9

Scheduler Subframe flow


RLC

MAC

PHY

Scheduler

Periodic Callback

SCHED_DL_TRIGGER_REQ

Start DL
scheduling
SCHED_DL_CONFIG_IND
SCHED_UL_ TRIGGER_REQ

Start UL
scheduling
SCHED_UL_CONFIG_IND

Build Transport Block

Subframe Configuration

References

[1] 3GPP TS 36.321: Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control
(MAC) protocol specification (Release 8), v8.5.0, March 200.
[2] 3GPP TS 36.211: Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Channels and
Modulation (Release 8), v8.6.0, March 2009.
[3] 3GPP TS 36.212: Evolved Universal Terrestrial Radio Access (E-UTRA); Multiplexing and channel
coding (Release 8), v8.6.0, March 2009.
[4] 3GPP TS 36.213: Evolved Universal Terrestrial Radio Access (E-UTRA); Physical Layer Procedures
(Release 8), v8.6.0, March 2009.
[5] 3GPP TS 36.331: Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC);
Protocol Specification (Release 8), v8.5.0, March 2009

Revision History

Version

Description

1.11

Prepared for public release

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 37

Appendix A: Performance and Functional Requirements for the LTE Femtocell


Scheduler API

This appendix provides a high level overview of performance and functionality requirements for LTE
schedulers that utilize the LTE femtocell scheduler API framework being defined by Femto Forum WG2.
These requirements are not totally comprehensive but represent a set of basic requirements that would be
reasonably expected by an operator from an LTE scheduler residing in an LTE home eNodeB.
Satisfy latency and packet error loss characteristics of each QCI class standardized in 3GPP 23.203 Table
6.1.7 under the following conditions:
o Single user case: one user accesses any one of the example services in below table via a home
eNodeB.
o Multiple user/services case: one or several users simultaneously access more than one of the
example services in below table via a home eNodeB.
Satisfy Guaranteed Bit Rate (GBR), Minimum Bit Rate (MBR, as applicable, for each service data flow
managed by the scheduler under the following conditions:
o Single user case: one user accesses any one of the example services in below table via a home
eNodeB.
o Multiple user/services case: one or several users simultaneously access more than one of the
example services in below table via a home eNodeB.
Enforce downlink maximum bit rate for sum of downlink bearers based on UE-AMBR and APN-AMBR (for
non-GBR flows). Enforce corresponding uplink maximum bit rates.
Interact with admission and load control mechanisms to ensure that new users are admitted only when
QoS requirements of existing and newly added users/bearers can be met.
When system load exceeds certain pre-defined thresholds, judiciously select lowest priority bearers for
service downgrade.
Dynamically perform frequency selective and frequency diverse scheduling (localized and distributed
virtual resource blocks) depending upon channel conditions, QoS requirements, etc.
Dynamically adapt transport block size selection, MIMO mode selection, and rank depending upon
Channel Quality Indicator (CQI), Pre-coding Matrix Indicator (PMI), and Rank Indication (RI) feedback
from UEs while taking into account the status of data buffers.
Provide higher priority to HARQ re-transmissions versus new transmissions for a bearer.
Monitor current packet allocations and overall system load.

2010 The Femto Forum, Doc. No. FF_Tech_001_v1.11

page 38

You might also like