CN110704828A - Verification method, device, equipment and computer readable storage medium - Google Patents
Verification method, device, equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN110704828A CN110704828A CN201910843038.8A CN201910843038A CN110704828A CN 110704828 A CN110704828 A CN 110704828A CN 201910843038 A CN201910843038 A CN 201910843038A CN 110704828 A CN110704828 A CN 110704828A
- Authority
- CN
- China
- Prior art keywords
- verification code
- verification
- target
- server
- rest layer
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
- G06F21/36—User authentication by graphic or iconic representation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2133—Verifying human interaction, e.g., Captcha
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a verification method, a verification device, verification equipment and a computer-readable storage medium, which are applied to cross-language middleware and comprise the following steps: when a user sends a verification code acquisition request to an REST layer through a client interface, receiving the verification code acquisition request sent by the REST layer; issuing the verification code acquisition request to a server side so that a target verification code is generated after the server side analyzes the verification code acquisition request; and after receiving the target verification code returned by the server, returning the target verification code to the REST layer, so that the user completes verification by using the target verification code after the REST layer returns the target verification code to the client interface. The method, the device, the equipment and the computer storage medium realize the interface access from the client to the server through the agent mechanism of the cross-language middleware.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a verification method, an apparatus, a device, and a computer-readable storage medium.
Background
Authentication codes are a public, fully automated program that distinguishes whether a user is a computer or a person. The place with the highest occurrence frequency of the verification codes in life is the entrance of the system, and the link of adding the verification codes during login can effectively prevent a hacker from continuously trying to login a certain specific registered user in a way of brute force cracking of a specific program.
In the prior art, the system login needs a verification code function, and the generation and verification of the verification code are completed in a system written by Python. The system login interface interacts with the REST layer written in the Java language. After the system login interface issues a request for acquiring the verification code to the REST layer, the REST layer needs to call the bottom layer to generate the verification code and return the verification code step by step to be displayed to the user, so that the user can conveniently input the verification code and then request the REST from the page again and then verify the REST to the bottom layer.
However, as shown in fig. 1, the REST layer written in Java language is not written in the same language as the bottom layer written in Python and is two different systems, so the interface call cannot be made directly. Therefore, the REST layer and the underlying server cannot interact with each other, so that the user cannot complete generation and verification of the verification code during system login.
In summary, it can be seen that how to make the REST layer interact with the underlying server is a problem to be solved at present.
Disclosure of Invention
The invention aims to provide a verification method, a verification device, verification equipment and a computer readable storage medium, which aim to solve the problem that a user cannot realize system verification because an REST layer and a bottom layer server cannot interact in the prior art.
In order to solve the above technical problem, the present invention provides a verification method applied to a cross-language middleware, comprising: when a user sends a verification code acquisition request to an REST layer through a client interface, receiving the verification code acquisition request sent by the REST layer; issuing the verification code acquisition request to a server side so that a target verification code is generated after the server side analyzes the verification code acquisition request; and after receiving the target verification code returned by the server, returning the target verification code to the REST layer, so that the user completes verification by using the target verification code after the REST layer returns the target verification code to the client interface.
Preferably, after receiving the target verification code returned by the server, returning the target verification code to the REST layer, so that after the REST layer returns the target verification code to the client interface, the user completes verification by using the target verification code includes:
after receiving the target verification code returned by the server, returning the target verification code to the REST layer so that the REST layer returns the target verification code to the client interface;
after the user inputs the target verification code and sends a verification code verification request to the REST layer through the client interface, receiving the verification code verification request sent by the REST layer;
issuing the verification code verification request to the server side so that the server side can analyze the verification code verification request, verify the target verification code and generate a verification result;
and after receiving the verification result returned by the server, returning the verification result to the REST layer so that the REST layer returns the verification result to the client interface.
Preferably, the server analyzes the verification code verification request, verifies the verification code to be verified, and generating a verification result includes:
the server analyzes the verification code verification request and verifies the target verification code;
when the target verification code is successfully verified, the server generates information of successful login, and returns the information of successful login to the cross-language middleware;
and when the target verification code fails to be verified, the server generates verification code error information and returns the verification code error information to the cross-language middleware.
Preferably, the cross-language middleware is ZeroC ICE.
Preferably, the cross-language middleware is hpose.
The invention also provides a verification device, which is applied to the cross-language middleware and comprises the following components:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving a verification code acquisition request sent by an REST layer when a user sends the verification code acquisition request to the REST layer through a client interface;
the issuing module is used for issuing the verification code acquisition request to a server so that a target verification code is generated after the server analyzes the verification code acquisition request;
and the return module is used for returning the target verification code to the REST layer after receiving the target verification code returned by the server, so that the user completes verification by using the target verification code after the REST layer returns the target verification code to the client interface.
Preferably, the return module comprises:
the verification code returning unit is used for returning the target verification code to the REST layer after receiving the target verification code returned by the server, so that the REST layer returns the target verification code to the client interface;
a verification request receiving unit, configured to receive the verification code verification request sent by the REST layer after the user inputs the target verification code and sends a verification code verification request to the REST layer through the client interface;
the verification request issuing unit is used for issuing the verification request of the verification code to the server so that the server can analyze the verification request of the verification code, verify the target verification code and generate a verification result;
and the verification result returning unit is used for returning the verification result to the REST layer after receiving the verification result returned by the server side, so that the REST layer returns the verification result to the client interface.
Preferably, the cross-language middleware is ZeroC ICE.
The present invention also provides a verification device comprising:
a memory for storing a computer program; a processor for implementing the steps of one of the above-described authentication methods when executing said computer program.
The invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of one of the authentication methods described above.
The verification method provided by the invention aims to solve the problem that two systems of the REST layer and the server side cannot interact in the prior art, and a cross-language middleware is added between the client side and the server side. And when a user sends a verification code acquisition request to the REST layer through a client interface, the REST layer sends the verification code acquisition request to the cross-language middleware. And the cross-language middleware sends the verification code acquisition request to the server. And the server receives and analyzes the verification code acquisition request, generates a target verification code, and returns the target verification code to the cross-language middleware. And after the cross-language middleware returns the target verification code to the RSET layer, the REST layer returns the target verification code to the client interface to display the target verification code for the user, so that the user can complete the verification of the server by using the target verification code. Cross-language middleware is software that connects two independent applications or independent systems. Two systems connected by cross-language middleware can interact with each other through the cross-language middleware even though the two systems have different interfaces. Therefore, in the invention, the easy and efficient access of the REST layer and the service-side quartic language is realized by using the cross-language middleware. According to the verification method provided by the invention, the cross-language middleware is utilized to connect the REST layer and the server, so that two different systems work separately and cooperate without paying attention to how to call the systems; the REST layer only needs to be focused on interaction with a client interface, and the server only needs to be focused on generation of the verification code and realization of the verification rule; the method and the device realize separation of services and can avoid the problem that different languages cannot be directly called.
Drawings
In order to more clearly illustrate the embodiments or technical solutions of the present invention, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 is a schematic flow chart of a prior art authentication method;
FIG. 2 is a flow chart of a first embodiment of a verification method provided by the present invention;
FIG. 3 is a flow chart of a second embodiment of the verification method provided by the present invention;
FIG. 4 is a logic diagram of a verification method provided by the present invention;
fig. 5 is a block diagram of a verification apparatus according to an embodiment of the present invention.
Detailed Description
The core of the invention is to provide a verification method, a verification device, verification equipment and a computer readable storage medium, and interface access from a client to a server is realized through a proxy mechanism of cross-language middleware.
In order that those skilled in the art will better understand the disclosure, the invention will be described in further detail with reference to the accompanying drawings and specific embodiments. It is to be understood that the described embodiments are merely exemplary of the invention, and not restrictive of the full scope of the 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. 2, fig. 2 is a flowchart illustrating a verification method according to a first embodiment of the present invention. The verification method provided by the embodiment is applied to cross-language middleware, and comprises the following specific operation steps:
step S201: when a user sends a verification code acquisition request to an REST layer through a client interface, receiving the verification code acquisition request sent by the REST layer;
in this embodiment, the cross-language middleware may be ZeroC ICE, hprose, or the like.
Step S202: issuing the verification code acquisition request to a server side so that a target verification code is generated after the server side analyzes the verification code acquisition request;
step S203: and after receiving the target verification code returned by the server, returning the target verification code to the REST layer, so that the user completes verification by using the target verification code after the REST layer returns the target verification code to the client interface.
The client interface interacts with the REST layer, and the REST layer is written by Java language; and the server side is written by Python language to realize generation and verification of the verification code. Therefore, in this embodiment, the cross-language middleware is introduced to connect the REST layer and the server, so as to implement cross-language system call, thereby completing the generation and verification of the whole verification code.
Based on the above embodiment, in this embodiment, after the server returns the generated target verification code to the client interface, the user inputs the target verification code to the client interface and sends a verification code check request to the REST layer, and after the REST layer sends the verification code check request to the cross-language middleware, the cross-language middleware sends the verification code check request to the server, so that the server returns a check result to the client interface after verifying the target verification code.
Referring to fig. 3, fig. 3 is a flowchart illustrating a verification method according to a second embodiment of the present invention. The verification method provided by the embodiment is applied to cross-language middleware, and comprises the following specific operation steps:
step S301: when a user sends a verification code acquisition request to an REST layer through a client interface, receiving the verification code acquisition request sent by the REST layer;
step S302: issuing the verification code acquisition request to a server side so that a target verification code is generated after the server side analyzes the verification code acquisition request;
step S303: after receiving the target verification code returned by the server, returning the target verification code to the REST layer, so that the REST layer returns the target verification code to the client interface and then displays the target verification code to the user;
step S304: after the user inputs the target verification code and sends a verification code verification request to the REST layer through the client interface, receiving the verification code verification request sent by the REST layer;
step S305: issuing the verification code verification request to the server side so that the server side can analyze the verification code verification request, verify the target verification code and generate a verification result;
when the target verification code is successfully verified, the server generates information of successful login, and returns the information of successful login to the cross-language middleware; and when the target verification code fails to be verified, the server generates verification code error information and returns the verification code error information to the cross-language middleware.
Step S306: and after receiving the verification result returned by the server, returning the verification result to the REST layer so that the REST layer returns the verification result to the client interface.
As shown in fig. 4, a user sends a verification code acquisition request to the REST layer through the client interface, the REST layer sends the verification code acquisition request to the cross-language middleware, and the cross-language middleware sends the verification code acquisition request to the server, so that the server analyzes the verification code acquisition request, generates the target verification code, and returns the target verification code to the client interface through the cross-language middleware and the REST layer. After obtaining the target verification code, the user inputs the target verification code into the client interface, and sends a verification code verification request to the REST layer, and the REST layer sends the verification code verification request to the server or sends the cross-message middleware to the server; and after the server analyzes the verification code check request, verifying the target verification code to generate a verification result, and returning the verification result to the client interface through the cross-language middleware and the REST layer.
In this embodiment, by introducing the cross-language middleware, a problem that the REST layer and the server cannot interact with each other when verification code generation and verification need to be completed by cooperation of systems in two different languages is solved. In the verification method provided by this embodiment, the REST layer only needs to pay attention to how to return the acquired target verification code to the client interface, and issue the target verification code input by the user to the server in what format for verification, and does not need to pay attention to how to issue the verification code acquisition request or the verification code verification request to the server. The server only needs to pay attention to how to generate the verification code and analyze the verification code verification request issued by the REST layer, so that the verification of the target verification code is realized, the verification result is generated, and the server does not need to pay attention to how to acquire the parameters issued by the REST layer. Based on the method provided by the embodiment, the separation of business logic is realized, meanwhile, the call logic between systems is not required to be realized specially, and the interaction between the REST layer and the server side is completed simply and efficiently through the cross-language middleware.
Referring to fig. 5, fig. 5 is a block diagram of a verification apparatus according to an embodiment of the present invention. The verification device provided by the embodiment is applied to cross-language middleware, and the specific device may include:
the system comprises a receiving module 100, a sending module and a receiving module, wherein the receiving module is used for receiving a verification code obtaining request sent by an REST layer when a user sends the verification code obtaining request to the REST layer through a client interface;
the issuing module 200 is configured to issue the verification code acquisition request to a server, so that the server generates a target verification code after analyzing the verification code acquisition request;
the returning module 300 is configured to return the target verification code to the REST layer after receiving the target verification code returned by the server, so that after the REST layer returns the target verification code to the client interface, the user completes verification by using the target verification code.
The verification apparatus of this embodiment is configured to implement the foregoing verification method, and therefore specific implementations of the verification apparatus may be found in the foregoing embodiments of the verification method, for example, the receiving module 100, the issuing module 200, and the returning module 300, and are respectively configured to implement steps S101, S102, and S103 in the foregoing verification method, so that the specific implementations of the verification apparatus may refer to descriptions of corresponding embodiments of each part, and are not described herein again.
A specific embodiment of the present invention further provides a verification apparatus, including: a memory for storing a computer program; a processor for implementing the steps of one of the above-described authentication methods when executing said computer program.
The specific embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps of the above-mentioned authentication method.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or 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 authentication method, apparatus, device and computer readable storage medium 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 (10)
1. A verification method applied to cross-language middleware comprises the following steps:
when a user sends a verification code acquisition request to an REST layer through a client interface, receiving the verification code acquisition request sent by the REST layer;
issuing the verification code acquisition request to a server side so that a target verification code is generated after the server side analyzes the verification code acquisition request;
and after receiving the target verification code returned by the server, returning the target verification code to the REST layer, so that the user completes verification by using the target verification code after the REST layer returns the target verification code to the client interface.
2. The method of claim 1, wherein the receiving the target authentication code returned by the server and returning the target authentication code to the REST layer, so that after the REST layer returns the target authentication code to the client interface, the user completing authentication using the target authentication code comprises:
after receiving the target verification code returned by the server, returning the target verification code to the REST layer so that the REST layer returns the target verification code to the client interface;
after the user inputs the target verification code and sends a verification code verification request to the REST layer through the client interface, receiving the verification code verification request sent by the REST layer;
issuing the verification code verification request to the server side so that the server side can analyze the verification code verification request, verify the target verification code and generate a verification result;
and after receiving the verification result returned by the server, returning the verification result to the REST layer so that the REST layer returns the verification result to the client interface.
3. The method of claim 2, wherein the server parses the verification request, verifies the verification code to be verified, and generates a verification result comprising:
the server analyzes the verification code verification request and verifies the target verification code;
when the target verification code is successfully verified, the server generates information of successful login, and returns the information of successful login to the cross-language middleware;
and when the target verification code fails to be verified, the server generates verification code error information and returns the verification code error information to the cross-language middleware.
4. The method of any of claims 1 to 3, wherein the cross-language middleware is zeroCICE.
5. A method as claimed in any one of claims 1 to 3, wherein the cross-language middleware is hpose.
6. A verification apparatus, applied to cross-language middleware, comprising:
the system comprises a receiving module, a sending module and a receiving module, wherein the receiving module is used for receiving a verification code acquisition request sent by an REST layer when a user sends the verification code acquisition request to the REST layer through a client interface;
the issuing module is used for issuing the verification code acquisition request to a server so that a target verification code is generated after the server analyzes the verification code acquisition request;
and the return module is used for returning the target verification code to the REST layer after receiving the target verification code returned by the server, so that the user completes verification by using the target verification code after the REST layer returns the target verification code to the client interface.
7. The apparatus of claim 6, wherein the return module comprises:
the verification code returning unit is used for returning the target verification code to the REST layer after receiving the target verification code returned by the server, so that the REST layer returns the target verification code to the client interface;
a verification request receiving unit, configured to receive the verification code verification request sent by the REST layer after the user inputs the target verification code and sends a verification code verification request to the REST layer through the client interface;
the verification request issuing unit is used for issuing the verification request of the verification code to the server so that the server can analyze the verification request of the verification code, verify the target verification code and generate a verification result;
and the verification result returning unit is used for returning the verification result to the REST layer after receiving the verification result returned by the server side, so that the REST layer returns the verification result to the client interface.
8. The apparatus of any of claims 6-7, wherein the cross-language middleware is zerocic.
9. An authentication apparatus, comprising:
a memory for storing a computer program;
a processor for implementing the steps of a method of authentication as claimed in any one of claims 1 to 5 when executing said computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of an authentication method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910843038.8A CN110704828A (en) | 2019-09-06 | 2019-09-06 | Verification method, device, equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910843038.8A CN110704828A (en) | 2019-09-06 | 2019-09-06 | Verification method, device, equipment and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110704828A true CN110704828A (en) | 2020-01-17 |
Family
ID=69194468
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910843038.8A Pending CN110704828A (en) | 2019-09-06 | 2019-09-06 | Verification method, device, equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110704828A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102799631A (en) * | 2012-06-26 | 2012-11-28 | 公安部第三研究所 | Method for realizing network electronic identity identification business process management control based on REST (Representation State Transfer) |
| CN103399734A (en) * | 2013-07-10 | 2013-11-20 | 北京慧点科技股份有限公司 | Method for generating REST service and achieving REST and corresponding equipment |
| CN106775616A (en) * | 2016-11-10 | 2017-05-31 | 中国电子科技集团公司第二十八研究所 | Distribution service based on C++ Yu Java hybrid programmings |
| CN108337211A (en) * | 2017-01-19 | 2018-07-27 | 北京京东尚科信息技术有限公司 | Method, apparatus, electronic equipment and the readable storage medium storing program for executing of Information Authentication |
-
2019
- 2019-09-06 CN CN201910843038.8A patent/CN110704828A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102799631A (en) * | 2012-06-26 | 2012-11-28 | 公安部第三研究所 | Method for realizing network electronic identity identification business process management control based on REST (Representation State Transfer) |
| CN103399734A (en) * | 2013-07-10 | 2013-11-20 | 北京慧点科技股份有限公司 | Method for generating REST service and achieving REST and corresponding equipment |
| CN106775616A (en) * | 2016-11-10 | 2017-05-31 | 中国电子科技集团公司第二十八研究所 | Distribution service based on C++ Yu Java hybrid programmings |
| CN108337211A (en) * | 2017-01-19 | 2018-07-27 | 北京京东尚科信息技术有限公司 | Method, apparatus, electronic equipment and the readable storage medium storing program for executing of Information Authentication |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107018119B (en) | Identity verification system, method and platform | |
| CN107426711B (en) | Method, device and system for binding or unbinding mobile phone number | |
| CN103489095A (en) | Electronic transaction method and system and payment platform system | |
| CN104994060A (en) | Method and device for providing verification for user login | |
| CN110401630B (en) | Transaction certificate verification method, device, electronic equipment and medium | |
| CN110070357B (en) | Data processing method, device and system | |
| CN110033280B (en) | Payment anti-shake method and device | |
| CN109995775B (en) | Block chain verification code application method, equipment and storage medium | |
| CN110543428B (en) | Application system testing method and device | |
| JP2022503458A (en) | Speech processing methods, devices, devices, programs and computer storage media | |
| US20120166893A1 (en) | Recording and Preventing Crash in an Appliance | |
| CN114186206A (en) | Login method and device based on small program, electronic equipment and storage medium | |
| CN107566421B (en) | Login method | |
| CN110704828A (en) | Verification method, device, equipment and computer readable storage medium | |
| CN114880397B (en) | Decentralised data storage method and device, computer medium and electronic equipment | |
| US9098693B2 (en) | Options detection in security protocols | |
| CN115801279A (en) | File secure transmission method and device | |
| CN111027950B (en) | Payment signing system, method and device | |
| CN106209742B (en) | Security verification method and system | |
| CN108462944B (en) | Information processing method and device, and USSDGW | |
| CN105427100A (en) | Bank card transaction method, apparatus and system | |
| CN110489276B (en) | Disaster recovery method and device for verification service based on business page | |
| CN114679336B (en) | Authentication method, authentication system, authentication device, and readable storage medium | |
| CN110351302B (en) | Bank account login method, equipment and storage medium | |
| CN116527284B (en) | Data storage security determination 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200117 |
|
| RJ01 | Rejection of invention patent application after publication |