KR20070049042A - Method and apparatus for delivering service guide contents source and notification event information in mobile broadcast system - Google Patents

Abstract

The present invention provides a method and apparatus for delivering a content event related to a service guide (SG) and a notification event that may occur in a content provider from a content provider (CC) to a portable broadcast system in a mobile broadcasting system. In more detail, in the service guide content supply source SGCCS of a content provider CC that provides a broadcast service, a request message including content information and attribute values for generation of the service guide is sent to the broadcast service application block BSA. Send to the service guide application source (SGAS), and receives a response message indicating the result of the generation of the service guide in response to the request message. In addition, the content provider CC may send a request message including notification event information and attribute values for requesting generation of a notification event indicating a change in the portable broadcasting service. And a response message indicating a result of generating the notification event in response to the request message. The present invention can improve the reliability of message transmission by defining a request message and a notification event message for service guide related content information and providing a delivery and response operation of the messages.

OMA BCAST, Service Guide, Backend Interface, Notification

Description

METHOD AND APPARATUS FOR DELIVERING SERVICE GUIDE CONTENTS SOURCE AND NOTIFICATION EVENT INFORMATION IN MOBILE BROADCAST SYSTEM}

1 is a diagram illustrating a configuration example of a portable broadcasting system for transmitting a service guide to a mobile terminal according to a preferred embodiment of the present invention.

2 is a diagram showing the structure of a notification interface for providing a notification message in a portable broadcasting system according to a preferred embodiment of the present invention.

3 is a diagram illustrating a message transmission flow between logical entities for providing a service guide in a portable broadcasting system.

4 is a diagram illustrating a message transmission flow between logical entities for providing a notification message in a portable broadcasting system.

5 is a diagram illustrating a protocol stack used for transmitting content information related to a service guide in an SG1 interface according to a preferred embodiment of the present invention.

6 is a flowchart illustrating an operation of transmitting content information through an SG1 interface according to a preferred embodiment of the present invention.

FIG. 7 illustrates a protocol stack used for transmitting notification event information in an NT-1 interface according to a preferred embodiment of the present invention. FIG.

8 is a flow diagram illustrating the operation of sending a notification message over an NT-1 interface in accordance with a preferred embodiment of the present invention.

9 illustrates a protocol stack used for providing a service guide source or requesting a notification event in accordance with a preferred embodiment of the present invention.

10 is a flow diagram illustrating operations for delivering a service guide source in accordance with a preferred embodiment of the present invention.

11 is a flowchart illustrating an operation for delivering a notification event in accordance with a preferred embodiment of the present invention.

The present invention relates to a broadcast system or a mobile communication system supporting a broadcast service (hereinafter referred to as BCAST), and in particular, content information related to a service guide (hereinafter referred to as SG) and a notification event that may occur in a content provider. The present invention relates to a method and apparatus for delivering a notification event.

Today, due to the development of communication and broadcasting technology, a broadcasting system or a mobile communication system provides portable broadcasting, and can transmit packet data through a broadcast channel as well as a general broadcasting service limited to a conventional voice and image. Mobile Broadcast is being discussed. The portable broadcast includes the discovery of a service by a mobile terminal such as a mobile phone, a notebook computer, a personal digital assistant (PDA), etc. that can receive the portable broadcast, a subscription of the service by the mobile terminal, and various control information for receiving the service. It can be made of a process of providing, the transmission of the service and the reception of the service by the mobile terminal.

The Open Mobile Alliance (hereinafter referred to as OMA) is an organization that researches standards for interoperability of individual mobility solutions, and is mainly responsible for setting various application standards for mobile games and Internet services. Among the working groups of OMA, in particular, the OMA BAC (Mobile Broadcast Sub Working Group) is studying a technology for providing a broadcast service using a mobile terminal.

In the mobile broadcasting system discussed in OMA, a mobile terminal for receiving a broadcast service includes a service guide (SG) including description information about the service itself, billing information about the service, and information on how to receive the service. Information is received, and the service is received using the service guide information.

Some of the information in the service guide may change at any time, so that whenever a particular service changes, the service guide for that service continues to be transmitted repeatedly. In addition, considering the appearance of a new mobile terminal due to the characteristics of the mobile broadcast, the service guide for the mobile broadcast service is repeatedly transmitted even if there is no change. That is, for example, when a user who wants to receive a mobile broadcast by newly turning on the mobile terminal newly emerges, or when a mobile terminal that needs to receive a new service guide due to the movement of the user appears, the mobile terminal has already appeared. Receives a service guide separately from the mobile terminals receiving the.

In the portable broadcasting system configured as described above, it is natural that reliable and efficient transmission and response of a notification event indicating service guide information, changes to broadcast service, and the like is very important. Therefore, the content provider delivers the content information and notification event information for generating the service guide of BCAST, determines the information elements and attributes necessary to compose related messages, and responds whether or not to fulfill the request. There is a need for specific skills to do this.

Accordingly, the present invention, which is designed to solve the problems of the prior art operating as described above, provides a method and apparatus for delivering content information and notification event for service guide generation in a portable broadcasting system.

The present invention provides a method and apparatus for determining information elements and attribute values necessary for composing messages related to the transmission of a service guide and notification event in a portable broadcast system.

The present invention provides a method and apparatus for responding to a result of generating a service guide and notification event in a portable broadcasting system.

Hereinafter, with reference to the accompanying drawings will be described in detail the operating principle of the preferred embodiment of the present invention. In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

The following detailed description will present representative embodiments of the present invention for achieving the above-described technical problem. Also, for convenience of description, the names of entities defined in BCAST of 3GPP (3G Generation Partnership Project), which is an asynchronous mobile communication standard, or OMA (Open Mobile Alliance), a standard organization for application of mobile terminals, will be used. These are not intended to limit the scope of the present invention, it is a matter of course that the present invention can be applied to a system having a similar technical background. Hereinafter, the OMA BCAST technology, which is one of the portable broadcast technology standards, will be described in order to provide specific examples in describing the embodiments of the present invention.

1 illustrates a configuration example of a portable broadcasting system for transmitting a service guide to a mobile terminal according to a preferred embodiment of the present invention. First, Tables 1 and 2 show interfaces used between components (logical entities) of FIG. 1.

In FIG. 1, a content provider (CC) block 101 is a provider of a broadcast service (hereinafter, referred to as a BCAST service), and the BCAST service is a file of a conventional voice / video broadcast service, a music file, or a data file. It may be a download service. The content provider 101 includes a service guide content creation source (hereinafter referred to as SGCCS) 102, content information necessary for constructing a service guide of a BCAST service, performance information of a mobile terminal, and a user profile. , Content time information, and the like, to the Service Guide Application Source (BSAS) 105 of the BCAST Service Application Block (BCSA) 104 via the SG1 interface 103. do.

The BCAST service application block 104 receives BCAST service data from the content provider block 101 and processes the BCAST service data into a form suitable for the BCAST network to create BCAST service data. In addition, the BCAST service application block 104 is responsible for generating standardized metadata for portable broadcast guidance. The SGAS 105 configures the service guide source data including various information necessary for the configuration of the service guide, such as schedule information and location information, including service and content information received from the SGCCS 102, and the SG2 interface 106. It is transmitted to the service guide generation (Service Guide Generation: SG-G) (109) of the BCAST Service Distribution / Adaptation block (BSD / A) (108).

In FIG. 1, the BCAST service distribution / adaptation block 108 sets a bearer for transmitting BCAST service data supplied from the BCAST service application block 104, determines a transmission schedule of the BCAST service, and portable broadcast. It is responsible for generating guide information. The BCAST service distribution / adaptation block 108 is connected to a broadcast distribution system (BDS) 122, which is a network for transmitting BCAST service data, and a bidirectional network 123 supporting bidirectional communication.

The SG-G 109 generates a service guide using the service guide source data and converts the service guide into a service guide distribution unit (SG Distribution: SG-D) 110 and an SG-5 interface 117. Transfer to the mobile terminal (Terminal) 119 through. If the service guide is delivered through the BDS 122 or the bi-directional network 123 supporting bi-directional communication, or if a match is required with respect to the system or network, the service guide generated from the SG-G 109 is adapted to the service guide. SG Adaptation (hereinafter referred to as SG-A) 111 is delivered to the SG-D 110 or via the SG-B1 interface 116 to the BSC Service Distribution block 121 to be described later. Delivered.

In FIG. 1, a BCAST subscription management block (hereinafter referred to as BSM) 113 manages subscription information for receiving a BCAST service, service provision information, and device information for a mobile terminal receiving a BCAST service. The service guide subscription source (hereinafter referred to as SGSS) 114 of the BCAST subscription management block 113 is a subscription-related, provisioning-related source and purchase information, promotion-related information, etc. The source of the message is delivered to the SG-G 109 generating a service guide through the SG4 interface 112.

In FIG. 1, the BDS service distribution block 121 distributes all received BCAST services through a broadcast channel or an interaction channel, and may exist according to the type of the BDS 122. An object that may or may not exist. The BDS 122 is a network transmitting BCAST service, and may be, for example, a broadcasting network such as DVB-H, MBMS of 3GPP, BCMCS of 3GPP2, and the like. The bidirectional network 123 transmits the BCAST service one-to-one or exchanges control information and additional information related to receiving the BCAST service in both directions, and may be, for example, an existing cellular network.

In FIG. 1, the mobile terminal 119 is a terminal capable of receiving a BCAST service and has a function of being connected to a cellular network according to terminal performance. The mobile terminal 119 includes a service guide client (hereinafter referred to as SG-C) to receive a service guide transmitted through the SG5 interface 117 or a notification message transmitted through the SG6 interface 118. Receives and performs the appropriate operation for receiving BCAST service.

Tables 3 to 5 below briefly illustrate the functions of the main components (logical entities) of FIG. 1 in the standard of the OMA BCAST service.

2 is a diagram illustrating a notification interface structure for providing a notification message in a portable broadcasting system according to a preferred embodiment of the present invention. A notification event may occur in several logical entities, and information about the notification event generated in each logical entity is transferred to other logical entities along the corresponding interface, so that the notification message according to the notification event or the notification event in the other logical entity. To generate.

Referring to FIG. 2, a content provider (CC) 201 is a provider of a broadcast (hereinafter referred to as BCAST) service, and the BCAST service is a conventional audio / video broadcast service and file (music file or data file). It may be a download service. When a problem or change occurs in the supply of the BCAST service, the content provider 201 may notify the Notification Event Function (NTE) located inside the BCAST Service Application (hereinafter referred to as BSA) 202 (NTE). The change is notified to 202-1.

The BCAST service application 202 receives the data of the BCAST service from the content provider 201 and processes the data into a form suitable for the BCAST network to create BCAST service data, and generates standardized metadata for portable broadcast guidance. It plays a role. In addition, a notification generation function (NTG) 204 located within the BCAST Subscription Management unit (BCSM) 204 is received from the content provider 201 is notified of changes in the service for BCAST. Notify by -1).

The BCAST service distribution / adaptation unit (BSD / A) 203 creates a role of setting up a bearer to transmit BCAST service data supplied from the BCAST service application 202, determines a transmission schedule of the BCAST service, and generates a portable broadcast announcement. It is connected to a broadcast distribution system (BDS) 206 that actually provides a broadcast service and an interworking network 207 that supports two-way communication. It also has a Notification Distribution / Adaptation Function (NTDA) 203-1, receives a notification message from the BCAST Subscription Management 204, and connects the BDS 206 or an interworking unit. Transmit to one user or multiple users via network 207.

The BCAST Subscription Management unit 204 manages subscription information and service provision information for receiving the BCAST service and device information on the equipment receiving the BCAST service, and in particular, a notification generation function (NTG). 204-1, receiving information about the notification event from the content provider 201 and the BDS 206 to generate a notification message or generating a notification message for the BCAST service itself event.

The BDS Service Distribution 205 distributes all the received BCAST services through a broadcast channel or an interaction channel, and exists according to the type of the BDS 206. An object that may or may not exist.

The BDS 206 is a network transmitting BCAST service, and may be, for example, DVB-H, MBMS of 3GPP, BCMCS of 3GPP2, or the like. In addition, when a change occurs in transmitting a specific BCAST service, if there is an X-1 interface 231 or a BDS service distribution unit 205, the BCAST service distribution / adaptive unit through the NT-B1 interface 224. The 203 is notified of the change.

The interworking network 207 transmits the BCAST service one-to-one or exchanges control information and additional information related to receiving the BCAST service in both directions, and may be, for example, an existing cellular network.

The mobile terminal 208 is a terminal capable of receiving a BCAST service and has a function of being connected to a cellular network according to the capability of the terminal. An example is a terminal, ie a cellular phone, that can be connected to a cellular network. The mobile terminal 208 receives a notification message transmitted through the NT-5 interface 225 by a notification client function (NTC) 208-1 to perform an appropriate operation, or NT- 6 receive the notification message sent through the interface 226 and perform an appropriate operation,

Next, interfaces between the logical entities will be described.

The NT-1 interface 221 is an interface between the notification event unit 202-1 and the content provider 201 located in the BCAST service application 202. When an event requiring notification occurs in the content provider 201, It is used to deliver the corresponding notification event to the notification event unit 202-1.

The NT-2 interface 222 is an interface from the notification event unit 102-1 located in the BCAST service application 202 to the notification generating unit 204-1 of the BCAST subscription management unit 204. The notification generating unit 204 In order to generate a notification message in -1), information necessary for generating a notification message or notification message is carried.

The NT-4 interface 223 transfers the notification generation unit 204-1 located in the BCAST subscription management unit 204 from the BCAST service distribution / adaptation unit 203 to the notification distribution / adaptation unit (NTDA) 203-1. It is an interface, and transmits the notification message generated by the notification generating unit 204-1 to the notification distribution / adapting unit 203-1 in order to be transmitted to the BDS 206 or the interworking network 207, or the BDS 206. When the event occurs in the notification distribution / adaptor 203-1 for the event is used to transmit.

NT-5 interface 225 is a notification message transmitted from the notification distribution / adaptation unit (NTDA) 203-1 of the BCAST service distribution / adaptation unit 203 directly to the terminal via a broadcast channel via the BDS (206) Interface used when transmitted, used to send a notification message to one terminal or multiple terminals.

The NT-6 interface 226 has a dedicated channel or interworking network with the terminal through which the notification message transmitted from the notification distribution / adapter 203-1 of the BCAST service distribution / adapter 203 passes through the interworking network 207. An interface used when directly transmitted to a terminal through a broadcast channel provided in 207, and used to transmit a notification message to one terminal or a plurality of terminals.

NT-B1 interface 224 provides BCAST service distribution / adaptation, which is used by BCAST service distribution / adaptation unit 203 to set up a transmission path that will be used by BDS 206 or as a reception path for event information generated in BDS 206. It is an interface between the adaptation unit 203 and the BDS service distribution unit 205.

The X-1 interface 231 is configured to set up a transmission path that the BCAST service distribution / adaptation unit 203 will use in the BDS 206 when the BDS service distribution unit 205 does not exist, or an event occurring in the BDS 206. Interface used as a receiving path for information. When the BDS service distribution unit 205 is present, it is used as an interface between the BDS 206 and the BDS service distribution unit 205 to notify of an event that has occurred in the BDS 206.

The X-2 interface 232 is an interface used for setting up a transmission path that the BCAST service distribution / adaptation unit 203 will use in the interworking network 207 when the BDS service distribution unit 205 does not exist. When the BDS service distribution unit 205 is present, it is used as an interface between the BDS 206 and the interworking network 207 to set up a bearer to use a notification message in the interlocking network 207 and to transmit a notification message.

The X-3 interface 233 is an interface between the BDS 206 and the terminal 208 and is used for all messages transmitted in the BCAST service or 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 an interworking channel interface between the BDS service distribution unit 205 and the terminal 208.

The X-6 interface 236 is a bidirectional interface through which the interworking network 207 can transmit control information related to the BCAST service.

The notification event unit 202-1 transmits the information necessary for generating the notification message to the notification generation unit 204-1, and when the notification event (i.e., notification event) has occurred, the notification event unit 202-1 receives the notification event. Information is sent to the notification generating unit 204-1. The notification generation unit 204-1 receives the information and the event necessary for generating the notification message from the notification event unit 202-1, generates a notification message, or generates a notification message through the notification distribution / adaptation unit 203-1. When the notification event of 206 is received, a notification message is generated and transmitted to the notification distribution / adaptation unit 203-1. When the notification message is to be generated, when it is necessary to notify the start of the service again, the content provider 201 is notified that there is a change in the information of the service and it is necessary to send a new portable broadcast guide and BDS It may be the case that a special event occurs at 206.

The notification distribution / adaptation unit 203-1 serves to transmit a notification message through the NT5 225 or the NT-6 226, and changes of information on a specific mobile broadcasting service from the BDS 206, For example, when receiving the adjustment of the transmission rate or the service unavailable due to a wireless network environment, the notification event is transmitted to the notification generating unit 204-1 through the NT-4 223. .

3 illustrates a message transmission flow between logical entities for providing a service guide in a portable broadcasting system. Here, reference numeral 301 denotes the SGCCS unit 102 of FIG. 1, reference numeral 302 denotes the SGAS unit 105 of FIG. 1, reference numeral 303 denotes the SGSS unit 114 of FIG. 1, and reference numeral 304 denotes the SG-G of FIG. 1. / D / A (109, 110, 111).

Referring to FIG. 3, in step 311, the SGCCS unit 301 delivers information and attribute values about content to the SGAS unit 302 in relation to the BCAST service. In step 312, the SGAS unit 302 uses the attribute values received from the SGCCS 301, and transfers information and attribute values for content and services to the SG-G / D / A 304 in accordance with the BCAST format. In step 313, the SG-G / D / A 304 may request information related to provisioning from the SGSS 303. In step 314, the SGSS 303 provides the supply related information requested to the SG-G / D / A 304. In step 315, the SG-G / D / A 304 generates a service guide SG with reference to the above information.

4 illustrates a message transmission flow between logical entities for providing a notification message in a portable broadcasting system. Here, reference numeral 401 denotes a notification event function unit (NTE) 202-1 of the BCAST service application block 204 of FIG. 2, and reference numeral 402 denotes a notification generation functional unit (NTG) 402 of the BCAST subscription management block 204. Reference numeral 403 denotes a notification distribution / adaptation function unit (NTDA) 203-1 of the BCAST service distribution / adaptation block 203.

Referring to FIG. 4, in step 411 or 412, a notification event generated in the NTE 401 and the NTDA 403 is delivered to the NTG 402, or a notification event occurs in the NTG 402 or the BDS 205. do. If a notification event occurs in the content provider 201 or the BSA 202, the NTE 401, in step 411, sends an NTG 402 in the BCAST subscription management block 204 to provide an event notice including the notification event information. ) Via NT-3 interface 222. If the notification event information originated from BCAST service distribution / adaptation block 203 or BDS 205, then it passes from NTDA 403 to NTG 402 via NT-4 interface 223 as step 412. The notification event information may be generated by the NTG 402 by itself in the BSM 204 as in step 413. As an example, a notification event is generated when an upcoming service, a change of a service guide, or an emergency occurs.

As described above, the NTG 402 receives notification event information through its own NT-3 interface 222 or NT-4 interface 223. In step 414, the NTG 402 generates a notification message according to the notification event information, and the NTG 402 then transfers the notification message to NTDA through the NT-4 interface 223.

Although FIG. 4 illustrates a case where a notification event occurs in the NTE 401, the NTDA 403, the NTG 402, or the BDS 205, the notification event may naturally occur in the CC 201. In more detail, examples of the notification event generated by the CC 201 may include a failure of the CC 201 or a change of a service guide.

Therefore, in the following case, as shown in FIGS. 3 and 4, the SGCCS 102 of the CC 101 generates content information for the service guide so that the SGAS 105 of the BSA 104 may configure the service guide. A detailed information format and an operation procedure and a detailed information format and an operation procedure for generating notification event information in the CC 201 and causing the NTE 202-1 of the BSA 202 to configure a notification event will be described.

Prior to describing specific embodiments of the present invention, each column of the message schema table used herein will be described for clarity. "Name" indicates the name of the element value and the attribute value constituting the message. "Type" means whether the name is an element value or an attribute value. Each element value has the same value as E1, E2, E3, E4, E1 means the upper element value for the whole message, E2 is the lower element value of E1, E3 is the lower element value of E2, and E4 is the value of E3. Represents a lower element value. "Attribute value" is denoted by A, where A represents the attribute value of the element. For example, A below E1 represents an attribute value of E1. "Category" is used to distinguish whether or not the element or attribute value is mandatory. It has M value if it is required and O value if it is optional. "Cardinality" represents a relationship between elements and has a value of 0, 0..1, 1, 0..n, 1..n. 0 means option, 1 means mandatory relationship and n means it can have many values. For example, 0..n means that the element value may not exist or may have n values. "Description" indicates what the element or attribute value means, and "Data Type" indicates the data type of the element or attribute value. Therefore, the message format is as shown in Table 6 below.

name type category Cardinality Explanation Data type

In addition, the following will illustrate various information elements necessary for the request / response of the service guide and the notification event generation according to the preferred embodiment of the present invention, but the messages of the present invention do not necessarily include all the above information elements. Of course, some or all information elements may be used depending on the intention or need.

5 illustrates a protocol stack used for transmitting content information related to a service guide in an SG1 interface according to a preferred embodiment of the present invention. Reference numeral 501 denotes the SG1 interface 103 of FIG. 1.

Referring to FIG. 5, messages delivered through the SG1 interface 501 may be delivered in the form of text or XML (eXtensible Markup Language). The format of the messages will be described in detail below. Messages over the SG1 interface 501 are transmitted using Internet Protocol (IP) 503, Transfer Control Protocol (TCP) 505, Hyper Text Transfer Protocol (HTTP) 507, and SGCCS in CC 101. 102 sends content information related to the service guide via HTTP POST to SGAS 105 in BSA 104. In this case, HTTP POST refers to a method of delivering data using a file without limitation of length, unlike an HTTP GET method using a URL (Universal Resource Locator). In addition, the SGAS 105 receives the content information from the SGCCS 102 and transmits the result of the generation of the service guide source data in the HTTP RESPONSE message or transmits the result through the HTTP POST.

6 is a flowchart illustrating an operation of transmitting content information through an SG1 interface according to a preferred embodiment of the present invention. Here, reference numeral 601 denotes the SGCCS 102 of FIG. 1, and reference numeral 602 denotes the SGAS 105 of FIG. 1.

Referring to FIG. 6, in step 611, the SGCCS 601 provides the SGAS 602 with information and attribute values of contents necessary for generating a service guide in a request message. The request message provided in step 611 is the same as the SGCCSReq message shown in Table 7 below. The SGAS 602 generates service guide source data using the information and attribute values received from the SGCCS 601 and additional information required, and then sends a response message to the SGCCS 601 to the completion of creation in step 612. The response message is the same as the SGCCSRes message shown in Table 8 below.

When the service guide source data is immediately generated according to the content information, the SGAS 602 sends the result of the generation of the service guide source data to the HTTP RESPONSE message corresponding to the request message in step 611. On the other hand, if the service guide source data is not immediately generated, the session between the SGAS 602 and the SGCCS 601 is terminated, and then, at the completion of the generation of the service guide source data, the SGAS 602 determines whether the service guide source data is completed. The result of the generation may be notified through HTTP POST using SGCCSId and CCAddress included in the SGCCSReq message. In this case, the SGAS 602 may send responses to various request messages of the SGCCS 601 to the SGCCS 601 in a single message.

The main information elements in Table 7 are as follows.

SGCCSId is a unique identifier representing the SGCCSReq message requested by SGCCS and is represented by a 32-bit unsigned integer. CCAddress represents the address of the CC to receive the response of the SGCCSReq message. "Content", an information element representing service guide related information, is a content ID (CCContentID), which is an attribute value, and content information (ContentInfo), a name of a content fragment, a description, and a parent rating (ParentalRating) as child elements. , Target user profile (TargetUserProfile), and genre.

As shown in Table 8, SGCCSId included in the SGCCSRes message is the same as that included in the SGCCSReq message. The attribute value "Response" indicating the result of the generation of the service guide source data has one of the value "0" indicating success or the value "1" indicating failure.

7 illustrates a protocol stack used for transmitting notification event information in an NT-1 interface according to a preferred embodiment of the present invention. Reference numeral 701 denotes the NT-1 interface 221 of FIG. 2.

Referring to FIG. 7, messages delivered through the NT-1 interface 701 may be delivered in text or XML form. The format of the messages will be described in detail below. Messages over NT-1 interface 701 are sent using IP 703, TCP 705, HTTP 707, and CC 201 is HTTP POST to NTE 202-1 in BSA 202. Send notification event information through. In addition, the NTE 202-1 receives the notification event information from the CC 201 and transmits the result of generating the notification event in an HTTP RESPONSE message or transmits the result through an HTTP POST.

8 is a flowchart illustrating an operation of transmitting notification event information through an NT-1 interface according to a preferred embodiment of the present invention. Here, reference numeral 801 denotes a CC 201 of FIG. 2, and reference numeral 802 denotes an NTE 202-1 of FIG. 2.

Referring to FIG. 8, in operation 811, the CC 801 transmits a notification event message requesting generation of a notification event to the NTE 802. The notification event message provided in step 811 includes notification event information as shown in the CCNTEReq message shown in Table 9 below. The NTE 802 generates a notification event using the notification event information received from the CC 801, and then, in step 812, the NTE 802 sends a response message to the CC 801 to indicate completion of creation. The response message is the same as the CCNTERes message shown in Table 10 below.

When the notification event is generated immediately, the NTE 802 sends the result of generating the notification event to the HTTP RESPONSE message corresponding to the request message in step 611. On the other hand, when the notification event is not generated immediately, the NTE 802 terminates the session between the CC 801 and the NTE 802 and then, upon completion of generating the notification event, inform the CC 801 of generating the notification event. , May be notified through HTTP POST using CCNTEId and CCAddress included in the CCNTEReq message. The CCNTERes message may include the results of various request messages of the CC 801.

The main information elements in Table 9 are as follows.

CCNTEId is a unique identifier representing the CCNTEReq message provided by the CC and represented by a 32-bit unsigned integer. CCAddress represents the address of the CC to receive the response of the CCNTEeq message. "NotificationEvent", an information element representing notification event-related information, is an attribute value of NotificationType and Validity, and its subelements are Name, Description, Priority, and Extension. It includes a URL (ExtensionURL) and media information (MediaInformation). The media information may include a picture, a video, an audio, and the like together with a MIME (Multipurpose Internet Mail Extension) type and a URI.

As shown in Table 10, CCNTEId included in the CCNTERes message is the same as that included in the CCNTEReq message. The attribute value "Response" indicating the result of the notification event generation has either a value "0" indicating success or a value "1" indicating failure.

9 illustrates a protocol stack used to provide service guide source data required for the construction of a service guide or to deliver a request message of a notification event according to a preferred embodiment of the present invention. As shown, an SG1 interface or an NT-1 interface 901 is used as a backend interface for the delivery of a service guide source or a request for a notification event between the SGCCS unit and the SGAS unit.

Referring to FIG. 9, HTTP 907 based on IP 903 and TCP 905 is used for message transmission over the SG1 / NT-1 interface 901 as shown in FIG. 5 or FIG. 7. do. In another embodiment, a web service protocol 909 for transmitting XML data, such as Simple Object Access Protocol (SOAP), eXtensible Markup Language-Remote Procedure Call (XML-RPC), and Blocks Extensible Exchange Protocol (BEEP), may be used. It may be used at the upper layer of HTTP 907. When the web service protocol 909 is used, the message of the present invention is included in the BODY of the web service protocol and transmitted.

10 is a flowchart illustrating an operation for delivering service guide (SG) source data through an SG-1 interface according to a preferred embodiment of the present invention.

Referring to FIG. 10, in step 1011, the SGCCS 1001 delivers SG source data necessary for constructing a service guide using the SG1 interface to the SGAS 1002. A message format (XML Schema) for delivering the SG source data is shown in Table 11 below. In step 1012, the SGAS 1002 responds to the SGCCS 1001 with the result of processing the SG source data as shown in Table 12 below.

