KR20090004430A - Method and apparatus for transmitting and receiving electronic service guide for roaming user in digital broadcasting system - Google Patents

Abstract

A method and an apparatus for transmitting and receiving an electronic service guide for a roaming user in a digital broadcasting system are provided to enable a transmitter to identify a change of SM(Service Management) and transmit roaming ESG information, thereby enabling a receiver to receive the transmitted roaming ESG information. A special ESG(Electronic Service Guide) indicates effective services to roaming users within a ntwork entering another network. The special ESG is generated. The roaming ESG information is set according to the special ESG(1101~1107). The set roaming ESG information is located according to a selected transmitting method. And the roaming ESG information is transmitted(1109).

Description

METHOD AND APPARATUS FOR TRANSMITTING AND RECEIVING ELECTRONIC SERVICE GUIDE FOR ROAMING USER IN DIGITAL BROADCASTING SYSTEM}

The present invention relates to a digital broadcasting system, and more particularly, to an apparatus and method for transmitting and receiving an electronic service guide (ESG) in a convergence of broadcasting and mobile service (CBMS) system. It is about.

Today, due to the development of communication and broadcasting technology, a broadcasting system or a mobile communication system provides a portable broadcasting, and a portable broadcasting service capable of transmitting packet data through a broadcast channel as well as a general broadcasting service limited to voice and video. Mobile Broadcast is under discussion. 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, transmitting the service, and receiving the service by the mobile terminal.

The Open Mobile Alliance (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. . 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, a terminal for receiving a broadcast service in a mobile broadcasting system receives a service guide (SG) including description information about the service itself, billing information for the service, and information on a method of receiving the service. By using the service guide, a desired service is received. Meanwhile, the terminal may move out of a home network belonging to a single Internet Protocol (IP) platform and move to a service area of a neighbor network belonging to another IP platform, which is called a roaming procedure. Therefore, there is a need for a technology for providing service guidance information for a terminal, that is, a roaming user, moved to a neighbor network through roaming.

1 is a block diagram showing the structure of a CBMS system. FIG. 1 illustrates logical entities interworking with each other to achieve the required capabilities for IP Data Cast (DVB-H) based IP Data Cast (IPDC). 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 creation block (CC) 110 produces a content source of a broadcast service and sends it to a service application block (SA) block 120. The SA block 120 aggregates the content sources from the content provider 110 and metadata necessary for service configuration to generate service data for a specific service. To this end, the SA block 120 is composed of a number of sub-entities that manage different applications for each service. Service Management (SM) block 130 is a service configuration (service configuration), resource allocation, electronic service guidance provisioning (provisioning), security, mobility management between the SA block 120 and the terminal 160 Mobility Management (hereinafter, referred to as MM)).

The broadcast network 140 is a network for transmitting broadcast service data, which is, for example, a DVB-H system. The bidirectional network 150 is generally a Universal Mobile Telecommunications System (UMTS) according to 3rd Generation Partnership Project (3GPP), International Mobile Telecommunications (IMT) -2000 according to 3GPP2, Wireless Local Area Network (WLAN) or WiBro (Wireless Broadband internet) Cellular mobile communication network such as c), and as another example, all kinds of mobile communication networks that provide a function for receiving information or requests transmitted from the terminal 160 and transmitting a response to the information or request. Can be. 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.

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 X-1, X-2, and X-3 interfaces refer to the reference point between the broadcast network and other entities, and are generally not used in the bidirectional standard based on DVB-H. The X-1 interface connects between the content provider 110 and the SA block 120, the X-2 interface connects between the bidirectional network 150 and the terminal 160, and the X-3 interface connects the SM block 130. ) And the bidirectional network 150.

The CBMS-1 interface carries broadcast related signaling from the broadcast network 140 to the terminal 160, and the CBMS-2 interface carries contents such as audio, video, files, and the like from the SA block 120 to the terminal 160. . The CBMS-3 interface carries an electronic service announcement (ESG) from the SM block 130 to the terminal 160 in the form of point-to-multipoint (hereinafter referred to as ptm) transmission via the broadcast network 140. The CBMS-4 interface transmits point-to-point (ptp) access control and electronic service announcement (ESG) metadata for the SAs of the SA block 120 between the SM block 130 and the terminal 160. Used for The CBMS-5 interface is for a point-to-point transmission service between the SA block 120 and the terminal 160, and is a short message service (SMS) and a multimedia message service (MMS) through the bidirectional network 150. ) And so on. The CBMS-6 interface carries configuration parameters, such as the number of services and the allocated bandwidth, between the SM block 130 and the broadcast network 140 for DVB-H transmission. The CBMS-7 interface is used for the SA declaration between the SA block 120 and the SM block 130, or for the description of the SA, including content descriptions and metadata.

FIG. 2 is a diagram illustrating an architecture related to roaming based on the CBSM system of FIG. 1 and logical functional blocks within each entity.

Referring to FIG. 2, the SM blocks 212 and 232 belong to different networks 210 and 230 and may be mapped to respective IP platforms 214 and 234. The SM blocks 212 and 232 provide service and necessary signaling information to the terminals in the corresponding network 210 and 230 through the broadcast networks 218 and 238, and the corresponding blocks through the bidirectional networks 216 and 236. Communicate with terminals in networks 210 and 230. If the terminal 220 in the network 230 moves (224) within the service area of the home IP platform 234, this corresponds to the handover 202, the service of the IP platform 214 belonging to another network 210 Moving to area 222 corresponds to roaming 204. Therefore, the ID of the IP platform is an important parameter for distinguishing between handover and roaming.

In addition, when the terminal 220 roaming 204 to the neighboring network 210 via the broadcast network 238 managed by the SM block 232 in the network 230, the neighboring network 210. Roaming of the terminal 220 is supported through the bidirectional network 216. The bidirectional network 216 is here managed by the SM block 214. Specifically, the bidirectional network 216 is used to request and receive a special ESG including service guide information for roaming users in the neighbor network 210.

Accordingly, since the transmitter can distinguish between handover and roaming according to the movement of the terminal based on whether the SM is changed, when the roaming ESG is provided by identifying whether the SM is changed, the receiver (terminal) recognizes the roaming ESG. There is a need for a method of transmitting a roaming ESG so as to receive the transmitted roaming ESG at a receiver.

The present invention provides an apparatus and method for transmitting roaming ESG information for roaming users in a network of a CBMS system.

The present invention also provides an apparatus and method for receiving roaming ESG information transmitted for a roaming user in a terminal of a CBMS system.

In the digital broadcasting system according to the present invention, a method of transmitting an electronic service guide (ESG) for a roaming user includes: generating a special ESG representing services valid for roaming users in a network entered from another network; And setting the roaming ESG information according to the pre-selected transmission method, and transmitting the roaming ESG information.

In addition, in the digital broadcasting system according to the present invention, a method of receiving an electronic service announcement (ESG) for a roaming user includes: receiving, from a transmitter, roaming ESG information according to a special ESG indicating services available to roaming users in a network; Recognizing the roaming ESG information, and analyzing the recognized roaming ESG information to recognize the detailed roaming properties of the ESG.

In addition, in the digital broadcasting system according to the present invention, in the transmitter of an electronic service announcement (ESG) for roaming users, roaming ESG information according to a special ESG indicating services available to roaming users in a network entered from another network is set. And an ESG entity for positioning the set roaming ESG information according to a preselected transmission method, and a bidirectional network and a broadcast network for transmitting the roaming ESG information to a receiver.

In addition, the receiver of an electronic service announcement (ESG) for roaming users in the digital broadcasting system according to the present invention includes a bidirectional converter and a broadcast receiving roaming ESG information according to a special ESG indicating services available to roaming users in a network from a transmitter. A receiver and a control block for recognizing the roaming ESG information, and then analyzes the recognized roaming ESG information to recognize the detailed roaming properties of the ESG.

When the roaming ESG is provided by identifying whether the SM is changed by the transmitter, the roaming ESG information may be transmitted so that the receiver may recognize the roaming ESG information, and the receiver may receive the transmitted roaming ESG information.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. In describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description thereof will be omitted. 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.

First, in order to distinguish between rover and roaming according to the movement of the terminal, whether to change the SM may use the following identifiers.

1. Service provider ID (service provider URI, service provider ID): If a service provider can have its own SM, the service provider URI and / or service provider ID may be used to identify the SM. Can be.

2. ESG Provider ID (Provider URI, Provider ID)

If each ESG provider is deployed in its own SM, an ESG provider ID (provider URI, provider ID) or a pair of ESG provider ID and IP platform ID may be used to identify the SM.

3. IP platform ID

If one IP platform is mapped to exactly one SM and another SM cannot share one IP platform, an IP platform ID can be used to identify the SM.

4. SM ID

Each SM can be identified by defining an SM ID for each SM.

If the definition of handover and roaming is based on the service provider, the service provider ID, service URI can be used to identify each service provider. And if the definition of handover and roaming is based on the ESG provider, the provider URI and / or provider ID for the ESG provider can be used for identification. If the ESG provider is unique within one IP platform, the IP platform ID and ESG provider ID (provider URI and / or provider ID) may be used for identification.

One possible definition of the handover and loading is based on the IPDC Key Management System (KMS) and the IPDC Operator. The IPDC KMS is identified by IPDCKMSID, and the IPDC operator is identified by IPDCKMSID and IPDCOperatorID.

Handover and roaming may also be defined by other parameters for different rules and identifiers. In this case, the corresponding description and parameters herein may be changed or modified.

Hereinafter, when the transmitter (server) identifies roaming ESG information for a roaming user by identifying whether the SM has been changed from the ESG provider by using at least one of the above-described methods of identifying whether the SM has been changed, the roaming ESG information may be received by the receiver (server). A method of transmitting to the terminal) will be described.

First, there are two types of roaming, depending on whether the service selected by the user accessing the IPDC service on the new IP platform rather than the original IP platform is available on the new IP platform. Firstly, service roaming is supported when the selected service of the original IP platform can be received on the new IP platform, and the selected service is received through the transport stream provided by the new IP platform in the DVB-H network or in the bidirectional network. Received over the channel. User roaming is then supported when the selected service of the original IP platform cannot be received on the new IP platform, and the roaming user can access the services provided by the new IP platform rather than the original IP platform.

At the transmitter, ESGs for local users, or generic ESGs, are provided free to air over the broadcast network, where users visiting from neighboring networks, i.e. roaming users, are able to access the generic ESG through the broadcast network of the current network. Although it can receive, the general ESG alone makes it difficult to select the desired service correctly. Special ESGs are roaming ESGs that provide service announcement information for services expected for such roaming users. Unlike the general ESG, the content of the special ESG includes service guide information for the following types as an example. For the description of the service guide information, refer to Korean Patent Application No. 2007-0048703 by the same applicant and the same inventor.

1. Information about some or all services offered by the current network that are available to visiting users.

2. Information on the services specifically provided for visiting users in the current network, ie visited services, including local maps, service guidelines, local culture and local weather. useful information for visiting users, such as the introduction of weather). This information is useful to visiting users and supports a special kind of user roaming service. For example, a local map provided in a common language, ie English, rather than the local language, helps visitors to find their desired location.

3. Information about roaming services from available home networks. This may be information about the ESG of the home network (ie home ESG) or some home services available in the neighbor network.

Table 1 below shows a list of services for a user roaming service, a visited service, and a service roaming service according to the above-described service type for a special ESG.

Type Service list Related information User roaming service ServiceID ESG Provider ID IP address IP platform_id IPDCKMSID IPDCOperatorID ESGURI Service provider ID SM ID Service_id Original network_id Cell_id Network_id Frequency Right information Charging information ServiceID Visited service service ESG Provider ID IPDCKMSID IPDCOperatorID ESGURI IP address IP platform_id Service provider ID SM ID Service_id Transport stream_id Original network_id Cell_id Network_id Frequency Right information Charging information ServiceID ESG ProviderID Service roaming service IP address IP platform_id IPDCKMSID IPDCOperatorID ESGURI Service provider ID SM ID Service_id Transport stream_id Original network_id Cell_id Network_id Frequency Right information Charging information

According to an embodiment of the present invention, the transmitter may transmit service guide information (hereinafter, referred to as roaming ESG information) about services expected for the roaming user described in Table 1 to the receiver as follows.

The first method for transmitting the roaming ESG information at the transmitter is to send the roaming ESG information to the receiver by adding new elements and / or descriptors to the ESG bootstrap session. The second method is to send the roaming ESG information to the receiver by adding a new element and / or container to the Announcement Carousel FLUTE session. The third method is to send roaming ESG information to the receiver by using a new partition rule. The fourth method is to transmit the roaming ESG information through a notification message for notifying the receiver of changes in broadcast service and / or system. The last method is to transmit the roaming ESG information through independent signaling.

Hereinafter, a method of transmitting the roaming ESG information from the transmitter to the receiver will be described in detail.

Method 1: Positioning and transmitting roaming ESG information in a bootstrap session.

3 is a diagram illustrating a bootstrap session in which new elements and / or descriptors of roaming ESG information are added to data transmitted through an ESG bootstrap session (hereinafter, referred to as ESG bootstrap data) according to an embodiment of the present invention.

Referring to FIG. 3, roaming ESG is added by adding roaming ESG information 303 within a new element and / or descriptor of the ESG bootstrap data 302 included in the bootstrap session 301 for a special ESG. Display. The new descriptor may be an ESG Provider Discovery Descriptor and an ESG Access Descriptor. The roaming ESG information 303 may be inserted into one descriptor, or the roaming ESG information 303 may be used. A portion of may be inserted into the ESG provider discovery descriptor and the remaining portion may be inserted into the ESG access descriptor.

