CN114217925A - Business program operation monitoring method and system for realizing abnormal automatic restart - Google Patents
Business program operation monitoring method and system for realizing abnormal automatic restart Download PDFInfo
- Publication number
- CN114217925A CN114217925A CN202111483149.6A CN202111483149A CN114217925A CN 114217925 A CN114217925 A CN 114217925A CN 202111483149 A CN202111483149 A CN 202111483149A CN 114217925 A CN114217925 A CN 114217925A
- Authority
- CN
- China
- Prior art keywords
- semaphore
- program
- subprocess
- parent
- log
- 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
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
-
- 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/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3013—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is an embedded system, i.e. a combination of hardware and software dedicated to perform a certain function in mobile devices, printers, automotive or aircraft systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
Abstract
The invention relates to a business program running monitoring method and a system for realizing abnormal automatic restart.A parent process and child process semaphore communication method is used, and program crash is judged according to the semaphore generated by the exit of a protected program (child process), so that the problem that the program crash is judged by using a software watchdog, and the CPU resource occupied by process polling communication is higher is solved; the problems that the current static detection means of memory management has high false detection rate and non-real time, the dynamic detection means can only rely on operation and maintenance personnel to inquire logs to obtain useful information, and the log can not be remedied in time are solved. Particularly, whether the service program is started for the first time can be automatically judged, and the influence on the normal running process caused by the execution of complete initialization under the condition of restarting the crash process is avoided. Meanwhile, the operation of the tampered subprocess is avoided through the completeness check of the subprocess program, and the abnormal exit information, the return semaphore and the subprocess restart log of the subprocess are recorded through the parent process, so that data support is provided for system maintenance personnel to analyze the code defects of the subprocess.
Description
Technical Field
The invention relates to the technical field of self-computer program operation guarantee, in particular to a service program operation monitoring method and system for realizing abnormal automatic restart.
Background
In embedded devices and computer systems running operating systems, application software crashes are mostly related to memory management. When the program is judged to be abnormal, the detection methods for finding the memory error mainly include two types: 1) static detection, namely, code-level static detection of cpp _ check, Logiscope RuleCheke, PC-Lint and the like which are common static detection tools at present, and the scheme can find errors that part of memory is not released in allocation; 2) and (3) dynamically detecting, namely detecting memory abnormality in the program running process by using a special debug tool, a core file viewing tool and other means, and feeding the suggestion back to a programmer designer to manually modify codes, wherein the suggestion comprises a memory error checking tool such as a Garbage Collector (GC), a Purify tool, a Valgrind tool and the like.
In the embedded field, the most common method for determining program exception and whether the program is running is to use a watchdog timer. The watchdog counts when the program runs, and if the program runs normally, the counter is reset at regular time; if the counter is increased to the set value, the program is considered to have been abnormal. The watchdog timer is an important component of the hardware of the single chip microcomputer, although the watchdog timer is a common method for detecting program exception, for an embedded application scene with an operating system, software is required to realize the watchdog function, and more CPU resources are occupied. In the application software memory error detection method for operating the operating system, the defect of static memory error detection is that the missed detection rate and the false detection rate are high; dynamic monitoring requires engineering maintenance and frequent attention of the log files by programmers, manual analysis for solving problems requires processes and time, and if the equipment is in use and the program is not crashed in time, the processing can cause great influence on equipment and even system outage.
Since program crash has many problems such as sporadic nature, probabilistic nature and difficult recurrence, and embedded devices are usually sensitive to the utilization rate of the program running CPU, the above methods for detecting program abnormality and memory error cannot meet the requirement of quickly finding and removing faults after program abnormality occurs in the devices in use.
Disclosure of Invention
In order to solve the defects of the prior art, the invention provides a service program operation monitoring method and a system for realizing abnormal automatic restart, which use a parent process and a child process semaphore communication method to judge program crash according to the semaphore generated by the exit of a protected program (child process), thereby solving the problem that the program crash is judged by using a software watchdog, and the CPU resource occupied by process polling communication is higher; the problems that the current static detection means of memory management has high false detection rate and non-real time, the dynamic detection means can only rely on operation and maintenance personnel to inquire logs to obtain useful information, and the log can not be remedied in time are solved. Particularly, whether the service program is started for the first time can be automatically judged, and the influence on the normal running process caused by the execution of complete initialization under the restarting condition is avoided. Meanwhile, the operation of the tampered subprocess is avoided through the completeness check of the subprocess program, and the abnormal exit information, the return semaphore and the subprocess restart log of the subprocess are recorded through the parent process, so that data support is provided for system maintenance personnel to analyze the code defects of the subprocess.
In order to achieve the above purpose, the technical scheme adopted by the invention comprises the following steps:
a service program operation monitoring method for realizing abnormal automatic restart is characterized by comprising the following steps:
s10, starting a first process;
s20, creating a second process through copying the first process;
s30, identifying the first process as a parent process and the second process as a child process according to the creating function return values of the first process and the second process;
s40, verifying the program integrity of the business program corresponding to the child process through the parent process;
s50, when the service program passes the program integrity verification, replacing the sub-process with the service program, setting a counting start mark in the sub-process, recording the parameter value of the counting start mark as 1, recording a start log, initializing and executing service logic according to the parameter value of the counting start mark, and simultaneously enabling the parent process to enter a dormant state to wait for the exit semaphore of the sub-process;
s60, the parent process receives the quit semaphore of the child process and wakes up from the sleep state, and judges whether the quit semaphore of the child process belongs to the normal semaphore or the abnormal semaphore;
s71, when judging that the quit semaphore of the child process belongs to the normal semaphore, recording the quit log and ending the parent process;
s72, when judging that the quit semaphore of the child process belongs to the abnormal semaphore, the parent process creates a third process and increases the parameter value of the counting start mark by 1;
s80, when the parent process creates the third process, using the third process as a new second process and the parent process as a new first process, repeatedly executing steps S30, S40, S50, S60 and S72 until the parent process judges that the exit semaphore belongs to the normal semaphore and executes step S71.
Further, the identifying the first process as a parent process and the second process as a child process according to the creation function return values of the first process and the second process comprises:
the return value of the creating function of the first process is greater than 0, and the first process is identified as a parent process;
when the return value of the creating function of the second process is 0, identifying the second process as a sub-process;
and when the return value of the creating function of the second process is less than 0, judging that the creating of the second process fails.
Further, the initializing according to the parameter value of the count start flag includes:
when the parameter value of the counting start mark is 1, the service program is identified as being started for the first time, namely the service program judges that the service program is a subprocess started for the first time, and complete initialization of the first start is executed;
when the parameter value of the counting start mark is larger than 1, the service program is identified as restarting, namely the service program judges that the service program is a restarted subprocess, and the complete initialization of the first start is not executed.
Further, the first process is started by executing the boot self-starting script.
Further, the step S30 further includes:
and resetting the parent process as the non-response interrupt semaphore, so as to prevent the parent process from exiting in advance in response to the interrupt semaphore, and the child process does not exit at the moment, thereby preventing the parent process from being incapable of protecting the child process.
The invention also relates to a service program operation monitoring system for realizing abnormal automatic restart, which is characterized by comprising the following steps:
the subprocess starting module is used for creating a subprocess;
the subprocess semaphore monitoring module is used for monitoring and receiving the quit semaphore of the subprocess;
the program integrity verification module is used for verifying the program integrity of the business program corresponding to the subprocess;
the log recording module is used for recording a starting log and an exiting log;
and the time service module is used for connecting the hardware clock and acquiring clock information as timestamps of starting and exiting the log.
The invention also relates to a computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the above-mentioned method.
The invention also relates to an electronic device, characterized in that it comprises a processor and a memory;
the memory is used for storing a service program;
the processor is used for executing the method by calling the service program.
The invention has the beneficial effects that:
by adopting the method and the system for monitoring the operation of the abnormal automatic restart service program, the program crash is judged according to the semaphore generated by the quitting of the protected program (subprocess), the problems that the polling communication of the software watchdog process occupies higher CPU resources are solved, the problems that the current static detection means of memory management has high false detection rate and is not real-time, the dynamic detection means can only rely on operation and maintenance personnel to inquire logs to obtain useful information and cannot timely remedy the problem are solved, the method for automatically restarting the program after the program crash caused by automatically discovering the memory error is realized, the program can be automatically restarted and services can be recovered under the condition of program abnormality, the normally-operated process can be isolated under certain scenes, the program cannot be restarted, the user experience is improved, and the basis and the time are provided for the problem troubleshooting of developers.
Drawings
Fig. 1 is a schematic flow chart of a service program operation monitoring method for implementing abnormal automatic restart according to the present invention.
Fig. 2 is a schematic structural diagram of a service program operation monitoring system for implementing abnormal automatic restart according to the present invention.
Fig. 3 is a schematic structural diagram of an embodiment of hardware of a device according to the application of the method of the present invention.
Detailed Description
For a clearer understanding of the contents of the present invention, reference will be made to the accompanying drawings and examples.
The first aspect of the present invention relates to a method for monitoring the operation of a service program for implementing abnormal automatic restart, the flow of which is shown in fig. 1, and the method includes:
s10, starting a first process by executing the startup self-starting script, wherein the starting parameters of the first process are solidified in the script, the parameters are a service program directory and a program file name which need to be started, and if the service program needs additional parameters for starting, the additional parameters can be added after the program file name;
s20, creating a second process through copying the first process, preferably, calling a fork function by the first process to start the second process;
s30, identifying the first process as a parent process and the second process as a child process according to the creation function return values of the first process and the second process, and particularly identifying the first process as the parent process when the creation function return value of the first process is greater than 0; when the return value of the creating function of the second process is 0, identifying the second process as a sub-process; when the return value of the creating function of the second process is less than 0, judging that the creating of the second process fails;
s40, verifying the program integrity of the business program corresponding to the child process through the parent process;
s50, when the service program passes program integrity verification, adding a counting start mark in the service program corresponding to the sub-process, recording the parameter value of the counting start mark as 1, recording a start log, replacing the sub-process with the service program by using execl () and executing service logic, and simultaneously transmitting the extra parameters needed by the start of the service program received by the parent process into the replaced service program; the parameter value of the counting start mark is 1, which indicates that the service program is started for the first time and needs to be initialized, and the parameter value of the counting start mark is not 1, which indicates that the service program is not started for the first time and does not need to be initialized; meanwhile, the parent process enters a dormant state to wait for the quitting semaphore of the child process, and at the moment, the parent process does not occupy system resources;
s60, the father process receives the quit semaphore of the child process to wake up from the sleep state and judges whether the quit semaphore belongs to the normal semaphore or the abnormal semaphore, preferably, calling WTERMSIG function in the father process can check the semaphore of the quit semaphore of the child process, for the embedded device adopting Linux system, the abnormal semaphore has the conventional definition, for example, an illegal access memory (SIGSEGV) is classified into the abnormal semaphore, ctrl + c is classified into an INTR character (SIGINT) and classified into the normal semaphore, and the father process can judge according to the related definition;
s71, when judging that the quit semaphore belongs to the normal semaphore, recording the quit log and ending the father process;
s72, when judging that the quit semaphore belongs to the abnormal semaphore, establishing a third process, increasing the parameter value of the counting start mark by 1, which is equivalent to that the restarting operation of the service program is restarted and executed through the sub-process, and changing the counting start mark to enable the parameter value to be more than 1, indicating that the service program is not started for the first time, and not needing to execute full initialization, so that other modules in normal operation and resources in use are not forced to be released, and the influence on the user is reduced;
s80, when the father process creates the third process, the third process is used as a new second process, the father process is used as a new first process, and the steps S30, S40, S50, S60 and S72 are repeatedly executed until the father process judges that the quit semaphore belongs to the normal semaphore and executes the step S71, namely, the monitoring process is repeated until the son process corresponding to the business program is judged to normally quit.
The second aspect of the present invention relates to a service program operation monitoring system for implementing abnormal automatic restart, which has a structure as shown in fig. 2, and includes:
the subprocess starting module is used for creating a subprocess;
the subprocess semaphore monitoring module is used for monitoring and receiving the quit semaphore of the subprocess;
the program integrity verification module is used for verifying the program integrity of the business program corresponding to the subprocess;
the log recording module is used for recording a starting log and an exiting log, in particular the starting log and the exiting log of the corresponding sub-process;
and the time service module is used for connecting the hardware clock and acquiring clock information, and the clock information is used as a timestamp for starting the log and exiting the log.
The implementation of the above method can be achieved by using the system.
Fig. 3 is a schematic diagram of a hardware structure of a device for monitoring operation of a service program by applying the method of the present invention, which shows a network communication device using a red-black isolation architecture, where a red-region optical interface is connected to an internal network and a black-region optical interface is connected to an external network; the key hardware components are a black area CPU, a red area CPU, an algorithm CPU and an FPGA; the reset key is connected with reset pins of the three CPUs.
The black area CPU, the red area CPU and the algorithm CPU have the same model and run the same embedded Linux operating system, and the application software of the three area CPU is developed according to the function application requirement in a customized manner. Initialization operation of the device: and the clock chip is used for time service to the Linux system of the three-region CPU, the algorithm CPU downloads an algorithm program to the FPGA, and the black region CPU and the red region CPU respectively initialize the optical interfaces of the black region and the red region. Once the communication link is established, the traffic data path is as indicated by the arrow in fig. 3. The three-area CPU will not participate in service operations most of the time, and only generates control signaling for the ongoing service when needed: the algorithm CPU sends algorithm updating instructions to the FPGA at regular time, the red area CPU responds when the local management instructions are sent, and the black area CPU is responsible for receiving the remote management instructions and then controlling the equipment to execute.
And service application programs of the three-area CPU are all protected by the parent process as child processes. When the child process of the CPU in the red area and the black area has memory errors and program crash, the parent process restarts the child process to only influence the local management and the remote management which are running at the moment, and after the child process is restarted, the management function is recovered. When the subprocess of the CPU of the algorithm module crashes, one algorithm replacement and some main control flows can be influenced, and because the program is stored on site when crashed, the algorithm updating and the main control flows can also be recovered after the subprocess is restarted. Since the parent process restarts the child process and the first-time promoter process are distinguished, the initialization operation of the device is not performed, and the ongoing communication is protected. The normal user experiences little impact of a CPU program crash on network traffic unless the operator of the device is doing remote or local administration.
If a reset key or a power key is pressed, or the device is restarted through a menu of remote management and local management, the parent process is also restarted, at this time, the initialization operation of the device needs to be executed after the device is restarted, the FPGA and the optical interface are also reset, and the ongoing communication is interrupted. This is a manually operated device control management command, and the system administrator is in the expectation of a communication interruption, and the temporary interruption of communication can be accepted.
According to the invention, through monitoring of the sub-process quit semaphore, the service program which crashes after the fault is found can be restarted in time, and the probability of communication system fault caused by program crash is reduced. The response time sensitivity from fault occurrence to fault elimination is reduced, so that the client acceptance time limit for solving the code defect in a limited period is prolonged. And the recorded program start and program stop logs are convenient for developers to position, check and modify defects in the codes in the future. Meanwhile, the service program monitoring is realized only by using a software method, and the hardware cost is effectively reduced without adding watchdog hardware. The method of the invention is used as an effective remedy for code defects introduced into actual engineering in the development and test stage and an auxiliary method for defect checking, and is verified to be effective in network communication engineering practice.
The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (8)
1. A service program operation monitoring method for realizing abnormal automatic restart is characterized by comprising the following steps:
s10, starting a first process;
s20, creating a second process through copying the first process;
s30, identifying the first process as a parent process and the second process as a child process according to the creating function return values of the first process and the second process;
s40, verifying the program integrity of the business program corresponding to the child process through the parent process;
s50, when the service program passes the program integrity verification, replacing the sub-process with the service program, setting a counting start mark in the sub-process, recording the parameter value of the counting start mark as 1, recording a start log, initializing and executing service logic according to the parameter value of the counting start mark, and simultaneously enabling the parent process to enter a dormant state to wait for the exit semaphore of the sub-process;
s60, the parent process receives the quit semaphore of the child process and wakes up from the sleep state, and judges whether the quit semaphore of the child process belongs to the normal semaphore or the abnormal semaphore;
s71, when judging that the quit semaphore of the child process belongs to the normal semaphore, recording the quit log and ending the parent process;
s72, when judging that the quit semaphore of the child process belongs to the abnormal semaphore, the parent process creates a third process and increases the parameter value of the counting start mark by 1;
s80, when the parent process creates the third process, using the third process as a new second process and the parent process as a new first process, repeatedly executing steps S30, S40, S50, S60 and S72 until the parent process judges that the exit semaphore belongs to the normal semaphore and executes step S71.
2. The method of claim 1, wherein identifying the first process as a parent process and the second process as a child process based on a create function return value for the first process and the second process comprises:
the return value of the creating function of the first process is greater than 0, and the first process is identified as a parent process;
when the return value of the creating function of the second process is 0, identifying the second process as a sub-process;
and when the return value of the creating function of the second process is less than 0, judging that the creating of the second process fails.
3. The method of claim 1, wherein initializing based on the parameter value of the count enable flag comprises:
when the parameter value of the counting start mark is 1, the service program is identified as being started for the first time, and complete initialization of the first start is executed;
when the parameter value of the counting start mark is larger than 1, the service program is identified as restarting, and the complete initialization of the first start is not executed.
4. The method of claim 1, wherein the first process is started by executing a power-on self-start script.
5. The method of claim 1, wherein the step S30 further comprises:
the parent process is reset to be unresponsive to the interrupt semaphore.
6. A service program operation monitoring system for realizing abnormal automatic restart is characterized by comprising:
the subprocess starting module is used for creating a subprocess;
the subprocess semaphore monitoring module is used for monitoring and receiving the quit semaphore of the subprocess;
the program integrity verification module is used for verifying the program integrity of the business program corresponding to the subprocess;
the log recording module is used for recording a starting log and an exiting log;
and the time service module is used for connecting the hardware clock and acquiring clock information as timestamps of starting and exiting the log.
7. A computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the method of any one of claims 1 to 5.
8. An electronic device comprising a processor and a memory;
the memory is used for storing a service program;
the processor is configured to execute the method according to any one of claims 1 to 5 by calling a service program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111483149.6A CN114217925A (en) | 2021-12-07 | 2021-12-07 | Business program operation monitoring method and system for realizing abnormal automatic restart |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111483149.6A CN114217925A (en) | 2021-12-07 | 2021-12-07 | Business program operation monitoring method and system for realizing abnormal automatic restart |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114217925A true CN114217925A (en) | 2022-03-22 |
Family
ID=80699929
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111483149.6A Pending CN114217925A (en) | 2021-12-07 | 2021-12-07 | Business program operation monitoring method and system for realizing abnormal automatic restart |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114217925A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116860508A (en) * | 2023-08-31 | 2023-10-10 | 深圳华锐分布式技术股份有限公司 | Distributed system software defect continuous self-healing method, device, equipment and medium |
-
2021
- 2021-12-07 CN CN202111483149.6A patent/CN114217925A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116860508A (en) * | 2023-08-31 | 2023-10-10 | 深圳华锐分布式技术股份有限公司 | Distributed system software defect continuous self-healing method, device, equipment and medium |
| CN116860508B (en) * | 2023-08-31 | 2023-12-26 | 深圳华锐分布式技术股份有限公司 | Distributed system software defect continuous self-healing method, device, equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11360842B2 (en) | Fault processing method, related apparatus, and computer | |
| EP3036633B1 (en) | Cloud deployment infrastructure validation engine | |
| US7802128B2 (en) | Method to avoid continuous application failovers in a cluster | |
| WO2022198972A1 (en) | Method, system and apparatus for fault positioning in starting process of server | |
| US5948112A (en) | Method and apparatus for recovering from software faults | |
| CN109144873B (en) | Linux kernel processing method and device | |
| CN114217925A (en) | Business program operation monitoring method and system for realizing abnormal automatic restart | |
| JP2012003651A (en) | Virtualized environment motoring device, and monitoring method and program for the same | |
| JPH10214208A (en) | System for monitoring abnormality of software | |
| CN116719657A (en) | Firmware fault log generation method, device, server and readable medium | |
| CN107273291B (en) | Processor debugging method and system | |
| CN112650610B (en) | Linux system crash control method, system and medium | |
| CN114003416A (en) | Dynamic memory error processing method, system, terminal and storage medium | |
| CN115562900B (en) | AMD server system installation power-off processing method, device, equipment and medium | |
| KR102255459B1 (en) | method for automatically starting computer program | |
| CN108415788B (en) | Data processing apparatus and method for responding to non-responsive processing circuitry | |
| CN114356708A (en) | Equipment fault monitoring method, device, equipment and readable storage medium | |
| CN115858224A (en) | Method, apparatus, device, medium and product for triggering watchdog reset | |
| CN115756914A (en) | Test method, test system, test platform and test machine | |
| CN106339285A (en) | Method for analyzing unexpected restart of LINUX system | |
| CN113742120A (en) | Method, system, device and medium for kdump triggering | |
| CN117931649A (en) | Testing method for deadlock reset of operating system and computing device | |
| CN115756935A (en) | Abnormal fault positioning method, device and equipment of embedded software system | |
| CN117215854A (en) | Method, system, equipment and storage medium for testing AMT (automated mechanical transmission) of server | |
| CN116302125A (en) | Switching control 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 |