Sender F-TEID for Control Plane

M

F-TEID

0

Temporary Mobile Group Identity (TMGI)

M

See NOTE 4.

TMGI

0

MBMS Session Duration

M

MBMS Session Duration

0

MBMS Service Area

M

MBMS Service Area

0

MBMS Session Identifier

C

This IE shall be forwarded to MME/SGSN if it is provided by the BM-SC.

MBMS Session Identifier

0

MBMS Flow Identifier

C

This IE shall be forwarded to MME/SGSN if it is provided by the BM-SC.

MBMS Flow Identifier

0

QoS profile

M

See NOTE 1.

Bearer QoS

0

MBMS IP Multicast Distribution

M

See NOTE 2.

MBMS IP Multicast Distribution

0

Recovery

C

This IE shall be included if contacting the peer for the first time.

Recovery

0

MBMS Time to Data Transfer

CO

This IE shall be forwarded to MME/SGSN if it is received from the BM-SC.

MBMS Time to Data Transfer

0

MBMS Data Transfer Start

CO

This IE shall be forwarded to the MME if it is received from the BM-SC.

Absolute Time of MBMS Data Transfer

0

MBMS Flags

CO

This IE shall be included if any one of the applicable flags is set to 1.

Applicable flags:

• MBMS Session Re-establishment Indication: this flag shall be set to 1 on the Sm/Sn interfaces if the MBMS Session Start Request message is used to re-establish an MBMS session (see 3GPP TS 23.007 [13]).

MBMS Flags

0

MBMS Alternative IP Multicast Distribution

CO

If the MBMS GW supports both IPv4 and IPv6 M1 multicast address types, the MBMS GW may include this IE on the Sm interface to provide an alternative MBMS IP Multicast Distribution Address with a different address type (i.e. IPv4 or IPv6) than the one provided in the MBMS IP Multicast Distribution IE.

See NOTE 2.

MBMS IP Multicast Distribution

1

MBMS Cell List

CO

The MBMS GW shall include this IE on the Sm interface if a MBMS Cell List was received from the BM-SC.

See NOTE 3.

ECGI-List

0

Private Extension

O

Private Extension

VS

NOTE 1: The uplink GBR and uplink MBR shall be ignored by MME/SGSN as specified in Clause 20.5 of 3GPP TS 29.061 [38].

NOTE 2: If the MBMS GW supports both IPv4 and IPv6 M1 multicast address types, the MBMS GW may provide both IPv4 and IPv6 MBMS IP Multicast Distribution addresses on the Sm interface by including the MBMS IP Multicast Distribution IE and the MBMS Alternative IP Multicast Distribution IE in the MBMS Session Start Request. In this case, one of these IEs shall carry an IP Multicast Distribution Address and an IP Multicast Source Address for IPv6 and the other IE shall carry IPv4 addresses. Both IEs shall contain the same C-TEID value.

NOTE 3: The MBMS Cell List can contain from 1 up to 4096 cells (see 3GPP TS 29.061 [38]).

NOTE 4: The PLMN ID in the TMGI IE received in the MBMS Session Start Request message may be different from the PLMN ID(s) either reported by the MCE(s) previously at the M3 Setup procedure or configured as supported PLMN(s), e.g. when shared MBMS network is deployed; the MME need not check it.

Cause

M

Cause

0

Sender F-TEID for Control Plane

M

F-TEID

0

MBMS Distribution Acknowledge

C

This IE shall be included on the Sn interface.

MBMS Distribution Acknowledge

0

Sn-U SGSN F-TEID

C

This IE shall be included on the Sn interface if some RNCs have not accepted IP multicast distribution.

F-TEID

1

Recovery

C

This IE shall be included if contacting the peer for the first time.

Recovery

0

Private Extension

O

Private Extension

VS

MBMS Service Area

C

This IE shall be forwarded to MME/SGSN if it is provided by the BM-SC.

MBMS Service Area

0

Temporary Mobile Group Identity (TMGI)

M

TMGI

0

Sender F-TEID for Control Plane

O

F-TEID

0

MBMS Session Duration

M

MBMS Session Duration

0

QoS profile

M

See NOTE 1.

Bearer QoS

0

MBMS Session Identifier

C

This IE shall be forwarded to MME/SGSN if it is provided by the BM-SC.

MBMS Session Identifier

0

MBMS Flow Identifier

C

This IE shall be forwarded to MME/SGSN if it is provided by the BM-SC.

MBMS Flow Identifier

0

MBMS Time to Data Transfer

CO

This IE shall be forwarded to MME/SGSN if it is provided by the BM-SC.

MBMS Time to Data Transfer

0

MBMS Data Transfer Start / Update / Stop

CO

This IE shall be forwarded to the MME if it is received from the BM-SC.

See NOTE 3.

Absolute Time of MBMS Data Transfer

0

MBMS Cell List

CO

The MBMS GW shall include this IE on the Sm interface if a MBMS Cell List was received from the BM-SC.

See NOTE 2.

ECGI List

0

Private Extension

O

Private Extension

VS

NOTE 1: The uplink GBR and uplink MBR shall be ignored by MME/SGSN as specified in Clause 20.5 of 3GPP TS 29.061 [38].

NOTE 2: The MBMS Cell List can contain from 1 up to 4096 cells (see 3GPP TS 29.061 [38]).

NOTE 3: The MME copies the absolute time received in this IE into the Time of MBMS Data Transfer IE in the M3AP MBMS SESSION START REQUESTor MBMS SESSION UPDATE REQUEST, or into the Time of MBMS Data Stop IE in the M3AP MBMS SESSION STOP REQUEST, as appropriate. See 3GPP TS 23.246 [37] and 3GPP TS 36.444 [79].

Cause

M

Cause

0

MBMS Distribution Acknowledge

C

This IE shall be included on the Sn interface if service area is changed.

MBMS Distribution Acknowledge

0

Sn-U SGSN F-TEID

C

This IE shall be included on the Sn interface if any of the newly added RNCs have not accepted IP multicast distribution.

F-TEID

0

Recovery

C

This IE shall be included if contacting the peer for the first time.

Recovery

0

Private Extension

O

Private Extension

VS

MBMS Flow Identifier

C

This IE shall be forwarded to MME/SGSN if it is provided by the BM-SC. See NOTE 1.

MBMS Flow Identifier

0

MBMS Data Transfer Stop

CO

This IE shall be forwarded to the MME if it is received from the BM-SC.

Absolute Time of MBMS Data Transfer

0

MBMS Flags

CO

This IE shall be included if any one of the applicable flags is set to 1.

Applicable flags:

• Local MBMS Bearer Context Release Indication: this flag shall be set to 1 on the Sm/Sn interfaces if the MBMS Session Stop Request message is used to release the MBMS bearer context locally in the MME/SGSN (see 3GPP TS 23.007 [13]).

MBMS Flags

0

Private Extension

O

Private Extension

VS

NOTE 1: The conditional MBMS Flow Identifier IE is redundant as MBMS Session Stop Request message is sent over non-zero TEID header. The receiver may ignore the MBMS Flow Identifier IE.

Cause

M

Cause

0

Recovery

CO

This IE shall be included if contacting the peer for the first time.

Recovery

0

Private Extension

O

Private Extension

VS