6 MBMS User Service requirements
22.2463GPPMultimedia Broadcast/Multicast Service (MBMS) user servicesRelease 17Stage 1TS
6.1 Charging
The MBMS User Service shall support standardized mechanisms to transfer charging related information.
It shall be possible to charge for MBMS content the user receives while roaming in a VPLMN.
As indicated in Annex A some services will require an indication that MBMS content has been received. Therefore it shall be possible for the UE to provide such an indication.
The MBMS User Service shall support the following charging mechanisms :
Charging on a subscription basis
Charging for keys that that allow the user access to the data
6.2 Security
The following security aspects shall be taken into account:
Any user modifiable MBMS service data (e.g. storage of deliveries in the UE, data type and format specific behaviours etc) shall only be modified by the authenticated user (see also 4.1.1 above).
6.3 Privacy
Third parties and VASP should not be aware about user IDs for MBMS subscriptions unless explicitly allowed by the operator.
6.4 Quality of service
It should be possible for the operator to collect statistical data such as lost frames, assigned resources, bit-rates achieved etc.
It shall be possible for the operator to adapt the distribution of a MBMS user service consisting of different MBMS transport services to provide multiple QoS levels according to the QoS resources provided by the access network(s), while maintaining the resource efficiency of the underlying MBMS transport services.
Note: It is necessary that an MBMS user service, consisting of different MBMS transport services providing multiple QoS levels, can be received by all MBMS-capable terminals.
It shall be possible to base the adaptation of the distribution of a MBMS user service to the QoS resources provided by the access network(s) on:
– the QoS resources within the same access network (e.g. UTRAN).
– the QoS resources provided by different access networks (e.g. UTRAN and GERAN).
It shall be possible to adapt the distribution of an ongoing MBMS user service to persistently changed QoS resource conditions in the access network(s).
Adaptation of the distribution of a MBMS user service to the QoS resources in different access networks or parts of the same access network shall not affect the QoS of the MBMS user service in other access networks or other parts of the same access network.
6.5 Subscription
During the lifetime of subscription to a Multicast Service it shall be possible for the user to declare the service preferences. It shall be possible for the network to store the user settings e.g. using GUP.
6.6 Availability
The user should be able to receive MBMS user services via generic IP access systems.
Note: The transport of MBMS user services over non 3GPP accesses is out of scope of 3GPP, however if the non 3GPP access system has multicast or broadcast capabilities these should be utilised if possible.
Annex A (informative):
Use Cases
|
Service Example |
Media |
Distribution Scope |
MBMS User Service Classification |
ApplicationBit rate Note 1 |
Delivery Verification Required Note 3 |
User Charging Note 4 |
|
Reliable text distribution (eg Local news) |
Text |
Multicast |
Download |
Up to 10 kbps |
Yes |
Event |
|
Unverified text distribution |
Text |
Multicast, Broadcast |
Carousel, download |
Up to 10 kbps |
No |
– |
|
Text distribution with still images and/or low quality video |
Text, Still images, Video (e.g. 3fps) |
Multicast, Broadcast |
Carousel, download |
Up to 32 kbps |
Service dependent |
User service dependent Note 2 |
|
Audio streaming |
Stereo Audio |
Multicast |
Streaming |
Up to 48kbps |
Service dependent |
– |
|
Audio streaming |
Stereo Audio |
Broadcast |
Streaming |
Up to 48kbps |
No |
– |
|
Audio download |
Stereo Audio |
Broadcast |
Download |
Up to 48kbps |
Service dependent |
– |
|
Audio download |
Stereo Audio |
Multicast |
Download |
Up to 48kbps |
Yes |
Event |
|
Audio distribution with low quality video |
Stereo Audio, Video (e.g. 3fps) |
Broadcast |
Streaming |
Up to 128kbps Note 5 |
No |
– |
|
Audio distribution with low quality video |
Stereo Audio, Video (e.g. 3fps) |
Multicast |
Streaming |
Up to 128kbps Note 5 |
Service dependent |
– |
|
Audio distribution with low quality video |
Stereo Audio, Video (e.g. 3fps) |
Broadcast |
Download |
Up to 128kbps Note 5 |
Service dependent |
– |
|
Audio distribution with low quality video |
Stereo Audio, Video (e.g. 3fps) |
Multicast |
Download |
Up to 128kbps Note 5 |
Yes |
Event |
|
Video streaming |
Video & supplementary data (e.g. text, still images) |
Broadcast |
Streaming |
Up to 384 kbps Note 5 |
No |
– |
|
Video streaming |
Video & supplementary data (e.g. text, still images) |
Multicast |
Streaming |
Up to 384 kbps Note 5 |
Service dependent |
– |
|
Video distribution |
Video & supplementary data (e.g. text, still images) |
Broadcast |
Download |
Up to 384 kbps Note 5 |
Service dependent |
– |
|
Video distribution |
Video & supplementary data (e.g. text, still images) |
Multicast |
Download |
Up to 384 kbps Note 5 |
Yes |
Event |
|
General Content Distribution |
Video, Audio, File Data (binary data) |
Broadcast |
Carousel, download |
Up to 384 kbps Note 5 |
Service dependent |
– |
|
General Content Distribution |
Video, Audio, File Data (binary data) |
Multicast |
Carousel, download |
Up to 384 kbps Note 5 |
Yes |
Event |
|
Secure data download |
File; eg UE type specific and/or application specific software |
Multicast |
Carousel, download |
Up to 10kbps |
– |
– |
|
Notes : 1. Bit rate of the user data at the application layer. 2. If User Charging is Event based then Delivery Verification is required 3 Delivery Verification relates only to verification itself. Quality assessments may be required in addition. 4 DRM may be applicable to User Charging. 5 For GERAN lower bandwidth availability may constrain some applications. In such cases it may be possible to provide the same content via different delivery methods. 6 The ‘ – ‘ mark indicates that no applicable information has been identified. |
||||||
Annex B (informative):
Example service scenarios
This annex provides a non-exhaustive list of potential service scenarios for MBMS User Services.
B.1 Text notification service
Media: Text
Precondition: The user is a member of a MBMS Multicast group supplying text alerts.
Actions: At an appropriate time an alert is sent to the user’s mobile handset using the MBMS Multicast service.
Post condition: The user receives the alert using her mobile handset and takes appropriate action.
B.2 Local Area Information distribution (Case A)
Media: Text & Text with low quality video
Precondition: The user is a registered with an MBMS Broadcast service providing information to the local area such as local news and weather reports.
Actions: Information in the form of text & text with low quality video is distributed to the user’s mobile handset by the MBMS Broadcast service. The text may be scrolled on the mobile handset. The information distributed by the MBMS Broadcast Service may be repeated periodically and updated at appropriate intervals.
Post condition: The user is aware of events that have taken place within the local area and can view appropriate images.
B.3 Local Area Information distribution (Case B)
Media: Video & Audio
Precondition: The user is a registered with an MBMS Broadcast service providing streaming audio and/or visual content related to a local area, such as audio and visual guides to local attractions, traffic reports etc…
Actions: Audio and/or visual information is distributed to the user’s mobile handset by the MBMS Broadcast service. The user is able experience the content on her mobile device. The user is able to receive the MBMS broadcast service continuously throughout the local area. At some points the user is able to interact with the content of the MBMS Broadcast service in order to access specific information regarding items being presented within the content. The user is able to activate/deactivate reception of the MBMS service at any time.
Post condition: The user experiences and interacts with the content provided and is therefore able to obtain information regarding the local area and act accordingly.
B.4 Multicast distribution
Media: Text & Text with still images
Precondition: The user is a member if a MBMS multicast group providing personally tailored content such as targeted advertising etc…
Actions: Information is provided by the MBMS Multicast service in the form of text & text with still images, to the user’s mobile handset based on her subscription to the Multicast group and current location.
Post condition: The user receives tailored content and is able to utilize this as appropriate.
B.5 Audio Distribution
Media: Stereo Audio
Precondition: The user is registered with an MBMS Broadcast service providing stereo quality streaming audio content.
Actions: Audio content is distributed to the user’s mobile handset by the MBMS Broadcast service. Whilst listening to the audio content the user is able to interact with the service using the capabilities of the mobile handset (e.g. messaging).
Post condition: The user is able to enjoy the stereo quality audio content and interacts with the service as appropriate.
B.6 General Content Distribution
Media: Video, Audio & File Data
Precondition: The user is registered with a MBMS Broadcast service providing a variety of content.
Actions: Content is periodically distributed to a particular area by the MBMS Broadcast service. When the user activates reception of the MBMS Broadcast service she is able to receive the content being distributed at that time.
Post condition: The user is able to receive and enjoy the content being distributed.
B.7 Software Download
Media : File
Preconditions :Need to update/download software in UE, the User is subscribed to MBMS User Service, OTA download is supported in UE
Actions: The operator compiles a list of affected users and sends them a text message (using MBMS) explaining the problem and that the user should select the MBMS application on their handset. The user sees a message inviting her to activate the Enable Upgrade, selects ‘yes’ and the software patch transferred by the MBMS User Service, including verification parameters.
Postcondition :The software once installed allows the user to view the MMs that she couldn’t see before.
Annex C (informative):
Change history
|
Change history |
|||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
WI |
|
Jun 2003 |
22.246 |
Initial draft presented |
0.0.0 |
0.1.0 |
MBMS |
||||||
|
Aug 2003 |
22.246 |
Output from MBMS adhoc Staines |
0.1.0 |
0.2.0 |
MBMS |
||||||
|
Sep 2003 |
22.246 |
Approved in SA1 for presentation to SA #21 |
0.2.0 |
1.0.0 |
MBMS |
||||||
|
Oct 2003 |
22.246 |
Rel-6 |
Raised to version 2.0.0 for approval at SA #22 |
1.0.0 |
2.0.0 |
MBMS |
|||||
|
SP-22 |
SP-030708 |
S1-031003 |
22.246 |
Rel-6 |
Approved at SA #22 |
2.0.0 |
6.0.0 |
MBMS |
|||
|
SP-23 |
SP-040204 |
22.246 |
0001 |
1 |
Rel-6 |
B |
CR on advertising of capabilities required to receive a particular transmission |
6.0.0 |
6.1.0 |
MBMS |
|
|
SP-23 |
SP-040204 |
S1-040226 |
22.246 |
0002 |
– |
Rel-6 |
F |
Addition of “MBMS transport service” definition |
6.0.0 |
6.1.0 |
MBMS |
|
SP-23 |
SP-040204 |
S1-040227 |
22.246 |
0003 |
– |
Rel-6 |
F |
Clarification on delivery verification for MBMS user services |
6.0.0 |
6.1.0 |
MBMS |
|
SP-23 |
SP-040204 |
22.246 |
0004 |
1 |
Rel-6 |
C |
Using a single MBMS transport service for multiple MBMS user services |
6.0.0 |
6.1.0 |
MBMS |
|
|
SP-25 |
SP-040505 |
S1-040634 |
22.246 |
0005 |
– |
Rel-6 |
D |
Minor corrections to TS 22.246 (MBMS User Services) |
6.1.0 |
6.2.0 |
MBMS |
|
SP-29 |
SP-050530 |
S1-050887 |
22.246 |
0006 |
– |
Rel-7 |
C |
Support of enhanced MBMS user services providing multiple QoS levels (2) |
6.2.0 |
7.0.0 |
MBMSE |
|
SP-29 |
SP-050530 |
S1-050939 |
22.246 |
0007 |
– |
Rel-7 |
C |
Support of enhanced MBMS user services providing multiple QoS levels |
6.2.0 |
7.0.0 |
MBMSE |
|
SP-32 |
SP-060308 |
S1-060513 |
22.246 |
0009 |
– |
Rel-7 |
F |
Proposed CR to clarify the requirements for roaming |
7.0.0 |
7.1.0 |
MBMSE |
|
SP-32 |
SP-060307 |
S1-060609 |
22.246 |
0010 |
– |
Rel-8 |
B |
Requirements on MBMS user service over generic IP accesses |
7.1.0 |
8.0.0 |
MBMSE |
|
SP-33 |
SP-060466 |
S1-060935 |
22.246 |
0011 |
– |
Rel-8 |
A |
Proposed CR to clarify the requirements for roaming (see CR 0009) |
8.0.0 |
8.1.0 |
MBMSE |
|
SP-34 |
SP-060770 |
S1-061433 |
22.246 |
0012 |
– |
Rel-8 |
B |
Requirements for LTE MBMS Television Service |
8.1.0 |
8.2.0 |
LTE |
|
SP-35 |
SP-070131 |
S1-070282 |
22.246 |
0015 |
1 |
Rel-8 |
C |
Requirements for LTE MBMS Television Service |
8.2.0 |
8.3.0 |
SAE-R (LTE) |
|
SP-35 |
SP-070115 |
S1-070181 |
22.246 |
0017 |
– |
Rel-8 |
A |
Parallel, but regional, MBMS Sessions within one MBMS service. |
8.2.0 |
8.3.0 |
MBMSE |
|
SP-36 |
SP-070364 |
S1-070784 |
22.246 |
0021 |
– |
Rel-8 |
A |
CR on Service Class Handling |
8.3.0 |
8.4.0 |
MBMS |
|
SP-39 |
SP-080043 |
S1-080302 |
22.246 |
0022 |
3 |
Rel-8 |
B |
Requirement for delivery verification in MBMS |
8.4.0 |
8.5.0 |
TEI8 |
|
SP-39 |
SP-080043 |
S1-080303 |
22.246 |
0023 |
3 |
Rel-8 |
B |
Requirement for pre-delivery verification in MBMS |
8.4.0 |
8.5.0 |
TEI8 |
|
SP-46 |
SP-090844 |
S1-094275 |
22.246 |
0029 |
1 |
Rel-9 |
F |
Updating to also include E-UTRAN for MBMS |
8.5.0 |
9.0.0 |
TEI9 |
|
2011-03 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.0.0 |
10.0.0 |
|
|
2012-09 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-11 by MCC |
10.0.0 |
11.0.0 |
|
|
2014-10 |
Updated to Rel-12 by MCC |
11.0.0 |
12.0.0 |
||||||||
|
2015-12 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-13 by MCC |
12.0.0 |
13.0.0 |
|
|
2017-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-14 by MCC |
13.0.0 |
14.0.0 |
|
|
2018-06 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-15 by MCC |
14.0.0 |
15.0.0 |
|
|
SA#88e |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
15.0.0 |
16.0.0 |
|
|
2022-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
16.0.0 |
17.0.0 |
|