CN110851262B - Multi-card software version management method and mobile terminal - Google Patents
Multi-card software version management method and mobile terminal Download PDFInfo
- Publication number
- CN110851262B CN110851262B CN201911115435.XA CN201911115435A CN110851262B CN 110851262 B CN110851262 B CN 110851262B CN 201911115435 A CN201911115435 A CN 201911115435A CN 110851262 B CN110851262 B CN 110851262B
- Authority
- CN
- China
- Prior art keywords
- card
- version
- mobile terminal
- card slot
- software
- 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/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
-
- 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/4401—Bootstrapping
- G06F9/4406—Loading of operating system
- G06F9/441—Multiboot arrangements, i.e. selecting an operating system to be loaded
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Telephone Function (AREA)
Abstract
The invention discloses a multi-card software version management method and a mobile terminal, wherein the method comprises the following steps: acquiring version information after receiving a switching instruction for switching the multi-card software version of the mobile terminal; and switching the multi-card software version of the mobile terminal to the target version identified by the version information according to the switching instruction. The invention realizes the switching process of the multi-card software version in the mobile terminal, thereby realizing the compatibility of the single-card version and the multi-card version at the system software side of the mobile terminal, adapting to the different requirements of users on the single-card version and the multi-card version, and further reducing the maintenance cost of the software because the system software of the single-card version and the multi-card version is integrated into the mobile terminal.
Description
Technical Field
The invention relates to the technical field of mobile terminals, in particular to a multi-card software version management method and a mobile terminal.
Background
With the development of mobile terminal technology, the functions of the mobile terminal are more and more abundant. At present, in order to solve the problem that when a user has multiple subscriber identity modules, the user needs to manually pull and insert the subscriber identity modules to switch the subscriber identity modules, the operation is complicated, and multi-card mobile terminals capable of simultaneously inserting multiple subscriber identity modules are increasingly popularized. However, the system software version in the current multi-card mobile terminal is a multi-card version, and the system software version in the single-card mobile terminal is a single-card version, that is, the current multi-card mobile terminal and the single-card mobile terminal are completely separated, so that the requirement that a user uses a single-card version in the multi-card mobile terminal or uses a multi-card version in the single-card mobile terminal cannot be met.
Disclosure of Invention
The invention mainly aims to provide a multi-card software version management method and a mobile terminal, aiming at realizing the compatibility of a single-card version and a multi-card version on the system software side of the mobile terminal, thereby adapting to different requirements of users on software versions.
In order to achieve the above object, the present invention provides a multi-card software version management method, including:
s11: acquiring version information after receiving a switching instruction for switching the multi-card software version of the mobile terminal;
s12: and switching the multi-card software version of the mobile terminal to the target version identified by the version information according to the switching instruction.
Optionally, the step S11 includes:
the version information is obtained from the switching instruction or the preset data of the mobile terminal.
Optionally, before the step S11, the method further includes:
when detecting that a target card slot is inserted into the mobile terminal, acquiring the card slot type of the target card slot;
detecting whether a first software version adapted to the card slot type is the same as a second software version currently operated by the mobile terminal;
and if the software versions are different, triggering a switching instruction for switching the multi-card software version of the mobile terminal.
Optionally, if the two versions are different, the step of triggering a switching instruction for switching the multi-card software version of the mobile terminal includes:
if not, outputting preset prompt information to prompt a user whether to switch the multi-card software version of the mobile terminal;
and when a confirmation instruction for confirming the switching of the multi-card software version triggered based on the preset prompt message is detected, a switching instruction for switching the multi-card software version of the mobile terminal is triggered.
Optionally, when it is detected that a target card slot is inserted into the mobile terminal, the step of obtaining the card slot type of the target card slot includes:
when the mobile terminal is detected to be inserted into a target card slot, detecting a high-low level state on a preset detection pin in the mobile terminal;
and determining the preset card slot type corresponding to the high and low level state as the card slot type of the target card slot.
Optionally, after the step of switching the multi-card software version of the mobile terminal to the target version identified by the version information according to the switching instruction, the method further includes:
detecting whether a user identification card is inserted into the card slot position on the target card slot;
and when the situation that the user identification card is inserted into the card slot position is detected, initializing the inserted user identification card.
Optionally, the step of initializing the inserted subscriber identity card when it is detected that the subscriber identity card is inserted into the slot position includes:
when the slot position is detected to be inserted with the user identification card, whether the slot position accords with the following conditions is judged: at least one of the slot position is matched with the target version, and the user identification card is matched with the target version;
and if so, initializing the inserted subscriber identity module card.
Optionally, after the step of initializing the inserted subscriber identification card when it is detected that the subscriber identification card is inserted into the slot position, the method further includes:
detecting whether the inserted subscriber identity module card is consistent with the information of the subscriber identity module card which is stored in advance;
and if the user identification cards are inconsistent, the network searching is restarted on the basis of the inserted user identification cards.
Optionally, after detecting a switching instruction for switching the multi-card software version of the mobile terminal, before the step of obtaining the version information, the method further includes:
when detecting that a target card slot is inserted into the mobile terminal, acquiring the card slot type of the target card slot;
detecting whether the card slot type is the same as a card slot type pre-stored by the mobile terminal;
and when the software versions are different, triggering a switching instruction for switching the multi-card software version of the mobile terminal.
In addition, in order to achieve the above object, the present invention further provides a method for managing versions of multi-card software, which is applied to a mobile terminal, wherein the mobile terminal is provided with software of a single-card version and a multi-card version, and the method comprises the following steps:
s21: acquiring the type of a card slot inserted into the mobile terminal;
s22: and controlling the mobile terminal to operate software of a corresponding version according to the card slot type.
Optionally, the card slot type includes: at least one of a single card slot and a multi-card slot;
optionally, the step S22 includes:
when the card slot type is a single card slot, controlling the mobile terminal to operate software of a single card version; and/or when the card slot type is a multi-card slot, controlling the mobile terminal to run multi-card version software.
Optionally, the step S22 further includes:
and if only one user identification card supporting the operation of the single-card version is inserted into the multi-card slot, controlling the mobile terminal to operate the single-card version or the multi-card version.
Optionally, the step S22 further includes:
and if the user identification card inserted into the single card slot supports the operation of the multi-card version, controlling the mobile terminal to operate the software of the single card version or the multi-card version.
In addition, to achieve the above object, the present invention further provides a multi-card software version management apparatus, including:
the acquisition module is used for acquiring version information after receiving a switching instruction for switching the multi-card software version of the mobile terminal;
and the switching module is used for switching the multi-card software version of the mobile terminal to the target version identified by the version information according to the switching instruction.
In addition, to achieve the above object, the present invention further provides a mobile terminal, which includes a memory, a processor, and a multi-card software version management program stored on the memory and operable on the processor, and when executed by the processor, the multi-card software version management program implements the steps of the multi-card software version management method as described above.
In addition, to achieve the above object, the present invention also provides a computer readable storage medium having stored thereon a multi-card software version management program, which, when executed by a processor, implements the steps of the multi-card software version management method as described above.
According to the invention, after the mobile terminal detects the switching instruction for switching the multi-card software version, the version information is obtained, and the multi-card software version of the mobile terminal is switched to the target version identified by the version information according to the switching instruction, so that the switching process of the multi-card software version in the mobile terminal is realized, and the compatibility of the single-card version and the multi-card version on the system software side of the mobile terminal is realized, thereby adapting to different requirements of users on the single-card software version and the multi-card software version.
Drawings
FIG. 1 is a schematic diagram of a hardware operating environment according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a method for managing multi-card software versions according to a first embodiment of the present invention;
fig. 3 is a schematic diagram of a user setting interface in a mobile terminal according to an embodiment of the present invention;
fig. 4 is a schematic diagram illustrating a multi-card software version switching prompt in a mobile terminal according to an embodiment of the present invention;
FIG. 5 is a block diagram illustrating the functions of the multi-card software version management apparatus according to the preferred embodiment of the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The invention provides a mobile terminal, and referring to fig. 1, fig. 1 is a schematic structural diagram of a hardware operating environment according to an embodiment of the present invention.
It should be noted that fig. 1 is a schematic structural diagram of a hardware operating environment of the mobile terminal. The mobile terminal of the embodiment of the invention can be a PC, and can also be terminal equipment with a display function, such as a smart phone, a smart television, a tablet computer, a portable computer and the like.
As shown in fig. 1, the mobile terminal may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. The communication bus 1002 is used to implement connection communication among these components. The user interface 1003 may include a Display (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.
Optionally, the mobile terminal may further include a camera, a Radio Frequency (RF) circuit, a sensor, an audio circuit, a WiFi module, and the like. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 1 is not intended to be limiting of mobile terminals and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a multi-card software version management program.
In the mobile terminal shown in fig. 1, the network interface 1004 is mainly used for connecting to a backend server and communicating with the backend server; the user interface 1003 is mainly used for connecting a client (user side) and performing data communication with the client; and processor 1001 may be configured to invoke the multi-card software version management program stored in memory 1005 and perform the following operations:
acquiring version information after receiving a switching instruction for switching the multi-card software version of the mobile terminal;
and switching the multi-card software version of the mobile terminal to the target version identified by the version information according to the switching instruction.
Further, the step S1 includes:
the version information is obtained from the switching instruction or the preset data of the mobile terminal.
Further, before the step S1, the processor 1001 may call the multi-card software version management program stored in the memory 1005, and further perform the following operations:
when detecting that a target card slot is inserted into the mobile terminal, acquiring the card slot type of the target card slot;
detecting whether a first software version adapted to the card slot type is the same as a second software version currently operated by the mobile terminal;
and if the software versions are different, triggering a switching instruction for switching the multi-card software version of the mobile terminal.
Further, if the two versions are different, the step of triggering the switching instruction for switching the multi-card software version of the mobile terminal includes:
if not, outputting preset prompt information to prompt a user whether to switch the multi-card software version of the mobile terminal;
and when a confirmation instruction for confirming the switching of the multi-card software version triggered based on the preset prompt message is detected, a switching instruction for switching the multi-card software version of the mobile terminal is triggered.
Further, when it is detected that a target card slot is inserted into the mobile terminal, the step of obtaining the card slot type of the target card slot includes:
when the mobile terminal is detected to be inserted into a target card slot, detecting a high-low level state on a preset detection pin in the mobile terminal;
and determining the preset card slot type corresponding to the high and low level state as the card slot type of the target card slot.
Further, after the step of switching the multi-card software version of the mobile terminal to the target version identified by the version information according to the switching instruction, the processor 1001 may call the multi-card software version management program stored in the memory 1005, and further perform the following operations:
detecting whether a user identification card is inserted into the card slot position on the target card slot;
and when the situation that the user identification card is inserted into the card slot position is detected, initializing the inserted user identification card.
Further, the step of initializing the inserted subscriber identity card when it is detected that the subscriber identity card is inserted into the slot position includes:
when the slot position is detected to be inserted with the user identification card, whether the slot position accords with the following conditions is judged: at least one of the slot position is matched with the target version, and the user identification card is matched with the target version;
and if so, initializing the inserted subscriber identity module card.
Further, after the step of initializing the inserted subscriber identity card when it is detected that the subscriber identity card is inserted into the card slot, the processor 1001 may call the multi-card software version management program stored in the memory 1005, and further perform the following operations:
detecting whether the inserted subscriber identity module card is consistent with the information of the subscriber identity module card which is stored in advance;
and if the user identification cards are inconsistent, the network searching is restarted on the basis of the inserted user identification cards.
Further, before the step of acquiring the version information after detecting the switching instruction for switching the multi-card software version of the mobile terminal, the processor 1001 may call the multi-card software version management program stored in the memory 1005, and further perform the following operations:
when detecting that a target card slot is inserted into the mobile terminal, acquiring the card slot type of the target card slot;
detecting whether the card slot type is the same as a card slot type pre-stored by the mobile terminal;
and when the software versions are different, triggering a switching instruction for switching the multi-card software version of the mobile terminal.
Further, the mobile terminal is provided with software of a single card version and a multi-card version, and the processor 1001 may be configured to call a multi-card software version management program stored in the memory 1005 and perform the following operations:
s21: acquiring the type of a card slot inserted into the mobile terminal;
s22: and controlling the mobile terminal to operate software of a corresponding version according to the card slot type.
Further, the card slot types include: at least one of a single card slot and a multi-card slot;
further, the step S22 includes:
when the card slot type is a single card slot, controlling the mobile terminal to operate software of a single card version; and/or when the card slot type is a multi-card slot, controlling the mobile terminal to run multi-card version software.
Further, the step S22 further includes:
and if only one user identification card supporting the operation of the single-card version is inserted into the multi-card slot, controlling the mobile terminal to operate the single-card version or the multi-card version.
Further, the step S22 further includes:
and if the user identification card inserted into the single card slot supports the operation of the multi-card version, controlling the mobile terminal to operate the software of the single card version or the multi-card version.
Based on the hardware structure, the invention provides various embodiments of the multi-card software version management method.
Referring to fig. 2, a first embodiment of the multi-card software version management method of the present invention provides a multi-card software version management method, it being noted that while a logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in an order different than here. The multi-card software version management method comprises the following steps:
step S11, when a switching instruction for switching the multi-card software version of the mobile terminal is received, acquiring version information;
the current dual-card mobile terminal is only provided with system software suitable for dual-card version of dual-user identification cards, and the dual-card mobile terminal is only required to be inserted into a dual-card slot, namely, a slot with two slot positions; the single-card mobile terminal is only provided with system software of a single-card version suitable for a single-user identification card, and the single-card mobile terminal can only be inserted into a single-card slot, namely, the single-card mobile terminal is only provided with a slot of a slot position. That is, the existing single-card mobile terminal and the existing dual-card mobile terminal are completely separated in hardware and software, so that the problem of switching software versions does not exist, and the requirement that a user wants to use the dual-card version on the single-card mobile terminal and the dual-card version on the dual-card mobile terminal cannot be met.
In this embodiment, to solve the above problem, it is proposed to configure a single-card version of system software and a multi-card version of system software (dual card, three card, etc.) in a mobile terminal at the same time, and implement switching between multiple versions of system software.
Specifically, a single-card version system software and a multi-card version system software are configured in the mobile terminal, and hereinafter collectively referred to as multi-card software, that is, the multi-card software version in the mobile terminal is divided into a single-card version and a multi-card version; one version of multi-card software is run in the mobile terminal. Switching instructions of the multi-card software version and triggering conditions of the switching instructions are preset in the mobile terminal. When the mobile terminal detects that the trigger condition is met, a switching instruction for switching the multi-card software version is triggered, and version information for identifying a target version to be switched, such as a version number, version configuration parameters and the like, is carried in the switching instruction.
And when the mobile terminal receives a switching instruction for switching the multi-card software version of the mobile terminal, acquiring version information, namely the information of the version to be switched.
Further, step S11 includes: the version information is obtained from the switching instruction or the preset data of the mobile terminal.
The mobile terminal may obtain the version information from the switching instruction, and may also obtain the version information from preset data of the mobile terminal, where the preset data may be data used by the mobile terminal to store the version information.
And step S12, switching the multi-card software version of the mobile terminal to the target version identified by the version information according to the switching instruction.
Specifically, the mobile terminal can acquire a system software file corresponding to the version number prestored in the mobile terminal according to the version number in the version information, and operate the system software file, so that the multi-card software version of the mobile terminal is switched to the target version identified by the version number. For example, when the version of the multi-card software currently operated by the mobile terminal is a single-card version, the mobile terminal detects a switching instruction for switching the multi-card software version, extracts version information for identifying a dual-card version from the switching instruction, and operates a system software file of the dual-card version pre-stored by the mobile terminal according to the version information, so that the switching process from the single-card version to the dual-card version is realized. It should be noted that, according to specific needs, the process of switching the versions of the mobile terminal may restart the mobile terminal system, or may not restart the mobile terminal system.
In the embodiment, after the mobile terminal receives the switching instruction for switching the multi-card software version, the version information is acquired, and the multi-card software version of the mobile terminal is switched to the target version identified by the version information according to the switching instruction, so that the switching process of the multi-card software version in the mobile terminal is realized, and the single-card version and the multi-card version are compatible on the system software side of the mobile terminal, thereby adapting to different requirements of a user on the single-card version and the multi-card version.
Further, in this embodiment, as shown in fig. 3, a user interface for a user to switch the multi-card software version may be preset in the mobile terminal, a version of the multi-card software currently running in the mobile terminal, such as a "single-card version", is displayed in the user interface, a switching control for switching the multi-card software version, such as a "switching to dual-card version" switching control, is displayed in the user interface, when the mobile terminal detects a touch operation of the user on the switching control, a switching instruction is triggered, when a touch operation of the user on the switching control for "switching to dual-card version" is detected, a switching instruction carrying version information identifying the dual-card version is triggered, and switching of the multi-card software version is performed according to the switching instruction. The method and the device have the advantages that the multi-card software version can be switched in the mobile terminal at any time by a user, for example, when only one user identification card is inserted into the mobile terminal of the user and the version of the multi-card software currently running in the mobile terminal is a dual-card version, the user can enter the user interface in the mobile terminal to switch and select to switch the multi-card software version of the mobile terminal to the single-card version, so that the management of one user identification card is facilitated, and the user experience is improved.
Further, based on the first embodiment, a second embodiment of the multi-card software version management method of the present invention provides a multi-card software version management method. In this embodiment, before the step S11, the method further includes:
step S13, when detecting that a target card slot is inserted into the mobile terminal, obtaining the card slot type of the target card slot;
in this embodiment, a single card slot or a multiple card slot may be inserted into the mobile terminal, where a single card slot is provided with a card slot location for placing one subscriber identity module card, and multiple card slots are provided with multiple card slots for placing multiple subscriber identity modules cards, where the subscriber identity modules cards may be SIM cards, UIM cards, USIM cards, or the like. The pulling-out and inserting actions of the card slot can be detected by arranging a sensor at the position of the card holder in the mobile terminal, and the sensor can be a mechanical sensor or a light-sensing sensor. When the mobile terminal detects that the target card slot is inserted into the mobile terminal, namely the card slot inserting action is detected, the card slot type of the target card slot is obtained. For example, a spring is arranged at the position of a card holder of the mobile terminal, when the card slot is inserted into the card holder, the spring is pushed to generate a pressure signal, the mechanical sensor senses the pressure signal and converts the pressure signal into an electric signal, and the mobile terminal judges that the card slot is inserted based on the electric signal. The types of the card slots include a single card slot and a multi-card slot. According to the different card slots inserted by the user, the card slot types of the target card slots acquired by the mobile terminal are different, and if the user inserts a single card slot, the card slot type of the target card slot acquired by the mobile terminal is the single card slot.
Specifically, the step S13 includes:
step a, when detecting that a target card slot is inserted into the mobile terminal, detecting a high-low level state on a preset detection pin in the mobile terminal;
when the mobile terminal detects that a target card slot is inserted into the mobile terminal, the high-low level state of a preset detection pin in the mobile terminal is detected. The mobile terminal can be provided with a detection pin, and the relationship between the level of the detection pin and the type of the target card slot is set through a hardware circuit, for example, when the card slot type of the inserted target card slot is a single card slot, the detection pin is designed to be a high level and a low level, and when the card slot type of the inserted target card slot is a double card slot, the detection pin is designed to be two high levels, or, when the card slot type of the inserted target card slot is a single card slot, the detection pin is designed to be a high level and a low level, and when the card slot type of the inserted target card slot is a double card slot, the detection pin is designed to be two low levels, which is not limited here.
And b, determining the preset card slot type corresponding to the high and low level states as the card slot type of the target card slot.
When the mobile terminal detects a high-low level state on the detection pin, the card slot type preset in the mobile terminal and corresponding to the high-low level state is obtained, and the card slot type is determined as the card slot type of the inserted target card slot. For example, when the card slot type of the target card slot to be inserted is designed to be a single card slot, the detection pin is at a high level and a low level, and when the card slot type of the target card slot to be inserted is a dual card slot, the detection pin is at two high levels, and if the mobile terminal detects that the high-low level state on the detection pin is at a high level and a low level, the card slot type of the target card slot to be inserted is determined to be a single card slot.
Step S14, detecting whether the first software version adapted to the card slot type is the same as the second software version currently operated by the mobile terminal;
after the mobile terminal obtains the card slot type of the target card slot, a first software version adaptive to the card slot type is obtained, and whether a second software version currently running by the mobile terminal is the same or not is detected. When the card slot type is a single card slot, the adaptive first software version is a single card version, and when the card slot type is a multi-card slot, the adaptive first software version is a multi-card version.
And step S15, if the software versions are different, triggering a switching instruction for switching the multi-card software version of the mobile terminal.
When the mobile terminal detects that the first software version is different from the second software version, the mobile terminal triggers a switching instruction for switching the multi-card software version of the mobile terminal, and the switching instruction can carry version information for identifying the first software version. For example, when the mobile terminal currently runs in a single-card version, a user inserts a dual-card slot into the mobile terminal, and at this time, it indicates that the user wants to use system software of a dual-card version, so that the mobile terminal can trigger an instruction for switching a multi-card software version, and the switching instruction carries version information of the dual-card version; for another example, when the mobile terminal currently runs in a dual-card version, the user inserts a single-card slot into the mobile terminal, which indicates that the user wants to use the system software of the single-card version, so that the mobile terminal can trigger an instruction for switching the multi-card software version, and the switching instruction carries version information of the single-card version.
Further, when the mobile terminal detects that the first software version and the second software version are the same, the mobile terminal may not perform the processing, i.e., does not trigger the switching instruction. If the mobile terminal is currently running in the single-card version, the user inserts the single-card slot into the mobile terminal, which indicates that the user wants to use the system software of the single-card version, i.e. the switching of the multi-card software version is not needed.
In the embodiment, when the mobile terminal detects that the mobile terminal is inserted into the target card slot, the card slot type of the target card slot is obtained, and when the first software version adaptive to the card slot type is different from the second software version currently running by the mobile terminal, a switching instruction for switching the multi-card software version of the mobile terminal is triggered, so that the requirement of a user on the software version in the mobile terminal is automatically judged according to the action of inserting the user into the card slot, and the switching of the multi-card software version is intelligently performed according to the requirement of the user, so that the manual switching of the user is not needed, the simplified user operation is realized, and the user experience is improved.
Further, in order to improve the accuracy of the mobile terminal in determining the behavior intention of the user, step S15 includes:
step c, if not, outputting preset prompt information to prompt a user whether to switch the multi-card software version of the mobile terminal;
and when the mobile terminal detects that the first software version is different from the second software version, outputting preset prompt information to prompt a user whether to switch the multi-card software version of the mobile terminal. The preset prompt message is a preset prompt message, and the content of the prompt message may be different according to different first software versions, as shown in fig. 4, for example, when the first software version is a single card version, the content of the prompt message is "detect that you are inserted into a single card slot, and whether to switch the mobile phone to the single card version or not"; when the first software version is a double-card version, the content of the prompt message is 'detecting whether a user inserts the double-card slot and switches the mobile phone to the double-card version'. In addition, the preset prompt information can be in a voice form, or a prompt box can be displayed on a display interface of the mobile terminal, and when the user is prompted in the prompt box, controls for the user to confirm whether to switch or not can be displayed in the prompt box, such as a "switch now" control and a "do not switch" control.
And d, when a confirmation instruction for confirming the switching of the multi-card software version triggered based on the preset prompt information is detected, triggering a switching instruction for switching the multi-card software version of the mobile terminal.
When the mobile terminal detects a confirmation instruction for confirming the switching of the multi-card software version triggered based on the preset prompt information, the switching instruction for switching the multi-card software version of the mobile terminal is triggered, and version information for identifying the first software version can be carried in the switching instruction. For example, when the form of the prompt information output by the mobile terminal is the prompt box form, when the mobile terminal detects a touch operation of a user on a "switch now" control in the prompt box, a confirmation instruction based on preset prompt information is detected, so as to trigger a switch instruction for switching the multi-card software version.
In the embodiment, when the mobile terminal detects that the first software version is different from the second software version, the prompt information is output to prompt the user to confirm whether to switch the multi-card software version, and the intention of the user is further accurately judged, so that the software versions are accurately switched according to the intention of the user, and the user experience is improved.
Further, it may also be that, during the startup of the mobile terminal, it is detected whether a card slot is inserted into the mobile terminal, if so, the card slot type of the inserted target card slot is detected, it is determined whether the first software version adapted to the card slot type is the same as the second software version currently running in the mobile terminal, and if not, a switching instruction is triggered. When a user starts the mobile terminal after the card slot is replaced by shutdown, the mobile terminal can automatically switch the multi-card software version to the version matched with the replaced card slot for the user.
Further, based on the second embodiment, a third embodiment of the multi-card software version management method according to the present invention provides a multi-card software version management method, where after step S12, the method further includes:
step S16, detecting whether the slot position on the target slot is inserted with a user identification card;
and after the multi-card software version is switched to the target version identified by the version information, the mobile terminal detects whether the user identification card is inserted into the card slot position on the target card slot.
Step S17, when it is detected that a user identification card is inserted into the slot position, initializing the inserted user identification card.
And when the user identification card is detected to be inserted into the card slot position, the mobile terminal initializes the inserted user identification card. The initialization mode may refer to a conventional implementation process for initializing a subscriber identity module card in the prior art, and the specific initialization mode does not limit the present invention.
Further, the step of S17 includes:
e, when detecting that the user identification card is inserted into the card slot position, judging whether the card slot position accords with the following conditions: at least one of the card slot position and the target version adaptation and the user identification card and the target version adaptation;
and f, if the user identification card is matched with the user identification card, initializing the inserted user identification card.
The mobile terminal can judge whether the slot position is matched with the target version or not and at least one item of the user identification card matched with the target version when the mobile terminal detects that the user identification card is inserted into the slot position of the target slot, and if so, the user identification card is initialized. The mobile terminal can design the card slot positions of the single card slot and the multi-card slot on hardware in advance so as to determine the positions of the card slot positions in the single card slot and the multi-card slot. If the single card slot and the double card slot are designed to be equal in length, two card slot positions are arranged in the double card slot for inserting two user identification cards, one card slot position is arranged in the single card slot, the card slot position corresponds to the card slot position on the left side of the double card slot, and the card slot position corresponding to the right side of the double card slot is designed to be a closed structure; based on the pre-designed slot positions of the single-card slot and the double-card slot, the slot positions corresponding to the single-card version and the double-card version are preset in the mobile terminal, if the slot position corresponding to the single-card version is the slot position on the left side of the slot, the slot positions corresponding to the double-card version are two slot positions in the slot. And the mobile terminal determines whether the card slot position is matched with the target version or not according to the position of the card slot position inserted with the user identification card. If the target version is the single card version, the mobile terminal determines that the card slot position is matched with the target version when detecting that the position of the card slot position inserted with the user identification card is the left card slot position of the target card slot, and determines that the card slot position is not matched with the target version when detecting that the position of the card slot position inserted with the user identification card is the right card slot position of the target card slot.
The mobile terminal can also judge whether the user identification card is matched with the target version according to the number of the inserted user identification cards, if the target version is a single card version, the number of the inserted user identification cards is one, the user identification card is determined to be matched with the target version, if the number of the inserted user identification cards is two, the user identification card is determined not to be matched with the target version, and at the moment, whether the slot position of the inserted user identification card is matched with the target version can be judged.
Further, when the mobile terminal detects an instruction of not switching the multi-card software version triggered based on the prompt message, the mobile terminal does not trigger the switching instruction, and at this time, the mobile terminal can detect whether a slot position on the target slot adapted to the currently running software version of the mobile terminal is inserted with the user identification card, for example, when the currently running software version is a single-card version, the user is inserted with a dual-card slot, but the user does not select to switch the multi-card software version to a dual-card version, and at this time, the mobile terminal only detects whether the left slot position of the dual-card slot is inserted with the user identification card.
In this embodiment, when the mobile terminal detects that the mobile terminal is inserted into the target card slot, the mobile terminal detects the user identification card in the card slot adapted to the currently running software version, and when the user identification card is detected, initializes the user identification card, so that the mobile terminal can accurately manage the user identification card according to the currently running software version.
Further, after step S17, the method further includes:
step S18, detecting whether the inserted user identification card is consistent with the pre-stored user identification card information;
after initializing the user identification card inserted into the adaptive slot position, the mobile terminal detects whether the user identification card is consistent with the information of the user identification card which is stored in advance. The pre-stored subscriber identity module card information is the information of the subscriber identity module card before the card slot is pulled out and stored in the mobile terminal. According to the difference of the user identification cards inserted before the card slot is pulled out, the pre-stored information of the user identification cards may include the information of two user identification cards or only include the information of one user identification card. For example, the pre-stored subscriber identity module card information is information of two subscriber identity modules (a and b), when the matched card slot is one and the subscriber identity module card (a or b) is inserted, the mobile terminal determines that the information is consistent, and when the subscriber identity module card (c) is inserted, the mobile terminal determines that the information is inconsistent. For another example, the pre-stored subscriber identity module card information is information of a subscriber identity module card, and when two card slot positions are matched and two subscriber identity module cards a and b are inserted, the mobile terminal determines that the information of the subscriber identity module card a is consistent and the information of the subscriber identity module card b is inconsistent.
And step S19, if not, reinitiating the network searching based on the inserted user identification card.
And if the subscriber identity module card inserted into the mobile terminal is inconsistent with the subscriber identity module card information stored in advance, re-initiating network searching based on the inserted subscriber identity module card. The specific network searching process can refer to the network searching implementation process of the subscriber identity module card in the prior art. In the above example, the mobile terminal re-initiates network searching for the b-subscriber identity card, but does not perform network searching again for the a-subscriber identity card.
In this embodiment, when the user identification card inserted into the slot adapted to the current running version of the mobile terminal is inconsistent with the pre-stored user identification card, a network re-search is initiated, so that the mobile terminal can meet the requirement that the user connects to the network through the newly inserted user identification card.
Further, based on the first embodiment, a fourth embodiment of the multi-card software version management method according to the present invention provides a multi-card software version management method, and after step S11, the method further includes:
step A1, when detecting that a target card slot is inserted into the mobile terminal, acquiring the card slot type of the target card slot;
in the present embodiment, a switching instruction triggering manner is proposed in parallel with steps S13, S14, and S15. The process of detecting the insertion of the target card slot and acquiring the card slot type of the target card slot in step a1 is the same as that in step S13, and is not described in detail herein.
Step A2, detecting whether the type of the card slot is the same as the type of the card slot pre-stored by the mobile terminal;
and after the mobile terminal acquires the type of the target card slot, detecting whether the type of the target card slot is the same as the type of the card slot pre-stored by the mobile terminal. The pre-stored card slot type is the type of a card slot inserted by the mobile terminal before the card slot is pulled out, if the card slot type inserted into the card slot in the mobile terminal is a single card slot, the mobile terminal stores the card slot type, when the mobile terminal detects the actions of pulling out the card slot and inserting the card slot, the card slot type of an inserted target card slot is obtained, and whether the card slot type of the target card slot is the pre-stored single card slot is detected.
Step A3, when the card types are different, triggering a switching instruction for switching the multi-card software version of the mobile terminal, and carrying version information in the switching instruction, wherein the version information is used for identifying the software version adapted to the card slot type of the target card slot.
When the mobile terminal detects that the type of the card slot of the target card slot is different from the type of the card slot pre-stored by the mobile terminal, a switching instruction for switching the multi-card software version of the mobile terminal is triggered, version information for identifying the software version matched with the type of the card slot of the target card slot is acquired, and the version information is carried in the switching instruction.
In this embodiment, when the mobile terminal detects that the card slot type of the inserted target card slot is different from the pre-stored card slot type, it indicates that the user will change the card slot, and if the single card slot is changed into the dual card slot, the mobile terminal runs the system software of the single card version, the mobile terminal can switch the multi-card software version into the dual card version according to the action of switching the user into the dual card slot, without manual switching by the user, thereby simplifying the operation of the user and improving the user experience.
Further, an embodiment of the present invention further provides a method for managing versions of multi-card software, where the method is applied to a mobile terminal, and software of a single-card version and a multi-card version is set in the mobile terminal, and the method includes:
s21: acquiring the type of a card slot inserted into the mobile terminal;
s22: and controlling the mobile terminal to run software of a corresponding version according to the card slot type.
And the mobile terminal acquires the type of the inserted card slot and controls the mobile terminal to operate the software with the corresponding version according to the type of the card slot. Specifically, the card slot type in the mobile terminal may be at least one of a single card slot and a multi-card slot, where the multi-card slot refers to a card slot with more than one card slot, for example, a dual-card slot with two card slots. Different card slot types corresponding to different versions of software are preset in the mobile terminal.
The step S22 includes:
when the card slot type is a single card slot, controlling the mobile terminal to run software of a single card version; and/or when the card slot type is a multi-card slot, controlling the mobile terminal to run multi-card version software.
And when the mobile terminal acquires that the type of the inserted card slot is a single-card slot, controlling the mobile terminal to operate software of a single-card version. Or when the mobile terminal acquires that the type of the inserted card slot is a dual-card slot, controlling the mobile terminal to run dual-card version software. Or when the mobile terminal acquires that the types of the inserted card slots are the single card slot and the double card slot, controlling the mobile terminal to run software of the single card version and the double card version. The user may use different types of card slots in the process of using the mobile terminal, for example, when the user uses two cards, the user uses a dual-card slot, and the mobile terminal controls and operates software of a corresponding version according to the type of the card slot, so that the user can obtain better experience.
Further, the step S22 further includes:
and if only one user identification card supporting the operation of the single-card version is inserted into the multi-card slot, controlling the mobile terminal to operate the single-card version or the multi-card version.
The mobile terminal user identification card may only support a single card version, may only support a double card version, and may support both the double card version and the multi card version.
And if the mobile terminal acquires that the card slot type is a multi-card slot and detects that only one user identity identification card supporting the single-card version is inserted into the multi-card slot, the mobile terminal runs software of the single-card version or the multi-card version. Specifically, whether the software of a single card version or the software of a multi-card version is run in this case may be set in advance as needed to meet the needs of different users. The software of the single card version is operated under the condition as set so as to meet the requirement that a user actually wants to use the software of the single card version when a user inserts the user identification card supporting the single card version by using the multi-card slot.
Further, the step S22 further includes:
and if the user identification card inserted into the single card slot supports the operation of the multi-card version, controlling the mobile terminal to operate the software of the single card version or the multi-card version.
And if the mobile terminal acquires that the card slot type is a single card slot and detects that the subscriber identity module card inserted into the single card slot supports a multi-card version, the mobile terminal runs software of the single card version or the multi-card version. Specifically, whether the software runs in a single-card version or a multi-card version in this case may be set in advance as needed to meet the needs of different users. If the multi-card version software is set to run under the condition, the requirement that a user actually wants to use the multi-card version software when the user identification card supporting the multi-card version is inserted into the single-card slot is met.
In addition, an embodiment of the present invention further provides a multi-card software version management apparatus, and referring to fig. 5, the multi-card software version management apparatus includes:
the obtaining module 10 is configured to obtain version information after receiving a switching instruction for switching a multi-card software version of the mobile terminal;
and the switching module 20 is configured to switch the multi-card software version of the mobile terminal to the target version identified by the version information according to the switching instruction.
Further, the obtaining module 10 is further configured to:
the version information is obtained from the switching instruction or the preset data of the mobile terminal.
Further, the obtaining module 10 is further configured to obtain a card slot type of a target card slot when it is detected that the target card slot is inserted into the mobile terminal;
the multi-card software version management device further comprises:
the detection module is used for detecting whether the first software version matched with the card slot type is the same as the second software version currently operated by the mobile terminal;
and the triggering module is used for triggering a switching instruction for switching the multi-card software version of the mobile terminal if the multi-card software versions are different.
Further, the triggering module is further configured to:
if not, outputting preset prompt information to prompt a user whether to switch the multi-card software version of the mobile terminal;
and when a confirmation instruction for confirming the switching of the multi-card software version triggered based on the preset prompt information is detected, triggering a switching instruction for switching the multi-card software version of the mobile terminal.
Further, the triggering module is further configured to:
when the fact that a target card slot is inserted into the mobile terminal is detected, detecting a high-low level state on a preset detection pin in the mobile terminal;
and determining the preset card slot type corresponding to the high and low level state as the card slot type of the target card slot.
Further, the detection module is further configured to detect whether a user identification card is inserted into the slot position on the target slot;
the multi-card software version management device further comprises:
and the initialization module is used for initializing the inserted user identification card when the situation that the user identification card is inserted into the card slot position is detected.
Further, the initialization module is further configured to:
when the slot position is detected to be inserted with the user identification card, whether the slot position accords with the following conditions is judged: at least one of the slot position is matched with the target version, and the user identification card is matched with the target version;
and if so, initializing the inserted subscriber identity module card.
Further, the detection module is further configured to:
detecting whether the inserted subscriber identity module card is consistent with the information of the subscriber identity module card which is stored in advance;
and if the user identification cards are inconsistent, the network searching is initiated again based on the inserted user identification cards.
Further, the obtaining module 10 is further configured to:
when detecting that a target card slot is inserted into the mobile terminal, acquiring the card slot type of the target card slot;
the detection module is also used for detecting whether the type of the card slot is the same as the type of the card slot pre-stored by the mobile terminal;
and when the software versions are different, triggering a switching instruction for switching the multi-card software version of the mobile terminal.
The specific implementation of the multi-card software version management apparatus of the present invention is basically the same as the embodiments of the multi-card software version management method, and is not described herein again.
In addition, an embodiment of the present invention further provides a computer-readable storage medium, where a multi-card software version management program is stored on the computer-readable storage medium, and when executed by a processor, the multi-card software version management program implements the steps of the multi-card software version management method described above.
The expanding contents of the specific implementation modes of the mobile terminal and the computer readable storage medium of the invention are basically the same as the embodiments of the multi-card software version management method, and are not described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (14)
1. A multi-card software version management method is characterized by comprising the following steps:
s11: acquiring version information after receiving a switching instruction for switching the multi-card software version of the mobile terminal;
s12: switching the multi-card software version of the mobile terminal to the target version identified by the version information according to the switching instruction;
before the step of S11, the method further includes:
when detecting that a target card slot is inserted into the mobile terminal, acquiring the card slot type of the target card slot;
detecting whether a first software version adapted to the card slot type is the same as a second software version currently operated by the mobile terminal;
and if the software versions are different, triggering a switching instruction for switching the multi-card software version of the mobile terminal.
2. The multi-card software version management method according to claim 1, wherein said step S11 includes:
the version information is obtained from the switching instruction or the preset data of the mobile terminal.
3. The method for managing versions of multi-card software of claim 1, wherein the step of triggering a switch command for switching the versions of the multi-card software of the mobile terminal if the versions are different comprises:
if not, outputting preset prompt information to prompt a user whether to switch the multi-card software version of the mobile terminal;
and when a confirmation instruction for confirming the switching of the multi-card software version triggered based on the preset prompt message is detected, a switching instruction for switching the multi-card software version of the mobile terminal is triggered.
4. The method for managing versions of multi-card software as claimed in claim 1, wherein the step of obtaining the card slot type of the target card slot when it is detected that the target card slot is inserted into the mobile terminal comprises:
when the fact that a target card slot is inserted into the mobile terminal is detected, detecting a high-low level state on a preset detection pin in the mobile terminal;
and determining the preset card slot type corresponding to the high and low level state as the card slot type of the target card slot.
5. The method for managing the multi-card software version of claim 1, wherein after the step of switching the multi-card software version of the mobile terminal to the target version identified by the version information according to the switching instruction, the method further comprises:
detecting whether a user identification card is inserted into the card slot position on the target card slot;
and when the situation that the user identification card is inserted into the card slot position is detected, initializing the inserted user identification card.
6. The method for managing versions of multi-card software of claim 5, wherein the step of initializing the inserted subscriber identity card when the insertion of the subscriber identity card into the card slot is detected comprises:
when the user identification card is inserted into the card slot position, judging whether the card slot position accords with the following conditions: at least one of the slot position is matched with the target version, and the user identification card is matched with the target version;
and if so, initializing the inserted user identification card.
7. The method for managing versions of multi-card software of claim 5, wherein, after the step of initializing the inserted subscriber identity card when it is detected that the subscriber identity card is inserted into the card slot, the method further comprises:
detecting whether the inserted user identification card is consistent with the information of the user identification card stored in advance;
and if the user identification cards are inconsistent, the network searching is restarted on the basis of the inserted user identification cards.
8. The multi-card software version management method according to claim 1 or 2, wherein before the step of obtaining the version information after receiving the switching instruction for switching the multi-card software version of the mobile terminal, the method further comprises:
when detecting that a target card slot is inserted into the mobile terminal, acquiring the card slot type of the target card slot;
detecting whether the card slot type is the same as a card slot type pre-stored by the mobile terminal;
and when the software versions are different, triggering a switching instruction for switching the multi-card software version of the mobile terminal.
9. A multi-card software version management method is applied to a mobile terminal, the mobile terminal is provided with software of a single card version and a multi-card version, and the method is characterized by comprising the following steps:
s21: acquiring the type of a card slot inserted into the mobile terminal;
s22: and controlling the mobile terminal to operate software of a corresponding version according to the card slot type.
10. The management method according to claim 9,
the card slot types include: at least one of a single card slot and a multi-card slot.
11. The method for managing as set forth in claim 10, wherein the step of S22 includes:
when the card slot type is a single card slot, controlling the mobile terminal to operate software of a single card version;
and/or when the card slot type is a multi-card slot, controlling the mobile terminal to run multi-card version software.
12. The method for managing as set forth in claim 10, wherein the step of S22 further includes:
and if only one user identification card supporting the operation of the single-card version is inserted into the multi-card slot, controlling the mobile terminal to operate the single-card version or the multi-card version.
13. The method for managing as set forth in claim 10, wherein the step of S22 further includes:
and if the user identification card inserted into the single card slot supports the operation of the multi-card version, controlling the mobile terminal to operate the software of the single card version or the multi-card version.
14. A mobile terminal, characterized in that the mobile terminal comprises a memory, a processor and a multi-card software version management program stored on the memory and executable on the processor, the multi-card software version management program, when executed by the processor, implementing the steps of the multi-card software version management method according to any one of claims 1 to 8 or 9 to 13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911115435.XA CN110851262B (en) | 2019-11-14 | 2019-11-14 | Multi-card software version management method and mobile terminal |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911115435.XA CN110851262B (en) | 2019-11-14 | 2019-11-14 | Multi-card software version management method and mobile terminal |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110851262A CN110851262A (en) | 2020-02-28 |
| CN110851262B true CN110851262B (en) | 2022-07-12 |
Family
ID=69600893
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911115435.XA Active CN110851262B (en) | 2019-11-14 | 2019-11-14 | Multi-card software version management method and mobile terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110851262B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116321106A (en) * | 2020-06-09 | 2023-06-23 | 华为技术有限公司 | Method and device for updating system data of user identity recognition module card |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101052183A (en) * | 2007-03-20 | 2007-10-10 | 中兴通讯股份有限公司 | Start net-selecting method for double mode mobile terminal |
| CN101052188A (en) * | 2007-04-25 | 2007-10-10 | 中兴通讯股份有限公司 | Double mode double standby terminal and its double mode double standby realizing method |
| CN201813417U (en) * | 2010-06-03 | 2011-04-27 | 四川盟宝实业有限公司 | Mobile phone system with multiple SIM cards |
| CN104320776A (en) * | 2014-10-31 | 2015-01-28 | 北京思特奇信息技术股份有限公司 | Method and system for achieving matching of double cards of smart phone |
| CN106899774A (en) * | 2017-01-17 | 2017-06-27 | 宇龙计算机通信科技(深圳)有限公司 | The dynamic adaptation method and dynamic adaptation device of terminal modem softwares |
| CN106973162A (en) * | 2017-03-28 | 2017-07-21 | 上海与德科技有限公司 | A kind of intelligent terminal system version-switching method and device |
| CN109451485A (en) * | 2018-11-27 | 2019-03-08 | Oppo（重庆）智能科技有限公司 | Moade setting method, information write-in method, device, terminal and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20140077435A (en) * | 2012-12-14 | 2014-06-24 | 삼성전자주식회사 | Software update service method and apparatus for mobile terminal |
-
2019
- 2019-11-14 CN CN201911115435.XA patent/CN110851262B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101052183A (en) * | 2007-03-20 | 2007-10-10 | 中兴通讯股份有限公司 | Start net-selecting method for double mode mobile terminal |
| CN101052188A (en) * | 2007-04-25 | 2007-10-10 | 中兴通讯股份有限公司 | Double mode double standby terminal and its double mode double standby realizing method |
| CN201813417U (en) * | 2010-06-03 | 2011-04-27 | 四川盟宝实业有限公司 | Mobile phone system with multiple SIM cards |
| CN104320776A (en) * | 2014-10-31 | 2015-01-28 | 北京思特奇信息技术股份有限公司 | Method and system for achieving matching of double cards of smart phone |
| CN106899774A (en) * | 2017-01-17 | 2017-06-27 | 宇龙计算机通信科技(深圳)有限公司 | The dynamic adaptation method and dynamic adaptation device of terminal modem softwares |
| CN106973162A (en) * | 2017-03-28 | 2017-07-21 | 上海与德科技有限公司 | A kind of intelligent terminal system version-switching method and device |
| CN109451485A (en) * | 2018-11-27 | 2019-03-08 | Oppo（重庆）智能科技有限公司 | Moade setting method, information write-in method, device, terminal and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110851262A (en) | 2020-02-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP2043395B1 (en) | Dual-sim mobile terminal and operation method for the same | |
| CN104394263A (en) | Accessing point list displaying method and device | |
| CN105744352B (en) | Wireless network connection method of television and television | |
| US20130219335A1 (en) | Method and Apparatus for Placing Icon | |
| CN101986739A (en) | Method for setting language by mobile terminal and mobile terminal | |
| CN105653276A (en) | Method and apparatus for language setting | |
| CN112423238A (en) | Electronic device, control terminal, storage medium, and device connection method | |
| CN114727275B (en) | Method and related device for processing active command | |
| EP3229130A1 (en) | Smart terminal information display method and smart terminal | |
| US9369889B2 (en) | Method for provisioning of a SIM card | |
| CN110851262B (en) | Multi-card software version management method and mobile terminal | |
| CN107466022B (en) | SIM card switching method, mobile terminal and storage medium | |
| CN105635852A (en) | Method and apparatus for matching of smart television with dynamic link library | |
| CN110933772A (en) | Connection method of wireless device, mobile terminal and computer readable storage medium | |
| EP1349406A1 (en) | Automatic setting method for terminal information using subscriber identity module | |
| CN105101157A (en) | Mobile terminal SIM control method and apparatus | |
| CN113242542B (en) | Network searching control method and device of mobile terminal and mobile terminal | |
| CN114415530A (en) | Control method, control device, electronic equipment and storage medium | |
| CN111464990B (en) | Information processing method and first device | |
| CN105979552B (en) | Method and system for using manual PLMN selection mode | |
| CN111381978A (en) | Method for accessing application program, storage medium and smart television | |
| CN107231576B (en) | Smart television control method and system and storage medium | |
| US20100009668A1 (en) | System and method for customizing functions of a mobile phone | |
| CN112399242A (en) | Mobile network connection method, device, equipment and medium based on television | |
| CN110708744B (en) | Communication control method, home appliance device, and computer-readable 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 |