4 is a diagram illustrating a bootstrap session in which new elements and / or descriptors of roaming ESG information are added to a bootstrap session according to an embodiment of the present invention.

Referring to FIG. 4, the roaming ESG information is transmitted to the receiver by adding all or a portion of the roaming ESG information 403 within a new element and / or attribute descriptor of the bootstrap session 401 for the special ESG. do. The ESG provider delivery descriptor and the ESG access descriptor 402 are then delivered in the bootstrap session 401 for the special ESG.

5A and 5B illustrate examples of a bootstrap session in which bootstrap data of a local ESG and bootstrap data of a roaming ESG are separated according to an embodiment of the present invention.

Referring to FIG. 5A, bootstrap data 502 and roaming ESG bootstrap data 503 of a local ESG are separately transmitted in a bootstrap session 501 for a special ESG. 5B, the bootstrap data 512 of the local ESG may be present in the first bootstrap session 511 and the roaming ESG bootstrap data 514 may be present in the second bootstrap session 513, respectively.

The roaming ESG information described above may be accessed through a broadcast or bidirectional network, and the detailed access method is referred to Korean Patent Application No. 2007-0016831 by the same applicant and the same inventor.

Roaming ESG information for the new element and / or descriptor includes ESG origin identifier, ESG access scope type information, ESG user object, and service scope in ESG. Contains information.

Syntax of roaming ESG information for the new element and / or descriptor may be represented as in Table 2, Table 3, or Table 4 below.

<element name = "ESGAttribute" type = "ESGAttributeType" maxOccurs = "unbounded" /> <complexType name = "ESGAttributeType" /> <sequence> <element name = "ESGOriginIdentifier" type = "ESGOriginIdentifierType" /> <element name = " ESGAccessScope "type =" ESGAccessScopeType "/> <element name =" ESGUserObject "type =" ESGUserObjectType "minOccurs =" 0 "maxOccurs =" unbounded "/> <element name =" ESGAccessScope "type =" ESGAccessScopeType "/> minOccurs =" 0 "maxOccurs =" unbounded "/> <element name =" ServiceScope "type =" ServiceScopeType "/> minOccurs =" 0 "maxOccurs =" unbounded "/> <element name =" GographicInformation "type =" anyURI "/> < element name = "AccessNetwork" type = "anyURI" /> <element name = "ServiceProviderURI" type = "anyURI" /> <element name = "ServiceProviderID" type = "positiveInteger" /> <element name = "SMID" type = "positiveInteger" /> </ sequence> </ complexType>

<element name = "ESGAttribute" type = "ESGAttributeType" <complexType name = "ESGAttributeType" /> <sequence> <element name = "ESGOriginIdentifier" type = "ESGOriginIdentifierType" /> <element name = "ESGAccessScope" type = "ESGAccessScopeType" /> <element name = "ESGUserObject" type = "ESGUserObjectType" minOccurs = "0" maxOccurs = "unbounded" /> <element name = "ESGAccessScope" type = "ESGAccessScopeType" /> minOccurs = "0" maxOccurs = "unbounded" /> <element name = "ServiceScope" type = "ServiceScopeType" /> minOccurs = "0" maxOccurs = "unbounded" /> <element name = "GographicInformation" type = "anyURI" /> <element name = "AccessNetwork" type = "anyURI" /> <element name = "ServiceProviderURI" type = "anyURI" /> <element name = "ServiceProviderID" type = "positiveInteger" /> <element name = "SMID" type = "positiveInteger" /> </ sequence> </ complexType>

<element name = "ESGAttribute" type = "ESGAttributeType" <complexType name = "ESGAttributeType" /> <sequence> <element name = "ESGOriginIdentifier" type = "ESGOriginIdentifierType" /> minOccurs = "0" maxOccurs = "unbounded" /> <element name = "ESGAccessScope" type = "ESGAccessScopeType" /> <element name = "ESGUserObject" type = "ESGUserObjectType" minOccurs = "0" maxOccurs = "unbounded" /> <element name = "ESGAccessScope" type = "ESGAccessScopeType" /> minOccurs = "0" maxOccurs = "unbounded" /> <element name = "ServiceScope" type = "ServiceScopeType" /> minOccurs = "0" maxOccurs = "unbounded" /> <element name = "GographicInformation" type = " anyURI "/> <element name =" AccessNetwork "type =" anyURI "/> <element name =" ServiceProviderURI "type =" anyURI "/> <element name =" ServiceProviderID "type =" positiveInteger "/> <element name = "SMID" type = "positiveInteger" /> </ sequence> </ complexType>

Hereinafter, the main information elements included in the roaming ESG information will be described in more detail.

1.ESG origin identifier

With reference to the ESG origin identifier, the receiver can know the SM that creates and owns the ESG. The ESG origin identifier includes at least some of the following parameters: IP platform ID, provider URI, provider ID, IPDCKMSID, IPDCOperatorID, ESGURI, network ID, service provider URI, service provider ID, SM ID, and the like. The ESG origin identifier may provide location information of the ESG. The location information includes at least some of network_id, cell_id, Global Positioning System (GPS), or other location parameters.

In addition, the ESG origin identifier may include one or more IPDC operator identification information (IPDCKMSID and IPDCOperatorID). When one or more IPDC operator identification information is included as described above, each IPDC operator identification information included in one ESG origin identifier may be listed in turn.

Syntax of the ESG origin identifier may be represented as shown in Table 5, Table 6, or Table 7 below.

<complexType name = "ESGOriginIdentifierType"> <sequence> <element name = "IPPlatformID" type = "positiveInteger" /> <element name = "ProviderURI" type = "anyURI" /> <element name = "ProviderID" type = "positiveInteger "/> <element name =" ESGURI "type =" anyURI "/> <element name =" IPDC "type =" IPDCType "/> <element name =" NetworkID "type =" positiveInteger "/> <element name =" CellID "type =" positiveInteger "/> <element name =" GographicInformation "type =" anyURI "/> <element name =" AccessNetwork "type =" anyURI "/> <element name =" ServiceProviderURI "type =" anyURI "/ > <element name = "ServiceProviderID" type = "positiveInteger" /> <element name = "SMID" type = "positiveInteger" /> </ sequence> </ complexType> <complexType name = "IPDCType"> <sequence> <element name = "IPDCKMSId" type = "unsignedShort" /> <element name = "IPDCOperatorId" type = "string" />] </ sequence> </ complexType>

<complexType name = "ESGOriginIdentifierType"> <sequence> <element name = "IPPlatformID" type = "positiveInteger" /> <element name = "ProviderURI" type = "anyURI" /> <element name = "ProviderID" type = "positiveInteger "/> <element name =" ESGURI "type =" anyURI "/> <element name =" IPDC "type =" IPDCType "/> minOccurs =" 0 "maxOccurs =" unbounded "/> <element name =" NetworkID " type = "positiveInteger" /> <element name = "CellID" type = "positiveInteger" /> <element name = "GographicInformation" type = "anyURI" /> <element name = "AccessNetwork" type = "anyURI" /> < element name = "ServiceProviderURI" type = "anyURI" /> <element name = "ServiceProviderID" type = "positiveInteger" /> <element name = "SMID" type = "positiveInteger" /> </ sequence> </ complexType> < complexType name = "IPDCType"> <sequence> <element name = "IPDCKMSId" type = "unsignedShort" /> <element name = "IPDCOperatorId" type = "string" />] </ sequence> </ complexType>

<complexType name = "ESGOriginIdentifierType"> <sequence> <element name = "IPPlatformID" type = "positiveInteger" /> <element name = "ProviderURI" type = "anyURI" /> <element name = "ProviderID" type = "positiveInteger "/> <element name =" ESGURI "type =" anyURI "/> <element name =" IPDC "type =" IPDCType "/> minOccurs =" 0 "<element name =" NetworkID "type =" positiveInteger "/> <element name = "CellID" type = "positiveInteger" /> <element name = "GographicInformation" type = "anyURI" /> <element name = "AccessNetwork" type = "anyURI" /> <element name = "ServiceProviderURI" type = "anyURI" /> <element name = "ServiceProviderID" type = "positiveInteger" /> <element name = "SMID" type = "positiveInteger" /> </ sequence> </ complexType> <complexType name = "IPDCType"> <sequence> <element name = "IPDCKMSId" type = "unsignedShort" /> <element name = "IPDCOperatorId" type = "string" />] </ sequence> </ complexType>

2. ESG access scope type

When roaming supporting ESGs is introduced, various types are used, such as local ESGs, roaming ESGs for roaming users only, and ESGs of local and roaming combined ESG types, which are indicated by ESG access range type information. This means that the local ESG only delivers information about services for the local user. The roaming ESG for roaming users only means that only information about services for roaming users is delivered. The local and roaming combined ESG means that some of the ESG's information is for local users and some is for roaming users.

The syntax of the ESG access range type information may be expressed as shown in Table 8 or Table 9 below.

<ClassificationScheme uri = "urn: dvb: ipdc: esg: cs: ESGAccessScopeTypeCS:> <Term termID =" 1.0 "<Name xml: lang =" en "> ESG access scope type </ Name> <Definition xml: lang =" en "> Type of ESG access scope, eg local ESG, ESG only for roaming user, local and roaming combined ESG </ Definition> <Term termID =" 1.1> <Name xml: lang = "en"> local ESG </ Name > <Definition xml: lang = "en"> A local ESG </ Definition> <Term termID = "1.2> <Name xml: lang =" en "> ESG only for roaming user </ Name> <Definition xml: lang = "en"> A ESG only for roaming user </ Definition> <Term termID = "1.3> <Name xml: lang =" en "> local and roaming combined ESG </ Name> <Definition xml: lang =" en "> local and roaming combined ESG </ Definition> </ Term> </ Term> </ ClassificationScheme>

<simpleType name = "ESGAccessScopeType"> <restriction base = "string"> <enumeration value = "local ESG" /> <enumeration value = "ESG only for roaming user" /> <enumeration value = "local and roaming combined ESG" /> </ restriction> </ simpleType>

3. ESG user object

An ESG user object means that the ESG is for a specific roaming user, or for all users, regardless of local or other roaming users. For example, if the ESG is for roaming users from IP platform A or SM 1 or roaming users from IPDC operator K (identified by IPDCKMSID = M and IPDCOperatorID = N), detail of the ESG user object The identifier must be clearly indicated for the ESG. If an ESG is valid for multiple specific groups of roaming users, then the identifiers of each particular group of roaming user objects should be enumerated one by one for the ESG. The ESG user object includes at least some of the following parameters: IP platform ID, IPDCKMSID, IPDCOperatorID, provider URI, provider ID, network ID, service provider URI, service provider ID, SM ID, and the like.

In addition, the ESG user object may include multiple local IPDC KMS systems and operator identification information (local IPDCKMSID and Local IPDCOperatorID). Each of the multiple local IPDC KMS systems and operator identification information includes roaming IPDC operator identification information (s) (roaming IPDCKMSID and roaming IPDCOperatorID). In other words, the ESG for each local IPDC operator includes such an ESG user object. As an example, the ESG includes a list of all local IPDC operators and a list of roaming IPDC operators of all local IPDC operators. As another example, the ESG includes, in turn, the detail relationship between local IPDC operators and roaming IPDC operators.

Meanwhile, the ESG user object is for all users or a specific user. If a specific attribute value (eg, 'ESGUserObjectType') is true, the ESG is for all users. It is for. Details elements of a specific user object are listed as shown in Table 10 below.

<complexType name = "ESGUserObjectType"> <sequence> <element name = "IPPlatformID" type = "positiveInteger" /> <element name = "ProviderURI" type = "anyURI" /> <element name = "ProviderID" type = "positiveInteger "/> <element name =" SpecificIPDC "type =" IPDCType "/> <element name =" ESGURI "type =" anyURI "/> <element name =" NetworkID "type =" positiveInteger "/> <element name =" CellID "type =" positiveInteger "/> <element name =" GographicInformation "type =" anyURI "/> <element name =" ServiceProviderURI "type =" anyURI "/> <element name =" ServiceProviderID "type =" positiveInteger "/ > <element name = "SMID" type = "positiveInteger" /> </ sequence> <attribute name = "AllOrSpecific" type = "Boolean"> </ complexType> <complexType name = "IPDCType"> <sequence> <element name = "IPDCKMSId" type = "unsignedShort" /> <element name = "IPDCOperatorId" type = "string" />] </ sequence> </ complexType>

4. Scope of Service in ESG

Service types in the roaming ESG include a local service, a visiting service, and a service roaming service for the roaming user as shown in Table 1 above. The service range in the ESG means information about roaming services available among the service types in the ESG. For example, if the information about the local service is available, the provider identifier of the local service is provided as service range information in the roaming ESG. Similarly, when information about the visited service is available, a visited service provider identifier is provided, and if the information about the service roaming service is available, a provider identifier of a service roaming service is provided.

The syntax of the service range information in the ESG may be expressed as shown in Table 11 or Table 12 below.

Scope of the service in the ESG {local service visited service service roaming service If (local service) {IPPlatformID ProviderURI ProviderID IPDCKMSId IPDCOperatorId ESGURI NetworkID CellID GographicInformation ServiceProviderURI ServiceProviderID SMID} If (visited service) {IPPlatformID ProviderURI ProviderID IPDCKMSId GIDCOperatorID ServiceProviderID SMID} If (service roaming service) {IPPlatformID ProviderURI ProviderID IPDCKMSId IPDCOperatorId ESGURI NetworkID CellID GographicInformation ServiceProviderURI ServiceProviderID SMID}

Roaming ESG information for the above-described [Method 1] may be represented as shown in Table 13 below. The fields of roaming ESG information described in Table 13 may be used in whole or in part, and new fields may be added or modified.

Method 2: ESG  notice Carousel FLUTE  Roam in Session ESG  How to locate and send information.

Parameters of roaming ESG information are inserted in an ESG initial container or in an independent container. FIG. 6 is a diagram illustrating an ESG notification carousel FLUTE session in which new elements and / or descriptors of roaming ESG information are added to an ESG initial container according to an embodiment of the present invention, and FIG. 7 is according to another embodiment of the present invention. A diagram illustrating an ESG notification carousel FLUTE session in which new elements and / or descriptors of roaming ESG information are added to an independent container.

Referring to FIG. 6, parameters included in roaming ESG information are inserted into an attribute field of an ESG initial container 602 in an ESG notification carousel FLUTE session 601. Referring to FIG. 7, parameters included in roaming ESG information are inserted into an independent attribute container 702 in the notification carousel FLUTE session 701.

In another embodiment, roaming ESG information is inserted in the ESG notification carousel FLUTE session 601 in other locations as well as in the ESG initial container 602 or independent attribute container 702.

Meanwhile, the roaming ESG information may be transmitted through a plurality of ESG notification carousel FLUTE sessions as shown in FIGS. 8 to 10, and each ESG notification carousel FLUTE session includes one ESG subset having attribute fields of roaming ESG information. subset).

8 illustrates an example of an ESG notification carousel FLUTE session for local and roaming users according to an embodiment of the present invention. Referring to FIG. 8, one ESG notification carousel FLUTE session 810 is for an ESG subset for a local user and another ESG notification carousel FLUTE session 850 is for an ESG subset for a roaming user. .

Different ESG notification carousel FLUTE sessions may be indicated in different ways as shown in FIG. 9.

9 illustrates another example of an ESG notification carousel FLUTE session for local and roaming users according to an embodiment of the present invention. Referring to FIG. 9, the original ESG notification carousel FLUTE session 910 may include another ESG notification carousel FLUTE session 930 that includes an ESG subset for local users, and another ESG notification including an ESG subset for roaming users. The access information (including the IP address and port number) of the carousel FLUTE session 950 is indicated by the ESG access descriptor.

10 illustrates another example of an ESG notification carousel FLUTE session for local and roaming users according to an embodiment of the present invention. Referring to FIG. 10, in an ESG notification carousel FLUTE session 1010, the ESG subset notification carousel FLUTE session access descriptor 1011 may specify the IP address and port number of another ESG notification carousel FLUTE session 1050 for another subset. (port number) can be indicated.

Method 3: ESG Partitioning

A method of transmitting the roaming ESG information to a receiver using a partitioning rule of the ESG in a transmitter, a method of transmitting one roaming ESG information in one IP flow and a method of partitioning into a plurality of IP flows have.

When one roaming ESG information is divided into a plurality of IP flows and transmitted, transmission efficiency is improved, and the receiver receives only the information of the desired IP flow and has the advantage of decoding. In addition, when one roaming ESG information is divided into a plurality of IP flows and transmitted, information about which IP flows and parameters of which roaming ESG information are transmitted is known to the receiver in advance. That is, information about the ESG partitioning rule is transmitted to the receiver in advance. Detailed operation thereof is described in the DVB CBMS ESG specification (ETSI TS 102 471). According to an embodiment of the present invention, roaming ESG information may be transmitted to a receiver using an ESG partitioning rule shown in Table 14 below.

In Table 14, 'value' indicates which partitioning rule is used, and 'encoding' indicates what data type the rule is represented. [0x00] and [0x01] represent the [the number of hours] rule and the [ServiceID] rule. The [the number of hours] rule transmits the roaming ESG information by time zone, and the [ServiceID] rule transmits the service ID by division.

And [0x30] represents a [specific ESG partitioning] rule in which roaming ESG information is transmitted. The encoding value of the [specific ESG partitioning] rule may be [0x0101 (unsigned short)] or may be a [0x0204 (Boolean)] value. In the case of [0x0101 (unsigned short)], a specific value may be assigned to indicate that the rule is used, or [0x0204 (Boolean)] may be assigned to indicate whether the rule is used as a boolean value.

Method 4: notification message

The transmitter may transmit the roaming ESG related information to the receiver by a notification message. The format of the notification message refers to Korean Patent Application No. 2006-0092506 made by the same applicant and the same inventor. In the format of the notification message, if a field of event type (EventType) is included in the notification header, when roaming ESG information is included in the notification and delivered, the field of the event type is set as the roaming ESG type and the detailed roaming ESG information is It can be delivered as the content of the notification message. When roaming ESG information is included, the event type field and detailed information of the notification message are shown in Table 15 below.

Method 5: Roaming ESG Information Signaling

The transmitter transmits roaming ESG information to the receiver using independent signaling. As an example, the transmitter transmits roaming ESG information when querying and requesting at the receiver. The format of roaming ESG information delivered through the independent signaling may be represented as shown in Table 15 below. For example, the receiver imposes some restrictions on roaming ESG information to the transmitter by setting the ESG origin identifier, ESG access range type information, ESG user object, service range information in the ESG as part of the query message. The transmitter responds to roaming ESG information in a format as shown in Table 16 through independent signaling when requested by the receiver.

Hereinafter, a procedure of transmitting and receiving roaming ESG information between a transmitter and a receiver according to an embodiment of the present invention will be described with reference to the drawings.

11 is a flowchart illustrating a method of transmitting roaming ESG information in a transmitter according to an embodiment of the present invention.

In steps 1101 to 1107 of FIG. 11, the transmitter sets roaming ESG information according to detailed local and roaming attributes of the ESG. Referring to steps 1101 to 1107 in detail, as described above, the roaming ESG information includes at least one of an ESG origin identifier, an ESG access range type, an ESG user object, and a service range in an ESG. Accordingly, the transmitter sets an ESG origin identifier among roaming ESG information in step 1101, sets an ESG access range type in step 1103, sets an ESG user object in step 1105, and sets a service range in the ESG in step 1107. do.

In step 1109 of FIG. 11, the transmitter transmits roaming ESG information by placing the roaming ESG in the bootstrap session, placing the roaming ESG information in the ESG notification carousel FLUTE session, and partitioning and roaming ESG. Transmit the set roaming ESG information to the receiver according to at least one selected transmission method (information notification, roaming ESG information signaling).

12 is a flowchart illustrating a method of receiving roaming ESG information in a receiver according to an embodiment of the present invention. In step 1201 of FIG. 12, the receiver receives roaming ESG information transmitted from a transmitter according to at least one of the above-described transmission methods.

In step 1201, the receiver analyzes and recognizes roaming ESG information according to a transmitter's transmission method. That is, when the roaming ESG is located and transmitted from the transmitter to the bootstrap session, the receiver obtains and analyzes the roaming ESG information from descriptors of the ESG bootstrap session. When the roaming ESG information is located and transmitted from the transmitter to the ESG notification carousel FLUTE session, the receiver obtains and analyzes the roaming ESG information from the descriptor of the ESG notification carousel FLUTE session. In addition, when roaming ESG information is transmitted from the transmitter using the ESG partitioning transmission method, the receiver obtains and analyzes the roaming ESG information from the descriptor of the ESG partitioning rule. In addition, when roaming ESG information is transmitted from the transmitter using the roaming ESG information notification transmission method, the receiver acquires and analyzes the roaming ESG information from the descriptor of the ESG information notification message. In addition, when roaming ESG information is transmitted from the transmitter using the ESG signaling transmission method, the receiver obtains and analyzes the roaming ESG information from the descriptor of ESG signaling.

In step 1203 of FIG. 12, the receiver recognizes an SM that generates and owns the roaming ESG information from the ESG origin identifier among the received roaming ESG information. In operation 1205, the receiver recognizes whether the roaming ESG information is available from an ESG access range type among the received roaming ESG information. In step 1207, the receiver recognizes whether the roaming ESG information is accessible from an ESG user object among the received roaming ESG information. In step 1209, the receiver recognizes a type of service information transferred from the service range of the ESG to the roaming ESG information among the received roaming ESG information.

In step 1211, the receiver analyzes the recognized roaming ESG information to recognize detailed roaming properties of the ESG information.

13 is a diagram illustrating a transmitter for transmitting roaming ESG information according to an embodiment of the present invention. Referring to FIG. 13, a transmitter for transmitting roaming ESG information includes an SA block 1301 and an SM block 1303.

The SA block 1301 collects content sources for the special ESG received from the content provider and additionally metadata necessary for service configuration, thereby roaming the ESG for the service used in the ESG. Generate information. The SA block 1301 generates roaming ESG information by configuring to transmit content encoded in a format that can be transmitted to a receiver through streaming or file carousel delivery. The SA block 1301 further includes the above-described transmission method (a method of positioning and transmitting roaming ESGs in a bootstrap session, a method of placing and transmitting roaming ESG information in an ESG notification carousel FLUTE session, ESG partitioning, and roaming ESG information notifications). And roaming ESG information signaling) so as to transmit the roaming ESG information. The SA block 1301 provides head end application logic and service protection, and may have each application provided for an IP datacast.

The SM block 1303 includes a service guide provisioning application block 1305, a service configuration & resource allocation block 1307, and provides security / service protection. service protection provision 1309 and the sub-entities of a location services block 1311.

The service configuration and resource allocation block 1307 allocates competing service applications for the bandwidth of the broadcast bearer. That is, one DVB? H IP platform is allocated to one DVB transport stream. The service configuration and resource allocation block 1307 then allocates for the service location (eg, broadcast network topology), bandwidth, and schedule service over time. The service guide providing application 1307 collects parameters of roaming ESG information from SA block 1301. The security / service protection provision block 1309 manages user access to the SA block 1301. The location service block 1311 provides location services to a service application, for example, with a two-way bearer network function or a GPS function.

14 illustrates a receiver for receiving roaming ESG information according to an embodiment of the present invention.

Referring to FIG. 14, a receiver for receiving roaming ESG information refers to a user terminal 1401. The broadcast receiver 1403 at the terminal 1401 receives service data or signaling (including roaming ESG information) from the broadcast network. The interactive adapter 1405 transmits and receives service data or signaling (including roaming ESG information) through a bidirectional network. The control block 1407 is responsible for the mobility process and analyzes and recognizes roaming ESG information according to the method of transmitting roaming ESG information, and subscription management block 1409 maintains rights acquisition management and tracking of acquired rights. Control the analysis of the service content. The content consumption block 1411 consumes content and also provides roaming ESG information to the user.

Meanwhile, the IPDC KMS system and the IPDC operator play a role for correct management, and the IPDC KMS system and the IPDC operator are identified by IPDCKMSID and / or IPDCOperatorID. When the role of subscription and correct management of the IPDC KMS system and the IPDC operator is changed, roaming ESG information may be modified with a new parameter to support the IPDC KMS system and the IPDC operator.

Hereinafter, examples to which embodiments of the present invention are applied will be described with reference to the drawings.

15 is a diagram illustrating a network structure according to an embodiment to which an embodiment of the present invention is applied.

Referring to FIG. 15, in the first area, the first terminal is a local user. The first terminal is subscribed to an IPDC operator having an identifier of IPDCKMSID = 1 and IPDCOperator = 1 as ESG origin identifier, and the service is valid at ESGURI = 1 and IP platformID = 1. Here, when the first terminal accesses ESGURI = 1, the first terminal discovers the subscribed IPDC operators (IPDCKMSID = 1 and IPDCOperator = 1). In this case, the IPDC KMS system and the IPDC operator (IPDCKMSID = 1, IPDCOperatorID = 1) may make a roaming agreement with another IPDC KMS system and the IPDC operator.

16 is a diagram illustrating a network structure according to another example to which an embodiment of the present invention is applied.

Referring to FIG. 16, in the first area, the first terminal is a local user, and the second terminal and the third terminal are roaming users. The first terminal is subscribed to IPDC operator 1 having an identifier of IPDCKMSID = 1 and IPDCOperator = 1 as ESG origin identifier, and the service is valid at ESGURI = 1 and IP platformID = 1. The second terminal is subscribed to IPDC operator 2 having an identifier of IPDCKMSID = 2 and IPDCOperator = 2, and the third terminal is subscribed to IPDC operator 3 having an identifier of IPDCKMSID = 3 and IPDCOperator = 3.

Here, IPDC operator 1 having IPDCKMSID = 1 and IPDCOperatorID = 1 performs local management, and when a roaming agreement is made with IPDC operator 2, a second terminal subscribed to IPDC operator 2 is IPDC operator 1 due to the roaming agreement. Access to services from That is, the user object of ESGURI is for not only the first terminal subscribed to IPDC operator 1 but also the second terminal subscribed to IPDC operator 2. On the other hand, since the third terminal subscribed to the IPDC operator 3 has no roaming agreement with the IPDC operator 1, the third terminal subscribed to the IPDC operator 3 cannot access the service by the IPDC operator 1.

Meanwhile, information about the roaming partner for roaming support may be instructed in advance. For example, in the ESG user object, the local (or original) IPDCKMSID and the IPDCOperatorID of the ESG are indicated one by one. Roaming partners for each local IPDCO operator are listed one by one as shown in Table 17 below.

As shown in Table 17, the roaming ESG information may include one or more sets of IPDCKMSID and IPDCOperatorID. Each set of IPDCKMSID and IPDCOperatorID included in roaming ESG information may include corresponding roaming partner identification information (roaming IPDCKMSID and roaming IPDCOperatorID). As described above, when each set of IPDCKMSID and IPDCOperatorID includes roaming partner identification information, each set of local IPDCKMSID and IPDCOperatorID is represented as IPDCKMSID and IPDCOperatorID as shown in FIG. 17 showing local and roaming IPDC operator identification information included in each ESG information. Instructs the IPDC operator identification information of the roaming partner configured in turn one by one.

Detailed information about all local IPDC operators and roaming partners of all local IPDC operators may be indicated as shown in Table 18 below.

In another embodiment, the roaming ESG information indicates a local IPDC operator and all roaming IPDC operators, but the relationship between each local IPDC operator and the partner roaming IPDC operator of each local IPDC operator is shown in <Table 19> or <Table 20> or < Like the syntax in Table 21, this may not be explicitly indicated.

If each local IPDC operator includes multiple roaming IPDC operators, there is a large burden that each roaming IPDC operator identification information must be listed one by one. Accordingly, the most frequently used roaming IPDC operators can be selected and listed in the roaming ESG information.

Roaming partners are updated every predetermined time. The newly subscribed roaming IPDC operator identification view may not be added for each ESG at an ESG bootstrap session, Program Specific Information / Service Information (PSI / SI) or at a predetermined location. If the terminal cannot find a subscribed IPDC operator in the roaming IPDC operator list, the terminal may attempt to access the ESG by finding the same IPDCKMSID and using the found IPDCKMSID. The reason for attempting to access the ESG as described above is because the terminal has an opportunity to access the service from the IPDC operator if there is a roaming agreement in advance.

Hereinafter, for example, when the roaming IPDC operator identification information is located at a predetermined position in roaming ESG information, a process of transmitting IPDC operator identification information from a server to access or purchase a service, and IPDC operator identification information at a terminal. It will be described the process of receiving.

18 is a diagram illustrating a process of transmitting IPDC operator identification information at a predetermined position by a server according to an embodiment of the present invention. In the following description, it is assumed that the predetermined position is an ESG bootstrap session.

Referring to FIG. 18, in step 1801, the server lists local IPDC operator identification information (local IPDCOKMSID and local IPDCOperatorID). In operation 1803, the server selects roaming partners for each local IPDC operator whose roaming IPDCKMSID and roaming IPDCOperatorID are listed.

In step 1805, the server includes local IPDCR operator identification information and roaming IPDCR operator identification information in the IPDC operator identification information.

In step 1807, the server transmits the IPDC operator identification information including the local IPDCR operator identification information and the roaming IPDCR operator identification information to the terminal in a bootstrap session.

19 is a diagram illustrating a process of receiving IPDC operator identification information located at a predetermined location in a terminal according to an embodiment of the present invention.

Referring to FIG. 19, in step 1901, the UE acquires PSI / SI, and in step 1903, selects an available IP platform for an ESG bootstrap session using the PSI / SI. In step 1905, the UE checks IPDC operator identification information in the ESG bootstrap session. In step 1907, the terminal determines whether the IPDC operator identification information of the terminal is included in the checked local or roaming IPDC operator identification information. When the IPDC operator identification information of the terminal is included in the checked local IPDC operator identification information, step 1909. If the IPDC operator identification information of the terminal is included in the checked roaming IPDC operator identification information, the process proceeds to step 1911, and if the IPDC operator identification information of the terminal is not included anywhere, proceeds to step 1913.

In step 1909, the terminal determines that the associated ESG can be accessed when the IPDC operator identification information of the terminal is included in the checked local IPDC operator identification information, and selects the ESG having the IPDC operator identification information of the terminal.

In step 1911, when the terminal includes the roaming IPDC operator identification information, the terminal determines that the associated ESG can be accessed, and selects an ESG having the roaming partner's IPDC operator identification information.

On the other hand, if the IPDC operator identification information of the terminal is not included anywhere in step 1913 (for example, it includes a local IPDCKMSID but does not include a local or roaming IPDCOperatorID), try to access the service or subscribe to the service Select the ESG having any IPDC operator identification information.

In step 1915, the UE accesses the selected ESG to obtain ESG information, and in step 1917, the UE accesses or subscribes to the service using the acquired ESG information. On the other hand, in accessing the service or attempting to subscribe to the service in step 1917, if the roaming agreement is confirmed, the attempt is successful, accessing or subscribing to the service, and if the roaming agreement is not confirmed, the attempt is failed. Cannot access or subscribe.

On the other hand, in the roaming scenario, local IPDC operator identification information is located in the ESG bootstrap session, but roaming partners for each local IPDC operator are not indicated or the list of roaming partners is not complete. In this case, it is difficult for a roaming user's terminal to select an appropriate ESG that includes an accessible service. Accordingly, a method of selecting an appropriate ESG including a service accessible through a query mechanism may be provided.

Hereinafter, a process of transmitting and receiving IPDC operator identification information by a combined mechanism according to an embodiment of the present invention will be described with reference to FIGS. 20 and 21. The combined mechanism is a method of combining the IPDC operator identification information at a predetermined position (eg, an ESG bootstrap session) and a query mechanism.

20 is a flowchart illustrating a process of transmitting IPDC operator identification information by a combined mechanism in a server according to an embodiment of the present invention.

Referring to FIG. 20, in step 2001, the server indicates all local IPDC operator identification information for each ESG to an ESG bootstrap session, which is a predetermined location. In step 2003, the server receives the ESG bootstrap query from the terminal having the IPDC operator identification information. Next, in step 2005, the server determines whether the IPDC operator identification information of the terminal indicates the roaming partner having the local IPDC operator through the received ESG bootstrap query, and if the server indicates the roaming partner having the local IPDC operator, in step 2007. Proceed to step 2009 if no roaming partner having a local IPDC operator is instructed.

In step 2007, the server collects all the ESG bootstrap information related to the local IPDC operator and transmits to the terminal. In step 2009, the server transmits the failure information to the terminal.

21 is a flowchart illustrating a process of receiving IPDC operator identification information by a combined mechanism in a terminal according to an embodiment of the present invention.

Referring to FIG. 21, in step 2101, the UE acquires PSI / SI, which is a control signal related to a broadcast service, and selects an available IP platform for ESG bootstrap using the PSI / SI in step 2103. In step 2105, the UE checks the IPDC operator identification information through the ESG bootstrap session. In step 2107, the terminal determines whether the IPDC operator identification information of the terminal is included in the local IPDC operator identification information, and if it is included in step 2109, the terminal proceeds to step 2113.

