RU2371879C1 - Device and method for supplying content of service control and information on notification event in mobile broadcasting system - Google Patents

Abstract

FIELD: information technologies.

SUBSTANCE: there is proposed system and method used for providing service control for mobile broadcasting service (BCAST) in a wireless communication/broadcasting system supporting BCAST service if there is the need in providing service control in mobile broadcasting system. Service Guidance Subscription Source (SGSS) submits initial subscription and submission data and source (initial data) of obtaining and activating to the unit of Adaptation/Distribution of BCAST Services. Then the above unit forms and provides service control by using that initial data.

EFFECT: supply of content information and notification event information, on the basis of which content provider generates BCAST service control by determining information elements and attributes required for forming associated messages, and the supply of the reply which indicates whether the requirements shall be fulfilled.

28 cl, 14 dwg, 35 tbl

Description

Technical field

The present invention generally relates to an apparatus and method for transmitting a message supporting a Broadcast Service (BCAST). In particular, the present invention relates to an apparatus and method for delivering a notification message including information indicating a change in a system and service.

Description of the Related Art

Today, with the development of communication (exchange) and broadcasting technologies, broadcasting systems and mobile communication systems have evolved into systems that are capable of providing mobile broadcasting services. Discussions are continuing on mobile broadcasting systems that are capable of transmitting packet data, as well as conventional audio / video broadcasting services, over the broadcasting channel.

The term "mobile broadcasting" refers to technologies for providing broadcasting services through mobile terminals that are capable of receiving mobile broadcasting, such as mobile phones, laptop computers (laptops) and personal digital assistants (PDAs). In order to receive a broadcast service, the mobile terminal must first be able to detect the provided service, and the subscriber of the mobile terminal must subscribe to the broadcast service so that he / she can receive the services provided. In addition, in order to receive broadcast services, the mobile terminal must receive a variety of control information provided by the broadcast system. In addition, a system supporting broadcasting services must transmit these services. If a broadcast service and a variety of information associated with them are provided, the mobile terminal receives service control information and broadcast service data. Thus, the user can view broadcast information.

The Open Mobile Alliance (OMA), a group studying standards for the interaction between individual mobile solutions, mainly guides the establishment of various applicable standards for mobile games, Internet services, etc. Among the OMA working groups, the OMA Browser and Content (BAC) Mobile Broadcasting Sub-Working Group (BCAST) is exploring technologies for providing broadcast services using mobile terminals.

In the mobile broadcasting system, according to the discussions in OMA, the mobile terminal for receiving the broadcasting service receives the service control information (UE, SG) including the service description information, the charging information for the service and information on the method of receiving the service, and receives the corresponding service, using service management information.

However, one or more pieces of service management information may change at any time. Therefore, each time, for example, a particular service is changed, the service control information for the corresponding service must be retransmitted. In addition, mobile broadcasting is characterized in that, in view of the emergence of a new mobile terminal, the service management information for the mobile broadcasting service is retransmitted even though there is no change in the management of the services. The emergence of a new mobile terminal refers to the presence of a new mobile terminal that previously did not accept the service, but now accepts the service. For example, if there is a new user who wants to receive broadcasting services by turning on the power of the mobile terminal, or if there is a mobile terminal that needs to receive new service control information due to the movement of his user, the new mobile terminal must accept service control regardless of the mobile terminals that have already received mobile broadcast information.

In a mobile broadcasting system, it is very important to reliably deliver and respond to service management information. Therefore, there is a need for a system and method for delivering content information and notification event information, on the basis of which the content provider generates BCAST service management, determining the information elements and attributes necessary for generating the associated messages, and sending a response indicating whether to fulfill the requirements.

SUMMARY OF THE INVENTION

Accordingly, embodiments of the present invention are provided in order to substantially solve at least the aforementioned problems and / or disadvantages and provide at least the advantages described below. Embodiments of the present invention provide an apparatus and method for delivering content information and notification events to generate service management information (guidance) in a mobile broadcast system.

Embodiments of the present invention provide an apparatus and method for reliably transmitting service control information in a mobile broadcast system.

Embodiments of the present invention also provide an apparatus and method for receiving service control information and transmitting a response signal thereto in a mobile broadcast system.

Embodiments of the present invention further provide an apparatus and method for generating a message necessary for transmitting service control information in a mobile broadcast system.

Embodiments of the present invention further provide an apparatus and method for detecting an information element necessary for generating messages related to the delivery of said service control and notification event.

Embodiments of the present invention further provide an apparatus and method for transmitting a response to received service control information and a notification event.

According to one aspect of embodiments of the present invention, there is provided a method for providing service management for a mobile broadcast service (BCAST) in a wireless communication / broadcasting system supporting the BCAST service, comprising the steps of detecting a need to provide service control in a mobile broadcast system and, if there is a need for providing service management in the mobile broadcast system, Source management (source data) Service Management Subscriptions (SGSS) to deliver the source (source subscription and provisioning data and the source (source data) of the acquisition and activation to the BCAST Services Adaptation / Distribution unit, and the BCAST Services Adaptation / Distribution unit management to generate and provide service management using these sources (source data).

According to another aspect of embodiments of the present invention, there is provided a system for providing service management for a mobile broadcasting service (BCAST) in a wireless communication / broadcasting system supporting the BCAST service, comprising a Service Management Subscription Source (SGSS) for delivering a subscription source and providing and an acquisition source and activation to the BCAST Services Adaptation / Distribution unit, and the BCAST Services Adaptation / Distribution Unit to generate service management using these sources and provide subscriber management services.

According to another aspect of embodiments of the present invention, there is provided a method for providing a notification message for a mobile broadcast service (BCAST) in a wireless communication / broadcast system supporting the BCAST service, comprising the steps of determining through the Notification Generation (NTG) function block in the BCAST Subscription Management (BSM) block whether there is a notification of a notification event requesting the formation of a notification message, and after detecting a notification event - NTG provides for the formation of community notification according to the notification event and delivery of the notification to the Notification Distribution Adaptation (NTDA) function block in the BCAST Services Distribution / Adaptation (BSD / A) block, thereby providing a notification message to subscribers.

According to yet another aspect of embodiments of the present invention, there is provided a system for providing a notification message for a mobile broadcast service (BCAST) in a wireless communication / broadcast system supporting the BCAST service, comprising a Notification Event (NTE) function (function block) for detecting a change in service, provided to the user from the (block) Use of BCAST Services (BSA) supporting the BCAST service, and providing a notification of a notification event to notify of the occurrence , and the Notification Generation (NTG) function block in the BCAST Subscription Management (BSM) block for, after receiving the notification of the notification event, generating the notification message and transmitting the notification message to the subscriber.

Brief Description of the Drawings

The above and other objects, features and advantages of embodiments of the present invention will become more apparent from the following detailed description when considered in conjunction with the accompanying drawings, in which:

1 is a block diagram illustrating an example architecture of a mobile broadcast system that can deliver service control information to a mobile terminal according to an embodiment of the present invention;

2 is a block diagram illustrating exemplary structures of notification interfaces, as defined in OAST BCAST, for providing notification messages in a mobile broadcast system according to an embodiment of the present invention;

3 is a signaling diagram illustrating an exemplary message flow between logical entities to provide service control in a mobile broadcast system according to an embodiment of the present invention;

4 is a signaling diagram illustrating an exemplary message flow between logical entities to provide a notification message in a mobile broadcast system according to an embodiment of the present invention;

5 is a block diagram illustrating an example data model for service management for generating service management in OAST BCAST according to an embodiment of the present invention;

6 is a block diagram illustrating an exemplary protocol stack that can be used to transmit a notification event in an NT-3 interface according to an embodiment of the present invention;

7 is a signaling diagram illustrating an exemplary NT-3 message transmission process in OAST BCAST according to an embodiment of the present invention;

FIG. 8 is a block diagram illustrating an exemplary BCAST architecture proposed in OAST BCAST for receiving information related to grant generation according to an embodiment of the present invention;

FIG. 9 illustrates an example flowchart of FIG. 8;

10 is a block diagram illustrating an example SG-3 transmission protocol interface stack in BCAST OMA according to an embodiment of the present invention;

11 is a signaling diagram illustrating an exemplary SG-3 message delivery in OAST BCAST according to an embodiment of the present invention;

12 is a flowchart illustrating an example protocol stack used to deliver a request message to provide a service control source (s) or notification event on an SG-3 or NT-3 output interface according to an embodiment of the present invention;

13 is a signaling diagram illustrating an exemplary delivery of a service control source between SGAS and SGSS over SG-3 according to an embodiment of the present invention; and

14 is a signaling diagram illustrating an example delivery of a notification event between NTE and NTG over NT-3 according to an embodiment of the present invention.

It is understood that in all the drawings, like reference numerals refer to like parts, components and structures.

Detailed Description of Exemplary Embodiments

Embodiments of the present invention are described in detail below with reference to the accompanying drawings. In the following description, a detailed description of known functions and configurations included therein is omitted for clarity and meaningfulness.

In the following detailed description, exemplary embodiments of the present invention are illustrated and described to achieve the above and other objects. The names of the entities defined in the 3rd Generation Partnership Project (3GPP), which is the standard for asynchronous mobile communications, or BCAST of the Open Mobile Alliance (OMA), which is the application standard for mobile terminals, will be used for convenience, moreover, the standards and names are not intended to limit the essence of the embodiments of the present invention, and the present invention can be applied to any number of systems having the same or similar technical foundations. A detailed description of embodiments of the present invention is made below with reference to BCAST OMA, which is one of several mobile broadcast standards, but the embodiments of the present invention are not limited to them.

1 is a block diagram illustrating an example architecture of a mobile broadcasting system that can deliver (information) service control to a mobile terminal according to an embodiment of the present invention. Table 1 and table 2 below show as examples the interfaces used between the elements (logical entities) of FIG. 1.

Table 1 Title Description SG1 (103) Server-server exchanges for the delivery of content attributes such as description information, location information, capabilities of the target terminal, target user profile, etc., either in the form of BCAST service control fragments (information) or in a native format. SG2 (106) Server-to-server exchanges for delivering BCAST service attributes, such as service / content description information, scheduling information, location information, target terminal capabilities, target user profile, and the like, in the form of BCAST service control fragments. SG-B1 (116) Server-to-server exchanges either for delivering BDS-specific attributes from the BDS to the BCAST service management adaptation function block to facilitate adaptation of service management to a specific BDS, or for BDS-specific adaptation and distribution. SG4 (112) Server-to-server exchanges for delivery information provision, purchase information, subscription information, activation information in the form of fragments (information) of BCAST service management. SG5 (117) Delivery of BCAST service management information (information) through an IP broadcast channel. SG6 (118) Delivery of BCAST service management through an interaction channel. Interactive access to extract (information) service management or additional information related to service management, for example, via HTTP, SMS or MMS.

table 2 Title Description X-1 (124) Checkpoint between BDS Service Distribution and BDS. X-2 (125) A reference point between the BDS Service Distribution and the Interaction Network. X-3 (126) The reference point between the BDS and the Terminal. X-4 (127) Checkpoint between the Distribution of BDS Services and the Terminal on the Broadcast Channel. X-5 (128) Checkpoint between the BDS Service Distribution and the Terminal on the Connectivity Channel. X-6 (129) Checkpoint between the Network of Interactions and the Terminal.

With reference to FIG. 1, a Content Creation Unit (SC (CC), or content provider) is a Broadcast Service Provider (BCAST), and the BCAST service may include a conventional audio / video broadcast service, a music / data file download service, and so on. .d. The Content Creation Unit 101, using the Service Management Content Creation Source (SGCCS) Source 102 (source data), delivers the content information needed to create BCAST service management, mobile terminal capabilities information, user profiles and time-related content information to the Source of the Service Management Application (SGAS) 105 in block 104 of the Use of BCAST Services (BSA) through the interface 103 SG1 from table 1.

The BCAST Service Use block 104 processes the BCAST service data provided from the Content Creation block 101 in a form suitable for the BCAST network, thereby generating BCAST service data. In addition, BCAST Services Use Block 104 generates standardized metadata that are necessary for managing mobile broadcasts. SGAS 105 delivers various sources (source data) needed to formulate service management, such as service / content information, scheduling information, and location information, including information transmitted from SGCCS 102, to a Service Control Generation (Information) function block 109 (SG- G) in block 108 Distribution / Adaptation of Services BCAST (BSD / A) through the interface 106 SG2.

The BCAST Services Adaptation / Distribution unit 108 has a unidirectional channel setting function through which it will transmit BCAST services data provided from the BCAST Services Use block 104, a BCAST service transmission scheduling determination function, and a mobile broadcast management information generation function. The BCAST Services Adaptation / Distribution Unit 108 is connected to the Broadcast Distribution System (BDS) 122, which is the BCAST service data network, and the Interaction Network 123, which supports interactive communication.

Service Management information generated by SG-G 109 is delivered to Terminal 119 via SG distribution function block 110 (SG-D) and SG5 interface 117. If the service control is delivered via a BDS 122 or Interaction Network 123, or if there is a need for coordination with the corresponding system or network, the service control information generated from the SG-G 109 is matched in the SG Adaptation function block 111 (SG-A ) and then delivered via SG-D 110 or delivered to BDS Service Distribution unit 121 via SG-B1 interface 116.

The BCAST Subscription Management Unit (BSM) 113 controls the subscription information and service provisioning information for receiving the BCAST service, and device information for the terminal receiving the BCAST service. The source (source data) of Service Management Subscriptions (SGSS) 114 in BCAST Subscription Management unit 113 delivers such source data as source and acquisition information related to generating service management information, subscription, provision and activation to SG-G 109, which generates (information) service management through the interface 112 SG4.

The BDS Service Distribution Unit 121 serves to distribute all received BCAST services through a broadcast channel or an interaction channel and is an entity that may or may not exist according to type BDS 122. BDS 122 is a network that transmits BCAST service, and may be a broadcast network, such as a Digital Video Broadcasting network for portable devices (DVB-H) based on 3GPP Multicast Unicast and Multicast Broadcast Services (MBMS) and 3GPP2 based Unicast and Multicast Broadcast Multimedia Information Services Missions (BCMCS). The Interaction network 123 transmits BCAST data on a point-to-point basis, or interactively exchanges control information and additional information related to receiving the BCAST service, and may be, for example, an existing cellular network.

Terminal 119 is a terminal that is capable of receiving BCAST services, and can be connected to a cellular communication network according to the capabilities of the terminal. The terminal 119, including the Service Management Client (information) (SG-C) 120, receives the service control information (information) transmitted via the SG5 interface 117, or receives a notification message transmitted via the SG6 interface 118, for example, via the air interface 130, and thus performing the appropriate operation to receive the BCAST service.

Tables 3-5 below provide by way of example definitions of the functions of the core elements (logical entities) shown in FIG. 1 in the BCAST OMA service standard.

Table 3 Title Description Content Creation (101) When Creating Content, a Service Management Content Creation Source (SGCCS) can provide content and attributes, such as content description information, target terminal capabilities, target user profile, content synchronization information, etc., and send them via SG1 in the form of standardized control fragments BCAST services or in native format. Using BCAST Services (104) In the BCAST Services Application, the BCAST Services Management Application Source (SGAS) provides service / content description information, scheduling information, location information, target terminal capabilities, target user profile, and the like. and sends them over SG2 in the form of standardized BCAST Service Management fragments. BCAST Subscription Management (113) In BCAST Subscription Management, the Service Management Description Source (SGSS) provides provision information, acquisition information, subscription information, activation information, and the like. and sends them via SG4 in the form of fragments (information) of the Service Management.

Table 4 Title Description Service Management Generation (SG-G) (109) The Service Control Information Generation Module (SG-G) in the network is responsible for receiving Service Control fragments from various sources, such as SGCCS, SGAS and SGSS, over the SG2 and SG4 interfaces. The SG-G collects these fragments, such as service and content access information, according to a standardized scheme and generates a Service Management, which sends to the Service Management Distribution (block) (SG-D) for transmission. Before transmission, it is optionally adapted in the Service Management Adaptation (SG-A) 111 function block to suit a particular BDS. Service Management Client Function Block (SG-C) (120) The Service Management Client Function Block (SG-C) in the terminal is responsible for receiving the Service Management information from the underlying BDS and ensuring the accessibility of service management to the mobile terminal. SG-C receives specific service management information. He can filter it to match terminal specific criteria (e.g. location, user profile, terminal capabilities and etc.), or he simply receives all the available Service Management information. Typically, the user can view the Service Management information in a menu, list, or tabular format. SG-C can send a request to the network via SG6 to obtain specific Service Management information or all Service Management information.

Table 5 Title Description Service Management Distribution
(SG-D) (110) The SG-D generates an IP stream for transmitting (information) service control over the SG5 interface and the broadcast channel to SG-C. Before transmission, the SG-G may send the service control to the service control adaptation function block (SG-A) to adapt the service control information (information) to the specific BDS according to the BDS attributes sent by the BDS service distribution block to SG-B1. Adaptation may lead to modification (information) of service management. It should be noted that, for adaptation purposes, SG-A can also send BCAST service control attributes or BCAST service control fragments on SG-B1 to the distribution unit BDS services to adapt. This adaptation within the BDS service distribution block lies outside the scope of BCAST. The SG-D may also receive a request for service control information and send the requested service control information to the terminal directly through the interaction channel. The SG-D may also filter service control information from the SG-G based on a predefined end-user profile. The SG-D may also send the service control to the BDS, which modifies the service control (for example, by adding BDS-specific information) and also distributes the service control to the SG-C in a BDS-specific manner.

FIG. 2 illustrates a block diagram illustrating exemplary notification interface structures, as defined in OAST BCAST, for issuing notification messages in a mobile broadcast system according to an embodiment of the present invention.

With reference to FIG. 2, a Content Creation (CC) unit 201 is a BCAST service provider, and the BCAST service may include conventional audio / video broadcasting services, a music / data file download service, and so on. When there is a problem in providing the BCAST service or when there is a change in the BCAST service, the Content Creation unit 201 notifies the Notification Event (NTE) Function Block 202-1 located in the BCAST Services Use Block (BSA) 202 of the change.

The BCAST Services Use unit 202 processes the BCAST services data provided from the Content Creation unit 201 into a form corresponding to the BCAST network, thereby creating BCAST service data, and generates standardized metadata that are necessary for managing the mobile broadcast. In addition, the BCAST Services Use Block 202 notifies the Notification Generation (NTG) function block 204-1 located in the BCAST Subscription Management block 204 (BSM) of changes to the BCAST service provided from the Content Creation block 201.

The BCAST Services Distribution / Adaptation Unit 203 (BSD / A) is responsible for setting up a unidirectional channel through which it will transmit BCAST services data provided from the BCAST Services Use unit 202, determining the BCAST service transmission scheduling and forming the mobile broadcast control, and is connected to the system 206 Broadcast Distribution (BDS) for service delivery by BCAST and Network 207 interworking, supporting interactive exchange. In addition, the BCAST Services Adaptation / Distribution unit 203 includes a Notification Adaptation and Distribution (NTDA) function block 203-1 and receives a notification message transmitted from the BCAST Subscription Management unit 204 and transmits a notification message to one or more users via BDS 206 or a network of 207 interactions.

The BCAST Subscription Management unit 204 controls subscription information for receiving the BCAST service, service provisioning information, and device information for the device receiving the BCAST service. In particular, the BCAST Subscription Management unit 204 has a Notification Generation (NTG) function block 204-1 and generates a notification message by receiving information regarding the notification event from the Content Creation unit 201 or the BDS 206, or generates a notification message for the BCAST service event.

The BDS Service Distribution function block 205 serves to distribute all received BCAST services through a broadcast channel or an interaction channel and is an entity that may or may not exist according to type BDS 206.

BDS 206 is a network that transmits a BCAST service, and may be, for example, DVB-H based on 3GPP MBMS and based on 3GPP2 BCMCS. In addition, when there is a change in the transmission of a particular BCAST service, the BDS 206 transmits a notification event indicating the change to the BCAST Services Adaptation / Distribution unit 203 via the X-1 interface 231 or the NT-B1 interface 224 if the BDS Service Distribution function block 205 exists .

The interaction network 207 transmits the BCAST service on a point-to-point basis (mode) or interactively exchanges control information and additional information related to the reception of the BCAST service, and may, for example, be an existing cellular communication network.

Terminal 208 is a terminal that is capable of receiving BCAST services, and may be connected to a cellular communications network according to the capabilities of the terminal. For example, terminal 208 includes a terminal, that is, a cellular telephone that is capable of connecting to a cellular communications network. Terminal 208 performs the corresponding operation by receiving a notification message transmitted via the NT-5 interface 225 by the Alert Client (NTC) function block 208-1, or performs the corresponding operation by receiving a notification message transmitted through the NT-6 interface 226.

The following is a description of the interfaces between the key logical entities of FIG. 2.

The NT-1 interface 221 is the interface between the Notification Events function block 202-1 located in the BCAST Services Use block 202 and the Content Creation block 201 and is used to deliver the notification event that occurs in the Content Creation block 201 to the Event function block 202-1 Notifications.

NT-3 interface 222 is the interface between the Notification Events function block 202-1 located in the BCAST Services Use block 202 and the Notification Generation function block 204-1 in the BCAST Subscription Management block 204 and delivers the information necessary to generate a notification event or notification message so that the Notification Generation function block 204-1 can generate a notification message.

NT-4 interface 223 is the interface between the Notification Generation function block 204-1 located in the BCAST Subscription Management block 204 and the Notification Distribution Adaptation function block 203-1 in the BCAST Services Adaptation / Distribution block 203 and is used to transmit the notification generated in the functional Notification Generation block 204-1, to the Notification Distribution Adaptation function block 203-1 so that it is transmitted through the BDS 206 or the interaction network 207, or the delivery of the notification event taking place in the BDS 206, from the Notification Distribution Adaptation function block 203-1 to the Notification Generation function block 204-1.

The NT-5 interface 225 is an interface used when a notification message sent from the BCAST Service Adaptation / Distribution Notification Distribution Adaptation function block 203-1 is directly transmitted to the Terminal 208 via the broadcast channel. The NT-5 interface 225 is used to transmit notification to one or more terminals.

The NT-6 interface 226 is the interface used when the notification message sent from the BCAST Service Adaptation / Distribution Notification Distribution Adaptation function block 203-1 is directly transmitted to the Terminal 208 through a dedicated channel with the Terminal 208 through the interaction network 207 or through the channel Broadcasts provided in a network of 207 interactions. The NT-6 interface 226 is used to transmit notification to one or more terminals.

The NT-B1 interface 224 is the interface between the BCAST Services Adaptation / Distribution unit 203 and the BDS Service Distribution function block 205 and is used to establish the transmission path (s) to be used in the BDS 206 through the BCAST Service Adaptation / Distribution unit 203 or the receive path notification events taking place in the BDS 206.

The X-1 interface 231 is the interface between the BCAST Services Adaptation / Distribution unit 203 and the BDS 206 and is used to establish the transmission path to be used in the BDS 206 by the BCAST Services Adaptation / Distribution unit 203, or the reception path of the notification event occurring in BDS 206 when the BDS Service Distribution Function block 205 does not exist. When a BDS Service Distribution Function block 205 exists, an X-1 interface 231 is used as an interface between the BDS 206 and the BDS Service Distribution function block 205 to deliver a notification event taking place in the BDS 206.

The X-2 interface 232 is the interface between the BCAST Services Adaptation / Distribution unit 203 and the interaction network 207 and is used to establish the transmission path to be used in the interaction network 207 by the BCAST Services Adaptation / Distribution unit 203 when the BDS Service Distribution function block 205 exist. When a BDS Service Distribution function block 205 exists, an X-2 interface 232 is used as the interface between the BDS 206 and the interaction network 207 to establish a unidirectional channel through which the notification message will be transmitted from the interaction network 207.

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

The X-4 interface 234 is a broadcast channel interface between the BDS Service Distribution function block 205 and the Terminal 208.

The X-5 interface 235 is the interface of the communication channel between the BDS Service Distribution function block 205 and the Terminal 208.

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

The Notification Events function block 202-1 delivers the information necessary for generating the notification message to the Notification Generation function block 204-1 and, after recognizing the occurrence of the required notification event, delivers information regarding the notification event to the Notification Generation function block 204-1. The Notification Generation function block 204-1 generates a notification message by receiving a notification event and information necessary for generating a notification message from the Notification Event function block 202-1, or generates a notification message using the notification event BDS 206 received through the function block 203-1 Notification Distribution Adaptations, and transmits the generated notification message to the Notification Distribution Adaptation function block 203-1. A notification message can be generated: (i) when there is a need to notify of another start of the service, (ii) when there is a need to transfer new mobile broadcast control after receiving a notification indicating a change in the service information from the Content creation unit 201, and (iii) when a specific event occurs in BDS 206 (i.e. an emergency event).

The Notification Distribution Adaptation function block 203-1 is used to transmit a notification message via NT-5 225 or NT-6 226 and after receiving a notification from the BDS 206 indicating a change in a particular mobile broadcast service, for example, indicating a data rate setting based on a wireless network environment or the impossibility of the service, is used to deliver the corresponding notification event to the function block 204-1 Generate Notifications via NT-4 223.

3 is a signaling diagram illustrating an exemplary message flow between logical entities to provide service control in a mobile broadcast system according to an embodiment of the present invention. Here, reference numeral 301 denotes SGCCS 102 in figure 1, reference numeral 302 indicates SGAS 105 in figure 1, reference numeral 303 indicates SGSS 114 in figure 1, and reference numeral 304 denotes SG-G / D / A 109, 110, and 111 in FIG.

With reference to FIG. 3, at step 311, SGCCS 301 delivers content information and attributes associated with the BCAST service to SGAS 302. At step 312, SGAS 302 delivers content / service broadcast information and attributes of SG-G / D / A 304 according to the format BCAST using the attributes provided by SGCCS 301. At step 313, the SG-G / D / A 304 sends a request for grant information to SGSS 303. At step 314, the SGSS 303 provides grant information to SG-G / D / A 304. At step 315 SG-G / D / A 304 generates a service management (SG) based on this information provided.

4 is a signaling diagram illustrating an exemplary message flow between logical entities to provide notification in a mobile broadcast system according to an embodiment of the present invention. Here, reference numeral 401 denotes the Notification Events (NTE) function block 202-1 in the BCAST Services Use block 202 of FIG. 2, reference numeral 402 denotes the Notification Generation (NTG) function block 204-1 in the BCAST Subscription Management block 204, and the reference position 403 denotes the Notification Distribution Adaptation (NTDA) function block 203-1 in the BCAST Services Adaptation / Distribution block 203.

With reference to FIG. 4, at step 411 and / or 412, a notification event that occurs in NTE 401 and NTDA 403 is delivered to NTG 402, or a notification event occurs in NTG 402 or BDS 206. If a notification event occurs in Block 201 Content or BSA 202, NTE 401 delivers an Event Notification to NTG 402 to BCAST Subscription Management unit 204 via NT-3 interface 222 in step 411. If a notification event is generated from BCAST or BDS 206 Service Adaptation / Distribution unit 203, NTDA 403 delivers an event notifications to the NTG 402 via the NT-4 interface 223 at step 412. At step 413, the notification event can t be spontaneously formed in the BSM 204 and then delivered to the NTG 402.

As described above, the NTG 402 is provided by the notification event itself, either via the NT-3 interface 222 or the NT-4 interface 223. In step 414, the NTG 402 generates a notification message according to the notification event, and then delivers the notification message to the NTDA 403 via the NT-4 interface 223 in step 415.

Before a detailed description will be given of embodiments of the present invention, a message diagram table used in the present invention is described below for a better understanding of the invention. The term "Name" means the names of the elements and attributes that make up the corresponding message. The term “Type” indicates whether the corresponding name matches the type of element or attribute. Each element has the values E1, E2, E3 and E4. The term E1 indicates the top element for the entire message, E2 indicates the sub-element E1, E3 indicates the sub-element E2, and E4 indicates the sub-element E3. The attribute is indicated as "A", and A indicates the attribute of the corresponding element. For example, A under E1 indicates an attribute E1.

The term “Category” is used to indicate whether the corresponding element or attribute is required, and has a value of M if the value is mandatory and a value of O if the value is optional. The term "Number of elements" indicates the relationship between the elements and has the meanings "0", "0..1", "1", "0..n" and "1..n", where "0" indicates an optional relationship, " 1 "denotes a required relationship, and" n "denotes the possibility of the presence of multiple values. For example, "0..n" indicates the possibility that there is no corresponding element, or that there are n corresponding elements. The term "Description" defines the value of the corresponding element or attribute. The term "data type" indicates the data type of the corresponding element or attribute. Therefore, the message format can be shown as illustrated below in table 6.

Table 6 Title Type of Category Amount of elements Description Data type

Although several information elements necessary for generating a service control request / response (information) and notification events according to an exemplary embodiment of the present invention are described below, messages proposed in embodiments of the present invention will not necessarily include all information elements and may include some or all of the information elements according to the intentions or needs of the designer.

6 is a block diagram illustrating an example protocol stack that can be used to transmit a notification event on an NT-3 interface according to an embodiment of the present invention. A message delivered via the NT-3 interface can be delivered in XML Form or as text. The corresponding message is described in more detail below with reference to Fig.7.

A message over the NT-3 interface is transmitted using the Internet Protocol (IP), Transmission Control Protocol (TCP), and / or Hypertext Transfer Protocol (HTTP), and NTE at the BSA requests the generation of a notification message by sending a notification event message to NTG in the BSM via HTTP POST (Send HTTP). After receiving a message from NTE, NTG can send the results of the notification generation along with the HTTP RESPONSE message (HTTP response), or it can send the result message via HTTP POST.

7 is a signaling diagram illustrating an exemplary process for transmitting a message over an NT-3 interface according to an embodiment of the present invention.

At step 703, the NTE 701 sends a request to generate a notification to the NTG 702. This message, provided at step 703, is shown below by way of example in Tables 7A-7D. In step 704, the NTG 702 generates a notification message depending on the information received from the NTE 701, and then sends a completion message to the NTE 701. If the notification message is generated and sent immediately, the NTG 702 may send a result message along with the HTTP Response message "in response to the request message provided at step 703. However, if time is required to generate the notification message, the NTG 702 may send an NTE 701 result message via NTGReqID and BSAAddress to NTGReq received at step 703 using HTTP POST during generation completion after the end of the communication session to NTE 701. Details of the result message are shown by way of example in Table 8 below.

At 704, responses to multiple requests from the NTE 701 can be sent from the NTG 702 to the NTE 701 using a single message.

Table 7A Title Type of Category Amount of elements Description Data type NTEReq E Specifies a notification event request message from NTE to NTG. Contains the following elements:
NTEId
BSAAddress. NTEId BUT M one BSA notification event identifier. Unsigned integer (32 bits) BSAAddress BUT M one The BSA address for receiving a response to this request. Any URI NotificationEvent E1 M 1..N Specifies a notification event from CC. Contains the following attributes:
NotificationType
Validity
Contains the following elements:
Name
Description
Priority
ExtensionURL
MediaInformation. NotificationType BUT M one Notification Type: If NotificationType = 0, this message is a user-oriented message, such as SP notification, multimedia message, alarm, etc.
If NotificationType = 1, this message is a terminal-oriented message, such as starting a service or downloading a file, etc. Other NotificationType values may be determined from the service provider, operators, or broadcaster targets. Whole

Table 7B Title Type of Category Amount of elements Description Data type Validity BUT ABOUT 0..1 Valid time of the Notification message fragment. If Validity is set, the notification message should expire at the specified time. Integer (32 bits) expressed as NTP time Name E2 ABOUT 0..N The name or title of the notification message, possibly in many languages. The language is expressed using the built-in XML attribute xml: lang with this element. Line Description E2 ABOUT 0..N Description of Notification Messages, possibly in many languages. The language is expressed using the built-in XML attribute xml: lang with this element. Line Priority E2 M one Determines the priority of this notification event. This information is used to generate the presentation type of the Notification Message type. Whole ExtensionURL E2 ABOUT 0..N URL containing additional information related to the notification message. Any URI

Table 7C Title Type of Category Amount of elements Description Data type Mediainformation E2 O 0..1 The multimedia information that is needed to construct multimedia notification messages. Contains the following elements:
Picture
Video
Audio Picture E3 O 0..N Determines how to get a picture and a MIME type. Contains the following elements:
Mimetype
PictureURI. Mimetype A O 0..1 Type MIME Pictures. Line Pictureuri A O 0..1 The URI that refers to the picture. Any URI Video E3 O 0..N Determines how to get the video and MIME type. Contains the following elements:
Mimetype
VideoURI. Mimetype A O 0..1 MIME type of video. Line VideoURI A O 0..1 The URI that refers to the video. Any URI

Table 7D Title Type of Category Amount of elements Description Data type Audio E3 O 0..N Determines how to get audio and MIME type. Contains the following elements:
Mimetype
AudioURI. Mimetype A O 0..1 MIME type of audio. Line AudioURI A O 0..1 URI that refers to the audio. Any URI

Table 8 Title Type of Category Amount of elements Description Data type NTERes E Specifies the response message for NTEReq. Contains the following elements: NTEId. NTEId E1 M 0..N NTEReq identifier. Contains the following attributes:
Response Unsigned integer (32 bits) Response BUT M one Sets the result of how NTERes is processed in BSM. If Response = 0, then a notification message is generated and delivered to NTD / A. If Response = 1, then the generation of the notification message fails and a retransmission is requested. Integer (8 bits)

5 is a block diagram illustrating an example data model for service management for generating service management information (information) in OAST BCAST according to an embodiment of the present invention.

The service management data model consists of Administrative group 500 to provide information to the top element of the entire service management, Provider group 510 to provide subscription and purchase information, Base group 520 to provide basic service management information such as service, content and service planning, and group 530 Access to provide access information to access the service or content. Each element is described below in more detail.

The Service Management Context 501 provides a method by which the terminal can recognize the service control, and also provides information regarding the operator for the distribution of the service control, or location information, and connection information with the Service Control Delivery Descriptor 502.

The Service Management Delivery descriptor 502 provides information regarding the delivery communication session where the Service Management Delivery Module (SGDU) is located, containing a fragment that is the minimum unit constituting the service control information, and also provides grouping information for the SGDU and information regarding the entry point for receiving the message notifications.

Fragment 521 Services, the upper combination of content included in the broadcasting service as a center for the complete management of services, provides information regarding the content of the service, genre, location of the service, etc. Fragment 522 Planning provides information about the time of each content included in the services of Streaming and Download. Content fragment 523 provides a detailed description of broadcast content, target user group, service location, and genre. Access group 530 provides access-related information to allow the user to view the service, and also provides a delivery method for the corresponding access session and session information. The Session Description fragment 532 may also be included in the Access fragment 531 of the Access group 530 and provides location information in the form of a URI so that the terminal can detect the corresponding session description information.

In addition, the Session Description fragment 532 provides address information and codec information for the multimedia content existing in the corresponding communication session. Fragment 511 The Acquisition Element provides a bundle of service, content, and time to help the user subscribe to or purchase the corresponding acquisition element. Fragment 512 of the Acquisition Data includes detailed acquisition and subscription information, such as pricing information and activation information for a service or bundle of services.

Purchase Channel Fragment 513 provides access information for subscription or purchase. The Service Management Context 501 allows the terminal to recognize (manage) service management information and provides location information or owner information based on which the terminal can take service control. The Service Management Delivery descriptor 502 provides grouping information for an entry point for receiving service control information (s) and an SGDU indicating a fragment container. A preview data unit 540 and an interaction data unit 550 can also be provided.

The Service Control information of FIG. 5 is preferably generated in SG-G 109 of FIG. 1, and the information of the Providing group 510 (hereinafter, the provision information) is preferably provided by SGCC 114 of FIG. 1. The corresponding provision information is delivered in step 314 of FIG. 3, and this information in step 314 can be delivered without a Request in step 313. However, since the information in step 313 is not necessarily required to obtain information for the provision, SGCC 114 should preferably have the appropriate service and content, or planning information. Therefore, as described in more detail below, there is a need for an SG3 interface 802 for exchanging information between SGAS 801 and SGSS 803 in FIG. 8, and service / content information and its scheduling information need to be provided from SGAS 901 to SGSS 902 through step 903, as shown in Fig.9.

10 is a flowchart illustrating an example protocol stack used to transmit information related to service management in an SG-3 interface according to an embodiment of the present invention.

A message delivered via SG-3 (for example, 802 according to FIG. 8) may be delivered in XML or text form. The corresponding message is described in more detail below with reference to Fig.11.

The SG-3 802 message is delivered using IP, TCP and / or HTTP, and the SGAS in the BSA transmits the service / content related message to the SGSS in the BSM via HTTP POST. After receiving a message from SGAS, SGSS can transmit the results of generating the provision information along with the HTTP Response message, or it can send the result message via HTTP POST.

11 is a signaling diagram illustrating an example SG-3 message transmission process according to an embodiment of the present invention. With reference to FIG. 11, a description will now be made of a process for transmitting a message on SG-3.

In step 1101, the SGAS (e.g., 901 of FIG. 9) provides service / content information and scheduling information in the service control data model, as described in FIG. 5, to the SGSS (eg, 902 of FIG. 9). Scheduling information cannot be provided as part of the delivered information, and corresponding planning can be generated in BSD / A and then issued, while SGSS 803 generates (service management information). The message provided in step 1101 is shown by way of example in table 9 below. In Table 9, the Service is accompanied by ServiceInfo information from Tables 10A-10D, Content (content) is accompanied by ContentInfo information from Tables 11A-11D, and Planning is accompanied by ScheduleInfo information from Tables 12A-12H. At step 1102, the SGSS 902 generates provisioning information for managing services with information issued from the SGAS 901, and then sends a generation complete message to the SGAS 901.

If the service control information is immediately generated and sent, the SGSS 902 may send a result message along with the HTTP Response message in response to the request message provided in step 1101. However, if time is required to generate the provision information in the service control information, the SGSS 902 may send a message result to SGAS 901 via HTTP POST using SGASProvReqId and BSAAddress during generation completion after the end of the communication session to SGSS 902. Details of the result message are shown by way of example in that blitz 13 below. At 1102, responses to multiple requests from SGAS can be sent from SGSS 902 to SGAS 901 using a single message.

Table 9 Title Type of Category Amount of elements Description Data type SGASProvReq Sets the request message for the formation of the provision section in the Service Management information. Information services, planning and content are possible values. Contains the following attributes:
SGASProvReqId.
Contains the following elements:
Service
Content
Schedule SGASProvReqId A M one The identifier SGASProvReq, which is the message for SGAS to request the generation of provision information to SGSS. Unsigned integer (32 bits) BSAAddress A M one BSA address to receive the response of this request. Any URI Service E1 O 0..N Specifies service information. ServiceInfo Content E1 O 0..N Specifies content information. ContentInfo Schedule E1 O 0..N Specifies planning information. ScheduleInfo

Table 10A Title Type of Category Amount of elements Description Data type ServiceInfo Specifies information services. Contains the following attributes:
id
Version
type
ServiceProtection.
Contains the following elements:
ExtensionURL
GlobalServiceID
Name
Description
Parentalating
TargetUserProfile
Genre
UserRating
Broadcast_Area. id A M one Service fragment identifier globally unique. Any URI Version A M one Version of this snippet. The new version overwrites the old one as soon as it is accepted. Unsigned integer (32 bits) type A M one Type of service. The allowed values are:
0 - not set
1 - basic TV, not interactive,
2 - basic TV, interactive,
3 - broadcasting clips (Clipcast),
4 - mixed basic TV and video broadcasting is not interactive,
5 - mixed base TV and interactive broadcasting of clips,
6 - Basic radio, not interactive,
7 - Basic radio, interactive,
8 - services downloaded as files,
9 - software management services,
10 - notification services,
11-200 - reserved for future use,
201-255 - Reserved for private use. Integer (8 bits)

Table 10B Title Type of Category Amount of elements Description Data type ServiceProtection BUT ABOUT 0..1 Indicates whether the service is encrypted (False) or not (True). It is the recommended value from SGAS. Boolean ExtensionURL E1 O 0..N A URL containing additional information related to this snippet on a web page. The terminal can retrieve additional information by accessing this URL. Any URI GlobalServiceID E1 O 0..1 A globally unique identifier identifying the service that describes this fragment of the service. Any URI Name E1 M 1..N Name of service, possibly in many languages. The language is expressed using the built-in XML attribute xml: lang with this element. Line Description E1 O 0..N Description, possibly in many languages. The language is expressed using the built-in XML attribute xml: lang with this element. Line Parentalating E1 O 0..1 A rating level defining a criterion that parent elements can use to determine whether the associated access element is suitable for children that are defined according to the regulatory requirements of the service area. Line

Table 10C Title Type of Category Amount of elements Description Data type TargetUserProfile E1 O 0..1 Profile of users for whom the service or content is intended. For example, age, gender, occupation, etc. Genre E1 O 0..N The classification of services associated with the characteristic form (for example, comedy, drama, etc.). Line UserRating E1 O 0..N Rating information collected from users (e.g. favoritism or recommended age limit). Whole broadcast_area E1 O 0..1 A broadcast area for including location information for BCAST content. Subelements:
target_area. target_area E2 O 0..N Target area for content distribution (as specified in [OMA MLP] with modifications). Subelements:
shape
cc
name_area
zip_code. shape E3 O 0..1 Forms used to represent and describe a geographic area (as specified in [OMA MLP]). See [OMA MLP]

Table 10D Title Type of Category Amount of elements Description Data type CC E3 O 0..1 Country code, 1-3 digits, for example, 355 for Albania (as specified in [OMA MLP]). See [OMA MLP] name_area E3 O 0..1 The geopolitical name of the region, for example, Seoul (as defined in [OMA MLP]). See [OMA MLP] zip_code E3 O 0..1 Postcode. Whole

Table 11A Title Type of Category Amount of elements Description Data type ContentInfo Specifies content information. Contains the following attributes:
id
version
ServiceIDRef
ContentType
Contains the following subelements:
ExtensionURL
Name
Description
Parentalating
TargetUserProfile
Genre
UserRating
Broadcast_Area
Filedescription id A M one Content fragment identifier globally unique. Any URI version A M one Version of this snippet. The new version overwrites the old one as soon as it is accepted. Unsigned integer (32 bits) ServiceIDRef A M one Link to the service fragment to which the content fragment belongs. Any URI Contenttype A M one A type of multimedia content defined by MIME media types [RFC2046]. Line

Table 11B Title Type of Category Amount of elements Description Data type ExtensionURL E1 O 0..N A URL containing additional information related to this snippet on a web page. The terminal can retrieve additional information by accessing this URL. Any URI Name E1 M 1..N The name of a piece of content, possibly in many languages. The language is expressed using the built-in XML attribute xml: lang with this element. Line Description E1 O 0..N Description, possibly in many languages. The language is expressed using the built-in XML attribute xml: lang with this element. Line Parentalating E1 O 0..N A rating level defining a criterion that parent elements can use to determine whether the associated access element is suitable for children that are defined according to the regulatory requirements of the service area. Recommended age limit. This age limit rating level overwrites the age limit rating level defined for the service during the validity of the planning fragment. If there are two overlapping planning fragments with different parental ratings, then one with the most restrictive parental rating defined for the planning fragment overwrites the other. Whole

Table 11C Title Type of Category Amount of elements Description Data type TargetUserProfile E1 O 0..1 Profile of users for whom the service or content is intended. For example, age, gender, occupation, etc. Genre E1 O 0..N Classification of content related to the characteristic form (for example, comedy, drama, etc.). Line UserRating E1 O 0..1 Rating information collected from users (e.g. favoritism or recommended age limit). Whole broadcast_area E1 O 0..1 A broadcast area for including location information for BCAST content. Subelements:
target_area. target_area E2 O 0..N Target area for content distribution (as specified in [OMA MLP] with modifications). Subelements:
shape
cc
name_area
zip_code. shape E3 O 0..1 Forms used to represent and describe a geographic area (as specified in [OMA MLP]). See [OMA MLP] ss E3 O 0..1 Country code, 1-3 digits, for example, 355 for Albania (as specified in [OMA MLP]). See [OMA MLP] name_area E3 O 0..1 The geopolitical name of the region, for example, Seoul (as defined in [OMA MLP]). See [OMA MLP] zip_code E3 O 0..1 Postcode. Whole Filedescription E1 O 0..1 A description of the file or files related to this content.
Attributes:
Content length
Transfer-length
Content type
Content encoding
Content-MD5. Content length A O 0..1 See RFC3926, section 3.4.2. Long unsigned Transfer-length A O 0..1 See RFC3926, section 3.4.2. Long unsigned Content type A O 0..1 See RFC3926, section 3.4.2. Line Content encoding A O 0..1 See RFC3926, section 3.4.2. Line

Table 12A Title Type of Category Amount of elements Description Data type ScheduleInfo A fragment of planning. Contains the following attributes:
id
version
ServiceIDRef.
Contains the following subelements:
InteractivityDataIDRef
ContentIDRef
ExtensionURL
Name
Description. id A M one Planning fragment identifier globally unique. Any URI version A M one Version of this snippet. The new version overwrites the old one as soon as it is accepted. Unsigned integer (32 bits) ServiceIDRef A M one Link to a service fragment to which the planning fragment belongs. Any URI

Table 12B Title Type of Category Amount of elements Description Data type InteractivityDataIDRef E1 ABOUT 0..N Link to the interactivity data fragment to which the planning fragment belongs. This IDRef declares delivery planning for the InteractivityMedia document file that the InteractivityData fragment points to. An InteractivityData fragment may also be associated with a ScheduleItem fragment, but this is preferably not the purpose of this IDRef. It contains the following attributes:
idRef
AutoStart
It contains the following subelements:
Distribution_window
The view window is actually declared using the Valid_From and Valid_To values in the media object document. Any URI idRef BUT M one Identification of the interactivity data fragment to which the Schedule fragment belongs. Any URI AutoStart BUT ABOUT 0..1 Indicates whether the associated interactivity data is automatically activated. If the AutoStart value is true, the associated interactivity data will automatically be activated when the document of the media object is valid. If the AutoStart value is false, the associated interactivity data will not be automatically activated, but can be activated at any time for the validity of the document of the multimedia object at the user's request. Preferably, the terminal settings allow users to configure whether to allow interactivity data to be automatically activated without prompting the user. Boolean

Table 12D Title Type of Category Amount of elements Description Data type RepeatType E3 ABOUT 0..1 Indicates whether the interactivity data referenced by the ContentID is repeated when distributed according to the Unit and Number attributes. Unit BUT M one Indicates the unit of time (for example, hours, days, ...) during which the content is repeated during distribution. Whole Number BUT M one Number of units. Whole ContentIDRef E1 O 0..N A link to the pieces of content to which the piece of planning belongs. It contains the following attributes:
Idref
AutoStart
RepeatPlayback.
It contains the following subelements:
Distribution_window
Presentation_Window idRef BUT M one Identification of the piece of content to which Schedule belongs. Any URI

Table 12F Title Type of Category Amount of elements Description Data type Distribution_window E2 ABOUT 0..N The time interval at which the referenced content specified by the ContentID is available for delivery. It contains the following attributes:
Distribution_Start_Time
Distribution_End_Time
Dwid.
It contains the following subelements:
RepeatType Distribution_Start_Time BUT ABOUT 0..1 Start of Distribution_Window. If not specified, it is assumed that validity began at some point in the past. Integer (32 bits), expressed as NTP time. DistributionEnd_Time A ABOUT 0..1 End of Distribution_Window. If not specified, it is assumed that validity will end at some uncertain point in the future. Integer (32 bits), expressed as NTP time. DWid A ABOUT 0..1 Identification of Distribution_Window, to which each Distribution_Window belongs. Whole RepeatType E3 ABOUT 0..1 Indicates whether the content referenced by the ContentID is repeated when distributed according to the Unit and Number attributes. Unit BUT M one Indicates the unit of time (for example, hours, days, ...) during which the content is repeated during distribution. Whole Number BUT M one Number of units. Whole

Table 12H Title Type of Category Amount of elements Description Data type ExtensionURL E1 O 0..N A URL containing additional information related to this snippet on a web page. The terminal can retrieve additional information by accessing this URL. Any URI Name E1 M 1..N Schedule name, possibly in many languages. The language is expressed using the built-in XML attribute xml: lang with this element. Line Description E1 ABOUT 0..N Description, possibly in many languages. The language is expressed using the built-in XML attribute xml: lang with this element. Line

Table 13 Title Type of Category Amount of elements Description Data type SGASProvRes E M 0..N Specifies the response message for SGASProvReq. Contains the following attributes:
SGASProvReqId. SGASProvReqId E1 M 0..N Identifier for SGASProvReq. Contains the following attributes:
Response Unsigned integer (32 bits) Response BUT M one Sets the result of how SGSS is handled by SGASProvReq. If Response = 0, a provision is generated by SGASProvReq specified by SGASProvReqId. If Response = 1, the grant generation fails and a retransmission is requested. Integer (8 bits)

12 is a flowchart illustrating an example protocol stack used for delivering a service request source message (source) of a service control or notification event on an SG-3 or NT-3 output interface according to an embodiment of the present invention.

To deliver the message via SG-3 or NT-3, indicated by 1201, the message can be directly delivered to HTTP using HTTP, as shown in FIG. 6 or FIG. 10. As another way, the corresponding request message can be sent using the Web Service Protocol to transmit XML data, like the Simple Object Access Protocol (SOAP), Extensible-Markup Language-Remote Procedure Call (XML-RPC), and Blocks Extensible Exchange Protocol (BEEP).

12 shows a hierarchical structure formed with respect to SG-3 or NT-3. For SG-3 or NT-3 exchange, it is preferable to provide the same hierarchical structure. Therefore, the same reference numbers are used for the same hierarchical objects in FIG. That is, reference numeral 1203 indicates an IP layer, reference numeral 1205 indicates a TCP layer, reference numeral 1207 indicates an HTTP layer, and reference numeral 1209 indicates a Web Service Protocol.

13 is a signaling diagram illustrating an exemplary delivery of a service control source (source information) between SGAS and SGSS over SG-3 according to an embodiment of the present invention.

In step 1311, the SGAS 1301 sends information regarding the source of the service control information, as shown by the example in table 14, to the SGSS 1302. After receiving the information of the service control source, the SGSS 1302 processes the information of the service control source, generates a response message using the processing result, and sends a response a message to SGAS 1301 in step 1312. An example message of the processing result is shown by way of example in table 15.

Table 14 Title Type of Category Amount of elements Description Data type SGSDelivery Specifies a service control information source delivery message that is used to generate service control information in SG-G. Contains the following attributes:
SGSDid
EntityAddress.
Contains the following elements:
SGData SGSDid A M one The identifier SGSDelivery, unique to the network entity that generates this message. Unsigned integer (32 bits) Entityaddress A M one The address of the network entity that generates this message and receives the request. Any URI SGData E1 ABOUT 0..1 Contains information from Content Creation to be included in service management information. Preferably, this information is delivered in the form of fragments of BCAST service management information. Other formats may be used. If fragments of BCAST service management information are used, network-required elements or attributes that are not relevant should preferably be delivered as empty fields, and network-optional elements or attributes that are not relevant should preferably not be created. Contains attribute:
Namespace. namespace A ABOUT 0..1 Set to the name of the BCAST service management information XML namespace to signal that SGData content is subordinate to BCAST SG. Any URI

Table 15 Title Type of Category Amount of elements Description Data type SGSDRes Specifies the response message for SGSDelivery. Contains the following elements:
SGSDid SGSDid E1 M 1..N SGSDelivery message identifier.
Contains the following attributes:
StatusCode Unsigned integer (32 bits) Statuscode A M one Indicates the overall result of how SGSDelivery is processed according to the global status code. Unsigned byte

14 is a signaling diagram illustrating an example notification event delivery between NTE and NTG over NT-3 according to an embodiment of the present invention. With reference to FIG. 14, a detailed description will be given of the delivery of a notification event between NTE 1401 and NTG 1402.

In step 1411, the NTE 1401 generates a notification event message and sends the generated notification event message to the NTG 1402. The notification event message is shown by way of example in table 16. After receiving the notification event message, the NTG 1402 processes the received notification event, generates a response signal using the processed result, and transmits a response message to NTE 1401 in step 1412. The processed result message for the notification event is shown by way of example in table 17.

Table 16 Title Type of Category Amount of elements Description Data type NTEReq E Specifies a notification event delivery message to generate a notification message. Contains the following attributes:
NTEId
Entityaddress
DeliveryPriority.
Contains the following elements:
NotificationEvent NTEId A M one Notification Event ID. Unsigned integer (32 bits) Entityaddress A M one The address of the network object to receive a response to this message. Any URI DeliveryPriority BUT ABOUT 0..1 Determines the priority of this notification event. This information is used to generate a notification message in NTG. NTG can be ignored in this field. Boolean NotificationEvent E1 M 1..N Defines a Notification Event containing information that should be included in the notification message. Preferably, this information is delivered in the form of a BCAST notification message format. Other formats may be used. If the BCAST notification message format is used, network mandatory elements or attributes that are not relevant should preferably be delivered as empty fields, and optional network elements or attributes that are not relevant should preferably not be created. Contains attribute: Namespace. Namespace BUT ABOUT 0..1 Set to the name of the BCAST notification XML namespace to signal that the NotificationEvent content is subordinate to the BCAST notification message format. Any URI

Table 17 Title Type of Category Amount of elements Description Data type NTERes Specifies the response message for NTEReq. Contains the following elements:
NTEId. NTEId E1 M 1..N The identifier of the NTEReq message. Contains the following attributes:
StatusCode Unsigned integer (32 bits) Statuscode A M one Indicates the overall result of how NTEReq is processed according to the global status code. Unsigned byte

Sample codes used to indicate result values in response messages are shown by way of example in Tables 18A-18C.

Table 18A The code Status 00 Success 0 The request was successfully processed. 00 Device Authentication Failure one This code indicates that BSM was not able to authenticate the device, which may be due to the fact that the user or device is not registered with BSM. In this case, the user can contact the BSM and establish contact or give credentials instead, which are used for authentication. 00 User Authentication Failure 2 This code indicates that BSM was not able to authenticate the user, which may be due to the fact that the user or device is not registered with BSM. In this case, the user can contact the BSM and establish contact or give credentials instead, which are used for authentication. 00 Unknown purchase item 3 This code indicates that the requested service element is unknown. This may be the case, for example, if the device has cached service management with old information. In this case, the user may retrieve the service control information. 00 Device Authorization Failure four This code indicates that the device is not authorized to receive the durable key message from the RI, for example, because the device certificate has been revoked. In this case, the user can contact the BSM operator. 00 User Authorization Failure 5 This code indicates that the user is not authorized to receive the durable key message from RI, for example, because the device certificate has been revoked. In this case, the user can contact the BSM operator. 00 Device not registered 6 This code indicates that the device is not registered in the RI that is used for the transaction. When this code is sent, the response message includes a registration initiator that allows the device to register. In this case, the device can automatically complete the registration, and if the registration is successful, re-initiate the original transaction. 00 server error 7 This code indicates that there was a server error, for example, a problem with the remote server system. In this case, the transaction can be successful if it is initiated later.

Table 18B The code Status 00 Badly formed message error 8 This code indicates that there is a device failure, for example, a poorly formed XML request. In this case, the transaction may or may not (for example, if there is a problem of interoperability) be successful if it is initiated later. 00 Billing Error 9 This code indicates that there is a refusal at the stage of charging (for example, an agreed credit limit has been reached, the account has been blocked, etc.), and therefore the requested message of the long-term key cannot be provided. The user in this case can contact the BSM operator. 01 No subscription 0 This code indicates that there has never been a subscription to this element of the service, or that the subscription for this element has expired. In this case, the user may issue a service request for a new subscription. 01 Operation not allowed one This code indicates that the operation that the device is trying to perform is not permitted by contract between the BSM and the user. In this case, the user can contact the BSM operator and change the contract. 01 Unsupported version 2 This code indicates that the version number indicated in the request message is not supported by the network. The user in this case can contact the BSM operator. 01 Invalid device 3 This code indicates that the device requesting the services is not acceptable to the BSM, for example, is blacklisted. The user in this case can contact the BSM operator. 01 Service area not allowed four This code indicates that services in the requested area are not allowed for the device due to subscription restrictions. In this case, the user can contact the BSM operator or subscribe to the applicable service. 01 Requested Services Unavailable 5 This code indicates that the requested services are unavailable due to data transfer problems. In this case, the request may be re-initiated at a later time.

Table 18C The code Status 01 Request has already been processed. 6 This code indicates that an identical request was previously processed. In this case, the user or object can check to see if the request has already been processed (for example, LTK has been accepted), and if not, repeat the request. 01 Information item does not exist. 7 This code indicates that the message includes an unrecognized information element, because the identifier of this information element is not defined or it is defined, but not implemented by the object receiving the message. In this case, the corresponding objects must be in contact with each other. 01 Not specified 8 This code indicates that there is an error that cannot be identified. In this case, the corresponding objects must be in contact with each other. 01 Process delayed 9 Due to the high load, the request is in the queue waiting to be processed. The user or object in this case must wait for the transaction to complete. 02 Generation Failure 0 This code indicates that the request information (message) cannot be generated. In this case, the user or object should try again later. 02 Information is false one This code indicates that the specified information is false and cannot be used in the system. In this case, the request should be re-checked and sent again. 02 Invalid request 2 This code indicates that key-requesting materials or messages (for example, LTKM) are invalid and cannot be satisfied. In this case, the request should be re-checked and sent again. 02 Invalid destination 3 This code indicates that the message destination is not intended. In this case, the request should be re-checked and sent again. 02 Delivery of incorrect key information four This code indicates that the delivered key information and messages (e.g. LTKM) are invalid. In this case, the request should be re-checked and sent again. 025-127 Reserved for future use. 128-255 Reserved for private use.

The global status codes shown in tables 18A-18C are included in the response message response field. That is, when the requirements are processed normally, the Response value is set to "000", and the mobile terminal can recognize from the value of the corresponding code that the requirements have been successfully processed. Therefore, tables 18A-18C must be stored in the system, or can be stored in the terminal. That is, tables 18A-18C are typically stored in the system and terminal for future use.

Further, additional codes may be determined according to the desired purpose of the service provider. The global status codes shown in tables 18A-18C can be used for response messages associated with embodiments of the present invention, as well as all response messages for delivering processing results to any system or terminal supporting mobile broadcasting services when the results are notified using Status codes or Response codes. Here, the Answer corresponds to the response field in the preceding tables. For example, it can be interpreted as a response field in table 13. Therefore, the response field from table 13 can be used as an equivalent to the StatusCode field.

As can be understood from the foregoing description, the mobile broadcast system needs a notification event message from NTE to the BSA in order to generate a notification message, and provides a method for delivering the corresponding message. For the delivered message, the NTE in the BSA must be aware of the generation result for the corresponding message, and the NTG in the BSM provides a method for generating and sending a response message for a plurality of BSAs or a plurality of event messages. Thus, in order to generate service control information, the SGSS in the BSM must provide the provision information to the SG-G in the BSD / A and can provide a method that is capable of pre-receiving the associated service / content information.

While the invention is shown and described with reference to some exemplary embodiments, it will be understood by those skilled in the art that various changes in form and details can be made therein without departing from the scope and spirit of the invention as defined by the appended claims and equivalents.

Claims (28)

1. A method for providing service control information for a mobile broadcast service (BCAST) in a wireless communication / broadcast system supporting the BCAST service, the method comprises the steps of:
inclusion by the Service Management Use Source (SGAS) of service information and content in the service control information generation request message and delivery of the service management information request message to the Service Management Subscription Source (SGSS) to provide service management; and
generating by SGSS information of formation and provision of service management after receiving a message of request for generating service management information and delivery of a response message of forming service management to SGAS. 2. The method of claim 1, wherein the request message for generating service control information includes an SGASProvreqid indicating an SGAS identifier that requested generation of control for a service and content, and a BSAAddress indicating BCAST Service Use Address Information (BSA) for SGAS. 3. The method of claim 1, wherein the SGAS also includes scheduling information in a request message for generating service control information issued to the SGSS. 4. The method according to claim 1, in which the provision information includes information PurchaseItem, PurchaseData and PurchaseChannel. 5. The method according to claim 1, in which the response message forming the service control is delivered using the HTTP Response message, including a unique identifier for distinguishing the request message, if the SGSS completes the formation of service control information and the formation of the provision information immediately after receiving the request message forming information service management. 6. The method according to claim 1, in which the response message forming the management of services is delivered using an HTTP POST message that includes a unique identifier to distinguish this request message at the time of completion of formation, if the SGSS does not complete the generation of information management services and the formation of information providing immediately after receiving a request message for generating service control information. 7. The method of claim 1, wherein the SGSS notifies the desired result with a single service control response message after receiving two or more service control information generating request messages from SGAS. 8. A service management support system for a mobile broadcast service (BCAST) in a wireless communication / broadcast system supporting the BCAST service, the system comprising:
A Service Management Use Source (SGAS) for including service and content information in a service control information generation request message and delivering a service management information request message to a Service Management Subscription Source (SGSS) to provide service management; and
SGSS for generating information providing and generating service management information after receiving a request message for generating service management information and delivering a response message for generating service management to SGAS. 9. The system of claim 8, in which the service control information generation request message includes an SGASProvreqid indicating an SGAS identifier that requested management generation for a service and content, and a BSAAddress indicating BCAST Service Use Address Information (BSA) for SGAS. 10. The system of claim 8, in which the SGAS also includes scheduling information in a request message for generating service control information issued to the SGSS. 11. The system of claim 8, in which the provision information includes information PurchaseItem, PurchaseData and PurchaseChannel. 12. The system of claim 8, in which the response message forming the service control is delivered using the HTTP Response message, including a unique identifier for distinguishing this request message, if the SGSS completes the generation of information providing and the formation of service control information immediately after receiving the message request formation service management information. 13. The system of claim 8, in which the response message forming the service control is delivered using an HTTP POST message that includes a unique identifier for distinguishing the request message at the time of completion of formation, if the SGSS does not complete the formation of service control and the formation of information provision immediately after receiving message request formation information management services. 14. The system of claim 8, in which the SGSS transmits a notification of the desired result with a single service control response message after receiving two or more service control information generation request messages from SGAS. 15. A method for providing a notification message for a mobile broadcast service (BCAST) in a wireless communication / broadcast system supporting the BCAST service, the method comprising the steps of:
send through the Notification Events (NTE) function block to the BCAST Service Use Block (BSA) a notification message generation request message notification message generation request message to the Notification Generation (NTG) function block in the BCAST Subscription Management function block (BSM); and
generating, by NTG, a notification message for notification information after receiving a request message generating a notification message and sending a result message for the result of generation to NTE. 16. The method of claim 15, wherein the notification message generating request message includes an NTEid indicating an NTE identifier and a BSAAddress indicating a BSA address. 17. The method of claim 15, wherein the notification message generating request message includes a Notification Type field indicating whether the notification message should be provided to the user or terminal and a Priority field indicating the priority of the notification. 18. The method of claim 17, wherein the notification message generation request message also includes a Validity field indicating valid time information of the notification message. 19. The method of claim 15, wherein the notification information represents an event that occurs when there is a change in the service provided to the subscriber, when there is an upcoming change in the service provided to the subscriber, or when there is an emergency event. 20. The method according to 17, in which the NTG immediately generates and delivers the result message after receiving the message request the formation of a notification message from NTE. 21. The method according to clause 16, in which the NTG generates and delivers the result message after closing the communication session between NTE and NTE after receiving the message request message formation notification messages from NTE. 22. A notification message system for a mobile broadcast service (BCAST) in a wireless communication / broadcast system supporting the BCAST service, the system comprising:
the Notification Events (NTE) function block in the BCAST Service Use block (BSA) for sending a notification message generation request message to a notification message generation request to the Notification Generation (NTG) function block in the BCAST Subscription Management (BSM) block; and
NTG for generating a notification message for notification information after receiving a request message for generating a notification message, and sending a result message for the generating result to NTE. 23. The system of claim 22, wherein the notification message generation request message includes an NTEid indicating an NTE identifier and a BSAAddress indicating a BSA address. 24. The system of claim 22, wherein the notification message generation request message includes a Notification Type field indicating whether the notification message should be provided to the user or terminal and a Priority field indicating the priority of the notification. 25. The system of claim 24, wherein the request message generating the notification message also includes a Validity field indicating valid time information of the notification message. 26. The system of claim 22, wherein the notification information is an event that occurs when there is a change in the service provided to the subscriber, when there is an upcoming change in the service provided to the subscriber, or when there is an emergency event. 27. The system according to item 22, in which the NTG immediately generates and delivers the result message after receiving the message request the formation of a notification message from NTE. 28. The system of claim 22, wherein the NTG generates and delivers a result message after a communication session between NTE and NTE is completed after receiving a notification message generation request message from NTE.

Images