CN111522623B - Modularized software multi-process running system - Google Patents
Modularized software multi-process running system Download PDFInfo
- Publication number
- CN111522623B CN111522623B CN202010299822.XA CN202010299822A CN111522623B CN 111522623 B CN111522623 B CN 111522623B CN 202010299822 A CN202010299822 A CN 202010299822A CN 111522623 B CN111522623 B CN 111522623B
- Authority
- CN
- China
- Prior art keywords
- container
- service
- component
- management
- framework
- 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
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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/20—Software design
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/34—Graphical or visual programming
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
-
- 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45575—Starting, stopping, suspending or resuming virtual machine instances
-
- 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/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a modularized software multi-process operation system, which comprises a service-oriented component framework, a container management framework and a software architecture configuration module, wherein the service-oriented component framework is used for providing a software provider with standards for developing components and releasing and subscribing strategies of the components; the software architecture configuration module provides a tool for configuring an operation scheme and distributed communication in the software system by a user, and generates an operation scheme configuration file and a distributed communication configuration file required by the container management framework; the container management framework is used for subscribing components from the service-oriented component framework to form containers according to the operation scheme configuration file, and establishing communication inside the containers and between the containers according to the distributed communication configuration file. The invention provides a unified environment and standard for developing, operating, integrating and testing unmanned aerial vehicle ground station software, and solves the problems of unified deployment, rapid integration, function expansion and the like of different application software of different manufacturers.
Description
Technical Field
The invention belongs to the field of computer software architecture, and particularly relates to a multi-process running system of componentized software.
Background
With the vigorous development of the unmanned aerial vehicle field and the continuous improvement of computer performance, the scale of unmanned aerial vehicle ground software becomes larger and larger, and the function becomes more and more complex. According to the load of the unmanned aerial vehicle, unmanned aerial vehicle ground station software covers various functions such as flight control, three-dimensional view, task planning, load display, target identification, target fusion and the like. Therefore, the scale and complexity of unmanned aerial vehicle ground station software are continuously improved, great challenges are brought to software development, and the performance requirements and the safety requirements of the software are improved.
Traditional software development mode is mainly integrated by single application, and each module is integrated by means of a link library or source code. Similar function repeated realization, lack of standardized defined call interfaces of single modules and complex cross-linking call relations among modules become main factors for restricting the development efficiency and performance of unmanned aerial vehicle ground station software. Therefore, a reconfigurable software componentization technology is needed to isolate different functional units (namely components) of an application program from each other, and the service interfaces among the components are defined to be connected with each other, so that loose coupling among the components is realized, the dependence among the modules can be effectively reduced, the interaction capability among the modules is improved, and the expansion capability and development efficiency of unmanned aerial vehicle ground station software are improved.
Meanwhile, the unmanned aerial vehicle ground station software system is generally provided by different software suppliers respectively, and provides new challenges for stable running, fault positioning and running performance of the software. There is therefore a need to provide multi-process concurrent run capability, provide greater isolation, better performance, and faster fault location capability based on componentized development.
Disclosure of Invention
The invention aims to provide a modularized software multi-process operation system, which provides a unified environment and standard for component development, operation, integration and test for unmanned aerial vehicle ground station software development and solves the problems of unified deployment, rapid integration, function expansion and the like of different application software of different manufacturers. Meanwhile, techniques such as system resource management, abnormal detection and fault tolerance during running, component container management and the like are provided, and common platform-level services are provided for the components.
The invention aims at realizing the following technical scheme:
a modularized software multi-process running system comprises a service-oriented component framework, a container management framework and a software architecture configuration module;
the service-oriented component framework is used for providing a software provider with standards for developing components and strategies for publishing and subscribing the components;
the software architecture configuration module is used for providing a tool for configuring an operation scheme and distributed communication in the software system by a user and generating an operation scheme configuration file and a distributed communication configuration file required by the container management framework;
the container management framework is used for subscribing components from the service-oriented component framework to form containers according to the operation scheme configuration file, and establishing communication inside the containers and between the containers according to the distributed communication configuration file.
The invention has the beneficial effects that:
the multi-process running system for analyzing the characteristics and the mission of the unmanned aerial vehicle ground station software has the following functions and characteristics:
easy integration: the service-oriented component framework should be able to provide a corresponding mechanism to facilitate the rapid integration of application software developed by a software provider into the overall software system;
distributed type: the communication mechanism provided by the container management framework enables application software of the platform frameworks deployed on different network nodes to exchange data;
the method comprises the following steps: the graphical software architecture configuration module provides convenience for software system architecture design and verification, component development and deployment and the like, and improves the efficiency of software design and development.
The invention provides an application software framework with high reusability, high expansibility and easy maintainability for unmanned aerial vehicle ground station software development. The method greatly improves the software development efficiency and code reusability, breaks through the performance bottleneck and safety problems of the traditional single-process software, provides a key technical route for the development of unmanned aerial vehicle ground station software, and has wide and profound application value.
Drawings
FIG. 1 is a block diagram of a componentized model.
FIG. 2 is a component lifecycle management block diagram.
FIG. 3 is a schematic diagram of a service management model of a component.
Fig. 4 is a block diagram of a container management model.
Fig. 5 is a container communication block diagram.
FIG. 6 is a runtime framework diagram.
FIG. 7 is a block diagram of a componentized software multiprocessing runtime system.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples.
Referring to fig. 7, a componentized software multiprocessing system according to the present embodiment specifically includes the following program modules: a service-oriented component framework, a container management framework, and a graphical software architecture configuration module. The program modules are described in detail below with reference to the figures.
Service oriented component framework
The service-oriented component framework is used to provide software providers with standards for developing components, and policies for publishing and subscribing to components, including componentized models, component lifecycle models, and service management models for components.
(1) Modularized model
The componentization model provides a form and loading strategy of a component for a software provider, and the componentization model is shown in a block diagram of the componentization model in fig. 1, and comprises metadata definition of the component, resource files of the component, internal information export strategy of the component, external access strategy of the component and the like, so that a dynamic component architecture is realized, and standards and constraints are provided for development of general or special components.
The metadata definition of a component is used to define the necessary key-value pairs and optional key-value pairs. The necessary key-value pair includes a component digital signature, a component name and a component version. The selectable key pairs include dependent components, and version ranges of the dependent components.
The resource file of the component is used for recording the file and the picture used by the component, the file used by the component contains a list of metadata used by the component, and the container can acquire the metadata of the component according to the exported resource file.
The internal information of the component derives the tactics, is used for defining the route and deriving tactics of the resource file of the component. The container acquires metadata of the component through the exported resource file of the component, and the management of the component is realized.
The external access strategy of the component is used for defining an event communication model between the component and other components after the component is put into the container, and releasing the state of the component. And registering the resource file of the component to the service management center.
The componentization model provides component management, and realizes loading and analyzing functions of the components based on the componentization model. The component loading needs to independently load each component to ensure the physical isolation of the components, and is specifically expressed as the operations of definition of the resource file of each component and analysis, loading, unloading and the like of the content of each component.
Component management of software componentized model techniques provides the following functions:
a) Storing component information;
b) Updating component information;
c) Acquiring component information;
d) Component version management.
(2) Component lifecycle model
The component lifecycle model is used to define access models and execution contexts for the component and related operations for the component lifecycle. The access model of the component comprises definitions of operations such as installation, analysis, starting and stopping of the component. The installation of the component comprises the analysis of the metadata of the component, so that the storage, the updating and the version management of the component information are realized.
FIG. 2 is a component lifecycle management block diagram, component lifecycle models provide a component lifecycle management technique that provides a set of management APIs for components when executing in a component framework. Lifecycle management achieves two roles:
outside the application, lifecycle management defines the relevant operations on the component lifecycle that allow the composition of the components running in the framework to be dynamically changed and thereby manage and improve the application;
within an application, lifecycle management defines the way components access and execute contexts, providing a way for components to interact with the component framework and conditions for execution.
(3) Service management model for components
The service management model of the component provides a service software management framework which is composed of five parts, namely a translator, a service manager, a registry service library, a service matcher and an execution engine.
The component developer distributes the component to a registry service library, the translator receives and translates the service request submitted by the component user, and the execution engine acquires the handle of the service from the service matcher for the component user to use according to the translated service request.
FIG. 3 is a schematic diagram of a service management model of a component, with the service layer of the component framework supporting and facilitating a flexible application programming model, the main concepts involving service-oriented publishing, lookup and binding interaction patterns. The service layer is a lightweight layer, and component developers are just some of the objects that are accessed by direct method calls. In addition, the service layer extends the component-based dynamics of the lifecycle layer by being based on the dynamics of the service (the service can appear or disappear at any time).
The service management model of the component provides a service calling mechanism for the component, which is the basis of communication among the components, and endows the component with collaboration, dynamic performance, security, version control capability and the like. The components are isolated from each other and operate independently, but in most cases the components still need to maintain the ability to communicate with each other. The service is used as the most important means of component communication, and is provided with a model of a service caller, a service user and a service manager, so that the service is called among components only by appointed service without knowing a real service provider.
(II) Container management framework
The container management framework is used for subscribing components from the service-oriented component framework to form a container according to the operation scheme configuration file, and establishing communication inside the container and between the containers according to the distributed communication configuration file, and comprises a container management model, a container communication model and a runtime framework of the container.
(1) Container management model
The container management model is used to subscribe components to form containers from the service-oriented component framework according to container start parameters.
The container starting parameters comprise a container running component list, stack size information of a process running by the container, running CPU (Central processing Unit) and priority setting of the process and the thread, and a database connection pool upper limit of a single container. FIG. 4 is a block diagram of a container management model, each container supporting the operation of multiple components; the running states of different containers are isolated from each other, and the containers have independent working catalogues, environment variables, dependency libraries and the like.
The component is subscribed to by entering a list set of component list descriptions in the container launch parameters into a component lifecycle model in the service-oriented component framework. The component list comprises basic general components except for the defined service components required by the running of the application program, and the basic general components comprise a log module, a fault detection module and an http server, and are used for collecting the running states of the components in the container in a browser mode.
(2) Container communication model
The communication model of the container integrates DDS (Data Distribution Service) and Qt event communication. The communication among the containers and the components is established by adopting a decentralised peer-to-peer network. The information transmission between the containers is carried out in a peer-to-peer mode, without server, daemon, message agent, bottleneck or single point failure of the information transmission is avoided.
The container communication model realizes the configuration of communication quality in the communication model by reading the distributed communication configuration file, thereby realizing reliable data transmission, maximum speed data transmission and other various communication qualities.
FIG. 5 is a block diagram of a container communication within which event communication is enabled using a publish-subscribe model, the event communication capability being derived from an event communication service registered by an event communication component. The service issues the event communication to the network through the DDS bus at the same time, thereby realizing the event communication among containers and event communication monitoring.
(3) Runtime framework for containers
The runtime framework provides a running model of the container, and the running model integrates the ftp server for upgrading and deploying the container. The system management container integrating the ASSAC standard realizes the configuration of the runtime framework and the health management.
FIG. 6 is a runtime framework diagram of a componentized multi-process system, running from the creation of a daemon that defaults to creating a system management container that conforms to the ASAAC standard.
And the system management container reads the running scheme configuration file to obtain a container list to be started. The container list, each of the entries, contains all the information that the container model needs at run-time, i.e. the container start-up parameters. According to the container list to be started, the system management container creates an application program by applying for creating a container to the daemon; the application program consists of a plurality of component containers; each component container has independent run properties (environment variables, working directory, external dependencies, memory resources, thread resources, process resources, etc.), and a list of components.
The daemon creates both an event management container and a service management container. The event management container registers the event service with the service management container. All the services registered in the container are registered in the service management container through the DDS distributed communication bus, so that unified service management and event communication management of the application software are realized.
In addition, monitoring of service and event communication can be achieved through monitoring of the DDS distributed bus.
(III) software architecture configuration module
The software architecture configuration module graphically provides a user with configuration of an operation scheme and distributed communication in the software system, and generates an operation scheme configuration file and a distributed communication configuration file required by the container management framework.
It will be understood that equivalents and modifications will occur to those skilled in the art in light of the present invention and their spirit, and all such modifications and substitutions are intended to be included within the scope of the present invention as defined in the following claims.
Claims (2)
1. A modular software multiprocessing runtime system comprising a service oriented component framework, a container management framework, and a software architecture configuration module, characterized by:
the service-oriented component framework is used for providing a software provider with standards for developing components and strategies for publishing and subscribing the components;
the software architecture configuration module is used for providing a tool for configuring an operation scheme and distributed communication in the software system by a user and generating an operation scheme configuration file and a distributed communication configuration file required by the container management framework;
the container management framework is used for subscribing components from the service-oriented component framework to form a container according to the operation scheme configuration file, and establishing communication inside the container and between the containers according to the distributed communication configuration file;
wherein:
the service-oriented component framework comprises a componentization model, a component life cycle model and a service management model of the component;
the componentization model provides a software provider with a form and loading strategy of a component;
the lifecycle model of the component is used to define an access model and execution context of the component and related operations of the component lifecycle;
the service management model of the component consists of five parts, namely a translator, a service manager, a registry service library, a service matcher and an execution engine, wherein a component developer distributes the component to the registry service library, the translator receives and translates a service request submitted by a component user, and the execution engine acquires a handle of the service from the service matcher for the component user according to the translated service request;
the container management framework comprises a container management model, a container communication model and a runtime framework of the container;
the container management model is used for subscribing components from the service-oriented component framework to form a container according to container starting parameters;
the container communication model realizes the communication configuration among containers, components and assemblies by reading the distributed communication configuration file;
the runtime framework provides an operational model of the container for upgrades, deployments of the container.
2. A componentized software multiprocessing runtime system according to claim 1, wherein the runtime framework comprises a system management container and daemon;
the system management container reads the operation scheme configuration file to obtain a container list to be started, and creates a container by applying to the daemon according to the container list to be started;
the daemon also creates an event management container and a service management container, the event management container registering event services with the service management container.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010299822.XA CN111522623B (en) | 2020-04-16 | 2020-04-16 | Modularized software multi-process running system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010299822.XA CN111522623B (en) | 2020-04-16 | 2020-04-16 | Modularized software multi-process running system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111522623A CN111522623A (en) | 2020-08-11 |
| CN111522623B true CN111522623B (en) | 2023-06-27 |
Family
ID=71910746
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010299822.XA Active CN111522623B (en) | 2020-04-16 | 2020-04-16 | Modularized software multi-process running system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111522623B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112199105A (en) * | 2020-10-15 | 2021-01-08 | 舟山网脉科技有限公司 | Method, system, medium and electronic device for function combination type software development |
| CN113190213A (en) * | 2021-03-25 | 2021-07-30 | 中国人民解放军海军工程大学 | Development framework of physical device component data processing program |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106155680A (en) * | 2016-06-27 | 2016-11-23 | 上海波汇科技股份有限公司 | A kind of distributed High Availabitity, expansible, portable software framework |
| CN107959718A (en) * | 2017-11-17 | 2018-04-24 | 西北工业大学 | The micro services framework of enterprise-level application software under a kind of cloud computing environment |
| CN110321152A (en) * | 2019-07-04 | 2019-10-11 | 青岛华正信息技术股份有限公司 | A kind of Software Development Platform |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9043458B2 (en) * | 2013-03-19 | 2015-05-26 | Cognizant Technology Solutions India Pvt. Ltd. | Framework for facilitating implementation of multi-tenant SaaS architecture |
-
2020
- 2020-04-16 CN CN202010299822.XA patent/CN111522623B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106155680A (en) * | 2016-06-27 | 2016-11-23 | 上海波汇科技股份有限公司 | A kind of distributed High Availabitity, expansible, portable software framework |
| CN107959718A (en) * | 2017-11-17 | 2018-04-24 | 西北工业大学 | The micro services framework of enterprise-level application software under a kind of cloud computing environment |
| CN110321152A (en) * | 2019-07-04 | 2019-10-11 | 青岛华正信息技术股份有限公司 | A kind of Software Development Platform |
Non-Patent Citations (1)
| Title |
|---|
| 包晓安 ; 张娜 ; 桂宁 ; 宋瑾钰 ; .基于架构的软实时软件的自适应框架的研究.电信科学.2012,(09),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111522623A (en) | 2020-08-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102370568B1 (en) | Containerized deployment of microservices based on monolithic legacy applications | |
| Arcangeli et al. | Automatic deployment of distributed software systems: Definitions and state of the art | |
| CA3096768A1 (en) | System and method for automated microservice source code generation and deployment | |
| CN111324571B (en) | Container cluster management method, device and system | |
| US20080288962A1 (en) | Method and System for Dynamic Remote injection of In-process Agents into Virtual Machine based Applications | |
| Ferry et al. | Genesis: Continuous orchestration and deployment of smart iot systems | |
| CN113434158B (en) | Custom management method, device, equipment and medium for big data component | |
| CN114077423A (en) | Airport APP development container architecture based on mobile cross-platform | |
| CN111522623B (en) | Modularized software multi-process running system | |
| CN117099079A (en) | System configuration freezing and change management of services deployed via continuous delivery configured on a data center in a cloud platform | |
| CN114675935A (en) | Method and system for deploying chain code in alliance chain | |
| Stoicescu et al. | From design for adaptation to component-based resilient computing | |
| Fortier et al. | Dyninka: a FaaS framework for distributed dataflow applications | |
| CN112015371A (en) | Software development device under non-embedded software platform | |
| Coelho | A software framework for nanosatellites based on CCSDS mission operations services with reference implementation for Esa’s OPS-SAT mission | |
| CN116028163A (en) | Method, device and storage medium for scheduling dynamic link library of container group | |
| CN115220873A (en) | Method for running Open Harmony application in Android system | |
| CN112445595B (en) | Multitask submission system based on slurm computing platform | |
| CN115145604A (en) | Containerized electric power marketing system deployment method | |
| CN114661421A (en) | Method and system for deploying chain code in alliance chain | |
| CN114461249A (en) | Micro-service deployment method, device, code server and storage medium | |
| CN114265595A (en) | Cloud native application development and deployment system and method based on intelligent contracts | |
| Hassane et al. | Process Enactment with Traceability Support for NFV Systems | |
| CN116225464B (en) | Rapid deployment method of platform | |
| Blümke | Planning and Execution of System Adaptations in Cloud-Based Environments |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |