CN115543699B - Application-transparent free scaling fault-tolerant method based on object snapshot - Google Patents

Application-transparent free scaling fault-tolerant method based on object snapshot Download PDF

Info

Publication number
CN115543699B
CN115543699B CN202211520750.2A CN202211520750A CN115543699B CN 115543699 B CN115543699 B CN 115543699B CN 202211520750 A CN202211520750 A CN 202211520750A CN 115543699 B CN115543699 B CN 115543699B
Authority
CN
China
Prior art keywords
activity
window
android application
android
snapshot
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
Application number
CN202211520750.2A
Other languages
Chinese (zh)
Other versions
CN115543699A (en
Inventor
温研
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Linzhuo Information Technology Co Ltd
Original Assignee
Beijing Linzhuo Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Linzhuo Information Technology Co Ltd filed Critical Beijing Linzhuo Information Technology Co Ltd
Priority to CN202211520750.2A priority Critical patent/CN115543699B/en
Publication of CN115543699A publication Critical patent/CN115543699A/en
Application granted granted Critical
Publication of CN115543699B publication Critical patent/CN115543699B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1438Restarting or rejuvenating
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements 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/44Arrangements for executing specific programs
    • G06F9/451Execution arrangements for user interfaces

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Quality & Reliability (AREA)
  • Retry When Errors Occur (AREA)

Abstract

The invention discloses an application transparent free scaling fault-tolerant method based on object snapshot, which comprises the steps of creating an Activity snapshot for Activity with changed size in an android compatible environment, protecting Activity Stack before restarting Activity operation, capturing response mode of abnormity in restarting Activity operation and determining abnormity according to abnormity characteristics, processing abnormity caused by size change of android application on the premise of not modifying android application codes, and realizing system level fault-tolerant processing of Activity crash.

Description

Application-transparent free scaling fault-tolerant method based on object snapshot
Technical Field
The invention belongs to the technical field of mobile application development, and particularly relates to an application transparent free scaling fault-tolerant method based on object snapshot.
Background
When an android application is run on a desktop platform, a need for scaling an android application window often arises according to a habit of a user using a desktop system. In the prior art, an android application is generally operated in a manner of installing an android operating environment on a desktop platform, a typical android compatible environment mainly includes an android application display unit and an android application compatible service, the android application display unit is used for implementing a user interface of the android application on a desktop operating system, the android application compatible service is used for providing the android compatible environment running on the desktop operating system, and the android application display unit and the android application compatible service are mutually matched to implement effective running of the android application on the desktop operating system.
In the existing android system, when the android application window changes, for example, the size of the android application window, the font or keyboard of the displayed text changes, the activtymanager in the framework layer of the android system triggers an activtyconfigurationchanged message and attempts to restart all active activities related to the application. Generally, an android application window is realized and controlled by an android system, and the Activity of the android application is realized by the android application itself. If the adaptive adjustment operation during the Activity restart is not considered in the android application development process, the problem of Activity crash caused by the adjustment of the size of the android application window may be generated, and the use mode of the android application determines that most application developers do not consider the problem, so that difficulty is brought to the use of the desktop system of the android application.
Disclosure of Invention
In view of this, the invention provides an application-transparent free-scaling fault-tolerant method based on an object snapshot, which can ensure the stability and reliability of an android application function when an android application window is scaled freely.
The invention provides an application transparent free scaling fault-tolerant method based on object snapshot, which specifically comprises the following steps:
step 1, when a scaling event related to an android application desktop window is generated in a desktop system, an android application display unit sends an android application window scaling event message containing the changed size of the android application window to an android compatible environment;
step 2, after receiving an android application window scaling event message sent by an android application display unit, the android compatible environment resets the size of a window of the android application according to the android application window scaling event message, and then creates active snapshots for all Activities of the android application, wherein all attributes of Activities are stored in the active snapshots; acquiring Activity Stack where each Activity is located, if the number of Activities stored in the Activity Stack is greater than 1, moving the Activity related to the current android application out of the Activity Stack, and recording the position of the Activity in the Activity Stack as an Activity index position;
step 3, the android compatible environment executes the operation of restarting all Activities, if the execution process generates abnormity, an abnormal call stack is analyzed after the abnormity is captured, if a function related to the Activity restart exists in the abnormal call stack, the step 4 is executed, otherwise, the step 5 is executed; if the execution process does not generate an exception, executing step 6;
step 4, resetting the corresponding Activity by adopting the attribute saved in the Activity snapshot created in the step 2, executing a redistribution operation on the android application window by adopting the window size of the android application reset in the step 2, and not throwing the exception upwards to finish the execution of the subsequent operation of the android system; if the Activity index position is null, executing step 7, otherwise, inserting Activity into Activity Stack according to the Activity index position and then executing step 7;
step 5, resetting the corresponding Activity by adopting the attribute saved in the Activity snapshot created in the step 2, executing the restarting operation of all Activities of the window corresponding to the android application by adopting the thread related to the current Activity operation, and not throwing the exception upwards to complete the execution of the subsequent operation of the android system; if the Activity index position is empty, executing step 7, otherwise, inserting Activity into the Activity Stack according to the Activity index position and then executing step 7;
step 6, if the Activity index position is empty, executing step 7, otherwise, inserting Activity into the Activity Stack according to the Activity index position and then executing step 7;
step 7, the android compatible environment sends an Activity restart completion message to the android application display unit; and after receiving the Activity restart finishing message, the android application display unit executes subsequent normal operation.
Further, when a zoom event related to the android application desktop window is generated in the desktop system in the step 1, the android application display unit creates an occlusion sub-window by using the size, screenshot and position of the current android application desktop window, and when the android application desktop window is zoomed, the occlusion sub-window is zoomed in an equal proportion.
Further, the occlusion sub-window is a Qt sub-window of the Image type.
Further, the creation of the occluded sub-window hides the display of the sub-window within the desktop window of the android application.
Further, in the step 7, the android application display unit destroys the blocked sub-window after receiving an Activity restart completion message.
Further, the way of saving all attributes of Activity in the Activity snapshot in step 2 is: after the attribute of the android application Activity is acquired, judging the data type of the attribute, and if the data type is POD, directly assigning the attribute value of the Activity to the Activity snapshot; if the data type is non-POD, judging whether the data type is a Java object, if so, assigning the reference of the Java object to the active snapshot, and if not, assigning the attribute value to the active snapshot.
Further, the attribute value is assigned to the active snapshot by calling an assignment function.
Has the beneficial effects that:
according to the method and the device, the Activity snapshot is created for the Activity with the changed size in the android compatible environment, the Activity Stack is protected before the operation of restarting the Activity in the android compatible environment, the abnormity is captured in the operation of restarting the Activity, and the response mode of the abnormity is determined according to the abnormity characteristics, so that the abnormity caused by the change of the size of the android application can be processed on the premise of not modifying the android application code, and the system level fault tolerance of Activity crash is realized.
Detailed Description
The present invention will be described in detail below with reference to examples.
The invention provides an application transparent free scaling fault-tolerant method based on object snapshot, which specifically comprises the following steps:
step 1, when a scaling event related to an android application desktop window is generated in a desktop system, an android application display unit sends an android application window scaling event message containing the changed size of the android application window to an android compatible environment.
The android application desktop window is an application window generated by an android application display unit in the desktop system of the android application. The android application display unit can send the scaling event message of the android application window to the android compatible environment through an RPC mechanism.
The android system is possible to be abnormal in the android application desktop window scaling process, the android application exits if the abnormity is not processed, and the android application desktop window is possible to have a black screen flicker phenomenon if the abnormity is processed.
Specifically, when a zoom event related to the android application desktop window is generated, the android application display unit stores the size, screenshot and position of the current android application desktop window (namely the android application desktop window before zooming), and creates an occlusion sub-window by adopting the stored size, screenshot and position, so that the occlusion sub-window has the same visual effect as the android application desktop window; when the android application desktop window is zoomed, the shielding sub-window is zoomed in an equal proportion, so that the zoomed android application desktop window can be continuously shielded.
In addition, in order to improve the operating performance of the android compatible environment, the display of the child window in the desktop window of the android application is hidden after the blocking child window is created, so that the refreshing operation related to the android application in the android compatible environment is reduced.
Step 2, after receiving an android application window scaling event message sent by an android application display unit, the android compatible environment resets the size of a window of the android application according to the android application window scaling event message, and then creates an active snapshot for all Activities of the android application, wherein all attributes of the Activities are stored in the active snapshot; and acquiring Activity Stack where each Activity is located, if the number of Activities stored in Activity Stack is greater than 1, removing Activity related to the current android application from Activity Stack, and recording the position of Activity in Activity Stack as Activity index position.
The process of creating Activity snapshots for all Activities of the android application can acquire classes corresponding to the Activities by using a reflection mechanism and then create instances of the classes.
In addition, in order to further improve the adaptability of the invention, after the attribute of the android application Activity is obtained, the Data type of the attribute is judged, and if the Data type is POD (plant Old Data), the attribute value of the Activity is directly assigned to the active snapshot; if the data type is non-POD, further judging whether the data type is Java objects such as Window or View, and the like, if so, assigning the reference of the Java objects to the active snapshot to prevent Activity from being released when an exception occurs, and if not, assigning the attribute value to the active snapshot. In the invention, the attribute value can be assigned to the active snapshot by calling an assignment function.
Step 3, the android compatible environment executes the operation of restarting all Activities, if the execution process generates abnormity, an abnormal call stack is analyzed after the abnormity is captured, if a function related to the Activity restart exists in the abnormal call stack, the step 4 is executed, otherwise, the step 5 is executed; if the execution process does not generate an exception, step 6 is executed.
Step 4, resetting the corresponding Activity by adopting the attribute saved in the Activity snapshot created in the step 2, executing a redistribution operation on the android application window by adopting the window size of the android application reset in the step 2, and not throwing the exception upwards to finish the execution of the subsequent operation of the android system; and if the Activity index position is null, executing the step 7, otherwise, inserting the Activity into the Activity Stack according to the Activity index position and then executing the step 7.
Step 5, resetting the corresponding Activity by adopting the attribute saved in the Activity snapshot created in the step 2, executing the restarting operation of all Activities of the window corresponding to the android application by adopting the thread related to the current Activity operation, and not throwing the exception upwards to complete the execution of the subsequent operation of the android system; and if the Activity index position is null, executing the step 7, otherwise, inserting the Activity into the Activity Stack according to the Activity index position and then executing the step 7.
And 6, if the Activity index position is null, executing the step 7, otherwise, inserting the Activity into the Activity Stack according to the Activity index position to execute the step 7.
Step 7, the android compatible environment sends an Activity restart completion message to the android application display unit; and after receiving the Activity restart completion message, the android application display unit executes subsequent normal operation.
And if the android application display unit creates a shielding child window which is the same as the desktop window of the android application, destroying the shielding child window after receiving the Activity restart finishing message so as to display the desktop window of the android application.
Example (b):
in this embodiment, the application-transparent free zooming fault-tolerant method based on the object snapshot provided by the present invention is adopted to implement the android application free zooming function with a fault-tolerant mechanism in the xDroid, and specifically includes the following steps:
s1, when an xDroidUI detects a Resize event related to a Linux window of an android application, executing the following operations:
s1.1, creating a Qt sub-window with the type of Image, wherein an Image displayed by the Qt sub-window is a screenshot of a Linux window of the android application before zooming, meanwhile, hiding and displaying the sub-window of the android application, and carrying out equal-ratio zooming on the Qt sub-window according to the zoomed size.
S1.2, sending an android application desktop window scaling event to an android application compatible service through an RPC mechanism.
S2, after receiving the android application window scaling event message sent by the android application display unit, the android compatible environment resets the sizes of all windows of the android application according to the android application window scaling event message, and then creates Activity snapshots for all Activities of the android application, wherein all attributes of Activities are stored in the Activity snapshots.
The specific process is that the relevant processing flow of acitvyconfigurationchanged in ActivityManager and activityStack in the android compatible environment is modified, and the process comprises the following steps:
for each Activity with the reset size, before the Relay Activity is executed on the Activity, creating an Activity snapshot of the Activity, wherein the Activity snapshot is created by acquiring and calling a getClass () method of the Activity by using a reflection mechanism to acquire a corresponding class, and then creating an instance of the class as ActivityClone; and then, acquiring all attributes of Activity by using a reflection mechanism, directly assigning an attribute value to an attribute corresponding to ActivityClone if the data type of the attribute is POD, assigning a reference of a Java object to the attribute corresponding to ActivityClone if the data type of the attribute is not POD but Java objects such as Window or View, and directly calling an assignment function if the data type of the attribute is neither POD nor Java object, such as an equal sign operator, and assigning an attribute value to the attribute corresponding to ActivityClone.
S3, if the version number of an android system corresponding to the android compatible environment is less than 9, that is, the system sets that a plurality of Activities belong to the same Activities Stack is explained, at this time, the Activities are moved out of the Activities Stack where the Activities are located, so that the possible abnormality of the Activities is prevented from affecting other Activities in the Activities Booth, the abnormality is difficult to process, the system is difficult to recover, and the index position of the Activities in the Activities Stack is recorded as IndexInStack; and if the android system version number corresponding to the android compatible environment is not less than 9, not processing.
And S4, introducing a Try-latch exception handling mechanism into codes called by related functions of the RelaunchActivity to capture all exceptions in the RelaunchActivity handling process, namely, protecting the related operations of the RelaunchActivity by adopting a Try-latch exception capturing code block. Related function calls of relaunch activity such as relaunch activity locked, etc.
S5, if abnormity is generated in the replay Activity processing process, judging whether related functions such as ActivitThread, handleRelaunchActivity functions and the like exist on an abnormity call stack after abnormity is captured, if so, assigning the related attributes of ActivitClone back to Activity, namely, recovering the Activity to the state before abnormity occurs, then using a new WindowSize to carry out replay operation on Window DecorView corresponding to the Activity, and normally executing subsequent operation without continuously throwing the abnormity upwards; if the Activity does not exist, the related attribute of the Activity clone is assigned back to Activity, that is, activity is restored to the state before the abnormality occurs, then a handleRelaunchActivity method of the thread where the current Activity is located is called, for example, the thread where the current Activity is located is obtained by calling a getActivities method, the handleRelaunchActivity method executes the releaset operation of decorView corresponding to Window of Activity, and the subsequent operation is normally executed without continuously throwing the abnormality upwards.
And S6, if the android system version number corresponding to the android compatible environment is less than 9, inserting the Activity back into the Activity Stack according to the position of the IndexInStack, and after the RelaunchActivity is processed, sending an Activity restart completion message to the xDroidVis through an RPC mechanism.
And S7, destroying the Qt sub-window and recovering the display of the sub-window in the desktop window of the android application after the xDroidUI receives the Activity restart finishing message.
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)

