WO2011005051A2 - Procédé et appareil permettant de contrôler et de mettre à niveau un micrologiciel à distance - Google Patents

Procédé et appareil permettant de contrôler et de mettre à niveau un micrologiciel à distance Download PDF

Info

Publication number
WO2011005051A2
WO2011005051A2 PCT/KR2010/004478 KR2010004478W WO2011005051A2 WO 2011005051 A2 WO2011005051 A2 WO 2011005051A2 KR 2010004478 W KR2010004478 W KR 2010004478W WO 2011005051 A2 WO2011005051 A2 WO 2011005051A2
Authority
WO
WIPO (PCT)
Prior art keywords
firmware
information
network
tracker
upgrade
Prior art date
Application number
PCT/KR2010/004478
Other languages
English (en)
Korean (ko)
Other versions
WO2011005051A3 (fr
Inventor
김경호
홍호택
김진필
이준휘
스톡하머토마스
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2011005051A2 publication Critical patent/WO2011005051A2/fr
Publication of WO2011005051A3 publication Critical patent/WO2011005051A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/81—Monomedia components thereof
    • H04N21/8166—Monomedia components thereof involving executable data, e.g. software
    • H04N21/818—OS software
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/434—Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream
    • H04N21/4348—Demultiplexing of additional data and video streams
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/632—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing using a connection between clients on a wide area network, e.g. setting up a peer-to-peer communication via Internet for retrieving video segments from the hard-disk of other client devices

Definitions

  • the present invention relates to a method and apparatus for remote management and firmware augmentation in an IP network environment. More particularly, in the IPTV network environment, a method of managing monthly IPTV receivers over an IP network and upgrading firmware of an IPTV receiver is provided. A method and apparatus are disclosed.
  • Existing TV transmits contents produced by broadcasting company through radio transmission media such as terrestrial, cable or satellite, and viewers watch through TV receiver which can receive each transmission media. Serviced in such a way.
  • various contents such as real-time broadcasting, contents on demand, games, news, etc. can be obtained by using the Internet connected to each household in addition to the existing radio media. It can be provided to viewers.
  • An example of content provision using the Internet is IPTVGnternet Protocol TV).
  • IPTV refers to a service that provides information services, video content, and broadcasting to a television using high-speed Internet.
  • IPTV is common in that it provides broadcast content including video. Similar to cable or satellite broadcasts, but with the added feature of bidirectionality. And unlike general public broadcasting, cable broadcasting or satellite broadcasting, viewers can watch programs they want to watch at their convenient time.
  • the detailed information, the access location, the service provider information, the service channel, etc. for each content may be provided using the content guide service.
  • the concentration of traffic to the provider of the content cannot be avoided, and the concentration of the traffic causes a decrease in the speed of providing and delivering the content and other deterioration in service quality.
  • the technical problem to be achieved by the present invention is to provide a more efficient and convenient broadcasting environment for the receiver manufacturers and users by performing remote management in the broadcast receiver of the IPTV environment, and upgrading the firmware of the IPTV receiver in a peer-to-peer manner. To provide.
  • the IPTV receiver can download various contents in a peer-to-peer manner.
  • IPTV receivers can download not only CoE Content on Demand, but also broadcast content provided in real time in a peer-to-peer manner, which greatly increases network utilization efficiency and significantly reduces traffic concentration in terms of service providers. have.
  • the content download path can be operated efficiently, increasing the content receiving speed and system efficiency.
  • according to the present invention has an effect that can provide the user with information about the various content that can be downloaded in a P2P manner through the program guide.
  • FIG. 1 is a diagram illustrating a layer model of an IPTV environment according to an embodiment of the present invention.
  • FIG. 2 is a diagram illustrating a Remote Management System (RMS) -FUSCFirmware Upgrade System (RMS) architecture according to an embodiment of the present invention.
  • RMS Remote Management System
  • RMS FUSCFirmware Upgrade System
  • FIG. 3 is a diagram illustrating a management object for an IPTV receiver of RMS according to an embodiment of the present invention.
  • FIG. 4 is a CE device according to an embodiment of the present invention, in which a DVB-IPTV receiver performs a provisioning process and receives SD & S information.
  • FIG. 5 is a diagram illustrating a file delivery architecture of a general IPTV network and a P2P network according to an embodiment of the present invention.
  • FIG. 6 is a diagram illustrating a firmware upgrade architecture using a P2P network according to an embodiment of the present invention.
  • FIG. 7 is a diagram illustrating a firmware upgrade architecture using a P2P network according to another embodiment of the present invention.
  • FIG. 8 is a diagram illustrating a granular firmware upgrade architecture using a P2P network according to an embodiment of the present invention.
  • FIG. 9 is a diagram illustrating a granular firmware upgrade architecture using a P2P network according to an embodiment of the present invention.
  • FIG. 10 is a diagram illustrating a remote management architecture using a P2P network according to an embodiment of the present invention.
  • 11A through 11D are diagrams illustrating information of a CE device that can be managed by RMS as an embodiment of an object information file transmitted from the CE device to the RMS.
  • 12 is a diagram illustrating a call pull for a method of transmitting managed objects from a CE device to an RMS server using the XCAP protocol according to an embodiment of the present invention.
  • FIG. 13 is a flowchart illustrating a multicast announcement method executed with booting according to an embodiment of the present invention.
  • FIG. 14 illustrates a FUS stub file received by a CE device according to an embodiment of the present invention.
  • FIG. 15 illustrates a FUS stub file for downloading firmware through a P2P protocol according to an embodiment of the present invention.
  • 16 is a flowchart illustrating a method of upgrading firmware by performing a firmware update announcement by multicast according to an embodiment of the present invention.
  • 17 is a diagram illustrating a call flow for upgrading firmware by performing a firmware update announcement by multicast according to an embodiment of the present invention.
  • 18 is a flowchart illustrating a method of upgrading firmware by performing a firmware update announcement unicast according to an embodiment of the present invention.
  • 19 is a diagram illustrating a call flow for upgrading firmware by performing a firmware update announcement unicast according to an embodiment of the present invention.
  • 20 is a flowchart illustrating a method of upgrading firmware by unicasting a firmware update announcement according to another embodiment of the present invention.
  • FIG. 21 is a diagram illustrating a call flow of upgrading firmware by performing a firmware update announcement unicast according to another embodiment of the present invention.
  • FIG. 22 is a diagram illustrating a call flow for upgrading firmware by performing a firmware update announcement unicast according to another embodiment of the present invention.
  • 23 is a diagram illustrating P2P network subscription / cancellation of an IPTV receiver according to an embodiment of the present invention.
  • 24 illustrates virtual disk space of peers connected to a P2P network according to an embodiment of the present invention.
  • 25 is a diagram illustrating a disk space management method of a CE device for a P2P network according to an embodiment of the present invention.
  • 26 is an interface illustrating a disk use management screen provided to a user according to an embodiment of the present invention.
  • FIG 27 illustrates an IPTV receiver according to an embodiment of the present invention.
  • FIG. 28 is a flowchart illustrating a firmware upgrade method of a CE device according to an embodiment of the present invention.
  • a CE (Customer Electronics) device detects a firmware upgrade and transmits firmware between products of the same model. How to download / upgrade, network connection of each product, It is about connection with CE manufacturer (Manucacturer).
  • the CE device may be described below as an example of an IPTV receiver.
  • the CE device may be connected to an image providing device such as a TV, such as an IPTV, a receiver, a set top box, a modem, a home network end device (HNED), It includes a device or a relay device for providing content through.
  • 1 is a diagram illustrating a layer model of an IPTV environment according to an embodiment of the present invention.
  • an IPTV environment may be divided into a plurality of layer models, which may be viewed as a business model classification. That is, how each provider handles different layers.
  • the IPTV layer may be classified into a physical layer 1010, a network / transport layer 1020, a session layer 1030, and an application (application) layer 1040.
  • Physical layer 1010 represents the physical connections described in each domain. That is, the flow of content will be described as an example, and the content may be provided from the content provider 1050 to the service provider 1060 and delivered to the home device 1080 through the delivery network 1070. .
  • the content provider 1050 may deliver content to the home device 1080 only through the service provider 1060 and the delivery network 1070. However, as the upper layer becomes less dependent on such a network, the content provider 1050 may directly provide content to the home device 1080 in the application layer 1040.
  • the present invention may describe a CE manufacturer as an embodiment of the content provider 1050 and a CE device or IPTV receiver as an embodiment of the home device 1080.
  • content providers, service providers, delivery network providers, users of home devices, and manufacturers of home devices have different roles and interests.
  • a user may focus on the use of the device, such as system usage and capacity of the home device.
  • the content provider may focus on managing content downloads from a CoE Content on Demand (SME) server, controlling the P2P network, copyright protection of the content, and the like.
  • the service provider may focus on provisioning home devices, such as IPTV receivers, managing media flow and content protection, and monitoring user channel usage.
  • the delivery network provider may focus on the management of the Dearvery Network Gateway (DNG), the provisioning of the home gateway, the bandwidth management of the up / down links, the gateway diagnosis, and the management of IP orders, routing paths, and ports.
  • DNG Dearvery Network Gateway
  • CE manufacturers can focus on diagnosing IPTV receivers (memory, storage, connected devices, etc.), feedback on hardware / software problems, and reporting problems.
  • CE manufacturers need to remotely manage CE devices such as IPTV receivers, which include providing services such as remote diagnostics and firmware upgrades.
  • CE manufacturers can provide these services only through the service provider or delivery network manager on the physical layer, and it is difficult to provide these services on the IPTV receiver side without the service provider.
  • CE manufacturers provide services such as remote management and firmware upgrades to IPTV receivers through a P2P network, and IPTV receivers automatically recognize these services and share firmware upgraded or downloaded firmware as P2P. Describe how to do this.
  • the DVB-IPTV environment is used as an example.
  • IPTV receivers provide a variety of services, the functions of IPTV receivers are becoming more complex, and the number of cases in which basic performances are released and upgrades are provided later to secure business feasibility.
  • the functions of CE devices such as IPTV receivers become more diverse and complex, the importance of firmware upgrades of software mounted on CE devices is increasing.
  • FIG. 2 is a diagram illustrating a Remote Management System (RMS) -FUSCFirmware Upgrade System (RMS) architecture according to an embodiment of the present invention.
  • RMS Remote Management System
  • RMS FUSCFirmware Upgrade System
  • FIG. 2 shows a DVB-IPTV network divided into FUS 2010 and RMS 2020.
  • the FUS (2010) and the RMS 2020 may be provided separately, and may perform firmware management and remote management, respectively.
  • FUSC2010 and RMS 2020 may be managed / operated by CE manufacturer 2030 or RMS manager 2040 and connected to CE device 2050.
  • the FUS 2010 includes the FUS storage 2060, the FUS manager 2070, the multicast server 2080, the unicast server 2090, and the firmware announcement service unit 2100.
  • 2020 includes an RMS manager 2110 and an RMS inventory unit 2120.
  • the RMS manager 2040 manages information according to the distribution of the CE device 2050, and can handle firmware upgrade by the RMS 2110 in a command, response, request, or the like manner. have.
  • the RMS 2020 detects the CE device 2050 to diagnose diagnostic, fault management, A function such as monitoring of the CE device 2050 may be performed, and when configured together with the FUS 2010, a function of controlling a firmware upgrade function of the FUS 2010 may be performed.
  • numbers indicated by arrows indicate respective interfaces and data transmitted and received on the interfaces.
  • Interface 1 is a firmware package transmitted from the CE manufacturer 2030 and may include files necessary for firmware upgrade.
  • Interface 2 is metadata transmitted from CE manufacturer 2030 and may convey attributes for the firmware package of interface 1 to FUS 2010 or RMS 2020.
  • Interface 3 represents an interface between the CE manufacturer 2030 and the RMS manager 2040 and may be defined as a B2B relationship.
  • Interface 4 represents an interface through which metadata is transmitted / received between FUS 2010 and RMS 2020 for firmware download.
  • Interface 5 represents a multicast delivery interface that is connected to the CE device 2050 via a network to provide service
  • interface 6 represents a unicast delivery interface that is connected to the CE device 2050 via a network to provide service.
  • Interface 7 represents an interface for transmitting a service that notifies CE device 2050 that there is an update of firmware available over the connected network.
  • Interface 8 represents a query answer channel interface for sending a query to determine if there is a firmware update available to CE device 2050 for FUS 2010 without RMS 2010.
  • Interface 9 represents an interface through which information necessary for remote management (eg, diagnostic information for CE device 2050 and its request, etc.) is transmitted.
  • Interface 11 is the firmware received by the FUS manager 2070 from the CE manufacturer 2030. Represents an interface to deliver an update package for storage in FUS storage 2060.
  • Interface 12 represents the interface to deliver to the multicast server 2080 or unicast server 2090 for sending a firmware update package to the CE device 2050.
  • the interface 13 represents an interface through which the RMS manager 2110 transmits information for remote management (eg, metadata, diagnostic information received from the CE device 2050) to the RMS inventory unit 2120.
  • There are two ways to upgrade the firmware 1) planned upgrade by RMS and 2) upgraded by periodic check of CE devices. 1) In the case of the planned upgrade method by RMS, network traffic can be managed and distributed because the planned upgrade is performed, but management burden is incurred.
  • CE devices can download firmware by accessing FUS storage using HTTP, FTP, and TFTP protocols.
  • the FUS and CE devices can perform an authentication step to determine which firmware to download. If authentication is successful, FUS uses Unicast protocols such as HTTP, HTTPS, FTP, TFTP and SFTP to update the firmware to the CE device. Can transmit
  • the multicast scheme represents a method in which a CE device receives firmware and upgrades by joining an arbitrarily designated multicast channel, and may include sub-protocols such as reserved transmission and simultaneous transmission of a plurality of files. If the firmware is transmitted by multicast, it can be transmitted by using DSMJX or FLUTE protocol.
  • the multicast method can be used only in a managed network. Since a variety of products can exist in a managed network, firmware of various models can be transmitted at the same time. Some service providers may use different multicast channels to transmit different firmware when software upgrades of CE devices throughout the network are required due to changes in IPTV services. In the case of reserved transmission, if the multicast for the firmware to be upgraded via the SAP protocol notifies the CE device of the start / end time, the CE device can connect to the channel at this time and download the firmware. However, providing these services directly by CE manufacturers requires a lot of investment in the provision and management of the network.
  • 3 is a diagram illustrating a management object for an IPTV receiver of RMS according to an embodiment of the present invention.
  • the management object defined in FIG. 3 is an object that is received by the RMS manager through interface 9 shown in FIG. 1 and then received by the RMS inventory unit through interface 13 and managed.
  • Each block divided into blocks represents a classification of objects for managing the IPTV receiver, and when such data is received from the IPTV receiver, the RMS manager makes a database It can manage and obtain the information needed to upgrade the firmware or information to be shared with other organizations.
  • FIG. 4 is a CE device according to an embodiment of the present invention, and illustrates a call flow in which a DVB 'IPTV receiver performs provisioning to receive SD & S information.
  • the IPTV receiver 4010 is a device in a consumer domain and corresponds to a set-top box required for a user to use an IPTV service.
  • Provisioning Server (4020), IPTV Application Server (4030), Multicast Server (4040) and LiveMediaServer (4050) are all IPTV service providers.
  • IPTV receiver 4010 via system provisioning server 4020, when the system starts It is provided with a setting to access the network, and in this process, authentication for service provision is performed. If you are authenticated as a normal user or device, you are connected to the network.
  • the service provider uses various methods to provide SD & S information to the IPTV 4010.
  • a typical method is the transmission of SD & S information through a multicast channel. By using multicast channels, the same information can be effectively transmitted to large IPTV receivers and network traffic can be reduced. Transmission over a multicast channel can also be used for live media streaming.
  • the SD & S information is transmitted through the multicast server 4040.
  • the multicast server 4040 data to be transmitted to the IPTV 4010 needs to be updated to the latest version.
  • the IPTV application server 4030 sends the SD & S information to the multicast server 4040
  • the multicast server 4040 creates a well-known multicast channel and sends the SD & S information over this channel. do.
  • an IPTV receiver is normally connected to a network
  • the IPTV receiver attempts to connect to a known multicast channel to receive SD & S information.
  • the IPTV receiver can provide an IPTV service to a user thereafter.
  • the IPTV receiver changes to the designated multicast channel using the received SD & S information.
  • FIG. 5 is a diagram illustrating a file delivery architecture of a general IPTV network and a P2P network according to an embodiment of the present invention.
  • a root node 5010 and 5040 may represent a server having three copies of a file
  • an inode 5020 may represent a relay server that distributes files
  • 5030 may represent a peer.
  • the peer on the network may represent a receiving terminal such as an IPTV.
  • the left diagram of FIG. 5 shows the file delivery architecture of a typical IPTV network.
  • each node 5030 connects to a root node 5030 where a file is provided through an inode 5020 serving as a distribution server, and receives a file. Therefore, as the number of nodes increases, the load and bottleneck of traffic on the inode and the root node become more severe, which may lead to deterioration of transmission speed and quality.
  • 5 shows the file delivery architecture of a P2P network.
  • nodes 5050 are directly connected under one root node 5040 and files are transmitted, and a file that has been once transmitted has a structure that helps mutual transmission between nodes. Therefore, once a file is transferred from a root node to a node, network traffic is distributed because each node plays the role of an child node.
  • the terminal accesses a predetermined P2P tracker address through an application that can access a specific P2P network.
  • P2P networks enable file sharing through logical connections from peer to peer in the network. Therefore, connection to peer-to-peer tracker is essential before peer-to-peer connection can be made.
  • the P2P tracker acts as a server that configures and manages the P2P network.
  • the P2P tracker can be viewed as a database that contains the peer's IP address, port information, version of the P2P application, and index information about the shared files. Therefore, a peer can share a file using a P2P network by connecting to a P2P tracker, and the address of the P2P tracker must be preset in the peer.
  • a peer is a basic unit constituting a P2P network, which may correspond to various broadcasting equipments and receiving terminals according to a network.
  • a peer corresponds to a CE device, an IPTV receiver, a DVB-IPTV receiver, a computer, and the like. can do.
  • Peers connect to the P2P tracker and inform their peers (eg, IP address, port information, version information of the P2P application) and peers attempting to connect. Therefore, smooth communication is possible according to the communication protocol, and data transmission can be performed efficiently.
  • there may be a peer that directly connects some or all of the file and a peer that wants to download the file from the other peer through the P2P network if only part of the file or no file exists.
  • the IPTV receiver basically connects to the central chip network to receive information about what services the receiver can use and how to receive it. This is called reception of service discovery & signaling (SD & S) or SD & S information.
  • SD & S service discovery & signaling
  • the DVB-IPTV system adopts a distribution and reception method of SD & S information through multicast or unicast.
  • the firmware upgrade method using the above-described P2P network will be described.
  • FIG. 6 is a diagram illustrating a firmware upgrade architecture using a P2P network according to an embodiment of the present invention.
  • IPTV service an SP managed system (IPTV service) provided by a service provider
  • the CE manufacturer may provide a firmware upgrade service directly through the P2P network 6040 using the P2P service 6030.
  • the P2P service 6030 may be a P2P tracker.
  • the P2P tracker can handle queries (search requests, search results reporting, etc.) of peers, such as CE devices, and can act as a path between the CE devices and as a search engine. If the CE device can only access the P2P service operated by the CE manufacturer, it can access the FUS storage operated by the CE manufacturer or another CE device that received the firmware and download the firmware at any time. In particular, when the CE manufacturer directly operates the P2P service or the P2P network as shown in FIG. 6, the delay according to the transmission server setting and schedule management of the service provider may be eliminated. For example, CE manufacturers can manage and distribute firmware whenever they need it. In addition, since the CE device that downloaded the firmware through the P2P network can deliver and distribute the firmware to other CE devices, the operating cost of the firmware storage and the cache server may be reduced.
  • FIG. 7 is a diagram illustrating a firmware upgrade architecture using a P2P network according to another embodiment of the present invention.
  • SP managed by a service provider System 7020 is used in conjunction with CE managed system 7010. That is, the service provider transmits the firmware announcement to the CE devices connected to the managed network through the multicast server or the unicast server, and the firmware is transmitted through the P2P network of the open Internet. It tells the network's access address. In this case, multicast channel resources for firmware transmission can be reduced, and service provider server management costs can be reduced. 8 is a diagram illustrating a granular firmware upgrade architecture using a P2P network according to an embodiment of the present invention.
  • the network architecture of FIG. 8 includes a FUS 8010 and an RMS 8020.
  • FUS 8010 and RMS 8020 may be managed / operated by CE manufacturer 8030 or RMS manager 8040 and connected to CE device 8050.
  • the FUS 8010 manages the FUS storage 8060, the FUS manager 8070, the multicast server 8080, the unicast server 8090, and the firmware announcement service unit 8100 and the P2P network service unit 8130.
  • the RMS 8020 includes an RMS manager 8110, an RMS inventory unit 8120, and an IPTV network inventory unit 8140. The description of the content overlapping with the description of FIG. 8 and the increase of the elements of FIG. 8 will be omitted.
  • the FUS manager 8070 controls the P2P network service 8130 to update the firmware location information.
  • the location information of the firmware may include address information of a Content Deli every Network (CDN) server operated by the CE manufacturer 8030 or another CE device 8050 that has successfully downloaded the firmware.
  • the firmware location information includes the firmware holding information, applicable product model information, and the manufacturer's OUI (Organizational Unique Identifier) information, which is the manufacturer's unique ID.
  • the devices 8050 may determine whether to download the corresponding firmware from the firmware location information.
  • forcibly receiving and storing firmware may allow the CE device 8050 to act as a peer in a P2P network, thereby facilitating distribution of the firmware.
  • the CE device 8050 may analyze whether the firmware is a normal firmware through a validation process of the downloaded firmware. If it is determined that the firmware is normal, the CE device 8050 may notify the FUS manager 8070 via the QRC (Query-Response Channel, Interface No. 8) that the downloaded firmware can be transmitted to another CE device. Now, the FUS manager 8070 controls the ⁇ 2 ⁇ network service 8130 to add the information of the CE device just received to the location information for downloading the firmware. According to an embodiment, even if all files or data required for firmware or firmware upgrade are not received, the FUS manager 8070 may be fed back via QRC.
  • interface 13 represents an interface through which the RMS manager 2110 transmits information for remote management (for example, metadata, diagnostic information received from the CE device 2050, etc.) to the RMS inventory unit 2120.
  • information for remote management for example, metadata, diagnostic information received from the CE device 2050, etc.
  • it can convey the configuration of the Internet-TV application of the CE device.
  • Internet—TV applications may be P2P applications that connect CE devices to P2P networks and download content. Service providers can identify Internet-TV applications.
  • Interface 14 represents an interface for transmitting firmware. Through the interface 14, not only the firmware but also location information of the firmware, metadata about the firmware, and the like may be transmitted.
  • the location information of the firmware may include the location information of the FUS storage as well as the location information of another CE device holding the pipware as described above.
  • 9 is a diagram illustrating a granular firmware upgrade architecture using a P2P network according to an embodiment of the present invention.
  • FIG. 9 The architecture of FIG. 9 is connected to UFUS (Unmaged FUS; 9060) and IFUS in addition to the FUS 9010, RMS 9020, CE manufacturer 2030, RMS manager 2040, as shown in FIG. A P2P network system 9070.
  • UFUS 9060 includes UFUS storage 9080 and UFUS manager 9090
  • P2P network system 9070 includes P2P server 9100.
  • CE manufacturer 9030 may directly run UFUS 9060. That is, the CE manufacturer 9030 directly manages firmware distribution using the UFUS manager 9090 and the UFUS storage 9080, and operates the P2P network using the P2P server 9100 to distribute firmware.
  • the UFUS 9060 or the P2P network system 9070 may be operated by a network operator managing a P2P network protocol, a service provider operating a tracker, or the like.
  • the interface la represents the interface through which the CE manufacturer sends the firmware package, as in interface 1.
  • Interface 2a represents an interface for transmitting metadata representing information about firmware. According to an embodiment, the interfaces la and 2a may be used as one interface.
  • Interface 6a represents an interface for delivering firmware to a CE device, in which case the firmware delivery interface may be HTTP (S), FTP, TFP, and P2P network services. In the case of P2P network service, the service provider may perform content delivery or firmware delivery. In addition, not only the firmware but also location information of the firmware, metadata about the firmware, and the like may be transmitted through the interface 6a.
  • the location information of the firmware is described in FUS storage as described above. It may also include location information as well as location information of other CE devices holding firmware.
  • Interface 8a basically performs the same role as interface 8.
  • Interface 11a represents the interface to transfer the firmware to be upgraded from the CE manufacturer to store in UFUS storage.
  • Interface 12a represents an interface through which UFUS transmits firmware to the CE provider to the CE device.
  • interface 12a may represent an interface that transmits firmware packages from the service provider to the P2P network server (or P2P tracker).
  • the interface 13 is the same as the interface 13 of FIG. 8.
  • P2P remote management does not need to distinguish between managed and unmanaged networks. This is because P2P networks can be configured and operated in managed networks.
  • FIG. 10 is a diagram illustrating a remote management architecture using a P2P network according to an embodiment of the present invention.
  • CE devices can be connected to a managed network to receive IPTV services.
  • the CE manufacturer can provide portal services to provide Internet content suitable for the receiver and can remotely manage the CE device. This is referred to as RMS, and remote diagnostics of its products is possible if the CE manufacturer runs the RMS directly.
  • a CE manufacturer may transmit firmware to a CE device requiring an upgrade while operating a P2P network.
  • X-Net is certified by CE devices It's a peer-to-peer network connected to a CE manufacturer that can be accessed easily through the process.
  • the CE device when the CE device is connected to a portal connected to the automatic and / portal to the initial transmission of the specific product information to the P2P CE device and can be connected to the tracker • X- Net.
  • the CE device may be connected to a designated CE manufacturer's portal service or network resource system as the system starts to operate and periodically connect to the P2P network to which the CE manufacturer or CE provider is connected.
  • CE devices are connected to firewalls or gateways provided by service providers, which can block access to external networks.
  • the NAT-T function can be operated with a P2P tracker to enable content or firmware exchange between CE devices.
  • 11A through 11D are diagrams illustrating information of a CE device that can be managed by RMS as an embodiment of an object information file transmitted from the CE device to the RMS.
  • the information included in FIGS. 11A through 11D are collected by the CE device and transmitted to the server, and the storage location of the information may be a server of the CE device or the service provider.
  • the CE device transmits and stores the setting information of the Internet-TV application mounted on the CE device to the Internet-TV service system operated by the service provider, and receives the information when the user uses the Internet-TV application on the CE device. It may work.
  • the files of FIGS. 11A-11D include, as management objects: 1) Bandwidth and transmission management objects, 2) Connect ion management objects, 3) File management objects, 4) Live Streaming Buffer management objects, 5) Storage management objects, 6) Fault management statistics, 7) Service management object, 8) Packet forwarding Statistics, 9) Internet-TV content delivery application configuration ⁇ Included These managed objects can be broken down into objects and attributes to form a detailed XML Schema, each of which will be described later.
  • FIG. 12 is a diagram illustrating a call flow for a method for transmitting managed objects from a CE device to an RMS server using the XCAP protocol according to an embodiment of the present invention.
  • the information of FIGS. 11A through 11D may be transmitted as shown in FIG. 12.
  • the XCAP protocol used in the call flow of FIG. 12 is a protocol capable of transmitting configuration information (brightness, user preference, etc.) of the CE device using the HTTP protocol.
  • the body of the HTTP (S) protocol consists of an XML format.
  • Configuration information is transmitted using the methods defined in XCAP protocol.
  • the CE manufacturer In order to upgrade new firmware, the CE manufacturer must inform the CE device of the model of the firmware to upgrade. This operation is referred to as a firmware announcement or a firmware upgrade announcement, and a service that functions as a firmware announcement must be provided to the CE device.
  • the firmware announcement or firmware upgrade announcement is It may also mean information about the firmware and target device to be upgraded. .
  • the method of transmitting the firmware announcement to the CE device includes 1) a multicast announcement method 2) a unicast announcement method including a P2P announcement method, which will be described in order below.
  • Firmware upgrades are performed by multicasting firmware announcements, including how CE devices receive FUSS information at boot time to upgrade firmware, and service provider provides update announcement information on managed networks. There is a method for transmitting over a multicast channel using a protocol. In the second method, the service provider performs only the firmware announcement, and the firmware upgrade itself may be performed through the P2P network. 13 is a flow chart illustrating a multicast announcement method executed with booting according to an embodiment of the present invention.
  • the CE device performs system booting by inputting power or driving a device of the user (S13010).
  • the CE device accesses the network interface and performs provisioning (S13020).
  • the CE device receives SD & S information with provisioning, as described above with respect to FIG.
  • the FUSS information is information transmitted by the service provider on the SD & S multicast channel.
  • the CE device completes provisioning, it waits for reception of the RMSFUSSDiscovery payload included in the FUSS information (S13030).
  • the CE device checks the Provider ID (S13050).
  • the ProviderlD value is set to '1', the ProviderlD is matched (S13060) to check the ManufacturerOUI value.
  • the ProviderlD is matched (S13060) to check the ManufacturerOUI value.
  • the FUS stub file included in the received FUSS information will be described. 14 illustrates a FUS stub file received by a CE device according to an embodiment of the present invention.
  • the FUS stub file of FIG. 14 is a device information (CE [DeviceClassInfoD], software information about a software or file package including firmware ([SoftwarePackagelnfo]), and a CE device to which the firmware is to be upgraded.
  • Resource information [ResourceAccessInfo]) for a resource that can be located in.
  • the information about the resource is a URL to a location such as a server of a service provider, a CE manufacturer, or the like, which must be connected to download firmware as shown in FIG. 15 is a diagram illustrating a FUS stub file for downloading firmware through a P2P protocol according to an embodiment of the present invention.
  • the information about the resource includes the URL information of the P2P locator.
  • the URL information of the P2P locator may be the address of the tracker of the P2P network for the firmware upgrade.
  • the CE device can know that the download of the firmware should be performed using a P2P application. Therefore, the CE device can run a P2P application or have a running P2P application connect to the URL address of the P2P locator.
  • the URL information included in the FUS stub file may include a query for information (model name, hardware version, etc.) of a product to be upgraded as follows.
  • the query may include various information about the CE device or software to perform the firmware upgrade. For example, if a service provider is requested to upgrade a specific model from a CE manufacturer, the Fus Stub File can be configured to include only queries for upgrading that model. In addition, as another embodiment, it may include only the URL for the software to upgrade as follows.
  • URL p2p: // tracker. lge.com/dvb/p2p/STB-Software
  • the CE device can directly query or download the firmware via established communication with the CE manufacturer.
  • 16 is a flowchart illustrating a method of upgrading firmware by performing a firmware update announcement by multicast according to an embodiment of the present invention.
  • a service provider using a multicast channel receives a request from a CE manufacturer and transmits an updater announcement of firmware through a managed network (S16010)
  • the CE receiver updates through a multicast channel. Receive a message (S16020).
  • the CE receiver may request metadata about the firmware from the analyzed 0ICD locator (S16050).
  • 01 CD Open Internet Content Deli every locator is a locator of an operator operating an OICD network, and may represent a locator of a P2P network or a locator of a P2P tracker in the present invention.
  • the CE device may access the location of the firmware using the metadata (S16070).
  • the metadata about the firmware may include information about the firmware (device information of the firmware upgrade, software information, location information of a peer (CE device) having the firmware, list information of peers having the firmware, and the like). have.
  • the CE device may check the next location information holding the firmware to be downloaded from the location list information of the metadata (S16090).
  • FIG. 17 is a diagram illustrating a call flow for upgrading firmware by performing a firmware update announcement by multicast according to an embodiment of the present invention. In FIG. 17, a description overlapping with FIG. 16 will be omitted.
  • the ISU7040 transmits a firmware upgrade announcement to the CE device 1 1730 through a multicast channel, and the CE device 1 1730 uses information included in the firmware upgrade announcement.
  • the 0ICD locator which is the tracker's position information, is interpreted, and the 0ICD locator, It can connect to the tracker 1720.
  • the CE device 117030 receives metadata about the above-described firmware from the P2P tracker 1720 and connects to the CE device 2 17010 having the firmware.
  • the CE device 117030 may request a firmware transmission from the CE device 217010 to download all or part of the firmware.
  • the following is an embodiment of a part of the displacement included in the firmware upgrade announcement of FIG. 17 and transmitted.
  • Firmware upgrade announcements can be sent via the SAP protocol.
  • the CE devices in the managed network first begin with the "x-dvb-rms-ce-manufactuer" line a. If the 0UI matches the 0UI by looking at the field, the "application 1234 TCP P2P" field of the m line is used to determine how to download the firmware. That is, as in the above embodiment, a TCP connection can be made to the port 1234 of the application, which means that it is an application layer of the P2P network, where "P2P" means "X-dvb-rms-qrc: p2p: // tracker. ce-manufacturer.
  • the ⁇ parameter> part may include information on the firmware to be upgraded. For example, you can send a unique identifier, such as a hashcode or UUID, or you can query and send some elements of data elements in the RMS-FUS XML schema. The following is an embodiment of such a query.
  • the CE device can inform the desired firmware location according to a query, where the location can be the CDN server of the CE manufacturer or the CE device of the CE manufacturer. As described above, information about the location of this firmware may be transmitted as part of the metadata for the firmware.
  • the unicast announcement method is a method in which a receiver connects to a CE manufacturer or service provider at boot time or periodically to check for new firmware.
  • the CE device may perform unicast communication using a unicast-only protocol such as HTTP (S) or FTP.
  • HTTP HTTP
  • FTP FTP
  • the announcement via the P2P network is performed when the CE device joins the P2P network according to the embodiment.
  • a method of receiving a firmware upgrade announcement by a tracker and a method of receiving a firmware upgrade announcement through communication between peers after connecting to a P2P network are possible, which will be described below in order.
  • 18 is a flowchart illustrating a method of upgrading firmware by performing a firmware update announcement unicast according to an embodiment of the present invention.
  • the CE device completes booting, performs provisioning (S18010), and then signs in to the P2P network and accesses it (S18020).
  • the CE device provides the tracker with its device information (e.g., serial number, firmware version, etc.) upon connection (S18030), and the tracker uses the CE device's information to download it via the P2P network. Search whether there is a newer firmware version (S18040).
  • device information e.g., serial number, firmware version, etc.
  • the tracker transmits a list of peers having the latest version of firmware to the CE device (S18060).
  • the CE device receives and arranges the list (S18070) and connects to a peer to download firmware (S18080). In this case, the CE device may simultaneously connect to a plurality of peers.
  • the CE device requests transmission of firmware to the connected peer (S18090).
  • the CE device may request transmission of all of the firmware to one peer, or may request transmission of all or part of the firmware to one or a plurality of peers. If it is possible to transmit new firmware (S18100), the CE device receives all or part of the firmware (S18110), and performs the upgrade using the received firmware.
  • 19 illustrates a firmware update announcement according to an embodiment of the present invention. A diagram showing a call flow for upgrading firmware by performing unicast.
  • the CE device 19030 connects to the portal 1902 and undergoes device recognition.
  • CE manufacturer information CEManufacturerlnfo
  • SoftwareVersionList software version information
  • SerialNuraber serial number
  • MAC address manufacturer-specific information
  • Vendor Specif iclnfo manufacturer-specific information
  • the P2P tracker 19010 may receive a firmware search request from the portal 1902 and search whether the firmware corresponding to the CE device 19030 connected to the portal 1902 needs to be upgraded.
  • the search results can be sent to the portal 1930, and eventually a firmware announcement is sent to the CE device 1930.
  • the firmware announcement may include metadata about the firmware in addition to the information about the firmware.
  • the metadata about the firmware may include list information of a peer including the firmware.
  • 20 is a flowchart illustrating a method of upgrading firmware by unicasting a firmware update announcement according to another embodiment of the present invention. In FIG. 20, first, a CE device signs and connects to a P2P network (S20010).
  • the CE device When connected to the P2P network, the CE device transmits a search request including a specific search word to the tracker (S20020).
  • the specific search word includes a search word for searching for the same or the same device that the connected CE device wants to connect to search for firmware.
  • the CE device may request a list of peers that can know whether to upgrade the firmware through a search word such as its device model or software information.
  • the CE device receives a list of peers for the search request (S20030).
  • the CE device connects to one or more peers included in the list (S20040), and the CE device.
  • the device information is exchanged with each other (S20050).
  • the CE device searches whether the latest firmware exists (S20070). If there is the latest firmware, it is determined whether the firmware is compatible with the CE device and its own device (S20080). If the firmware is compatible, the firmware is requested to be downloaded (S20090) and the firmware is downloaded from the peer (s) (S20100). .
  • the CE device may check whether the downloaded firmware is a valid firmware from the CE manufacturer (S20110). If the firmware is valid (S20120), the firmware may be upgraded (or system upgraded) (S20140), and the system may be rebooted (S21050) to notify the user that the upgrade of the firmware is completed (S20160). Upon rebooting the system, the CE device detects a boot error, or detects a driving error of the firmware. If there is no error, the CE device can confirm that the firmware upgrade is completed.
  • FIG. 21 is a diagram illustrating a call flow of upgrading pipware by performing a firmware update announcement unicast according to another embodiment of the present invention.
  • contents overlapping with those described in FIG. 20 will be omitted or briefly described.
  • FIG. 21 illustrates a method of exchanging information with peers directly without transmitting device information to a portal or tracker to which a CE device connects, unlike FIG. 20.
  • FIG. 21 illustrates a method of exchanging information with peers directly without transmitting device information to a portal or tracker to which a CE device connects, unlike FIG. 20.
  • the CE device 1 21030 connects to the P2P tracker 21010 to receive a list of peers, and connects to a peer included in the list.
  • CE device 121030 connects to CE device 221020 and exchanges device related information such as manufacturer 0UI, model number, and version information.
  • the CE device 1 21030 may request the CE device 2 21020 to download the firmware.
  • the CE device 1 21030 may determine whether the firmware upgrade is necessary based on the version number of the firmware.
  • FIG. 22 is a diagram illustrating a call flow for upgrading firmware by performing a firmware update announcement unicast according to another embodiment of the present invention. In FIG. 22, contents overlapping with those described in FIG. 20 or 21 will be omitted or briefly described.
  • the CE device 1 22030 does not download firmware directly from the CE device 2 22020 and transmits a request for the confirmed firmware to the portal 22010.
  • the portal (22010) can be a FUS server operated by a CE manufacturer and can be used by service providers that perform firmware upgrades. It could be a server or a P2P tracker.
  • the portal 22010 may check the firmware request requested from the CE device 1 22030 and transmit metadata or firmware upgrade announcement about the firmware to the CE device 1 22030 when the firmware upgrade is required. Thereafter, the process of downloading and upgrading firmware by accessing another peer through a list is as described above. In the following, remote management of the Internet-TV application will be described.
  • the Internet-TV application is a video application installed in a product using a service of which quality of service (QoS) of the open Internet is not guaranteed, and may be a network program that operates by receiving video data through a P2P network.
  • Internet-TV applications can be installed in the receiver as plug-ins sent by service providers on the open Internet, or CE manufacturers can be provided in embedded software to meet protocol specifications or application requirements.
  • FIGS. 11A through 11D information briefly described with reference to FIGS. 11A through 11D will be described.
  • Information for such remote management can be transmitted to the tracker or portal using the XCAP protocol, or can be transmitted using the SOAP method used in the existing RMS.
  • the bandwidth and transport management object contains information about the bandwidth available to the CE-Internet application of the CE device and the size and transmission rate of the content transmitted over the P2P network. This information is reported to the tracker when it is connected, and using this information along with file management object information, the tracker can You can find out what content is being sent and at what speed.
  • a peer with a high ratio can compensate by assigning a priority of fast transmission or transmission from other peers or CDN server.
  • P2P network is a structure in which peers are connected and content is exchanged by transmitting each other. If peers do not operate in this collaborative structure, the content distribution structure of the P2P network is slow and inefficient. Therefore, proper management is necessary to maintain transmission efficiency. By sending information related to peers' connections to the tracker, the tracker can easily determine which peers actively participate in the transmission and content distribution.
  • an Internet-TV application when an Internet-TV application receives content through a P2P network, it distinguishes between a CE device that actively participates in content transmission and an inactive CE device to determine which peer participates in the transmission. You can tell the tracker the record. Peers record information about what content they sent, their capacity, and who they sent it to, and the receiving peers also report it to the tracker.
  • Inactive peers are known as CE devices that cover part or all of the content to the tracker, but they are information of peers that are not connected by excessive connections or who have requested to send content. The reason for sending this information is to schedule and manage the transmission when other peers are up and off or have problems connecting. Occasionally, an inactive peer finishes all transmissions requested by another inactive peer to a portion of the reserved content. In this case, the state may be changed to an active peer. As such, the CE devices in the inactive peer list and the active peer list may change according to circumstances.
  • the rejected connection and disconnected connection information records peers who have requested content download from peers received as a list from the tracker but have been denied or disconnected. In some RMS systems, it may be used as a way to reject blacklisted peers.
  • FIG. 23 is a diagram illustrating P2P network subscription / cancellation of an IFTV receiver according to an embodiment of the present invention.
  • FIG. 23 a case of subscribing to a service provider or canceling or withdrawing from a specific service provider is shown.
  • Both service provider A and service provider B provide content through the open Internet, which can be referred to as service A and service B, respectively.
  • the user of the IPTV receiver terminates service A and attempts to subscribe to service B.
  • the P2P service can be divided into a live media streaming service and a download service. Since the download service performs high-definition content distribution or scheduled transmission of a user, storage management of a storage medium is required. That is, storage management according to the capacity setting of the receiver's hard disk and the subscription / unsubscription of the P2P service provider are required.
  • the target disk can be divided into system disk space and user disk space.
  • the system disk space is basically the receiver's disk space required by the service provider to which it subscribes. Freely available Each stands for disk space.
  • System disk space is a space reserved by the Internet-TV application and is not accessible to users.
  • each disk space may be divided and referred to as a partition, and the stored space may be protected through encryption.
  • the reason service providers need system disk space is to virtualize the user's receiver space to reduce the cost of maintaining the service provider's CDN, and to distribute content by appropriately distributing the virtualized missions. .
  • FIG. 24 illustrates virtual disk space of peers connected to a P2P network according to an embodiment of the present invention.
  • the service provider A and the service provider B can know which peers are connected through the P2P tracker, and how much system disk space can be used. In this way, the storage management object information as defined in FIGS. 11A to 11D may be transmitted through the tracker so that service providers can identify each system disk space. In addition, when a CE device joins, information about such a local disk space can be exchanged.
  • the service provider uses 1.5 GB of virtualized system disk space of six IPTV receivers connected to the P2P network. It is possible to secure a content distribution capacity of. That is, if 1000 CE devices are connected as shown in FIG. 24, a CDN having a capacity of 15 TB may be configured.
  • 25 is a diagram illustrating a disk space management method of a CE device for a P2P network according to an embodiment of the present invention.
  • the local disk space of the CE device may be a boot area (Boot). Area, OS, and firmware may be used as a space for a P2P network.
  • the receiver must provide the logical partitions that these physical spaces and Internet-TV applications access.
  • the user space is defined as "Vdev / hdal / p2p / user” and the system disk space required by the service provider is defined as "Vdev / hdal / p2p / system” so that Internet-TV applications can access it. can do.
  • System disk space allows addresses to be mapped backwards from the maximum capacity of the physical address on the local disk, improving disk access performance due to partitioning of the system disk that occurs when a user uses multiple services.
  • 26 is an interface illustrating a disk use management screen provided to a user according to an embodiment of the present invention.
  • the screen of FIG. 26 is a screen that a service provider may provide to a user through a screen of a CE device when the user subscribes to a specific service.
  • the current disk usage is represented by a graph, and the screen is composed of information obtained from a tracker or a portal.
  • the information on the screen may be transmitted in the form of HTML through the HTTP protocol.
  • the user may be provided with the list of service providers, the number of connected peers, the number of available contents, the required disk capacity, and whether to subscribe.
  • FIG. 27 is a diagram illustrating an IPTV receiver according to an embodiment of the present invention.
  • FIG. 27 is a diagram illustrating an IPTV receiver according to an embodiment of the present invention.
  • the IPTV receiver of FIG. 27 includes a front end 27010, a network transport 27020, a service access 27030, a storage (Volatile / Non-Volatile Storage System) 27040, and a PS.
  • I decoder Program System Information Decoder; 27050
  • Authentication DRM / CP / CAS; 27060
  • DVR Engine DVR Engine; 27070
  • DBMS / File System Embedded DBMS / Firesystem; 27080
  • System Control Hybrid / OITF / HNED Subsystem 27090 and an application unit (0TIF / HNED Applications) 27100.
  • the front end 2710 includes an RF interface for receiving a digitized radio frequency (RF) signal and a network interface for transmitting and receiving an IP (Internet Protocol) packet.
  • RF radio frequency
  • IP Internet Protocol
  • the network transmitter 2720 delivers IP packets, TCP / IP managers that classify IP packets with appropriate Internet protocol managers, adjust bandwidths according to services, and adjust the quality of IPTV services.
  • QoS & Bandwidth Control QoS & Bandwidth Control
  • Service Protection Control Service Protection Control
  • the bandwidth may be controlled by an IPTV application or a service provider, and in particular, may block the connection of another peer or another system.
  • the service access unit 2730 may perform discovery of IP services through a two-way IP network and provide service for selecting a service, and manage XML data and store them in a file system.
  • a service / session control unit that selects or controls communication sessions and services such as live broadcast services using the Metadata Manager, I Internet Group Management Protocol (GMP), or Real-Time Transport Control Protocol (RTCP) protocols.
  • GMP I Internet Group Management Protocol
  • RTCP Real-Time Transport Control Protocol
  • Service and Session Management includes a service delivery unit for receiving content from a content server and processing real-time streaming data.
  • the service delivery unit may retrieve and receive content selected by a user from another peer or an IPTV receiver.
  • the storage unit 2704 includes a content database for storing content received through the content download system and a metadata / SI database for storing service discovery information and metadata related to the service. do.
  • the PSI decoder 2550 sets a PID for system information (SI) or program system information (PSI) in the demultiplexer to decode the extracted system information and program system information.
  • SI system information
  • PSI program system information
  • the decoded system information and program information may include SD & S information and 0ICD discovery information included therein.
  • the authentication unit 2760 stores a license or a key for the content, and performs content authentication through decoding or descrambling on the encrypted content according to a use right.
  • DVR engine 27070 live streaming controller. Performs recording and playback of 3/4]. It may also collect metadata about the recorded content that may be provided to the user.
  • the DBMS / file system unit 27080 manages data such as electronic program schedule data and XML data.
  • the system controller 2690 includes a system decoder for decoding MPEG-2 TS packets and an IP packet, a demultiplexer (DEMUX) for demultiplexing received signals and packets under control of a PSI decoder, and a video.
  • a video decoder (Video Decoder) for decoding an element
  • an audio decoder (Audio Decoder) for decoding an audio element.
  • the system control unit 2690 includes an IEEE1394 support unit (IEEE1394), an encryption / decryption unit, and an IEEE1394 interface unit.
  • Display protection to prevent content copying through scramble / descramble, USB Host with USB interface, caption and UI display, control 0SD and 2D graphic data, render 3D data 2D / 3D Graphic Processor, Video Display Processor to control and process video and still or video, and RS-232 support with RS-232 interface to PC compatible systems (RS—232), HDMI output and HDMI / HDCP support (HDMI / HDCP) to support HDCP content protection, I / O control unit to control I / O data flow by filtering packets or blocking streams inside the device (External 1/0) IR receiver for receiving input signals from user input devices such as remote controllers and analyzing and demodulating the received signals. nfrared) Receiver).
  • HDMI output and HDMI / HDCP support HDMI / HDCP support
  • I / O control unit to control I / O data flow by filtering packets or blocking streams inside the device (External 1/0) IR receiver for receiving input signals from user input devices such as remote controllers and
  • the application unit 27100 controls the TV system and the EPG / BCG display unit (EPG / BCG) that collects XML data and content information and displays an EPG (Eletronic Program Guide) or BCG (Broadband Content Guide). And a user interface (UI Application) for controlling the UI and receiving user input through a user input means or a display panel.
  • the application unit 27100 transmits downloadable content to a P2P via an Internet connection.
  • 0ICD Application Remote Management Client
  • ITF Internet Terminal Function
  • P2P Remote Scheduler retrieve the latest firmware and software, and provide it to the user to perform a firmware upgrade to upgrade the firmware portion
  • the device may further include an event handler configured to manage received messages and events, and determine messages and events to be transmitted, and an embedded web browser that renders open internet content to a screen.
  • 28 is a flowchart illustrating a firmware upgrade method of a CE device according to an embodiment of the present invention.
  • FIG. 28 As an embodiment of the CE device as described above, an IPTV receiver as shown in Fig. 27 will be described as an example.
  • the IPTV receiver accesses and provisions the IP network using the service access unit (S28010). Performing such IP network connection and provisioning of the IPTV receiver may be performed as described above with respect to FIGS. 4 and 4.
  • the IPTV receiver may receive the SD & S information through the provisioning, as described above.
  • the IPTV receiver may receive firmware update announcement information through a network interface in operation S28020.
  • the firmware update announcement information may be received in a multicast channel or a unicast channel.
  • the firmware update announcement information may be received as FUSS information via SD & S information.
  • the IPTV receiver may drive the P2P application in the application unit and access the P2P network through the service access unit to receive firmware update announcement information in unicast.
  • the firmware update announcement information includes information on a device to be upgraded with firmware (manufacturer identification information (CE manufacturer 0UI, etc.), device model information, etc.), and firmware.
  • firmware manufactured by manufacturer 0UI, etc.
  • Software information, including information about the software, and resource information about the resource for downloading the firmware may be included.
  • the resource information may include a server address of a service provider providing a firmware or a server address of a CE manufacturer, and may include address information of a P2P tracker when providing firmware to a P2P network.
  • the IPTV receiver may parse the firmware upgrade announcement information through the firmware upgrade unit to obtain P2P tracker address information of the P2P network (S28030).
  • the IPTV receiver may download the firmware to the P2P network through the service access unit and the network interface by using the P2P tracker address information obtained from the firmware upgrade unit (S28040).
  • the IPTV receiver receives metadata about the advertised firmware from the P2P tracker by connecting to the P2P tracker, and uses this metadata to connect to the peer that has the firmware to download. You can download the firmware.
  • the metadata about the firmware may include device information that is the target of firmware, location information of a peer having firmware, and list information including peers having firmware and their locations.
  • the IPTV receiver may determine whether to download the firmware from metadata about the firmware and perform the download.
  • the P2P network connection and data transmission and reception of the IPTV receiver may be performed through a service access unit or an application unit.
  • the IPTV receiver may transmit device information of the IPTV receiver while connecting to the P2P tracker.
  • the P2P tracker may determine whether the IPTV receiver needs to download the firmware from the received device information and transmit firmware metadata corresponding to the IPTV receiver.
  • the device information sent by the IPTV receiver is
  • the device may include at least one of device manufacturer identification information (0UI, etc.), hardware model information of the device, software information of the device, and software version information.
  • the firmware upgrade method of the IPTV receiver described in FIG. 28 may be performed as described above with reference to FIGS. 13 to 22 in a system such as FIGS. 6 to 10. That is, the description of FIG. 28 is one embodiment, and each step of the embodiment can be performed according to the above descriptions, and it should be understood organically.
  • Method invention according to the present invention are all implemented in the form of program instructions that can be executed by various computer means can be recorded on a computer readable medium.
  • the computer readable medium may include program instructions, data files, and data structures alone or in combination. Program instructions recorded on the media may be those specially designed and constructed for the purposes of the present invention, or they may be of the kind well-known and available to those having skill in the computer software arts.
  • Examples of the computer readable recording medium such as an optical recording medium (optical media), flop tikeol disk (floptical 'disk) such as a magnetic medium (magnetic media), CD-ROM, DVD, such as hard disks, floppy disks, and magnetic tape Magneto-opt ical media, and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like.
  • Examples of program instructions include machine code, such as produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter or the like.
  • An alternative hardware device may be configured to operate as one or more software modules to perform the operations of the present invention, and vice versa.
  • the present invention may be applied in whole or in part to a digital broadcasting system or an IPTV broadcasting system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Information Transfer Between Computers (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention se rapporte à un procédé et à un appareil permettant de contrôler et de mettre à niveau un micrologiciel à distance dans un environnement en réseau IP. Le procédé pour la mise à niveau d'un micrologiciel d'un récepteur de TV sur IP selon l'un des modes de réalisation de la présente invention consiste : à réaliser la connexion à un réseau IP dans le but d'exécuter une opération de mise à disposition ; à recevoir des informations d'annonce de mise à jour de micrologiciel ; à acquérir des informations d'adresse de traceur P2P d'un réseau P2P sur la base des informations d'annonce de mise à jour de micrologiciel ; et à télécharger le micrologiciel sur le réseau P2P en utilisant les informations d'adresse de traceur P2P. D'autre part, le récepteur de TV sur IP selon l'un des modes de réalisation de la présente invention comprend : un module d'accès au service pour réaliser la connexion à un réseau IP dans le but d'exécuter une opération de mise à disposition ; un module d'interface réseau pour recevoir des informations d'annonce de mise à jour de micrologiciel ; et un module de mise à niveau de micrologiciel pour acquérir des informations d'adresse de traceur P2P d'un réseau P2P sur la base des informations d'annonce de mise à jour de micrologiciel. Selon l'invention, le module de mise à niveau de micrologiciel télécharge le micrologiciel sur le réseau P2P en utilisant les informations d'adresse de traceur P2P.
PCT/KR2010/004478 2009-07-10 2010-07-09 Procédé et appareil permettant de contrôler et de mettre à niveau un micrologiciel à distance WO2011005051A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US22447609P 2009-07-10 2009-07-10
US61/224,476 2009-07-10

Publications (2)

Publication Number Publication Date
WO2011005051A2 true WO2011005051A2 (fr) 2011-01-13
WO2011005051A3 WO2011005051A3 (fr) 2011-04-07

Family

ID=43429692

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2010/004478 WO2011005051A2 (fr) 2009-07-10 2010-07-09 Procédé et appareil permettant de contrôler et de mettre à niveau un micrologiciel à distance

Country Status (1)

Country Link
WO (1) WO2011005051A2 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20170121911A (ko) * 2016-04-26 2017-11-03 삼성에스디에스 주식회사 P2P를 이용한 IoT 기기의 펌웨어 업데이트 방법 및 그 장치
CN107885507A (zh) * 2016-09-29 2018-04-06 上海华测导航技术股份有限公司 一种提高接收机固件升级效率的方法
US10728523B1 (en) 2017-02-13 2020-07-28 Valmont Industries, Inc. System and method for use of 3D visual sensors on mechanized irrigation machinery
CN112118313A (zh) * 2020-09-17 2020-12-22 紫光展锐(重庆)科技有限公司 一种终端设备远程升级的方法及相关装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080022012A1 (en) * 2006-07-20 2008-01-24 Matrix Xin Wang Peer-to-peer file download system for IPTV network
KR20080071818A (ko) * 2007-01-31 2008-08-05 주식회사 케이티 Ｐ2ｐ 기반의 화상통화 서비스 제공 시스템, 제공 방법, 통신 방법 및, 이를 기록한 기록매체
US20090049491A1 (en) * 2007-08-16 2009-02-19 Nokia Corporation Resolution Video File Retrieval

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080022012A1 (en) * 2006-07-20 2008-01-24 Matrix Xin Wang Peer-to-peer file download system for IPTV network
KR20080071818A (ko) * 2007-01-31 2008-08-05 주식회사 케이티 Ｐ2ｐ 기반의 화상통화 서비스 제공 시스템, 제공 방법, 통신 방법 및, 이를 기록한 기록매체
US20090049491A1 (en) * 2007-08-16 2009-02-19 Nokia Corporation Resolution Video File Retrieval

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20170121911A (ko) * 2016-04-26 2017-11-03 삼성에스디에스 주식회사 P2P를 이용한 IoT 기기의 펌웨어 업데이트 방법 및 그 장치
KR102423084B1 (ko) * 2016-04-26 2022-07-19 삼성에스디에스 주식회사 P2P를 이용한 IoT 기기의 펌웨어 업데이트 방법 및 그 장치
CN107885507A (zh) * 2016-09-29 2018-04-06 上海华测导航技术股份有限公司 一种提高接收机固件升级效率的方法
US10728523B1 (en) 2017-02-13 2020-07-28 Valmont Industries, Inc. System and method for use of 3D visual sensors on mechanized irrigation machinery
CN112118313A (zh) * 2020-09-17 2020-12-22 紫光展锐(重庆)科技有限公司 一种终端设备远程升级的方法及相关装置
CN112118313B (zh) * 2020-09-17 2023-04-18 紫光展锐(重庆)科技有限公司 一种终端设备远程升级的方法及相关装置

Also Published As

Publication number Publication date
WO2011005051A3 (fr) 2011-04-07

Similar Documents

Publication Publication Date Title
CN101479988B (zh) 多dvr节点通信
KR101817339B1 (ko) 네트워크로 연결된 방송 수신 디바이스와 다른 디바이스 간 연결을 관리하는 방법 및 장치
US8843599B2 (en) Storing and synchronizing media device information
KR100782854B1 (ko) 원격 사용자 인터페이스를 이용한 콘텐트 관리 방법 및장치
US20090235319A1 (en) Video on Demand Gateway
US10554745B2 (en) Method and apparatus for managing connection between broadcasting reception device and another device which are connected through network
US8601115B2 (en) Providing state information and remote command execution in a managed media device
WO2006017218A2 (fr) Service de syntoniseur et recepteur dtv en tant que dispositif upnp
EP2658210B1 (fr) Dispositif de transfert de contenu et procédé de transfert de contenu
US20110296460A1 (en) Method and apparatus for providing remote user interface (ui) service
WO2018034172A1 (fr) Dispositif de traitement d'informations, dispositif client et procédé de traitement de données
US9380104B2 (en) Media player web service
WO2011005051A2 (fr) Procédé et appareil permettant de contrôler et de mettre à niveau un micrologiciel à distance
CA3038028A1 (fr) Dispositif de reception, dispositif de transmission, et procede de traitement de donnees
EP2413600A2 (fr) Récepteur iptv et procédé de téléchargement de contenu associé
CN104303517A (zh) 信息处理设备、信息处理方法和程序
US20140012955A1 (en) Communication System, Communication Device, And Communication Method
WO2015072764A1 (fr) Procédé et appareil de gestion de connexion entre une pluralité de dispositifs sur un réseau
Heredia An introduction to the DLNA architecture: network technologies for media devices
CN105917659A (zh) 服务提供商网络中的节目记录的混合存储
EP2484089A1 (fr) Surveillance d'un reseau upnp

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10797325

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10797325

Country of ref document: EP

Kind code of ref document: A2