Method and system for transmitting and receiving access information for a broadcast service
Abstract
A broadcasting system for providing access information of a broadcast service, wherein a transmission apparatus generates the access information for at least one of a broadcast network and an interaction network, from which the broadcast service is transmitted, and transmits the access information to a terminal via a specific communication network. A reception apparatus receives the access information of the broadcast service via the communication network, analyzes the received access information to determine a network from which the broadcast service is provided, among the broadcast network and the interaction network, and sets an access address for reception of the broadcast service.
Term
Term ended
Projected expiry passed 11 August 2026, 0.1 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
65 claims: 5 independent, 60 dependent
- 1A method for transmitting access information of a broadcast service in a transmitter of a broadcasting system, the method comprising the steps of:generating access information for at least one of a broadcast network and an interaction network, via which broadcast service is transmitted;andtransmitting the access information to a terminal via a specific communication network.
- 16An apparatus for transmitting access information of a broadcast service in a transmitter of a broadcasting system, the apparatus comprising:an access information generator for generating access information for at least one of a broadcast network and an interaction network, via which broadcast service is transmitted;anda transmitter for transmitting the access information to a terminal via a specific communication network.
- 31A method for receiving access information of a broadcast service in a terminal of a broadcasting system, the method comprising the steps of:receiving, via a specific communication network, access information for at least one of a broadcast network and an interaction network, from which broadcast service is transmitted;andreceiving the broadcast service from the at least one of the broadcast network and the interaction network according to the received access information.
- 47An apparatus for receiving access information of a broadcast service in a terminal of a broadcasting system, the apparatus comprising:a receiver for receiving, via a specific communication network, access information for at least one of a broadcast network and an interaction network from which broadcast service is transmitted and receiving the broadcast service from the at least one of the broadcast network and the interaction network according to the received access information.
- 63A broadcasting system providing access information of a broadcast service, comprising:a transmission apparatus for generating access information for at least one of a broadcast network and an interaction network, from which broadcast service is transmitted, and transmitting the access information to a terminal via a specific communication network;anda reception apparatus for receiving, via a specific communication network, the access information of the broadcast service and receiving the broadcast service from the at least one of the broadcast network and the interaction network according to the received access information.
Independent claims5
130 paragraphs, as filed
<u style="single">BACKGROUND OF THE INVENTION</u>
Field of the Invention
:
The present invention relates generally to a method and apparatus for providing broadcast services in a broadcasting system. In particular, the present invention relates to an access information transmission/reception method and apparatus for efficiently achieving access to broadcast services, and a system and terminal thereof.
Description of the Related Art
:
The mobile communication market continuously requires production of new services through for example, the recombination or integration of existing technologies. Today, with the development of communication and broadcast technologies, the conventional broadcasting system or mobile communication system has reached the phase of providing broadcast services through portable terminals (or mobile terminals), such as mobile phones and personal digital assistants (PDAs). Due to the latent and actual market needs and the increasing demand for multimedia services, the service providers' intended strategies for providing new services such as broadcast service in addition to the existing voice service, and the identified interests of Information Technology (IT) companies which are bolstering their mobile communication businesses to meet the user's demands, convergence of the mobile communication service and the Internet Protocol (IP) has become the mainstream of development of the next generation mobile communication technologies.
The Open Mobile Alliance (OMA), one of the standardization groups for broadcast services, was established in June, 2002, by about 200 companies including Nokia, NTT and IBM, to perform research on the standard for interworking between individual mobile solutions. The OMA mainly serves to define various application standards for mobile games and Internet services. Of the working groups belonging to the OMA, the Open Mobile Alliance Browser and Content Mobile Broadcast Sub Working Group (OMA BAC BCAST) is now performing research on the technology for providing broadcast services using mobile terminals. A brief description will now be made of the broadcasting system which is under discussion in the OMA.
In a BCAST system, which is a broadcasting system proposed by the OMA, a mobile terminal desiring to receive a broadcast service should receive so-called service guide information containing description information for the service, billing information for the service, and information on a receiving method for the service. The mobile terminal receives the service according to the information provided through the service guide information. A description will now be made of the conventional broadcast service access method with reference to the BCAST system as an example of the general broadcasting system using the service guide. FIG. 1 is a block diagram illustrating a structure of a service guide used for receiving broadcast services in a general broadcasting system. This structure is proposed to provide broadcast services to the mobile terminal in the BCAST system. One service guide is comprised of a plurality of groups each having its own purpose, and all the groups are classified into four groups according to use, as shown in FIG 1. FIG. 1 illustrates an exemplary service guide comprised of an administrative group 100, a provisioning group 110, a core group 120, and an access group 130.
The administrative group 100 is a group for providing basic information needed by a mobile terminal to receive a service guide and includes a service guide context fragment 101 and a service guide delivery descriptor fragment 102. The service guide context fragment 101 provides a service guide identifier (ID), identification information of the service provider that generated and transmitted the service guide, and the entire information on the service guide. The service guide delivery descriptor fragment 102 provides a channel capable of receiving fragments for a plurality of service guides, scheduling information, and update information to a mobile terminal so that the mobile terminal may receive only the necessary service guide at an appropriate time.
The provisioning group 110 is a group for providing fee information for service reception and includes a purchase item fragment 111, a purchase data fragment 112, and a purchase channel fragment 113. The purchase item fragment 111 provides fee information for a service or a service bundle, the purchase data fragment 112 provides information indicating how a service user can pay the fee, and the purchase channel fragment 113 provides information on the system where the service user can actually purchase the service.
The core group 120 is a group for providing information on the service itself and includes a service fragment 121, a schedule fragment 122, and a content fragment 123. The service fragment 121 provides a description of the service itself that the user will receive, and also provides information indicating with which content the service can be configured. The schedule fragment 122 provides information on the time at which the service can be provided and used. The content fragment 123 provides information on a plurality of contents constituting the service.
The access group 130 includes an access fragment 131 and a session description fragment 132, and provides service access information indicating how to receive the services provided through the core group 120, and detailed information on the session in which the contents constituting the corresponding service are transmitted, so as to allow the mobile terminal to access the corresponding service. The access fragment 131 provides a plurality of access methods for one service to the mobile terminal, thereby providing a method capable of accessing various additional services based on one service. The session description fragment 132 provides session information for the service defined in one access fragment.
The service guide information, as shown in FIG. 1, can further include a preview data fragment 124 that provides a preview and icon for the service and content in addition to the foregoing four fragments.
With reference to Table 1 to Table 7 below, a description will now be made of the details of the access fragment defined in the conventional OMA BCAST by way of example. Table 1 to Table 7 are divided from one table, for convenience, and a definition of items in each table follows the definition of Table 1. <tables id="tabl0001" num="0001"><table frame="all"><title>Table 1</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="16mm" /><colspec colnum="3" colname="col3" colwidth="13mm" /><colspec colnum="4" colname="col4" colwidth="19mm" /><colspec colnum="5" colname="col5" colwidth="22mm" /><colspec colnum="6" colname="col6" colwidth="56mm" /><colspec colnum="7" colname="col7" colwidth="20mm" /><thead><row><entry align="center" valign="top" /><entry align="center" valign="top"><b>Name</b></entry><entry align="center" valign="top"><b>Type</b></entry><entry align="center" valign="top"><b>Category</b></entry><entry align="center" valign="top"><b>Cardinality</b></entry><entry align="center" valign="top"><b>Description</b></entry><entry align="center" valign="top"><b>Data Type</b></entry></row></thead><tbody><row rowsep="0"><entry>201</entry><entry>Access</entry><entry>E</entry><entry>O</entry><entry>0..N</entry><entry>Access fragment</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Contains the following attributes:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> id</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> version</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> validFrom</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> validTo</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> ServiceProtection</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> AccessType</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> AudioLanguage</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Contains the following sub-elements:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> ExtensionURL</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> AccessType</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> ServicelD</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> UsageInfo</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> SessionDescriptionURI</entry><entry /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0"> SDP</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0"> InteractiveAccessURL</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0"> TerminalCapabilityRequirement</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0"> BandwidthRequirement</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0"> ApplicationSpec</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry /><entry> MediaInformation</entry><entry /></row></tbody></tgroup></table></tables>
In Table 1, a first item "Name" indicates names of attributes or elements of an access fragment, and a second item "Type" indicates whether each object included in the access fragment corresponds to Attribute (A) or Element (E). As to a difference between the attribute and the element, the attribute is a value indicating an attribute of an access fragment and its element, and the element is a value indicating the information actually used. A third item "Category" indicates whether the attribute or element is a mandatory value (M) or an optional value (O). A fourth item "Cardinality" indicates whether the attribute or element is repeated, and a fifth item "Description" indicates a description of the attribute or element. Finally, a sixth item "Data Type" indicates a data type of the attribute or element.
In Table 1, reference numeral 201 indicates what the attribute or element included in the access fragment comprises. <tables id="tabl0002" num="0002"><table frame="all"><title>Table 2</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="30mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="48mm" /><colspec colnum="7" colname="col7" colwidth="48mm" /><tbody><row><entry>202</entry><entry>id</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>ID of the Access fragment.</entry><entry>Integer</entry></row><row><entry>203</entry><entry>version</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>Version of this fragment. The newer version overrides the older one as soon as it has been received.</entry><entry>Byte (8 bits)</entry></row><row><entry>204</entry><entry>validFrom</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry>The first moment when this fragment is valid. If not given, the validity is assumed to have started at some time in the past.</entry><entry>Integer (32 bits), expressed as NTP time.</entry></row><row><entry>205</entry><entry>validTo</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry>The last moment when this fragment is valid. If not given, the validity is assumed to end in an undefined time in the future.</entry><entry>Integer (32 bits), expressed as NTP time.</entry></row><row><entry>206</entry><entry>ServiceProtection</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry>If true, this indicates that this service is protected; if false, this indicates that this service is free to air.</entry><entry>Boolean</entry></row></tbody></tgroup></table></tables>
In Table 2, reference numeral 202 denotes an identifier of the access fragment, and this is an attribute for enabling a mobile terminal to uniquely identify a corresponding access fragment when it refers to the corresponding access fragment in other fragments. Reference numeral 203 denotes an attribute indicating a version of the access fragment, and enables indication of whether the mobile terminal has received an access fragment of the same version or an access fragment of a new version.
The "validFrom" attribute denoted by reference numeral 204 and "validTo" denoted by reference numeral 205 are attributes indicating a valid period of the information included in the access fragment, and "ServiceProtection" denoted by reference numeral 206 is an attribute indicating whether there is a need for a separate authentication procedure during access, as the service that can be accessed through information of the access fragment is service-protected. <tables id="tabl0003" num="0003"><table frame="all"><title>Table 3</title><tgroup cols="7" rowsep="0"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="23mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="88mm" /><colspec colnum="7" colname="col7" colwidth="15mm" /><thead><row><entry valign="top">207</entry><entry valign="top">AccessType</entry><entry valign="top">A</entry><entry valign="top">M</entry><entry valign="top">1</entry><entry>Defines the type of access Possible values:</entry><entry valign="top">Integer</entry></row></thead><tbody><row><entry /><entry /><entry /><entry /><entry /><entry> 1. Default access object; has to exist for A/V streaming services (such as TV radio etc). It is used as default in case of multiple accesses, associated SDP needed;</entry><entry>(8 bits)</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry> 2. Alternated access object, associated SDP needed;</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry> 3. File carousel, to be used for scheduled file download and file carousel type of services; associated SDP needed;</entry><entry /></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0"> 4. File download to be used for file download over interaction network; associated AccessURI needed;</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry /><entry> 5. Service_SMS; this type of access is used for creation of various SMS-based services (voting, etc); no associated SDP;</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry> 6. Service_web_local; this type of access is used for pointing to locally stored web pages; no associated SDP;</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry> 7. Service_web; this type of access is used for pointing to internet services; no associated SDP;</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry> 8. Service_voice_call; this type of access is used for making a phone call;</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry> 9. Service_MMS; this type of access is used for creating various MMS-based services (voting, etc); no associated SDP; and</entry><entry /></row><row><entry rowsep="1" /><entry rowsep="1" /><entry rowsep="1" /><entry rowsep="1" /><entry rowsep="1" /><entry rowsep="1"> 10. Service_java_app; this type of access is used for launching Java applications.</entry><entry rowsep="1" /></row></tbody></tgroup></table></tables>
In Table 3, "AccessType" denoted by reference numeral 207 is an attribute indicating in which method the mobile terminal capable of receiving broadcast service can receive the broadcast service that provides access information in the access fragment, and 10 Access Types are currently defined. Therefore, it is undesirably necessary to newly define Access Type every time a service of a new type occurs. <tables id="tabl0004" num="0004"><table frame="all"><title>Table 4</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="28mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="11mm" /><colspec colnum="6" colname="col6" colwidth="51mm" /><colspec colnum="7" colname="col7" colwidth="47mm" /><tbody><row><entry>208</entry><entry>AudioLanguage</entry><entry>A</entry><entry>O</entry><entry>0..N</entry><entry>The language of the Audio Stream.</entry><entry>3-byte ISO 639 language code</entry></row><row><entry>209</entry><entry>ExtensionURL</entry><entry>E1</entry><entry>O</entry><entry>0..N</entry><entry>URL containing additional information in an extension fragment.</entry><entry>AnyURI</entry></row><row><entry>210</entry><entry>ServiceID</entry><entry>E1</entry><entry>M</entry><entry>1..N</entry><entry>Reference to the service fragment(s) to which the access fragment belongs.</entry><entry>Integer</entry></row><row><entry rowsep="0">211</entry><entry rowsep="0">UsageInfo</entry><entry rowsep="0">E1</entry><entry rowsep="0">O</entry><entry rowsep="0">0..N</entry><entry rowsep="0">This text helps the user understand what difference it makes to use one or the other access fragment. It is mandatory in case more than one access fragment is available at a given point in time.</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Possibly provided in multiple languages.</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Attributes:</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry /><entry>Lang</entry><entry /></row><row><entry>212</entry><entry>Lang</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry>Language</entry><entry>3-byte ISO 639 language code</entry></row></tbody></tgroup></table></tables>
In Table 4, "AudioLanguage" denoted by reference numeral 208 is used to indicate a language of an audio stream transmitted through the access fragment, and "ExtensionURL" denoted by reference numeral 209 is used to indicate an address of an extended fragment. The "ServiceID" denoted by reference numeral 210 is an element indicating an identifier of the service that can be accessed through information of the access fragment, and "UsageInfo" denoted by reference numeral 211 is an element that provides information capable of indicating the usage and correlation of a plurality of corresponding access fragments for users when there are multiple access fragments capable of providing various access information so as to receive various types of additional services for one service, and provides an attribute "Lang" denoted by reference numeral 212 so that it can be provided in various languages. <tables id="tabl0005" num="0005"><table frame="all"><title>Table 5</title><tgroup cols="7" rowsep="0"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="38mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="11mm" /><colspec colnum="6" colname="col6" colwidth="52mm" /><colspec colnum="7" colname="col7" colwidth="36mm" /><tbody><row><entry>213</entry><entry>AccessURI</entry><entry>E1</entry><entry>O</entry><entry>0..1</entry><entry>The URI to the SG delivery unit(s) which contain the session description that the media application in the terminal uses to access the service.</entry><entry>AnyURI</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>In case of non-broadcast service, AccessURI contains information how that particular service can be accessed.</entry><entry /></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Attribute:</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry /><entry>Type</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry /><entry>Note; Using either AccessURI or SDP is mandatory.</entry><entry /></row><row><entry>214</entry><entry>Type</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>Type of the AccessURI:</entry><entry>Integer</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>1 - SDP; AccessURI is a reference to SDP description;</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry /><entry>2 - MBMS-USD; AccessURI is a reference to MBMS user service description (MEMS-USD) as specified in [26.346] section 5.2. It may contain one or several SDP descriptions.</entry><entry /></row><row rowsep="1"><entry>215</entry><entry>SDP</entry><entry>E1</entry><entry>O</entry><entry>0..1</entry><entry>A session description in SDP (IFTF session description protocol) format.</entry><entry>String (in SDP format)</entry></row><row rowsep="1"><entry>216</entry><entry>Interactive AccessURL</entry><entry>E1</entry><entry>O</entry><entry>0..N</entry><entry>Specify alternative URL of the content for retrieving it via the interaction channel if the content cannot be received via the broadcast channel.</entry><entry>AnyURI</entry></row></tbody></tgroup></table></tables>
In Table 5, "AccessURI" denoted by reference numeral 213 is an element indicating an address of the place where information on the session in which the service indicated by the access fragment is transmitted can be acquired, and has, for example, an attribute "Type" denoted by reference numeral 214. The Type 214 is an attribute indicating the type of session information and supports a Session Description Protocol (SDP) type, which is a protocol of the current IEFT, and a session information type used in Multimedia Broadcast Multicast Service (MBMS), which is portable broadcast technology specified by the asynchronous mobile communication standardization group. The "SDP" 215 is an element providing information on actual session description, and "InteractiveAccessURL" 216 is an element notifying an address so that a mobile terminal can receive the service through an interaction channel. <tables id="tabl0006" num="0006"><table frame="all"><title>Table 6</title><tgroup cols="7" rowsep="0"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="50mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="11mm" /><colspec colnum="6" colname="col6" colwidth="60mm" /><colspec colnum="7" colname="col7" colwidth="15mm" /><tbody><row rowsep="1"><entry>217</entry><entry>TerminalCapabilityRequirement</entry><entry>E1</entry><entry>O</entry><entry>0..1</entry><entry>Specification of required terminal capabilities, such as protocols, codecs, bit rate, and processing memory; UAprof is used for expressing the capabilities.</entry><entry>String</entry></row><row><entry>218</entry><entry>BandwidthRequirement</entry><entry>E1</entry><entry>0</entry><entry>0..1</entry><entry>Specification of required network bandwidth.</entry><entry>Integer</entry></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry /><entry>A broadcast service can include multiple accessible streams (same content) with different bandwidth, so that the terminal can make a choice depending on its current reception condition.</entry><entry /></row><row rowsep="1"><entry>219</entry><entry>ApplicationSpec</entry><entry>E1</entry><entry>O</entry><entry>0..N</entry><entry>Application type that can consume the service using this access spec defined by MIME type.</entry><entry>String</entry></row></tbody></tgroup></table></tables>
In Table 6, "TerminalCapabilityRequirement" denoted by reference numeral 217 is an element indicating the software and hardware requirements of a mobile terminal for receiving the service that can be accessed through information of the access fragment, and based on this, a mobile terminal having a portable broadcast receiving function can determine whether it has the capability of receiving the corresponding service. In addition, "BandwidthRequirement" denoted by reference numeral 218 is an element indicating a data rate in a wireless environment of the service that can be accessed through the access fragment, and enables selection of the data rate required by the mobile terminal among several data rates, and reception of the service at the selected data rate. The "ApplicationSpec" 219 is an element providing separate information capable of receiving the service defined in MIME type. <tables id="tabl0007" num="0007"><table frame="all"><title>Table 7</title><tgroup cols="7" rowsep="0"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="43mm" /><colspec colnum="3" colname="col3" colwidth="24mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="11mm" /><colspec colnum="6" colname="col6" colwidth="42mm" /><colspec colnum="7" colname="col7" colwidth="26mm" /><tbody><row><entry>220</entry><entry>MediaInformation</entry><entry>E1</entry><entry>O</entry><entry>0..N</entry><entry>Optional reference to an icon, pictogramme, animation or audio.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>PreviewData or reference to PreviewData is used here.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>Attributes:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>usage</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry /><entry>id</entry><entry /></row><row rowsep="1"><entry>221</entry><entry>usage</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>Possible values; background, icon(e.g.).</entry><entry>Integer (8 bits)</entry></row><row rowsep="1"><entry>222</entry><entry>id</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>ID of the PreviewData fragment.</entry><entry>Integer (8 bits)</entry></row><row rowsep="1"><entry>223</entry><entry><proprietary elements/attributes></entry><entry>E1 or lower. A</entry><entry>O</entry><entry>0..N</entry><entry>Any number of proprietary or application-specific elements or attributes that are not defined in this specification.</entry><entry /></row></tbody></tgroup></table></tables>
In Table 7, "MediaInformation" denoted by reference numeral 220 is an element providing preview information of the service indicated by the access fragment by the mobile terminal that received the access fragment, and has an attribute "usage" 221 and an attribute "id" 222. The attribute "usage" indicates whether it will use information of the fragment associated with the attribute "id" as preview information or background information. Reference numeral 223 denotes an element or attribute capable of providing other information that is not provided through the access fragment.
The access fragment of the conventional BCAST system, shown in Table 1 to Table 7, has the following problems.
First, because "AccessType" conceptually defines Access Type for an actual service in Table 3, Access Type should be newly defined every time a new service occurs. Second, most broadcast services provided to the mobile terminal are multimedia services requiring a high data rate, and should efficiently use radio resources in order to support high-speed transmission. Therefore, most broadcast technologies for the mobile terminal introduce the multicast concept used in the Internet Protocol, and support a method for enabling the service only in the place where the user is located. However, this method is not currently supported for the Access Type. Third, in the currently proposed broadcasting system, there is no method for simply providing to the mobile terminal a transmission scheme or transmission topology supported in the broadcasting system for access to the broadcast service.
Accordingly, a need exists for a system and method for efficiently transmitting/receiving access information of broadcast services in a broadcasting system.
<u style="single">SUMMARY OF THE INVENTION</u>
Embodiments of the present invention are provided to substantially solve the above and other problems, and provide a method and apparatus for efficiently transmitting/receiving access information of broadcast services in a broadcasting system, and a system thereof.
Further, embodiments of the present invention provide a method and apparatus for transmitting/receiving access information of a broadcast network or an interaction network via which broadcast services are transmitted in a broadcasting system, and a system thereof.
Further, embodiments of the present invention provide a method and apparatus for transmitting/receiving an access fragment including access information of broadcast services in an IP-based broadcasting system, and a system thereof.
Moreover, embodiments of the present invention provide an access fragment format for efficiently providing access information for broadcast services in a broadcasting system.
According to one aspect of embodiments of the present invention, a method is provided for transmitting access information of a broadcast service in a transmitter of a broadcasting system. The method comprises the steps of generating access information for at least one of a broadcast network and an interaction network, via which broadcast service is transmitted, and transmitting the access information to a terminal via a specific communication network.
According to another aspect of embodiments of the present invention, an apparatus is provided for transmitting access information of a broadcast service in a transmitter of a broadcasting system. The apparatus comprises an access information generator for generating access information for at least one of a broadcast network and an interaction network, via which broadcast service is transmitted, and a transmitter for transmitting the access information to a terminal via a specific communication network.
According to another aspect of embodiments of the present invention, a method is provided for receiving access information of a broadcast service in a terminal of a broadcasting system. The method comprises the steps of receiving, via a specific communication network, access information for at least one of a broadcast network and an interaction network, from which broadcast service is transmitted, and receiving the broadcast service from the at least one of the broadcast network and the interaction network according to the received access information.
According to yet another aspect of embodiments of the present invention, an apparatus is provided for receiving access information of a broadcast service in a terminal of a broadcasting system. The apparatus comprises a receiver for receiving, via a specific communication network, access information for at least one of a broadcast network and an interaction network from which broadcast service is transmitted and receiving the broadcast service from the at least one of the broadcast network and the interaction network according to the received access information.
According to still another aspect of embodiments of the present invention, a broadcasting system is provided for providing access information of a broadcast service. The system comprises a transmission apparatus for generating access information for at least one of a broadcast network and an interaction network, from which broadcast service is transmitted, and transmitting the access information to a terminal via a specific communication network, and a reception apparatus for receiving, via a specific communication network, the access information of the broadcast service and receiving the broadcast service from the at least one of the broadcast network and the interaction network according to the received access information.
<u style="single">BRIEF DESCRIPTION OF THE DRAWINGS</u>
The above and other objects, features and advantages of embodiments of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which: <ul id="ul0001" list-style="none" compact="compact"><li>FIG. 1 is a block diagram illustrating a structure of a service guide used for receiving broadcast services in a general broadcasting system;</li><li>FIG. 2 is a block diagram illustrating a structure of a transmission apparatus for generating an access fragment and transmitting the access fragment to a mobile terminal in a broadcasting system according to an exemplary embodiment of the present invention;</li><li>FIG. 3 is a flowchart illustrating a process of generating and transmitting an access fragment in a broadcasting system according to a first exemplary embodiment of the present invention;</li><li>FIG. 4 is a block diagram illustrating a structure of a reception apparatus for receiving an access fragment in a broadcasting system according to an exemplary embodiment of the present invention;</li><li>FIG. 5 is a flowchart illustrating a process of receiving and analyzing an access fragment in a broadcasting system according to the first exemplary embodiment of the present invention;</li><li>FIG. 6 is a flowchart illustrating a process of generating and transmitting an access fragment in a broadcasting system according to a second exemplary embodiment of the present invention; and</li><li>FIG. 7 is a flowchart illustrating a process of receiving and analyzing an access fragment in a broadcasting system according to the second exemplary embodiment of the present invention.</li></ul>
Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures.
<u style="single">DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS</u>
Exemplary embodiments of the present invention will now be described in detail with reference to the annexed drawings. In the following description, a detailed description of known functions and configurations incorporated herein has been omitted for clarity and conciseness.
In the following description, exemplary embodiments of the present invention will be presented to accomplish the above and other objects. Although the exemplary embodiments will be described based on the BCAST system, which is one of many portable broadcast technology standards, embodiments of the present invention are not limited thereto, and the following descriptions are not provided to restrict the possible scope of the present invention. In this specification, it should be construed that the broadcasting system comprises various communication systems supporting IP-based broadcast services, such as the BCAST system and the DVB-H system. In addition, although a receiver of the BCAST system will herein be described as a mobile terminal for convenience, embodiments of the present invention are not limited thereto, and it would be obvious to those skilled in the art that the technical spirit of the present invention can also be applied to wired communication systems supporting IP-based broadcast services.
Although the term "service guide" will be used herein as the information including, for example, relevant description and receiving method for the broadcast service of the BCAST system, and "access fragment" will be used herein as the information including an access method of broadcast services, the terms "service guide" and "access fragment" are subject to change according to type of corresponding broadcasting system.
The present invention provides a number of embodiments, including the exemplary first to third embodiments described below. In the first exemplary embodiment, the BCAST system proposes a new access fragment efficiently configured to indicate an access method for a specific service in service guide information that the mobile terminal receives to receive the service. In the first embodiment, the access fragment is configured such that it includes only the attribute related to the service access. Further, in the first embodiment, the access fragment is configured to indicate whether the service is transmitted over a broadcast channel or an interaction channel of the mobile communication network, without individually configuring "AccessType" providing access information of the service for each service as shown in Table 3.
The second exemplary embodiment proposes an efficient access fragment format in which information of the same access fragment can be used for a plurality of different services. Finally, the third exemplary embodiment proposes another embodiment capable of simply providing access information for service transmission through the broadcast network and service transmission through the interaction network using the access fragment. In addition, it should be noted that the first to third embodiments show various types of exemplary access fragment formats, and commonly include features of the present invention of providing the detailed access information of the broadcast network and the interaction network via which the services are transmitted.
Herein, the first exemplary embodiment will be described with reference to Table 8 to Table 14, the second exemplary embodiment will be described with reference to Table 15 to Table 18, and the third exemplary embodiment will be described with reference to Table 19 to Table 37. Although operations of a transmission apparatus of FIG. 2 and a reception apparatus of FIG. 4 will be described based on the first embodiment for convenience, structures of the apparatuses of FIGs. 2 and 4 can also be applied to the second, third, and other embodiments.
First Exemplary Embodiment
Table 8 to Table 14 show by way of example, a format of an access fragment according to the first exemplary embodiment of the present invention. Table 8 to Table 14 are divided from one table, for convenience, and a definition of items in each table follows the definition of Table 8. In addition, the definition of each item in Table 8 to Table 14 is substantially equal to the definition of Table 1, and a detailed description of the same parts throughout Table 1 to Table 7, and Table 8 to Table 14, will be omitted. <tables id="tabl0008" num="0008"><table frame="all"><title>Table 8</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="19mm" /><colspec colnum="3" colname="col3" colwidth="13mm" /><colspec colnum="4" colname="col4" colwidth="19mm" /><colspec colnum="5" colname="col5" colwidth="22mm" /><colspec colnum="6" colname="col6" colwidth="44mm" colsep="0" /><colspec colnum="7" colname="col7" colwidth="40mm" /><thead><row><entry align="center" valign="top" /><entry align="center" valign="top"><b>Name</b></entry><entry align="center" valign="top"><b>Type</b></entry><entry align="center" valign="top"><b>Category</b></entry><entry align="center" valign="top"><b>Cardinality</b></entry><entry colsep="1" align="center" valign="top"><b>Description</b></entry><entry align="center" valign="top"><b>Data Type</b></entry></row></thead><tbody><row rowsep="0"><entry>301</entry><entry>Access</entry><entry>E</entry><entry>O</entry><entry>0..N</entry><entry colsep="1">Access fragment</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">Contains the following attributes:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> id</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> version</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> validFrom</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> validTo</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">Contains the following sub-elements:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> ServicelD</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> UsageInfo</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> SessionDescriptionURI</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> SDP</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> ApplicationSpec</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> MediaInformation</entry><entry /></row><row><entry>302</entry><entry>Id</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry colsep="1">ID of the Access fragment.</entry><entry>Integer</entry></row><row><entry>303</entry><entry>version</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry colsep="1">Version of this fragment. The newer version overrides the older one as soon as it has been received.</entry><entry>Byte (8 bits)</entry></row><row><entry>304</entry><entry>validFrom</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry colsep="1">The first moment when this fragment is valid. If not given, the validity is assumed to have started at some time in the past.</entry><entry>Integer (32 bits), expressed as NTP time.</entry></row></tbody></tgroup></table></tables>
An access fragment of the first embodiment comprises attributes of "Id" 302, "version" 303 and "validFrom" 304 in Table 8, and "ValidTo" 305 in Table 9. These four attributes represent unique attributes for the access fragment, and their functions are substantially equal to those of the attributes having the same names in Table 2. However, as to the difference between the conventional access fragment described in Table 2 and the access fragment proposed in embodiments of the present invention, the conventional access fragment has, as attributes, even the values not associated with the attributes of the access fragment, whereas the proposed access fragment is configured such that it has only the attributes associated with the access fragment, and has changed the other attributes to the elements matched to the corresponding characteristics.
The access fragment of the first embodiment, as presented in Table 8, comprises "ServiceID" 306 in Table 9, and "UsageInfo" 319, "SessionDescriptionURI" 321, "SDP" 323, "ApplicationSpec" 324 and "MediaInformation" 325 in Table 12 to Table 14, as sub-elements. <tables id="tabl0009" num="0009"><table frame="all"><title>Table 9</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="33mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="11mm" /><colspec colnum="6" colname="col6" colwidth="56mm" colsep="0" /><colspec colnum="7" colname="col7" colwidth="36mm" /><tbody><row><entry>305</entry><entry>validTo</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry colsep="1">The last moment when this fragment is valid. If not given, the validity is assumed to end in an undefined time in the future.</entry><entry>Integer (32 bits), expressed as NTP time.</entry></row><row rowsep="0"><entry>306</entry><entry>ServiceID</entry><entry>E1</entry><entry>M</entry><entry>1..N</entry><entry colsep="1">Reference to the service fragment(s) to which the access fragment belongs.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">Contains the following Attribute:</entry><entry /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry colsep="1" rowsep="0"> Service Protection</entry><entry rowsep="0" /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">Contains the following elements:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> TerminalCapabilityRequirement</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> BandwidthRequirement</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> AccessType</entry><entry /></row><row rowsep="0"><entry>307</entry><entry>ServiceProtection</entry><entry>A</entry><entry>M</entry><entry>0..1</entry><entry colsep="1">"1" indicates that this service is protected,</entry><entry>Boolean</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1">"0" indicates that this service is free to air.</entry><entry /></row><row rowsep="0"><entry>308</entry><entry>TerminalCapability Requirement</entry><entry>E2</entry><entry>O</entry><entry>0..1</entry><entry colsep="1">Specification of required terminal capabilities, such as protocols, codecs, bit rate, processing, and memory.</entry><entry>String</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1">UAprof is used for expressing the capabilities.</entry><entry /></row></tbody></tgroup></table></tables>
In Table 9, "ServiceID" denoted by reference numeral 306 is a service identifier with which a mobile terminal can obtain access information of a service through the access fragment, and has "ServiceProtection" 307 as its attribute. The "ServiceID" has "TerminalCapabilityRequirement" 308 in Table 9, and "BandwidthRequriement" 309 and "AccessType" 310 in Table 10, as its sub-elements. Therefore, in the first embodiment, because the element "ServiceID" has all access information of the service, being coincident with the corresponding service, the proposed access fragment has higher efficiency than the conventional access fragment in terms of the format.
The "TerminalCapabilityRequirement" 308 in Table 9 and "BandwidthRequirement" 309 in Table 10 have substantially the same functions as those of the conventional access fragment. <tables id="tabl0010" num="0010"><table frame="all"><title>Table 10</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="38mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="73mm" colsep="0" /><colspec colnum="7" colname="col7" colwidth="15mm" /><tbody><row rowsep="0"><entry>309</entry><entry>BandwidthRequirement</entry><entry>E2</entry><entry>O</entry><entry>0..1</entry><entry colsep="1">Specification of required network bandwidth;</entry><entry>Integer</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1">A broadcast service can include multiple accessible streams (same content) with different bandwidth, so that the terminal can make a choice depending on its current reception condition.</entry><entry /></row><row rowsep="0"><entry>310</entry><entry>AccessType</entry><entry>E2</entry><entry>M</entry><entry>1</entry><entry colsep="1">Defines the type of access.</entry><entry>String</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">Possible values;</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">Contains the following Attributes:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> TransmissionMedia</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">Contains the following elements:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> TransmissionTopology</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> TransmissionScheme</entry><entry /></row><row rowsep="0"><entry>312</entry><entry>Transmission_Media</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry colsep="1">0: Broadcast channel</entry><entry>ENUM</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1">1: Interaction channel</entry><entry /></row><row rowsep="0"><entry>313</entry><entry>Transmission_Topology</entry><entry>E3</entry><entry>O</entry><entry>0..1</entry><entry colsep="1">0: Broadcast Mode</entry><entry>ENUM</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">1: Multicast Mode</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">Contains the following attributes:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> IP_Address</entry><entry /></row></tbody></tgroup></table></tables>
The "AccessType" 310 in Table 10, provided to indicate in which method the mobile terminal can receive the service, is used to indicate whether the service is transmitted over the broadcast channel or transmitted over the interaction channel provided in the mobile communication network, and also indicate with which protocol or system the mobile terminal transmits the service. For this purpose, in the first embodiment, the "AccessType" is comprised of one attribute and two sub-elements.
That is, "Transmission_Media" 312 in Table 10 is an attribute indicating whether the service is transmitted over the broadcast channel or is provided from a communication network capable of bidirectional communication, and a type of the sub-element that can be included in the "AccessType" is determined according to a value of the attribute. For example, if the "TransmissionMedia" indicates that the service is transmitted over the broadcast channel, "AccessType" comprises "Transmission_Topology" 313 in Table 10 and "IP_Address" 314 in Table 11, as its sub-elements.
The "Transmission_Topology" in Table 10 is an element indicating whether the service transmitted over the broadcast channel will be transmitted in a broadcast mode or a multicast mode. The broadcast mode and the multicast mode are used in Internet Protocol, and if the "Transmission_Topology" indicates the broadcast mode, it means that the service is transmitted to a particular area regardless of the position of the service recipient. If the "Transmission_Topology" indicates the multicast mode, it means that the service is transmitted to the place where the service recipient is located in the serviceable area according to location information of the service recipient. In addition, when the "Transmission_Topology" indicates the multicast mode, the mobile terminal capable of receiving the broadcast service preferably should make a subscription application to an IP address of the multicast mode and receive the broadcast service. <tables id="tabl0011" num="0011"><table frame="all"><title>Table 11</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="45mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="11mm" /><colspec colnum="6" colname="col6" colwidth="64mm" /><colspec colnum="7" colname="col7" colwidth="16mm" /><tbody><row rowsep="0"><entry>314</entry><entry>IP_Address</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry>IP address of IP stream, which transport A Service over Broadcast channel.</entry><entry>String</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>If Transmission Topology is 0, then Type of IP address is IP Broadcast address.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>If Transmission Topology is 1, then Type of IP address is IP Broadcast address.</entry><entry /></row><row rowsep="0"><entry>315</entry><entry>Transmission_Scheme</entry><entry>E3</entry><entry>O</entry><entry>0..1</entry><entry>1: Interaction Channel provided by</entry><entry>ENUM</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Interaction Network</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>2:MMS</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>3: WAP 1.0</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>4: WAP 2 x</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>5: SMS</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>6: HTTP</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>7: Service Provider defined</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>Transmission Scheme</entry><entry /></row><row><entry>316</entry><entry>AccessServerIPAddress</entry><entry>E4</entry><entry>O</entry><entry>0..N</entry><entry>IP address of Sever, which provides different access (over interaction Channel) of a Service.</entry><entry>String</entry></row><row><entry>317</entry><entry>AccessServerURL</entry><entry>E4</entry><entry>O</entry><entry>0..N</entry><entry>ULR of Server, which provides different access (over Interaction Channel) of a Service.</entry><entry>AnyURI</entry></row><row><entry>318</entry><entry>AccessServerPhoneNumber</entry><entry>E4</entry><entry>O</entry><entry>0..N</entry><entry>Phone number of Server, which provides different access (over Interaction Channel) of a Service.</entry><entry /></row></tbody></tgroup></table></tables>
The "IP_Address" 314 in Table 11, because the service is transmitted to mobile terminals in the form of IP flow in the BCAST system, is an attribute indicating an address for the IP flow. The "IP_Address" becomes an IP broadcast address or an IP multicast address according to a value of the "Transmission_Topology" in Table 10. Commonly, an IP address of the service is indicated in the session description. However, when the session description is not transmitted together with the access fragment, it should be provided to the mobile terminal for identification of the service on the IP level.
If the attribute "Transmission_Media" 312 in Table 10 indicates Interaction Channel, "Transmission_Scheme" 315 in Table 11 is included in the "AccessType" of Table 10, and the "Transmission_Scheme" comprises "AccessServerIPAddress" 316, "AccessServerURL" 317, and "AccessServerPhoneNumber" 318 as its sub-elements.
The "Transmission_Scheme" is an element indicating the communication system or protocol used in the interaction channel, when it is possible to access the service through the interaction channel. Although OMA BCAST currently specifies, for example, Web Browsing, Multimedia Messaging Service (MMS), Wireless Application Protocol 1.0 (WAP1.0), Wireless Application Protocol 2.x (WAP 2.x), Short Messaging Service (SMS), and Hyper Text Transmission Protocol (HTTP) as the communication systems or protocols that can be used for the interaction channel, further communication systems and protocols that can be used for the interaction channel can be added in the future.
In Table 11, "AccessServerIPAddress" 316, "AccessServerURL" 317, and "AccessServerPhoneNumber" 318 are elements indicating an address of the server that provides the service over the interaction channel in order to indicate whether the mobile terminal receiving the access fragment can access the service through the interaction channel in any place. Because an addressing system used in each communication system or protocol is different, the representative addressing system of the communication system and protocol, currently adapted to support the interaction channel, is presented.
The "AccessServerIPAddress" 316 is an element indicating a position of the server based on Internet Protocol, the "AccessServerURL" 317 is an element indicating a position of the server that uses the communication system or protocol supporting Web or URL, and the "AccessServerPhoneNumber" 318 is an element indicating a position of the server that enables access to the service using MMS or SMS. Further, in embodiments of the present invention, a new communication system or protocol is added to the "Transmission_Scheme" 315 in Table 11, and if the addressing system of the communication system or protocol is different from the currently provided one, a new addressing system can be added as a sub-element of the "Transmission_Scheme". <tables id="tabl0012" num="0012"><table frame="all"><title>Table 12</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="38mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="11mm" /><colspec colnum="6" colname="col6" colwidth="43mm" /><colspec colnum="7" colname="col7" colwidth="45mm" /><tbody><row rowsep="0"><entry>319</entry><entry>UsageInfo</entry><entry>E1</entry><entry>O</entry><entry>0..N</entry><entry>The text explains the characteristic of this access fragment for a User. This text also contains the information about other Access fragments of a Service if there exists more than 1 Access fragment.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Possibly provided in multiple languages.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Attributes:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>Lang</entry><entry /></row><row><entry>320</entry><entry>Lang</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry>Language</entry><entry>3-byte ISO 639 language code</entry></row><row rowsep="0"><entry>321</entry><entry>SessionDescriptionURI</entry><entry>E1</entry><entry>O</entry><entry>0..1</entry><entry>The URI to the SG delivery unit(s) which contains the session description that the media application in the terminal uses to access the service.</entry><entry>AnyURI</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>In case of non-broadcast service, AccessURI contains information on how that particular service can be accessed.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Contains following Attribute and element:</entry><entry /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Type</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry /><entry>Note; Using either AccessURI or SDP is mandatory.</entry><entry /></row></tbody></tgroup></table></tables>
The "UsageInfo" 319 in Table 12 is an element for giving a description of the characteristic of the access fragment to the user of the mobile terminal, especially an element that can be used for describing the characteristic and correlation of each access fragment for the user even when there are a plurality of access fragments for one service, providing sub-services having different characteristics. The "UsageInfo" has "Lang" 320 as an attribute.
The "SessionDescriptionURI" 321 in Table 12, and "Type" 322, "SDP" 323, "ApplicationSpec" 324, "MediaInformation" 325, "Usage" 326, "Id" 327, and "<proprietary elements/attributes>" 328 in Table 13 and Table 14, have substantially the same functions as those of the conventional access fragment, so a detailed description thereof will be omitted. <tables id="tabl0013" num="0013"><table frame="all"><title>Table 13</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="28mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="12mm" /><colspec colnum="6" colname="col6" colwidth="61mm" /><colspec colnum="7" colname="col7" colwidth="35mm" /><tbody><row rowsep="0"><entry>322</entry><entry>Type</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>Type of the AccessURI:</entry><entry>Integer</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>1 - SDP; AccessURI is a reference to SDP description;</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>2 - MBMS-USD; AccessURI is a reference to MBMS user service description (MBMS-USD) as specified in [26.346] section 5.2. It may contain one or several SDP descriptions.</entry><entry /></row><row><entry>323</entry><entry>SDP</entry><entry>E1</entry><entry>O</entry><entry>0..1</entry><entry>A session description in SDP (IETF session description protocol) format.</entry><entry>String (in SDP format)</entry></row><row><entry>324</entry><entry>ApplicationSpec</entry><entry>E1</entry><entry>O</entry><entry>0.. N</entry><entry>Application type that can consume the service using this access spec defined by MIME type.</entry><entry>String</entry></row></tbody></tgroup></table></tables><tables id="tabl0014" num="0014"><table frame="all"><title>Table 14</title><tgroup cols="7" rowsep="0"><colspec colnum="1" colname="col1" colwidth="11mm" /><colspec colnum="2" colname="col2" colwidth="43mm" /><colspec colnum="3" colname="col3" colwidth="24mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="11mm" /><colspec colnum="6" colname="col6" colwidth="42mm" /><colspec colnum="7" colname="col7" colwidth="26mm" /><tbody><row rowsep="1"><entry rowsep="0">325</entry><entry rowsep="0">MediaInformation</entry><entry rowsep="0">E1</entry><entry rowsep="0">O</entry><entry rowsep="0">0..N</entry><entry rowsep="0">Optional reference to an icon, pictogramme, animation or audio.</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry /><entry>PreviewData or reference to PreviewData is used here.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>Attributes:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>usage</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry /><entry>id</entry><entry /></row><row rowsep="1"><entry>326</entry><entry>Usage</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>Possible values: background, icon(e.g.).</entry><entry>Integer (8 bits)</entry></row><row rowsep="1"><entry>327</entry><entry>Id</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>ID of the PreviewData fragment.</entry><entry>Integer (8 bits)</entry></row><row rowsep="1"><entry>328</entry><entry><proprietary elements/attributes></entry><entry>E1 or lower. A</entry><entry>O</entry><entry>0..N</entry><entry>Any number of proprietary or application-specific elements or attributes that are not defined in this specification.</entry><entry /></row></tbody></tgroup></table></tables>
With reference to FIGs. 2 to 5, a description will now be made of a structure and operation of a transmission apparatus for generating and transmitting an access fragment configured in the format of Table 7 to Table 14, and a reception apparatus for receiving the access fragment to receive a desired service.
FIG. 2 is a block diagram illustrating a structure of a transmission apparatus for generating an access fragment and transmitting the access fragment to a mobile terminal in a broadcasting system according to an exemplary embodiment of the present invention. The transmission apparatus comprises an access fragment generator 201, a service guide generator 203, and a transmitter 205.
Referring to FIG. 2, the access fragment generator 201 generates an access fragment configured in the format of Table 7 to Table 14. The service guide generator 203 generates service guide information having the structure of FIG. 1 using the access fragment output from the access fragment generator 201, and the transmitter 205 transmits the service guide information to the mobile terminal via a transmission network. The transmission network can be a network providing a broadcast channel, or a network providing an interaction channel.
The transmission apparatus of FIG. 2 can be applied to a transmitter of the BCAST system. Alternatively, the transmission apparatus can also be applied to a transmitter of any number of communication systems that provide IP-based broadcast service to a plurality of users, like the DVB-H system.
FIG. 3 is a flowchart illustrating a process of generating and transmitting an access fragment in a broadcasting system according to the first exemplary embodiment of the present invention. This process corresponds to an operation of the access fragment generator 201 of FIG. 2.
Referring to FIG. 3, the access fragment generator 201 determines in step 301 whether there is a need to generate a new access fragment. If there is a need to generate a new access fragment, it means that a new service starts, or that there is a need to provide a new additional service or a new access method for the current service to a mobile terminal receiving the broadcast service. If it is determined in step 301 that there is a need to generate a new access fragment, the access fragment generator 201 sets basic information for the access fragment in step 303. The basic information comprises at least one of "Id", "version", and "validFrom" and "validTo" both related to validity of the access fragment, described in connection with Table 8 and Table 9.
In step 305, the access fragment generator 201 sets a service ID corresponding to the information provided by the access fragment, and sets a basic attribute of the service corresponding to the service ID. The basic attribute comprises at least one of information indicating whether to apply the service protection, information indicating the requirements of the mobile terminal for receiving the service, and information indicating a data rate at which the service is transmitted in a wireless environment, all of which have been described in connection with Table 9 and Table 10. In step 307, the access fragment generator 201 determines whether the service will be transmitted over a broadcast channel or an interaction channel. If the service is to be transmitted over the interaction channel, the access fragment generator 201 proceeds to step 309. However, if the service is to be transmitted over the broadcast channel, the access fragment generator 201 proceeds to step 315.
The access fragment generator 201 sets a transmission scheme for a communication system or protocol to be used, in step 309, and sets an address for the corresponding communication system or protocol in step 311. Thereafter, in step 313, the access fragment generator 201 sets service usage information "UsageInfo", and if there is characteristic description for the corresponding access fragment and a plurality of access fragments for one service, the access fragment generator 201 adds description of characteristic and correlation for each of them to the access fragment so that a broadcast service recipient may detect the difference.
In step 315, the access fragment generator 201 sets transmission topology information indicating whether the corresponding service will be transmitted in a broadcast mode or a multicast mode. The mode-related information is determined by a transmission entity or a service providing entity, and the access fragment generator 201 receives the mode-related information provided from the corresponding entity, and sets the mode depending on the mode-related information. In step 317, the access fragment generator 201 sets IP information of an IP flow where the service is transmitted. Thereafter, in step 313, the access fragment generator 201 sets service usage information "UsageInfo".
In step 319, the access fragment generator 201 sets information on the session in which the service, whose access information is provided through the corresponding access fragment, is transmitted. The session information comprises an IP address of a sender, an IP address of a recipient, a type of data transmitted through the session, and a codec used. Session Description Protocol defined by IETF is a typical example of the session information. Thereafter, in step 321, the access fragment generator 201 sets the other information constituting the access fragment, and then ends the operation.
FIG. 4 is a block diagram illustrating a structure of a reception apparatus for receiving a service guide containing an access fragment to receive a broadcast service in a broadcasting system according to an exemplary embodiment of the present invention. The reception apparatus comprises a receiver 401, a service guide disassembler 403, and an access fragment analyzer 405.
Referring to FIG. 4, the receiver 401 receives service guide information transmitted from the transmission apparatus of the broadcasting system via a transmission network, and outputs the received service guide information to the service guide disassembler 403. The service guide disassembler 403 extracts each fragment from the received service guide, and delivers the extracted fragment to a corresponding fragment analyzer. FIG. 4 shows only the access fragment analyzer 405 related to embodiments of the present invention, from among a plurality of possible fragment analyzers. The access fragment analyzer 405 analyzes a received access fragment having the format of Table 7 to Table 14, included in the service guide information according to an operation of FIG. 5 described below, and a mobile terminal performs an operation of receiving the service based on the analysis result.
FIG. 5 is a flowchart illustrating a process of receiving and analyzing an access fragment in a broadcasting system according to the first exemplary embodiment of the present invention. This process corresponds to an operation of the access fragment analyzer 405 of FIG. 4.
Referring to FIG. 5, the access fragment analyzer 405 determines in step 501 whether there is any new access fragment received. The determination criteria is an attribute "version" of the received access fragment. If it is determined in step 501 that there is any access fragment received, the access fragment analyzer 405 analyzes, in step 503, the basic information of the access fragment, determines a valid period of the access fragment in the basic information, and recognizes that the information provided through the access fragment is valid only in the valid period.
In step 505, the access fragment analyzer 405 determines a service ID that can be accessed through access information provided by the access fragment, and determines whether the corresponding service undergoes service protection before being transmitted. When the service undergoes service protection, the access fragment analyzer 405 prepares to perform a related operation so as to correctly receive the corresponding service. In addition, the access fragment analyzer 405 checks a basic attribute for the corresponding service ID, compares a performance condition of the mobile terminal requiring the corresponding service with a performance condition of the current mobile terminal to determine whether the service is receivable, and selects an appropriate channel taking into account a bandwidth provided by the service.
In step 507, the access fragment analyzer 405 determines whether the service will be transmitted over a broadcast channel or an interaction channel based on the access information provided by the access fragment. If the service is to be transmitted over an interaction channel, the access fragment analyzer 405 proceeds to step 509. However, if the service is to be transmitted over a broadcast channel, the access fragment analyzer 405 proceeds to step 515.
In step 509, the access fragment analyzer 405 checks a transmission scheme and recognizes a communication system or protocol to be used. After recognizing that it preferably should receive the service using the determined communication system or protocol, the access fragment analyzer 405 analyzes, in step 511, an address of the server that transmits the service over the interaction channel, and prepares to transmit a service request. The addressing system may differ according to communication system and protocol using the interaction channel. Thereafter, in step 513, the access fragment analyzer 405 checks service usage information "UsageInfo", and if there is characteristic description for the access fragment and a plurality of access fragments for one service, the access fragment analyzer 405 recognizes characteristic and correlation for each of them, and the mobile terminal displays the corresponding description for the user who will receive the service so as to allow the user to make an appropriate selection.
In step 515, the access fragment analyzer 405 checks the transmission topology, analyzes the information indicating whether the service will be transmitted in the broadcast mode or the multicast mode, and prepares to perform an operation appropriate for the analysis result. For the service transmitted in the broadcast mode, the mobile terminal can receive the corresponding service without joining in the service. However, for the service transmitted in the multicast mode, the mobile terminal preferably should perform a Join process for a multicast IP address group of an IP flow where the service is transmitted, in order to receive the service.
In step 517, the access fragment analyzer 405 checks an address of the IP flow where the service is transmitted. The address of the IP flow is very important for the mobile terminal scheduled to receive the service in the process of distinguishing an IP flow where the service is transmitted. If the address of the IP flow is not provided, the mobile terminal preferably should perform an operation of receiving all IP flows transmitted through the broadcast channel and determining whether the corresponding service is a desired service, for every IP flow. The address of the IP flow is connected to a communication bearer under an IP layer and indicates which communication bearer the mobile terminal should receive in order to receive the IP flow. The method may be different in each broadcast system providing the broadcast channel and departs from the scope of the present invention, so a detailed description thereof will be omitted.
After step 513, the access fragment analyzer 405 checks, in step 519, information on the session where the service, whose access information is provided from the access fragment, is transmitted, and allows the mobile terminal to prepare to receive the session where the service is actually transmitted. Thereafter, in step 521, the access fragment analyzer 405 analyzes the other information provided from the access fragment and uses the related information for an appropriate purpose. In step 523, the access fragment analyzer 405 prepares to access and receive the service according to the information analyzed from the access fragment, and then ends the operation.
Second Exemplary Embodiment
With reference to Table 15 to Table 18 and FIGs. 6 and 7, a description will now be made of a method for transmitting/receiving an access fragment according to a second exemplary embodiment of the present invention.
Table 15 to Table 18 show by way of example, a format of an access fragment according to the second embodiment of the present invention. A difference in the access fragment between the first embodiment and the second embodiment is in that information of the same access fragment is used for a plurality of different services, and an efficient structure thereof will be proposed in the second embodiment. A definition of items in each table is substantially equal to the definition of Table 1, and a detailed description of the same parts throughout Table 15 to Table 18 and Table 8 to Table 14 will be omitted.
In addition, compared with the attributes or elements defined in Table 8 to Table 14, the unchanged parts of Table 15 to Table 18 will not be shown for simplicity. <tables id="tabl0015" num="0015"><table frame="all"><title>Table 15</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="30mm" /><colspec colnum="3" colname="col3" colwidth="13mm" /><colspec colnum="4" colname="col4" colwidth="19mm" /><colspec colnum="5" colname="col5" colwidth="22mm" /><colspec colnum="6" colname="col6" colwidth="49mm" /><colspec colnum="7" colname="col7" colwidth="24mm" /><thead><row><entry valign="top" /><entry valign="middle"><b>Name</b></entry><entry valign="middle"><b>Type</b></entry><entry valign="middle"><b>Category</b></entry><entry valign="middle"><b>Cardinality</b></entry><entry valign="middle"><b>Description</b></entry><entry valign="middle"><b>Data Type</b></entry></row></thead><tbody><row rowsep="0"><entry>*01</entry><entry>Access</entry><entry>E</entry><entry>O</entry><entry>0..N</entry><entry>Access fragment</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Contains the following attributes:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> id</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> version</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> validFrom</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> validTo</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> ServiceProtection</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Contains the following sub-elements:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> TerminalCapabilityRequire ment</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> BandwidthRequirement</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> AccessType</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry> ServiceID</entry><entry /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0"> ExtensionURL</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0"> UsageInfo</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0"> SessionDescriptionURI</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0"> SDP</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0"> ApplicationSpec</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry /><entry> MediaInformation</entry><entry /></row><row><entry>*02</entry><entry>Id</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>ID of the Access fragment.</entry><entry>Integer</entry></row><row><entry>*03</entry><entry>version</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>Version of this fragment. The newer version overrides the older one as soon as it has been received.</entry><entry>Byte (8 bits)</entry></row><row><entry>*04</entry><entry>validFrom</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry>The first moment when this fragment is valid. If not given, the validity is assumed to have started at some time in the past.</entry><entry>Integer (32 bits), expressed as NTP time.</entry></row><row><entry>*05</entry><entry>validTo</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry>The last moment when this fragment is valid. If not given, the validity is assumed to end in an undefined time in the future.</entry><entry>Integer (32 bits), expressed as NTP time.</entry></row><row><entry>*06</entry><entry>ServiceProtection</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>If true, this indicates that this access related to the associated service is protected by OMA BCAST Service protection; if false, this indicates this access related to the associated service is not protected by OMA BCAST Service protection.</entry><entry>Boolean</entry></row></tbody></tgroup></table></tables>
In Table 15, the access fragment proposed by the second embodiment comprises attributes of "Id" *02, "version" *03, "validFrom" *04, "validTo" *05, and "ServiceProtection" *06, as specified in "Access" denoted by reference numeral *01. The five attributes represent unique attributes for the access fragment, and their functions are substantially equal to those of the attributes having the same names in Table 2. Further, the access fragment proposed in the second embodiment comprises "TerminialCapabilityRequirement" *07, "BandwidthRequirement" *08, "AccessType" *09, "ServiceID" *17, "ExtensionURL" *18, "UsageInfo" *19, "SessionDescriptionURI" *21, "SDP" *23, "ApplicationSpec" *24, and "MediaInformation" *25 as its sub-elements, as specified in the "Access" *01. <tables id="tabl0016" num="0016"><table frame="all"><title>Table 16</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="51mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="10mm" /><colspec colnum="6" colname="col6" colwidth="60mm" colsep="0" /><colspec colnum="7" colname="col7" colwidth="15mm" /><tbody><row rowsep="0"><entry>*07</entry><entry>TerminalCap abilityRequir ement</entry><entry>E1</entry><entry>O</entry><entry>0..1</entry><entry colsep="1">Specification of required terminal capabilities for this access, such as protocols, codecs, bit rate, processing and memory;</entry><entry>String</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1">UAprof is used for expressing the capabilities.</entry><entry /></row><row rowsep="0"><entry>*08</entry><entry>BandwidthRe quirement</entry><entry>E1</entry><entry>O</entry><entry>0..1</entry><entry colsep="1">Specification of required network bandwidth to access described in this fragment.</entry><entry>Integer</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1">A broadcast service can include multiple accessible streams (same content) with different bandwidth, so that the terminal can make a choice depending on its current reception condition.</entry><entry /></row><row rowsep="0"><entry morerows="5" rowsep="1">*09</entry><entry morerows="5" rowsep="1">AccessType</entry><entry morerows="5" rowsep="1">E1</entry><entry morerows="5" rowsep="1">M</entry><entry morerows="5" rowsep="1">1</entry><entry colsep="1">Defines the type of access;</entry><entry /></row><row rowsep="0"><entry colsep="1">Contains the following Attributes:</entry><entry /></row><row rowsep="0"><entry colsep="1"> TransmissionMedia</entry><entry /></row><row rowsep="0"><entry colsep="1">Contains the following elements:</entry><entry /></row><row rowsep="0"><entry colsep="1"> TransmissionTopology</entry><entry /></row><row><entry colsep="1"> TransmissionScheme</entry><entry /></row><row rowsep="0"><entry>*10</entry><entry>Transmission_Media</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry colsep="1">This attribute indicates which channel is used for the delivery of services, whose IDs are listed in this Access Fragment.</entry><entry>Integer</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">0: Broadcast Channel</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1">1: Interaction Channel</entry><entry /></row><row rowsep="0"><entry>*11</entry><entry>Transmission_Topology</entry><entry>E2</entry><entry>O</entry><entry>0..1</entry><entry colsep="1">This element is used for the indication of IP transmission mode over Broadcast Channel.</entry><entry>Integer</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">There are two possible modes.</entry><entry /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry colsep="1" rowsep="0">0: Broadcast Mode</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry colsep="1" rowsep="0">1: Multicast Mode</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry colsep="1" rowsep="0">Contains the following Attributes:</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1"> IF_Address</entry><entry /></row><row rowsep="0"><entry>*12</entry><entry>IP_Address</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry colsep="1">IF address of IF stream, which transport A Service over Broadcast channel.</entry><entry>String</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">If Transmission Topology is 0, then Type of IP address is IP Broadcast address.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">If Transmission Topology is 1, then Type of IP address is IP Multicast address.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry colsep="1">Note: This attribute is used when SDP is not included in Access Fragment.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry colsep="1">If SDP in Access Fragment exists, IP address of the receiver IP address in SDP is used.</entry><entry /></row><row><entry>*13</entry><entry>Interaction_Scheme</entry><entry>E2</entry><entry>O</entry><entry>0..1</entry><entry colsep="1">This element indicates which communication system or protocol is used for Interaction.</entry><entry>Integer</entry></row></tbody></tgroup></table></tables>
The "TerminalCapabilityRequirement" *07 in Table 16 indicates the requirement for the mobile terminal that accesses the service through the access fragment, and "BandwidthRequirement" *08 indicates the bandwidth in the wireless channel of the service accessed through the access fragment. The "AccessType" *09, provided to indicate in which method the mobile terminal will receive the service, is used to indicate whether the service is transmitted over the broadcast channel or transmitted over the interaction channel provided in the mobile communication network, and also indicate with which protocol or system the mobile terminal transmits the service. For this purpose, in the second embodiment, the "AccessType" is comprised of one attribute and two sub-elements.
That is, "Transmission_Media" *10 in Table 16 is an attribute indicating whether the service is transmitted over the broadcast channel or is provided from a communication network capable of bidirectional communication, and a type of the sub-element that can be included in the "AccessType" is determined according to a value of the attribute. If the "Transmission_Media" indicates that the service is transmitted over the broadcast channel, "AccessType" comprises "Transmission_Topology" *11 and "IP_Address" *12, as its sub-elements.
The "Transmission_Topology" in Table 16 is an element indicating whether the service transmitted over the broadcast channel will be transmitted in a broadcast mode or a multicast mode. The broadcast mode and the multicast mode are used in Internet Protocol, and if the "Transmission_Topology" indicates the broadcast mode, it means that the service is transmitted to a particular area regardless of the position of the service recipient.
If the "Transmission_Topology" indicates the multicast mode, it means that the service is transmitted to the place where the service recipient is located in the serviceable area according to location information of the service recipient. In addition, when the "Transmission_Topology" indicates the multicast mode, the mobile terminal capable of receiving the broadcast service preferably should make a subscription application to an IP address of the multicast mode and receive the broadcast service.
The "IP_Address" *12 in Table 16, because the service is transmitted to mobile terminals in the form of IP flow in the broadcasting system, is an attribute indicating an address for the IP flow. The "IP_Address" becomes an IP broadcast address or an IP multicast address according to a value of the "Transmission_Topology". Commonly, an IP address of the service is indicated in the session description. However, when the session description is not transmitted together with the access fragment, it preferably should be provided to the mobile terminal for identification of the service on the IP level.
If the attribute "Transmission _Media" *10 in Table 16 indicates Interaction Channel, "Interaction_Scheme" *13 is included in the "AccessType" *09, and the "Interaction_Scheme" has a substantially equivalent meaning to the "Transmission_Scheme" described in the first embodiment. In the second embodiment, the "Transmission_Scheme" has "AccessServerIPAddress" *14, "AccessServerURL" *15, and "AccessServerPhoneNumber" *16 as its sub-elements.
The "Transmission_Scheme" is an element indicating the communication system or protocol used in the interaction channel, when it is possible to access the service through the interaction channel. Although OMA BCAST currently specifies, for example, Web Browsing, Multimedia Messaging Service (MMS), Wireless Application Protocol 1.0 (WAP1.0), Wireless Application Protocol 2.x (WAP 2.x), Short Messaging Service (SMS), and Hyper Text Transmission Protocol (HTTP) as the communication systems or protocols that can be used for the interaction channel, further communication systems and protocols that can be used for the interaction channel can be added in the future. <tables id="tabl0017" num="0017"><table frame="all"><title>Table 17</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="45mm" /><colspec colnum="3" colname="col3" colwidth="10mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="11mm" /><colspec colnum="6" colname="col6" colwidth="39mm" /><colspec colnum="7" colname="col7" colwidth="41mm" /><tbody><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Channel.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>1: Interaction Channel provided by Interaction network</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>2: MMS</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>3: WAP 1.0</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>4:WAP2x</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>5: SMS</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>6: HTTP</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>7: Service Provider defined</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>Transmission Scheme</entry><entry /></row><row><entry>*14</entry><entry>AccessServerIPAddress</entry><entry>E3</entry><entry>O</entry><entry>0..N</entry><entry>IP address of Server, which provides different access (over interaction Channel) of a Service.</entry><entry>String</entry></row><row><entry>*15</entry><entry>AccessServerURL</entry><entry>E3</entry><entry>O</entry><entry>0..N</entry><entry>ULR of Server, which provides different access (over interaction Channel) of a Service.</entry><entry>AnyURI</entry></row><row><entry>*16</entry><entry>AccessServerPhoneNumber</entry><entry>E3</entry><entry>O</entry><entry>0..N</entry><entry>Phone number of Server, which provides different access (over Interaction Channel) of a Service.</entry><entry>Integer</entry></row><row><entry>*17</entry><entry>ServiceID</entry><entry>E1</entry><entry>M</entry><entry>0..N</entry><entry>Reference to the service fragment(s) to which the access fragment belongs.</entry><entry>Integer</entry></row><row><entry>*18</entry><entry>ExtensionURL</entry><entry>E1</entry><entry>O</entry><entry>0..N</entry><entry>URL containing additional information in an extension fragment.</entry><entry>AnyURI</entry></row><row rowsep="0"><entry>*19</entry><entry>UsageInfo</entry><entry>E1</entry><entry>O</entry><entry>0..N</entry><entry>This text helps the user understand what difference it makes to use one or the other access fragment. It is mandatory in case more than one access fragment is available at a given point in time.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Possibly provided in multiple languages.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>aAttributes:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>Lang</entry><entry /></row><row><entry>*20</entry><entry>Lang</entry><entry>A</entry><entry>O</entry><entry>0..1</entry><entry>Language</entry><entry>3-byte ISO 639 language code</entry></row><row rowsep="0"><entry>*21</entry><entry>SessionDescriptionURI</entry><entry>E1</entry><entry>O</entry><entry>0..1</entry><entry>The URI to the SG delivery unit(s) which contain the session description that the media application in the terminal uses to access the service. In case of non-broadcast service, SessionDescriptionURI contains information how that particular service can be accessed.</entry><entry>AnyURI</entry></row><row><entry /><entry /><entry /><entry /><entry /><entry>Contains the following Attribute:</entry><entry /></row></tbody></tgroup></table></tables>
In Table 17, "AccessServerIPAddress" *14, "AccessServerURL" *15, and "AccessServerPhoneNumber" *16 are elements indicating an address of the server that provides the service over the interaction channel in order to indicate whether the mobile terminal receiving the access fragment can access the service through the interaction channel in any place. Because an addressing system used in each communication system or protocol is different, the representative addressing system of the communication system and protocol, currently adapted to support the interaction channel, is presented.
The "AccessServerIPAddress" * 14 is an element indicating a position of the server based on Internet Protocol, the "AccessServerURL" * 15 is an element indicating a position of the server that uses the communication system or protocol supporting Web or URL, and the "AccessServerPhoneNumber" *16 is an element indicating a position of the server that enables access to the service using MMS or SMS. Further, a new communication system or protocol is added to the "Interaction_Scheme" *13 in Table 16, and if the addressing system of the communication system or protocol is different from the one currently provided, a new addressing system can be added as a sub-element of the "Interaction_Scheme".
In Table 17, "ServiceID" *17 indicates an identifier of the service that can be accessed using access information provided from the access fragment, and when a plurality of services use the same access, a plurality of the "ServiceIDs" may exist. The "UsageInfo" *19 is an element for giving a description of the characteristic of the access fragment to the user of the mobile terminal, especially an element that can be used for describing the characteristic and correlation of each access fragment for the user, even when there are a plurality of access fragments for one service, providing sub-services having different characteristics. The "UsageInfo" has "Lang" *20 as an attribute. <tables id="tabl0018" num="0018"><table frame="all"><title>Table 18</title><tgroup cols="7"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="39mm" /><colspec colnum="3" colname="col3" colwidth="24mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="11mm" /><colspec colnum="6" colname="col6" colwidth="38mm" /><colspec colnum="7" colname="col7" colwidth="35mm" /><tbody><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Type</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Note: Using either</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>SessionDescriptionURI or SDP is mandatory.</entry><entry /></row><row rowsep="0"><entry>*22</entry><entry>Type</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>Type of the AccessURI</entry><entry>Integer</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>1 - SDP; AccessURI is a reference to SDP description;</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>2 - MBMS-USD; AccessURI is a reference to MBMS user service description (MBMS-USD) as specified in [26.346] section 5.2. It may contain one or several SDP descriptions.</entry><entry /></row><row><entry>*23</entry><entry>SDP</entry><entry>E1</entry><entry>O</entry><entry>0..1</entry><entry>A session description in SDP (IETF session description protocol) format.</entry><entry>String (in SDP format)</entry></row><row><entry>*24</entry><entry>ApplicationSpec</entry><entry>E1</entry><entry>O</entry><entry>0..N</entry><entry>Application type that can consume the service using this access spec defined by MIME type.</entry><entry>String</entry></row><row rowsep="0"><entry>*25</entry><entry>MediaInformation</entry><entry>E1</entry><entry>O</entry><entry>0..N</entry><entry>Optional reference to an icon, pictogramme, animation or audio. PreviewData or reference to PreviewData is used here.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>Attributes:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry /><entry>usage</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry /><entry>id</entry><entry /></row><row><entry>*26</entry><entry>Usage</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>Possible values: background, icon(e.g.).</entry><entry>Integer (8 bits)</entry></row><row><entry>*27</entry><entry>Id</entry><entry>A</entry><entry>M</entry><entry>1</entry><entry>ID of the PreviewData fragment.</entry><entry>Integer (8 bits)</entry></row><row><entry>*28</entry><entry><proprietary elements/attributes></entry><entry>E1 or lower. A</entry><entry>O</entry><entry>0..N</entry><entry>Any number of proprietary or application-specific elements or attributes that are not defined in this specification.</entry><entry /></row></tbody></tgroup></table></tables>
In Table 17 and Table 18, the "SessionDescriptionURI" *21, "Type" *22, "SDP" *23, "ApplicationSpec" *24, "MediaInformation" *25, "Usage" *26, "Id" *27, and "<proprietary elements/attributes>" *28 have substantially the same functions as those of the conventional access fragment, so a detailed description thereof will be omitted.
FIG. 6 is a flowchart illustrating a process of generating and transmitting an access fragment in an OMA broadcasting system according to the second embodiment of the present invention. This process corresponds to an operation of the access fragment generator 201 in the transmission apparatus of FIG. 2.
Referring to FIG 6, the access fragment generator 201 determines in step 601 whether there is a need to generate a new access fragment. If there is a need to generate a new access fragment, it means that a new service starts, or that there is a need to provide a new additional service or a new access method for the current service to a mobile terminal receiving the broadcast service. If it is determined in step 601 that there is a need to generate a new access fragment, the access fragment generator 201 sets basic information for the access fragment in step 603. The basic information comprises at least one of "Id", "version", "validFrom" and "validTo" both related to validity of the access fragment, "ServiceProtection" indicating whether Service Protection is applied or not, "TerminalCapabilityRequirement" indicating the requirement of the mobile terminal intending to have access to the service, and "BandwidthRequirement" indicating a data rate of the service in the wireless channel, all of which are described in connection with Table 15 and Table 16.
In step 605, the access fragment generator 201 determines whether the service that can be accessed through the corresponding access fragment will be transmitted over a broadcast channel or an interaction channel. If the service is to be transmitted over the interaction channel, the access fragment generator 201 proceeds to step 607. However, if the service is to be transmitted over the broadcast channel, the access fragment generator 201 proceeds to step 613.
The access fragment generator 201 sets a transmission scheme for a communication system or protocol to be used, in step 607, and sets an address for the corresponding communication system or protocol in step 609. Thereafter, in step 611, the access fragment generator 201 sets at least one service ID that can be accessed with the information provided in the access fragment.
In step 613, the access fragment generator 201 sets transmission topology information indicating whether the corresponding access or the service using the access will be transmitted in a broadcast mode or a multicast mode. The mode-related information is determined by a transmission entity or a service providing entity, and the access fragment generator 201 receives the mode-related information provided from the corresponding entity, and sets the transmission topology information depending on the mode-related information. In step 615, the access fragment generator 201 sets IP information of an IP flow where the service is transmitted, and then proceeds to step 611.
Thereafter, in step 617, the access fragment generator 201 sets service usage information "UsageInfo", and if there is characteristic description for the corresponding access fragment and a plurality of access fragments for one service, the access fragment generator 201 adds description of characteristic and correlation for each of them to the access fragment so that a broadcast service recipient may detect the difference.
In step 619, the access fragment generator 201 sets information on the session in which the service, whose access information is provided through the corresponding access fragment, is transmitted. The session information comprises an IP address of a sender, an IP address of a recipient, a type of data transmitted through the session, and a codec used. Session Description Protocol defined by IETF is a typical example of the session information. Thereafter, in step 621, the access fragment generator 201 sets the other information constituting the access fragment, and then ends the operation.
FIG. 7 is a flowchart illustrating a process of receiving and analyzing an access fragment in a broadcasting system according to the second embodiment of the present invention. This process corresponds to an operation of the access fragment analyzer 405 in the reception apparatus of FIG. 4.
Referring to FIG. 7, the access fragment analyzer 405 determines in step 701 whether there is any new access fragment received. The determination criteria is an attribute "version" of the received access fragment. If it is determined in step 701 that there is any access fragment received, the access fragment analyzer 405 analyzes, in step 703, the basic information of the access fragment, determines a valid period of the access fragment in the basic information, and recognizes that the information provided through the access fragment is valid only in the valid period. With the use of the basic information, the access fragment analyzer 405 determines whether the service provided by the access fragment underwent service protection before being transmitted. If the service underwent service protection, the access fragment analyzer 405 prepares to perform a related operation so that it can correctly receive the service provided through the corresponding access information. In addition, the access fragment analyzer 405 checks a basic attribute for the corresponding access information, and compares a performance condition of the mobile terminal required by the service based on the access information with a performance condition of the current mobile terminal to determine whether the service is receivable. Further, if there are several access fragments for the same service taking into account the bandwidth in the wireless channel where the service based on the access information is provided, the access fragment analyzer 405 can select an appropriate access fragment determined taking the performance of the mobile terminal into consideration, and receive the service according to the information provided from the access fragment.
In step 705, the access fragment analyzer 405 determines whether the access information for receiving at least one service is for the broadcast channel or the interaction channel. If the access information is for the interaction channel, the access fragment analyzer 405 proceeds to step 707. However, if access information is for the broadcast channel, the access fragment analyzer 405 proceeds to step 713.
In step 707, the access fragment analyzer 405 checks a transmission scheme and recognizes a communication system or protocol to be used. After recognizing that it should access the corresponding service using the determined communication system or protocol, the access fragment analyzer 405 analyzes, in step 709, an address of the server that provides the corresponding service over the interaction channel, and prepares to transmit a service request. The addressing system may differ according to communication system and protocol using the interaction channel.
Thereafter, in step 711, the access fragment analyzer 405 checks service usage information "UsageInfo" for at least one service that can be accessed with the access information, and if there is characteristic description for the access fragment and a plurality of access fragments for one service, or if there is one access fragment for a plurality of services, the access fragment analyzer 405 recognizes characteristic and correlation for each of them, and the mobile terminal displays the corresponding description for the user who will receive the service so as to allow the user to make an appropriate selection.
In step 713, the access fragment analyzer 405 checks the transmission topology, analyzes the information indicating whether the service will be transmitted in the broadcast mode or the multicast mode, and prepares to perform an operation appropriate for the analysis result. For the service transmitted in the broadcast mode, the mobile terminal can receive the corresponding service without joining in the service. However, for the service transmitted in the multicast mode, the mobile terminal preferably should perform a Join process for a multicast IP address group of an IP flow where the service is transmitted, in order to receive the service.
In step 715, the access fragment analyzer 405 checks an address of the IP flow from the access information with which access to the corresponding service is possible. The address of the IP flow is very important for the mobile terminal scheduled to receive a corresponding service in the process of distinguishing an IP address with which access to the service is possible. If the address of the IP flow is not provided, the mobile terminal preferably should perform an operation of receiving all IP flows transmitted through the broadcast channel and determining an IP address for the desired service. The address of the IP flow is connected to a communication bearer under an IP layer and indicates which communication bearer the mobile terminal should receive in order to receive the IP flow. The method may be different in each broadcast system providing the broadcast channel and departs from the scope of the present invention, so a detailed description thereof will be omitted.
After determining an address of the IP flow in step 715, the access fragment analyzer 405 proceeds to step 711 where it checks and displays a service ID and service usage information. In step 717, the access fragment analyzer 405 checks information on the session where the service(s), whose access information is provided from the access fragment, is transmitted, and allows the mobile terminal to prepare to receive the session where the service is actually transmitted. Thereafter, in step 719, the access fragment analyzer 405 analyzes the other information provided from the access fragment and uses the related information for an appropriate purpose. In step 721, the access fragment analyzer 405 prepares to access and receive the service according to the information analyzed from the access fragment, and then ends the operation.
Third Exemplary Embodiment
With reference to Table 19 to Table 37, a description will now be made of a method for providing access information for service transmission via a broadcast network and service transmission via an interaction network according to a third exemplary embodiment of the present invention.
As described in the first and second exemplary embodiments, the access fragment provides access information that the mobile terminal uses to have access to the service.
In Table 19 and Table 20 below, "Id", "version", "validFrom" and "validTo" indicate basic information of ID, version and valid period for the access fragment, respectively. In Table 20, "AccessType" comprises detailed access information of the broadcast network or interaction network for the service. In Table 26, "KeyManagementSystem" comprises information indicating during service access whether the corresponding service is encrypted or whether the corresponding content is encrypted, and also comprises information on the method used for the encryption. In Table 29, "AlternativeAccessURL" comprises information on an address, access to which is possible via the interaction network, in case the mobile terminal has difficulty in accessing the corresponding broadcast network when the "AccessType" of Table 20 comprises broadcast network information. The "TerminalCapabilityRequirement" in Table 30 and "BandwidthRequirement" in Table 35, indicate the requirement of the mobile terminal for having access to the corresponding service, and bandwidth information of the service, respectively.
In Table 35, "ServiceClass" indicates the purposes of using the corresponding access fragment, i.e. service guide reception, file transmission, stream transmission, and so forth. In Table 37, "NotificationReception" comprises address information for reception of notification messages.
The "AccessType" in Table 20 according to embodiments of the present invention will now be described in greater detail. The "AccessType" comprises detailed information for the service access. That is, the corresponding "AccessType" indicates whether it is access information for the broadcast network or access information for the interaction network according to "transmissionMedia" information in Table 20. If the "transmissionMedia" is access information for the broadcast network, the "AccessType" comprises only the "BroadcastServiceDelivery" information of Table 20, and if the "transmissionMedia" is access information for the interaction network, the "AccessType" comprises only the "UnicastServiceDelivery" information of Table 24.
In Table 20, the "transmissionMedia" used for distinguishing between the broadcast network and the interaction network can be optionally included in the "AccessType". Even when the "transmissionMedia" is not included, only one of the "BroadcastServiceDelivery" information of Table 20 for access to the broadcast network, and the "UnicastServiceDelivery" information of Table 24 for access to the interaction network, is included in the "AccessType", so the mobile terminal can determine whether it will have access to the broadcast network or the interaction network by determining which information is included in the "AccessType".
The "BroadcastServiceDelivery" information comprises detailed access information related to the broadcast network, and based on "bdsType" of Table 21, the mobile terminal can determine through which broadcast network the service is received. For example, if the "bdsType" has a value of 0, the mobile terminal is serviced through DVB-H IPDC, and the values specified in the "BroadcastServiceDelivery" comprise the detailed information that the mobile terminal uses to access the DVB-H IPDC and receive the service.
The "destinationIPAddress" in Table 21 denotes an IP address used for receiving the service via the broadcast network, and the mobile terminal accesses the corresponding address and receives the service. The corresponding address information is used when "SessionDescriptionReference" or SDP information of Table 22 is not included. When the "SessionDescriptionReference" or SDP is included, the mobile terminal checks the address value and detailed access information in the corresponding SDP information, and accesses the broadcast network.
The "UnicastServiceDelivery" in Table 24 denotes access information for the case where the mobile terminal receives the service via the interaction network. The detailed address information used by the mobile terminal to receive the service is specified in "AccessServerURL" of Table 24. In addition, "transmissionSchemeType" in Table 25 indicates a transport mechanism used for accessing the corresponding "AccessServerURL" and downloading the service, and the transport mechanism indicates information on HTTP, MMS, WAP, and so forth. For example, if the "transmissionSchemeType" is 0, the mobile terminal accesses the corresponding address "AccessServerURL" using the HTTP, and receives the service. <tables id="tabl0019" num="0019"><table frame="all"><title>Table 19</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="19mm" /><colspec colnum="2" colname="col2" colwidth="13mm" /><colspec colnum="3" colname="col3" colwidth="19mm" /><colspec colnum="4" colname="col4" colwidth="22mm" /><colspec colnum="5" colname="col5" colwidth="50mm" /><colspec colnum="6" colname="col6" colwidth="45mm" /><thead><row><entry><b>Name</b></entry><entry valign="top"><b>Type</b></entry><entry valign="top"><b>Category</b></entry><entry valign="top"><b>Cardinality</b></entry><entry><b>Description</b></entry><entry><b>Data Type</b></entry></row></thead><tbody><row rowsep="0"><entry>Access</entry><entry>E</entry><entry /><entry /><entry>Access fragment</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Contains the following attributes:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>id</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>version</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>validFrom</entry><entry /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">validTo</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Contains the following sub-elements:</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">AccessType</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">ServiceAccessNotificationURL</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">KeyManagementSystem</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">TerminalBindingKeyID</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">ExtensionURL</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">ServiceIDRef</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">ScheduleReference</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">UsageInfo</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">AlternativeAccessURL</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">TerminalCapabilityRequirement</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">BandwidthRequirement</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">ServiceClass</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">PreviewDataIDRef</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry>NotificationReception</entry><entry /></row><row><entry>Id</entry><entry>A</entry><entry>NM/TM</entry><entry>1</entry><entry>ID of the Access fragment, globally unique.</entry><entry>anyURI</entry></row><row><entry>version</entry><entry>A</entry><entry>NM/TM</entry><entry>1</entry><entry>Version of this fragment. The newer version overrides the older one as soon as it has been received.</entry><entry>unsignedInt (32 bits)</entry></row><row><entry>validFrom</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The first moment when this fragment is valid. If not given, the validity is assumed to have started at some time in the past.</entry><entry>int (32 bits). expressed as NTP time.</entry></row></tbody></tgroup></table></tables><tables id="tabl0020" num="0020"><table frame="all"><title>Table 20</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="42mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="54mm" /><colspec colnum="6" colname="col6" colwidth="36mm" /><tbody><row><entry>validTo</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The last moment when this fragment is valid. If not given, the validity is assumed to end in an undefined time in the future.</entry><entry>int (32 bits), expressed as NTP time.</entry></row><row rowsep="0"><entry>AccessType</entry><entry>E1</entry><entry>NM/TM</entry><entry>1</entry><entry>Defines the type of access.</entry><entry /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Contains the following Attribute:</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">transmissionMedia</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Contains the following elements:</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">BroadcastServiceDelivery</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry>UnicastserviceDelivery</entry><entry /></row><row rowsep="0"><entry>transmissionMedia</entry><entry>A</entry><entry>NM/TM</entry><entry>1</entry><entry>This attribute indicates which channel is used for the delivery of service.</entry><entry>Boolean</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>0 : Broadcast Channel</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>1 : Interaction Channel</entry><entry /></row><row rowsep="0"><entry>BroadcastServiceDelivery</entry><entry>E2</entry><entry>NO/TM</entry><entry>0..1</entry><entry>This element is used for the indication of IP transmission.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>This element may only be present when:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>TransmissionMedia == 0.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Contains the following Attribute:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry> bdsType</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry> destinationIPAddress</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Contains the following elements:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry> SessionDescriptionReference</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry> SDP</entry><entry /></row></tbody></tgroup></table></tables><tables id="tabl0021" num="0021"><table frame="all"><title>Table 21</title><tgroup cols="6" rowsep="0"><colspec colnum="1" colname="col1" colwidth="35mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="71mm" /><colspec colnum="6" colname="col6" colwidth="25mm" /><tbody><row><entry>bdsType</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>Identifier of the type of underlying distribution system that this access fragment relates to. This attribute may only be present when:</entry><entry>unsignedByte</entry></row><row><entry /><entry /><entry /><entry /><entry>TransmissionMedia == 0.</entry><entry /></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Defined values</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry>0: DVB-H IPDC</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>1. 3GPP MBMS Re1-6</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>2: 3GPP MBMS Rel-7</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>3: 3GPP2 BCMCS (1x)</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>4: 3GPP2 BCMCS (HRPD)</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>5: 3GPP2 Enhanced BCMCS (HRPD)</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>6 -127: reserved for future use</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry>128 -255: reserved for proprietary use</entry><entry /></row><row><entry>destinationIPAddress</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>DestinationIP address of IP stream, which transport A Service over Broadcast channel.</entry><entry>string</entry></row><row><entry /><entry /><entry /><entry /><entry>Note: This attribute is used when SDP is not included in Access Fragment.</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry>If SDP in Access Fragment exists, IP address of the receiver IP address in SDP is used.</entry><entry /></row></tbody></tgroup></table></tables><tables id="tabl0022" num="0022"><table frame="all"><title>Table 22</title><tgroup cols="6" rowsep="0"><colspec colnum="1" colname="col1" colwidth="48mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="11mm" /><colspec colnum="5" colname="col5" colwidth="72mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><tbody><row><entry>Session Description Reference</entry><entry>E3</entry><entry>NO/TM</entry><entry>0..N</entry><entry>The reference to the SessionDescription this access relates to.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Note: The SessionDescription itself may be delivered in two ways via broadcast or via fetch over interaction channel.</entry><entry /></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">In the case of broadcast delivery, the SessionDescription fragment is either delivered in SGDU or encapsulated in this Access fragment. In the latter case the SDP</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry>element is used instead of the Session Description Reference.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>If AuxiliaryDescription fragments are provided they are referenced by the SessionDescriptionReference.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>In the case of fetch over interaction channel, the Session Description can be acquired by accessing the URI (given as attribute of this element).</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Contains the following Attributes:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>type</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>uri</entry><entry /></row><row><entry rowsep="1" /><entry rowsep="1" /><entry rowsep="1" /><entry rowsep="1" /><entry rowsep="1">idRef</entry><entry rowsep="1" /></row></tbody></tgroup></table></tables><tables id="tabl0023" num="0023"><table frame="all"><title>Table 23</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="13mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="94mm" /><colspec colnum="6" colname="col6" colwidth="25mm" /><tbody><row rowsep="0"><entry>type</entry><entry>A</entry><entry>NM/TM</entry><entry>1</entry><entry>Type of the session description referred by this SessionDescriptionReference</entry><entry>unsignedByte</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>0 - SDP</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>1 - MBMS User Service Description (MBMS-USD) as specified in [26.346] section 5.2. It may contain one or several SDP descriptions.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>2 - AssociatedDeliveryProcedure for File Distribution</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>3 - AssociatedDeliveryProcedure for Stream Distribution</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>4-127 Reserved for future use</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>128-255 Reserved for proprietary use</entry><entry /></row><row><entry>uri</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The URI to the file containing SessionDescription that the media application in the terminal uses to access the service or the URI for associatedDeliveryProcedure for File and Stream Distribution.</entry><entry>anyURI</entry></row><row><entry>idRef</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The id of the SessionDescription fragment this access refers to, globally unique.</entry><entry>anyURI</entry></row><row><entry>SDP</entry><entry>E3</entry><entry>NO/TM</entry><entry>0..1</entry><entry>A session description in SDP (IETF session description protocol) format.</entry><entry>string</entry></row></tbody></tgroup></table></tables><tables id="tabl0024" num="0024"><table frame="all"><title>Table 24</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="38mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="11mm" /><colspec colnum="5" colname="col5" colwidth="77mm" /><colspec colnum="6" colname="col6" colwidth="16mm" /><tbody><row rowsep="0"><entry>UnicastServiceDelivery</entry><entry>E2</entry><entry>NO/TM</entry><entry>0..N</entry><entry>This element indicates which server and/or protocol is used for delivery of service over Interaction Channel.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>This element may only be present when: TransmissionMedia == 1.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Contains the following elements:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry> AccessServerURL</entry><entry /></row><row rowsep="0"><entry>AccessServerURL</entry><entry>E3</entry><entry>NO/TM</entry><entry>0..N</entry><entry>Server URL from which the terminal can receive the service via the Interaction Network.</entry><entry>anyURI</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>For example, AccessServerURL can be an HTTP URL pointing to downloadable content, or an RTSP URL pointing to a streaming server for starting a streaming session.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Contains the following Attribute:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry> transmissionSchemeType</entry><entry /></row></tbody></tgroup></table></tables><tables id="tabl0025" num="0025"><table frame="all"><title>Table 25</title><tgroup cols="6" rowsep="0"><colspec colnum="1" colname="col1" colwidth="48mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="11mm" /><colspec colnum="5" colname="col5" colwidth="58mm" /><colspec colnum="6" colname="col6" colwidth="25mm" /><tbody><row><entry>transmission SchemeType</entry><entry>A</entry><entry>NM/TM</entry><entry>1</entry><entry>Specifies transport mechanism that is used for this access.</entry><entry>unsignedByte</entry></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">0-HTTP</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry>1 - MMS</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>2 - WAP1.0</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>3- WAP 2.x</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>4 - RTP</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>5 - 3GPP-PSS (3GPP packet-switched streaming service)</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>6 - 3GPP2-MSS (3GPP2 multimedia streaming services)</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>7 - 3GPP CS videotelephony (3GPP Circuit Switched H324m call)</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>8 - FLUTE</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>9-127 Reserved for future use</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>128-255 Reserved for proprietary use</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry>(Note: Other protocol or communication system may be added based on OMA Service interaction function).</entry><entry /></row><row><entry>ServiceAccessNotificationURL</entry><entry>E1</entry><entry>NO/TM</entry><entry>0..N</entry><entry>URL that the terminal may use to notify when it accesses (switches to) this service over this access. The terminal shall not use this URL for notification without user consent.</entry><entry>anyURI</entry></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry>Note: This URL can for example be used for initiating server-managed channel switching in unicast transmission.</entry><entry /></row></tbody></tgroup></table></tables><tables id="tabl0026" num="0026"><table frame="all"><title>Table 26</title><tgroup cols="6" rowsep="0"><colspec colnum="1" colname="col1" colwidth="40mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="11mm" /><colspec colnum="5" colname="col5" colwidth="80mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><tbody><row><entry>KeyManagementSystem</entry><entry>E1</entry><entry valign="middle">NO/TM</entry><entry>0..N</entry><entry>Identifies the type of Key Management System(s)(KMS) that can be used to contact the Rights Issuer and, for GBA, whether GBA_U is mandatory or whether either GBA_ME or GBA_U can be used.</entry><entry /></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Note that the Rights Issuer can support more than one KMS.</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry>If KeyManagementSystem is not specified, it means no protection is applied.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Values:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>oma-bcast-drm-pki</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Indicates OMA DRM PKI (Public Key Infrastructure);</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>oma-bcast-gba_u-mbms</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Indicates GBA_U 3GPP MBMS SKI (Symmetric Key Infrastructure);</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>oma-bcast-gba_me-mbms</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Indicates GBA_ME 3GPP MBMS SKI i.e. either GBA_ME or GBA_U can be used;</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>oma-bcast-gba_u-bcmcs</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Indicates GBA_U 3GPP2 BCMCS SKI;</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>oma-bcast-gba_me-bcmcs</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Indicates GBA_ME 3GPP2 BCMCS SKI i.e. either GBA_ME or GBA_U can be used;</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>oma-bcast-prov-bcmcs</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Indicates provisioned 3GPP2 BCMCS SKI.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Contains the following Attributes:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>ProtectionType</entry><entry /></row><row><entry rowsep="1" /><entry rowsep="1" /><entry rowsep="1" /><entry rowsep="1" /><entry rowsep="1">RightsIssuerURI</entry><entry rowsep="1" /></row></tbody></tgroup></table></tables><tables id="tabl0027" num="0027"><table frame="all"><title>Table 27</title><tgroup cols="6" rowsep="0"><colspec colnum="1" colname="col1" colwidth="37mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="59mm" /><colspec colnum="6" colname="col6" colwidth="35mm" /><tbody><row><entry>ProtectionType</entry><entry>A</entry><entry>NM/TM</entry><entry>1..2</entry><entry>Specifies the protection type offered by the KMS.</entry><entry>unsignedByte (8 bits)</entry></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Values:</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry>1 Content protection only</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>2 Service protection only</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>3 Both Content protection and Service Protection</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>4 Use of terminal binding (smartcard profile only)</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>5 - 127 Reserved for future use</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry>128 - 255 Reserved for proprietary use</entry><entry /></row><row rowsep="1"><entry>RightsIssuerURI</entry><entry>A</entry><entry>NM/TM</entry><entry>1</entry><entry>Specifies the RightsIssuer URI.</entry><entry>anyURI</entry></row><row><entry>TerminalBinding KeyID</entry><entry>E1</entry><entry>NO/TM</entry><entry>1</entry><entry>Number identifying the Terminal Binding Key ID (TBK ID) that is needed to access the service.</entry><entry>int (32 bits)</entry></row><row><entry /><entry /><entry /><entry /><entry>It is TM for terminals with the smartcard profile.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>It does not apply to the DRM profile.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Contains the following optional Attribute:</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry>RightsIssuerURI</entry><entry /></row><row><entry>RightsIssuerURI</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>Specifies the RightsIssuer URI for the TenninalBindingKey if it is different to the RightsIssuerURI indicated in the KeyManagementSystem element.</entry><entry>anyURI</entry></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry>i.e. If the attribute is not present, the same RightsIssuerURI is used to acquire both SEK / PEK and TerminalBindingKey.</entry><entry /></row></tbody></tgroup></table></tables><tables id="tabl0028" num="0028"><table frame="all"><title>Table 28</title><tgroup cols="6" rowsep="0"><colspec colnum="1" colname="col1" colwidth="33mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="11mm" /><colspec colnum="5" colname="col5" colwidth="81mm" /><colspec colnum="6" colname="col6" colwidth="16mm" /><tbody><row><entry>ServiceIDRef</entry><entry>E1</entry><entry>NO/TM</entry><entry>0..N</entry><entry>Reference to the service fragment(s) to which the access fragment belongs.</entry><entry>anyURI</entry></row><row><entry /><entry /><entry /><entry /><entry>Either one of the ServiceIDRef or ScheduleIDRef but not both shall be instantiated.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Note: Implementation in XML Schema using <choice>.</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry>Each Service fragment shall be associated to at least one Access fragment to enable the terminal to access the Service.</entry><entry /></row><row><entry>ScheduleReference</entry><entry>E1</entry><entry>NM/TM</entry><entry>0..N</entry><entry>Reference to the schedule fragment(s) to which the access fragment belongs.</entry><entry /></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">This provides a reference to a Schedule fragment to temporarily override the default Access fragment of the Service addressed by the Schedule.</entry><entry rowsep="0" /></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Either one of ServiceIDRef or SchedulelDRef but not both shall be instantiated. Note: Implementation in XML Schema using <choice>.</entry><entry rowsep="0" /></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Contains Attribute:</entry><entry rowsep="0" /></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">idRef</entry><entry rowsep="0" /></row><row rowsep="1"><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Contains sub-element:</entry><entry rowsep="0" /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry>DistributionWindowID</entry><entry /></row></tbody></tgroup></table></tables><tables id="tabl0029" num="0029"><table frame="all"><title>Table 29</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="37mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="11mm" /><colspec colnum="5" colname="col5" colwidth="77mm" /><colspec colnum="6" colname="col6" colwidth="16mm" /><tbody><row><entry>idRef</entry><entry>A</entry><entry>NM/TM</entry><entry>1</entry><entry>Identification of the Schedule fragment which the Access fragment relates to.</entry><entry>anyURI</entry></row><row rowsep="0"><entry>DistributionWindowID</entry><entry>E2</entry><entry>NO/TM</entry><entry>0..N</entry><entry>Relation reference to the DistributionWindowID to which the access fragment belongs.</entry><entry>integer</entry></row><row><entry /><entry /><entry /><entry /><entry>The DistributionWindowIDs declared in this element shall be the complete collection or a subset of the DWids declared in the Schedule fragment, to which "idRef" reference belongs.</entry><entry /></row><row rowsep="0"><entry>UsageInfo</entry><entry>E1</entry><entry>NO/TM</entry><entry>0..N</entry><entry>This text helps the user understand what difference it makes to use one or the other access fragment. It 'is mandatory in case more than one access fragment is available at a given point in time.</entry><entry>string</entry></row><row><entry /><entry /><entry /><entry /><entry>Possibly provided in multiple languages. The language is expressed using built-in XML attribute xml:lang with this element.</entry><entry /></row><row><entry>AlternativeAccessURL</entry><entry>E1</entry><entry>NO/TM</entry><entry>0..N</entry><entry>Specify alternative URL of the content for retrieving it via the interaction channel (e.g. if the content cannot be received via the broadcast channel).</entry><entry>anyURI</entry></row></tbody></tgroup></table></tables><tables id="tabl0030" num="0030"><table frame="all"><title>Table 30</title><tgroup cols="6" rowsep="0"><colspec colnum="1" colname="col1" colwidth="51mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="70mm" /><colspec colnum="6" colname="col6" colwidth="10mm" /><tbody><row><entry>TerminalCapability Requirement</entry><entry>E1</entry><entry>NO/TM</entry><entry>0..1</entry><entry>Terminal capabilities required to consume the service or content.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>For video and audio, the media type and the related type attributes in the SDP (see section 5.1.2.5) signal the audio/video decoder. This way, these parameters complement the TerminalCapabilityRequirement.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Additionally, the complexities of the audio/video streams are described here if they differ from the complexities which can be derived from the media type attributes in the SDP (e.g. level). In this case, the parameters defined in the Access fragment take priority.</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Sub-elements:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Video</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Audio</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry>DownloadFile</entry><entry /></row><row><entry>Video</entry><entry>E2</entry><entry>NO/TM</entry><entry>0..1</entry><entry>Video codec capability related requirements</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Sub-elements:</entry><entry /></row><row rowsep="1"><entry /><entry /><entry /><entry /><entry>Complexity</entry><entry /></row></tbody></tgroup></table></tables><tables id="tabl0031" num="0031"><table frame="all"><title>Table 31</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="21mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="73mm" /><colspec colnum="6" colname="col6" colwidth="38mm" /><tbody><row rowsep="0"><entry>Complexity</entry><entry>E3</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The complexity the video decoder has to deal with. It is recommended that this element is included if the complexity indicated by the MIME type parameters in the SDP differs from the actual complexity.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Sub-elements:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Bitrate</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Resolution</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>MinimumBufferSize</entry><entry /></row><row rowsep="0"><entry>Bitrate</entry><entry>E4</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The total bit-rate of the video stream.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Attributes:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>average</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>maximum</entry><entry /></row><row><entry>average</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The average bit-rate in kbits/sec</entry><entry>unsigned Short (16 bits)</entry></row><row><entry>maximum</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The maximum bit-rate in kbits/sec</entry><entry>unsigned Short (16 bits)</entry></row></tbody></tgroup></table></tables><tables id="tabl0032" num="0032"><table frame="all"><title>Table 32</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="33mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="60mm" /><colspec colnum="6" colname="col6" colwidth="38mm" /><tbody><row rowsep="0"><entry>Resolution</entry><entry>E4</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The resolution of the video.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Attributes:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>horizontal</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>vertical</entry><entry /></row><row><entry>horizontal</entry><entry>A</entry><entry>NM/TM</entry><entry>1</entry><entry>The horizontal resolution of the video.</entry><entry>unsignedShort (16 bits)</entry></row><row><entry>vertical</entry><entry>A</entry><entry>NM/TM</entry><entry>1</entry><entry>The vertical resolution of the video.</entry><entry>unsignedShort (16 bits)</entry></row><row><entry>Minimum BufferSize</entry><entry>E4</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The minimum decoder buffer size required to process the video content in kbytes.</entry><entry>unsignedInt (32 bits)</entry></row><row rowsep="0"><entry>Audio</entry><entry>E2</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The audio codec capability.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Sub-elements:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Complexity</entry><entry /></row></tbody></tgroup></table></tables><tables id="tabl0033" num="0033"><table frame="all"><title>Table 33</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="33mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="10mm" /><colspec colnum="5" colname="col5" colwidth="60mm" /><colspec colnum="6" colname="col6" colwidth="38mm" /><tbody><row rowsep="0"><entry>Complexity</entry><entry>E3</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The complexity the audio decoder has to deal with. It is recommended that this element is included if the complexity indicated by the MIME type parameters in the SDP differs from the actual complexity.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Sub-elements:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Bitrate</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>MinimumBufferSize</entry><entry /></row><row rowsep="0"><entry>Bitrate</entry><entry>E4</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The total bit-rate of the audio stream.</entry><entry /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Attributes:</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">average</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry>maximum</entry><entry /></row><row><entry>average</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The average bit-rate in kbits/sec.</entry><entry>unsignedShort (16 bits)</entry></row><row><entry>maximum</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The maximum bit-rate in kbits/sec.</entry><entry>unsignedShort (16 bits)</entry></row><row><entry>MinimumBufferSize</entry><entry>E4</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The minimum decoder buffer size required to process the video content in kbytes.</entry><entry>unsignedInt (32 bits)</entry></row></tbody></tgroup></table></tables><tables id="tabl0034" num="0034"><table frame="all"><title>Table 34</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="26mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="11mm" /><colspec colnum="5" colname="col5" colwidth="92mm" /><colspec colnum="6" colname="col6" colwidth="13mm" /><tbody><row rowsep="0"><entry>DownloadFile</entry><entry>E2</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The required capability for the download files.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Sub-elements:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>MIMETypeSet</entry><entry /></row><row rowsep="0"><entry>MIMETypeSet</entry><entry>E3</entry><entry>NO/TM</entry><entry>0..N</entry><entry>Assuming a download service consists of a set of files with different MIME types which together make up the service, the terminal must support all of these MIME types in order to be able to present the service to the user.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>A MIMETypeSet lists all of these MIME types. If a terminal does not support one or more of the MIME types, it will probably not be able to present the service.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Sub-elements:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>Type</entry><entry /></row><row><entry rowsep="0">Type</entry><entry rowsep="0">E4</entry><entry rowsep="0">NO/TM</entry><entry rowsep="0">0..N</entry><entry rowsep="0">One MIME type in the MIMETypeSet. The format of this string shall follow the Content-type syntax in [RFC 2045].</entry><entry rowsep="0">string</entry></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">Contains the following Attributes:</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry>Codec</entry><entry /></row></tbody></tgroup></table></tables><tables id="tabl0035" num="0035"><table frame="all"><title>Table 35</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="38mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="11mm" /><colspec colnum="5" colname="col5" colwidth="77mm" /><colspec colnum="6" colname="col6" colwidth="15mm" /><tbody><row><entry>Codec</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>The codec parameters for the associated MIME Media type. If the file's MIME type definition specifies mandatory parameters, these must be included in this string. Optional parameters containing information that can be used to determine as to whether the terminal can make use of the file should be included in the string. One example of the parameters defined for audio/3GPP, audio/3GPP2, video/3GPP, video/3GPP2 is specified in [RFC4281].</entry><entry>string</entry></row><row rowsep="0"><entry>BandwidthReq uirement</entry><entry>E1</entry><entry>NO/TM</entry><entry>0..1</entry><entry>Specification of required network bandwidth to access described in this fragment;</entry><entry>integer</entry></row><row><entry /><entry /><entry /><entry /><entry>A broadcast service can include multiple accessible streams (same content) with different bandwidth, so that the terminal can make a choice depending on its current reception condition.</entry><entry /></row><row><entry>ServiceClass</entry><entry>E1</entry><entry>NM/TM</entry><entry>1..N</entry><entry>The ServiceClass identifies the class of service. This identification is more detailed than the type attribute in the service fragment and allows the association of service/access combination to specific applications.</entry><entry>string</entry></row></tbody></tgroup></table></tables><tables id="tabl0036" num="0036"><table frame="all"><title>Table 36</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="32mm" /><colspec colnum="2" colname="col2" colwidth="10mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="11mm" /><colspec colnum="5" colname="col5" colwidth="63mm" /><colspec colnum="6" colname="col6" colwidth="35mm" /><tbody><row rowsep="0"><entry>PreviewData IDRef</entry><entry>E1</entry><entry>NO/TM</entry><entry>0..N</entry><entry>Reference to the PreviewData fragment which specifies an icon, pictogramme, animation or audio.</entry><entry>anyURI</entry></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Attribute:</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>usage</entry><entry /></row><row rowsep="0"><entry>usage</entry><entry>A</entry><entry>NM/TM</entry><entry>1</entry><entry>Possible values:</entry><entry>unsignedByte (8 bits)</entry></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">0. unspecified</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">1. background</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">2. icon/logo</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">3. poster</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">4. trailer</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">5. barker</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">6. service/channel zapping</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">7-127. reserved for future use</entry><entry rowsep="0" /></row><row><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0" /><entry rowsep="0">128 -255. reserved for proprietary use</entry><entry rowsep="0" /></row><row><entry /><entry /><entry /><entry /><entry>Note: only usage = 6 (service/channel zapping) is the valid value when the preview data is associated with Access fragment.</entry><entry /></row></tbody></tgroup></table></tables><tables id="tabl0037" num="0037"><table frame="all"><title>Table 37</title><tgroup cols="6"><colspec colnum="1" colname="col1" colwidth="50mm" /><colspec colnum="2" colname="col2" colwidth="24mm" /><colspec colnum="3" colname="col3" colwidth="16mm" /><colspec colnum="4" colname="col4" colwidth="11mm" /><colspec colnum="5" colname="col5" colwidth="51mm" /><colspec colnum="6" colname="col6" colwidth="16mm" /><tbody><row rowsep="0"><entry>Notification Reception</entry><entry>E1</entry><entry>NO/TM</entry><entry>0..1</entry><entry>Reception information for Notification Messages.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>NotificationPort is mandatory because a designated UDP Port shall be used to deliver the notification message through an on-going session or the designated session while NotificationAddress is optionally used for the delivery of Notification Messages through the designated multicast or broadcast session.</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>Contains the following attributes:</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>NotificationPort</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>NotificationAddress</entry><entry /></row><row rowsep="0"><entry /><entry /><entry /><entry /><entry>NotificationRequestURL</entry><entry /></row><row><entry /><entry /><entry /><entry /><entry>NotificationPollURL</entry><entry /></row><row><entry>Notification Port</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>Service-specific Notification Message delivery UDP Port number.</entry><entry>integer</entry></row><row><entry rowsep="0">Notification Address</entry><entry rowsep="0">A</entry><entry rowsep="0">NO/TM</entry><entry rowsep="0">0..1</entry><entry rowsep="0">Service-specific Notification Message delivery IP multicast address.</entry><entry rowsep="0">string</entry></row><row><entry /><entry /><entry /><entry /><entry>Note: If Notification Message is delivered over interaction channel, this attribute should be combined with NotificationPort.</entry><entry /></row><row><entry>Notification RequestURL</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>URL through which the terminal can subscribe to service-specific Notification Messages.</entry><entry>anyURI</entry></row><row><entry>Notification PollURL</entry><entry>A</entry><entry>NO/TM</entry><entry>0..1</entry><entry>URL through which the terminal can poll service-specific Notification Messages.</entry><entry>anyURI</entry></row><row><entry><proprietary elements/attributes></entry><entry>E1 or lower, A</entry><entry>NO/TO</entry><entry>0..N</entry><entry>Any number of proprietary or application-specific elements or attributes that are not defined in this specification.</entry><entry /></row></tbody></tgroup></table></tables>
As can be understood from the foregoing description, embodiments of the present invention can provide detailed access information of the broadcast network or the interaction network, via which the broadcast service is transmitted, in the broadcasting system providing IP-based broadcast services.
Embodiments of the present invention can provide detailed access information of the broadcast network or the interaction network, via which the service is transmitted to the mobile terminal, by providing an efficient access fragment format in the broadcasting system providing IP-based broadcast services.
Further, embodiments of the present invention can provide an efficient access fragment format when accessing a plurality of services through one access fragment.
In addition, embodiments of the present invention provide an access fragment transmission/reception method and apparatus for efficiently supporting the transmission scheme/transmission topology and protocol for each individual channel over which the service is transmitted, in the process of configuring Access Type of the access fragment, thereby allowing the mobile terminal to efficiently access the service.
Moreover, embodiments of the present invention provide IP multicast transmission information to the mobile terminal in the broadcasting system requiring a high data rate, contributing to a reduction in the wireless resources.
While the invention has been shown and described with reference to certain exemplary embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.
8 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US10015642B2 | Cited by | United States of America | Applicant |
| US8180358B2 | Cited by | United States of America | Search report |
| US8578424B2 | Cited by | United States of America | Applicant |
| EP2045936A2 | Cited by | European Patent Office (EPO) | Search report |
| EP2153652A1 | Cited by | European Patent Office (EPO) | Search report |
| EP2076019A2 | Cited by | European Patent Office (EPO) | Search report |
| US8917706B2 | Cited by | United States of America | Applicant |
| EP2824932A1 | Cited by | European Patent Office (EPO) | Search report |
| EP2271083A2 | Cited by | European Patent Office (EPO) | Search report |
| US9578467B2 | Cited by | United States of America | Applicant |
| US9819453B2 | Cited by | United States of America | Applicant |
| EP2045936A3 | Cited by | European Patent Office (EPO) | Search report |
| US8180358B2 | Cited by | United States of America | Applicant |
| EP2076032A2 | Cited by | European Patent Office (EPO) | Search report |
| WO2008143446A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| EP2174492A4 | Cited by | European Patent Office (EPO) | Search report |
| WO2009085944A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| WO2008100674A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| EP2153652A4 | Cited by | European Patent Office (EPO) | Search report |
| KR20150011320A | Cited by | Republic of Korea | Search report |
| WO2009101602A3 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| EP2271083A3 | Cited by | European Patent Office (EPO) | Search report |
| KR100960400B1 | Cited by | Republic of Korea | Search report |
| US8555319B2 | Cited by | United States of America | Applicant |
| EP2174492A1 | Cited by | European Patent Office (EPO) | Search report |
| EP2830258A1 | Cited by | European Patent Office (EPO) | Search report |
| US9544073B2 | Cited by | United States of America | Applicant |
| EP2353289A2 | Cited by | European Patent Office (EPO) | Search report |
| WO2009101602A2 | Cited by | World Intellectual Property Organization (WIPO) | Applicant |
| EP2353289A4 | Cited by | European Patent Office (EPO) | Search report |
| WO2010064836A2 | Cited by | World Intellectual Property Organization (WIPO) | Applicant |
| EP1562322A1 | Cites | European Patent Office (EPO) | Search report |
| US2002141591A1 | Cites | United States of America | Search report |
27 members in 10 offices
Priority claims15
| Document | Office | Kind | Date |
|---|---|---|---|
| 20050074011 | Republic of Korea | A | |
| 20050074011 | Republic of Korea | A | |
| 20050074011 | Republic of Korea | – | |
| 20050074534 | Republic of Korea | A | |
| 20050074534 | Republic of Korea | A | |
| 20050074534 | Republic of Korea | – | |
| 20060064116 | Republic of Korea | A | |
| 20060064116 | Republic of Korea | A | |
| 20060064116 | Republic of Korea | – | |
| 20050074011 | – | – | – |
| 20050074534 | – | – | – |
| 20060064116 | – | – | – |
| KR20050074011 | – | – | – |
| KR20050074534 | – | – | – |
| KR20060064116 | – | – | – |
Members27
| Document | Office | Kind | |
|---|---|---|---|
| EP1753166A2This record | European Patent Office (EPO) | A2 | |
| AU2006277101A1 | Australia | A1 | |
| CA2615311A1 | Canada | A1 | |
| KR20070019538A | Republic of Korea | A | |
| US2007036102A1 | United States of America | A1 | |
| WO2007018415A1 | World Intellectual Property Organization (WIPO) | A1 | |
| EP1753166A3 | European Patent Office (EPO) | A3 | |
| CN101238732A | China | A | |
| JP2009504074A | Japan | A | |
| RU2008104862A | Russian Federation | A | |
| RU2372742C1 | Russian Federation | C1 | |
| KR100960400B1 | Republic of Korea | B1 | |
| AU2006277101B2 | Australia | B2 | |
| AU2006277101C1 | Australia | C1 | |
| EP2259494A2 | European Patent Office (EPO) | A2 | |
| JP4620777B2 | Japan | B2 | |
| BRPI0614744A2 | Brazil | A2 | |
| EP2259494A3 | European Patent Office (EPO) | A3 | |
| CN101238732B | China | B | |
| CA2615311C | Canada | C | |
| US8917706B2 | United States of America | B2 | |
| US2015103729A1 | United States of America | A1 | |
| US9578467B2 | United States of America | B2 | |
| US2017150328A1 | United States of America | A1 | |
| US10015642B2 | United States of America | B2 | |
| BRPI0614744B1 | Brazil | B1 | |
| EP2259494B1 | European Patent Office (EPO) | B1 |
12 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Application refused18R | 18R | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE APPLICATION HAS BEEN REFUSEDSTAA | STAA | |
| Party data changed (applicant data changed or rights of an application transferred)RAP1 | RAP1 | |
| Designation fees paidAKX | AKX | |
| First examination report despatched17Q | 17Q | |
| Designated contracting statesAK | AK | |
| Request for extension of the european patentAX | AX | |
| Search report despatchedORIGINAL CODE: 0009013PUAL | PUAL | |
| Request for examination filed17P | 17P | |
| Designated contracting statesAK | AK | |
| Request for extension of the european patentAX | AX | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI |
Numbers
- Publication
- 1753166
- Publication, DOCDB
- 1753166
- Publication, EPODOC
- EP1753166
- Application
- 6016838
- Application, DOCDB
- 06016838
- Application, EPODOC
- EP20060016838
Titles3
- German
- Verfahren und Vorrichtung zum Übertragen und Empfangen von Zugangsinformationen eines Mehrfachsendungsdienstes
- English
- Method and system for transmitting and receiving access information for a broadcast service
- French
- Procédé et dispositif pour transmettre et recevoir une information d'accès à un service de multidiffusion
Classification
- CPC, 14
- H04H20/93
- H04W4/06
- H04H60/91
- H04L12/1877
- H04L12/189
- H04W4/12
- H04H20/82
- H04H60/73
- H04H2201/33
- H04W80/10
- H04W72/30
- H04H20/86
- H04W48/10
- H04W80/12
- IPC, 8
- H04L12 18
- H04H20 57
- H04L12 70
- H04N7 173
- H04N21 83
- H04W4 06
- H04W48 18
- H04W80 10
Designated states36
- Contracting states, 31
- Austria
- Belgium
- Bulgaria
- Switzerland
- Cyprus
- Czechia
- Germany
- Denmark
- Estonia
- Spain
- Finland
- France
- United Kingdom
- Greece
- Hungary
- Ireland
- Iceland
- Italy
- Liechtenstein
- Lithuania
- Luxembourg
- Latvia
- Monaco
- Netherlands (Kingdom of the)
and 7 moreShow fewer
- Poland
- Portugal
- Romania
- Sweden
- Slovenia
- Slovakia
- Türkiye
- Extension states, 5
- Albania
- Bosnia and Herzegovina
- Croatia
- North Macedonia
- Yugoslavia, later Serbia and Montenegro (until 2006)