throbber
.·.oma
`
`Open Mobile Alliance
`
`Service Guide for Mobile Broadcast Services
`Candidate Version 1.1 - 07 Jul 2008
`
`Open Mobile Alliance
`OMA-TS-BCAST Service Guide-V1 1-20080707-D
`
`© 2008 Open Mobile Alliance Ltd. All Rights Reserved.
`Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
`
`Koninklijke KPN NV - Exhibit 2007
`Ericsson Inc. v. Koninklijke KPN NV PTAB-IPR2022-00557
`Page 1 of 213
`
`

`

`OMA-TS-BCAST Service Guide-V1 1-20080707-D
`
`Page 2 (213)
`
`Use of this document is subject to all of the terms and conditions of the Use Agreement located at
`http://www.openmobilealliance.org/UseAgreement.html.
`
`Unless this document is clearly designated as an approved specification, this document is a work in process, is not an
`approved Open Mobile Alliance™ specification, and is subject to revision or removal without notice.
`
`You may use this document or any part of the document for internal or educational purposes only, provided you do not
`modify, edit or take out of context the information in this document in any manner. Information contained in this document
`may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior
`written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided
`that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials
`and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products
`or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document.
`
`Each Open Mobile Alliance member has agreed to use reasonable endeavors to inform the Open Mobile Alliance in a timely
`manner of Essential IPR as it becomes aware that the Essential IPR is related to the prepared or published specification.
`However, the members do not have an obligation to conduct IPR searches. The declared Essential IPR is publicly available
`to members and non-members of the Open Mobile Alliance and may be found on the "OMA IPR Declarations" list at
`http://www.openmobilealliance.org/ipr.html. The Open Mobile Alliance has not conducted an independent IPR review of
`this document and the information contained herein, and makes no representations or warranties regarding third party IPR,
`including without limitation patents, copyrights or trade secret rights. This document may contain inventions for which you
`must obtain licenses from third parties before making, using or selling the inventions. Defined terms above are set forth in
`the schedule to the Open Mobile Alliance Application Form.
`
`NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY THE OPEN
`MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER OR ITS AFFILIATES REGARDING ANY OF
`THE IPR'S REPRESENTED ON THE "OMA IPR DECLARATIONS" LIST, INCLUDING, BUT NOT LIMITED TO THE
`ACCURACY, COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR NOT
`SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL.
`
`THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT,
`PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN
`CONNECTION WITH THE USE OF DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS.
`
`© 2008 Open Mobile Alliance Ltd. All Rights Reserved.
`Used with the permission of the Open Mobile Alliance Ltd. under the terms set forth above.
`
`© 2008 Open Mobile Alliance Ltd. All Rights Reserved.
`Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
`
`Koninklijke KPN NV - Exhibit 2007
`Ericsson Inc. v. Koninklijke KPN NV PTAB-IPR2022-00557
`Page 2 of 213
`
`

`

`OMA-TS-BCAST Service Guide-V1 1-20080707-D
`
`Page 3 (213)
`
`Contents
`
`1.
`
`SCOPE ................................................................................................................................................................................ 7
`
`2. REFERENCES .................................................................................................................................................................. 8
`NORMATIVE REFERENCES .......................................................................................................................................... 8
`2.1
`2.2
`INFORMATIVE REFERENCES ..................................................................................................................................... 10
`
`3. TERMINOLOGY AND CONVENTIONS .................................................................................................................... 11
`3.1
`CONVENTIONS ........................................................................................................................................................... 11
`3.2
`DEFINITIONS .............................................................................................................................................................. 11
`3.3
`ABBREVIATIONS ........................................................................................................................................................ 12
`
`4.
`
`INTRODUCTION ........................................................................................................................................................... 14
`
`4.1
`
`VERSION 1.0 .............................................................................................................................................................. 14
`
`5.
`
`SERVICE GUIDE ............................................................................................................................................................ 15
`
`SERVICE GUIDE DATA MODEL ................................................................................................................................. 15
`5.1
`5 .1.1
`Service Guide Structure and Fragmentation ...................................................................................................... 15
`5.1.2
`Service Guide Elements, Attributes and Meta Data ........................................................................................... 19
`5.2
`ANNOUNCING SERVICE GUIDES WITHIN A SERVICE GUIDE .................................................................................. 110
`5.3
`INTERFACES FOR SERVICE GUIDE GENERATION ................................................................................................... 11 l
`5.3.1
`Service Guide Data Model as Generic Interchange format.. ............................................................................ 11 l
`5.4
`SERVICE GUIDE DELIVERY ..................................................................................................................................... 11 l
`5.4.1
`Encapsulating and identifying fragments ......................................................................................................... 11 l
`Delivery over the Broadcast Channel .............................................................................................................. 133
`5.4.2
`5.4.3
`Delivery over the Interaction Channel ............................................................................................................. 136
`5.5
`SERVICE GUIDE UPDATE AND MANAGEMENT ....................................................................................................... 143
`5.5.1
`Service Guide Update and Management using the Broadcast Channel ........................................................... 144
`Service Guide update and management using the Interaction Channel ........................................................... 150
`5.5.2
`5 .5 .3
`Service Guide Update and Management Cases for Hybrid Broadcast/Interactive Scenario (Informative ) ...... 151
`5.6
`SERVICE GUIDE BACKEND INTERFACES ................................................................................................................ 151
`5.6.1
`Service Guide management in the backend ..................................................................................................... 15 l
`5.6.2
`Service Guide contents exchange .................................................................................................................... 152
`5.7
`USE OF PREVIEWDATA TO SUPPORT SERVICE SWITCHING, BROWSING AND PREVIEW ...................................... 159
`5.7.1
`Preview Data for Service-by-Service Switching .............................................................................................. 161
`5.7.2
`Preview Data for Service Guide Browsing ...................................................................................................... 162
`Preview Data for Service Preview ................................................................................................................... 163
`5.7.3
`5. 7 .4
`Preview Data for Barker .................................................................................................................................. 164
`Preview Data as an alternative to blackout ...................................................................................................... 165
`5.7.5
`5.8
`ASSOCIATING ACCESSES \VITH SERVICES AND CONTENT ....................................................................................... 166
`5.8.1
`Multiple accesses ............................................................................................................................................. 166
`5.8.2
`Association between 'Service' and 'Access' fragment.. .................................................................................. 167
`5.8.3
`Association between 'Service' and 'Access' fragment through 'Schedule' fragment.. ................................... 167
`5.8.4
`Association between 'Content' and 'Access' fragment through 'Service' or 'Schedule' fragment.. ............... 168
`5 .8.5
`Use of' defaultSchedule' and 'onDemand' attributes ...................................................................................... 169
`5.8.6
`Terminal interpretation for content consumption ............................................................................................. 170
`5.8.7
`Distribution Window and Presentation Window for Cachecast Services ........................................................ 172
`6. DISCOVERY OF SERVICE GUIDE .......................................................................................................................... 173
`6.1
`SERVICE GUIDE TRANSMITTED OVER BROADCAST CHANNEL ............................................................................. 173
`6.1.1
`Service Guide Discovery over Broadcast Channel .......................................................................................... 173
`6.1.2
`Service Guide Discovery over Interaction Channel ......................................................................................... 173
`6.2
`SERVICE GUIDE TRANSMITTED OVER INTERACTION CHANNEL ........................................................................... 174
`7. MULTI-LANGUAGE SUPPORT ................................................................................................................................ 175
`7.1
`DECLARING SERVICE GUIDE ELEMENTS IN DIFFERENT LANGUAGES IN THE SERVICE GUIDE ............................. 175
`7.2
`DECLARING COMPONENTS OF THE BROADCAST SERVICE IN DIFFERENT LANGUAGES IN THE SERVICE GUIDE .. 176
`7.2.1
`Service and content specialization with audio tracks and sub-titles ................................................................. 176
`
`© 2008 Open Mobile Alliance Ltd. All Rights Reserved.
`Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
`
`Koninklijke KPN NV - Exhibit 2007
`Ericsson Inc. v. Koninklijke KPN NV PTAB-IPR2022-00557
`Page 3 of 213
`
`

`

`OMA-TS-BCAST Service Guide-V1 1-20080707-D
`
`Page 4 (213)
`
`APPENDIX A.
`
`CHANGE HISTORY (INFORMA TIVE) ............................................................................................ 178
`
`A.l
`A.2
`
`APPROVED VERSION HISTORY ............................................................................................................................... 178
`DRAFT/CANDIDATE VERSION 1.0 HISTORY ........................................................................................................... 178
`
`APPENDIX B.
`
`STATIC CONFORMANCE REQUIREMENTS (NORMATIVE) •••••.•••••••••••••••••••••••••••••.••••••••••••••• 179
`
`B.1
`B.2
`B.3
`B.4
`
`SCR FOR BCAST SERVICE GUIDE CLIENT (SG-C) .............................................................................................. 179
`SCR FOR BCAST SERVICE GUIDE GENERATION/ADAPTATION/DISTRIBUTION (SG-GAD) •••••••••••••••••••••••••••••• 180
`SCR FOR BCAST SERVICE GUIDE SUBSCRIPTION SOURCE (SGSS) ••.••••••••••••••••••••.••••••••••••••••••••••••••••••••.••••••••••• 181
`SCR FOR BCAST SERVICE GUIDE APPLICATION SOURCE (SGAS) ••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••• 182
`
`APPENDIX C.
`
`SERVICE GUIDE APPLICATION SCENARIOS (INFORMATIVE) •••••••••••••••••••••.•••••••••••••••••••••• 183
`
`SCENARIO OF SELECTIVE VIEWING BASED ON THE CODEC REQUIREMENT IN THE SG ••..•••.••••.•••••••••••••••••••••••••••• 183
`C.1
`SCENARIO OF SELECTIVE VIEWING BASED ON THE BANDWIDTH REQUIREMENT IN THE SG ••••.••••••••••••••••••••••••.•• 183
`C.2
`SCENARIO OF A TV PROGRAM WHICH IS BROADCASTED IN TWO LANGUAGES ..................................................... 183
`C.3
`SCENARIO OF A BROADCAST STREAMING SERVICE PROTECTED BY MULTIPLE KEY MANAGEMENT SYSTEMS •• 185
`C.4
`SCENARIO OF A MAIN SERVICE \VITH INTERACTION ••••••••••••.•.•••••••••••••••••••••••••••••••••••••••••••••••.••.•••••••••••••••••••••••••••• 187
`C.5
`C.5.1
`Service (//this.example.com/service/401) ........................................................................................................ 188
`C.5.2
`Schedule (//this.example.com/schedule/501) ................................................................................................... 188
`C.5.3
`Content (//this.example.com/content/601) ....................................................................................................... 189
`C.5.4
`Interactivity Data (////this.example.com/int/801) .............................................................................................. 189
`C.5.5
`Access (//this.example.com/access/901) .......................................................................................................... 190
`C.5.6
`Access (//this. example.com/access/902) ......................................................................................................... 190
`C.6
`SCENARIO OF A MAIN SERVICE WITH PURCHASABLE PROTECTED AUXILIARY DATA CONTENT •••••••••••••••••••••••••.. 191
`C.7
`SCENARIO OF MULTIPLE SERVICES PROVIDED WITH SINGLE CHANNEL EACH •••••...••.•••.•••••••••••••••••••••••••••••••••••••• 192
`C.8
`SCENARIO OF BUNDLING MULTIPLE CHANNELS INTO A SINGLE SERVICE •••••••••••••••••••••..•••••••••••••••••••••••••••••••••••••. 193
`C.9
`SCENARIO OF USING SINGLE SERVICE GUIDE TO PROVIDE SERVICE DESCRIPTIONS FOR MULTIPLE SERVICE
`PROVIDERS .......................................................................................................................................................................... 195
`C.10
`SCENARIO OF SERVICE GUIDE ANNOUNCING OTHER SERVICE GUIDES •••••••••••.••.•••••••••••••••••••••••••••..••••••••••••••• 198
`C.11
`SCENARIO OF SERVICE GUIDE WITH BOTH BROADCAST AND UNICAST SERVICES •••••••••••••••••••••••••••.•••••••••••••• 200
`
`APPENDIX D.
`
`EXAMPLE OF SGDD AND SGDU ..................................................................................................... 206
`
`APPENDIX E.
`
`SERVICE CLASS IDENTIFIER HANDLING (NORMATIVE) ••••••••.•••••••.••••••••.••••••••••••••••••••••.••••• 207
`
`DEFINITION OF SERVICE CLASS VALUES ................................................................................................................. 207
`E.l
`E.1.1
`Service Class Definition .................................................................................................................................. 207
`E.1.2
`Service Class Naming and Registration ........................................................................................................... 207
`E.2
`SERVICE CLASSES DEFINED IN OMA BCAST ·······································································································207
`E.2.1
`urn:oma:bcast:oma _ bsc:sg: 1.0 ......................................................................................................................... 207
`um:oma: bcast:oma bsc:fc: 1.0 ......................................................................................................................... 208
`E.2.2
`E.2.3
`urn:oma:bcast:oma_bsc:tp:1.0 ......................................................................................................................... 208
`E.2.4
`um:oma:bcast:oma_bsc:nt:1.0 ......................................................................................................................... 208
`E.2.5
`urn:oma: bcast:oma _ bsc:csg: 1.0 ....................................................................................................................... 208
`E.2.6
`urn:oma: bcast:oma _ bsc:st: 1.0 .......................................................................................................................... 208
`E.2. 7
`um:oma: bcast:oma _ bsc:rifc: 1.0 ....................................................................................................................... 208
`APPENDIXF.
`GLOBAL STATUS CODES ••••••••••••.•.•••••..••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••.•••••••••••••••. 209
`
`APPENDIX G. MIME MEDIA TYPES ......................................................................................................................... 210
`
`G.l MEDIA-TYPE REGISTRATION REQUEST FOR APPLICATION/VND.OMA.BCAST.SGDU ............................................ 210
`G.2 MEDIA-TYPE REGISTRATION REQUEST FOR APPLICA TION/vND.OMA.BCAST.SGDD+XML •••••••••••••••••••••••••••••••••• 211
`
`APPENDIX H. APPENDIX H. IDENTIFICATION OF UNIQUE ELEMENTS (NORMA TIVE) •••••••••••••••••••••••••• 213
`
`H.1
`H.2
`
`DEFINITION OF BCAST IDENTIFICATION AUTHORITY ••••••••••••••••••••••••••••••••••••••••••••.•.••••••••••••••••••••••••••••••••••••••••.• 213
`IDENTIFICATION OF CONTENT WITH BASECID ••••••••••••••.•••••••••••.••••••••••••••••••••••••••••••..••••••••••••••••••••••••••••••••••••••••••. 213
`
`Figures
`
`Figure 1: Structure of Service Guide ••••••••••••••••••••••..•••••••••••••••••••••••••••••••••••••••••••••••••••••.•••••••••••••••••••••••••••••.•••••••.••••••••••••••••. 16
`
`Figure 2: Cardinalities and Reference Direction between Service Guide Fragments ....................................................... 17
`
`© 2008 Open Mobile Alliance Ltd. All Rights Reserved.
`Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
`
`Koninklijke KPN NV - Exhibit 2007
`Ericsson Inc. v. Koninklijke KPN NV PTAB-IPR2022-00557
`Page 4 of 213
`
`

`

`OMA-TS-BCAST Service Guide-V1 1-20080707-D
`
`Page 5 (213)
`
`Figure 3: SG fragment change and its propagation on the different levels of Service Guide, when Split-TOI is not used
`neither for SGDU nor for SGDD .................................................................................................................................. 145
`
`Figure 4: Fragment version change and its detection at ALC packet header level of SGDU/SGDD delivery, when Split-
`TO I is used ...................................................................................................................................................................... 146
`
`Figure 5: New fragment introduced and its detection at ALC packet header level ofSGDU delivery, when Split-TOI is
`used ................................................................................................................................................................................. 147
`
`Figure 6: New fragment introduced and its propagation on the different levels of Service Guide, when Split-TOI is not
`used ................................................................................................................................................................................. 148
`
`Figure 7: Algorithm for determining a subset of Service Guide ........................................................................................ 150
`
`Figure 8: Example case how preview data supports service-by-service switching ........................................................... 162
`
`Figure 9: Example case how preview data supports Service Guide browsing with schedule view ................................. 162
`
`Figure 10: Example case how preview data supports Service Guide browsing with purchase view .............................. 163
`
`Figure 11: Example case how preview data supports service preview .............................................................................. 164
`
`Figure 12: Example case how preview data supports barker ............................................................................................ 165
`
`Figure 13: Example case how preview data supports alternative to blackout ................................................................. 166
`
`Figure 14: Use of SG to signal service and content protection information ..................................................................... 185
`
`Figure 15: Service example on a timeline ............................................................................................................................ 187
`
`Figure 16: Service Guide example for main service with interactivity ............................................................................. 187
`
`Figure 17: Simple encapsulation of Service Guide fragments in this example ................................................................. 188
`
`Figure 18: Service example on a timeline ............................................................................................................................ 191
`
`Figure 19: Service Guide example for main Service with value-added, protected data .................................................. 191
`
`Figure 20: Simple encapsulation of Service Guide fragments in this example ................................................................. 192
`
`Figure 21: Service Guide example ........................................................................................................................................ 193
`
`Figure 22: Simple encapsulation of Service Guide fragments in this example ................................................................. 193
`
`Figure 23: Service Guide figure ............................................................................................................................................ 194
`
`Figure 24: Simple encapsulation of Service Guide fragments in this example ................................................................. 195
`
`Figure 25: Service Guide figure ............................................................................................................................................ 196
`
`Figure 26: Service Guide example ........................................................................................................................................ 199
`
`Figure 27: Simple encapsulation of Service Guide fragments in this example ................................................................. 200
`
`Figure 28: Service example on a timeline ............................................................................................................................ 201
`
`Figure 29: Service Guide Delivery Descriptor role in Service Guide delivery showing SG fragments grouped by time
`......................................................................................................................................................................................... 206
`
`Tables
`Table 1: Service Guide Delivery Unit structure .................................................................................................................. 114
`
`© 2008 Open Mobile Alliance Ltd. All Rights Reserved.
`Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
`
`Koninklijke KPN NV - Exhibit 2007
`Ericsson Inc. v. Koninklijke KPN NV PTAB-IPR2022-00557
`Page 5 of 213
`
`

`

`OMA-TS-BCAST Service Guide-V1 1-20080707-D
`
`Page 6 (213)
`
`Table 2: Mnemonics used in Table 1 .................................................................................................................................... 114
`
`Table 3: Semantics for Table 1 ............................................................................................................................................. 116
`
`Table 4: Uses of 'PreviewData' fragment when referenced by other Service Guide fragments ..................................... 161
`
`Table 5: Elements that can be specialized for different Ianguages .................................................................................... 176
`
`Table 6· SGDD Example ....................................................................................................................................................... 197
`
`Table 7· SGDD Example ....................................................................................................................................................... 198
`
`Table 8: Cross Reference Table (Informative) .................................................................................................................... 209
`
`© 2008 Open Mobile Alliance Ltd. All Rights Reserved.
`Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
`
`Koninklijke KPN NV - Exhibit 2007
`Ericsson Inc. v. Koninklijke KPN NV PTAB-IPR2022-00557
`Page 6 of 213
`
`

`

`OMA-TS-BCAST Service Guide-V1 1-20080707-D
`
`Page 7 (213)
`
`1. Scope
`
`The scope of this specification is the Service Guide functionality of OMA Mobile Broadcast Enabler. The Service Guide
`functionality is used to provide information about the services and contents available via broadcast channel, interaction
`channel or both.
`
`The present document defines the Service Guide data model, the interfaces, the delivery and the discovery of the Service
`Guide functionality (including the declaration of Service Guides within a Service Guide) and the use of Preview Data for
`services switching, browsing and preview.
`
`© 2008 Open Mobile Alliance Ltd. All Rights Reserved.
`Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
`
`Koninklijke KPN NV - Exhibit 2007
`Ericsson Inc. v. Koninklijke KPN NV PTAB-IPR2022-00557
`Page 7 of 213
`
`

`

`OMA-TS-BCAST Service Guide-V1 1-20080707-D
`
`Page 8 (213)
`
`2. References
`
`2.1 Normative References
`[3GPP TS 22.022]
`
`"Personalisation ofGSM Mobile Equipment (ME); Mobile functionality specification", 3rd Generation
`Partnership Project, Technical Specification 3GPP TS 22.022 Release 6,
`URL: http://www.3gpp.orghttp://www.3gpp.org/
`
`[3GPP TS 23.003)
`
`[3GPP TS 26.346)
`
`[3GPP TS 31.102]
`
`[3GPP TS 33.220]
`
`"Numbering, Addressing and Identification", 3rd Generation Partnership Project TS 23.003 Release 6,
`URL: http://www.3gpp.org/ftp/Specs/
`
`"Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs", 3rd Generation Partnership
`Project TS 26.346 Release 6,
`URL: http://www.3gpp.org/ftp/Specs/
`
`"Characteristics of the Universal Subscriber Identity Module (USIM) application", 3rd Generation
`Partnership Project, Technical Specification 3GPP TS 31.102, Release 6,
`URL: http://www.3gpp.org/
`
`"Generic Authentication Architecture, Generic Bootstrapping Architecture", 3rd Generation Partnership
`Project, Technical Specification 3GPP TS 33.220 Release 6,
`URL: http://www.3gpp.org
`
`[3GPP2 C.S0002-0]
`
`3GPP2 C.S0002-0 "Physical Layer Standard for cdma2000 Spread Spectrum Systems", Release 0
`
`[3GPP2 C.S000S-D]
`
`[3GPP2 C.S0023-C)
`
`3GPP2 C.S0024-D v2.0 "Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum
`Systems," Release D
`
`"http://www.3gpp2.org/Public html/specs/C.S0023-C v1 .0 060530.pdfRemovable User Identity
`Module for Spread Spectrum Systems", 3rd Generation Partnership Project 2, Technical Specification
`3GPP2 C.S0023, Release C, Version 1.0, June 2006,
`URL: http://www.3gpp2.org/
`
`[3GPP2 C.S0024-A]
`
`3GPP2 C.S0024-A v2.0 "cdma2000 High Rate Packet Data Air Interface Specification", Release A
`
`[3GPP2 C.S0054-0]
`
`[3GPP2 C.S0065-0]
`
`[3GPP2 C.S0068-0]
`
`3GPP2 C.S0054-0 v2.0 "cdma000 High Rate Broadcast-Multicast Packet Data Air Interface
`Specification"
`
`"cdma2000 Application on UICC for Spread Spectrum Systems", 3rd Generation Partnership Project 2,
`Technical Specification 3GPP2 C.S0065, Release 0, Version 1.0, June 2006,
`URL: http://www.3gpp2.org/
`
`"ME Personalization for cdma2000 Spread Spectrum Systems", 3rd Generation Partnership Project 2,
`Technical Specification 3GPP2 C.S0068, Release 0, Version 1.0, May 2006,
`URL: http://www.3gpp2.org/
`
`[BCASTl0-BCMCS(cid:173)
`Adaptation]
`
`"Broadcast Distribution System Adaptation- 3GPP2/BCMCS", Open Mobile Alliance™, OMA-TS(cid:173)
`BCAST_BCMCS_Adaptation-VI_0,
`URL: http://www.openmobilealliance.org/
`
`[BCASTl 0-Distribution]
`
`"File and Stream Distribution for Mobile Broadcast Services", Open Mobile Alliance™, OMA-TS(cid:173)
`BCAST _Distribution-VI_ 0,
`URL: http://www.openmobilealliance.org/
`
`[BCASTl0-DVBH(cid:173)
`IPDC-Adaptation]
`
`[BCASTl 0-MBMS(cid:173)
`Adaptation]
`
`[BCASTl0-
`Rcquircmcnts]
`
`[BCASTl0-
`ServContProt]
`
`"Broadcast Distribution System Adaptation- IPDC over DVB-H", Open Mobile Alliance™, OMA-TS(cid:173)
`BCAST _DVB_ Adaptation-VI_ 0,
`URL: http://www.openmobilealliance.org/
`
`"Broadcast Distribution System Adaptation - 3GPP/MBMS", Open Mobile Alliance™, OMA-TS(cid:173)
`BCAST _ MBMS _Adaptation-VI_ 0,
`URL: http://www.openmobilealliance.org/
`
`"Mobile Broadcast Services Requirements", Open Mobile Alliance™, OMA-RD-BCAST-VI_0,
`URL: http://www.openmobilealliance.org/
`
`"Service and Content Protection for Mobile Broadcast Services", Open Mobile Alliance™, OMA-TS(cid:173)
`BCAST_SvcCntProtection-VI_0,
`URL: http://www.openmobilealliance.org/
`
`© 2008 Open Mobile Alliance Ltd. All Rights Reserved.
`Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
`
`Koninklijke KPN NV - Exhibit 2007
`Ericsson Inc. v. Koninklijke KPN NV PTAB-IPR2022-00557
`Page 8 of 213
`
`

`

`OMA-TS-BCAST Service Guide-V1 1-20080707-D
`
`Page 9 (213)
`
`[BCASTI 0-Scrviccs]
`
`"Mobile Broadcast Services", Open Mobile Alliance™, OMA-TS-BCAST_Services-Vl_0,
`URL: http://www.openmobilealliance.org/
`
`[BCASTl0-Schcma-sg-f]
`
`"Mobile Broadcast Services -XML Schema for Service Guide Fragments", Open Mobile Alliance™,
`OMA-SUP-XSD _bcast_sg_fragments-V 1_0,
`URL: http://www.openmobilealliance.org/
`
`[BCASTI 0-Schcma-sg(cid:173)
`bc]
`
`[BCASTl0-Schcma-sg(cid:173)
`sgdd]
`
`[DRM20-Broadcast(cid:173)
`Extcnsions]
`
`"Mobile Broadcast Services - XML Schema for Service Guide Backend Interfaces", Open Mobile
`Alliance™, OMA-SUP-XSD_bcast_sg_backend-Vl_0,
`URL: http://www.openmobilealliance.org/
`
`"Mobile Broadcast Services -XML Schema for SGDD", Open Mobile Alliance™, OMA-SUP(cid:173)
`XSD_bcast_sg_sgdd-Vl_0,
`URL: http://www.openmobilealliance.org/
`
`"OMA ORM v2.0 Extensions for Broadcast Support", Open Mobile Alliance™, OMA-TS-DRM-XBS(cid:173)
`Vl_0,
`URL: http://www.openmobilealliance.org/
`
`[HTML401]
`
`[IOPPROC]
`
`[ITU-MNC]
`
`[MIGFGJ
`
`[OMAMLP]
`
`[OMNAJ
`
`[RFC 1035]
`
`[RFC 1123]
`
`[RFC I305]
`
`[RFC 1952)
`
`[RFC 2046]
`
`[RFC 2119)
`
`[RFC 2234]
`
`[RFC 2246]
`
`[RFC 2326]
`
`HTML 4.01 Specification, W3C Recommendation 24 December 1999,
`URL: http://www.w3.org/TR/html4/.
`
`"OMA Interoperability Policy and Process", Version 1.1, Open Mobile Alliance™, OMA-IOP-Process(cid:173)
`Vl_l,
`URL: URL:http://w,vw.openmobilealliance.org/
`
`"Annex to ITU Operational Bulletin No. 871 - 1.XI.2006, Mobile Network Code (MNC) for the
`international identification plan for mobile terminals and mobile users (According to ITU-T
`Recommendation E.212 (05/2004))"
`URL: http://www.itu.int/
`
`The Moving Image Genre-Form Guide, Library of US Congress,
`URL: http://www.loc.gov/rr/mopic/miggen.html
`
`"Mo

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket