KR100913097B1 - A method of performing parental control a channel for building a channel map in an ???? receiver and apparatus thereof - Google Patents

Abstract

The present invention relates to a method and apparatus for performing parental control to form a channel map in an IPTV receiver. The present invention relates to a method for building a channel map using a plurality of tables in service information during a service discovery process in an IPTV receiver according to the present invention. An example of a method of performing viewing restriction on a virtual channel afterwards receives a virtual channel map table defining a virtual channel map instance. Parse first location information about the virtual channel description table in the received virtual channel map table. The virtual channel description table for defining virtual channel descriptions for the virtual channel in the virtual channel map is received according to the parsed first location information. Parse parental restriction information indicating a default parental guidance associated with the rating system of the virtual channel in the received virtual channel description table. The viewing is restricted for the corresponding virtual channel. Therefore, according to the present invention, viewing of a virtual channel rather than content can be restricted, so that user convenience can be pursued.

IPTV, Channel Map, Services, RRT, Parental Control

Description

A method of performing parental control a channel for building a channel map in an IPT receiver and apparatus about

The present invention relates to a method and apparatus for performing parental control in order to form a channel map in an IPTV receiver, and more particularly, to a method and apparatus capable of performing parental control for each virtual channel.

The broadcasting environment was separated from each other using the conventional terrestrial, cable, and satellite media, but it is becoming more and more integrated. In this process, an IPTV environment for providing services based on IP has recently been created and related standards have been made. For example, channel-based services still exist in IPTV environments.

In relation to this, there are various contents and services in the IPTV environment. Therefore, there is a need for viewing restriction on each content and service properly in the IPTV environment. If not, there is a problem that may inconvenience the user.

The present invention aims to solve the above problems, and an object of the present invention is to enable an IPTV receiver, that is, an ITTV (IPTV Terminal Function), to perform parental control for each virtual channel.

Another object of the present invention is to provide a method and apparatus for viewing restriction on each virtual channel.

Another object of the present invention is to enable the ITF to determine whether to access each virtual channel and whether to provide the guide information for the virtual channel.

Hereinafter, in order to achieve the above object, a channel map is generated using a plurality of tables in service information in a service discovery process in an IPTV receiver according to the present invention. An example of a method of performing viewing restrictions on a virtual channel after building, receives a virtual channel map table defining a virtual channel map instance. do. Parsing first location information about a virtual channel description table in the received virtual channel map table. The virtual channel description table defining virtual channel descriptions for virtual channels in the virtual channel map is received according to the parsed first location information. Parse parental restriction information indicating default parental guidance associated with a rating system of the virtual channel in the received virtual channel description table. The viewing is restricted for the corresponding virtual channel.
At this time, in the service provider discovery process, among the detailed information on the service provider, the authentication server location information of the service provider, and the connection server location information for the service provider attachment, It may further receive a service provider information record (serviceproviderinfo record) including at least one.
Further, an authentication information record may be further received according to the authentication server location information in the received service provider information record.
In addition, a provision information record for accessing an authenticated service provider may be further received based on the received authentication information record.
The second location information of the master service information table in the received provision information record may be further parsed.
In addition, the server may further receive a master service information table including a list of virtual channel map tables according to the parsed second location information.
The third location information of the virtual channel map table in the received master service information table may be further parsed.
The provision information record further includes EPG provider information that provides electronic program guide (EPG) data, wherein the EPG data received according to the EPG provider information is for different regions. It may include a rating region table (RRT) table that provides the allowed values with respect to the viewing restriction information, and program description information that provides detailed information about program contents and services. .
The EPG data may further include virtual channel identifier information and service identifier reference information.
The viewing restriction information in the virtual channel description table and the viewing restriction information in EPG data may each include at least one of attribute information of a rating area, dimension information defining a dimension, and rating description information describing ratings. Can be.
In addition, the dimension information may include rating dimension information for identifying a rating dimension and rating value information for identifying a rating value.
The EPG data may be linked with the virtual channel description table based on link information, and may be used to restrict viewing of the virtual channel.
The link information may include virtual channel identifier information in the EPG data and virtual channel identifier information in the virtual channel description.
An example of an IPTV receiver according to the present invention includes an IP network stack for receiving an IP protocol stream including service information data and program guide data, and the received IP stream. File handler demultiplexing service information data and program guide data included in the master, master service information table, virtual channel map table, and virtual channel defaults Service information handler that demultiplexes a virtual channel description table that includes a first element indicating that there is a default parental guidance rating, a default pair of virtual channels to demultiplexed program guide data. 2nd Elliman indicating that there is a LAN Guidance Rating A program guide handler for demultiplexing a rating region table (RRT) comprising: a service information decoder for parsing the first element from the demultiplexed virtual channel description table; and parsing the first element from the demultiplexed RRT A program guide parser, and a control unit configured to control to display and apply a rating based on a type of a parental guidance system according to the parsed first and second elements.
In this case, the controller may control to display a program guide screen based on the parsed second element.
The apparatus may further include a storage configured to store the demultiplexed master service information table, a virtual channel map table, a virtual channel description table, and an RRT.
The display apparatus may further include a display unit displaying the displayed program guide screen and the virtual channel service.

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

delete

Therefore, according to the parental control method and the IPTV receiver according to the present invention, it is possible to restrict the viewing of the virtual channel instead of the content, so that the convenience of the user can be pursued.

Hereinafter, with reference to the accompanying drawings, preferred embodiments of the present invention that can specifically realize the above object will be described. At this time, the configuration and operation of the present invention shown in the drawings and described by it will be described as at least one embodiment, by which the technical spirit of the present invention and its core configuration and operation is not limited.

The terms used in the present invention have been selected as widely used general terms as possible in consideration of the functions in the present invention, but may vary according to the intention or custom of the person skilled in the art or the emergence of new technologies. In addition, in certain cases, there is also a term arbitrarily selected by the applicant, in which case the meaning will be described in detail in the description of the invention. Therefore, it is intended that the terms used in the present invention should be defined based on the meanings of the terms and the general contents of the present invention rather than the names of the simple terms.

1 is a system configuration diagram illustrating the concept of an IPTV service.

Referring to FIG. 1, an IPTV system includes a service provider domain, a network provider domain, and a consumer domain.

The service provider area may include a content provider and a service provider. The content provider serves to provide content to a service provider. The service provider serves to provide a service to subscribers, collects various contents, and modifies a signal according to an IP environment and delivers it to a user. In addition, the service provider transmits multimedia data, and provides infrastructure and functions for network management and maintenance of the transmission network to enable stable reception of content to the customer. In this case, the service provider may be a virtual entity, and the content provider may be the service provider.

The network provider area serves to connect a user and a service provider through an IP network. The transmission system may use various network networks, such as an access network, a backbone network, or a wireless wide area network (WAN).

The customer area is an area consuming an IPTV service. The customer domain plays a role in reproducing incoming data using an infrastructure such as a digital subscriber loop (xDSL) or a cable and reacting immediately to a user's request. Most of them are made up of companies that produce IPTV, and the types can be divided into IPTV, IP set-top box (STB), and IP phone. The customer area device may be used to receive content from the customer area and receive a broadcast. The customer area device may include a set top box (STB), a personal computer (PC), a mobile terminal, an IPTV terminal function (ITF) device, or a delivery network gateway (DNG) device.

Learn more about each area.

First, a content provider may include a TV station and a radio station that make a broadcast program. A TV station means a conventional terrestrial or cable station, which can create and store a program that users can watch and convert it digitally. In general, it is to be able to transmit in various broadcast forms.

Radio station means a general radio station, and although there may be video channels at times, it can be said that most of them operate without a video channel. Video on Demand (VoD) and Audio on Demand (AoD) services have different characteristics from TV stations and radio stations. Content providers will also store and store programs for broadcast, but this is a live broadcast with continuity, which can't be rewound or stopped unless recorded. However, in the case of VoD or AoD, I store the broadcasting program, movie, music, etc. that I want and then play it for viewing. For example, if there is a broadcast program that was not properly watched because there is no current time, it is possible to access a site that provides such a broadcast service and download the file or play it back. AoD also offers the ability to record audio programs in real time or make it difficult to record audio programs. Music on Demand (MoD) service can download and listen to the music I want. MoD's services can be performed by record labels or record distributors by extending existing web services.

Hereinafter, an embodiment of a service provided by a content provider will be described.

The PF server can be serviced by a company that manages all broadcasting information and location information provided by the content provider. This service mainly contains broadcasting time or location information necessary for broadcasting and information that a user can access. The user can obtain this information and display it on the screen. The PF server is one of services that each broadcasting station should provide, so that the user can access the broadcasting station by providing the service in the IPTV environment.

The EPG service is one of convenient services that allows a user to search a broadcast program by time zone and to grasp by channel. The EPG service is already installed so that the program can be automatically installed and executed on the user's side. The user can only obtain information on the corresponding broadcasting station from the PF server, but the EPG service can obtain information on the real time broadcasting channels of all broadcasting stations at once, which is very convenient. For example, it has a powerful built-in function to schedule recording of CNN news or to schedule watching a Disney broadcast. Therefore, the EPG service must provide the information of the broadcasting program of the corresponding region in detail for each time zone. In particular, in some dramas, the contents of a drama can be searched or divided into categories, so that SF, Drama, and Animation can be distinguished. Information may also be included. A major problem of the EPG service is that there are many types of licenses for users watching IPTV, and thus, how to transmit EPG data suitable for the user may be a problem. To access the EPG service, the user simply finds and presses an input key on the remote control.

The electronic contents guide (ECG) service has all the functions for the user to conveniently use the content provider's content information, access server location and access rights. In short, it is an Electronic Content Guide (ECG) that provides detailed information about the content and functions that make it easy to access servers with content. In other words, rather than real-time broadcasting, services such as AoD, MoD, and VoD can be bundled together like an electronic program guide (EPG) to relieve the burden of users connecting to a specific content service to view or download the content. give. Similar to the EPG service, this service does not inform the real-time broadcast channel information but is already stored in the server so that it can be watched at any time and downloaded and stored. To connect to the server with each content, the user will have to get a very difficult address or PF servers. This is a very complicated process and time consuming. Companies that provide ECG allow ECG programs to be automatically installed on users, and collect information about all content and provide data. To access the ECG service, the user can also click the Enter key button on the remote control.

The portal server is a web service provided by each broadcasting station and is connected to a web server of a company serving a broadcasting station or content. The role of the portal server may search for or view a list of programs provided by each broadcasting station or a content provider providing a content service. It can be thought of as a function like ECG or EPG. However, the portal service also has functions such as user authentication and license agreement, so I need to connect to watch the program I want. In addition, the ECG or EPG provides an integrated broadcast or content list, but the portal service may provide detailed search by providing broadcast or content list information for a corresponding program provider. To access the portal service, the user simply clicks the portal input button on the remote control.

In this way, the content provider side should include a function for providing such services, and in order for these functions to operate normally, the server 130 of each service provider may provide an IP network to transmit a corresponding program or broadcast information in real time. You must be connected to. In addition, each broadcasting station or service provider must be connected to the service provider's network and transmitted without delay and error. Therefore, real time protocol (RTP), real time streaming protocol (RTSP), resource reservation protocol (RSVP), and MPLS (multi) System should be equipped to transmit multimedia data using internet real-time protocol such as protocol label switching. For example, if you're trying to deliver multimedia in real time in a TV studio that's currently delivering news, you'll need to transcode the MPEG-2 and AC-3 audio specifications to match the format of your IPTV. . When passing through a server that does this, the system passes the IP provider-provided IP network with RTP / UDP (user datagram protocol) protocols containing time information to enable captioning or lipsync. Configure

The service provider provides network stability and bandwidth to transmit multimedia data and broadcast data transmitted from the content provider. Service providers can also provide IPTV services over existing cable networks, in which case the equipment of the delivery network needs to be changed. In other words, network devices capable of real-time data transmission must be configured, and users must configure the network in consideration of bandwidth. These devices need to reduce bandwidth by processing large amounts of multimedia data using multicast service, which is the basic network service of IPTV. If the bandwidth is not secured, the service provider may retranscode multimedia broadcast data from the optical fiber network configuration or the content provider and transform it into MPEG-4 or MPEG-7 in an effort to secure the bandwidth. . Service providers need to provide several services for this purpose. They are designed to provide size Network Management System (NMS), Dynamic Host Control Protocol (DHCP), and content delievery network (CDN) services.

The NMS service manages the transport network that service providers can send to each user and performs the Remote Configuration and Management Server (RCMS) function. That is, when a problem occurs in the transmission network and the user cannot receive the broadcast, there must be a means for emergency processing. NMS is widely used as a standardized means to smoothly control and manage machines in remote transport layers. Using this service, you can see how much traffic is being generated for which broadcasts, and in which areas there is not enough bandwidth. In addition, the content provider must be provided to the content provider so that the group can be created and managed during multicast. Sometimes it is necessary to create more multicast groups.

The DHCP service allows you to automatically assign an IP address to your IPTV receiver and use it to tell the address of the CDN server. DHCP services are also a good way to assign IP to PCs in the general network. The IPTV receiver should be sent an address that allows access to the licensed IPTV receiver so that the user can register during the initial connection. In general, IPv4 will be provided by IPTV receivers, but IPv6 is also available. Thus, IPTV receivers that provide IPv4 do not mean they cannot be used.

The CDN service is data provided by the service provider. When the IPTV receiver is powered on for the first time, the CDN service receives the CDN information from the service provider while receiving the IP by the DHCP service. This information contains the registration or authentication of the user of the IPTV provider and the aforementioned PF information. By receiving the CDN information from the service provider by the IPTV receiver, it may be possible to receive an IP broadcast signal.

The user may have various types of IPTV receivers. If you have a regular TV, you can rent an IPTV set-top box (STB) to enjoy IPTV at a low price, and service providers can also apply for an IP phone at an affordable price. The IPTV receiver basically has a network interface to connect to the network, and has an Internet protocol to receive and process data packets coming from the network, and play them back on the screen in the case of multimedia data. The packet must be sent quickly over the network to get the information from the server and respond. That is, the IPTV receiver may operate to transmit the user's requirements in both directions while processing the multimedia data. In addition, the remote control can provide buttons for IPTV to use the service well. In the provided IPTV receiver, the user can store and view the wonderful scene in the drama and enjoy the additional service such as location information or hotel reservation.

On the other hand, the NMS mentioned above performs the RCMS function as well as the function that the service provider manages the network. RCMS helps users to control and manage their own IPTV receivers. As the number of IPTV receivers increases and additional services increase, the role of RCMS becomes more important. For this reason, the Simple Network Management Protocol (SNMP) protocol is mandatory for IPTV broadcast receivers. This is intended to allow service providers to manage and control IPTV broadcast receivers. IPTV broadcast receivers can then learn in detail the statistics of the protocol they are currently communicating with, information about the processor they are using, and what TV manufacturer they are using.

In order to receive the IPTV service in the customer area, the ITF 120 may transmit a server address resolution request to the DNS server 110. DNS server 110 then transmits the server address to ITF 120. The ITF 120 can then connect to the server 130 with the received server address and receive the IPTV service. Here, the ITF 120 may be connected to the server 130 in at least one of a multicast scheme and a unicast scheme.

2 is a diagram schematically illustrating a multicast scheme.

Referring to FIG. 2, the multicast method is a method of transmitting data to a plurality of recipients of a specific group. For example, a service provider can send data to multiple pre-registered ITFs at once. The Internet Group Management Protocol (IGMP) protocol may be used for the multicast registration.

3 is a diagram schematically illustrating a unicast scheme.

Referring to FIG. 3, the unicast method is a method of transmitting data 1: 1 between one sender and one receiver. For example, in the unicast scheme, when an ITF requests a service from a service provider, the service provider transmits the service to the ITF according to the request.

4 is a flowchart illustrating a preferred embodiment of the method for searching for an IPTV service according to the present invention.

Referring to FIG. 4, in order to receive an IPTV service, the ITF performs a service provider discovery to find a list of addresses of a service discovery server. Here, the service provider discovery refers to a process in which the ITF finds information about the IPTV service provider and information for accessing the service provider through a security managed network. ITF can find the address list of the SD server in the following way.

Address list search method of SD server

1. Preset or manual setting: Follow the preset address in ITF or set the user manually

2. DHCP-based Service Provider Discovery (SP Discovery): Get the address list of SD server using DHCP option.

3. DNS SRV-based service provider discovery: Get the SD server speed list by using DNS SRV mechanism

The ITF 420 may find a specific SD server through the SD server address list obtained by the above methods 1 to 3 and may receive a service provider discovery record from the specific SD server.

The service provider 410 transmits a service provider discovery record to the ITF 420 (S400). Here, the service provider discovery record includes information about the useful IPTV service provider and information for accessing the service provider through the security managed network. The service provider discovery record may be transmitted in a push mode or a pull mode. When transmitted in the pull mode, the service provider 410 transmits the service provider discovery record when the ITF 420 has a request for the transmission of the service provider discovery record. However, when transmitted in push mode, the service provider 410 transmits the service provider discovery record regardless of the request for the ITF 420 to transmit the service provider discovery record.

The ITF 420 accesses a registration server designated by address information of a registration server included in the service provider discovery record and performs an ITF registration procedure (S405). In this case, the information delivered from the ITF 420 to the service provider 410 may be delivered in the form of an ITFRegistrationInputType record and may include subscriber identifier information and subscriber location information. And here, the ITF registration may be referred to as a SP (Service Provider Attachment), which may vary according to the intention or custom of a person skilled in the art or the appearance of a new technology.

After successful authentication, the service provider 410 transmits a provision information record to the ITF 420 (S410). Here, the provisioning information record is a record providing provisioning information and authentication information obtained by the ITF during the SP connection procedure. The provision information record has a form of an ITFRegistrationOutputType record, and may be data customized to a subscribed service based on information included in the ITFRegistrationInputType record. Here, the ITFRegistrationInputType record may include at least one of subscriber identifier information and subscriber location information. Here, the subscriber location information may be an address where the subscriber's ITF is located. In addition, when the ITFRegistrationInputType record includes only subscriber identifier information, the registration server may obtain previously stored subscriber location information and subscription status information based on the subscriber identifier information.

In one example, the provisioning information record may be customized to the subscriber's subscription status and ITF location. The ITF 420 provides its ID and location information through the ITFRegistrationInputType record, and the registration server can specify the service to which the ITF subscribes based on this. The registration server provides an address, in the form of an ITFRegistrationOutputType record, from which the ITF 420 may obtain service information based on the specified service.

Service Information provides a Master Service Information (SI) Table Record that manages the version of Channel Map and Channel Details and a list of channels in package form. It is divided into Channel Map Record and Channel Details Record which contains detailed information of each channel. In this case, the service information may be transmitted in a push mode or a pull mode.

The service provider 410 transmits a master SI table record to the ITF 420 (S415). Here, the ITF 420 may receive the master SI table record or request the service provider 410 based on the location information of the master SI table included in the provision information record.

In addition, the service provider 410 transmits a channel map record to the ITF 420 (S420). Here, the ITF 420 may receive the corresponding channel map record or request the service provider 410 based on the channel information included in the master SI table record.

The service provider 410 transmits a channel details record to the ITF 420 (S425). Here, the ITF 420 may receive the channel detail record or request the service provider 410 based on the virtual channel information included in the master SI table record or the channel detail location information included in the channel map record.

5 is a diagram illustrating a schema of a preferred embodiment of a service provider discovery type according to the present invention.

Referring to FIG. 5, the service provider discovery record includes a ServiceProviderID attribute, a Version attribute, a LogoURI attribute, a Name element, a Description element, and an SProviderRegistrationServer element.

The ServiceProviderID property includes unique identifier information for identifying a service provider, and can guarantee uniqueness of an identifier by using a domain name registered as an identifier.

The Version attribute contains the version information for this record.

The LogoURI attribute includes logo image information that specifies a uniform resource identifier (URI) of the logo image of the service provider, and may be optionally used.

The Name element contains information about the name of the service provider. The service provider may have one name for each language. To this end, the Name element includes a Language attribute, and the Language attribute includes information about a name defined for each language. Here, the Name element should include at least one Language attribute.

The Description element includes detailed text description information about the service provider, and the text description information may be one for each language similarly to the information about the name of the service provider. To this end, the Description element includes a Language attribute and may include a plurality of Language attributes. The Language property contains textual description information. Here, the text description information may be optionally provided and may not be provided.

The SProviderRegistrationServer element contains address information of the registration server of the service provider. To this end, the SProviderRegistrationServer element may include a Location URL attribute, and the Location URL attribute includes address information of the registration server. Here, the address information of the registration server may be in the form of a URL, for example.

Figure 6 illustrates a schema of one preferred embodiment for an ITF Registration Input Type according to the present invention.

Referring to FIG. 6, the ITF registration input record includes a ConsumerID attribute and a ConsumerLocation attribute, and information transmitted from the ITF to the registration server for registration may be transmitted in the structure of the ITF registration input type.

The ConsumerID attribute includes subscriber identifier information for uniquely identifying a subscriber, and a media access control address (MAC) of the ITF may be used as the subscriber identifier.

The ConsumerLocation attribute contains subscriber location information indicating the location of the subscriber. Through the information included in the ConsumerLocation, the registration server may recognize the location of the subscriber by determining the location of the subscriber, and may select and send flows suitable for the ITF according to the determined area. In this case, the subscriber location information may be obtained through a DHCP option in a network attachment step.

FIG. 7 illustrates a schema of a preferred embodiment of an ITF Registration Output Type according to the present invention.

Referring to FIG. 7, the ITF registration output record includes a MasterSITableLocation element, a SubscribedChannelMap element, an UnsubscribedChannelMap element, an EPGDiscoveryLocation element, and a SPRemoteConfigurationServerLocation element. When the registration is successful, the information transmitted from the registration server to the ITF is an ITF registration output type (ITF). Regitstration Output Type) structure.

The MasterSITableLocation element contains location information of the master SI table.

The SubscribedChannelMap element contains information about the channel map to which the user subscribed. Service providers can provide their channels in the form of multiple channel maps so that users can select and subscribe to one or more of them. In addition, the channel map may not be directly visible to the user, but may be internally configured in the form of a channel map to provide a list of channels subscribed to by the user in combination of the channel map.

The UnsubscribedChannelMap element contains information about channel maps to which the user has not subscribed. The service provider may need to provide such a list of channels for promotion, although the user is not currently subscribed and can not watch. The service provider may optionally provide such channel maps.

The EPGDiscoveryLocation element contains EPG data provider information for discovering EPG data. The EPG data provider information includes address information for receiving EPG data. EPGs may optionally be provided and one or more EPGs may be provided. Here, the EPGDiscoveryLocation element may be defined as an EPG Discovery Record Type as an example.

The SPRemoteConfigurationServerLocation element contains address information of the remote configuration server provided by the service provider. If the address information of the remote configuration server exists, the ITF must connect to the remote configuration server and perform the remote configuration procedure. Here, the remote configuration server performs the above-described RCMS function.

8 is a diagram illustrating a relationship between tables constituting a service information.

Referring to FIG. 8, a Master SI Table Record provides pointers to Virtual Channel Maps. Here, the pointers are information necessary to start the virtual channel discovery process. In addition, master SI table records allow ITF to detect changes in some versions of SI. The master SI table record includes a channel map master containing version information of each channel map and a virtual channel master containing version information about channel detail including channel details. Master). Here, the master SI table record may optionally include a virtual channel master.

Each channel map is uniquely identified by VCListID and has two version information of VCListVerion and ChannelDetailsVersion. VCListVersion is a version of the channel list of the channel map. The version is changed only when a channel is added or deleted. ChannelDetailsVersion is version information for managing whether the detailed information of a channel included in the channel map is changed. The version is changed only when the detailed information of the channel is changed.

There can be only one master SI table record in the service provider. However, if the service configuration differs by region, it would be more efficient to configure one master SI table record for each region. In this case, the registration step makes it possible to provide a master SI table record for the region in which the ITF belongs.

In FIG. 8, two channel maps are illustrated in the master SI table record, which can be uniquely identified by the VCListID. Each channel map may have one or more channels and does not include detailed information of the channels on the channel map, but rather specifies where to obtain this information. That is, the channel details location plays a role in designating the location of the channel details.

The channel details record contains channel details and can be found by channel details location on the channel map. In addition to this method, the channel detail location delivery method may have various methods as follows.

Channel Details Location Delivery

1. How to provide a single multicast stream globally

A single global multicast stream that sprinkles channel detail records for all channels provided by a service provider. In this case, as described above, the global multicast stream can be provided in the ITFRegistrationOutputType without providing the address of the detailed information for each channel on the channel map.

2. How to provide one multicast stream per region

In the first method, channel detail information is provided in one stream globally. In this case, channel detail information may be provided through a separate multicast stream for each region. In this case, the registration process allows the region to belong to the ITF. Therefore, the ITFRegistrationOutputType can be used to address the region's only multicast stream.

3. How to specify Default Channel details location in the channel map

If some or all of the details of a channel in a channel map can be obtained from the same address, it is sufficient to specify it once in the channel map rather than for each channel detail location. In this case, if there is a channel to obtain detailed information from another address, the address specified in the channel map may be overridden by additionally or additionally designating the channel detail location.

4. A method of designating the location of detailed information for each channel through the channel detail location as shown in FIG.

This is a method of specifying detailed information of channels belonging to each channel map for each channel detail location. For example, for a channel having a ServiceID of "WNBC.COM/ch9" and "WNBC.COM/ch11", respectively, if "WNBC.COM/ch9", the LocationURL of the channel detail location of the channel is "ipm." For channels with "WNBC.COM/ch11", the LocationURL of the channel details location for the channel's details is set to "ipm: //sd.verizon.com". Specify each one.

In order to find the details of each channel in the transmitted channel details records, the ServiceID of the channel details record location can serve as a unique identifier that distinguishes the details of each channel, and the ServiceID of the channel details record location This allows you to find the channel detail record for that channel.

If the channel detail record is received in a multicast manner, the channel detail record corresponding to the ServiceID may be found while joining the corresponding stream to continue receiving the record.

If a channel detail record is received in a unicast manner, only the desired channel detail record can be received by passing the ServiceID as a parameter to the server to transmit only the desired channel detail record.

The master SI table record, the channel map record, and the channel detail record are logically conveyed through three separate flows, and may be delivered in any of push mode and pull mode.

Passing Master SI Table Records ITF can manage updates of channel maps and channel details. The ITF monitors the master SI table to determine whether the channel map and channel details have changed, and if the version has changed, recognizes that the channel map and channel details have been updated and then updates the channel map and channel details. Can be.

Here, the update of the channel details can be confirmed in two ways. The first can be checked through the Channel Details Version of the Channel Map Master in the Master SI Table Record. If the channel detail version of the channel map master has changed, it can be recognized that the channel details have been updated. The second can be seen through the channel detail version of the channel map record. That is, the presence of an update can be checked by finding a channel map record indicated by the channel map master and determining whether the channel detail version of the corresponding channel map record has changed. In the second method, the master SI table record does not need to include a virtual channel master and the channel map master does not need to include a channel detail version.

FIG. 9 illustrates a schema of a preferred embodiment of a Master SI Table Record Type. FIG.

Referring to FIG. 9, the master SI table record includes channel map management information. To this end, the master SI table record may include a ServiceProviderID attribute, a Version attribute, a ChannelMapMaster element, and a VirtualChannelMaster element. Here, the VirtualChannelMaster element may optionally be included.

The ServiceProviderID property may include service provider identifier information for uniquely identifying a service provider, and may use a domain name registered as a service provider identifier.

The Version attribute contains version information of the master SI table record. Version information included in the Version property can determine whether to update the master SI table record.

The ChannelMapMaster element contains information for receiving a channel map. In other words, the ChannelMapMaster element includes a pointer to a channel map instance. In addition, the master SI table record may include one or more pointers for respectively indicating one or more channel map records. A channel map record may be received based on the information included in the ChannelMapMaster element, and it may be determined whether the channel map is updated. To this end, the ChannelMapMaster element may include a VCListID attribute, a VCListVersion attribute, and a ChannelDetailsVersion attribute. The VCListID attribute contains identifier information that uniquely identifies the channel map instance. The VCListVersion attribute includes version information that determines whether or not the channel lists constituting the channel map are changed. Here, the version information included in the VCListVersion attribute is changed when the channel is added or deleted. The ChannelDetailsVersion attribute includes version information indicating whether detailed information of channels constituting the channel map has changed. Here, the version information included in the ChannelDetailsVersion property is changed when the detailed information of the channel is changed.

The VirtualChannelMaster element includes a ServiceID attribute and a VCVersion attribute. The ServiceID attribute contains identifier information for uniquely identifying a service. You can find the channel detail record you want based on the information contained in the ServiceID attribute. The VCVersion attribute contains version information of channel details.

FIG. 10 illustrates a schema of a preferred embodiment of a channel map type.

Referring to FIG. 10, a channel map is a structure that contains channel map information and does not include detailed information of a channel, and serves as a package of channels. Here, the channel map of FIG. 10 illustrates a method of separately specifying an address for each channel detail, which is the fourth method of the channel detail delivery method described above with reference to FIG. 8. Here, the channel map information may be, for example, a channel map instance.

Channel map records contain channel map instances. To this end, the channel map record includes a ServiceProviderID attribute, a VCListID attribute, a VCListVersion attribute, a ChannelDetailsVersion attribute, and a ChannelDetailsLocation element.

The ServiceProviderID property may include service provider identifier information for uniquely identifying a service provider, and may use a domain name registered as a service provider identifier.

The VCListID includes identifier information that uniquely identifies the channel map.

The VCListVersion attribute includes version information indicating whether the channel lists constituting the channel map have changed. Here, the version information included in the VCListVersion attribute is changed when the channel is added or deleted.

The ChannelDetailsVersion attribute includes version information indicating whether the detailed information of a channel constituting the channel map is changed. Here, the version information included in the ChannelDetailsVersion property is changed when the detailed information of the channel is changed.

The ChannelDetailsLocation element includes location information of detailed information of each channel. For this purpose, the ChannelDetailsLocation element includes a ServiceID attribute, a LocationURL attribute, and a VCVersion attribute. The ServiceID attribute contains identifier information for uniquely identifying a service. You can find the channel detail record you want based on the information contained in the ServiceID attribute. The LocationURL attribute contains address information from which you can get detailed information about this service. The VCVersion attribute contains version information of channel details.

FIG. 11 illustrates a schema of another preferred embodiment of a channel map type. FIG.

Referring to FIG. 11, the channel map is a structure containing channel map information, and serves as a package in the form of a bundle of channels, and does not include the detailed information of the channel, and instead, the channel map information includes information about a debate position of the detailed information of the channel. It includes. Here, the channel map of FIG. 11 illustrates a method for designating default channel details location in a channel map, which is the third method of the channel details delivery method described above with reference to FIG. 8. The channel map information may be, for example, a channel map instance.

Channel map records contain channel map instances. To this end, the channel map record includes a ServiceProviderID attribute, a VCListID attribute, a VCListVersion attribute, a ChannelDetailsVersion attribute, a ChannelDetailsDefaultLocation element, and a ChannelDetailsLocation element.

The ServiceProviderID property may include service provider identifier information for uniquely identifying a service provider, and may use a domain name registered as a service provider identifier.

The VCListID includes identifier information that uniquely identifies the channel map.

The VCListVersion attribute includes version information indicating whether the channel lists constituting the channel map have changed. Here, the version information included in the VCListVersion attribute is changed when the channel is added or deleted.

The ChannelDetailsVersion attribute includes version information indicating whether the detailed information of a channel constituting the channel map is changed. Here, the version information included in the ChannelDetailsVersion attribute is changed when the channel details change.

The ChannelDetailsDefaultLocation element contains the default location information of the detailed information of the channel belonging to the channel map. To do this, the ChannelDetailsDefaultLocation element contains a LocationURL attribute. The LocationURL attribute contains the default location information. Here, the default location information is an address capable of receiving all or part of detailed information of a channel belonging to one channel map. If there is a channel for which detailed information is to be obtained from another address, the location information of the detailed information of the corresponding channel may be overridden in the ChannelDetailsLocation element.

The ChannelDetailsLocation element includes location information of detailed information of each channel. That is, when there is detailed information of a channel that cannot be obtained from the default location information included in the ChannelDetailsDefaultLocation element, the ChannelDetailsLocation element includes the location information of the detailed information of the channel. For this purpose, the ChannelDetailsLocation element includes a ServiceID attribute, a LocationURL attribute, and a VCVersion attribute. The ServiceID attribute contains identifier information for uniquely identifying a service. The desired Channel Details Record can be found based on the information included in the ServiceID property. The LocationURL attribute contains address information from which you can get detailed information about this service. The VCVersion attribute includes version information of channel details.

12A and 12B illustrate a schema of one preferred embodiment for Channel Details Type.

12A and 12B, a channel detail record includes detailed information of a channel included in a channel map. The channel detail record for this includes the ServiceProviderID attribute and the VirtualChannelDetails element.

The ServiceProviderID property contains service provider identifier information that can uniquely identify the service provider.

The VirtualChannelDetails element contains detailed information of each channel. To this end, the VirtualChannelDetails element includes a ChannelType attribute, a ServiceID attribute, a VCVersion attribute, a ShortChannelName element, a ChannelNumber element, and a ChannelSource element. Here, the ChannelSource element may be optionally included. If the VirtualChannelDetails element does not include the ChannelSource element, the ChannelSource element may be independently transmitted as a separate ChannelSource record, and the VirtualChannelDetails element may include location information and identification information capable of receiving the ChannelSource record.

The ChannelType attribute includes service type information indicating a service type of a channel, and the service type information indicates whether the corresponding channel is a video channel, an audio channel, or a data broadcasting channel.

The ServiceID attribute contains identifier information for uniquely identifying a service. You can find the channel detail record you want based on the information contained in the ServiceID attribute.

The VCVersion attribute contains version information of channel details.

The ShortChannelName element contains the name of the channel as a short text value of 7 characters or less. For example, it could be a value like "WABC".

The ChannelNumber element contains the channel number. In the present invention, both the one part channel number and the two part channel number can be supported, and the corresponding channel number can be any one of the one part channel number and the two part channel number. To this end, the ChannelNumber element may include a MajorChannelNumber element including physical channel information and a MinorChannelNumber including logical channel information.

The ChannelSource element contains information specifying the actual source of the channel. To this end, the ChannelSource element includes a VirtualChannelLocation element, a ChannelSourcePurpose element, a VideoAttribute element, an AudioAttributes element, and an ECMLocation element.

The VirtualChannelLocation element contains the IP address and transport protocol information that can receive the source of the channel. For this purpose, the VirtualChannelLocation element includes a ProgramNumber attribute and an IPLocation element. By selectively supporting the ProgramNumber attribute, it guarantees scalability to multi program transport stream (MPTS) and provides an opportunity to check whether the received stream is a desired stream even in the case of a single program transport stream (SPTS). The IPLocation element contains a Location URL attribute that contains URL information that can receive the source of the channel.

The ChannelSourcePurpose element may include source type information, which is a value indicating the characteristics of a channel, and may include a plurality of source type information. Here, the source type information may be one of a high definition (HD), a standard definition (SD), a picture in picture (PIP), and a barker. Barker channel is a channel for advertising or promotion. When the channel is not available due to the authority of the channel, it is automatically selected and serves as a guide for promoting and subscribing to the channel, and Barker is at least one of HD Barker, SD Barker, and PIP Barker. Contains a single value.

One channel can have one source for each value specified by ChannelSourcePurpose. That is, when the ChannelSourcePurpose element includes one HD and one SD at the same time, one channel may have one HD source and one SD source. However, one channel does not need to have two HD sources simultaneously, so the ChannelSourcePurpose element does not contain two HDs at the same time.

The VideoAttributes element contains video attribute information of the source. To this end, the VideoAttributes element includes a Codec attribute including video codec information, a Profile attribute including video profile information, and a Level attribute including video level information.

The AudioAttributes element contains audio attribute information of the source. To this end, the AudioAttributes element includes a codec including audio codec information, a profile attribute including video profile information, a level attribute including audio level information, a bitrate attribute including audio bitrate information, and an audio sampling frequency. Contains SamplingFrequency information, including information.

The video attribute information included in the VideoAttribute element and the audio attribute information included in the AudioAttributes element allow the user to select and watch the optimal source according to the function of the ITF.

The ECMLocation element contains ECMLocation address information that can receive ECM information.

FIG. 13 is a flowchart illustrating an exemplary embodiment of a service provider discovery according to the present invention. Referring to FIG.

Referring to FIG. 13, the ITF searches for an SD server (S1300). Here, the ITF may find the SD server according to the address list search method of the SD server described above with reference to FIG. 4.

The ITF accesses the SD server based on the main list of the SD servers, and obtains a service provider discovery record from the SD server (S1310). Here, the service provider discovery record may be the service provider discovery record described above with reference to FIG. 5. The ITF can also receive service provider discovery records in push mode or pull mode from the SD server.

The ITF parses the ServiceProviderID attribute of the received Service Provider Discovery Record to calculate service provider identifier information included in the ServiceProviderID attribute (S1320).

The ITF checks whether the calculated service provider identifier information is a service provider who wants to receive a service (S1330). If the service provider does not want to be provided with the service, the ITF performs step S1300 to find another SD server in the main list of SD servers.

If the service provider wants to receive the service, the ITF parses the Name and Description attributes of the provider discovery record, and the service provider is included in the Information and Description attributes of the service provider's name contained in the Name attribute. Detailed text description information about the provider is calculated (S1340).

The ITF parses the SProviderRegistrationServer element of the provider discovery record and calculates address information of the registration server of the service provider included in the SProviderRegistrationServer element (S1350). The ITF may access the registration server based on the calculated address information of the registration server and perform the ITF registration procedure.

FIG. 14 is a flowchart illustrating a preferred embodiment of a service provider registration and service discovery according to the present invention.

Referring to FIG. 14, the ITF transmits a registration request to a registration server designated by address information of a registration server included in a service provider discovery record (S1400). Here, the ITF may transmit the ITFRegistrationInputType record described above with reference to FIG. 6 as a registration request.

The registration server receives the registration request and determines whether to register the ITF (S1410). Here, the registration server may receive an ITFRegistrationInputType record as a registration request, and may determine whether to register based on subscriber identifier information and subscriber location information included in the ITFRegistrationInputType record.

If the registration is approved, the ITF receives the ITFRegistrationOutputType record (S1420). Here, the ITFRegistrationOutputType record may be the ITFRegistrationOutputType record described above with reference to FIG. 7, and the information included in the ITFRegistrationOutputType record may be information customized by the information included in the ITFRegistrationInputType record.

The ITF parses the MasterSITableLocation element of the received ITFRegistrationOutputType record and calculates position information of the master SI table included in the MasterSITableLocation element (S1430).

The ITF receives a Master SI Table Record based on the calculated position information of the Master SI Table (S1440). Here, the received master SI table record may be the master SI table record described above with reference to FIG. 9.

The ITF parses the SubscribedChannelMap element of the received ITFRegistrationOutputType record, and calculates information about the channel map subscribed to by the user included in the SubscribedChannelMap element (S1450). Here, the ITF may calculate channel map position information for receiving the channel map subscribed to by the user from ChannelMapMaster of the master SI table record.

The ITF receives a channel map record based on the calculated channel map position information in operation S1460. Here, the received channel map record may be at least one of the channel map record described above with reference to FIG. 10 and the channel map record described above with reference to FIG. 11.

The ITF parses the ChannelDetailsLocation element of the received channel map record, and calculates location information of the detailed information of the channel included in the ChannelDetailsLocation element (S1470).

The ITF receives a Channel Details Record based on the calculated position information of the detailed information of the channel (S1480). Here, the received channel detail record may be the channel detail record shown in FIGS. 12A and 12B.

The ITF starts the received service service (S1490).

15 is a flowchart illustrating an exemplary embodiment of a method of processing an update of a master SI table.

Referring to FIG. 15, the ITF updates the master SI table (S1500). ITF monitors the master SI table in real time and can check whether the received version of the master SI table record has changed. If the version of the received master SI table record is changed, the ITF updates the master SI table with information included in the received master SI table record.

The ITF selects a ChannelMapMaster element for updating among ChannelMapMaster elements included in the master SI table (S1510).

The ITF checks whether the selected ChannelMapMaster element includes information for receiving a channel map subscribed to by the user (S1520). To do this, the ITF can use information about the channel maps subscribed to by the user included in the SubscribedChannelMap in the ITFRegistrationOutputType record.

If the user includes information for receiving the subscribed channel map, the ITF checks whether the version information included in the VCListVersion attribute of the selected ChannelMapMaster element has been changed (S1530). If the version information included in the VCListVersion attribute is changed, the ITF receives the updated channel map record, and updates the channel map with the information included in the received channel map record (S1540).

Check whether there is a ChannelMapMaster element that is not selected in the master SI table (S1550). If there is a ChannelMapMaster element that is not selected, the ITF performs step S1510.

FIG. 16 is a flowchart illustrating a process of another preferred embodiment of the method for processing an update of a master SI table.

Referring to FIG. 16, the ITF updates the master SI table (S1600). ITF monitors the master SI table in real time and can check whether the received version of the master SI table record has changed. If the version of the received master SI table record is changed, the ITF updates the master SI table with information included in the received master SI table record.

The ITF selects a ChannelMapMaster element for updating among ChannelMapMaster elements included in the master SI table (S1610).

The ITF checks whether the selected ChannelMapMaster element includes information for receiving a channel map subscribed to by the user (S1620). To do this, the ITF can use information about the channel maps subscribed to by the user included in the SubscribedChannelMap in the ITFRegistrationOutputType record.

If the user includes information for receiving the subscribed channel map, the ITF checks whether the version information included in the VCListVersion attribute of the selected ChannelMapMaster element is changed (S1630). If the version information included in the VCListVersion attribute is changed, the ITF receives the updated channel map record and updates the channel map with the information included in the received channel map record (S1640).

The ITF checks whether the version information included in the ChannelDetailsVersion attribute of the selected ChannelMapMaster element has changed (S1650). If the version information included in the ChannelDetailsVersion attribute is changed, the channel detail information is updated (S1650).

Check whether there is a ChannelMapMaster element that is not selected in the master SI table (S1670). If there is no ChannelMapMaster element selected, the ITF performs step S1610.

FIG. 17 is a flow diagram illustrating the implementation of one preferred embodiment of a method for processing an update of a channel details version.

Referring to FIG. 17, the ITF updates the channel map (S1700).

The ITF selects a channel from the channel map (S1710). Here, the ITF may also select a ChannelDetailsLocation element including location information of detailed information of the channel selected in the channel map.

The ITF checks whether the version information included in the VCVersion attribute of the selected ChannelDetailsLocation element has changed (S1720). If the version information is changed, the ITF receives the updated channel detail record and updates the channel detail of the selected channel based on the information included in the received channel detail record (S1730).

The ITF checks whether there is a channel that is not selected in the channel map (S1740). If there is a channel that is not selected, the ITF performs step S1710.

FIG. 18 is a flowchart illustrating another exemplary embodiment of a method of processing an update of a channel details version.

Referring to FIG. 18, the ITF selects a channel in the channel map (S1800). Here, the ITF may also select a ChannelDetailsLocation element including location information of detailed information of the channel selected in the channel map.

The ITF searches for a Virtual Channel Master element including a ServiceID attribute including identifier information such as identifier information included in the ServiceID attribute of the ChannelDetailsLocation element selected in the master SI table (S1810).

The ITF determines whether the version information included in the VCVersion attribute of the found Virtual Channel Master element is the same as the version information included in the VCVersion attribute of the selected ChannelDetailsLocation element (S1820). If it is different from the version information, the ITF receives the updated channel details record and updates the channel details of the selected channel based on the information included in the received channel details record (S1830).

The ITF checks whether there is a channel that is not selected in the channel map (S1840). If there is a channel that is not selected, the ITF performs step S1800.

19 is a diagram illustrating a schema of a preferred embodiment of an EPG Discovery Record Type according to the present invention.

Referring to FIG. 19, an EPG discovery record includes EPG discovery information for discovering EPG data. For this purpose, the EPG discovery record includes an EPGProviderID attribute, a Version attribute, a Name element, a Description element, an EPG ServerLocation element, a TargetServiceProviderID element, and a Logo element.

EPGProviderID includes identifier information that can uniquely identify a provider that provides EPG data. Here, a domain name registered as identifier information may be used.

The Version attribute includes version information of the EPG Discovery Record.

The Name element includes information about the text name of the EPG data provider, and the EPG data provider may have one name for each language. For this purpose, the Name element contains a Language attribute. In addition, the Name element may include a plurality of Language attributes, and each of the plurality of Language attributes includes information about a text name of an EPG data provider defined for each language.

The Description element includes detailed text description information about the EPG data provider, and the text description information may be one for each language similarly to the information against the name of the EPG data provider. For this purpose, the Description element includes a Language attribute. In addition, the Description element may include a plurality of Language attributes, and each of the plurality of Language attributes includes text description information defined for each language.

The EPG ServerLocation element includes IP address information capable of receiving EPG data and protocol information used for receiving EPG data.

The TargetServiceProviderID element contains ID information of service providers supported by the EPG data provider.

Logo contains location information of the logo of this EPG data provider. Here, the location information of the logo may be in the form of a URI.

20 is a block diagram showing the configuration of a preferred embodiment of the ITF (IPTV Terminal Function) according to the present invention.

Referring to FIG. 20, the ITF includes a network interface unit, an IP network stack 2015, a file handler 2020, an SI handler 2025, and an EPG handler. 2030, Storage 2035, SI Decoder 2040, EPG Decoder 2045, ITF Operation Controller 2050, Channel Service Manager Service Manager 2055, Application Manager 2060, Demultiplexer 2065, PSI / PSIP Parser 2070, A / V Decoder 2075 and And a display module 2080. The network interface unit may include a modem 2005 and an Ethernet NIC 2010.

The modem 2005 serves as an interface through which the ITF is connected to the IP network at the physical level. The modem 2005 demodulates a signal transmitted through a physical medium, restores it to a digital signal, and modulates a digital signal transmitted by the ITF to a service provider. Output to the network. The modem 2005 may be implemented as a cable modem, a DSL modem, or the like.

The Ethernet network interface 2010 restores the IP packet and outputs the digital signal received through the modem 2005 to the IP network stack 2015. In addition, the Ethernet network interface 2010 encapsulates an IP packet output from the IP network stack 2015 into an Ethernet datagram and outputs it to the modem 2005.

The IP network stack 2015 processes the processing module of each layer according to the IP protocol stack. The IP network stack 2015 is involved in packet forwarding from source to destination for packets received at the ITF and packets transmitted by the ITF. The IP network stack 2015 classifies the received packet to correspond to an appropriate protocol, and outputs the classified packet to the file handler 2020 and the demultiplexer 2065. For example, the network stack 2015 may include a Service Provider Discovery Record, an ITF Registration Output Record, a Master SI Table Record, and a Channel Map Record. ), When a packet including any one of a channel details record and an EPG discovery record is received, data included in the packet is output to the file handler 2020. In addition, the network stack 2015 IP packetizes the ITF Registration Input Record and outputs the IPF Registration Input Record to the Ethernet network interface 2010 to be delivered to the service provider.

The file handler 2020 collects the data output from the IP network stack 2015 and restores the data in the form of a file. Here, the file handler 2020 may restore data output from the IP network stack 2015 to a file form using FLUTE. That is, the service provider may transmit a file using FLUTE, and the file handler 2020 may receive a file transmitted by the service provider using FLUTE. The file handler 2020 classifies the converted file and outputs the converted file to either the SI handler 2025 or the EPG handler 2030.

The SI handler 2025 processes a portion corresponding to the IPTV SI data among the data in the file form received from the file handler 2020 and stores the portion corresponding to the IPTV SI data in the storage 2035. Here, the IPTV SI data includes a Service Provider Discovery Record, an ITF Regitstration Output Record, a Master SI Table Record, a Channel Map Record, a Channel. It may be at least one of a Channel Details Record and an EPG Discovery Record.

The EPG handler 2030 may process a portion corresponding to the IPTV EPG data among the file type data received from the file handler 2020 and store it in the storage 2035. Here, the IPTV EPG data may be received from the service provider using the information included in the EPG discovery record.

The storage unit 2035 stores the SI provided by the SI handler 2025, the EPG provided by the EPG handler 2030, and data provided by the ITF operation controller 2050.

The SI decoder 2040 decodes SI data stored in the storage 2035 to restore necessary information, and provides the information to the ITF operation controller 2050. The SI decoder 2040 calculates information about a useful IPTV service provider from a service provider discovery record and information for accessing the service provider through a security managed network. For example, the SI decoder 2040 may parse a service provider discovery record to calculate registration server address information included in the service provider discovery record.

In addition, the SI decoder 2040 may parse an ITF registration output record to calculate information included in the ITF registration output record. For example, the SI decoder 2040 may calculate EPG discovery information for discovering EPG data included in an ITF registration output record and address information for receiving a master SI table record.

In addition, the SI decoder 2040 parses the master SI table record to receive the channel map record and the channel detail record included in the master SI table record, the version information of the channel map record, and the version of the channel detail record. Information can be calculated.

The SI decoder 2040 may calculate channel map information from a channel map record, and calculate channel detail information of a corresponding channel from a channel details record.

When EPG information is needed, the EPG decoder 2045 retrieves and analyzes EPG data stored in the storage 2035 to restore EPG data. The EPG decoder 2045 provides the restored EPG data to the ITF operation controller 2050.

The ITF operation controller 2050 controls the operation of the ITF. The ITF operation controller 2050 controls the SI decoder 2040, the EPG decoder 2045, and the display module 2080, and processes requests input from the channel service manager 2055 and the application manager 2060.

The ITF operation controller 2050 controls the SI decoder 2040 to create a channel map and selects a channel using the channel map according to a key input received from the channel service manager 2055. The ITF operation controller 2050 controls the SI decoder 2015 to receive the selected channel. In addition, the ITF operation controller 2050 may control the IP network stack 2015 so that the selected channel is received. Also, the ITF operation controller 2050 may control the PSI / PSIP parser 2070 such that the selected channel is received.

The channel service manager 2055 receives a channel request signal from a user, and provides the input channel request signal to the ITF operation controller 2050 to change the channel to the requested channel.

The application manager 2060 manages the overall state and provides a user interface. When the application manager 2060 receives the EPG display request from the user through the user interface, the application manager 2060 provides the EPG display request to the ITF operation controller 2050 to manage the display module 2080 to display the EPG.

The demultiplexer 2065 demultiplexes the received packet into audio data, video data, and program specific information (PSI) data, and transmits the demultiplexer 2065 to the A / V decoder 2075 and the PSI / PSIP parser 2070, respectively. That is, the demultiplexer 2065 extracts MPEG-2 Transport Stream data from an IP packet received from the IP network stack 2015, and according to each PID (packet identifier) PSI / PSIP parser 2070 or A To the / V decoder 2075.

The PSI / PSIP parser 2070 may store program elements such as PID information of each data (A / V etc.) of the MPEG-2 transport stream in the IP datagram received from the demultiplexer 2060. Extract and parse PSI / PSIP data containing accessible information. In addition, the PSI / PSIP parser 2070 may control the demultiplexing process of the demultiplexer 2065 based on the extracted PSI / PSIP data.

The A / V decoder 2075 decodes the video data and the audio data received at the demultiplexer 2065. To this end, the A / V decoder 2075 may include an audio decoder and a video decoder. The audio data decoded by the audio decoder is provided to the user through the display module 2080, and the video data decoded by the video decoder is displayed through the display module 2080.

The display module 2080 displays video data and audio data decoded by the A / V decoder 2075 under the control of the ITF operation controller 2050. In addition, the display module 2080 receives the EPG data from the ITF operation controller 2050 and displays the received EPG data according to the ITF operation controller 2050.

21 is a flowchart illustrating a process of performing a preferred embodiment of the method for establishing a virtual channel according to the present invention.

Referring to FIG. 21, the ITF performs a network attachment (S2100). Here, the network connection is a procedure in which the ITF establishes a connection between the IP network and the layer 3 layer and acquires network configuration data.

The ITF performs a service provider discovery to obtain a service provider discovery record (S2105). Here, the ITF may perform service provider discovery described above in FIG. 13.

The ITF acquires SI and EPG data using the information included in the obtained service provider discovery record (S2110). Here, the ITF may perform service provider registration and service discovery described above with reference to FIG. 14 to obtain SI metadata. The ITF performs a Service Provider Registration, which allows the ITF to obtain a Registration Output Record (ITF), and based on the information contained in the obtained Registration Output Record (ITF). Discovery can be performed. The ITF may perform service discovery to obtain a master SI table record, a channel map record, and a channel details record. The SI metadata may be calculated from information included in a channel map record and a channel details record.

In addition, the ITF may obtain EPG data based on the information included in the EPGDiscoveryLocation included in the registration output record.

The ITF generates a channel map using the obtained SI metadata and stores the generated channel map (S1215). The ITF receives a user's virtual channel request signal (S1220). Here, the user may select a virtual channel to watch by up / down the channel.

In addition, the ITF generates an EPG using the obtained EPG data and stores the generated EPG (S1225). The ITF displays the stored EPG (S1230). The ITF receives the selected virtual channel request signal from the displayed EPG (S1235). Here, the user can select a specific virtual channel to watch in the EPG displayed on the screen.

The ITF searches for information about the requested virtual channel in the stored channel map according to the virtual channel request signal (S1240). Here, the ITF searches for the channel details location (Channel Details Location) including the SeviceID that matches the SeviceID of the requested virtual channel in the channel map to receive the virtual channel included in the LocationURL of the channel details location. Can be detected. In addition, the ITF may detect channel details including the SeviceID that matches the SeviceID of the requested virtual channel, and detect detailed information of the requested virtual channel.

The ITF tunes to the requested virtual channel based on the information on the retrieved virtual channel (S1245). Here, the ITF may receive an IPTV service for the requested virtual channel by accessing an address indicated by location information capable of receiving the detected virtual channel. The ITF provides the received IPTV service to the user (S1250).

Hereinafter, a method and apparatus for parental control in order to build a channel map in an IPF terminal function (ITF) according to the present invention will be described in detail with reference to the accompanying drawings.

In particular, the present disclosure describes a method and apparatus for more effectively restricting viewing in the ITF according to the present invention using system information (SI) and electronic programming guide (EPG) data essential for service and content use.

In this regard, the term "channel" is used herein to mean both the concept of a channel used in an existing broadcast environment and a channel related to the use of IP-based services and content.

In the present specification, the term "Parental Control" includes a service provided through a corresponding channel when referring to SI data and EPG data that include contents defined in a related standard and are essential for service and content use. The term "access" or "limit" is used to determine whether each content is accessible or the case where the corresponding channel itself is accessed or "limited".

In connection with the present invention, the Federal Communications Commission (FCC), a related organization in North America, forces all digital TV receivers to perform viewing restrictions in accordance with the Rating Region Table (RRT) as defined by ATSC A / 65C and EIA-766A. . Therefore, the ITF requires a parental control function for the virtual channel.

In particular, the following describes the viewing restrictions on each virtual channel in the ITF, not the viewing restrictions on services or contents through each virtual channel. Herein, an example of performing viewing restriction on each virtual channel is described using SI metadata.

FIG. 22 is a diagram for explaining a rating region value allocation of RRT defined in ATSC A / 65C and EIA-766A in relation to the present invention.

Referring to FIG. 22, a current rating region value is allocated from '0x01' to '0x05', and a rating region corresponding to each rating range value is defined. Here, the rating range values '0x01' to '0x04' refer to the United States (50 States + Other Possessions), Canada, Taiwan, and Korea, respectively. In particular, in the United States, in addition to the rating system that corresponds to the existing '0x01', the downloadable rating system is assigned by assigning '0x05' as the rating range value to correspond to the rating system to be newly defined. System is defined to be expandable, and all digital TV receivers are forced to respond to the expansion.

23 illustrates U.S. in connection with the present invention. It is illustrated to describe the rating ratio table system.

Figure 23 shows the current U.S. FCC in the United States FCC. Definitions related to the RRT system. Referring to FIG. 23, a rating system, a number of dimensions, and rating values for each of the dimensions are illustrated. However, referring to the contents of the US FCC described in more detail for this, the detailed description is omitted herein.

24 is a relationship diagram illustrating a correlation between SI data and EPG data of an IPTV system according to an embodiment of the present invention.

4, 5 and 24, the ITF receives a ServiceProviderInfor Table (SI) that provides access information of the service provider registration server and additional information about the service provider. Thus, the ITF can find the service provider and perform the registration procedure.

4, 7 and 24, the ITF provides access information of the master SI table, a list of channel IDs subscribed to by the user, and a service provider remote configuration server. ), ITFRegistrationOutput (SI) that provides access information of the EPG metadata, access information of the EPG metadata, and additional information about the EPG provider. Therefore, the ITF receives the master SI table by using the access information of the received master SI table.

4, 9 and 24, the ITF receives IIFMasterSiTalbe (SI) that provides access information of virtual channel maps and version information of the virtual channel map. Accordingly, the ITF may receive the virtual channel map using the access information and manage the version information.

4, 10 to 11 and 24, the ITF provides access information of a virtual channel description table, a list of virtual channel services, and additional information about each virtual channel service. Receives IIFVirtual Channel Map. Thus, the ITF may use the access information to receive the virtual channel description table.

Referring to FIG. 24, the ITF describes a category of a virtual channel service and receives a virtual channel description table including access information of a stream of the virtual channel service and description information of the virtual channel service. Here, the description information of the virtual channel service includes a virtual channel short name and channel parental guidance rating information.

Referring to FIG. 24, the ITF receives EPG metadata that provides schedule information of content, purchase information of content, and description information of the scheduled content. Here, the description information of the scheduled content includes content name information and content parental guidance rating information.

The virtual channel description table and the EPG metadata are linked to each other. Here, link information is used as the link, and the link information may include a VirtualChannelServiceID and a ServiceIDRef.

In the following, parental control information of SI data format is referred to as channel parental guidance rating information, and parental control information of EPG metadata format is referred to as contents parental guidance information. Name it. However, it is not limited to each said name.

Referring to FIG. 24, channel parity guidance rating information information according to an embodiment of the present invention is included in a VirtualChannelService element. The VirtualChannelService element is included in a VirtualChannelDescriptionTable providing a detailed description thereof, and the included VirtualChannelDescriptionTable may be accessed using access information in a pre-formed VirtualChannelMap element.

In addition, the EPG element includes information about the content parental guidance rating information corresponding to the information on the channel parental guidance rating information according to an embodiment of the present invention in the description information of the scheduled content.

Hereinafter, channel parity guidance rating information according to an embodiment of the present invention will be described in detail.

FIG. 25 illustrates a schema of a rating region table (RTT), which is content parity guidance information received by an ITF as part of EPG data in an IPTV system, and FIG. 26 illustrates the schema of FIG. 25. It is shown in XML form. The RRT defines dimensions and values for the parental guidance rating system.

The ITF receives the RRT and stores it in the storage. The ITF provides an EPG screen that allows the user to set parental control according to the stored RRT if desired. The RRT Type element includes a RatingRegionName element, a RatingRegion element, a TableVersion element, and a Dimension element, and the Dimension element includes child RatingDimensionName element, RatingDimension element, GraduatedScale element, and DimensionValue element. The DimensionValue element is a lower element and includes a RatingValueText element, an AbbrevValueText element, and a RatingValue element. Hereinafter, each element of the RRT Type element will be described with reference to FIGS. 25 and 26. At this time, the name of each element of the RRT type element is displayed in bold to distinguish.

The RatingRegionName element is the name of a rating region applied to the table. The element corresponds to a rating_region_name_text field in the ATSC PSIP standard. (Name of rating region to which this table applies; corresponds to the rating_region_name_text field in the ATSC PSIP Standard).

The RatingRegion element is the code number for the rating ratio to which this table applies. The code number corresponds to the rating_region field of the RRT table of the ATSC PSIP standard. The values approved by ATSC as the Registration Authority will only be used. A table with a RatingRegion value of '1' will not be downloaded (Code number for the rating region to which this table applies; corresponds to the rating_region field of the Rating Region Table in the ATSC PSIP standard.Only those values approved by the ATSC in its role as Registration Authority shall be used.No table with RatingRegion value “1” shall be downloaded).

