RU2380856C2 - Device and method for notification message transmit/receive in broadcasting system, and system for this - Google Patents

Abstract

FIELD: information technologies.

SUBSTANCE: receiving device receives notification message from broadcasting system. Message analyser analyses notification message received through receiving device as per certain format. Controller determines that received notification message is the notification message which should be used by user or notification message which should be used by terminal on the basis of notification message content analysed using message analyser and executes operation according to determination result.

EFFECT: providing possibility to set clearly notification message formats and to work on the basis of message formats.

49 cl, 46 tbl, 9 dwg

Description

State of the art

FIELD OF THE INVENTION

The present invention generally relates to a device and method for transmitting / receiving messages in a broadcast system. More specifically, the present invention relates to a device and method for transmitting / receiving a notification message in a broadcast system, and a system for this.

State of the art

In general, broadcast services are intended to be provided to all users having terminals. Broadcasting services are classified into audio broadcasting services, such as broadcasting a radio broadcast that represents only an audio service, and video broadcasting services, such as television (TV), providing audio and video transmission services, and multimedia broadcasting services including transmission services audio, video and / or data. These broadcasting services are mainly based on analogue technologies, but today they are evolving into digital broadcasting services as a result of the rapid progress of communication technologies. In addition, broadcasting services are moving from existing tower-based broadcasting services to wired network-based multimedia broadcasting services providing high-definition high-speed data through wires, wired satellite multimedia broadcasting services, and wired-based multimedia broadcasting services and satellites.

The development of mobile communication technologies and broadcasting services has contributed to the provision of mobile broadcasting to users.

Figure 1 is a conceptual diagram of a general system for providing mobile broadcasting services.

The mobile terminal 104 may receive multimedia content provided by the content provider or service provider 105, and the service guide 101 for the provided service via broadcast channel 102 or interaction channel 103. Broadcast channel 102 includes digital video broadcasting (DVB), multimedia broadcast and multicast service according to the Third Generation Partnership Project (3GPP MBMS), and multicast broadcast and multicast service according to the Third Generation Partnership Project 2 (3GPP2 BCMCS), and may also include other broadcast technologies, such as digital multimedia broadcasting (DMB), digital broadcasting audio (DAB), etc. Interaction channel 103 may include networks capable of providing interactive services, including various mobile networks, such as code division multiple access (CDMA), general packet radio service (GPRS), and third-generation (3G) networks, and also a wireless local area network (WLAN). The content provider or service provider 105 may unidirectionally broadcast the service guide, high volume multimedia content, and the notification service to multiple terminals via broadcast channel 102, and can provide services via interaction channel 103 when an interaction service is required.

In a mobile broadcasting service system (hereinafter referred to as a “portable broadcasting system”), the networks of the content provider or service provider 105 must transmit a notification for transmitting or modifying the service manual and multimedia content to the user of the mobile terminal 104. In addition, the service providers of the portable broadcasting system also must have a notification function to provide messages transmitting public notifications, emergency, emergency notifications etc., the mobile terminal user.

Therefore, there is a need for clearly defining message formats used for notifications, and a method of working based on message formats. In addition, there is a need to enable the mobile terminal to efficiently process notification messages and provide these messages to the user.

SUMMARY OF THE INVENTION

Exemplary embodiments of the present invention solve at least the above problems and / or disadvantages and provide at least the advantages described below. Accordingly, an aspect of an exemplary embodiment of the present invention is to provide an apparatus and method for transmitting / receiving notification messages in a broadcast system, and a system for this.

Another aspect of an exemplary embodiment of the present invention is to provide an apparatus and method for generating notification messages in a broadcast system, and a system for this.

A further further aspect of an exemplary embodiment of the present invention is to provide an apparatus and method for receiving notification messages from a broadcast system, and a system for this.

According to one aspect of an exemplary embodiment of the present invention, there is provided a device for transmitting a message in a broadcast system. The device comprises a notification event function for receiving a notification indicating content change information provided from the content creating unit and generating a notification event message for generating a notification message; a notification generation function for generating a notification message that must be used by a user of a terminal designated to receive a notification message, or a notification message that must be used by a terminal using a notification event message from a notification event function; and a distribution / notification adaptation function for transmitting a notification message received from the notification generation function to the terminal via a specific network.

According to another aspect of an exemplary embodiment of the present invention, there is provided a message transmitting apparatus in a broadcast system. The device comprises a notification event function for receiving a notification indicating content change information provided from the content creating unit and generating a notification event message for generating a notification message; a notification generation function for generating a notification message using a notification event message received from the notification event function, wherein the notification message includes a NotificationType (Notification Type) indicating whether the notification message is a notification message to be used by a user of the terminal designated in order to receive a notification message, or a notification message that should be used by the terminal, NotificationVersion (Notification Version), I indicate the information version of the generated notification message, PresentationType indicating the presentation type of the notification message, UsageType indicating the use of SessionInformation in the notification message, EventType indicating the event through which the message is configured notifications, and a FilteringValue indicating the information for executing content previously stored in the terminal; and a distribution / notification adaptation function for receiving the notification message from the notification generation function and transmitting the received notification message to the terminal through the specific network.

According to a further another aspect of an exemplary embodiment of the present invention, there is provided a method for transmitting a message in a broadcast system. The method comprises the steps of receiving, by a notification event function, a notification indicating content change information provided from the content creating unit, generating a notification event for generating a notification message, and transmitting the generated notification event message to the notification generation function; receiving, through the function of generating notifications, a notification event message, generating a notification message that should be used by the user, or a notification message that should be used by the terminal, and transmitting the generated notification message to the notification distribution / adaptation function; and receiving, through the distribution / adaptation function of the notifications, a notification message and transmitting the received notification message to the terminal via a specific network.

According to yet another aspect of an exemplary embodiment of the present invention, a method for transmitting a message in a broadcast system is provided. The method comprises the steps of receiving, by a notification event function, a notification indicating content change information provided from the content creating unit, generating a notification event message to generate a notification message, and transmitting the generated notification event message to the notification generation function; generating, by the notification generation function, a notification message using the notification event message received from the notification event function, and transmitting the generated notification message to the notification distribution / adaptation function, wherein the notification message includes a NotificationType indicating that the notification message is a message A notification that should be used by the user, or a notification message that should be used by the terminal, PresentationType indicating type of representation of the notification message, the EventType, indicating it by a configured event notification message, and FilteringValue, indicating information for driving the performance of the content previously stored in the terminal; and receiving, through the distribution / adaptation function of the notifications, a notification message from the notification generation function and transmitting the received notification message to the terminal via a specific network.

According to yet another aspect of an exemplary embodiment of the present invention, there is provided a terminal apparatus for receiving a broadcast service from a broadcast system. The device comprises a receiver for receiving a notification message from a broadcast system; and a controller for determining whether the received notification message is a notification message that should be used by the user, or a notification message that should be used by the terminal, based on the contents of the notification message, and performing the operation according to the determination result.

According to yet another aspect of an exemplary embodiment of the present invention, there is provided a terminal apparatus for receiving a broadcast service from a broadcast system. The device comprises a receiver for receiving a notification message from a broadcast system; and a controller for determining whether the received notification message is a notification message that should be used by the user, or a notification message that should be used by the terminal, according to the NotificationType information of the notification message, controlling the operation of displaying the notification message according to PresentationType information of the notification message, UsageType verification of the notification message to access the session according to the use of the SessionInformation of the notification message, information verification Notificat ionVersion notification messages to determine if the received notification message is a new received notification message, check the EventType of the notification message to perform the appropriate operation according to the type of event of the received notification message, and check the FilteringValue of the notification message to provide the user with a FilteringValue of which FilteringValue of previously saved content.

According to yet another exemplary embodiment of the present invention, there is provided a method comprising the steps of receiving, by a terminal, a notification message from a broadcast system; determining whether the notification message is a notification message that should be used by the user or a notification message that should be used by the terminal; and performing any of the PresentationType verification operation of the notification message if the notification message is a notification message that should be used by the user, and the SessionInformation verification operation of the notification message to access the corresponding session if the notification message is a notification message that should be used by the terminal.

According to yet another exemplary embodiment of the present invention, there is provided a method comprising the steps of receiving, by a terminal, a notification message from a broadcast system; checking the NotificationVersion of the notification message to determine whether the received notification message is a new received notification message; if the received notification message is a new received notification message, check the NotificationType of the notification message to determine whether the received notification message is a notification message to be used by the user or a notification message to be used by the terminal; checking EventType notification messages to detect the contents included in the notification message; checking PresentationType of the notification message if the received notification message is a notification message to be used by the user; performing the operation of displaying the notification message according to the PresentationType of the notification message; and checking the FilteringValue of the received notification message and providing the user with content whose FilteringValue is equal to FilteringValue from the content previously stored in the terminal.

According to yet another aspect of an exemplary embodiment of the present invention, there is provided a broadcast system comprising a notification message transmitter for generating a notification message and transmitting a notification message to a terminal when receiving a notification event message generated due to content change information provided from the content creating unit, or change information from a broadcast system related to content transfer ; and a terminal for receiving the transmitted notification message, determining whether the notification message is a notification message to be used by the user or a notification message to be used by the terminal, checking the PresentationType of the notification message if the notification message is a notification message to be used by the user , and checking the SessionInformation of the notification message to access the corresponding session if the analyzed message is not omleniya a notification message to be used by the terminal.

According to yet another aspect of an exemplary embodiment of the present invention, a method for providing a broadcast service is provided. The method comprises the steps of receiving a notification event message generated as a result of content change information provided from a content creation unit or change information of a broadcast system related to content transfer; generating a notification message that must be used by the user of the terminal designated to use the notification message, or a notification message that must be used by the terminal using the generated notification event message; transmitting the generated notification message to the terminal through a specific network; receiving a transmitted notification message; determining whether the notification message is a notification message that should be used by the user or a notification message that should be used by the terminal; and performing one of the verification operation PresentationType of the notification message if the notification message is a notification message to be used by the user, and the SessionInformation verification operation of the notification message to access the corresponding session if the notification message is a notification message that should be used by the terminal.

Other aspects, advantages, and pronounced features of the invention should become apparent to those skilled in the art from the following detailed description, which, when taken in conjunction with the accompanying drawings, discloses exemplary embodiments of the invention.

Brief Description of the Drawings

The above and other aspects, features and advantages of the present invention should become more apparent from the following detailed description, taken in conjunction with the accompanying drawings, of which:

Figure 1 is a conceptual diagram of a general system for providing mobile broadcasting services;

FIG. 2 is a block diagram illustrating an architecture for transmitting a notification message in a portable broadcast system according to an embodiment of the present invention;

FIG. 3 is a diagram illustrating a notification message diagram table according to the first and second embodiments of the present invention; FIG.

4 is a block diagram illustrating a structure of a terminal according to the first and second embodiments of the present invention;

5 is a flowchart illustrating the reception of a notification message in a terminal according to a first embodiment of the present invention;

6 is a flowchart illustrating a process for generating a notification message in a portable broadcast system according to a first embodiment of the present invention;

7 is a flowchart illustrating a process for receiving a notification message in a terminal according to a second embodiment of the present invention;

8 is a flowchart illustrating a notification generation process in a portable broadcast system according to a second embodiment of the present invention;

FIG. 9 is a diagram illustrating an example process in which, upon receiving a notification message used for an advertising purpose or the like, according to a fourth embodiment of the invention, the terminal provides previously stored advertising content or data to a user.

In all the drawings, the same reference numbers of the drawings should be understood to mean the same elements, features and structures.

Detailed Description of Exemplary Embodiments

Aspects indicated in the description, such as a detailed structure and elements, are provided in order to help in a comprehensive understanding of embodiments of the invention, and are merely exemplary. Therefore, those skilled in the art should recognize that various changes and modifications to the embodiments described herein can be made without departing from the scope and spirit of the invention. In addition, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

Although the object names defined in the BCAST of the Open Mobile Alliance (OMA BCAST), a standard group for mobile terminal applications, are used identically for convenience herein, this does not limit the scope of the present invention, and exemplary embodiments of the present invention can be applied to any system with a similar level of technology based on the Internet Protocol (IP).

2 is a block diagram illustrating an architecture for transmitting a notification message in a portable broadcast system according to an embodiment of the present invention.

The content creation unit 201 (or content provider) is a broadcast service provider (hereinafter referred to as a BCAST service), and the BCAST service may include a traditional audio / video broadcast service, a file download service (music files or data files) etc. The content creation unit 201, if there is any problem in providing the BCAST service or any changes in the service content, reports a change to the notification event function (NTE) 202a in the BCAST service application 202. The notification event function 202a transmits a message about notification events to the notification generation function (NGF) 204a based on the received event.

The BCAST service application 202 has a data receiving function for the BCAST service provided from the content creating unit 201, processing received data in a form suitable for the BCAST network, and generating the BCAST service data. The BCAST service application 202 also has the function of generating the standardized metadata needed to guide portable broadcasts. In addition, the BCAST service application 202 receives the change in the content or BCAST service notified by the content creation unit 201 and notifies the change to the notification generation function 204a located in the BCAST subscription control unit 204.

The BCAST service distribution / adaptation unit 203 has the function of establishing a unidirectional channel for transmitting BCAST service data provided from the BCAST service application 202, a transmission schedule determination function for the BCAST service, and a guide generation function for portable broadcasting. The BCAST service distribution / adaptation unit 203 is connected to a broadcast distribution system (BDS) 206 capable of providing a broadcast service, and to an interaction network 207 that supports interaction communication. In addition, the BCAST service distribution / adaptation unit 203 including the notification distribution / adaptation function (NTDA) 203a receives a notification message from the BCAST subscription management unit 204 and transmits a notification message to one user or multiple users via BDS 206 or network 207 interactions. The BCAST service distribution / adaptation unit 203 has the session information required by the notification generation function 204a to generate notification messages for the terminals, and the notification distribution / adaptation function 203a transmits the session information to the notification generation function 204a.

The BCAST subscription management unit 204 manages service provisioning information, such as subscriber information for receiving the BCAST service, and information indicating whether the subscriber has acquired related content, and device information for receiving the BCAST service, i.e. terminal 208 for receiving a BCAST service. In particular, the BCAST subscription management unit 204 includes a notification generation function 204a. Therefore, when an event indicating the addition or change of a new function associated with the BCAST service occurred in the content creation unit 201 and the BDS 206, the notification generation function 204a receives a notification event message including information about the event that has occurred and generates a notification message according to him. In addition, when an event such as a change in the BCAST service spontaneously occurs in the BCAST subscription control unit 204, the BCAST subscription control unit 204 internally delivers the corresponding event to the notification function 204a to generate a notification message.

The BDS service distribution unit 205 has the function of distributing all received BCAST services through a broadcast channel or an interaction channel, and is an entity that may or may not exist, according to the type implemented by BDS 206.

BDS 206 is a network for transmitting BCAST services, and it can be, for example, DVB-H, 3GPP MBMS or 3GPP2 BCMCS. In addition, if there is a change in broadcast information related to the transmission of content when transmitting a particular BCAST service, if an X-1 interface 231 or BDS service distribution unit 205 exists, the BDS 206 notifies the change to the distribution / adaptation unit 203 BCAST services through NT-B1 interface 224.

The interaction network 207 transmits BCAST services on a one-to-one basis, or interactively exchanges control information and additional information related to receiving BCAST services, and may be, for example, an existing cellular network.

A terminal 208, a terminal capable of receiving a BCAST service, has a possible function of accessing a cellular network according to its characteristics. This document assumes terminal 208 is a terminal capable of accessing a cellular network. The terminal 208 receives the notification message transmitted via the NT-5 interface 225 using the client notification function (NTC) 208a, and performs the corresponding operation according to the received notification message. Alternatively, the terminal 208 receives the notification message transmitted via the NT-6 interface 226 and performs the corresponding operation according to the received notification message. The structure of terminal 208 is described in detail herein later with reference to FIG. 3.

The following is a description of the interfaces between the block elements of a portable broadcast system.

The NT-1 interface 221, the interface between the notification event function 202a located in the BCAST service application 202 and the content creation unit 201, is used to deliver the corresponding notification event to the notification event function 202a when an event requiring notification is generated in the block 101 content creation.

The NT-3 interface 222, the interface from the notification event function 202a located in the BCAST service application 202 to the notification generation function 204a of the BCAST subscription control unit 204, delivers the information required to notify the event or to generate a notification message, so that the notification generating function 204a can generate a notification message.

The NT-4 interface 223 is the interface between the notification generation function 204a located in the BCAST subscription control unit 204 and the notification distribution / adaptation function 203a of the BCAST service distribution / adaptation block 203. The NT-4 interface 223 is used to transmit the notification message to the notification distribution / adaptation function 203a to transmit the notification message generated in the notification generation function 204a to the BDS 206 or the interaction network 207, or is used by the notification distribution / adaptation function 203a to to send a notification message for an event that occurred in the BDS 206.

The NT-5 interface 225, an interface used when a notification message provided from the notification distribution / adaptation function 203a of the BCAST service distribution / adaptation block 203, is directly transmitted to the terminal 208 via a broadcast channel through the BDS 206, is used to transmit the notification message to one or multiple terminals.

NT-6 interface 226, an interface used when a notification message transmitted from the notification distribution / adaptation function 203a of the BCAST service distribution / adaptation block 203 is directly delivered to the terminal 208 via a dedicated channel to the terminal 208 via the interaction network 207 or the broadcast channel provided by the interaction network 207 is used to transmit a notification message to one or a plurality of terminals 208.

The NT-B1 interface 224 is an interface between the BCAST service distribution / adaptation unit 203 and the BDS service distribution unit 205 used as a transmission path to be used by the BCAST service distribution / adaptation unit 203 in the BDS 206, or as a reception path for event information generated in BDS 206. The NT-B1 interface 224 serves to transmit a notification event message generated by the interaction network 207 to the BCAST service distribution / adaptation unit 203. Those. the notification distribution / adaptation function 203a of the BCAST service distribution / adaptation unit 203 transmits an event message received from the BDS 206 or the interaction network 207 via the NT-B1 interface 224 to the notification function 204a via the NT-4 interface 223.

The X-1 interface 231 is the interface used to establish the transmission path that the BDS 206 should use in the interaction network 207 by the BCAST service distribution / adaptation unit 203 when the BDS service distribution unit 205 is not available. However, when the unit A BDS service distribution 205 exists, an X-1 interface 231 is used as an interface between the BDS 206 and the BDS service distribution unit 205 to notify that an event has occurred in the BDS 206.

The X-2 interface 232 is an interface used to establish the transmission path that the BCAST service distribution / adaptation unit 203 should use in the interaction network 207 when the BDS service distribution unit 205 is not available. However, when the BDS distribution unit 205 -services exist, the X-2 interface 232 is used as an interface between the BDS 206 and the interaction network 207 to establish a unidirectional channel in which the notification message should be used in the interaction network 207, as well as to transmit the notification message .

The X-3 interface 233, the interface between the BDS 206 and the terminal 208, is used for the BCAST service or all messages transmitted via the broadcast channel.

The X-4 interface 234 is a broadcast channel interface between the BDS service distribution unit 205 and the terminal 208.

The X-5 interface 235 is the interface of the communication channel between the BDS service distribution unit 205 and the terminal 208.

The X-6 interface 236 is an interaction interface through which the interaction network 207 can transmit control information associated with the BCAST service.

The notification event function 202a has a function of providing information required to generate a notification message to the notification generation function 204a, and upon detecting the occurrence of a notification requiring event, provides event information to the notification generation function 204a. The notification generating function 204a generates a notification message using the information and event required to generate the notification message received from the notification event function 202a. When the notification generation function 204a receives a notification event from the BDS 206 by the notification distribution / adaptation function 203a, it generates a notification message and transmits a notification message to the notification distribution / adaptation function 203a.

In the process of generating the notification message, if there is a need to indicate the start of the service, the notification event function 202a receives a notification indicating a change in the service information from the content creation unit 201. Accordingly, one case is specified when there is a need to transmit a new portable broadcast guide, and another case when a specific event occurs in the BDS 206.

The notification distribution / adaptation function 203a serves to transmit the notification message via the NT-5 interface 225 or the NT-6 interface 226. When the notification distribution / adaptation function 203a receives from the BDS 206 a change in information on a particular portable broadcast service, it delivers the corresponding notification event to the notification generation function 204a via the NT-4 interface 223. An example of changing information about a particular portable broadcast service is information indicating a speed adjustment and data transmission due to the wireless network environment, or information indicating the unavailability of the service. 2, a notification generation function 204a and a notification distribution / adaptation function 203a are referred to as a “notification message transmitter”.

In the description below, an embodiment in which the terminal performs the corresponding operation according to the notification message received from the portable broadcast system is set as the first embodiment, and an embodiment in which the terminal checks the version information of the received notification message and performs the corresponding operation according to the version information, is defined as the second embodiment.

3 is a diagram illustrating a table of a notification message scheme according to the first and second exemplary embodiments of the present invention.

Referring to FIG. 3, “Name” 301 indicates the names of the element value and attribute value constituting the corresponding message.

A “type” 302 indicates whether the corresponding name corresponds to an element value or an attribute value. The value of an element has the values E1, E2, E3, and E4 in three forms: E1 means the value of the top element for the entire message, E2 means the value of the element E1, E3 means the value of the element E2, and E4 means the value of the element E3. The attribute value is indicated by A, and A means the attribute value of the corresponding element. For example, A according to E1 means the value of the attribute E1.

A “category” 303 is used to indicate whether the corresponding element value or attribute value is mandatory, and has a value of M if the value is mandatory and a value of O if the value is optional.

The "number of elements" 304 means the relationship between the elements, and has the meanings "0", "0 ... 1", "1", "0 ... N", "1 ... N", where 0 means an optional relationship, 1 means a mandatory relationship, and N means the possibility of having multiple values. For example, "0 ... N" means the possibility that there is no corresponding element value or that there are N corresponding element values.

Description 305 defines the meaning of the corresponding value of an element or attribute.

With reference to tables 1-5, the following is a description of the entire scheme for a notification message according to an embodiment of the present invention.

Tables 1-5 illustrate the complete notification message scheme. As illustrated, the data types of all element values and attribute values of a schema according to an embodiment of the present invention can be defined in various ways according to application.

Tables 1-5 are separated from one table for convenience, and the definition of the elements in each table follows the definition from table 1.

Table 1 room Name Type of Category Amount of elements Description 501 Notification E1 O 0 ... N Snippet of notification message.
Contains the following attributes and elements.
Attributes:
ID
NotificationType
Validity
Items:
Name
Description
PresentationType
ExtensionURL
Sessioninformation
Mediainformation 502 ID A M one The identifier of the notification message. 503 NotificationType A M one Notification Type:
if 0, UserUse (user application)
if 1, TerminalUse (application by the terminal)
ServiceProvider Defined allowed. 504 Validity A O 0 ... 1 Allowed fragment time. 505 Name E2 M 1 ... N The title of the notification fragment.
Contains the following attribute:
Lang 506 Lang A O 0 ... 1 Language 507 Description E2 M 1 ... N The content or description of the notification message. 508 Lang A O 0 ... 1 Language.

Notification 501 indicates the corresponding fragment of the notification message and includes the values of the attributes ID (Identifier) 502, NotificationType 503 and Validity 504 and the values of the subordinate elements Name 505 and Description 507 in table 1, PresentationType 509 in the table 2, ExtensionURL (Add-on URL) 510 and SessionInformation 511 in Table 3, and MediaInformation 523 in Table 4. The attribute values ID 502, NotificationType 503 and Validity 504, as well as the values of the Name 505, Description 507, PresentationType 509, and ExtensionURL 510 in the notification message are typically used For each notification message. Notification 501 may not include SessionInformation 511 and MediaInformation 523 according to the use of the notification message.

ID 502, a unique identifier for the notification message fragment, is a required element. Corresponding identifiers help distinguish stored notification messages.

NotificationType 503 indicates what type or application of the notification message indicates the application for the user (hereinafter referred to as "user application"), the application for the terminal (hereinafter referred to as "terminal application") or other application, and is a required element. If the corresponding value is 0, it indicates the user application, and if the corresponding value is 1, it indicates the application by the terminal. In addition, NotificationType 503 can set various values according to the purpose of the service provider.

Validity 504 indicates the valid time of the notification message and is optional. Therefore, if the time set in Validity 504 expires, the notification message stored in the terminal is deleted.

Name 505 indicates the title or name of the notification message and is a required element. It can be set in various languages.

Lang 506, the attribute value for Name 505, indicates the language of the content written in Name 505, and is an optional value. If the Lang 506 does not matter, it is assigned a default value, and the default value can indicate the language in the corresponding service area or English.

Description 507 is the actual content of the message included in the notification message or part of the message description. It can be specified in various languages and is required.

Lang 508, the attribute value for Description 507, indicates the language of the content written in Description 507, and is an optional value. If the Lang 508 does not matter, it is assigned a default value, and the default value can indicate the language in the corresponding service area or English.

table 2 509 PresentationType E2 M one Specifies the type of message presentation.
PresentationType = 0. The terminal immediately displays a notification message on the screen when it is received.
PresentationType = 1. The terminal stores the notification message in a storage device so that the user can check it later. (Default).
PresentationType = 2. The terminal displays a notification message for the currently running service in an overlapping manner.
If necessary, an optional PresentationType can be specified.

In Table 2, PresentationType 509 specifies the type of notification presentation and is a required value. The presentation type indicates whether the terminal should display the corresponding message on the display after giving priority to the notification message and stop all services, save the contents of the message to the specified device, i.e. to the storage device, or to block the notification message on the current service or content being received before being displayed. PresentationType 509 can be set in various types according to the purpose of the service provider.

For example, if PresentationType is set to 0, the terminal receiving the notification message provides a notification message to the user when the message is received. If PresentationType is set to 1, the terminal stores the received notification message in the storage device, and then provides the notification message to the user upon user request. In addition, if PresentationType is set to 2, the terminal blocks the notification message for the service currently provided through the display to the user.

Table 3 510 ExtensionURL E2 O 0 ... N URL for more information. 511 Sessioninformation E2 O 0 ... N Session information by data.
Attributes:
ValidFrom
Validto
Usagetype
Items:
DeliverySession
TransportObjectID
Fragment
AlternativeURI 512 ValidFrom A O 0 ... 1 Session Start Time. 513 Validto A O 0 ... 1 Session End Time. 514 Usagetype A O 0 ... 1 The type of session use (e.g., service manual, file delivery, etc.). 515 DeliverySession E3 M one Session information on delivery content.
Attributes:
Sourceip
TransportSessionID 516 Sourceip A M one The IP address of the source to be transmitted. 517 TransportSessionID A M one The identifier of the session to be transmitted. 518 TransportObjectID E3 O 0 ... N The identifier of the transfer object.

In Table 3, ExtensionURL 510 indicates the URL of the service or content server for additional information on the notification message and is an optional value.

SessionInformation 511 indicates session information for receiving data and is an optional value. SessionInformation 511 is session information where there is an appropriate service guide or there are files and contents when the service guide is updated or the file or content is received. SessionInformation 511 has attribute values ValidFrom (Valid from) 512, ValidTo (Valid until) 513 and UsageType 514 and the values of DeliverySession elements 515 and TransportObjectID (Transport object identifier) 518 in Table 3 and Fragment 519 and AlternativeURI ( Alternate URI) 522 in Table 4 as its subordinate element values.

ValidFrom 512 indicates the start time when SessionInformation 511 is valid, and is an optional value.

ValidTo 513 indicates the end time when SessionInformation 511 is valid, and is an optional value.

UsageType 514 indicates the usage type of SessionInformation 511, i.e. using session information included in the notification message. UsageType 514 indicates the application, either to update the service manual or to receive files, and can be set in various types according to the purpose of the service provider.

DeliverySession 515 indicates the position value for the session where an object, such as a service manual or file, should actually be transmitted, and has the values of the SourceIP 516 and TransportSessionID (Transportation Session Identifier) 517 attributes.

SourceIP 516, the IP address of the corresponding transmission session, is available for both broadcast and multicast.

TransportSessionID 517 has an identifier value for the transmission session.

TransportObjectID 518 is the unique identifier for the object being transferred during the session.

Table 4 519 Fragment E3 O 0 ... N Information of the fragment of the transmitted object.
Attributes:
Fragmentid
Fragmentmentersion 520 Fragmentid A O 0 ... 1 The fragment identifier value. 521 Fragmentmentersion A O 0 ... 1 Fragment version information. 522 AlternativeURI E3 O 0 ... 1 An alternate URI that accepts the transmitted object. 523 Mediainformation E2 O 0 ... 1 Multimedia information for generating a multimedia notification message.
Items:
Picture
Video
Audio 524 Picture E3 O 0 ... N Image information.
Attributes:
Mimetype
Pictureuri 525 Mimetype A O 0 ... 1 MIME type. 526 Pictureuri A O 0 ... 1 URI indicating the position of the image. 527 Video E3 O 0 ... N Image information.
Attributes:
Mimetype
VideoURI

In table 4, the Fragment 519, which is the fragment information of the transmitted object, indicates the updated information of the particular fragment for the service guide and allows the terminal to check the corresponding identifier and version information, receive only the updated fragment and save the received fragment. Fragment 519 and its subordinate attributes are required only when the notification message is used to notify you of an update to the service guide, and are not used when the notification message is used for another purpose.

FragmentID 520 is the value of the unique identifier of the fragment to be received.

FragmentVersion (Fragment Version) 521 indicates version information of a fragment to be received, and for a fragment having the same FragmentID, the corresponding version information is checked to determine if the terminal has a FragmentID corresponding to the latest version. If there is the latest version in the session, the terminal takes the value of the latest version from the session and stores the accepted version value.

AlternativeURI 522 represents the value of the URI address with the corresponding object and is provided if the transmission through the session is unsuccessful, or if there is a need for reception not on the broadcast channel, but on the interaction channel. The terminal can access the position of the corresponding URI address through the interaction channel and receive the desired transmitted object.

MediaInformation 523 indicates multimedia information for generating a notification message and is required for a notification message configured with multimedia. MediaInformation 523 consists of the values of the subordinate elements Picture (Video), Video (Video) and Audio (Audio).

Picture 524 indicates picture or image information, MIMEtype 525 indicates the type of Internet Multipurpose Email Extensions (MIME) for the corresponding moving image, PictureURI 526 is a URI address indicating the position of the picture or image, and Video 527 indicates information about the moving image. “Image position” means the position of a particular server when the corresponding image exists on a particular server, instead of including transmission notifications in the message.

Table 5 528 Mimetype A O 0 ... 1 MIME type. 529 VideoURI A O 0 ... 1 URI indicating the position of the video. 530 Audio E3 O 0 ... N Image information.
Attributes:
Mimetype
AudioURI 531 Mimetype A O 0 ... 1 MIME type. 532 AudioURI A O 0 ... 1 A URI indicating the position of the audio.

In Table 5, the MIMEtype 528 indicates the MIME type for the corresponding moving image, and VideoURI 529 is the URI address indicating the position of the moving image. “Moving image position” means the position of a specific server when a corresponding moving image exists on a specific server, instead of including a transmission notification in the message.

Audio 530 indicates information on audio, music, and notification sounds. MIMEtype 531 indicates the MIME type for the corresponding audio. AudioURI (Audio URI) 532 is a URI address indicating the position of the audio. “Audio position” means the position of a specific server when the corresponding audio exists on a specific server, instead of including transmission notifications in the message.

Table 6 and table 7 illustrate a message format configured with text, which is a notification message scheme used for a user application according to a first embodiment of the present invention. The definition of each element in table 6 and table 7 is identical to the definition in table 1, and a detailed description of the same blocks as the blocks in tables 1-5 is omitted. For convenience, table 6 and table 7 are separated from one table.

Table 6 room Name Type of Category Amount of elements Description 601 Notification E1 O 0 ... N Snippet of notification message.
Contains the following attributes and elements.
Attributes:
ID
NotificationType
Validity
Items:
Name
Description
PresentationType
ExtensionURL 602 ID A M one The identifier of the notification message. 603 NotificationType A M one Notification Type:
if 0, UserUse
if 1, TerminalUse
ServiceProvider Defined allowed. 604 Validity A O 0 ... 1 Allowed fragment time. 605 Name E2 M 1 ... N The title of the notification fragment.
Contains the following attribute:
Lang 606 Lang A O 0 ... 1 Language. 607 Description E2 M 1 ... N The content or description of the notification message. 608 Lang A O 0 ... 1 Language.

Table 7 609 PresentationType E2 M one Specifies the type of message presentation.
PresentationType = 0. The terminal immediately displays a notification message on the screen when it is received.
PresentationType = 1. The terminal stores the notification message in a storage device so that the user can check it later. (Default).
PresentationType = 2. The terminal displays a notification message for the currently running service in an overlapping manner.
If necessary, an optional PresentationType can be specified. 610 ExtensionURL E2 O 0 ... N URL for more information.

A notification message for user use shown in Table 6 and Table 7, proposed in an exemplary embodiment of the present invention, can be used to receive public notifications, advertising messages, billing information and billing information for a service provider or content provider. ExtensionURL 610, acting as a CallbackURL (callback URL), can receive additional information through an interaction channel.

The corresponding notification message includes the attribute values ID 602, NotificationType 603 and Validity 604 and the values of the Name elements 605, Description 607, PresentationType 609 and ExtensionURL 610. A description of all the values of the sub attributes and the values of the sub elements composing the notification message shown in Table 6 and table 7, identical to the description in tables 1-5.

With reference to Tables 8-10, a description will now be made of a message format configured with multimedia, which is a notification message scheme used for a user application according to a first embodiment of the present invention. For convenience, tables 8-10 are divided from one table. The definition of each element in tables 8-10 is identical to the definition in table 1, and a detailed description of the same blocks as the blocks in tables 1-5 is omitted.

Table 8 room Name Type of Category Amount of elements Description 701 Notification E1 O 0 ... N Snippet of notification message.
Contains the following attributes and elements.
Attributes:
ID
NotificationType
Validity
Items:
Name
Description
PresentationType
ExtensionURL
Mediainformation 702 ID A M one The identifier of the notification message. 703 Notification type A M one Notification Type:
if 0, UserUse
if 1, TerminalUse
ServiceProvider Defined allowed. 704 Validity A O 0 ... 1 Allowed fragment time. 705 Name E2 M 1 ... N The title of the notification fragment.
Contains the following attribute:
Lang 706 Lang A O 0 ... 1 Language. 707 Description E2 M 1 ... N The content or description of the notification message. 708 Lang A O 0 ... 1 Language.

Table 9 709 PresentationType E2 M one Specifies the type of message presentation.
PresentationType = 0. The terminal immediately displays a notification message on the screen when it is received.
PresentationType = 1. The terminal stores the notification message in a storage device so that the user can check it later. (Default).
PresentationType = 2. The terminal displays a notification message for the currently running service in an overlapping manner.
If necessary, an optional PresentationType can be specified. 710 ExtensionURL E2 O 0 ... N URL for more information. 723 Mediainformation E2 O 0 ... 1 Multimedia information for generating a multimedia notification message.
Items:
Picture
Video
Audio 724 Picture E3 O 0 ... N Image information.
Attributes:
Mimetype
Pictureuri 725 Mimetype A O 0 ... 1 MIME type. 726 Pictureuri A O 0 ... 1 URI indicating the position of the image.

Table 10 727 Video E3 O 0 ... N Image information.
Attributes:
Mimetype
VideoURI 728 Mimetype A O 0 ... 1 MIME type. 729 VideoURI A O 0 ... 1 URI indicating the position of the video. 730 Audio E3 O 0 ... N Image information.
Attributes:
Mimetype
AudioURI 731 Mimetype A O 0 ... 1 MIME type. 732 AudioURI A O 0 ... 1 A URI indicating the position of the audio.

Tables 8-10 illustrate a message format configured with multimedia, which is a notification message scheme used for a user application according to a first embodiment of the present invention. The user notification message shown in Tables 8-10 of the exemplary embodiment of the present invention allows the message to be configured using various multimedia files, such as an image, a moving image, audio, etc., and may be different. used as an advertising message on the service and content and a public good message, such as searching for a missing child. The notification message in Tables 8-10 includes the attribute values ID 702, NotificationType 703, and Validity 704 and the values of the Name 705, Description 707, PresentationType 709, ExtensionURL 710, and MediaInformation 723 elements. Description of all subordinate attribute values and sub-element values that make up the message the notice shown in tables 8-10 is identical to the description in tables 1-5.

With reference to tables 11-13, the following describes a message format including session information, which is a notification message scheme used for use by a terminal according to a first embodiment of the present invention. For convenience, tables 11-13 are separated from one table for convenience, and the definition of the elements in each table follows the definition of tables 1-5.

Table 11 room Name Type of Category Amount of elements Description 801 Notification E1 O 0 ... N Snippet of notification message.
Contains the following attributes and elements.
Attributes:
ID
NotificationType
Validity
Items:
Name
Description
PresentationType
ExtensionURL
Sessioninformation 802 ID A M one The identifier of the notification message. 803 Notification type A M one Notification Type:
if 0, UserUse
if 1, TerminalUse
ServiceProvider Defined allowed. 804 Validity A O 0 ... 1 Allowed fragment time. 805 Name E2 M 1 ... N The title of the notification fragment.
Contains the following attribute:
Lang 806 Lang A O 0 ... 1 Language. 807 Description E2 M 1 ... N The content or description of the notification message. 808 Lang A O 0 ... 1 Language.

Table 12 809 PresentationType E2 M one Specifies the type of message presentation.
PresentationType = 0. The terminal immediately displays a notification message on the screen when it is received.
PresentationType = 1. The terminal stores the notification message in a storage device so that the user can check it later. (Default).
PresentationType = 2. The terminal displays a notification message for the currently running service in an overlapping manner.
If necessary, an optional PresentationType can be specified. 810 ExtensionURL E2 0 0 ... N URL for more information. 811 Sessioninformation E2 O 0 ... N Session information by data.
Attributes:
ValidFrom
Validto
Usagetype
Items:
DeliverySession
TransportObjectID
Fragment
AlternativeURI 812 ValidFrom A O 0 ... 1 Session Start Time. 813 Validto A O 0 ... 1 Session End Time. 814 Usagetype A O 0 ... 1 The type of session use (e.g., service manual, file delivery, etc.).

Table 13 815 DeliverySession E3 M one Session information on delivery content.
Attributes:
Sourceip
TransportSessionID 816 Sourceip A M one The IP address of the source to be transmitted. 817 TransportSessionID A M one The identifier of the session to be transmitted. 818 TransportObjectID E3 O 0 ... N The identifier of the transfer object. 819 Fragment E3 O 0 ... N Information of the fragment of the transmitted object.
Attributes:
Fragmentid
Fragmentmentersion 820 Fragmentid A O 0 ... 1 The fragment identifier value. 821 Fragmentmentersion A O 0 ... 1 Fragment version information. 822 AlternativeURI A O 0 ... 1

Tables 11-13 illustrate a message format including session information, which is a notification message scheme used for use by a terminal according to a first embodiment of the present invention. A typical application of a notification message used for use by a terminal recorded in Tables 11-13 is to provide update information of a service manual to the terminal in order to help the terminal maintain the updated service manual.

In addition, the notification message scheme in Tables 11-13 can be used in different ways to start a service or content, start a file download, and deliver a multimedia notification message transmitted through a separate session.

Although it is indicated that a typical application of a notification message is to provide update information of a service manual to a terminal, applications other than the above applications may replace a typical application.

For a single session, a portable broadcast system generally opens a session with a multicast address to transmit content, and transmits the corresponding content to the terminal. In this case, when the terminal is already receiving the content service from the portable broadcast system using a specific session, another separate session, different from the previously established session, is called a separate session.

The notification message for use by the terminal shown in Tables 11-13 proposed in the first embodiment of the present invention includes the values of the attributes ID 802, NotificationType 803 and Validity 804 and the values of the elements Name 805, Description 807, PresentationType 809, ExtensionURL 810 and SessionInformation 811. The description of all the values of the subordinate attributes and the values of the subelements making up the notification message shown in tables 11-13 is identical to the description in tables 1-5.

4 is a block diagram illustrating a structure of a terminal according to the first and second embodiments of the present invention. In a portable broadcast system to which embodiments of the present invention are applied, the terminal 208 has the conceptual structure shown in FIG. 2, but it can also have the actual logical structure shown in FIG. 4.

The receiver 400 receives the notification message from the portable broadcast system and provides the received notification message to the message analyzer 402.

The message analyzer 402 analyzes the notification message received from the portable broadcast system by the receiver 400 according to the message format. If the terminal receives the notification message from the portable binary broadcast system, the message analyzer 402 must include a specific function block for analyzing the notification message received in the binary format.

If the notification message is configured in an Extensible Markup Language (XML) format, the message parser 402 includes an XML parser to parse the received notification message. The message analyzer 402 analyzes the notification message received by the receiver 400, checks the contents of the NotificationType, which is one of the attribute values, and delivers the contents to the controller 404. For example, if the value of NotificationType is 0, indicating that the received notification message is for user use , the analyzer 402 messages delivers the contents to the controller 404 and allows the controller 404 to perform the corresponding operation.

A controller 404 controls the terminal depending on the NotificationType of the notification message analyzed by the message analyzer 402 according to the first and second embodiments of the present invention. For example, in the first embodiment, if the NotificationType is 0, indicating that the received notification message is for user use, the controller 404 provides the received notification message to the user through the display 406. In this case, the notification message may be a short message service (SMS) message or multimedia message.

Conversely, if the NotificationType is 1, indicating that the received notification message is intended to be used by the terminal, the controller 404 recognizes that the corresponding message is a notification message about the service and update guide. To check the contents of the changed or updated session information, the controller 404 allows the session access unit 408 to access the corresponding session, receive the specified content, such as a service manual, file and object in the session that has been accessed, and store the received content in storage device 410. As used herein, “accessing an appropriate session” means accessing a portable broadcast system with session information, adannoy in the notification message if the session information is included in the received notification message.

According to a second embodiment of the present invention, if the new received notification message is identical in version to the previously received notification message, the controller 404 discards the new received notification message. If the notification messages are not equal to each other in version, the controller 404 performs the corresponding operation according to the contents of the newly received notification message. In particular, the controller 404 determines whether the received message is new or independent of the ID 502 of table 1 and the NotificationVersion information added according to the second embodiment of the present invention. These processes are described in more detail below with reference to tables 14-26.

Of these processes, the process according to the first embodiment is described in more detail below with reference to FIG. 5, the process according to the second embodiment is described in more detail below with reference to FIG. 7.

If the PresentationType of the notification message analyzed by the message analyzer 402 is 1, the controller 404 stores the received notification message in the memory 410 so that the user can use it in the future.

If the NotificationType of the notification message analyzed by the message analyzer 402 according to an embodiment of the present invention is 1, indicating that the received notification message is for use by the terminal, the session access block 408 accesses the corresponding session under the control of the controller 404. Additionally, the block 408 accessing a session accepts the specified content, such as a service guide, file and object, in a session that has been accessed.

The storage device 410 stores the service manual, file and object received by the session access block 408, and also stores the notification message with PresentationType = 1.

The display 406 generally displays text, an image, a moving image and / or a still image under the control of the controller 404. According to an embodiment of the present invention, if PresentationType is 0, the display 406 under the control of the controller 404 stops content in the service, such as the image, and displays the received notification message.

However, if the PresentationType of the notification message is 2, the display 406 under the control of the controller 404 displays a received notification message for the content currently provided in the service in an overlapping manner.

5 is a flowchart illustrating the reception of a notification message in a terminal according to a first embodiment of the present invention. The attribute values and element values for the notification message are described above.

At step 501, the terminal receives the notification message from the portable broadcast system using the receiver 400. At step 502, the message analyzer 402 analyzes the corresponding message according to the format in which the received notification message is configured. If the notification message is configured in XML format, the message parser 402 parses the received message using the XML parser included therein.

At step 503, the controller 404 checks the NotificationType of the notification message analyzed by the message analyzer 402, and performs a predetermined operation according to the result of the verification, and is described later in this document. If the NotificationType is 0, indicating that the received notification message is for user use, the controller 404 proceeds to step 510. If the NotificationType is 1, indicating that the received notification message is intended for use by the terminal, the controller 404 proceeds to step 530. If NotificationType is 2 or more, indicating that the received notification message is a message specified by the service provider, the controller 404 proceeds to step 520, where it performs the specific operation specified by the service provider. In this document, to where NotificationType is 2, the service provider is free to set a notification message according to its business model and services.

At step 510, the controller 404 may provide the received notification message to the user through the display 406, since the received notification message is a message received for user use. The notification message received for the user notification may be an SMS message or a multimedia message. Using this message, a service provider can provide various types of messages, such as a notification of a service event, a system failure / check notification, a text or multimedia advertisement for a service / content, a broadcast failure message, an invoice notification, etc. Regarding this notification message, the controller 404 checks the PresentationType, and if the received notification message has a high priority, which is set according to the result of the check, the controller 404 displays the received notification message through the display 406. PresentationType can be freely set according to the business model and services of the service provider and must have a value other than the value specified above.

At step 511, the controller should determine whether to process the received notification message, depending on the PresentationType of the received notification message. If the PresentationType of the received notification message is 0, the controller 404 determines that the received notification message is a message that should be urgently provided to the user. If PresentationType is 1, the controller 404 stores the received notification message in the storage device 410 so that the user can use it in the future.

Finally, if PresentationType is 2, the controller 404 overlaps the corresponding notification message on the content of the service.

If it is determined at step 511 that the PresentationType of the received notification message is 0, indicating that the corresponding message should be immediately sent to the user, the controller 404 proceeds to step 512, where it stops the current service. At step 513, the controller 404 configures the received notification message so that it can be directly provided to the user. At step 514, the controller 404 displays the configured notification message through the display 406 according to a predefined screen configuration method. As used herein, “configuring a received notification message” means, if the notification message is configured in XML format, reconfiguring the message according to a predetermined screen configuration method so as to provide information such as text, image, video and audio included in the message to the user .

If it is determined in step 511 that the PresentationType of the received notification message is 1, the controller 404 stores the notification message in the storage device 410 in step 515. The user can then check the notification message stored in the storage device 410 by a corresponding operation.

Finally, if it is determined in step 511 that the PresentationType of the received notification message is 2, the controller 404 reconfigures the notification message in step 516 according to the screen configuration method set by the terminal 208 to block the received notification message about the current service / content through the display 406.

At step 517, the controller 404 overlaps the notification message generated at step 516 with the currently received content and provides the results of the overlap to the user through the display 406.

However, if it is determined in step 503 that the PresentationType of the received notification message is 1, the controller 404 determines in step 530 that the received notification message is intended for use by the terminal.

The controller 404 checks the content of the session information of the received notification message in step 531 and accesses the corresponding session based on the contents of the session information in step 532. The controller 404 receives the specified content, such as a service guide, file and object in the session that has been accessed, at step 533 and stores or updates the received content in the storage device 410 at step 534.

6 is a flowchart illustrating a process for generating a notification message in a portable broadcast system according to a first embodiment of the present invention.

The element values and attribute values for the notification message described in FIG. 6 are explained with reference to tables 1-10.

A notification message is generated by the notification generation function 204a described in FIG. 2 at the request of a content provider, service provider or network service provider, or based on a notification event generated by a portable broadcast service system.

In step 601, the notification generation function 204a receives, from the notification event function 202a, a notification event message notifying of a change / failure in the system and service, change / delivery of the service manual, content delivery, advertisement, emergency, emergency, etc. .

At 602, based on the received notification event message, the notification generation function 204a generates basic information for the notification event, i.e. the values of the ID and Validity attributes; and the values of the Name, Description, ExtensionURL, and MediaInformation elements.

In step 603, after the creation of the basic information, the notification generation function 204a determines whether the notification message to be transmitted to the terminal is intended for user or terminal use, and sets NotificationType according to the determination result.

If the notification message is for user use (610), the notification generation function 204a sets the NotificationType to 0 in step 611.

After setting NotificationType to 0 in step 611, the notification generation function 204a determines in step 612 whether it should immediately display the corresponding message on the user terminal, save the corresponding message in the terminal so that it can be displayed later at the user's request, or block the corresponding message on the content of the service for the user.

If the notification generation function 204a determines to immediately display the notification message when it is received (620) in the process of determining the method of displaying the notification message in the terminal at step 612, it sets the PresentationType of the notification message to 0 at step 621. However, if the notification generation function 204a determines save the notification message in the terminal so that it can be displayed later at the request of the user (630); it sets PresentationType to 1 at step 631.

Finally, if the notification generation function 204a determines to overlap the notification message with the currently provided content for the user (640), it sets the PresentationType in the notification message to 2 in step 641.

However, if it is determined in step 603 that the notification message is intended to be used by the terminal (650), the notification generation function 204a sets the NotificationType of the notification message to 1 in step 651.

At step 652, a notification message for use by the terminal, as described in the notification message format section, is used as a message notifying about updating / delivery of a service guide or delivery of service / content, and requires session information for the corresponding message. Therefore, in order to generate a notification message for use by the terminal, corresponding notification information is required for the notification generation function 204a. The session information is stored in the BCAST service distribution / adaptation unit 203, and when the notification distribution / adaptation function 203a of the BCAST service distribution / adaptation unit 203 delivers the session information to the notification generation function 204a, the notification generation function 204a checks the session information and then sets the associated information. Session information is recorded in items 511-522 in Table 3 and Table 4 in the first embodiment.

Upon completion of the task of the notification message for user application or for application by the terminal, the notification generation function 204a generates a notification message at step 660. At step 670, the notification generation function 204a transmits the generated notification message to the terminal via the notification distribution / adaptation function 203a.

The following is a description of the format of the notification message, as well as the apparatus and method for transmitting / receiving notification messages in a portable broadcast system according to a second embodiment of the present invention.

The following describes a complete notification message scheme according to a second embodiment of the present invention with reference to tables 14-18.

Tables 14-18 illustrate the complete notification message scheme according to the second embodiment of the present invention, and it further includes a NotificationVersion indicating the version of the notification message, in comparison with the scheme of the first embodiment of the present invention. NotificationVersion is the base value of the attribute, regardless of the application of the notification message, as the value typically used in the first embodiment.

Tables 14-18 are separated from one table for convenience, and the definition of the elements in each table follows the definition of table 14.

Table 14 room Name Type of Category Amount of elements Description 1100 Notification E1 O 0 ... N Snippet of notification message.
Contains the following attributes and elements.
Attributes:
ID
NotificationVersion
NotificationType
Validity
Items:
Name
Description
PresentationType
ExtensionURL
Sessioninformation
Mediainformation 1101 ID A M one The identifier of the notification message. 1102 NotificationVersion A M one Notification message version information. 1103 NotificafionType A M one Notification Type:
if 0, UserUse
if 1, TerminalUse
ServiceProvider Defined allowed. 1104 Validity A O 0 ... 1 Allowed fragment time. 1105 Name E2 M 1 ... N The title of the notification fragment.
Contains the following attribute:
Lang 1106 Lang A O 0 ... 1 Language. 1107 Description E2 M 1 ... N The content or description of the notification message. 1108 Lang A O 0 ... 1 Language.

Notification 1100 indicates the corresponding fragment of the notification message and includes attribute values: ID 1101, NotificationVersion 1102, NotificationType 1103, Validity 1104 and sub-element values: Name 1105 and Description 1107, both in table 14, PresentationType 1109 in table 15, ExtensionURL 1110 and SessionInformation 1111 in table 16 and MediaInformation 1123 in table 17.

ID 1101, a unique identifier for the notification message fragment, is a required element. Corresponding identifiers help distinguish stored notification messages.

NotificationVersion 1102 indicates the version number of the notification message. In a second embodiment of the present invention, the reason for setting the version number of the notification message in the notification message is that the portable broadcast system can repeatedly transmit the notification message if necessary. This is effective when a notification message is lost during transmission or there is a need to notify about an updated version for a particular notified service. When the portable broadcast system retransmits the notification message, the terminal requires criteria to determine whether the received notification message is a new message. Therefore, the second embodiment of the present invention adds the NotificationVersion attribute 1102 shown in Table 14 as an attribute of the Notification fragment 1100. According to the second embodiment of the present invention, the terminal receiving the notification message can check the version information of the corresponding notification message when it uses NotificationVersion 1102 and ID 1101 together. Those. when the terminal receives the notification message repeatedly transmitted by the portable broadcast system, it can determine whether the received notification message is a new notification message.

In order to use NotificationVersion 1102 according to a second embodiment of the present invention, it is possible to assign NotificationVersion 1102 an integer type version number or time stamp using the Network Time Protocol (NTP), which is the Internet standard used to synchronize computers connected to a network . Other methods may also be used for NotificationVersion 1102. For a repeatedly transmitted message indicated by NotificationVersion 1102, the time stamp or version number of the integer type NotificationVersion 1102 stores the NotificationVersion information specified when the notification message is initially generated.

NotificationType 1103 indicates whether the type or use of the notification message indicates a user application, terminal application, or other application, and is a required element. If the value of NotificationType 1103 is 0, it indicates a user application, and if the value of NotificationType 1103 is 1, it indicates a use by the terminal. In addition, NotificationType 1103 may set various values according to the purpose of the service provider.

Validity 1104 indicates the valid time of the notification message and is optional. Therefore, if the time set in Validity 1104 expires, the notification message stored in the terminal is deleted.

Name 1105 indicates the title or name of the notification message and is a required element. It can be set in various languages.

Lang 1106, the attribute value for Name 1105, indicates the language of the content written in Name 1105, and is an optional value. If Lang 1106 does not matter, it is assigned a default value, and the default value can indicate the language in the corresponding service area or English.

Description 1107 is the actual content of the message included in the notification message or part of the message description. It can be specified in various languages and is required.

Lang 1108, the attribute value for Description 1107, indicates the language of the content written in Description 1107, and is an optional value. If Lang 1108 does not matter, it is assigned a default value, and the default value can indicate the language in the corresponding service area or English.

Table 15 1109 PresentationType E2 M one Specifies the type of message presentation.
PresentationType = 0. The terminal immediately displays a notification message on the screen when it is received.
PresentationType = 1. The terminal stores the notification message in a storage device so that the user can check it later. (Default).
PresentationType = 2. The terminal displays a notification message for the currently running service in an overlapping manner.
If necessary, an optional PresentationType can be specified.

In Table 15, PresentationType 1109 specifies the type of notification presentation and is a required value. The presentation type indicates whether the terminal should display the corresponding message on the display after giving priority to the notification message and terminating all services, save the contents of the message to the specified device, i.e. to the storage device, or to block the notification message on the current service or content being received before being displayed. PresentationType 1109 can be set in various types according to the purpose of the service provider.

For example, if PresentationType is set to 0, the controller 404 of the terminal receiving the notification message provides the notification message to the user through the display 406 upon receipt of the message. If PresentationType is set to 1, the controller 404 stores the received notification message in the memory 410. In addition, if PresentationType is set to 2, the controller 404 blocks the notification message about the service currently provided through the display 406 to the user.

Table 16 1110 ExtensionURL E2 O 0 ... N URL for more information. 1111 Sessioninformation E2 O 0 ... N Session information by data.
Attributes:
ValidFrom
Validto
Usagetype
Items:
DeliverySession
TransportObjectID
Fragment
AlternativeURI 1112 ValidFrom A O 0 ... 1 Session Start Time. 1113 Validto A O 0 ... 1 Session End Time. 1114 Usagetype A O 0 ... 1 The type of session use (e.g., service manual, file delivery, etc.). 1115 DeliverySession E3 M one Session information on delivery content.
Attributes:
Sourceip
TransportSessionID 1116 Sourceip A M one The IP address of the source to be transmitted. 1117 TransportSessionID A M one The identifier of the session to be transmitted. 1118 TransportObjectID E3 O 0 ... N The identifier of the transfer object.

In table 16, ExtensionURL 1110 indicates the URL of a service or content server for additional information on the notification message and is an optional value.

SessionInformation 1111 indicates session information for receiving data and is an optional value. SessionInformation 1111 is session information where there is an appropriate service guide or there are files and contents when the service guide is updated or a file or content is received. SessionInformation 1111 has the ValidFrom 1112, ValidTo 1113, and UsageType 1114 attribute values and the values of the DeliverySession 1115 and TransportObjectID 1118 elements in Table 16 and the Fragment 1119 and AlternativeURI (Alternative URI) 1122 in Table 17 as their subordinate element values. Those. SessionInformation 1111 is used to provide session information on the service that terminal 208 should accept. The use of SessionInformation 1111 may be determined depending on the UsageType 1114. The terminal may determine what content should be included on the SessionInformation 1111, depending on the UsageType 1114 received notification messages.

ValidFrom 1112 indicates the start time when SessionInformation 1111 is valid, and is an optional value.

ValidTo 1113 indicates the end time when SessionInformation 1111 is valid, and is an optional value.

UsageType 1114 indicates the usage type of SessionInformation 1111. That is, UsageType 1114 indicates whether the application is intended to update a service manual or to receive files, and can be set in various types according to the purpose of the service provider.

DeliverySession 1115 indicates the position value for the session where an object such as a service manual or file should actually be transmitted, and has the values of the SourceIP 1116 and TransportSessionID 1117 attributes.

SourceIP 1116, the IP address of the corresponding transmission session, is available for both broadcast and multicast.

TransportSessionID 1117 has an identifier value for the transmission session.

TransportObjectID 1118 is a unique identifier for the object that is transmitted during the session.

Table 17 1119 Fragment E3 O 0 ... N Information of the fragment of the transmitted object.
Attributes:
Fragmentid
Fragmentmentersion 1120 Fragmentid A O 0 ... 1 The fragment identifier value. 1121 Fragmentmentersion A O 0 ... 1 Fragment version information. 1122 AlternativeURI E3 O 0 ... 1 An alternate URI that accepts the transmitted object. 1123 Mediainformation E2 O 0 ... 1 Multimedia information for generating a multimedia notification message.
Attributes:
Picture
Video
Audio 1124 Picture E3 O 0 ... N Image information.
Attributes:
Mimetype
Pictureuri 1125 Mimetype A O 0 ... 1 MIME type. 1126 Pictureuri A O 0 ... 1 URI indicating the position of the image. 1127 Video E3 O 0 ... N Image information.
Attributes:
Mimetype
VideoURI

In table 17, Fragment 1119, which is the fragment information of the transmitted object, indicates the updated information of the particular fragment for the service guide and allows the terminal to check the corresponding identifier and version information, receive only the updated fragment and save the received fragment.

FragmentID 1120 is the value of the unique fragment identifier that terminal 208 should receive.

FragmentVersion 1121 indicates version information of a fragment to be received, and for a fragment having the same FragmentID, the corresponding version information is checked to determine if the terminal has a FragmentID corresponding to the latest version. If there is the latest version in the session, the terminal takes the value of the latest version from the session and stores the accepted version value.

AlternativeURI 1122 represents the value of the URI address with the corresponding object in the event that the transmission through the session is unsuccessful, or if there is a need for reception not on the broadcast channel, but on the interaction channel. The terminal can access the position of the corresponding URI address through the interaction channel and receive the desired transmitted object.

MediaInformation 1123 indicates multimedia information for generating a notification message and is required for a notification message configured with multimedia. MediaInformation 1123 consists of the values of the subordinate elements Picture (Video), Video (Video) and Audio (Audio).

Picture 1124 indicates picture or image information, MIMEtype 1125 indicates the type of Internet Multipurpose Email Extensions (MIME) for the corresponding moving image, PictureURI 1126 is a URI address indicating the position of the picture or image, and Video 1127 indicates information about the moving image.

Table 18 1128 Mimetype A O 0 ... 1 MIME type. 1129 VideoURI A O 0 ... 1 URI indicating the position of the video. 1130 Audio E3 O 0 ... N Image information.
Attributes:
Mimetype
AudioURI 1131 Mimetype A O 0 ... 1 MIME type. 1132 AudioURI A O 0 ... 1 A URI indicating the position of the audio.

In table 18, the MIMEtype 1128 indicates the MIME type for the corresponding moving image, and VideoURI 1129 is the URI address indicating the position of the moving image. “Moving image position” means the position of a specific server when a corresponding moving image exists on a specific server, instead of including a transmission notification in the message.

Audio 1130 indicates information on audio, music and notification sounds, MIMEtype 1131 indicates the MIME type for the corresponding audio, and AudioURI 1132 is a URI address indicating the position of the audio.

Table 19 and table 20 illustrate a message format configured with text, which is a notification message scheme used for a user application according to a second embodiment of the present invention. The definition of each element in table 19 and table 20 is identical to the definition in table 14, and a detailed description of the same blocks as the blocks in tables 14-18 is omitted.

Table 19 room Name Type of Category Amount of elements Description 1200 Notification E1 O 0 ... N Snippet of notification message.
Contains the following attributes and elements.
Attributes:
ID
NotificationVersion
NotificationType
Validity
Items:
Name
Description
PresentationType
ExtensionURL 1201 ID A M one The identifier of the notification message. 1202 NotificationVersion A M one Notification message version information. 1203 NotificationType A M one Notification Type:
if 0, UserUse
if 1, TerminalUse
ServiceProvider Defined allowed. 1204 Validity A O 0 ... 1 Allowed fragment time. 1205 Name E2 M 1 ... N The title of the notification fragment.
Contains the following attribute:
Lang 1206 Lang A O 0 ... 1 Language. 1207 Description E2 M 1 ... N The content or description of the notification message. 1208 Lang A O 0 ... 1 Language.

Table 20 1209 PresentationType E2 M one Specifies the type of message presentation.
PresentationType = 0. The terminal immediately displays a notification message on the screen when it is received.
PresentationType = 1. The terminal stores the notification message in a storage device so that the user can check it later. (Default).
PresentationType = 2. The terminal displays a notification message for the currently running service in an overlapping manner.
If necessary, an optional PresentationType can be specified. 1210 ExtensionURL E2 O 0 ... N URL for more information.

The user notification message shown in Table 19 and Table 20, proposed in exemplary embodiments of the present invention, can be used to receive public notifications, advertising messages, billing information and billing information for a service provider or content provider, and ExtensionURL 610 acting as CallbackURL can receive additional information through the interaction channel.

The corresponding notification message includes the attribute values ID 1201, NotificationVersion 1202, NotificationType 1203 and Validity 1204 and the values of the Name elements 1205, Description 1207, PresentationType 1209 and ExtensionURL 1210. The description of all the values of the sub-attributes and the values of the sub-elements that make up the notification message shown in table 19 and table 20, identical to the description in table 14-18.

With reference to tables 21-23, a description will now be made of a message format configured with multimedia, which is a notification message scheme used for a user application according to a second embodiment of the present invention. For convenience, tables 21-23 are divided from one table. The definition of each element in tables 21-23 is identical to the definition in table 14, and a detailed description of the same blocks as the blocks in tables 14-18 is omitted.

Table 21 room Name Type of Category Amount of elements Description 1300 Notification E1 O 0 ... N Snippet of notification message.
Contains the following attributes and elements.
Attributes:
ID
NotificationVersion
NotificationType
Validity
Items:
Name
Description
PresentationType
ExtensionURL
Mediainformation 1301 ID A M one The identifier of the notification message. 1302 NotificationVersion A M one Notification message version information. 1303 NotificationType A M one Notification Type:
if 0, UserUse
if 1, TerminalUse
ServiceProvider Defined allowed. 1304 Validity A O 0 ... 1 Allowed fragment usage time. 1305 Name E2 M 1 ... N The title of the notification fragment.
Contains the following attribute:
Lang 1306 Lang A O 0 ... 1 Language. 1307 Description E2 M 1 ... N The content or description of the notification message. 1308 Lang A O 0 ... 1 Language.

Table 22 1309 PresentationType E2 M one Specifies the type of message presentation.
PresentationType = 0. The terminal immediately displays a notification message on the screen when it is received.
PresentationType = 1. The terminal stores the notification message in a storage device so that the user can check it later. (Default).
PresentationType = 2. The terminal displays a notification message for the currently running service in an overlapping manner.
If necessary, an optional PresentationType can be specified. 1310 ExtensionURL E2 O 0 ... N URL for more information. 1323 Mediainformation E2 O 0 ... 1 Multimedia information for generating a multimedia notification message.
Items:
Picture
Video
Audio 1324 Picture E3 O 0 ... N Image information.
Attributes:
Mimetype
Pictureuri 1325 Mimetype A O 0 ... 1 MIME type. 1326 Pictureuri A O 0 ... 1 URI indicating the position of the image.

Table 23 1327 Video E3 O 0 ... N Image information.
Attributes:
Mimetype
VideoURI 1328 Mimetype A O 0 ... 1 MIME type. 1329 VideoURI A O 0 ... 1 URI indicating the position of the video. 1330 Audio E3 O 0 ... N Image information.
Attributes:
Mimetype
AudioURI 1331 Mimetype A O 0 ... 1 MIME type. 1332 AudioURI A O 0 ... 1 A URI indicating the position of the audio.

Tables 21-23 illustrate a message format configured with multimedia, which is a notification message scheme used for a user application according to a second embodiment of the present invention. The user notification message shown in Tables 21-23, proposed in an exemplary embodiment of the present invention, allows the message to be configured using various multimedia files, such as an image, a moving image, audio, etc., and may be different used as an advertising message on the service and content and a public good message, such as searching for a missing child. The notification message in Tables 21-23 includes the attribute values ID 1301, NotificationVersion 1302, NotificationType 1303 and Validity 1304 and the values of the Name 1305, Description 1307, PresentationType 1309, ExtensionURL 1310 and MediaInformation 1323 element values. Description of all subordinate attribute values and sub element values constituting the notification message shown in tables 21-23 is identical to the description in tables 14-18.

With reference to tables 24-26, a description will now be made of a message format including session information, which is a notification message scheme used for use by a terminal according to a second embodiment of the present invention. For convenience, tables 24-26 are separated from one table for convenience, and the definition of the elements in each table follows the definition of tables 14.

Table 24 room Name Type of Category Amount of elements Description 1400 Notification E1 O 0 ... N Snippet of notification message.
Contains the following attributes and elements.
Attributes:
ID
NotificationVersion
NotificationType
Validity
Items:
Name
Description
PresentationType
ExtensionURL
Sessioninformation 1401 ID A M one The identifier of the notification message. 1402 NotificationVersion A M one Notification message version information. 1403 NotificationType A M one Notification Type:
if 0, UserUse
if 1, TerminalUse
ServiceProvider Defined allowed. 1404 Validity A O 0 ... 1 Allowed fragment time. 1405 Name E2 M 1 ... N The title of the notification fragment.
Contains the following attribute:
Lang 1406 Lang A O 0 ... 1 Language. 1407 Description E2 M 1 ... N The content or description of the notification message. 1408 Lang A O 0 ... 1 Language.

Table 25 1409 PresentationType E2 M one Specifies the type of message presentation.
PresentationType = 0. The terminal immediately displays a notification message on the screen when it is received.
PresentationType = 1. The terminal stores the notification message in a storage device so that the user can check it later. (Default).
PresentationType = 2. The terminal displays a notification message for the currently running service in an overlapping manner.
If necessary, an optional PresentationType can be specified. 1410 ExtensionURL E2 O 0 ... N URL for more information. 1411 Sessioninformation E2 O 0 ... N Session information by data.
Attributes:
ValidFrom
Validto
Usagetype
Items:
DeliverySession
TransportObjectID
Fragment
AlternativeURI 1412 ValidFrom A O 0 ... 1 Session Start Time. 1413 Validto A O 0 ... 1 Session End Time. 1414 Usagetype A O 0 ... 1 The type of session use (e.g., service manual, file delivery, etc.).

Table 26 1415 DeliverySession E3 M one Session information on delivery content.
Attributes:
Sourceip
TransportSessionID 1416 Sourceip A M one The IP address of the source to be transmitted. 1417 TransportSessionID A M one The identifier of the session to be transmitted. 1418 TransportObjectID E3 O 0 ... N The identifier of the transfer object. 1419 Fragment E3 O 0 ... N Information of the fragment of the transmitted object.
Attributes:
Fragmentid
Fragmentmentersion 1420 Fragmentid A O 0 ... 1 The fragment identifier value. 1421 Fragmentmentersion A O 0 ... 1 Fragment version information. 1422 AlternativeURI A O 0 ... 1

Tables 24-26 illustrate a message format including session information, which is a notification message scheme used for use by a terminal according to a second embodiment of the present invention. A typical application of the notification message used for application by the terminal, shown in Tables 24-26, is to provide update information on the service manual to the terminal in order to help the terminal maintain the updated service manual. In addition, the notification message scheme in Tables 24-26 can be used in different ways to start a service or content, start a file download, and deliver a multimedia notification message transmitted through a separate session. Although it is indicated that a typical application of a notification message is to provide update information of a service manual to a terminal, applications other than the above applications may replace a typical application.

For a single session, a portable broadcast system generally opens a session with a multicast address to transmit content, and transmits the corresponding content to the terminal. In this case, when the terminal is already receiving the content service from the portable broadcast system using a specific session, another separate session, different from the previously established session, is called a separate session.

The notification message for use by the terminal, shown in Tables 24-26, proposed in the second embodiment of the present invention, includes the attribute values ID 1401, NotificationVersion 1402, NotificationType 1403 and Validity 1404 and the values of the elements Name 1405, Description 1407, PresentationType 1409, ExtensionURL 1410 and SessionInformation 1411. The description of all the values of the sub-attributes and the values of the sub-elements making up the notification message shown in tables 24-26 is identical to the description in tables 14-18.

7 is a flowchart illustrating a process for receiving a notification message in a terminal according to a second embodiment of the present invention. The attribute values and element values for the notification message are described above.

At step 701, the terminal receives the notification message from the portable broadcast system using the receiver 400. At step 702, the message analyzer 402 analyzes the corresponding message according to the format in which the received notification message is configured. If the notification message is configured in XML format, the message parser 402 parses the received message using the XML parser included therein.

At step 703, the controller 404 determines whether the received notification message is an already received notification message by comparing a previously received notification message with a new received notification message regarding ID and NotificationVersion. If the new received notification message is identical to the previously received notification message, the controller 404 proceeds to step 705, where it discards the new received notification message and then terminates the process. However, if the new received notification message is not identical to the previously received notification message, the controller 404 proceeds to step 704.

At 704, the controller 404 checks the NotificationType of the notification message analyzed by the message analyzer 402, and performs a predetermined operation according to the result of the verification, and will be described later in this document. If the NotificationType is 0, indicating that the received notification message is for user use, the controller 404 proceeds to step 710. If the NotificationType is 1, indicating that the received notification message is intended for use by the terminal, the controller 404 proceeds to step 730. If NotificationType equal to 2 or more, indicating that the received notification message is a message specified by the service provider, the controller 404 proceeds to step 720, where it performs the specific operation specified by the service provider. In this document, to where NotificationType is 2, the service provider is free to set a notification message according to its business model and services.

At step 710, the controller 404 may provide the received notification message to the user through the display 406, since the received notification message is a message received for user use. The notification message received for the user notification may be an SMS message or a multimedia message. Using this message, a service provider can provide various types of messages, such as a notification of a service event, a system failure / check notification, a text or multimedia advertisement for a service / content, a broadcast failure message, an invoice notification, etc. Regarding this notification message, the controller 404 checks the PresentationType, and if the received notification message has a high priority, which is set according to the result of the check, the controller 404 displays the received notification message through the display 406. PresentationType can be freely set according to the business model and services of the service provider and must have a value other than the value specified above.

At step 711, the controller should determine whether to process the received notification message, depending on the PresentationType of the received notification message. If the PresentationType of the received notification message is 0, the controller 404 determines that the received notification message is a message that should be urgently provided to the user. If PresentationType is 1, the controller 404 stores the received notification message in the storage device 410 so that the user can use it in the future. Finally, if PresentationType is 2, the controller 404 superimposes the corresponding notification message on the content of the service.

If it is determined at step 711 that the PresentationType of the received notification message is 0, indicating that the corresponding message should be immediately sent to the user, the controller 404 proceeds to step 712, where it stops the current service. At 713, the controller 404 configures the received notification message so that it can be directly provided to the user. At step 714, the controller 404 displays the configured notification message through the display 406 according to a predefined screen configuration method. As used herein, “configuring a received notification message” means, if the notification message is configured in XML format, reconfiguring the message according to a predetermined screen configuration method so as to provide information such as text, image, video and audio included in the message to the user .

If it is determined in step 711 that the PresentationType of the received notification message is 1, the controller 404 stores the notification message in the storage device 410 in step 715. The user can then check the notification message stored in the storage device 410 by a corresponding operation.

Finally, if it is determined in step 711 that the PresentationType of the received notification message is 2, the controller 404 reconfigures the notification message in step 716 according to the screen configuration method set by the terminal 208 to overlay the received notification message on the current service / content on the display 406.

At step 717, the controller 404 superimposes the notification message generated at step 716 on the currently received content and provides the overlay results to the user through the display 406.

However, if it is determined at step 704 that the PresentationType of the received notification message is 1, the controller 404 determines at step 730 that the received notification message is intended for use by the terminal.

The controller 404 checks the content of the session information of the received notification message in step 731 and accesses the corresponding session based on the contents of the session information in step 732. The controller 404 receives the specified content, such as a service guide, file and object in the session that has been accessed, at step 733 and stores or updates the received content in the storage device 410 at step 734.

FIG. 8 is a flowchart illustrating a process for generating a notification message in a portable broadcast system according to a second embodiment of the present invention.

The element values and attribute values for the notification message described in FIG. 8 are explained with reference to tables 14-26.

A notification message is generated by the notification generation function 204a described in FIG. 2 at the request of a content provider, service provider or network service provider, or based on a notification event generated by a portable broadcast service system.

At step 801, the notification generation function 204a receives from the notification event function 202a a notification event message notifying of a change / failure in the system and service, change / delivery of the service manual, content delivery, advertisement, emergency, emergency, etc. .

At 802, based on the received notification event message, the notification generation function 204a generates basic information for the notification message, i.e. the values of the ID and Validity attributes; and the values of the Name, Description, ExtensionURL, and MediaInformation elements.

In step 803, after the creation of the basic information, the notification generation function 204a determines whether the corresponding notification message is intended for user use or for use by the terminal, and sets the NotificationType according to the determination result.

If the notification message is for user use (810), the notification generation function 204a sets the NotificationType to 0 in step 811.

After setting NotificationType to 0 in step 811, the notification function 204a determines in step 812 whether it should immediately display the corresponding message on the user terminal, save the corresponding message in the terminal so that it can be displayed later at the user's request, or block the corresponding message on the content of the service for the user.

If the notification generation function 204a determines to immediately display the notification message when it is received (820) in the process of determining the method for displaying the notification message in the terminal at 812, it sets the PresentationType of the notification message to 0 at 821. However, if the notification generation function 204a determines save the notification message in the terminal so that it can be displayed later at the user's request (830); it sets PresentationType to 1 at step 831.

Finally, if the notification generation function 204a determines to overlap the notification message with the currently provided content for the user (840), it sets the PresentationType in the notification message to 2 in step 841.

However, if it is determined in step 803 that the notification message is intended to be used by the terminal (850), the notification generation function 204a sets the NotificationType of the notification message to 1 in step 851.

At step 852, a notification message for use by the terminal, as described in the section of the notification message format, is used as a message notifying about updating / delivery of a service manual or delivery of service / content, and requires session information for the corresponding message. Therefore, in order to generate a notification message for use by the terminal, corresponding notification information is required for the notification generation function 204a. The session information is stored in the BCAST service distribution / adaptation unit 203, and when the notification distribution / adaptation function 203a of the BCAST service distribution / adaptation unit 203 delivers the session information to the notification generation function 204a, the notification generation function 204a checks the session information and then sets the associated information. Session information is recorded in elements 1111-1122 of table 16 and table 17 in the second embodiment.

Upon completion of the task of the notification message for user or terminal use, the notification function 204a generates a notification message at 860. At 870, the notification function 204a transmits the generated notification message to the terminal via the notification distribution / adaptation function 203a.

Table 27 below is a notification message diagram provided for a better understanding of tables representing element values and attribute values constituting the notification message illustrated above, and tables representing element values and attribute values constituting the notification message illustrated below.

Table 27 Name Type of Category Amount of elements Description Data type

In Table 27, “Name” indicates the name of the element or attribute making up the corresponding fragment. “Type” indicates whether the name matches the value of the element (E) or the value of the attribute (A). The value of an element includes E, E1, and E2. A “category” is used to indicate whether the corresponding element value or attribute value is mandatory or optional in the network (N) or terminal (T), and has the value M if the value is mandatory and the value O if the value is optional. Therefore, mandatory content on the network is designated as “NM (mandatory on the network)”, mandatory content on the terminal is indicated on “TM (mandatory on the terminal)”, optional content on the network is designated as “NO (optional on the network)”, and optional content in the terminal is indicated as "TO (optional in the terminal)". "Number of elements" means the relationship between the elements, and has the meanings "0", "0 ... 1", "1", "0 ... N", "1 ... N", where 0 means an optional relationship, 1 means a mandatory relationship, and N means the possibility of having multiple values. For example, "0 ... N" means the possibility that there is no corresponding element value or that there are N corresponding element values. Description describes the meaning of the corresponding element value or attribute value. Data type means the data type for the corresponding value of an element or attribute, i.e. sets the type of programming language used to compose the message. For example, “Data Type” may indicate the data type used in XML.

Tables 28-36 illustrate the notification message described in table 27 according to a third embodiment of the present invention. The notification message according to the third embodiment differs from the notification message according to the first embodiment in that the “Category” means whether the corresponding content is mandatory or optional in the network and terminal, as described in table 27. In addition, among the values of the elements, Name 1205 in table 19, indicating the name of the notification message in the first and second embodiments, is replaced by Title in the table 29 below. In addition, although the first and second embodiments access the session using the session information included in the notification message and receive the corresponding file, the third embodiment adds ServiceGuideDeliveryDescriptor (Service Guide Delivery Descriptor) and Fragment to the notification message to use them for service manual updates. The third embodiment differs from previous embodiments in that the NotificationType used for a user or terminal application differs according to the use or event of the notification message.

The notification message in Tables 28-36 generally includes the values of the ID, NotificationVersion, NotificationType, and Validity attributes and the values of the Title, Description, PresentationType, and ExtensionURL elements and can optionally include SessionInformation, MediaInformation, ServiceGuideDeliveryDescriptor, or Fragment according to its application.

Table 28 Name Type of Category Amount of elements Description Data type NotificationMessage E Snippet of notification message.
Contains the following attributes:
ID
NotificationVersion
NotificationType
Validity
Contains the following elements:
Title
Description
PresentationType
ExtensionURL
Sessioninformation
Mediainformation
ServiceGuideDeliveryDescriptor
Fragment ID A NM / TM one The identifier of the notification message. anyURI NotificationVersion A NM / TM one Notification message version information. It should be used to check redundancy of notification messages and new notification messages. int (32 bits), expressed as NTP time NotificationType A NM / TM one The type of notification carried in this notification message. See section 8.2. integer Validity A NO / TM 0 ... 1 The valid time of the notification message fragment.
If Validity is set, the notification message must expire at the specified time. int (32 bits), expressed as NTP time

Table 29 Title E1 NM / TM 0 ... N Notification message header, possibly in several languages.
The language is expressed using the xml: lang built-in XML attribute using this element. string Description E1 NO / TM 0 ... N Description or notification messages, possibly in several languages.
The language is expressed using the xml: lang built-in XML attribute using this element. string PresentationType E1 NM / TM one Specifies the type of presentation of received notification messages.
If PresentationType = 0, the terminal prepares for viewing the notification message immediately after the interruption of all applications.
If PresentationType = 1, the terminal saves the notification message. The user can view the saved message every time he wants. (Default.)
If PresentationType = 2, the terminal prepares a notification message for viewing, blocking the current playable services.
Other PresentationType values may be determined according to the designation of service providers, operators, or broadcast stations. integer ExtensionURL E1 NO / TM 0 ... N A URL containing additional information related to the notification message. anyURI

Table 30 Sessioninformation E1 NO / TM 0 ... N This element MUST be present when a notification message moves the pointer to another delivery session.
SessionInformation specifies delivery session information, information of objects or fragments delivered by the specified session, and a URI address as an alternative delivery method. After receiving the notification message with SessionInformation, the terminal must access the corresponding session indicated by SessionInformation and take an appropriate action, such as receiving content.
Contains the following attributes:
ValidFrom
Validto
Usagetype
Contains the following elements:
DeliverySession
TransportObjectID
AlternativeURI ValidFrom A NO / TM 0 ... 1 The first moment when the session for the terminal to receive data is valid. int (32 bits), expressed as NTP
time Validto A NO / TM 0 ... 1 The last moment when the session for the terminal to receive data is valid. int (32 bits), expressed as NTP
time

Table 31 Usagetype A NO / TM 0 ... 1 Specifies the type of object transmitted through the specified delivery session.
If UsageType = 0, the specified delivery session should be used to deliver files.
If UsageType = 1, the service should begin through the specified scheduled delivery session.
Other PresentationType values may be determined according to the designation of service providers, operators, or broadcast stations. integer DeliverySession E2 NO / TM 0 ... 1 Information about the target delivery session indicated by the notification message.
Contains the following attributes:
Sourceip
TransportSessionID Sourceip A NM / TM one The source IP address for the delivery session. string TransportSessionID A NM / TM one ID of the target delivery session. Unsigned Short (16 bits) TransportObjectID E2 NO / TM 0 ... N The identifier of the transportation object (TOI) for the object transmitted through the specified delivery session, which includes the corresponding elements of the fragments. unsignedInt (32 bits) AlternativeURI E2 NO / TM 0 ... 1 An alternative URI for receiving an object through an interaction channel. If the terminal cannot access the specified delivery session, the terminal can receive the object associated with the notification message through AlternativeURI. anyURI

Table 32 Mediainformation E1 NO / TM 0 ... 1 This element MUST be present when a notification message carries information to provide notification support.
MediaInformation is used to compose and prepare to view notification messages.
Contains the following elements:
Picture
Video
Audio Picture E2 NO / TM 0 ... N Specifies how to get the image and the MIME type.
Contains the following elements:
Mimetype
Pictureuri Mimetype A NO / TM 0 ... 1 MIME type of image. string Pictureuri A NO / TM 0 ... 1 The URI that refers to the image. anyURI Video E2 NO / TM 0 ... N Specifies how to get the video and MIME type.
Contains the following elements:
Mimetype
VideoURI Mimetype A NO / TM 0 ... 1 MIME type of video. string VideoURI A NO / TM 0 ... 1 The URI that refers to the video. anyURI Audio E2 NO / TM 0 ... N Specifies how to get the audio and MIME type.
Contains the following elements:
Mimetype
AudioURI

Table 33 Mimetype A NO / TM 0 ... 1 MIME type of audio. string AudioURI A NO / TM 0 ... 1 A URI that refers to audio. anyURI ServiceGuideDeliveryDescriptor E1 NO / TM 0 ... N This element MUST be present when the notification message carries SGDD.
ServiceGuideDeliveryDescriptor contains the following subordinate element:
DescriptorEntry ID A NM / TM one ServiceGuideDeliveryDescriptor fragment identifier globally unique. anyURI Version A NM / TM one Version of this snippet. A newer version overrides the older one as soon as it is accepted. unsignedInt (32 bits) DescriptorEntry E2 NM / TM 1 ... N Record in ServiceGuideDeliveryDescriptor.
Contains the following subordinate elements:
Grouping critery
Transport
AlternativeAccessURL
ServiceGuideDeliveryUnit Grouping criteria E3 NO / TM 0 ... 1 Defines criteria for grouping fragments of a service guide in this DescriptorEntry service guide.
If several criteria for grouping are present at the same time, all these grouping criteria apply to the set of fragments of the service guide in this DescriptorEntry service guide.
Contains the following subordinate elements:
TimeGroupingCriteria
GenreGroupingCriteria
ServiceProviderCriteria

Table 34 TimeGroupingCriteria E4 NO / TM 0 ... 1 Specifies the time period that this DescriptorEntry describes. (For example: announces a specific subgroup of eligible fragments of a service guide for the next 2 hours).
Contains the following attributes:
Starttime
Endtime Starttime A NM / TM one Beginning of the time period for which this DescriptorEntry declares fragments.
(Note that this differs from the fragment validity time). int (32 bits) expressed
NTP time Endtime A NM / TM one The end of the time period for which this DescriptorEntry declares fragments.
(Note that this differs from the fragment validity time). int (32 bits) expressed
NTP time GenreGroupingCriteria E4 NO / TM 0 ... 1 Defines the classification of services / content associated with fragments in this block of delivery of the service manual (for example, comedy, action, drama) string ServiceProviderCriteria E4 NO / TM 0 ... 1 Specifies each service provider by a unique name. string Transport E3 NO / TM 0 ... 1 A pointer to a transport session delivering fragments of a service guide within the service guide delivery blocks specified in this DescriptorEntry.
Contains the following attributes:
Ipaddress
Port
Srcippdress
Sessionid Ipaddress A NM / TM one Destination IP address of the target delivery session. string Port A NM / TM one Destination port of the target delivery session. Unsigned Short (16 bits) Srcippdress A NO / TM 0 ... 1 The source IP address for the delivery session. string

Table 35 Sessionid A NM / TM one ID of the target delivery session. unsignedShort (16 bits) AlternativeAccessURL E3 NO / TM 0 ... N An alternate URL for retrieving service guide delivery blocks through an interaction channel. anyURI ServiceGuide DeliveryUnit E3 NM / TM 1 ... N Group of fragments.
Contains the following attributes:
transportObjectID
validFrom
validTo
Contains the following subordinate element:
Fragment transportObjectID A NO / TM 0 ... 1 The identifier of the transport object of the service guide delivery block transferring the advertised fragments within this group. unsignedInt (32 bits) validFrom A NO / TM 0 ... 1 The first point in time when this group of fragments of the service guide is valid. The format is NTP.
Note. If this element is missing, the validFrom attribute MUST be present in the sub Fragment element. int (32 bits) expressed
NTP time validTo A NO / TM 0 ... 1 The last moment in time when this group of fragments of the service guide is valid. The format is NTP.
Note. If this element is missing, the validTo attribute MUST be present in the sub Fragment element. int (32 bits) expressed
NTP time Fragment E4 NM / TM 1 ... N Announcement of a fragment of a service manual that is available on a broadcast channel.
Contains the following attributes:
transportID
ID
Version
validFrom
validTo
Type

Table 36 transportID A NM / TM one Identifier of the advertised fragment of the service guide to be used in the header of the service guide delivery block. unsignedInt (32 bits) ID A NM / TM one Identifier of the advertised snippet of the service guide. anyURI Version A NM / TM one Version of the announced fragment of the service manual.
Note. The scope of the Version is limited to the specified transport session. Version value ranges from 2 ^ 32-1 to 0. unsignedInt (32 bits) validFrom A NO / TM 0 ... 1 The first moment when this fragment is valid. If not provided, it is assumed that validity started some time ago.
Note. If this attribute is present, and the validFrom attribute for ServiceGuideDeliveryUnit is also present, the value of this attribute overrides the value of the validFrom attribute for ServiceGuideDeliveryUnit. int (32 bits), expressed as NTP time validTo A NO / TM 0 ... 1 The last moment when this fragment is valid. If not provided, it is assumed that validity ends at an undetermined time in the future.
Note. If this attribute is present, and the validTo attribute for ServiceGuideDeliveryUnit is also present, the value of this attribute overrides the value of the validTo attribute for ServiceGuideDeliveryUnit. int (32 bits), expressed as NTP time Type A NM / TM one An enumerated value indicating the schema or MIME type for the fragment. string Fragment E1 NO / TM 0 ... N This element MUST be present when a notification message carries a fragment of the service guide.
This element can carry any part of the service guide. <TBD>

Tables 37-45 below illustrate a notification message according to a fourth embodiment of the present invention. The differences between the notification message according to the fourth embodiment and the notification message according to other embodiments are as follows. The terminal determines whether the corresponding notification message is intended for user use or for use by the terminal, depending on the NotificationType. The notification generation function 204a configures the message according to the type of event (added) of the notification message using an EventType indicating the type of notification event. The terminal may determine by which event the received notification message is configured, depending on the EventType of the received notification message. In addition, the notification generation function 204a adds a FilteringValue to the notification message so as to display content stored in the subscriber terminal or content existing in a particular session and content corresponding to FilteringValue so that users can view different contents. Those. since the notification generating function 204a generates a notification message according to the received notification event message, it is possible to configure the notification message including only the element required for the notification message by including an EventType indicating the type of event in the notification message to enable the generating function 204a notifications form a notification message.

In addition, although the fourth embodiment may send a ServiceGuideDeliveryDescriptor (SGDD) or Fragment itself for the purpose of updating the service guide, it can access the progress of the notification message to the corresponding session by identifier, version information and session information for SGDD, find the SGDD corresponding to the reported identifier from SGDDs existing in the accessed session and update the service manual when the version information indicates the latest version.

The Generic Field of the notification message according to the fourth embodiment includes the values of the ID, NotificationVersion, NotificationType, EventType, PresentationType and Validity attribute values and the values of the Title, Description and ExtensionURL elements. FilteringValue, SessionInformation, MediaInformation, ServiceGuideDeliveryDescriptior and Fragment, along with the Generic Field, can be configured differently according to EventType.

Table 37 Name Type of Category Amount of elements Description Data type NotificationMessage E Snippet of notification message.
Contains the following attributes:
ID
NotificationVersion
NotificationType
Eventtype
PresentationType
Validity
Contains the following elements:
Title
Description
ExtensionURL
Filteringvalue
Sessioninformation
Mediainformation
ServiceGuideDeliveryDescriptor
Fragment ID A NM / TM one The identifier of the notification message. anyURI NotificationVersion A NM / TM one Notification message version information. It should be used to check redundancy of notification messages and new notification messages. int (32 bits) expressed
NTP time

Table 38 NotificationType A NM / TM one Notification Type:
If NotificationType = 0, this message is a user-oriented message, such as a notification from the SP, a multimedia message, an emergency message, etc.
If NotificationType = 1, this message is a terminal-oriented message, such as starting a service or downloading a file, etc.
Other NotificationType values may be determined according to the designation of service providers, operators or broadcasting stations. UnsignedByte Eventtype A NM / TM one The type of notification event carried in this notification message. unsignedByte PresentationType A NM / TM one Specifies the type of presentation of received notification messages.
If PresentationType = 0, the terminal prepares for viewing the notification message immediately after the interruption of all applications.
If PresentationType = 1, the terminal saves the notification message. The user can view the saved message every time he wants. (Default.)
If PresentationType = 2, the terminal prepares a notification message for viewing, blocking the current playable services.
Other PresentationType values may be determined according to the designation of service providers, operators, or broadcast stations. unsignedByte Validity A NO / TM 0 ... 1 The valid time of the notification message fragment.
If Validity is set, the notification message must expire at the specified time.
Note. If the notification message is used for advertising notice and this field is present, it MUST be used to indicate the start time of the advertisement. int (32 bits), expressed as NTP time

Table 39 Title E1 NO / TM 0 ... N Notification message header, possibly in several languages.
The language is expressed using the xml: lang built-in XML attribute using this element. string Description E1 NO / TM 0 ... N Description or notification messages, possibly in several languages.
The language is expressed using the xml: lang built-in XML attribute using this element. string ExtensionURL E1 NO / TM 0 ... N A URL containing additional information related to the notification message. AnyURI Filteringvalue E1 NO / TO 0 ... N Specifies the value to be used for filtering. String FilteringType A NM / TM one The type of filtering is affected. Possible values are Genre, Age, Name, Location, etc. String Sessioninformation E1 NO / TM 0 ... N This element MUST be present when a notification message moves the pointer to another delivery session.
SessionInformation specifies delivery session information, information of objects or fragments delivered by the specified session, and a URI address as an alternative delivery method. After receiving the notification message with SessionInformation, the terminal must access the corresponding session indicated by SessionInformation and take an appropriate action, such as receiving content.
Contains the following attributes:
ValidFrom
Validto
Usagetype
Contains the following elements: DeliverySession
TransportObjectID
AlternativeURI

Table 40 ValidFrom A NO / TM 0 ... 1 The first moment when the session for the terminal to receive data is valid. int (32 bits), expressed as NTP time Validto A NO / TM 0 ... 1 The last moment when the session for the terminal to receive data is valid. int (32 bits) expressed
NTP time DeliverySession E2 NO / TM 0 ... 1 Information about the target delivery session indicated by the notification message.
Contains the following attributes:
Sourceip
TransportSessionID Sourceip A NM / TM one The source IP address for the delivery session. string TransportSessionID A NM / TM one ID of the target delivery session. Unsigned Short (16 bits) TransportObjectID E2 NO / TM 0 ... N The identifier of the transportation object (TOI) for the object transmitted through the specified delivery session, which includes the corresponding elements of the fragments. unsignedInt (32 bits) AlternativeURI E2 NO / TM 0 ... 1 An alternative URI for receiving an object through an interaction channel. If the terminal cannot access the specified delivery session, the terminal can receive the object associated with the notification message through AlternativeURI. anyURI Mediainformation E1 NO / TM 0 ... 1 This element MUST be present when a notification message carries information to provide notification support.
MediaInformation is used to compose and prepare to view notification messages.
Contains the following elements:
Picture
Video
Audio

Table 41 Picture E2 NO / TM 0 ... N Specifies how to get the image and the MIME type.
Contains the following elements:
Mimetype
Pictureuri Mimetype A NO / TM 0 ... 1 MIME type of image. string Pictureuri A NO / TM 0 ... 1 The URI that refers to the image. anyURI Video E2 NO / TM 0 ... N Specifies how to get the video and MIME type.
Contains the following elements:
Mimetype
VideoURI Mimetype A NO / TM 0 ... 1 MIME type of video. string VideoURI A NO / TM 0 ... 1 The URI that refers to the video. anyURI Audio E2 NO / TM 0 ... N Specifies how to get the audio and MIME type.
Contains the following elements:
Mimetype
AudioURI Mimetype A NO / TM 0 ... 1 MIME type of audio. string AudioURI A NO / TM 0 ... 1 A URI that refers to audio. anyURI ServiceGuide DeliveryDescriptor E1 NO / TM 0 ... N This element MUST be present when the notification message carries SGDD.
ServiceGuideDeliveryDescriptor contains the following subordinate element:
DescriptorEntry

Table 42 ID A NM / TM one ServiceGuideDeliveryDescriptor fragment identifier globally unique. anyURI Version A NM / TM one Version of this snippet. A newer version overrides the older one as soon as it is accepted. unsignedInt (32 bits) DescriptorEntry E2 NO / TM 1 ... N A record in the delivery descriptor of the service manual.
Contains the following subordinate elements:
Grouping critery
Transport
AlternativeAccessURL
ServiceGuideDeliveryUnit Grouping criteria E3 NO / TM 0 ... 1 Defines criteria for grouping fragments of a service guide in this DescriptorEntry service guide.
If several criteria for grouping are present at the same time, all these grouping criteria apply to the set of fragments of the service guide in this DescriptorEntry service guide.
Contains the following subordinate elements:
TimeGroupingCriteria
GenreGroupingCriteria
ServiceProviderCriteria TimeGrouping Criteria E4 NO / TM 0 ... 1 Specifies the time period that this DescriptorEntry describes. For example: announces a specific subgroup of valid fragments of a service guide for the next 2 hours).
Contains the following attributes:
Starttime
Endtime Starttime A NM / TM one Beginning of the time period for which this DescriptorEntry declares fragments.
(Note that this differs from the fragment validity time). int (32 bits) expressed
NTP time

Table 43 Endtime A NM / TM one The end of the time period for which this DescriptorEntry declares fragments.
(Note that this differs from the fragment validity time). int (32 bits) expressed
NTP time GenreGrouping Criteria E4 NO / TM 0 ... 1 Defines the classification of services / content associated with fragments in this block of delivery of the service manual (for example, comedy, action, drama) string ServiceProvider
Criteria E4 NO / TM 0 ... 1 Specifies each service provider by a unique name. string Transport E3 NO / TM 0 ... 1 A pointer to a transport session delivering fragments of a service guide within the service guide delivery blocks specified in this DescriptorEntry.
Contains the following attributes:
Ipaddress
Port
Srcippdress
Sessionid Ipaddress A NM / TM one Destination IP address of the target delivery session. string Port A NM / TM one Destination port of the target delivery session. Unsigned
Short
(16 bits) Srcippdress A NO / TM 0 ... 1 The source IP address for the delivery session. string Sessionid A NM / TM one ID of the target delivery session. unsignedShort (16 bits) AlternativeAccess
URL E3 NO / TM 0 ... N An alternate URL for retrieving service guide delivery blocks through an interaction channel. anyURI

Table 44 ServiceGuideDeliveryUnit E3 NM / TM 1 ... N Group of fragments.
Contains the following attributes:
transportObjectID
validFrom
validTo
Contains the following subordinate element: Fragment transportObjectID A NO / TM 0 ... 1 The identifier of the transport object of the service guide delivery block transferring the advertised fragments within this group. unsignedInt (32 bits) validFrom A NO / TM 0 ... 1 The first point in time when this group of fragments of the service guide is valid. The format is NTP.
Note. If this element is missing, the validFrom attribute MUST be present in the sub Fragment element. int (32 bits) expressed
NTP time validTo A NO / TM 0 ... 1 The last moment in time when this group of fragments of the service guide is valid. The format is NTP.
Note. If this element is missing, the validTo attribute MUST be present in the sub Fragment element. int (32 bits) expressed
NTP time Fragment E4 NM / TM 1 ... N Announcement of a fragment of a service manual that is available on a broadcast channel.
Contains the following attributes:
transportID
ID
Version
validFrom
validTo
Type transportID A NM / TM one Identifier of the advertised fragment of the service guide to be used in the header of the service guide delivery block. unsignedInt (32 bits)

Table 45 ID A NM / TM one Identifier of the advertised snippet of the service guide. anyURI Version A NM / TM one Version of the announced fragment of the service manual.
Note. The scope of the Version is limited to the specified transport session. Version value ranges from 2 ^ 32-1 to 0. unsignedInt (32 bits) validFrom A NO / TM 0 ... 1 The first moment when this fragment is valid. If not provided, it is assumed that validity started some time ago.
Note. If this attribute is present, and the validFrom attribute for ServiceGuideDeliveryUnit is also present, the value of this attribute overrides the value of the validFrom attribute for ServiceGuideDeliveryUnit. int (32 bits) expressed
NTP time validTo A NO / TM 0 ... 1 The last moment when this fragment is valid. If not provided, it is assumed that validity ends at an undetermined time in the future.
Note. If this attribute is present, and the validTo attribute for ServiceGuideDeliveryUnit is also present, the value of this attribute overrides the value of the validTo attribute for ServiceGuideDeliveryUnit. int (32 bits) expressed
NTP time Type A NM / TM one An enumerated value indicating the schema or MIME type for the fragment. string Fragment E1 NO / TM 0 ... N This element MUST be present when a notification message carries a fragment of the service guide.
This element can carry any part of the service guide. <TBD>

Table 46 illustrates the values used in the NotificationType of the third embodiment and the EventType of the fourth embodiment. The notification message format of the third and fourth embodiment is subject to change according to EventType. For EventType = 1, the notification message can be configured using Generic Field + MediaInformation. For EventType = 2, when there is an intention to show related ads or content stored in the terminal by filtering, the notification message can be configured using Generic Field + FilteringValue. To send advertising content in a specific session, to enable the user to access a specific session and view the advertisement in real time, the notification message can be configured using Generic Field + SessionInformation or it can also be configured using Generic Field + FileteringValue + SessionInformation, with so that the user can view the ads associated with him through FilteringValue during the corresponding session.

For EventType = 3, the notification message is configured using Generic Field + SessionInformation to transmit a session in which the corresponding service or file should be transmitted to indicate the start of the service or file delivery. For EventType = 4, to notify only about a session where there is an updated service guide to indicate an update to the service guide, the notification message can be configured using the Generic Field + Session Information, and the corresponding ServiceGuideDelieveryDescriptor can be delivered along with the Generic Field + ServiceGuideDeliveryDescriptor with using the notification message or configure the modified Fragment itself as a Generic Field + Fragment.

In addition, when there are several SGDDs in the notification session where the SGDD is transmitted, the notification message is configured using Version + SessionInformation and the Generic Field + ServiceGuideDeliveryDescriptor identifier together to notify about the change of a specific SGDD in the session, allowing SGDD to be updated. For EventType = 5, the notification message can only be configured using the Generic Field. For EventType = 6, the notification message is configured in the form of Generic Field + MediaInformation, and then delivered to the terminal. As for the EventType in Table 46, various EventType values may be added according to application.

Table 46 Eventtype Name Description one Emergency notification To send emergency messages to users. 2 Advertisement To pass the insertion of advertising to the terminals. 3 Service availability announcement To convey the availability of services to users. four Service Guide update To transmit updates to the service manual for users. 5 Text message To report text notifications to users. 6 Multimedia message To report multimedia notifications to users.

Fig. 9 is an exemplary process in which, upon receiving a notification message used for an advertising purpose or the like, according to a fourth embodiment of the invention, the terminal provides previously stored advertising content or data to a user.

Those. The drawing illustrates the process in which when an advertising message with EventType = 2 includes FilteringValue, the subscriber terminal displays previously saved advertising content or similar data on its advertisement using FilteringValue. Distribution / Adaptation of Broadcast Services (BSD / A) 901 is a network entity for controlling distribution in OMA BCAST, and Distribution / Adaptation of Notifications (NTDA) 902 is a component of the notification function for delivering a notification message to BSD / A 901.

The NTDA 902 delivers a 903 notification message with EventType = Advertisement, FilteringType = Genre and FilteringValue = Sports from OMA BCAST to NTC 904 of terminal 911 via interface 930 defined between BSD / A 901 and terminal 911.

NTC 904 checks the received notification message and searches for content with Genre = Sports from the content 906909 stored in the storage device 905 using the corresponding function in the terminal 911. In this example, since Content (ID: 1) 906 corresponds to the advertising content associated with the FilteringValue received notification message 903, the content is displayed on the display 910 via the interface 940. Since the Validity in the received notification message is set as 2006.01.01 10:00 AM, the corresponding content is automatically displayed at 10:00 AM.

The FilteringValue and FilteringType described in the fourth embodiment of the invention can be assigned different values according to their application, and the main types may include User Preference, User Location, Target Group, Service Provider (Service Provider), User demographic profile, Time of day, Day of week, channel, etc. In addition, the corresponding type must be used with the same name if it is used for the same application or content as the contents of element values or attribute values describing a Fragment associated with the content or service guide service. The element values and attribute values used in the Fragment associated with the content or service include Genre, ParentalRating (Parent rating), UserRating (Target rating), TargetUserProfile (Target user profile), BroadcastArea (Broadcast area), etc. d.

As for FilteringType and FilteringValue in the above embodiments, FilteringType can be used with the same application and function with respect to Title, and FilteringValue can be used with the same application and function with respect to Description.

Although specific exemplary embodiments of the present invention are described only for a portable broadcast system in the first to fourth embodiments of the present invention, exemplary embodiments of the present invention can actually be applied to any IP-based broadcast system.

As can be understood from the above description, in a broadcast or communication system capable of portable broadcasting, exemplary embodiments of the present invention separate notification messages into a notification message for user use and a notification message for use by a terminal so as to enable the terminal to perform the desired operation instantly without a separate user operation, providing the ability to update the service manual or perform uploading files without user intervention. In a notification message for custom use, PresentationType is separately set in the message to give priority to the message. If the corresponding message is an urgent notification message, the terminal may stop the corresponding content service and provide the received notification message to the user.

In addition, the terminal checks the version information of the notification message while receiving the notification message from the portable broadcast system and discards the corresponding notification message if the message is a duplicated notification message, and performs the corresponding operation only when the corresponding notification message is a new notification message, thereby , reducing unnecessary terminal operations.

Exemplary embodiments of the present invention can be implemented in a general purpose or special purpose computer by executing a program from a computer-readable medium, including, but not limited to, storage media such as magnetic storage media (ROM, RAM, floppy disks, magnetic disks, etc.) .d.), optically readable media (CD-ROM, DVD, etc.), and wave carriers (transmission over the Internet).

Moreover, exemplary embodiments of the present invention can specifically configure the notification message according to EventType and add FilteringValue to the notification message to display the contents stored in the terminal for each user in various ways, thereby simplifying the individual setting of the content and the dynamic display of the desired content.

Although specific exemplary embodiments of the invention are shown and described herein, those skilled in the art should understand that various changes in form and content can be made without departing from the spirit and scope of the invention defined by the appended claims and their equivalents.

Claims (49)

1. A device for transmitting a message in a broadcast system, the device comprising:
a notification event function for receiving a notification indicating content change information provided from the content creating unit and generating a notification event message;
a notification generation function for generating a notification message that must be used by a user of a terminal designated to receive a notification message, or a notification message that must be used by a terminal using a notification event message from a notification event function; and
a notification distribution / adaptation function for transmitting a notification message received from the notification generation function to a terminal via a specific network. 2. The device according to claim 1, in which the function of the distribution / adaptation of notifications additionally transmits a message about the notification event received from the distribution unit of services of the distribution system by broadcast (BDS) due to information of the change of the broadcast system associated with the transfer of content to the generation function notifications. 3. The device according to claim 1, in which the function of generating notifications generates a notification message including NotificationType indicating the application of the notification message. 4. The device according to claim 1, in which the function of generating notifications generates a notification message, including NotificationVersion, indicating version information of the notification message. 5. The device according to claim 1, in which the function of generating notifications generates a notification message, including PresentationType, indicating the type of presentation of the notification message. 6. The device according to claim 1, in which the notification generation function generates a notification message including a UsageType indicating the use of SessionInformation indicating session information for receiving data in the notification message. 7. The device according to claim 1, in which the notification generation function generates a notification message including an EventType indicating how the notification message is configured through which event. 8. The device according to claim 1, wherein the notification generation function generates a notification message including a FilteringValue indicating information for executing content previously stored in the terminal. 9. A device for transmitting a message in a broadcast system, the device comprising:
a notification event function for receiving a notification indicating content change information provided from the content creating unit and generating a notification event message;
a notification generation function for generating a notification message using a notification event message received from the notification event function, wherein the notification message includes a NotificationType indicating whether the notification message is a notification message to be used by a user of a terminal designated to receive a notification message, or a notification message that should be used by the terminal, NotificationVersion, indicating the version information of the generated notification messages, PresentationType indicating the presentation type of the notification message, UsageType indicating the use of SessionInformation indicating session information for receiving data in the notification message, EventType indicating which event the notification message is configured to, and FilteringValue indicating information for executing the contents previously stored in the terminal; and
the function of distribution / adaptation of notifications for receiving a notification message from the function of generating notifications and transmitting the received notification message to the terminal through a specific network. 10. A method for transmitting a message in a broadcast system, the method comprising the steps of:
receiving, by the notification event function, a notification indicating content change information provided from the content creating unit, generating a notification event message and transmitting the generated notification event message to the notification generation function;
receive, by means of the notification generation function, a notification event message, generate a notification message that should be used by the user, or a notification message that should be used by the terminal, and transmit the generated notification message to the notification distribution / adaptation function; and
receive, via the distribution / adaptation function of the notifications, a notification message and transmit the received notification message to the terminal via a specific network. 11. The method of claim 10, wherein the step of generating a notification message by a notification generation function further comprises receiving a notification of a notification event from a notification distribution / adaptation function that has received an event generated by a distribution unit of services of the distribution system by broadcast ( BDS) due to broadcast system change information related to content transfer. 12. The method according to claim 11, in which the step of generating a notification message by means of the notification generation function comprises the step of generating a notification message including NotificationType indicating the application of the notification message. 13. The method according to claim 11, in which the step of generating a notification message by means of the notification generation function comprises the step of generating a notification message including a PresentationType indicating a presentation type of the notification message. 14. The method according to claim 11, in which the step of generating a notification message by means of the notification generation function comprises the step of generating a notification message including a UsageType indicating the use of SessionInformation indicating session information for receiving data in the notification message. 15. The method according to claim 11, in which the step of generating a notification message by means of the notification generation function comprises the step of generating a notification message including an EventType indicating which event the notification message is configured to. 16. The method according to claim 11, in which the step of generating a notification message by means of a notification generation function comprises the step of generating a notification message including a FilteringValue indicating information for executing content previously stored in the terminal. 17. A method for transmitting a message in a broadcast system, the method comprising the steps of:
receiving, by the notification event function, a notification indicating content change information provided from the content creating unit, generating a notification event message and transmitting the generated notification event message to the notification generation function;
generating, by the notification generation function, a notification message using a notification event message received from the notification event function, and transmitting the generated notification message to the notification distribution / adaptation function, wherein the notification message includes a NotificationType indicating whether the notification message is a message a notification to be used by the user, or a notification message to be used by the terminal, PresentationType indicating the type presenting a notification message, an EventType indicating which event the notification message is configured to, and a FilteringValue indicating information for executing content previously stored in the terminal; and
receive, via the distribution / adaptation function of the notifications, a notification message from the notification generation function, and transmit the received notification message to the terminal via a specific network. 18. A terminal device for receiving a broadcast service from a broadcast system, the device comprising;
a receiver for receiving a notification message from the broadcast system; and
a controller for determining whether the received notification message is a notification message that should be used by the user, or a notification message that should be used by the terminal, based on the contents of the notification message, and performing the operation according to the determination result. 19. The terminal device of claim 18, wherein the controller compares the NotificationVersion included in the received notification message with the NotificationVersion included in the previous received notification message to determine whether the received notification message is a new notification message and discards the received notification message, if the received notification message is not a new notification message. 20. The terminal apparatus of claim 18, wherein the controller checks the NotificationType information of the received notification message to determine whether the received notification message is a notification message to be used by the user or a notification message to be used by the terminal. 21. The terminal apparatus of claim 18, wherein the controller checks the PresentationType information of the received notification message and controls the display operation of the received notification message according to the verification result. 22. The terminal device according to item 21, in which, if PresentationType information of the received notification message is 0, the controller performs a control operation to display the notification message through the display immediately after receiving the notification message. 23. The terminal device according to item 21, in which, if the PresentationType information of the received notification message is 1, the controller performs a control operation to store the notification message in a storage device. 24. The terminal device according to item 21, in which, if the PresentationType information of the received notification message is 2, the controller performs a control operation to overlay the notification message on the current service and display the overlay result through the display. 25. The terminal apparatus of claim 18, wherein the controller verifies the UsageType indicating the use of SessionInformation, indicating session information for receiving data, in the notification message, and controls the session access unit so that it accesses according to the application. 26. The terminal device according A.25, in which, if UsageType is 0, the controller controls the session access unit so that it accesses the session according to Sessionlnformation and receives the file. 27. The terminal device according A.25, in which, if UsageType is 1, the controller controls the session access unit so that it accesses the session and receives the corresponding service that the user has joined. 28. The terminal apparatus of claim 18, wherein the controller checks the EventType of the notification message and performs an appropriate operation according to the EventType of the received notification message. 29. The terminal apparatus of claim 18, wherein the controller checks the FilteringValue of the notification message and provides the user with content whose FilteringValue is equal to the FilteringValue from the content previously stored in the terminal. 30. A terminal device for receiving a broadcast service from a broadcast system, the device comprising:
a receiver for receiving a notification message from the broadcast system; and
a controller for determining whether the received notification message is a notification message that should be used by the user, or a notification message that should be used by the terminal, according to the NotificationType information of the notification message, controlling the operation of displaying the notification message according to PresentationType information of the notification message, UsageType verification of the notification message, to access the session according to the use of the SessionInformation of the notification message, verification of the Notification information Version of the notification message to determine whether the received notification message is a new received notification message, checking the EventType of the notification message to perform the appropriate operation according to the type of event of the received notification message, and checking the FilteringValue of the notification message to provide the user with a FilteringValue of which FilteringValue of previously saved content. 31. A method for receiving a broadcast service from a broadcast system, comprising the steps of:
receiving, by the terminal, a notification message from the broadcast system;
determining whether the notification message is a notification message to be used by the user or a notification message to be used by the terminal; and
perform any of the PresentationType verification operations of the notification message if the notification message is a notification message to be used by the user, and the SessionInformation verification operation of the notification message to access the corresponding session if the notification message is a notification message that should be used by the terminal. 32. The method of claim 31, wherein the step of determining whether the received notification message is a notification message that should be used by the user or a notification message that should be used by the terminal comprises determining that the received notification message is a message a notification to be used by the user if the NotificationType information of the notification message is 0, and it is determined that the received notification message is a notification message that ave to be used by the terminal if the information NotificationType notification message is equal to 1. 33. The method according to p, optionally containing stages in which:
comparing the NotificationVersion of the received notification message with the NotificationVersion of the previous received notification message; and
discard the received notification message if the received notification message is not a new notification message as a result of the comparison. 34. The method of claim 32, further comprising checking the PresentationType information of the notification message if the received notification message is a notification message to be used by the user. 35. The method according to clause 34, further comprising the step of displaying the received notification message to the user immediately after receiving the notification message if the PresentationType information of the notification message is 0. 36. The method according to clause 34, further comprising storing the received notification message in a storage device if the PresentationType information of the notification message is 1. 37. The method according to clause 34, further comprising the step of overlaying the received notification message on top of the current service and displaying the result of the overlay to the user if the PresentationType information of the notification message is 2. 38. The method according to p, further comprising a step of checking the UsageType indicating the use of the SessionInformation of the received notification message, and accessing the session according to the application of SessionInformation. 39. The method according to 38, further comprising the step of accessing the session according to SessionInformation and accepting the file if UsageType is 0. 40. The method according to § 38, further comprising the step of accessing the session and accepting the corresponding service that the user has joined if UsageType is 1. 41. The method of claim 31, further comprising inspecting the EventType of the notification message to detect content included in the received notification message. 42. The method according to p, optionally containing stages in which:
check the FilteringValue of the received notification message; and
provide the user with content whose FilteringValue is equal to
FilteringValue from previously saved content. 43. A method for receiving a broadcast service from a broadcast system, comprising the steps of:
receiving, by the terminal, a notification message from the broadcast system;
checking the NotificationVersion notification messages to determine whether the received notification message is a new received notification message;
if the received notification message is a new received notification message, the NotificationType of the notification message is checked to determine whether the received notification message is a notification message to be used by the user or a notification message to be used by the terminal;
checking the EventType of the notification message to detect the contents included in the notification message;
checking the PresentationType of the notification message if the received notification message is a notification message to be used by the user;
perform the operation of displaying the notification message according to the PresentationType of the notification message; and
check the FilteringValue of the received notification message and provide the user with content whose FilteringValue is equal to the FilteringValue from the content previously stored in the terminal. 44. The method according to item 43, further comprising stages, in which:
checking the UsageType notification message if the received notification message is a notification message to be used by the terminal; and
determine the use of SessionInformation according to UsageType and access the corresponding session. 45. A broadcast system comprising:
a notification message transmitter for generating a notification message and transmitting the notification message to the terminal when receiving a notification event message generated as a result of content change information provided from the content creating unit or change information of the broadcast system related to the content transfer; and
a terminal for receiving a transmitted notification message, determining whether the notification message is a notification message that should be used by the user, or a notification message that should be used by the terminal, checking the PresentationType of the notification message if the notification message is a notification message that should be used by the user, and checking the SessionInformation of the notification message to access the corresponding session if the notification message is co scheniem notifications to be used by the terminal. 46. The broadcast system of claim 45, wherein the notification message transmitter comprises:
a notification generation function for generating a notification message that should be used by the user or a notification message that should be used by the terminal using the notification event; and
a notification distribution / adaptation function for transmitting a notification message generated by the notification generation function to a terminal via a specific network. 47. A method for providing a broadcast service, comprising the steps of:
receiving a notification event message generated as a result of content change information provided from the content creating unit, or broadcast system change information related to the content transfer;
generating a notification message that must be used by the user of the terminal designated to use the notification message, or a notification message that must be used by the terminal using the generated notification event message;
transmit the generated notification message to the terminal through a specific network;
receive the transmitted notification message;
determining whether the notification message is a notification message to be used by the user or a notification message to be used by the terminal; and
perform any of the PresentationType verification operations of the notification message if the notification message is a notification message to be used by the user, and the SessionInformation verification operation of the notification message to access the corresponding session if the notification message is a notification message that should be used by the terminal. 48. A computer-readable recording medium storing a program for implementing a method for transmitting a message in a broadcast system, the method comprising the steps of:
receiving a notification indicating the content change information, generating a notification event message to generate a notification message, and transmitting the generated notification event message;
receive a notification event message, generate a notification message that should be used by the user, or a notification message that should be used by the terminal, and transmit the generated notification message; and
receive the notification message and transmit the received notification message to the terminal through the specific network. 49. A computer-readable recording medium storing a program for implementing a method for a terminal, the method comprising the steps of:
receive a notification message from the broadcast system;
determining whether the notification message is a notification message to be used by the user or a notification message to be used by the terminal; and
perform any of the PresentationType verification operations of the notification message if the notification message is a notification message to be used by the user, and the SessionInformation verification operation of the notification message to access the corresponding session if the notification message is a notification message that should be used by the terminal.

Images