KR20080017245A - Method and apparatus for service delivery and reception through bidirectional channel in digital broadcasting system - Google Patents

Abstract

The present invention relates to a method and apparatus for delivering and receiving a broadcast service through a bidirectional channel in a convergence of a broadcast and mobile communication service (CBMS) system. When the service management (SM) block receives a request message for requesting delivery of service / content through a bidirectional network from a terminal, the service management (SM) block generates an assignment message instructing an accessible bidirectional network to allocate a bidirectional channel for the delivery. And an allocation response message indicating that the bidirectional channel has been allocated from the bidirectional network, and transmitting a response message indicating that the bidirectional channel has been allocated to the terminal. If the acknowledgment message indicating that the terminal agrees to transfer through the bidirectional network after transmitting the response message is received in the service management block, the service application block broadcasts the terminal desired by the notification from the service management block. The service is delivered to the terminal through the bidirectional channel of the bidirectional network.

Description

METHOD AND APPARATUS FOR DELIVERING AND RECEIVING SERVICE OVER INTERACTION CHANNEL IN DIGITAL BROADCASTING SYSTEM}

1 is a block diagram showing the structure of a CBMS system according to a preferred embodiment of the present invention.

2 is a conceptual diagram of service delivery through a bidirectional network according to a first embodiment of the present invention;

3 is a conceptual diagram of service delivery through a bidirectional network according to a second embodiment of the present invention;

4 illustrates a data model of an ESG in accordance with a preferred embodiment of the present invention.

5 is a message flow diagram illustrating a transfer operation over a bidirectional network in accordance with a preferred embodiment of the present invention.

6 is a flow diagram illustrating operation of a network for delivery via a bidirectional network in accordance with a preferred embodiment of the present invention.

7 is a flowchart illustrating an operation of a terminal receiving a service through a bidirectional network according to a preferred embodiment of the present invention.

8 is a message flow diagram illustrating a forwarding operation via a bidirectional network in accordance with another embodiment of the present invention.

9 is a flow diagram illustrating operation of a network for delivery via a bidirectional network in accordance with another embodiment of the present invention.

10 is a flowchart illustrating an operation of a terminal receiving a service through a bidirectional network according to another embodiment of the present invention.

11 is a block diagram showing the structure of a terminal receiver according to a preferred embodiment of the present invention.

The present invention relates to a digital broadcasting system, and more particularly, to a method and apparatus for transmitting and receiving a broadcasting service through a bidirectional channel in a convergence of broadcasting and mobile service (CBMS) system. .

Today, due to the development of communication and broadcasting technology, a broadcast system or a mobile communication system provides a mobile broadcast, and not only a general broadcast service limited to voice and video but also packet data through a broadcast channel. Portable broadcasts that can be transmitted are being discussed. The portable broadcast includes a discovery of a service by a mobile terminal such as a mobile phone, a notebook computer, a personal digital assistant (PDA), etc. that can receive the portable broadcast, a subscription of the service by the mobile terminal, and various services for receiving the service. Providing branch control information, the transmission of the service and the reception of the service by the mobile terminal can be made.

The Open Mobile Alliance (hereinafter referred to as OMA) is one of the organizations that research standards for interoperability of individual mobility solutions, and is mainly responsible for setting various application standards for mobile games and Internet services. Doing. Among the working groups of OMA, especially the sub working group of OMA BAC (Browser and Content) BCAST (Mobile Broadcast), a broadcasting service and a mobile communication service are provided by using a mobile terminal capable of communicating with an interactive network. I'm working on a technique for fusion. In addition, DVB-CBMS (Digital Video Broadcasting-Convergence of Broadcasting and Mobile Service), which is one of the standards for portable broadcasting terminal, also defines a system structure and interface for convergence of broadcasting service and mobile communication service.

In general, when a mobile station leaves the service area of a broadcast network, the mobile station can no longer receive a broadcast service. Therefore, even if the terminal leaves the service area of the broadcast network, there is a need for a solution for continuing the desired broadcast service.

Therefore, the present invention, which was devised to solve the problems of the prior art operating as described above, delivers a broadcast service to a terminal through a bidirectional network even when the terminal is separated from the service area of the broadcast network, and the terminal receives the broadcast service. It provides a method and apparatus.

The present invention provides a method and apparatus for transmitting a service delivery notification through a bidirectional channel in a network to deliver a broadcast service to a terminal through a bidirectional network.

The present invention provides a method and apparatus for transmitting a service delivery request through a bidirectional channel from a terminal to a network in order to deliver a broadcast service to a terminal through a bidirectional network.

According to a preferred embodiment of the present invention, in a method for delivering a service through a bidirectional channel in a digital broadcasting system,

Receiving a request message for requesting service delivery through a bidirectional network from a terminal;

Transmitting an assignment message instructing the terminal to access a bidirectional channel for service delivery to an accessible bidirectional network, and receiving an assignment response message indicating that the bidirectional channel has been allocated from the bidirectional network;

Transmitting a response message indicating that the bidirectional channel is allocated to the terminal;

Transmitting a desired broadcast service to the terminal through the bidirectional channel of the bidirectional network when the terminal receives the confirmation message indicating that the terminal agrees to transfer the service through the bidirectional network after transmitting the response message. Characterized in that it comprises a.

According to a preferred embodiment of the present invention, in a method for receiving a service through a bidirectional channel in a digital broadcasting system,

Transmitting a request message for requesting service delivery through a bidirectional network to a network entity of a broadcasting system;

When the terminal receives a response message from the network entity indicating that the bidirectional channel is allocated by an accessible bidirectional network, transmitting a confirmation message to the network entity indicating that the terminal agrees to transfer the service through the bidirectional network;

And receiving a broadcast service desired by the terminal through the bidirectional channel of the bidirectional network.

In a preferred embodiment of the present invention, in a digital broadcasting system supporting service delivery through a bidirectional channel,

Upon receiving a request message for requesting service delivery through a bidirectional network from a terminal, the terminal transmits an assignment message instructing an accessible bidirectional network to allocate a bidirectional channel for service delivery, and transmits the bidirectional network from the bidirectional network. Receives an allocation response message indicating that a channel has been allocated, transmits a response message indicating that the bidirectional channel has been allocated to the terminal, and indicates that the terminal agrees to transfer the service through the bidirectional network after transmitting the response message. A service management (SM) block receiving a confirmation message;

A service application (SA) for delivering a broadcast service desired by the terminal to the bidirectional network so that the terminal can receive a service desired by the terminal through the bidirectional channel of the bidirectional network by notification of the service management block. It characterized in that it comprises a block.

Hereinafter, with reference to the accompanying drawings will be described in detail the operating principle of the preferred embodiment of the present invention. In the following description of the present invention, detailed descriptions of well-known functions or configurations will be omitted if it is determined that the detailed description of the present invention may unnecessarily obscure the subject matter of the present invention. Terms to be described later are terms defined in consideration of functions in the present invention, and may be changed according to intentions or customs of users or operators. Therefore, the definition should be made based on the contents throughout the specification.

The main subject of the present invention to be described later is to deliver a broadcast service through a bidirectional channel of a bidirectional network for a terminal leaving a broadcast network in a convergence of a broadcast and mobile communication service (CBMS) system. Here, the bidirectional network refers to a cellular mobile communication network capable of exchanging signaling and services through a bidirectional channel between terminals, and according to a Universal Mobile Telecommunications System (UMTS) according to 3GPP (3rd Generation Partnership Project) and 3GPP2. International Mobile Telecommunications (IMT) -2000, Wireless Broadband Internet (WiBro), or Wireless Local Area Network (WLAN). In the present invention, a service may include information different from broadcast content included in one service, or may include only broadcast content.

1 is a block diagram showing the structure of a CBMS system according to a preferred embodiment of the present invention. Here, logical entities that interoperate with each other to achieve the capabilities required for DVB-H (Digital Video Broadcasting-Handheld) based IP data cast (IPDC) are called. Shown. The illustrated entities are shown separately according to major functional differences, and can be located in physically separated servers or in the same server.

Referring to FIG. 1, a content provider 110 generates a content source of a broadcast service and sends the content source to a service application block 120. The service application block 120 aggregates content sources from the content provider 110 and metadata necessary for service configuration to additionally generate a head-end for generating a service data for a specific service. (head-end) application logic, and provides content encoded in a format that can be understood by the terminal through streaming or carousel delivery. In addition, the service application block 120 generates service description metadata used for the electronic service announcement (ESG), operates as an interactive end point for the terminal in conjunction with other service application blocks, and service protection (Service) Protection) function. To this end, the service application block 120 is composed of a number of sub-entities that manage different applications for each service. Each service application entity may be configured to provide IP datacasts.

The service management block (hereinafter referred to as SM) block 130 independently performs functions such as service configuration, resource allocation, and the like between the service application block 120 and the terminal 160. Contains sub-entities that perform. As an example, the service management block 130 is composed of the following four sub-entities that can be independently illustrated.

The service configuration and resource allocation entity is responsible for registration of service applications competing for the bandwidth of the broadcast bearer (ie, one DVB-H IP platform in one DVB transport stream), location (broadcast network topology), service allocation to bandwidth and It has instances associated with service scheduling over time and contention of broadcast bandwidth. The service guide providing application entity collects ESG (metadata information) information from service application entities and may have multiple instances. The security / service protection policy entity is responsible for managing service access to service application entities. Location services An entity provides location services to service applications in an independent manner, in conjunction with a two-way network or Global Positioning System (GPS) system.

The broadcast network 140 is a network for transmitting broadcast service data, which is, for example, a DVB-H system. The bidirectional network 150 generally refers to a cellular mobile communication network such as UMTS according to 3GPP, IMT-2000 according to 3GPP2, WiBro, or WLAN. As another example, the bidirectional network 150 receives information or requests transmitted from the terminal 160. It can be any type of mobile communication network that provides the ability to send a response to an information or request. The broadcast network 140 and the bidirectional network 150 operate as transmission bearers in the CBMS system.

The terminal 160 refers to a user terminal, and refers to a receiver capable of accessing the bidirectional network 150 and receiving a broadcast service from the broadcast network 140. In the CBMS system, the terminal 160 receives service data and signaling information from the broadcast network 140, and communicates the service data and signaling information with the bidirectional network 150 in both directions. As an example, the terminal 160 may include the following sub-entities. That is, the DVB-H receiver is in charge of service reception or signaling through a broadcast network. The interactive adapter is in charge of service reception / transmission or signaling through a bidirectional network. The MM block is responsible for the move procedure. The subscription management block manages rights acquisition, tracks rights acquired for the terminal, and controls the decryption process of the service content. The content consumption block is responsible for the consumption of the service.

