KR20090106334A - Method and system for providing custom bundle in mobile broadcasting system - Google Patents

Abstract

The present invention relates to a mobile broadcasting system, and is a system and method for providing a user-oriented customized service by providing a user-defined bundle composed of services selected by a user in consideration of a user's preference.

According to an embodiment of the present invention, there is provided a method of receiving a user-defined bundle in a terminal of a portable broadcasting system, the method comprising: receiving a service guide from a broadcast service distribution / adaptation unit (BSDA); Generating a user-defined bundle based on desired content or service, including the user-defined bundle in a user-defined bundle subscription request message and transmitting it to a broadcast service subscription management unit (BCAST Subscription Management, BSM), and the BSM Determining whether the received message is a purchase inquiry request message or a user-defined bundle subscription response message; and if the purchase inquiry request message is a message, a purchase inquiry response message including whether to accept the purchase from the user is generated and transmitted to the BSM. It includes the process of doing.

Description

METHOD AND SYSTEM FOR PROVIDING USER DEFINED BUNDLE IN MOBILE BROADCAST SYSTEM}

The present invention relates to a portable broadcast system, and more particularly, to a method and system for providing a broadcast service in a portable broadcast system.

The mobile communication market is constantly demanding the production of new services through recombination or integration of existing technologies. Today, due to the development of communication and broadcasting technologies, mobile phones, personal digital assistants (PDAs), etc. are used in conventional broadcasting systems or mobile communication systems. It is in the step of providing a broadcast service through a mobile terminal (hereinafter, referred to as a "mobile terminal"). IT is strengthening the mobile communication business by accommodating such potential and actual market demands, increasing user demands for multimedia services, strategies of operators to provide new services such as broadcasting services in addition to existing voice services, and demands of consumers. With companies' interests in mind, the convergence of mobile communication services and IP is becoming a big trend in the development of next generation mobile technology. This has led to the introduction and application of various services existing in wireless or broadcasting, not only in the mobile telecommunication market, but also in the general wired market. This omnidirectional convergence creates the same consumption environment for various services regardless of wired or wireless broadcasting. It became.

Meanwhile, the Open Mobile Alliance (OMA) is an organization that researches standards for interoperability of individual mobile solutions, and is mainly responsible for setting various application standards for mobile games and Internet services. In particular, the OMA BCAST (Mobile Broadcast Working Group) of the working group of the OMA is studying a technical standard for providing a broadcast service using a mobile terminal. OMA BCAST standardizes technologies for providing IP-based broadcasting services in mobile terminal environments such as service guide, download and streaming transmission technology, service and content protection technology, service subscription, and roaming.

In accordance with the market flow of integrated service provision due to the convergence of wired and wireless environments described above, portable broadcasting technologies such as OMA BCAST will evolve to provide services in a wired and wireless integrated environment beyond the mobile environment.

On the other hand, in the BCAST system, the services that the BCAST provider wants to provide to users are bundled and provided as a bundle. This bundle, called a bundle, is similar in concept to the channel package currently offered in conventional cable television or satellite television. Such a bundle is a bundle defined in advance by the operator to provide a service, and is defined at the operator's discretion. In general, most commonly configured to suit a large number of user groups, such a carrier-based bundle does not support a direct selection according to the user's preferences. Therefore, if a user wants a bundle other than the bundle provided by the operator, the user cannot request or apply for the bundle. Therefore, a method and system for supporting the user's direct selection according to the preference are required.

Accordingly, the present invention provides a method and system for providing a user-defined bundle that can be used by bundling, subscribing and using services directly selected by a user in consideration of a user's preference in a portable broadcasting system.

According to an embodiment of the present invention, there is provided a method of receiving a user-defined bundle in a terminal of a portable broadcasting system, the method comprising: receiving a service guide from a broadcast service distribution / adaptation unit (BSDA); Generating a user-defined bundle based on desired content or service, including the user-defined bundle in a user-defined bundle subscription request message and transmitting it to a broadcast service subscription management unit (BCAST Subscription Management, BSM), and the BSM Determining whether the received message is a purchase inquiry request message or a user-defined bundle subscription response message; and if the purchase inquiry request message is a message, a purchase inquiry response message including whether to accept the purchase from the user is generated and transmitted to the BSM. It includes the process of doing.

The present invention has an effect of providing a user-oriented customized service by providing a user-defined bundle composed of services selected by the user in consideration of the user's preference.

Hereinafter, with reference to the accompanying drawings a detailed description of preferred embodiments of the present invention will be described in detail. It should be noted that the same components in the figures represent the same numerals wherever possible.

In addition, specific details appear in the following description, which is provided to help a more general understanding of the present invention, and it is obvious to those skilled in the art that the present invention may be practiced without these specific details. Will do. In the following description of the present invention, detailed descriptions of related well-known functions or configurations will be omitted when it is determined that the detailed descriptions may unnecessarily obscure the subject matter of the present invention.

 In the following description will be presented a representative embodiment in the present invention for achieving the above technical problem. In addition, for convenience of description of the present invention, the names of entities defined in BCAST of 3GPP (3G Generation Partnership Project), which is an asynchronous mobile communication standard, or OMA (Open Mobile Alliance), which is a standard organization for application of a mobile terminal, will be identically used. However, these standards and names do not limit the scope of the present invention, and of course, they are applicable to systems having similar technical backgrounds. Before describing the present invention, the message schema table used in the present invention is used for better understanding. The description is as shown in Table 1a.

In Table 1a, Name represents names of element and attribute values that constitute the message. Type means whether the name is an element value or an attribute value. Element values have the same values as E1, E2, E3, and E4, where E1 is the upper element value for the entire message, E2 is the lower element value of E1, E3 is the lower element value of E2, and E4 is the lower element of E3. Represents an element value. Attribute values are denoted by A, where A represents the attribute value of the element. For example, A below E1 indicates an attribute value of E1. Category is used to distinguish whether the element value or attribute value is mandatory or not. It has M value if it is required and O value if it is optional. Cardinality represents a relationship between elements and has values of 0, 0..1, 1, 0..n, and 1..n. 0 means option, 1 means mandatory relationship, and n means that it can have many values. For example, 0..n means that the element value may be absent or may have n values. Description indicates what the corresponding element or attribute value means, and Data Type indicates the data type of the corresponding element value or attribute value.

In addition, since the present invention is based on a standard defined by BCAST, a detailed description related to the procedure or message element defined by BCAST is omitted.

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

1 is a logical structure diagram of a BCAST working group of OMA which establishes a standard technology for an application layer and a lower layer transport layer for a mobile broadcast service.

First, the logical entities shown in FIG. 1 will be described in detail. A content creation (CC) 101 supplies content that is the basis of a BCAST service, which may be a file for a normal broadcast service, such as data for a movie, audio, video, or the like. . In addition, the content provider 101 provides a BCAST service application 102 with an attribute of the content for generating a service guide and determining a transport bearer to which the service is to be transmitted.

The BCAST service application 102 receives the data of the BCAST service from the content provider 101 and processes it into a form suitable for providing media encoding, content protection, and interactive services. In addition, the attributes of the content supplied from the content provider 101 are provided to a BCAST Service Distribution / Adaptation 103 and a BCAST Subscription Management 104.

The BCAST service distribution / coordinator 103 uses the BCAST service data supplied from the BCAST service application 102 to perform operations such as file and streaming transmission, service collection, service protection, service guide generation and transmission, and service notification. Do this. In addition, the BCAST service distribution / adjustment unit 103 adjusts the service to match the broadcast distribution system 112.

The BCAST subscription management unit 104 manages hardware such as service provision, such as subscription and charge related functions of BCAST service users, regulation of information used for BCAST service, and terminals receiving BAST services in hardware or software.

The terminal 105 receives program support information such as content and service guides and content protection and provides a broadcast service to the user. The BDS Service Distribution 111 transmits a portable broadcast service to a plurality of terminals through mutual communication with the broadcast distribution system 112 and the Interaction Network 113.

The broadcast distribution system 112 transmits a portable broadcast service through a broadcast channel. For example, BCMCS of 3GPP's Multimedia Broadcast Multicast Service (MBMS) and 3rd Generation Project Partnership 2 (3GPP2), a third-generation synchronous mobile communication standard organization. (Broadcast Multicast Service), DVB-H (DVB-Handheld) or IP (Internet Protocol) based broadcast / communication network of digital broadcast standard (DVB). The interworking network 113 provides a bidirectional channel and may be, for example, a cellular network.

Next, reference points which are connection paths between the logical entities will be described. The reference point has a plurality of interfaces according to the purpose, and this interface is used for communication between two or more logical entities for a predetermined purpose, and a message format and a protocol for this purpose are applied.

BCAST-1 121 is a transmission path of content and content attributes, and BCAST-2 122 is a content-protected or content-unprotected BCAST service and a property of the BCAST service. And a transmission path of the content attribute.

The BCAST-3 123 is an attribute of a BCAST service, an attribute of a content, user preference and subscription information, a user request, and a transmission path of a response to the request.

The BCAST-4 124 is a transmission path of a notification message, an attribute used for a service guide, a key used for content protection, and service protection.

BCAST-5 (125) includes protected BCAST service, unprotected BCAST service, content-protected BCAST service, content-unprotected BCAST service, BCAST It is transmitted through security material and broadcast channel such as service property, content property, notification, service guide, digital right management (DRM) RO and kit value used for BCAST service protection. It is the channel of all data and signals.

BCAST-6 (126) is a protected BCAST service, an unprotected BCAST service, a content-protected BCAST service, a content-unprotected BCAST service, BCAST Transmitted through the interaction channel with security materials such as service attributes, content attributes, notifications, service guides, and digital rights management (DRM) ROs and kit values used for BCAST service protection. It is the channel of all data and signals.

The BCAST-7 127 includes security elements such as service provisioning, subscription information, device management, and digital rights management (DRM) RO and key values used for BCAST service protection. It is a transmission path of user preference information transmitted through an interaction channel of control information related to reception of a material.

BCAST-8 128 is a transmission path through which user data for BCAST service is interacted. BDS-1 129 is a DRM (DRM) used for protected BCAST services, unprotected BCAST services, BCAST service properties, content properties, notifications, service guides, and BCAST service protection. Digital Right Management) This is the transmission path of security material such as RO and key value.

The BDS-2 130 includes security elements such as Digital Right Management (DRM) RO and key values used for service provisioning, subscription information, device management, and BCAST service protection. material). X-1 131 is a reference point between the BDS service distribution unit 111 and the broadcast distribution system 112.

X-2 132 is a reference point between the BDS service distribution unit 111 and the interworking network 113.

X-3 133 is a reference point between broadcast distribution system 112 and terminal 105.

X-4 (134) is a reference point between the BDS service distribution unit 111 and the terminal 105 through a broadcast channel.

X-5 135 is a reference point between the BDS service distribution unit 111 and the terminal 105 through the interaction channel.

X-6 136 is a reference point between the interworking network 113 and the terminal 105.

FIG. 2 is a diagram illustrating a data model of a service guide for generating a service guide in OMA BCAST to which the present invention is applied. In FIG. 2, a solid line connecting each fragment means a cross reference between each fragment.

As shown in FIG. 2, the service guide data model includes an administrative group 200 that provides upper configuration information of the entire service guide, a core group that is an essential part of a service guide such as services, contents, and schedules. Core 220, an Access 230 that provides access information to access a service or content, and a Provisioning 210 that includes subscription and purchase information. Each component of the management group 200 is a service guide delivery interpreter (ServiceGuidedeliveryDescriptor) 201, the supply group 210 is a purchase item (PurchaseItem) 211, purchase data (PurchaseData) 212, purchase channel It consists of (PurchaseChannel) 213.

The core group 220 includes a service 221, a schedule, and a content 223, and the access group 230 includes an access 231 and a session description. 232).

In addition, as shown in FIG. 2, the service guide information includes preview data 241 and interactivity data 251 in addition to the above four groups. Each of the above-mentioned components is called a fragment, which is the minimum unit constituting the service guide.

Looking at each of the fragment components described above, the service guide transmission interpreter (ServiceGuideDeliveryDescriptor) fragment 201 informs the transmission session information that the service guide transmission unit (ServiceGuideDeliveryUnit: SGDU) containing the fragments constituting the service guide, the SGDU It informs the entry point for receiving the grouping information and the notification message.

The service fragment 221 is a superset of contents included in the broadcast service centered on the entire service guide and includes information on the content, genre, and service area of the service.

The schedule fragment 222 represents time information of each content included in the service, such as streaming and downloading.

The content fragment 223 includes a detailed description of the broadcasted content, a target user group, a service area, a genre, and the like.

The access fragment 231 provides information related to the connection so that the service can be viewed, and provides a transmission method, session information, and the like for the access session.

The SessionDescription fragment 232 may be included in the Access Fragment 231 or the terminal may inform the location information in the form of a URI so that the terminal may check the corresponding SessionDescription fragment 232 information. The session interpretation fragment 232 provides address information, codec information, and the like for multimedia content existing in the session.

The PurchaseItem fragment 211 provides a bundle of services, content, time, etc. to help the user subscribe or purchase the corresponding PurchaseItem fragment 211.

The purchase data fragment 212 includes detailed information on purchase and subscription, such as price information and promotion information about a service or a service bundle.

The purchase channel fragment 213 informs access information for subscription or purchase. The service guide transmission interpreter (ServiceGuideDeliveryDescriptor) fragment 201 informs grouping information about an entry point for receiving a service guide and an SGDU that is a container of the fragment.

In addition, the preview data (PreviewData) fragment 241 provides the preview information on the service, schedule, content, or through the interactivity data (InteractivityData) fragment 251 according to the service, schedule, content according to the interactive service during the broadcast You can also provide Specific information on the service guide may be defined through various element values and attribute values for providing details and values based on the higher data model of FIG. 2.

For the convenience of the present invention, detailed element values and attribute values for each fragment of the service guide are not included in the present disclosure, but the above detailed element values and attribute values do not limit the present invention, and for the mobile broadcasting service, The present invention can be applied to all element values and attribute values defined as needed in providing a service guide. 3 is a message flow diagram according to a preferred embodiment of the present invention.

The logical object terminal 301 of FIG. 3, the BCAST Service Distribution / Adaptation (BSDA) 302, and the BCAST Subscription Management (BCSM) 303 are respectively illustrated in FIG. 1. Are the same objects as 105, 103 and 104. In step 304, the terminal 301 receives the service guide from the BSDA 302 and shows the contents to the user. Information on all services and contents provided by the BCAST service provider is provided to the terminal 301 through the service guide transmitted through step 304. In step 304, the BSM 303 may inform the user that a bundle can be directly configured by the user, if desired, for the services and contents described in the service guide. To this end, UDBAllowed elements are added to the service and content fragments in the service guide to inform the user. The structure is as follows <Table 1b> and <Table 1c>.

In step 305, the user selects a desired service or content through the service guide shown by the terminal 301 to the user. In step 305, the user selects a service or content other than the bundle provided by the BCAST service provider, so that the terminal 301 configures a bundle desired by the user. When the user-defined bundle is configured in step 305, the terminal 301 requests a user-defined bundle subscription to the BSM through step 306. The user defined bundle subscription request message transmitted in step 306 is added by adding the following elements to the service subscription request message defined in the existing BCAST.

The UserDefinedBundle element is for informing that the user-defined bundle subscription request message has a request for a user-defined bundle.

The UDBService element represents an identifier of a service that the user wants to add to the custom bundle selected in the service guide.

The notification element is for determining whether to receive a notification message for the service selected by the user.

The UDBcontent element represents an identifier of content that the user wants to add to the custom bundle selected in the service guide.

PurchaseItemID is used when you want to add the bundle provided by the project to the bundle you configure. The configuration of the user-defined bundle subscription request message is as shown in Tables 2a to 2g, and description and usage of elements not described above are not defined in the present invention because they are previously defined in BCAST.

 Upon receiving the user-defined bundle subscription request message in step 306, the BSM 303 determines whether to accept the bundle requested by the user in step 307. In this case, if the user's request cannot be processed, the BSM 303 transmits a message including the fact that the user cannot accept the user-defined bundle subscription request response message in step 310. However, if the user can support the custom bundle service requested by the user, the BSM 303 calculates the price charged based on the service and the content in the requested message, and generates a purchase inquiry request message to the terminal 301 in step 308. send. Configuration of the purchase inquiry request message is as shown in Table 3a to Table 3c.

The PriceNegotiationRequest element of Table 3a indicates a message for notifying the purchase price of the user-defined bundle requested by the user. The requestID of the purchase inquiry request message element is an element for identifying the message. The UDBPrice element contains information about the purchase price of the user-defined bundle requested by the user, and the validTo element represents the validity period of the purchase price provided through the purchase inquiry request message, and currency represents a unit of the purchase price provided. . SubscriptionPeriod represents the subscription validity period of the user-defined bundle for which the user has requested a subscription.

TermOfUse of <Table 3b> is an element for indicating a service subscription condition, and type is an element for indicating a kind of agreement.

Id in Table 3c is a unique identifier of the agreement, and userConsentReqiured explicitly indicates whether user consent is required. Country and language respectively indicate the country and language to which the terms apply, PreviewDataIDRef is used when displaying the terms through separate PreviewData, and TermsofUseText is the actual terms. After receiving the purchase inquiry request message in step 308, the terminal 301 notifies the user of the price suggested by the BSM 303, and then in step 309, the terminal 301 informs the BSM 303 of the purchase inquiry response message. send. The configuration of the purchase inquiry response message transmitted is shown in Table 4 below.

PriceNegotiationResponse in Table 4 is an element representing a message for notifying the purchase price of the user-defined bundle requested by the user. requestID is an element for identifying the message. subscribe indicates whether the user confirms the subscription to the agreement or rejection of the price of the custom bundle service proposed by the BSM 303. userConsent is an element to indicate the response when the user agrees to the terms in the purchase inquiry request message. Finally, step 310 is a user-defined bundle response message informing the BSM 303 of the result of the subscription request of the user-defined bundle. The configuration of the custom bundle response message informing the result of the subscription request of the custom bundle is shown in Tables 5a to 5e and adds some elements of the subscription request message previously defined in the BACST.

In the present invention, the UserDefinedBundle element among the message elements shown in Table 5d is to inform the present message that it is a response to the user-defined bundle. The UDBService element represents the identifier of the service that the user added to the custom bundle selected in the service guide. The UDBcontent element of the message elements of Table 5e indicates an identifier of content added to the user-defined bundle selected by the service guide. PurchaseItemID indicates that the bundle provided by the provider has been added to the bundle defined by the user. In addition, through this message, subscription success and failure can be set. In particular, globalStatusCode in Table 5a is set and used immediately as defined in BCAST. Finally, step 311 shows how to obtain an encryption key (LTKM) necessary for the use of content or services, and follows the method defined by BCAST.

In the present invention, in addition to the user-defined bundle response messages of Tables 5a to 5e, a user-defined bundle response message having a configuration as shown in Tables 6a to 6e may be used. Add some elements of the subscription request message defined in BACST. The custom bundle response message configured as shown in <Table 6a> to <Table 6e> is used when the service, content, or purchase items received through the custom bundle from the BSM 303 are bundled and processed as one purchase item. do.

In the present invention, the UserDefinedBundle element described in Table 6e of the message elements of Tables 6a to 6e is to inform the present message that it is a response to the user-defined bundle. In addition, PurchaseItemFragment and PurchaseDataFragment described in Table 6e are used when BSM 303 newly defines a purchase fragment on a server for a user to provide a custom bundle service.

The PurchaseItemFragment provides a bundle of a service, content, time, etc. of the user-defined bundle, and the PurchaseDataFragment includes detailed information on purchase and subscription, such as price information and promotion information, regarding the bundle of the PurchaseItemFragment. <Table 5a> to <Table 5e> or <Table 6a> to <Table 6e> indicating the response message defined above may be optionally used depending on the BCAST system implementation. In addition, the user-defined bundle response message is not limited to the <Table 5a> to <Table 5e> or <Table 6a> to <Table 6e>, it should be noted that various modifications are possible. When using <Table 6a> to <Table 6e>, in order to perform step 311 of FIG. 3, the terminal 301 and the BSM 303 exchange the PurchaseItemFragement and PurchaseDataFragment received through the <Table 6a> to <Table 6e>. You can also follow the usual BCAST service signup process using. The present invention does not cover the usual BCAST service subscription procedure.

4 is a flowchart of a terminal according to an exemplary embodiment of the present invention.

In step 401 the terminal 301 receives a service guide from the BSDA (302). When the terminal 301 shows the received service guide to the user, the user selects the content or service that he / she wants to see and informs the terminal, the terminal 301 bundles it in a user-defined bundle in step 402 and the user in step 403. It generates a definition bundle subscription request message and transmits it to the BSM 303. In this case, the message generated in step 403 is as shown in Tables 2a to 2g described in the description of FIG. 3. The terminal 301 which transmits the user-defined bundle subscription request message in step 403 waits for a response message from the server and receives a message in step 404 to determine the type of message in step 405. That is, the terminal 301 determines whether the type of message is a bundle purchase message or a rejection message. If the message received in step 404 is not a purchase inquiry request message but a user-defined bundle response message (<Table 5a> to <Table 5e> or <Table 6a> to <Table 6e>), the BSM 303 registers a subscription. The terminal 301 terminates the user-defined bundle purchasing process because of an unacceptable situation. At this time, the globalStatusCode described in Table 5a or Table 6a of the message indicates a subscription failure. When the message is a purchase inquiry request message (<Table 3a> to <Table 3c>) in step 405, the terminal 301 requests the user to confirm the amount of money included in the purchase inquiry request message, and the user makes a purchase inquiry. Determine if the request has been accepted. If the user refuses, the terminal 301 sets a rejection in the purchase inquiry response message in step 410, generates a purchase inquiry response message, and transmits it to the BSM 303. Thereafter, the terminal 301 is notified of the failure to join the user-defined bundle response message through the BSM 303 in step 411. At this time, the globalStatusCode of the message indicates a subscription failure. When the user decides to purchase at the price suggested by the BSM 303, that is, when the user accepts the purchase inquiry request message, the terminal 301 transmits a purchase inquiry response message (< Table 4>) is generated and sent to the BSM 303. In step 407, the terminal 301, which has sent a purchase inquiry response (Table 4) message to the BSM 303, receives a user-defined bundle response message (Table 5a) to Table 5e from the BSM 303 in step 408. FIG. Or <Table 6a> to <Table 6e>). In the case of the message received in step 408, the terminal 301 is marked with the globalStatusCode element, unlike step 405 or step 411. Finally, through step 409, the terminal 301 receives a cryptographic key (LTKM) value required for using the content or service defined in BCAST.

5 is a flowchart of a BSM according to a preferred embodiment of the present invention.

In step 501, the BSM 303 receives a user-defined bundle subscription request message from the terminal 301. The message format received in step 501 is as shown in Table 2. The BSM 303 reviewing the message determines whether to provide a user-defined bundle service in step 502. When the BSM 303 determines that the service cannot be provided, the BSM 303 indicates the subscription processing impossible in the user-defined bundle response message through step 503, and transmits it to the terminal 301 and terminates. In this case, the transmitted message is shown in Tables 5a to 5e or Tables 6a to 6e, and the globalStatusCode element is set as a subscription failure.

However, if the BSM 303 allows a user-defined bundle subscription request in step 502, the BSM 303 determines a price to be charged for the bundle defined by the user in step 504, and the <Table 2a> to <Table 2g>. A purchase inquiry request message is generated and transmitted to the terminal 301 as shown. In step 505, the BSM 303 receives a response to the purchase inquiry request message transmitted in step 504, that is, receives a purchase inquiry response message, and when the user declines the purchase after analyzing the message, the user through step 507. A globalStatusCode element of the definition bundle response message (<Table 5a> to <Table 5e> or <Table 6a> to <Table 6e>) is set as a subscription failure and transmitted to the terminal 301. However, if the user accepts the subscription in step 506, the BSM 303 succeeds in the user-defined bundle response message (<Table 5a> to <Table 5e> or <Table 6a> to <Table 6e>) in step 508. It is set in the globalStatusCode element and transmitted to the terminal 301. Finally, in step 509, the BSM 303 transmits an encryption key (LTKM) necessary for using a content or service to the terminal 301 according to the method defined in BACST.

*

1 is a logical structure diagram of a BCAST working group of OMA which establishes a standard technology for an application layer and a lower layer transport layer for a mobile broadcast service;

2 is a diagram illustrating a data model for a service guide for generating a service guide in OMA BCAST to which the present invention is applied;

3 is a message flow diagram according to a preferred embodiment of the present invention;

4 is a flowchart of a terminal according to an embodiment of the present invention;

5 is a flowchart of a BSM according to a preferred embodiment of the present invention.

Claims (2)

In the method of receiving a user-defined bundle at a terminal of a mobile broadcasting system, Receiving a service guide from a Broadcast Service Distribution / Adaptation (BSDA); Creating a custom bundle based on the content or service desired by the user, Transmitting the user defined bundle in a user defined bundle subscription request message to a broadcast service subscription management unit (BCAST Subscription Management, BSM); Determining whether the message received from the BSM is a purchase inquiry request message or a user-defined bundle subscription response message; And in the case of the purchase inquiry request message, generating a purchase inquiry response message including whether to accept the purchase from a user and transmitting the purchased inquiry response message to the BSM. In the broadcast service subscription management unit (BCAST Subscription Management, BSM) of the portable broadcasting system, Receiving a custom bundle subscription request message from the terminal; Determining whether to provide a custom bundle service through the custom bundle join request message; When providing the custom bundle service, including the charge determined for the custom bundle service in a purchase inquiry request message and transmitting it to the terminal; Receiving a purchase inquiry response message from the terminal and confirming whether the user accepts the subscription through the purchase inquiry response message; And a step of including whether to accept the subscription in a user defined bundle subscription response message and transmitting the same to the terminal.

Images