The TableVersion element is a version of this RRT table (Version of this Rating Region Table).

The Dimension element is a rating definition for a specific rating dimension.

The RatingDimensionName element is the name of a rating dimension. The name corresponds to the dimension_name_text field of the RRT of the ATSC PSIP standard (Name of the rating dimension; corresponds to the dimension_name_text field of the Rating Region Table in the ATSC PSIP Standard).

The RatingDimension element is the code number of the rating dimension. The element corresponds to the index “i” of the rating dimension in the dimensions_defined loop of the RRT of the ATSC PSIP specification (code number of the rating dimension; corresponds to the index “i” of the rating dimension in the dimensions_defined loop of the Rating Region Table in the ATSC PSIP Standard).

The GraduatedScale element is a flag indicating whether there is a rating dimension using the graduated scale. The element corresponds to the graduated_scale field of the RRT of the ATSC PSIP standard. If the gradated scale is used, DimensionValue elements will appear in a table in the order of the most restrictive last in the list restrictive first; corresponds to the graduated_scale field of the Rating Region Table in the ATSC PSIP Standard.If a graduated scale is used, the DimensionValue elements shall appear in the table in order of least restrictive first to most restrictive last).

The DimensionValue element is a definition of a rating value for the dimension.

The RatingValueText element is the text description of the rating value. The element corresponds to the rating_value_text field of the RRT of the ATSC PSIP standard (Text description of the rating value; corresponds to the rating_value_text field of the Rating Region Table in the ATSC PSIP Standard).

The AbbrevValueText element is the simplified text for the rating value. The element corresponds to the abbrev_rating_value_text field of the RRT of the ATSC PSIP standard (corresponding to the abbrev_rating_value_text field of the Rating Region Table in the ATSC PSIP Standard).

The RatingValue element is a code number of the rating value. The element corresponds to the index "j" of the rating value in the values_defined loop of the RRT of the ATSC PSIP standard. (Code number of the rating value; corresponds to the index "j" of the rating value in the values_defined loop of the Rating Region Table in the ATSC PSIP Standard).

The ITF receives and stores the RRT Type element including the elements of FIGS. 25 and 26 described above. In addition, an EPG may be generated and provided according to a user's request to enable a user to restrict viewing.

FIG. 27 is a diagram illustrating a schema structure of SI data and VirtualChannelDescription Table including parental control information according to an embodiment of the present invention, and FIG. 28 is represented as XML as a schema structure of VirtualChannelDescription Table in FIG. 27. 29 shows the schema structure of the RRTParentalGuidance element in FIG. 27 in XML format.

27 to 29, parental control information of the SI data format according to the present invention is included as one of a plurality of sub-elements in a VirtualChannelDescriptionTable element, and the element is called an RRTParentalGuidance element. However, this is arbitrarily determined in order to explain the present invention, but not limited thereto. The VirtualChannelDescriptionTable Type element is a lower element and includes a VirtualChannelServiceId element, a VirtualChannelServiceVersion element, a VirtualChannelServiceCategory element, a VirtualChannelShrotName element, a ProgrammingSource element, and an RRTParentalGuidance element. Here, the RRTParentalGuidance element includes a ratingRegion attribute, a Dimension element, and a RatingDescriptionText element. In addition, the Dimension element includes a RatingDimension element and a RatingValue element. Hereinafter, each element constituting the VirtualChannelDescriptionTable Type element will be described.

The VirtualChannelServiceId element is an ID of each virtual channel. The Virtual Channel has an ID which is used to link to the VIrtual Channel Map and to the EPG entries.

The VirtualChannelServiceVersion element is a counter that increments when any modification are made to this instance of a Virtual Channel Description.

The VirtualChannelServiceCategory element is a type of Virtual Channel Service (Linear or VOD).

The VirtualChannelShortName element defines the short name of the virtual channel (Short name (<7 characters) of the Virtual Channel).

The ProgrammingSource element is typically one or more sources available to the Virtual Channel, differentiated by resolution (eg HD, SD, PIP) and entitlement (eg Barker). generally differentiated by resolution (eg HD, SD, PIP) and entitlement state (eg Barker)).

The RRTParentalGuidance element defines a type for describing parental guidance ratings according to the structure of a single instance of the rating_region loop in the ATSC content advisor descriptor. In any element of this type, the ratingRegion value is a ratingValue associated with a ratingDimension in an instance that matches the ratingValue corresponding to the RRT, each ratingDimension of an instance that matches the ratingDimension that appears in the RRT, and a regular body or specification applicable to the region of interest. Type definition for specifying a parental guidance rating that conforms to the structure of a single instance of the rating_region loop in the ATSC Content Advisory Descriptor [1] .In any element of this type, the ratingRegion value shall match the ratingRegion value of a Rating Region Table approved by a standards or regulatory body applicable to the region of interest, and each rating Dimension of the instance shall match a ratingDimension that appears in that Rating Region Table, and the ratingValue associated with a ratingDimension in the instance shall match a ratingValue for the correspon ding dimension in that Rating Region Table).

The Dimension field is a rating for a specific rating dimension.

The RatingDimension element is a code number for a rating level for a dimension corresponding to the rating_value in the ATSC content advisory descriptor (contents_advisory_descriptor). In any RRTParentalGuidance element, a child element of another dimension may have different values of the rating dimension attribute (Code number for the dimension, corresponding to the rating_dimension field in the ATSC Content Advisory Descriptor.In any RRTParentalGuidance element, different Dimension sub-elements shall have different values of the rating Dimension attribute).

The RatingValue element is a code number for a rating level for a dimension corresponding to the rating_value in an ATSC Content Advisory Descriptor (Code number for the rating level for the dimension, corresponding to the rating_value field in the ATSC Content Advisory Descriptor).

The RatingDescriptionText element is a text description of the overall rating.

The ratingRegion attribute is a code number for rating rating to which this parental guidance rating applies, corresponding to the rating_region field in the ATSC Content Advisory Descriptor. ATSC Content Advisory Descriptor.

30 is a flowchart illustrating a flow of allowing ITF to set parental control to a user according to an embodiment of the present invention.

Here, the ITF receives and stores the RRT data as part of the EPG data and uses the data in enabling the user to set the parental control as described above.

The ITF performs a network attachment (Network Attachment) (S3001). Here, the network connection is a procedure in which the ITF establishes a connection between the IP network and the layer 3 layer and acquires network configuration data. For example, step S3001 may be performed at the Ethernet network interface 2010 and the IP network stack 2015.

The ITF performs a service provider discovery to obtain a service provider discovery record, and receives service providers lists in the obtained service provider discovery record. (S3002). Here, the ITF may perform the service provider discovery described above in FIG. 4. For example, step S3002 may be performed in the Ethernet network interface 2010 and the IP network stack 2015, or may be performed in the SI handler 2025 and the decoder 2040.

ITF selects a service provider SP from the received service provider lists. In operation S3003, an authentication procedure is performed with the selected service provider (SP). Step S3003 is performed at, for example, the Ethernet network interface 2010 and the IP network stack 2015.

The ITF may obtain the SI data and the EPG data using the information included in the obtained service provider discovery record. Here, the ITF may perform service provider registration and service discovery described above with reference to FIG. 4 to obtain SI metadata. The ITF may perform a service provider registration, so that the ITF may receive a registration output record (ITF Regitstration Output Record) (S3004) and perform service discovery based on the information included in the obtained registration output record.

The ITF may perform service discovery to obtain a master SI table record, a channel map record, and a channel details record. SI metadata may be calculated from information included in the channel map record and the channel details record.

The ITF finds location information on the EPG server from which the EPG metadata can be obtained based on the information included in the EPGDiscoveryLocation in the registration output record (S3005). Steps S3004 and S3005 are performed by the file handler 2020, the SI handler 2025, and the decoder 2040, for example.

The EPG server is accessed based on the location information found above (S3006). For example, step S3006 may be performed in the Ethernet network interface 2010 and the IP network stack 2015, or may be performed in the SI handler 2025 and the decoder 2040.

The ITF receives RRT and other EPG metadata from the accessed EPG server (S3007). For example, step S3007 is performed in the file handler 2020 of FIG. 20.

The ITF parses the received RRT and stores the rating system in the parsed RRT (S3008). For example, step S3008 may be performed by the EPG handler 2030, the decoder 2045, and the storage 2035.

When the ITF receives a request for parental control from the user, the ITF appropriately controls parental control on the corresponding virtual channel according to the stored rating system (S3009). For example, operation S3009 may be performed by the application manager 2060, the ITF operation controller 2050, and the storage 2035.

FIG. 31 illustrates access and guide information for a corresponding virtual channel using parental control information received by an ITF included in SI data and parental control settings set by the user in the ITF according to an embodiment of the present invention. It is a flow chart showing the flow of determining whether to provide.

Hereinafter, the steps S3101 to S3103 of FIG. 31 overlapping with the above-described FIG. 30 are used for the steps S3001 to S3003 of FIG. 30 described above and will be described after the step S3103.

The ITF finds location information of SI tables as an output of authorization / registration through step S3103 (S3104). In operation S3105, the virtual channel description table is received and parsed using the location information of the found SI tables.

The ITF parses (S3106) the RRTParentalGuidance element included in the parsed virtual channel description table. The ITF includes a RatingDimension element including one or more rating dimensions applied to the corresponding virtual channel according to the information of the RRTParentalGuidance element parsed and analyzed, and a RatingValue according to the RatingDimension element. The element is also parsed (S3107). Steps S3104 to S3107 are performed by the file handler 2020, the SI handler 2025, and the decoder 2040, for example.

In step S3107, the ITF blocks the corresponding virtual channel based on the values of the parsed RatingDimension element and RatingValue element, that is, at least one rating dimension for the corresponding virtual channel and the rating value according to each rating dimension. Determine whether to block). Hereinafter, the process will be described in more detail.

First, the ITF determines whether a graduated scale is applied to the rating dimension extracted from the parsed field (S3108).

