CN101433090B - Method and system for providing notification message in mobile broadcasting system - Google Patents

Abstract

A method for providing a notification message in a transmitter of a mobile broadcast system supporting an interaction channel is disclosed. Upon occurrence of a notification event, the first device generates a notification message and generates at least one delivery request message including a target address based on subscription information of a corresponding terminal using the generated notification message. The second device determines a channel on which it is to transmit the notification message to the corresponding terminal based on the target address, and transmits the notification message on the determined channel.

Description

Method and system for providing notification message in mobile broadcasting system

technical field

The present invention generally relates to a method and system for providing notification messages in a mobile broadcast system, and more particularly, to a method and system for providing notification messages using an interaction channel in a mobile broadcast system. the

Background technique

The mobile communication market is often faced with the need to continuously generate new services through the reorganization or integration of existing technologies. Currently, due to the development of communication and broadcasting technologies, conventional broadcasting systems or mobile communication systems have reached a stage of providing broadcasting services through portable terminals (or mobile terminals or terminals) such as mobile phones, personal digital assistants (PDAs), and the like. Now, the convergence (convergence) of mobile communication services and Internet Protocol (IP) technology has become the mainstream of next-generation mobile communication technologies, thereby following potential market requirements, increasing user demand for multimedia services, for providing services in addition to existing voice Strategies of service providers of new services like broadcasting services other than services, and interests of information technology (IT) companies that are improving their mobile communication business to meet user demands. the

The Open Mobile Alliance (OMA) is a group organized to study inter-working standards between various mobile solutions. It is responsible for establishing various application standards for mobile games and Internet services. In particular, the OMA Browser and Content (BAC) Mobile Broadcast (BCAST) sub-working group, which is one of the OMA working groups, is researching technologies for providing broadcast services using mobile terminals. A brief description of the mobile broadcasting system being discussed in the OMA BCAST working group will now be given. the

The mobile broadcasting system includes a process of discovering a service through a terminal capable of receiving mobile broadcasting, a process of subscribing to a service through a terminal, a process of providing various control information for receiving the service, a process of transmitting the service, and a process of The terminal receives the processing of the service. In a mobile broadcast system, during a mobile broadcast process, when a terminal receives a broadcast service, the terminal receives a notification message including various control information for the broadcast service. the

In a mobile broadcast system, when a terminal receives a broadcast, due to various factors, changes may occur in the broadcast system. Some changes may be information that should have to be provided to the terminal. The information may include, for example, changes in mobile broadcast service time, changes in information for receiving mobile broadcast services, and the like. the

A method for transmitting a notification message in a mobile broadcast system has been defined. the

Contents of the invention

However, in a mobile broadcast system supporting an interactive channel, a transmission method for a notification message has not yet been defined. Therefore, a notification message delivery method needs to be defined. the

An aspect of the present invention is to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present invention is to provide a method and system for transmitting a notification message in a mobile broadcast system. the

Another aspect of the present invention is to provide a method and system for transmitting a notification message in a mobile broadcast system supporting an interactive channel. the

According to an aspect of the present invention, there is provided a method for providing a notification message in a transmitter of a mobile broadcast system supporting an interactive channel, the method comprising the steps of: when a notification event occurs, for managing the subscription of a terminal The first means of information generates a notification message, and uses the generated notification message, based on the subscription information of the terminal to generate at least one transmission request message including the destination address; and the second means for transmitting the notification message determines that the second means will The channel on which the notification message is transmitted to the corresponding terminal is based on the target address, and the notification message is transmitted on the determined channel. the

According to still another aspect of the present invention, there is provided a transmitter in a mobile broadcast system supporting an interactive channel, the transmitter comprising: first means for managing subscription information of a terminal, generating a notification when a notification event occurs message, and using the generated notification message, based on the subscription information of the terminal to generate at least one transmission request message including a target address; and a second means for determining that the second means will transmit to the terminal based on the target address A channel for the notification message, and the notification message is transmitted on the determined channel. the

According to yet another aspect of the present invention, there is provided a method for receiving a notification message in a terminal of a mobile broadcast system supporting an interactive channel, the method including the steps of: checking notification content from a service guide, and ordering/subscribing for a service purchasing, transmitting a subscription request message of a notification message to a first device for managing subscription information of a terminal, the request message including reception channel information of the notification message; receiving a response message including verification information from the first device; and at After the verification is completed, the notification message transmitted according to the transmission channel information is received. the

According to still another aspect of the present invention, there is provided a terminal in a mobile broadcast system supporting an interactive channel, the terminal including: first means for checking notification content from a service guide, and for service subscription/purchase, to An entity for managing subscription information of a terminal transmits a subscription request message of a notification message, and in response thereto receives verification information, the request message including reception channel information of the notification message; and second means for receiving, after the verification is completed, according to Entity that transmits notification messages for channel information transfers. the

According to still another aspect of the present invention, there is provided a method for providing a notification message in a mobile broadcast system supporting an interactive channel, the method including: a terminal checks notification content from a service guide, and for service subscription/purchase, submits a notification message to The transmitter for managing the subscription information of the terminal transmits a subscription request message of the notification message, the request message including a reception channel message of the notification message; and the transmitter performs verification according to the subscription request message, stores the subscription information of the terminal, and when notification occurs When an event occurs, the notification message of the corresponding service is transmitted based on the channel information. the

According to still another aspect of the present invention, there is provided a mobile broadcasting system supporting interactive channels, the system including: a terminal for checking notification content from a service guide, and for service subscription/purchase, to The transmitter of the information transmits the reservation request message of the notification message, the request message includes the receiving channel information of the notification message; and the transmitter is used to store the reservation information of the terminal according to the reservation request message, and when a notification event occurs, based on the channel information and transmitting a notification message of the corresponding service to the terminal. the

Specifically, according to the first aspect of the present invention, there is provided a method for providing a notification message in a transmitter of a mobile broadcast system supporting an interactive channel, the method comprising the following steps: (a) when a notification event occurs When , the entity for managing the subscription information of the terminal generates the notification message, and generates at least one transmission request message including a target address based on the subscription information of the terminal to request transmission of the generated notification message, the subscription information including The terminal receives the receiving channel information of the notification message, and the target address includes the receiving channel information for the terminal to receive the notification message; and (b) the entity used to transmit the notification message determines the The entity is to transmit the notification message to the terminal based on the channel on which the target address is to be transmitted, and transmits the notification message on the determined channel. the

According to a second aspect of the present invention, there is provided a transmitter in a mobile broadcast system supporting interactive channels, the transmitter comprising: an entity for managing subscription information of a terminal, generating a notification message when a notification event occurs, And generate at least one transmission request message including a target address based on the subscription information of the terminal to request transmission of the generated notification message, the subscription information includes receiving channel information for the terminal to receive the notification message, and the target address includes the user receiving channel information for the terminal to receive the notification message; and an entity for determining a channel for determining a channel on which the entity for determining the channel is to transmit the notification message to the terminal based on the target address, and The notification message is transmitted on the determined channel. the

According to a third aspect of the present invention, there is provided a method for receiving a notification message in a terminal of a mobile broadcast system supporting an interactive channel, the method comprising the steps of: checking notification content from a service guide, checking service subscription/purchase Information, transmitting a reservation request message of the notification message to the entity for managing the subscription information of the terminal, the request message includes receiving channel information of the notification message; receiving from the entity for managing the subscription information of the terminal includes a response message for verifying the information; and after completing the verification, receiving the notification message transmitted according to the transmission channel information. the

According to a fourth aspect of the present invention, there is provided a terminal in a mobile broadcast system supporting interactive channels, the terminal comprising: a first entity for checking notification content from a service guide, checking service subscription/purchase information, and sending an entity for managing subscription information of a terminal transmits a subscription request message of a notification message, and receives verification information in response thereto, the request message including reception channel information of the notification message; The entity of the notification message for which information is transferred. the

According to a fifth aspect of the present invention, there is provided a method for providing a notification message in a mobile broadcast system supporting an interactive channel, the method comprising: checking notification content from a service guide by a terminal, checking service subscription/purchase information, and sending a transmitter for managing subscription information of the terminal transmits a subscription request message of the notification message, the request message including receiving channel information of the notification message; and the transmitter performs verification according to the subscription request message, stores the subscription information of the terminal, And when a notification event occurs, the notification message of the corresponding service is transmitted based on the receiving channel message of the notification message. the

According to a sixth aspect of the present invention, there is provided a mobile broadcasting system supporting an interactive channel, the system including: a terminal for checking notification content from a service guide, checking service subscription/purchase information, and sending a message to the terminal for managing the The transmitter of the subscription information transmits the subscription request message of the notification message, and the request message includes the receiving channel information of the notification message; and the transmitter is used to store the subscription information of the terminal according to the subscription request message, and when the notification occurs When an event occurs, a notification message of a corresponding service is transmitted to the terminal based on a receiving channel message of the notification message. the

Description of drawings

According to the following detailed description in conjunction with the accompanying drawings, the above and other objects, features and advantages of the present invention will become more apparent, wherein:

FIG. 1 illustrates a system for transmitting a service guide (service guide) to a mobile terminal in a mobile broadcast system according to a first embodiment of the present invention;

FIG. 2 illustrates a notification architecture in a mobile broadcast system according to a first embodiment of the present invention;

Figure 3 illustrates the architecture of service provision in a mobile broadcast system according to a first embodiment of the present invention;

FIG. 4 illustrates an architecture for transmitting notification messages in a mobile broadcast system according to a first embodiment of the present invention;

5A to 5D illustrate packets in a mobile broadcast system according to a first embodiment of the present invention

Fig. 6 illustrates according to the first embodiment of the present invention, in the mobile broadcasting system through the subscription of notification message through interactive channel;

Fig. 7 illustrates the generation and request processing for notification event (Notification Event) in the mobile broadcast system according to the first embodiment of the present invention;

Fig. 8 illustrates the processing that NTDA transmits a notification message to a terminal when receiving a transmission request for a notification message from an NTG;

Figure 9A illustrates an example of an access fragment (Access fragment) in a mobile broadcast system according to a first embodiment of the present invention;

Figure 9B illustrates the access type (Access Type) in the access segment in the mobile broadcast system according to the first embodiment of the present invention;

FIG. 10 illustrates an exemplary screen of a user terminal by a service guide receiving method in a mobile broadcast system according to a first embodiment of the present invention;

11 illustrates a CBMS-based electronic service guide (ESG) delivery architecture in a mobile broadcast system according to a second embodiment of the present invention;

FIG. 12 illustrates a CBMS network entity for transmitting a notification message in a mobile broadcast system according to a second embodiment of the present invention;

FIG. 13 illustrates a CBMS-based service purchase architecture in a mobile broadcast system according to a second embodiment of the present invention;

FIG. 14 illustrates signaling between network entities in a mobile broadcast system according to a second embodiment of the present invention;

15A to 15D illustrate fragments of a CBMS-based ESG data model in a mobile broadcast system according to a second embodiment of the present invention; and

FIG. 16 illustrates a CBMS-based ESG data module in a mobile broadcast system according to a second embodiment of the present invention. the

Detailed ways

Exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. In the drawings, the same or similar elements are denoted by the same reference numerals although they are depicted in different drawings. In the ensuing description, detailed descriptions of well-known functions and configurations incorporated herein are omitted for clarity and conciseness.

The present invention provides a method and system for managing notification messages in a mobile broadcast system supporting interactive channels. Several embodiments of the mobile broadcast system according to the present invention will be described here. A notification message transmission method according to the present invention will also be described. In the first embodiment, a broadcast system defined in the 3rd Generation Partnership Project (3GPP) (which is a standard for asynchronous mobile communication), or defined in the Open Mobile Alliance (OMA) (a standards body for terminal applications) will be described broadcasting system, and in the second embodiment, a Digital Video Broadcasting-Consolidated Broadcasting and Mobile Services (DVB-CBMS) system, which is another mobile broadcasting standards body, will be described. The first embodiment of the present invention will be described with reference to the architecture and terminology used in the OMA, and the architecture and terminology used in the second embodiment will be mapped to the architecture and terminology of the mobile broadcast system according to the first embodiment. the

For better understanding of notification messages, a mobile broadcast system according to a first embodiment will now be described. Although the entities and names defined in OMA's BCAST will be used in the first embodiment, the standards and entity names described therein are not intended to limit the scope of the present invention, and the present invention can be applied to any system having a similar technical background . the

In a mobile broadcast system, a mobile terminal receiving a broadcast service should receive service guide (SG) information including description information of the service itself, charging information of the service, and information on a reception method of the service. The mobile terminal receives the corresponding service using the service guide information. the

Although the present invention will be described herein by way of example with reference to OMA BCAST technology, which is one of mobile broadcast technology standards, the description is not intended to limit the present invention. the

FIG. 1 illustrates constituent elements for delivering a service guide to a mobile terminal in a mobile broadcast system according to a first embodiment of the present invention. Before the description of FIG. 1 is given, definitions of interfaces used between constituent elements are given in Table 1. the

Table 1

interface definition SG1 Server-to-server communication for transmitting content attributes, such as description information, location information, target terminal capabilities, target user profiles, etc., in the form of BCAST service guide fragments, or in a proprietary format. SG2 Server-to-server communication is used to transmit BCAST service attributes in the form of BCAST service guide fragments, such as service/content description information, scheduling information, location information, target terminal capabilities, target user profiles, etc. SG-B1 Server-to-server communication for BDS-specific attributes from BDS to BCAST service guide adaptation function to assist in service guide adaptation to specific BDS

compiled, or used to convey BCAST service guide attributes to BDS specific adaptation and distribution. SG4 Server-to-server communication for conveying offer information, purchase information, reservation information, promotional information, etc. in the form of BCAST service guide fragments. SG5 The BCAST service guide is delivered over a broadcast channel via IP. SG6 For example, the BCAST service guide is communicated via an interactive channel via HTTP, SMS, or MMS for interactive access to retrieve the service guide or additional information related to the service guide.

Referring to FIG. 1, content creation (Content Creation, CC) 101 is a provider of broadcast services (BCAST services), and the BCAST services may include traditional audio/video broadcast services, music/data file download services, and the like. Using the Service Guide Content Creation Source (SGCCS) 102, the CC 101 transmits the content information necessary for generating the Service Guide for the BCAST service to the Service Guide Application Source (SGAS) 105 of the BCAST Service Application (BSA) 104 via the SG1 interface 103 of Table 1 , performance information of the mobile terminal, user profile, content time information, and the like. the

BSA104 controls and processes the BCAST service data provided from CC101 into a format suitable for the BCAST network. In addition, the BSA 104 controls the generation of standardized metadata required for the mobile broadcast guide. SGAS 105 communicates via SG2 interface 106 to Service Guide Generation (SG-G) 109 in BCAST Service Distribution/Adaptation (BSD/A) 108 for generating a Service Guide including information provided from SGCCS 102 (e.g. service/content specific information, scheduling information, location information, etc.) necessary for various sources. the

The BSD/A 108 controls, establishes a bearer on which it will transmit BCAST service data provided from the BSA 104, determines a delivery schedule for the BCAST service, and generates mobile broadcast guide information. The BSD/A 108 is connected to a broadcast distribution system (BDS) 131 for delivering BCAST service data through a broadcast channel and an interactive network (IN) 133 for supporting interactive communication through an interactive channel. the

The service guide generated from the SG-G 109 is transmitted to the mobile terminal (terminal) 119 via the SG distribution (SG-D) 110 and the SG5 interface 117 . the

The BCAST Subscription Management (BSM) 113 manages subscription information and service provision information for receiving BCAST services, and device information of mobile terminals for receiving BCAST services. Service Guide Subscription Source (SGSS) 114 in BSM 113 transmits to SG-G 109 via SG4 interface 112 subscription/provision sources related to generation of service guides, and sources such as purchase information and promotional information to generate service guides. the

The terminal 119 is a terminal capable of receiving BCAST services, and has a function of being able to connect to a cellular network according to terminal performance. Terminal 119 having service guide client (SG-C) 120 receives service guide transmitted via SG5 interface 117, or receives notification message transmitted via SG6 interface 118, and performs an operation suitable for BCAST service reception. the

Tables 2 to 4 illustrate the functional definitions for the main constituent elements of Figure 1 as specified in the OMA BCAST standard. the

Table 2

logical entity definition content creation In content creation, a Service Guide Content Creation Source (SGCCS) can provide content attributes such as content description information, target terminal capabilities, target user profiles, content Timing information, etc., and send them via SG1. BCAST service application In BCAST service application, the service guide application source (SGAS) provides service/content description information, scheduling information, location information, target terminal capability, target user profile, etc. in the form of standardized BCAST service guide fragments, and sends them via SG2 they. BCAST Reservation Management In BCAST Subscription Management, Service Guide Subscription Source (SGSS) provides offer information, purchase information, subscription information, subscription information, promotion information, etc. in the form of service guide fragments and transmits them via SG4.

table 3

logical entity definition Service Guide Generation (SG-G) Service Guide Generation (SG-G) in the network is responsible for receiving service guide fragments from various sources such as SGCCS, SGAS, SGSS via SG-2 and SG-4 interfaces, SG-G aggregates information such as service and content access according to standardized schemes segment of the incoming information and generate a Service Guide to be sent to Service Guide Distribution (SG-D) for delivery. It is optionally adapted to fit a specific BDS in the Service Guide Adaptation function (SG-A) before delivery. Service Guide Customer Functions (SG-G) The Service Guide Client function (SG-C) in the terminal is responsible for receiving service guide information from the implicit BDS and making this service guide available for mobile

[0054] terminal. The SG-C obtains specific service guide information, which it can filter to match terminal-specific criteria (e.g., location, user profile, terminal capabilities), or it simply obtains all available service guide information, typically, the user can use View Service Guide information in menu, list, or table format. SG-C can send a request to the network through SG-t in order to obtain specific service guide information or the entire service guide.

Table 4

logical entity definition SG Distribution (SG-D) SG-D generates IP flows to deliver Service Guide to SG-C via SG5 interface and broadcast channel. Before delivery, SG-G may send the Service Guide to Service Guide Adaptation (SG-A) in order to adapt the Service Guide to a suitable specific BDS according to the BDS attributes sent via BDS service distribution via SG-B1. Such adaptations may result in modifications to the Service Guide. Note that for adaptation purposes, SG-A may also send BCAST Service Guide attributes or BCAST Service Guide fragments to BDS service distribution via SG-B1 for adaptation, said adaptation within BDS service distribution is not within the scope of BCAST, SG- D can also receive a request for service guide information, and directly send the requested service guide information to the terminal through the interaction channel. SG-D can also filter service guide information from SG-G based on the end user's pre-specified profile. SG-D may also send the Service Guide to the BDS, which modifies the Service Guide (eg by adding BDS-specific information), and also distributes the Service Guide to SG-C in a BDS-specific manner.

FIG. 2 illustrates a notification architecture in a mobile broadcast system according to a first embodiment of the present invention. the

CC101 is a broadcast service (BCAST service) provider. BCAST services may include traditional audio/video broadcast services, music/data file download services, and the like. If any problem or change occurs in provisioning BCAST service, CC101 notifies Notify Event Function (NTE) 201 in BSA104 of the change. the

BSA 104 performs control, processes BCAST service data provided from CC 101 into a format suitable for BCAST network, and generates standardized metadata required for mobile broadcast guide. In addition, BSA 104 notifies notification generation function (NTG) 203 in BSM 113 of a change in the BCAST service provided from CC 101. the

The BSD/A 108 controls to establish a bearer channel via which the BSD/A 108 will transmit BCAST service data provided from the BSA 104, determines a transmission schedule of the BCAST service, and generates mobile broadcast guide information, and the BSD/A 108 connects to the BDS 113 and the IN 133. In addition, BSD/A 108 having a notification distribution/adaptation function (NTDA) 202 receives a notification message from BSM 113 and transmits the notification message to a single user or multiple users via BDS 131 or IN 133 . the

The BSM 113 manages subscription information and service provision information for receiving BCAST services, and device information of mobile terminals for receiving BCAST services. Specifically, the BSM 113 with the NTG 203 receives information on notification events occurring in various network entities for providing mobile broadcast services, and generates a notification message using the received information, or generates a notification message for a self-event of the BCAST service. the

Terminal 119 is a terminal capable of receiving BCAST services, and has a function of being able to connect to a cellular network according to terminal performance. Using the notification client function (NTC) 204, the terminal 119 receives a notification message transmitted via the NT5 interface 214, and performs an appropriate operation according to the NT5 notification message, or receives a notification message transmitted via the NT6 interface 215, and performs an appropriate operation according to the NT6 notification message. operate. the

The NT-1 interface 211 serving as an interface between the NTE 201 in the BSA 104 and the CC 101 is used to transmit notification events occurring in the CC 101 to the NTE 201 . the

The NT-3 interface 212, which is an interface from the NTE 201 in the BSA 104 to the NTG 203 in the BSM 113, is used to carry information required to generate event notifications or notification messages so that the NTG 203 can generate notification messages. the

NT-4 interface 213 as the interface from NTG203 in BSM113 to NTDA202 in BSD/A108 is used to transmit the notification message generated in NTG203 to NTDA202, so that the notification message is further transmitted to BDS131 or IN133, or the NT -4 interface 213 is used to transfer events occurring in BSD/A108 or BDS131 to NTDA202. the

The NT-5 interface 214 is an interface used to directly transmit a notification message provided from the NTDA 202 in the BSD/A 108 to the terminal 119 via the BDS 131 through a broadcast channel. NT-5 interface 214 is used to transmit notification messages to multiple terminals. the

The NT-6 interface 215 is an interface used to directly transmit a notification message provided from the NTDA 202 in the BSD/A 108 to the terminal 119 via the IN 133 . NT-6 interface 215 is used to transmit notification messages to individual terminals.

The NT-B1 interface 216 is used as a transmission path for the BSD/A108 to be used in the BDS131, or as a reception path for event information generated in the BDS131. NT-B1 interface 216 is the interface between BSD/A 108 and BDS Service Distribution (BDS-SD) 130 . the

NTE 201 controls to transmit to NTG 203 information necessary for generating a notification message, and if there is information on notification event generation, controls to transmit the information to NTG 203 . The NTG203 controls to generate a notification message using information and events received from the NTE201 required for generating a notification message, or controls to generate a notification message upon receipt of a notification event from the BDS131 or IN133 via the NTDA202, and controls to transmit the notification message to NTDA202. (i) when it is necessary to re-notify the start of the service, (ii) when a new mobile broadcast guide needs to be transmitted when NTG203 receives a notification indicating a change in service information from CC101, and (iii) when it has been NTG 203 can generate notification messages when certain events occur. the

NTDA 202 controls the transmission of notification messages via NT-5 interface 214 or NT-6 interface 215 . In addition, upon receiving information indicating a change in a specific mobile broadcast service due to the wireless network environment, for example, information indicating rate control or service impossibility, from the BDS 131, the NTDA 202 transmits a corresponding notification to the NTG 203 via the NT-4 interface 213 event. the

Fig. 3 illustrates an architecture for service provisioning in a mobile broadcast system according to a first embodiment of the present invention. The service provisioning framework controls the user subscription for BCAST services and the purchase process for the subscribed services. Additionally, the service provisioning framework provides additional information for processing payments and purchases, such as status information for user accounts. the

Referring to FIG. 3, a Broadcast Service Provisioning Manager (BSP-M) 301 provides subscription and purchase information. Based on user subscription information, BSP-M 301 provides user charging information to relevant entities and supports charging for the mobile broadcast service. BSP-M 301 receives requests and reports for subscription and charging from Broadcast Service Provisioning Client (BSP-C) 302 via SP-7 interface 311 and SP-8 interface 312 . BSP-C 302 controls generation of reports on subscriptions and purchases for mobile broadcast services. The BSP-C 302 can request subscription and purchase or request additional information based on the offer information extracted from the service guide. The descriptions of the SP-7 interface 311 and the SP-8 interface 312 are shown in Table 5. the

table 5

interface reference point use SP-7 BCAST-7 Messages for subscriptions are conveyed, such as subscription requests by users and responses from BCAST subscription management. Send payment information

SP-8 out of band End users subscribe and purchase services through the out-of-band interface. It is outside the scope of OMA BCAST.

值。“基数(Cardinality)”指明元素之间的关系，并具有值0、0..1、1、0..n、1..n。这里，0是指可选关系，1是指强制关系，而n是指可被使用多个值。例如，0..n是指对应的消息可能没有元素或者可能具有n个元素。“描述”指明对应元素或属性的含义，“数据类型”指明对应元素或属性的数据类型。 Referring to Table 6, "Name" indicates the names of elements and attributes constituting the corresponding message. "Type" indicates the type (element or attribute) of the corresponding name. This element has values El, E2, E3 and E4. E1 designates an upper layer element of the entire message, E2 designates a sub-element of E1, E3 designates a sub-element of E2, and E4 designates a sub-element of E3. The attribute is represented by A, and A designates the attribute of the corresponding element. For example, A under E1 indicates the attribute of E1. "Category" is used to determine whether the corresponding element or attribute is mandatory or optional, and has an M value for mandatory elements or attributes, and an M value for optional elements or attributes

value. "Cardinality" specifies the relationship between elements and has values 0, 0..1, 1, 0..n, 1..n. Here, 0 means an optional relationship, 1 means a mandatory relationship, and n means multiple values can be used. For example, 0..n means that the corresponding message may have no elements or may have n elements. "Description" indicates the meaning of the corresponding element or attribute, and "data type" indicates the data type of the corresponding element or attribute.

Table 6

name type category Cardinality describe type of data

FIG. 4 illustrates an architecture for transmitting notification messages in a mobile broadcast system according to a first embodiment of the present invention. For convenience, FIG. 4 includes only elements required for transmitting notification messages among the entities described in FIGS. 1 to 3 . the

Referring to FIG. 4 , SG-G 109 generates a service guide including time, purchase and access information related to services and contents in step 401 , and then sends a request for service guide delivery to SG-D 110 . SG-D 110 then sends the service guide to terminal 119 at step 402 . The service guide can be delivered via BDS and/or IN through a broadcast channel and/or an interactive channel, respectively. When the service guide is transmitted through the broadcast channel, the terminal 119 receives the service guide from the session through which the service guide is transmitted, and when the service guide is transmitted through the interactive channel, the terminal 119 accesses the IN and then receives the service guide in response to a corresponding request . the

SG-C 120 in terminal 119 controls service guide reception from SG-D 110, and the user acquires service and content information from the received service guide. Based on the service guide, the user determines subscription and purchase information for services, schedules, contents, etc., and then makes a request for service provision such as subscription and purchase using BSP-C302. In order to receive related service notification messages, BSP-C 302 sends a subscription/unsubscription request to BSP-M 301 in step 403 . the

Upon receiving a request for user ID, device ID and service/notification subscription information, BSP-M 301 stores the corresponding user information in DB 411 in BSM 113. Notification events may occur in various network entities for providing mobile broadcast services. In FIG. 4, a notification event may occur in CC 101, BSA 104, BSD/A 108, and BSM 113, and in steps 404 to 406, CC 101, BSA 104, and BSD/A 108 send a request for notification message generation to NTG 203. the

NTG 203 generates notification messages for received events. After generating the notification message, the NTG 203 acquires the target address TargetAddress to which it will transfer the notification message from the DB 411 , and then generates a request message for message transfer. If there is any user who has subscribed to the message reception service through the interaction channel setting, the NTG 203 generates a request message including information on an address where the corresponding user can receive the message. the

At step 407, NTG 203 sends to NTDA 202 a request for notification message delivery. At step 408, NTDA 202 transmits a notification message to NTC 204. In this case, NTDA 202 transmits the notification message through a broadcast channel or an interactive channel according to the target address. the

Notification messages can be broadly classified into common notification messages for notifying services and service-specific notification messages as an auxiliary means for related services. After receiving the service guide, the terminal or user can identify the common notification message and/or the specific service notification message according to the next procedure. The term "Notification Service" refers to a service that consists of notifications. For example, a notification service refers to a service delivered through a Short Message Service (SMS) or Multimedia Messaging Service (MMS) notification message on a daily basis, like "today's weather information", "today's English", etc. A specific service notification message as a supplementary means is an example of a supplementary service of a main program, rather than an independent notification service. For example, when the voting for the music ranking is performed while the service "Music Top 10 Ranking" is being broadcast, and the SMS notification message for voting is transmitted to TV viewers for collecting voting information, the notification message for voting is used as an auxiliary Mode specific service notification messages. The notification service refers to a service consisting of notification only, and the service-specific notification message refers to a notification message that can occur in a main program. the

For the notification service, when the service type ServiceType in the service fragment of the service guide has a notification value, the terminal recognizes that the corresponding service is a notification service. the

For a specific service that transmits notification messages, the terminal can recognize that it can receive notification messages related to the corresponding service in the following cases: (i) when the service-related access segment includes the element "NotificationReception" (NotificationReception) 904, ( ii) when the element "ServiceClass" (ServiceClass) 903 in the service-related access fragment has a URI value specifying "sdo.oma.nt" or its similar notification value, and (iii) when in the service fragment or " When an element or attribute of a corresponding fragment indicating the possibility of receiving a notification message such as NTviaInteraction exists in the "PurchaseItem" fragment.

5A to 5D illustrate a detailed embodiment of a service guide including a notification value in a mobile broadcast system according to a first embodiment of the present invention. Since the access fragments in FIGS. 5A and 5B are shown in detail in FIGS. 9A and 9B , reference will be made thereto. the

5A illustrates an example of an access fragment 901 that includes notification reception information, and a notification message related to a corresponding service has an access to a notification transmitted through a broadcast channel contained in an element "notification reception" 904. Access information, and contains information related to the corresponding service in the element "Access Type" 902. the

Figure 5B illustrates an example of access including service and notification messages, respectively. The use on which the corresponding access information is distinguished depends on the value of the "service class" 903 . For example, for a file transfer service, an "Access Type" 902 of an access with a "Service Class" 903="sdo.oma.fd" contains access information that can be used for file downloads, and an access with a "Service Class" 903="sdo.oma.fd" sdo.oma.nt" access's "Access Type" 902 contains access information for receiving notifications. the

FIG. 5C illustrates an exemplary configuration of a service consisting of notification messages only, where the "service type" of the service fragment is notification service. One difference between FIG. 5A and FIG. 5C is that the access segment contains address information for notification message receipt, rather than "notify receipt" included separately in the access segment. the

FIG. 5D illustrates an exemplary configuration for a case where subscription/purchase of services has a specific schedule, the corresponding services including notifications. the

As described above, when the "service type" is a notification service, the access includes "notification reception" 904, or the "service type" 903 of the access is sdo.oma.nt, the terminal can recognize that the corresponding service is related to notification. the

FIG. 6 illustrates subscription to a notification message through an interactive channel in a mobile broadcast system according to a first embodiment of the present invention. the

Referring to FIG. 6 , the terminal 119 receives a service guide at step 601 . Afterwards, in step 602, the terminal 119 checks the notification content from the received service guide using the service guide described in FIG. Booking. the

Tables 7A to 7C show exemplary subscription request messages for this. the

Table 7A

name type category Cardinality describe type of data PR-7 version E. m 1 The PR-7 version interface supported by the terminal. The version number of PR-7 described in this manual is 1. integer

User ID E. m 1 User identities known to BSM. string Device ID E. m 1 A unique device identity (eg International Mobile Equipment Identity, IMEI) known to the BSM. string Request ID E. o 1 The identifier of the service request message. integer Service Protection Agreement E. o 1 Lists each service protection protocol supported by the device, including mandatory service protection protocols. Defined values: "ipsec," "srtp". The device is allowed to include more identifiers; however, they may be ignored depending on the protocols supported by the network. [Note] This element is only included in the message if the service is delivered via an interaction channel. string broadcast mode E. o 1 Indicates whether the device supports an optional broadcast mode of operation for rights acquisition in addition to interactive mode of operation. "Yes or no"

Table 7B

name type category Cardinality describe type of data BsdaID E. m 1 The global equivalent ID for BSD/A. Note: This ID is used by BSM to restore service information from BSD/A. any ur RiURL E. o 1 The Rights Issuer URL from which the BSM can retrieve the ROAP Trigger** that will be delivered to the device. any URI purchase item E. m 1..N A list of items the user wants to order Composite type project ID E1 m 1 The ID of the purchase item fragment. The project ID is advertised in the service guide and inserted in the message in the same format. any URI order options E1 o 1 Order option identifier. Possible order options are advertised in the service guide. string

price E1 o 1 This price is known to the user. integer currency A o 1 The currency in which the price is expressed. If missing, the system default is assumed. Currency codes are specified in [ISO4217]. string

Table 7C

name type category Cardinality describe type of data verify E. o 1 message validation, Base 64 encoded binary notify E. o 0..1 A subscription for receiving notification messages via an interaction channel. If notification = "true", it means subscription to notification via interaction channel. If notification = "false", this means that notifications via the interaction channel will not be delivered. Boolean

In step 603, the terminal 119 sends a request for subscription/purchase of notification messages to the BSP-M 301 using the BSP-C 302 . Afterwards, in step 604, the BSP-M 301 processes the subscription request message and stores the corresponding service and user information. After processing the corresponding event, BSP-M 301 sends a response message to the subscription request to BSP-C 302 in step 605 . An example of a response message is shown in Table 8. the

Table 8

name type category Cardinality describe type of data global status code E. m 1 The full result of the request, based on the return codes defined in Table 2 integer Right effective end time E. o 0..N The last time and date of validity of the long-term key information, after which it must be updated. [Note] This element is valid if the RO is broadcast. Otherwise, this element is not required. date time ID A m 1 The ID of the "Purchased Items" fragment relative to the valid end time any URI

Request ID E. o 1 The identifier of the corresponding service request message. integer verify E. o 1 Message verification, [Note] The method of message verification is defined in 5.1.3 Base 64 encoded binary trigger E. m 1 ROAP RO GET TRIGGER ^** . The device is expected to use the trigger to initiate one or more long-term key message acquisitions. MIME part

If Terminal 119 determines in step 611 that there is an unsubscribe from the notification message after receiving the service, then in step 612, BSP-C 302 sends an unsubscribe request for service subscription/purchase to BSP-M 301. An example of an unsubscribe request message is shown in Table 9. the

Table 9

name type category Cardinality describe type of data PR-7 version E. m 1 The terminal supports the version of the PR-7 interface. The version number of PR-7 described in this specification is 1. integer User ID E. m 1 User identities known to BSM string Device ID E. o 0..N A unique device identifier known to the BSM (eg, International Mobile Equipment Identity, IMEI) [Note] If the user has more than one device, this element indicates the device or group of devices that the user wants to unsubscribe from. string Purchase item ID E. m 1..N The ID of the "Purchased Items" fragment that the user wants to unsubscribe from. any URI Request ID E. o 1 Identifier of the unsubscribe request message integer verify E. o 1 Message verification, [Note] The method of message verification is defined in 5.1.3 Base 64 encoded binary notify E. o 0..1 A subscription to receive notification messages via an interaction channel. If notify = "true", this Boolean

Means to unsubscribe from notifications on the interaction channel. If notification = "false", this means that notifications via the interaction channel will not be delivered.

BSP-M 301 handles the unsubscribe request in step 613 and then sends a response message to BSP-C 302 in step 614 . An example of the response message is shown in Table 10. the

Table 10

name type category Cardinality describe type of data global status code E. m 1 The full result of the request, according to the return codes defined in Table 2. integer Unsubscribe from informational messages E. m 1..N For each subscription successfully canceled, a message (in free text format) indicating when the cancellation of the subscription will become effective string Purchase item ID A m 1 The ID of the "Purchased Item" fragment associated with the message. any URI Request ID E. o 1 The identifier corresponding to the unsubscribe request message integer verify E. o 1 message validation, Base 64 encoded binary

FIG. 7 illustrates generation and request processing for notification events in a mobile broadcast system according to a first embodiment of the present invention. This process shows the flow in which NTG 203 receives a notification event, or generates a message for a notification event occurring in BSM 113 , and sends a request for message transmission. the

Referring to FIG. 7, at step 701, NTG 203 has a notification event occurring in BSM 113 or receives a notification event from another network entity. Table 11A and Table 11B show request messages generated for notification messages from corresponding network entities (eg, CC, BSA, and BSD/A) for notification events. In addition, Table 12 shows an example of a response message corresponding to the request message. the

Table 11A

name type category Cardinality describe type of data NTEReq E. Specifies the delivery message for the notification event used to generate the notification message.

Contains the following attributes: NTEId Entity Address Delivery Priority Contains the following elements: Notification Event NTEId A m 1 The identifier of the notification event unsigned integer (32 bits) physical address A m 1 The address of the network entity to receive the response to this message. any URI Send Priority A o 0..1 Defines the priority of this notification event. This information is used in NTG to generate notification messages. NTG can be ignored in this field. Boolean

Form 11B

name type category Cardinality describe type of data notification event E1 m 1..N Specifies the notification event from the CC, containing the information from the CC to be included in the notification message. It is recommended that this information be conveyed in the form of a BCAST notification message format (as specified in Section 8.3). Other formats may be used. If the BCAST notification message format is used, irrelevant network mandatory elements or attributes shall be transmitted as empty fields, and irrelevant network optional elements or attributes shall not be instantiated. Contains attribute: "Namespace" namespace A o 0..1 Set to the name of the BCAST notification XML namespace to signal any URI

The content of the "notification event" conforms to the BCAST notification message format.

Table 12

name type category Cardinality describe type of data NTERes It is specified that the response message of NTEReq contains the following elements: NTEid NTEid E1 m 1..N The identifier of an NTEReq message contains the following attributes: "Status Code" unsigned integer (32 bits) status code A m 1 Indicates how to handle the overall results of NTEReq, according to the global status code (as specified in Appendix G). unsigned byte

After a notification event occurs or is received from another network entity, the NTG 203 generates a notification message at step 702 . Afterwards, in step 703, the NTG 203 determines which path it will pass through to transmit the corresponding notification message. The notification message can be transmitted through one or both of the broadcast channel and the interactive channel. When the NTG 203 determines to transmit the notification message through the broadcast channel 710 , the NTG 203 checks in step 711 the target session address to which it sends the corresponding notification message. In step 712 , NTG 203 generates a delivery request message for requesting notification message delivery in step 712 , including the corresponding destination address, and sends the request for notification message delivery to NTDA 202 in step 713 . However, if the NTG 203 determines to transmit the notification message through the interactive channel 720, the NTG 203 checks in step 721 the target user address of the user who has agreed/subscribed to receive the notification message through the interactive channel. Afterwards, in step 722, the NTG 203 generates a delivery request message for requesting delivery of the notification message, including the target address (TargetAddress) of each user related to the notification message. In this case, if there are many users, NTG 203 can generate several delivery request messages for the same notification message. Afterwards, in step 723, NTG203 sends a corresponding notification delivery message to NTDA202. the

FIG. 8 illustrates a process in which the NTDA 202 transmits a notification message to a terminal upon receiving a transmission request for the notification message from the NTG 203 . the

Referring to FIG. 8 , NTDA 202 receives a transmission request message for a notification message at step 801 . Table 13A to Table 13C show examples of transmission request messages for notification messages from NTG 203 to NTDA 202 . Table 14 shows an example of its response message.

Table 13A

name type category Cardinality describe type of data NTDReq E. A request message specifying the transfer of a notification message from NTG to NTDA contains the following attributes: NTDReqid entity address transfer priority contains the following elements: destination address notification message NTD Reqid A m 1 Identifier for NTDReq unsigned integer (32 bits) physical address A m 1 The address of the network entity to receive responses to this message. any URI delivery priority A o 0..1 Defines the delivery priority for this notification message. NTG may request NTDA to deliver the notification message with high priority. If priority = "true", this means high priority. If priority = "false", this means a general message. Boolean

Form 13B

name type category Cardinality describe type of data target address E1 o 0..N Specifies the destination address for delivering notification messages. For a specific service notification, "Access ID" or "IP Address" under "Notification Received" in the Access section may be possible values. string

If the notification message is to be delivered via an interaction channel, this value may be an email address, IMSI, etc. If not given, notification messages should be delivered to all users using SGDD. Contains the following properties: "Transfer Channel""AddressType" transmission channel A m 1 Specify delivery channel If "delivery channel" = 0, notification messages should be delivered via the broadcast channel. If "Transfer Channel" = 1, the notification message should be transmitted via the interaction channel. Boolean address type A m 1 Specifies the type of "destination address" value 0 - IP address 2 - any URI 3 - IMSI 4 - 200: for future use 201 - 255: for proprietary use unsigned byte

Table 13C

name type category Cardinality describe type of data notification message E1 m 1..N Specifies the notification message, containing the information to be included in the notification message. It is recommended that this information be conveyed in the form of a BCAST notification message format (as specified in Section 8.3). Other formats may be used. If the BCAST notification message format is used, irrelevant network mandatory elements or attributes shall be transmitted as empty fields, and irrelevant network optional elements or attributes shall not be instantiated.

Contains the following attributes: Namespace namespace A o 0..1 Set to the name of the BCAST notification XML namespace so that the content of the signaled "notification event" conforms to the BCAST notification message format. any URI

Table 14

name type category Cardinality describe type of data NTDRes Specifies the response message for NTDReq. Contains the following elements: NTDReqid NTD Reqid E1 m 1..N The identifier of an NTDReq message contains the following attributes: Status Code unsigned integer (32 bits) status code A m 1 According to the global status code (as specified in Appendix G), indicates how to process all results of NTDReq unsigned byte

In step 802, NTDA 202 checks the destination address included in the request message. Afterwards, NTDA 202 determines whether it will use the broadcast channel or the interactive channel for message transmission by parsing the "target address" information in step 803 . If NTDA 202 determines to use broadcast channel 810 for message transmission, NTDA 202 checks session information such as IP address from "target address" information in the request message in step 811, and then transmits a notification message in the corresponding session. the

However, if NTDA 202 determines to use interactive channel 820 , NTDA 202 checks in step 821 the type of "target address". After that, in step 822, the NTDA 202 determines a delivery method according to the type of the destination address, and then uses the delivery message to deliver the notification message. the

Tables 15 to 17 show exemplary methods of subscribing/unsubscribing notification messages for each individual service in the notification message subscription described in FIG. 6 . the

Table 15

name type category Cardinality describe type of data Service ID E. o 0..1 A unique ID for the service. It can be an ID of a service fragment or a "global service ID" any URI

(GlobalServiceID) contains the following properties: Notification notify A m 1 Subscriptions receive service-related notification messages via an interaction channel. If notify = "true", this means subscribed to notifications on the interactive channel. If notification = "false", this means that notifications on the interaction channel will not be delivered. Boolean

Table 16

name type category Cardinality describe type of data Service ID E. o 0..1 A unique ID for the service. It can be the ID of a service fragment or a "Global Service ID" (GlobalServiceID) with the following properties: Notification any URI notify A m 1 Unsubscribe to receive notification messages via the interaction channel. If notification = "true", this means to unsubscribe from notifications via the interaction channel. If notify = "false" or the value is absent, this means that the current subscription for notification messages will be kept. Boolean

Table 17

name type category Cardinality describe type of data hold book A o 0..1 Keep your current subscription for Purchased Items. When a user maintains a current subscription to a "purchased item" and wants to unsubscribe from receipt of related notification messages via the interaction channel. the field Boolean

Is required and is set to "true" If this element is absent or has a value of "false", it means that "purchased items" and their associated notifications will be unsubscribed.

Table 15 shows messages in the case of subscribing to "Purchase Item" or Service Bundle, notification message reception of a specific service is selected from among services included in the corresponding bundle. During service subscription in step 603 of Figure 6, the elements in Table 15 and their associated attributes are transferred using a request message. If a specific "Service ID" (ServiceID) notification message reception is expected, the property notify is set to "true", and if a specific "service ID" notification message reception is not expected, the property notify is set to "false". the

Table 16 shows messages of a case in which reception of a notification message of a specific service unsubscribed among services included in a 'purchased item' or a service bundle is performed. During service unsubscribing in step 612 of Figure 6, the elements in Table 16 and their associated attributes are transmitted with the request message. If a specific "Service ID" is desired to be notified of message unsubscribing, set the property Notify to "true". If attribute notification is set to "false" or there is no attribute notification, it means that the user keeps its current subscription. Each related service and notification message reception undergoes unsubscription without specific service selection through Table 16 if the user requests to unsubscribe from the corresponding "purchase item" or service package. However, if the user desires an unsubscribe notification message for a particular service while maintaining its subscription to a "purchased item" or service bundle, Tables 16 and 17 are included in the unsubscribe message, and the attributes in Table 17 are Set to "true" and Table 16 may be used to opt out of notification message receipt for each individual service. the

FIG. 10 illustrates exemplary screens of a user terminal by a service guide receiving method in a mobile broadcast system according to a first embodiment of the present invention. Shown is a method and process for subscribing to a notification message while receiving a subscribing "item of purchase" through a service guide. the

After the user terminal receives the service guide, the user can check the service and content information, and can also check the service package information through the 'purchase item' information. The user terminal can display service guide content on the terminal screen 1001 so that the user can check the service content. A terminal screen 1001 is an exemplary screen of a sports channel pack. Reference numeral 1011 designates a service package name as a title of "purchase item", and reference numeral 1013 shows a list of services included in the corresponding package. the

Using reference numerals 1012 and 1014, the user determines whether to provide notification messages for each individual service through interaction. In this embodiment, only ESPN and SBS Sports interact to provide notification messages. If the user subscribes to a service using a subscription button 1015, the screen 1001 changes to a subscription message generation screen 1002. If the user desires to receive notification messages through interaction in a particular service, he/she selects it in the check box 1024, and uses the button 1025 to request a subscription to the service and related notification messages, and through the service including Table 15 A provisioning subscription message transfers the corresponding information to the BSM, thereby completing the subscription. A similar method is also used to perform unsubscribing. the

A notification message transmission method in a Digital Video Broadcasting-Consolidated Broadcasting and Mobile Services (DVB-CBMS) system according to a second embodiment of the present invention will now be described. the

Although the terminology used in the second embodiment of the present invention for network entities, interfaces, and information communicated between network entities and terminals is mapped to terms used in the DVB-CBMS WG for convenience, this is to illustrate the present invention It is applicable to similar broadcasting systems and is not intended to limit the scope of the present invention. the

FIG. 11 illustrates a CBMS-based electronic service guide (ESG) delivery architecture mapped to the architecture of FIG. 1 . The definitions of the network entities used in Figure 11 are given in Table 18. Among the entities shown in FIG. 11 , “Specific Logical ESG Aggregator” is an important entity in the present invention, and has the combined function of SG-D110 and SG-G109 of FIG. 1 , ie, controls generation and transmission of ESG. the

Table 18

logical subentity Which logical entity is it part of reference points involved describe ESG source service application CBMS-7, CBMS-2 Service application specific sources of ESG fragments, including offer information, acquisition information (from service application configuration sub-entity) and purchase information SDP files, which are part of acquisition information, can be delivered separately from ESG. In that case, the service application can transmit the SDP file via the CBMS-2 reference point. ESG Buying Information service application inside SA Helpful sources of ESG buying information. Service applications can rely on other sources for this information. Specific Logic ESG Aggregators service management CBMS-7CBMS-3 This entity receives ESG information chunks from one or more service applications, aggregates them into an ESG (as perceived by the end user), and generates a consistent set of ESG information chunks, including containers; the information chunks are output to

The physical ESG aggregator ESG logical aggregator is responsible for managing the container version The service application can contribute to more than one logical ESG aggregator. Bootstrap ESG Aggregator service management CBMS-3 This entity receives ESG announcement information from all specific aggregators and generates guided ESG flows. logical subentity Which logical entity is it part of reference point describe Resource Provisioning and Scheduling service management CBMS-6 Specific configuration for ESG delivery here interactive delivery server service management CBMS-4 Provide peer-to-peer access (pull or push) to ESG via interactive network Physical ESG Aggregator broadcast network CBMS-3 This entity receives ESG information chunks (e.g. containers) from one or more logical ESG aggregators, puts them into a FLUTE carousel and optimizes the mapping on DVB-H bursts (e.g. avoiding ESG information split) DVB-H Explorer broadcast network CBMS-6 See description in service configuration section IP-to-Section Mapper broadcast network CBMS-6 This entity is responsible for encapsulating IP packets into DVB-HMPE parts and generating MPE-FEC parts by performing MPE-FEC encoding. Usually part of an IP wrapper. Service and Content Description Handlers terminal CBMS-3 Receiving and aggregating a subset or all of ESG information chunks, maintaining them up-to-data, and making them available to ESG applications Presentation and interaction of ESG information is outside the scope of this specification

FIG. 12 illustrates an architecture corresponding to the OMA-based architecture of FIG. 2 . The structure of network entities used to transmit notification messages in CBMS is shown.

Referring to FIG. 12, a content creation (CC) 1201 is a provider of broadcasting services, and the broadcasting services may include conventional audio/video broadcasting services, music/data file download services, and the like. If there is any problem or change in provisioning of the broadcast service, the CC 1201 notifies the change to the Notification Event Function (NEF) 1202a in the Service Application (SA) 1202 . The NEF 1202a communicates notification events to a Notification Generation Function (NCF) 1203a based on the received events. the

SA1202 controls the processing of the content data of the broadcast service provided from CC1201 into a format suitable for the broadcast network (for example, audio/video streaming, or movie download) in order to generate broadcast service data, controls the generation of standardized metadata necessary for the service guide, and Controls the generation of charging information for users. In addition, SA1202 transfers a notification event to NGF1203a in service management (SM)1203 for a change in broadcast service provided from CC1201, and provides service guide attribute information for generating a notification message to NGF1203a. the

SM1203 controls determination of delivery schedule for broadcast service provided from SA1202 and generates service guide, and SM1203 is connected to DVB-H network 1206 supporting broadcast channel and interactive network 1207 supporting interactive channel. In addition, the SM1203 having a notification distribution/adaptation function (NDAF) 1203b therein receives a notification message transmitted from the SM1203 and transmits the notification message to a terminal or a group of terminals via a broadcast network 1206 or an interactive network 1207 . The SM1203 has the session information required by the NGF1203a, and is used to generate a terminal notification message. This session information is provided from NDAF1203b to NGF1203a. the

The SM1203 manages subscription information for receiving a broadcast service and service provision information such as information indicating whether a user has purchased related content, and also manages device information of a terminal for receiving a broadcast service. In addition, SM1203 transmits user charging information to SA1202, and provides subscription information, service provision information, and device information to broadcast network 1206 and interactive network 1207. Specifically, when SM1203 includes NGF1203a, it generates a notification event for the occurrence (if any) of the addition of new functions or the change of existing functions provided from content creation 101, SA1202, SM1203 and broadcasting network 1206. or generate a notification message indicating an ego event that broadcast service provision content (ie, a corresponding broadcast service) will be provided after a predetermined time elapses. the

The broadcast network 1026 is a network for delivering broadcast services. Here, by way of example, a DVB-H network is used as the broadcast network 1206 . If there is any change in the delivery of the broadcast service, the broadcast network 1206 controls to notify the SM 1203 of the change via the CBMS-6 interface 1224a or the X-3 interface 1224b. the

The interactive network 1207 transmits broadcast services on a point-to-point basis, or interactively exchanges control information and additional information related to broadcast service reception. For example, the interaction network 1207 may be an existing cellular network, such as a 3GPP Wideband Code Division Multiple Access (WCDMA) network. the

The terminal 1208 is a terminal capable of receiving broadcast services, and has a function of being able to connect to a cellular network according to terminal performance. Terminal 1208 is assumed to be a terminal capable of connecting to a cellular network. Using the notification client function (NCF) 1208a, the terminal 1208 receives a notification message transmitted via the CBMS-5 1225 interface and performs an operation appropriate therefor, or receives a notification message transmitted via the CBMS-4 interface 1226 and performs an operation appropriate therefor . the

The CBMS-7 interface 1222 is an interface from the NEF 1202a in the SA 1202 to the NGF 1203a in the SM 1203, and carries information (for example, attribute information of a service guide) required to generate an event notification or a notification message so that the NGF 1203a can generate a notification message. the

The CBMS-3 interface 1225 is an interface used when a notification message transmitted from the NDAF 1203b in the SM 1203 is directly transmitted to the terminal 1208 via the broadcast network 1206 through the broadcast channel. This interface is used to transmit notification messages to one or more terminals. the

The CBMS-4 interface 1226 is an interface used when a notification message transmitted from the NDAF 1203b in the SM 1203 is directly transmitted to the terminal 1208 via the interactive network 1207 through a dedicated channel or through a broadcast channel provided in the interactive network 1207 . This interface is used to transmit notification messages to one or more terminals. the

The CBMS-6 interface 1224 a is an interface between the SM 1203 and the broadcast network 1206 for establishing a transmission path used in the SM 1203 in the broadcast network 1206 or a reception path for event information generated in the broadcast network 1206 . the

The X-3 interface 1224b is an interface for establishing a transmission path to be used between the SM 1203 and the interactive network 1207 . the

The CBMS-1 interface 1233 is an interface through which the control information of the broadcast network 1206 is delivered to the terminal 1208 . In DVB-H, a control signal channel called Program Specific Information/Service Information (PSI/SI) corresponds to this interface. the

The NEF 1202a controls the transfer of information necessary to generate a notification message to the NGF 1203a, and controls the transfer of information indicating the occurrence (if any) of a notification event to the NGF 1203a. The NGF 1203a controls to generate a notification message using information and events received from the NEF 1202a required for generating a notification message, or controls to generate a notification message when a notification event from the broadcast network 1206 is received via the NDAF 1203b, and controls to transmit the notification message to NDAF1203b. (i) when it needs to re-notify the start of the service, (ii) when it needs to transmit a new service guide when it receives a notification from CC 1201 indicating a change in service information, and (iii) when a specific service has occurred in the broadcast network 1206 When an event occurs, the NGF1203a can generate a notification message. the

The NDAF 1203b controls the transmission of notification messages via the CBMS-3 interface 1225 or the CBMS-4 interface 1226 . In addition, upon receiving information indicating a change in a specific mobile broadcast service due to the wireless network environment (for example, information indicating rate control or service impossibility) from the broadcast network 1206, the NDAF 1203b transmits a corresponding notification event to the NGF 1203a. the

Compared with the entities of FIG. 2 , network entities corresponding to notification messages are equivalent to those in OMA and CBMS in terms of definition and name, so descriptions thereof are not provided here. For the interface, NT-6 corresponds to CBMS-4, and NT-5 corresponds to CBMS-3. the

FIG. 13 illustrates a CBMS-based service purchase architecture corresponding to the OMA-based architecture of FIG. 3 . Table 19 gives the description of the entities in Figure 13. the

Table 19

logical subentity Which logical entity is it part of reference points involved describe encoded stream source service application CBMS-2 This entity outputs media streams (e.g., audio, video, data) to the broadcast network, using configuration parameters obtained from the service application configuration sub-entity content encryption service application CBMS-2 This entity is responsible for encrypting content streams. Content encryption and link encryption do not have to be used at the same time. link encryption broadcast network CBMS-2 The entity responsible for encrypting data streams at the link level. This type of encryption is relevant to the content of the service. Content encryption and link encryption do not have to be used at the same time. Business key generation and ECM/KSM generation service application or broadcast network CBMS-2 This entity generates service encryption keys for content or link services respectively. TEK is changed frequently. Service/Program Key Generation service application or broadcast network CBMS-7 This entity generates keys for service/program access. It is controlled by the Access Criteria/Policy Management sub-entity of Service Management. Service/program keys are exchanged with the Rights Issuing sub-entity in Service Management. IP-to-Section broadcast network Please refer to Table 5

Access Policy/Policy Management service management CBMS-7, CBMS-6 This entity can define services, programs and their lifetimes, and it packages the media stream packages and access criteria they contain as content. Purchasable items, such as service packs, can also be defined. Release of rights service management CBMS-3, CBMS-4, CBMS-6, CBMS-7 This entity supplies entitlement messages for transmission to the key management system agent of the terminal. This process may require access criteria, service/program keys, and results of a successful purchase transaction. The latter is managed by the Subscription Management sub-entity. booking management service management X-5 (optional) This entity manages the details of each end user's subscription. It can use the billing function of the interactive network via the X-5 reference point or other, and operate independently of the billing system. However, this billing function is out of the scope of this specification. Resource provisioning/scheduling service management Please refer to Table 3. This is used to configure KSM delivery Content/Service Decryption terminal CBMS-2 This entity decrypts the content/link traffic using the TEK provided by the Key Management System Proxy. Key Management System Proxy terminal CBMS-2, CBMS-3, CBMS-4 This entity receives and manages entitlement messages and keystream messages. If all criteria for entitlement are matched, the TEK is reconstructed and provided to the content/service decryption entity. content consumption entity terminal CBMS-2 An entity that processes received media streams; it may include facilities for buffering, synchronization, storage, and presentation of streamed content.

Among the entities in FIG. 13 and Table 19, entities necessary for the present invention include a "subscription management" entity, a "rights issuance" entity, and a "key management system agent" entity in the terminal. the

The functions of the "subscription management" entity and the "rights issuance" entity are mapped to the functions of BSP-M 301 in FIG. 3, and the "Key Management System Agent" entity is mapped to BSP-C 302 in FIG. the

FIG. 14 illustrates an architecture corresponding to the OMA-based architecture of FIG. 4 . Shown are signaling procedures corresponding to signaling procedures 402, 403, 405 and 408 between network entities described in FIG. 4 . That is, reference numerals 1450, 1460, 1470, and 1440 correspond to reference numerals 402, 408, 403, and 405 of FIG. 4 . the

Figures 15A-15D illustrate CBMS-based ESG data model fragments corresponding to those of Figures 5A-5D. However, the segment corresponding to the "purchased item" segment is omitted here because it is irrelevant to the present invention. The "Service" segment and the "Acquisition" segment correspond to the "Service" segment and the "Access" segment in FIGS. 5A to 5D , respectively. the

For the elements and attributes in the fragment, "Service Type (ServiceType)" corresponds to "Service Type (ServiceType)", "Access Type (AccessType)" corresponds to "Session Description (SessionDescription)", "Service Class (ServiceClass)" corresponds to "ComponentCharacteristic", and "NotificationReception" corresponds to "NotificationReception". That is, in FIGS. 15A to 15D , 'Notification Service (NotificationService)' may be defined as a type of a service type (ServiceType) in 'Service Type (ServiceType)'. When the "Access Type (AccessType)" in Fig. 5A to Fig. 5D includes the access information for the access notification message, the corresponding access message is expressed in "Session Description (SessionDescription)". Similar to the "Service Class" that specifies the notification message service class, use the element "ComponentCharacteristicType" to define the notification component type (NotificationComponentType) except for video, audio and files, thereby specifying the corresponding collection (Acquisition ) fragment's component type is Notification Message. the

Table 20A shows an exemplary XML schema for a newly defined notification component type (NotificationComponentType), and it has an element "NotificationType". the

Form 20A

The configuration shown in Table 20B is also possible. In Table 20B, a notification type (NotificationType) is defined as an element notification component type (NotificationComponentType), and a plurality of notification types (NotificationType) can be used. In addition, other elements that define the NotificationComponent can also be added. "esg:ComponentCharacteristicType" in Table 20B is a part indicating the characteristics of the basic component defined in the current DVB-CBMS ESG specification (ETSI TS102471), and it is like in the existing video component type (VideoComponentType) or audio component type (AudioComponentType ) as used in . the

Form 20B

Table 21A shows an example of a notification message subscription request message suitable for a CBMS network according to the present invention mapped to the messages of Table 7. Table 21B includes an embodiment that enables ServiceID-specific subscriptions in Table 15. In Table 21, for the notification message subscription request, the italicized part is added. the