1. An application-transparent free scaling fault-tolerant method based on object snapshots is characterized by specifically comprising the following steps of:
step 1, when a scaling event related to an android application desktop window is generated in a desktop system, an android application display unit sends an android application window scaling event message containing the changed size of the android application window to an android compatible environment;
step 2, after receiving an android application window scaling event message sent by an android application display unit, the android compatible environment resets the size of a window of the android application according to the android application window scaling event message, and then creates an active snapshot for all Activities of the android application, wherein all attributes of the Activities are stored in the active snapshot; acquiring Activity Stack where each Activity is located, if the number of Activities stored in the Activity Stack is greater than 1, moving the Activity related to the current android application out of the Activity Stack, and recording the position of the Activity in the Activity Stack as an Activity index position;
step 3, the android compatible environment executes the operation of restarting all Activities, if the execution process generates abnormity, an abnormal call stack is analyzed after the abnormity is captured, if a function related to the Activity restart exists in the abnormal call stack, the step 4 is executed, otherwise, the step 5 is executed; if the execution process does not generate an exception, executing step 6;
step 4, resetting the corresponding Activity by adopting the attribute saved in the Activity snapshot created in the step 2, executing a re-layout operation on an android application window by adopting the window size of the android application reset in the step 2, and not throwing an exception upwards to complete the execution of the subsequent operation of the android system; if the Activity index position is empty, executing step 7, otherwise, inserting Activity into the Activity Stack according to the Activity index position and then executing step 7;
step 5, resetting the corresponding Activity by adopting the attribute saved in the Activity snapshot created in the step 2, executing the restarting operation of all Activities of the window corresponding to the android application by adopting the thread related to the current Activity operation, and not throwing the exception upwards to complete the execution of the subsequent operation of the android system; if the Activity index position is empty, executing step 7, otherwise, inserting Activity into the Activity Stack according to the Activity index position and then executing step 7;
step 6, if the Activity index position is null, executing step 7, otherwise, inserting Activity into Activity Stack according to the Activity index position and then executing step 7;
step 7, the android compatible environment sends an Activity restart completion message to the android application display unit; and after receiving the Activity restart finishing message, the android application display unit executes subsequent normal operation.
2. The free scaling fault-tolerant method according to claim 1, wherein in step 1, when a scaling event related to an android application desktop window is generated in the desktop system, the android application display unit creates an occlusion sub-window by using the size, screenshot and position of the current android application desktop window, and when the android application desktop window is scaled, the occlusion sub-window is scaled in an equal proportion.
3. The free scaling fault tolerant method of claim 2 wherein said occlusion sub-window is an Image type Qt sub-window.
4. The free scaling fault tolerant method of claim 2, wherein the creation of the occluded sub-window hides the display of the sub-window within the desktop window of the android application.
5. The free scaling fault tolerant method according to claim 2, wherein in step 7, the android application display unit destroys the blocked sub-window after receiving an Activity restart complete message.
6. The free scaling fault tolerant method according to claim 1, wherein said step 2 is characterized in that all attributes of Activity are saved in said active snapshot in a manner that: after the attribute of the android application Activity is acquired, judging the data type of the attribute, and if the data type is POD, directly assigning the attribute value of the Activity to the Activity snapshot; if the data type is non-POD, judging whether the data type is a Java object, if so, assigning the reference of the Java object to the active snapshot, and if not, assigning the attribute value to the active snapshot.
7. Freely scalable fault tolerant method according to claim 6, characterized in that the attribute values are assigned to the active snapshot by calling an assignment function.
CN202211520750.2A 2022-11-30 2022-11-30 Application-transparent free scaling fault-tolerant method based on object snapshot Active CN115543699B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211520750.2A CN115543699B (en) 2022-11-30 2022-11-30 Application-transparent free scaling fault-tolerant method based on object snapshot

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211520750.2A CN115543699B (en) 2022-11-30 2022-11-30 Application-transparent free scaling fault-tolerant method based on object snapshot