The following describes an interface between each entity including the logical entities described above. CBMS-x and Xx are reference points between different functional entities, where CBMS-x is a reference point within the range of IP datacasts for the DVB-H specification, and Xx is an IP datacast for the DVB-H specification. The reference point is outside the range of.

The CBMS-1 interface carries broadcast related signaling, for example, program specific information and service information (PSI / SI) signaling of DVB-H from the broadcast network 140 to the terminal 160, and the CBMS-2 interface Contents such as audio, video, and files are transported from the service application block 120 to the terminal 160. Content flows delivered through the CBMS-2 interface include audio and video (A / V) streams, auxiliary data and files (clips and the like) delivered by the carousel mechanism. Software).

The CBMS-3 interface is a service management block (hereinafter referred to as an electronic service guide (ESG) meta data) through a broadcast network 140 in the form of point-to-multipoint (hereinafter referred to as ptm) transmission. 130 to the terminal 160. The CBMS-4 interface is a point-to-point of access control and electronic service announcement (ESG) metadata for service applications of the service application block 120 between the service management block 130 and the terminal 160. ptp) is used for transmission. In particular, the CBMS-4 interface is used for access control of service delivery through bidirectional channels and for one-to-one delivery of services (such as broadcast streaming and files). The CBMS-5 interface is for a point-to-point transmission service between the service application block 120 and the terminal 160, and a short message service (SMS) and multimedia message in the form of point-to-point transmission through the bidirectional network 150. Transport services such as Multimedia Message Service (MMS). In particular, the CBMS-5 interface is used for one-to-one delivery of services (such as broadcast streaming and files).

The CBMS-6 interface carries configuration parameters, such as the number of services and the allocated bandwidth, between the service management block 130 and the broadcast network 140 for DVB-H transmission. The CBMS-7 interface is used for the declaration of the service application or the description of the service application including content description and metadata between the service application block 120 and the service management block 130. In particular, the CBMS-7 interface is used for reconstructing service delivery and for service delivery from broadcast network 140 to bidirectional network 150.

X-1. X-2 and X-3 interfaces refer to a reference point between a broadcast network and another entity. The X-1 interface is used between the content provider 110 and the service application block 120. The X-1 interface includes content essence and content description / metadata and content control policy. 120). The X-2 interface is used to deliver specific interactions between the bidirectional network 150 and the terminal 160, that is, specific services such as authentication, mobility management, and voice. The X-3 interface is used between the service management block 130 and the bidirectional network 150 to access specific functions available in the bidirectional network, such as subscriber management and billing functions. In particular, the X-4 interface is used to transmit assignment messages for service delivery in a bidirectional network.

In CBMS, some services are delivered through the broadcast network, others are delivered exclusively through the bidirectional network, and some may be retransmitted from the broadcast network via the bidirectional network. To this end, information indicating whether the service can be delivered through the bidirectional network and whether the delivery path of the service has been changed from the broadcast network to the bidirectional network is transmitted to the terminal. In this case, if the terminal is out of the service area of the broadcast network but still belongs to the service area of the bidirectional network, it can be determined whether the service can be continuously received by the information. The information indicating whether a service can be delivered through a bidirectional network and whether the delivery path of the service has been changed to a bidirectional network can be transmitted in addition to a service fragment, a content fragment, an acquisition fragment, or some other fragment of the ESG.

The above description is only representative of the functions of the respective interfaces, and the functions of the respective interfaces are not limited only by the above description.

In the CBMS system, one service management instance is mapped to one IP platform. Therefore, "in one platform" means "in one service management block 130," and another IP platform means another service management block, that is, a service management block belonging to another network.

The following terms simply define terms used in the present specification.

An IP platform is a set of IP flows managed by an organization, and one IP platform may correspond to one service management block. Definitions of ESG providers, service providers, bidirectional networks and broadcast networks can be defined by the system's standard protocols or system designers.

Description of the identifier of each component is as follows.

The IP platform is identified by the IP platform ID. An ESG provider is herein identified by providerURI, or providerID, or a pair of providerURI and providerID, or other parameter according to the definition and description in the system. A service provider is identified herein by a serviceproviderURI, or serviceproviderID, or a pair of serviceproviderURI and serviceproviderID, or other parameter according to the definition and description in the system. The network is identified by the network ID.

Service Management (SM) blocks are identified according to their relationship to the IP platform. As an example, when one SM corresponds to one IP platform, the IP platform ID may be used as the SM identifier. In other cases, a service management block ID that can be set independently of the IP platform ID may be used. In addition, various other methods for identifying the service management block may be used. Examples for identifying the service management block are as follows.

1. If a service provider owns his service management block, the service provider ID is used to identify his service management block. If the service provider is unique within the IP platform, the pair of service provider ID and IP platform ID is used as the identifier of the service management block. If the service provider ID is unique in another range, the service provider ID and the range are used as the SM identifier.

2. If each ESG provider is located in its own service management block, the ESG provider ID is used as the identifier of the service management block. If the ESG provider is unique only within the IP platform, then the pair of ESG provider ID and IP platform ID is used as the identifier of the service management block. If the ESG provider ID is unique within another range, the service provider ID and its range are used as the identifier of the service management block.

3. If one IP platform corresponds to exactly one service management block and different service management blocks cannot share one IP platform, an IP platform ID is used to identify the service management block.

4. Defining a service management block ID for each service management block is the clearest way to identify each service management block. If the identifier of the service management block has a certain range, a pair of the identifier of the service management block and the identifier of the range can be used as the identifier of the service management block.

5. Identification of the service management block follows the structure and description of the system.

Definitions for handover and roaming may be based on changes in the IP platform. If the terminal is in the same IP platform even after moving, this corresponds to the case of handover, and if it is on another IP platform, this corresponds to the case of roaming. Therefore, the IP platform ID is an important parameter for distinguishing handover and roaming. Rules for distinguishing handover from roaming can be extended to bidirectional networks. As already mentioned, the distinction between handover and roaming is based on IP platforms, ESG providers, service providers, service management blocks, IPDC domains, networks or other concepts.

Thus, the definition of mobility is not specified herein. However, embodiments of the present invention may be used in similar systems regardless of the structure and definition of the system. In this case, a clear description of the concept, figures, parameters, etc. of each parameter is made according to the structure and definition of the system. The definition of handover and roaming can be made according to the IP platform, ESG provider, service provider, SM, IPDC domain, network or the like. Thus, in this specification, when relevant parameters (eg, identifiers) are required, all relevant parameters are listed. Thus, in implementing an embodiment of the present invention, all or some of the disclosed parameters may be required, and new parameters may be required. These parameters can be modified, added, removed or replaced according to the final definition of the system.

The system structure, concept, and parameters applied to the embodiment of the present invention may be changed according to the final definition of the system. However, the spirit of the present invention may be employed regardless of such a change and according to the final definition of the system, Modifications can be made within the predictable range of the skilled artisan.

In this specification, two embodiments are disclosed according to a relationship between a bidirectional network and a service management block.

The first embodiment is illustrated in FIG. 2 as a case where a bidirectional network and a broadcast network are managed by the same service management block, and the service management block can directly allocate a bidirectional channel for service delivery. The second embodiment is a case where the bidirectional network is not managed by the service management block of the broadcast network, and the service management block communicates with an administrator of the bidirectional network to obtain a right for service delivery through the bidirectional network. Shown.

2 is a conceptual diagram of service delivery through a bidirectional network according to a first embodiment of the present invention. As shown in FIG. 2, services in the CBMS system 200 are managed by the service management block 210. 230 receives a service through a broadcast network 220 or a bidirectional network 222 belonging to the CBMS system 200. If the bi-directional network 222 is managed by the service management block 210 is considered to belong to the CBMS system 200, it is located in the same IP platform as the broadcast network 220. In this case, the path of service delivery is changed from the broadcast channel of the broadcast network 220 to the bidirectional channel of the bidirectional network 222, and is treated as a kind of handover (hereinafter referred to as broadcast-bidirectional network handover).

3 is a conceptual diagram of service delivery through a bidirectional network according to a second embodiment of the present invention. As shown in FIG. 3, services in the CBMS system 300 are managed by the service management block 310. 330 receives a service through a broadcast network 320 belonging to the CBMS system 300. When the terminal 330 is out of the service area of the broadcast network 320 but exists in the service area of the bidirectional network 322, the terminal 330 receives a service through the bidirectional network 322. Since the bidirectional network 322 does not belong to the CBMS system 300, the service management block 310 may not directly manage the bidirectional network 322. The bidirectional network 322 may exist independently or belong to another CBMS system. The service management block 310 requires the approval of the manager / service management block 312 of the bidirectional network 322 to deliver the service over the bidirectional network 322. In this case, the path of service delivery is changed from the broadcast channel of the broadcast network 220 to the bidirectional channel of the bidirectional network 222 belonging to another IP platform, and is treated as a kind of roaming.

In FIG. 2 and FIG. 3, when the movement of the terminal is performed within the same IP platform or service management block, the handover and the other case are described as roaming. It may be done according to the ESG provider or according to different rules, rather than whether the management blocks are the same. For convenience of description, in the present specification, handover and roaming may be distinguished by changing a service management block mapped to one IP platform. However, a rule for distinguishing roaming and handover may be made according to another definition.

For the above two embodiments, the network may inform the terminal in advance of information indicating whether the path of service delivery can be changed from the broadcast network to the bidirectional network. If the terminal is out of the service area of the broadcast network but is within the service area of the bidirectional network, the terminal may know from the above information whether the desired service can be received. An example of information elements for supporting delivery through a bidirectional network for each service and / or content is shown in Table 1 below.

Item Explanation One Forward over two-way network 0x00: independent Services / content are provided over a two-way network, not for handover or roaming 0x01: handover Services / content are delivered over a bidirectional network to support handover 0x02: roam Services / content are delivered over a two-way network to support roaming 2 Represents a URI that uniquely identifies detailed information about a bidirectional network provider and / or a bidirectional network provider 3 Represents an IP address for a bidirectional network 4 Indicates the port number of the bidirectional network 5 Indicates the entry point of a bidirectional network as a URL 6 Represents an entry point in a two-way network, which can be a URL, phone number, or other related information 7 InteractiveNetworkType 0x01: 3GPP Represents various types of bidirectional networks 0x02: 3GPP2 0x03: WLAN 0x04: WIBRO Other 8 Indicates acquisition criteria information of bidirectional network

At least some of the information elements shown in Table 1 above are used to support service delivery over a bidirectional network.

Information to support delivery over a bidirectional network may be sent via ESG, notification messages or other signaling. The terminal knows whether the service delivery through the bidirectional network can be performed alone, handover or roaming type and the information on the bidirectional network based on the information, and receives the desired service through the bidirectional network Learn about it through ESG. Here, "alone" means a delivery type when a terminal receives a service independently in a bidirectional network without moving from a broadcast network to a bidirectional network. When the information is transmitted through the ESG, the location of the information related to the bidirectional network may be variously determined within the ESG. The following illustrates a transmission location of information according to a preferred embodiment of the present invention with reference to the data model of the ESG.

4 illustrates a data model of an ESG in accordance with a preferred embodiment of the present invention.

Referring to FIG. 4, each block shown represents fragments of ESG data. In other words, the ESG data model includes a service fragment 402, a schedule event fragment 404, a content fragment 406, an acquisition fragment 408, a service bundle fragment 410, a purchase fragment 412, and a purchase. Channel fragment 414.

The service fragment 402 includes a description of the overall service, the schedule event fragment 404 represents the information of the service over time, and the acquisition fragment 408 provides the service access information that must be known in order to receive the service data. The service bundle fragment 410 includes information on a case where multiple services are bundled into one service bundle, and the purchase fragment 412 informs price information for purchasing the service bundle, and a purchase channel fragment. 414 informs the system about which system to use to obtain the right to purchase.

Each fragment of the data model may refer to another fragment and arrows between the fragments indicate the reference relationship. The reference refers to information that a current fragment is associated with its fragment using information transmitted from another fragment. That is, when one service is composed of multiple contents, the service fragment 402 includes only the description of the entire service, for example, the name of the service and the language of the service, and the content itself transmitted through the service. The description is not included, but the service fragment is referred to in the content fragment 406 of the corresponding content. In addition, in order to know various pieces of information necessary for the terminal to receive the service, for example, session information used in a protocol to be transmitted, the information is obtained by receiving and demodulating the acquisition fragment 408 referenced by the service fragment 402. Can get them.

The ESG data is separately transmitted to the terminal using at least one IP (Internet Protocol) stream at a separate time from the data stream. Thus, the service provider can use the ESG data model to provide information before the service is sent that the user should know before receiving the service. By receiving the ESG stream, the terminal acquires information necessary for receiving the services provided by the service provider, and when the user selects a specific service, the terminal uses the obtained information to transmit the data stream. After accessing, you will receive data. Information for the terminal to access the data stream is transmitted through the acquisition fragment 408 as described in FIG.

The ESG data model is bundled in several pieces for each fragment and contained in one container, and each container is regarded as one object in a File Delivery over Unidirectional Transport Protocol (FLUTE) session and transmitted. For the reception of the ESG, the UE accesses an ESG bootstrap FLUTE session that carries the information necessary for ESG transmission, discovers ESG providers, selects one of them, and then accesses an associated ESG access descriptor from the selected ESG provider. ) And receive it. If the service desired by the user exists, the terminal immediately accesses the ESG through the broadcast network according to the ESG access descriptor.

The service ID for each service is specified in the service fragment 402, the IP address is specified in the acquisition fragment 408, and the charging information is specified in the purchase fragment 412. The service ID, transport stream ID, original network ID, cell ID, network ID, and frequency information are transmitted through PSI / SI (Program specific information and Service information), which is control information for a broadcast service.

Among the information for supporting the transmission through the bidirectional network, information related to the bidirectional network may be included in the service fragment 402, the content fragment 406, the acquisition fragment 408, the purchase fragment 412, or another fragment to be transmitted. Can be. As another example, some of the information may be located in one fragment and some of the information may be located in another fragment. For example, type information of delivery through a bidirectional network (hereinafter referred to as delivery type information) is added to the service fragment 402 or the content fragment 406, and other related information is added to the acquisition fragment 412. In this case, an example of the syntax of information for supporting the transmission through the bidirectional network is shown in Table 2 below.

<complex Type name = "delivery over interactive network" minOccurs = "0" maxOccurs = "unbounded" /> <sequence> <elementname = "DeliveryOverInteractiveType" type = "InteractiveDeliveryType"> <element name = "InteractiveEntrypointURL" type = "anyURI" <element name = "InteractiveEntrypoint" type = "anyURI" <element name = "InteractiveNetworkType" type = "InteractiveNetworkType" <element name = "InteractiveNetworkProvider" type = "anyURI"> <element name = "InteractiveNetworkIPAddress" type = "anyURI"> <element name = "InteractiveNetworkPortNumber" type = "anyURI"> <element name = "AcquisitionRef" type = "anyURI"> </ sequence> </ complex type>

In Table 2, information indicating a type of delivery through a bidirectional network (“DeliveryOverInteractiveType” or “InteractiveDeliveryType”, hereinafter referred to as delivery type information) may have bit values as shown in Table 3a below.

beat Explanation DeliveryOverInteractiveType 00 Independent. Services / content are provided over a two-way network, not for handover or roaming. 01 Delivery over bidirectional network is by handover 10 Roaming through bidirectional network is by roaming

When the <Table 3a> is expressed in the form of syntax, it is as follows.

<simpleType name = "DeliveryOverInteractiveType"> <restriction base = "string"> <enumeration value = "Independent" /> <enumeration value = "delivery over interactive network handover" /> <enumeration value = "delivery over interactive network roaming" / > </ restriction> </ simpleType>

Another example of the <Table 3a> in the form of a syntax is shown in the following <Table 3c>.

<complex Type name = "DeliveryOverInteractiveType"> <attribute name = "delivery over interactive network independent" type = "Boolean"> <attribute name = "delivery over interactive network handover" type = "Boolean"> <attribute name = "delivery over interactive network roaming "type =" Boolean "> </ complex type>

The meaning of each attribute of the delivery type information is shown in Table 3d below.

field Explanation delivery over interactive network independent If set to "true", this indicates that the service / content delivery through the bidirectional network is done by itself, and if set to "false" it means that delivery through the bidirectional network is not made by itself. delivery over interactive network handover If set to "true", this indicates that the service / content can be delivered over the bidirectional network by handover. If set to "false", it is not possible to deliver over the bidirectional network by handover. Indicates delivery over interactive network roaming When set to "true", this indicates that service / content can be delivered over a two-way network by roaming; and if set to "false", indicates that delivery over a two-way network is not possible by roaming.

In Table 2, a bidirectional network type (“InteractiveNetworkType”) may be variously used as 3GPP, 3GPP2, WIBRO, WLAN, etc., and thus may be described as shown in Table 4 below.

<simpleType name = "InteractiveNetworkType"> <restriction base = "string"> <enumeration value = "3GPP" /> <enumeration value = "3GPP2" /> <enumeration value = "WLAN" /> <enumeration value = "WIBRO" /> </ restriction> </ simpleType>

The syntaxes of the three types of delivery over the bidirectional network, namely the information related to the delivery over the bidirectional network, according to sole delivery, handover and roaming, are shown in Tables 5a to 5c, respectively.

<complex Type name = "delivery over interactive network independent" minOccurs = "0" maxOccurs = "unbounded" /> <sequence> <element name = "InteractiveEntrypointURL" type = "anyURI" <element name = "InteractiveEntrypoint" type = "anyURI "<element name =" InteractiveNetworkType "type =" InteractiveNetworkType "<element name =" InteractiveNetworkProvider "type =" anyURI "> <element name =" InteractiveNetworkIPAddress "type =" anyURI "> <element name =" InteractiveNetworkPortNumber "type =" anyURI "> <element name =" AcquisitionRef "type =" anyURI "> </ sequence> </ complex type>

<complex Type name = "delivery over interactive network handover" minOccurs = "0" maxOccurs = "unbounded" /> <sequence> <element name = "InteractiveEntrypointURL" type = "anyURI" <element name = "InteractiveEntrypoint" type = "anyURI "<element name =" InteractiveNetworkType "type =" InteractiveNetworkType "<element name =" InteractiveNetworkProvider "type =" anyURI "> <element name =" InteractiveNetworkIPAddress "type =" anyURI "> <element name =" InteractiveNetworkPortNumber "type =" anyURI "> <element name =" AcquisitionRef "type =" anyURI "> </ sequence> </ complex type>

<complex Type name = "delivery over interactive network roaming" minOccurs = "0" maxOccurs = "unbounded" /> <sequence> <element name = "InteractiveEntrypointURL" type = "anyURI" <element name = "InteractiveEntrypoint" type = "anyURI "<element name =" InteractiveNetworkType "type =" InteractiveNetworkType "<element name =" InteractiveNetworkProvider "type =" anyURI "> <element name =" InteractiveNetworkIPAddress "type =" anyURI "> <element name =" InteractiveNetworkPortNumber "type =" anyURI "> <element name =" AcquisitionRef "type =" anyURI "> </ sequence> </ complex type>

Table 6 below shows an example of using different information element names for the three types of delivery through the bidirectional network, namely alone, handover and roaming syntax.

<complex Type name = "delivery over interactive network" minOccurs = "0" maxOccurs = "unbounded" /> <sequence> <element name = "IndependentInteractiveEntrypointURL" type = "anyURI" <element name = "IndependentInteractiveEntrypoint" type = "anyURI" <element name = "IndependentInteractiveNetworkType" type = "InteractiveNetworkType" <element name = "IndependentInteractiveNetworkProvider" type = "anyURI"> <element name = "IndependentInteractiveNetworkIPAddress" type = "anyURI"> <element name = "IndependentInteractiveNetworkPortNumber" type = "anyURI" > <element name = "IndependentAcquisitionRef" type = "anyURI"> <element name = "HandoverInteractiveEntrypointURL" type = "anyURI" <element name = "HandoverInteractiveEntrypoint" type = "anyURI" <element name = "HandoverInteractiveNetworkType" type = "InteractiveNetworkType" <element name = "HandoverInteractiveNetworkProvider" type = "anyURI"> <element name = "HandoverInteractiveNetworkIPAddress" type = "anyURI"> <element name = "HandoverInteractiveNetworkPort Number "type =" anyURI "> <element name =" HandoverAcquisitionRef "type =" anyURI "> <element name =" RoamingInteractiveEntrypointURL "type =" anyURI "<element name =" RoamingInteractiveEntrypoint "type =" anyURI "<element name =" RoamingInteractiveNetworkType "type =" InteractiveNetworkType "<element name =" RoamingInteractiveNetworkProvider "type =" anyURI "> <element name =" RoamingInteractiveNetworkIPAddress "type =" anyURI "> <element name =" RoamingInteractiveNetworkPortNumber "type =" anyURI "> <element name = "RoamingAcquisitionRef" type = "anyURI"> </ sequence> </ complex type>

An example of the syntax of an acquisition fragment that includes information related to a bidirectional network for supporting delivery over a bidirectional network is shown in Table 7a below. Table 7a shows a format in which information related to the bidirectional network is added to a session description base type information element of an acquisition fragment. The session description base type is an information element included in an acquisition fragment for a session description.

<schema xmlns: esg2 = "urn: dvb: ipdc: esg: 2007" xmlns: esg = "urn: dvb: ipdc: esg: 2005" xmlns = "http://www.w3.org/2001/XMLSchema" targetNamespace = "urn: dvb: ipdc: esg: 2007" elementFormDefault = "qualified" attributeFormDefault = "unqualified"> <import namespace = "urn: dvb: ipdc: esg: 2005" schemaLocation = "dvb_ipdc_esg.xsd" /> <complexType name = "InteractiveAccessType"> <complexContent> <extension base = "esg: SessionDescriptionBaseType"> <choice> <sequence> <element name = "SDP" type = "esg: SDPType" /> <element name = "InteractiveEntrypointURL" type = " anyURI "minOccurs =" 0 "/> <element name =" DeliveryOverInteractiveType "type =" InteractiveDeliveryType "> <element name =" InteractiveNetworkType "type =" InteractiveNetworkType "</ sequence> <element name =" InteractiveEntrypointURL "type =" anyURI " /> <elementname = "DeliveryOverInteractiveType" type = "InteractiveDeliveryType"> <element name = "InteractiveNetworkType" type = "InteractiveNetworkType" </ choice> </ extension > </ complexContent> </ complexType> </ schema>

In the ESG data model, the terminal performs service acquisition using an acquisition fragment. Service access parameters required for service acquisition are specified in a Session Description Protocol (SDP) file, which is embedded in an acquisition fragment to contain the service access parameters or to establish a FLUTE session. Points to a separate file containing the service access parameters carried over the external band via. The service access parameters included in the SDP file (InlinedSDPType) or obtained by referring to the SDP file (SDPRefType) are included in a Session Description element in an acquisition fragment, and the terminal includes two of the session description information elements. The session description information element is interpreted by classifying branches, that is, InlinedSDPType or SDPRefType. The type of the session description information element is defined by the session description base type information element. Table 7b shows the syntax of the session description base type.

<complexType name = "SessionDescriptionBaseType" abstract = "true" /> <complexType name = "InlinedSDPType"> <complexContent> <extension base = "esg: SessionDescriptionBaseType"> <sequence> <element name = "SDP" type = "esg: SDPType "/> <element name =" AssociatedDeliveryProcedure "type =" anyURI "minOccurs =" 0 "/> </ sequence> </ extension> </ complexContent> </ complexType> <complexType name =" SDPRefType "> <complexContent> <extension base = "esg: SessionDescriptionBaseType"> <sequence> <element name = "SDPStream" type = "esg: SDPType" /> <element name = "SDPURI" type = "anyURI" /> <element name = "AssociatedDeliveryProcedure" type = "anyURI" minOccurs = "0" /> </ sequence> </ extension> </ complexContent> </ complexType>

In the present invention, an additional definition of a session description base type is used for delivery of a service through a transmission channel other than DVB-H.

Table 8 below shows an example of using different information element names for the session description base type information element of the acquisition fragment according to the preferred embodiment of the present invention. Table 8 is divided into <Table 8a> to <Table 8c> for convenience.

<schema xmlns: esg2 = "urn: dvb: ipdc: esg: 2007" xmlns: esg = "urn: dvb: ipdc: esg: 2005" xmlns = "http://www.w3.org/2001/XMLSchema" targetNamespace = "urn: dvb: ipdc: esg: 2007" elementFormDefault = "qualified" attributeFormDefault = "unqualified"> <import namespace = "urn: dvb: ipdc: esg: 2005" schemaLocation = "dvb_ipdc_esg.xsd" /> <complexType name = "IndependentInteracrivetAccessType"> <complexContent> <extension base = "esg: SessionDescriptionBaseType"> <choice> <sequence> <element name = "SDP" type = "esg: SDPType" /> <element name = "IndependentInteractiveEntrypointURL" type = " anyURI "minOccurs =" 0 "/> <element name =" IndependentInteractiveNetworkType "type =" InteractiveNetworkType "</ sequence> <element name =" IndependentInteractiveEntrypointURL "type =" anyURI "minOccurs =" 0 "/> <element name =" IndependentInteractiveNetworkType "type =" InteractiveNetworkType "</ choice> </ extension> </ complexContent> </ complexType>

<complexType name = "HandoverInteracrivetAccessType"> <complexContent> <extension base = "esg: SessionDescriptionBaseType"> <choice> <sequence> <element name = "SDP" type = "esg: SDPType" /> <element name = "HandoverInteractiveEntrypointURL" type = "anyURI" minOccurs = "0" /> <element name = "HandoverInteractiveNetworkType" type = "InteractiveNetworkType" </ sequence> <element name = "HandoverInteractiveEntrypointURL" type = "anyURI" minOccurs = "0" /> <element name = "HandoverInteractiveNetworkType" type = "InteractiveNetworkType" </ choice> </ extension> </ complexContent> </ complexType>

<complexType name = "RoamingInteracrivetAccessType"> <complexContent> <extension base = "esg: SessionDescriptionBaseType"> <choice> <sequence> <element name = "SDP" type = "esg: SDPType" /> <element name = "RoamingInteractiveEntrypointURL" type = "anyURI" minOccurs = "0" /> <element name = "RoamingInteractiveNetworkType" type = "InteractiveNetworkType" </ sequence> <element name = "RoamingInteractiveEntrypointURL" type = "anyURI" minOccurs = "0" /> <element name = "RoamingInteractiveNetworkType" type = "InteractiveNetworkType" </ choice> </ extension> </ complexContent> </ complexType> </ schema>

In the above, the case in which the information related to the transmission through the bidirectional network is transmitted through the ESG has been described. However, the information may be transmitted to the terminal through a notify message or other means. The notification message here is for indicating whether there is a change in the service and the system. On the basis of the above information, the terminal knows whether service delivery through the bidirectional network can be performed in a handover or roaming type, and information on the bidirectional network, and about a method for receiving a desired service through the bidirectional network. Get to know through ESG.

5 is a message flow diagram illustrating a delivery operation through a bidirectional network according to a preferred embodiment of the present invention. Here, an embodiment in the case where the information related to the transmission is notified to the terminal from the network.

Referring to FIG. 5, the terminal receives and stores information related to delivery through a bidirectional channel through an ESG or a notify message. [1] As an example, the format of the notification message is shown in Table 9 below.

designation Explanation Notify ID for Service delivery over interactive network Identifier for the notification message Service_ID Service identifier in the ESG ESG provider URL URL to the ESG provider ESG provider ID Identifier for ESG Provider IP address IP address of the service IP platform ID IP platform identifier Service_id Service Identifier in PSI / SI Transport stream_id Transport stream identifier Original network_id Original network identifier Cell_id Cell identifier to which the terminal belongs Network_id Network identifier for current network Service delivery over interactive network independent Is it possible to 'service delivery through two-way network' alone? Interactive network provider (for independent) Provider of bidirectional networks for exclusive delivery Interactive Entry point URL (for independent) URL to entry point in bidirectional network for exclusive delivery Interactive network phone number (for independent) Phone number in bidirectional network for exclusive delivery Interactive network IP address (for independent) IP address of the bidirectional network for exclusive delivery Interactive network port number (for independent) Port number for bidirectional network for exclusive delivery Acquisition reference (for independent) Acquisition Criteria for Bidirectional Networks for Sole Delivery The type of the interactive network (for independent) Type of bidirectional network for single delivery (3GPP, 3GPP2, WIBRO, WLAN, etc.) Handover possibility for Service delivery over interactive network Is handover possible for 'service delivery over a two-way network'? Interactive network provider (for handover) Bidirectional network provider for handover Interactive Entry point URL (for handover) URL to entry point in bidirectional network for handover Interactive network phone number (for handover) Phone number in bidirectional network for handover Interactive network IP address (for handover) IP address of the bidirectional network for handover Interactive network port number (for handover) Port number of the bidirectional network for handover Acquisition reference (for handover) Acquisition Criteria Information of Bidirectional Network for Handover The type of the interactive network (for handover) Bidirectional network type for handover (3GPP, 3GPP2, WIBRO, WLAN, etc.) Roaming possibility for Service delivery over interactive network Is it possible to roam for 'service delivery over a two-way network'? Interactive network provider (for roaming) Provider of bidirectional networks for roaming Interactive Entry point URL (for roaming) URL to entry point in bidirectional network for roaming Interactive network phone number (for roaming) Phone number in the bidirectional network for roaming Interactive network IP address (for roaming) IP address of the bidirectional network for roaming Interactive network port number (for roaming) Port number of the bidirectional network for roaming Acquisition reference (for roaming) Acquisition Criteria Information for Bidirectional Networks for Roaming The type of the interactive network (for roaming) Bidirectional network type for roaming (3GPP, 3GPP2, WIBRO, WLAN, etc.) Charging (optional) Billing information for service delivery over a two-way network Frequency Frequency of bidirectional network Modulation Modulation method Coding Coding method

When it is determined that service consumption through the broadcast network is not possible, the terminal transmits a request message for requesting 'delivery through a bidirectional channel' to the service management block of the network. As an example, the format of the request message is shown in Table 10 below.

designation Explanation Request ID for Service delivery over interactive network Identifier of the request message User ID User identifier Home network ID Identifies the home network to which the user belongs Service_ID Service identifier in the ESG ESG provider URL URL of the ESG provider ESG provider ID Identifier of ESG Provider IP address IP address of the service IP platform ID IP platform identifier Service_id Service Identifier in PSI / SI Transport stream_id Transport stream identifier Original network_id Original network identifier Cell_id Cell identifier to which the terminal belongs Network_id Network identifier representing the current network Service delivery over interactive network independent requirement UE requires exclusive delivery of service through bidirectional network Interactive network provider (for independent) Provider of bidirectional networks for exclusive delivery Interactive network IP address (for independent) IP address of the bidirectional network for exclusive delivery Interactive network port number (for independent) Port number for bidirectional network for exclusive delivery The type of the interactive network (for independent) Type of bidirectional network for single delivery (3GPP, 3GPP2, WIBRO, WLAN, etc.) Handover requirement for Service delivery over interactive network UE requests handover for service delivery through bidirectional network Interactive network provider (for handover) Provider of bidirectional network for handover Interactive Entry point URL (for handover) URL to entry point in bidirectional network for handover Interactive network phone number (for handover) Phone number in bidirectional network for handover Interactive network IP address (for handover) IP address of the bidirectional network for handover Interactive network port number (for handover) Port number of the bidirectional network for handover The type of the interactive network (for handover) Bidirectional network type for handover (3GPP, 3GPP2, WIBRO, WLAN, etc.) Roaming requirement for Service delivery over interactive network Terminal requires roaming for service delivery through bidirectional network Interactive network provider (for roaming) Provider of bidirectional networks for roaming Interactive Entry point URL (for roaming) URL to entry point in bidirectional network for roaming Interactive network phone number (for roaming) Phone number in the bidirectional network for roaming Interactive network IP address (for roaming) IP address of the bidirectional network for roaming Interactive network port number (for roaming) Port number of the bidirectional network for roaming The type of the interactive network (for roaming) Bidirectional network type for roaming (3GPP, 3GPP2, WIBRO, WLAN, etc.)

Upon receipt of the request message, the service management block sends an allocation message to the bidirectional network to instruct the bidirectional network to allocate a bidirectional channel for service delivery [3] and the bidirectional channel is allocated from the bidirectional network. Receive an allocation response message indicating that a message has been sent. Steps [3, 4] is a handover or roaming procedure according to the relationship between the service management block and the bidirectional network. In this case, the authentication procedure between the service management block and the bidirectional network may be required.

As an example, formats of the assignment message and the assignment response message are shown in Tables 11 and 12 below.

designation Explanation Allocation ID for Service delivery over interactive network Identifier of the assignment message User ID User identifier Home network ID Identifies the home network to which the user belongs Service delivery over interactive network independent requirement UE requires exclusive delivery of service through bidirectional network Handover requirement for Service delivery over interactive network UE requests handover for service delivery through bidirectional network Roaming requirement for Service delivery over interactive network Terminal requires roaming for service delivery through bidirectional network Bandwidth requirement Bandwidth Required for Service Delivery Service_ID Service identifier in the ESG ESG provider URL URL of the ESG provider ESG provider ID Identifier of ESG Provider IP address IP address of the service IP platform ID IP platform identifier Service_id Service Identifier in PSI / SI Transport stream_id Transport stream identifier Original network_id Original network identifier Cell_id Cell identifier to which the terminal belongs Network_id Network identifier representing the current network Service provider ID Identifier of the service provider

designation Explanation Allocation response ID for Service delivery over interactive network Identifier of the assignment response message User ID User identifier Home network ID Identifies the home network to which the user belongs Interactive network provider (for independent) Provider of bidirectional networks for exclusive delivery Interactive Entry point URL (for independent) URL to entry point in bidirectional network for exclusive delivery Interactive network phone number (for independent) Phone number in bidirectional network for exclusive delivery Interactive network IP address (for independent) IP address of the bidirectional network for exclusive delivery Interactive network port number (for independent) Port number for bidirectional network for exclusive delivery Acquisition reference (for independent) Acquisition Criteria for Bidirectional Networks for Sole Delivery The type of the interactive network (for independent) Type of bidirectional network for single delivery (3GPP, 3GPP2, WIBRO, WLAN, etc.) Interactive network provider (for handover) Provider of bidirectional network for handover Interactive Entry point URL (for handover) URL to entry point in bidirectional network for handover Interactive network phone number (for handover) Phone number in bidirectional network for handover Interactive network IP address (for handover) IP address of the bidirectional network for handover Interactive network port number (for handover) Port number of the bidirectional network for handover The type of the interactive network (for handover) Bidirectional network type for handover (3GPP, 3GPP2, WIBRO, WLAN, etc.) Interactive network provider (for roaming) Provider of bidirectional networks for roaming Interactive Entry point URL (for roaming) URL to entry point in bidirectional network for roaming Interactive network phone number (for roaming) Phone number in the bidirectional network for roaming Interactive network IP address (for roaming) IP address of the bidirectional network for roaming Interactive network port number (for roaming) Port number of the bidirectional network for roaming The type of the interactive network (for roaming) Bidirectional network type for roaming (3GPP, 3GPP2, WIBRO, WLAN, etc.) Bandwidth Bandwidth allocated for service delivery Service_ID Service identifier of the ESG ESG provider URL URL of the ESG provider ESG provider ID Identifier of ESG Provider IP address IP address of the service IP platform ID IP platform identifier Service_id Service identifier of the PSI / SI Transport stream_id Transport stream identifier Original network_id Original network identifier Cell_id Cell identifier to which the terminal belongs Network_id Network identifier representing the current network Service provider ID Identifier of the service provider Charging Billing information for service delivery over a two-way network Acquisition reference Acquisition Criteria Information for Bidirectional Networks Frequency Frequency of bidirectional network Modulation Modulation method Coding Coding method

In the assignment response message of Table 12, handover related information such as a provider, an IP address, a port number, and a bidirectional network type of a bidirectional network for handover, the handover is required in the assignment message of <Table 11>. Included in the case. Also, in the assignment response message, roaming related information such as a provider of an interactive network for roaming, an IP address, a port number, and a bidirectional network type are included when roaming is requested in the assignment message of Table 11.

After the bidirectional channel is allocated in the bidirectional network, the service management block transmits a response message to the terminal informing that the transmission is possible through the bidirectional channel. After transmitting the response message, if a confirmation message indicating that the terminal agrees to transfer through the bidirectional channel is received [6], the service / content transfer through the bidirectional channel of the bidirectional network is performed in step 502 or 504. Is done. The process 502 or 504 is selected by standard protocol or designer's intention.

As an example, the formats of the response message and the confirmation message are shown in Tables 13 and 14 below.

designation Explanation Response ID for Service delivery over interactive network Identifier of the response message User ID User identifier Home network ID Identifies the home network to which the user belongs Interactive network provider (for independent) Provider of bidirectional networks for exclusive delivery Interactive Entry point URL (for independent) URL to entry point in bidirectional network for exclusive delivery Interactive network phone number (for independent) Phone number in bidirectional network for exclusive delivery Interactive network IP address (for independent) IP address of the bidirectional network for exclusive delivery Interactive network port number (for independent) Port number for bidirectional network for exclusive delivery Acquisition reference (for independent) Acquisition Criteria for Bidirectional Networks for Sole Delivery The type of the interactive network (for independent) Type of bidirectional network for single delivery (3GPP, 3GPP2, WIBRO, WLAN, etc.) Interactive network provider (for handover) Provider of bidirectional network for handover Interactive Entry point URL (for handover) URL to entry point in bidirectional network for handover Interactive network phone number (for handover) Phone number in bidirectional network for handover Interactive network IP address (for handover) IP address of the bidirectional network for handover Interactive network port number (for handover) Port number of the bidirectional network for handover The type of the interactive network (for handover) Bidirectional network type for handover (3GPP, 3GPP2, WIBRO, WLAN, etc.) Interactive network provider (for roaming) Provider of bidirectional networks for roaming Interactive Entry point URL (for roaming) URL to entry point in bidirectional network for roaming Interactive network phone number (for roaming) Phone number in the bidirectional network for roaming Interactive network IP address (for roaming) IP address of the bidirectional network for roaming Interactive network port number (for roaming) Port number of the bidirectional network for roaming The type of the interactive network (for roaming) Bidirectional network type for roaming (3GPP, 3GPP2, WIBRO, WLAN, etc.) Bandwidth Bandwidth allocated for service delivery Service_ID Service identifier in the ESG ESG provider URL URL of the ESG provider ESG provider ID Identifier of ESG Provider IP address IP address of the service IP platform ID IP platform identifier Service_id Service identifier of the PSI / SI Transport stream_id Transport stream identifier Original network_id Original network identifier Cell_id Cell identifier to which the terminal belongs Network_id Network identifier representing the current network Service provider ID Identifier of the service provider Charging Billing information for service delivery over a two-way network Acquisition reference Acquisition Criteria Information for Bidirectional Networks Frequency Frequency of bidirectional network Modulation Modulation method Coding Coding method

designation Explanation Confirm ID for Service delivery over interactive network Identifier of the confirmation message User ID User identifier Home network ID Identifies the home network to which the user belongs Agreed or not Does the terminal agree to receive the service over the bidirectional network? Interactive network provider (for independent) Provider of bidirectional networks for exclusive delivery Interactive Entry point URL (for independent) URL to entry point in bidirectional network for exclusive delivery Interactive network phone number (for independent) Phone number in bidirectional network for exclusive delivery Interactive network IP address (for independent) IP address of the bidirectional network for exclusive delivery Interactive network port number (for independent) Port number for bidirectional network for exclusive delivery Acquisition reference (for independent) Acquisition Criteria for Bidirectional Networks for Sole Delivery The type of the interactive network (for independent) Type of bidirectional network for single delivery (3GPP, 3GPP2, WIBRO, WLAN, etc.) Interactive network provider (for handover) Provider of bidirectional network for handover Interactive Entry point URL (for handover) URL to entry point in bidirectional network for handover Interactive network phone number (for handover) Phone number in bidirectional network for handover Interactive network IP address (for handover) IP address of the bidirectional network for handover Interactive network port number (for handover) Port number of the bidirectional network for handover The type of the interactive network (for handover) Bidirectional network type for handover (3GPP, 3GPP2, WIBRO, WLAN, etc.) Interactive network provider (for roaming) Provider of bidirectional networks for roaming Interactive Entry point URL (for roaming) URL to entry point in bidirectional network for roaming Interactive network phone number (for roaming) Phone number in the bidirectional network for roaming Interactive network IP address (for roaming) IP address of the bidirectional network for roaming Interactive network port number (for roaming) Port number of the bidirectional network for roaming The type of the interactive network (for roaming) Bidirectional network type for roaming (3GPP, 3GPP2, WIBRO, WLAN, etc.) Bandwidth Bandwidth allocated for service delivery Service_ID Service identifier in the ESG ESG provider URL URL of the ESG provider ESG provider ID Identifier of ESG Provider IP address IP address of the service IP platform ID IP platform identifier Service_id Service Identifier in PSI / SI Transport stream_id Transport stream identifier Original network_id Original network identifier Cell_id Identifier of the cell to which the terminal belongs Network_id Network identifier representing the current network Service provider ID Identifier of the service provider Charging Billing information for service delivery over a two-way network Acquisition reference Acquisition Criteria Information for Bidirectional Networks Frequency Frequency of bidirectional network Modulation Modulation method Coding Coding method

In step 502, if the service management block delivers an inform message requesting delivery through a bidirectional channel to the service application block, [7-1] service / content is performed by the CBMS-5 between the service application block and the terminal. Is transmitted directly to the terminal through the bidirectional network, i.e. without passing through the service management block. [8-1]

In step 504, if the service management block delivers a notification message requesting delivery through a bidirectional channel to the service application block, [7-2] the service desired by the terminal is transmitted to the CBMS-7 between the service application block and the service management block. By the CBMS-4 between the service management block and the terminal, and then to the terminal through the allocated bidirectional channel of the bidirectional network.

As an example, the format of the notification message used in step 502 is shown in Table 15 below, and the format of the notification message used in step 504 is shown in Table 16 below.

designation Explanation Inform for Service delivery over interactive network Identifier of the notification message User ID User identifier Home network ID Identifies the home network to which the user belongs Interactive network provider (for independent) Provider of bidirectional networks for exclusive delivery Interactive Entry point URL (for independent) URL to entry point in bidirectional network for exclusive delivery Interactive network phone number (for independent) Phone number in bidirectional network for exclusive delivery Interactive network IP address (for independent) IP address of the bidirectional network for exclusive delivery Interactive network port number (for independent) Port number for bidirectional network for exclusive delivery Acquisition reference (for independent) Acquisition Criteria for Bidirectional Networks for Sole Delivery The type of the interactive network (for independent) Type of bidirectional network for single delivery (3GPP, 3GPP2, WIBRO, WLAN, etc.) Interactive network provider (for handover) Provider of bidirectional network for handover Interactive Entry point URL (for handover) URL to entry point in bidirectional network for handover Interactive network phone number (for handover) Phone number in bidirectional network for handover Interactive network IP address (for handover) IP address of the bidirectional network for handover Interactive network port number (for handover) Port number of the bidirectional network for handover The type of the interactive network (for handover) Bidirectional network type for handover (3GPP, 3GPP2, WIBRO, WLAN, etc.) Interactive network provider (for roaming) Provider of bidirectional networks for roaming Interactive Entry point URL (for roaming) URL to entry point in bidirectional network for roaming Interactive network phone number (for roaming) Phone number in the bidirectional network for roaming Interactive network IP address (for roaming) IP address of the bidirectional network for roaming Interactive network port number (for roaming) Port number of the bidirectional network for roaming The type of the interactive network (for roaming) Bidirectional network type for roaming (3GPP, 3GPP2, WIBRO, WLAN, etc.) Bandwidth Bandwidth allocated for service delivery Service_ID Service identifier in the ESG ESG provider URL URL of the ESG provider ESG provider ID Identifier of ESG Provider IP address IP address of the service IP platform ID IP platform identifier Service_id Service Identifier in PSI / SI Transport stream_id Transport stream identifier Original network_id Original network identifier Cell_id Cell identifier to which the terminal belongs Network_id Network identifier Service provider ID Identifier of the service provider Frequency Frequency of bidirectional network Modulation Modulation method Coding Coding method

designation Explanation Inform ID for Service delivery over interactive network Identifier of the notification message User ID User identifier Home network ID Identifies the home network to which the user belongs Service management ID Identifies the SM Service management IP address SM's IP Address ESG provider URL URL of the ESG provider ESG provider ID Identifier of ESG Provider Interactive network provider (for independent) Provider of bidirectional networks for exclusive delivery Interactive Entry point URL (for independent) URL to entry point in bidirectional network for exclusive delivery Interactive network phone number (for independent) Phone number in bidirectional network for exclusive delivery Interactive network IP address (for independent) IP address of the bidirectional network for exclusive delivery Interactive network port number (for independent) Port number for bidirectional network for exclusive delivery Acquisition reference (for independent) Acquisition Criteria for Bidirectional Networks for Sole Delivery The type of the interactive network (for independent) Type of bidirectional network for single delivery (3GPP, 3GPP2, WIBRO, WLAN, etc.) Interactive network provider (for handover) Provider of bidirectional network for handover Interactive Entry point URL (for handover) URL to entry point in bidirectional network for handover Interactive network phone number (for handover) Phone number in bidirectional network for handover Interactive network IP address (for handover) IP address of the bidirectional network for handover Interactive network port number (for handover) Port number of the bidirectional network for handover The type of the interactive network (for handover) Type of bidirectional network for handover (3GPP, 3GPP2, WIBRO, WLAN, etc.) Interactive network provider (for roaming) Provider of bidirectional networks for roaming Interactive Entry point URL (for roaming) URL to entry point in bidirectional network for roaming Interactive network phone number (for roaming) Phone number in the bidirectional network for roaming Interactive network IP address (for roaming) IP address of the bidirectional network for roaming Interactive network port number (for roaming) Port number of the bidirectional network for roaming The type of the interactive network (for roaming) Bidirectional network type for roaming (3GPP, 3GPP2, WIBRO, WLAN, etc.) Bandwidth Bandwidth allocated for service delivery Service_ID Service identifier in the ESG ESG provider URL URL of the ESG provider ESG provider ID Identifier of ESG Provider IP address IP address of the service IP platform ID IP platform identifier Service_id Service Identifier in PSI / SI Transport stream_id Transport stream identifier Original network_id Original network identifier Cell_id Cell identifier to which the terminal belongs Network_id Network identifier Service provider ID Identifier of the service provider Frequency Frequency of bidirectional network Modulation Modulation method Coding Coding method

The above tables disclose a number of information fields that can be included in messages used for service delivery over a bidirectional network. However, at least one of the information fields may be included in each corresponding message according to a standard protocol or a system selection.

6 is a flowchart illustrating the operation of a network for delivery via a bidirectional network according to a preferred embodiment of the present invention. Here, an embodiment in the case where the information related to the transfer from the network to the terminal via the bidirectional network is shown.

Referring to FIG. 6, in step 602, a network entity in a CBMS system, such as a service management block, notifies the terminal of information related to delivery through a bidirectional network using an ESG, a notification message, or other signaling. If a request message for requesting the terminal to deliver the desired service is received from the terminal in step 604, the network entity performs an authentication procedure in step 606 if necessary, and in step 608 a bidirectional channel for delivery of the desired service. Send an assignment message to the bidirectional network to indicate that it should be allocated. For example, if the service delivery information or the bidirectional network information indicates roaming, an authentication procedure is performed in step 606.

If an allocation response message reporting that the bidirectional channel is allocated in step 610 is received from the bidirectional network, in step 612, the network entity transmits a response message indicating that the bidirectional channel is allocated to the terminal, and in step 614, the terminal responds to the response message. Receive a confirmation message indicating that this bidirectional channel has been recognized. Since the confirmation message includes consent information indicating whether the terminal has agreed to the reception of the service through the bidirectional network, in step 616, the network entity agrees to the reception of the service through the bidirectional network according to the agreement information. In one case, the process proceeds to step 618 or 622, otherwise, the operation ends. Proceeding to step 618 or 622 is a matter of standard protocol or system choice.

In step 618, the service management block in the CBMS system delivers a notification message requesting the service application block to deliver the service through a bidirectional channel. Accordingly, in step 620, the service application block delivers the service / content requested by the terminal to the bidirectional network, and the service / content is delivered from the bidirectional network to the terminal through the assigned bidirectional channel.

In step 622, the service management block in the CBMS system delivers a notification message requesting service delivery through the bidirectional channel to the service application block. Accordingly, in step 624, the service application block delivers the service / content desired by the terminal to the service management block, and in step 626, the service management block delivers the service / content to the terminal through the assigned bidirectional channel of the bidirectional network. .

7 is a flowchart illustrating an operation of a terminal receiving a service through a bidirectional network according to a preferred embodiment of the present invention. Here, an embodiment in which information related to service delivery is notified to a terminal from a network is illustrated.

Referring to FIG. 7, in step 702, a UE receives information related to delivery through a bidirectional network from a network entity in a CBMS system through an ESG, a notification message, or other signaling. If it is determined in step 704 that the service cannot be received through the broadcast network, in step 706, the terminal transmits a request message to the network entity requesting delivery of a desired service through the bidirectional network.

In step 708, when receiving a response message indicating that the transfer is possible through the bidirectional network from the network entity, in step 710, the terminal determines whether to agree to the transfer through the bidirectional network. The determination in step 710 is made according to preset information or a user's selection. As an example, the terminal presents a message indicating that a cost is added to the delivery of a service through a bidirectional network, required billing information, etc. to the user through a screen, and inquires whether the user agrees to deliver the service through the bidirectional network. Generate consent information according to the selection.

If the user does not agree to the service delivery through the two-way network, in step 716, a confirmation message including consent information set to 'Not' is transmitted to the network entity, and the operation ends. On the other hand, if the user agrees to the service delivery through the bidirectional network, in step 712, the terminal transmits a confirmation message including consent information set to 'Agree' to the network entity, and in step 714 to the response message Receive the desired service / content from a bidirectional network over the bidirectional channel indicated by.

Hereinafter, an embodiment of a case where information related to delivery through a bidirectional network is not transmitted to the terminal in advance. In this case, the terminal does not know in advance whether the desired service can be delivered through the bidirectional network. Therefore, after making a request to the terminal, the network checks whether the service can be delivered to the terminal through a bidirectional network, and if not, transmits a failure response to the terminal. If possible, the subsequent procedure is similar to that described above.

8 is a message flow diagram illustrating a transfer operation through a bidirectional network according to another embodiment of the present invention. Here, an embodiment in which the information related to the transmission from the network to the terminal via the bidirectional network is not shown.

Referring to FIG. 8, when it is determined that service consumption is not possible through a broadcast network, the terminal transmits a request message for requesting 'service delivery through a bidirectional channel' to a service management block of the network. One] When the service management block receives the request message, the service management block determines whether the terminal can deliver a desired service to the terminal through a bidirectional network, and performs process 802 or 804 according to the confirmation result. If delivery through the bidirectional network is not possible, a failure response message is transmitted to the terminal in step 802. [2] On the other hand, if delivery through a bidirectional network is possible, step 804 is performed.

In step 804, the service management block performs an authentication procedure with the bidirectional network if necessary, and transmits an allocation message to the bidirectional network to instruct the bidirectional network to allocate the bidirectional channel for the desired service. [3] Receive an allocation response message indicating that the allocation of the bidirectional channel is completed from the bidirectional network. Steps [3, 4] is a handover or roaming procedure according to the relationship between the service management block and the bidirectional network. In this case, the authentication procedure between the service management block and the bidirectional network may be required.

After the bidirectional channel is allocated in the bidirectional network, the service management block transmits a response message to the terminal informing that the transmission is possible through the bidirectional channel. After transmitting the response message, if a confirmation message is received from the terminal [6], the service / content is delivered through the bidirectional channel of the bidirectional network in step 806 or 808. The process 806 or 808 is selected by standard protocol or designer's intention.

In step 806, if the service management block delivers an inform message requesting service delivery through a bidirectional channel to the service application block, [7-1] service / service is performed by the CBMS-5 between the service application block and the terminal. The content is delivered directly to the terminal via the bidirectional network, i.e. without passing through the service management block. [8-1]

In step 808, if the service management block delivers a notification message requesting service delivery through a bidirectional channel to the service application block, [7-2] the service / content desired by the terminal is a CBMS between the service application block and the service management block. [7-2], and then the CBMS-4 between the service management block and the terminal to the terminal through the allocated bidirectional channel of the bidirectional network.

9 is a flowchart illustrating an operation of a network for delivery through a bidirectional network according to another embodiment of the present invention. Here, an embodiment in the case that the information related to the transmission from the network to the terminal is not shown.

Referring to FIG. 9, when a request message for requesting a terminal to deliver a desired service is received from a terminal through a bidirectional network in step 902, the network entity determines whether delivery through a bidirectional network is possible for the terminal. The determination in step 904 takes into account various factors such as whether the terminal can use the bidirectional network, whether there is an agreement for service delivery between the CBMS system and the bidirectional network, and whether the terminal can use the service delivery through the bidirectional network. Can be done. If delivery via the bidirectional network is possible, the process proceeds to step 906, otherwise, the operation ends.

In step 906, the network entity performs an authentication procedure if necessary, and in step 908, the network entity transmits an assignment message to the bidirectional network to instruct to allocate a bidirectional channel for delivery of the desired service. If an allocation response message reporting that the bidirectional channel is allocated in step 910 is received from the bidirectional network, in step 912, the network entity transmits a response message indicating that the bidirectional channel is allocated to the terminal, and in step 914 the terminal responds to the response message. Receive a confirmation message indicating that this bidirectional channel has been recognized. Since the confirmation message includes consent information indicating whether the terminal has agreed to the reception of the service through the bidirectional network, in step 916, the network entity agrees to the reception of the service through the bidirectional network according to the agreement information. In one case, the process proceeds to step 918 or 922, otherwise, the operation ends. Proceeding to step 918 or 922 is a matter of standard protocol or system choice.

In step 918, the service management block in the CBMS system delivers a notification message requesting delivery through the bidirectional channel to the service application block. Accordingly, in step 920, the service application block delivers the service / content requested by the terminal to the bidirectional network, and the service / content is delivered from the bidirectional network to the terminal through the assigned bidirectional channel.

In step 922, the service management block in the CBMS system delivers a notification message for requesting delivery through the bidirectional channel to the service application block. Accordingly, in step 924, the service application block delivers the service / content desired by the terminal to the service management block, and in step 926, the service management block delivers the service / content to the terminal through the assigned bidirectional channel of the bidirectional network. .

10 is a flowchart illustrating an operation of a terminal receiving a service through a bidirectional network according to another embodiment of the present invention. Here, an embodiment in the case where the information related to the transfer from the network to the terminal via the bidirectional network is shown.

Referring to FIG. 10, if it is determined in step 1002 that a service cannot be received through a broadcast network, in step 1004, the terminal transmits a request message to the network entity requesting to deliver a desired service through a bidirectional network, and in step 1006. Receive a response message corresponding to the request message. In step 1008, the UE determines whether the response message includes allocation information of the bidirectional channel. If the response message is a failure response message that does not include the bidirectional channel allocation information, the terminal proceeds to step 1018 to perform another procedure. On the other hand, if the response message is a message as shown in Table 9 including the allocation information of the bidirectional channel, the terminal proceeds to step 1010. Here, the allocation information of the bidirectional channel means bidirectional network information for handover or roaming and bandwidth allocated for service delivery.

In step 1010, the UE determines whether to agree to the delivery of the service through the bidirectional network. The determination in step 1010 is made according to preset information or a user's selection. If the service is not agreed to be transmitted through the bidirectional network, in step 1016, a confirmation message including the agreement information set as 'Not' is transmitted to the network entity, and the operation ends. On the other hand, if the user agrees to transfer the service through the bidirectional network, in step 1012, the UE transmits an acknowledgment message including agreement information set to 'Agree' to the network entity, and is indicated by the response message in step 1014. The desired service / content from a bi-directional network via an established bi-directional channel.

11 is a block diagram showing the structure of a terminal receiver according to a preferred embodiment of the present invention.

Referring to FIG. 11, the terminal receiver 1000 includes a broadcast receiver 1102 capable of receiving broadcast signals from a broadcast network, as well as an interactive adapter 1104 capable of connecting to a bidirectional network. Doing. The broadcast receiver 1102 receives service data or signaling information such as PSI / SI and ESG from a broadcast network, and the bidirectional converter 1104 transmits and receives service data or signaling information through a bidirectional network.

The control block 1108 is a mobility management that processes handover related operations in association with a subscription management block 1110 which is in charge of the management / acquisition of terminal authority related to service subscription and the decryption of service content. (MM) function, while controlling the broadcast receiver 1102 according to the above-described embodiment of the present invention to receive information related to service delivery through a bidirectional network, control the bidirectional converter 1104 to request messages, It exchanges response and acknowledgment messages and receives service data through the assigned bidirectional channel. The audio and video streams of the received service data are delivered to a content consumption block 1112 and stored immediately so as to be provided to the user or later.

Meanwhile, in the detailed description of the present invention, specific embodiments have been described, but various modifications are possible without departing from the scope of the present invention. As an example, the present disclosure discloses information related to the delivery of a service / content through a bidirectional network. The information is not only provided to other broadcasting networks, for example DVB-H, but also Digital Multimedia Broadcasting (DMB) and Digital Audio Broadcasting (DAB). It can also be applied to the delivery of service / content through a network. In this case, the information related to the bidirectional network mentioned in this specification may be related to similar information related to the broadcast network, specifically, the delivery type (only delivery, handover, roaming), entry point (URL, IP address, port number, telephone number). , Broadcast network type (DAB, DMB, etc.). Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims, but also by those equivalent to the scope of the claims.

In the present invention operating as described in detail above, the effects obtained by the representative ones of the disclosed inventions will be briefly described as follows.

The present invention supports a roaming procedure of a roaming user more efficiently by providing a special ESG including service guide information on services available to roaming users separately from the general ESG for local users.

Claims (29)

