JP2009528763A - Notification message providing method and apparatus in mobile broadcast system - Google Patents

Abstract

  A method for providing a notification message at a transmitter of a mobile broadcast system that supports a bi-directional channel is disclosed. The first means generates a notification message when a notification event occurs, and generates at least one transmission request message including a target address based on subscription information of a corresponding terminal using the generated notification message. Then, the second means determines a channel for transmitting the notification message to the corresponding terminal based on the target address, and transmits the notification message through the determined channel.

Description

  The present invention relates to a notification message providing method and apparatus in a mobile broadcast system, and more particularly, to a notification message providing method and apparatus using a bidirectional channel in a mobile broadcast system.

  In the mobile communications market, there is a continuing demand for the production of new services through the reconfiguration or integration of existing technologies. Currently, with the development of communication and broadcast technologies, conventional broadcast systems or mobile communication systems provide broadcast services via mobile terminals (mobile terminals) such as mobile phones and PDAs (Personal Digital Assistants). Such potential and practical market demands, rapidly increasing user demand for multimedia services, service provider's target strategy to provide new services such as broadcast services in addition to existing voice services, In the background of the interest of IT (Information Technology) companies that are strengthening the mobile communication business at the request of users, the fusion of mobile communication services and Internet protocol (IP) is the mainstream in the development of next-generation mobile communication technology It has become.

  The Open Mobile Alliance (hereinafter referred to as “OMA”) is a group that studies standards for interoperability between individual mobile solutions, such as mobile communication games and Internet services. It plays a role in setting various application standards. In particular, in this OMA working group, OMA BAC (Browser and Content) BCAST (Mobile Broadcast Sub Working Group) is researching a technology for providing a broadcast service using a mobile terminal. The following briefly describes the mobile broadcast system discussed in the OMA BCAST working group.

  In the mobile broadcast system, a mobile terminal for receiving a broadcast service includes explanation information about the service itself, billing information about the service, and information about a method of receiving the service.

  A mobile broadcast system includes a process of discovering a service by a terminal capable of receiving a mobile broadcast, a process of subscribing to a service by the terminal, and a process of providing various control information for receiving the service. The process of transmitting the service and the process of receiving the service by the terminal are included. In this mobile broadcast system, during a mobile broadcast process, when receiving a broadcast service, a terminal receives a notification message including various control information related to the broadcast service.

  In a mobile broadcast system, fluctuations may occur in the broadcast system due to various factors while the terminal is receiving the broadcast. Some of these variations may be information that should be provided to the terminal. For example, this information may include a change in mobile broadcast service time, a change in information for receiving the mobile broadcast service, and so on.

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

  However, in the mobile broadcast system that supports the bidirectional channel, the method for transmitting the notification message has not been defined yet. Therefore, a definition for the transmission method of this notification message is required.

  Accordingly, the present invention has been proposed to solve the above-described problems of the prior art, and an object thereof is to provide a method and system for transmitting a notification message in a mobile broadcast system. .

  Another object of the present invention is to provide a method and system for transmitting a notification message in a mobile broadcast system that supports bidirectional channels.

  In order to achieve the above object, according to one aspect of the present invention, a method for providing a notification message in a transmitter of a mobile broadcast system that supports a bi-directional channel includes: (a) the occurrence of a notification event; An entity managing terminal subscription information generates a notification message, and using the generated notification message, generates at least one transmission request message including a target address based on the terminal subscription information; (B) an entity that transmits the notification message determines a channel for transmitting the notification message to a corresponding terminal based on the target address, and transmits the notification message through the determined channel; It is characterized by comprising.

  According to another aspect of the present invention, a transmitter in a mobile broadcast system supporting a bidirectional channel manages subscription information of a terminal, generates a notification message when a notification event occurs, and generates the notification message. The notification message is used to determine an entity that generates at least one transmission request message including a target address based on subscription information of the terminal, and a channel to be transmitted to the terminal based on the target address. And an entity that transmits the notification message through a channel.

  According to still another aspect of the present invention, a method for receiving a notification message in a terminal of a mobile broadcast system that supports a bidirectional channel confirms a notification content from a service guide, checks service subscription / purchase information, Transmitting a notification message subscription request message including reception channel information of the notification message to an entity managing subscription information of the terminal; receiving a response message including authentication information from the entity managing subscription information; Receiving a notification message transmitted according to the transmission channel information after completion of the authentication.

  According to still another aspect of the present invention, a terminal in a mobile broadcast system supporting a bidirectional channel confirms notification contents from a service guide, checks service subscription / purchase information, and receives reception channel information of a notification message. A notification request including a notification message is transmitted to an entity that manages subscriber information of the terminal, and in response thereto, a first entity that receives authentication information, and after completion of the authentication, according to the transmission channel information And an entity for receiving the transmitted notification message.

  According to still another aspect of the present invention, a method for providing a notification message in a mobile broadcast system that supports a bidirectional channel includes: a terminal confirming notification content from a service guide; checking service subscription / purchase information; Transmitting a subscription request message of a notification message including reception channel information of the notification message to a transmitter managing the subscription information of the terminal; the transmitter performs authentication according to the subscription request message; and the subscription information of the terminal And a notification message of a corresponding service is transmitted based on the channel information when a notification event occurs.

  According to still another aspect of the present invention, a mobile broadcast system supporting a bidirectional channel confirms notification contents from a service guide, checks service subscription / purchase information, and includes reception channel information of a notification message. A terminal that transmits a subscription request message of a notification message to a transmitter that manages the subscription information of the terminal, and stores the subscription information of the terminal according to the subscription request message, and based on the channel information when a notification event occurs And a transmitter for transmitting a notification message of a corresponding service to the terminal.

  In the present invention, by defining a notification message in a bidirectional channel, the notification message can be transmitted not only in a broadcast channel but also in a bidirectional channel. Provide a way to verify that it is. In this way, it is possible to subscribe and cancel the corresponding notification message.

  DESCRIPTION OF EXEMPLARY EMBODIMENTS Hereinafter, a preferred embodiment of the invention will be described in detail with reference to the accompanying drawings. In the drawings, the same reference numerals and numbers are used in common as much as possible to the same components and parts. In the following description, specific descriptions regarding functions and configurations well known to those skilled in the art are omitted from the viewpoints of clarity and conciseness.

