6.3.7 MBMS information elements

36.3313GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Protocol specificationRadio Resource Control (RRC)Release 15TS

MBMS-NotificationConfig

The IE MBMS-NotificationConfig specifies the MBMS notification related configuration parameters, that are applicable for all MBSFN areas.

MBMS-NotificationConfig information element

— ASN1START

MBMS-NotificationConfig-r9 ::= SEQUENCE {

notificationRepetitionCoeff-r9 ENUMERATED {n2, n4},

notificationOffset-r9 INTEGER (0..10),

notificationSF-Index-r9 INTEGER (1..6)

}

MBMS-NotificationConfig-v1430 ::= SEQUENCE {

notificationSF-Index-v1430 INTEGER (7..10)

}

— ASN1STOP

MBMS-NotificationConfig field descriptions

notificationOffset

Indicates, together with the notificationRepetitionCoeff, the radio frames in which the MCCH information change notification is scheduled i.e. the MCCH information change notification is scheduled in radio frames for which: SFN mod notification repetition period = notificationOffset.

notificationRepetitionCoeff

Actual change notification repetition period common for all MCCHs that are configured= shortest modification period/ notificationRepetitionCoeff. The ‘shortest modificaton period’ corresponds with the lowest value of mcch-ModificationPeriod of all MCCHs that are configured. Value n2 corresponds to coefficient 2, and so on.

notificationSF-Index

Indicates the subframe used to transmit MCCH change notifications on PDCCH. FDD: Value 1, 2, 3, 4, 5 and 6 correspond with subframe #1, #2, #3 #6, #7, and #8 respectively. Value 7, 8, 9 and 10 correspond with subframe #0, #4, #5 and #9 respectively. If notificationSF-Index-v1430 is included, UE ignores notificationSF-Index-r9. TDD: Value 1, 2, 3, 4, and 5 correspond with subframe #3, #4, #7, #8, and #9 respectively.

MBMS-ServiceList

The IE MBMS-ServiceList provides the list of MBMS services which the UE is receiving or interested to receive.

MBMS-ServiceList information element

— ASN1START

MBMS-ServiceList-r13 ::= SEQUENCE (SIZE (0..maxMBMS-ServiceListPerUE-r13)) OF MBMS-ServiceInfo-r13

MBMS-ServiceInfo-r13 ::= SEQUENCE {

tmgi-r13 TMGI-r9

}

— ASN1STOP

MBSFN-AreaId

The IE MBSFN-AreaId identifies an MBSFN area by means of a locally unique value at lower layers i.e. it concerns parameter NIDMBSFN in TS 36.211 [21], clause 6.10.2.1.

MBSFN-AreaId information element

— ASN1START

MBSFN-AreaId-r12 ::= INTEGER (0..255)

— ASN1STOP

MBSFN-AreaInfoList

The IE MBSFN-AreaInfoList contains the information required to acquire the MBMS control information associated with one or more MBSFN areas.

MBSFN-AreaInfoList information element

— ASN1START

MBSFN-AreaInfoList-r9 ::= SEQUENCE (SIZE(1..maxMBSFN-Area)) OF MBSFN-AreaInfo-r9

MBSFN-AreaInfo-r9 ::= SEQUENCE {

mbsfn-AreaId-r9 MBSFN-AreaId-r12,

non-MBSFNregionLength ENUMERATED {s1, s2},

notificationIndicator-r9 INTEGER (0..7),

mcch-Config-r9 SEQUENCE {

mcch-RepetitionPeriod-r9 ENUMERATED {rf32, rf64, rf128, rf256},

mcch-Offset-r9 INTEGER (0..10),

mcch-ModificationPeriod-r9 ENUMERATED {rf512, rf1024},

sf-AllocInfo-r9 BIT STRING (SIZE(6)),

signallingMCS-r9 ENUMERATED {n2, n7, n13, n19}

},

…,

[[ mcch-Config-r14 SEQUENCE {

mcch-RepetitionPeriod-v1430 ENUMERATED {rf1, rf2, rf4, rf8,

rf16 } OPTIONAL, — Need OR

mcch-ModificationPeriod-v1430 ENUMERATED {rf1, rf2, rf4, rf8, rf16, rf32, rf64, rf128,

rf256, spare7} OPTIONAL — Need OR

} OPTIONAL, — Need OR

subcarrierSpacingMBMS-r14 ENUMERATED {kHz7dot5, kHz1dot25} OPTIONAL — Need OR

]]

}

— ASN1STOP

MBSFN-AreaInfoList field descriptions

mcch-ModificationPeriod

Defines periodically appearing boundaries, i.e. radio frames for which SFN mod mcch-ModificationPeriod = 0. The contents of different transmissions of MCCH information can only be different if there is at least one such boundary in-between them. In case mcch-ModificationPeriod-v1430 is configured, the UE shall ignore the mcch-ModificationPeriod-r9.

mcch-Offset

Indicates, together with the mcch-RepetitionPeriod, the radio frames in which MCCH is scheduled i.e. MCCH is scheduled in radio frames for which: SFN mod mcch-RepetitionPeriod = mcch-Offset.

mcch-RepetitionPeriod

Defines the interval between transmissions of MCCH information, in radio frames, Value rf32 corresponds to 32 radio frames, rf64 corresponds to 64 radio frames and so on. In case mcch-RepetitionPeriod-v1430 is configured, the UE shall ignore the mcch-RepetitionPeriod-r9.

non-MBSFNregionLength

Indicates how many symbols from the beginning of the subframe constitute the non-MBSFN region. This value applies in all subframes of the MBSFN area used for PMCH transmissions as indicated in the MSI. The values s1 and s2 correspond with 1 and 2 symbols, respectively: see TS 36.211 [21], Table 6.7-1.

notificationIndicator

Indicates which PDCCH bit is used to notify the UE about change of the MCCH applicable for this MBSFN area. Value 0 corresponds with the least significant bit as defined in TS 36.212 [22], clause 5.3.3.1 and so on.

sf-AllocInfo

Indicates the subframes of the radio frames indicated by the mcch-RepetitionPeriod and the mcch-Offset, that may carry MCCH. Value "1" indicates that the corresponding subframe is allocated. The following mapping applies:

FDD: The first/ leftmost bit defines the allocation for subframe #1 of the radio frame indicated by mcch-RepetitionPeriod and mcch-Offset, the second bit for #2, the third bit for #3, the fourth bit for #6, the fifth bit for #7 and the sixth bit for #8.

TDD: The first/leftmost bit defines the allocation for subframe #3 of the radio frame indicated by mcch-RepetitionPeriod and mcch-Offset, the second bit for #4, third bit for #7, fourth bit for #8, fifth bit for #9. Uplink subframes are not allocated. The last bit is not used.

signallingMCS

Indicates the MCS applicable for the subframes indicated by the field sf-AllocInfo and for each (P)MCH that is configured for this MBSFN area, for the first subframe allocated to the (P)MCH within each MCH scheduling period (which may contain the MCH scheduling information provided by MAC). Value n2 corresponds with the value 2 for parameter in TS 36.213 [23], Table 7.1.7.1-1, and so on.

subcarrierSpacingMBMS

The value indicates subcarrier spacing for MBSFN subframes and kHz7dot5 refers to 7.5kHz subcarrier spacing and kHz1dot25 refers to 1.25 kHz subcarrier spacing as defined in TS 36.211 [21], clause 6.12. These subframes do not have non-MBSFN region. If subcarrierSpacingMBMS is present, then non-MBSFNregionLength shall be ignored. EUTRAN configures parameter subcarrierSpacingMBMS only when the MBSFN subframes have subcarrier spacing other than 15kHz.

MBSFN-SubframeConfig

The IE MBSFN-SubframeConfig defines subframes that are reserved for MBSFN in downlink.

MBSFN-SubframeConfig information element

— ASN1START

MBSFN-SubframeConfig ::= SEQUENCE {

radioframeAllocationPeriod ENUMERATED {n1, n2, n4, n8, n16, n32},

radioframeAllocationOffset INTEGER (0..7),

subframeAllocation CHOICE {

oneFrame BIT STRING (SIZE(6)),

fourFrames BIT STRING (SIZE(24))

}

}

