CN102169439A - Data transmission system - Google Patents

Data transmission system Download PDF

Info

Publication number
CN102169439A
CN102169439A CN2010101244306A CN201010124430A CN102169439A CN 102169439 A CN102169439 A CN 102169439A CN 2010101244306 A CN2010101244306 A CN 2010101244306A CN 201010124430 A CN201010124430 A CN 201010124430A CN 102169439 A CN102169439 A CN 102169439A
Authority
CN
China
Prior art keywords
data
peripheral interface
interface controller
firmware
firmware update
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
Application number
CN2010101244306A
Other languages
Chinese (zh)
Other versions
CN102169439B (en
Inventor
刘鹏
陈志伟
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.)
Ningxia Haitong Electronic Technology Co ltd
Original Assignee
Inventec 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 Inventec Corp filed Critical Inventec Corp
Priority to CN201010124430.6A priority Critical patent/CN102169439B/en
Publication of CN102169439A publication Critical patent/CN102169439A/en
Application granted granted Critical
Publication of CN102169439B publication Critical patent/CN102169439B/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Stored Programmes (AREA)

Abstract

The invention provides a data transmission system which comprises a remote control end and a server end, wherein the remote control end can supply firmware updating data to the server end; the server end comprises an internal memory which is at least divided into a first zone and a second zone; when the firmware updating data is transmitted and overwritten to the second zone, overwritten state data and overwritten schedule data are updated in the first zone; and according to the overwritten state data, the server end can feed back the information through which the remote control end can decide to send the complete or residual firmware updating data. By using the data transmission system provided by the invention, the server can ask the remote control end to go on transmitting the residual firmware updating data after the firmware transmission process is interrupted, thereby saving the time for overwriting data, reducing the times of invalid overwriting in the internal memory, prolonging the service life of the internal memory and improving the working efficiency and stability of the server.

Description

