US6141795A - Communication system - Google Patents

Communication system Download PDF

Info

Publication number
US6141795A
US6141795A US08/990,871 US99087197A US6141795A US 6141795 A US6141795 A US 6141795A US 99087197 A US99087197 A US 99087197A US 6141795 A US6141795 A US 6141795A
Authority
US
United States
Prior art keywords
software
software block
memories
new version
stored
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.)
Expired - Fee Related
Application number
US08/990,871
Other languages
English (en)
Inventor
Armin Laugner
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.)
US Philips Corp
Original Assignee
US Philips Corp
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 US Philips Corp filed Critical US Philips Corp
Assigned to U.S. PHILIPS CORPORATION reassignment U.S. PHILIPS CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LAUGNER, ARMIN
Application granted granted Critical
Publication of US6141795A publication Critical patent/US6141795A/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/247—Telephone sets including user guidance or feature selection means facilitating their use
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14—Error detection or correction of the data by redundancy in operation
    • G06F11/1402—Saving, restoring, recovering or retrying
    • G06F11/1415—Saving, restoring, recovering or retrying at system level
    • G06F11/1417—Boot up procedures
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/247—Telephone sets including user guidance or feature selection means facilitating their use
    • H04M1/2471—Configurable and interactive telephone terminals with subscriber controlled features modifications, e.g. with ADSI capability [Analog Display Services Interface]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/1305—Software aspects
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13093—Personal computer, PC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13103—Memory
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13106—Microprocessor, CPU
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13109—Initializing, personal profile
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13209—ISDN
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13376—Information service, downloading of information, 0800/0900 services

Definitions

  • the invention relates to a communication system comprising a terminal unit which includes a control circuit and at least two memories for storing software, and comprising a station for supplying software to the terminal unit whose control circuit is provided for exchanging software contained in at least one memory in response to an exchange command.
  • Such a communication system is known from DE 43 33 272 A1 which discusses a terminal unit coupled to a network and a maintenance device.
  • the maintenance device sends new process software for a control circuit of the terminal unit over the network, which operating software is exchanged in the terminal unit by means of an exchange control unit included in the control circuit.
  • the exchange control unit utilizes exchange software for the exchange operation, which software is stored in an exchange memory.
  • the system software is stored in another memory which is called operating memory.
  • This communication system requires a separate memory (exchange memory) and a separate control unit (exchange control unit) for the exchange operation.
  • the object is achieved with a communication system of the type defined in the opening paragraph in that the software comprises at least two blocks which are stored each in a respective memory and one block of which contains specific functions for an exchange operation, and in that, during an exchange operation, the control circuit is first provided for replacing the block without the specific functions by a new version of the block with the specific functions.
  • the control circuit in the terminal unit carries out the exchange operation of the software which is divided into two blocks and stored in at least two memories.
  • a new version of a block is understood to mean a software block produced by the station, which block is either or not changed compared with the previous version.
  • Such specific functions are delete and store functions which are necessary for exchanging blocks in the memories.
  • the block without specific functions contained in the memory is deleted first. Then the control circuit replaces the old version of the block with the specific functions by a new version of the block without the specific functions.
  • the exchange operation does not need the use of a separate memory, but the working memory (buffer memory) of the control circuit is used which is arranged, for example, as a microprocessor system. Neither is any further control unit used for the exchange, but the control circuit is used that also carries out the normal operating functions.
  • a disturbance for example, power failure
  • the terminal unit can no longer be operated because the rudimentary software is no longer available in that specific memory.
  • the control circuit does not erase the memory area of a memory during the exchange operation, which memory area contains rudimentary software for executing basic functions of the control circuit.
  • An exchange operation may be started by a control center which is coupled to the terminal unit and the station over a network. Once a connection has been set up with the terminal unit and the station, the control center transmits an exchange command. Then, after a first connection has been set up, the station starts successively sending segments of a first block to the terminal unit. The terminal unit transmits the segments to a first memory after the segments of the first block have been received in a buffer memory of the control circuit. After all the segments of the first block have been transmitted and a disconnection has taken place, the control circuit sets up a second connection to the station and receives segments of a second block from the station. The terminal unit transmits the segments to a second memory after the segments of the second block have been received in a buffer memory of the control circuit. The control circuit then erases the first or second memory after the first segment of the first or second block has been stored in the buffer memory.
  • FIG. 1 gives a diagrammatic representation of a communication system comprising two terminal units and one control center
  • FIG. 2 shows a block circuit diagram of a terminal unit
  • FIGS. 3 and 4 show blocks in explanation of the software exchange operation in the terminal unit.
  • FIG. 1 diagrammatically shows a communication system comprising a terminal unit 1, a station 2 for supplying software and a control center 3.
  • the terminal unit 1, the station 2 and the control center 3 are coupled to the network 4 outlined diagrammatically, which is, for example, an integrated services digital network (ISDN).
  • ISDN integrated services digital network
  • Such a terminal unit 1 may be, for example, a terminal adapter for adapting an ISDN S O interface to an a/b interface.
  • the station 2 may be a transmission unit of a terminal unit or, which is presupposed in the following, a terminal unit itself.
  • the terminal unit 1 comprises a control circuit 5, for example, a microprocessor, for controlling all the operations in the terminal unit 1, two non-volatile memories 6 and 7 which may be, for example, flash EPROMs for restoring the stored data even in the switched-off state of the terminal 1, and a switching element 8 which will not be described any further and performs, for example, the interface function of the terminal unit arranged as a terminal adapter.
  • Two software blocks having the same or different version numbers are stored in each non-volatile memory 6 and 7.
  • the software is necessary for operating the terminal unit 1.
  • the control circuit 5 After the control circuit 5 has been switched on or reset, it always reads the software from the first memory 6 first.
  • this memory 6 is also available a software portion (rudimentary software) which is first read by the control circuit 5 and is provided for executing basic functions of the terminal unit 1.
  • the terminal unit 2 has an identical structure.
  • the control center 3 has for its function to induce a software exchange in the terminal unit 1.
  • the software is supplied by the station or the terminal unit 2.
  • the terminal unit 1 and the station 2 are moved to an exchange state after an exchange command has been transmitted by the control center 3.
  • the terminal unit 1 and also the station 2 may be moved to the exchange state as a result of a command given locally.
  • the terminal unit 1 is referenced receiver and the station 2 transmitter.
  • the software for the terminal unit 1 or the receiver comprises two equally large blocks A and B which have each a version number and are stored in the memories 6 and 7 arranged as flash EPROMs. While the software is being exchanged, two connections are set up consecutively to renew the blocks A and B. Only at the beginning and at the end is available software in blocks A and B which have the same version number.
  • the coarse routine of the exchange will be explained with reference to FIGS. 3 and 4.
  • the blocks referenced (Ia), (IIa), (IIIa) and (IVa) show the contents of the memory 6 during various stages of the software exchange.
  • the blocks referenced (Ib), (IIb), (IIIb) and (IVb) relate to different stages of the memory 7 during the software exchange.
  • FIG. 4 shows the complementary exchange operation.
  • memory 6 stores the block B having the version number n (IIIa) and at the end of the exchange operation the block A having the version number m (IVa).
  • the memory 7 first contains the block A having the version number n (IIIb) and at last the block B having the version number m (IVb). Then, first the block B having version number n is replaced by block A having the version number m.
  • each software block A and B contains the rudimentary software discussed above. After an abortion and the subsequent reset, first the control circuit 5 loads the rudimentary software contained in the memory 6 and then extracts the erase and programming function from the complete block A.
  • the control center 3 sends the exchange command to the transmitter after the connection has been set up.
  • the control circuit 5 of the transmitter sets the mark "SWDL -- TRA" and is ready for transmitting the software.
  • a reset is then carried out by the transmitter.
  • the receiver is also invoked by the control center 3. Once the connection has been set up, the control center 3 sends the receiver the exchange command, the call number of the transmitter and the software version number to be transmitted.
  • the control circuit S of the receiver sets the mark "SWDL -- REC" and performs a reset.
  • the control circuit 5 of the receiver After a reset, the control circuit 5 of the receiver recognizes the mark "SWDL -- REC" and attempts to set up a connection to the transmitter.
  • the control circuit 5 of the transmitter recognizes the mark "SWDL -- TRA" after the reset and accepts the call of the receiver.
  • the control circuit 5 of the receiver requests the transmitter for a first block carrying the version number stated by the control center 3 by a request command. After the request command has been received, the transmitter switches the version number of the stored software while being controlled by its control circuit 5.
  • the control circuit 5 of the receiver compares the version number stated by the control center 3 with the version number supplied by the transmitter.
  • the receiver sends the message "FFF2" to the receiver. This message indicates that the software carrying the version number is not necessary.
  • the receiver disconnects, deletes the mark “SWDL -- REC" and carries out a reset.
  • the transmitter receives the message "FFF2" and the disconnection command.
  • the control circuit 5 of the transmitter keeps the mark "SWDL -- TRA" set and does not carry out a reset.
  • the control circuit 5 of the receiver transmits the command "FFF0" to the transmitter and thus requests the transmitter to transmit the block.
  • the blocks A and B of the software are subdivided into segments.
  • a first segment is transmitted to the receiver.
  • the first segment arriving at the receiver is stored in a buffer which forms part of the control circuit 5 of the receiver.
  • the control circuit 5 of the receiver transmits an acknowledgement to the control circuit 5 of the transmitter. This operation of transmitting segments from the transmitter to the receiver is continued with further segments until the buffer in the control circuit 5 of the receiver is filled.
  • the contents of a first memory (6 or 7) of the control circuit 5 of the receiver are deleted in a next step.
  • control circuit 5 of the receiver detects an error when the first memory is erased, this control circuit sends the error message "FFFE" to the transmitter.
  • the receiver disconnects and resets.
  • the transmitter receives the message "FFFE” and the disconnection command.
  • the control circuit 5 of the transmitter leaves the mark "SWDL -- TRA" set and does not reset the transmitter. Subsequently, again a connection between transmitter and receiver is set up and the transmission of the version numbers and of the segments of the first block is repeated.
  • the segments available in the buffer are written in the first memory (programming of the memory). If a transmission or memory error then occurs, the same operation is carried out as for an erase error.
  • the control circuit 5 of the receiver requests the control circuit 5 of the transmitter for further segments.
  • the transmitter then consecutively switches segments of the block A in ascending order to the receiver. This means that, for example, the segments 11, 12, . . . , 19 and 20 are transmitted in sequence if the segments 1 to 10 have been sent in a first step.
  • the segments are stored in the buffer and an acknowledgement is sent to the transmitter after the buffer is full. Then the segments are transmitted to the first memory.
  • the receiver is reset and the software exchange is started with the first block if the segments have not been transmitted in full. Otherwise, the transmission of the second block is started with.
  • the terminal unit 2 cannot be taken into operation again.
  • the routine described above may be changed, so that an exchange of the rudimentary software is excluded.
US08/990,871 1996-12-18 1997-12-15 Communication system Expired - Fee Related US6141795A (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
DE19652628A DE19652628A1 (de) 1996-12-18 1996-12-18 Kommunikationssystem
DE19652628 1996-12-18

Publications (1)

Publication Number Publication Date
US6141795A true US6141795A (en) 2000-10-31

Family

ID=7815096

Family Applications (1)

Application Number Title Priority Date Filing Date
US08/990,871 Expired - Fee Related US6141795A (en) 1996-12-18 1997-12-15 Communication system

Country Status (4)

Country Link
US (1) US6141795A (de)
EP (1) EP0849676A3 (de)
JP (1) JPH10190832A (de)
DE (1) DE19652628A1 (de)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6415435B1 (en) * 1999-03-18 2002-07-02 International Business Machines Corporation Method and apparatus for determining compatibility of parent classes in an object oriented environment using versioning
WO2002076020A1 (en) * 2001-03-21 2002-09-26 Telecom Italia S.P.A. . Method for upgrading network server programming conditions, associated system and software product
US6640334B1 (en) * 1999-09-27 2003-10-28 Nortel Networks Limited Method and apparatus of remotely updating firmware of a communication device
US20050116835A1 (en) * 2002-03-28 2005-06-02 Bernard Grehant Remote control device for an actuator
EP1574952A1 (de) * 2004-03-10 2005-09-14 Sony Ericsson Mobile Communications AB Automatisierter Datensicherungsspeicher in Firmware-Aufwertungen
WO2005085997A2 (en) * 2004-03-10 2005-09-15 Sony Ericsson Mobile Communications Ab Automatic backup store in firmware upgrades
US6993758B1 (en) * 1999-12-08 2006-01-31 Japan Cash Machine Co., Ltd. Method and apparatus for renewing software in a software-operated machine
US20100058315A1 (en) * 2007-05-17 2010-03-04 Huawei Technologies Co., Ltd. Method and system for process upgrade
US20130038440A1 (en) * 2011-08-09 2013-02-14 Continental Automotive Systems Us, Inc. Tire Pressure Monitoring Apparatus And Method

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6678741B1 (en) * 1999-04-09 2004-01-13 Sun Microsystems, Inc. Method and apparatus for synchronizing firmware
DE10053952A1 (de) * 2000-10-31 2002-06-27 Siemens Ag Verfahren und Anordnung zum Updaten von Software auf einem mobilen prozessorgesteuerten Gerät

Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4788637A (en) * 1985-09-30 1988-11-29 Kabushiki Kaisha Toshiba Communication control apparatus
US4954941A (en) * 1988-08-31 1990-09-04 Bell Communications Research, Inc. Method and apparatus for program updating
US5155847A (en) * 1988-08-03 1992-10-13 Minicom Data Corporation Method and apparatus for updating software at remote locations
DE4333272A1 (de) * 1993-09-30 1995-04-06 Philips Patentverwaltung Kommunikationssystem
US5430877A (en) * 1992-07-21 1995-07-04 Orbitel Mobile Communications Limited Reprogramming methods and apparatus
US5778234A (en) * 1992-05-08 1998-07-07 Paradyne Corporation Method for downloading programs
US5787288A (en) * 1993-11-19 1998-07-28 Mita Industrial Co., Ltd. Method and device for renewing an internal program of an apparatus having communication capability
US5901320A (en) * 1996-11-29 1999-05-04 Fujitsu Limited Communication system configured to enhance system reliability using special program version management
US5909581A (en) * 1995-12-30 1999-06-01 Samsung Electronics Co., Ltd. Automatic software updating method
US5974454A (en) * 1997-11-14 1999-10-26 Microsoft Corporation Method and system for installing and updating program module components
US5978916A (en) * 1997-11-25 1999-11-02 International Business Machines Corporation Method, system and computer program product for updating region-dependent software using a common update module for multiple regions
US6014725A (en) * 1995-07-04 2000-01-11 Siemens Aktiengesellschaft Method of up-dating the contents of the electronic memory of an electronic appliance

Patent Citations (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4788637A (en) * 1985-09-30 1988-11-29 Kabushiki Kaisha Toshiba Communication control apparatus
US5155847A (en) * 1988-08-03 1992-10-13 Minicom Data Corporation Method and apparatus for updating software at remote locations
US4954941A (en) * 1988-08-31 1990-09-04 Bell Communications Research, Inc. Method and apparatus for program updating
US5778234A (en) * 1992-05-08 1998-07-07 Paradyne Corporation Method for downloading programs
US5430877A (en) * 1992-07-21 1995-07-04 Orbitel Mobile Communications Limited Reprogramming methods and apparatus
DE4333272A1 (de) * 1993-09-30 1995-04-06 Philips Patentverwaltung Kommunikationssystem
US5787288A (en) * 1993-11-19 1998-07-28 Mita Industrial Co., Ltd. Method and device for renewing an internal program of an apparatus having communication capability
US6014725A (en) * 1995-07-04 2000-01-11 Siemens Aktiengesellschaft Method of up-dating the contents of the electronic memory of an electronic appliance
US5909581A (en) * 1995-12-30 1999-06-01 Samsung Electronics Co., Ltd. Automatic software updating method
US5901320A (en) * 1996-11-29 1999-05-04 Fujitsu Limited Communication system configured to enhance system reliability using special program version management
US5974454A (en) * 1997-11-14 1999-10-26 Microsoft Corporation Method and system for installing and updating program module components
US5978916A (en) * 1997-11-25 1999-11-02 International Business Machines Corporation Method, system and computer program product for updating region-dependent software using a common update module for multiple regions

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6415435B1 (en) * 1999-03-18 2002-07-02 International Business Machines Corporation Method and apparatus for determining compatibility of parent classes in an object oriented environment using versioning
US6640334B1 (en) * 1999-09-27 2003-10-28 Nortel Networks Limited Method and apparatus of remotely updating firmware of a communication device
US6993758B1 (en) * 1999-12-08 2006-01-31 Japan Cash Machine Co., Ltd. Method and apparatus for renewing software in a software-operated machine
WO2002076020A1 (en) * 2001-03-21 2002-09-26 Telecom Italia S.P.A. . Method for upgrading network server programming conditions, associated system and software product
US20040088693A1 (en) * 2001-03-21 2004-05-06 Gianni Canal Method for upgrading network server programming conditions, associated system and software product
US7644189B2 (en) 2001-03-21 2010-01-05 Telecom Italia S.P.A. Method for upgrading network server programming conditions, associated system and software product
US20050116835A1 (en) * 2002-03-28 2005-06-02 Bernard Grehant Remote control device for an actuator
WO2005085997A2 (en) * 2004-03-10 2005-09-15 Sony Ericsson Mobile Communications Ab Automatic backup store in firmware upgrades
WO2005085997A3 (en) * 2004-03-10 2006-06-29 Sony Ericsson Mobile Comm Ab Automatic backup store in firmware upgrades
US20080126672A1 (en) * 2004-03-10 2008-05-29 Sony Ericsson Mobile Communications Ab Automatic Backup Store In Firmware Upgrades
US7502813B2 (en) 2004-03-10 2009-03-10 Sony Ericsson Mobile Communications Ab Software update process using an extra memory block
EP1574952A1 (de) * 2004-03-10 2005-09-14 Sony Ericsson Mobile Communications AB Automatisierter Datensicherungsspeicher in Firmware-Aufwertungen
US20100058315A1 (en) * 2007-05-17 2010-03-04 Huawei Technologies Co., Ltd. Method and system for process upgrade
US8495610B2 (en) * 2007-05-17 2013-07-23 Huawei Technologies Co., Ltd. Method and system for process upgrade
US20130038440A1 (en) * 2011-08-09 2013-02-14 Continental Automotive Systems Us, Inc. Tire Pressure Monitoring Apparatus And Method

Also Published As

Publication number Publication date
DE19652628A1 (de) 1998-06-25
EP0849676A3 (de) 2001-08-08
JPH10190832A (ja) 1998-07-21
EP0849676A2 (de) 1998-06-24

Similar Documents

Publication Publication Date Title
US6141795A (en) Communication system
US6002690A (en) Time division multiplex transferring system capable of increasing transferring efficiency and preventing interruption of communication
US7606565B2 (en) Radio base station program update method and apparatus not requiring update host computer
KR100219828B1 (ko) 패킷전송방법 및 이동통신시스템
US5311590A (en) Protocol adaptation
US5619653A (en) Buffer device with resender
JPH06103854B2 (ja) 無線電話機データ遠隔書き込み方式
JP3641154B2 (ja) 交換機のデータ変換システム
JP2683795B2 (ja) 通信中チャネル切替方式
JP2972742B1 (ja) 制御プログラム更新方式
US6449364B2 (en) Programmable hands free telephone system
JPS57203365A (en) Connection system for additional device to facsimile terminal
JP2852252B2 (ja) 制御プログラム更新制御方式
WO1999045728A2 (en) An air-interface controlled base station for a cellular radio network
JP3282690B2 (ja) オンライン通信制御ソフトウェア変更方法
JP2514910B2 (ja) ファクシミリ装置
JP3452398B2 (ja) 無線電話装置
JPH1165850A (ja) Ｉｓｄｎ端末の遠隔制御方式
JP2898203B2 (ja) ルーチング制御方式
JPS62120761A (ja) デ−タ送受信制御方式
EP0828373A2 (de) Übertragungsgerät
JPH088903A (ja) Ｉｓｄｎ端末及びネットワーク管理装置
KR100245164B1 (ko) 위성통신시스템에서 트랜스폰더 채널할당장치 및 그 방법
KR100353647B1 (ko) 차세대 지능망 시스템에서 자국 신호점 인지방법
JPH0344470B2 (de)

Legal Events

Date Code Title Description
AS Assignment

Owner name: U.S. PHILIPS CORPORATION, NEW YORK

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LAUGNER, ARMIN;REEL/FRAME:009208/0198

Effective date: 19980212

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: 20041031