KR20070108310A - Method and system for transmission of notification message in a mobile broadcast system - Google Patents

Abstract

A method for transmitting a notification message in a portable broadcasting system and a system according to the same are provided to support a bidirectional channel. If a notification event is received, a notification generation function(203) writes a notification message corresponding to the notification event. The notification generation function(203) determines a path of the notification message. When the path of the notification message is a bidirectional channel, the notification generation function(203) transmits a transmission request message including a target address of a corresponding terminal(119) to an NDAF(Notification Distribution/Adaptation Function)(202). The NDAF(202) receives the transmission request message, confirms the transmission path and the target address, and transmits the notification message to the terminal(119) through the corresponding target address.

Description

Method of transmitting notification message in portable broadcasting system and system according thereto {METHOD AND SYSTEM FOR TRANSMISSION OF NOTIFICATION MESSAGE IN A MOBILE BROADCAST SYSTEM}

1 is a view showing a component for transmitting a service guide to a mobile terminal in a portable broadcasting system according to a first embodiment of the present invention

2 is a diagram showing a notification structure in the portable broadcasting system according to the first embodiment of the present invention.

3 is a diagram showing a structure for service provision in a portable broadcasting system according to a first embodiment of the present invention;

4 is a block diagram showing a structure for transmitting a notification message in a portable broadcasting system according to a first embodiment of the present invention.

5A to 5D are diagrams showing an example of a service guide configuration for a service including a notification;

6 is a signal flow diagram illustrating a case where a notification message is subscribed through a bidirectional network in a portable broadcasting system according to a first embodiment of the present invention.

7 is a diagram illustrating a generation and request process of a notification message event in a portable broadcasting system according to a first embodiment of the present invention.

8 is a flowchart illustrating a process of receiving and transmitting a request for transmission of a notification message in NTDA to a terminal;

9A is a diagram illustrating in detail an example of an access fragment in a portable broadcasting system according to a first embodiment of the present invention.

9B is a diagram showing a connection form in an access fragment in the portable broadcasting system according to the first embodiment of the present invention.

10 is a diagram illustrating an example screen of a user terminal through a service guide receiving method in a portable broadcasting system according to a first embodiment of the present invention.

11 is a diagram illustrating an electronic service guide (ESG) transmission structure of a CBMS in a mobile broadcasting system according to a second embodiment of the present invention.

12 illustrates a structure of network entities for transmitting a notification message in a CBMS in a portable broadcasting system according to a second embodiment of the present invention.

13 is a diagram related to service purchase of a CBMS in a portable broadcasting system according to a second embodiment of the present invention.

14 is a diagram illustrating signaling between network entities in a mobile broadcasting system according to a second embodiment of the present invention.

15A to 15D are diagrams illustrating a CBMS-based ESG data model fragment in a portable broadcasting system according to a second embodiment of the present invention.

16 is a diagram illustrating a CBMS ESG data model in a portable broadcasting system according to a second embodiment of the present invention.

The present invention relates to a method and a system for transmitting a notification message in a portable broadcasting system, and more particularly, to a method and system for transmitting a notification message in a portable broadcasting system providing a bidirectional network.

The mobile communication market is continuously demanding the production of new services through recombination or integration of existing technologies. Today, due to the development of communication and broadcasting technologies, mobile terminals such as mobile phones and PDAs in conventional broadcasting systems or mobile communication systems are , A "mobile terminal"). IT is strengthening the mobile communication business by accommodating such potential and actual market demands, rapidly increasing user demands for multimedia services, strategies of operators to provide new services such as broadcasting services in addition to existing voice services, and demands of consumers. With the interests of companies interlocked, the convergence of mobile communication service and IP is becoming a big flow of development of next generation mobile communication technology.

Meanwhile, the Open Mobile Alliance (OMA) is an organization that researches standards for interoperability of individual mobile solutions. The OMA mainly plays a role in setting various application standards for mobile communication games and Internet services. In particular, OMA BAC BCAST (Open Mobile Alliance Browser and Content Mobile Broadcast Sub Working Group) of the working group of the OMA is studying a technology for providing a broadcast service using a mobile terminal. Hereinafter, a brief description will be given of the portable broadcasting system discussed in the OMA.

The portable broadcasting system includes a discovery of a service by a terminal capable of receiving a portable broadcast, a subscription of a service by the terminal, provision of various control information for receiving the service, transmission of the service, and Receive process. In the portable broadcast system, when the mobile broadcast is performed, the terminal receives a notification message including various control information about the broadcast service.

In such a system, changes may occur in the broadcast system due to various factors during which the terminal receives a broadcast, and some of the changes may be information that must be known in the terminal. An example of the information may be a change in a portable broadcast service time, a change in information for receiving a portable broadcast service, and the like.

A method of transmitting a notification message in such a portable broadcasting system is already defined. However, in a portable broadcasting system providing a bidirectional network, a method of transmitting a notification message is not defined. Therefore, a procedure and method for the notification message are required.

Accordingly, an object of the present invention is to provide a method and system for transmitting a notification message in a portable broadcasting system.

Another object of the present invention is to provide a method and system for transmitting a notification message in a portable broadcasting system supporting a bidirectional channel.

According to an aspect of the present invention, there is provided a notification message transmission method in a portable broadcasting system supporting a bidirectional channel, comprising: generating a notification message corresponding to a notification event when a notification generator receives a notification event by a predetermined method; Determining, by the notification generating unit, a path of the notification message, and when the path of the notification message is a bidirectional channel, transmitting a transmission request message including a target address of a corresponding terminal to a notification distribution / adaptive unit, and The notification distribution / adapter receiving the transmission request message checks the transmission path and the target address, and then transmits the notification message to the terminal through the corresponding target address. In addition, the method includes a method for recognizing a notification message as a service or an auxiliary means related to a service from a received service guide, and a method and a process for transmitting a subscription or termination message for subscribing or terminating a notification message for each service. .

DETAILED DESCRIPTION Hereinafter, detailed descriptions of preferred embodiments of the present invention will be described with reference to the accompanying drawings. It should be noted that the same components in the figures represent the same numerals wherever possible. Specific details are set forth in the following description, which is provided to aid a more general understanding of the invention. In the following description of the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted.

The present invention proposes a method and system for transmitting a notification message in a portable broadcasting system supporting a bidirectional network. This will be described with reference to embodiments of the present invention for the purpose of understanding the portable broadcasting system according to the embodiment of the present invention. In the first embodiment, a broadcasting system defined by the 3rd Generation Partnership Project (3GPP), which is an asynchronous mobile communication standard, or the Open Mobile Alliance (OMA), which is a standard organization of terminal applications, is used. In the second embodiment, a digital video broadcasting (Convergence of Broadcasting and Mobile Service: DVB-CBMS) system, which is another portable broadcasting standard organization, will be described. In the following embodiments of the present invention described below, the architecture and terms used in the OMA will be described first, and the embodiments will be described by mapping the architecture and terms used in the CBMS.

Next, the portable broadcasting system according to the first embodiment will be described to assist in understanding the notification message. In the first embodiment, the names of entities defined in BCAST of the Open Mobile Alliance (OMA) will be used the same, but these standards and names do not limit the scope of the present invention and are applied to a system having a similar technical background. Of course it is possible.

First, a mobile terminal for receiving a broadcast service in a mobile broadcasting system must receive service guide (SG) information including description information about the service itself, billing information about the service, and information on how to receive the service. The mobile terminal receives the corresponding service using the service guide information.

Hereinafter, a description will be given based on the OMA BCAST technology, which is one of the portable broadcast technology standards, to give a concrete example in the description of the present invention, but this description does not limit the content of the present invention.

1 is a diagram illustrating a component for transmitting a service guide to a mobile terminal in a portable broadcasting system according to a first embodiment of the present invention. Prior to the description of FIG. 1, interfaces used between components are shown in Table 1 below.

Referring to FIG. 1, a content provider 101 is a provider of a broadcast service (hereinafter, referred to as a BCAST service), and the BCAST service is a conventional voice / video broadcast service, a file download service of a music file, a data file, or the like. This can be The content provider 101 uses 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 required for constructing a service guide of a BCAST service. The service guide application source (hereinafter referred to as SGAS) of the BCAST Service Application (BSA) 104 is provided through the SG1 interface 103 of Table 1 above. To pass).

The BCAST service application 104 receives the data of the BCAST service from the content provider 101 and processes the data into a form suitable for the BCAST network to create BCAST service data. In addition, the BCAST service application 104 is responsible for generating standardized metadata required for portable broadcast guidance. The SGAS unit 105 will be described later through the interface SG2 106 various sources necessary for the configuration of the service guide, including the information received from the SGCCS unit 102, such as service and content detailed information, schedule information, location information, etc. The service guide generation (hereinafter referred to as SG-G) of the BCAST service distribution / adaptation unit 108 is transmitted to the unit 109.

The BCAST service distribution / adaptation unit 108 sets a bearer for transmitting BCAST service data supplied from the BCAST service application 104, determines a transmission schedule of the BCAST service, and portable broadcast guide information. It is responsible for generating the. The BCAST service distribution / adapter 108 is connected to a broadcast distribution system (BDS), which is a network for transmitting BCAST service data, and a bidirectional network 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.

In FIG. 1, the BCAST Subscription Management (BSM) block 113 manages subscription information and service provision information for receiving the BCAST service and device information for the mobile terminal receiving the BCAST service. The service guide subscription source (SGSS) unit 114 of the BCAST subscription management block 113 may include a subscription related to provision of a service guide, a provisioning related source and purchase information, and a promotion related information. The source is delivered to the SG-G unit 109 which generates a service guide via the SG4 interface 112.

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 the capability of the terminal. 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 2 to 4 summarize the functions of the main components of FIG. 1 in the standard of the OMA BCAST service.

2 is a diagram showing a notification structure in the portable broadcasting system according to the first embodiment of the present invention.

The content provider 101 is a provider of a broadcast service, and the broadcast service may be a conventional voice / video broadcast service, a file (music file or data file) download service, or the like. When a problem or change occurs in the supply of the BCAST service, the content provider 101 transmits the change to a notification event function (NTE) 201 located inside the BCAST service application 104. Notify.

The BCAST service application 104 receives the data of the BCAST service from the content provider 101, processes it into a form suitable for the BCAST network, and serves to create BCAST service data, and generates standardized metadata for portable broadcast guidance. It plays a role. In addition, the content provider 101 is notified of changes in the service for BCAST and notified to a notification generation function 203 located in the BCAST subscription management unit (BSM) 113.

The BCAST service distribution / adaptation unit 108 is responsible for establishing a bearer for transmitting BCAST service data supplied from the BCAST service application 104, determining a transmission schedule of the BCAST service, and generating a portable broadcast guide. It is connected to a broadcast distribution system (BDS) 131 capable of providing a broadcast service and an interworking network (IN) 133 supporting bidirectional communication. In addition, the BCAST service distribution / adaptation unit 108 has a notification distribution / adaptation function (NTDA) 202, receives a notification message from the BCAST subscription management unit (BSM) 113, and receives a BDS. Or it transmits to individual users or multiple users through interworking network.

The BCAST subscription management unit (BSM) 113 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 203. In order to receive a notification event generated from various network entities for providing a mobile broadcasting service, a notification message is generated or a notification message for a BCAST service itself event is generated.

The terminal 119 is a terminal capable of receiving BCAST service and has a function of being connected to a cellular network according to the capability of the terminal. The terminal 119 receives a notification message transmitted through the NT5 interface 214 by a notification client function (NTC) 204 to perform an appropriate operation, or is transmitted through the NT6 interface 215. Receive a notification message and take appropriate action.

Next, interfaces between the logical entities will be described.

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

The NT-3 interface 212 is an interface from the notification event unit 201 located in the BCAST service application 104 to the notification generation unit 203 of the BCAST subscription management unit 113, and the notification message from the notification generation unit 203. Carries the information necessary for the generation of a notification or a notification message for the event so that it can be generated.

The NT-4 interface 213 is an interface from the notification generation unit 203 located in the BCAST subscription management unit 113 to the notification distribution / adaptive unit (NTDA) 202 of the BCAST service distribution / adaptive unit 108, and the notification. The notification message generated by the generation unit 203 is transmitted to the notification distribution / adaptive unit (NTDA) 202 to be transmitted to the BDS or the interworking network, or the BCAST service distribution / adaptive unit 108 or the BDS (Broadcast Distribution System). When an event occurs in the BDS) 131 or the like, the notification distribution / adapter 202 transmits the event.

The NT-5 interface 214 is an interface used when a notification message transmitted from the notification distribution / adaptation unit 202 of the BCAST service distribution / adaptation unit 103 is directly transmitted to a terminal through a broadcast channel through a BDS. It is used to send a notification message to multiple terminals.

The NT-6 interface 215 is an interface used when a notification message transmitted from the notification distribution / adaptive unit 202 of the BCAST service distribution / adaptive unit 103 is directly transmitted to the terminal via a bidirectional network. Used to send a message.

The NT-B1 interface 216 is used by the BCAST service distribution / adapter 108 to set up a transmission path that the BCAST service distribution / adapter 108 will use in the BDS or to receive the event information generated in the BDS. And the interface between the BDS Service Distribution.

The notification event unit 201 delivers the information necessary to generate the notification message to the notification generation unit 203, and when the notification event unit 201 knows that an event that requires notification has occurred, the notification event unit 201 sends information about the event to the notification generation unit 203. To pass. The notification generating unit 203 receives the information and events necessary for generating the notification message from the notification event unit 201 and generates a notification message, or generates a notification event of the BDS or the interworking network through the notification distribution / adaptive unit 202. If received, it generates a notification message and transmits it to the notification distribution / adaptation unit 202. When the notification message is generated, when it is necessary to notify the start of the service again, the content provider 101 is notified that there is a change in the information of the service and when it is necessary to transmit a new portable broadcast guide and BDS 131 or the case in which a special event occurs in the interworking network 133.

The notification distribution / adaptation unit 202 transmits a notification message through the NT-5 214 or the NT-6 215, and changes the information of the specific mobile broadcasting service from the BDS, for example, wirelessly. When receiving the adjustment of the transmission rate or the service unavailable due to the network environment, the notification event is transmitted to the notification generating unit 203 through the NT-4213.

3 is a diagram illustrating a structure of service provisioning in the portable broadcasting system according to the first embodiment of the present invention. The service provisioning is in charge of user subscription to BCAST service and purchase of a subscribed service. It also provides additional information about payments and purchases, such as status information for user accounts.

Referring to FIG. 3, the broadcast service provisioning management (BSP-M) 301 function provides subscription and purchase information. Based on the user subscription information, the BSP-M 301 provides the charging information of the user to the related entity and supports the charging for the portable broadcasting service. The BSP-M 301 also requests for subscription and billing from the Broadcast Service Provisioing Client (BSP-C) 302 through the interface of the SP-7 311 and the SP-8 312. And reports. The BSP-C 302 plays a role of reporting on subscription and purchase of a mobile broadcast service. The BSP-C 302 may extract provisioning information from a service guide to request subscription and purchase, or request additional information. The description of the SP-7 (311) and SP-8 (312) is shown in Table 5 below.

Next, the message schema table used in the present invention will be described. Referring to Table 6 below, the name represents the name of the element value and the attribute value constituting the message. The type indicates whether the name is an element value or an attribute value. The element value has the same values as E1, E2, E3, and E4. E1 means the upper element value of the whole message. E2 means the lower element of E1. The value E3 represents the lower element value of E2 and E4 represents the lower element value of E3. Attribute values are denoted by A, where A represents the attribute value of the element. For example, A below E1 indicates an attribute value of E1. The category is used to distinguish whether the element or attribute value is mandatory or not, and if it is required, it has a value of M and an option of O. Cardinality represents the relationship between elements and has values of 0, 0..1, 1, 0..n, and 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 be absent 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.

FIG. 4 is a block diagram illustrating a structure for transmitting a notification message in a portable broadcasting system according to a first embodiment of the present invention, and illustrates the entire process for receiving a notification message. In the description of this drawing, only the necessary elements of the contents described with reference to FIGS. 1 to 3 are included for convenience of description, and only a notification message transmission will be described.

Referring to FIG. 4, in step 401, the SG-G 109 generates a service guide including time, purchase, and access information related to a service and content, and then requests the service guide transmission from the SG-D 110. Thereafter, the SG-D 110 transmits the service guide to the terminal 119 in step 402. A broadcast system or a two-way network may be used for service guide transmission. When transmitted through a broadcast system, the terminal 119 receives a service guide from a session in which the service guide is transmitted. Access the service guide. The SG-C 120 of the terminal 119 is responsible for receiving a service guide from the 110 SG-D 110, and the user confirms information about the service and the content therefrom. The user decides to subscribe and purchase a service, schedule, content, etc. through the service guide, and then proceeds with a request for service provisioning such as subscription and purchase through the BSP-C 302. Upon receipt of the notification message relating to the service, the BSP-C 302 requests subscription or termination of the BSP-M 301 in step 403. The BSP-M 301 receives a request for user information (UserID), device ID (DeviceID), service and notification subscription information, and stores corresponding user information in the DB 411 in the BSM 113. do. A notification event may occur at various network entities for providing a portable broadcast service. In the figure, a notification event may occur in the CC 101, the BSA 104, the BSD / A 108, and the BSM 113. In the steps 404 to 406, the CC 101, the BSA 104, BSD / A 108 requests NTG 203 to generate a notification message. NTG 203 creates a notification message for the received event. After generating the notification message, the NTG 203 checks the target address (TargetAddress) for transmitting the notification message from the DB 411 and generates a request message for message delivery. If there is a user who subscribes to a message through a two-way network in connection with the service, a request message is created including address information that the user can receive.

The NTG 203 requests the NTDA 202 to deliver a notification message in step 407. NTDA 202 forwards the notification message to NTC 204 in step 408. At this time, the message is transmitted to the broadcasting system or the bidirectional network according to the target address.

The notification message can be largely divided into a notification service and a notification message as an auxiliary means related to the service. After receiving the service guide, a method of recognizing a notification service or a service-related notification message by a terminal or a user is as follows. In the case of the notification service, if the service type in the service fragment of the service guide has a notification value, the service is recognized as a notification service. When a notification message is transmitted to a corresponding service in connection with a service, when a notification fragment (Access Fragment) related to the service includes a notification reception (904) element value, among the access fragments related to the service And if there is a URI value indicating that the value of the element of the service class 903 is sdo.oma.nt or similarly, and a service fragment or a purchaseitem fragment When there is an element value or attribute value of a corresponding fragment that indicates that a notification message such as NTviaInteraction can be received, it can be recognized that a notification message can be received in relation to the corresponding service.

5A to 5D are detailed exemplary embodiments of the service guide including a notification value in the service guide according to the first embodiment of the present invention. In addition, since the connection fragments in FIGS. 5A to 5B are shown in FIGS. 9 and 9B, the following description will be made with reference.

In the case of FIG. 5A, a notification message associated with a corresponding service in a form of containing notification reception information in an access fragment 901 may include a notification reception 904 element value. The access information of the notification transmitted to the broadcast channel is included, and the access type 902 contains information related to the service.

In the case of FIG. 5B, an access to a service and a notification message is differently included. The purpose of which the information of the corresponding access is classified depends on the value of the service class 903. As an example of a file delivery service, an access type of access in which a service class 903 is sdo.oma.fd includes access information for downloading a file, and a service class 903. An access type 902 of access having sdo.oma.nt contains access information for receiving a notification.

In the case of FIG. 5C, as a configuration example of a service configured to only receive a notification message in which a service type of a service fragment is a notification service, the service fragment may subscribe / purchase a service of a specific schedule. This is a configuration example in which the service includes notification. As such, the service type (ServiceType) is the notification service (NotificaitonService), or the access (Notification) includes a notification reception (NotificationReception) (904), or the service class (Access) of the access (ServiceClass) 903 is sdo.oma. If nt, the service may be aware that it is related to Notification.

6 is a signal flowchart illustrating a case in which a notification message is subscribed through a bidirectional network in a portable broadcasting system according to a first embodiment of the present invention. Referring to FIG. 6, the terminal 119 receives a service guide in step 601. Thereafter, the terminal 119 confirms the notification contents from the service guide received in step 602 using the service guide as described in FIG. 5 and receives a notification in the bidirectional network upon subscription / purchase of the service. Determine whether or not to subscribe to the notification message (Notification Message).

An example of a subscription request message for this is shown in the following Tables 7a to 7c.

In step 603, the terminal 119 requests subscription or purchase of a notification message to the BSP-M 301 using the BSP-C 302. The BSP-M 301 then processes the subscription request message in step 604 and stores the service and user information. The BSP-M 301 processes the matter and transmits a response message to the BSP-C 302 in step 605. An example of the response message is shown in Table 8 below.

If the terminal determines to cancel the notification message in step 611 after receiving the service, the BSP-C 302 requests the subscription and cancellation of the purchase in step 612. An example of the cancellation request message is shown in Table 9 below.

The BSP-M 301 processes the release request in step 613 and then provides a response message to the BSP-C 302 in step 614. An example of the response message is shown in Table 10 below.

FIG. 7 is a diagram illustrating a generation and request process of a notification message event in a portable broadcasting system according to a first embodiment of the present invention. In FIG. 7, the NTG 203 receives a notification event or receives a notification event. It shows the flow up to the process of creating a message and requesting a message transmission for the notification event occurred within 113).

Referring to FIG. 7, in operation 701, the NTG 203 receives a notification event from the BSM 113 or receives a notification event from another network entity. Here, Tables 11a to 11c show messages for requesting to generate a notification message from a corresponding network entity (CC, BSA, BSD / A) when a notification event occurs. In addition, Table 12 below shows an example of a response message to the request message.

If a notification event occurs or a notification event is received from another network entity, the NTG 203 generates a notification message in step 702. Then, in step 703, it is determined through which path to send the notification message. The notification message may be delivered in a broadcast channel, a bidirectional channel, or a broadcast / bidirectional channel. In case of sending a notification message to the broadcast channel 710, in step 711, a target session address (TargetSession Address) to which the notification message is sent is checked. In step 712, a delivery request message for requesting delivery of a notification message including a target address is generated, and in step 713, the NTDA 202 is requested to transmit a notification message.

In contrast, when the notification message is transmitted to the bidirectional network 720, in operation 721, the target user address of the user who agrees to receive the notification message through the bidirectional network is subscribed. Thereafter, in step 722, a transmission request message for requesting transmission of the notification message to the NTDA 202 is created, including target addresses of all users associated with the notification message. At this time, if there are a large number of users, the transmission request message may be written in a plurality of requests for the same notification message. Thereafter, in step 723, the notification delivery request message is transmitted to the NTDA 202.

8 is a flowchart illustrating a process of receiving a request for transmission of a notification message from the NTG 203 by the NTDA 202 and delivering the message to the terminal. Referring to FIG. 8, the NTDA 202 receives a transmission request message for a notification message in step 801. The following Table 13a to Table 13c show an example of a request message for transmission of a notification message from NTDA 202 to NTG 203, and Table 14 shows an example of a response message thereto.

The NTDA 202 checks a target address included in the request message in step 802. In operation 803, the target address information is determined to determine a broadcast channel or an interaction channel for transmission. In the case of transmission through the broadcast channel 801, in step 811, after confirming session information such as an IP address from target address information in the request message, a notification message is transmitted to the corresponding session.

In contrast, in the case of the interactive channel 820, the type of the target address is determined in step 821. Then, in step 822, the transmission method is determined according to the type of the target address, and a notification message is transmitted.

FIG. 10 is a view illustrating an example screen of a user terminal through a service guide receiving method in a mobile broadcasting system according to a first embodiment of the present invention. And the flow of operation.

After receiving the service guide, the user terminal can check the information on the service and the content, and can check the service bundle information through the purchase item information. That is, the service guide content is displayed on the terminal screen 1001 so that the user can check the service content. The terminal screen 1001 is an example screen for a sports channel bundle. Reference numeral 1011 denotes a service bundle name as a title of a purchase item, and reference numeral 1013 denotes a list of services included in the bundle. Reference numerals 1012 and 1014 confirm whether or not a notification message is provided through interaction for each service. In this example, only ESPN and SBS Sports provide a notification message through interaction. When the user subscribes to the service through the reference numeral 1015 button, the user moves to the subscription message creation screen as shown by the reference numeral 1002. If a user wants to receive a notification message through interaction for a specific service, the user selects it from a check box of 1024 and subscribes to a service and a related notification message through a reference 1025 button. The service is delivered to the BSM through a service provisioning subscription message including a subscription. Termination is also made through a similar method and will be omitted.

In the second embodiment, a method of transmitting a notification message in a digital video broadcasting (Convergence of Broadcasting and Mobile Service: DVB-CBMS) system, which is another portable broadcasting standard organization, will be described.

Terms for the network architecture and interface used in the second embodiment of the present invention, and information transmitted between the network and the terminal will be described by mapping them to terms used in the DVB-CBMS WG. It is described to show that the present invention can be applied to a broadcasting system, and the gist of the present invention is not changed.

FIG. 11 is a diagram illustrating an electronic service guide (ESG) transmission structure of a CBMS mapped to FIG. 1. Definitions of network entities used in FIG. 11 are shown in Table 18 below. <Table 18a> and <Table 18b> are classified for convenience. Among the entities shown in FIG. 11, an important entity in the present invention is a 'Specific Logical ESG Aggregator', which is a function of combining the SG-D 110 and the SG-G 109 of FIG. 1, that is, generating and transmitting an ESG. .

FIG. 12 is a diagram corresponding to FIG. 2 based on OMA, showing a structure of network entities for transmitting a notification message in a CBMS.

Referring to FIG. 12, a content creation (CC) 1201 is a provider of a broadcast service, and the broadcast service may be a conventional voice / video broadcast service, a file (music file or data file) download service, or the like. Can be. When a problem or a change occurs in the provision of a broadcast service, the content provider 1201 changes the notification to a notification event generator (NEF) 1202a inside a broadcast service application (SA) 1202. Notice the matter. The notification event generator 1202a transmits a notification message event to a notification generation function (NGF) 1203a based on the received event.

The broadcast service application 1202 receives the content data of the broadcast service from the content provider 1201 and processes the broadcast data into a form suitable for a broadcast network (for example, streaming audio / video or movie download) to create broadcast service data. It is responsible for generating standardized metadata required for service guides and generating billing information according to users. In addition, the notification of the change in the broadcast service from the content provider 1201 and delivers a notification event to the notification generation function (Notification Generation Function) 1203a located in the broadcast service management unit (1203). Service guide attribute information used to generate the notification message is provided to the notification message generator 1203a.

The broadcast service management unit (SM) 1203 is responsible for determining a transmission schedule of a broadcast service received from the broadcast service application 1202 and generating a service guide. It is connected to an H network 1206 and an Interaction Network 107 supporting bidirectional communication. In addition, the broadcast service management unit 1203 has a Notification Distribution / Adaption Function (NDAF) 1203b therein, and receives a notification message from the broadcast service management unit 1203 to receive the broadcast network 1206. Alternatively, a notification message is transmitted to one terminal or a group of terminals through the interworking network 1207. The broadcast service management unit 1203 has session information necessary for the notification message generation unit 1204a to generate a notification message for a terminal, and the session information is sent from the notification distribution / adaptation unit 1203b to the notification message generation unit 1203a. Is provided.

The broadcast service manager 1203 may provide service provisioning information such as subscriber information for receiving a broadcast service and information on whether the subscriber has purchased related contents, and device information for terminals receiving the broadcast service. It manages, and transmits the user billing information to the service application 1202 and provides the subscription information, service provision information, device information and the like to the broadcast network 1206 and the interworking network 1207. In particular, the broadcast service management unit 1203 includes a notification generation function (NGF) 103a, so that the content provider 101, the service application 1202, the service management unit 1203, and the broadcast network 1206 are provided. A notification message for the notification event is generated when an event such as a new function has been added or changed, or information indicating that the broadcast is provided after a predetermined time is provided. Create a notification message for your own event.

The broadcast network 1206 is a network for transmitting a broadcast service. As an example, the present disclosure will be described with reference to DVB-H. When a change occurs in transmitting a broadcast service, the broadcast network 1206 notifies the change to the broadcast service manager 1203 through the CBMS-6 interface 1224a or the X-3 interface 124b. Do this.

The interworking network 1207 exchanges control information and additional information related to transmitting a broadcast service one-to-one or receiving a broadcast service in both directions, and may be an existing cellular network such as 3GPP wideband code division multiple access (WCDMA). Can be.

The terminal 1208 is a terminal capable of receiving a broadcast service and has a function of being connected to a cellular network according to the capability of the terminal. In the description of the present invention, it is assumed that the terminal can be connected to the cellular network. The terminal 1208 is informed by a Notification Client Function 1208a. Receive a notification message sent through the CBMS-5 interface 1225 to perform an appropriate operation, or receive a notification message sent through the CBMS-4 interface 1226 to perform an appropriate operation.

Next, interfaces between respective block configurations of the portable broadcasting system will be described.

The CBMS-7 interface 1222 is an interface from the notification event unit 1202a located in the broadcast service application 1202 to the notification message generation unit 1203a of the broadcast service management unit 103, and in the notification message generation unit 103a. In order to generate a notification message, information necessary for generating a notification message or notification message (for example, attribute information of a service guide) is carried.

The CBMS-3 interface 1225 is used when the notification message transmitted from the notification distribution / adapter 1203b of the broadcast service management unit 1203 is directly transmitted to the terminal 1208 through the broadcast channel via the broadcast network 106. An interface that is used to transmit a notification message to one terminal or multiple terminals.

In the CBMS-4 interface 1226, a notification message transmitted from the notification distribution / adapter 1203b of the broadcast service management unit 1203 passes through the interworking network 1207 in a dedicated channel or the interworking network 1207 with the terminal 1208. An interface used when directly transmitted to the terminal 1208 through a provided broadcast channel, and used to transmit a notification message to one terminal or a plurality of terminals.

The CBMS-6 interface 1224a is a broadcast service manager 1203 used by the broadcast service manager 1203 to set up a transmission path that will be used by the broadcast network 1206 or as a reception path for event information generated in the broadcast network 1206. ) And the broadcast network 1206.

The X-3 interface 1224b is an interface used for setting a transmission path to be used between the broadcast service manager 1203 and the interworking network 1207.

The CBMS-1 interface 1233 is an interface on which a control signal of a broadcast network is to be delivered to a terminal, and in DVB-H, a control signal channel called PSI / SI (Program Specific Information / Service Information) corresponds to this.

The notification event generating unit 1202a transfers the information necessary for generating the notification message to the notification message generating unit 1203a, and when the notification event generating unit needs to know that an event requiring notification has occurred, the notification event generating unit 1202a provides information about the event. 1203a). The notification message generating unit 1203a receives information and an event necessary for generating the notification message from the notification event generating unit 1202a and generates a notification message, or generates a notification message through the notification distribution / adapting unit 1203b of the broadcast network 1206. When the notification event is received, a notification message is generated and transmitted to the notification distribution / adaptation unit 1203b. When the notification message is generated, when it is necessary to notify the start of the service again, the content provider 1201 is notified that there is a change in the information of the service and when it is necessary to transmit a new service guide and the broadcast network It may be the case that a special event occurs at 106.

The notification distribution / adapter 1203b transmits a notification message through the CBMS-31225 or the CBMS-41226, and changes of information on a specific portable broadcasting service from the broadcast network 1206. For example, when receiving a control of a transmission rate or a service unavailable due to a wireless network environment, a notification event is transmitted to the notification message generator 1203a.

Compared with each entity of FIG. 2, each network entity corresponding to the notification message is omitted because the definition and name of the case of OMA and CBMS are the same. For the interface, NT-6 corresponds to CBMS-4 and NT-5 corresponds to CBMS-3.

FIG. 13 is a diagram related to the service purchase of the CBMS corresponding to FIG. 3 based on OMA, and descriptions of the entities of FIG. 13 are shown in Table 19. Tables 19a and 19b are for convenience.

Among the entities of FIG. 13 and Table 19, what is needed in the gist of the present invention is a 'Subscription Management' entity, a 'Rights issuing' entity, and a 'Key management system agent' entity in the terminal.

