EP1761848A2 - Procede et appareil pour telecharger une pluralite d'images - Google Patents

Procede et appareil pour telecharger une pluralite d'images

Info

Publication number
EP1761848A2
EP1761848A2 EP05769612A EP05769612A EP1761848A2 EP 1761848 A2 EP1761848 A2 EP 1761848A2 EP 05769612 A EP05769612 A EP 05769612A EP 05769612 A EP05769612 A EP 05769612A EP 1761848 A2 EP1761848 A2 EP 1761848A2
Authority
EP
European Patent Office
Prior art keywords
target
image
identifier
download file
intelligent device
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP05769612A
Other languages
German (de)
English (en)
Inventor
Derek Douglas Dickinson
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Solutions and Networks GmbH and Co KG
Original Assignee
Siemens AG
Nokia Siemens Networks GmbH and Co KG
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 Siemens AG, Nokia Siemens Networks GmbH and Co KG filed Critical Siemens AG
Publication of EP1761848A2 publication Critical patent/EP1761848A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation

Definitions

  • the present invention relates to a method and apparatus for downloading software on a plurality of network devices in a communications network, and more particularly, to a method and apparatus for downloading a plurality of images to a plurality of intelligent network devices.
  • a typical communications network includes numerous devices each having software to perform communications functionalities.
  • a Passive Optical Network would typically have a plurality of Optical Network Units (ONUs).
  • An ONU that is capable of providing service to a plurality of subscribers is called a Multiple Distribution Unit (MDU) whereas an ONTJ that may only supply service to a single subscriber is called a Single Family Unit (SFU).
  • MDU Multiple Distribution Unit
  • SFU Single Family Unit
  • the software that executes on the MDU may differ from the software on the SFU since they have a different functionality, e.g. supplying service to one versus multiple subscribers.
  • the ONUs may have different core processors than other ONTJs in which case the ONUs may require different versions of the software, where each version is a different image of the software.
  • a NIOS processor from Altera Corporation and a PowerPC ® processor from IBM might require different images of the software.
  • the coprocessors may be different such that different images of the ⁇ software may be desirable.
  • Wintegra Incorporated and Broadcom Corporation communications processors both use a MIPS core processor but may have different coprocessors.
  • a software upgrade may be for a new release of the product having different and/or improved functionality and in some cases the upgrade provides fixes to the current software.
  • a management system may upgrade the software by downloading the image to the device; however, the management of which device gets which image is typically a manual process. Therefore, there exists a need to provide an improved way to download images to devices for software upgrades.
  • a download file for use in a communications network comprising a plurality of target blocks, each target block including an image to be downloaded to an intelligent device, a target identifier indicating an intelligent device that may use the image, and a qualifier that qualifies how the image is to be downloaded, and an end indicator indicating the end of the download file.
  • a method for downloading an image to an intelligent device in a broadband communications network comprising receiving a download file by intelligent device, the download file having a signature, a plurality of target blocks, and an end indicator, and validating the signature in the download file by the intelligent device, if the signature is valid determining a target block that has an image compatible with the intelligent device by comparing a target identifier in the target block with a device identifier in the intelligent device, copying the compatible image from the target block to the intelligent device, if the signature is invalid disregarding the download file.
  • Figure 1 illustrates an exemplary prior art schematic diagram of a communications network having a plurality of download files communicated to a plurality of devices
  • Figure 2 illustrates an embodiment of an exemplary schematic diagram of the present invention having a download file communicated to a plurality of devices
  • Figure 3 illustrates an exemplary download file layout in accordance with the present invention.
  • the invention described herein may employ one or more of the following concepts.
  • one concept relates a download file having a plurality of images to a plurality of intelligent devices.
  • Another concept relates to a modified management system to send a download file having a plurality of images.
  • Yet another concept relates to an intelligent device to determine which image(s) to use from a plurality of images in a download file.
  • the present invention is disclosed in context of use of a Passive Optical Network (PON) having a plurality of Optical Network Units (ONTJs) managed by a management system.
  • PON Passive Optical Network
  • ONTJs Optical Network Units
  • the principles of the present invention are not limited to use within a PON but may be applied to networks having high speed, such as broadband networks, as well as networks having lower bandwidth.
  • the present invention may be used in Internet, Digital Subscriber Line (DSL), cable, wireless, and optical networks.
  • DSL Digital Subscriber Line
  • the present invention is disclosed having a plurality of ONUs any device having software that may be accessed via the management system, such as a DSL modem may be used.
  • Embedded processors for embedded systems are applicable to the exemplary context of use.
  • any presently available or future developed processor may be used with the present invention with the exemplary or other contexts of use.
  • One skilled in the art may find additional application for the apparatus, processes, systems, components, configurations, methods and applications disclosed herein.
  • the illustration and description of the present invention disclosed in context of use of a PON having a plurality of ONUs managed by management system is merely one possible application of the present invention.
  • the present invention has particular applicability for use in a PON having a plurality of ONUs managed by management system.
  • a communications network 10 includes a management system 12 that communicates download files toward a plurality of devices 20 via a network 14.
  • Each download file having an "image" of a software executable file, a text file, a script file, picture file or any other file or data to be copied to the device 20.
  • each of the devices 20 is an ONU.
  • the device 20(1) includes a Wintegra Incorporated communications processor type from a MIPS core processor family and is a Single Family Unit (SFU) target type.
  • Device 20(2) includes a Broadcom Corporation communications processor type from a MIPS core processor family, and is a Multiple Distribution Unit (MDU) target type.
  • Device 20(3) has a processor from a PowerPC core processor family and is a SFU target type.
  • Device 20(4) includes a MPC8260 core variation from the PowerPC core processor family and is a MDU target type.
  • Device 20(5) includes a MPC860 core variation from the PowerPC core processor family and is a MDU target type.
  • a first download file having a first image is directed to 16(al), 16(bl) the device 20(1) via the PON.
  • a second download file having a second image is directed to 16(a2), 16(b2) the device 20(2) via the PON.
  • a third download file having a third image is directed to 16(a3), 16(b3) the device 20(3) via the PON.
  • a forth image ⁇ Ft may be used for the MPC8260 and MPC860 variations of the PowerPC core Processor and therefore may be used for devices 20(4), 20(5).
  • a fourth download file having the fourth image therefore may be used for devices 20(4), 20(5).
  • the fourth image is sent separately 16(a4), 16(b4), 16(a5), 16(b5), in this case twice, once to each of the two devices.
  • the communications network 10 includes a management system 12 communicating a download file having a plurality of images toward a plurality of intelligent devices 22 having download intelligent via a network 14.
  • Exemplary intelligent device 22(1) includes a Wintegra Incorporated communications processor type from the MIPS core processor family and is a SFU target type.
  • Exemplary intelligent device 22(2) includes a Broadcom Corporation communications processor type from a MIPS core processor family, and is a MDU target type.
  • Exemplary intelligent device 22(3) has a processor from a PowerPC core processor family and is a SFU target type.
  • Exemplary intelligent device 22(4) includes a MPC8260 core variation from the PowerPC core processor family and is a MDU target type.
  • Exemplary intelligent device 22(5) includes a MPC860 core variation from the PowerPC core processor family and is a MDU target type.
  • the download file including the first image, the second image, the third, and the fourth images is directed to 18 the intelligent devices 22.
  • the illustrated exemplary embodiment makes use of broadcasting the file to the intelligent devices 22; however, the file may be sent via a unicast method.
  • the intelligent device 22 compares data in the file to information within the intelligent device 22 to intelligently determine if one or more images are compatible with the intelligent device 22.
  • Each compatible image is copied to the intelligent device 22 whereas a non-compatible image is ignored.
  • intelligent device 22(1) determines the first image is compatible
  • intelligent device 22(2) determines the second image is compatible
  • intelligent device 22(3) determines the third image is compatible
  • intelligent devices 22(4), 22(5) both determine the fourth image is compatible.
  • the compatible image is copied to the intelligent device 22.
  • more than one image may be compatible such as is described in further detail below.
  • the download file 30 includes information to allow the intelligent device 22 to intelligently determine which image is compatible with the intelligent device 22.
  • the download file 30 includes a signature 32, an end 36 and a plurality of target blocks 34.
  • the signature 32 is an expected data, such as a string, that the intelligent device 22 can look at to determine if the download file 30 is valid. If the file 30 is invalid, the intelligent device 22 disregards the file 30; otherwise, it processes the file 30 to determine a compatible image. Disregard may include for example, not processing the rest of the download file 30 or not storing the download file 30 or combinations or portions thereof. It would be appreciated by those skilled in the art that the download file 30 may not include the signature 32 in which case the intelligent device 22 would process the file 30 to determine a compatible image.
  • the end indicates the end of the download file 30.
  • Each target block 34 includes a target identifier, one or more qualifiers, and one or more images.
  • the target identifier describes which intelligent devices 20 may use the image(s).
  • the target identifier may include one or more target elements, such as a family identifier, a core variation, a type, a function type, a version, combinations thereof, and the like.
  • the family identifier indicates which core processor family may use the image, e.g. NIOS, MIPS, PowerPC, or Intelx86.
  • the core variation is based on the iamily identifier and indicates the variation of the core processor that is valid for the image. For example, when the femily identifier is PowerPC, the core variation might indicate MPC860 or MPC8260.
  • the type is also based on the family identifier and indicates a type of communication s processor.
  • the type when the femily identifier is a MIPS, the type may be Wintegra Incorporated or Broadcom Corporation.
  • the function type describes target functionality of the intelligent device 22, such as,.for an ONU the target may be a SFU or a MDU.
  • the version indicates a version of the image.
  • different target elements maybe used. For example, if all the intelligent devices 22 within a network 14 have the same functionality the function type target element may be omitted. Likewise, depending on the context of use, one skilled in the art would recognize that additional target elements might be used.
  • the target identifier may be formatted in any suitable way, such as a bit field, ordinal, or combinations thereof, to provide the target elements for describing which intelligent devices 22 may use the image. Additionally, the target identifier may be formatted as part of a header wherein the header has a header identifier and may include a header length and a next header field. The target identifier may have different formats based on the header identifier for example a target identifier may be formatted in a bit field for one header identifier and another target identifier may be formatted as an ordinal in a different header identifier.
  • the header length provides the length of the header and the next header field provides information to access a next header.
  • the target identifier may indicate that the image is compatible to more than intelligent device 22.
  • the fourth image is compatible for intelligent device 22(4) and intelligent device 22(5).
  • the target identifier can indicate that the family identifier is the PowerPC and that the core variation indicates both MPC8260 and MPC860 in which case any images for the target identifier would be copied to the intelligent devices 22(4), 22(5).
  • the core variation indicates both MPC8260 and MPC860 in which case any images for the target identifier would be copied to the intelligent devices 22(4), 22(5).
  • Those skilled in the art would appreciate that other combinations could also be made, such as, an image might be compatible with both an SFU and MDU target.
  • a qualifier advantageously provides information for downloading the image and/or updating memory in the intelligent device 22 for a specific target identifier.
  • the qualifier may be an image type, an address, a compression identifier, a size, a start address, a filler, combinations thereof, and the like.
  • the image type indicates the type of image such as boot or operational to allow different operations based on the type of image.
  • the address provides a device address to where the image is to be written.
  • the compression identifier identifies if the image is in a compressed format. When the image is in a compressed format it may be uncompressed before writing to the address. This is preferable for a boot image since image should be in an executable form upon rebooting.
  • the file may be written in the compressed format, for example when writing an operation image it may be desirable to keep the image compressed to save memory, such as a flash memory, within the intelligent device 22.
  • the size may indicate the size of the compressed and/or uncompressed image.
  • a start address indicates an address to start execution of the image.
  • the filler qualifier includes a value, fill size and fill address fields. The fill qualifier allows certain areas of memory, including a disk memory, to be written to using the value. The area of memory is specified by the fill address. The fill size determines how much memory to fill with the fill value.
  • a target block 32 having a boot image may include the image type, the address, and the start address.
  • the image type might not be needed when the intelligent device 22 doesn't specifically need to know the image type but simply uses the other qualifiers. Additional qualifiers may be used without departing from the present invention.
  • the qualifier may be formatted in any suitable way, such as a bit field, or ordinal to provide the qualifying information about a target identifier. Additionally, the qualifier may be formatted as part of a header wherein the header has a header identifier and may include a header length and a next header field. Similarly to the target identifier, the qualifier may have different formats based on the header identifier. The header length provides the length of the header and the next header field provides information to access a next header.
  • the intelligent device 22 determines the signature to be valid, the intelligent device 22 checks each target block 34 to determine a compatible image.
  • the intelligent device 22 includes one or more device identifiers having information corresponding to the target identifiers.
  • the device identifier may include one or more target elements, such as a device family identifier, a device core variation, a device type, a device target, a device version, combinations thereof, and the like.
  • the device family identifier indicates the core processor family used by the device.
  • the device core variation is based on the device family identifier and indicates the variation of the core processor used by the device.
  • the device type is also based on the family identifier and indicates a type of communication s processor used by the device.
  • the device version indicates a version of the image used by the device
  • the device identifier may be formatted in any suitable way, such as a bit field or ordinal, to provide the identifiers for describing what is used by the device.
  • the qualifiers are used to download the image. Once the image is downloaded, the address provided in the start address may be used if the device is restarted.
  • the download file 30 be organized such that the target blocks 34 having more specific target identifiers would precede the target blocks 34 having more generic target identifiers. If. for example, a first target block had target identifiers indicating an image compatible with a MPC8260 core variation of PowerPC core processor family and a second target block had a target identifiers indicating image compatible with a MPC8260 or a MPC860 core variations of PowerPC core processor family. The first target block has more specific target identifiers since it only matches with one type of core variation.
  • target blocks 34 are organized from more specific to more general format the device could discard the remainder of the file 30 once a target block is identified as compatible. It would be appreciated by those skilled in the art that a target black 34 may not be identified as having a compatible image for the intelligent device 22 in which case an image is not downloaded.
  • download file 30 may be used in a broadband network having a higher bandwidth such as a PON 3 DSL, wireless, or cable networks.
  • the invention may be embodied in many different forms and may be applied to many different types of networks, protocols, and protocol versions and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Thus, the scope of the invention should be determined based upon the appended claims and their legal equivalents, rather than the specific embodiments described above.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Un fichier de téléchargement (30) à utiliser dans un réseau de communications comportant une pluralité de blocs cibles (32), une fin (36) et une signature (32). Chaque bloc cible (32) incluant une image à télécharger vers un dispositif intelligent (22), un identifiant cible indiquant un dispositif intelligent (22) qui peut utiliser l'image, et un qualifiant qui qualifie la façon dont l'image doit être téléchargée. La fin (36) indiquant la fin du fichier de téléchargement. La signature (32) utilisée pour valider le fichier de téléchargement (30) auprès du dispositif intelligent (22).
EP05769612A 2004-06-30 2005-06-30 Procede et appareil pour telecharger une pluralite d'images Withdrawn EP1761848A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US58435604P 2004-06-30 2004-06-30
PCT/EP2005/053109 WO2006003177A2 (fr) 2004-06-30 2005-06-30 Procede et appareil pour telecharger une pluralite d'images

Publications (1)

Publication Number Publication Date
EP1761848A2 true EP1761848A2 (fr) 2007-03-14

Family

ID=35783214

Family Applications (1)

Application Number Title Priority Date Filing Date
EP05769612A Withdrawn EP1761848A2 (fr) 2004-06-30 2005-06-30 Procede et appareil pour telecharger une pluralite d'images

Country Status (3)

Country Link
EP (1) EP1761848A2 (fr)
CN (1) CN101002172A (fr)
WO (1) WO2006003177A2 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101102546B (zh) * 2007-07-24 2010-12-08 中兴通讯股份有限公司 一种结束移动多媒体数据广播组文件下载的方法
CN112000346B (zh) * 2020-07-22 2023-12-29 西安广和通无线软件有限公司 文件升级方法、装置、计算机设备和存储介质

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5742829A (en) * 1995-03-10 1998-04-21 Microsoft Corporation Automatic software installation on heterogeneous networked client computer systems
US5951639A (en) * 1996-02-14 1999-09-14 Powertv, Inc. Multicast downloading of software and data modules and their compatibility requirements
US6263497B1 (en) * 1997-07-31 2001-07-17 Matsushita Electric Industrial Co., Ltd. Remote maintenance method and remote maintenance apparatus
FI990461A0 (fi) * 1999-03-03 1999-03-03 Nokia Mobile Phones Ltd Menetelmä ohjelmiston lataamiseksi palvelimelta päätelaitteeseen
GB2384066A (en) * 2002-01-09 2003-07-16 Hewlett Packard Co Installation of software components having multiple implementations
WO2004031949A2 (fr) * 2002-10-07 2004-04-15 Koninklijke Philips Electronics N.V. Diffusion de progiciels

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2006003177A3 *