In step 2109, the terminal transmits an ESG bootstrap query to the server including the IPDC operator identification information of the terminal. In operation 2111, the terminal determines that the roaming partner for the IPDC operator of the terminal is one of the local operators, and may receive ESG information related to the local IPDC operator.

In contrast, in step 2113, the UE selects an ESG having ESG information having IPDC operator identification information of the UE.

In step 2115, the UE accesses the ESG to obtain ESG information, and the UE accesses or subscribes to the service using the ESG information acquired in step 2117. As described above, the embodiment described with reference to FIGS. A method of placing and transmitting IPDC operator identification information at a location has been used, and in the embodiments described with reference to FIGS. 20 and 21, a combined mechanism is used. In addition to the methods described above, it is also possible to use the query mechanism independently. When using the query mechanism independently, the terminal does not check the indicated IPDC operator identification information, but queries only with the expected IPDC operator identification information (for example, IPDC operator identification information of the IP platform).

If the terminal wants to query the ESG information (ESG bootstrap information) included in the ESG bootstrap session from one specific IPDC operator on some specific IP platforms, the query message is shown in Table 22 below. Can be represented.

If the terminal wants to query the ESG bootstrap from one specific IPDC operator on all IP platforms, the query message may be expressed as shown in Table 23 below.

1 is a block diagram showing the structure of a CBMS system;

FIG. 2 is a diagram illustrating an architecture related to roaming based on the CBSM system of FIG. 1 and logical functional blocks within each entity; FIG.

3 is a diagram illustrating a bootstrap session in which new elements and / or descriptors are added to existing ESG bootstrap data according to an embodiment of the present invention;

4 illustrates a bootstrap session in which new elements and / or descriptors are added to the bootstrap session according to an embodiment of the present invention;

5A and 5B illustrate a bootstrap session in which bootstrap data of a local ESG and bootstrap data of a roaming ESG are separated according to an embodiment of the present invention;

6 illustrates an ESG notification carousel FLUTE session in which a new element and / or descriptor is added to an initial container of an ESG according to an embodiment of the present invention;

7 is a diagram illustrating an ESG notification carousel FLUTE session in which new elements and / or descriptors are added to an independent container according to an embodiment of the present invention;

8 illustrates an example of an ESG notification carousel FLUTE session for local and roaming users according to an embodiment of the present invention;

9 illustrates another example of an ESG notification carousel FLUTE session for local and roaming users according to an embodiment of the present invention;

10 is a view showing another example of an ESG notification carousel FLUTE session for local and roaming users according to an embodiment of the present invention;

11 is a flowchart illustrating a method of transmitting roaming ESG information in a transmitter according to an embodiment of the present invention;

12 is a flowchart illustrating a method of receiving roaming ESG information in a receiver according to an embodiment of the present invention;

13 is a diagram illustrating a transmitter for transmitting roaming ESG information according to an embodiment of the present invention;

14 illustrates a receiver for receiving roaming ESG information according to an embodiment of the present invention;

15 is a view showing an example to which an embodiment of the present invention is applied;

16 is a view showing another example to which an embodiment of the present invention is applied;

17 illustrates roaming and local IPDC operator identification information;

18 is a diagram illustrating a process of transmitting IPDC operator identification information at a predetermined position by a transmitter according to an embodiment of the present invention;

19 illustrates a method of receiving IPDC operator identification information located at a predetermined location in a receiver according to an embodiment of the present invention;

20 is a flowchart illustrating a method for transmitting IPDC operator identification information by a combined mechanism in a transmitter according to an embodiment of the present invention;

21 is a flowchart illustrating a method of receiving IPDC operator identification information by a combined mechanism in a receiver according to an embodiment of the present invention.

Claims (10)

A method of transmitting an electronic service announcement (ESG) for a roaming user in a digital broadcasting system, Creating a special ESG representing services available to roaming users in a network entering from another network; Setting roaming ESG information according to the special ESG; And transmitting the roaming ESG information by locating the set roaming ESG information according to a preselected transmission method. The method of claim 1, wherein the roaming ESG information, An ESG origin identifier for the SM that creates and owns the ESG, an ESG access range type for the range in which the ESG is available, an ESG user object for the user information of the ESG, and a roaming service available in the ESG. A transmission method comprising at least one of a service range in the ESG for the service. The method of claim 1, wherein the transmission method, A method of positioning and transmitting a roaming ESG in a bootstrap session, a method of positioning and transmitting roaming ESG information in an ESG notification carousel FLUTE session, an ESG partitioning method, a roaming ESG information notification method, and a roaming ESG information signaling method. A transmission method comprising at least one. A method of receiving an electronic service announcement (ESG) for a roaming user in a digital broadcasting system, Receiving roaming ESG information according to a special ESG representing services available to roaming users in the network from a transmitter, Recognizing the roaming ESG information; And analyzing the recognized roaming ESG information to recognize detailed roaming properties of the ESG. The method of claim 4, wherein the roaming ESG information, An ESG origin identifier for the SM that creates and owns the ESG, an ESG access range type for the range in which the ESG is available, an ESG user object for the user information of the ESG, and a roaming service available in the ESG. Receiving method comprising at least one of the service range in the ESG. A transmitter of an electronic service announcement (ESG) for a roaming user in a digital broadcasting system, An ESG entity that sets roaming ESG information according to a special ESG representing services available to roaming users in a network entering from another network, and locates the set roaming ESG information according to a previously selected transmission method; And an interactive network and a broadcast network for transmitting the roaming ESG information to a receiver. The method of claim 6, wherein the roaming ESG information, An ESG origin identifier for the SM that creates and owns the ESG, an ESG access range type for the range in which the ESG is available, an ESG user object for the user information of the ESG, and a roaming service available in the ESG. ESG transmitter comprising at least one of the service range in the ESG for. The method of claim 6, wherein the transmission method, How to locate and transmit roaming ESG in bootstrap session, How to locate and transmit roaming ESG information in ESG notification carousel FLUTE session, ESG partitioning method, Roaming ESG information notification method, Roaming ESG information signaling method ESG transmitter containing. A receiver of an electronic service announcement (ESG) for a roaming user in a digital broadcasting system, A bidirectional converter and broadcast receiver for receiving roaming ESG information according to a special ESG representing services available to roaming users in the network from a transmitter, After recognizing the roaming ESG information, the ESG receiver including a control block for recognizing the roaming properties of the ESG by analyzing the recognized roaming ESG information. The method of claim 9, wherein the roaming ESG information, An ESG origin identifier for the SM that creates and owns the ESG, an ESG access range type for the range in which the ESG is available, an ESG user object for the user information of the ESG, and a roaming service available in the ESG. An ESG receiver comprising at least one of the service ranges for the ESG.

Images