TW201108653A - Rich media-enabled service guide provision method and system for broadcast service - Google Patents

Abstract

A service guide provision method and system for a digital broadcast service is provided for distributing a rich media-enabled service guide. A rich media-enabled service guide provisioning method for a digital broadcast service includes creating a Rich Media Solution (RMS) template for a service guide with reference to service guide fragments; creating a service guide delivery descriptor containing RMS information on the RMS template and service guide fragment information on the service guide fragments; and broadcasting the service guide fragments, the RMS template, and the service guide delivery descriptor.

Description

201108653. jj^upif VI. Invention Description: [Priority] This application claims wisdom in Korea on January 15, 2009, June 5, 2009, June 12, 2009 and June 24, 2009, respectively. The title of the application is “RICH MEDIA-ENABLED SERVICE GUIDE PROVISION METHOD” by the Property Bureau and the assignments are No. 10-2009-0003185, No. 10-2009-0049958, No. 10-2009-0052574 and No. 10-2009-0056688. The priority of the application of the AND SYSTEM FOR BROADCAST SERVICE, the contents of each of which is incorporated herein by reference. [Technical Field of the Invention] The present invention relates to a broadcast service, and in particular to a service guide supply method and system for a digital broadcast service capable of distributing rich media enhanced service guidance. [Prior Art] A broadcast is a service that can be received by all users having a broadcast receiver. Broadcast services can be broadly classified into two categories: radio broadcast services that only carry audio and multimedia broadcast services that carry audio and video plus data. These broadcast services have evolved from analog services to digital services. Currently, various types of broadcast systems (such as cable broadcasting systems, satellite broadcasting systems, and hybrid broadcasting systems using both cable networks and satellites) have been developed to provide high quality. Audio and video broadcasting services and high-speed data services. The mobile communications market is faced with the need for new services due to the reorganization or reintegration of existing technologies. Development of communication and broadcast technologies has allowed users

201108653 f vOlX enjoys broadcast services in action using portable devices such as mobile phones and personal digital assistants (pe_i D.g.tal Assistant, ship). Due to the potential and actual market needs of multi-ship services and increased user demand, service providers are also providing services such as services (10) in addition to existing voice services, and information technology (Information Technology, ΓΓ) The company's established interest in supporting the communication business to meet user needs, and the convergence of mobile communication services and Internet Protocol (〇) technology has become the next generation of mobile communications. Priority in the development of technology^. The aggregation has introduced and applied various wireless/broadcast services not only in the mobile communications market but also in the general wired pass b market, and all-around aggregation has enabled the same consumer environment to be used for different services, regardless of The service is a wired or wireless broadcast service. 〇pen Mobile Alliance (OMA)_ Develop a community of standards for intercommunication between individual action solutions - used to define mobile games and Internet services

Various application standards. 0MA mobile broadcast service intensifier set (〇MA

Mobile Broadcast Services Enabler Suite (OMABCAST) is an open global 〇 〇 ) 曰疋 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。 。. OMA BCAST addresses the standardization of technologies for providing ip-based mobile content delivery, such as multiple functional areas 'including service guidance, download and streaming, service and valley protection, service reservations And roaming. With the trend of fixed and mobile aggregation, such as OMA BCAST, etc. 6 201108653 Mobile broadcast technology is evolving. To provide services in a fixed_action integration environment

In the nickname, the service guide has content-related information, so that the display format of the service guide depends on the implementation of the terminal. Since the service guidance as a starting point for all services provided by the service provider can be displayed in different formats depending on the manufacturer and model of the terminal, it is difficult to provide uniform service accessibility to broadcast users (accessibility). ). In order to solve this problem, a rich media technology is needed to define a display format suitable for various terminal displays. Moving Pictures Experts Group-Lightweight Application Scene Representation » MPEG-LASeR, 3rd Generation Partnership-Dynamic and Interactive

Multimedia Scenes, 3GPP-DIMS) and the Open Mobile Alliance_Rich Media Environment (OMA-RME) are representative rich media integration solutions. However, in the case of applying rich media technologies to service guidance, compatibility issues arise such that service guidance can only be displayed on rich media enhanced terminal displays. There is therefore a need to develop a method for providing rich media enhanced service guidance suitable for terminal capabilities. SUMMARY OF THE INVENTION To overcome at least the problems of the prior art, the present invention provides a rich media enhanced service guide provisioning method and system for broadcasting 201108653〆 services. Moreover, the present invention provides a rich media enhanced service guidance provisioning method and system for broadcast services, which can be backward compatible without the use of a female media by using a rich media based service guide template In the case of sex, 'reproduce rich media to strengthen service guidance. According to an embodiment of the present invention, a rich media enhanced service guidance provisioning method for a digital broadcast service includes: creating a rich media solution (Rich Media Solution' RMS) template for service guidance by referring to a service guide segment; Creating a service guide delivery descriptor containing RMS information about the RMS template, and service guide segment information about the service guide segment; and broadcasting the service guide segment, the RMS template, and the The service guide passes the descriptor. According to another embodiment of the present invention, a rich media enhanced service guidance handling method for a digital broadcast service includes: receiving at least one service guide delivery descriptor; referring to a service guide contained in a service guide delivery descriptor The service guide segment is extracted by referring to the information of the segment; the rich media solution (RMS) template is received with reference to the RMS information of the service guide delivery descriptor; and the service guide for rendering the service guide segment is output using the RMS template. According to still another embodiment of the present invention, a rich media enhanced service guidance provisioning system for a digital broadcast service includes: a broadcast distribution/adaptation unit 'which transmits a service guide delivery descriptor' Information about the service guide segment, rich media solution (RMS) template, service guide segment information, and rms template information; and 8 201108653 . and the terminal, the reference service guide delivers the descriptor of the service guide segment information The service guide segment is extracted, the RMS template is received with reference to the RMS template information of the service guide delivery descriptor, and the RMS template is used to output the service guide reproduced by the service guide segment. The above and other objects, features and advantages of the present invention will become apparent from [Embodiment] Embodiments of the present invention will be described in detail with reference to the accompanying drawings. The same reference numbers are used in the drawings to refer to the same or the like. Detailed descriptions of well-known functions and structures incorporated herein may be omitted to avoid obscuring the subject matter of the present invention. The use of the terms and words in the following description and claims is not to be construed as a limitation Therefore, it is to be understood that the description of the embodiments of the present invention is intended to be provide. Hereinafter, description will be made using the techniques and expressions of 3GPP DIMS and OMA BCAST standards. However, the present invention is not limited to this and it is based on the A and the system which can be developed under the difficult concept. 〃 digits; the digital broadcasting system of the invention of the embodiment. Although 201108653pif Figure 1 is a block diagram illustrating the logical architecture of the BCAST system that handles the application layer and transport layer specified by the OMA BCAST work group. As shown in Figure 1, the logical architecture of the BCAST system includes content creation.

(Content Creation ' CC ) 1 (U, BCAST Service Application 1, 2, BCAST Service Distribution / Adaptation 103, BCAST Subscription Management l〇4, Terminal ι〇5, BDS Service Distribution 111, Broadcast Distribution System 112, and Networked Network 113. Content Creation (CC) 101 provides content that is the basis of the BCAST service. The content may be files for common broadcast services, such as materials for movies, audio, and video. Content Creation 101 to BCAST Service Application 102 Providing an attribute of content for creating a service guide and determining a transport bearer on which the service will be delivered. The BCAST service application 102 receives data from the BCAST service provided by the content creation 1.1, and The received data is converted into a form suitable for providing media encoding, content protection, interactive services, etc. The BCAST service application 102 provides attributes of the content received from the content creation 101 to BCAST Service Distribution/Adaptation (BCAST Service Distribution/Adaptation, BSDA) 103 and BCAST Subscription Management (BSM) 104 〇 BCAST Service Distribution/Adaptation 103 is used from the BCAST Service Application 102 provides BCAST service data to perform operations such as archival/streaming, service collection, service protection, service guidance creation/delivery, and service notification. BCAST Service Distribution/Adaptation 103 adapts the service to a broadcast distribution system (Broadcast Distribution System) , BDS) 112 In particular, in the embodiment of the present invention, 'BCAST Service Distribution/Adaptation 103 201108653 Create Rich Media Solution (RMS) Template' and transmit the RMS template information along with the RMS template to the terminal 1〇5. BCAST Reservation The management 104 manages, by hardware and/or software, service offerings such as subscription and charge related functions for BCAST service users, information provision for BCAST services, and mobile terminals that receive BCAST services. Terminal 105 receives content/ The service guide and the program support information such as content protection 'and provide the broadcast service to the user. Especially in the embodiment of the present invention, the terminal 105 receives the RMS information and the RMS template based on the RMS information. The terminal 105 also receives the service. Guide, and use rmS template to output the service guide. BDS service distribution 111 via The broadcast distribution system 112 and the interactive network 113 communicate with each other to deliver the mobile broadcast service to a plurality of terminals. The broadcast distribution system 112 communicates the mobile broadcast service via a broadcast channel and may include, for example, a third generation partnership program ( 3rd Generation Project Partnership (3GPP) Multimedia Broadcast Multicast Service (MBMS), 3rd Generation Project Partnership 2 (3GPP2) Broadcast Multicast Service (BCMCS) DVB-Handheld (DVB-H) function, or Internet Protocol (IP)-based broadcast/communication network, achieved by Digital Video Broadcasting (DVB). Interacti〇 Network 113 provides interactive channels and may include, for example, a cellular network and the like. 11 201108653 , now describes the reference point as the connection path between the above logical entities. The reference point has multiple interfaces depending on its purpose. The interface is used for communication between two or more logical entities to achieve its specific purpose, and the message formats, protocols, and the like for the interface are applied. BCAST-1 121 in Figure 1 is a routing path for content and content attributes, and BCAST-2 122 is a passer for BCAST services, attributes of BCAST services, and content attributes for content protected or unprotected content. path. BCAST-3 123 is the transmission path for the attributes of the BCAST service, the attributes of the content, user preferences/subscription information, user requests, and responses to requests. BCAST-4 124 is a transmission path for a notification message, attributes used for service guidance, and a key used for content protection and service protection. BCAST-5 125 is a transmission path for: Protected BCAST Service, Unprotected BCAST Service, Content Protected BCAST Service, Content Unprotected BCAST Service, BCAST Service Attribute, Content Attribute, Notification , service guidance, such as Digital Right Management 'DRM' rights object (Rights)

Object 'RO' and security material such as key value for BCAST service protection' and all data and signaling via broadcast channel 0 BCAST-6 126 is the transmission path for: protected BCAST service, unprotected BCAST service, content protected BCAST service, content unprotected BCAST service, bcAST service 12 201108653. Service attributes, internal attributes, notifications, service guides, such as DR]y[R安全 and security materials used for BCAST service protection cryptographic values, etc., as well as all materials and transmissions transmitted via interactive channels. BCAST-7 127 is a transmission path for: service provisioning, subscription information, device management, and user preference information transmitted via interactive channels for use with, for example, DRM RO and for BCAST service protection. Control information related to the reception of security materials such as key values. BCAST-8 128 is the transmission path through which the user data of the BCAST service interacts. BDS-1 129 is a transmission path for: · Protected BCAST services, unprotected BCAST services, BCAST service attributes, content attributes, notifications, service guides, and such as DRMRO and for BCAST service protection Security material such as key value. The BDS-2 130 is a transmission path for service provisioning, subscription information, device management, and security materials such as DRMRO and key values for BCAST service protection. X-1 131 is a reference point between the BDS service distribution 111 and the broadcast distribution system 112. X-2 132 is the reference point between the BDS service distribution 111 and the interactive network 113. X-3 133 is a reference point between the broadcast distribution system 112 and the terminal 105. X-4 134 is a reference point between the BDS service distribution 111 and the terminal 1〇5 via the broadcast channel. X-5 135 is a reference point between the BDS service distribution 111 and the terminal 105 via an interactive channel. X-6 136 is the reference point between the interactive network 113 and the terminal 105. 13 201108653pif A description will now be made of a service guidance data model for providing service guidance according to an embodiment of the present invention. Figure 2 is a diagram illustrating the structure of a service guide > material model for use in the 〇MA BCAST system. In Figure 2, each square is referred to as a segment, and the solid arrows between the segments indicate the reference direction between the segments. As shown in FIG. 2, the service guidance data model includes: a management group 200 for providing basic information about the entire service guide; a supply group 210 for providing subscription and purchase information; and a core group 22〇, as The core part of the service guide; and the access group 23, which is used to provide access to information to control access to services and content. Management Group 200 contains Service Guide Delivery Descriptors (Service Guide)

Delivery Descriptor 'SGDD) 2 (H. [Please change "Description" in block 2Θ1 of Figure 2 to "Descriptor".) Supply group 210 includes purchase item 211, purchase material 212, and purchase channel 213. Core group 220 contains The service 22 schedules 222 and the content 223. The access group 230 includes an access 231 and a session description 232. In addition to the four information groups 200, 210, 220, and 230, the service guide data The model further includes preview data 241 and interactive data 251. The components mentioned above are referred to as fragments and are the basic units that constitute the service guide. In the following, descriptions of individual segments of the service guidance data model are described. The SGDD fragment 201 provides information about the delivery session, including the service guide delivery unit that constitutes the segment of the service guide (Service Guide 201108653.

The Delivery Unit 'SGDU' is located in the delivery session. The SGDU is used to include the service guide segments 211, 212, 213, 221 constituting the service guide.

The inclusions 222, 223, 231, 232, 241, and 251 〇 SGDD 201 also provide information about entry points for receiving packet information and notification messages. The service fragment 221 is an upper aggregate of content included in the broadcast service and contains information about service content, genre, service location, and the like. The scheduling segment 222 defines a time frame in which the associated content items are available for streaming, downloading, and/or rendering. The content segment 223 provides a detailed description of a particular content item and information about the target user group or geographic area and style. The access fragment 231 provides access to relevant information to allow the user to view the service and delivery method' and provides session information associated with the corresponding access session. The session description segment 232 can be included in the access segment 231 and provided in the form of a Uniform Resource Identifier (URI) to provide location information so that the terminal can detect the negative information about the session description segment 232. The session description segment 232 provides address information, codec information, and the like for the multimedia content present in the session. The purchase item segment 211 provides a bundle of services, content, time, etc. to assist the user in booking or purchasing the purchase item segment 211. The purchase material segment 212 contains detailed purchase and reservation information for the service or content bundle, such as price information and promotion (prom〇ti〇n) 15 201108653. == Fragment 213 provides access information for booking or giving. Pre-investment; bucket segment 241 can be used to provide previews of services, schedules, and content. The interactive material segment 251 provides interactive services based on the services, schedules, and content of the broadcast middle. Detailed information about the service guide can be defined based on the top data model in Figure 2, which provides the details and values of the elements and attributes. Although not depicted, the segments that make up the service guide may contain elements and attribute values for a plurality of purposes. A message summary table in accordance with an embodiment of the present invention is described below. The table shows an exemplary summary table used in the embodiment of the present invention. Table 1 Name Type Type Cardinality Description Data Type As shown in Table 1, the summary table contains the name field, type field, category field, cardinality field, description block, and data type field. The name field indicates the name of the element value or attribute value. The type field indicates the type of element or attribute. The element has one of the values (ie, El, E2, E3, and E4). E1 is the sub element of element e, E2 is the sub element of E1' E3 is a child element of E2, and E4 is a child element of E3. The attribute has a value of A and indicates the attribute of the element. For example, the layer below the E1 s stomach element. The type bar is used to indicate that the element/attribute is mandatory or optional and is marked by the element for mandatory elements/attributes and for the optional element/attribute 201108653 j»upif. "The cardinality block indicates the relationship between elements and has the values "〇", 〇'1, 1, ‘‘〇.·η', and Ύ. An element or attribute is optional if it has a base of zero. An element or attribute is mandatory if it has a cardinality 丨. And ^ ' if the element or attribute has a base n, it can have multiple values. For example, the base "Gn" means that the element or attribute may have no value or have n values. This description field provides a detailed description of the element or attribute. Data Type The block indicates the data type of the element or attribute. 3 is a block diagram showing the relationship between SGDD and SGDU in the service guidance data model of FIG. 2. Referring to Figure 3, the Service Guided Delivery Descriptor (SGDD) fragment 301 (201 in Figure 2) contains session information, grouping information, and notification message access information associated with all segments containing service information. Especially in an embodiment of the invention 'SGDD 301 contains information about the RMS template. The information on the RMS template is described in more detail later. If the terminal supporting the mobile broadcast service is powered on and starts receiving the service guide, then the terminal accesses the service guide advertisement channel (Service Guide)

Announcement Channe SG Announcement Channel) 300. The SG announcement channel 300 contains at least one SGDD 301 (e.g., SGDD #1, ..., SGDD #2, ..., SGDD #3), which is formatted as shown in Table 2. Table 2 Hemp _ class 歪 | type I base I description

I data type I 17

201108653 f v/plX

The ServiceGuide Delivery Descriptor E service-directed delivery descriptor contains the following attributes: The id version contains the following elements: NotificationReception BSMList DescriptorEntry Id A NM/ TM 0..1 Unique identifier of the SGDD in a particular SG Any URI Version A NM/ TM 0 ..1 version of SGDD. As soon as a newer version is received, the newer version will surpass the older version. Unsigned integer Notification Reception El NM/ TM 0..1 Used to receive information for general notification messages. In the case of delivery via a broadcast channel, IPBroadcastDelivery specifies the address information used to receive the notification message. In the case of delivery via an interactive channel, the RequestURL specifies the address information for the subscription notification, and the PollURL specifies the address information for the polling notification. When the notification message resource pointed to by this element provides a notification message for the service delivery guide update, their notification message will be related to the currently initiated service guide. If this element exists, at least one of the attributes "IPBroadcastDelivery", "RequestURL" or "PollURL" will exist. Contains the following elements: IPBroadcastDelivery RequestURL PollURL TimeGrouping Criteria E3 NM/ TM 0..1 Specifies the time period described by this DescriptorEntry. (For example: a sub-group of valid service guides is declared for the next 2 hours). This field contains the 32-bit integer part of the NTP timestamp. Contains the following attributes: startTime endTime If the fragment describes the distribution and consumption during the time interval that does not deviate from the time interval specified by startTime and / or endTime 18 201108653.

Or the activated content or interactive message' then the segment matches the TimeGroupingCriteria. IPBroadcast Delivery E2 NM/TM 0..1 provides IP multicast addresses and nicknames for broadcast via broadcast channels. ° Contains the following attributes: port address startTime A NM/ TM 1 TimeGroupmgCntena Start. This block contains the 32-bit integer part of the NTP time #·#. ° Unsigned integer endTime A NM/ TM 1 End of TimeGroupingCntena. This block contains the 32-bit integer part of the NTP time. ° Unsigned integer GenreGrouping Criteria E3 NM/ TM 0..1 Specifies the classification of services/content associated with this service guide ^^^· segment (^丨如,喜剧, action 'drama)》 OMA BCAST Service Guide The format allows the format of the style element in the service guide to be described in two ways: The first way is to use a free string. The second-hand method uses the “href” attribute of the style element to convey information in the form of a controlled vocabulary (such as the classification scheme defined in [TVA-Metadata] or a classification list as defined in [MIGFG]). The built-in XML attribute xmi:lang can be used with this element to express the language. ϊ Illustrate a set of different style elements 〇 'Use it as a free string or with ^^ attribute: use. The network will ensure that different sets have a sudden The meaning of the terminal, and the terminal will be selected. The final use string contains the following attributes: type href Port A NM/ TM 1 , the message UDp destination nickname; Μ by the broadcast channel value. Unsigned Integer Address A NM/ TM 1 Known message delivery 1ρ multicast address; via broadcast channel value #. String RequestURL E2 NM/ 0..1 Any URI 19 201108653 f V ^ VL/ll TM URL; passed via interactive channel PollURL E2 NM/ TM 0..1 The terminal can poll the URL via which the general notification message is sent via the interactive channel. Any URI BSMList El NM/ TM 0..1 declaration can be used in the GroupingCriteria section defined below. BSM The following elements are included: BSMSelector BSMSelector E2 NM/ TM 1..N Specifies that the BSM associated with the segment in this service pilot delivery unit allows the terminal to determine this SGDD in the SGDUs published in various DescriptorEntry in various SGDDs. Whether the SGDU in the DescriptorEntry is associated with the terminal affiliated BSM. The terminal attached BSM is represented in the terminal as a management object with the identifier &lt;x&gt;/ BSMSelector/BSMFilterCodeor, such as [3GPP TS 22.022], [3GPP2 C.S0068- The code on the smart card defined by [3GPP TS 31.102], [3GPP2 C.S0023-C] or [3GPP2 C.S0065-0]... To interpret BSMSelector in SGDD, the following sections will apply. : If any of the BSMFilterCodes present in this element match any of the &lt;X&gt;BSMSelector//BSMFilterCode entries in the terminal or with any of the code on the smart card, ie, all instantiation properties of BSMFilterCode have &lt;X&gt;/BSMFilterCode under the matching example attribute or the matching code on the smart card, the terminal can process, reproduce, interpret and process the film without restriction . Note that a match is considered to be a match when the instantiated property under BMSFilterCode matches a subset of the instance attributes of &lt;X&gt;/BSMSelector/BSMFilterCode or matches a subset of the code on the smart card. However, when the BSMFilterCode is represented as a superset of the attributes of the <X>/BSMSelector/BSMFilterCode or a superset of the code on the smart card 4, it is not considered a match because it is not all the examples under the BSMFilterCode 20 201108653 jj^ The yupif attribute matches the code on the instantiation attribute of the &lt;X&gt;/BSMSelector/BSMFilterCode or the smart card. If the BSMFilterCode present in this element does not match any of the &lt;X&gt;/BSMSelector/BSMFilterCode entries in the terminal, that is, not all of the instantiated attributes of the BSMFilterCode have &lt;X&gt;/BSMSelector/BSMFilterCode or smart card The matching instantiation attribute under the code above, the terminal can reproduce, interpret and process the fragment according to the RoamingRule (identified by the attribute id) associated with the BSMSelector. In the case where the terminal does not have such a Roaming Rule, the terminal will not reproduce the clip to the user. The terminal can obtain the rule by sending a RoamingRuleRequest to the address indicated by the attribute "roamingRuleRequestAddress". In the case where the terminal does not have an &lt;X&gt;/BSMSelector/BSMFilterCode entry or does not have a code on the smart card, in order to interpret the BSMSelector in the SGDD, the following sections will apply: The terminal can be associated with this BSMSelector RoamingRule (identified by the attribute id) to reproduce, interpret, and process fragments. In the event that the terminal does not have such a RoamingRule, the terminal will not reproduce the clip to the user. The terminal can obtain the rule by sending a RoamingRuleRequest to the address indicated by the attribute &quot;roamingRuleRequestAddress&quot;. Note: The RoamingRuleRequest message and associated roaming method are specified in [BCAST10-Services]. Contains the following attributes: id 21 201108653 f

The roamingRuleRequestAddress contains the following elements: BSMFilterCode Name RoamingRule Type A NO/ TO 0..1 This attribute indicates the level of this style element. The following values are allowed: "Primary" "Secondary" "Other" String Href A NO/ TO 0..1 This attribute represents a controlled vocabulary for this style element. If this attribute is supported, the following sections apply to support and use the classification scheme according to [TVA-Metadata]: For values equal to the type attribute of "main" or "secondary", the terminal can support [TVA-metadata) The classificationSchemeURI defined in Appendix A.8 of Appendix A.8: tva:metadata:cs :ContentCS :2005 The level 1 to 4 of the TV Anytime ContentCS classification scheme identified. For the value of the type attribute equal to "other", the terminal can support the TV Anytime IntendedAudienceCS identified by the classificationSchemeURI urn:tva:metadata: cs: IntendedAudience CS :2005 as defined in Appendix A.11 of [TVA-Metadata] Grades 1 to 3 of the classification scheme. When both the ExtendedAudienceCS and the TargetUserProfile are provided, the two will be equivalent. The network will use the following URI syntax to represent items from the classification scheme: <classificationSchemeURI> &quot;:&quot;&lt;termID&gt; If this attribute is instantiated by the network, the element Genre will be an empty string and xml will not be used: Lang attribute. Any URI 22 201108653 jjnyupif If this property is supported then the following sections apply to support and use the classification from [MIGFG]: This "category will be URI http://www.loc. gov/rr/mopic/mi ggen.html" Said. The string value carried in the Genre element will be used to convey the actual value of the classification as given in [MIGFG]. The network can use the values of the type attribute "primary" and "secondary" to provide ordering for the two categories of the same service. The href attribute can be used to indicate other classification schemes' but how it is used beyond the scope of this specification. If this attribute is not instantiated, the Genre element will be a free string. BSMSelector E3 NM/TM 0..N specifies the BSM associated with the segment in this service steering delivery unit by reference to the BSMSelector structure declared above. Contains the following attributes: idRef idRef A NM/ TM 1 Reference to the identifier of the BSMSelector declared in the above BSMList. Any URI ServiceCriteria E3 NM/TM 0..1 allows packets to be grouped by service. The value of this field is the fragment ID of the service fragment associated with the service. Any URI Transport E2 NM/TM 0..1 points to the transport session that conveys the transport session of the service pilot segment within the service transport delivery unit published in this DescriptorEntry. Contains the following attributes: ipAddress, port, srcIpAddress, transmissionSessionID, hasFDT Id A NM/ TM 1 BSMSelector identifier. This id is unique within the network. Any URI roamingRuleReq uestAddress A NO/ TM 0..1 The terminal can send a RoamingRuleRequest to it to request the address of the RoamingRule (identified by the id attribute) associated with this BSMSelector. Any URI BSMFilterCode E3 NM/ 0..1 is used to specify the code of this BSMSelector. 23 201108653 f TM contains the following attributes: type serviceProviderCode corporateCode serviceProviderName The nonSmartCardCode contains the following elements: NetworkCode3GPP NetworkCode3GPP2 Note: At most NetworkCode3GPP or NetworkCode3GPP2 will be present. Implementations in the XML Schema should use &lt;choice&gt;. ipAddress A NM/ TM 1 Destination IP address string of the destination delivery session Port A NM/ TM 1 Purpose of the destination delivery session 埠 '&quot;Unsigned short character srcIpAddress A NM/ TM 0..1 Source IP of the delivery session If the address applies a source-specific multicast scheme in the transmission, then the "srcIpAddress" attribute will have its IP address found in the IP packet belonging to the stream of interest. In the absence of this attribute, there will be only one source IP address from which the file delivery session originates, which is defined by the combination of the given destination IP address, 埠 and transport session ID. String Type A NM/ TM 1 Type of bsmFilterCode. 1 BSMCode (Smart Card Code) This BSMCode uses 2 BSMCode (non-smart card code) when it is determined based on the country code of the (U)SIM/(R-)UIM/CSIM: BSMCode uses other values to reserve if it is determined based on the country and vendor code in the terminal. Unsigned byte Transmission SessionID A NM/ TM 1 This is the transport session for the session at the ALC/LCT level. Transmission Session Identifier (TSI) '------ Unsigned short character hasFDT A NO/ TM 0..1 If FDT is transmitted in the delivery session of the delivery service pilot segment, this attribute will be set It is "true". Otherwise this property will be set to &quot;false." The default value for this property is "true". --^- Buer 24 201108653 j^nyupif

妄This element is slaved H', then the FEC parameters associated with the transport object passing the SGDU in the transport session will be represented using EXT_FTI [RFC 3926]. The optional compression of the SGDU will be represented using EXT_CENC [RFC 3926]. Note that EXT-CENC was originally defined in [RFC 3926] to indicate the programming of the FDT, but is assigned to different uses in this specification for the specific case of direct use of ALC for SGDU delivery. serviceProvider Code A NO/ TM 0..1 The service provider code specified as [3GPP TS 22.022] or [3GPP2 C.S0068-0]. Applicable only for "type" = =1 unsigned byte corporateCode A NO/ TM 0..1 The company code specified by [3GPP TS 22.022] or [3GPP2 C.S0068-0]. The unsigned byte serviceProvider Name A NO/ TM 0..1 is applied only when "type" = = 1 such as [3GPP TS 31.102], [3GPP2 C.S0023-C] or [3GPP2 C.S0065-0] The specified Service Provider Name (SPN) » Applies to the string nonSmartCard Code A NO/ TM 0..1 only when Type ==2, BSMFilterCode value string NetworkCode3 GPP E4 NO/ TM 0..1 An IMSI-based network, network subset, or SIM/USIM program as specified by [3GPP TS 22.022]. Applicable only when "type" = =1, with the following attributes: -mobileCountryCode -mobileN etworkCode -networkSubsetCode -networkSubsetCodeRangeStart -networkSubsetCodeRangeEnd -codeRangeStart -codeRangeEnd Alternative AccessURL E2 NM/ TM 0..N Announced for fetching the mother through the interactive channel ( Parent) An alternate URL for the service guide fragment declared in the DescriptorEntry element. In addition, fragments that are not declared in the parent DescriptorEntry may also be available. The terminal may check the availability of the undeclared segment by any URI 25 201108653 f -- . , -pif issuing a non-specific service guidance request for AitemativeAccessURL as specified in 5.4.3.2 of this document. If there are multiple instances of the indicated AitemativeAccessURL, the terminal will randomly select one of them to use. Note: The purpose of this element is specified in 5.4.1.5.4 of this document. ~~---~~i mobileCountry Code A NO/ TM 0..1 The country code (3 digits) as specified in [3GPP TS 22.022]. 3 digit string mobileNetwork Code A NO/ TM 0..1 i [3GPP TS 23.003] specified mobile network code (2-3 digits). 2-3 digits of the string networkSubset Code A NO/ TM 0..1 As specified in [3GPP TS 22.022], the network subset program (2 digits). 2 digit string networkSubset CodeRangeStart A NO/ TM 0..1 Instead of providing an explicit code in the attribute networkSubsetCode, the network can instead provide a range of code. In this case, the network will provide the maximum code in the minimum code * attribute networkSubsetCodeRangeEnd that will cause the terminal to accept this attribute, and will not instantiate the attribute networkSubsetCode » The terminal will have all the code values between the minimum and maximum code. Interpreted as a value to be accepted. ~--- 2 digit string ServiceGuide DeliveryUnit E2 NM/ TM 1..N fragment group contains the following attributes: transportObjectID, versionIDLength, contentLocation, validFrom, validTo contains the following elements: Fragment Table 2 describes the elements that make up the SGDD fragment 301 and Attributes. SGDD 301 can be extensible markup language (extensible Markup 26 201108653.,

Lan Xing's 6' XML) outline of the silk. Table 2 is divided into sections for money, and individual sections describe the corresponding items. Actual = 疋 疋 疋 提供 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 疋 SG 疋 疋 疋 疋 疋 疋)) to provide. The SGDD 3.1 transmitted on the SG announcement channel 300 contains a description entry 302. The description entry 302 contains the transfer information about the SGDU 312 carrying the clip information, and the terminal 105 checks the transfer information of the SGDU 312 by means of the description entry 3〇2. As shown in Table 2, the description entry 3〇2 contains Gr〇upingCriteria”, “ServiceGuideDeliveryUnit”, Transport” and “AlteraativeAccessURI”. The channel information related to the transmission is provided by "Transport" or "AlternativeAccessURI", and the actual value of the corresponding channel is provided by ServiceGuideDeliveryUnit". And the 'upper group information about SGDU 312 such as "Service" and "Genre" may be "GroupingCriteria" The terminal 105 can receive all SGDUs 312 according to the corresponding group information and present all SGDUs 312 to the user. Once the transmission information has been verified, the terminal 105 accesses all the transmissions obtained from the SGDD 301 on the SG delivery channel 310. Channel to receive the actual SGDU 312. The SG delivery channel 310 can be identified by using "GroupingCriteria" » In the case of time grouping, available such as hourly SG channel 27