In the service delivery method through a bidirectional channel in a digital broadcasting system, Receiving a request message for requesting service delivery through a bidirectional network from a terminal; Transmitting an assignment message instructing the terminal to access a bidirectional channel for service delivery to an accessible bidirectional network, and receiving an assignment response message indicating that the bidirectional channel has been allocated from the bidirectional network; Transmitting a response message indicating that the bidirectional channel is allocated to the terminal; Transmitting a desired broadcast service to the terminal through the bidirectional channel of the bidirectional network when the terminal receives the confirmation message indicating that the terminal agrees to transfer the service through the bidirectional network after transmitting the response message. Service delivery method comprising a. The service fragment, content fragment, acquisition fragment, purchase fragment, and notification message of an electronic service guide (ESG) of the service related information according to claim 1, prior to receiving the request message. The service delivery method further comprises the step of transmitting through at least one of. The method of claim 2, wherein the information is, First information indicating whether service delivery through the bidirectional network is possible, second information indicating whether service delivery through the bidirectional network is possible alone, by handover or by roaming, and provider of the bidirectional network A URL for an entry point of the bidirectional network, a phone number of the bidirectional network, an Internet Protocol (IP) address for accessing the bidirectional network, a port number for accessing the bidirectional network, an acquisition criterion for the bidirectional network Ref), at least one of the network type of the bidirectional network. The method of claim 2, wherein the notification message, At least one service identifier representing the desired service, a URL and an identifier of an electronic service announcement (ESG) provider referenced for the service identifier, an IP address of the desired service, an IP platform identifier, a transport stream identifier, an original network identifier, Service delivery comprising at least one of a cell identifier to which the terminal belongs, a current network identifier, bidirectional network information for handover, bidirectional network information for roaming, charging information, frequency of the bidirectional network, a modulation method and an encoding method Way. The method of claim 1, wherein the request message, A user identifier representing the terminal, a network identifier of a home network to which the terminal belongs, at least one service identifier representing the desired service, a URL and an identifier of an electronic service announcement (ESG) provider referenced for the service identifier, the desired IP address of service, IP platform identifier, transport stream identifier, original network identifier, cell identifier to which the terminal belongs, current network identifier, bidirectional network information for exclusive delivery, bidirectional network information for handover, bidirectional network information for roaming Service delivery method comprising at least one. The method of claim 1, wherein the assignment message, A user identifier representing the terminal, a network identifier of the home network to which the terminal belongs, request information indicating whether the terminal requests single delivery, handover, or roaming, bandwidth required for delivery of the desired service At least one service identifier representing the desired service, a URL and identifier of an electronic service announcement (ESG) provider referenced for the service identifier, an IP address of the desired service, an IP platform identifier, a transport stream identifier, an original network identifier. And at least one of a cell identifier to which the terminal belongs, a current network identifier, and an identifier indicating a service provider. The method of claim 1, wherein the assignment response message, A user identifier representing the terminal, a network identifier of a home network to which the terminal belongs, bidirectional network information for single delivery, bidirectional network information for handover, bidirectional network information for roaming, bandwidth allocated for delivery of the desired service, At least one service identifier representing the desired service, a URL and an identifier of an electronic service announcement (ESG) provider referenced for the service identifier, an IP address of the desired service, an IP platform identifier, a transport stream identifier, an original network identifier, Service delivery comprising at least one of a cell identifier to which the terminal belongs, a current network identifier, an identifier indicating a service provider, charging information, an acquisition criterion for the bidirectional network, a frequency of the bidirectional network, a modulation method, and an encoding method. room . The method of claim 1, wherein the response message, A user identifier representing the terminal, a network identifier of a home network to which the terminal belongs, bidirectional network information for single delivery, bidirectional network information for handover, bidirectional network information for roaming, bandwidth allocated for delivery of the desired service At least one service identifier representing the desired service, a URL and identifier of an electronic service announcement (ESG) provider referenced for the service identifier, an IP address of the desired service, an IP platform identifier, a transport stream identifier, an original network identifier. And at least one of a cell identifier to which the terminal belongs, a current network identifier, an identifier indicating a service provider, charging information, an acquisition criterion for the bidirectional network, a frequency of the bidirectional network, a modulation method, and an encoding method. I'm Way. The method of claim 1, wherein the confirmation message, A user identifier representing the terminal, a network identifier of a home network to which the terminal belongs, information indicating whether the terminal agrees to transfer services through the bidirectional network, bidirectional network information for single delivery, bidirectional network for handover Information, bidirectional network information for roaming, bandwidth allocated for delivery of the desired service, at least one service identifier indicative of the desired service, a URL of an electronic service guidance (ESG) provider referenced for the service identifier, and An identifier, an IP address of the desired service, an IP platform identifier, a transport stream identifier, an original network identifier, a cell identifier to which the terminal belongs, a current network identifier, an identifier indicating a service provider, billing information, acquisition criteria for the bidirectional network, the Bidirectional Service delivery method, which is characterized in that it comprises at least one of a frequency of the network, the modulation method, coding method. The method of claim 1, wherein delivering the desired broadcast service comprises: Delivering the desired broadcast service from the service application block of the digital broadcasting system to the bidirectional network through a service management block; And delivering the desired service to the terminal through the bidirectional channel from the bidirectional network. The method of claim 1, wherein delivering the desired broadcast service comprises: Delivering the desired broadcast service from a service application block of the digital broadcasting system to the bidirectional network; And delivering the desired service to the terminal through the bidirectional channel from the bidirectional network. In the method of receiving a service through a bidirectional channel in a digital broadcasting system, Transmitting a request message for requesting service delivery through a bidirectional network to a network entity of a broadcasting system; When the terminal receives a response message from the network entity indicating that the bidirectional channel is allocated by an accessible bidirectional network, transmitting a confirmation message to the network entity indicating that the terminal agrees to transfer the service through the bidirectional network; And receiving the broadcast service desired by the terminal through the bidirectional channel of the bidirectional network. 13. The method of claim 12, wherein before transmitting the request message, information related to service delivery from the network entity through the two-way network is received at least from a service fragment of an electronic service guide (ESG), an acquisition fragment of the ESG, and a notification message. Service receiving method further comprises the step of receiving through one. The method of claim 13, wherein the information, First information indicating whether service delivery through the bidirectional network is possible, second information indicating whether service delivery through the bidirectional network is possible alone, by handover or by roaming, and provider of the bidirectional network A URL for an entry point of the bidirectional network, a phone number of the bidirectional network, an Internet Protocol (IP) address for accessing the bidirectional network, a port number for accessing the bidirectional network, an acquisition criterion for the bidirectional network Ref), at least one of the network type of the bidirectional network. The method of claim 13, wherein the notification message, At least one service identifier representing the desired service, a URL and an identifier of an electronic service announcement (ESG) provider referenced for the service identifier, an IP address of the desired service, an IP platform identifier, a transport stream identifier, an original network identifier, Receiving a service comprising at least one of a cell identifier to which the terminal belongs, a current network identifier, bidirectional network information for handover, bidirectional network information for roaming, charging information, frequency of the bidirectional network, a modulation method and an encoding method Way. The method of claim 12, wherein the request message, A user identifier representing the terminal, a network identifier of a home network to which the terminal belongs, at least one service identifier representing the desired service, a URL and an identifier of an electronic service announcement (ESG) provider referenced for the service identifier, the desired IP address of service, IP platform identifier, transport stream identifier, original network identifier, cell identifier to which the terminal belongs, current network identifier, bidirectional network information for exclusive delivery, bidirectional network information for handover, bidirectional network information for roaming Service receiving method comprising at least one. The method of claim 12, wherein the response message, At least one indicating a user identifier representing the terminal, a network identifier of a home network to which the terminal belongs, bidirectional network information for handover, bidirectional network information for roaming, bandwidth allocated for delivery of the desired service, and the desired service A service identifier of, an URL of the electronic service guide (ESG) provider referenced for the service identifier, an IP address of the desired service, an IP platform identifier, a transport stream identifier, an original network identifier, a cell identifier to which the terminal belongs, a current And at least one of a network identifier, an identifier indicating a service provider, charging information, an acquisition criterion for the bidirectional network, a frequency of the bidirectional network, a modulation method, and an encoding method. The method of claim 12, wherein the confirmation message, A user identifier representing the terminal, a network identifier of a home network to which the terminal belongs, information indicating whether the terminal agrees to deliver a service through the bidirectional network, bidirectional network information for handover, and bidirectional network information for roaming A bandwidth allocated for delivery of the desired service, at least one service identifier representing the desired service, a URL and identifier of an electronic service announcement (ESG) provider referenced for the service identifier, an IP address of the desired service, IP platform identifier, transport stream identifier, original network identifier, cell identifier to which the terminal belongs, current network identifier, identifier indicating service provider, charging information, acquisition criteria for the bidirectional network, frequency of the bidirectional network, modulation method, encoding Way Service receiving method comprising at least one of. In a digital broadcasting system supporting service delivery through a bidirectional channel, Upon receiving a request message for requesting service delivery through a bidirectional network from a terminal, the terminal transmits an assignment message instructing an accessible bidirectional network to allocate a bidirectional channel for service delivery, and transmits the bidirectional network from the bidirectional network. Receives an allocation response message indicating that a channel has been allocated, transmits a response message indicating that the bidirectional channel has been allocated to the terminal, and indicates that the terminal agrees to transfer the service through the bidirectional network after transmitting the response message. A service management (SM) block receiving a confirmation message; A service application (SA) for delivering a broadcast service desired by the terminal to the bidirectional network so that the terminal can receive a service desired by the terminal through the bidirectional channel of the bidirectional network by notification of the service management block. Digital broadcasting system comprising a block. The method of claim 19, wherein the service management block, Prior to receiving the request message, information related to service delivery through the bidirectional network is transmitted to the terminal through at least one of a service fragment of an electronic service guide (ESG), an acquisition fragment of the ESG, and a notification message. Digital broadcasting system. The method of claim 20, wherein the information, First information indicating whether service delivery through the bidirectional network is possible, second information indicating whether service delivery through the bidirectional network is possible alone, by handover or by roaming, and provider of the bidirectional network A URL for an entry point of the bidirectional network, a phone number of the bidirectional network, an Internet Protocol (IP) address for accessing the bidirectional network, a port number for accessing the bidirectional network, an acquisition criterion for the bidirectional network Ref), at least one of the network type of the bidirectional network. The method of claim 20, wherein the notification message, At least one service identifier representing the desired service, a URL and an identifier of an electronic service announcement (ESG) provider referenced for the service identifier, an IP address of the desired service, an IP platform identifier, a transport stream identifier, an original network identifier, A digital broadcast comprising at least one of a cell identifier to which a terminal belongs, a current network identifier, bidirectional network information for handover, bidirectional network information for roaming, charging information, a frequency of a bidirectional network, a modulation method, and an encoding method system. The method of claim 19, wherein the request message, A user identifier representing the terminal, a network identifier of a home network to which the terminal belongs, at least one service identifier representing the desired service, a URL and an identifier of an electronic service announcement (ESG) provider referenced for the service identifier, the desired IP address of service, IP platform identifier, transport stream identifier, original network identifier, cell identifier to which the terminal belongs, current network identifier, bidirectional network information for exclusive delivery, bidirectional network information for handover, bidirectional network information for roaming And at least one. The method of claim 19, wherein the assignment message, A user identifier representing the terminal, a network identifier of the home network to which the terminal belongs, request information indicating whether the terminal requests single delivery, handover, or roaming, bandwidth required for delivery of the desired service At least one service identifier representing the desired service, a URL and identifier of an electronic service announcement (ESG) provider referenced for the service identifier, an IP address of the desired service, an IP platform identifier, a transport stream identifier, an original network identifier. And a cell identifier to which the terminal belongs, a current network identifier, and an identifier indicating a service provider. The method of claim 19, wherein the assignment response message, A user identifier representing the terminal, a network identifier of a home network to which the terminal belongs, bidirectional network information for single delivery, bidirectional network information for handover, bidirectional network information for roaming, bandwidth allocated for delivery of the desired service, At least one service identifier representing the desired service, a URL and an identifier of an electronic service announcement (ESG) provider referenced for the service identifier, an IP address of the desired service, an IP platform identifier, a transport stream identifier, an original network identifier, A digital broadcast comprising at least one of a cell identifier to which the terminal belongs, a current network identifier, an identifier indicating a service provider, charging information, an acquisition criterion for the bidirectional network, a frequency of the bidirectional network, a modulation method, and an encoding method city System. The method of claim 19, wherein the response message, A user identifier representing the terminal, a network identifier of a home network to which the terminal belongs, bidirectional network information for single delivery, bidirectional network information for handover, bidirectional network information for roaming, and the like allocated for delivery of the desired service Bandwidth, at least one service identifier indicative of the desired service, a URL and identifier of an electronic service announcement (ESG) provider referenced for the service identifier, an IP address of the desired service, an IP platform identifier, transport stream identifier, original network And at least one of an identifier, a cell identifier to which the terminal belongs, a current network identifier, an identifier indicating a service provider, charging information, an acquisition criterion for the bidirectional network, a frequency of the bidirectional network, a modulation method, and an encoding method. Digital room Song system. The method of claim 19, wherein the confirmation message, A user identifier representing the terminal, a network identifier of a home network to which the terminal belongs, information indicating whether the terminal agrees to transfer services through the bidirectional network, bidirectional network information for single delivery, bidirectional network for handover Information, bidirectional network information for roaming, bandwidth allocated for delivery of the desired service, at least one service identifier indicative of the desired service, and the URL and identifier of an electronic service announcement (ESG) provider referenced for the service identifier. An IP address of the desired service, an IP platform identifier, a transport stream identifier, an original network identifier, a cell identifier to which the terminal belongs, a current network identifier, an identifier indicating a service provider, charging information, acquisition criteria for the bidirectional network, the bidirectionalThe digital broadcasting system characterized in that it comprises at least one of a frequency of the network, the modulation method, coding method. The method of claim 19, wherein the service application block, And delivering the desired broadcast service to the bidirectional network through the service management block. The method of claim 19, wherein the service application block, And delivering the desired broadcast service directly to the bidirectional network.

Images