If it is determined in step S3108 that the graded scale has not been applied to the corresponding rating dimension, the ITF determines whether there is a user setting for parental control in the corresponding rating dimension and corresponding rating value (S3109). . As a result of the determination in step S3109, if there is no user setting, the ITF does not block the virtual channel (S3110) and determines whether there are other rating dimensions (S3114). If the ITF determines that there are no more Rating Dimensions as a result of the step S3114, the ITF terminates the procedure. However, if the ITF determines that there are more Rating Dimensions as a result of the step S3114, the ITF will step on the step S3107 again sequentially. Here, in step S3110, the ITF does not block the corresponding virtual channel, which may mean that it consumes IPTV service through the corresponding virtual channel or displays guide information for the corresponding virtual channel. .

However, if the user's setting exists as a result of the determination in step S3109, the ITF blocks the corresponding virtual channel (S3113).

If it is determined in step S3108 that the graded scale is applied to the corresponding rating dimension, the ITF extracts the rating value (first rating value) according to the user's setting for parental control and extracted from the parsed field. The rating value (second rating value) according to the rating dimension is compared (S3111).

The ITF determines whether the second rating value is greater than or equal to the first rating value according to the user's setting (S3112). If the second rating value is greater than or equal to the first rating value, the ITF blocks the corresponding virtual channel (S3113). However, if the second rating value is less than the first rating value, the corresponding virtual channel does not block (S3110). The ITF determines whether the corresponding virtual channel is blocked or not, and then further determines whether there are other dimensions (S3114).

In the above, when the corresponding virtual channel is blocked, the ITF may limit the user's access to the corresponding virtual channel, and also limit the provision of guide information on the EPG for the corresponding virtual channel.

32 to 34 illustrate embodiments of an EPG screen of an ITF including rating information using a rating system defined in an RRT according to the present invention.

32 is an embodiment of an EPG screen under the assumption that no parental control by a user is set. Referring to FIG. 32, in case of an 99-1 channel (adult service), contents having an R rating value are provided in chronological order. For example, in the EPG provision screen, Playboy weekly is provided from 12: 00-13: 00, Basic Instinct is provided from 13: 00-14: 00, and Hustler content is provided from 14: 00-15: 00. In particular, since the parental control is not set to the R rating value, each content of the 99-1 channel will not be blocked.

FIG. 33 illustrates an embodiment in which a user sets parental control (applied to a TV-14 level) in an ITF using EPG data, and an EPG screen is also blocked according to a schedule / content rating. Referring to FIG. 33, content is provided between 12:00 and 13:30 of the 32-1 (Fox-1 service) channel and time between 12:00 and 15:00 through the 99-1 (ADULT service) channel. Three contents provided in units are blocked according to the user's setting.

FIG. 34 illustrates an embodiment of blocking an EPG screen for a virtual channel according to a user's parental control setting (applied to a TV-14 grade) using SI data proposed by the present invention. In the case of FIG. 34, it is assumed that a block for Schedule / Content and an EPG screen block for the virtual channel are combined in parallel using EPG data. In the case of FIG. 33, the content is blocked according to a user's setting, whereas in FIG. 34 according to an embodiment of the present invention, the corresponding virtual channel is blocked. At the same time, it also blocks EPG data.

Therefore, according to the present invention, it is possible for the ITF to implement parental control for each virtual channel by using parental control information included in SI data, thereby providing a more secure IPTV service. There is an effect that can be provided.

On the other hand, the terms used in the present invention (terminology) are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of a person skilled in the art, the definition of which is used throughout the present invention. It should be based on what has been done.

The present invention is not limited to the above-described embodiments, and can be modified by those skilled in the art as can be seen from the appended claims, and such modifications are within the scope of the present invention.

And, the above-mentioned numerical value is a preferred embodiment or merely an example, and the scope of the present invention is not limited to the numerical values, and as can be seen in the appended claims, the general scope of the present invention. Modifications are possible by those skilled in the art and such modifications are within the scope of the present invention.

1 is a system configuration diagram showing the concept of an IPTV service;

2 schematically illustrates a multicast scheme,

3 is a diagram schematically illustrating a unicast scheme;

4 is a flowchart illustrating a process of searching for an IPTV service according to an embodiment of the present invention;

5 is a diagram illustrating a schema of a service provider discovery type according to one embodiment of the present invention;

6 is a diagram illustrating a schema of an ITF Registration Input Type according to an embodiment of the present invention;

7 is a diagram illustrating a schema of an ITF registration output type according to an embodiment of the present invention;

8 is a view showing a relationship between each table constituting a service information (SI) in the context of the present invention,

9 illustrates a schema of a Master SI Table Record Type according to an embodiment of the present invention;

10 illustrates a schema of a channel map type according to an embodiment of the present invention.

11 is a diagram illustrating a schema of a channel map type according to another embodiment of the present invention;

12A and 12B illustrate a schema of a channel details type according to an embodiment of the present invention.

FIG. 13 is a flowchart illustrating a process of performing service provider discovery according to an embodiment of the present invention. FIG.

14 is a flowchart illustrating a process of performing service provider registration and service discovery according to an embodiment of the present invention.

15 is a flowchart illustrating a process of a method of processing an update of a master SI table according to an embodiment of the present invention;

16 is a flowchart illustrating a procedure of a method of processing an update of a master SI table according to another embodiment of the present invention;

17 is a flowchart illustrating a process of a method of processing an update of Channel Details Version according to an embodiment of the present invention;

18 is a flowchart illustrating a process of a method of processing an update of a channel detail version according to another embodiment of the present invention;

FIG. 19 illustrates a schema of an EPG Discovery Record Type according to an embodiment of the present invention. FIG.

20 is a block diagram showing the configuration of an IPTV terminal function (ITF) according to an embodiment of the present invention;

21 is a flowchart illustrating a process of performing a virtual channel setting method according to an embodiment of the present invention;

FIG. 22 is a view to explain rating region value allocation of RRT defined by ATSC A / 65C and EIA-766A in relation to the present invention;

23 illustrates U.S. in connection with the present invention. Depicted to describe the rating ratio table system,

24 is a relationship diagram showing a correlation between SI data and EPG data of an IPTV system according to an embodiment of the present invention;

FIG. 25 illustrates a schema of a rating region table (RRT) which is Contents Parental Guidance Rating information that an ITF receives as part of EPG data in an IPTV system in accordance with the present invention.

FIG. 26 illustrates the schema of FIG. 25 in an XML format.

27 illustrates a schema structure of SI data, VirtualChannelDescription Table, including parental control information according to an embodiment of the present invention;

FIG. 28 is a schema structure of a VirtualChannelDescription Table of FIG. 27 in XML format.

FIG. 29 is a diagram illustrating an XML format of a schema structure of an RRTParentalGuidance element in FIG. 27;

30 is a flow chart illustrating a flow for ITF to set up Parental Control for a user according to an embodiment of the present invention;

FIG. 31 determines whether to provide access and guide information for a corresponding virtual channel by using the Parental Control information received by the ITF included in the SI data and the Parental Control setting already set in the ITF according to an embodiment of the present invention. A flow chart showing the flow

32 to 34 illustrate embodiments of the EPG screen of the ITF including rating information using the rating system defined in the RRT according to the present invention.

Claims (18)

In the IPTV receiver, after building a channel map using a plurality of tables in service information in a service discovery process, a virtual channel is built. In performing parental controls, Receiving a virtual channel map table defining a virtual channel map instance; Parsing first location information about a virtual channel description table in the received virtual channel map table; Receiving the virtual channel description table defining virtual channel descriptions for the virtual channel in the virtual channel map according to the parsed first location information; Parsing viewing restriction information indicating default parental guidance associated with a rating system of the virtual channel in the received virtual channel description table; And Parental control for the corresponding virtual channel; Parental control method for a virtual channel comprising a. The method of claim 1, At least one of detailed information about the service provider, service server authentication information of the service provider, and connection server location information for the service provider attachment in the service provider discovery process. Receiving a service provider information record (serviceproviderinfo record) comprising a; viewing restriction method for a virtual channel further comprising. The method of claim 2, Receiving an authentication information record (authenticationinfo record) in accordance with the authentication server location information in the received service provider information record. The method of claim 3, And receiving a provision information record for accessing an authenticated service provider based on the received authentication information record. The method of claim 4, wherein Parsing second location information for a master service information table in the received provisioning information record. The method of claim 5, And receiving a master service information table including a list of virtual channel map tables according to the parsed second location information. The method of claim 6, Parsing third location information of the virtual channel map table in the received master service information table. The method of claim 4, wherein The provision information record, It further includes EPG provider information that provides electronic program guide (EPG) data. The EPG data received according to the EPG provider information includes a rating region table (RRT) table that provides the allowed values for the parental control information for different regions, program contents and services. A parental control method for a virtual channel that includes program description information that provides detailed information. The method of claim 8, The EPG data, A viewing restriction method for a virtual channel further comprising virtual channel identifier information and service identifier reference information. delete The method of claim 8, The parental level information in the virtual channel description table and the RRT table information in EPG data are respectively: A viewing restriction method for a virtual channel comprising at least one of attribute information of a rating area, dimension information defining dimensions, and rating description information describing ratings. The method of claim 11, The dimension information, A viewing restriction method for a virtual channel including rating dimension information identifying a rating dimension and rating value information identifying a rating value. The method of claim 9, The EPG data, A parental control method for a virtual channel linked to the virtual channel description table based on link information and used for parental control for the virtual channel. The method of claim 13, The link information, And a virtual channel identifier information in the EPG data and virtual channel identifier information in the virtual channel description. An IP network stack for receiving an IP stream including service information data and program guide data; A file handler for demultiplexing service information data and program guide data included in the received IP stream; A first element including a master service information table, a virtual channel map table, and a first element indicating that there is a default parental guidance rating of the virtual channel A service information handler for demultiplexing a virtual channel description table; A program guide handler for demultiplexing a rating region table (RRT) that includes a second element in the demultiplexed program guide data indicating that there is a default parental guidance rating of the virtual channel; A service information decoder for parsing the first element from the demultiplexed virtual channel description table; A program guide parser that parses the first element from the demultiplexed RRT; And And a controller configured to control the display by applying a rating based on a type of a parental guidance system according to the parsed first and second elements. The method of claim 15, The control unit, And control to display a program guide screen based on the parsed second element. The method of claim 16, And a storage unit for storing the demultiplexed master service information table, a virtual channel map table, a virtual channel description table, and an RRT. The method of claim 17, And a display unit for displaying the displayed program guide screen and a virtual channel service.

Images