Universal Mobile Telecommunications System (UMTS); Study on Personal Broadcast Service (PBS) (3GPP TR 22.947 version 15.0.0 Release 15)

RTR/TSGS-0122947vf00

General Information

Status
Published
Publication Date
22-Jul-2019
Technical Committee
Current Stage
12 - Completion
Completion Date
23-Jul-2019
Ref Project

Buy Standard

Standard
ETSI TR 122 947 V15.0.0 (2019-07) - Universal Mobile Telecommunications System (UMTS); Study on Personal Broadcast Service (PBS) (3GPP TR 22.947 version 15.0.0 Release 15)
English language
20 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

ETSI TR 122 947 V15.0.0 (2019-07)






TECHNICAL REPORT
Universal Mobile Telecommunications System (UMTS);
Study on Personal Broadcast Service (PBS)
(3GPP TR 22.947 version 15.0.0 Release 15)

---------------------- Page: 1 ----------------------
3GPP TR 22.947 version 15.0.0 Release 15 1 ETSI TR 122 947 V15.0.0 (2019-07)



Reference
RTR/TSGS-0122947vf00
Keywords
UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2019.
All rights reserved.

DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and
of the oneM2M Partners.
®
GSM and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TR 22.947 version 15.0.0 Release 15 2 ETSI TR 122 947 V15.0.0 (2019-07)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
Legal Notice
This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.
Modal verbs terminology
In the present document "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be
interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 3 ----------------------
3GPP TR 22.947 version 15.0.0 Release 15 3 ETSI TR 122 947 V15.0.0 (2019-07)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 5
Introduction . 5
1 Scope . 6
2 References . 6
3 Definitions, symbols and abbreviations . 6
3.1 Definitions . 6
3.2 Symbols . 7
3.3 Abbreviations . 7
4 General description. 7
4.1 Service concept and definition . 7
4.2 Roles of actors in use cases . 8
4.2.1 Personal Broadcast Content Provider (PBCP) . 8
4.2.2 Personal Broadcast Service Provider (PBSP) . 8
4.2.3 Broadcast Service User (BSU). 8
4.2.4 Mobile Broadcast/Multicast Network Operator (MBNO) . 8
5 Use cases . 10
5.1 Receive only personal streaming content services . 10
5.1.1 Service description . 10
5.1.2 Service benefit . 10
5.1.3 Additional remarks . 10
5.1.4 Service requirements. 10
5.2 Interactive Personal Broadcast Services . 11
5.2.1 Service description . 11
5.2.2 Service benefit . 11
5.2.3 Additional remarks . 11
5.2.4 Service requirements. 11
5.3 Mobile Content Provider Service . 12
5.3.1 Service description . 12
5.3.2 Service benefit . 12
5.3.3 Additional remarks . 13
5.3.4 Service requirements. 13
5.4 Public Transport Information Broadcast Service . 13
5.4.1 Service description . 13
5.4.2 Service benefit . 14
5.4.3 Additional remarks . 14
5.4.4 Service requirements. 14
5.5 Shared VoD Service . 14
5.5.1 Service description . 14
5.5.2 Service benefit . 15
5.5.3 Additional remarks . 15
5.5.4 Service requirements. 15
5.6 Personal Download Content Service . 15
5.6.1 Service description . 15
5.6.2 Service benefit . 16
5.6.3 Additional remarks . 16
5.6.4 Service requirements. 16
5.7 Localized Broadcast Service . 16
5.7.1 Service description . 16
5.7.2 Service benefit . 16
ETSI

---------------------- Page: 4 ----------------------
3GPP TR 22.947 version 15.0.0 Release 15 4 ETSI TR 122 947 V15.0.0 (2019-07)
5.7.3 Additional remarks . 17
5.7.4 Service requirements. 17
6 Charging . 17
7 Security. 17
8 Conclusion . 17
Annex A: Change history . 18
History . 19

ETSI

---------------------- Page: 5 ----------------------
3GPP TR 22.947 version 15.0.0 Release 15 5 ETSI TR 122 947 V15.0.0 (2019-07)
Foreword
rd
This Technical Report has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
As a mobile service network evolves to a versatile packet data network, the service paradigm of mobile operators is
gradually shifting from voice oriented communication to multimedia information sharing. A mobile device is no longer
a simple tool for person to person communication, but now becomes an indispensable item for receiving essential
information distributed for human society. Information for entertainment services such as TV or Radio show, as well as
information for public safety, energy saving, environmental conservation, and for searching emergency aid, need to be
delivered to the right person at the right time in any location. The multimedia broadcast service, MBMS [2], and packet
switched streaming [8][9] is a widely deployed technique which fulfils the basic service requirements. However
provisioning of content is currently allowed for a limited group of content providers, and ordinary users have no way to
utilize the service.
The rationale of Personal Broadcast Service is to give an open opportunity for ordinary people to generate content, and
broadcast it on air. A variety of broadcast services and a new device market may emerge once users are able to access
the content distribution service. Abundant broadcast content will be available to be selected by 3GPP users. The extent
of other potential service area is unbounded.
The objective of this document is to present some envisaged use cases of Personal Broadcast Service, for creative
engineers and standard developers to pursue further investigation of PBS, and move to the next steps necessary for
enhancement of relevant 3GPP standards.
ETSI

---------------------- Page: 6 ----------------------
3GPP TR 22.947 version 15.0.0 Release 15 6 ETSI TR 122 947 V15.0.0 (2019-07)
1 Scope
This Technical Report presents potential use cases of Personal Broadcast Service. It aims to take account of service and
system aspect of PBS. The minimum set of service requirements associated with each use case will be identified.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.146: "Multimedia Broadcast/Multicast Service; Stage 1".
[3] 3GPP TS 22.246: "Multimedia Broadcast/Multicast Service (MBMS) user services".
[4] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional
description".
[5]  ETSI TS 181 016 v.2.0.0, "Telecommunications and Internet converged Services and Protocols for
Advanced Networking (TISPAN); Service Layer Requirements to Integrate NGN Services and
IPTV," 2007-11
[6]  OMA, "Mobile Broadcast Services Requirements," Approved Version 1.0 – 12 Feb 2009
[7]  3GPP TS 22.115: “Service Aspects; Charging and Billing (Release-9)”
[8] 3GPP TS 22.233: "Transparent end-to-end packet-switched streaming service; Stage 1".
[9] 3GPP TS 26.234: " Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols
and codecs".
[10] 3GPP TS 26.346: "Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs".
[11] U.S. Department of Transportation Research and Innovative Technology Administration,
“Intelligent Transportation Systems Benefits, Costs, Deployment, and Lessons Learned:2008
Update”, September 2008, www.its.dot.gov
[12] ERTICO - ITS Europe, “Activities 2008”, 08 May 2008, www.ertico.com
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A
term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
(void)
ETSI

---------------------- Page: 7 ----------------------
3GPP TR 22.947 version 15.0.0 Release 15 7 ETSI TR 122 947 V15.0.0 (2019-07)
3.2 Symbols
For the purposes of the present document, the following symbols apply:
(void)

3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
TR 21.905 [1].
BSU Broadcast Service User
CoD Contents on Demand
MBNO Mobile Broadcast/Multicast Network Operator
PBS Personal Broadcast Service
PBSP Personal Broadcast Service Provider
PBSF Personal Broadcast Service Function
PBCP Personal Broadcast Contents Provider
UGC User Generated Contents
VoD Video on Demand

4 General description
4.1 Service concept and definition
Personal Broadcast Service (PBS) is a content distribution service using 3GPP accesses. This enables any Internet user,
private company or mobile user to generate content, and broadcast/multicast it to mobile users. Types of User
Generated Content (UGC) in this context include not only multimedia files such as video, audio or image, but also
variety of digital information distributed for various purposes such as e.g. public safety, energy saving, environment
conservation.
The User Generated Content can be distributed in either a time unconstrained Content on-Demand (CoD) method, or in
a time constrained, real-time method. In the former case, the contents are uploaded to a server and downloaded at the
request of users at a convenient time. Most CoD applications and some MBMS user services may be delivered using
unicast bearers as defined in [3][10]. However in some application, CoD users may share the content using multicast
bearer service. A use case of shared VoD service is presented in this document.
In the case of live broadcast, content is delivered to multiple users simultaneously, as such a broadcast or multicast
bearer is necessary for resource saving. A broadcast bearer service [3] is efficient when a large number of receivers are
expected and the receivers are spread in many cellular areas. Major TV or Radio services are examples that may utilize
such a broadcast bearer. UGC stream may also be transmitted using broadcast bearer if the population of receivers
justifies cost for delivering the content. Private show of very popular celebrity or daily episodes of small production
company may be a potential example. Another area of use case is localized broadcast in campus, theatre or theme park.
Details of the use cases are presented in this document.
In contrast to broadcast bearer service, UGC will be delivered using multicast bearer service in many use cases. Content
providers of Personal Broadcast Service may appear and disappear at any time. Content distribution may commence on
an ad-hoc basis. Therefore, it will be inefficient to pre-allocate resources for such unpredictable content providers. New
interfaces and requirements will be necessary to support such content providers. The communication may occasionally
be bi-directional. Interactive data generated by mobile receivers needs to be passed to content providers. Some
additional functions, e.g. time-stamping or adding cell ID, may need to be performed on upstream user data. This
aspects associated with interactivity will be discussed in detail.
Currently, 3GPP supports an OMA [6] defined interface to be used between mobile operator and broadcast content
provider [4]. Therefore, most broadcast applications that require a static allocation of resource may be supported using
existing 3GPP and OMA standards. However new set of requirements and standards may be necessary to support
distinctive features of PBS use cases as introduced in this document.
ETSI

---------------------- Page: 8 ----------------------
3GPP TR 22.947 version 15.0.0 Release 15 8 ETSI TR 122 947 V15.0.0 (2019-07)
4.2 Roles of actors in use cases
The roles of major actors used in the description of each use case are explained in this section.
4.2.1 Personal Broadcast Content Provider (PBCP)
Personal Broadcast Content Provider (PBCP) is an individual or organization that produces electronic content for the
purpose of distribution to mobile users. Any Internet user, company, school, government or even major TV or radio
broadcasting company can be a Personal Broadcast Content Provider if one uses PBS.
In order to provide PBS service, PBCP needs to make information about the content available to a service provider, and
reserve necessary resources via a wired or wireless connection that will be used for content delivery. The connection
may be established via Internet or 3GPP radio access. When 3GPP radio access is used, the type of content provider is
referred to Mobile PBCP. The Mobile PBCP is a 3GPP user, and the user typically generates contents while it is
moving.
PBCP may receive user data via the Internet. For example, interactive data transmitted by service users, or user
information provided by mobile operator can be delivered to PBCP.
4.2.2 Personal Broadcast Service Provider (PBSP)
Personal Broadcast Service Provider (PBSP) is an independent service provider whose major role is brokering content
delivery between PBCPs and the mobile operator. While it is always possible for a mobile operator to directly receive
contents from PBCPs without the involvement of PBSP, independent service providers may do better business by
advertising, collecting good PBCPs and developing convenient User Interface software. Use cases in this document
assume the role of PBSP between mobile operator and PBCP.
In some use cases, distinction between PBCP and PBSP is unclear. An example is when a PBSP creates contents using
automated content production machine or unmanned device, e.g. game server, surveillance camera. In such case, the
role of PBSP and PBCP are combined.
4.2.3 Broadcast Service User (BSU)
The Broadcast Service User (BSU) is typically a 3GPP UE that consumes PBS content distributed via 3GPP accesses.
Some use cases assume a dedicated PBS service terminal integrated with a vehicle (e.g. car audio, GPS navigation) be
used rather than a hand held device. The actual transmission method (i.e. unicast, MBMS) is transparent to the BSU.
4.2.4 Mobile Broadcast/Multicast Network Operator (MBNO)
The Mobile Broadcast Network Operator (MBNO) provides content distribution services to PBSP and PBCP. The
service typically includes distribution of content information, session notification and content transmission. MBNO is
responsible for protecting content from unauthorized access by users. MBNO may report information of usage statistics
(e.g. receiver population, resource consumption, access failure of user) to PBSP and PBCP.
When an interactive service is requested, the MBNO provides reliable bi-direction communication path between BSUs
and PBSP (or PBCP). Upon reception of BSU data, MBNO may perform access control, fairness control, DoS
ETSI

---------------------- Page: 9 ----------------------
3GPP TR 22.947 version 15.0.0 Release 15 9 ETSI TR 122 947 V15.0.0 (2019-07)
prevention and other filtering actions. MBNO may further perform some value added functions on the BSU data, such
as e.g. time-stamping, appending cell identity.
Figure 1 below shows an example of service association between the actors.
Note: This diagram is intended to provide clarification of the MBNO service interaction with other actors.


Figure 1: MBNO service association with actors
In Figure 1, the PBSF (Personal Broadcast Service Function) box depicts an interconnection point with PBSP, PBCP
and Mobile PBCP. The PBSF may be a sub-function of the BM-SC [4] or an independent network element. Details of
the architectural description are beyond the scope of this document.
Figure 1 illustrates that MBNO needs to provide external interfaces to PBSP and PBCP respectively, and an internal
interface via network of the Mobile PBCP. The interfaces are used for dynamic resource provisioning , content
delivery, information transfer, upstream data delivery, and there may be other uses. The interface between MBNO and
broadcast content provider is used for static resource provisioning, and it is shown for completeness.

ETSI

---------------------- Page: 10 ----------------------
3GPP TR 22.947 version 15.0.0 Release 15 10 ETSI TR 122 947 V15.0.0 (2019-07)
5 Use cases
5.1 Receive only personal streaming content services
5.1.1 Service description
The receive only personal streaming content service is similar to real-time Internet TV or radio service. Any Internet
user or 3GPP user may register the service, and distribute contents at their convenient time. The content provider (i.e.
PBCP) should be able to negotiate resources and costs for distribution of contents. The negotiation may be performed
directly with operator (i.e. MBNO) or indirectly via PBSP. Failure of receiver (i.e. BSU) access to the content due to
resource shortage or UE incapability should be reported to PBCP, therefore PBCP may adjust resource demand of the
content.
Notification should be given to BSUs prior to PBS session initiation. The BSU may choose categories of broadcast to
be notified about, e.g. from an electronic service guide. The service system of this use case must be able to support
various size of BSU group, from single user to hundreds of users per cell.
From a user's perspective, the service type is similar to operator provided TV or VoD service [3]. List of available PBS
streams may be provided and users may change content streams. Latency for content switching must be within a
bearable bound to the user’s perception.
BSUs should be able to access PBS service using third party software which is not supplied by MBNO or PBSP.
QoS should be supported. Resource allocation may be triggered by the request of user or by service provider. It should
be possible to report the number of users to the service provider, and remove resource when there is no more a user
receiving the service.
A number of subscription and c
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.