CN107526673B - Method for testing log backup memory of storage system - Google Patents
Method for testing log backup memory of storage system Download PDFInfo
- Publication number
- CN107526673B CN107526673B CN201710739308.1A CN201710739308A CN107526673B CN 107526673 B CN107526673 B CN 107526673B CN 201710739308 A CN201710739308 A CN 201710739308A CN 107526673 B CN107526673 B CN 107526673B
- Authority
- CN
- China
- Prior art keywords
- test
- log
- test file
- file
- size
- 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.)
- Active
Links
- 238000012360 testing method Methods 0.000 title claims abstract description 181
- 238000000034 method Methods 0.000 title claims abstract description 29
- 238000013461 design Methods 0.000 claims abstract description 62
- 230000003247 decreasing effect Effects 0.000 claims description 9
- 230000000694 effects Effects 0.000 description 3
- 238000005259 measurement Methods 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
-
- 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/1471—Saving, restoring, recovering or retrying involving logging of persistent data for recovery
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method for testing a log backup memory of a storage system, which comprises the following steps: obtaining a design value N of a log backup memory; view original file size in log backup directory N1; copying a test file a into a log backup directory, wherein the size of the test file a is N2< N-N1; restarting a system log recorder, checking whether a test file a exists or not, if so, entering the next step, and if not, ending the test; copying a test file b into a log backup directory, wherein the size of the test file b is N3-N1-N2; restarting a system log recorder, checking whether an original file exists or not, if not, entering the next step, and if so, ending the test; copying a test file c into a log backup directory, wherein the test file c has the size N4> N-N2-N3; and restarting the system log recorder to check whether the test file a exists. The test is carried out by operating the directory storing the log backup in the system, so that the test time of the size of the memory is greatly shortened, and the working efficiency is improved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method for testing a log backup memory of a storage system.
Background
When the storage system is in a problem, a system log provides problem analysis guarantee for customer service staff in the repairing process, and the customer service staff can analyze the system according to the system log to check the previous operation records of the system so as to quickly locate the problem and solve the problem. In order to prevent log loss due to system problems, the log needs to be backed up.
Therefore, the backup of the log is crucial in the storage system. In the memory size test of log backup, the memory size of the log backup needs to be accurately tested to ensure that when the backup of the log is up to a few, the system can automatically delete the older log backup to make enough space for the new log backup to perform the log backup, and provide the desired log for customer service and research and development personnel to perform problem analysis.
Generally, in the process of testing the size of a log backup memory, a directory storing a log backup file needs to be tested, then a storage system is operated to generate a system log, and the log is backed up and stored in the directory of the log backup.
Disclosure of Invention
In order to solve the problems, the method for testing the memory of the log backup of the storage system is provided, and the directory for storing the log backup in the system is operated to test, so that the time for testing the size of the memory is greatly shortened, and the working efficiency is improved.
The embodiment of the invention provides a method for testing a log backup memory of a storage system, which comprises the following steps:
obtaining a design value N of a log backup memory;
view original file size in log backup directory N1;
copying a test file a into a log backup directory, wherein the size of the test file a is N2< N-N1;
restarting a system log recorder, checking whether a test file a exists, if so, entering the next step, if not, indicating that the log backup memory is smaller than a design value, and ending the test;
copying a test file b into a log backup directory, wherein the size of the test file b is N3-N1-N2;
restarting a system log recorder, checking whether an original file exists or not, if not, entering the next step, if so, indicating that the log backup memory is larger than a design value, and ending the test;
copying a test file c into a log backup directory, wherein the test file c has the size N4> N-N2-N3;
and restarting the system log recorder, checking whether the test file a exists, if not, indicating that the log backup memory is equal to a design value, finishing the test, if so, indicating that the log backup memory is greater than the design value, and finishing the test.
Further, if the size of the log backup memory is not equal to the design value, the test file is increased or decreased by the set minimum unit until the size of the log backup memory is measured.
Preferably, the files in the test file a, the log backup memory and the log backup directory satisfy the following relationship: N-N1-N2 is more than or equal to 1 and less than or equal to 2.
Further, the test file a comprises a plurality of files.
The embodiment of the invention also provides a method for testing the log backup memory of the storage system, which comprises the following steps:
obtaining the design size N of a log backup memory;
clearing files in the log backup catalog;
copying a test file a into a log backup directory, wherein the size of the test file a is N2< N;
restarting a system log recorder, checking whether a test file a exists, if so, entering the next step, if not, indicating that the log backup memory is smaller than a design value, and ending the test;
copying a test file b into a log backup directory, wherein the size of the test file b is N3-N2;
restarting a system log recorder, checking whether a test file a exists or not, if not, entering the next step, if so, indicating that the log backup memory is larger than a design value, and ending the test;
copying a test file c into a log backup directory, wherein the test file c has the size N4> N-N3;
and restarting the system log recorder, checking whether the test file b exists, if not, indicating that the log backup memory is equal to a design value, finishing the test, and if so, indicating that the log backup memory is greater than the design value, and finishing the test.
Further, if the size of the log backup memory is not equal to the design value, the test file is increased or decreased by the set minimum unit until the size of the log backup memory is measured.
Preferably, the test file a and the log backup memory satisfy the following relationship: N-N2 is more than or equal to 1 and less than or equal to 2.
Further, the test file a comprises a plurality of files.
The effect provided in the summary of the invention is only the effect of the embodiment, not all the effects of the invention, and one of the above technical solutions has the following advantages or beneficial effects:
1. according to the scheme, the test is not performed after the log is generated by long-time operation of the system, and only the size of the memory of the directory storing the log backup is tested.
2. For the memory which does not conform to the design value, the size of the accurate log backup memory can be ensured by increasing or decreasing the test file with the minimum unit, and the guarantee is provided for later customer service and research and development personnel to solve the problem.
3. The test file a is composed of a plurality of files, the size of the deleted file of the test file a is smaller in the test process, refinement of the test can be guaranteed, meanwhile, under the same size, the copying speed of the plurality of small files is far faster than that of a single large file, and the test efficiency can be improved.
Drawings
FIG. 1 is a flow diagram of a method of one embodiment of the invention;
fig. 2 is a flow chart of a method of another embodiment of the present invention.
Detailed Description
In order to clearly explain the technical features of the present invention, the following detailed description of the present invention is provided with reference to the accompanying drawings. The following disclosure provides many different embodiments, or examples, for implementing different features of the invention. To simplify the disclosure of the present invention, the components and arrangements of specific examples are described below. Furthermore, the present invention may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed. It should be noted that the components illustrated in the figures are not necessarily drawn to scale. Descriptions of well-known components and processing techniques and procedures are omitted so as to not unnecessarily limit the invention.
Example 1
As shown in fig. 1, a method for testing a backup memory of a storage system log includes the following steps:
1. and acquiring a design value N of the log backup memory. For example, if a storage system is a system, the storage directory of the log backup of the system is/mnt/disk 3/log/bkup, and if the storage log backup of the system is 15M at most, the generated log backup files are all in the directory/bkup.
2. View file size N1 in the log backup directory. In the directory/bkup, a file is found, with a file size of 5M.
3. Copy test file a into the log backup directory, the test file a having a size N2< N-N1. The test file a is file1, the file1 is copied to the/mnt/disk 3/log/bkup directory, and the file1 file size is 8M.
Preferably, the files in the test file a, the log backup memory and the log backup directory satisfy the following relationship: N-N1-N2 is more than or equal to 1 and less than or equal to 2. The unit in the formula is mega, and the condition is set so as to be as close to the design value of the memory as possible when the test file a is copied for the first time, and inaccurate measurement caused by small difference between the design value and the actual value is avoided. For example, the design value is 15M, the actual value is 13M, if the sum of the file in the memory and the test file is less than 10M, the value of 13M cannot be measured, and if the maximum reserved in the formula does not exceed 2M of the free memory, the value of 13M can be measured.
It should be noted here that, since the design value of the illustrated sub-memory is only 15M, the test file a itself is relatively small, only one file is needed, when the design value of the memory is relatively large, for example, 100M, a single file meeting the requirements has several tens of megabytes, the copying speed is relatively slow, a plurality of files can be selected to form the test file a, on one hand, the refinement of the test can be ensured, and on the other hand, under the same size, the copying speed of a plurality of small files is much faster than that of a single large file, so that the test efficiency can be improved.
4. And restarting the system log recorder, checking whether the test file a exists, entering the next step if the test file a exists, and ending the test if the test file a does not exist and the log backup memory is smaller than the design value. If the test file a is composed of a plurality of files, whether all the files in the test file a are complete or not needs to be checked, if the files are complete, the next step is carried out, if the test file a is incomplete, the log backup memory is smaller than a design value, and the test is finished.
5. And copying a test file b into the log backup directory, wherein the size of the test file b is N3-N1-N2. This step is to test whether the actual value and the design value are not equal, for example, the previous design value of 15M is stored in the 5M original file and the 8M test file a, and then a 2M test file b needs to be prepared to see the situation when the memory reaches the design value.
6. And restarting the system log recorder, checking whether the original file exists, wherein in a normal aspect, if the design value of the memory is consistent with the actual value, the original file is regarded as the file with the earliest time stored in the memory when the memory is full, and is deleted theoretically, if the original file is deleted indeed, the design value of the memory is consistent with the actual value, the oldest file is deleted after the memory is full, the next step is carried out, and if the original file is not deleted, the log backup memory is larger than the design value, and the test is finished.
7. Copying a test file c into the log backup directory, the test file c having a size N4> N-N1-N3. This step is to test the situation when the size of the stored file exceeds the design value of the memory, for example, the previous design value of 15M stores the 5M original file, the 8M test file a, and the 2M test file b, but the 5M original file has been deleted in the previous step, and then it is necessary to prepare a test file c exceeding 5M to see the situation when the memory exceeds the design value.
8. And restarting the system log recorder, checking whether the test file a exists, wherein normally, if the design value of the memory is consistent with the actual value, when the memory overflows, the test file a is used as the file with the earliest time stored in the memory and can be deleted theoretically, if the test file a is deleted indeed, the oldest file can be deleted after the memory overflows, the whole test is completed, and if the original file is not deleted, the log backup memory is larger than the design value, and the test is also finished.
In the whole process, if the size of the log backup memory is not equal to the design value, the test file is increased or decreased by the set minimum unit until the size of the log backup memory is measured. Generally, the minimum unit is fixed at 1M, that is, if the actual size is less than the design value, one million is decreased downwards until the actual memory value is found, and if the actual size is greater than the design value, one million is increased upwards until the actual memory value is found.
Example 2
As shown in fig. 2, an embodiment of the present invention further provides a method for testing a backup memory of a storage system log, where the method includes the following steps:
1. and obtaining the design size N of the log backup memory. For example, if a storage system is a system, the storage directory of the log backup of the system is/mnt/disk 3/log/bkup, and if the storage log backup of the system is 15M at most, the generated log backup files are all in the directory/bkup.
2. And clearing the files in the log backup directory. This step is to avoid the original files in the memory from being complicated and causing inaccurate test.
3. Copy test file a into the log backup directory, the test file a having a size N2< N. The test file a is file1, the file1 is copied to the/mnt/disk 3/log/bkup directory, and the file1 file size is 14M.
Preferably, the test file a and the log backup memory satisfy the following relationship: N-N2 is more than or equal to 1 and less than or equal to 2. The unit in the formula is mega, and the condition is set so as to be as close to the design value of the memory as possible when the test file a is copied for the first time, and inaccurate measurement caused by small difference between the design value and the actual value is avoided. For example, the design value is 15M, the actual value is 13M, if none of the test files a is 10M, the value of 13M cannot be measured, and if the maximum reserved in the formula does not exceed 2M of the free memory, the value of 13M can be measured.
It should be noted here that, since the design value of the illustrated sub-memory is only 15M, the test file a itself is relatively small, only one file is needed, when the design value of the memory is relatively large, for example, 100M, a single file meeting the requirements has several tens of megabytes, the copying speed is relatively slow, a plurality of files can be selected to form the test file a, on one hand, the refinement of the test can be ensured, and on the other hand, under the same size, the copying speed of a plurality of small files is much faster than that of a single large file, so that the test efficiency can be improved.
4. And restarting the system log recorder, checking whether the test file a exists, entering the next step if the test file a exists, and ending the test if the test file a does not exist and the log backup memory is smaller than the design value. If the test file a is composed of a plurality of files, whether all the files in the test file a are complete or not needs to be checked, if the files are complete, the next step is carried out, if the test file a is incomplete, the log backup memory is smaller than a design value, and the test is finished.
5. And copying a test file b into the log backup directory, wherein the size of the test file b is N3-N2. This step is to test whether the actual value and the design value are not equal, for example, the previous design value of 15M is stored in a 14M test file a, and then a test file b of 1M is prepared to see the situation when the memory reaches the design value.
6. And restarting the system log recorder, checking whether the test file a exists, wherein in a normal aspect, if the design value of the memory is consistent with the actual value, when the memory is full, the test file a is used as the file with the earliest time stored in the memory and can be deleted theoretically, if the test file a is deleted indeed, the design value of the memory is consistent with the actual value, the oldest file is deleted after the memory is full, the next step is carried out, and if the test file a is not deleted, the log backup memory is larger than the design value, and the test is finished.
7. Copying a test file c into the log backup directory, the test file c having a size N4> N-N3. This step is to test the situation when the size of the stored file exceeds the design value of the memory, for example, the previous design value of 15M stores the 14M test file a and the test file b of 1M, but the 14M test file a has been deleted in the previous step, and then it is necessary to prepare a test file c exceeding 14M to see the situation when the memory exceeds the design value.
8. And restarting the system log recorder, checking whether the test file b exists, wherein normally, if the design value of the memory is consistent with the actual value, when the memory overflows, the test file b is used as a file stored in the memory and having earlier time than the test file c, and is deleted theoretically, if the test file b is deleted indeed, the earliest old file is deleted after the memory overflows, the whole test is completed, and if the original file is not deleted, the log backup memory is larger than the design value, and the test is also finished.
In the whole process, if the size of the log backup memory is not equal to the design value, the test file is increased or decreased by the set minimum unit until the size of the log backup memory is measured. Generally, the minimum unit is fixed at 1M, that is, if the actual size is less than the design value, one million is decreased downwards until the actual memory value is found, and if the actual size is greater than the design value, one million is increased upwards until the actual memory value is found.
While the invention has been described in detail in the specification and drawings and with reference to specific embodiments thereof, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted; all technical solutions and modifications thereof which do not depart from the spirit and scope of the present invention are intended to be covered by the scope of the present invention.
Claims (8)
1. A method for testing a log backup memory of a storage system is characterized by comprising the following steps: the method comprises the following steps:
obtaining a design value N of a log backup memory;
view original file size in log backup directory N1;
copying a test file a into a log backup directory, wherein the size of the test file a is N2< N-N1;
restarting a system log recorder, checking whether a test file a exists or not, if so, entering the next step, and if not, ending the test;
copying a test file b into a log backup directory, wherein the size of the test file b is N3-N1-N2;
restarting a system log recorder, checking whether an original file exists or not, if not, entering the next step, and if so, ending the test;
copying a test file c into a log backup directory, wherein the test file c has the size N4> N-N2-N3;
and restarting the system log recorder, checking whether the test file a exists or not, if not, finishing the test, and if so, finishing the test.
2. The method for testing the backup memory of the storage system log according to claim 1, wherein: and if the size of the log backup memory is not equal to the design value, increasing or decreasing the test file by the set minimum unit until the size of the log backup memory is measured.
3. The method for testing the backup memory of the storage system log according to claim 1 or 2, wherein: the test file a, the log backup memory and the files in the log backup catalog satisfy the following relations: N-N1-N2 is more than or equal to 1M and less than or equal to 2M.
4. The method for testing the backup memory of the storage system log according to claim 1 or 2, wherein: the test file a comprises a plurality of files.
5. A method for testing a log backup memory of a storage system is characterized by comprising the following steps: the method comprises the following steps:
obtaining a design value N of a log backup memory;
clearing files in the log backup catalog;
copying a test file a into a log backup directory, wherein the size of the test file a is N2< N;
restarting a system log recorder, checking whether a test file a exists or not, if so, entering the next step, and if not, ending the test;
copying a test file b into a log backup directory, wherein the size of the test file b is N3-N2;
restarting a system log recorder, checking whether a test file a exists or not, if not, entering the next step, and if so, ending the test;
copying a test file c into a log backup directory, wherein the test file c has the size N4> N-N3;
and restarting the system log recorder, checking whether the test file b exists or not, if not, finishing the test, and if so, finishing the test.
6. The method for testing the backup memory of the storage system log according to claim 5, wherein: and if the size of the log backup memory is not equal to the design value, increasing or decreasing the test file by the set minimum unit until the size of the log backup memory is measured.
7. The method for testing the backup memory of the storage system log according to claim 5 or 6, wherein: the test file a and the log backup memory satisfy the following relationship: N-N2 is more than or equal to 1M and less than or equal to 2M.
8. The method for testing the backup memory of the storage system log according to claim 5 or 6, wherein: the test file a comprises a plurality of files.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710739308.1A CN107526673B (en) | 2017-08-25 | 2017-08-25 | Method for testing log backup memory of storage system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710739308.1A CN107526673B (en) | 2017-08-25 | 2017-08-25 | Method for testing log backup memory of storage system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107526673A CN107526673A (en) | 2017-12-29 |
| CN107526673B true CN107526673B (en) | 2021-02-02 |
Family
ID=60682112
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710739308.1A Active CN107526673B (en) | 2017-08-25 | 2017-08-25 | Method for testing log backup memory of storage system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107526673B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109189610B (en) * | 2018-08-16 | 2021-10-29 | 郑州云海信息技术有限公司 | Method for processing server monitoring data under linux |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5313604A (en) * | 1990-11-13 | 1994-05-17 | Hewlett-Packard Company | Method for locating compressed data in a computed memory back up device including steps of refining estimater location |
| US20120221896A1 (en) * | 2009-08-28 | 2012-08-30 | International Business Machines Corporation | Generation of realistic file content changes for deduplication testing |
| CN105589928A (en) * | 2015-12-02 | 2016-05-18 | 中国银联股份有限公司 | Simulation testing method for distributed data processing system |
| CN105630672A (en) * | 2015-12-16 | 2016-06-01 | 北京奇虎科技有限公司 | Automatic application monitoring method and device |
-
2017
- 2017-08-25 CN CN201710739308.1A patent/CN107526673B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5313604A (en) * | 1990-11-13 | 1994-05-17 | Hewlett-Packard Company | Method for locating compressed data in a computed memory back up device including steps of refining estimater location |
| US20120221896A1 (en) * | 2009-08-28 | 2012-08-30 | International Business Machines Corporation | Generation of realistic file content changes for deduplication testing |
| CN105589928A (en) * | 2015-12-02 | 2016-05-18 | 中国银联股份有限公司 | Simulation testing method for distributed data processing system |
| CN105630672A (en) * | 2015-12-16 | 2016-06-01 | 北京奇虎科技有限公司 | Automatic application monitoring method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107526673A (en) | 2017-12-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11321081B2 (en) | Affinity recommendation in software lifecycle management | |
| US10437703B2 (en) | Correlation of source code with system dump information | |
| US10635473B2 (en) | Setting support program, setting support method, and setting support device | |
| CN103473158A (en) | Disk pressure testing method for Linux server | |
| CN110008129B (en) | Reliability test method, device and equipment for storage timing snapshot | |
| US10976942B2 (en) | Versioning a configuration of data storage equipment | |
| WO2015154517A1 (en) | Software failure locating method, apparatus and equipment | |
| CN106997316B (en) | System and method for detecting abnormal increase of memory | |
| CN103902435A (en) | System and method for recording log events in server testing | |
| CN103984634A (en) | Memory unsteady state pressure test method of LINUX server | |
| CN107526673B (en) | Method for testing log backup memory of storage system | |
| CN110764960B (en) | Solid state disk firmware testing method | |
| CN106407123B (en) | A kind of automated testing method and device of server interface | |
| CN105630653A (en) | CPU vacancy rate determination method and device for Docker container | |
| US11151013B2 (en) | Systems and methods for performance evaluation of input/output (I/O) intensive enterprise applications | |
| CN116450418B (en) | Breakpoint difference synchronization method and system based on volume backup and volume real-time backup method | |
| CN103279408A (en) | RAID (redundant array of inexpensive disk) performance testing method | |
| CN103400602A (en) | Automatic hard disk bad track repairing method and equipment | |
| US10382311B2 (en) | Benchmarking servers based on production data | |
| CN116820932A (en) | BMC fault diagnosis method, device, equipment and medium | |
| CN114968753A (en) | Equipment upgrading test method, medium, electronic equipment and test system | |
| US10936400B2 (en) | Dynamic handling of callhome data | |
| CN109344023B (en) | System and method for testing stability of USB3.0 interface of server | |
| JP5747755B2 (en) | Process relationship analysis program, process relationship analysis apparatus, and process relationship analysis method | |
| CN111338956A (en) | Automatic pressure measurement method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210113 Address after: Building 9, No.1, guanpu Road, Guoxiang street, Wuzhong Economic Development Zone, Wuzhong District, Suzhou City, Jiangsu Province Applicant after: SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd. Address before: Room 1601, floor 16, 278 Xinyi Road, Zhengdong New District, Zhengzhou City, Henan Province Applicant before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |