D.2 Architecture
23.2463GPPArchitecture and functional descriptionMultimedia Broadcast/Multicast Service (MBMS)Release 17TS
D.2.1 Architecture for per PLMN MBSFN synchronization area
Figure D.2.1-1 shows and example network architecture for Shared MBMS Network with MBMS synchronization area defined within each PLMN. The example shows two PLMNs (PLMN 1 and PLMN2) providing shared MBMS service. In the example, F3 is shared spectrum used by all involved PLMN for MBMS service.
Figure D.2.1-1: Shared MBMS Network architecture with per-PLMN MBMS synchronization area
The SMN contains the following network elements:
– Shared BM-SC (denoted BM-SC(SMN) in Figure D.2.1-1):
– Provides all the functionality defined in clause 5.1 for EPC.
– Shared MBMS-GW (denoted MBMS-GW(SMN) in Figure D.2.1-1)
– Provides all the functionality defined in clause 5.9.1.
– In addition:
– It connects to MMEs from one or multiple PLMNs via the inter-PLMN Sm-s reference point for control plane signalling.
– It connects to E-UTRAN nodes from one or multiple PLMNs via the inter-PLMN M1-s reference point for IP multicast distribution.
The SMN may also contain shared E-UTRAN functionality for the purpose of MBMS service only. In that case the SMN also contains the following network entities:
– Shared E-UTRAN – eNB, MCE (denoted RAN(SMN) in Figure D.2.1-1)
– Provides functionality as defined in clause 5.9.1.
– Shared MME MBMS function (denoted MME(SMN)):
– The shared MME MBMS control function provides the functionality defined in clause 5.9.2.
NOTE: The shared MME MBMS control function provides only a subset of the functionality of a regular MME as defined in TS 23.401 [16], dedicated only to providing control plane functionality related to MBMS service.
D.2.2 Reference Points
The following reference points are defined for Shared MBMS Network:
– All internal reference points within the SMN leverage existing reference points M1, M2, M3, Sm, SGmb, SGi-mb.
– All internal reference points within each PLMN existing reference points M2, M3
– M1-s:
– Inter-PLMN reference point between the Shared MBMS‑GW and the E-UTRAN node from a participating PLMN.
– Provides equivalent functionality to M1.
– Sm-s:
– Inter-PLMN reference point between the Shared MBMS‑GW and MME from a participating PLMN.
– Provides equivalent functionality to Sm.
D.2.3 UE Aspects
Different scenarios can be supported from the perspective of the UE. The following is a non-exhaustive list of possible scenarios:
UE Scenario 1: The UE receives both unicast and broadcast service from same PLMN. The UE follows the same functionality as defined in clause 5.2.
UE Scenario 2: The UE receives broadcast MBMS service without PLMN subscription over E-UTRAN without the need to access and register with the PLMN offering the MBMS service. The UE acts in Receive Only mode as defined in Annex E.
UE Scenario 3: The UE receives unicast service from one serving PLMN’s (e.g. the PLMN for which it has unicast subscription), and receive MBMS service through a different PLMN. The UE acts in Receive Only mode with independent unicast as defined in Annex E.
D.2.4 TMGI for shared MBMS networks
AS described in TS 23.003 [13], the TMGI is composed by an MBMS Service ID and a PLMN ID (MCC/MNC).
There construction of the PLMN ID field in the TMGI is deployment dependent. The following are example deployment options:
– Example Deployment Option 1: Shared PLMN ID
– A Shared PLMN ID is used for the shared MBMS service. The shared PLMN ID is broadcasted in the cells broadcasting the shared MBMS service content.
– Example Deployment Option 2: Internal PLMN ID in the Shared MBMS network
– The Shared MBMS network (i.e. BMSC) uses the "Internal" PLMN ID to generate the TMGI. MBMS-GW uses the PLMN ID from the incoming SGmb interface towards the rest of the network entities in the MBMS path. eNB announces a MBMS session TMGI whose PLMN ID is not in the SIB1 PLMN ID list. The "Internal" PLMN ID is not used for any other PLMN services.
Annex E (normative):
UE behaviour in Receive Only Mode
A UE configured as Receive Only Mode can receive only MBMS broadcast service over E-UTRAN without the need to access and register with the PLMN offering the MBMS service. A UE configured to operate in Receive Only Mode shall shall camp on a network cell in an eMBMS Broadcast carrier, shall attempt to receive MBMS service based only on a standardised TMGI value range for Receive Only Mode. The UE shall not attempt to receive MBMS service for TMGIs outside the standardized TMGI range. The UE shall refrain from any Mobility Management or other signalling with the network offering MBMS. The UE uses the acquired system information to receive MBMS broadcast. Use of Receive Only Mode does not require USIM for the UE.
A UE may be configured as Receive Only Mode with independent unicast using EPS bearer contexts. This configuration option allows a UE to operate as Receive Only Mode (as defined above) for MBMS broadcast service, and independently follows regular NAS/RRC procedures for unicast service with a PLMN. This mode of operation requires USIM and PLMN subscription to receive unicast service. No additional subscription or credentials are required to receive MBMS broadcast service.
Any device that is equipped with MBMS broadcast receiver and is configured to operate in Receive Only Mode is able to receive the broadcast content, with the following characteristics:
– No PLMN credentials/subscription are required, as long as use of EPS unicast bearers is not required by the device.
– Without PLMN credentials/subscription, the UE can only access broadcast services without subscription. The content can be Free To Air (FTA) content as defined in TS 22.101 [30] in which case it can be viewed without content subscription.
– There is no need for the UE to support uplink.
NOTE: It is possible though that there is content protection handled at application layer. In that case security is provided at application layer, and keys, etc. are provisioned out of band. This provisioning is out of scope of 3GPP.
The UE is preconfigured with all the necessary information for the UE to acquire the system information and receive MBMS service. This information includes:
– PLMN ID(s) that provide the MBMS service.
– TMGI(s):
– In the case of the network providing MBMS service in MBMS transport only mode, the TMGI(s) for each MBMS service need to be configured in the UE.
– The UE may be configured to receive TMGI(s) via Service Announcement (see clauses 4.4.3.1, 5.1.4 and 6.4).
– RAN specific information,
– USD(s).
Figure E-1 shows the components of a UE in Receive Only Mode and in Receive Only Mode with independent unicast.
Figure E-1: UE components in Receive Only Mode and Receive Only Mode with independent unicast
The unicast component is active only in Receive Only Mode with independent unicast. The unicast component follows regular NAS/RRC procedures for E-UTRAN/EPC in order to receive unicast service.
For the broadcast component, the UE is configured with MBMS radio resources for TV service with no PLMN subscription. The broadcast component of the UE shall camp on a network cell in an eMBMS Broadcast carrier and shall attempt to receive MBMS service based only on a standardised TMGI value range. The UE shall not attempt to receive MBMS service for TMGIs outside the standardized TMGI range. The broadcast component shall refrain from any Mobility Management or other signalling with the network offering MBMS. The broadcast component uses the acquired system information to receive MBMS broadcast.
Annex C (Informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2011-12 |
SA#54 |
SP-110748 |
0269 |
4 |
C |
MBMS data transfer time |
11.0.0 |
|
2012-03 |
SA#55 |
SP-120088 |
0273 |
– |
F |
Correction to Absolute Start Time for MBMS Data Delivery |
11.1.0 |
|
2013-12 |
SA#62 |
SP-130534 |
0276 |
3 |
C |
M1 Group reuse |
12.0.0 |
|
2014-03 |
SA#63 |
SP-140102 |
0277 |
1 |
B |
MBMS bearer priority update |
12.1.0 |
|
2014-06 |
SA#64 |
SP-140377 |
0279 |
2 |
F |
Resource allocation for the MBMS bearer |
12.2.0 |
|
2014-06 |
SA#64 |
SP-140260 |
0281 |
1 |
F |
Lift restriction GBR=MBR for MBMS when GCSE is used |
12.2.0 |
|
2014-09 |
SA#65 |
SP-140425 |
0384 |
1 |
F |
Clarify the MBMS session update procedure |
12.3.0 |
|
2014-12 |
SA#66 |
SP-140678 |
0387 |
4 |
F |
Long Group Calls and New Cells |
12.4.0 |
|
2015-03 |
SA#67 |
SP-150015 |
0390 |
– |
A |
Correction to BM-SC initiated Session Update procedure |
12.5.0 |
|
2015-03 |
SA#67 |
SP-150027 |
0391 |
2 |
B |
eMBMS alternative IP multicast distribution address |
13.0.0 |
|
2015-03 |
SA#67 |
SP-150239 |
0392 |
1 |
F |
MBMS Session Start procedure correction and editorial corrections |
13.1.0 |
|
2015-09 |
SA#69 |
SP-150239 |
0394 |
2 |
A |
Support for UE Consumption Reporting towards BM-SC |
13.2.0 |
|
2015-09 |
SA#69 |
SP-150506 |
0396 |
2 |
B |
MBMS bearer establishment and update with cell ID list |
13.2.0 |
|
2015-12 |
SA#70 |
SP-150616 |
0397 |
2 |
F |
Cell ID in MBMS bearer context table for EPS |
13.3.0 |
|
2015-12 |
SA#70 |
SP-150614 |
0398 |
2 |
F |
Differentiate MBMS User and Bearer Services |
13.3.0 |
|
2016-09 |
SA#73 |
SP-160656 |
0402 |
1 |
B |
Enhanced TV services using Broadcast and Unicast mode of operation |
14.0.0 |
|
2016-09 |
SA#73 |
SP-160656 |
0404 |
2 |
B |
Introducing Shared eMBMS Network and Receive Only Mode for TV services |
14.0.0 |
|
2016-12 |
SA#74 |
SP-160820 |
0405 |
1 |
F |
Corrections of MBMS Shared Network |
14.1.0 |
|
2016-12 |
SA#74 |
SP-160820 |
0406 |
1 |
F |
3GPP network and Content provider reference point |
14.1.0 |
|
2016-12 |
SA#74 |
SP-160820 |
0407 |
1 |
F |
Shared MBMS Network scope clarification |
14.1.0 |
|
2016-12 |
SA#74 |
SP-160820 |
0408 |
2 |
F |
Use of TMGI & PLMN ID for Shared MBMS Network |
14.1.0 |
|
2016-12 |
SA#74 |
SP-160825 |
0412 |
1 |
F |
MBMS Update with session time |
14.1.0 |
|
2017-09 |
SA#77 |
SP-170723 |
0414 |
4 |
C |
UE Capabilities for MBMS |
14.2.0 |
|
2017-12 |
SA#78 |
SP-170928 |
0415 |
1 |
C |
MBMS session setup/event notification procedure alignment with RAN WG3 |
15.0.0 |
|
2017-12 |
SA#78 |
SP-170928 |
0416 |
2 |
F |
MB2 improvements for GCS AS to be able to request application of FEC and/or RoHC to a MBMS bearer |
15.0.0 |
|
2019-03 |
SA#83 |
SP-190175 |
0417 |
1 |
F |
Change xMB reference |
16.0.0 |
|
2019-09 |
SA#85 |
SP-190602 |
0419 |
2 |
A |
Fix missed update to Session Update procedure – add delayed response |
16.1.0 |
|
2022-03 |
SA#95E |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |