CN102957669A - Version updating method and version updating system for embedded equipment - Google Patents
Version updating method and version updating system for embedded equipment Download PDFInfo
- Publication number
- CN102957669A CN102957669A CN2011102427879A CN201110242787A CN102957669A CN 102957669 A CN102957669 A CN 102957669A CN 2011102427879 A CN2011102427879 A CN 2011102427879A CN 201110242787 A CN201110242787 A CN 201110242787A CN 102957669 A CN102957669 A CN 102957669A
- Authority
- CN
- China
- Prior art keywords
- message
- variant
- boot loader
- embedded device
- loader utility
- 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.)
- Pending
Links
Images
Abstract
The invention discloses a version updating method and a version updating system for embedded equipment. The method includes: storing a Boot Loader program of a variant on a client side; transmitting the Boot Loader program of the variant to the embedded equipment when the client side receives a version updating request of the embedded equipment; and enabling the embedded equipment to execute the received Boot Loader program of the variant and updating a version. The system comprises the client side and the embedded equipment. By the method and the system, RAM (random access memory) space in the embedded equipment is saved.
Description
Technical field
The present invention relates to the communications field, relate in particular to a kind of method for updating edition and system of embedded device.
Background technology
General embedded device, often hardware resource all is limited, such as RAM (random accessmemory, random access memory), ROM (Read-Only Memory, read-only memory) capacity is less, NAND-flash is a kind of nonvolatile flash memory technology, the cell density that tool is higher can reach high storage density, writes with erasing speed very fast.The cell size of NAND-flash almost is half of NOR-flash, higher capacity can be provided in given die size, have very fast writing and erasing speed, but use NAND-flash to have the problem of promoter region, and the boot section size that generally can directly use only has 16kb.
The Boot Loader of standard is the one section small routine that moved before the operating system of equipment, by Boot Loader, but initiating hardware equipment, set up the mapping graph of memory headroom, thereby take the hardware environment of equipment to a suitable state, in order to be ready to correct environment for final call operation system kernel.The Boot Loader of standard generally only provides TFTP (Trivial File Transfer Protocol, TFTP) upgrade service, but it can be rewritten, the Boot Loader of revised standard is called the Boot Loader of variant, usually, Boot Loader is cured in the equipment, and particularly in Embedded Application, it seriously depends on hardware; In the use of embedded device, when moving the version abnormal or special requirement arranged, often need to be under Boot Loader or boot edition changes, existing method of carrying out version updating by Boot Loader has following defective: the one, and passive upgrading and dumb, need personnel's active operation, and Boot Loader has cured at embedded device, can't upgrade at any time as required; The 2nd, hardware requirement is higher, needs jumbo storage chip (General Requirements surpasses 1M byte) and internal memory.
Summary of the invention
The objective of the invention is, a kind of method for updating edition and system of embedded device is provided, to optimize prior art large problem of committed memory resource in the version updating process.
The invention provides a kind of method for updating edition of embedded device, said method with the BootLoader procedure stores of variant in client, when client is received the version updating request of embedded device, the Boot loader utility of above-mentioned variant is handed down to above-mentioned embedded device;
Above-mentioned embedded device is carried out the Boot loader utility of the variant of receiving, carries out version updating.
Preferably, above-mentioned version updating request is the xmodem request.
Preferably, above-mentioned client is handed down to above-mentioned embedded device by the xmodem message with the Boot loader utility burst of above-mentioned variant, when above-mentioned embedded device is received message, judge whether xmodem message of above-mentioned message, if, then the Boot loader utility data with the variant in the above-mentioned xmodem message are saved in the internal memory, otherwise, abandon above-mentioned message.
Preferably, above-mentioned embedded device also carries out verification to the Boot loader utility of above-mentioned variant after the Boot of variant loader utility receives, if verification succeeds, then carry out the BootLoader program of above-mentioned variant, otherwise, again send the version updating request to above-mentioned client.
Preferably, the above-mentioned embedded device Boot loader utility of carrying out above-mentioned variant is carried out the version updating step and is specially:
According to the driving that the Boot loader utility of above-mentioned variant provides, the corresponding port of initialization;
By above-mentioned port, HTML (HypertextMarkup Language, the text mark language) page that the Boot loader utility of above-mentioned variant is provided sends to above-mentioned client;
Wait for that above-mentioned client issues version file;
The version file data of receiving are saved in the internal memory;
After version file receives, according to the method that the Boot loader utility of above-mentioned variant provides, above-mentioned version file is carried out verification;
If verification succeeds is then deposited above-mentioned version file among the local Flash in addition, enable simultaneously the version file in the internal memory; If the verification failure, then prompting verification failure in the WEB of the machine page.
Preferably, after above-mentioned client is received html page, above-mentioned html page is shown to the user and waits for that the user imports version file;
After detecting the user and importing version file, by TCP/IP (Transmission ControlProtocol/Internet Protocol, transmission control protocol/Internet Interconnection agreement) message above-mentioned version file burst is handed down to above-mentioned embedded device.
Preferably, after above-mentioned embedded device is received message, also carry out following operation:
Judge whether TCP/IP message of above-mentioned message, if the protocol type of then judging above-mentioned message is HTTP (Hyper Text Transfer Protocol, HTML (Hypertext Markup Language)) whether, if then the version file data in the above-mentioned message are deposited in the internal memory; Otherwise, abandon above-mentioned message.
The present invention further provides a kind of version updating system of embedded device, comprised client and embedded device,
Above-mentioned client is used for the Boot loader utility of storage variant, and when the version updating request of receiving embedded device, and the Boot loader utility of above-mentioned variant is handed down to above-mentioned embedded device;
Above-mentioned embedded device is used for sending the version updating request to above-mentioned client when needs carry out version updating, and carries out the Boot loader utility of the variant of receiving, carries out version updating.
Preferably, above-mentioned client is used for by the xmodem message Boot loader utility burst of above-mentioned variant being handed down to above-mentioned embedded device, and the interface that the Boot loader utility of revising above-mentioned variant is provided for the user;
Above-mentioned embedded device, be used in request stage, judge whether xmodem message of the message receive, and the Boot loader utility data of the variant in the xmodem message are saved in the internal memory, abandon non-xmodem message, and the Boot loader utility of the variant received carried out verification, and when the verification failure, resend the version updating request to above-mentioned client.
Preferably, above-mentioned client is used for after receiving html page, and above-mentioned html page is shown to the user and after detecting the user and importing version file, by the TCP/IP message above-mentioned version file burst is handed down to above-mentioned embedded device;
Above-mentioned embedded device, be used for the driving that the Boot loader utility according to above-mentioned variant provides, the corresponding port of initialization, and by above-mentioned port, the html page that the Boot loader utility of above-mentioned variant is provided sends to above-mentioned client, and in the Boot loader utility process of carrying out variant, when receiving the message that client issues, judge whether TCP/IP message of above-mentioned message, and when above-mentioned message is the TCP/IP message, the protocol type of judging above-mentioned message is HTTP whether, when above-mentioned message is the TCP/IP message of HTTP type, the version file data in the above-mentioned message is deposited in the internal memory; Be non-TCP/IP message or during for the TCP/IP message of non-HTTP type at above-mentioned message, abandon above-mentioned message, after version file receives, according to the method that the Boot loader utility of above-mentioned variant provides, above-mentioned version file is carried out verification, and when verification succeeds, above-mentioned version file is deposited among the local Flash in addition, enable above-mentioned version file from internal memory simultaneously, when the verification failure, prompting verification failure in the WEB of the machine page.
The present invention is stored in the mode of client by the Boot loader utility of use variant and with it, so that only store boot among the ROM of embedded device, reduced the use of ROM resource, because itself taking resource, the Boot loader utility of variant just lacks than the Boot loader utility of standard, therefore the present invention has saved the ram space in the embedded device.
Description of drawings
Accompanying drawing described herein is used to provide a further understanding of the present invention, consists of a part of the present invention, and illustrative examples of the present invention and explanation thereof are used for explaining the present invention, do not consist of improper restriction of the present invention.In the accompanying drawings:
Fig. 1 is the version updating system preferred embodiment theory diagram of embedded device of the present invention;
Fig. 2 is the preferred embodiment flow chart of client-side in the method for updating edition of embedded device of the present invention;
Fig. 3 is the preferred embodiment flow chart of embedded device side in the method for updating edition of embedded device of the present invention.
Embodiment
In order to make technical problem to be solved by this invention, technical scheme and beneficial effect clearer, clear, below in conjunction with drawings and Examples, the present invention is further elaborated.Should be appreciated that specific embodiment described herein only in order to explain the present invention, is not intended to limit the present invention.
As shown in Figure 1, be the version updating system preferred embodiment theory diagram of embedded device of the present invention, comprise client and embedded device,
Client, be used to the user that the interface of the Boot loader utility of revising described variant is provided, the Boot loader utility of storage variant, and when the version updating request of receiving embedded device, by the xmodem message Boot loader utility burst of above-mentioned variant is handed down to embedded device, and after receiving the html page that embedded device sends, above-mentioned html page is shown to the user, and after detecting the user and importing version file, by the TCP/IP message above-mentioned version file burst is handed down to embedded device;
Embedded device, be used for detecting to carry out version updating the time, send the version updating request to above-mentioned client, and in request stage, judge whether xmodem message of the message receive, and sequentially be saved in internal memory according to reception the Boot loader utility data of the variant in the above-mentioned message, abandon non-xmodem message, and when the Boot of variant loader utility receives, Boot loader utility to the above-mentioned variant received is carried out verification, and when the verification failure, resend the version updating request to client, when verification succeeds, carry out the Boot loader utility of above-mentioned variant, the driving that provides according to the Boot loader utility of above-mentioned variant, the corresponding port of initialization, and by above-mentioned port, the html page that the Boot loader utility of above-mentioned variant is provided sends to client, and in the Boot loader utility process of carrying out variant, when receiving the message that client issues, judge whether TCP/IP message of above-mentioned message, and when above-mentioned message is the TCP/IP message, the protocol type of judging above-mentioned message is HTTP whether, when above-mentioned message is the TCP/IP message of HTTP type, the version file data in the above-mentioned message are deposited in the internal memory; Be non-TCP/IP message or during for the TCP/IP message of non-HTTP type at above-mentioned message, abandon above-mentioned message, after version file receives, according to the method that the Boot loader utility of above-mentioned variant provides, above-mentioned version file is carried out verification, and after verification succeeds, above-mentioned version file is saved among the local Flash, enable simultaneously the above-mentioned version file in the internal memory, when the verification failure, prompting verification failure in the WEB of the machine page.
As shown in Figure 2, be the preferred embodiment flow chart of client-side in the method for updating edition of embedded device of the present invention, the Boot loader utility of having preserved variant on the present embodiment hypothesis client may further comprise the steps:
Step S000: the version updating request of receiving embedded device;
In the present embodiment, above-mentioned version updating request is the xmodem request.
Step S001: the Boot loader utility burst of variant is handed down to above-mentioned embedded device by the xmodem message;
Step S002: receive html page, show that above-mentioned html page is to the user;
Step S003: wait for that the user imports version file;
Step S004: detect the user and import version file;
The user all can log in the WEB page of above-mentioned embedded device by the IP address of the above-mentioned embedded device of input in the address field of client browser in any time after receiving html page, understands the dynamic of above-mentioned embedded device.
Step S005: the TCP/IP message by the HTTP type is handed down to above-mentioned embedded device with the version file burst.
As shown in Figure 3, be the preferred embodiment flow chart of embedded device side in the method for updating edition of embedded device of the present invention, the present embodiment may further comprise the steps:
Step S100: detect and to carry out version updating;
Version updating may be that for example the default key is pressed owing to default external event occurs to cause, and perhaps the user is by calling the WEB page of embedded device, input version updating order etc. in client; Also may local version is unavailable cause, such as version is unusual, version is lost etc.
Step S101: send the version updating request to client;
Owing to by using the serial communication of xmodem agreement, asking therefore the version updating request is xmodem between embedded device and the client.
Step S102: receive the message that client issues;
Step S103: judge whether xmodem message of above-mentioned message, if, execution in step S105 then; Otherwise, execution in step S104;
Step S104: abandon above-mentioned message, execution in step S102;
Step S105: sequentially be saved in internal memory according to reception the Boot loader utility data of the variant in the above-mentioned xmodem message;
Step S106: judge whether end message of above-mentioned xmodem message, if, execution in step S107 then, otherwise, execution in step S102 continued;
Step S107: the Boot loader utility to the variant in the internal memory is carried out verification;
Step S108: judge whether verification succeeds, if, execution in step S109 then; Otherwise, execution in step S101;
Above step belongs to the boot flow of embedded device.
After the verification succeeds, namely begin to carry out the Boot loader utility of above-mentioned variant; The WEB service procedure of following steps for carrying out under the Boot of variant Loader environment, the WEB service processes is carried out in idle process.
Step S109: according to the driving that the Boot loader utility of above-mentioned variant provides, the corresponding port of initialization;
Step S110: by above-mentioned port, the html page that the Boot loader utility of above-mentioned variant is provided sends to client;
Step S111: receive the message that client issues;
Step S112: judge whether TCP/IP message of above-mentioned message, if, execution in step S113 then; Otherwise, execution in step S114;
Step S113: the protocol type of judging above-mentioned message is HTTP whether, if, execution in step S115 then; Otherwise, execution in step S114:
Step S114: abandon above-mentioned message, continue execution in step S011;
Step S115: sequentially be saved in internal memory according to reception the version file data in the above-mentioned message;
Step S116: judge whether end message of above-mentioned message, if, execution in step S117 then, otherwise, execution in step S111 continued;
Step S117: according to the method that the Boot loader utility of described variant provides, the version file in the internal memory is carried out verification;
Integrality and the legitimacy of this step verification version file, method of calibration can be CRC (Cyclicredundancy check, cyclic redundancy check (CRC)) or SUM (SUMmation, verification and) etc.
Step S118: judge whether verification succeeds, if, execution in step S119 then; Otherwise, execution in step S120;
Step S119: above-mentioned version file is deposited among the local Flash in addition, enabled simultaneously the version file in the internal memory;
Variant Boot loader utility of the present invention can directly start from internal memory, and does not need need to guide from ROM and could start as existing standard Boot loader utility.
Step S120: prompting verification failure in the WEB of the machine page.
Above-mentioned explanation illustrates and has described the preferred embodiments of the present invention, but as previously mentioned, be to be understood that the present invention is not limited to the disclosed form of this paper, should not regard the eliminating to other embodiment as, and can be used for various other combinations, modification and environment, and can in invention contemplated scope described herein, change by technology or the knowledge of above-mentioned instruction or association area.And the change that those skilled in the art carry out and variation do not break away from the spirit and scope of the present invention, then all should be in the protection range of claims of the present invention.
Claims (10)
1. the method for updating edition of an embedded device, it is characterized in that, described method is stored in client with the Boot loader utility of variant, when client is received the version updating request of embedded device, the Boot loader utility of described variant is handed down to described embedded device;
Described embedded device is carried out the Boot loader utility of the variant of receiving, carries out version updating.
2. method according to claim 1 is characterized in that, described version updating request is the xmodem request.
3. method according to claim 1, it is characterized in that, described client is handed down to described embedded device by the xmodem message with the Boot loader utility burst of described variant, when described embedded device is received message, judge whether xmodem message of described message, if then the Boot loader utility data with the variant in the described xmodem message are saved in the internal memory, otherwise, abandon described message.
4. each described method according to claim 1-3, it is characterized in that, described embedded device is after the Boot of variant loader utility receives, also the Boot loader utility of described variant is carried out verification, if verification succeeds, then carry out the Boot loader utility of described variant, otherwise, again send the version updating request to described client.
5. method according to claim 4 is characterized in that, the Boot loader utility that described embedded device is carried out described variant is carried out the version updating step and is specially:
According to the driving that the Boot loader utility of described variant provides, the corresponding port of initialization;
By described port, the text mark language html page that the Boot loader utility of described variant is provided sends to described client;
Wait for that described client issues version file;
The version file data of receiving are saved in the internal memory;
After version file receives, according to the method that the Boot loader utility of described variant provides, described version file is carried out verification;
If verification succeeds is then deposited described version file among the local Flash in addition, enable simultaneously the version file in the internal memory; If the verification failure, then prompting verification failure in the WEB of the machine page.
6. method according to claim 5 is characterized in that, after described client is received html page, described html page is shown to the user and waits for that the user imports version file;
After detecting the user and importing version file, by transmission control protocol/Internet Interconnection agreement TCP/IP message described version file burst is handed down to described embedded device.
7. method according to claim 6 is characterized in that, after described embedded device is received message, also carries out following operation:
Judge whether TCP/IP message of described message, if the protocol type of then judging described message is HTML (Hypertext Markup Language) HTTP whether, if then the version file data in the described message are deposited in the internal memory; Otherwise, abandon described message.
8. the version updating system of an embedded device comprises client and embedded device, it is characterized in that,
Described client is used for the Boot loader utility of storage variant, and when the version updating request of receiving embedded device, and the Boot loader utility of described variant is handed down to described embedded device;
Described embedded device is used for sending the version updating request to described client when needs carry out version updating, and carries out the Boot loader utility of the variant of receiving, carries out version updating.
9. system according to claim 8 is characterized in that,
Described client is used for by the xmodem message Boot loader utility burst of described variant being handed down to described embedded device, and the interface that the Boot loader utility of revising described variant is provided for the user;
Described embedded device, be used in request stage, judge whether xmodem message of the message receive, and the Boot loader utility data of the variant in the xmodem message are saved in the internal memory, abandon non-xmodem message, and the Boot loader utility of the variant received carried out verification, and when the verification failure, resend the version updating request to described client.
10. according to claim 8 or 9 described systems, it is characterized in that,
Described client is used for after receiving html page, and described html page is shown to the user and after detecting the user and importing version file, by the TCP/IP message described version file burst is handed down to described embedded device;
Described embedded device, be used for the driving that the Boot loader utility according to described variant provides, the corresponding port of initialization, and by described port, the html page that the Boot loader utility of described variant is provided sends to described client, and in the Boot loader utility process of carrying out variant, when receiving the message that client issues, judge whether TCP/IP message of described message, and when described message is the TCP/IP message, the protocol type of judging described message is HTTP whether, when described message is the TCP/IP message of HTTP type, the version file data in the described message is deposited in the internal memory; Be non-TCP/IP message or during for the TCP/IP message of non-HTTP type at described message, abandon described message, after version file receives, according to the method that the Boot loader utility of described variant provides, described version file is carried out verification, and when verification succeeds, described version file is deposited among the local Flash in addition, enable described version file from internal memory simultaneously, when the verification failure, prompting verification failure in the WEB of the machine page.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011102427879A CN102957669A (en) | 2011-08-23 | 2011-08-23 | Version updating method and version updating system for embedded equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011102427879A CN102957669A (en) | 2011-08-23 | 2011-08-23 | Version updating method and version updating system for embedded equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102957669A true CN102957669A (en) | 2013-03-06 |
Family
ID=47765904
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011102427879A Pending CN102957669A (en) | 2011-08-23 | 2011-08-23 | Version updating method and version updating system for embedded equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102957669A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109828769A (en) * | 2018-12-24 | 2019-05-31 | 同济大学 | A kind of embedded program remote update system and method based on TCP/IP |
| CN116599953A (en) * | 2023-07-13 | 2023-08-15 | 苏州浪潮智能科技有限公司 | File uploading method, device, system, equipment and readable storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0450462A2 (en) * | 1990-04-04 | 1991-10-09 | Eastman Kodak Company | System for updating software in automatic film processor |
| CN101216773A (en) * | 2008-01-09 | 2008-07-09 | 深圳国人通信有限公司 | Embedded Linux system firmware downloading method and device |
| CN101557583A (en) * | 2009-03-19 | 2009-10-14 | 珠海银邮光电技术发展股份有限公司 | Remote-updating and version-switching method of repeater equipment embedded software |
| CN102043652A (en) * | 2010-12-08 | 2011-05-04 | 苏州捷泰科信息技术有限公司 | Processing system and method for embedded device root file system |
| CN102075564A (en) * | 2010-12-23 | 2011-05-25 | 李华嵩 | Remote software upgrading technique |
-
2011
- 2011-08-23 CN CN2011102427879A patent/CN102957669A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0450462A2 (en) * | 1990-04-04 | 1991-10-09 | Eastman Kodak Company | System for updating software in automatic film processor |
| CN101216773A (en) * | 2008-01-09 | 2008-07-09 | 深圳国人通信有限公司 | Embedded Linux system firmware downloading method and device |
| CN101557583A (en) * | 2009-03-19 | 2009-10-14 | 珠海银邮光电技术发展股份有限公司 | Remote-updating and version-switching method of repeater equipment embedded software |
| CN102043652A (en) * | 2010-12-08 | 2011-05-04 | 苏州捷泰科信息技术有限公司 | Processing system and method for embedded device root file system |
| CN102075564A (en) * | 2010-12-23 | 2011-05-25 | 李华嵩 | Remote software upgrading technique |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109828769A (en) * | 2018-12-24 | 2019-05-31 | 同济大学 | A kind of embedded program remote update system and method based on TCP/IP |
| CN109828769B (en) * | 2018-12-24 | 2022-02-18 | 同济大学 | Embedded program remote updating system and method based on TCP/IP |
| CN116599953A (en) * | 2023-07-13 | 2023-08-15 | 苏州浪潮智能科技有限公司 | File uploading method, device, system, equipment and readable storage medium |
| CN116599953B (en) * | 2023-07-13 | 2024-02-02 | 苏州浪潮智能科技有限公司 | File uploading method, device, system, equipment and readable storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8442509B2 (en) | System and method for managing a wireless device from removable media with processing capability | |
| KR101768236B1 (en) | A method and arrangements for application scope management | |
| CN101593119B (en) | Method and device for firmware over-the-air of exclusive flash memory combined equipment | |
| RU2009132388A (en) | AGREEMENT OF DOWNLOAD BETWEEN MULTIPLE DEVICES ABLE TO DOWNLOAD | |
| CN104750515A (en) | Firmware version upgrading method and system | |
| CN104243479A (en) | Peripheral integration device and method | |
| RU2006134628A (en) | PERFORMANCE OF UNVERIFIED PROGRAMS IN THE OPERATIONAL ENVIRONMENT OF A RADIO COMMUNICATION DEVICE | |
| KR20130108613A (en) | Method and device for interprocess communication and computer storage medium | |
| CN106708748B (en) | Method and system for improving mounting performance of OpenStack block storage volume | |
| CN104965744A (en) | System upgrading method and embedded system | |
| US9820310B2 (en) | Network connection method and system | |
| CN102957669A (en) | Version updating method and version updating system for embedded equipment | |
| US9509431B2 (en) | Method and apparatus for controlling an optical network unit to restart upon completion of downloading new software | |
| CN105320534B (en) | BOOT remote upgrading method, device and system for single board | |
| CN107547285B (en) | Configuration information storage method and device | |
| CN103442041A (en) | Method, device and system for upgrading firmware of embedded device | |
| CN103530159A (en) | Upgrading method and system of wireless communication module | |
| CN111352642B (en) | Service equipment and service software upgrading method | |
| CN102890635A (en) | Method and device for loading digital signal processor | |
| WO2013004175A1 (en) | Software upgrading method and apparatus for electronic devices | |
| US20120047521A1 (en) | Electronic device and data collection method of the electronic device | |
| CN105704707A (en) | Slave equipment and air upgrading method thereof | |
| KR100524588B1 (en) | succeeding method of data in mobile | |
| CN106445599B (en) | Application program upgrading method and device and terminal | |
| WO2017076258A1 (en) | Smart card and application downloading 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20130306 |