CN116028267A - Dual-system secure mobile phone resetting method and device, server and storage medium - Google Patents

Dual-system secure mobile phone resetting method and device, server and storage medium Download PDF

Info

Publication number
CN116028267A
CN116028267A CN202211674267.XA CN202211674267A CN116028267A CN 116028267 A CN116028267 A CN 116028267A CN 202211674267 A CN202211674267 A CN 202211674267A CN 116028267 A CN116028267 A CN 116028267A
Authority
CN
China
Prior art keywords
container
init
reset
file
restarting
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211674267.XA
Other languages
Chinese (zh)
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.)
Tianyi Telecom Terminals Co Ltd
Original Assignee
Tianyi Telecom Terminals 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 Tianyi Telecom Terminals Co Ltd filed Critical Tianyi Telecom Terminals Co Ltd
Priority to CN202211674267.XA priority Critical patent/CN116028267A/en
Priority to PCT/CN2022/143688 priority patent/WO2024138588A1/en
Publication of CN116028267A publication Critical patent/CN116028267A/en
Pending legal-status Critical Current

Links

Images

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
    • 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/4401Bootstrapping
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Computer Security & Cryptography (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Telephone Function (AREA)

Abstract

The embodiment of the invention discloses a dual-system secure mobile phone resetting method, a device, a server and a storage medium. Wherein the method comprises the following steps: restarting a container corresponding to the reset operation, and generating a restart modification sub-process by utilizing an init process; determining an init process of the reset container and an init. Rc file of the reset container; modifying a file mount part in a main function of an init.rc file of the reset container by utilizing a restarting modification subprocess so as to point to a corresponding data file for resetting; loading a mirror image of the container at the previous exit; and adjusting the init process of the reset container by utilizing a restarting modification subprocess so that the init process directly jumps to the file mounting part in the guiding init. Rc script to run. The resetting operation saves the erasing process of the data file, does not need to mount the hardware driver again, greatly saves the system resetting time corresponding to the container, and improves the user experience of resetting by using the dual-system mobile phone.

Description

Dual-system secure mobile phone resetting method and device, server and storage medium
Technical Field
The embodiment of the invention relates to the technical field of mobile terminals, in particular to a dual-system secure mobile phone resetting method, a device, a server and a storage medium.
Background
With the continuous advancement of mobile terminal technology, smart phones are widely used in various scenarios. Becomes an inseparable tool in daily work and life. To facilitate separation of work and life, and for security reasons, some users employ a dual-handset strategy, with one handset for life and the other for office use. Based on the above-mentioned needs of users, dual-system secure handsets have been developed. The dual system secure handset is capable of using two systems in parallel by means of container technology. The background system can be awakened at any time, so that the simultaneous switching of the two systems is realized;
in the process of realizing the invention, the inventor finds the following technical problems: in the use process of the mobile phone, the mobile phone cannot be restored to the factory setting operation. However, for the dual system handset described above, three systems are actually provided: the Linux system after slimming is used for realizing configuration and calling of a bottom layer interface and is responsible for starting an android system corresponding to each container, and error exception is easy to generate when a user performs reset operation; in the existing mode, the host is required to inform the container of the factory setting restoration information, select Boot Loader in the container, erase the corresponding file content in the file system, and finish restarting. The factory setting can be restored, the time consumption is close to that of OTA upgrading, and the use experience of a user is affected.
Disclosure of Invention
The embodiment of the invention provides a dual-system safe mobile phone resetting method, a device, a server and a storage medium, which are used for solving the technical problem that the time consumption for resetting the dual-system safe mobile phone in the prior art is long.
In a first aspect, an embodiment of the present invention provides a dual-system secure mobile phone resetting method, including:
restarting a container corresponding to the reset operation, and generating a restart modification sub-process by utilizing an init process;
determining an init process of the reset container and an init. Rc file of the reset container;
modifying a file mount part in a main function of the init.rc file of the reset container by utilizing a restarting modification subprocess so as to point to a mirror image when the corresponding data file is loaded into the container and exits for the last time;
and adjusting the init process of the reset container by utilizing a restarting modification subprocess so that the init process directly jumps to the file mounting part in the guiding init. Rc script to run.
In a second aspect, an embodiment of the present invention further provides a dual-system secure mobile phone resetting device, including:
the generation module is used for restarting the container corresponding to the reset operation and generating a restarting modification subprocess by utilizing the init process;
the determining module is used for determining an init process of the reset container and an init.rc file of the reset container;
the modification module is used for modifying the file mounting part in the main function of the init.rc file of the reset container by utilizing the restarting modification subprocess so as to point to the corresponding data file of the corresponding reset;
the loading module is used for loading the mirror image of the container when the container exits for the previous time;
and the adjusting module is used for adjusting the init process of the reset container by utilizing the restarting modification subprocess so that the init process directly jumps to the file mounting part in the guiding init.rc script to run.
In a third aspect, an embodiment of the present invention further provides a server, including:
one or more processors;
a storage means for storing one or more programs;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the dual system secure handset reset method as provided in the above embodiments.
In a fourth aspect, embodiments of the present invention also provide a storage medium containing computer executable instructions which, when executed by a computer processor, are used to perform a dual system secure handset reset method as provided by the above embodiments.
According to the dual-system secure mobile phone resetting method, device, server and storage medium provided by the embodiment of the invention, the restart modification subprocess is generated by utilizing the init process through restarting the container corresponding to the resetting operation; determining an init process of the reset container and an init. Rc file of the reset container; modifying a file mount part in a main function of an init.rc file of the reset container by utilizing a restarting modification subprocess so as to point to a corresponding data file for resetting; loading a mirror image of the container at the previous exit; and adjusting the init process of the reset container by utilizing a restarting modification subprocess so that the init process directly jumps to the file mounting part in the guiding init. Rc script to run. The interference capability of the host machine to the container is fully utilized, and the restarting modification subprocess is generated by utilizing the kernel process of the host machine. The init.rc script of the container which needs to be subjected to system reset is modified, corresponding mounted file data are adjusted, and the init process corresponding to the container is adjusted, so that the init script is directly jumped to the recorded file mounting part in the guided init.rc script to run, and the corresponding hardware mounting part is not required to be reconfigured, so that the erasing process of the data file is saved in the resetting operation, the hardware driving is not required to be mounted again, the system resetting time corresponding to the container is greatly saved, and the user experience of resetting by using the dual-system mobile phone is improved.
Drawings
Other features, objects and advantages of the present invention will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the accompanying drawings in which:
fig. 1 is a flowchart of a dual-system secure mobile phone resetting method according to a first embodiment of the present invention;
fig. 2 is a schematic diagram of a dual-system secure mobile phone architecture in a dual-system secure mobile phone resetting method according to a first embodiment of the present invention;
fig. 3 is a flowchart of a dual-system secure mobile phone resetting method according to a second embodiment of the present invention;
fig. 4 is a flowchart of a dual-system secure mobile phone resetting method according to a third embodiment of the present invention;
fig. 5 is a block diagram of a dual-system secure mobile phone resetting device according to a fourth embodiment of the present invention;
fig. 6 is a structural diagram of a server according to a fifth embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
Example 1
Fig. 1 is a flowchart of a dual-system secure mobile phone resetting method according to an embodiment of the present invention, where the method is applicable to a case of quickly resetting one of the systems in the dual-system secure mobile phone, and the method may be executed by a dual-system secure mobile phone resetting device and correspondingly set in a terminal of the dual-system secure mobile phone, and specifically includes the following steps:
and 110, restarting a container corresponding to the reset operation, and generating a restart modification sub-process by using the init process.
An exemplary dual-system mobile phone may be implemented by using a container technology, and fig. 2 is a schematic diagram of dual-system secure mobile phone architecture in a dual-system secure mobile phone resetting method according to an embodiment of the present invention, referring to fig. 2, where the dual-system secure mobile phone includes: the lean Linux system (basic platform) is used for bottom hardware and corresponding driving, and provides a corresponding hardware foundation for the double systems. While the dual system is implemented by container technology, LXC (Linux Container) technology is exemplary. LXCs can provide lightweight virtualization to isolate processes and resources, and do not need to provide instruction interpretation mechanisms and other complexities of full virtualization. The LXC can realize hardware control of the basic platform by means of hardware driving of the basic platform.
In this embodiment, the user may reset the system corresponding to LXC through the operation, that is, restore the factory setting operation.
And restarting the container corresponding to the factory setting restoration operation when receiving the reset operation. Illustratively, at startup, the restart modification sub-process is generated by utilizing the init process of the lean Linux system. The init process is one of the programs indispensable in the operation of the Linux system, and is a user-level process started by the kernel.
Because the restarting container is required to be controlled, a corresponding process is required to be implanted into the Linux system after the weight is reduced to realize the purpose of controlling the restarting container. Because only the drive of hardware is provided in the Linux system after slimming, a hardware foundation is provided for the LXC. Therefore, the number of processes is small, and only init processes exist in the processes which can survive in the normal period of the Linux system after weight reduction. Thus, the init process may be utilized to generate a restart modification sub-process, which may be utilized to implement the adjustment and control of the system in the LXC container.
Step 120, determining an init process of the reset container and an init. Rc file of the reset container.
In this embodiment, there are three systems. And the reset corresponds to only one of the systems, therefore, firstly, the init process corresponding to the restarting system and the init. Rc file of the reset container need to be determined. Since the restart system is implemented using LXC containers, it is necessary to determine the init process of the reset container and the init. Rc file of the reset container. For example, the init process of the reset container and the init. Rc file of the reset container may be determined by corresponding reference numerals, or generation times.
And 130, modifying the file mounting part in the main function of the init.rc file of the reset container by utilizing a restarting modification subprocess so as to point to the corresponding data file of the corresponding reset.
init.rc is based on AIL (Android Init Language) being a very simple language, mainly used to define what needs to be done in the initialization procedure. Main functions are arranged in init.rc, and mainly comprise five types of sentences: action, command, service, option, import. Options are an option for Service, used in conjunction with Service. In which a corresponding data file may be defined. For example, the data file corresponding to the overlay may be loaded using a chown < owner > < group > < path > option statement. Wherein chown is used to change the genus owner and/or genus group of each file. In this embodiment, the method may be defined as a generic group of the container, and the path for resetting the corresponding data file is written into the corresponding < path >, and the corresponding service is started with an on flag.
Step 140, loading the mirror image of the container when the container exits last time.
After the container is started, a corresponding mirror image needs to be loaded, and the mirror image can be the mirror image when the container exits last time.
And step 150, adjusting the init process of the reset container by utilizing a restarting modification subprocess so that the init process directly jumps to the file mounting part recorded in the guiding init.rc script to run.
Normally, the init process usually only needs to remain alive all the time, without any adjustments, since the previous image has been loaded. In this embodiment, however, the file data is changed, and the init. Therefore, the init process needs to be adjusted to register file data in main functions in the init. Rc script. Because the loading mirror image method is adopted, the hardware driver part is loaded, and the init process does not need to reload the hardware driver and only needs to re-register the corresponding data file. Therefore, the init process of the reset container can be controlled by utilizing the restarting modification subprocess, the hardware driving part is skipped to be loaded, and the operation is directly skipped to the operation script of the file mounting part recorded in the guide init.
In the embodiment, the restart modification subprocess is generated by utilizing the init process through restarting the container corresponding to the reset operation; determining an init process of the reset container and an init. Rc file of the reset container; modifying a file mount part in a main function of an init.rc file of the reset container by utilizing a restarting modification subprocess so as to point to a corresponding data file for resetting; loading a mirror image of the container at the previous exit; and adjusting the init process of the reset container by utilizing a restarting modification subprocess so that the init process directly jumps to the file mounting part in the guiding init. Rc script to run. The interference capability of the host machine to the container is fully utilized, and the restarting modification subprocess is generated by utilizing the kernel process of the host machine. The init.rc script of the container which needs to be subjected to system reset is modified, corresponding mounted file data are adjusted, and the init process corresponding to the container is adjusted, so that the init script is directly jumped to the recorded file mounting part in the guided init.rc script to run, and the corresponding hardware mounting part is not required to be reconfigured, so that the erasing process of the data file is saved in the resetting operation, the hardware driving is not required to be mounted again, the system resetting time corresponding to the container is greatly saved, and the user experience of resetting by using the dual-system mobile phone is improved.
In a preferred implementation of this embodiment, the method may further comprise the steps of: and adding factory setting restoration broadcasting service in the container system by restarting the modification subprocess, broadcasting factory setting restoration information, and enabling the android system to clear the memory content. Because the mobile phone service is provided by adopting a container loading mirror image mode, some active processes including a system process and an application process exist in the loaded mirror image, and the situation of occupying original user data exists in the processes. At this time, a sub-process can be derived from the init process in the container system by restarting the modification sub-process, and is used for providing corresponding broadcasting service, broadcasting all processes in the container system, broadcasting corresponding factory setting information, so that the corresponding processes clear the memory content, and avoiding the read-write errors of the system.
Example two
Fig. 3 is a flowchart of a dual-system secure mobile phone resetting method according to a second embodiment of the present invention. The present embodiment is optimized based on the above embodiment, and in this embodiment, the method may further include the following steps; when receiving the reset operation of the current system, storing a container mirror image corresponding to the current system; reading an init process from a kernel, acquiring a container code corresponding to the current system from the init process, and resetting user data in the current system; closing the container corresponding to the container code.
Correspondingly, the dual-system secure mobile phone resetting method provided by the embodiment specifically comprises the following steps:
step 210, when receiving the reset operation of the current system, saving the container mirror image corresponding to the current system.
In this embodiment, the user may implement resetting the currently used system by operating the dual system secure mobile phone. To facilitate user operation, the system reset operation may be consistent with normal cell phone operation. And when a system reset operation is received, determining a container currently in a foreground active state, and storing a container mirror image corresponding to the current system.
And 220, reading an init process from a kernel, acquiring a container code corresponding to the current system from the init process, and resetting user data in the current system.
And reading an init process of the thinned Linux system from the kernel of the thinned Linux system, wherein the init process of the thinned Linux system is responsible for managing containers, acquiring a container code of the current system from the process, and resetting user data in the current system by utilizing the container code.
For example, a file system environment corresponding to the container number may be searched, where the file system environment may be a folder under a root2 (2 is the container number) directory, including: folders such as/dev,/sys,/etc,/data,/cache,/metadata, etc.
The original data file system comprises the following steps: and (3) clearing folders such as/data,/cache,/metadata and the like, and resetting user data in the current system.
And 230, closing the container corresponding to the container code.
And closing the container corresponding to the container code, so as to facilitate the later restarting and realize the recovery of the system from factory setting.
Step 240, restarting the container corresponding to the reset operation, and generating a restart modification sub-process by using the init process.
Step 250, determining an init process of the reset container and an init. Rc file of the reset container.
Step 260, modify the file mount portion in the main function of the init.rc file of the reset container by using the restart modification sub-process to point to the corresponding data file of the corresponding reset.
Step 260, loading the mirror image of the previous exit of the container.
And step 270, adjusting the init process of the reset container by utilizing the restarting modification subprocess, so that the init process directly jumps to the file mounting part recorded in the guiding init.rc script to run.
The embodiment adds the following steps: when receiving the reset operation of the current system, storing a container mirror image corresponding to the current system; reading an init process from a kernel, acquiring a container code corresponding to the current system from the init process, and resetting user data in the current system; closing the container corresponding to the container code. When receiving the reset operation, the container system corresponding to the reset operation is definitely determined, so that the interference of the reset to other systems is avoided, and the user data file needing to restore the factory setting can be correctly selected.
In a preferred implementation of this embodiment, after closing the container corresponding to the container code, the method may further comprise the steps of: and distinguishing and isolating the user data of the current system by using a naming space. Namespace is a "namespace," also known as "namespace. Is a form of code organization used by many programming languages, categorized by namespace. The user data of the current system can be effectively distinguished from other user data by using the naming space.
In another preferred implementation of the present embodiment, the method may further comprise the steps of: and dividing the resources of the restarted container by using the Cgroup according to the resources of the container when the container exits last time, so that the Cgroup consistent with the resources of the container exits last time can refer to a specific process group. The Cgroup is a mechanism for managing processes according to groups in Linux, and in the user plane, the Cgroup technology can organize all processes in each system into an independent tree, each tree contains all processes of the system, and each node of the tree is a process group. Through the Cgroup mechanism, all processes when the container exits last time can be determined, and corresponding resources can be determined. The resources required by various processes can be correspondingly set, and the resources after the container is started can be kept consistent. Avoiding the occurrence of system errors.
Example III
Fig. 4 is a flow chart of a dual-system secure mobile phone resetting method according to a third embodiment of the present invention. The present embodiment optimizes the data file corresponding to the reset based on the above embodiment, and in this embodiment, the data file corresponding to the reset is specifically optimized as follows: a data file prior to a reset operation, the data file prior to the reset operation comprising: the container belongs to the hidden attribute and recovers the hidden mark attribute; correspondingly, the current system reset operation package is specifically optimized as follows: the current system resumes operation; correspondingly, the init process of the reset container is adjusted by using the restart modification subprocess, and is specifically optimized as follows: and adding a recovery operation level to the init process of the reset container by using the restarting modification subprocess, wherein the recovery operation level corresponds to the init process of the container and directly jumps to the file mounting part in the guiding init. Rc script to operate.
Correspondingly, the dual-system secure mobile phone resetting method provided by the embodiment specifically comprises the following steps:
step 310, restarting the container corresponding to the recovery operation, and generating a restart modification sub-process by using the init process.
Step 320, determining an init process of the recovery container and an init. Rc file of the recovery container.
And 330, modifying the file mount part in the main function of the init.rc file of the recovery container by utilizing the restarting modification subprocess to point to the data file before the corresponding resetting operation.
In this embodiment, not only the mobile phone reset but also the recovery service can be provided. That is, the user may restore the factory setting of the current system by mistake or other reasons, and want to restore to the previous state, and then the method provided by this embodiment may be implemented. Illustratively, the data file prior to the reset operation includes: container attribute hiding and restore hidden flag attribute. In this embodiment, after receiving the reset operation of the user, the existing user data file may be transferred to another storage location and set to an unwritable state. Meanwhile, the hidden attribute of the container attribution can be added to the user data file according to the corresponding relation between the user data file and the container, the hidden attribute is in an invisible state, and only the init process of the Linux system after slimming can be read. Correspondingly, newly creating user data for the current system, and adding a container attribution hiding attribute for the newly created user data to avoid file pointing errors. In addition, the data file before the resetting operation needs to additionally increase or decrease the attribute of the recovery hidden mark for marking the corresponding container and the time during the resetting operation, so that the corresponding user data file can be conveniently searched during the recovery.
Step 340, loading the mirror image of the previous exit of the container.
And 350, adding a recovery operation level to the init process of the reset container by utilizing the restarting modification subprocess, wherein the recovery operation level corresponds to the operation of the init process of the container and directly jumps to the file mounting part in the guiding init. Rc script.
The original init is divided into 7 levels, and the 7 levels are respectively a shutdown level, a single user mode, a multi-user (not networked), a complete multi-user mode (standard operation level), a security mode, a graphical interface mode and a restarting level, and in the embodiment, the two levels can be adjusted to increase the recovery level. The user can generate a recovery operation through the combined operation of the physical keys of the dual-system secure mobile phone. And adding a recovery operation level to the init process of the reset container, so that the init process directly jumps to the file mounting part in the guide init. Rc script to operate, and a quick recovery function is realized.
The embodiment specifically optimizes the data file corresponding to the reset as follows: a data file prior to a reset operation, the data file prior to the reset operation comprising: the container belongs to the hidden attribute and recovers the hidden mark attribute; correspondingly, the current system reset operation package is specifically optimized as follows: the current system resumes operation; correspondingly, the init process of the reset container is adjusted by using the restart modification subprocess, and is specifically optimized as follows: and adding a recovery operation level to the init process of the reset container by using the restarting modification subprocess, wherein the recovery operation level corresponds to the init process of the container and directly jumps to the file mounting part in the guiding init. Rc script to operate. The quick recovery operation of the single system in the double-system safety mobile phone can be realized.
Example IV
Fig. 5 is a schematic structural diagram of a dual-system secure mobile phone resetting device according to a fourth embodiment of the present invention, as shown in fig. 5, the device includes:
a generating module 410, configured to restart the container corresponding to the reset operation, and generate a restart modification sub-process by using the init process;
a determining module 420, configured to determine an init process of the reset container and an init. Rc file of the reset container;
a modification module 430, configured to modify, with a restart modification sub-process, a file mount portion in a main function of an init.rc file of the reset container to point to a corresponding reset corresponding data file;
a loading module 440 for loading the mirror image of the previous exit of the container;
and the adjusting module 450 is configured to adjust the init process of the reset container by using the restart modification sub-process, so that the init process directly jumps to the file mounting part in the boot init. Rc script to run.
According to the dual-system secure mobile phone resetting device provided by the embodiment, a restarting modification sub-process is generated by using an init process through restarting a container corresponding to a resetting operation; determining an init process of the reset container and an init. Rc file of the reset container; modifying a file mount part in a main function of an init.rc file of the reset container by utilizing a restarting modification subprocess so as to point to a corresponding data file for resetting; loading a mirror image of the container at the previous exit; and adjusting the init process of the reset container by utilizing a restarting modification subprocess so that the init process directly jumps to the file mounting part in the guiding init. Rc script to run. The interference capability of the host machine to the container is fully utilized, and the restarting modification subprocess is generated by utilizing the kernel process of the host machine. The init.rc script of the container which needs to be subjected to system reset is modified, corresponding mounted file data are adjusted, and the init process corresponding to the container is adjusted, so that the init script is directly jumped to the recorded file mounting part in the guided init.rc script to run, and the corresponding hardware mounting part is not required to be reconfigured, so that the erasing process of the data file is saved in the resetting operation, the hardware driving is not required to be mounted again, the system resetting time corresponding to the container is greatly saved, and the user experience of resetting by using the dual-system mobile phone is improved.
On the basis of the above embodiments, the device further includes:
the storage module is used for storing the container mirror image corresponding to the current system when receiving the reset operation of the current system;
the reading module is used for reading an init process from the kernel, acquiring a container code corresponding to the current system from the init process, and resetting user data in the current system;
and the closing module is used for closing the container corresponding to the container code.
On the basis of the above embodiments, the upgrade code temporary storage area is the same as the second flash memory area of the vehicle ECU.
On the basis of the above embodiments, the device further includes:
and the isolation module is used for distinguishing and isolating the user data of the current system by using the name space.
On the basis of the above embodiments, the device further includes:
and the dividing module is used for dividing the restarted container resources by utilizing the cgroup according to the container resources when the container exits last time so as to be consistent with the previously exited resources.
On the basis of the above embodiments, the device further includes:
the attribute adding module is used for adding the attribute hiding attribute of the container for the user data file according to the corresponding relation between the user data file and the container;
correspondingly, the reading module comprises:
and the new building unit is used for building user data for the current system and adding the attribute of the container attribution hiding attribute for the new user data.
On the basis of the above embodiments, the resetting the corresponding data file includes:
a data file prior to a reset operation, the data file prior to the reset operation comprising: the container belongs to the hidden attribute and recovers the hidden mark attribute;
the current system reset operation includes:
the current system resumes operation;
the adjustment module comprises:
and the level increasing unit is used for increasing the recovery operation level for the init process of the reset container by utilizing the restarting modification subprocess, wherein the recovery operation level corresponds to the init process of the container and directly jumps to the file mounting part operation recorded in the guiding init. Rc script.
The dual-system safe mobile phone resetting device provided by the embodiment of the invention can execute the dual-system safe mobile phone resetting method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example five
Fig. 6 is a schematic structural diagram of a server according to a fifth embodiment of the present invention. Fig. 6 shows a block diagram of an exemplary server 12 suitable for use in implementing embodiments of the present invention. The server 12 shown in fig. 6 is merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 6, the server 12 is in the form of a general purpose computing server. The components of server 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, a bus 18 that connects the various system components, including the system memory 28 and the processing units 16.
Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, micro channel architecture (MAC) bus, enhanced ISA bus, video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.
Server 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by server 12 and includes both volatile and nonvolatile media, removable and non-removable media.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and/or cache memory 32. The server 12 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 34 may be used to read from or write to non-removable, nonvolatile magnetic media (not shown in FIG. 6, commonly referred to as a "hard disk drive"). Although not shown in fig. 6, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. The system memory 28 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of the embodiments of the invention.
A program/utility 40 having a set (at least one) of program modules 42 may be stored in, for example, system memory 28, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods of the embodiments described herein.
The server 12 may also communicate with one or more external servers 14 (e.g., keyboard, pointing server, display 24, etc.), with one or more servers that enable users to interact with the server 12, and/or with any servers (e.g., network card, modem, etc.) that enable the server 12 to communicate with one or more other computing servers. Such communication may occur through an input/output (I/O) interface 22. Also, the server 12 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, via a network adapter 20. As shown, network adapter 20 communicates with the other modules of server 12 via bus 18. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with server 12, including, but not limited to: microcode, server drives, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, for example, implementing the dual system secure handset reset method provided by the embodiment of the invention.
Example six
A sixth embodiment of the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform the dual system secure handset reset method as provided in any of the above embodiments.
The computer storage media of embodiments of the invention may take the form of any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or terminal. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.

Claims (10)

1. The dual-system secure mobile phone resetting method is characterized by comprising the following steps of:
restarting a container corresponding to the reset operation, and generating a restart modification sub-process by utilizing an init process;
determining an init process of the reset container and an init. Rc file of the reset container;
modifying a file mount part in a main function of an init.rc file of the reset container by utilizing a restarting modification subprocess so as to point to a corresponding data file for resetting;
loading a mirror image of the container at the previous exit;
and adjusting the init process of the reset container by utilizing a restarting modification subprocess so that the init process directly jumps to the file mounting part in the guiding init. Rc script to run.
2. The method according to claim 1, wherein the method further comprises:
when receiving the reset operation of the current system, storing a container mirror image corresponding to the current system;
reading an init process from a kernel, acquiring a container code corresponding to the current system from the init process, and resetting user data in the current system;
closing the container corresponding to the container code.
3. The method of claim 2, wherein after closing the container corresponding to the container code, the method further comprises, prior to restarting the container:
and distinguishing and isolating the user data of the current system by using a naming space.
4. A method according to claim 3, characterized in that the method further comprises:
and dividing the resources of the restarted container by utilizing the cgroup according to the resources of the container when the container exits last time so as to be consistent with the resources of the container which exits last time.
5. The method according to claim 4, wherein the method further comprises:
adding a container attribution hiding attribute to the user data file according to the corresponding relation between the user data file and the container;
correspondingly, the resetting the user data in the current system includes:
newly establishing user data for the current system, and adding a container attribution hiding attribute for the newly established user data.
6. The method of claim 5, wherein resetting the corresponding data file comprises:
a data file prior to a reset operation, the data file prior to the reset operation comprising: the container belongs to the hidden attribute and recovers the hidden mark attribute;
accordingly, the current system reset operation includes:
the current system resumes operation;
correspondingly, the adjusting the init process of the reset container by using the restart modification sub-process includes:
and adding a recovery operation level to the init process of the reset container by using the restarting modification subprocess, wherein the recovery operation level corresponds to the init process of the container and directly jumps to the file mounting part in the guiding init. Rc script to operate.
7. The method according to any one of claims 1-6, further comprising:
and adding factory setting restoration broadcasting service in the container system by utilizing the restarting modification subprocess, broadcasting factory setting restoration information, and enabling the system of the resetting container to clear the memory content.
8. A dual system secure handset reset device comprising:
the generation module is used for restarting the container corresponding to the reset operation and generating a restarting modification subprocess by utilizing the init process;
the determining module is used for determining an init process of the reset container and an init.rc file of the reset container;
the modification module is used for modifying the file mounting part in the main function of the init.rc file of the reset container by utilizing the restarting modification subprocess so as to point to the corresponding data file of the corresponding reset;
the loading module is used for loading the mirror image of the container when the container exits for the previous time;
and the adjusting module is used for adjusting the init process of the reset container by utilizing the restarting modification subprocess so that the init process directly jumps to the file mounting part in the guiding init.rc script to run.
9. A server, the server comprising:
one or more processors;
a storage means for storing one or more programs;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the dual system secure handset reset method of any of claims 1-7.
10. A storage medium containing computer executable instructions which when executed by a computer processor are for performing the dual system secure handset reset method of any of claims 1-7.
CN202211674267.XA 2022-12-26 2022-12-26 Dual-system secure mobile phone resetting method and device, server and storage medium Pending CN116028267A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202211674267.XA CN116028267A (en) 2022-12-26 2022-12-26 Dual-system secure mobile phone resetting method and device, server and storage medium
PCT/CN2022/143688 WO2024138588A1 (en) 2022-12-26 2022-12-30 Dual-system secure mobile phone resetting method and apparatus, terminal, and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211674267.XA CN116028267A (en) 2022-12-26 2022-12-26 Dual-system secure mobile phone resetting method and device, server and storage medium

Publications (1)

Publication Number Publication Date
CN116028267A true CN116028267A (en) 2023-04-28

Family

ID=86080611

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211674267.XA Pending CN116028267A (en) 2022-12-26 2022-12-26 Dual-system secure mobile phone resetting method and device, server and storage medium

Country Status (2)

Country Link
CN (1) CN116028267A (en)
WO (1) WO2024138588A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117075984A (en) * 2023-10-17 2023-11-17 海马云(天津)信息技术有限公司 Module processing method, device, communication equipment and computer readable storage medium

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8612735B2 (en) * 2010-12-27 2013-12-17 Verizon Patent And Licensing Inc. Resetting an LTE unit that is not in a readily accessible location
CN107704337B (en) * 2017-08-22 2020-08-25 北京珠穆朗玛移动通信有限公司 Factory setting restoring method, mobile terminal and device with storage function
CN107918567A (en) * 2017-10-20 2018-04-17 广州视源电子科技股份有限公司 Method and system for restoring factory settings, readable storage medium and electronic device
CN111786904B (en) * 2020-07-07 2021-07-06 上海道客网络科技有限公司 System and method for realizing container dormancy and awakening

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117075984A (en) * 2023-10-17 2023-11-17 海马云(天津)信息技术有限公司 Module processing method, device, communication equipment and computer readable storage medium
CN117075984B (en) * 2023-10-17 2023-12-26 海马云(天津)信息技术有限公司 Module processing method, device, communication equipment and computer readable storage medium

Also Published As

Publication number Publication date
WO2024138588A1 (en) 2024-07-04

Similar Documents

Publication Publication Date Title
US20220053068A1 (en) Methods, apparatuses and computer storage media for applet state synchronization
CN101751273B (en) Safety guide device and method for embedded system
US9436557B2 (en) Method and computation node for processing application data
US20080114923A1 (en) Apparatus and method for controlling operation processing in nonvolatile memory
CN105468410B (en) Method for upgrading system and device
WO2015074526A1 (en) Method and apparatus for injecting java by tecode into target process
CA2710416C (en) Method and device for application archiving
CN109284142A (en) File preloads method, apparatus, electronic equipment and computer readable storage medium
CN114721719B (en) Method and system for containerized deployment of heterogeneous applications in cluster
CN116028267A (en) Dual-system secure mobile phone resetting method and device, server and storage medium
US9852028B2 (en) Managing a computing system crash
CN116643778B (en) Application program optimization method and electronic equipment
KR102663196B1 (en) User terminal device, server, control method of user terminal device and control method of server
CN116700768B (en) Application processing method and related device
CN111399926A (en) Method and device for downloading starting program
CN106843895B (en) Method, system and readable storage medium for processing requests
US20150128208A1 (en) Apparatus and method for dynamically controlling security in computing device with plurality of security modules
CN115185745A (en) Data processing method, system, electronic device and computer readable storage medium
CN101714092A (en) Method for controlling boot sequence of server
CN108121562B (en) Firmware version switching method, electronic device and BIOS chip
CN114443582B (en) File system mounting method, device, equipment and medium on operating system
CN114528147B (en) Fingerprint deleting method and device in dual operating system
CN116414649A (en) Log information storage method, log information sending method and log information sending system
CN108170437B (en) Application management method and terminal equipment
CN114035825A (en) Method, device, equipment and medium for updating control style

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