Publications (2)

Publication Number Publication Date
CN115543699A CN115543699A (en) 2022-12-30
CN115543699B true CN115543699B (en) 2023-02-03

Family

ID=84721950

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211520750.2A Active CN115543699B (en) 2022-11-30 2022-11-30 Application-transparent free scaling fault-tolerant method based on object snapshot

Country Status (1)

Country Link
CN (1) CN115543699B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116931933B (en) * 2023-09-19 2023-12-01 北京麟卓信息科技有限公司 Automatic judging method for application adaptive free scaling
CN117112118B (en) * 2023-10-20 2023-12-26 北京麟卓信息科技有限公司 View display integrity verification and repair method based on rendering process tracking

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020107972A1 (en) * 2018-11-27 2020-06-04 Oppo广东移动通信有限公司 Video decoding control method and apparatus, electronic device, and storage medium
CN113986446A (en) * 2021-12-23 2022-01-28 北京麟卓信息科技有限公司 Scaling optimization method for android application window in android running environment
CN114356158A (en) * 2021-12-21 2022-04-15 浪潮金融信息技术有限公司 Suspended window control method, system and medium for android application
WO2022228236A1 (en) * 2021-04-29 2022-11-03 华为技术有限公司 Method and apparatus for controlling android app, and terminal device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022169892A1 (en) * 2021-02-02 2022-08-11 Quantum Metric Inc. Detecting, diagnosing, and alerting anomalies in network applications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020107972A1 (en) * 2018-11-27 2020-06-04 Oppo广东移动通信有限公司 Video decoding control method and apparatus, electronic device, and storage medium
WO2022228236A1 (en) * 2021-04-29 2022-11-03 华为技术有限公司 Method and apparatus for controlling android app, and terminal device
CN114356158A (en) * 2021-12-21 2022-04-15 浪潮金融信息技术有限公司 Suspended window control method, system and medium for android application
CN113986446A (en) * 2021-12-23 2022-01-28 北京麟卓信息科技有限公司 Scaling optimization method for android application window in android running environment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
自适应显示环境可视化表达的线要素图形化简;刘子轩等;《测绘地理信息》;20170118(第01期);全文 *