Form 21A

Form 21B

Table 22 shows an example of a notification message unsubscribe request message, and a result obtained by mapping the unsubscribe messages of Table 9, Table 16, and Table 17 to a CBMS network. Referring to Table 22B, the requested notification message may be individually unsubscribed for each individual Service ID (ServicelD). When the specific service ID unsubscription (ServiceID-specific unsubscription) is not required, it may be an embodiment for unsubscribing all notifications of the "purchase item" (Purchaseitem) as shown in Table 22A. Additionally, when unsubscribing from general services, the user may not desire to unsubscribe from service-related notification messages. In this case, as shown in Table 22C, even when unsubscribing from the main service using the attribute "KeepSubscription", the user cannot unsubscribe from the notification message provided in association with the main service. the

Form 22A

Form 22B

Form 22C

7 and 8 are used even in the CBMS-based embodiment, and thus a detailed description thereof is omitted. the

FIG. 16 illustrates a CBMS-based ESG data model mapped to the OMA-based ESG data model of FIG. 9 and illustrates elements of the ESG data model described in FIG. 15 . Referring to FIG. 16, it should be noted that "Notification Component Type" 1603 is newly defined to indicate the collection fragment used for the notification message in the Component Characteristic. the

It can be understood from the above description that the present invention defines the notification message in the interaction channel, so that the notification message can be transmitted not only in the broadcast channel, but also in the interaction channel. In addition, the present invention provides a method of an auxiliary way of checking a service according to a service guide when there is a service or a notification message. In this way, subscription and unsubscription of corresponding notification messages can be performed. the

Although the invention has been shown and described with reference to a certain preferred embodiment of the invention, it should be understood by those skilled in the art that, without departing from the spirit and scope of the invention as defined by the appended claims, other Various changes in form and detail have been made therein.

Claims (27)

1. A method for providing a notification message in a transmitter of a mobile broadcast system supporting an interactive channel, the method comprising the steps of: (a) when a notification event occurs, the entity for managing the subscription information of the terminal generates the notification message, and generates at least one delivery request message including a destination address based on the subscription information of the terminal to request delivery of the generated A notification message, the subscription information includes receiving channel information for the terminal to receive the notification message, and the target address includes the receiving channel information for the terminal to receive the notification message; and (b) the entity for transmitting the notification message determines a channel on which the entity for transmitting the notification message is to transmit the notification message to the terminal based on the target address, and on the determined channel Send the notification message above. 2. The method of claim 1, wherein step (b) comprises: If the notification message is transmitted using the interaction channel, checking the address type of the terminal based on the target address; and Transmitting the notification message to the terminal through an interaction channel according to the address type. 3. The method of claim 1, wherein step (b) comprises: If a broadcast channel is used to transmit the notification message, checking a target session address of the broadcast channel based on the target address; and Transmitting the notification message to the terminal through a broadcast channel according to the target session address. 4. The method of claim 1, further comprising: said entity for managing subscription information of said terminal receives a message from said terminal requesting a subscription or purchase of said notification message; and Handling subscription or purchase request messages and storing subscription information for said terminal. 5. The method of claim 1, further comprising: said entity for managing subscription information of said terminal receives a message from said terminal requesting a subscription or purchase of a specific service notification message; and Handle subscription or purchase request messages and store corresponding services and subscription information for the terminal. 6. The method of claim 1, further comprising: said entity for managing subscription information of said terminal receives a message requesting unsubscription of notification messages for all services from said terminal; and Unsubscribe from notification messaging for all services of the terminal. 7. The method of claim 1, further comprising: said entity for managing subscription information of said terminal receives a message from said terminal requesting unsubscription of service-specific notification messages; and Unsubscribing from the transmission of said notification messages for the service for which unsubscribing has been requested. 8. The method of claim 1, wherein, for each terminal, the destination address includes channel information for transmitting the notification message and an address type based on a transmission channel. 9. A transmitter in a mobile broadcast system supporting interactive channels, the transmitter comprising: An entity for managing subscription information of a terminal, generating a notification message when a notification event occurs, and generating at least one delivery request message including a destination address based on the subscription information of the terminal, to request delivery of the generated notification message, the subscription information including receiving channel information for the terminal to receive the notification message, and the target address includes the receiving channel information for the terminal to receive the notification message; and an entity for determining a channel, for determining a channel on which the entity for determining a channel is to transmit the notification message to the terminal based on the target address, and transmit the notification message on the determined channel . 10. The transmitter of claim 9, wherein the entity for determining a channel operates as follows: If the notification message is transmitted using the interaction channel, checking the address type of the terminal based on the target address; and Transmitting the notification message to the terminal through an interaction channel according to the address type. 11. The transmitter of claim 9, wherein the entity for determining a channel operates as follows: If a broadcast channel is used to transmit the notification message, checking a target session address of the broadcast channel based on the target address; and Transmitting the notification message to the terminal through a broadcast channel according to the target session address. 12. The transmitter of claim 9, wherein the entity for managing subscription information for the terminal operates as follows: receiving a message from said terminal requesting to subscribe or purchase said notification message; and Handling subscription or purchase request messages and storing subscription information for said terminal. 13. The transmitter of claim 9, wherein the entity for managing subscription information of the terminal operates as follows: receiving a subscription or purchase request message for a specific service notification message from said terminal; and Handle subscription or purchase request messages and store corresponding services and subscription information for the terminal. 14. The transmitter of claim 9, wherein the entity for managing subscription information for the terminal operates as follows: Upon receiving a message requesting to unsubscribe from the notification message for all services from the terminal, unsubscribe notification message delivery for all services of the terminal. 15. The transmitter of claim 9, wherein the entity for managing subscription information for the terminal operates as follows: Upon receiving a message for requesting unsubscription of a specific service notification message from the terminal, unsubscribe from notification message transmission of the service for which unsubscription has been requested. 16. The transmitter of claim 9, wherein, for each terminal, the target address includes channel information for transmitting the notification message and an address type based on a transmission channel. 17. The transmitter according to claim 9, wherein said entity for managing subscription information of said terminal is a Notification Generation Function NTG and said entity for determining a channel is a Notification Distribution/Adaptation Function NTDA. 18. A method for receiving a notification message in a terminal of a mobile broadcast system supporting an interactive channel, the method comprising the steps of: Checking notification content from the service guide, checking service subscription/purchase information, transmitting a subscription request message of the notification message to an entity for managing subscription information of the terminal, the request message including reception channel information of the notification message; receiving a response message including verification information from said entity for managing subscription information of said terminal; and After the verification is completed, the notification message transmitted according to the transmission channel information is received. 19. The method of claim 18, wherein the subscription request message of the notification message includes service identification information, and subscription and purchase information of the notification message of the service. 20. The method of claim 18, further comprising: An unsubscribe request message of a notification message of all services is transmitted to the entity for managing the subscription information of the terminal. 21. The method of claim 18, further comprising: A message for requesting unsubscription of service-specific notification messages is transmitted to said entity for managing subscription information of said terminal. 22. A terminal in a mobile broadcast system supporting interactive channels, the terminal comprising: A first entity for checking notification content from a service guide, checking service subscription/purchase information, transmitting a subscription request message of a notification message to an entity for managing subscription information of a terminal, and receiving verification information in response thereto, the request message including receiving channel information of the notification message; and An entity for receiving said notification message transmitted according to the transmission channel information after the verification is completed. 23. The terminal of claim 22, wherein the subscription request message of the notification message includes service identification information, and subscription and purchase information of the notification message of the service. 24. The terminal of claim 22, wherein the first entity transmits an unsubscribe request message of a notification message of all services to the entity for managing subscription information of the terminal. 25. The terminal of claim 22, wherein the first entity transmits a message requesting unsubscription of service-specific notification messages to the entity for managing subscription information of the terminal. 26. A method for providing notification messages in a mobile broadcast system supporting an interactive channel, the method comprising: The terminal checks notification content from the service guide, checks service subscription/purchase information, and transmits a subscription request message of the notification message to a transmitter for managing subscription information of the terminal, the request message including reception channel information of the notification message; and The transmitter performs authentication according to the subscription request message, stores subscription information of the terminal, and transmits a notification message of a corresponding service based on a reception channel message of the notification message when a notification event occurs. 27. A mobile broadcast system supporting interactive channels, the system comprising: A terminal for checking notification contents from a service guide, checking service subscription/purchase information, transmitting a subscription request message of a notification message to a transmitter for managing subscription information of said terminal, said request message including receipt of said notification message channel information; and The transmitter is configured to store the subscription information of the terminal according to the subscription request message, and when a notification event occurs, transmit a notification message of a corresponding service to the terminal based on a receiving channel message of the notification message.

Images