KR101263504B1 - 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 service guide application source (SGAS) for information on services and contents in order to provide a service guide in the portable broadcasting system in a wireless communication / broadcasting system supporting a broadcast (BCAST) service. Is included in the service guide generation request message and provided as a service guide subscription source (SGSS), and the SGSS generates service guide and provisioning information when the service guide generation request message is received. A guide generation response message is provided to the SGAS, and the service guide generation request message includes an identifier (SGASProvreqid) of the SGAS requesting the guide generation of the service and the content and a BAST address of the SGAS. Including information (BSAAddress) All.

Mobile Broadcasting System, Notification Event, Notification Message, Content Information

Description

Device and method for transmitting service guide content and notification event information in mobile broadcasting system {METHOD AND APPARATUS FOR DELIVERING SERVICE GUIDE CONTENTS SOURCE AND NOTIFICATION EVENT INFORMATION IN MOBILE BROADCAST SYSTEM}

1 is a view showing a configuration example of a mobile broadcasting system to which the present invention is transmitted to transmit a service guide to a mobile terminal;

2 is a diagram illustrating a notification interface structure defined in OMA BCAST for providing a notification message in a mobile broadcasting system;

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.

FIG. 5 illustrates a data model of a service guide for generating a service guide in OMA BCAST.

6 is a diagram illustrating a protocol stack used for transmitting a notification event in an NT-3 interface.

7 is a flow diagram of message transmission through NT-3 in OMA BCAST;

8 is a BCAST structure diagram proposed for receiving related information for generating provisioning in OMA BCAST;

9 is a message flow diagram for FIG. 8;

10 is a diagram of a transport protocol stack of SG-3 in OMA BCAST,

11 is a flow chart of message transmission through SG-3 in OMA BCAST;

12 is a view for explaining delivery of a request message for providing a service guide source or providing a notification event to a backend interface of SG-3 or NT-3 according to the present invention;

13 is a signal flow diagram for service guide source delivery through SG-3 between SGAS and SGSS in accordance with the present invention;

14 is a signal flow diagram for delivery of notification events over NT-3 between NTE and NTG in accordance with the present invention.

The present invention relates to an apparatus and method for transmitting a message supporting a broadcast service (hereinafter referred to as BCAST), and more particularly, to an apparatus and method for delivering changes of a system and a service through a notification message. It is about.

Today, due to the development of communication and broadcasting technology, it has been developed to provide portable broadcasting in broadcasting system or mobile communication system. Such broadcast services are discussed as well as mobile broadcasts capable of transmitting packet data through broadcast channels as well as conventional broadcast services limited to voice and images. The portable broadcast refers to receiving a broadcast service through a mobile terminal such as a mobile phone, a notebook computer, a personal digital assistant (PDA), etc. that can receive the portable broadcast. In order to receive the broadcast service as described above, the mobile terminal must first discover the service provided. In addition, the subscriber of the mobile terminal should be in a state in which the broadcast service can be provided by subscribing to the broadcast service. In addition, in order to receive a broadcast service, the mobile terminal must receive various control information provided from a broadcast system. In a system providing a broadcast service, service data should be transmitted. As such, when a broadcast service and various kinds of information thereof are provided, the mobile terminal receives service control information and receives broadcast service data. This allows the user to watch the broadcast.

On the other hand, there is an open mobility alliance (“OMA”) as a standard research organization for providing broadcast services. The OMA is a group that studies standards for interworking of individual mobility solutions, and is mainly responsible for setting various application standards for mobile communication games and Internet services. In addition, the OMA BAC (Browser and Content) Mobile Broadcast Sub Working Group (BCA) among the working groups of OMA is studying a technology for providing a broadcast service using a mobile terminal.

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

Some of the information of the above service guide may change at any time, and therefore, whenever a specific service is changed, the service guide for the service must be repeatedly transmitted. Also, 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. Here, the appearance of a new mobile terminal refers to a case in which a new mobile terminal that has not been previously provided with a service receives a service. For example, when a user wants to receive a mobile broadcast by turning on the mobile terminal, a new user appears, or a mobile terminal that needs to receive a new service guide appears when the user moves. As such, the newly introduced mobile terminal can receive a broadcast service only by receiving a service guide separately from the mobile terminals already receiving the portable broadcast.

Therefore, it is natural that reliable transmission and response of service guide information is very important in a mobile broadcasting system. Therefore, a specific technology for delivering content information and notification events for BCAST service guide generation, determining information elements necessary for composing messages related to service guide transmission, and responding whether or not the request is performed is performed. Needed.

Accordingly, the present invention provides an apparatus and method for delivering content information and notification event for service guide generation in a portable broadcasting system.

The present invention provides an apparatus and method for reliably transmitting service guide information in a portable broadcasting system.

The present invention provides an apparatus and method for receiving service guide information in a portable broadcasting system and transmitting a response signal thereto.

The present invention provides an apparatus and method for generating a message required for transmitting service guide information in a portable broadcasting system.

The present invention provides an apparatus and method for determining an information element required for composing messages related to the transmission of a service guide and notification event.

The present invention provides an apparatus and method for transmitting a response to the receipt of a service guide and notification event.

A method according to a preferred embodiment of the present invention comprises: In a method for providing a service guide of the mobile broadcast service in a wireless communication / broadcast system supporting a broadcast (BCAST) service, a service guide application source for providing a service guide in the mobile broadcast system (Service Guide) Application Source (SGAS) to provide information about the service and content in the service guide generation request message to the Service Guide Subscription Source (SGS), and the SGSS receives the service guide generation request message Generating a service guide and provisioning information, and providing a service guide generation response message to the SGAS, wherein the service guide generation request message includes an identifier of an SGAS requesting guide generation of the service and content; SGASProvreqid) and the mobile broadcast of the SGAS Characterized in that: (BSA BCAST Service Application) address information including (BSAAddress) service applications.
System according to a preferred embodiment of the present invention; A system for providing a service guide of the mobile broadcast service in a wireless communication / broadcasting system supporting a broadcast (BCAST) service, wherein the information about a service and content is provided to provide a service guide in the mobile broadcast system. Service Guide Application Source (SGAS) included in the service guide generation request message and provided as a service guide subscription source (SGSS), and service guide and provisioning information when the service guide generation request message is received. And SGSG for providing a service guide generation response message to the SGAS, wherein the service guide generation request message includes an identifier (SGASProvreqid) of the SGAS requesting guide generation of the service and the content and a portable broadcast of the SGAS. BCAST Service Application n: BSA) address information (BSAAddress) is included.
Another method according to a preferred embodiment of the present invention; In a method for providing a notification message of the portable broadcast service in a wireless communication / broadcasting system supporting a broadcast (BCAST) service, a notification event function (NTE) of a BCAST service application (BSA) ) Transmits a notification message generation request message requesting generation of a notification message to a notification generation function (NTG) of a mobile broadcast service subscriber management unit (BCAST Subscription Management (BSM)); Receiving a generation request message, generating a notification message for notification information, and transmitting a result message for the generation result to the NTE to the NTE, wherein the notification message generation request message sends the notification message to a user; Notification type to distinguish whether to provide to the terminal or not And a Priority field of the notification message.
Another system according to a preferred embodiment of the present invention is; In a system for providing a notification message of the portable broadcast service in a wireless communication / broadcasting system supporting a broadcast (BCAST) service, a notification generation unit of a mobile broadcast service subscriber management unit (BCAST Subscription Management: BSM) A notification event function (NTE) of a BCAST Service Application (BSA) for transmitting a notification message generation request message requesting generation of a notification message to a generation function (NTG), and the notification message generation request message; The NTG for generating a notification message for the notification information upon receipt of the NTE and for transmitting a result message for the result of generation to the NTE, wherein the notification message generation request message is to provide the notification message to a user. Notification Type to distinguish whether or not to provide to the terminal And a Priority field of the notification message.

delete

The operation principle of the preferred embodiment of the present invention will be described in detail with reference to the accompanying drawings. In the following description of the present invention, a detailed description of known functions and configurations incorporated herein will be omitted when it may make the subject matter of the present invention rather unclear. The following terms are defined in consideration of the functions of the present invention, and may be changed according to the intentions or customs of the user, the operator, and the like. Therefore, the definition should be based on the contents throughout this specification.

In the following description will be presented a representative embodiment of the present invention for achieving the above technical problem. For convenience of explanation, the names of entities defined in BCAST of 3GPP (3G Generation Partnership Project), asynchronous mobile communication standard, or OMA (Open Mobile Alliance), a standard organization for application of mobile terminal, will be used. These are not intended to limit the scope of the present invention, it is of course possible to apply the present invention to a system having a similar technical background. Hereinafter, in describing the embodiments of the present invention, the OMA BCAST technology, which is one of the portable broadcast technology standards, will be described.

1 illustrates an example of a configuration of a portable broadcasting system to which the present invention transmits a service guide to a mobile terminal. 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 download of a conventional voice / video broadcast service, a music file, or a data file. Service, etc. The content provider 101 uses a service guide content creation source (hereinafter referred to as SGCCS) unit 102 to provide content information, performance information of a mobile terminal, and user profile necessary for constructing a service guide of a BCAST service. The service guide application source (BCAS) of the BCAST Service Application Block (BCA Service Application) (BSA) 104 is provided via the SG1 interface 103 shown in Table 1 above. Transfer to section 105.

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 plays a role of generating standardized metadata required for a mobile broadcast guide. The SGAS unit 105 includes various information required for the configuration of the service guide, including the information received from the SGCCS unit 102, the service guide, the schedule information, the location information, and the like through the interface SG2 106. It is delivered to the Service Guide Generation (hereinafter referred to as SG-G) unit 109 of the BCAST Service Distribution / Adaption 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 service guide generated from the SG-G unit 109 is transmitted to a terminal 119 through the service guide distribution unit (SG Distribution: SG-D) unit 110 and the SG-5 interface 117. Delivered. If the service guide is transmitted through the BDS 122 or the bidirectional network 123 supporting bidirectional communication, or if a matching is required in relation to the system or network, the service guide generated from the SG-G unit 109 is a service guide. The BSC Service Distribution block 121, which is matched in the SG-A unit 111 and delivered to the SG-D unit 110 or described later through the SG-B1 interface 116, will be described later. Is passed).

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 (SGSS) unit 114 of the BCAST subscription management block 113 is a subscription-related, provisioning-related source and purchase information, and promotion-related information related to the generation of a service guide. And the like to the SG-G unit 109 for 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 for transmitting the BCAST service, and may be a broadcast network such as DVB-H, 3GPP MBMS, and 3GPP2 BCMCS. 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 has 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 summarize 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 defined in OMA BCAST to provide a notification message in a portable broadcasting system.

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, the content provider 201 is notified of changes in the service for BCAST to a notification generation function (NTG) 204-1 located inside the BCAST Subscription Management 204. Notify me.

The BCAST service distribution / adaptation unit (hereinafter referred to as BSD / A) 203 serves to set up a bearer to transmit BCAST service data supplied from the BCAST service application 202, to determine a transmission schedule of the BCAST service, and to carry a portable broadcast. It is responsible for generating a, and is connected to a broadcast distribution system (BDS) 206 capable of providing a broadcast service and an interworking network 207 supporting bidirectional communication. In addition, the BCAST service distribution / adaptation unit (hereinafter referred to as BSD / A) 203 has a notification distribution / adaptation function (NTDA) 203-1, so that the BCAST subscription management unit (BCAST Subscription Management) 204 receives a notification message and transmits the notification message to one or more users through the BDS 206 or the interworking 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, and receives information on the notification event from the content provider 201 and the BDS 206 to generate a notification message or to generate a notification message for the BCAST service itself event.

The BDS Service Distribution 105 distributes all 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 1: 1 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. In this specification, it is assumed that a terminal capable of connecting with a cellular network, that is, a cellular phone. The terminal 208 receives a notification message transmitted through the NT5 interface 225 by a notification client function (NTC) 208-1, and performs an appropriate operation, or the NT6 interface 226. Receives a notification message sent through the SMS and performs an appropriate operation.

Next, interfaces between the logical entities will be described.

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

The NT3 interface 222 is an interface from the notification event unit 202-1 located in the BCAST service application 202 to the notification generation unit 204-1 of the BCAST subscription management unit 204, and the notification generation unit 204-1. In order to generate a notification message, information about the notification of the event or generation of the notification message is carried.

The NT4 interface 223 is a notification distribution / adaptation unit (notification Distribution / Adaptation Function) 203-1 of the BCAST service distribution / adaptation unit 203 in the notification generation unit 204-1 located in the BCAST subscription management unit 204. Is an interface to the notification distribution / adaptive unit 203-1 in order to transmit the notification message generated by the notification generation unit 204-1 to the BDS 206 or the interworking network 207, or BDS ( When an event occurs at 206, the notification distribution / adapter 203-1 is used to transmit the event.

The NT5 interface 225 is used when a notification message transmitted from the notification distribution / adaptation unit 203-1 of the BCAST service distribution / adaptation unit 203 is directly transmitted to the terminal through a broadcast channel via the BDS 206. As an interface, it is used to send a notification message to one terminal or multiple terminals.

The NT6 interface 226 is a dedicated channel or interworking network 207 with a terminal through which the notification message transmitted from the notification distribution / adapting unit 203-1 of the BCAST service distribution / adapting unit 203 passes through the interworking network 207. This is an interface used when transmitted directly to a terminal through a broadcast channel provided by. The terminal is 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 delivers information necessary for generating a notification message to the notification generation unit 204-1, and when the notification event unit needs to know that an event requiring notification has occurred, the notification generation unit notifies the information about the event. Forward to (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 about the content and an attribute value to the SGAS unit 302 in relation to the BCAST service. In step 312, the SGAS unit 302 delivers the information and the property value of the content and service to the SG-G / D / A 304 in accordance with the BCAST format as the attribute value received from the SGCCS (301). In step 313, the SG-G / D / A 304 requests the SGSS 303 for information related to provisioning. In step 314, SGSS 303 provides supply related information to SG-G / D / A 304. In step 315, the SG-G / D / A 304 generates a service guide 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 202 of FIG. 2, and reference numeral 402 denotes a notification generation functional unit (NTG) 204 of the BCAST subscription management block 204. -1), 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 sends an event notice to the NTG 402 in the BCAST subscription management block 204, NT-3, as in step 411. Pass through interface 222. If the notification event originated from BCAST service distribution / adaptation block 203 or BDS 205, then it passes through NT-4 interface 223 from NTDA 403 to NTG 402 as shown in step 412. As in step 413, the notification event may be generated in the BSM 204 itself and forwarded to the NTG 402.

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

Before describing specific embodiments of the present invention, a 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 parent element value for the whole message, E2 is the child element value of E1, E3 is the child element value of E2, E4 is the value of E3 Represents a child 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 value or attribute value is mandatory. The value "M" is required and the value "O" 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 that 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 required 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 should not necessarily include all of the above information elements. Of course, some or all information elements may be used depending on the intention or need.

6 shows a protocol stack used for transmitting a notification event in an NT-3 interface. Messages delivered via NT-3 can be delivered in text or XML format. The message will be described in detail with reference to FIG. 7. Messages over NT-3 are sent using the Internet Protocol (IP), Transfer Control Protocol (TCP), and Hyper Text Transfer Protocol (HTTP), and the NTE in the BSA is a notification event via HTTP POST to the NTG of the BSM. Send a message to request the creation of a notification message. In addition, NTG can send the result of notification message generation in HTTP RESPONSE message after receiving message from NTE, or send result message through HTTP POST.

7 is a flowchart for transmitting a message via NT-3.

In step 703, the NTE 701 requests the NTG 702 to generate a notification message. The messages provided in step 703 are as shown in Tables 7a to 7d. Then, in step 704, the NTG 702 generates a notification message with the information received from the NTE 701, and then sends a message about the generation completion to the NTE 701. If a notification message is generated and sent immediately, an HTTP response (response_) may be included in the response message in step 703 and a NTE (701) may be required if it takes time to generate a notification message. At the end of creation after the session between the NTG 702 and the NTG 702, the NTG 702 may notify the NTE 701 of the result message using the HTTP POST through the NTGReqId and the BSAAddress of the NTGReq received in step 703. Details of the result message can be shown in <Table 8>.

In step 704, the response to the NTE request may send a response to multiple requests of the NTG in a single message from the NTG to the NTE.

FIG. 5 illustrates a data model of a service guide for generating a service guide in OMA BCAST.

The service guide data model includes an administrative group 500 that provides the upper configuration information of the entire service guide, a core group 520, which is a core part of the service guide, such as services, contents, and schedules. An access group 530 provides access information for accessing a service or content, and a provisioning group 510 including subscription and purchase information. Looking at each component, the service guide context (501) provides a way for the terminal to recognize the service guide, the operator (Operator) for distributing the service guide or location information and associated service guide transmission descriptor ( ServiceGuideDeliveryDescriptor) 502 provides connection information.

The service guide transmission descriptor 502 informs delivery session information in which a ServiceGuide Delivery Unit (SGDU) containing a fragment, which is a minimum unit constituting a service guide, is located, and grouping information and notification of the SGDU Inform the entry point to receive the message.

The service group 521 is a superset of contents included in the broadcast service as a center of the entire service guide and includes information such as service content, genre, and service area. The schedule group 522 represents time information of each content included in a service, such as streaming and downloading. The content group 523 includes a detailed description of broadcast content, a target user group, a service area, a genre, and the like. The access group 530 provides information related to the connection so that the service can be viewed, and provides a delivery method, session information, etc. for the access session. The session descriptor group 532 may include an access group 531, and inform the location information in the form of a URI so that the terminal can check the corresponding session description information and for the multimedia content existing in the session. It provides address information, codec information, and so on. PurchaseItem 511 provides a bundle of services, content, time, etc. to help a user subscribe or purchase a corresponding PurchaseItem. Purchase Data 512 includes detailed information on purchase and subscription, such as price information and promotion information about a service or a service bundle.

Purchase Channel 513 informs access information for subscription or purchase. The service guide content (ServiceGuideContext) 501 allows the terminal to recognize the service guide and informs the location information or owner information from which the service guide can be received. The service guide transmission descriptor (ServiceGuideDeliveryDescriptor) 502 informs grouping information about an SGDU, which is a container of an entry point and a fragment for receiving a service guide.

The service guide of FIG. 5 is generated in the above-described SG-G 109 of FIG. 1 and the provisioning 510 information of FIG. 5 is provided by the SGSS 114 of FIG. The supply information is transmitted in step 314 of FIG. 3 described above, and step 314 is delivered without the query of step 313. However, step 313 is not necessary information to obtain information for supply, so SGSS 114 must know the service and contents or schedule information in advance, but the system cannot support it. Accordingly, an interface of the SG-3 802 for exchanging information between the SGAS 801 and the SGSS 803 of FIG. 8 is required. As shown in FIG. 9, the service and contents from the SGAS 901 to the SGSS 902 as shown in FIG. The schedule information should be provided through step 903.

FIG. 10 is a diagram illustrating a protocol stack used for transmitting information related to a service guide in an SG-3 interface.

The message delivered through SG-3 802 may be delivered in text or XML form. The message will be described in detail with reference to FIG. 11.

The message through the SG-3 802 is transmitted using IP, TCP, and HTTP, and the SGAS in the BSA transmits a service and content related message through an HTTP POST to the SGSS in the BSM. In addition, the SGSS may receive a message from the SGAS and transmit a result of generating provisioning information in an HTTP RESPONSE message, or send a result message through an HTTP POST.

11 is a flowchart for transmitting a message via SG-3. Hereinafter, a process of transmitting a message through SG-3 will be described with reference to FIG. 11.

In step 1101, the SGAS 901 provides the SGSS 902 with information about the service and the content and the schedule information in the Service Guide Data Model described above with reference to FIG. 5. do. Information about a schedule may not be provided among the delivered information, and the schedule may be generated and provided in BSD / A while generating a service guide in the SG-G 803. The message provided in step 1101 is as shown in Table 9 below. In <Table 9>, the service schedules the service information (ServiceInfo) of <Table 10a> to <Table 10d>, and the content schedules the content information (ContentInfo) of <Table 11a> to <Table 11d>. ) Receives (inherited) the contents of the schedule information (ScheduleInfo) of Tables 12a to 12h, respectively. In step 1102, the SGSS 901 generates provisioning information of a service guide using the information received from the SGAS 902, and then sends a message about completion of creation to the SGAS 901. If the service guide is generated and sent immediately, the result message may be included in the HTTP response for the request message in step 1101. If it takes time to generate provisioning information of the service guide, SGAS 901 After completing the session between the SGSS 902 and the creation completion point, the SGSS 902 may notify the SGAS 901 of the result message through the HTTP POST using the SGASProvReqId and the BSAAddress. Details of the result message are shown in Table 13 below. In step 1102, the response to the SGAS request may send responses to several requests of the SGAS in one message from SGSS to SGAS.

12 is a diagram illustrating a request message delivery for providing a service guide source or providing a notification event to a backend interface of SG-3 or NT-3 according to the present invention.

In order to transmit a message between the SG-3 and the NT-3, such as the reference numeral 1201, the message may be directly transmitted to the HTTP using the HTTP as shown in FIG. 6 or 10 described above. Alternatively, the Web Service Protocol for the transport of XML data, such as Simple Object Access Protocol (SOAP), eXtensible Markup Language-Remote Procedure Call (XML-RPC), and Blocks Extensible Exchange Protocol (BEEP). You can send that request message using.

12 illustrates a hierarchical structure configured between SG-3 or NT-3. The communication between the SG-3 or NT-3 should have the same hierarchical structure. Therefore, the same reference numerals are used for the same hierarchical structure in FIG. 12. That is, the IP layer is shown at 1203, the TCP layer is shown at 1205, and the HTTP layer is shown at 1207. Finally, reference numeral 1209 illustrates the Web Service Protocol.

13 is a signal flow diagram for service guide source delivery through SG-3 between SGAS and SGSS in accordance with the present invention.

First, in step 1311, the SGAS 1301 transmits information about a service guide source to the SGSS 1302 as shown in Table 14 below. When the SGSS 1302 receives the information on the service guide source, the SGSS 1302 processes the information related to the service guide source, and generates a response signal as a response signal in step 1312 and transmits the result to the SGAS 1301. In this case, the message on the processing result may be exemplified as shown in Table 15 below.