201108653 f w w ^ vf b/lX (Hourly SG Channel) 311 and the daily SG channel and the like transmit the SGDU based on the transmission channel. Between the squad, therefore, the terminal 105 can selectively access the channel and all the SGDUs present on the connected channel. Once all SGDUs have been completely received on the SG delivery channel ^, the terminal 105 checks all SG segments 32 载 carried by the SGDU received on the SG transmission channel (21, 212, 213, 22, 222 in Fig. 2) , 223, 23, 232, 241, and 251), and the SG segments are combined to display the actual service guide on the screen. In an embodiment of the invention, all service guide segments can be output with the RMS template. A description of an RMS template based on a service guide provisioning method according to an embodiment of the present invention is described below. RMS is an acronym that stands for "rich media solutions," which is defined in the OMABCAST standard to fully express rich media technologies. If the RMS is directly applied to the service guide segment containing the service guide information to display the service guide, the legacy BCAST terminal does not interpret or process the newly introduced service guide due to lack of compatibility. To address compatibility issues, the RMS template is configured such that the RMS-enabled terminal uses the RMS template to display the service guide, while the legacy terminal displays the service guide in its own display format. Information about the RMS template (hereafter referred to as RMS information) is transmitted on the SGDD. In the first embodiment of the present invention, in addition to the information shown in Table 2, the SGDD also includes the RMS information as shown in Fig. 7 and Table 3a. Table 3a depicts RMS information in accordance with a first embodiment of the present invention. 28 201108653 jj^fvupif Table 3a Name Type Type Cardinality Description RMS El NO/TO 1 The entry in the service-directed delivery descriptor. Indicates the existence of a rich media solution template file for SG. Contains the following elements: RMSTemplate RMSTemplate E2 NO/TM 1..n Used to retrieve access details for rich media solution template files. Contains the following elements: ScreenSize contains the following attributes: type version Type A NM/TM 1 RMS used to create the service guide template file. Permitted values are: 0—W3C SVG Rarely 1—OMARME 2—MPEG LASeR 3—3GPP DIMS 4—127 Reserved for future use 128-255 reserved for exclusive use Version A NM/TM 1 for creating service guides The RMS version of the template. ScreenSize E3 NM/TM l..n provides the screen size to allow the terminal to correctly capture the RMS template for the terminal. Contains the following elements: Transport AltemativeURL contains the following attributes: value compression Value A NM/TM 1 Minimum screen resolution required to reproduce the RMS template. The allowed values are: (Width * Height) 0 - Applicable to all screens 1 - 320 * 240 2 - 240 * 320 3 - 480 * 320 4 - 320 * 480 5 - 640 * 480 6480 * 640 7 - 800 * 480 8— 480 * 800 29 201108653 f 9-127 Reserved for future use 128 - 255 reserved for exclusive use A NM/TM 1 compression algorithm for compressing RMS templates. The allowed values are: 0 - Empty 1 - Gzip 2 - BIM 3 - 127 Reserved for future use 128 - 255 Reserved for exclusive use Transport E4 NM/TM 1 Pointer to the delivery session that passes the RMS template. Contains the following attributes: ipAddress port srcIpAddress transmissionSessionID hasFDT transmissionObjectID contentLo cation ipAddress A NM/TM 1 Destination IP address of the destination delivery session Port A NM/TM 1 Purpose of the destination delivery session 埠srcIpAddress A NM/TM 0..1 Delivery session Source IP Address In the case where a source-specific multicast scheme is applied in the transmission, the "srcIpAddress" attribute will have its IP address found in the IP packet belonging to the IP stream of interest as its value. In the absence of this attribute, there will be only one source IP address from which the file delivery session originates, which is defined by the combination of the given destination IP address, port and transport session ID. transmissionSessionl DA NM/TM 1 This is the Transport Session Identifier (TSI) for the ALC/LCT level session hasFDT A NO/TM 0..1 If FDT is transmitted during the transfer session that passes the RMS template, this property will be set to "true". Otherwise this property will be set to "false". The default value for this property is true. If this element is set to "false", then (1) the FEC parameters associated with the transport object passing the SGDU in the transport session will be represented using EXT_FTI [RFC 3926], and (2) the optional compression of the SGDU will use EXT_CENC [RFC 3926] to indicate. Note that EXT_CENC was originally defined in [RFC 3926] for the encoding of FDT, but in this specification 30 201108653. jonyvpif is assigned to different uses for the specific case of SGDU delivery directly using ALC. transmissionObjectID A The transport object id of the NMTM 1 RMS template. If hasFDT is assigned a true value, the value of transportObjeetlD will match the value of the TOI paired with Content-Location in the FDT instance. The Content-Location has the value of the contentLocation attribute below as its value. contentLocation A NM/TM 0..1 Location of RMS Template" which corresponds to the Content-Location attribute in FDT. This attribute will be exemplified if and only if the attribute hasFDT is instantiated. AltemativeURL E4 NM/TM 0..1 declares an alternate URL for extracting the RMS template declared in the parent RMSTemplate element via the interactive channel. In Table 3a, the data type block as described with reference to Table 1 is omitted. Referring to Table 3a, the rms information according to an embodiment of the present invention contains information about an RMS template flag indicating whether an RMS template exists, information about an RMS template, information about requirements for executing an RMS template, and about an RMS template. Information transmitted. RMS information includes such things as RMS, RMSTemplete, Type, Version, ScreenSize, Value, Compression, Transport, IpAddress ' port ' srcIPAddress ' TransmissionsessionID ' hasFDT, TransmissionObjectlD, contentLocation and

