CN114546536B - Method for using same android application by multiple android applications on Linux platform - Google Patents
Method for using same android application by multiple android applications on Linux platform Download PDFInfo
- Publication number
- CN114546536B CN114546536B CN202210276873.XA CN202210276873A CN114546536B CN 114546536 B CN114546536 B CN 114546536B CN 202210276873 A CN202210276873 A CN 202210276873A CN 114546536 B CN114546536 B CN 114546536B
- Authority
- CN
- China
- Prior art keywords
- activity
- request
- android
- call
- calling
- 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/445—Program loading or initiating
- G06F9/44552—Conflict resolution, i.e. enabling coexistence of conflicting executables
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method for using the same android application by a plurality of android applications on a Linux platform, which comprises the steps of acquiring the set attributes when the android applications call other android applications by adding a detection mechanism in an android compatible environment, dynamically determining the execution sequence of the plurality of android applications for calling the related functions of the same android application according to the acquired attributes when the plurality of android applications call the same android application, and meanwhile, avoiding the closing processing of the timeout android application by the android compatible environment by modifying the timeout mechanism of an android system, thereby realizing the function that the plurality of android applications call the same android application on the Linux platform at the same time and effectively improving the user experience.
Description
Technical Field
The invention belongs to the technical field of development of running mobile applications on a desktop operating system, and particularly relates to a method for using the same android application by multiple android applications on a Linux platform.
Background
The android compatible environment (hereinafter abbreviated as android compatible environment) of the Linux operating system is a technology for running android applications (apps) on the Linux operating system, and has important significance for enriching the application ecology of the Linux operating system. The xDroid is a typical Linux operating system android compatible environment, and compatibility of android application and a Linux operating system is achieved through coordination of the xDroid and the xDroid ui. In order to facilitate the user to operate multiple applications simultaneously, the android system introduced a multi-window mode starting from version 7.0, i.e., allowing the user to open multiple applications simultaneously in the same screen. When using the multi-window mode of the android system in the android compatible environment, a situation may occur that multiple android applications use the same android application at the same time, for example, xDroid supports simultaneous display of multiple android applications, and these android applications have a need to call the same third-party android application at the same time to realize functions such as login, payment, sharing, and the like, where the third-party android application includes: WeChat, QQ, microblog, etc.
In the existing android system, although some flat panels can support simultaneous display of multiple applications, the mutual calling mode among android applications still only considers the situation that the android applications are only called by a single android application at the same time, specifically, most android applications adopt a mode of calling a third-party android application through an SDK or Intent interface to realize functions of logging in, paying, sharing and the like, and under the situation, when the current android application does not call the third-party android application, the new android application also calls the third-party android application, so that the call of the new android application fails. For a mobile phone or tablet user, the problem is not obvious because only one android application can be often displayed in the mobile phone or tablet, but for the user of the android application on the Linux platform, the convenience of user operation is reduced, and the user experience is affected.
Disclosure of Invention
In view of this, the present invention provides a method for multiple android applications on a Linux platform to use the same android application, which can implement a function that multiple android applications running on the Linux platform start the same android application at the same time.
The method for using the same android application by multiple android applications on the Linux platform comprises the following steps:
step 1, acquiring a program package name, a called Activity name and a RequestID of a current Activity calling request in an android compatible environment, and determining LaunchMode of the called Activity;
step 2, if an Activity concurrent calling request with the same package name and Activity name as the called Activity exists in the prestored request, executing step 4, otherwise, executing step 3;
step 3, if the value of the launchMode is Standard, executing the Activity call request and returning to the step 1; if the value of the LaunchMode is not the Standard, constructing an Activity concurrent call request with the Activity state being the execution state, adding the Activity concurrent call request to the tail of the prestored information, and executing step 6;
step 4, if the value of the LaunchMode is singleInstance, notifying a user of execution failure, and returning to the step 1; if the value of the launchMode is Standard, executing an Activity call request and returning to the step 1; if the value of the LaunchMode is SingleTop or SingleTask, executing step 5;
step 5, constructing an Activity concurrent call request with an Activity state as a waiting state, and adding the Activity concurrent call request to the tail part of the prestored information;
step 6, determining the calling Activities of the Activities concurrent calling requests, acquiring calling function names of the calling Activities, and executing step 7 if the same calling function names exist in the prestored calling functions; if the calling function name does not exist, adding the calling function name into the prestored calling function, prolonging the waiting time set in the timeout mechanism, suspending the execution of the Activity concurrent calling request, intercepting the input event sent to the calling Activity in the Linux platform, and regularly refreshing the content of a display window of the calling Activity on the Linux platform in the android compatible environment;
step 7, if the Activity state of the Activity concurrent call request is an execution state, executing the Activity concurrent call request and returning to the step 1; if the Activity state is the waiting state, the waiting time set in the overtime mechanism is prolonged, and the Activity execution is suspended and the request execution step 8 is called;
step 8, after the android compatible environment monitors that the current Activity call request or the concurrent Activity call request is responded, if the request with the same requestID exists in the prestored request, deleting the responded request from the prestored request and the prestored call function, if the Activity state of the responded request is an execution state, setting the Activity state of the first request in the prestored request as the execution state, re-executing the system operation of startActivity, and returning to the step 1; and if the request with the same requestID does not exist in the prestored requests, executing the current Activity call request or the concurrent Activity call request, and returning to the step 1.
Further, after the package name, the called Activity name and the RequestID of the current Activity call request are obtained in the android compatible environment in the step 1, if the called Activity related to the current Activity call request is an analysis target, the LaunchMode of the called Activity is obtained; otherwise, executing the current Activity call request and returning to the step 1.
Further, the analysis target comprises functions of logging, sharing, sending and payment calling of the QQ and the WeChat.
Further, the pre-stored request is stored in a queue or a file.
Further, the method for determining the Activity of the Activity concurrent call request in step 6 is a method of backtracking call stack.
Further, the waiting time in the waiting time set in the extended timeout mechanism in step 6 is 30 seconds.
Further, after executing the current Activity call request or the Activity concurrent call in step 8, forwarding the input event sent to the call Activity to the android compatible environment in the Linux platform, and dynamically refreshing the content of the display window of the call Activity on the Linux platform in the android compatible environment.
Has the advantages that:
according to the android application execution method and device, the detection mechanism is added in the android compatible environment to obtain the attributes set when the android application calls other android applications, when the plurality of android applications call the same android application, the execution sequence of the related functions of the plurality of android applications calling the same android application is dynamically determined according to the obtained attributes, meanwhile, the timeout mechanism of the android system is modified to avoid the shutdown processing of the timeout android application by the android compatible environment, therefore, the function that the plurality of android applications call the same android application on the Linux platform at the same time is achieved, and the user experience is effectively improved.
Drawings
Fig. 1 is a flowchart of a method for multiple android applications on a Linux platform to use the same android application provided by the present invention.
Detailed Description
The invention is described in detail below by way of example with reference to the accompanying drawings.
The calling mechanism in the existing android system does not allow a plurality of android applications to start the same android application at the same time, firstly, the android system does not allow the android applications to start the same android application by adopting an Intent interface, and secondly, a timeout mechanism exists in the android system. The timeout mechanism means that the android system stops the current calling process when the waiting time of the calling process exceeds a set threshold in the android system.
The launch mode (LaunchMode) of Activity provided in the android system includes a Standard mode (Standard), a top-of-stack multiplexing mode (SingleTop), an intra-site multiplexing mode (SingleTask), and a single instance mode (SingleInstance). The standard mode is also a default mode, namely, the system can create a new instance in the current task stack only by starting Activity once. The stack top multiplexing mode is that if an Activity instance exists in the current stack and the instance is located at the stack top, the system does not create the instance, but multiplexes the instance at the stack top, and transmits an Intent object into the system to call back the onNewInten () method; if the Activity instance exists in the current stack but is not on the top of the stack or does not exist in the current stack, the processing mode of the system is the same as that of the standard mode. The in-stack multiplexing mode is that a corresponding task stack is searched according to taskAffinity during multiplexing, if no specified task stack exists, the system can newly build a corresponding task stack and newly build an Activity instance to be pressed into the stack; if the specified task stack exists, whether the Activity instance exists in the task stack is searched, if the Activity instance does not exist, the Activity instance is newly built in the task stack, if the Activity instance exists, the onNewIntent () method of the instance is directly referred and called back, and the Activity above the instance in the task stack is completely destroyed. The single instance mode is that when the Activity is started, whether the Activity exists in the system is searched, if not, the Activity instance is created after a task stack is built, and if so, the Activity instance is referred and an oneNewIntent () method is called.
The Activity manager service is an Activity management server for android system service, and is used for managing various activities of Activity, controlling the life cycle of Activity, dispatching message events, managing low memory and the like.
The invention provides a method for using the same android application by a plurality of android applications on a Linux platform, wherein the flow is shown as a figure 1, and the method specifically comprises the following steps:
step 1, monitoring the execution process of startActivity in an android compatible environment, obtaining a program package name, an Activity name, a RequestID and a starting parameter related to an Activity calling request, determining called Activity, and obtaining LaunchMode of the called Activity.
Starting parameters, required authority and starting type (newly-built Task starting and starting at the current Task).
Specifically, the android system builds an Activity calling request by calling startActivity of system service Activity manager service to realize the starting of Activity, can acquire PackageName, Activity Name and starting parameters of Activity according to the Activity calling request, and judges whether the called Activity is a call which should be processed or not according to the PackageName and Activity Name.
Further, in order to improve the execution efficiency of the android application on the Linux platform, the following steps are added in the step 1: judging whether the called Activity related to the Activity calling request is in a monitoring android application list or not according to the package name and the Activity name, if so, determining the called Activity in an android compatible environment, and acquiring LaunchMode of the called Activity; if not, executing the Activity call request in a default mode of the android system, and executing the step 1.
The monitoring android application list is used for storing monitored android applications, and the monitored android applications are logged in, shared, sent, paid and called and the like, such as QQ, WeChat and the like.
And 2, searching whether an Activity concurrent call request with the same package name and Activity name as the called Activity exists in the call request queue, if so, executing the step 4, and if not, executing the step 3.
The call request queue is used for storing the constructed Activity concurrent call requests. The Activity concurrent call request is an Activity call request comprising a requestID and an Activity related attribute, the requestID is a unique identifier of the Activity call request, the Activity attribute comprises a PackageName, an Activity Name, a launchMode and an Activity state, the Activity state comprises an execution state and a waiting state, the execution state represents that the Activity is executing, and the waiting state represents that the Activity is not executed.
In the invention, the request information can be saved by adopting a calling request queue, and the request information can be saved in a file mode.
Step 3, if the value of the launcher mode of the invoked Activity is Standard, executing the Activity invoking request, and executing the step 1; and if the value of the LaunchMode of the called Activity is not the Standard, constructing an Activity concurrent call request with the Activity state as the execution state, adding the Activity concurrent call request to the tail of the call request queue, and executing the step 6.
Step 4, if the value of the LaunchMode of the invoked Activity is singleInstance, notifying the user that the execution fails, and executing the step 1; if the value of the launcher mode of the called Activity is Standard, executing an Activity calling request, and executing the step 1; and if the value of the LaunchMode of the called Activity is SingleTop or SingleTask, executing the step 5.
And 5, constructing an Activity concurrent call request with the Activity state as a waiting state, and adding the Activity concurrent call request to the tail of the call request queue.
Step 6, backtracking the call stack to determine the call Activities which send Activities and send call requests, acquiring call function names of the call Activities, searching whether the same call function names exist in a call function queue, and executing step 7 if the same call function names exist; if the calling function name does not exist, the calling function name is added into the calling function queue, the waiting time set in the timeout mechanism is prolonged, and the execution of the concurrent call request of Activity is suspended.
Step 7, if the Activity state in the Activity concurrent call request is the execution state, executing the Activity concurrent call request, and executing the step 1; and if the Activity state in the Activity concurrent call request is the waiting state, prolonging the waiting time set in the timeout mechanism, suspending the execution of the Activity concurrent call request, and executing the step 8.
The process of backtracking the call stack can adopt methods such as Exception (). printstackTrace (), the method of backtracking the call stack is adopted to position the call Activity of the function calling the current startActivity, the call function name of the call Activity is obtained, the call function name is added into the call function name queue, and before the startActivity receives a return value, an interception function called by an API or a timeout function of the android system is added into the call Activity.
Specifically, the modification is made by adding the following steps to the timeout function:
backtracking the call stack, and when the function name of the call function is in the pendingfunctional list, if the Activity state in the Activity concurrent call request is the execution state, executing the default operation of the system; if the Activity state in the Activity concurrent Call request is a wait state, the timeout is set to a time long enough not to cause a system to falsely death, e.g., 30 seconds.
In order to suspend the call Activity to execute the Activity concurrent call request, the method is realized by suspending the thread of the call function, namely, the subsequent startActivity operation is not executed, and at the moment, in order to not interfere the current operation of the Linux system, the invention provides the following operations:
and S1, informing the android application display program through the RPC that the input event of the call Activity corresponding to the call function is not forwarded to the android compatible environment any more, so as to avoid that the android system is prompted to close the process when the input event cannot be processed by the call Activity. The android application display program is used for being responsible for displaying android applications on a Linux platform, such as xDreidUI and the like.
And S2, informing the android compatible environment, and forcibly refreshing the display window of the call Activity in the waiting state on the Linux platform.
The invoking Activity refers to an android application where a invoking function related to the concurrent invoking request of the Activity is located. The operation of android compatible environment forced refresh can be implemented by modifying the surfaceFlinger of the android system.
Step 8, after the android compatible environment monitors that the current Activity invoking request or the concurrent Activity invoking request is responded, executing the following steps:
step 8.1, if a request with the same requestID as the current Activity call request or Activity concurrent call request exists in the call request queue, deleting the Activity call request or Activity concurrent call request corresponding to the current response from the call request queue, and deleting the call function name of the call Activity related to the current Activity call request or Activity concurrent call request from the call function name queue, and executing step 8.2; if the request with the same requestID as the current Activity call request or Activity concurrent call request does not exist in the call request queue, executing the current Activity call request or Activity concurrent call request, and then executing the step 1;
step 8.2, if the Activity state of the request with the same requestID in the call request queue is an execution state, setting the Activity state of the first request in the call request queue as the execution state;
re-executing the startActivity system operation in a default mode of an android system;
informing the xDroidUI through RPC to forward the input event sent to the invoking Activity to an android compatible environment (xDroid); and informing the android compatible environment to refresh the display window of the call Activity on the Linux platform according to the android system refreshing mode.
Specifically, in an android compatible environment, the above process can be realized by monitoring an Activity calling process, when the Activity calling process is finished, the Activity calls an import function, at this time, whether a request with the same identifier as that of the current call exists in a call request queue is judged, if yes, the Activity belongs to the android application processed by the method, such as QQ, WeChat, microblog and the like, and the Activity corresponding to the Activity is concurrently called and requested to be deleted from the call request queue.
In the invention, the called Activity refers to Activity corresponding to an Activity calling request and an android application called by the Activity concurrent calling request. And the step of invoking the Activity refers to initiating an Activity invocation request and the Activity corresponding to the android application of which the Activity concurrently invokes the invocation request.
In summary, the above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (7)
- A method for using the same android application by multiple android applications on a Linux platform is characterized by comprising the following steps:step 1, acquiring a program package name, a called Activity name and a RequestID of a current Activity calling request in an android compatible environment, and determining LaunchMode of the called Activity;step 2, if an Activity concurrent calling request with the same package name and Activity name as the called Activity exists in the prestored request, executing step 4, otherwise, executing step 3;step 3, if the value of the launchMode is Standard, executing the Activity call request and returning to the step 1; if the value of the launch mode is not Standard, constructing an Activity concurrent call request with the Activity state as an execution state, adding the Activity concurrent call request to the tail of prestored information, and executing step 6;step 4, if the value of the LaunchMode is singleInstance, notifying a user of failed execution, and returning to the step 1; if the value of the launchMode is Standard, executing an Activity call request and returning to the step 1; if the value of the LaunchMode is SingleTop or SingleTask, executing step 5;step 5, constructing an Activity concurrent call request with an Activity state as a waiting state, and adding the Activity concurrent call request to the tail part of the prestored information;step 6, determining the calling Activities of the Activities concurrent calling requests, acquiring calling function names of the calling Activities, and executing step 7 if the same calling function names exist in the prestored calling functions; if the calling function name does not exist, adding the calling function name into the prestored calling function, prolonging the waiting time set in the timeout mechanism, suspending the execution of the Activity concurrent calling request, intercepting the input event sent to the calling Activity in the Linux platform, and regularly refreshing the content of a display window of the calling Activity on the Linux platform in the android compatible environment;step 7, if the Activity state of the Activity concurrent call request is an execution state, executing the Activity concurrent call request and returning to the step 1; if the Activity state is the waiting state, the waiting time set in the overtime mechanism is prolonged, and the Activity execution is suspended and the request execution step 8 is called;step 8, after the android compatible environment monitors that the current Activity call request or the concurrent Activity call request is responded, if the request with the same requestID exists in the prestored request, deleting the responded request from the prestored request and the prestored call function, if the Activity state of the responded request is an execution state, setting the Activity state of the first request in the prestored request as the execution state, re-executing the system operation of startActivity, and returning to the step 1; and if the request with the same requestID does not exist in the prestored requests, executing the current Activity call request or the concurrent Activity call request, and returning to the step 1.
- 2. The method according to claim 1, wherein after obtaining the package name, the called Activity name and the RequestID of the current Activity call request in the android compatible environment in step 1, if the called Activity related to the current Activity call request is an analysis target, obtaining LaunchMode of the called Activity; otherwise, executing the current Activity call request and returning to the step 1.
- 3. The method of claim 2, wherein the analysis objective includes QQ and WeChat Login, sharing, sending, and Payment Call functions.
- 4. The method of claim 1, wherein the pre-stored request is stored in a queue or file.
- 5. The method according to claim 1, wherein said determining Activity of Activity concurrent call requests in step 6 is by tracing back call stacks.
- 6. The method according to claim 1, wherein the waiting time in the step 6 is 30 seconds in the waiting time set in the timeout mechanism.
- 7. The method according to claim 1, wherein in step 8, after executing the current Activity call request or Activity concurrent call, forwarding the input event addressed to the call Activity to the android compatible environment in the Linux platform, and dynamically refreshing the content of the display window of the call Activity on the Linux platform in the android compatible environment.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210276873.XA CN114546536B (en) | 2022-03-21 | 2022-03-21 | Method for using same android application by multiple android applications on Linux platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210276873.XA CN114546536B (en) | 2022-03-21 | 2022-03-21 | Method for using same android application by multiple android applications on Linux platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114546536A CN114546536A (en) | 2022-05-27 |
| CN114546536B true CN114546536B (en) | 2022-07-05 |
Family
ID=81665889
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210276873.XA Active CN114546536B (en) | 2022-03-21 | 2022-03-21 | Method for using same android application by multiple android applications on Linux platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114546536B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107705122A (en) * | 2017-09-11 | 2018-02-16 | 福建新大陆支付技术有限公司 | The method and system of secure payment are carried out in Android system |
| CN110413352A (en) * | 2019-07-15 | 2019-11-05 | 北京天眼查科技有限公司 | The call method and device of application component |
| CN113254154A (en) * | 2021-05-21 | 2021-08-13 | 技德技术研究所(武汉)有限公司 | Application starting method and device for compatibly running Android system on Linux |
| CN114047933A (en) * | 2021-10-20 | 2022-02-15 | 北京鲸鲮信息系统技术有限公司 | Method, device, equipment and medium for multi-open Android application |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101997061B1 (en) * | 2017-09-29 | 2019-07-05 | 숭실대학교산학협력단 | Linux based android container platform, device equipped with the same and method for apply security system in linux based android container environment |
-
2022
- 2022-03-21 CN CN202210276873.XA patent/CN114546536B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107705122A (en) * | 2017-09-11 | 2018-02-16 | 福建新大陆支付技术有限公司 | The method and system of secure payment are carried out in Android system |
| CN110413352A (en) * | 2019-07-15 | 2019-11-05 | 北京天眼查科技有限公司 | The call method and device of application component |
| CN113254154A (en) * | 2021-05-21 | 2021-08-13 | 技德技术研究所(武汉)有限公司 | Application starting method and device for compatibly running Android system on Linux |
| CN114047933A (en) * | 2021-10-20 | 2022-02-15 | 北京鲸鲮信息系统技术有限公司 | Method, device, equipment and medium for multi-open Android application |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114546536A (en) | 2022-05-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10268531B2 (en) | Managing delivery of code and dependent data using application containers | |
| AU2018232915B2 (en) | System and method for introducing functionality to an application for use with a network service | |
| US9323556B2 (en) | Programmatic event detection and message generation for requests to execute program code | |
| US20170116051A1 (en) | Processing event messages for user requests to execute program code | |
| WO2018028055A1 (en) | Method and apparatus for running android application program on windows system | |
| US20060253548A1 (en) | Method and system for hosting and executing a component application | |
| US20150067167A1 (en) | Hot pluggable extensions for access management system | |
| CN109308241B (en) | Method and device for monitoring starting process of application program, terminal equipment and storage medium | |
| CN111625293B (en) | Terminal dual system based on linux kernel and hardware access management method thereof | |
| US7970885B2 (en) | Method for interacting with user and terminal thereof | |
| WO2019201340A1 (en) | Processor core scheduling method and apparatus, terminal, and storage medium | |
| US20170206119A1 (en) | System and method for achieving specific behaviors by intercepting file access calls in a mainframe rehosting platform | |
| CN106775952B (en) | Android application process management method and device | |
| GB2463370A (en) | Method of allowing an application to run as a service application on a mobile computing device. | |
| CN114860327B (en) | Quick starting method for android application in android compatible environment | |
| CN113032125A (en) | Job scheduling method, device, computer system and computer-readable storage medium | |
| CN114721807A (en) | Batch business task execution method, device, equipment, medium and program product | |
| CN112596757A (en) | Method and device for upgrading agent component of cloud desktop virtual machine and storage medium | |
| CN114201087A (en) | Method for displaying android application icon in Linux taskbar | |
| CN114546536B (en) | Method for using same android application by multiple android applications on Linux platform | |
| US8458716B2 (en) | Enterprise resource planning with asynchronous notifications of background processing events | |
| CN115640100B (en) | Virtual machine information synchronization method and computer readable medium | |
| WO2021129853A1 (en) | Mobile service upgrade method and apparatus, and terminal | |
| CN110445861B (en) | Container cloud platform service registration discovery method based on F5 adapter | |
| CN113535143A (en) | Stack information processing method and device, electronic 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |