CN107357701B - SAS signal testing method and device under distributed scene - Google Patents
SAS signal testing method and device under distributed scene Download PDFInfo
- Publication number
- CN107357701B CN107357701B CN201710607061.8A CN201710607061A CN107357701B CN 107357701 B CN107357701 B CN 107357701B CN 201710607061 A CN201710607061 A CN 201710607061A CN 107357701 B CN107357701 B CN 107357701B
- Authority
- CN
- China
- Prior art keywords
- log file
- physical interface
- number information
- integrity
- file
- 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 70
- 238000000034 method Methods 0.000 claims abstract description 19
- 230000008569 process Effects 0.000 description 4
- 238000004422 calculation algorithm Methods 0.000 description 3
- 238000013112 stability test Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000008054 signal transmission Effects 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/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/26—Functional testing
- G06F11/273—Tester hardware, i.e. output processing circuits
- G06F11/2733—Test interface between tester and unit under test
-
- 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/3409—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 for performance assessment
- G06F11/3414—Workload generation, e.g. scripts, playback
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method and a device for testing SAS signals in a distributed scene, wherein the method comprises the steps of obtaining the error number information of a first physical interface of each storage node by running a test script; storing the error number information of the first physical interface to generate a first log file; after the test is finished, acquiring the error number information of the second physical interface of each storage node; storing the error number information of the second physical interface to generate a second log file; running a file integrity comparison instruction and judging whether the file integrity is consistent or not; if not, generating a new physical interface error; if so, no new physical interface error is generated. According to the method and the device, the collected physical interface error number information before and after the test is stored in two different log files, the integrity of the two log files is compared, the SAS signal is tested on line, extra instrument equipment and interrupt service are not needed, and the test accuracy and efficiency are improved.
Description
Technical Field
The invention relates to the field of testing, in particular to a method and a device for testing SAS signals in a distributed scene.
Background
Serial Attached SCSI (SAS) is a disk connection technology that uses a Serial communication protocol as a protocol infrastructure.
At present, distributed storage is widely applied, and a distributed storage application scene has the characteristics of complexity, huge cluster topology, different working load models and the like, so that the SAS link stability test of a distributed cluster is difficult.
The existing SAS link stability test of the distributed cluster generally requires additional equipment, such as an oscilloscope, and needs to be disassembled and shut down, i.e., the service needs to be interrupted during the test, so as to perform the SAS signal stability test for a long time. Thus, the accuracy and efficiency of the SAS signal test in a distributed scenario are necessarily low.
Disclosure of Invention
The invention aims to provide a method and a device for testing SAS signals in a distributed scene, and aims to solve the problem that the accuracy and efficiency of the SAS signal test in the existing distributed scene are low.
In order to solve the technical problem, the invention provides a method for testing an SAS signal in a distributed scenario, which comprises the following steps:
running a test script to obtain the error number information of the first physical interface of each storage node;
storing the error number information of the first physical interface to generate a first log file;
after the test is finished, acquiring the second physical interface error number information of each storage node;
storing the second physical interface error number information to generate a second log file;
running a file integrity comparison instruction, comparing the integrity of the first log file with the integrity of the second log file, and judging whether the file integrity is consistent;
if not, generating a new physical interface error; if so, no new physical interface error is generated.
Optionally, the running a file integrity comparison instruction, comparing the integrity of the first log file with the integrity of the second log file, and determining whether the file integrity is consistent includes:
and operating the file integrity comparison instruction, comparing md5 values of the first log file and the second log file in a preset time period, and judging whether the md5 values are the same.
Optionally, the storing the second physical interface error number information, and generating a second log file includes:
judging whether the second log file exists or not;
if the log file exists, deleting the first log file, and renaming the second log file to be the first log file;
and storing the second physical interface error number information to generate a new second log file.
In addition, the invention also provides a device for testing the SAS signal in the distributed scene, which comprises:
the first acquisition module is used for running the test script and acquiring the error number information of the first physical interface of each storage node;
the first log file generation module is used for storing the error number information of the first physical interface and generating a first log file;
the second acquisition module is used for acquiring the error number information of the second physical interface of each storage node after the test is finished;
the second log file generation module is used for storing the second physical interface error number information to generate a second log file;
the file integrity comparison module is used for operating a file integrity comparison instruction, comparing the integrity of the first log file with the integrity of the second log file and judging whether the file integrity is consistent; if not, generating a new physical interface error; if so, no new physical interface error is generated.
Optionally, the file integrity comparison module includes:
and an md5 value comparison unit, configured to run the file integrity comparison instruction, compare md5 values of the first log file and the second log file within a preset time period, and determine whether the md5 values are the same.
Optionally, the second log file generating module includes:
a judging unit, configured to judge whether the second log file exists;
a deleting unit configured to delete the first log file and rename the second log file to the first log file if the first log file exists;
and the generating unit is used for storing the second physical interface error number information to generate a new second log file.
The SAS signal testing method and device under the distributed scene provided by the invention obtain the information of the number of errors of the first physical interface of each storage node by running a testing script; storing the error number information of the first physical interface to generate a first log file; after the test is finished, acquiring the error number information of the second physical interface of each storage node; storing the error number information of the second physical interface to generate a second log file; running a file integrity comparison instruction, comparing the integrity of the first log file and the integrity of the second log file, and judging whether the file integrity is consistent; if not, generating a new physical interface error; if so, no new physical interface error is generated. According to the SAS signal online testing method and device, the collected physical interface error number information before and after testing is stored in two different log files, whether a newly-added physical interface error exists or not is judged by comparing the integrity of the two log files, whether an SAS link is stable or not is judged, whether the SAS signal is reliable or not is judged, the SAS signal is tested online, extra instrument equipment is not needed, service interruption is not needed, and therefore testing accuracy and efficiency can be improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic flowchart of an embodiment of a method for testing SAS signals in a distributed scenario according to an embodiment of the present invention;
fig. 2 is a schematic block diagram of a structure of an SAS signal testing apparatus in a distributed scenario according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a schematic flowchart illustrating an embodiment of a method for testing SAS signals in a distributed scenario according to the present invention, where the method includes the following steps:
step 101: and running the test script to acquire the error number information of the first physical interface of each storage node.
It is understood that the first physical interface error number information refers to PHY error number information, which may be actively recorded by an operating system on each node, for example, in a Linux system, using an smp-utils tool to monitor SAS PHY signal states of all expanders under the system, and recording PHY error number information based on a PHY error counter function, that is, recording the number of errors in each PHY signal transmission.
And running a pre-written test script, wherein the script is mainly used for capturing the number information of the phy errors of each storage node at one time and recording and storing the captured information.
Step 102: and storing the error number information of the first physical interface to generate a first log file.
Step 103: and after the test is finished, acquiring the error number information of the second physical interface of each storage node.
After the SAS signal test is completed according to the test requirement and the test time, the test script is used for capturing the number information of the phy errors of each storage node again, and the captured number information of the phy errors is recorded.
Step 104: and storing the error number information of the second physical interface to generate a second log file.
The post-test number of phy errors information is stored to a second log file, which may be named phy _ error _ log2, and the first log file storing the pre-test number of phy errors information may be named phy _ error _ log1 to distinguish from phy _ error _ log 2.
When a plurality of tests are carried out, a log file with the file name of phy _ error _ log2 may already exist, and at this time, the previous log file can be deleted, and a new log file can be regenerated.
In some embodiments of the present invention, the storing the second physical interface error number information, and the process of generating the second log file may specifically be: judging whether a second log file exists or not; if the log file exists, deleting the first log file, and renaming the second log file to be the first log file; and storing the error number information of the second physical interface to generate a new second log file.
It can be understood that a log file with a file name of ph _ error _ log2 may be set as a file for fixedly storing tested ph error information, and a log file with a file name of ph _ error _ log1 may be set as a file for fixedly storing tested ph error information, that is, ph _ error _ log1 is an old log file and ph _ error _ log2 is a new log file each time testing is performed.
Therefore, when the second log file already exists, for the convenience of comparison of subsequent files, the ph _ error _ log1 log file can be deleted, and the ph _ error _ log2 log file is renamed to ph _ error _ log1, so that new ph _ error information can be stored to generate a new log file of ph _ error _ log 2.
Of course, since the test script generates a log file under the directory/tmp each time the test script performs information capture, if there is no log file under the directory file at the beginning, it may generate a ph _ error _ log1, and if there is a ph _ error _ log1, it may generate a ph _ error _ log 2.
Step 105: running a file integrity comparison instruction, comparing the integrity of the first log file and the integrity of the second log file, and judging whether the file integrity is consistent; if not, generating a new physical interface error; if so, no new physical interface error is generated.
The file integrity comparison instruction may specifically be MD5sum/tmp/phy _ error _ log, and the integrity of the two files is compared, that is, the MD5(Message Digest Algorithm, MD5) values of the two files are compared, and whether the MD5 values are the same is determined, so as to determine whether the file integrity is consistent.
Specifically, the process of comparing the integrity of the first log file with the integrity of the second log file by the above-mentioned running file integrity comparison instruction and determining whether the integrity of the files is consistent may be: and running a file integrity comparison instruction, comparing md5 values of the first log file and the second log file in a preset time period, and judging whether the md5 values are the same.
It can be understood that the preset time period can be set manually according to requirements, that is, the client can set the required comparison time autonomously according to the comparison requirements, so as to meet the personalized requirements of the client.
The Md5 value is a widely used term in the field of computer security to verify the integrity of a message or document. Specifically, the md5 values of the two files can be compared to determine whether the two files are complete.
When the integrity of the two log files is inconsistent, namely the md5 values are different, it can be judged that a new phy error is generated in the SAS signal testing process, so that the md5 values of the tested log file and the log file before testing are different, and then it can be judged that the tested SAS signal is poor in quality and low in reliability.
When the integrity of the two log files is consistent, it can be judged that no new phy error is generated in the SAS signal testing process, and then it can be judged that the quality of the SAS signal is good and the reliability is high.
In the SAS signal testing method under the distributed scenario provided by this embodiment, by running a test script, information of the number of errors of a first physical interface of each storage node is obtained; storing the error number information of the first physical interface to generate a first log file; after the test is finished, acquiring the error number information of the second physical interface of each storage node; storing the error number information of the second physical interface to generate a second log file; running a file integrity comparison instruction, comparing the integrity of the first log file and the integrity of the second log file, and judging whether the file integrity is consistent; if not, generating a new physical interface error; if so, no new physical interface error is generated. The number information of the physical interface errors before and after the collected test is stored in two different log files, and whether a newly added physical interface error exists is judged by comparing the integrity of the two log files, so that whether an SAS link is stable or not and whether an SAS signal is reliable or not are judged, the SAS signal is tested on line, extra instrument equipment is not used, the service is not interrupted, and the test accuracy and efficiency can be improved.
In the following, the SAS signal testing apparatus in a distributed scenario provided by the embodiment of the present invention is introduced, and the SAS signal testing apparatus in a distributed scenario described below and the SAS signal testing method in a distributed scenario described above may be referred to correspondingly.
Referring to fig. 2, fig. 2 is a schematic block diagram of a structure of an SAS signal testing apparatus under a distributed scenario according to an embodiment of the present invention, where the apparatus includes:
the first obtaining module 21 is configured to run a test script and obtain information on the number of errors of the first physical interface of each storage node;
the first log file generating module 22 is configured to store the first physical interface error number information, and generate a first log file;
the second obtaining module 23 is configured to obtain information about the number of errors of the second physical interface of each storage node after the test is completed;
the second log file generation module 24 is configured to store the second physical interface error number information, and generate a second log file;
the file integrity comparison module 25 is used for running a file integrity comparison instruction, comparing the integrity of the first log file with the integrity of the second log file and judging whether the file integrity is consistent; if not, generating a new physical interface error; if so, no new physical interface error is generated.
Optionally, the file integrity comparison module 25 includes:
and the md5 value comparison unit is used for running a file integrity comparison instruction, comparing md5 values of the first log file and the second log file in a preset time period, and judging whether the md5 values are the same.
Optionally, the second log file generating module 24 includes:
a judging unit, configured to judge whether a second log file exists;
a deleting unit configured to delete the first log file and rename the second log file to the first log file if the first log file exists;
and the generating unit is used for storing the information of the number of the errors of the second physical interface to generate a new second log file.
The SAS signal testing device under the distributed scenario provided by this embodiment stores the collected physical interface error number information before and after the test into two different log files, and determines whether there is an additional physical interface error by comparing the integrity of the two log files, thereby determining whether an SAS link is stable and whether an SAS signal is reliable, implementing online testing of SAS signals, without using additional instruments or equipment, and without interrupting service, and further improving testing accuracy and efficiency.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The SAS signal testing method and apparatus under the distributed scenario provided by the present invention are described in detail above. The principles and embodiments of the present invention are explained herein using specific examples, which are presented only to assist in understanding the method and its core concepts. It should be noted that, for those skilled in the art, it is possible to make various improvements and modifications to the present invention without departing from the principle of the present invention, and those improvements and modifications also fall within the scope of the claims of the present invention.
Claims (6)
1. A SAS signal testing method under a distributed scene is characterized by comprising the following steps:
running a test script to obtain the error number information of the first physical interface of each storage node;
storing the error number information of the first physical interface to generate a first log file;
after the test is finished, acquiring the second physical interface error number information of each storage node;
storing the second physical interface error number information to generate a second log file;
running a file integrity comparison instruction, comparing the integrity of the first log file with the integrity of the second log file, and judging whether the file integrity is consistent;
if not, generating a new physical interface error; if yes, no new physical interface error is generated;
the physical interface error number information is the number information of the phy error.
2. The method for testing the SAS signal under the distributed scenario as claimed in claim 1, wherein the running the file integrity comparison instruction to compare the integrity of the first log file and the integrity of the second log file and determine whether the file integrity is consistent comprises:
and operating the file integrity comparison instruction, comparing md5 values of the first log file and the second log file in a preset time period, and judging whether the md5 values are the same.
3. The method for testing SAS signals under distributed scenarios according to claim 1 or 2, wherein the storing the second physical interface error number information and generating a second log file comprises:
judging whether the second log file exists or not;
if the log file exists, deleting the first log file, and renaming the second log file to be the first log file;
and storing the second physical interface error number information to generate a new second log file.
4. An SAS signal testing device under distributed scene, characterized by comprising:
the first acquisition module is used for running the test script and acquiring the error number information of the first physical interface of each storage node;
the first log file generation module is used for storing the error number information of the first physical interface and generating a first log file;
the second acquisition module is used for acquiring the error number information of the second physical interface of each storage node after the test is finished;
the second log file generation module is used for storing the second physical interface error number information to generate a second log file;
the file integrity comparison module is used for operating a file integrity comparison instruction, comparing the integrity of the first log file with the integrity of the second log file and judging whether the file integrity is consistent; if not, generating a new physical interface error; if yes, no new physical interface error is generated;
the physical interface error number information is the number information of the phy error.
5. The apparatus for testing SAS signals under distributed scenarios as recited in claim 4, wherein the file integrity comparison module comprises:
and an md5 value comparison unit, configured to run the file integrity comparison instruction, compare md5 values of the first log file and the second log file within a preset time period, and determine whether the md5 values are the same.
6. The SAS signal testing device under distributed scenario of claim 4 or 5, wherein the second log file generation module includes:
a judging unit, configured to judge whether the second log file exists;
a deleting unit configured to delete the first log file and rename the second log file to the first log file if the first log file exists;
and the generating unit is used for storing the second physical interface error number information to generate a new second log file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710607061.8A CN107357701B (en) | 2017-07-24 | 2017-07-24 | SAS signal testing method and device under distributed scene |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710607061.8A CN107357701B (en) | 2017-07-24 | 2017-07-24 | SAS signal testing method and device under distributed scene |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107357701A CN107357701A (en) | 2017-11-17 |
| CN107357701B true CN107357701B (en) | 2020-10-23 |
Family
ID=60284638
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710607061.8A Active CN107357701B (en) | 2017-07-24 | 2017-07-24 | SAS signal testing method and device under distributed scene |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107357701B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108958775A (en) * | 2018-07-18 | 2018-12-07 | 郑州云海信息技术有限公司 | A kind of detection method of SAS holding firmware online upgrading reliability |
| CN111223516B (en) * | 2019-12-26 | 2021-09-07 | 曙光信息产业(北京)有限公司 | RAID card detection method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103488945A (en) * | 2013-09-24 | 2014-01-01 | 曙光信息产业(北京)有限公司 | Authentication method and device for kernel in operation system of firewall |
| CN105843916A (en) * | 2016-03-24 | 2016-08-10 | 上海上讯信息技术股份有限公司 | Sensitive data detection method and equipment based on file merging |
| CN106502897A (en) * | 2016-10-24 | 2017-03-15 | 北京润科通用技术有限公司 | Test model generation method and device |
| CN106844114A (en) * | 2016-12-14 | 2017-06-13 | 合网络技术（北京）有限公司 | The monitoring method and device of interface testing stability |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8775876B2 (en) * | 2011-11-22 | 2014-07-08 | Lsi Corporation | Method to improve I/O reliability on a degraded wide port connection |
| CN103164289A (en) * | 2011-12-09 | 2013-06-19 | 鸿富锦精密工业（深圳）有限公司 | Switching method and switching system for physical layer of storage device |
-
2017
- 2017-07-24 CN CN201710607061.8A patent/CN107357701B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103488945A (en) * | 2013-09-24 | 2014-01-01 | 曙光信息产业(北京)有限公司 | Authentication method and device for kernel in operation system of firewall |
| CN105843916A (en) * | 2016-03-24 | 2016-08-10 | 上海上讯信息技术股份有限公司 | Sensitive data detection method and equipment based on file merging |
| CN106502897A (en) * | 2016-10-24 | 2017-03-15 | 北京润科通用技术有限公司 | Test model generation method and device |
| CN106844114A (en) * | 2016-12-14 | 2017-06-13 | 合网络技术（北京）有限公司 | The monitoring method and device of interface testing stability |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107357701A (en) | 2017-11-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109634258B (en) | Bus message checking method, device and system for hardware-in-loop test | |
| CN108459850B (en) | Method, device and system for generating test script | |
| CN109522181B (en) | Performance test method, device and equipment of distributed storage system | |
| CN111880508A (en) | Automatic calibration and test method and device for T-box parameters | |
| CN107357701B (en) | SAS signal testing method and device under distributed scene | |
| WO2021169280A1 (en) | Virtual disk check code generation method, apparatus and device, and storage medium | |
| CN110019067A (en) | A kind of log analysis method and system | |
| CN108628734B (en) | Functional program debugging method and terminal | |
| CN111427777B (en) | SOL test method, system, equipment and medium | |
| CN112148599A (en) | Performance pressure measurement method, device and equipment | |
| CN110147313B (en) | Log output method and device | |
| CN116662197A (en) | Automatic interface testing method, system, computer and readable storage medium | |
| CN113704087B (en) | File service testing method and device of cross-domain transmission equipment and electronic equipment | |
| CN114116351A (en) | Chip verification method, device, equipment and readable medium | |
| CN111211853B (en) | BMC time synchronization checking method and equipment | |
| CN103914377A (en) | Interface testing method and device | |
| CN114141302A (en) | Test method of solid state disk and electronic equipment | |
| CN113392021A (en) | Method, device and equipment for analyzing cluster reliability test result and readable medium | |
| CN110740134B (en) | URL authentication test method, device, equipment and medium | |
| CN113626325A (en) | Interface testing method, device and equipment in code iterative updating | |
| CN112506721A (en) | REST interface checking method, device, equipment and readable medium | |
| CN112492301A (en) | Performance test method and system of IPTV set top box | |
| CN111625449A (en) | File filtering rule testing method, device, equipment and readable storage medium | |
| CN111881021A (en) | Interface test method, device and system | |
| CN113722129B (en) | Storage reliability test method and related device |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200922 Address after: 215100 No. 1 Guanpu Road, Guoxiang Street, Wuzhong Economic Development Zone, Suzhou City, Jiangsu Province Applicant after: SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd. Address before: 450018 Henan province Zheng Dong New District of Zhengzhou City Xinyi Road No. 278 16 floor room 1601 Applicant before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |