KR20080041551A - Method and apparatus for transmitting and receiving service change information in digital broadcasting system - Google Patents

Abstract

The present invention relates to a method and apparatus for indicating a service change in a convergence of a broadcast and mobile communication service (CBMS) system. The network entity collects information about a second service of another network related to each first service that can be provided in the network, so that the second service changes at least one of language, subtitle, and camera angle compared to the first service. Service change information indicating whether the service is changed, and the service change information is transmitted to a terminal in the network through a broadcast network or a bidirectional network. The terminal may determine whether to receive the second service continuously to the first service in the other network using service change information.

Description

TECHNICAL AND APPARATUS FOR TRANSMITTING AND RECEIVING SERVICE VARIATION INFORMATION 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.

2A and 2B illustrate an example of service change according to a preferred embodiment of the present invention.

3 is a flow diagram illustrating operation of a network entity in accordance with a preferred embodiment of the present invention.

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

5 is a block diagram showing the structure of a network according to a preferred embodiment of the present invention.

6 is a block diagram showing the structure of a terminal 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 indicating a change in a broadcasting service in a convergence of broadcasting and mobile service (hereinafter referred to as 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 digital broadcasting systems such as CBMS, it is necessary to guarantee service continuity when the Internet protocol (IP) platform, service provider, network, frequency, etc. for the terminal receiving the service are changed. have. Compared with the service that the terminal is currently receiving, services from different IP platforms, different service providers, different networks and / or different frequencies may not be exactly the same and may have some differences. Therefore, there is a need for a technology for determining whether a terminal continuously receives a service provided through another IP platform, another service provider, another network, and a different frequency to a current service.

Accordingly, the present invention, which was devised to solve the problems of the prior art operating as described above, provides a method and apparatus for determining service continuity when a terminal performs handover or roaming.

The present invention provides a method and apparatus for instructing a terminal of a change in a service being received by the terminal so that the terminal can determine service continuity.

According to a preferred embodiment of the present invention, in a method of transmitting service change information in a digital broadcasting system,

Collecting information about a second service of another network related to each first service that can be provided in a network, and generating service change information indicating how the second service has changed compared to the first service;

And transmitting the service change information to a terminal in the network through a predetermined delivery bearer.

According to a preferred embodiment of the present invention, in a method of receiving service change information in a digital broadcasting system,

Receiving service change information from the network through a forwarding bearer, the service change information indicating how a second service of another network related to each first service available in the network has changed compared to the first service;

Determining whether to receive the second service continuously to the first service in the other network by using the service change information;

And if it is determined that the second service is to be continuously received, receiving the second service continuously when moving to the other network.

According to a preferred embodiment of the present invention, in a digital broadcasting system for transmitting service change information,

Collecting information about a second service of another network related to each first service that can be provided in a network, to generate service change information indicating how the second service has changed compared to the first service, and the service change information A network entity that transmits through a predetermined delivery bearer,

Receiving the service change information through the delivery bearer, and determining whether to receive the second service continuously with the first service in the other network using the service change information, and continuously receiving the second service. If it is determined that the reception is to move to another network, characterized in that it comprises a terminal that receives the second service continuously.

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 below is to instruct a terminal of a change in a broadcast service in a convergence of a broadcast and mobile communication service (CBMS) system. In this case, the change of the service means, for example, a change of the service of the new network with respect to the old network during handover or roaming. In addition, the term "service" in the present specification 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. In the service application block 120, a head-end for generating service data for a specific service by aggregating content sources from the content provider 110 and additionally metadata required for service configuration. (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 (sub-entities) for managing 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 the 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.

The DVB-H receiver is responsible for service reception or signaling through the 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. 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).

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 between the service application block 120 and the service management block 130 for the declaration of the service application or for the description of the service application, including content descriptions and metadata.

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 certain functions available in the bidirectional network, such as subscriber management and billing functions.

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 as an example, another IP platform means another service management block, that is, a service management block belonging to another network. do.

When a terminal moves to a new service area belonging to another IP platform, another service provider, another network, or a different frequency while receiving a broadcast service in a digital broadcasting system, a service similar to the received service may be provided in the new service area. It is necessary to determine if it can be provided. Examples of such movements are roaming and handover. The definition of roaming and handover in a CBMS system varies with different rules, for example, changes in IP platform, provider (ESG, service and / or other provider), service management (SM) block, network, etc. Can be decided. The following briefly defines terms used herein.

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 can be 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 may be used as an identifier of the service management block. If the service provider ID is unique in another range, the service provider ID and the range may be used as the SM identifier.

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

3. If one IP platform corresponds to exactly one service management block and different service management blocks cannot share one IP platform, the IP platform ID may be 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 service management block ID has a range, a pair of the service management block ID and the identifier of the range may be used as the SM identifier.

5. Follow 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. The 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.

Therefore, the problem of mobility definition in this document is general and not specific. Whatever the structure and definition, the ideas proposed in this document may still be used. The problem, however, is that it is difficult to give a clear explanation when related problems, for example concepts, figures, parameters, etc. are mentioned. Since the rules for handover and roaming definitions are not clear, this can be an IP platform, ESG provider, service provider, SM, IPDC domain, network or others. Therefore, when relevant parameters (eg, identifier) are required, all relevant parameters are listed. Thus, all or some of these may be needed, and new parameters may be needed. These fields may be modified, added, removed or replaced according to the final definition in the CBMS.

In any case, the structure, concept and parameters may be changed according to the final definition, but the ideas proposed in this document may be adopted and may be slightly modified according to the final definition in the CBMS.

If the terminal wants to continue to consume the service even though the service that the terminal is receiving is no longer available in the new service area, the terminal may for example be an IP platform, a service provider, a network, Change the reception parameters by frequency. The service newly received through the reception parameter may be exactly the same as the service received in the previous service area or may have a slight difference.

If the service received by the terminal should be changed slightly, it is advantageous for the terminal and the user to indicate what change. Therefore, even if the service received by the terminal is changed in a new service area, in order to guarantee service continuity when the terminal moves, in the current network, a service indicating how a service provided by another neighboring service area is different from a similar service of the current network. Send change information. As described above, the other service area means a service area belonging to a different IP platform, service provider or network, or using a different frequency than the service area of the network where the terminal is currently located. In the CBMS system, since there are two types of delivery bearers, that is, a broadcast network and a bidirectional network, service change information may be transmitted through the bidirectional network and / or the bidirectional network.

The terminal determines whether there is a service that can be continuously received in the current service when moving to the other service area with reference to the service change information, and if present, continuously receives the changed service. Specifically, the terminal recognizes what kind of service change has occurred from the service change information and whether the service change is acceptable. Through this, the terminal or the user can determine whether to receive the changed service. As such, the terminal acquires the service change information before starting to receive the changed service.

2A and 2B show an example of service change according to a preferred embodiment of the present invention. Here, the case of handover in which the IP platform is changed is illustrated.

Referring to FIG. 2A, the terminal 208 receives the service A 206 at the IP platform A 202 and moves to the service area of the IP platform B 204. In this movement, the terminal 208 refers to the service change information received at the IP platform A 202 to determine whether the content of the service A 206 is valid at the IP platform B 204.

An example of the changed service provided in IP platform B 204 is shown in FIG. 2B.

Referring to FIG. 2B, the original content associated with service A 206 consists of one video stream 210 and different audio streams A, B 212, 214 that are specific to the region. Video stream 210 is provided identically at IP platform A 202 and IP platform B 204, but audio stream A 212 is provided at IP platform A 202 and audio stream B 214 is IP platform. Provided at B 204. Therefore, service A 206 provided by IP platform A 202 is composed of video stream 210 and audio stream A 212, and service B 200 provided by IP platform B 204 is service A ( It is composed of video stream 210 and audio stream B 214 as a modified service for 206.

Representative examples of changed services related to service A 206 provided in IP platform B 204 include world wide news, live sport broadcasts, and the like. Sports broadcasts generally have the same video content, but audio is localized. That is, there may be a plurality of different audio streams, for example commentaries broadcast in different languages or commentaries by different commentators having the same language for video of the same sports relay broadcast. . As an example, IP platform A 202 provides channels for Euro TV, and IP platform B 204 provides channels for national TV.

The service change information provided by IP platform A 202 indicates how service B 200 has changed in the criteria of service A 206. Details of the service change information may be defined by a service provider or a provider of the service change information. For example, a service such as a service of another language, a service of another subtitle, or a service of another camera angle may be used. Indicates a change.

The following describes three types of service changes. However, the details of the service change information according to the preferred embodiment of the present invention are not limited to these three service changes, and another type of service change desired by the provider may be added.

1) Services in different languages mean services expressed in the same content or in different languages.

2) A service of another subtitle means a service having the same content or different subtitles.

3) The service of another camera means the same service or a service having a video image obtained from different camera angles.

Table 1 below summarizes the description of the above service changes.

Classification Explanation One Services in other languages Same service expressed in different languages 2 Services in other subtitles Same service with different subtitles 3 Service of different camera angles Same service with footage from different camera angles

Therefore, service change information between services may be given as shown in Table 2 below. In the following, information related to the service identifier and the location may be changed according to the definition of handover and roaming. While the relevant relevant parameters have been disclosed here, they may be removed, added or modified according to the CBMS final definitions and requirements. The syntax for service change varies, but the main ideas are shown in <Table 2>.

Service A Service A ' Service identifier and location Service ID Service ID ' IP address IP address " ESG Provider ID ESG Provider ID ' IP platform ID IP platform ID " Service provider ID Service provider ID " SM ID SM ID ' Network ID Network id ' Access information

Service change type 1. Services in other languages 0: means the languages are the same between the two services 1: means the language is different between the two services Language type used by service A Language type used by service A ' 2. Services of other subtitles 0: This means that the subtitles between the two services are the same. 1: means the subtitle is different between the two services Subtitle Type Used by Service A Subtitle type used by service A ' 3. Service of different camera angle 0: means the camera angle between the two services is the same 1: means that the camera angle between the two services is different Camera angle type used by service A Camera angle type used by service A '

The service change information for indicating specific details of service change to the terminal is transported through a broadcast network or a bidirectional network. As an example, the service change information is included in an electronic service announcement (ESG), notification message, PSI / SI or other signaling. When delivered through an ESG, the service change information is added to a service type information element or service mapping information element of a service fragment including a description of the service as a whole for each service that can be provided, or the service. It is added to a new information element of a fragment or included in a content fragment, an acquisition fragment, or another fragment. When delivered through a bidirectional network, the service change information may be included in a response message corresponding to the request of the terminal.

Tables 3a and 3b below show examples of information elements for service change types included in service change information. In addition to the types shown in Tables 3a and 3b, types of service changes may be defined by the provider.

<complexType name = "ServiceVariationType"><sequence><element name = "different language" type = "mpeg: extendedLanguageType" use = "optional"/><element name = "different subtitle" type = "mpeg: extendedLanguageType" use = "optional"/><element name = "different camera angle" type = "anyURI" use = "optional"/></sequence><attribute name = "service with different language" type = "boolean"/> <attribute name = "service different subtitle" type = "boolean"/> <attribute name = "service different camera angle" type = "boolean"/></complexType>

<ClassificationScheme uri = "urn: dvb: ipdc: esg: cs: ServiceVariationTypeCS:> <Term termID =" 1.0 "<Name xml: lang =" en "> Service Variation Type </ Name> <Definition xml: lang =" en "> Type of service variation, eg different language, different subtitle, different camera </ Definition> <Term termID =" 1.1 "> <Name xml: lang =" en "> service with different language </ Name> <Definition xml: lang = "en"> A service with different language </ Definition> <Term termID = "1.2"> <Name xml: lang = "en"> service different subtitle </ Name> <Definition xml: lang = "en"> A service with different subtitle </ Definition> <Term termID = "1.3"> <Name xml: lang = "en"> service different camera angle </ Name> <Definition xml: lang = "en"> A Service with different camera angle </ Definition> <Term termID = "1.4"> <Name xml: lang = "en"> service without variation </ Name> <Definition xml: lang = "en"> A service without variation </ Definition> </ Term> </ Term> </ ClassificationScheme>

Both services may have the same language, different subtitles, and different camera angles. In this case, <Table 3b> can be modified to the following <Table 3c>.

<ClassificationScheme uri = "urn: dvb: ipdc: esg: cs: ServiceVariationTypeCS:> <Term termID =" 1.0 "<Name xml: lang =" en "> Service Variation Type </ Name> <Definition xml: lang =" en "> Type of service variation, eg different language, different subtitle, different camera </ Definition> <Term termID =" 1.1 "> <Name xml: lang =" en "> service with same language </ Name> <Definition xml: lang = "en"> A service with same language </ Definition> <Term termID = "1.1.1"> <Name xml: lang = "en"> service samesubtitle </ Name> <Definition xml: lang = "en" > A service with same subtitle </ Definition> <Term termID = "1.1.1.1> <Name xml: lang =" en "> service same camera angle </ Name> <Definition xml: lang =" en "> A Service with same camera angle </ Definition> </ Term> <Term termID = "1.1.1.2> <Name xml: lang =" en "> service different camera angle </ Name> <Definition xml: lang =" en "> A Service with different camera angle </ Definition> </ Term> </ Term> <T erm termID = "1.1.2> <Name xml: lang =" en "> service different subtitle </ Name> <Definition xml: lang =" en "> A service with different subtitle </ Definition> <Term termID =" 1.1 .2.1> <Name xml: lang = "en"> service same camera angle </ Name> <Definition xml: lang = "en"> A Service with same camera angle </ Definition> </ Term> <Term termID = " 1.1.2.2> <Name xml: lang = "en"> service different camera angle </ Name> <Definition xml: lang = "en"> A Service with different camera angle </ Definition> </ Term> </ Term> </ Term> <Term termID = "1.2> <Name xml: lang =" en "> service with different language </ Name> <Definition xml: lang =" en "> A service with different language </ Definition> <Term termID = "1.2.1"> <Name xml: lang = "en"> service same subtitle </ Name> <Definition xml: lang = "en"> A service with same subtitle </ Definition> <Term termID = "1.2 .1.1> <Name xml: lang = "en"> service same camera angle </ Name> < Definition xml: lang = "en"> A Service with same camera angle </ Definition> </ Term> <Term termID = "1.2.1.2> <Name xml: lang =" en "> service different camera angle </ Name> <Definition xml: lang = "en"> A Service with different camera angle </ Definition> </ Term> </ Term> <Term termID = "1.2.2> <Name xml: lang =" en "> service different subtitle </ Name> <Definition xml: lang = "en"> A service with different subtitle </ Definition> <Term termID = "1.2.2.1> <Name xml: lang =" en "> service same camera angle </ Name> <Definition xml: lang = "en"> A Service with same camera angle </ Definition> </ Term> <Term termID = "1.2.2.2> <Name xml: lang =" en "> service different camera angle </ Name > <Definition xml: lang = "en"> A Service with different camera angle </ Definition> </ Term> </ Term> </ Term> </ Term> </ ClassificationScheme>

Tables 4a and 4b below show details of service change information indicating available languages / subtitles / camera angles for other services.

For services with different languages, subtitles and / or camera angles, the available languages, subtitles and / or camera angles may be indicated. Detailed information about the service identifier and location may also be displayed as shown in Table 4a or Table 4b. For example, other parameters such as positive integers may be used instead of the URI type in the definition of the ESG provider ID and the service provider ID.

<complexType name = "ServiceVariation" minOccur = "0" maxOccur = "unbounded" /> <sequence> <element name = "Service_ID" type = "anyURI" /> <element name = "IP_address" type = "positive Integer" / > <element name = "ESGProviderID" type = "anyURI"> <element name = "IP platform_ID" type = "positive Integer" /> <element name = "ServiceProvider_ID" type = "anyURI" /> <element name = "SM_ID "type =" anyURI "/> <element name =" Network_ID "type =" anyURI "> <element name =" ServiceVariationType "type =" esg: ServiceVatiationType "> <element name =" Service_ID_other "type =" anyURI "/> <element name = "IP_address_other" type = "positive Integer" /> <element name = "ESGProviderID_other" type = "anyURI"> <element name = "IP platform_ID_other" type = "positive Integer" /> <element name = "ServiceProvider_ID_other "type =" anyURI "/> <element name =" SM_ID_other "type =" anyURI "/> <element name =" Network_ID_other "type =" anyURI "> </ sequence> </ complexType>

<complexType name = "ServiceVariation" minOccur = "0" maxOccur = "unbounded" /> <sequence> <element name = "Service_ID" type = "anyURI" /> <element name = "IP_address" type = "positive Integer" / > <element name = "ESGProviderID" type = "anyURI"> <element name = "IP platform_ID" type = "positive Integer" /> <element name = "ServiceProvider_ID" type = "anyURI" /> <element name = "SM_ID "type =" anyURI "/> <element name =" Network_ID "type =" anyURI "> <element name =" ServiceVariationType "type =" esg: ServiceVatiationType "> <element name =" different language "type =" mpeg: extendedLanguageType "use =" optional "/> <element name =" different subtitle "type =" mpeg: extendedLanguageType "use =" optional "/> <element name =" different camera angle "type =" anyURI "use =" optional "/ > <element name = "Service_ID_other" type = "anyURI" /> <element name = "IP_address_other" type = "positive Integer" /> <element name = "ESGProviderID_other" type = "anyURI"> <element name = "IP platform_ID_other "type =" positive Integer "/> <element name =" ServiceProvider_ID_other "type =" anyURI "/> <element name =" SM_ID_other "type =" anyURI "/> <element name =" Network_ID_other "type =" anyURI "> </ sequence> </ complexType>

Here, the changed service for the service provided in the current network may include at least one of another service identifier (service_ID_other), another IP address (IP_address_other), another provider (id_provider_id_other), another IP platform identifier (IP platform_id_other), and another network identifier (network_id_other). Is identified by one. Also included in the service change information is a service change type of the changed service and information elements for language, subtitle and / or camera.

The service change information may be included in service mapping information indicating a mapping of a service of a neighboring network to a service of a current network, as shown in Table 5a.

<complexType name = ServiceMapping_same "minOccur =" 0 "maxOccur =" unbounded "><sequence><element name =" Service_ID "type =" anyURI "/><element name =" IP_address "type =" positive Integer "/>< element name = "ESGProviderID" type = "anyURI"><element name = "IP platform_ID" type = "positive Integer"/><element name = "ServiceProvider_ID" type = "anyURI"/><element name = "SM_ID" type = "anyURI"/><element name = "Network_ID" type = "anyURI"><element name = "Service_ID_other" type = "anyURI"/><element name = "IP_address_other" type = "positive Integer"/><element name = "ESGProviderID_other" type = "anyURI"><element name = "IP platform_ID_other" type = "positive Integer"/><element name = "ServiceProvider_ID_other" type = "anyURI"/><element name = "SM_ID_other" type = "anyURI"/><element name = "Network_ID_other" type = "anyURI"><element name = "ServiceVariation" type = "esg: ServiceVatiation"> </ sequence></complexType>

The service change type may be used for service mapping information as shown in Table 5b below.

<complexType name = ServiceMapping_same "minOccur =" 0 "maxOccur =" unbounded "><sequence><element name =" Service_ID "type =" anyURI "/><element name =" IP_address "type =" positive Integer "/>< element name = "ESGProviderID" type = "anyURI"><element name = "IP platform_ID" type = "positive Integer"/><element name = "ServiceProvider_ID" type = "anyURI"/><element name = "SM_ID" type = "anyURI"/><element name = "Network_ID" type = "anyURI"><element name = "Service_ID_other" type = "anyURI"/><element name = "IP_address_other" type = "positive Integer"/><element name = "ESGProviderID_other" type = "anyURI"><element name = "IP platform_ID_other" type = "positive Integer"/><element name = "ServiceProvider_ID_other" type = "anyURI"/><element name = "SM_ID_other" type = "anyURI"/><element name = "Network_ID_other" type = "anyURI"><element name = "ServiceVariationType" type = "esg: ServiceVatiationType"> <element name = "ServiceRelatedType" type = "esg: ServiceRelatedType"> <element name = "related service" type = "anyURI"> </ sequence></ complexTy pe>

Table 5c below is another example of service mapping information.

<complexType name = ServiceMapping_same "minOccur =" 0 "maxOccur =" unbounded "><sequence><element name =" Service_ID "type =" anyURI "/><element name =" IP_address "type =" positive Integer "/>< element name = "ESGProviderID" type = "anyURI"><element name = "IP platform_ID" type = "positive Integer"/><element name = "ServiceProvider_ID" type = "anyURI"/><element name = "SM_ID" type = "anyURI"/><element name = "Network_ID" type = "anyURI"><element name = "Service_ID_other" type = "anyURI"/><element name = "IP_address_other" type = "positive Integer"/><element name = "ESGProviderID_other" type = "anyURI"><element name = "IP platform_ID_other" type = "positive Integer"/><element name = "ServiceProvider_ID_other" type = "anyURI"/><element name = "SM_ID_other" type = "anyURI"/><element name = "Network_ID_other" type = "anyURI"><element name = "ServiceVariationType" type = "esg: ServiceVatiationType"> <element name = "different language" type = "mpeg: extendedLanguageType" use = "optional"/><element name = "different subtitle" type = "mpeg: extend edLanguageType "use =" optional "/><element name =" different camera angle "type =" anyURI "use =" optional "/><element name =" ServiceRelatedType "type =" esg: ServiceRelatedType "> <element name =" related service "type =" anyURI "> </ sequence></ complexType

When the service change information is loaded on the PSI / SI, the PSI / SI already includes information on each service, that is, an IP address, a transport stream identifier, a network identifier, and the like. Therefore, other information elements of the service change information may be additionally inserted into the PSi / SI so as not to overlap.

3 is a flowchart illustrating the operation of a network entity according to a preferred embodiment of the present invention. The network entity referred to herein is at least one entity capable of collecting and transmitting information related to service mapping and service change. For example, the network entity may be a service application block, a service management block, or both.

Referring to FIG. 3, in step 302, the network entity refers to information on services that can be provided in other networks adjacent to each service that can be provided in the current network, or services that are provided in other networks. Information related to the change is collected, and service change information is generated with reference to the collected information. The service change information is, for example, a service of the same content provided in English on another network but currently provided in a local language on a network, and a film service provided with English subtitles on another network but currently provided with subtitles in a local language on a network. And change information elements for the like.

The service change information is transmitted to the terminal by at least one of steps 310 to 312 according to a standard protocol or a system designer's intention. In more detail, in step 310, the service change information is loaded on the ESG and transmitted to the terminal. In step 312, the service change information is transmitted to the terminal in a notification message. In step 314, the service change information is transmitted to the terminal in a predetermined signaling message. In step 316, the service change information is transmitted to the terminal in a response message transmitted by the network entity through the bidirectional network in response to a request from the terminal through the bidirectional network.

In the case of handover or roaming, if the original network provides service change information, the terminal may select the reception parameter based on the service change information before switching to the new reception parameter. If another network provides the service change information, the terminal may find a difference for the service based on the service change information and does not need to analyze it by itself. Therefore, it is very useful to provide the service change information in the network.

4 (composed of FIGS. 4A to 4C) is a flowchart illustrating an operation of a terminal according to an exemplary embodiment of the present invention. Here, the case where the service change information is included in the service mapping information and transmitted is described. 4A or 4B is performed according to a means for transmitting service mapping information in a network.

Referring to FIG. 4A, in step 402, the UE receives PSI / SI, and in step 404, receives an ESG, a notification message, or other signaling, and proceeds to step 422 of FIG. 4C. Referring to FIG. 4B, in step 412, the UE determines whether the current service cannot be received in the current network, that is, whether to continue receiving the current service in another service area. If it is determined that the current service is to be continuously received in another service area, the terminal proceeds to step 414 and the terminal transmits a request message for service mapping information to the network, and in step 416, receives the service mapping information in response to the request message. After that, the process proceeds to step 422 of FIG. 4C.

Referring to FIG. 4C, the terminal analyzes the service mapping information to find whether a desired service exists in step 422, and determines whether a service mapped to the current service exists in the other service area in step 424. As a result of analyzing the service mapping information, if a service matching the current service is found or only another related service exists, the terminal performs a corresponding procedure in steps 426 and 428.

On the other hand, if the changed service for the current service is found, the terminal checks the service change type of the changed service by analyzing the service change information included in the service mapping information in step 430. If the service change type is "other language", in step 432, the terminal determines whether the changed service language is valid for the user. If the service change type is "other subtitle", in step 436, the terminal determines whether the subtitle of the changed service is valid for the user. If the service change type is "other camera", in step 434, the terminal determines whether the camera angle of the changed service is valid for the user. The terminal notifies the user of the other language / subtitle / camera for the determination in steps 432 to 436 and inquires whether the user will receive the changed service through the other language / subtitle / camera.

In step 438, the terminal determines whether the user has allowed the changed service having the different language / subtitle / camera, and if the user has allowed, proceeds to step 442 to receive the other service area after moving to the other service area. Receive the changed service according to the parameters. On the other hand, if the user does not want to use the changed service, the process proceeds to step 440 to perform another procedure. In another case, in step 438, the terminal may automatically select whether to receive the changed service according to a preset operation mode without user intervention.

5 is a diagram showing the structure of a network according to a preferred embodiment of the present invention. Only those entities that perform logical functions related to the preferred embodiment of the present invention in the network are shown here.

Referring to FIG. 5, a service application (SA) block 502 combines associated metadata and broadcast content from multiple sources to provide a particular service to generate service data including a video stream, an audio stream, and the like. After encoding the service data in a format that can be understood by the terminal, the service data is provided to the terminal through streaming or file carousel delivery, and generates metadata including a service description to be used for the ESG. In particular, it provides metadata for services of the service types described above, which are valid for roaming users, to be used separately to create a special ESG.

The ESG entity 506 within the service management (SM) block 504 is responsible for creating and transmitting the ESG using the metadata provided from the SA block 502. When an ESG is used for the transmission of service change information, the ESG entity 506 inserts the service change information configured as described above into the ESG, which is broadcasted and / or bidirectionally by the MM block 512. It is delivered to the terminal 520 through the network.

The Service Configuration & Resource Allocation entity 508 is responsible for service configuration and network resource allocation, and communicates with the SA block 502 to negotiate bandwidth of a broadcast bearer. It allocates services to locations on a broadcast network topology or determines service bandwidth and schedules service times. The security / service protection provision entity 510 is responsible for security and authentication, service protection, and service provisioning. The entities 506 to 510 are connected to the MM block 512 to perform functions necessary for handover and roaming. The MM block 512 performs tasks related to mobility of the terminal, in particular handover and roaming.

6 is a diagram illustrating the structure of a terminal receiver according to a preferred embodiment of the present invention.

Referring to FIG. 6, the receiver 600 includes an interactive adapter 604 capable of connecting to a bidirectional network as well as a broadcast receiver 602 capable of receiving a broadcast signal from a broadcast network. The broadcast receiver 602 receives service data or signaling information such as PSI / SI and ESG from a broadcast network, and the bidirectional converter 604 transmits and receives service data or signaling information through a bidirectional network. The control block 608 is a mobility management that processes handover related operations in association with a subscription management block 610 that is in charge of the management / acquisition of terminal authority related to service subscription and the decryption of service content. While performing the (MM) function, it controls the broadcast receiver 602 or the bidirectional converter 604 according to the embodiment of the present invention described above to receive the service conversion information. If necessary, the control block 608 transmits a request message for service conversion information by the bidirectional converter 504, and receives and analyzes the service conversion information by the bidirectional converter 504 in response to the request message. .

