US20010042113A1 - Method of distributing data packets of system software - Google Patents
Method of distributing data packets of system software Download PDFInfo
- Publication number
- US20010042113A1 US20010042113A1 US09/159,155 US15915598A US2001042113A1 US 20010042113 A1 US20010042113 A1 US 20010042113A1 US 15915598 A US15915598 A US 15915598A US 2001042113 A1 US2001042113 A1 US 2001042113A1
- Authority
- US
- United States
- Prior art keywords
- server
- system software
- dec
- transmitted
- data packets
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Definitions
- This invention relates to a method of distributing data packets of system software as set forth in the preamble of claim 1 .
- a server is provided as a send unit, and the receive units are decoders.
- the decoders are designed as set-top boxes.
- the system software of the set-top boxes needs to be updated when a new version of the system software is available.
- this procedure always requires an action by the receive unit together with a request to the server. If a plurality of receive units are present, each receive unit must request the new version by itself. Because of the structure of the distribution system, the new version, which is generally identical for all receive units, is transmitted from the send unit to the receive units separately. If there are 500 receive units, the send unit must transmit the new version 500 times, once to each receive unit. This takes a certain time. Thus, the transmission of further information is unnecessarily blocked, at least in a predetermined frequency range, for a certain period of time.
- this object is attained by a method as set forth in claim 1 .
- the method is characterized in that by advance information in the form of an announce signal which is transmitted to all receive units by the broadcast method, the receive units are notified of the forthcoming transmission of the current version of the system software, whereupon they can prepare for the reception of the new version.
- the new version is also transmitted by the broadcast method, and ideally only once. If individual receive units should not have received the advance information, the method may, for example, be automatically repeated at a later time or the remaining receive units may request the new version from the server separately.
- the transmission time is ideally shortened by a factor corresponding to the number of receive units present, i.e., by a factor 500 if there are 500 receive units. If, for example, 10% of the receive units should not have received the advance information, the transmission time is still shortened by a factor of 250 (in case of automatic repetition) or approximately 100 (if separate requests are made).
- the point-to-multipoint SYS comprises a send unit SERVER, a network NET, and a plurality of receive units DEC.
- the point-to-multipoint system SYS is designed, for example, as a service-on-demand system.
- the send unit SERVER contains a server which is connected via the network NET to the receive units DEC, which are designed as decoders.
- the point-to-multipoint system SYS makes available a downstream channel and an upstream channel. Via the upstream channel, e.g., a narrow-band channel, customers can transmit information from their decoders through the network NET to the server.
- the information consists, for example, of request signals by means of which a video film, for example, is requested, which is then broadcast over the downstream channel, e.g., a broadband channel, to all decoders or to a group of decoders in a subarea dependent on the topology of the network.
- a logon authorization granted, for example, by issuing a key for each transmission, ensures that only the decoder from which the video film was requested has the right and capability to receive the transmitted video film.
- the decoders are designed, for example, as set-top boxes.
- Each set-top box has system software, i.e., programs that make up the operating system.
- the system software serves, for example, to receive and process the menu broadcast by the server for the selection of video films and the like. From time to time, the system software is upgraded and updated, or modified to eliminate systematic errors.
- Each set-top box then needs an update of its system software.
- a new version of the system software needs to be transferred to the set-top box. This is done by downloading the new version from the server to the set-top boxes.
- the new version or, if possible, only the changes in the new version from the old one are transmitted in the form of data packets from the server to the set-top boxes through the network NET.
- the system software is the same for all set-top boxes, so that ideally, one download will suffice to transmit the necessary data packets of the new version to all set-top boxes.
- the set-top box may go through a initialization phase in which various checks are made and a buffer storage area is enabled to buffer and subsequently load the system software.
- the announce signal is received by all set-top boxes, since instead of an address in the header of a data packet, which serves to select a given set-top box, a so-called default address, e.g., XXXXXXX, is used, which can be received by all set-top boxes.
- the data packets of the new system software are transmitted from the server to all set-top boxes by the broadcast method. This is also done using the default address. All set-top boxes can receive the transmitted data packets. A single transmission of the data packets thus suffices to transfer the new version of the system software to all set-top boxes prepared by the announce signal. Thus, in ideal circumstances, the system software of all set-top boxes is updated by a single transfer of the new system software.
- the announce signal may contain information as to which version of the system software will be transmitted and how much storage capacity is needed. This enables the set-top boxes to determine in advance whether the data packets shortly to be transmitted are to be received or not. If, for example, a set-top box has already received the new version of the system software, e.g., in response to a previous request, via a PCMCIA card, or otherwise, the reception of the new version and the preparation therefor would be unnecessary.
- the information on the storage capacity required enables the set-top box to check whether sufficient storage space is available for receiving the latest version and, if so, to reserve a corresponding area of the new version.
- the receive units DEC i.e., the set-top boxes
- the receive units DEC can buffer the version of this system software, compare it with the version available in the respective set-top box, and, if the two versions are identical, prevent the reception of the data packets transmitted in step 2.
- the receive units DEC i.e., the set-top boxes
- a repetition of the transmission of individual data packets for individual set-top boxes is not provided for, since this would introduce delays. If a set-top box does not receive individual data packets for some reason or other, it must wait for another transfer of a complete version if this is provided for, or request the new version from the server, which will then send a complete version to the respective set-top box separately.
- the acknowledge signals from the set-top boxes contain information for identifying the set-top boxes, e.g., the address of the respective set-top box.
- the server can thus determine which of the set-top boxes have received the transmitted data packets and which have not. To this end, the server stores in a list, for example, the addresses of those set-top boxes which have acknowledged receipt of the data packets. This may be accomplished, for example, by storing the addresses directly in a separate memory area or by providing the respective addresses of the set-top boxes with an identifier if all of them have already been stored in a list. By comparing the received acknowledgements with the number of set-top boxes available, the server can determine to how many set-top boxes the new version has been successfully transmitted.
- a success ratio can be determined, e.g., 80%. Based on this ratio, the server can decide whether or not to repeat the transmission with the preceding announce signal at a later time. Furthermore, the address information can be used to determine whether transmission errors are present in locally limited areas, e.g., if no acknowledgement is received from those set-top boxes which are connected to a subarea dependent on the topology of the network.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
- This invention relates to a method of distributing data packets of system software as set forth in the preamble of
claim 1. - In a point-to-multipoint system, particularly a service-on-demand system, a server is provided as a send unit, and the receive units are decoders. The decoders are designed as set-top boxes. The system software of the set-top boxes needs to be updated when a new version of the system software is available.
- From an article by Carl W. Symborski, “Updating Software And Configuration Data In A Distributed Communications Network”, Proceedings of the Computer Networking Symposium, IEEE Comput. Soc. Press, 1988, pages 331-338, a procedure for distributing data packets of system software in a point-to-multipoint system is known. The procedure is executed in a receive unit and consists of the following steps:
- 1. Wait until a predetermined period of time has expired or a notice has been received that a new version of the system software may be available.
- 2. Request information from the server as to whether a new version is available.
- 3. Compare the version communicated by the server with the version available in the receive unit.
- 4. If no change is detected, return to
step 1. - 5. If a change is detected, request the new version from the server.
- 6. Replace the old version with the new one.
- 7. Store the new version.
- 8. Return to
step 1. - Thus, to obtain the new version of the system software, this procedure always requires an action by the receive unit together with a request to the server. If a plurality of receive units are present, each receive unit must request the new version by itself. Because of the structure of the distribution system, the new version, which is generally identical for all receive units, is transmitted from the send unit to the receive units separately. If there are 500 receive units, the send unit must transmit the new version 500 times, once to each receive unit. This takes a certain time. Thus, the transmission of further information is unnecessarily blocked, at least in a predetermined frequency range, for a certain period of time.
- From an article by K. Rath and J. W. Wendorf, “Set-Top Box Control Software: a Key Component in Digital Video”, Philips Journal of Research (1996), Vol. 50, No. 1/2, pages 185-199, a method of distributing data packets of system software in a point-to-multipoint system is known in which a receive unit designed as a set-top box obtains a new version of the system software telemetrically via a network. The set-top box sends a request to the server or obtains the new version from the server automatically on a periodic basis. The former corresponds essentially to the procedure described above. The latter involves the establishment of a connection between the server and an individual set-top box, which eliminates the need for the set-top box to actively request a new version but does not prevent the multiple transmission of the same information.
- It is therefore an object of the invention to provide a method whereby the system software can be updated in a simple manner.
- According to the invention, this object is attained by a method as set forth in
claim 1. The method is characterized in that by advance information in the form of an announce signal which is transmitted to all receive units by the broadcast method, the receive units are notified of the forthcoming transmission of the current version of the system software, whereupon they can prepare for the reception of the new version. The new version is also transmitted by the broadcast method, and ideally only once. If individual receive units should not have received the advance information, the method may, for example, be automatically repeated at a later time or the remaining receive units may request the new version from the server separately. Thus, compared with the prior art, the transmission time is ideally shortened by a factor corresponding to the number of receive units present, i.e., by a factor 500 if there are 500 receive units. If, for example, 10% of the receive units should not have received the advance information, the transmission time is still shortened by a factor of 250 (in case of automatic repetition) or approximately 100 (if separate requests are made). - Further advantageous features of the invention are defined in the dependent claims.
- The invention will become more apparent from the following description of an embodiment when taken in conjunction with the accompanying drawing. The single figure of the drawing is a schematic representation of a point-to-multipoint system according to the invention for carrying out the method according to the invention.
- The point-to-multipoint SYS comprises a send unit SERVER, a network NET, and a plurality of receive units DEC.
- The point-to-multipoint system SYS is designed, for example, as a service-on-demand system. The send unit SERVER contains a server which is connected via the network NET to the receive units DEC, which are designed as decoders. The point-to-multipoint system SYS makes available a downstream channel and an upstream channel. Via the upstream channel, e.g., a narrow-band channel, customers can transmit information from their decoders through the network NET to the server. The information consists, for example, of request signals by means of which a video film, for example, is requested, which is then broadcast over the downstream channel, e.g., a broadband channel, to all decoders or to a group of decoders in a subarea dependent on the topology of the network. A logon authorization, granted, for example, by issuing a key for each transmission, ensures that only the decoder from which the video film was requested has the right and capability to receive the transmitted video film.
- The decoders are designed, for example, as set-top boxes. Each set-top box has system software, i.e., programs that make up the operating system. The system software serves, for example, to receive and process the menu broadcast by the server for the selection of video films and the like. From time to time, the system software is upgraded and updated, or modified to eliminate systematic errors. Each set-top box then needs an update of its system software. A new version of the system software needs to be transferred to the set-top box. This is done by downloading the new version from the server to the set-top boxes. The new version or, if possible, only the changes in the new version from the old one are transmitted in the form of data packets from the server to the set-top boxes through the network NET. As a rule, the system software is the same for all set-top boxes, so that ideally, one download will suffice to transmit the necessary data packets of the new version to all set-top boxes.
- The method of distributing the data packets of the system software is carried out in the following steps, which are taken one after the other:
- 1. From the send unit SERVER, which contains the server, an announce signal containing the information that the system software of the set-top boxes or part of this software will subsequently be transmitted is sent to all receive units DEC, which contain the set-top boxes, simultaneously.
- 2. From the send unit SERVER, the system software or part thereof is sent in the form of data packets to all receive units DEC simultaneously.
- Thus, by the first step, all set-top boxes connected to the network NET are informed that the new version or the changes from the old version will be transmitted by the server shortly. Each set-top box thus has sufficient time to prepare for the reception of the new software. For example, the set-top box may go through a initialization phase in which various checks are made and a buffer storage area is enabled to buffer and subsequently load the system software. The announce signal is received by all set-top boxes, since instead of an address in the header of a data packet, which serves to select a given set-top box, a so-called default address, e.g., XXXXXXXX, is used, which can be received by all set-top boxes.
- In the second step, the data packets of the new system software are transmitted from the server to all set-top boxes by the broadcast method. This is also done using the default address. All set-top boxes can receive the transmitted data packets. A single transmission of the data packets thus suffices to transfer the new version of the system software to all set-top boxes prepared by the announce signal. Thus, in ideal circumstances, the system software of all set-top boxes is updated by a single transfer of the new system software.
- The announce signal may contain information as to which version of the system software will be transmitted and how much storage capacity is needed. This enables the set-top boxes to determine in advance whether the data packets shortly to be transmitted are to be received or not. If, for example, a set-top box has already received the new version of the system software, e.g., in response to a previous request, via a PCMCIA card, or otherwise, the reception of the new version and the preparation therefor would be unnecessary. The information on the storage capacity required enables the set-top box to check whether sufficient storage space is available for receiving the latest version and, if so, to reserve a corresponding area of the new version.
- Between
1 and 2 of the method for distributing the data packets of the new system software, the receive units DEC, i.e., the set-top boxes, can buffer the version of this system software, compare it with the version available in the respective set-top box, and, if the two versions are identical, prevent the reception of the data packets transmitted insteps step 2. - The receive units DEC, i.e., the set-top boxes, then acknowledge the receipt of the last data packet transmitted by the send unit SERVER and belonging to the system software. This has the advantage that the transmission of the data packets is not interfered with by the acknowledgements from the set-top boxes. A repetition of the transmission of individual data packets for individual set-top boxes is not provided for, since this would introduce delays. If a set-top box does not receive individual data packets for some reason or other, it must wait for another transfer of a complete version if this is provided for, or request the new version from the server, which will then send a complete version to the respective set-top box separately.
- The acknowledge signals from the set-top boxes contain information for identifying the set-top boxes, e.g., the address of the respective set-top box. The server can thus determine which of the set-top boxes have received the transmitted data packets and which have not. To this end, the server stores in a list, for example, the addresses of those set-top boxes which have acknowledged receipt of the data packets. This may be accomplished, for example, by storing the addresses directly in a separate memory area or by providing the respective addresses of the set-top boxes with an identifier if all of them have already been stored in a list. By comparing the received acknowledgements with the number of set-top boxes available, the server can determine to how many set-top boxes the new version has been successfully transmitted. From this, a success ratio can be determined, e.g., 80%. Based on this ratio, the server can decide whether or not to repeat the transmission with the preceding announce signal at a later time. Furthermore, the address information can be used to determine whether transmission errors are present in locally limited areas, e.g., if no acknowledgement is received from those set-top boxes which are connected to a subarea dependent on the topology of the network.
Claims (7)
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| DE19741870 | 1997-09-23 | ||
| DE19741870.8 | 1997-09-23 | ||
| DE19741870A DE19741870A1 (en) | 1997-09-23 | 1997-09-23 | Method for distributing data packets of operating software |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| US20010042113A1 true US20010042113A1 (en) | 2001-11-15 |
| US6836793B1 US6836793B1 (en) | 2004-12-28 |
Family
ID=7843288
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US09/159,155 Expired - Fee Related US6836793B1 (en) | 1997-09-23 | 1998-09-23 | Method of distributing data packets of system software where the receiving units acknowledge only proper reception |
Country Status (8)
| Country | Link |
|---|---|
| US (1) | US6836793B1 (en) |
| EP (1) | EP0903666B1 (en) |
| JP (2) | JPH11163943A (en) |
| CN (1) | CN1186902C (en) |
| AU (1) | AU8422298A (en) |
| CA (1) | CA2245384A1 (en) |
| DE (2) | DE19741870A1 (en) |
| ES (1) | ES2237830T3 (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040174319A1 (en) * | 2003-01-21 | 2004-09-09 | Mitsubishi Denki Kabushiki Kaisha | Information transmission apparatus and information transmission method |
| WO2007050067A1 (en) * | 2005-10-26 | 2007-05-03 | Thomson Licensing | A system and method for advertising the availability of a software upgrade |
| US20070106777A1 (en) * | 2005-11-04 | 2007-05-10 | Internet Initiative Japan Inc. | Automatic functionality generating mechanism for network connecting appliances |
| US20070195770A1 (en) * | 2006-02-20 | 2007-08-23 | Fujitsu Limited | Network controller, receiving terminal device, content delivery system, network control method, and content receiving method |
| US20070288985A1 (en) * | 2006-06-13 | 2007-12-13 | Candelore Brant L | Method and system for uploading content to a target device |
| US20100058403A1 (en) * | 2008-08-29 | 2010-03-04 | Vaidyanathan Ramaswami | Distributing On-Demand Multimedia Content |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20020014799A (en) * | 1999-05-20 | 2002-02-25 | 추후제출 | Broadcast download technique |
| DE10050546B4 (en) * | 2000-10-12 | 2008-07-24 | Rohde & Schwarz Gmbh & Co. Kg | Method of distributing a meter firmware program code to multiple meters |
| KR100456978B1 (en) * | 2001-08-17 | 2004-11-10 | 엘지전자 주식회사 | Method for File Downloading in Agent |
| US20030135575A1 (en) * | 2002-01-14 | 2003-07-17 | Richard Marejka | Self-monitoring and trending service system with cascaded pipeline linking numerous client systems |
| US7376713B2 (en) * | 2002-06-27 | 2008-05-20 | International Business Machines Corporation | Apparatus, system and method of distributing block data on a private network without using TCP/IP |
| US7673297B1 (en) * | 2003-09-03 | 2010-03-02 | The Directv Group, Inc. | Automatic software update detection and flexible installer for set-top boxes |
| US7500235B2 (en) * | 2003-09-05 | 2009-03-03 | Aol Time Warner Interactive Video Group, Inc. | Technique for updating a resident application and associated parameters in a user terminal through a communications network |
| US7099753B2 (en) * | 2004-04-27 | 2006-08-29 | The Boeing Company | Automatic generation of telemetry flight software, accompanying specifications, and decode files |
| US20070288986A1 (en) * | 2006-06-13 | 2007-12-13 | Candelore Brant L | Method and system for downloading content to a target device |
| US8424041B2 (en) | 2005-09-07 | 2013-04-16 | Sony Corporation | Method and system for downloading content to a content downloader |
Family Cites Families (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4654654A (en) * | 1983-02-07 | 1987-03-31 | At&T Bell Laboratories | Data network acknowledgement arrangement |
| IN170793B (en) | 1987-12-18 | 1992-05-23 | Hitachi Ltd | |
| JPH04175952A (en) * | 1990-11-09 | 1992-06-23 | Hitachi Ltd | Software resource distribution control system |
| JPH05145548A (en) * | 1991-11-19 | 1993-06-11 | Hitachi Ltd | Download control method for information communication network system |
| US5421009A (en) * | 1993-12-22 | 1995-05-30 | Hewlett-Packard Company | Method of remotely installing software directly from a central computer |
| DE4408544C2 (en) * | 1994-03-14 | 1997-06-19 | Siemens Nixdorf Inf Syst | Automatic installation |
| US5666293A (en) * | 1994-05-27 | 1997-09-09 | Bell Atlantic Network Services, Inc. | Downloading operating system software through a broadcast channel |
| US5768539A (en) * | 1994-05-27 | 1998-06-16 | Bell Atlantic Network Services, Inc. | Downloading applications software through a broadcast channel |
| DE4429969A1 (en) | 1994-08-24 | 1996-02-29 | Sel Alcatel Ag | Process for exchanging program packages in a multi-computer system and computer therefor |
| DE4438697A1 (en) * | 1994-10-29 | 1996-05-02 | Sel Alcatel Ag | Method for loading multi-computer systems |
| DE4438698A1 (en) * | 1994-10-29 | 1996-05-02 | Sel Alcatel Ag | Method of loading multi-computer systems |
| US6128648A (en) * | 1994-11-23 | 2000-10-03 | International Business Machines Corporation | Information handling system and method for maintaining coherency between network servers and mobile terminals |
| GB2296167A (en) * | 1994-12-16 | 1996-06-19 | Ibm | Serialising updates in a data conferencing network |
| US5553083B1 (en) * | 1995-01-19 | 2000-05-16 | Starburst Comm Corp | Method for quickly and reliably transmitting frames of data over communications links |
| JPH08241206A (en) * | 1995-03-07 | 1996-09-17 | Mitsubishi Electric Corp | Data communication processing method |
| US5671225A (en) * | 1995-09-01 | 1997-09-23 | Digital Equipment Corporation | Distributed interactive multimedia service system |
| JP3326672B2 (en) * | 1995-09-26 | 2002-09-24 | 日本電信電話株式会社 | Message retransmission method and system |
| GB2311389B (en) * | 1996-03-18 | 2000-06-07 | Ibm | Software installation in data processing network |
| US5848064A (en) * | 1996-08-07 | 1998-12-08 | Telxon Corporation | Wireless software upgrades with version control |
-
1997
- 1997-09-23 DE DE19741870A patent/DE19741870A1/en not_active Withdrawn
-
1998
- 1998-08-28 ES ES98440186T patent/ES2237830T3/en not_active Expired - Lifetime
- 1998-08-28 EP EP98440186A patent/EP0903666B1/en not_active Expired - Lifetime
- 1998-08-28 DE DE59812742T patent/DE59812742D1/en not_active Expired - Lifetime
- 1998-09-14 AU AU84222/98A patent/AU8422298A/en not_active Abandoned
- 1998-09-18 JP JP26518298A patent/JPH11163943A/en not_active Withdrawn
- 1998-09-22 CA CA002245384A patent/CA2245384A1/en not_active Abandoned
- 1998-09-23 CN CNB981196969A patent/CN1186902C/en not_active Expired - Fee Related
- 1998-09-23 US US09/159,155 patent/US6836793B1/en not_active Expired - Fee Related
-
2008
- 2008-10-16 JP JP2008267121A patent/JP2009104603A/en active Pending
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040174319A1 (en) * | 2003-01-21 | 2004-09-09 | Mitsubishi Denki Kabushiki Kaisha | Information transmission apparatus and information transmission method |
| US7636773B2 (en) * | 2003-01-21 | 2009-12-22 | Mitsubishi Denki Kabushiki Kaisha | Information transmission apparatus and information transmission method |
| WO2007050067A1 (en) * | 2005-10-26 | 2007-05-03 | Thomson Licensing | A system and method for advertising the availability of a software upgrade |
| US20070106777A1 (en) * | 2005-11-04 | 2007-05-10 | Internet Initiative Japan Inc. | Automatic functionality generating mechanism for network connecting appliances |
| US7660266B2 (en) * | 2005-11-04 | 2010-02-09 | Internet Initiative Japan, Inc. | Automatic functionality generating mechanism for network connecting appliances |
| US20070195770A1 (en) * | 2006-02-20 | 2007-08-23 | Fujitsu Limited | Network controller, receiving terminal device, content delivery system, network control method, and content receiving method |
| US20070288985A1 (en) * | 2006-06-13 | 2007-12-13 | Candelore Brant L | Method and system for uploading content to a target device |
| US20100058403A1 (en) * | 2008-08-29 | 2010-03-04 | Vaidyanathan Ramaswami | Distributing On-Demand Multimedia Content |
| US8589993B2 (en) | 2008-08-29 | 2013-11-19 | At&T Intellectual Property I, L.P. | Distributing on-demand multimedia content |
Also Published As
| Publication number | Publication date |
|---|---|
| AU8422298A (en) | 1999-04-15 |
| EP0903666A1 (en) | 1999-03-24 |
| DE59812742D1 (en) | 2005-05-25 |
| CN1212541A (en) | 1999-03-31 |
| JPH11163943A (en) | 1999-06-18 |
| ES2237830T3 (en) | 2005-08-01 |
| JP2009104603A (en) | 2009-05-14 |
| EP0903666B1 (en) | 2005-04-20 |
| CN1186902C (en) | 2005-01-26 |
| CA2245384A1 (en) | 1999-03-23 |
| DE19741870A1 (en) | 1999-03-25 |
| US6836793B1 (en) | 2004-12-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP2009104603A (en) | Method of distributing data packet of system software | |
| US7627653B2 (en) | Method and apparatus for distributing computer files across a network | |
| US6954853B2 (en) | Remote boot system for multiple client terminals and method thereof | |
| US20040261071A1 (en) | Peer version control system | |
| JP2000504863A (en) | Method and apparatus for connecting a client node to a server node based on load level | |
| US20010034230A1 (en) | Information delivery system using satellite communication | |
| JPH06284131A (en) | Identity distribution device and method for digital transmission system | |
| KR101298644B1 (en) | Scheduled delivery of software download | |
| US20010005862A1 (en) | Method for down-loading data | |
| CN116055481B (en) | Method, system, device and storage medium for sharing files | |
| CN101877722A (en) | Electronic program guide (EPG) system and file downloading method | |
| US20020042910A1 (en) | Method of detecting write conflicts in replicated databases without memory overhead | |
| JP4838935B2 (en) | Processing and apparatus for managing objects in a communication network | |
| CN116112065B (en) | File sharing method, system, device and storage medium based on satellite communication | |
| JPH11219330A (en) | Transmitting device and transmitting method, receiving device and receiving method, transmitting / receiving system and transmitting / receiving method | |
| KR101591534B1 (en) | Peer to Peer Transmittance System for Hierarchical Tracker and Tracker Apparatus therefor | |
| CN111585795B (en) | Software storing, loading and upgrading method and system for communication equipment | |
| KR20230013943A (en) | Apparatus, system and method for upgrading IPTV terminal | |
| US8261313B2 (en) | Mobile communication terminal and method of transmitting broadcast viewing information thereof | |
| JP2001331398A (en) | Server-managing system | |
| KR100672524B1 (en) | How to download the program for upgrade | |
| JP2025032664A (en) | Service agent device, service providing system, and service agent method | |
| AU702953B2 (en) | Loading method for multi computer system | |
| JP2000207337A (en) | Data distribution system | |
| GB2295035A (en) | Computer network distributed data storage. |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| AS | Assignment |
Owner name: ALCATEL, FRANCE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CESAR, BOZO;KEIL, KLAUS;RIEMER, JOACHIM;REEL/FRAME:009562/0108 Effective date: 19981008 |
|
| CC | Certificate of correction | ||
| FPAY | Fee payment |
Year of fee payment: 4 |
|
| FPAY | Fee payment |
Year of fee payment: 8 |
|
| AS | Assignment |
Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:LUCENT, ALCATEL;REEL/FRAME:029821/0001 Effective date: 20130130 Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:ALCATEL LUCENT;REEL/FRAME:029821/0001 Effective date: 20130130 |
|
| AS | Assignment |
Owner name: ALCATEL LUCENT, FRANCE Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:033868/0001 Effective date: 20140819 |
|
| REMI | Maintenance fee reminder mailed | ||
| LAPS | Lapse for failure to pay maintenance fees | ||
| STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
| FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20161228 |