Also Published As

Publication number Publication date
WO2006003177A3 (fr) 2006-09-14
WO2006003177A2 (fr) 2006-01-12
CN101002172A (zh) 2007-07-18

Similar Documents

Publication Publication Date Title
US8074212B2 (en) Method and apparatus for software upgrade in a digital television receiving device
US7313791B1 (en) Firmware update network and process employing preprocessing techniques
US7940407B2 (en) Image forming apparatus, terminal apparatus and management apparatus
AU2004279173B2 (en) System and method for updating files utilizing delta compression patching
US7747997B1 (en) Firmware update in electronic devices employing SIM card for saving metadata information
CN1187984C (zh) 用于下载和管理编码对象列表的执行的方法和系统
AU2004279202B2 (en) System and method for updating installation components in a networked environment
AU2004279162B8 (en) System and method for a software distribution service
KR101098745B1 (ko) 소프트웨어 업데이트를 관리하고 통신하기 위한 시스템 및방법
CN101110788B (zh) 升级客户端软件的方法及系统
US6493871B1 (en) Method and system for downloading updates for software installation
US7676448B2 (en) Controlling installation update behaviors on a client computer
US20060080650A1 (en) Method and system for reducing storage requirements for program code in a communication device
EP1775913B1 (fr) Procédé de controle d'un appareil multimédia middleware controle par métadonnées
US20090222810A1 (en) Preventing Overwrite Of Nonessential Code During Essential Code Update
US9319418B2 (en) Method and apparatus for software downloads in a network
WO2007081163A1 (fr) Procede et appareil de gestion de securite dans un intergiciel multimedia, et support de stockage associe
WO2006003177A2 (fr) Procede et appareil pour telecharger une pluralite d'images
CN101924958B (zh) 以太无源光网络的光网络单元的更新方法及其装置
KR100582437B1 (ko) 네트워크 장치에 대한 정확한 운용 소프트웨어 버전을 결정하기 위한 장치 및 방법

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20061227

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL BA HR LV MK YU

RAP1 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG

DAX Request for extension of the european patent (deleted)
RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS S.P.A.

RAP3 Party data changed (applicant data changed or rights of an application transferred)

Owner name: NOKIA SIEMENS NETWORKS GMBH & CO. KG

17Q First examination report despatched

Effective date: 20080403

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20080814