The received service conversion information is used to determine whether service continuity is possible in the control block 608, and a content consumption block 612 controls audio and video of a broadcast service under the control of the control block 608. Is stored to be provided to the user or to be provided to the user 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. 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 enables the terminal to determine service continuity by providing the terminal with service change information indicating how the service is changed in the service area after the move in advance for the mobile terminal.

Claims (15)

A method of transmitting service change information in a digital broadcasting system, Collecting information about a second service of another network related to each first service that can be provided in a network, and generating service change information indicating how the second service has changed compared to the first service; And transmitting the service change information to a terminal in the network through a predetermined delivery bearer. The method of claim 1, wherein the service change information, A service change type indicating whether the second service is expressed in the same content or a different language as the first service, has a subtitle different from the first service, and has an image obtained from a camera angle different from that of the first service And an information element. The method of claim 2, wherein the service change information, And at least one of a service identifier of the second service, an internet protocol (IP) address of the second service, a provider identifier of the second service, an IP platform identifier of the second service, and a network identifier of the other network. A method of transmitting service change information, characterized in that. The method of claim 1, wherein the transmitting of the The service change information is transmitted to the terminal through at least one of an electronic service guide (ESG) of a broadcast network, program specific information and service information (PSI / SI) of the broadcast network, and a response message of a bidirectional network accessible by the terminal. The service change information transmission method characterized by the above-mentioned. The method of claim 1, wherein the delivery bearer is, And at least one of broadcast network and bidirectional network information to which the terminal is accessible. In the method of receiving service change information in a digital broadcasting system, Receiving service change information from the network through a predetermined delivery bearer indicating how a second service of another network related to each first service provided by the network has changed compared to the first service; Determining whether to receive the second service continuously to the first service in the other network by using the service change information; And receiving the second service continuously when moving to the other network when it is determined that the second service is to be continuously received. The method of claim 6, wherein the service change information, A service change type indicating whether the second service is expressed in the same content or a different language as the first service, has a subtitle different from the first service, and has an image obtained from a camera angle different from that of the first service And an information element. The method of claim 7, wherein the service change information, And at least one of a service identifier of the second service, an internet protocol (IP) address of the second service, a provider identifier of the second service, an IP platform identifier of the second service, and a network identifier of the other network. Method for receiving service change information, characterized in that. The method of claim 6, wherein the receiving process Receiving the service change information through at least one of an electronic service guide (ESG) of a broadcast network, program specific information and service information (PSI / SI) of the broadcast network, and a response message of a bidirectional network to which the terminal is accessible. A method of receiving service change information. The method of claim 6, wherein the delivery bearer, And receiving at least one of broadcast network and bidirectional network information to which the terminal is accessible. In a digital broadcasting system for transmitting service change information, Collecting information about a second service of another network related to each first service that can be provided in a network, to generate service change information indicating how the second service has changed compared to the first service, and the service change information A network entity that transmits through a predetermined delivery bearer, Receiving the service change information through the forwarding bearer, and determining whether to receive the second service continuously to the first service in the other network using the service change information, and continuously receiving the second service. And a terminal for continuously receiving the second service when moving to the other network when it is determined to receive. The method of claim 11, wherein the service change information, A service change type indicating whether the second service is expressed in the same content or a different language as the first service, has a subtitle different from the first service, and has an image obtained from a camera angle different from that of the first service A digital broadcasting system comprising an information element. The method of claim 12, wherein the service change information, And at least one of a service identifier of the second service, an internet protocol (IP) address of the second service, a provider identifier of the second service, an IP platform identifier of the second service, and a network identifier of the other network. Digital broadcasting system, characterized in that. The method of claim 11, wherein the service change information, Digital broadcasting system characterized in that the transmission through at least one of the electronic service announcement (ESG) of the broadcast network, the program specific information and service information (PSI / SI) of the broadcast network, the response message of the bidirectional network to which the terminal is accessible. . The method of claim 11, wherein the delivery bearer, And at least one of a broadcast network accessible by the terminal and bidirectional network information.

Images