Elements and attributes such as AlternativeURL. The RMS is a higher element indicating whether the rms template used to display the service guide exists. The RMSTemplate is an element that indicates at least one RMS technology that can be used with the RMS template.

Type is the 31 201108653pif attribute indicating the rms used to create the service guide template file.

Version is an attribute indicating the version of the RMS used to create the service guide template. The value of the Type attribute "W3C" in Table 3a includes SVG, SVB Basic, SVG actions, etc. derived from Scalable Vector Graphics (SVG).

ScreenSize is an element used to provide the screen size to allow the terminal to correctly retrieve the RMS template for the terminal.

Value is an attribute indicating the minimum screen resolution required to reproduce the RMS template. Although the value of this attribute is expressed in "width * height" in Table 3a, the value can also be determined by pixel resolution, diagonal length of the screen, or such as the common intermediate format / quarter intermediate format (Common Intermediate Format) /Quarter Common Intermediate Format » CIF/QCIF) is expressed in a standardized format.

Compression indicates whether the RMS is compressed, and if compressed, indicates the attributes of the compression algorithm used to compress the RMS template.

Transport is an element that indicates an indicator that points to a delivery session that delivers an RMS template.

The IpAddress is an attribute for providing information on the destination address of the target delivery session, and the Port is an attribute for providing information about the destination of the target delivery session. srcIpAddress is an attribute used to provide information about the source IP address of the delivery session (i.e., the IP address required for the source specific multicast).

TransmissionsessionID is an attribute indicating the session's transport session identifier 32 201108653 334yupif (TSI). hasFDT is an attribute used to indicate whether FDT is transmitting in a delivery session that delivers an RMS template. If this attribute is set to "true", the terminal machine 105 receives the RMS template by using the contentLocation attribute to indicate the file name of the RMS template.

The TransmissionObjectID is an attribute indicating that the transport object of the RMS template is still.

The AlternativeURL is an element for providing information to be used when transmitting an RMS template via a one-to-one interactive channel. According to an embodiment of the invention, the RMS information is transmitted on the SGDD and the terminal uses the RMS information to receive the RMS template. As described with reference to Figures 2, 3 and 7, the terminal receives the service guide (service guide segment) and uses the RMS template to output the received service guide. In the second embodiment of the present invention, in addition to the information shown in Table 2, the SGDD also includes the RMS information as shown in FIG. 7 and Table 3b. Table 3b depicts RMS information in accordance with a second embodiment of the present invention. The rms information represented by Table 3b is defined to support the case where multiple BCAST Subscription Management (BSM) shares the SGDD. Table 3b Name Type Category Cardinality Description The ServiceGuideDeli very E Service Guided Delivery Descriptor Descriptor contains the following attributes: id version contains the following elements: NotificationReception 33 pif 201108653 BSMList DescriptorEntry TerminalCapability Id A NM/TM 0..1 SGDD in a specific SG The unique identifier will be instantiated if the SGDD is passed via the broadcast channel. Version A NM/TM 0..1 ^GDD version. As soon as a newer version is received, the newer version overrides the older version. This attribute will be instantiated if SGDD is passed via the broadcast channel. NotificationReception El NO/TO 0..1 Used to receive information for general notification messages. In the case of delivery via a broadcast channel, IPBroadcastDelivery specifies the address information used to receive the notification message. In the case of delivery via an interactive channel, PollURL specifies the address information for the polling notification, and "PollPeriod" specifies the associated polling period. When the notification message resource pointed to by this element provides a notification message for the service delivery guidance update, their notification message will be related to the currently initiated service guidance. If this element is present, at least one of the elements "IPBroadcastDelivery" or "PollURL" will exist. This element will be supported by the network when the network supports notifications. Similarly, this element will be supported by the terminal when the terminal supports the notification function. Contains the following elements: IPBroadcastDelivery PollURL PollPeriod IPBroadcastDelivery E2 NM/TM 0..1 Provides an IP multicast address and nickname for receiving notification messages via the broadcast channel. Contains the following attributes: port address Port A NM/TM 1 The general notification message conveys the UDP destination nickname; it is passed through the broadcast channel. Address A NM/TM 1 General notification message delivery IP multicast address; delivered via broadcast channel. 34 201108653.

PollURL E2 NM/TM 0..N The terminal can poll the URL via which the general notification message is sent via the interactive channel. If there are multiple instances of the indicated "PollURL", the terminal will balance the polling request within the "PollURL" set. In addition, after a given URL has been randomly selected at a given time, the terminal will temporarily use the URL to benefit from the cache management information as specified in HTTP 1.1 [RFC 2616] because it is remembered that this information belongs to a The scope of the given URL. PollPeriod E2 NO/TM 0..1 When polling this notification message, NTC is expected to poll every "PollPeriod" seconds. When this attribute is instantiated, any of the HTTP 1.1 [RFC2616] cache mechanisms will not conflict with the fact that NTC expects a new set of notification messages per "PollPeriod" value. The unit of this attribute is seconds. BSMList El NM/TM 0..1 declares a BSM selector that can be used in the GroupingCriteria section defined below. Contains the following elements: BSMSelector BSMSelector E2 NM/TM 1..N Specifies that the BSM associated with the fragment in this Service Pilot Delivery Unit allows the terminal to determine this SGDD DescriptorEntry in the SGDU published in various DescriptorEntry in various SGDDs. Whether the SGDD is associated with a terminal affiliated BSM. The affiliated BSM of the terminal is represented in the terminal as a management object having the identifier &lt;X&gt;/ BSMSelector/ BSMFilterCodeor, as by [3GPP TS 22.022], [3GPP2 C.S0068-0], [3GPPTS 31.102], [3GPP2 The code on the smart card defined by C.S0023-C] or [3GPP2 C.S0065-0]. To interpret BSMSelector in SGDD, the following sections will apply: • If any of the BSMFilterCodes present in this element are associated with any of the &lt;X&gt;BSMSelector//BSMFilterCode entries in the terminal or with the code on the smart card Matching, that is, all the instantiation properties of BSMFilterCode 35 201108653. have the matching instantiation attribute under the <X>/BSMFilterCode or the matching code on the smart card, the terminal can process, reproduce, and without restriction. Interpret and dispose of the fragment. Note that a match is considered when the instantiated property under BMSFilterCode matches a subset of the instantiation properties of &lt;X&gt;/BSMSelector/BSMFilterCode or matches a subset of the code on the smart card. However, when the BSMFilterCode is represented as a superset of the attributes of the <X>/BSMSelector/BSMFilterCode or a superset of the code on the smart card, it is not considered a match because not all of the instantiation attributes under the BSMFilterCode are associated with &lt;X&gt; The example attribute of /BSMSelector/BSMFilterCode or the code on the smart card matches. If the BSMFilterCode present in this element does not match any of the <X&gt;/BSMSelector/BSMFilterCode entries in the terminal, that is, not all of the instantiated attributes of the BSMFilterCode have a match under &lt;X&gt;/BSMSelector/BSMFilterCode By instantiating the matching code on the attribute or smart card, the terminal can reproduce, interpret, and dispose of the fragment based on the RoamingRule (identified by the attribute id) associated with this BSMSelector. In the case where the terminal does not have such a Roaming Rule, the terminal does not reproduce the clip to the user. The terminal can obtain the _ rule by sending a RoamingRuleRequest to the address indicated by the attribute roamingRuleRequestAddress. In the case where the terminal does not have a code on the &lt;X&gt;/BSMSelector/BSMFilterCode entry or smart card, in order to interpret the BSMSelector in the SGDD, the following sections will apply: The terminal can be based on the RoamingRule associated with this BSMSelector ( The segment is reproduced, interpreted, and processed by the attribute id). In the case where the terminal does not have such a RoamingRule, the terminal does not reproduce the clip to the user. The terminal can obtain the rule by sending a RoamingRuleRequest to the address indicated by the attribute roamingRuleRequestAddress 36 201108653. Note: The RoamingRuleRequest message and associated roaming method are specified in [BCAST10-Services]. Contains the following attributes: id roamingRuleRequestAddress contains the following elements: BSMFilterCode Name RoamingRule NotificationReception RMS ' Id A NM/TM 1 BSMSelector identifier. This id is unique within the network. roamingRuleRequest Address A NO/TO 0..1 The terminal can send a RoamingRuleRequest to it to request the address of the RoamingRule (identified by the id attribute) associated with this BSMSelector. This property will be supported by terminals that support broadcast roaming. BSMFilterCode E3 NM/TM 0..1 is used to specify the code of this BSMSelector. Contains the following attributes: type serviceProviderCode corporateCode serviceProviderName The nonSmartCardCode contains the following elements: NetworkCode3GPP NetworkCode3GPP2 Note: At most the implementation of "NetworkCode3GPP" or "NetworkCode3GPP2" XML Profile should use &lt;choice&gt;. Type A NM/TM 1 Type of bsmFilterCode. 1 A BSMCode (Smart Card Program Code) This BSMCode is used when the decision is made based on the country code of the (U)SIM/(R-)UIM/CSIM. 37 201108653 fi-BSMCode (non-smart card program) Code): This BSMCode is reserved with other values if it is determined based on the country and the operator in the terminal. serviceProviderCode A NO/TM 0..1 ^ [3GPP TS 22.022] or [3GPP2 C.S0068-0] specified service provider code. CoiporateCode A NO/TM 0..1 is applied only when "type" = =1. The company code specified by [3GPP TS 22.022] or [3GPP2 C.S0068-0]. ServiceProviderName A NO/TM 0..1 is only applicable when "type" = =1. The service provider name specified by [3GPP TS 31.102], [3GPP2 C.S0023-C] or [3GPP2 C.S0065-0] SPN). NonSmartCardCode A NO/TM 0..1 only when Type ===1 When the type == 2, the value of BSMFilterCode NetworkCode3GPP E4 NO/TM 0..1 is based on imSI based on [3GPP TS 22.022] Network, network subset or SIM/USIM code. Applicable only when "Type" ==1. Contains the following attributes: mobileCountryCode mobileN etworkCode networkSubsetCode networkSubsetCodeRangeStart networkSubsetCodeRangeEnd codeRangeStart codeRangeEnd mobileCountryCode A NO/TM 0..1 The action country program (3 digits) as specified in [3GPP TS 22.022]. mobileNetworkCode A NO/TM 0..1 The mobile network code (2-3 digits) as specified in [3GPP TS 23.003]. networkSubsetCode A NO/TM 0..1 The network subset code (2 digits) as specified in [3GPP TS 22.022]. networkSubsetCode RangeStart A NO/TM 0..1 Instead of providing explicit code in the attribute "networkSubsetCode", the network can instead provide a continuous range of code. In this case, the network will provide the minimum code that allows the terminal to accept this attribute, • The attribute "networkSubsetCodeHange 38 201108653.

The largest code in End", and - • does not instantiate the attribute "networkSubset Code". The terminal will interpret all code values between the minimum and maximum code to be accepted. networkSubsetCode RangeEnd A NO/TM 0 ..1 This attribute represents the end of the range of the network subset code specified above. codeRangeStart A NO/TM 0..1 This attribute table does not come from the lowest program of one or more consecutive ranges of code. The code value, which is used by the BCAST terminal to determine if there is a match of the area SIM/USIM code. The terminal will accept all programs between the lowest * and highest code values (and containing the lowest and most program values). Code value for matching area SIM/USIM program. codeRangeEnd A NO/TM 0..1 This attribute table does not consider the BCAST terminal to be the highest code value valid for the matching area SIM/USIM code, as above The network code3 GPP2 E4 NO/TM 0..1 is based on the IMSI and/or NAI network, or the (R-)UIM/CSIM code specified by [3GPP2 C.S0068-0]. Only in "type" ” = =1 applies. Contains the following attributes: mobileCountryCode mobileNetworkCode iRMBasedMIN hRPDRealm ruimCSIMCodeRangeStart ruimCSIMCodeRangeEnd mobileCountryCode A NO/TM 0..1 [3GPP2 C.S0068-0] The action country code specified for network type i (3 number bamboo, mobileNetworkCode A NO/TM 0..1 [3GPP2 C.S0068-0] for the network to prepare for the specified mobile network code (2-3 mobile office, iRMBasedMIN A NO/TM 0..1 [3GPP2 C.S0068-0] for the specified The first 4 of the IRM-based MIN: if hRPDRealm A NO/TM 0..1 The REALM code of the relevant HRPD network specified by [3GPP2 C.S0068-0] ruimCSIMCodeRange Start A NO/TM 0..1 The (R-) UIM or CSIM code specified in [3GPP2 C.S0023-C], [3GPP2 C.S0065-0] or [3GPP2 C.S0068-0]. This attribute represents the lowest code value from a continuous range of 39 201108653 f code, which is used by the BCAST terminal to determine if there is a match with the area (R-) UIM/CSIM code. The terminal will accept all code values between the lowest and highest code values (and the lowest and highest code values) for the matching area (R-) UIM/CSIM code. ruimCSIMCodeRange End A NO/TM 0..1 (R-) UIM or CSIM code as specified in [3GPP2 C.S0023-C], [3GPP2 C.S0065-0] or [3GPP2 C.S0068-0]. This attribute represents the lowest code value from one or more code ranges in a contiguous range that is used by the BCAST terminal to determine if there is a match with the area (R-) UIM/CSIM code. The terminal will accept all code values between the lowest and highest code values (and the lowest and highest code values) for the matching area (R-) UIM/CSIM code. Name E3 NM/TM 1..N The user-readable name for BSM_Selector may be available in multiple languages. The language is expressed in this element using the built-in XML attribute xml:lang. This element can be used to provide information to the user, so he can choose the BSMSelector that the terminal must use. RoamingRule E3 NO/TO 0..N Specifies the roaming rules associated with BSMSelector. The roaming rules specified by this element are not specific to any Home BSM. This roaming rule can be interpreted as being common to any home BSM, but the validity of roaming rules for a particular pair of visited BSMs (as announced by the parent BSMSelector element) and the home BSM cannot be guaranteed. Contains the following attributes: allowAll denyAll Contains the following elements: TimeFrame AllowPurchaseltem AllowPurchaseData AllowService AllowContent DenyPurchaseltem DenyPurchaseData 40 201108653.

This element is supported by DenyService DenyContent terminals that support broadcast roaming. The terminal will interpret the roaming rules for each segment so that the “deny” rule can take precedence if both the “allow” rule and the “deny” rule apply. allowAll A 0 0..1 When set to "true", allows the terminal to use the rules of all fragments associated with the BSMFilterCode associated with these RoamingRules. The default value for this property is False. This attribute does not exist if the attribute "denyAll" exists. denyAll A 0 0..1 When set to "true", the terminal is prohibited from using the rules of any fragment associated with the BSMFilterCode associated with such RoamingRule. The default value for this property is False. If the attribute "allowAll" exists, this attribute does not exist. TimeFrame E4 0 0..N The rule used to define the time range for this RoamingRule. Contains the following attributes: startTime endTime startTime A 0 0..1 The beginning of the time range. If not given, it is assumed that the time range has started at some time in the past. This field is expressed as the 32-bit integer part of the NTP timestamp. endTime A 0 0..1 The end of the time range. If not given, it is assumed that the time range ends at some time in the future. This block is expressed as the 32-bit integer part of the NTP timestamp. Allow Purchaseltem E4 0 0..1 Allows the terminal to use the rules of the listed Purchaseltem. If one of the "allowAll" or "denyAll" attributes exists, this element will not exist. Contains the following elements: Id 41 201108653

Pif