Data transmission system
Technical Field
The present invention relates to a server system, and more particularly, to a server system for transmitting data.
Background
When updating a firmware image from a Peripheral Interface Controller (PIC) of a server, the firmware image data needs to be completely transmitted to the server at the local end. When a Baseboard Management Control (BMC) unit in the server receives the entire firmware image data, the BMC unit can overwrite the firmware image data to a memory.
In the process of overwriting the firmware data to the memory, once the server is powered off or in other special conditions, the baseboard management control unit stops overwriting the firmware data to the memory. After the server resumes normal operation and performs the firmware image updating again, the server requests to start transmitting the firmware image data again no matter what the progress of writing the previous firmware image data into the memory.
However, since the speed of updating the firmware image is limited, if the server requires the firmware image data to be sent again after the firmware image transmission process is interrupted, the time that the previous firmware image data has been overwritten to the memory is wasted, the invalid overwriting times of the memory is increased, the service life of the memory is reduced, and the working efficiency and stability of the server are reduced.
Therefore, how to develop a solution for continuously overwriting data after power failure, which overcomes the above inconvenience and disadvantages, is an important issue that related manufacturers are reluctant to find.
Disclosure of Invention
One objective of the present invention is to disclose a server system capable of continuously overwriting data after power failure, so as to avoid wasting the overwriting time of the firmware image data and increasing the invalid overwriting times of the memory when the server system needs to repeat the transmission of the firmware image data after the firmware image transmission procedure is interrupted, thereby reducing the service life of the memory and the working efficiency and stability of the server.
The data transmission system comprises a remote control end and a server end. The remote control end is used for providing a firmware update data. The server comprises a network transmission unit, a substrate management controller, a memory and a peripheral interface controller. The baseboard management controller is connected with the remote control end through the network transmission unit. The memory is divided into at least a first area and a second area, and the first area is used for placing overwriting state data and overwriting progress data. The second area is used for storing the firmware update data. The peripheral interface controller is electrically connected with the memory and the substrate management controller.
The peripheral interface controller reads the overwriting state data and judges whether the remote control end transmits complete firmware update data or not according to the overwriting state data, and the substrate management controller feeds back the judgment result of the peripheral interface controller to the remote control end so that the remote control end transmits the complete or residual firmware update data to the server end according to the judgment result.
In an embodiment of the present invention, the server further includes a BIOS module and a BIOS memory. The BIOS memory is electrically connected with the BIOS module and the peripheral interface controller. The firmware update data is used for updating firmware in the peripheral interface controller or the BIOS memory.
In another embodiment of the present invention, the remaining firmware update data comprises a plurality of consecutive data packets, wherein the data packets have consecutive numbers respectively, and the overwrite progress data records the number of the last sent data packet in the previous firmware transmission procedure.
In this embodiment, when the peripheral interface controller overwrites the firmware update data to the second area, the overwrite status data of the first area has the information "firmware update procedure is not completed". In addition, the peripheral interface controller requests the remote control end to transmit the remaining firmware update data according to the overwrite status data of the first area.
In another embodiment of the present invention, after the peripheral interface controller overwrites the firmware update data to the second area, the overwrite status data of the first area has the information that the firmware transmission process is completed. In addition, the peripheral interface controller requests the remote control end to transmit another complete firmware update data according to the overwrite status data of the first area.
In summary, the present invention enables the server to request the remote control end to continue to transmit the remaining firmware update data after the firmware transmission procedure is interrupted. Therefore, the time for completing data overwriting can be saved, the invalid overwriting times of the memory can be reduced, the service life of the memory can be prolonged, and the working efficiency and the stability of the server can be improved.
Drawings
The various aspects of the present invention will become more apparent to the reader after reading the detailed description of the invention with reference to the attached drawings. Wherein,
fig. 1 is a block diagram of a data transmission system according to an embodiment of the invention.
FIG. 2 is a flowchart illustrating the operation of the data transmission system of the present invention after power off to continue to overwrite data.
[ description of main reference symbols ]
100: the server 421: first region
101: the server 422: overwriting status data
200: the management module 423: overwriting progress data
210: network transmission unit 424: second region
220: baseboard management controller 425: data packet
300: the main board 430: BIOS module
400: peripheral interface control module 431: BIOS memory
410: the peripheral interface controller 600: remote control terminal
411: update procedure 201-: step (ii) of
420: memory device
Detailed Description
While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.
The present invention provides a data transmission system, which records the firmware-copy overwriting progress of the previous firmware-copy transmission procedure so as to continue overwriting the firmware-copy data, thereby preventing the firmware-copy data from being overwritten again.
Referring to fig. 1, fig. 1 is a block diagram illustrating a data transmission system according to an embodiment of the invention. In an embodiment of the present invention, the data transmission system includes a server 100 and at least one remote control 600. A server 101 of the server 100 at least has a management module 200 and a motherboard 300. The management module 200 is at least provided with a Network interface (Network interface connector) 210 and a Baseboard Management Controller (BMC) 220. The motherboard 300 has a Peripheral Interface Control (PIC) module 400, and the PIC module 400 has a memory 420 and a PIC controller 410.
The network transmission unit 210 is electrically connected to the bmc 220, and can be externally connected to a plurality of remote devices (e.g., file servers, etc.) through a network (networks), wherein one of the remote devices can be the remote control end 600 described above to provide firmware update data. The bmc 220 is electrically connected to the network transmission unit 210, and is electrically connected to the remote control end 600 through the network transmission unit 210 to request the remote control end 600 to provide the firmware update data. The bmc 220 is electrically connected to the pci controller 410, for example, through an I2C bus, for controlling the pci controller 410 to perform firmware update.
The memory 420 is, for example, a FLASH memory 420(FLASH), which can be independently installed on the motherboard 300 relative to the peripheral interface controller 410 and electrically connected to the peripheral interface controller 410. A first area 421 and a second area 424 are pre-divided in the memory 420, and an overwrite status data 422 and an overwrite progress data 423 are placed in the first area 421. The second region 424 is for storing the aforementioned firmware update data. The peripheral interface controller 410 is electrically connected to the memory 420 and the bmc 220, and has a firmware therein.
In another variation of the present embodiment, the first area may be a memory unit (not shown) built in the peripheral interface controller 410 for the peripheral interface controller 410 to directly read and write the overwrite status data 422 and the overwrite progress data 423.
In addition, the motherboard 300 of the embodiment may also be provided with a BIOS module 430 and a BIOS memory 431. The BIOS module 430 is electrically connected to the peripheral interface controller 410. The BIOS memory 431 is electrically connected to the BIOS module 430 and the peripheral interface controller 410. The BIOS memory 431 is configured to store BIOS firmware for the BIOS module 430 to read when booting. The firmware update data in the second region 424 may be the update firmware of the peripheral interface controller 410 and/or the update firmware of a BIOS module 430, as appropriate.
Referring to fig. 2, fig. 2 is a flowchart illustrating an operation of the data transmission system according to the present invention to implement a method for continuously overwriting data after power off. The server 101 proceeds as follows: in step (201), when the server 101 is powered on, the overwrite status data 422 and the overwrite progress data 423 in the memory 420 are read:
in this step, when the server 101 of the server 100 is powered on, the bmc 220, the network transmission unit 210, the BIOS module 430, the memory 420, and the peripheral interface controller 410 respectively enter a boot program.
When the BIOS module 430 enters the boot process, the BIOS module 430 reads the BIOS firmware in the BIOS memory 431.
When the peripheral interface controller 410 enters the start-up procedure, the peripheral interface controller 410 reads the firmware thereof, wherein the start-up procedure of the peripheral interface controller 410 includes reading the overwrite status data 422 and the overwrite progress data 423 in the first area 421.
Step 202 waits for an indication to proceed with a firmware transfer process:
after the above-mentioned start-up procedure, the peripheral interface controller 410 performs normal operation according to the firmware image thereof. When the peripheral interface controller 410 receives an indication of a firmware update procedure from the bmc 220, the peripheral interface controller 410 determines whether the firmware update procedure is completed according to the overwrite status data 422, i.e. the peripheral interface controller 410 can determine whether the remote control 600 has transmitted the complete firmware update data. Specifically, the overwrite status data 422 in the first region 421 of the memory 420 can be about one byte in size, such as "True" for the completion of the firmware transfer process, or "False" for the completion of the firmware transfer process.
Step (203) determines whether the bremsstrahlung transmission process is completed, if yes, step (206) is performed, otherwise step (204) is performed:
in this step, since the firmware can be interrupted due to power failure or other factors during the firmware transmission process, the peripheral interface controller 410 needs to first determine whether the firmware transmission process is completed.
Step (204) feeding back the first information to the remote control end 600 according to the overwriting progress data 423 for the remote control end 600 to continue to transmit the remaining firmware update data;
in this step, when the peripheral interface controller 410 determines that the firmware transfer process is not completed according to the overwrite status data 422, the bmc 220 feeds back a first message to the remote control 600 according to the determination result of the peripheral interface controller 410.
When the remote control 600 obtains the first message, the remote control 600 knows that the "firmware transfer program is not completed" and the current overwriting progress data of the first area 421 of the memory 420. The remote control side 600 transmits the firmware update data to the server side 100 accordingly.
Specifically, the remote control 600 parses the firmware update data into a plurality of consecutive data packets 425, and the consecutive data packets 425 have consecutive numbers respectively. Thus, the overwrite progress data 423 in the memory 420 can be about four bytes in size, for example, the number of the last data packet 425 (for example, the 60 th packet in 100 packets) sent in the previous transmission procedure of the firmware image can be recorded.
Step 205 overwrites the remaining firmware update data to memory 420:
in this step, when the remote control 600 obtains the first information, the remote control 600 sequentially transmits all data packets 425 (from the 61 st packet to the 100 th packet in the above example) starting from the next data packet 425 after the data packet 425 number to the server 101 according to the data packet 425 number in the overwriting progress data 423.
Specifically, when the peripheral interface controller 410 overwrites the consecutive data packets 425 to the second area 424, the peripheral interface controller 410 records the "firmware transfer transaction unfinished" information to the overwrite status data 422 of the first area 421. When the PCI controller 410 overwrites a consecutive data packet 425 in the second area 424 each time, the PCI controller 410 updates the serial number of the data packet 425 to the overwrite progress data 423 of the first area 421. Thus, when the firmware transmission process is interrupted due to power failure or other factors, the peripheral interface controller 410 can determine that the previous firmware transmission process is not completed, and vice versa. Subsequently, step (207) is performed.
In another embodiment, the data packet 425 may be, for example, an Intelligent Platform Management Interface (IPMI) data packet. After the remote control 600 sends the remaining data packets 425 to the bmc 220 through the network transmission unit 210, the bmc 220 parses the remaining data packets 425 into IPMB (Intelligent platform management Bus) data packets 425, and allows the peripheral interface controller 410 to overwrite the firmware update data in the second area 424.
Step (206) feeds back the second information to the remote control 600 according to the overwriting progress data 423, so that the remote control 600 transmits a complete firmware update data and sequentially overwrites the complete firmware update data in the memory 420: in this step, when the peripheral interface controller 410 determines that the firmware transfer process is completed according to the overwrite status data 422, the bmc 220 feeds back the second information to the remote control 600 according to the determination result of the peripheral interface controller 410.
When the remote control 600 obtains the second message, the remote control 600 knows that the firmware transmission procedure is completed, and transmits the complete firmware update data to the server 100, wherein the remote control 600. The entire firmware update data is parsed into a plurality of consecutive data packets 425 in sequence and transferred to a second region 424 of the memory 420. The consecutive data packets 425 each have a consecutive number.
Specifically, when the peripheral interface controller 410 overwrites the consecutive data packets 425 to the second area 424, the peripheral interface controller 410 records the "firmware transfer transaction unfinished" information to the overwrite status data 422 of the first area 421. When the PCI controller 410 overwrites a consecutive data packet 425 in the second area 424 each time, the PCI controller 410 updates the serial number of the data packet 425 to the overwrite progress data 423 of the first area 421.
Thus, when the firmware transmission process is interrupted due to power failure or other factors, the peripheral interface controller 410 can determine that the previous firmware transmission process is not completed, and vice versa. Subsequently, step (207) is performed.
The data packet 425 may be, for example, an SMI data packet. When the remote control 600 sends the complete and continuous ipmi data packets 425 to the bmc 220 through the network transmission unit 210. The bmc 220 parses the ipmi data packets 425 into ipmi bus data packets 425 for the peripheral interface controller 410 to overwrite the firmware update data into the second area 424.
After completing the transfer and overwriting of the firmware update data to the memory 420, step 207 performs the firmware update using the complete firmware update data:
in this step, after the peripheral interface controller 410 completes overwriting of the data packet 425 into the second area 424, the peripheral interface controller 410 records the information that the "firmware transfer process is completed" into the overwriting status data 422 of the first area 421.
When the remote control 600 finishes transmitting the firmware update data and the peripheral interface controller 410 finishes overwriting the data packet 425 to the second area 424, the peripheral interface controller 410 first records the information that the firmware transmission process is finished in the overwrite status data 422 of the first area 421 and the peripheral interface controller 410 clears the overwrite progress data 423 of the first area 421.
Thus, the peripheral interface controller 410 can know that the previous firmware transfer process is successfully completed.
Thereafter, when the firmware update data is a firmware for updating the peripheral interface controller 410, the peripheral interface controller 410 reads the firmware update data in the second area 424 according to a firmware update procedure 411 to perform the firmware update on the peripheral interface controller 410 itself.
Alternatively, when the firmware update data is a firmware update for updating the BIOS module 430, the BIOS module 430 requests the peripheral interface controller 410 to transmit the firmware update data in the second region 424 to the BIOS memory 431 for updating the BIOS module 430.
In summary, since the memory 420 is a non-volatile memory, the overwriting status data 422, the overwriting progress data 423 and the firmware update data still do not disappear due to power failure after being overwritten and updated into the memory 420, and the remote control end 600 can know whether to transmit the complete or the remaining firmware update data through feedback from the bmc 220, thereby embodying the purpose of continuously updating after power failure and power re-on.
Therefore, the time for completing data overwriting can be saved, the invalid overwriting times of the memory 420 can be reduced, the service life of the memory 420 can be prolonged, and the working efficiency and the stability of the server can be improved.
Hereinbefore, specific embodiments of the present invention are described with reference to the drawings. However, those skilled in the art will appreciate that various modifications and substitutions can be made to the specific embodiments of the present invention without departing from the spirit and scope of the invention. Such modifications and substitutions are intended to be included within the scope of the present invention as defined by the appended claims.

Claims (7)

1. A data transmission system, characterized in that the data transmission system comprises:
a remote control end for providing a firmware update data; and
a server side, comprising:
a network transmission unit;
a baseboard management controller connected to the remote control end through the network transmission unit;
the memory is divided into at least a first area and a second area, the first area is used for placing overwriting state data and overwriting progress data, and the second area is used for storing the firmware update data; and
a peripheral interface controller electrically connected to the memory and the baseboard management controller,
when the peripheral interface controller receives the firmware update data from the substrate management controller and overwrites the firmware update data to the second region, the peripheral interface controller updates the overwrite status data and the overwrite progress data of the first region, wherein the peripheral interface controller reads the overwrite status data and accordingly determines whether the remote control end has transmitted the complete firmware update data, and the substrate management controller feeds back the determination result of the peripheral interface controller to the remote control end so that the remote control end transmits the complete or the remaining firmware update data according to the determination result.
2. The data transmission system of claim 1, wherein the server further comprises a server, the server further comprises a management module and a motherboard, wherein the network transmission unit and the baseboard management controller are disposed in the management module, the motherboard has a peripheral interface control module, and the peripheral interface controller and the memory are disposed in the peripheral interface control module.
3. The data transmission system according to claim 1, wherein said data transmission system further comprises a BIOS module and a BIOS memory electrically connected to said BIOS module and said peripheral interface controller, wherein said firmware update data is used to update firmware in said peripheral interface controller or said BIOS memory.
4. The data transmission system of claim 1, wherein said firmware update data is divided into a plurality of data packets, wherein said data packets have consecutive numbers respectively, and said overwrite progress data records the number of said data packet last sent in the previous transmission of said firmware.
5. The data transmission system as claimed in claim 4, wherein the overwrite status data of the first area is updated when the peripheral interface controller overwrites the firmware update data to the second area, the overwrite status data being updated in real time each time the peripheral interface controller receives one of the data packets.
6. The data transmission system according to claim 5, wherein said peripheral interface controller requests said remote control end to send said remaining firmware update data according to said overwrite status data of said first area.
7. The data transmission system according to claim 1, wherein the overwrite status data of the first region is a complete status after the peripheral interface controller overwrites all of the firmware update data to the second region.
CN201010124430.6A 2010-02-26 2010-02-26 Data transmission system Expired - Fee Related CN102169439B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201010124430.6A CN102169439B (en) 2010-02-26 2010-02-26 Data transmission system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201010124430.6A CN102169439B (en) 2010-02-26 2010-02-26 Data transmission system

Publications (2)

Publication Number Publication Date
CN102169439A true CN102169439A (en) 2011-08-31
CN102169439B CN102169439B (en) 2014-05-07

Family

ID=44490606

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201010124430.6A Expired - Fee Related CN102169439B (en) 2010-02-26 2010-02-26 Data transmission system

Country Status (1)

Country Link
CN (1) CN102169439B (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103488491A (en) * 2012-06-11 2014-01-01 腾讯科技(深圳)有限公司 Method for carrying out system upgrade on terminal and terminal
CN103713911A (en) * 2012-09-28 2014-04-09 中兴通讯股份有限公司 Single version upgrading method and single version upgrading device
CN108021518A (en) * 2017-11-17 2018-05-11 华为技术有限公司 A kind of data interactive method and computing device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009641A (en) * 2006-12-31 2007-08-01 中国建设银行股份有限公司 Method and system for transferring large number of data
US20090083447A1 (en) * 2006-08-30 2009-03-26 International Business Machines Corporation Control of information units in fibre channel communications
CN101582924A (en) * 2009-06-19 2009-11-18 深圳市五巨科技有限公司 Data transmission method of mobile terminal and device thereof

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090083447A1 (en) * 2006-08-30 2009-03-26 International Business Machines Corporation Control of information units in fibre channel communications
CN101009641A (en) * 2006-12-31 2007-08-01 中国建设银行股份有限公司 Method and system for transferring large number of data
CN101582924A (en) * 2009-06-19 2009-11-18 深圳市五巨科技有限公司 Data transmission method of mobile terminal and device thereof

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103488491A (en) * 2012-06-11 2014-01-01 腾讯科技(深圳)有限公司 Method for carrying out system upgrade on terminal and terminal
CN103488491B (en) * 2012-06-11 2016-11-23 腾讯科技(深圳)有限公司 Terminal is carried out method and this terminal of system upgrade
CN103713911A (en) * 2012-09-28 2014-04-09 中兴通讯股份有限公司 Single version upgrading method and single version upgrading device
CN103713911B (en) * 2012-09-28 2017-11-10 中兴通讯股份有限公司 A kind of single version upgrade method and device
CN108021518A (en) * 2017-11-17 2018-05-11 华为技术有限公司 A kind of data interactive method and computing device
CN108021518B (en) * 2017-11-17 2019-11-29 华为技术有限公司 A kind of data interactive method and calculate equipment

Also Published As

Publication number Publication date
CN102169439B (en) 2014-05-07

Similar Documents

Publication Publication Date Title
EP3200072B1 (en) Method for updating terminal system, terminal and system
EP3043512B1 (en) Firmware upgrade method and system, upper computer and optical module
CN112947977B (en) Online software upgrading method and system
CN101595442B (en) Updating a power supply microcontroller
US9235405B2 (en) Apparatus, system and method for upgrading firmware of energy metering device
CN101621411B (en) Method and system for remotely updating microcontrollers
CN110244971A (en) A kind of On-line Product upgrade-system and method based on multiple load
CN101605189A (en) The online upgrade system of intelligent platform management controller and method
EP3435628A1 (en) Systems and methods for upgrading firmware in multiple devices of a wireless fire detection system
CN101196823A (en) Method, system and equipment for on-line software upgrade in open application structure
CN102169439B (en) Data transmission system
CN111756858B (en) Remote development processing system, method and device for embedded equipment
CN114201197A (en) Firmware upgrading method and device, electronic equipment and readable storage medium
CN102693142A (en) Network adaptation method and device
US20040019720A1 (en) Multi-master extended 12C protocol
CN108874700A (en) Electronic equipment
CN110209531A (en) A kind of long-range ARM online upgrade system and method based on RS422 interface
CN105278992A (en) Firmware updating method and apparatus
CN112771497A (en) Method and device for upgrading equipment and storage medium
CN109697077B (en) Method, device and equipment for starting hard disk firmware
CN117055923A (en) Firmware upgrading system, method and device, electronic equipment and storage medium
JP2006318394A (en) Management method for uninterruptible power supply device in network system
CN103176931B (en) A kind of DMA communication means of improvement and device
CN115080091A (en) Method and system for upgrading MCU firmware on line by satellite communication equipment
CN103984657A (en) interface controller, external electronic device and control method thereof

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
TR01 Transfer of patent right
TR01 Transfer of patent right

Effective date of registration: 20190709

Address after: Sixth Floor, Building A, Jinfeng District and Xin Business Center, Yinchuan City, Ningxia Hui Autonomous Region

Patentee after: Ningxia Haitong Electronic Technology Co.,Ltd.

Address before: Taipei City, Taiwan Chinese Shilin District Hougang Street No. 66

Patentee before: Yingda Co.,Ltd.

CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20140507