Among the entities of FIG. 13 and Table 19, what is needed in the gist of the present invention is that the roles of the 'Subscription Management' entity and the 'Rights issuing' entities are mapped to the roles of the BSP-M of FIG. 3, and the 'Key management system agent' entity is shown in FIG. It corresponds to BSP-C of 3.

FIG. 14 is a diagram corresponding to FIG. 4 based on OMA, and illustrates signaling corresponding to each of the signaling 402, 403, 405, and 408 between each network entity described in FIG. 4. That is, reference numerals 402, 408, 403, and 405 of FIG. 4 correspond to 1450, 1460, 1470, and 1440 of FIG. 14, respectively.

FIG. 15 is a diagram corresponding to a CBMS-based ESG data model fragment corresponding to FIG. 5. However, in FIG. 15, the fragment corresponding to the purchase item (PurchaseItem) is omitted since there is no role to perform according to the gist of the present invention. Referring to each fragment, the 'Service' fragment of FIG. 5 corresponds to the 'Service' fragment in FIG. 15 and the 'Access' fragment corresponds to the 'Acquisition' fragment. In addition, when looking at each element value and attribute value in the fragment, 'ServiceType' is 'ServiceType', 'AccessType' is 'SessionDescription', 'ServiceClass' is 'ComponentCharacteristic', and 'NotificationReception' is 'NotificationReception'. admit. That is, in FIG. 15, 'NotificationService' may be defined as one kind of general ServiceType in 'ServiceType', and the corresponding connection is defined in SessionDescription 'as shown in FIG. 5 containing access information for accessing a notification message. Information can be mapped and can be mapped to indicate that the component type of the corresponding acquisition fragment is a notification message by defining a NotificationComponentType in addition to video, audio, and file using a 'ComponentCharacteristicType' element such as 'ServiceClass' indicating a notification message service class. .

Table 20 below shows the XML schema of the newly defined NotificationComponentType and has a NotificationType as an element value.

Next, message formats of CBMSs corresponding to <Table 7> to <Table 17> representing notification message subscription / cancellation message formats corresponding to FIG. 6 will be described. However, Table 13 and Table 14 do not need to be applied to CBMS because the interface corresponding to BCAST-4 is not necessary according to the configuration of network entity of CBMS. Tables 20 and 21 below correspond to <Table 7>, <Table 9>, <Table 15>, <Table 16>, and <Table 17> of the OMA-based embodiment. In addition, <Table 8>, <Table 10>, <Table 11>, and <Table 12> are used as they are messages that do not change when mapped to CBMS network.

Table 21 below is an example of a notification message subscription request message tailored to a CBMS network according to the gist of the present invention, which is mapped to Table 7 above, and Table 21b below shows the services of Table 15 below. Includes an embodiment that enables subscription by ID. In the red italic part of <Table 21> below, it is added to request notification message subscription.

The following <Table 22> is an example of a notification message termination request message, which is a result of mapping the termination messages of <Table 9>, <Table 16>, and <Table 17> to the CBMS network. As shown in Table 22b, each service ID can be used to individually terminate the applied notification message. If it is not necessary to cancel each service ID, Table 22a cancels the notification of the entire Purchase Item. Will be the same as the embodiment. Also, when canceling a general service, if you do not want to cancel the notification message related to the service, use the 'KeepSubscription' attribute value as shown in <Table 22c> to close the main service and provide it with the main service. The notification message may not be canceled.

7 and 8 are used in the CBMS-based embodiment as it is, so a detailed description thereof will be omitted.

FIG. 16 illustrates elements of the ESG data model described with reference to FIG. 15 by mapping the ESG data model of FIG. 9 of the OMA-based embodiment to the CBMS ESG data model. Referring to FIG. 16, it can be seen that 'NotificationComponentType' 1603 is newly defined to indicate an Acquisition fragment for a notification message in Component Characteristic.

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 the equivalents of the claims.

As described above, the present invention can transmit a notification message in a bidirectional channel as well as a broadcast channel by defining a notification message in a bidirectional channel. In addition, a method of confirming that there is a notification message as a service or an auxiliary means of the service from the service guide, and through this, subscription and termination of the notification message can be performed.

Claims (1)

A notification message transmission method in a portable broadcasting system supporting a bidirectional channel, When the notification generator receives the notification event by a predetermined method, creating a notification message corresponding thereto; Determining, by the notification generating unit, a path of the notification message; When the path of the notification message is a bidirectional channel, transmitting a transmission request message including a target address of the terminal to a notification distribution / adaptive unit; And transmitting a notification message to the terminal through the target address after confirming the transmission path and the target address by the notification distribution / adaptive unit receiving the transmission request message.

Images