MBSFN-SubframeConfig-v1430 ::= SEQUENCE {

subframeAllocation-v1430 CHOICE {

oneFrame-v1430 BIT STRING (SIZE(2)),

fourFrames-v1430 BIT STRING (SIZE(8))

}

}

— ASN1STOP

MBSFN-SubframeConfig field descriptions

fourFrames

A bit-map indicating MBSFN subframe allocation in four consecutive radio frames, "1" denotes that the corresponding subframe is allocated for MBSFN. The bitmap is interpreted as follows:

FDD: Starting from the first radioframe and from the first/leftmost bit in the bitmap, the allocation applies to subframes #1, #2, #3, #6, #7, and #8 in the sequence of the four radio-frames.

TDD: Starting from the first radioframe and from the first/leftmost bit in the bitmap, the allocation applies to subframes #3, #4, #7, #8, and #9 in the sequence of the four radio-frames. The last four bits are not used. E-UTRAN allocates uplink subframes only if eimta-MainConfig is configured.

fourFrames-v1430

A bit-map indicating MBSFN subframe allocation in four consecutive radio frames, "1" denotes that the corresponding subframe is allocated for MBSFN. The bitmap is interpreted as follows:

FDD: Starting from the first radioframe and from the first/leftmost bit in the bitmap, the allocation applies to subframes #4 and #9 in the sequence of the four radio-frames.

oneFrame

"1" denotes that the corresponding subframe is allocated for MBSFN. The following mapping applies:

FDD: The first/leftmost bit defines the MBSFN allocation for subframe #1, the second bit for #2, third bit for #3, fourth bit for #6, fifth bit for #7, sixth bit for #8.

TDD: The first/leftmost bit defines the allocation for subframe #3, the second bit for #4, third bit for #7, fourth bit for #8, fifth bit for #9. E-UTRAN allocates uplink subframes only if eimta-MainConfig is configured. The last bit is not used.

oneFrame-v1430

"1" denotes that the corresponding subframe is allocated for MBSFN. The following mapping applies:

FDD: The first/leftmost bit defines the MBSFN allocation for subframe #4 and the second bit for #9.

radioFrameAllocationPeriod, radioFrameAllocationOffset

Radio-frames that contain MBSFN subframes occur when equation SFN mod radioFrameAllocationPeriod = radioFrameAllocationOffset is satisfied. Value n1 for radioframeAllocationPeriod denotes value 1, n2 denotes value 2, and so on. When fourFrames is used for subframeAllocation, the equation defines the first radio frame referred to in the description below. Values n1 and n2 are not applicable when fourFrames is used.

subframeAllocation

Defines the subframes that are allocated for MBSFN within the radio frame allocation period defined by the radioFrameAllocationPeriod and the radioFrameAllocationOffset.

PMCH-InfoList

The IE PMCH-InfoList specifies configuration of all PMCHs of an MBSFN area, while IE PMCH-InfoListExt includes additional PMCHs, i.e. extends the PMCH list using the general principles specified in 5.1.2. The information provided for an individual PMCH includes the configuration parameters of the sessions that are carried by the concerned PMCH. For all PMCH that E-UTRAN includes in PMCH-InfoList, the list of ongoing sessions has at least one entry.

PMCH-InfoList information element

— ASN1START

PMCH-InfoList-r9 ::= SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF PMCH-Info-r9

PMCH-InfoListExt-r12 ::= SEQUENCE (SIZE (0..maxPMCH-PerMBSFN)) OF PMCH-InfoExt-r12

PMCH-Info-r9 ::= SEQUENCE {

pmch-Config-r9 PMCH-Config-r9,

mbms-SessionInfoList-r9 MBMS-SessionInfoList-r9,

}

PMCH-InfoExt-r12 ::= SEQUENCE {

pmch-Config-r12 PMCH-Config-r12,

mbms-SessionInfoList-r12 MBMS-SessionInfoList-r9,

}

MBMS-SessionInfoList-r9 ::= SEQUENCE (SIZE (0..maxSessionPerPMCH)) OF MBMS-SessionInfo-r9

MBMS-SessionInfo-r9 ::= SEQUENCE {

tmgi-r9 TMGI-r9,

sessionId-r9 OCTET STRING (SIZE (1)) OPTIONAL, — Need OR

logicalChannelIdentity-r9 INTEGER (0..maxSessionPerPMCH-1),

}

PMCH-Config-r9 ::= SEQUENCE {

sf-AllocEnd-r9 INTEGER (0..1535),

dataMCS-r9 INTEGER (0..28),

mch-SchedulingPeriod-r9 ENUMERATED {

rf8, rf16, rf32, rf64, rf128, rf256, rf512, rf1024},

}

PMCH-Config-r12 ::= SEQUENCE {

sf-AllocEnd-r12 INTEGER (0..1535),

dataMCS-r12 CHOICE {

normal-r12 INTEGER (0..28),

higerOrder-r12 INTEGER (0..27)

},

mch-SchedulingPeriod-r12 ENUMERATED {

rf4, rf8, rf16, rf32, rf64, rf128, rf256, rf512, rf1024},

…,

[[ mch-SchedulingPeriod-v1430 ENUMERATED {rf1, rf2} OPTIONAL — Need OR

]]

}

TMGI-r9 ::= SEQUENCE {

plmn-Id-r9 CHOICE {

plmn-Index-r9 INTEGER (1..maxPLMN-r11),

explicitValue-r9 PLMN-Identity

},

serviceId-r9 OCTET STRING (SIZE (3))

}

— ASN1STOP

PMCH-InfoList field descriptions

dataMCS

Indicates the value for parameter in TS 36.213 [23], which defines the MCS applicable for the subframes of this (P)MCH as indicated by the field commonSF-Alloc. Value normal corresponds to Table 7.1.7.1-1 and value higherOrder corresponds to Table 7.1.7.1-1A. The MCS does however neither apply to the subframes that may carry MCCH i.e. the subframes indicated by the field sf-AllocInfo within SystemInformationBlockType13 nor for the first subframe allocated to this (P)MCH within each MCH scheduling period (which may contain the MCH scheduling information provided by MAC).

mch-SchedulingPeriod

Indicates the MCH scheduling period i.e. the periodicity used for providing MCH scheduling information at lower layers (MAC) applicable for an MCH. Value rf8 corresponds to 8 radio frames, rf16 corresponds to 16 radio frames and so on. The mch-SchedulingPeriod starts in the radio frames for which: SFN mod mch-SchedulingPeriod = 0. E-UTRAN configures mch-SchedulingPeriod of the (P)MCH listed first in PMCH-InfoList to be smaller than or equal to mcch-RepetitionPeriod. In case mch-SchedulingPeriod-v1430 is configured, the UE shall ignore mch-SchedulingPeriod-r12.

plmn-Index

Index of the entry across the plmn-IdentityList fields within SystemInformationBlockType1.

sessionId

Indicates the optional MBMS Session Identity, which together with TMGI identifies a transmission or a possible retransmission of a specific MBMS session: see TS 29.061 [51], clauses 20.5, 17.7.11, and 17.7.15. The field is included whenever upper layers have assigned a session identity i.e. one is available for the MBMS session in E-UTRAN.

serviceId

Uniquely identifies the identity of an MBMS service within a PLMN. The field contains octet 3- 5 of the IE Temporary Mobile Group Identity (TMGI) as defined in TS 24.008 [49]. The first octet contains the third octet of the TMGI, the second octet contains the fourth octet of the TMGI and so on.

sf-AllocEnd

Indicates the last subframe allocated to this (P)MCH within a period identified by field commonSF-AllocPeriod. The subframes allocated to (P)MCH corresponding with the nth entry in pmch-InfoList are the subsequent subframes starting from either the next subframe after the subframe identified by sf-AllocEnd of the (n-1)th listed (P)MCH or, for n=1, the first subframe defined by field commonSF-Alloc, through the subframe identified by sf-AllocEnd of the nth listed (P)MCH. Value 0 corresponds with the first subframe defined by field commonSF-Alloc.