Id E5 M 1..N This element contains a value indicating the GlobalPurchaseltemID that is allowed to be interpreted, reproduced, and retrieved. Allow PurchaseData E4 0 0..1 Allows the terminal to use the rules of the listed PurchaseData. This attribute is "false". This attribute does not exist if the "denyAll" attribute is present. Id E5 M 1..N This element contains a value indicating the PurchaseData fragment ID that is allowed to be interpreted, reproduced, and retrieved. 0 Allow Service E4 0 0..1 Allows the terminal to use the rule corresponding to the fragment of the listed globalService1D. If one of the "allowAll" or "denyAll" attributes exists, this element will not exist. Contains the following elements: Id Id E5 M 1..N This element contains a value that represents globalServicelD. Allows interpretation, rendering, and access to fragments associated with this globalServicelD. Deny Purchaseltem E4 0 0..1 Used to reject the rules of the terminal using the listed Purchaseltem. If one of the "allowAll" or "denyAll" attributes exists, this element will not exist. Contains the following elements: Id Id E5 M 1..N This element contains the value of globalPurchaseltemlD indicating that it is refused to be interpreted, reproduced, and retrieved. Deny PurchaseData E4 0 0..1 Rejects the rules for the terminal to use the listed PurchaseData item. If one of the "allowAll" or "denyAll" attributes exists, this element will not exist. Contains the following elements: Id Id E5 M 1..N This element contains a value indicating the PurchaseData fragment ID that is rejected for interpretation, reproduction, and retrieval. Deny Service E4 0 0..1 Rejects the terminal to use the rules corresponding to the fragments of the listed globalServicelD. If one of the "allowAll" or "denyAll" attributes exists, this element will not exist. Contains the following elements: Id Id E5 M 1..N This element contains a value that represents globalServicelD. Refusal to interpret, reproduce, and access the fragment associated with this 42 201108653 f globalServicelD. Deny Content E4 0 0..1 Rejects the terminal to use the rule corresponding to the fragment of the globalContentID. This element does not exist if one of the "allowAU" or "denyAll" attributes exists. Contains the following elements: Id Id E5 M 1..N This element contains a value that represents the globalContentID. Refuse to interpret, reproduce, and access fragments associated with this globalContentID. NotificationReception E3 NO/TM 0..1 Receive information for the notification message dedicated to the parent BSMSelector. The terminal will define the scope of the information provided in the notification message delivered to the parent BSMSelector via the sub-system "IPBroadcastDelivery" or "PollURL". In the case of delivery via a broadcast channel, IPBroadcastDelivery specifies the address information used to receive the notification message. In the case of delivery via an interactive channel, PollURL specifies the address information for polling notifications and "PollPeriod" specifies the associated polling period. If this element exists, at least one of the elements ''IPBroadcastDelivery' or 'PollURL' will exist. Contains the following elements: IPBroadcastDelivery PollURL PollPeriod IPBroadcastDelivery E4 NM/TM 0..1 蜒 is used to receive notification messages via broadcast channels IP multicast address and nickname. Contains the following attributes: port address port A NM/TM 1 BSM dedicated notification message is passed UDP destination nickname; delivered via broadcast channel. address A NM/TM 1 bSM dedicated notification message delivery π&gt; Multicast address; via broadcast channel. PollURL E4 NM/TM 0..N The terminal can poll the URL via which the notification message is sent via the interactive channel. 43 201108653 If there are multiple instances of the represented "PollURL" , the terminal will balance the polling request within the "PollURL" collection. Furthermore, after a given URL has been randomly selected at a given time, the terminal should temporarily use the URL to benefit from the HTTP 1.1 [RFC 2616] The specified cache management information, because it is remembered that this information belongs to a given URL. PollPeriod E4 NO/TM 0..1 in polling When a service-specific notification message is received, NTC is expected to poll every "PollPeriod" seconds. When this attribute is instantiated, any cache mechanism of HTTP 1.1 [RFC 2616] should not request a new notification with the expected NTC per "PollPeriod" value. The factual conflict of the message collection. The unit of this attribute is seconds. RMS E3 NO/TO 0..1 indicates the existence of the rich media solution template file for SG. Contains the following elements: RMSTemplate RMSTemplate E4 NO/TM l..n Access details for extracting rich media solution template files. Contains the following elements: Criteria Update Capabilities Transport AltemativeURL GlobalContentld Criteria E5 NO/TO 0..N The criteria required to declare receipt of this template contain the following attributes: templateVersion attributeNaxne attributeValue templateVersion A version of the NO/TM 1 template. If the template version is newer than the version stored on the terminal, the terminal is suitable for receiving the RMS template. attributeName A NO/NM 1 Profile attribute name attributeValue A NO/TM 1 Profile attribute value Capabilities E5 NO/TM 1 contains the following attributes: type version 44 201108653. Contains the following elements: MIMEType Complexity type A NM/TM 1 Indicates RM content Type. The allowed values are: 0 - according to MIME type 1 - W3C SVG is rarely 2 - OMARME 3 - MPEG LASeR 4 - 3GPP DIMS 5 - 127 reserved for future use 128-255 for exclusive use while retaining version A NM/TM 1 Defines the version MIMEType E6 NM/TM 0..N associated with the type of MME media type for rich media content. Contains the following attributes: Codec codec A NM/TM 0..1 Coding parameters for the associated MIME media type. If the file's MME type definition specifies a mandatory parameter, then these parameters must be included in this string. Optional parameters containing information that can be used to determine if the terminal is available for use should be included in the string. An example of a parameter defined for video/rich media + xml is defined in clause 7 of the 3GPP DIMS specification. Complexity E6 NM/TM 1 The richness that the rich media engine must address. Contains the following attributes: profile sceneUpdateCommands screenOrientation Contains the following elements: Animations EmbeddedMediaElements DOMnodes Scripting Compression profile A NO/TO 0..1 Defines the RMS profile/level instance: For DIMS: Action setting level 10 For LASeR: 2006 amdl Note :profile is conditional on the "type" and "version" attributes. sceneUpdateComman A NO/TM 1 Indicates whether rich media content needs to be processed. 45 201108653.^ vpll

Ds updates the command to reproduce the content. Preset: False screenOrientation A NO/TM 1 Indicates whether the rich media scene requires scene orientation management Preset: False Animations E6 NO/TM 1 The number of dynamics in the rich media scene. Contains the following attributes: Maximum maximum A NM/TM 0..1 The maximum number of animations in a rich media scene. EmbeddedMediaElem ents E6 NM/TM 1 The number of media elements (ie, video and audio) embedded in a rich media scene. Contains the following attributes: embeddedVideo embeddedAudio embeddedVideo A NM/TM 0..1 The number of embedded video elements running simultaneously in a rich media scene. embeddedAudio A NM/TM 0..1 The number of embedded audio elements that are running simultaneously in a rich media scene. DOMNodes E6 NO/TM 1 The number of DOM nodes required to reproduce rich media content. Contains the following attributes: Maximum maximum A NM/TM 1 The maximum number of active DOM nodes in a rich media scene at any given time. Scripting E6 NO/TM 1 Indicates whether the rich media scene needs to process a script (for example, ECMAScript) to reproduce the content. Contains the following attributes: MIMEType MIMEType A NM/TM 0..1 Indicates the MIME type of the script used within rich media content. If it does not exist, the indication does not contain any scripts. Compression E6 NO/TM 1 Indicates whether the rich media scene passed is compressed/encoded. Contains the following attributes: contentEncoding content Encoding A NM/TM 1 Scheme for encoding/compressing rich media content 0 - Empty 1 - XML 2 - Gzip 3 - LASeR 4 - BiM 46 201108653J^4yupif 5-127 for future use Reserved ~~ 128-255 is reserved for exclusive use: the default value is 0. Transport E5 NM/TM 0..1 points to the transfer ^^· tag that passes the RMS template. Contains the following attributes: ipAddress port srcIpAddress transmissionSessionID hasFDT transmissionObj ectID contentLo cation ipAddress A NM/TM 1 destination IP address of the destination delivery session — Port A NM/TM 1 The purpose of the destination delivery session. srcIpAddress A NM/TM 0..1 Passing the source IP address of the session In the case of applying a source-specific multicast scheme in the transport, the "srcIpAddress" attribute will have the positive found in the π» packet belonging to the IP stream of interest. The address is taken as its value. In the absence of this attribute, there will be only one source 位»Address' The file delivery session is derived from this address and is defined by the combination of the given destination IP address, 埠 and transport session ID. transmissionSessionl DA NM/TM 1 This is the transmission and identifier (TSI) of the ALC/LCT level session ° hasFDT A NO/TM 0..1 If the FDT is passed in the RMS template, this attribute will be set to " true". Otherwise this property will be set to "false". This property has a default value of "true". If this element is set to "false", then (1) the FEC parameters associated with the transport object passing the SGDU in the transport session will be represented using EXT FTI [RFC 3926] - (2) optional compression of the SGDU will be used. Also 1'_€ ugly &gt; 10: [1〇^3926] to indicate. Note that EXT_CENC was originally defined in [rfc 3926] to represent the encoding of the FDT, but is assigned a different purpose in this specification for the specific case of direct delivery using the SGDU of the ALC. transmissionObj ectID A NM/TM 1 RMS template pass is assigned the value "true", then 47 201108653 "transportObjectlD" value will match the value of the TOI paired with "Content-Location" in the FDT instance, the Content- Location has the value of the "contentLocation" attribute below as its value. contentLocation A nm/tm 0..1 Location of the RMS template. It corresponds to the "Content-Location" attribute in FDT. This attribute will be instantiated if and only if the attribute hasFDT is instantiated. AltemativeURL E5 no/tm 0..1 is declared to be used to retrieve an alternate URL for the RMS template declared in the parent "RMSTemplate" element via the interactive channel. GlobalContentld E5 NO/TM 0..1 If the RMSTemplate is instantiated as content, this element contains a value that represents the relevant GlobalContentID. DescriptorEntry &quot;El nm/tm 1..N The service guide passes the entry in the descriptor. The following attributes are included: type contains the following elements: GroupingCriteria, Transport, AltemativeAccessURL, ServiceGuideDelivervUnit Omitted The RMS information according to the second embodiment of the present invention is defined in consideration of a plurality of service providers sharing a single network. In the case of multiple service providers sharing networks, RMS information provides a rich media service guidance template for individual service providers. Referring to Table 3b, when multiple BSMs share SGDD, this information is provided by using a BSMSelector element that is a child of the BSMList element. In an embodiment of the invention, the 'BSMSelector element also contains information about whether the RMS template is present, i.e., the RMS element is included in the BSMSelector element and contains the RMSTemplate element. 48 201108653 j^^yupif The RMSTemplate element contains Criteria, Capabilities, Transport, AlternativeURL, and GlobalContentID elements. BSMSelector is an element that provides information for identifying service providers in BCAST. The BSMSelector element provides an important criterion for distinguishing the service guidance of the multiple service providers when the SGDD is shared by multiple service providers. To do this, add the RMSTemplate element as a child of BSMSelector' to support the provider-specific service guidance template. By inserting the RMS element into the SGDD, the terminal can prepare the RMS process in advance before receiving the metadata passed by the service pilot segment, and thus quickly display the service guide in a rich media format.

The Criteria element provides a filtering rule that allows RMS templates to be used only for terminals that meet certain criteria. The Criteria element is not specifically defined so that the service provider can define the various conditions required, and the Criteria element contains the template Version and attributeName and the attribute Value attribute. The template Version attribute allows the terminal to receive an RMS template that is newer than the template stored in the terminal based on time. The attributeName and attribute Value attributes can be defined by the service provider.

The Capabilities element provides a response to the monthly b-force required to display the rms template on the terminal. Since the problem may occur with a terminal that does not meet the requirements of the Capabilities element, the terminal does not receive the template. The Transport element contains the information needed by the terminal 105 to receive the RMS template via the broadcast channel. The transmission element is the same as the Transport element in Table 3a according to the first embodiment of the present invention. 49 201108653 f --.pif

The AlternativeURL element provides information about an alternate URL for extracting the RMS template via a one-to-one interactive channel.

The GlobalContentld element provides an identifier for the content fragment when the service provider wishes to provide the RMS template as content. Although the RMS template is transmitted according to the conventional BCAST file transfer method in the above method, the terminal uses the RMS template to display that the service guide may be delayed compared to the use of the Transport element contained in the SGDD. The structure of the RMS information according to the third embodiment of the present invention is described below. Fig. 7 and Table 3c describe the structure of RMS information according to the third embodiment of the present invention. The third embodiment is identical to the second embodiment in supporting SGDD sharing of a plurality of BSMs' but the RMS element is a higher element containing BSM information. Table 3c Name Type Type Cardinality Description — RMS E1 NO/TO 0..1 Indicates the existence of a rich media template template file for SG rendering. If the 'end machine has a delay in reproducing the rich media solution template, the terminal can simultaneously use its 'body's rendering engine to reproduce the SG. ' Contains the following elements: BSMSelector RMSTemplate BSMSelector E2 NM/TM 0,.1 Refers to the BSM associated with the RMSTemplate by reference to the BSMSelector structure above. Note that if this element is not instantiated, any terminal that takes a given SGDD will consider the RMSTemplate for 咐 50 50 201108653 BSM. Contains the following attributes: idRef idRef A NM/TM 1 Reference to the identifier of the BSMSelector declared in the above "BSMList". RMSTemplate E2 NO/TM 1..N is used to capture access details for rich media solution template files. Contains the following attributes: templateVersion contains the following elements: Criteria Capabilities Transport AltemativeURL GlobalContentld templateVersion A NO/TM 1 template version. If the template version is newer than the version stored on the terminal, the terminal is suitable for receiving the RMS template. Criteria E3 NO/TO 0..N The criteria required to declare receipt of this template contain the following attributes: attributeName attributeValue attributeName A NO/NM 1 Criteria attribute name attributeValue A NO/TM 1 Criteria attribute value Capabilities E3 NO/TM 1 contains the following attributes : type version contains the following elements: MIMEType Complexity type A NM/TM 1 Indicates the type of RM content. The allowed values are: 0—Depending on the MIME type 1 a W3C SVG is rarely 2—OMARME 3—MPEG LASeR 4—3GPP DIMS 5—127 retains 128-255 for exclusive use for future use while retaining version A NM/TM 1 A version associated with the type is defined. 51 201108653 MIMEType E4 NM/TM 0..N MIME media type for rich media content. Contains the following attributes: Codec codec A NM/TM 0..1 bat-decoding parameters for the associated MIME media type. If the file's MIME type definition specifies a mandatory parameter, then these parameters must be included in this string. Optional parameters that contain information that can be used to determine if the terminal is available for archival purposes should be included in the word dispute. An example of a parameter defined for video/rich media + xml is defined in clause 7 of the 3GPP DIMS specification. Complexity E4 NM/TM 1 The richness that the rich media engine must address. Contains the following attributes: profile sceneUpdateCommands screenOrientation Contains the following elements: Animations EmbeddedMediaElements DOMnodes Scripting Compression profile A NO/TO 0..1 Defines the RMS profile/level instance: For DIMS: Action setting gears 1 for LASeR: 2006 amdl Note: The profile is conditional and the "version" attribute is conditional. sceneUpdateCommands A NO/TM 1 indicates whether Fengchang Media Content is used to process the scene update command to reproduce the content. Preset: False screenOrientation A NO/TM 1 refers to the non-rich media per-admin management preset: Fake Animations K4 NO/TM 1 Rich media scene - contains the following attributes: Maximum maximum A NM/TM 0..1 Fengchang media scene The maximum number of animations in the 〇EmbeddedMediaElements E4 NM/TM 1 rich media scene, namely video and audio) Weng曰0 52 201108653. j^H-yupif

Contains the following attributes: embeddedVideo embeddedAudio embedded Video A NM/TM 0..1 The number of embedded video elements running simultaneously in a rich media scene. embeddedAudio A NM/TM 0..1 The number of embedded audio elements that are running simultaneously in a rich media scene. DOMNodes E4 NO/TM 1 The number of DOM nodes required to reproduce rich media content. Contains the following attributes: Maximum maximum A NM/TM 1 The maximum number of active DOM nodes in a rich media scene at any given time. Scripting E4 NO/TM 1 Indicates whether the rich media scene needs to process the script (for example, ECMAScript) to reproduce the content. Contains the following attributes: MIMEType MIMEType A NM/TM 0..1 Indicates the MIME type of the script used in rich media content. If it does not exist, the indication does not contain any scripts. Compression E6 NO/TM 1 Indicates whether the rich media scenes passed are compressed/encoded. Contains the following attributes: contentEncoding content Encoding A NM/TM 1 Scheme 0 for encoding/compressing rich media content - Empty 1 - XML 2 - Gzip 3 - LASeR 4 - BiM 5 - 127 Reserved for future use 128-255 Note for exclusive use: The default is 0. Transport E3 NM/TM 0..1 Pointer to the delivery session that passes the RMS template. Contains the following attributes: ipAddress port srcIpAddress transmissionSessionID 53

201108653 f •mf ^ t ^ ^iJlL hasFDT~ transmissionObjectID contentLocation ipAddress A NM/TM 1 Destination IP address of the destination delivery session. – Port A NM/TM 1 1 The purpose of the delivery session 埠 srcIpAddress A NM/TM 0..1 Source IP address of the delivery session - In the case of applying a source-specific multicast scheme in transit, the "srcIpAddress" attribute The IP address to be in the IP packet belonging to the IP stream of interest will be taken as its value. In the absence of this attribute, there will be only one source IP address from which the file delivery session originates, which is defined by the combination of the given destination IP address, port and transport session ID. transmissionSessionID A NM/TM 1 it匕 is the Transport Session Identifier (TSI) for the ALC/LCT level session hasFDT A NO/TM 0..1 If the FDT is transmitted in the delivery session passing the RMS template, this attribute will Is set to "true". Otherwise this property will be set to "false" and the default value for this property is "true". If this element is set to "false", then (1) the FEC parameters associated with the transport object passing the SGDU in the transport session will be represented using EXT_FTI [RFC 3926] (2) The optional compression of the SGDU will use EXT_CENC [RFC 3926] to express. Note that EXT_CENC was originally defined in [RFC 3926] to indicate the encoding of the FDT, but is assigned different uses in this specification for the specific case of SGDU delivery directly using ALC. transmissionObjectID A NM/TM 1 RMS template transport object ID. If "hasFDT" is assigned a true value, then the value of "transportObjectlD" will match the value of the TOI paired with "Content-Location" in the FDT instance, which has the "contentLocation" attribute below The value is taken as its value. contentLo cation A NM/TM 0..1 Location of the RMS template. It corresponds to the "Content-Location" attribute in FDT. This attribute will be instantiated if and only if the attribute "hasFDT" is instantiated. 54 201108653 J34yupif

AltemativeURL E3 NO/TM 0..1 is declared to be used to retrieve an alternate URL for the RMS template declared in the parent "RMSTemplate" element via the interactive channel. — GlobalContentld E3 NO/TM 0..1 If the RMSTemplate is instantiated as content, then this voxel contains the value of the globalContentED that is not relevant. Newly introduced in the RMS information in Table 3c, but the elements not included and described in the RMS information in Table 3b are described. The BSMSelector element contains an idRef attribute' which contains the service provider value to specify the BSM value representing the service provider. The value of the idRef attribute is used to determine whether to apply the RMS template. The RMS transmission method according to an embodiment of the present invention is described below. 4 is a flow chart illustrating a rich media enhanced service guide provisioning method in accordance with an embodiment of the present invention. Referring to Fig. 4, in step S401, BSDA 103 creates a service guide (SG) with the required service guide segment. Once the service guide has been created, the BSDA 103 creates an RMS template in step S403 for the terminal to display the service guide. At step S403, BSDA 130 selects RMS technology for creating an RMS template in W3C SVT (rare), OMA RME, MPEG LASeR, and 3GPP DIMS. In the absence of a previously created template, BSDA 103 may create a new template 'and if present' then select one of the previously created templates. Once the template has been selected or created, BSDA 103 creates an SGDD containing the RMS information in step S405. The RMS information can be provided in one of the formats described in Tables 3a, 3b, and 3c. That is, bsda1〇3 55 201108653 generates SGDD containing information about the service guide segments required to form the service guide as described in Table 2, and formatted as shown in Table 3a, Table 3b or Table 3c. RMS information. Finally, in step S407, the BSDA 103 broadcasts the SGDD, the service guide, and the RMS template so that the terminal 105 receives the SGDD, the service guide, and the RMS template. In the case where the RMS template is transmitted via the interactive channel, the BSDA 103 adds RMS information notifying the transmission of the RMS template to the SGDD via the interactive channel at step S405, and broadcasts the service guide segment at step S407, and via the interactive channel Transfer the RMS template. A procedure for a terminal to receive a service guide and an RMS template in a rich media enhanced service guide provisioning method according to an embodiment of the present invention is described below. 5 is a flow chart illustrating a procedure for handling received rich media enhanced service guidance in a rich media enhanced service guided provisioning method in accordance with an embodiment of the present invention. Referring to FIG. 5, the terminal set 105 first receives the SGDD transmitted by the BSDA 103 in step S501. At this time, the terminal terminal 1〇5 accesses the SG advertisement channel to receive the SGDD&apos; as shown in Fig. 3. As shown in Figure 3, at least one SGDD 301 is transmitted on the SG published channel 300, and the terminal set 1 接收 5 receives the SGDD whose destination is its own. Subsequently, the terminal 105 receives the SGDU whose destination is its own by referring to the SGDD in step S503, and extracts the service pilot segment from the received SGDU in step S505. The service guide fragment can be metadata. Subsequently, the terminal 105 analyzes the received 56 201108653 with yupif SGDD in step S507 to detect RMS information from the SGDD (formatted as shown in Table 3a, Table 3b or Table 3c). If the rms information has been detected at step S5, the terminal 105 determines in step S509 whether or not the RMS template contained in the RMS information is supportable. Whether the RMS template is supportable can be determined based on the RMS information described in Tables 3a, 3b, and 3c. For example, the RMS information is formatted as shown in Table 3a, and the terminal 105 refers to the Type attribute and the Version attribute contained in the RMSTemplate element to determine whether it supports the RMS template. In the case where the RMS information is formatted as shown in Table 3b, the terminal 105 refers to the Criteria element and the Capability element contained in the RMSTemplate element to determine whether the terminal 丨05 supports the RMS template. If it has been determined at step S590 that the terminal machine supports the RMS template, the terminal device receives the rms template in step S511. Here, the rms information contains information about the transmission. The transport information contains the Transport element (containing the IpAddress attribute, the P0rt attribute, the srcipAddress attribute, the transmissionSessionlD attribute, the hasFDT attribute, the contentLocation attribute, and the transmissionObjectID attribute) and the AlternativeURL element. Terminal 105 receives the RMS template with reference to these elements and attributes. Once the RMS template has been received, the terminal 105 uses the RMS template to display the service guide (service guide segment) extracted from the SGDU at step S505 in step S513. In this manner, terminal 105 can output services in a given environment of the service provider. If the RMS information is not detected at step S507 or if it is determined at step S509 that the RMS template is not supportable, the terminal device 1 再现5 reproduces the service using the rendering engine of its body in step 57 201108653 step S515. guide. The structure and operation of a terminal device supporting the rich media enhanced service guide supply method according to an embodiment of the present invention are described below. Figure 6 is a block diagram showing the configuration of a terminal set according to an embodiment of the present invention. As shown in Fig. 6, the terminal device 105 includes a receiving module 601, an RMS engine 603, and a BCAST client 605. The receiving module 601 receives the SGDD, obtains the SGDU' with reference to the SGDD, and extracts the service pilot segment from the SGDU. The receiving module 601 also obtains the RMS template by referring to the rms information contained in the SGDD. The RMS engine 603 interprets the RMS template and outputs the results to the BCAST client 605. The BCAST client 605 interprets each service guide segment and outputs the service guide using the RMS template provided by the RMS engine 603. The service guide can be provided in the form of metadata. A detailed description of the RMS engine 603 for reproducing the service guide is provided. In the embodiment of the present invention, a description is made under the assumption that the RMS engine 6〇3 is a Lightweight Application for Scene Representation ' LASeR engine. However, other rich media rendering engines can be used to implement the RMS engine 6〇3. Where the rms engine 603 (or system) is replaced by another type of rendering engine (or another system), the terminology may vary in accordance with the art of replacement, and such a situation will be apparent to those skilled in the art. In an embodiment of the invention, the RMS engine 603 pushes the received rms 58 201108653 template (i.e., the LASeR template). In the case where the LASeR template is delivered in the form of the original service content without pressing It, the decoding process is omitted. The RMS engine 603 checks the command ' in the exhausted LASeR template' and executes the command. The LASeR command expresses the scene change in a declarative manner, and includes "NewSeene, an element (command), an "Insert" element (command) for instructing the insertion of the attribute, and an instruction attribute for instructing the drawing of the new scene. The deleted "Delete" element (command). The components of the LASeR-based scene contain elements and attributes that represent the nature of the element's expressions that represent the media and graphics objects, events, and scripts of the scene in a declarative manner. The LASeR template contains information about The information contained in the service guide segment obtained from sGDu is used to display the links of the service guide and the reference information. The RMS engine 603 interprets the link and reference information of the LASeR template and is based on the interpreted information. The information contained in each service guide segment is checked. The LASeR engine 603 uses the information contained in each service guide segment to reproduce the LASeR content in a format suitable for the terminal. The LASeR engine 603 supports users of video and audio. The interface component outputs the reproduced service guide. The information provided by the service guide segment is for output Meta-data for service guidance. Description of service guidance metadata (hereinafter referred to as SG metadata). 59 201108653. Table 4 shows exemplary sg metadata according to an embodiment of the present invention. Table 4 &lt;Content id=&quot ; um:bbc:2891&quot;version=&quot;5&quot;&gt;&lt;Name&gt;Spendaholics&lt;/Name&gt;&lt;Genre&gt;NON-FICTION&lt;/Genre&gt; <//Content> &lt;PurchaseTable&gt; <Purchase ...&gt;&lt; ServiceBundleRef IDRef=&quot;ServiceBundleid_A&quot;/&gt;&lt;MediaTitle&gt;&lt;Mpeg7:TitleImage&gt;&lt;mpeg7:MediaUri&gt;EasterTitle.jpg&lt;/mpeg7:MediaUri&gt;&lt;/Mpeg7:TitleImage&gt;&lt;/MediaTitle&gt;&lt;/Purchase&gt;&lt;/PurchaseTable&gt; Table 4 is a structured XML data format that expresses the SG metadata that will be displayed on the LASeR template. As mentioned earlier, the SG metadata will be displayed to the user via the RMS template. An RMS template in accordance with an embodiment of the present invention is shown. Table 5 <text id=&quot;Genre&quot;...&gt;&lt;trefxlink:href=&quot;ESGxml# xmlns(ESGMain/ESG/Content [@id=lum:bbc:2891 ']/Genre/text() ) H /&gt;&lt;/text&gt; <image id=&quot;ServiceBundlelmage&quot;xlink:href=&quot;ESG.xml# xmlns(ESGMain/ESG/PurchaseTable/Purchase/MediaTitle/ mpeg7 :TitleImage/ mpeg7:MediaUri/text〇 )&quot; ... /&gt; 60 201108653 Table 5 shows the information provided by the service guide segment (ie, the SG meta data in Table 4), which is expressed in the LASeR template as an RMS template. Here, the 'LASeR template contains an image identified by the attribute value "genre," and the image identified by the id having the attribute value "ServiceBundlelmage". The file name or file location can be used as shown in Table 5 to indicate the actual data and image files of the "text" element and the image file of the "image" element. For example, Table 5 can be used to express a file name (such as "a.jpg") or a file location (such as ".../.../.../a.jpg"). That is, the RMS engine 603 is provided with the slot name, file path and location to access the archive by presenting the information provided by the obtained service pilot segment by the RMS engine 603 (e.g., the LASeR engine). In Table 5, 'LASeR engine uses "tref, attribute to refer to external data" and presents reference material in the form of "text" material of LASeR service content. Information such as "image", "video" and "audio" can be used. The "xlink:href" attribute that provides a link to the external data is presented as a component of the LASeR service content, for example, "xlink:href=ESG.xml#xmlns(ESGMain/ESG/PurchaseTable/ Purchase/MediaTitle/mpeg7:TitleImage /mpeg7:MediaUri/tex tor. In this case, when the LASeR template of Table 5 is displayed on the screen, the "id" attribute has the attribute value "Genre" of "text".