11 is a flowchart illustrating an operation of delivering a notification event through an NT-1 interface according to a preferred embodiment of the present invention. Here, reference numeral 1101 denotes a CC 201 of FIG. 2, and reference numeral 1102 denotes an NTE 202-1 of FIG. 2.

Referring to FIG. 11, in operation 1111, the CC 1101 transmits a notification event to the NTE 1102 using a message configured as shown in Table 13 below. In step 1112, the NTE 1102 responds to the CC 1101 with the result of processing the notification event as shown in Table 14 below.

Table 15 below shows examples of status codes included in the response messages shown in Table 12 and Table 14. It can also be used in the response messages of Tables 8 and 12. That is, the response messages include the status code indicating the processing result of SG source data or notification event. When the SG source data or notification event is processed normally, the status code is '000' and the terminal knows that the processing result is successful according to the status code. Tables 15a to 15e below show <Table 15> for convenience.

Table 15 is stored in the network entity and the terminal sending the response message, and additional values may be defined according to the purpose of the operator. In addition, the values of the status codes shown in Table 15 may be used in a wide range of cases in which not only the response message relating to the preferred embodiment of the present invention but also the result of the processing in the system or the terminal for providing the mobile broadcasting service should be answered. It can be used for (Global) purposes and is also called a global status code in this respect.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by those equivalent to the scope of the claims.

In the present invention operating as described in detail above, the effects obtained by the representative ones of the disclosed inventions will be briefly described as follows.

The present invention defines a content information providing message for the service guide and a notification event message from the CC for generating the notification event, so that the content provider can deliver the content information and the notification event for the service guide generation in the portable broadcasting system. Provides delivery and response behavior of messages. Each response message sends the result of completion of operation in the BSA to improve the reliability of the message operation from the CC and to send the response messages collectively after the operation is completed in the BSA to improve efficiency in the network. Can be improved.

Claims (6)

In the method for transmitting the content information necessary for generating a service guide of the portable broadcasting service in a wireless communication / broadcasting system supporting a portable broadcasting (BCAST) service, Providing, at a service guide content supply source (SGCCS) of a content provider (CC) providing a broadcast service, a request message including content information and attribute values for generating the service guide source data; The service guide application source (SGAS) of the broadcast service application block (BSA) generates the service guide source data using the content information and attribute values included in the request message, and responds to indicate a result of generating the service guide source data. And transmitting a message to the SGCCS. The method of claim 1, wherein the request message, SGCCSId, which is a unique identifier representing the request message sent by the SGCCS, CCAddress indicating the address of the CC to receive the response of the request message; As content information necessary for generating the service guide source data, the content ID (CCContentID), which is an attribute value, and the content information (ContentInfo), the name of the content fragment, the description, and the parent rating (ParentalRating) as sub-elements. And at least one of a target user profile (TargetUserProfile) and a genre (Genre). The method of claim 1, wherein the response message, SGCCSId, which is a unique identifier representing the request message sent by the SGCCS, And a property value "Response" indicating success or failure of the generation of the service guide source data. In the method for transmitting information required for generating a notification event of the portable broadcasting service in a wireless communication / broadcasting system supporting a portable broadcasting (BCAST) service, Providing, by a content provider (CC) providing a broadcast service, a request message including notification event information and attribute values for requesting generation of a notification event indicating a change situation of the portable broadcasting service; The notification event unit (NTE) of the broadcast service application block (BSA) generates a notification event by using the notification event information and attribute values included in the request message, and sends a response message indicating a result of generating the notification event to the CC. And transmitting the notification event information. The method of claim 4, wherein the request message, CCNTEId, a unique identifier representing the request message sent by the CC; CCAddress indicating the address of the CC to receive the response of the request message; As information elements required for generating the notification event, notification type and validation time, which are attribute values, and name, description, priority, and extended URL (as sub-elements) ExtensionURL) and media information (MediaInformation). The media information may include at least one of a picture, a video, and an audio together with a MIME (Multipurpose Internet Mail Extension) type and a URI. The method of claim 4, wherein the response message, CCNTEId, a unique identifier representing the request message sent by the CC; And a property value "Response" indicating success or failure in generating a notification event.

Images