14 is a signal flow diagram for notification event delivery over NT-3 between NTE and NTG in accordance with the present invention. Hereinafter, a process of signal flow in transmitting a notification event between an NTE 1401 and an NTG 1402 will be described in detail with reference to FIG. 14.

The NTE 1401 generates a notification event message and transmits the notification event message to the NTG 1402 in step 1411. The notification event message may be shown in Table 16 below. When the NTG 1402 receives the notification event message, the NTG 1402 processes the received notification event, generates a processed result as a response signal, and transmits the result to the NTE 1402 in step 1412. In this case, the processing result message for the notification event may be shown in Table 17 below.

The code used to indicate the result value in the response message may be shown in Tables 18a to 18c below.

Global Status codes shown in Tables 18a to 18c are included as values in the response of the response message. That is, if the request is well processed, the response value is 000, and the mobile terminal may know that the request was successful from the corresponding code value. Therefore, Tables 18a to 18c should be stored in the system and may be stored in the terminal. That is, it should be stored and used in common to the system and the terminal. In addition, additional codes may be defined according to the purpose of the operator. The Global Status Code shown in Tables 18a to 18c indicates a status code when the system or terminal providing the portable broadcasting service should respond to the result of the processing in addition to the response message related to the present invention. It can be used to inform the result through code values such as) or response. In this case, the response corresponds to the response field in the above table. For example, it can be interpreted as a response field among the fields of <Table 13>. Therefore, the response field of Table 13 may be used as an equivalent to a status code.

As described above, in order to generate a notification message in the portable broadcasting system, a notification event message is required from the NTE of the BSA, and a transmission method for the corresponding message has been presented. In addition, for the transmitted message, the NSA of the BSA needs to know the result of generating the message, and the NTG of the BSM suggests a method for generating and sending a response message for a plurality of BSAs or a plurality of event messages. Through this, in case of service guide, SGSSM of BSM should provide supply related information to SG-G of BSD / A in order to create service guide, and can provide a way to receive information about service and contents in advance. .

Claims (28)

In the method for providing a service guide of the portable broadcast service in a wireless communication / broadcasting system supporting a broadcast (BCAST) service, In order to provide a service guide in the mobile broadcasting system, a service guide application source (SGAS) includes information about a service and content in a service guide generation request message and includes a service guide subscription source (SGSG). ), The SGSS may include generating a service guide and provisioning information upon receiving the service guide generation request message and providing a service guide generation response message to the SGAS. The service guide generation request message includes an identifier (SGASProvreqid) of the SGAS requesting the guide generation of the service and the content, and a BAST (BCAST Service Application) address information (BSAAddress) of the SGAS. How to provide a service guide. delete The method of claim 1, The SGAS further includes scheduling information in the service guide generation request message and provides the service guide to the SGSS. The method of claim 1, The supply information includes a purchase item (PurchaseItem), data purchase (PurchaseData), and channel purchase (PurchaseChannel) information. The method of claim 1, Upon receipt of the service guide generation request message, when SGSS completes the generation of the service guide and supply information, the service guide generation response message includes an HTTP response message including a unique identifier that distinguishes the service guide generation request message. Service guide providing method characterized in that. The method of claim 1, Upon receipt of the service guide generation request message, if the SGSS does not complete generation of the service guide and supply information, the service guide generation response message is a unique identifier that distinguishes the service guide generation request message at the time of completion of creation. Service guide providing method characterized in that the HTTP POST message including. The method of claim 1, The SGSS is a service guide providing method characterized in that the notification of the requested result through a service guide response message when receiving two or more service guide generation request message from the SGAS. In the system for providing a service guide of the mobile broadcast service in a wireless communication / broadcasting system supporting a broadcast (BCAST) service, A service guide application source (SGAS) for providing a service guide subscription source (SGSS) by including information about a service and content in a service guide generation request message to provide a service guide in the mobile broadcasting system; Receiving the service guide generation request message, the service guide and provisioning information, and the SGSS for providing a service guide generation response message to the SGAS; The service guide generation request message includes an identifier (SGASProvreqid) of the SGAS requesting the guide generation of the service and the content, and a BAST (BCAST Service Application) address information (BSAAddress) of the SGAS. Service guide delivery system. delete 9. The method of claim 8, The SGAS further includes scheduling information in the service guide generation request message and provides the SGAS to the SGSS. 9. The method of claim 8, The supply information includes an item purchase (PurchaseItem), data purchase (PurchaseData), and channel purchase (PurchaseChannel) information. 9. The method of claim 8, Upon receipt of the service guide generation request message, when SGSS completes the generation of the service guide and supply information, the service guide generation response message includes an HTTP response message including a unique identifier that distinguishes the service guide generation request message. Service guide providing system, characterized in that. 9. The method of claim 8, Upon receipt of the service guide generation request message, if the SGSS does not complete generation of the service guide and supply information, the service guide generation response message is a unique identifier that distinguishes the service guide generation request message at the time of completion of creation. Service guide providing system, characterized in that the HTTP POST message, including. 9. The method of claim 8, The SGSS, when receiving two or more service guide generation request messages from the SGAS, the service guide providing system, characterized in that notified of the result required by one service guide response message. A method of providing a notification message of the portable broadcast service in a wireless communication / broadcasting system supporting a broadcast (BCAST) service, The Notification Event Function (NTE) of the BCAST Service Application (BSA) generates a notification message to the Notification Generation Function (NTG) of the BCAST Subscription Management (BSM). Generating a notification message requesting a request message; When the NTG receives the notification message generation request message, the NTG generates a notification message for notification information, and transmits a result message for the generation result to the NTE to the NTE. The notification message generation request message includes a notification type field for distinguishing whether to provide the notification message to a user or a terminal, and a priority field of the notification message. How to provide a message. 16. The method of claim 15, The notification message generation request message includes an identifier (NTEid) of the NTE and an address (BSAAddress) of the BSA. delete 16. The method of claim 15, The notification message generation request message further includes a validity field indicating a valid time information of the notification message. 16. The method of claim 15, The notification information is a method for providing a notification message, characterized in that the modification of the service provided to the subscriber, the impending revision, or an event according to the emergency situation. 16. The method of claim 15, And the NTG generates and sends the result message immediately upon receipt of the notification message generation request message from the NTE. 17. The method of claim 16, The NTG, upon receiving the notification message generation request message from the NTE, terminates the session between the NTE and the NTG, and generates and transmits the result message. In a system for providing a notification message of the portable broadcast service in a wireless communication / broadcast system supporting a broadcast (BCAST) service, Of a BCAST Service Application (BSA) that transmits a notification message generation request message requesting generation of a notification message to a notification generation function (NTG) of a BAST subscription service. Notification Event Function (NTE), Generating the notification message for the notification information upon reception of the notification message generation request message, and transmitting the result message for the generation result to the NTE to the NTE; The notification message generation request message includes a notification type field for distinguishing whether to provide the notification message to a user or a terminal, and a priority field of the notification message. Message Delivery System. 23. The method of claim 22, The notification message generation request message includes an identifier (NTEid) of the NTE and an address (BSAAddress) of the BSA. delete 23. The method of claim 22, The notification message generation request message further includes a validity field indicating a valid time information of the notification message. 23. The method of claim 22, The notification information is a notification message providing system, characterized in that an event according to the modification, impending modification or emergency situation of the service provided to the subscriber. 23. The method of claim 22, And the NTG generates and sends the result message immediately upon receipt of the notification message generation request message from the NTE. 23. The method of claim 22, The NTG, upon receiving the notification message generation request message from the NTE, terminates the session between the NTE and the NTG, and generates and transmits the result message.

Images