The present invention proposes a method and system for managing notification messages in a mobile broadcast system that supports bidirectional channels. A mobile broadcast system according to the present invention will be described for each embodiment. A notification message transmission method according to the present invention will also be described. In the first embodiment, the third Generation Partnership Project is a standards group for asynchronous mobile communication: either defined ^{(3 rd Generation Partnership Project 3GPP)} , or Open Mobile Alliance (Open a standardized group of applications of the terminal A broadcast system defined by “Mobile Alliance: hereinafter referred to as“ OMA ”) will be described. In the second embodiment, another mobile broadcast standardization group, Digital Video Broadcasting-Convergence of Broadcasting. and Mobile Service (DVB-CBMS) system will be described. The first embodiment of the present invention will be described with reference to the architecture and terminology used in OMA, and the architecture and terminology used in the second embodiment will refer to the mobile broadcast system according to the first embodiment. To the architecture and terminology.

  For further understanding of the notification message, the mobile broadcast system according to the first embodiment will be described. Even though entities and names defined in OMA BCAST are used in the first embodiment, such standards and entity names do not limit the scope of the invention and have a similar technical background. It can also be applied to the system.

  In a mobile broadcast system, a mobile terminal that receives a broadcast service must receive service guide information including description information about the service itself, billing information about the service, and information about a service reception method. The mobile terminal receives the corresponding service using this service guide information.

  Although the present invention has been described with reference to OMA BCAST technology, which is one of the standards for mobile broadcast technology, this description does not limit the content of the present invention.

  FIG. 1 is a diagram illustrating components for transmitting a service guide to a mobile terminal in the mobile broadcast system according to the first embodiment of the present invention. Prior to the description of FIG. 1, the definition of the interface used between each component is as shown in Table 1.

  Referring to FIG. 1, a content provider (CC) 101 is a provider of a broadcast service (hereinafter referred to as “BCAST service”). The BCAST service is a conventional audio / video broadcast service, music file. Alternatively, a data file download service or the like can be included. The CC 101 uses the service guide content creation source (Service Guide Content Creation Source: hereinafter referred to as “SGCCS”) unit 102 to use the content information necessary to generate the service guide for the BCAST service and the performance information of the mobile terminal. , User profile, content time information, and the like, the service guide application source (Service Guide) of the BCAST service application (hereinafter referred to as “BSA”) 104 via the SG1 interface 103 of Table 1 described above. Application Source: hereinafter referred to as “SGAS”).

  The BSA 104 plays a role of processing BCAST service data provided from the CC 101 in a format compatible with the BCAST network. The BSA 104 also serves to generate standardized metadata necessary for mobile broadcast guides. The SGAS unit 105 includes information provided from the SGCCS unit 102, and transmits various sources necessary for generating a service guide such as service / content detailed information, schedule information, and location information via the SG2 interface 106. The data is transmitted to a service guide generation (Service Guide Generation: hereinafter referred to as “SG-G”) unit 109 in service distribution / adaptation (BSD / A) 108.

  The BSD / A 108 is responsible for setting a bearer for transmitting BCAST service data provided from the BSA 104, for determining a transmission schedule for the BCAST service, and for generating mobile broadcast guide information. The BSD / A 108 supports both a broadcast distribution system (hereinafter referred to as “BDS”) 131 for transmitting BCAST service data via a broadcast channel and bidirectional communication via a bidirectional channel. It is connected to a communication network (IN) 133.

  The service guide generated from the SG-G unit 109 is transmitted to the mobile terminal (ie, terminal) 119 via the service guide distribution (SG Distribution: hereinafter referred to as “SG-D”) unit 110 and the SG5 interface 117. Is done.

  The BCAST subscription management (BSM) unit 113 manages subscription information and service provision information for receiving the BCAST service, and device information related to the mobile terminal that receives the BCAST service. A Service Guide Subscription Source (hereinafter referred to as “SGSS”) unit 114 in the BSM 113 includes a subscription / supply source related to generation of a service guide, and a source such as purchase information and advertisement related information. , Are transmitted to the SG-G unit 109 for generating a service guide via the SG4 interface 112.

  The terminal 119 is a terminal that can receive the BCAST service, and has a function of connecting to the cellular network according to the performance of the terminal. A terminal 119 including a service guide client (hereinafter referred to as “SG-C”) 120 receives a service guide transmitted through the SG5 interface 117 or transmits it through the SG6 interface 118. Received notification message and take appropriate action for reception of the BCAST service.

  Table 2 to Table 4 below describe the definition of functions for the main components of FIG. 1 defined in the OMA BCAST service standard.

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

  The CC 101 is a provider of a broadcast service (hereinafter referred to as “BCAST service”). The BCAST service may include a conventional audio / video broadcast service, a music file or data file download service, or the like. When a problem or a change item occurs in the supply of the BCAST service, the CC 101 notifies the change event to the notification event unit (NTE) 201 in the BSA 104.

  The BSA 104 serves to process the data of the BCAST service provided from the CC 101 in a format compatible with the BCAST network and generate standardized metadata necessary for the mobile broadcast guide. Also, the BSA 104 notifies the notification generation unit (NTG) 203 in the BSM 113 of the variation of the BCAST service provided from the CC 101.

  The BSD / A 108 plays a role of setting a bearer channel for transmitting BCAST service data provided from the BSA 104, a role of determining a transmission schedule of the BCAST service, and a role of generating mobile broadcast guide information. Connected. The BSD / A 108 having the notification distribution / adaptation unit (NTDA) 202 receives a notification message from the BSM 113 and transmits the notification message to an individual user or a plurality of users via the BDS 131 or the IN 133.

  The BSM 113 manages subscription information for receiving the BCAST service, service provision information, and device information regarding the mobile terminal that receives the BCAST service. In particular, the BSM 113 including the NTG 203 receives information on notification events generated at various network entities for providing mobile broadcast services and uses this received information to generate a notification message or BCAST. Generate a notification message for the service's own event.

  The terminal 119 is a terminal that can receive the BCAST service, and has a function of being able to connect to the cellular network depending on the performance of the terminal. The terminal 119 receives a notification message transmitted via the NT5 interface 214 using the notification client unit (NTC) 204 and performs an appropriate operation according to the NT5 notification message or transmits the notification message via the NT6 interface 215. Received notification message and perform appropriate action according to the NT6 notification message.

  Next, an interface between logical entities will be described.

  The NT-1 interface 211 is an interface between the NTE 201 located in the BSA 104 and the CC 101, and is used to transmit a notification event generated in the CC 101 to the NTE 201.

  The NT-3 interface 212 is an interface from the NTE 201 located in the BSA 104 to the NTG 203 in the BSM 113, and information necessary for event notification or notification message generation so that the NTG 203 can generate a notification message. Transport.

  The NT-4 interface 213 is an interface from the NTG 203 located in the BSM 113 to the NTDA 202 in the BSD / A 108, and transmits the notification message generated by the NTG 203 to the NTDA 202 or the BSD for transmission to the BDS 131 or IN 133. / A 108 and BDS 131 are used to transmit events generated in the NTDA 202.

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

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

  The NT-B1 interface 216 is used as a transmission path in which the BSD / A 108 is used in the BDS 131, or is used as a reception path for event information generated in the BDS 131. The NT-B1 interface 216 is an interface between the BSD / A 108 and the BDS service distribution unit (BDS-SD) 130.

  The NTE 201 has a role of transmitting information necessary for generating a notification message to the NTG 203 and a role of transmitting information regarding the occurrence of the notification event to the NTG 203 when an event requiring notification occurs. The NTG 203 generates a notification message using information and events necessary for generating a notification message received from the NTE 201, or generates a notification message when receiving a notification event from the BDS 131 or the IN 133 via the NTDA 202. The notification message is transmitted to the NTDA 202. The NTG 203 needs to (i) transmit a new mobile broadcast guide when receiving a notification indicating a change in service information from the CC 101 when it is necessary to further notify the start of this service. And (iii) this notification message can be generated if a specific event occurs in the BDS 131 or IN 133.

  The NTDA 202 serves to transmit a notification message via the NT-5 interface 214 or the NT-6 interface 215. In addition, upon receiving information from the BDS 131 indicating information indicating a change in a specific mobile broadcast service, for example, information indicating that the service is disabled or the transmission speed is adjusted due to the wireless network environment, the NTDA 202 sends a corresponding notification event to the NT- 4 to the NTG 203 via the interface 213.

  FIG. 3 is a diagram illustrating an architecture for service provision in the mobile broadcast system according to the first embodiment of the present invention. The service supply architecture is responsible for user subscription to the BCAST service and the purchase procedure for the subscribed service. The service supply architecture also provides additional information to process payments and purchases, such as user account status information.

  Referring to FIG. 3, a broadcast service supply management (BSP-M) unit 301 provides subscription and purchase information. Based on the user subscription information, the BSP-M 301 provides user charging information to related entities to support charging for mobile broadcast services. The BSP-M 301 receives subscription and billing requests and reports from the broadcast service supply client unit (BSP-C) 302 via the SP-7 interface 311 and the SP-8 interface 312. The BSP-C 302 serves as a report on subscriptions and purchases for mobile broadcast services. The BSP-C 302 can request subscription and purchase, or request additional information based on supply information extracted from the service guide. The description regarding the SP-7 interface 311 and the SP-8 interface 312 is as shown in Table 5.

  Referring to <Table 6> below, the name indicates the name of the element value and attribute value constituting the corresponding message. The type indicates the type (element value or attribute value) of the corresponding name. The element values have values such as E1, E2, E3, and E4, E1 indicates the upper element value for all messages, E2 indicates the lower element value of E1, and E3 indicates the lower element of E2. E4 indicates a lower element value of E3. The attribute value is indicated by A, and A indicates the attribute value of the corresponding element. For example, A under E1 indicates the attribute value of E1. A category is used to determine whether a corresponding element value or attribute value is mandatory or optional, and has a value of M (Mandatory) if it is a mandatory element value or attribute value. If it is an arbitrary element value or attribute value, it has a value of O (Optional). Cardinality indicates the relationship between elements, 0, 0. . 1, 1, 0. . n, 1. . It has a value of n. Here, 0 means an arbitrary relationship, 1 means an essential relationship, and n means that a plurality of values can be used. For example, 0. . n means that the corresponding message may not have an element value and may have n element values. The description indicates the meaning of the corresponding element value or attribute value, and the data type indicates the data type for the corresponding element value or attribute value.

  FIG. 4 is a block diagram illustrating an architecture for transmitting a notification message in the mobile broadcast system according to the first embodiment of the present invention. For convenience of explanation, among the entities described in FIGS. 1 to 3, only elements necessary for transmission of the notification message are included in FIG.

  Referring to FIG. 4, the SG-G 109 generates a service guide including time, purchase, and access information related to services and contents in step 401, and then transmits a request for service guide transmission to the SG-D 110. . Thereafter, the SG-D 110 transmits a service guide to the terminal 119 in step 402. This service guide may be transmitted via a broadcast channel and / or a bi-directional channel through BDS and / or IN. When this service guide is transmitted via the broadcast channel, the terminal 119 receives the service guide from the session in which this service guide is transmitted, and when this service guide is transmitted via the bidirectional channel, After connecting to the IN, the terminal 119 receives this service guide in response to a corresponding request.

  The SG-C 120 in the terminal 119 is in charge of receiving the service guide from the SG-D 110, and the user acquires service and content information from the received service guide. The user determines subscription and purchase information regarding services, schedules, contents, and the like based on the service guide, and then uses BSP-C302 to make a request for service supply such as subscription and purchase. In response to receiving the notification message related to the service, the BSP-C 302 transmits a subscription or unscription request to the BSP-M 301 in step 403.

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

  The NTG 203 creates a notification message for the received event. After generating the notification message, the NTG 203 confirms the target address for transmitting the notification message from the DB 411 and then generates a request message for message transmission. If there is a user who has subscribed to the message reception service via the bi-directional channel, the NTG 203 generates a request message that includes information about an address at which the corresponding user can receive the message.

  In step 407, the NTG 203 sends a request for transmission of the notification message to the NTDA 202. NTDA 202 transmits this notification message to NTC 204 at step 408. At this time, the NTDA 202 transmits this notification message via the broadcast channel or the bidirectional channel according to the target address.

  This notification message can be broadly classified into a common notification message for a notification service and a service specific notification message as service-related auxiliary means. After receiving the service guide, the terminal or the user can recognize the common notification message and / or the service specific notification message according to the following procedure. Here, 'notification service' means a service configured by notification. For example, the notification message may be a service transmitted via a short message service (SMS) or multimedia messaging service (MMS) notification message every day, such as 'Today's weather information', 'Today's English'. means. The service specification notification message as an auxiliary means is not an independent notification service but an example of an auxiliary service for the main program. For example, while a service such as “Music Top 10” is being broadcast, a vote for the first song is performed, and an SMS notification message for such a vote collects voting information. The notification message for voting is a service specific notification message as an auxiliary means. That is, the notification service means a service configured only by notification, and the service specific notification message means a notification message that can occur in the main program.

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

  In the particular service in which the notification message is transmitted, the terminal may: (ii) if the access fragment associated with the service includes the element value notification reception 904, (ii) the element value service class 903 in the access fragment associated with the service. 'Sdo. oma. nt 'or a similar fragment value indicating the likelihood of receiving a notification message such as' NTviaInteraction' in a service fragment or purchased item fragment if it has a URI value indicating a notification value If there is an element value or attribute value, it can be recognized that a notification message related to the corresponding service can be received.

  5A to 5D are diagrams illustrating a detailed embodiment of a service guide including a notification value in the mobile broadcast system according to the first embodiment of the present invention. The access fragments in FIGS. 5A and 5B are shown in detail in FIGS. 9 and 9B and will be described in detail below.

  FIG. 5A shows an example of an access fragment 901 including notification reception information, and a notification message related to the corresponding service includes notification access information transmitted via the broadcast channel included in the element value notification reception 904. And includes information related to the corresponding service in element value access type 902.

  FIG. 5B is a diagram illustrating an example in which access to a service and a notification message is individually included. The purpose of distinguishing the corresponding access information depends on the value of the service class 903. For example, in the case of a file transmission service, service class 903 = ’sdo. oma. The access type 902 of access having “fd” includes access information that can be used for file download, and the service class 903 = ’sdo. oma. The access type 902 of access having nt 'includes access information for receiving the notification.

  FIG. 5C shows a configuration example of a service including only a notification message whose service type is a notification service. The difference between FIG. 5A and FIG. 5C is that the notification fragment is not included individually in the access fragment, but the access fragment includes address information for reception of the notification message.

  FIG. 5D is a configuration example in the case where a service corresponding to a specific schedule includes a notification when the service is subscribed / purchased.

  As described above, the terminal determines that the service type is the notification service, the access includes the notification reception 904, or the access service class 903 is sdo. oma. nt. , It can be recognized that the corresponding service is related to the notification.

  FIG. 6 is a flowchart illustrating subscription to a notification message through a bidirectional channel in the mobile broadcast system according to the first embodiment of the present invention.

  Referring to FIG. 6, the terminal 119 receives a service guide in step 601. Thereafter, in step 602, the terminal 119 confirms the notification contents using the service guide described in FIG. 5 from the received service guide, and during the service subscription / purchase, the terminal 119 passes through the bidirectional channel. After determining whether or not to receive the notification, the subscription to the notification message is determined.

  An example of the subscription request message for this is shown in Table 7A to Table 7C.

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

  After receiving the service, if the terminal 119 determines to cancel the notification message in step 611, the BSP-C 302 transmits a cancellation request for service subscription / purchase to the BSP-M 301 in step 612. An example of the cancellation request message is shown in <Table 9>.

  The BSP-M 301 transmits a response message to the BSP-C 302 in step 614 after processing the release request in step 613. An example of a response message to this is shown in Table 10.

  FIG. 7 is a diagram illustrating a generation process and a request process of a notification event in the mobile broadcast system according to the first embodiment of the present invention. This process shows a flow in which the NTG 203 receives a notification event or generates a message for the notification event generated in the BSM 113 and transmits a request for message transmission.

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

  When a notification event occurs or a notification event is received from another network entity, the NTG 203 generates a notification message in step 702. Thereafter, in step 703, the NTG 203 determines via which route the corresponding notification message is transmitted. This notification message can be transmitted over one or all of a broadcast channel and a bidirectional channel. If the NTG 203 decides to transmit the notification message via the broadcast channel 710, the NTG 203 confirms the target session address for transmitting the corresponding notification message in step 711. In step 712, the NTG 203 creates a transmission request message for requesting transmission of a notification message including the corresponding target address, and transmits a request for transmission of the notification message to the NTDA 202 in step 713.

  However, if the NTG 203 decides to transmit the notification message via the bi-directional channel 720, the NTG 203 will, in step 721, target the user who has agreed / subscribed to receive the notification message via the bi-directional channel. Check the user address. Thereafter, in step 722, the NTG 203 creates a transmission request message for requesting transmission of a notification message including target addresses of all users related to the notification message. At this time, if there are a plurality of users, the NTG 203 can create several transmission request messages for the same notification message. Thereafter, in step 723, the NTG 203 transmits a corresponding notification transmission message to the NTDA 202.

  FIG. 8 is a flowchart illustrating a process in which the NTDA 202 transmits a notification message to the terminal after receiving a transmission request for the notification message from the NTG 203.

  Referring to FIG. 8, the NTDA 202 receives a transmission request message for the notification message in step 801. Table 13A to Table 13C show an example of a transmission request message for the notification message transmitted from the NTG 203 to the NTDA 202. <Table 14> shows an example of a response message to this.

  In step 802, the NTDA 202 confirms the target address included in the request message. Thereafter, the NTDA 202 determines whether to use a broadcast channel or bidirectional channel for message transmission by parsing the target address information in step 803. When the NTDA 202 decides to use the broadcast channel 810 for message transmission, the NTDA 202 responds after confirming the session information such as the IP address from the target address information in the request message in step 811. Transmit a notification message in the session.

  However, if the NTDA 202 decides to use the bidirectional channel 820, the NTDA 202 confirms the type of the target address at step 821. Thereafter, in step 822, the NTDA 202 determines a transmission method according to the type of the target address, and then transmits a notification message using the transmission message.

  The following Table 15 to Table 17 show an example of performing subscription / cancellation for a notification message for each service in subscription of the notification message described with reference to FIG.

  Table 15 shows a message for a case where, when subscribing to a purchase item or a service bundle, reception of a notification message for a specific service is selected from among the services included in the corresponding bundle. The element values of Table 15 and the attribute values related thereto are transmitted together with the request message during service subscription in step 603 of FIG. If it is desired to receive the specific notification message for each service ID, the attribute value notification is set to TRUE. If it is not desired to receive the specific notification message for each service ID, the attribute value notification is set to FALSE. .

  <Table 16> shows a message for the case of canceling reception of the notification message for a specific service among the services included in the purchase item or the service bundle. The element values of Table 16 and the attribute values corresponding thereto are transmitted together with the request message during service release in step 612 of FIG. When it is desired to cancel the notification message for each service ID, the attribute value notification is set to TRUE. If this attribute value notification is set to FALSE or there is no attribute value notification, it means that the user is currently subscribed. When the user requests to cancel the corresponding purchase item or service bundle, reception of all related services and notification messages is canceled without having to select each service via <Table 16>. However, when the user wishes to cancel the notification message for a specific service while maintaining the subscription state to the purchased item and the service bundle, the above-described <Table 16> and <Table 17> are included in the cancellation message. The attribute value of <Table 17> is included in TRUE, and the cancellation of reception of the notification message can be selected for each service using <Table 16>.

  FIG. 10 is a diagram illustrating an exemplary screen of a user terminal through a service guide reception method in the mobile broadcast system according to the first embodiment of the present invention. Fig. 4 illustrates a method and process for subscribing to a notification message while subscribing to a purchased item via reception of a service guide.

  After the user terminal receives the service guide, the user can check the service and content information, and can also check the service bundle information through the purchase item information. When the user terminal displays the service guide content on the terminal screen 1001, the user can check the service content. The terminal screen 1001 is an exemplary screen for a sports channel bundle. Reference numeral 1011 indicates a service bundle name as the title of the purchased item, and reference numeral 1013 indicates a service list included in the corresponding bundle.

  Using reference numerals 1012 and 1014, the user checks whether a notification message is provided via interaction for each service. In this embodiment, only ESPN and SBS sports provide notification messages via interaction. When the user subscribes to the service using the subscription button 1015, the screen 1001 moves to the subscription message creation screen 1002. If a user wishes to receive a notification message via interaction for a particular service, select this with checkbox 1024 and request to subscribe to the service and associated notification message using button 1025 and respond accordingly. The information is transmitted to the BSM through a service provision subscription message including <Table 15>, so that the subscription is finally completed. Release is also done using a similar method.

  A notification message transmission method in a digital video broadcasting (DVB-CBMS) system according to a second embodiment of the present invention will be described.

  For convenience of explanation, the terms for the network entity, interface, and information transmitted between the network entity and the terminal used in the second embodiment of the present invention are mapped to the terms used in the DVB-CBMS WG. This is merely to show that the present invention can be applied to similar broadcast systems, and does not limit the scope of the present invention.

  FIG. 11 is a diagram illustrating a CBMS-based electronic service guide (ESG) transmission architecture mapped to the architecture of FIG. The definition of the network entity used in FIG. 11 is as shown in Table 18A and Table 18B below. Among the entities shown in FIG. 11, a specific logical ESG aggregator is an important entity in the present invention, and is a function that combines SG-D110 and SG-G109 of FIG. It plays the role of generating and transmitting ESG.

  FIG. 12 shows a diagram corresponding to the OMA-based architecture of FIG. 2 shows the architecture of a network entity for transmitting notification messages in CBMS.

  Referring to FIG. 12, a content supplier (CC) 1201 is a broadcast service provider, which may include a conventional audio / video broadcast service, a music file or data file download service, or the like. The CC 1201 notifies the notification event generation unit (NEF) 1202a in the service application (SA) 1202 when there is a problem or variation in supply of the broadcast service. The NEF 1202a transmits a notification event to the notification generation unit (NGF) 1203a based on the received event.

  In order to generate broadcast service data, the SA 1202 processes the content data of the broadcast service provided from the CC 1201 in a format suitable for the broadcast network (for example, audio / video streaming or movie downloading), and is necessary for the service guide. To generate standardized metadata and generate user billing information. Further, the SA 1202 transmits a notification event to the NGF 1203a in the service management unit (SM) 1203 for a change in the broadcast service provided from the CC 1201, and is a service guide used for generating a notification message. Attribute information is provided to NGF 1203a.

  The SM 1203 plays a role of determining a transmission schedule of a broadcast service provided from the SA 1202 and a service guide, and connects to a DVB-H network 1206 that supports a broadcast channel and a bidirectional network 1207 that supports a bidirectional channel. Is done. Also, the SM 1203 has a notification distribution / adaptive unit (NDAF) 1203b in the SM 1203, receives the notification message from the SM 1203, and transmits the notification message to one terminal or the like via the broadcast network 1206 or the bidirectional network 1207. Transmit to one group of terminals. The SM 1203 has session information required for the notification message generation unit 1204a to generate a terminal notification message. This session information is provided from the NDAF 1203b to the NGF 1203a.

  The SM 1203 manages service provision information such as subscription information for receiving a broadcast service and information indicating whether or not a user has purchased related content, and manages device information related to a terminal that receives the broadcast service. Further, the SM 1203 transmits user billing information to the SA 1202 and provides subscription information, service provision information, and device information to the broadcast network 1206 and the bidirectional network 1207. In particular, since the SM 1203 includes a notification generation unit (NGF) 1203a, an event has occurred that notifies the addition of a new function provided by the CC 101, the SA 1202, the SM 1203, and the broadcast network 1206 or a change in the current function. In some cases, a notification message is generated for this notification event, or a notification message for its own event indicating that the broadcast service provides content, that is, the corresponding broadcast service is provided after a predetermined time has elapsed. Generate.

  The broadcast network 1206 is a network that transmits a broadcast service. Here, for example, the DVB-H network is used as the broadcast network 1206. When there is a change in transmitting the broadcast service, the broadcast network 1206 serves to notify the SM 1203 of the change through the CBMS-6 interface 1224a or the X-3 interface 1224b.

  The bidirectional network 1207 transmits a broadcast service in a point-to-point manner, or exchanges control information and additional information related to reception of the broadcast service in both directions. For example, the bi-directional network 1207 can be an existing cellular network such as a 3GPP wideband code division multiple access (WCDMA) network.

  The terminal 1208 is a terminal that can receive a broadcast service, and has a function of connecting to a cellular network according to the performance of the terminal. Here, it is assumed that the terminal 1208 is a terminal that can be connected to the cellular network. The terminal 1208 receives a notification message transmitted through the CBMS-5 interface 1225 using the notification client unit (NCF) 1208a and performs an appropriate operation according to the received notification message, or CBMS- 4. A notification message transmitted via the four interface 1226 is received, and an appropriate operation is executed according to the received notification message.

  The CBMS-7 interface 1222 is an interface between the NEF 1202a located in the broadcast service application 1202 and the NGF 1203a of the SM 103. For the NGF 1203a to generate a notification message, the CBMS-7 interface 1222 can generate a notification or notification message regarding an event. Carries necessary information (for example, attribute information of service guide).

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

  The CBMS-4 interface 1226 is a terminal in which a notification message transmitted from the NDAF 1203b in the SM 1203 is transmitted via a dedicated channel with the terminal 1208 via the bidirectional network 1207 or via a broadcast channel provided by the bidirectional network 1207. This is an interface used when directly transmitted to 1208. This interface is used to transmit this notification message to one terminal or a plurality of terminals.

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

  The X-3 interface 1224b is an interface used for setting a transmission path used between the SM 1203 and the bidirectional network 1207.

  The CBMS-1 interface 1233 is an interface used when a control signal of the broadcast network 1206 is conveyed to the terminal 1208. In DVB-H, a control signal channel called program specific information / service information (PSI / SI) corresponds to this interface.

  The NEF 1202a transmits information necessary for generating a notification message to the NGF 1203a, and when an event requiring notification occurs, the NEF 1202a transmits information related to the event to the NGF 1203a. The NGF 1203a generates a notification message using the information and events necessary for generating the notification message received from the NEF 1202a, or receives the notification message when receiving the notification event from the broadcast network 1206 via the NDAF 1203b. It generates and transmits this notification message to the NDAF 1203b. The NGF 1203a (i) when it is necessary to further notify the start of this service, and (ii) when it is necessary to transmit a new service guide when receiving a notification indicating the change of service information from the CC 1201 And (iii) if a specific event occurs in the broadcast network 1206, this notification message can be generated.

  The NDAF 1203b is responsible for transmitting a notification message through the CBMS-3 interface 1225 or the CBMS-4 interface 1226. In addition, when receiving information from the broadcast network 1206 indicating information indicating a change in a specific mobile broadcast service, for example, information indicating an inability of service due to a wireless network environment or adjustment of a transmission rate, the NDAF 1203b performs a corresponding notification. The event is transmitted to NGF 1203a.

  Compared with the entity of FIG. 2, the network entity corresponding to the notification message is the same as the network entity of OMA and CBMS in terms of definition and name, and thus detailed description thereof is omitted. In the interface, NT-6 corresponds to CBMS-4, and NT-5 corresponds to CBMS-3.

  FIG. 13 is a diagram illustrating a CBMS-based service purchase architecture corresponding to the OMA-based architecture of FIG. The description of each entity in FIG. 13 is as shown in Table 19A and Table 19B.

  Among the entities shown in FIG. 13, <Table 19A> and <Table 19B>, the entities required for the present invention include a 'SubscriptionManagement' entity, a 'Rights Issuing' entity, and a 'Key Management System Agent' entity in the terminal. Including.

  The functions of the 'SubscriptionManagement' entity and the 'Rights Issuing' entity correspond to the function of the BSP-M301 in FIG. 3, and the 'Key Management System Agent' entity corresponds to the BSP-C302 of FIG.

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

  15A to 15D are diagrams illustrating CBMS-based ESG data model fragments corresponding to FIGS. 5A to 5D. However, since the fragment corresponding to the purchased item fragment is not directly related to the present invention, it is omitted here. The 'Service' fragment and the 'Acquisition' fragment correspond to the 'Service' fragment and the 'Access' fragment in FIGS. 5A to 5D, respectively.

  Explaining the element value and attribute value in the above fragment, 'ServiceType' corresponds to 'ServiceType', 'AccessType' corresponds to 'SessionDescription', 'ServiceClass' corresponds to' ComponentCharacteristic ',' “NotificationReception” corresponds to “NotificationReception”. That is, in FIG. 15A to FIG. 15D, 'NotificationService' can be defined as one type of ServiceType with 'ServiceType'. Since access information for accessing the notification message is included in ‘AccessType’ in FIGS. 5A to 5D, the corresponding access information is represented by ‘SessionDescription’. In addition to video, audio, and file, NotificationComponentType is defined using element value 'ComponentCharacteristicType' like 'ServiceClass' indicating notification message service class, so that the component type of the corresponding Acquisition fragment is the notification message. Indicates that

  Table 20A shows an example of a newly defined XML schema of NotificationComponentType, which has an element value NotificationType.

  A configuration similar to the following <Table 20B> is also possible. In <Table 20B>, NotificationType is defined as an element value NotificationComponentType, and a plurality of NotificationTypes can be used. Also, other components that can define NotificationComponent can be added. “Esg: ComponentCharacteristicType” in <Table 20B> below is a part indicating the characteristics of the basic components defined in the current DVB-CBMS ESG spec (ETSI TS 102 471), which is an existing VideoComponentType Or it is used similarly to what is used by AudioComponentType.

  Table 21A below shows an example of a notification message subscription request message adapted to the CBMS network according to the present invention, which is mapped to the message of Table 7 above, and Table 21B below shows the table <Table 21A> described above. Embodiments that allow subscription by service ID in Table 15> are included. In Table 21, the italicized part is a part added for this notification message subscription request.

  <Table 22A>, <Table 22B>, and <Table 22C> below show examples of notification message release request messages, which are release messages of <Table 9>, <Table 16>, and <Table 17>. Is the result obtained by mapping to the CBMS network. Referring to <Table 22B>, the requested notification message can be individually released for each service ID. When it is not necessary to cancel for each service ID, as shown in <Table 22A>, the embodiment may be an embodiment for canceling all notifications of purchased items. If the user does not wish to cancel the notification message related to the service when canceling the general service, the main service is canceled using the attribute value 'KeepSubscription' as shown in Table 22C. However, the user does not have to cancel the notification message provided in association with the main service.

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

  FIG. 16 shows a CBMS-based ESG data model mapped to the OMA-based ESG data model of FIG. 9, and shows the elements of the ESG data model described in FIG. Referring to FIG. 16, it can be seen that 'NotificationComponentType' 1603 is newly defined to indicate an acquisition fragment for the notification message in ComponentCharacteristic.

  Although the present invention has been described in detail with reference to specific embodiments, it will be apparent to those skilled in the art that various modifications can be made without departing from the scope and spirit of the invention. The scope of the present invention should not be limited to the above-described embodiments, but should be defined within the scope of the appended claims and their equivalents.

It is a figure which shows the system for transmitting a service guide to the mobile terminal in the mobile broadcast system by the 1st Embodiment of this invention. It is a figure which shows the notification architecture in the mobile broadcast system by the 1st Embodiment of this invention. 1 is a diagram illustrating an architecture for service provision in a mobile broadcast system according to a first embodiment of the present invention; FIG. 1 is a block diagram illustrating an architecture for transmitting a notification message in a mobile broadcast system according to a first embodiment of the present invention. FIG. It is a figure which shows detailed embodiment of the service guide containing the notification value in the mobile broadcast system by the 1st Embodiment of this invention. It is a figure which shows detailed embodiment of the service guide containing the notification value in the mobile broadcast system by the 1st Embodiment of this invention. It is a figure which shows detailed embodiment of the service guide containing the notification value in the mobile broadcast system by the 1st Embodiment of this invention. It is a figure which shows detailed embodiment of the service guide containing the notification value in the mobile broadcast system by the 1st Embodiment of this invention. 2 is a flowchart illustrating subscription to a notification message through a bidirectional channel in the mobile broadcast system according to the first embodiment of the present invention. It is a figure which shows the generation | occurrence | production and request | requirement process of the notification event in the mobile broadcast system by the 1st Embodiment of this invention. 5 is a flowchart illustrating a process of transmitting a notification message to a terminal after the NTDA 202 receives a transmission request for the notification message from the NTG 203; It is a figure which shows an example of the access fragment in the mobile broadcast system by the 1st Embodiment of this invention. It is a figure which shows the access type in the access fragment in the mobile broadcast system by the 1st Embodiment of this invention. It is a figure which shows the example screen of a user terminal through the service guide reception method in the mobile broadcast system by the 1st Embodiment of this invention. FIG. 3 is a diagram illustrating a CBMS-based electronic service guide (ESG) transmission architecture in a mobile broadcast system according to a second embodiment of the present invention. FIG. 6 is a diagram illustrating a configuration of a CBMS network entity for transmitting a notification message in a mobile broadcast system according to a second embodiment of the present invention. FIG. 6 is a diagram illustrating a CBMS-based service purchase architecture in a mobile broadcast system according to a second embodiment of the present invention. FIG. 6 is a diagram illustrating signaling between network entities in a mobile broadcast system according to a second embodiment of the present invention. FIG. 5 is a diagram illustrating a CBMS-based ESG data model fragment in a mobile broadcast system according to a second embodiment of the present invention. FIG. 5 is a diagram illustrating a CBMS-based ESG data model fragment in a mobile broadcast system according to a second embodiment of the present invention. FIG. 5 is a diagram illustrating a CBMS-based ESG data model fragment in a mobile broadcast system according to a second embodiment of the present invention. FIG. 5 is a diagram illustrating a CBMS-based ESG data model fragment in a mobile broadcast system according to a second embodiment of the present invention. FIG. 6 is a diagram illustrating a CBMS-based ESG data model in a mobile broadcast system according to a second embodiment of the present invention.

Explanation of symbols

701 Notification event generation / reception step 702 Notification eye message creation step 703 Broadcast channel or bidirectional channel determination step 711 Target session address confirmation step 712, 722 Backend interface message creation step 713, 723 Transmission request step 721 Target user address confirmation step

Claims (27)

A method for providing a notification message at a transmitter of a mobile broadcast system that supports a bi-directional channel, comprising:
(A) When a notification event occurs, an entity that manages the subscription information of the terminal generates a notification message, and uses the generated notification message to include at least one target address based on the subscription information of the terminal Generating a transmission request message;
(B) an entity that transmits a notification message determines a channel for transmitting the notification message to a corresponding terminal based on the target address, and transmits the notification message through the determined channel;
A method comprising the steps of: The step (b)
Checking the address type of the terminal based on the target address when the notification message is transmitted using a bidirectional channel;
Transmitting the notification message to the terminal via the bidirectional channel according to the address type;
The method of claim 1, comprising: The step (b)
Confirming a target session address for the broadcast channel based on the target address when the notification message is transmitted using a broadcast channel;
Transmitting the notification message to the terminal via the broadcast channel according to the target session address;
The method of claim 1, comprising: An entity that manages the subscription information,
Receiving a message requesting subscription or purchase of a notification message;
Processing the subscription or purchase request message and storing subscriber information of the terminal;
The method of claim 1, further comprising: An entity that manages the subscription information,
Receiving a service specific notification message subscription or purchase request message from the terminal;
Processing the subscription or purchase request message and storing the corresponding service and subscriber information of the terminal;
The method of claim 1, further comprising: An entity that manages the subscription information,
Receiving a message requesting release of notification messages for all services;
Canceling transmission of all service notification messages to the terminal;
The method of claim 1, further comprising: An entity that manages the subscription information,
Receiving a message requesting release of the service specific notification message;
Canceling transmission of the notification message of the service requested to be canceled;
The method of claim 1, further comprising: The target address is
For each terminal, channel information for transmission of notification messages,
An address type based on the transmission channel;
The method of claim 1, comprising: A transmitter in a mobile broadcast system that supports a bi-directional channel, comprising:
Manages the subscription information of the terminal, generates a notification message when a notification event occurs, and uses the generated notification message to generate at least one transmission request message including a target address based on the subscription information of the terminal The entity to generate,
An entity for determining a channel to be transmitted to the terminal based on the target address, and transmitting the notification message through the determined channel;
A transmitter comprising: The entity transmitting the notification message is:
When the notification message is transmitted using a bidirectional channel, the terminal confirms the address type of the terminal based on the target address, and sends the notification message to the terminal via the bidirectional channel according to the address type. The transmitter according to claim 9, which transmits the transmitter. The entity transmitting the notification message is:
When the notification message is transmitted using the broadcast channel, a target session address for the broadcast channel is confirmed based on the target address, and the notification message is transmitted through the broadcast channel according to the target session address. The transmitter according to claim 9, wherein the transmitter is transmitted to a terminal. The entity that generates the transmission request message is:
The transmitter of claim 9, wherein a message requesting subscription or purchase of a notification message is received from the terminal, the subscription or purchase request message is processed, and subscriber information of the terminal is stored. The entity that generates the transmission request message is:
10. The service specific notification message subscription or purchase request message is received from the terminal, the subscription or purchase request message is processed, and the corresponding service and subscriber information of the terminal are stored. Transmitter. The entity that generates the transmission request message is:
10. The transmitter according to claim 9, wherein when a message requesting cancellation of all service notification messages is received from a specific terminal, transmission of all service notification messages to the terminal is canceled. The entity that generates the transmission request message is:
The transmitter according to claim 9, wherein when a message requesting cancellation of a service specific notification message is received from the terminal, the transmission of the notification message of the service requested to be canceled is canceled.   The transmitter of claim 9, wherein the target address includes channel information for transmitting a notification message and an address type based on the transmission channel for each terminal.   The transmitter according to claim 9, wherein the entity that generates the transmission request message is a notification generator (NTG), and the second means is a notification distributor / adapter (NTDA). A method for receiving a notification message at a terminal of a mobile broadcast system that supports a bidirectional channel, comprising:
Confirming the notification content from the service guide, checking service subscription / purchase information, and transmitting a subscription request message of a notification message including reception channel information of the notification message to an entity managing subscription information of the terminal;
Receiving a response message including authentication information from an entity that manages the subscription information;
Receiving a notification message transmitted according to the transmission channel information after completion of the authentication;
A method comprising the steps of: The subscription request message of the notification message is:
Service identification information;
Subscription and purchase information for notification messages for the service;
The method of claim 18, comprising:   The method of claim 18, further comprising: transmitting a notification request cancellation message for all services to an entity managing the subscription information.   The method of claim 18, further comprising: transmitting a message requesting cancellation of a service specific notification message to an entity that manages the subscription information. A terminal in a mobile broadcast system that supports a bidirectional channel,
Confirm the notification contents from the service guide, check the service subscription / purchase information, and transmit the subscription request message of the notification message including the reception channel information of the notification message to the entity managing the subscriber information of the terminal, and respond accordingly A first entity for receiving authentication information;
An entity for receiving a notification message transmitted according to the transmission channel information after completion of the authentication;
A terminal comprising:   The terminal of claim 22, wherein the subscription request message of the notification message includes service identification information and subscription and purchase information of the notification message for the service.   The terminal of claim 22, wherein the first entity transmits a notification request cancellation message for all services to an entity that manages subscription information.   The terminal of claim 22, wherein the first entity transmits a message requesting cancellation of a service specific notification message to an entity that manages subscription information. A method for providing a notification message in a mobile broadcast system that supports a bi-directional channel, comprising:
A terminal confirming notification contents from a service guide, inspecting service subscription / purchase information, and transmitting a subscription request message of a notification message including reception channel information of the notification message to a transmitter managing subscription information of the terminal; ,
The transmitter performs authentication according to the subscription request message, stores subscription information of the terminal, and transmits a notification message of a corresponding service based on the channel information when a notification event occurs;
A method comprising the steps of: A mobile broadcast system that supports bidirectional channels,
A terminal for confirming notification contents from a service guide, inspecting service subscription / purchase information, and transmitting a subscription request message of a notification message including reception channel information of the notification message to a transmitter for managing subscription information of the terminal;
A transmitter for storing subscription information of the terminal according to the subscription request message, and transmitting a notification message of a corresponding service to the terminal based on the channel information when a notification event occurs;
A mobile broadcast system comprising:

Images