201108653 W&gt; I 〆 I is now the information "NON__FICTION" provided by the service guide segment. Moreover, the actual image file of the "image" with the attribute value "ServiceBundlelmage" of the "id" attribute is presented as the information "EasterTitle.jpg" provided by the service guide segment. Table 6 shows an RMS template in accordance with another embodiment of the present invention. Table 6 &lt;xsl'.template match=&quot;PurchaseTable&quot;&gt;&lt;xsl:iftest=&quot;@id = ../../ESGMainBCAST/Content[@id='BBCThree_d0el052']&quot;&gt;&lt;svg:text...&gt;&lt;xsl:value-ofselect^&quot;./Genre&quot;/&gt;&lt;/svg:text&gt;&lt;/xsl:if&gt;&lt;svg:image...&gt;&lt;xsl: attribute name=&quot; href' &gt;&lt;xsl:value-ofselect=&quot;ESGxml# xmlns(ESGMain/ESG/PurchaseTable/Purchase/MediaTitle/mpeg7:TitleImage/ mpeg7:MediaUri/text() )&quot;/&gt;&lt;/xsl:attribute&gt;&lt;/svg:image&gt;&lt;/xsl:template&gt; Table 6 shows the information provided by the service guide fragments expressed in the W3C SVG template, and the results are The results in Table 5 are the same. In this case, the RMS engine 603 refers to external data using various expression and reference methods such as XPath, Xpointer, and extensible Stylesheet Language Transformation (XSLT). 62 201108653. Although the above description is directed to the RMS engine for the method of referring to the SG metadata, the invention is not limited thereto, but may be implemented using various reference methods. Although the description of the terminal is made with reference to the RMS information formatted as shown in Table 3a, the mobile terminal can be configured to support the RMS information format of Table 3c and Table 3a. As described above, the rich media enhanced service guidance provisioning method and system of the present invention can provide rich media enhanced service guidance to terminals having different capabilities in a predetermined format by a service provider by using an rMS template. Moreover, the rich media enhanced service guidance provisioning method and system of the present invention can distribute rich media enhanced service guidance without compromising backward compatibility. Although the embodiments of the present invention have been described in detail above, it is to be understood that The spirit and scope of the invention are defined. BRIEF DESCRIPTION OF THE DRAWINGS Fig. 1 is a block diagram showing the logical architecture of a BCAST system for processing an application layer and a transport layer specified by the OMA BCAST work group. Figure 2 is a diagram illustrating the structure of a service guidance data model for use in a 〇MAbcaST system. 3 is a block diagram showing the relationship between a Service Pilot Delivery Descriptor (SGDD) and a Service Pilot Transfer Unit (SGDU) in the Service Guided Data Model of FIG. 2. 4 is a flow chart illustrating a rich media enhancement service method according to an embodiment of the present invention. Figure 5 is a flow chart illustrating a procedure for handling received rich-enhanced service guidance in a rich media enhancement service guide provisioning method in accordance with an embodiment of the present invention. Figure 6 is a block diagram showing the configuration of a terminal set according to an embodiment of the present invention. Figure 7 is a block diagram illustrating a rich media based service guidance data model. [Main Component Symbol Description] 101: Content Creation 102: BCAST Service Application 103: BCAST Service Distribution/Adaptation 104: BCAST Subscription Management 105: Terminal 111: BDS Service Distribution 112: Broadcast Distribution System 113: Networked/Interactive Network 121 : BCAST-1 122 : BCAST-2 123 : BCAST-3 124 : BCAST-4 125 : BCAST-5 126 : BCAST-6 127 : BCAST-7 64 201108653 j^^yupif 128 : BCAST-8 129 : BDS- 1 130 : BDS-2 131 : Xl 132 : X-2 133 : X-3 134 : X-4 135 : X-5 136 : X-6 200 : Management Group 201 : Service Guide Transfer Descriptor 210 : Supply Group 211: Purchase Item/Service Guide/Purchase Item Segment 212: Purchase Information/Service Guide/Purchase Segment 213: Purchase Channel/Service Guide/Purchase Channel Segment 220: Core Group 221: Service/Service Guide/Service Fragment 222: Scheduling/Service Pilot/Scheduling Segment 223: Content/Service Pilot/Content Fragment 230: Access Group 231: Access/Service Pilot/Access Fragment 232: Session Description/Service Pilot/Session Description Section 241: Preview Data/Service Guide/Preview Profile 251: Interactive Data/Service Guide/ Mutual material fragment 65 201108653 300: Service Guided Release Channel 301: Service Guided Delivery Descriptor 302: Description Entry 310: SG Delivery Channel 311: By SG Channel 312: Service Guidance Delivery Unit 320: SG Fragment 601: Receive Module 603: RMS Engine 605: BCAST Client 66

Claims (1)

201108653. oj^yupif VII. The scope of application for patents: ι_ - The method of strengthening the media-enhanced guidance for the digital service of the digital service' includes the following steps: the capacity is set to be transmitted to the user device or within multiple broadcast services. Generating information to generate a Service Guided Delivery Descriptor (SGDD), the SGDD including rich media content information rich media content information including capability information of the user device; to broadcast the SGDD to the user device . The method of claim 2, wherein the capability information is provided by the user in a rich solution (RMS) template descriptor towel. 3. The method of claim 2, wherein the template descriptor comprises a transmission indicator that points to an RMS template for rendering the rich media enhanced service guide on the secret carrier device. 4. The method of claim 3, wherein the transmission indicator comprises at least one of a destination address, a nickname, a source address, and a transmission session identifier. 5. The method of claim 1, wherein the rich media content information further comprises a broadcast subscription management H(10)(4) identifier identifying a BSM with an rMS template for rendering the rich media enhanced service guide. 6. A method for reproducing a media enhanced service guide for a digital broadcast service on a user device, comprising the steps of: 67 201108653 f receiving based on a broadcast service to be delivered to the user device a service guide delivery descriptor (SGDD) of the content information, the SGDD includes a rich media content information that includes the capability information of the user device, and the rich media content information is used to determine the location Compatible with the user device; and ~ if the user device is determined to be compatible with the rich media content information, rendering the rich media enhanced guide on the user device based on the SGDD . 7. The method of claim 6, wherein the capability data of the user device is provided in a rich media solution (RMS) template descriptor. 8. The method of claim 7, wherein the rmS template descriptor comprises a delivery indicator pointing to an RMS template for rendering the rich media enhanced service guide on the user device. 9. The method of claim 8, wherein the transmission indicator comprises at least one of a destination address, a nickname, a source address, and a transmission session identifier. 10. The method of claim 6, wherein the rich media content information further comprises a Broadcast Subscription Manager (BSM) identifier, the identification identifying an RMS template for rendering the rich media enhanced service guide BSM. 11. A data structure for rich media enhanced service guidance in a digital broadcast service embodied on a processor readable medium, the data structure 68 201108653 jj^yupif comprising: a Service Guided Delivery Descriptor (SGDD), It is based on content information to be delivered to one or more of the user devices; a rich media solution (RMS) segment containing rich media content information directed by the rich media enhancement service; and an RMS template descriptor The device includes capability information of the user device for determining compatibility of the user device with the rich media content information. 12. The data structure of claim 5, further comprising a transfer indicator pointing to an RMS template for rendering the rich media enhanced service guide on the user device. 13. For the data structure described in the patent application scope fl2, wherein the delivery indicator includes at least one of a destination address, a nickname, a source location (4), and a transmission session identifier. 14. The data structure described in the patent application scope f u, including the broadcast reservation management H (dirty) job, and the knowledge of the rich media enhancement service 丨 丨 RMS template bsm. 69