Also Published As

Publication number Publication date
CN115543699A (en) 2022-12-30

Similar Documents

Publication Publication Date Title
CN115543699B (en) Application-transparent free scaling fault-tolerant method based on object snapshot
RU2286595C2 (en) Method for realization of computer multi-task system through virtual organization of thread processing
KR102003663B1 (en) Controlling generation of debug exceptions
JP2002268914A (en) Method for monitoring execution of privileged instruction
KR20180125498A (en) Android-based pop-up prompt methods and devices
EP2807541B1 (en) Image-based application automation
CN102890641B (en) Process behavior control method and device
KR20200139706A (en) Exception handling in transaction
CN108334779A (en) A kind of processing method of application, equipment and computer storage media
US20190121591A1 (en) Display structure, display method, display device and operating system
CN113467981A (en) Exception handling method and device
US20240231892A1 (en) Method, apparatus, device and storage medium for searching and killing a front-end process
CN110851294A (en) Method and device for remedying program operation breakdown
JPH10214208A (en) System for monitoring abnormality of software
US8261238B2 (en) Shield for user interface testing
CN116522299A (en) Application program window watermark adding method and device based on Linux system
CN109783261B (en) Crash processing method and device for terminal application, electronic equipment and storage medium
CN108345486B (en) Interface covering method, equipment and readable medium
US11671440B1 (en) Detection failure monitoring system
CN113127260A (en) Display exception handling method, device, equipment and medium
CN110837433A (en) Performance optimization method and device and electronic equipment
CN111563000A (en) File generation method, intelligent terminal and storage medium
CN111814180A (en) Method for ensuring safety of financial App local operating environment
CN102004669A (en) Computer system suitable for child to operate and control method thereof
CN114546598B (en) Control method for processes, files and network access in container

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