Information hiding method and electronic device

Abstract

The application provides an information hiding method and an electronic device, and relates to the technical field of terminals. The electronic device comprises a main space, a parallel space and a plurality of SIM cards. After the parallel space is bound with a first SIM card in the plurality of SIM cards, the electronic device receives a short message of the first SIM card during the running of the main space in the foreground. In the case that the parallel space is determined to be not opened and the information hiding function is closed, it is indicated that the user wants the electronic device to hide the short message associated with the subsystem when the parallel space is not opened, so that the electronic device can not display the information of the sender number of the short message, thereby avoiding the leakage of information. Then, the user can view the short message through the parallel space, thereby avoiding the loss of the short message, and the user cannot directly view the short message in the main system, thereby protecting the user privacy.

Description

An information hiding method and electronic device

[0001] This application claims priority to Chinese Patent Application No. 202410941875.5, filed on July 12, 2024, entitled "An Information Hiding Method and Electronic Device", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminal technology, and in particular to an information hiding method and electronic device. Background Technology

[0003] With the development of electronic devices (such as mobile phones), more and more mobile phones support dual SIM cards. These phones can use either of the two SIM cards (subscriber identification module cards) to provide SMS services, such as receiving text messages.

[0004] However, since mobile phones can use either of the two SIM cards for SMS service, and users' SMS service needs vary in different scenarios, there is an urgent need for a solution on how to use different SIM cards for SMS service to meet users' needs in different scenarios and thus improve the user experience. Summary of the Invention

[0005] This application provides an information hiding method and electronic device for preventing the display of information related to received text messages in specific scenarios, thereby preventing the leakage of user privacy and meeting user needs in different usage scenarios.

[0006] To achieve the above objectives, this application adopts the following technical solution:

[0007] In a first aspect, an information hiding method is provided, applied to an electronic device including a first SIM card and a second SIM card. During the display of a first interface of a main system, the electronic device receives a first SMS message from a first number to the first SIM card. Subsequently, the electronic device displays the first information from the first number. Then, in response to a first user input operation, a subsystem is associated with the first SIM card. After association, during the display of a second interface of the main system, the electronic device receives a second SMS message from a second number to the first SIM card. When the subsystem is not enabled and a first hiding function is activated, the first information from the second number is not displayed.

[0008] The second operation of receiving user input, the first information application of the electronic device display subsystem, includes a second SMS and a third interface.

[0009] In this application, before associating the subsystem with the first SIM card, during the foreground operation of the main system, upon receiving the first SMS message from the first SIM card, the sender's number (i.e., the first information of the first number) can be displayed normally, achieving normal SMS message notification. After associating the subsystem with the first SIM card, if the electronic device receives a second SMS message from the first SIM card while the main system is running in the foreground, and the subsystem is not activated while the first hiding function is enabled, indicating that the user wishes to hide SMS messages associated with the subsystem when it is not activated, the electronic device can choose not to display the first information of the first number, preventing leakage of this information and effectively protecting user data associated with the unactivated subsystem. After the subsystem is displayed in the foreground, the user can still view the first SMS message associated with the subsystem received while the subsystem is closed, preventing SMS data loss and allowing the user to view the second SMS message at an appropriate time. Furthermore, the user needs to view the second SMS message through the subsystem, and cannot directly view it through the main system, achieving isolation of SMS messages from different SIM cards, thereby hiding the second SMS message and protecting user privacy.

[0010] In one possible design, the electronic device may display a fourth interface of the subsystem before displaying the third interface of the first information application of the subsystem. This fourth interface includes a first notification message indicating the existence of a text message for the first SIM card.

[0011] In this application, after the subsystem is switched to the foreground display, the electronic device can first display a prompt message so that the user can be informed in a timely manner of receiving SMS messages associated with the subsystem during the subsystem shutdown period, thus enabling timely viewing of the SMS messages.

[0012] In one possible design, the fourth interface described above is the desktop of the subsystem, and the second operation described above can be the operation of starting the subsystem. The first prompt information described above is the unread mark on the icon of the first information application on the subsystem's desktop. The unread mark includes the number of SMS messages received by the electronic device from the first SIM card associated with the subsystem while the subsystem is not turned on.

[0013] Based on this, by displaying an unread mark on the icon of the first information application, users can quickly know the number of SMS messages received by the electronic device associated with the subsystem while the subsystem is off, thus enabling users to view the relevant SMS messages in a timely manner.

[0014] Optionally, the aforementioned fourth interface can also be other interfaces of the subsystem, such as the interface displayed when switching to the inactive state. This application does not limit it.

[0015] In one possible design, the aforementioned first information is carried in the first notification message. Based on this, when the subsystem is not enabled and the first hiding function is enabled, the electronic device does not display the notification message for the first SMS (or the notification message corresponding to the first SMS), thereby disabling SMS notifications for the SIM card associated with the parallel space while the parallel space is not enabled. This prevents unnecessary frequent push notifications and avoids interference with the user's use of the electronic device. Furthermore, it also prevents the leakage of SMS messages corresponding to the parallel space, satisfying the user's need to use part of the SIM card for private purposes, thus effectively protecting the user's privacy.

[0016] In one possible design, the aforementioned first information includes the contact information corresponding to the second number in the contact information within the subsystem.

[0017] When the subsystem is disabled and the first hidden function is enabled, the electronic device can display a notification message from a second SMS message, which does not include the first information from the second number. Based on this, it prevents user privacy leaks and improves the user experience while providing SMS notification reminders.

[0018] Optionally, the notification message may include a first icon, which indicates the presence of new information in the subsystem.

[0019] In one possible design, after associating the subsystem with the first SIM card, during the display of the fifth interface of the main system (which represents any interface of the main system), while the subsystem is on and not visible in the foreground, a third SMS message is received from the first SIM card, and a first pop-up window is displayed. The first pop-up window includes a first notification message and a first icon; the first notification message indicates the existence of new information, and the first icon indicates the existence of new information in the subsystem.

[0020] When the subsystem is on and not visible in the foreground, a fourth SMS message is received for the second SIM card, and a second pop-up window is displayed. The second pop-up window includes a second notification message, which indicates that information exists.

[0021] Based on this, while the main system is running in the foreground, if a third SMS message associated with a subsystem is received, and the subsystem is active but not visible in the foreground, indicating that the subsystem is running in the background, the electronic device can display a first pop-up window. This first pop-up window includes a first notification message and a first icon, thereby reminding the user that an SMS message associated with the subsystem has been received. If a fourth SMS message associated with the main system is received, and the subsystem is active but not visible in the foreground, the electronic device can display a second pop-up window. This second pop-up window does not include the first icon, thus achieving the notification of the SMS message associated with the main system.

[0022] In one possible design, the sender number of the third SMS message is the same as that of the fourth SMS message. After the main system displays the first pop-up window, in response to the operation of the first pop-up window, the sixth interface of the first information application of the subsystem is displayed. The sixth interface includes the third SMS message associated with the subsystem, but does not include the fourth SMS message associated with the main system. Based on this, normally, SMS records from the same number would be displayed on the same interface. However, after associating the first SIM card with the subsystem, even if SMS messages from the same number are received, such as the third and fourth SMS messages, the recipient number of the third SMS message is the number of the first SIM card, and the recipient number of the fourth SMS message is the number of the second SIM card. Therefore, they need to be stored separately. Accordingly, after triggering the first pop-up window, the electronic device switches to displaying the interface of the first information application of the subsystem that includes the third SMS message, allowing the user to quickly view the third SMS message. Furthermore, this interface does not include SMS messages received with the second SIM card after association, achieving isolated management of the SIM cards.

[0023] In one possible design, after the second pop-up window is accessed, the electronic device displays the interface of the main system's second information application, which includes the fourth SMS message.

[0024] In one possible design approach, a subsystem being inactive indicates that it is neither displayed in the foreground nor running in the background. Specifically, a subsystem being inactive indicates that it has been exited or destroyed.

[0025] In one possible design, a third notification message from the second SMS message is displayed when the subsystem is active. Based on this, the active subsystem indicates it is in use, allowing the electronic device to send SMS notifications normally.

[0026] When the subsystem is not enabled and the first hidden function is disabled, the fourth notification message of the second SMS message is displayed. Based on this, the fact that the subsystem is not enabled and the first hidden function is disabled indicates that the user wants the electronic device to still send SMS notifications to messages associated with the subsystem even when the subsystem is not enabled. Therefore, the electronic device can display the fourth notification message of the second SMS message to provide SMS notification reminders, allowing the user to promptly view received SMS messages associated with the subsystem.

[0027] In one possible design, the third notification message includes the first information. The fourth notification message does not include the first information, thereby protecting user privacy while providing SMS notification reminders.

[0028] In one possible design, both the third and fourth notification messages include a preset prompt message indicating that the first notification application has received the SMS message. Based on this, SMS notification reminders are implemented while protecting user privacy.

[0029] In one possible design, the association between the aforementioned subsystem and the first SIM card is performed within the subsystem. In response to a user's input to activate the subsystem in the main system, the subsystem is activated to associate it with the first SIM card within the subsystem, improving the security and privacy of the association. Correspondingly, before receiving a second SMS message from the second number to the first SIM card while the second interface of the main system is displayed, in response to a fourth user input in the subsystem, the main system is switched to display.

[0030] Optionally, to improve security, the subsystem is activated after successful authentication in response to a user's input to activate the subsystem in the main system.

[0031] In addition, the association between the aforementioned subsystem and the first SIM card can also be performed within the main system, improving the convenience of the association.

[0032] Optionally, the above-mentioned association process may include:

[0033] In response to user input, a corresponding interface is displayed. This interface includes a first option corresponding to the first SIM card and a second option corresponding to the second SIM card. The first option is used to associate the subsystem with the first SIM card and the main system with the second SIM card. The second option is used to associate the subsystem with the second SIM card and the main system with the first SIM card.

[0034] The first operation mentioned above refers to the operation on the first option corresponding to the first SIM card.

[0035] Based on this, the subsystem provides an interface that allows users to associate the parallel space with their SIM card. Users can select the first or second option on the interface according to their association needs, which improves the convenience of the association operation and makes it easier for users to associate the parallel space with the SIM card.

[0036] In one possible design approach, the aforementioned operations for opening the subsystem include operations on the subsystem icon on the main system's desktop, gesture operations, voice operations, or operations on the access controls provided by the main system's settings application, making it convenient for users to quickly open the subsystem.

[0037] In one possible design, after the subsystem is associated with the first SIM card, the user cannot configure the availability of the first SIM card through the main system, ensuring the effectiveness of SIM card isolation. This means that within the main system, the user can only configure the second SIM card associated with that main system. The main system receives user input and displays the corresponding interface. This interface includes information about both the first and second SIM cards. The first SIM card information includes a prompt message but does not include the first SIM card number. This prompt message indicates that the first SIM card is associated with the subsystem. The second SIM card information includes the second SIM card number. Therefore, after associating the first SIM card with the subsystem, the second SIM card number is not visible through the main system, protecting user privacy.

[0038] This interface includes a third option for the second SIM card, but does not include a fourth option for the first SIM card. The third option is used to enable or disable the second SIM card. The fourth option is used to enable or disable the first SIM card. This is to prevent users from knowing information about the first SIM card associated with the subsystem, thus protecting user privacy.

[0039] Alternatively, the interface may include a third option and a fifth option corresponding to the first SIM card. The fifth option is used to indicate the association of the first SIM card with the subsystem, and the fifth tab cannot be used to set the first SIM card to be on or off.

[0040] In one possible design, the aforementioned third interface includes a first sending control and the SMS records of the first SIM card, but excludes the SIM card option control and the SMS records of the second SIM card. The second SMS message belongs to the SMS records of the SIM card. The first sending control is used to trigger the sending of an SMS message using the first SIM card.

[0041] Before associating the subsystem with the first SIM card, in response to a fourth operation input by the user, the electronic device displays a seventh interface of the second information application in the main system. This seventh interface includes a SIM card option control and a second sending control, SMS records of the first SIM card and the second SIM card, and the SIM card option control is used to trigger switching of the SIM card for sending SMS messages.

[0042] In this application, before associating the subsystem with the first SIM card, since the electronic device includes multiple SIM cards, the sixth interface provided by the second information application of the main system, which includes a sending control, also includes a SIM card option control, requiring the user to select the SIM card for SMS service according to their needs. After associating the subsystem with the first SIM card, the first information application of the subsystem provides a third interface including a sending control. This third interface no longer includes the SIM card option control and does not support the user selecting the SIM card for SMS service. This allows the user to directly use a specific SIM card for SMS service, achieving SIM card isolation and meeting the user's need to use a specific SIM card for SMS service within the subsystem, i.e., in a parallel space. This satisfies user needs in different usage scenarios and ultimately meets the user's personalized communication needs. Furthermore, it avoids the need for the user to select a SIM card to use SMS service, improving the efficiency of SMS service. In addition, before association, the sixth interface mixed SMS records from multiple SIM cards, while after association, the third interface only included SMS records from the first SIM card associated with the subsystem being used, thus isolating the SMS records of the SIM cards and meeting the user's need to use some SIM cards for privacy purposes, thereby effectively protecting the user's privacy.

[0043] In one possible design, the SMS records of the first SIM card represent SMS messages received and sent via the first SIM card. The SMS records of the second SIM card represent SMS messages received and sent via the second SIM card.

[0044] After associating the subsystem with the first SIM card, the SMS records of the first SIM card are stored in the first storage location, and the SMS records of the second SIM card are stored in the second storage location. The second storage location differs from the first storage location, achieving isolated storage of SMS records from different SIM cards. This ensures that SMS records within different systems are not visible to each other, protecting user privacy, achieving effective management of SIM card isolation, and improving the user experience.

[0045] In one possible design, the first storage location is a first data table in the SMS database within the electronic device, and the second storage location is a second data table in the same SMS database. The first and second data tables are different. Based on this, by storing SMS records from different SIM cards in different data tables within the same SMS database, the electronic device only needs to manage and maintain one database. This improves the efficiency of managing and maintaining the SMS database while achieving isolated storage of SMS records from different SIM cards.

[0046] Alternatively, the first storage location can be a second SMS database within the electronic device, and the second storage location can be a first SMS database within the electronic device, with the second SMS database being different from the first SMS database. Based on this, by storing SMS records from different SIM cards in different SMS databases, each SMS database only stores the SMS records of its corresponding SIM card, facilitating SMS record management.

[0047] In one possible design, before associating the subsystem with the first SIM card, the SMS records of both the first and second SIM cards are stored in a second storage location. Correspondingly, after associating the subsystem with the first SIM card, the electronic device can save the SMS records of the first SIM card from the second storage location to the first storage location, achieving SMS record migration and thus enabling isolated storage for different SIM cards.

[0048] Alternatively, before associating the subsystem with the first SIM card, the SMS records of both the first and second SIM cards are stored in a third storage location. This third storage location is different from both the first and second storage locations. After associating the subsystem with the first SIM card, the electronic device can save the SMS records of the first SIM card from the third storage location to the first storage location, and save the SMS records of the second SIM card from the third storage location to the second storage location, thus migrating the SMS records and achieving isolated storage for different SIM cards.

[0049] In one possible design approach, the aforementioned third interface includes a first contact control, which is used to trigger the display of contact information within the subsystem.

[0050] The seventh interface includes a second contact control, which is used to trigger the display of contact information within the main system.

[0051] The contact information in the subsystem differs from that in the main system.

[0052] Based on this, contact information within the subsystem and the main system are isolated from each other, allowing users to configure contact information in different systems according to their needs. Furthermore, contact information in one system cannot be viewed in another, ensuring that contact information across different systems is mutually invisible and protecting user privacy.

[0053] In one possible design approach, the difference between the contact information in the aforementioned subsystem and the contact information in the main system includes at least one of the following situations:

[0054] The contact information in the subsystem includes the name of the first contact person, and the contact information in the main system also includes the name of the first contact person. However, the number corresponding to the name of the first contact person in the subsystem is different from the number corresponding to the name of the first contact person in the main system.

[0055] The contact information in the subsystem includes the first number, and the contact information in the main system also includes the first number. However, the contact name corresponding to the first number in the subsystem is different from the contact name corresponding to the first number in the main system.

[0056] The contact information within the subsystem includes the first contact information, while the contact information within the main system does not include the first contact information.

[0057] The contact information in the main system includes the second contact information, while the contact information in the subsystem does not include the first contact information.

[0058] Optionally, the contact information in the above subsystem includes a first number and a first contact name corresponding to the first number, and the contact information in the main system includes a first number and a second contact name corresponding to the first number, wherein the first contact name and the second contact name are different;

[0059] The contact information in the subsystem includes the second number, while the contact information in the main system does not include the second number.

[0060] In some embodiments, contact information in the main system and subsystem is isolated before association. Of course, it can also be set to not be isolated, depending on requirements. After association, contact information in the main system and subsystem is isolated; that is, contact information stored in the main system is stored separately from contact information stored in the subsystem.

[0061] In a second aspect, an electronic device is provided, including a memory, a display screen, and one or more processors. The memory and processors are coupled. The memory stores computer program code, including computer instructions. The display screen displays images generated by the processor. When the processor executes the computer instructions, it causes the electronic device to perform any of the actions described in the first aspect above.

[0062] Thirdly, a computer-readable storage medium is provided, including computer instructions that, when executed on an electronic device, enable the electronic device to perform any of the methods described in the first aspect above.

[0063] Fourthly, a computer program product is provided, including a computer program, wherein when the computer program is executed by a processor, it implements any one of the methods in the first aspect above.

[0064] It is understood that the beneficial effects achieved by the electronic device of the second aspect, the computer-readable storage medium of the third aspect, and the computer program product of the fourth aspect provided above can be referred to the beneficial effects of the first aspect and any possible implementation thereof, which will not be repeated here. Attached Figure Description

[0065] Figure 1A is a schematic diagram of a parallel space provided in an embodiment of this application;

[0066] Figure 1B is a schematic diagram of a parallel space provided in an embodiment of this application;

[0067] Figure 1C is a schematic diagram of a parallel space provided in an embodiment of this application;

[0068] Figure 1D is a schematic diagram of a parallel space provided in an embodiment of this application;

[0069] Figure 1E is a schematic diagram of a parallel space provided in an embodiment of this application;

[0070] Figure 1F is a schematic diagram of a parallel space provided in an embodiment of this application;

[0071] Figure 1G is a schematic diagram of a parallel space provided in an embodiment of this application;

[0072] Figure 2 is a schematic diagram of a text message scenario provided in an embodiment of this application;

[0073] Figure 3 is a schematic diagram of a text message scenario provided in an embodiment of this application;

[0074] Figure 4 is a schematic diagram of a SIM card binding method provided in an embodiment of this application;

[0075] Figure 5 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0076] Figure 6 is a schematic diagram of the software architecture of an electronic device provided in an embodiment of this application;

[0077] Figure 7 is a flowchart illustrating a method for sending text messages according to an embodiment of this application;

[0078] Figure 8 is a schematic diagram of a text message scenario provided in an embodiment of this application;

[0079] Figure 9 is a schematic diagram of a text message scenario provided in an embodiment of this application;

[0080] Figure 10 is a schematic diagram of a text message scenario provided in an embodiment of this application;

[0081] Figure 11 is a schematic diagram of a text message scenario provided in an embodiment of this application;

[0082] Figure 12 is a schematic diagram of a text message scenario provided in an embodiment of this application;

[0083] Figure 13 is a flowchart illustrating a method for receiving text messages according to an embodiment of this application;

[0084] Figure 14 is a schematic diagram of a text message scenario provided in an embodiment of this application;

[0085] Figure 15 is a flowchart illustrating a notification display method provided in an embodiment of this application;

[0086] Figure 16A is a schematic diagram of a text message scenario provided in an embodiment of this application;

[0087] Figure 16B is a schematic diagram of a text message scenario provided in an embodiment of this application;

[0088] Figure 17 is a schematic diagram of a text message scenario provided in an embodiment of this application;

[0089] Figure 18 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0090] Figure 19 is a schematic diagram of the structure of a chip system provided in an embodiment of this application. Detailed Implementation

[0091] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "exemplary" or "for example" are used in the embodiments of this application to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a specific manner. In the embodiments of this application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. In the embodiments of this application, "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "multiple" means two or more.

[0092] For ease of understanding, some terms involved in the embodiments of this application will be explained below.

[0093] The main system is the primary operating system of an electronic device. It is responsible for managing and controlling the device's resources, such as hardware resources like the CPU and software resources like applications (APPs). The main system runs the main space, which is the primary user space of the electronic device. Users can install and run applications within this main space as needed.

[0094] A subsystem is an application running at the application layer of the main system, and its operation depends on the main system. A subsystem can run a virtual user space (hereinafter referred to as "parallel space"). The parallel space is an independent virtual user space relative to the main space, enhancing privacy and security. Applications can also be installed and run within the parallel space. Applications in the parallel space are independent of those in the main space; they can be the same or different. The parallel space and the main space can be displayed simultaneously (including split-screen display as shown in Figure 1A, or floating display of the parallel space on top of the main space as shown in Figure 1B). Alternatively, only one of the parallel space or the main space can be displayed in the foreground (refer to Figure 1C showing the main space in the foreground). The parallel space and the main space each have independent storage space. For example, users cannot access user data in the parallel space while in the main space; they can only access user data in the parallel space after entering it. Furthermore, the parallel space can store highly confidential data.

[0095] The simultaneous display of the parallel space and the main space can be achieved in response to user actions while only the parallel space is displayed in the foreground of the electronic device. For example, while the parallel space is displayed in the foreground, the electronic device can display full-screen display controls, split-screen display controls, and floating window display controls. The split-screen display control triggers the split-screen display of the parallel space and the main space, while the floating window display control triggers the parallel space to float on top of the main space. Users can trigger the split-screen display control or the floating window display control as needed to allow the electronic device to display both the parallel space and the main space simultaneously. As another example, while the parallel space is displayed in the foreground, the user can trigger the simultaneous display of the parallel space and the main space through a specific gesture 1.

[0096] Additionally, while the parallel space and the main space are displayed simultaneously, users can also stop displaying the parallel space or the main space using the full-screen display control or a specific gesture 2.

[0097] It should be noted that the parallel space and the main space can be displayed in split-screen mode, either horizontally or vertically. In horizontal split-screen mode, the parallel space can be displayed on the left and the main space on the right (see Figure 1A); or the parallel space can be displayed on the right and the main space on the left. In vertical split-screen mode, the parallel space can be displayed at the top or bottom, and the main space on the other side.

[0098] The aforementioned floating display can be either a parallel space as shown in Figure 1B floating on the main space, or a main space floating on a parallel space; this application does not limit it.

[0099] To enhance data security within the parallel space, user identity verification can be performed upon entry. Therefore, a password or biometric authentication method, such as fingerprint or facial recognition, can be set for entering the parallel space. The parallel space password can be different from or the same as the main space password; the parallel space biometric authentication method can be the same as or different from the main space biometric authentication method, depending on the application requirements. For example, in response to a user's interaction with the parallel space icon displayed in the main space (Figure 1D(a)), the electronic device displays the authentication interface shown in Figure 1D(b). After successful authentication, the user enters the parallel space and sees the desktop of the parallel space as shown in Figure 1D(c). It is understood that the parallel space icon displayed in the main space as shown in Figure 1D(a) is only one possible way to enter the parallel space; other methods are also available, such as entering via gestures as shown in Figure 1E, or entering via the parallel space entry control in the main space settings application as shown in Figure 1F. Alternatively, if the electronic device does not have a parallel space created, the user can create one first. For example, when a user needs to create a parallel space, they can click the "Start" control on the creation interface as shown in Figure 1G, and the electronic device will respond by creating the parallel space. Afterward, the electronic device can directly or in response to the user's operation to enter the parallel space. Optionally, after the parallel space is created, the parallel space icon as shown in Figure 1C will be displayed on the desktop of the electronic device's main space.

[0100] Parallel Space Usage / Enablement: The "Parallel Space Usage / Enablement" in this solution includes two situations: (1) When the electronic device displays the interface in the parallel space, it returns to the main space through a preset gesture. After the electronic device detects the preset gesture, it displays the system desktop of the main space, and the parallel space runs in the background. For example, the user can slide their finger from the bottom of the screen of the electronic device to the top of the screen (slide-up gesture) until the finger is beyond the center line of the screen and then lift it up. After the electronic device detects the slide-up gesture, it returns to the main space and displays the desktop of the main space. (2) The parallel space is displayed in the foreground.

[0101] Parallel Space Not Used / Not Opened: Parallel Space is either exited or destroyed, referred to as "Parallel Space Not Used / Not Opened" in this solution. Users can trigger the electronic device to exit Parallel Space and enter the main space by clicking the exit control shown in Figure 1D (c) on the desktop of Parallel Space. Exiting Parallel Space means closing Parallel Space and stopping its use. After exiting Parallel Space, it will not continue to run in the background.

[0102] Additionally, if a user no longer wishes to use the parallel space, they can destroy it. For example, in response to the user's action of destroying the parallel space control as shown in Figure 1F, the electronic device destroys the parallel space. Optionally, after the parallel space is destroyed, the parallel space icon will no longer exist on the main system's desktop, and the data within the parallel space will also be lost.

[0103] The term "parallel space" is used for illustrative purposes only. In practical applications, parallel space can also be referred to as parallel system, twin system application, twin security system, clone system, second system, security system, etc. In the embodiments of this application, it is described as "parallel space". In addition, the electronic device of this application can be a foldable screen phone or a non-foldable screen phone, etc., without limitation. For ease of explanation, a foldable screen phone is used as an example for illustration in this application.

[0104] The above has introduced some of the terms used in this application. The following is a description of the solution proposed in this application.

[0105] Based on the functions currently offered by electronic devices, users can use them for activities such as making calls and sending / receiving text messages. Currently, electronic devices support multiple SIM cards, meaning multiple phone numbers can be used to make and receive voice calls, and to send and receive text messages and MMS. Taking dual SIM cards as an example, currently users use both SIM cards in the primary SIM slot, making it impossible to distinguish between usage scenarios, which causes inconvenience. In different scenarios such as work and daily life, users may wish to be able to differentiate the usage scenarios of different SIM cards.

[0106] The following example uses a foldable screen phone that supports dual SIM cards to illustrate how an electronic device can use multiple SIM cards for SMS services within its main storage space.

[0107] Sending SMS: While the electronic device is in its main space, when a user wants to send an SMS to a phone number named "Xiaoming" (hereinafter referred to as sending an SMS to "Xiaoming"), the user can enter the SMS content in the SMS content editing box 12 on the SMS interface 11 shown in Figure 2(a). Additionally, the SIM card option control 13 on the SMS interface 11 displays an icon for SIM card 1 (optionally, this icon displays the number 1), indicating that if an SMS is sent, the electronic device will use SIM card 1 to send the SMS.

[0108] If a user wants the electronic device to send a text message using SIM card 2, the user can click the SIM card option control 13. In response to clicking the SIM card option control 13, the electronic device can display SIM card option 14 as shown in Figure 2(b), which includes option 15 for SIM card 1 and option 16 for SIM card 2. Then, in response to the user's action on option 16, the electronic device displays the text message interface 17 as shown in Figure 2(c), where the SIM card option control 13 displays the icon of SIM card 2 (optionally, the icon displays the number 2). The user can click the send control 18 on the text message interface 17. In response to the user's click on the send control 18, the electronic device uses SIM card 2 to send text message 1 to Xiaoming, displaying interface 19 as shown in Figure 2(d). Interface 19 displays the text message content 20 of the just-sent text message 1 and the icon of the SIM card 2 corresponding to text message 1. It should be understood that SMS 1 can be considered as a single SMS record for the recipient, or the SMS record may include not only SMS 1 but also other information about SMS 1, such as the sending time.

[0109] In addition, the interface 19 also includes the historical SMS records corresponding to "Xiaoming", such as historical SMS records 21a, 21b, and 22 on interface 19. Historical SMS record 21a represents SMS messages sent by the electronic device through SIM card 1. Historical SMS record 21b represents SMS messages sent by the electronic device through SIM card 1. Historical SMS record 22 represents SMS messages received by the electronic device through SIM card 2.

[0110] Receiving SMS: When the electronic device receives an SMS message whose recipient number is the number corresponding to SIM card 1 while in the main space, it displays SMS notification message 30 as shown in Figure 3(a). In response to the user's click operation on the SMS notification message 30, the electronic device displays SMS message 31 corresponding to SMS notification message 30 as shown in Figure 3(b), indicating that the recipient number of SMS message 31 is the number corresponding to SIM card 1, that is, the electronic device received SMS message 31 through SIM card 1.

[0111] In addition, while in the main space, the electronic device can also receive SMS messages with the recipient number being the number corresponding to SIM card 2, such as SMS 32 shown in Figure 3(b) above.

[0112] Because electronic devices do not effectively isolate and manage the two SIM cards, it is impossible to support only the use of a specific SIM card for SMS services in specific scenarios according to user needs. Furthermore, the same user interface (such as the SMS interface including Xiaoming's SMS records mentioned above) displays SMS data from both SIM cards, increasing the difficulty for users to view SMS data from different SIM cards and thus increasing the complexity of SMS management. Additionally, it fails to meet users' needs to display only the SMS records corresponding to a specific SIM card in a particular user space, thus failing to effectively protect user privacy.

[0113] Therefore, to address the aforementioned issues, this application proposes a solution for isolating and managing multiple SIM cards on an electronic device. The electronic device supports establishing a correspondence between user spaces and SIM cards, allowing users to specify the SIM card used for services within a user space according to their needs. Taking SMS service as an example, after binding a SIM card to a user space (such as a parallel space), while in that parallel space, the electronic device can only use the SIM card bound to that parallel space for SMS service, and cannot use any SIM card not bound to the parallel space. Furthermore, the main space can only use its corresponding SIM card, i.e., the SIM card not bound to the parallel space, for SMS service. This effectively isolates and manages multiple SIM cards, meeting users' needs or preferences in different user spaces, thereby satisfying users' personalized communication service needs and avoiding the need for users to select a specific SIM card for SMS service, thus improving the efficiency of SMS service.

[0114] After receiving a text message from the SIM card bound to Parallel Space, the electronic device can determine whether preset conditions are met. These preset conditions may include one or more of the following: Parallel Space is in an unused state, or Parallel Space is in an unused state and the message hiding function is enabled. The message hiding function means that when Parallel Space is disabled, notification messages corresponding to the SIM card associated with Parallel Space are not displayed.

[0115] If preset conditions are met, indicating that the user does not want notification messages corresponding to SMS messages from the parallel space to be displayed in the main space during periods when the parallel space is not in use, the electronic device can hide these notification messages to avoid displaying unnecessary notifications. This effectively disables SMS notifications for the SIM card bound to the parallel space while it is not active, preventing interference with the user's use of the electronic device. Furthermore, it prevents the leakage of SMS messages related to the parallel space and keeps others from knowing that the electronic device has other SIM cards, satisfying the user's need to use some SIM cards for private purposes and effectively protecting user privacy. Additionally, the user cannot directly view these SMS messages through the main system, thus achieving message hiding.

[0116] Furthermore, by isolating and managing SIM cards, each user space only displays SMS data associated with that specific SIM card (i.e., SMS messages received or sent through that SIM card), and excludes SMS data associated with other SIM cards. This allows users to quickly view the SMS data they need, reducing the complexity of SMS management. It also ensures that SMS data from different user spaces are mutually invisible, meeting users' needs to keep some SIM card-related SMS data private, thus effectively protecting user privacy.

[0117] The process of binding a SIM card to the parallel space can be performed within the parallel space. For example, the parallel space displays interface 40 as shown in Figure 4(a). This interface 40 can be used to trigger the binding of the parallel space with a SIM card, thereby enabling the SIM card isolation function. Interface 40 may include option 41 corresponding to SIM card 1, option 42 corresponding to SIM card 2, and option 43 (no setting). Option 41 corresponding to SIM card 1 triggers the binding of the parallel space with SIM card 1, option 42 corresponding to SIM card 2 triggers the binding of the parallel space with SIM card 2, and option 43 (no setting) triggers the parallel space not to establish a binding with any SIM card, i.e., the SIM card isolation function is disabled. In response to the user's selection of option 42 corresponding to SIM card 2, indicating that the user wants to bind SIM card 2 with the parallel space, the parallel space binds it to SIM card 2, displaying interface 44 as shown in Figure 4(b). After the parallel space is bound to SIM card 2, a corresponding relationship is established between the two. Correspondingly, the main space is bound to SIM card 1, and a corresponding relationship is also established between them. The interface 44 shown in Figure 4(b) includes a switch control 45 for the information hiding function. The information hiding function (or the first hiding function) means that when the parallel space is not in use, SMS messages received through the SIM card bound to the parallel space will not be notified. This switch control is used to set the state of the information hiding function. When the switch control 45 for the information hiding function shown in Figure 4(b) is in the off state, the information hiding function is in the off state. When the user wants to enable the information hiding function, the user can trigger the switch control to enable it (see the switch control 45 in Figure 4(c) in the on state), and the information hiding function will also switch to the on state. For more details about the information hiding function, please refer to the relevant content in Figure 15 below.

[0118] After binding SIM card 2 to the parallel space, the user will not be able to set SIM card 2 in the main space, nor will they be able to see SIM card 2's information, such as its number. For example, after binding the SIM card to the parallel space, the option 47 corresponding to SIM card 1 in the SIM card management interface displayed in the main space (see interface 46 shown in Figure 4(d)) can still be used to set whether SIM card 1 is enabled or disabled (or whether it is available). The option 48 corresponding to SIM card 2 does not support setting whether SIM card 2 is enabled or disabled; it indicates that SIM card 2 has been bound to the parallel space. Of course, the "Parallel space bound" displayed by option 48 corresponding to SIM card 2 in interface 46 shown in Figure 4(d) is only an example. Option 48 corresponding to SIM card 2 can also directly show that no card is inserted, hiding the information of SIM card 2 bound to the parallel space, thus meeting the user's need to prevent others from knowing that SIM card 2 is bound to the parallel space.

[0119] Understandably, users can typically choose to bind either SIM card 1 or SIM card 2 to the parallel space. This means that options 41 and 42 corresponding to SIM card 2 are actually single-select controls. Alternatively, users can choose to bind both SIM card 1 and SIM card 2 to the parallel space; in this case, options 41 and 42 corresponding to SIM card 2 can be multi-select controls.

[0120] Furthermore, the above-described method of binding a SIM card within a parallel space is merely an example; the process of binding a SIM card within a parallel space can also be performed within that parallel space. Similarly, the method of binding a SIM card through the interface 40 provided in Figure 4(a) is also just an example; binding between the parallel space and the SIM card can be achieved in other ways, such as through voice commands. This application does not limit this method.

[0121] For example, the electronic device in this application embodiment can be a mobile phone, tablet computer, desktop computer, laptop computer, handheld computer, notebook computer, ultra-mobile personal computer (UMPC), netbook, as well as wearable devices, personal digital assistant (PDA), augmented reality (AR) / virtual reality (VR) devices, and other electronic devices capable of using multiple SIM cards. The display screen of the electronic device can be a foldable screen or a non-foldable screen; this application embodiment does not impose any special limitations on the specific form of the electronic device.

[0122] Figure 5 shows a schematic diagram of the structure of the electronic device 100.

[0123] Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc.

[0124] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0125] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0126] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0127] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0128] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0129] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the electronic device 100.

[0130] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

[0131] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0132] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0133] The modem processor may include a modulator and a demodulator. The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLANs) (such as Wi-Fi), Bluetooth, Global Navigation Satellite System (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signal, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0134] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, so that electronic device 100 can communicate with networks and other devices through wireless communication technology.

[0135] Electronic device 100 implements display functions through GPU, display screen 194, and application processor.

[0136] The display screen 194 is used to display images, videos, etc. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0137] In some embodiments, the display screen 194 can be a foldable screen, which can be folded or unfolded. Accordingly, the foldable screen device has two device states: a folded state and an unfolded state. The folding method of the foldable screen device can be folding left and right or folding up and down. This application embodiment does not limit the folding method of the foldable screen phone.

[0138] The electronic device 100 can implement shooting functions through an ISP, a camera 193, a video codec, a GPU, a display 194, and an application processor. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0139] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0140] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 100 (such as multimedia files (e.g., images, videos, audio, etc.), structured data, etc.). Furthermore, internal memory 121 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0141] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0142] The sensor module 180 may include pressure sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, accelerometers, distance sensors, proximity sensors, fingerprint sensors, temperature sensors, touch sensors, ambient light sensors, bone conduction sensors, etc.

[0143] Buttons 190 include a power button, volume buttons, etc. Motor 191 can generate vibration feedback. Indicator 192 can be an indicator light, used to indicate charging status, battery level changes, and also to indicate messages, missed calls, notifications, etc.

[0144] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to achieve contact and separation with the electronic device 100. In this scheme, the electronic device 100 can support N SIM card interfaces, where N is a positive integer greater than or equal to N.

[0145] For example, the software system of the aforementioned electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This embodiment of the invention uses the layered architecture Android system as an example to illustrate the software structure of the electronic device 100.

[0146] Figure 5 is a software structure block diagram of an electronic device 100 according to an embodiment of the present invention.

[0147] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system can be divided into at least four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0148] The application layer can include a series of application packages.

[0149] As shown in Figure 6, the application package can include applications in the main space (such as messaging applications, contact applications, call applications, card isolation monitoring modules, etc.) and applications in the parallel space (such as messaging applications, contact applications, call applications, etc.). The messaging application can also be called the SMS application. In addition, the main space and parallel space can also include other applications, such as camera, gallery, etc. This application does not impose any restrictions on the applications included in the main space and parallel space.

[0150] The card isolation monitoring module is used to determine the isolation status of the SIM card in the electronic device, such as determining the SIM card corresponding to the user space. For example, when the user triggers option 16 corresponding to SIM card 2 as shown in Figure 2(b), the parallel space binds it to SIM card 2 and sends a binding instruction to the card isolation monitoring module of the main space. This binding instruction includes the identifier of the parallel space and its corresponding ID of SIM card 2, so that the card isolation monitoring module can save the correspondence between the identifier of the parallel space and the ID of SIM card 2.

[0151] The identifier for a parallel space can be its userid. For example, the userid can be a preset value.

[0152] Optionally, the binding instruction may also include the identifier of the main space and its corresponding identifier ID of the SIM card 1, so that the card isolation module records the correspondence between the identifier of the main space and the ID of the SIM card 1.

[0153] In some embodiments, the operations related to binding the SIM card performed in the parallel space can be performed through the settings application of the parallel space, such as the settings application sending a binding instruction to the card isolation monitoring module of the main space.

[0154] Understandably, since the operation of a subsystem depends on the main system, to ensure smooth operation, functional modules shared by user spaces (such as the main space and parallel spaces) (e.g., isolated listening modules) can run in the main space. When a parallel space needs to use an isolated listening module, it can communicate with the main space to invoke the isolated listening module.

[0155] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0156] As shown in Figure 6, the application framework layer may include telecommunication services, a notification center, a contact database, a telecommunication provider, an SMS database, and a User space Mode-Setting (UMS) service.

[0157] The telecom service is used to implement SMS services, such as sending and receiving SMS messages.

[0158] The notification center is used to display notification messages, such as those from the messaging app.

[0159] Contact database 1 stores contact information within the parallel space of the electronic device. Contact database 2 stores contact information within the main space of the electronic device. Contact database 1 and contact database 2 are independent of each other. Optionally, contact database 1 can be located within the parallel space, and contact database 2 can be located within the main space. Alternatively, contact database 1 can be located at a specific location 1 on the electronic device, and contact database 2 can be located at a specific location 2. Specific location 1 allows access from the parallel space but not from the main space. Specific location 2 allows access from the main space but not from the parallel space.

[0160] The User Space Display Mode Settings service is used to manage user spaces, such as their status. Specifically, the status of a user space can be the running status of the main space (foreground running, background running) or the status of a parallel space (used status, unused status).

[0161] The communication provider stores SMS messages (such as received SMS messages) in an SMS database. The SMS database stores SMS data in the parallel space of the electronic device (i.e., SMS messages received and sent through the SIM card corresponding to the parallel space) and SMS data in the main space (i.e., SMS messages received and sent through the SIM card corresponding to the main space).

[0162] The SMS data in the parallel space and the SMS data in the main space are independent of each other. For example, the SMS data in the parallel space is stored in the data table corresponding to the parallel space (or the first data table) in the SMS database, and the SMS data in the main space is stored in the data table corresponding to the main space (or the second data table) in the SMS database. The data table corresponding to the parallel space is different from the data table corresponding to the main space. Optionally, the SMS database can be located at a specific location 3 on the electronic device, and this specific location 3 allows access from both the parallel space and the main space.

[0163] In some embodiments, as shown in FIG6, the SMS database may include SMS database 1 (or first SMS database) corresponding to the parallel space and SMS database 2 (or second SMS database) corresponding to the main space. SMS database 1 stores SMS data within the parallel space, and contact database 2 stores SMS data within the main space. Optionally, SMS database 1 may be located in the parallel space, and SMS database 2 may be located in the main space. Alternatively, SMS database 1 may be located at a specific location 4 on the electronic device, and SMS database 2 may be located at a specific location 5. This specific location 4 allows access from the parallel space but not from the main space. This specific location 5 allows access from the main space but not from the parallel space.

[0164] Alternatively, both SMS database 1 and SMS database 2 can be stored in the main space; this application does not restrict their storage location.

[0165] In this embodiment, SMS data corresponding to SIM cards in different user spaces is isolated through an application layer and an application framework layer. The application layer isolates the operational logic that interacts with the user; simply put, the user can only obtain the SMS data corresponding to the SIM card in that user space from the content displayed in that user space. The application framework layer stores the SMS data corresponding to the SIM cards in different user spaces in an isolated manner.

[0166] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

[0167] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0168] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0169] The kernel layer is the layer between hardware and software. The kernel layer contains at least display drivers and sensor drivers.

[0170] The software layers included in the electronic device described above are merely examples. An electronic device may include other software layers or only one or more of the aforementioned software layers; this application does not limit its scope. Similarly, the content included in the aforementioned software layers is merely an example. For instance, the application framework layer may also include other modules, such as a window manager, content provider, view system, phone manager, resource manager, etc.

[0171] This application provides a method for sending and receiving SMS messages in a multi-user space, as well as a method for displaying notifications. The electronic device supports multiple SIM cards, and the user space of the electronic device can establish a correspondence with each SIM card. This ensures that the electronic device can only use its corresponding SIM card when sending or receiving SMS messages within that user space, and cannot use uncorresponding SIM cards, thus effectively achieving isolated management of the SIM cards. Furthermore, during SIM card isolation, after receiving an SMS message, the electronic device can hide SMS notifications based on the usage of the parallel space, protecting user privacy and avoiding the interference of frequent and unnecessary SMS notifications, thereby improving user satisfaction.

[0172] The following section, using a foldable phone that supports dual SIM cards as an example, and referring to Figure 5, will introduce the possible implementation processes of SMS sending, receiving, and notification display methods after SIM isolation. The implementation process of the SMS sending method can be found in the SMS sending section below, the SMS receiving method can be found in the SMS receiving section below, and the notification display method can be found in the section on hiding SMS notifications below.

[0173] Send SMS:

[0174] In this embodiment, the parallel space can be bound to a SIM card (such as SIM card 2) using the SIM card binding method described in Figure 4 above, or other methods. After binding SIM card 2 to the parallel space, a corresponding relationship is established between the parallel space and SIM card 2, and a corresponding relationship is established between the main space and SIM card 1. Then, when a user wants to send a text message in the parallel space, the user can input relevant operations within the parallel space to trigger the display of the corresponding text message interface. This text message interface includes a sending control but does not include a SIM card option control; that is, the parallel space does not support selecting SIM card 1 to send a text message. After the user finishes editing the text message on the text message interface (such as entering the recipient's number, text message content, etc.), in response to the user's click operation on the sending control, the parallel space directly uses SIM card 2 to send the text message, satisfying the user's need to use only a specific SIM card in a specific scenario, thereby meeting the user's personalized communication needs. Specifically, the text message sending process can include S601-S622 as shown in Figure 7.

[0175] S601, Receive user operations on information application 1.

[0176] S602. In response to the user's operation on Information Application 1, start Information Application 1 and send Request 1 to the card isolation listening module in the main space.

[0177] Request 1 is used to query the card isolation status, i.e., the isolation status of the SIM card. Specifically, it queries whether the electronic device has enabled the SIM card isolation function, and if so, the SIM card ID corresponding to the parallel space.

[0178] For example, the user's operation on the information application 1 could be an operation on the information application 1 icon on the desktop within the parallel space. Of course, launching the information application 1 via the information application 1 icon displayed on the parallel space desktop is only one possible way to launch the information application 1. The information application 1 can also be launched in other ways, such as responding to a specific voice command input by the user, or, if the parallel space supports a negative one screen, responding to the user's click on the information application 1 icon displayed on the negative one screen, the parallel space can launch the information application 1.

[0179] For example, a user clicks the icon 50 of the Message Application 1 on the desktop displayed in the parallel space, as shown in Figure 8(a). In response to the user's click on the icon 50, Message Application 1 can perform a startup operation and send the aforementioned request 1 to the card isolation monitoring module in the main space to determine whether a corresponding SIM card exists in the parallel space. Here, the user's operation on the icon 50 of Message Application 1 can refer to the user's operation on Message Application 1 itself.

[0180] S603. In response to request 1, the card isolation monitoring module returns information 1, which includes the ID of the SIM card corresponding to the parallel space. The ID of the SIM card corresponding to the parallel space is the ID of SIM card 2.

[0181] Specifically, if the binding process records the correspondence between the identifier of the parallel space and the slotid ID of SIM card 2, then in step 603, request 1 is used to obtain the value of slotid. If the slotid value is a first value (e.g., -1), it indicates that the electronic device has not enabled SIM card isolation, and the parallel space can use any SIM card, meaning there is no corresponding SIM card. If the slotid value is a second value (e.g., 1), it indicates that the electronic device has enabled SIM card isolation, and the parallel space corresponds to SIM card 1; correspondingly, the main space also corresponds to SIM card 1. If the slotid value is a third value (e.g., 0), it indicates that the electronic device has enabled SIM card isolation, and the parallel space corresponds to SIM card 2; correspondingly, the main space also corresponds to SIM card 1.

[0182] The aforementioned parallel space can be bound to a single SIM card, in which case the slotid value is a single numeric value, such as a first numeric value or a second numeric value. Alternatively, a parallel space may be bound to multiple SIM cards; therefore, the slotid value may include two numeric values, such as a second numeric value and a third numeric value.

[0183] It should be noted that the SIM card ID can also be other types of IDs, such as the SIM card subid or ICC ID, and this application does not impose any restrictions on them. Furthermore, the fact that the SIM card ID corresponding to the aforementioned parallel space is the ID of SIM card 2 is merely an example; the SIM card corresponding to the parallel space can also be SIM card 1, or both SIM card 1 and SIM card 2, and this application does not impose any restrictions on them.

[0184] S604. After startup, the messaging application 1 displays the SMS interface 1. This SMS interface 1 includes a new SMS control 1.

[0185] The New SMS control 1 is used to trigger the display of the New SMS interface 1, through which SMS messages can be sent.

[0186] Following the example above, after the messaging application 1 is started, the messaging application 1 can display the initial SMS interface, which is the SMS interface 51 shown in Figure 8(b). This SMS interface 1 includes a new SMS control 52. Here, SMS interface 51 can refer to SMS interface 1 in S604, and new SMS control 52 can refer to new SMS control 1 in S604.

[0187] S605. In response to the user's click operation on the new SMS control 1, the messaging application 1 displays the new SMS interface 1. The new SMS interface 1 includes an SMS content editing box, a send control, a recipient number input box, and a contact control, and the new SMS interface 1 does not display the information of the SIM card 1.

[0188] The SMS content edit box is used to enter the SMS message content. The send space is used to trigger the sending of the SMS message. The recipient number input is used to enter the recipient's number. The contact control is used to select the recipient, i.e., the SMS recipient.

[0189] Continuing with the above example, in response to a user's click on the new SMS control 52 shown in Figure 8(b), the messaging application 1 can display the new SMS interface 53 shown in Figure 8(c). This new SMS interface 53 may include an SMS content editing box 54, a sending control 55, a recipient number input box (i.e., a recipient's number input box) 56, and a contact control 57. However, this new SMS interface 53 does not include a SIM card option (such as SIM card option 13 shown in Figure 2(a) above), and no longer displays information about the SIM card 1. This makes the SIM card 1 imperceptible to the user, achieving SIM card isolation and protecting user privacy. Alternatively, the new SMS interface 53 may also include other content besides the SMS content editing box 54, the sending control 55, the recipient number input box (i.e., a recipient's number input box) 56, and the contact control 57; this application does not limit this. The new SMS interface 53 shown in Figure 8(c) may refer to the new SMS interface 1 in S605 above.

[0190] In some embodiments, a corresponding SIM card exists in the parallel space. As described above, after corresponding to SIM card 2, the SMS sending interface (i.e., the interface that can trigger sending SMS) can display the icon of SIM card 2 instead of displaying the information of SIM card 1, thus not supporting the user's selection of SIM card 1. For example, in response to the user's click operation on the new SMS control 1, the messaging application 1 can display the new SMS interface 58 as shown in Figure 8(d). This new SMS interface 58 can include the icon 59 of SIM card 2, so that the user knows that the messaging application 1 will use SIM card 2 to send SMS, avoiding the situation where the user wants to use SIM card 1 to send SMS but uses SIM card 2 instead. Here, the new SMS interface 58 shown in Figure 8(d) can refer to the new SMS interface 1 in S605 above.

[0191] In some embodiments, the SMS interface 1 described above may include an SMS list. The SMS list may include the SMS entries corresponding to SIM card 2 after SIM card 2 is bound to the parallel space. It represents the SMS entries corresponding to SMS messages received or sent through SIM card 2 (such as SMS entry 60 corresponding to Xiaoming as shown in Figure 8(b)). It does not include the SMS messages corresponding to SIM card 1 in the main space after the parallel space is bound to SIM card 2. Thus, the user cannot perceive the SMS messages corresponding to SIM card 1 in the main space within the parallel space, thereby achieving isolated management of SMS messages corresponding to SIM cards and effectively protecting user privacy data.

[0192] In addition, if Message Application 1 is installed in the parallel space before it is bound to the SIM card, the SMS records displayed by Message Application 1 are the same as those displayed by Message Application 2 in the main space. The SMS records corresponding to different SIM cards are not isolated and managed. This meets the user's need to avoid the need for isolated management of SIM cards by electronic devices. It also avoids the situation where the user's needs cannot be met due to the isolation management of SIM cards, which would prevent the user from using two SIM cards for SMS service in one user space.

[0193] The above describes the process of creating a new text message in the information application. After the new text message interface is displayed, you can edit the text message on this interface, such as editing the text message content, the recipient's number, etc. The following will continue to describe the process of editing the text message.

[0194] S606. Receive the user's click operation on the above contact control.

[0195] Taking the simultaneous operation of the main space and parallel space on the foreground of an electronic device as an example, the user clicks on the contact control 62 on the new SMS interface 61 shown on the left side of Figure 9(a). Here, the contact control 62 can refer to the contact control in S606.

[0196] S607. In response to a click on the contact control, the information application 1 sends request 2 to the contact application 1 in the parallel space. Request 2 is used to query the contact information corresponding to the parallel space.

[0197] The contact information in the parallel space refers to the contact information stored in contact database 1, which users cannot access in the main space. The contact information in the parallel space may be completely the same as or different from the contact information in the main space; for details on the differences, please refer to the explanation below.

[0198] The contact information corresponding to the aforementioned parallel space can be entered by the user within the parallel space. Users can set different contact names for the same contact number in the main space and the parallel space. The contact information in the parallel space can also come from the contact database 2 in the main space. For example, after the parallel space is destroyed or exited, the contact data of the original parallel space can be saved to the contact database 2 in the main space. When the parallel space is opened again, the contact data of the parallel space in the main space will be migrated to the contact database 1 of the parallel space.

[0199] S608. In response to request 2, Contact Application 1 queries the contact information corresponding to the parallel space from Contact Database 1.

[0200] S609. Contact application 1 sends contact information corresponding to the parallel space to information application 1.

[0201] S610, Information Application 1 displays contact information corresponding to the parallel space.

[0202] In this embodiment of the application, the contact control triggers information application 1 to obtain and display contact information (or describe it as contact information within the parallel space) in the user data corresponding to the parallel space, so as to select the recipient (i.e., the recipient) from the contact information.

[0203] Continuing with the example above, in response to the user's click on the contact control 62 in Figure 9(a), the information application 1 queries the contact information corresponding to the parallel space through the contact application 1, and displays the contact information list corresponding to the parallel space as shown in the left part of Figure 9(b). This list includes contact information 63 with the name "Xiaomei", contact information 64 with the name "Xiaoming", and contact information 67 with the name "Xiaowang". Xiaomei's number is 13XX, Xiaoming's number is 15XX, and Xiaowang's number is 18XX.

[0204] In addition, the right side of Figure 9(b) shows the contact information list corresponding to the main space. By comparing it with the contact information list corresponding to the parallel space shown on the left side, the contact information lists corresponding to the main space and the parallel space can be different. That is to say, the contact information in the main space and the contact information in the parallel space can be different.

[0205] In this embodiment, the contact databases corresponding to different user spaces are different, thereby achieving isolated storage of contact information corresponding to different user spaces. This prevents the contact information displayed in one user space from including contact information corresponding to other user spaces, thus preventing the leakage of contact information corresponding to other user spaces and effectively protecting user privacy.

[0206] It should be noted that the difference between the contact information in the main space and the parallel space can be entirely different or partially different. Completely different means that every contact in the parallel space is different from the contact information in the main space. Partially different means that some contact information in the parallel space also exists in the main space, but for other contacts in the parallel space, the main space does not contain that contact information. Specifically, the difference between the contact information in the parallel space and the main space can be that for the same number, both the main space and the parallel space store that number (i.e., both contact database 2 and contact database 1 store that number), but the corresponding contacts are different. For example, in Figure 9(b), the contact information 65 in the main space named "Xiao Li" contains the number "15XX," and the contact information 64 in the parallel space named "Xiao Ming" also contains the number "15XX." Although the numbers are the same, the corresponding contact names are different.

[0207] The contact information in the parallel space differs from that in the main space in another way: both the main space and the parallel space store a certain contact name, but the corresponding phone number is different. For example, as shown in Figure 9(b), both the main space and the parallel space store contact information for a person named "Xiaomei". The phone number in contact information 66 for "Xiaomei" in the main space is "12XX", while the phone number in contact information 63 for "Xiaomei" in the parallel space is "13XX".

[0208] The difference between contact information in the parallel space and the main space can also be that, for a certain contact information in the parallel space, there is no contact information in the main space (i.e., contact database 2) with the same contact name or number as that contact information. For example, as shown in Figure 9(b), contact information 67 with the name "Xiao Wang" does not exist in the main space, nor does it contain contact information with the name "Xiao Wang" or the number "Xiao Wang's number, i.e., 18XX". Similarly, for a certain contact information in the main space (i.e., contact database 2), there is no contact information in contact database 1 with the same contact name or number as that contact information.

[0209] It is understandable that both the aforementioned Contacts Application 1 and Messages Application 1 belong to a parallel space, and the aforementioned Contacts Database 1 can also belong to a parallel space, or be located in a specific location 1 on the electronic device. This specific location 1 allows access from the parallel space but not from the main space. The sending of Request 2 is actually a mutual call between applications. Simply put, S607-S609 can be described as follows: Messages Application 1 calls Contacts Application 1 to query contact information in the parallel space from Contacts Database 1.

[0210] S611, Information Application 1 receives the user's operation on the information of Contact 1 in the contact information corresponding to the parallel space.

[0211] Continuing with the example above, in response to the user's selection of contact information 64 with the name "Xiaoming" as shown in Figure 9(b), contact application 1 sends contact information 64 to messaging application 1. Then, messaging application 1 can display "Xiaoming" in the recipient number input box 69 in interface 68 shown in Figure 9(c), where "Xiaoming" is the recipient.

[0212] S612. In response to an operation on the information of contact 1, information application 1 displays the name of contact 1 in the recipient number input box.

[0213] S613, Information Application 1 displays the SMS content entered by the user in the SMS content editing box.

[0214] Continuing with the example above, users can enter text message content in the text message content editing box 70 within interface 68 to edit the text message to be sent. Interface 68 may also include a sending control 71, which can be used to trigger the sending of a text message.

[0215] In addition, since there are SMS records corresponding to "Xiaoming" in the parallel space, that is, Xiaoming sent SMS to the number corresponding to SIM card 2 and received SMS from the number corresponding to SIM card 2, the SMS records corresponding to "Xiaoming" can also be displayed in Figure 9(c) above.

[0216] In some embodiments, determining the recipient's number through contact information as described in S606-S612 above is only one possible way to determine the recipient. Other methods can also be used, such as directly entering the recipient's number in the recipient number input box 69. Furthermore, the above-mentioned method of triggering the display of the SMS sending interface in the parallel space via the newly created SMS control 1 (or newly created message control 1) is only one example. The electronic device also supports other methods for displaying the SMS sending interface. For example, taking the example of the electronic device running both the main space and the parallel space simultaneously in the foreground, the user can click on the SMS entry 72 corresponding to "Xiaoming" shown in the left part of the parallel space in Figure 10(a). In response to this click, the message application 1 can display an interface 73 including the SMS records corresponding to "Xiaoming," as shown in the left part of the parallel space in Figure 10(b). This interface 73 includes a sending control 74 and can also serve as the SMS sending interface. As another example, taking the example of the electronic device only running the parallel space in the foreground, the parallel space displays the call records corresponding to "Xiaoming," as shown in Figure 11(a). In response to a click on the icon 75 of the information application 1 in the call log, the parallel space launches the information application 1 and displays an interface 76 as shown in Figure 11(b), which includes the SMS record corresponding to "Xiaoming". This interface 76 includes a sending control 77 and can be used as an SMS sending interface.

[0217] In some embodiments, after Parallel Space is bound to a SIM card, when Parallel Space displays SMS records, the SMS records may include an icon of the SIM card 2 corresponding to Parallel Space (icon 78 as shown in Figure 12) to indicate that the SMS data in the SMS record was sent or received through the SIM card 2 of the electronic device. Furthermore, since Parallel Space is only bound to SIM card 2, the electronic device is essentially a single SIM card for Parallel Space. Therefore, the SIM card 2 icon may not be displayed for the SMS records, as shown in Figure 9(c), Figure 10(b), or Figure 11(b) above. This prevents others from knowing that the electronic device has another SIM card when only Parallel Space is running in the foreground, thus protecting user privacy.

[0218] In some embodiments, to effectively isolate SIM cards, when the electronic device is running only the parallel space in the foreground, the status bar of the electronic device only displays the signal strength icon corresponding to the SIM card in the parallel space (see signal strength icon 79 shown in Figure 11(b)), thus making the SIM card in the main space undetectable to the user and protecting user privacy. Similarly, when the electronic device is running only the main space in the foreground, the status bar of the electronic device only displays the signal strength icon corresponding to the SIM card in the main space, thus making the SIM card in the parallel space undetectable to the user.

[0219] When the electronic device simultaneously runs parallel space and main space, the interface displaying parallel space shows an icon indicating the signal strength of the SIM card corresponding to parallel space, while the interface displaying main space shows an icon indicating the signal strength of the SIM card corresponding to main space, as shown in Figure 10(a) or (b). The wireless network icon can also be displayed on the left and right sides as shown in Figure 10(a) or (b). Alternatively, the wireless network icon can be displayed only on one side, as shown in Figure 9(a), (b), or (c) above, where the wireless network icon is displayed on the left.

[0220] Furthermore, regardless of whether the electronic device is running only the parallel space, only the main space, or both parallel and main spaces simultaneously, the status bar of the electronic device will display the signal strength icons for the SIM cards corresponding to the parallel space and the main space, as shown in Figure 9(a), (b), or (c) above. Typically, the electronic device is used by the owner. Displaying the signal strength icons for both SIM cards avoids confusion as to why only one SIM card is displayed when two are installed, thus preventing the owner from mistakenly believing the electronic device is malfunctioning.

[0221] The above describes the process of editing a text message. After editing, the electronic device can send the edited message to realize the text message sending service. The following will continue to describe the text message sending process.

[0222] S614. In response to the user's click operation on the aforementioned send control, the messaging application 1 generates SMS 1 and sends instruction 1 to the telecom service. Instruction 1 is used to trigger the telecom service to send SMS 1 to contact 1.

[0223] For example, instruction 1 may include the ID of SIM card 2, the number of contact 1, and the content of the text message. After receiving instruction 1 from messaging application 1, the telecom service responds to instruction 1 by sending text message 1 to the number of contact 1 using SIM card 2. Accordingly, the terminal with the SIM card corresponding to the number of contact 1 installed can receive text message 1, thereby fulfilling the need to send text messages using a specific SIM card in a parallel space.

[0224] S615, In response to instruction 1, the Telecom service sends SMS 1 to contact 1.

[0225] S616. If the transmission is successful, the telecom service sends a success response message to the messaging application 1.

[0226] S617, in response to a successful message being sent, Message application 1 displays SMS interface 2, which includes SMS 1.

[0227] For example, the successful transmission response message is a success message. After receiving the successful transmission response message, the messaging application 1 determines that SMS 1 has been successfully sent, and SMS 1 can be displayed as a new SMS record on the messaging interface 2.

[0228] Optionally, the SMS interface 2 may also include the sending status of SMS 1, which indicates that SMS 1 has been sent successfully.

[0229] In some embodiments, not only may SMS messages be sent successfully, but they may also fail to be sent. When SMS message 1 fails to be sent, the messaging application 1 can display an SMS interface 3, which includes SMS message 1 and its corresponding sending status, indicating that the sending failed.

[0230] Optionally, if SMS 1 fails to be sent, the messaging application 1 can also obtain and display the reason for the failure to send SMS 1, so that the user can discover and resolve the problem in a timely manner.

[0231] In some embodiments, after the electronic device sends SMS 1, the messaging application 1 can also save SMS 1 in the SMS database, so that the messaging application 1 can read SMS 1 from the SMS database and perform operations on SMS 1, such as displaying SMS 1. The process of saving SMS 1 will be described below.

[0232] S618, Information application 1 sends request 3 to the communication provider. Request 3 is used to trigger the saving of SMS message 1.

[0233] Request 3 may include SMS 1. If SMS 1 is successfully sent, the messaging application 1 may send request 3 carrying SMS 1 to the communication provider so that the communication provider can save SMS 1 to the SMS database.

[0234] In addition, SMS sending may fail. If SMS 1 fails to send, messaging application 1 can also send SMS 1 to the communication provider so that the communication provider can save SMS 1 to the SMS database. This way, when messaging application 1 needs to read the SMS records of contact 1 from the SMS database, it can read all the SMS records.

[0235] Optionally, request 3 may further include sending status information (or status bits) corresponding to SMS 1, which indicates whether SMS 1 was sent successfully. For example, the sending status information can be 0 or 1, where 0 indicates successful sending and 1 indicates sending failure.

[0236] S619. In response to request 3, the communication provider saves SMS 1 to the SMS database.

[0237] In some embodiments, the communication provider can save SMS 1 to the SMS database, such as saving the SMS record corresponding to SMS 1 to the data table corresponding to the parallel space in the SMS database (e.g., the threads_para_space table). Additionally, the communication provider can save SMS messages sent from the main space to the data table corresponding to the main space in the SMS database (the threads data table).

[0238] In other embodiments, the aforementioned SMS database may include SMS database 1 corresponding to the parallel space and SMS database 2 corresponding to the main space. The communication provider can save SMS messages 1 sent in the parallel space to SMS database 1. Correspondingly, the communication provider can save SMS messages sent in the main space to SMS database 2.

[0239] Optionally, request 3 includes tag 1, which is used to determine the user space corresponding to SMS 1, i.e., the user space to which SMS 1 belongs, thereby determining whether to save SMS 1 to the data table (or SMS database 1) corresponding to the parallel space, or to the data table (or SMS database 2) corresponding to the main space. The following will describe two possible implementation methods by which communication providers determine the user space corresponding to SMS 1 using tag 1.

[0240] In one possible implementation, the value of tag1 can determine which user space's data table or SMS database to save SMS 1 to. For example, if tag1 carried in the above request 3 is the first character, it indicates that the above request 3 is a request sent from a parallel space, that is, it indicates the parallel space corresponding to SMS 1. Then, the communication provider can save SMS 1 to the data table or SMS database 1 corresponding to the parallel space.

[0241] If the tag1 carried in the above request 3 is the second character, it indicates that the above request 3 is a request for the main space, that is, it indicates that the main space corresponding to SMS 1, the communication provider can save SMS 1 to the data table or SMS database 2 corresponding to the main space.

[0242] The tag1 parameter and its value can be set according to requirements. For example, tag1 can be set to is_para_space, and its value can be either the first character (e.g., true) or the second character (e.g., false). When is_para_space = true, it indicates that SMS 1 corresponds to the parallel space. When is_para_space = false, it indicates that SMS 1 corresponds to the main space.

[0243] In another possible implementation, the parallel space corresponding to SMS 1 can be determined by judging whether request 3 carries tag 1. For example, if request 3 includes tag 1, the communication provider can save SMS 1 to the data table or SMS database 1 corresponding to the parallel space. If request 3 does not include tag 1, the communication provider can save SMS 1 to the data table or SMS database 2 corresponding to the main space.

[0244] Of course, the communication provider can also determine the user space corresponding to SMS 1 through other means, such as by including a user space identifier in request 3 above. If the user space identifier is the identifier of the primary space, SMS 1 is determined to correspond to the primary space. If the user space identifier is the identifier of a parallel space, SMS 1 is determined to correspond to the parallel space.

[0245] In some embodiments, even when there is no direct correspondence between the user space and the SIM card, it may still be necessary to save SMS messages corresponding to the parallel space. For example, in response to a user's click on the "Do not set" option 43 shown in Figure 4(a), the electronic device disables the SIM card isolation function, unbinding the parallel space from the SIM card 2, thus eliminating the direct correspondence between the user space and the SIM card. When it is necessary to save an SMS message, the request sent by the parallel space to the communication provider to trigger saving the SMS message may also contain an identifier indicating the user space to which the SMS message belongs, such as tag1 mentioned above, thereby triggering the communication provider to save the SMS message to the data table or SMS database corresponding to that user space. The identifier of the user space to which the SMS message belongs can be determined according to a preset rule. For example, the preset rule might be that when the parallel space determines that the recipient's number belongs to a contact number corresponding to the parallel space, it determines that the identifier of the user space to which the SMS message belongs is the identifier of the parallel space. Another example is that the preset rule might be determined based on the priority of the user spaces; for instance, if the primary space has a higher priority than the parallel space, then the identifier of the user space to which the SMS message belongs is the identifier of the primary space. For example, the default rule means that the user space identifier is set by default. If a SIM card is not bound to the parallel space, the SMS messages will be saved to the data packets or SMS database corresponding to the main space by default.

[0246] S620. If the saving is successful, the communication provider returns a save success response message to the information application 1.

[0247] S621. In the event of a save failure, the communication provider returns a save failure response message to the information application 1.

[0248] S622. In response to the failure to save the response message, the information application 1 resends the above request 3 to the communication provider.

[0249] For example, the above-mentioned successful save response message can be a success message, and the above-mentioned failed save response message can be a fail message. After receiving the failed save response message, the messaging application 1 can resend the above-mentioned request 3 to the communication provider until the SMS 1 is successfully saved to the SMS database. Alternatively, generally speaking, the possibility of SMS saving failure is relatively small. Therefore, after the messaging application 1 sends request 2 to the communication provider to trigger the communication provider to save SMS 1 to the SMS database, the communication provider does not need to return a corresponding response message. That is to say, the above-mentioned steps S619-S621 are optional, thereby reducing resource consumption.

[0250] It is understood that the step numbers in this application do not represent the execution order of the steps. For example, S606-S612 and S613 above can be executed sequentially or simultaneously, and this application does not impose any restrictions on them.

[0251] In this embodiment, the SMS records in the parallel space include the SMS records corresponding to SIM card 2 after the parallel space is bound to SIM card 2 (that is, SMS messages received and sent by the electronic device using SIM card 2), but exclude the SMS records corresponding to SIM card 1 after the parallel space is bound to SIM card 2. Similarly, the SMS records in the main space include the SMS records corresponding to SIM card 1 after the parallel space is bound to SIM card 2, but exclude the SMS records corresponding to SIM card 2 after the parallel space is bound to SIM card 2.

[0252] In some embodiments, before enabling the SIM card isolation function, such as before binding SIM card 2 to the parallel space, if the parallel space does not contain messaging application 1 (in other words, messaging application 1 is installed in the parallel space only after binding SIM card 2), or although the parallel space has messaging application 1 installed, but no SMS records, then after binding SIM card 2, the SMS records in the parallel space can include not only the SMS records corresponding to SIM card 2 after binding the parallel space with SIM card 2, but also the SMS records corresponding to SIM card 2 before binding SIM card 2, thus achieving SMS migration. For example, the SMS record corresponding to "08:00" in the parallel space shown in Figure 11(b) above is an SMS sent by the electronic device through SIM card 2 before the parallel space was bound to SIM card 2. Correspondingly, the SMS records in the main space may no longer include SMS messages sent and received by the electronic device through SIM card 2 before binding SIM card 2, thereby migrating the SMS records corresponding to SIM card 2 to the parallel space, achieving SMS record isolation, and preventing the leakage of SMS records belonging to the parallel space. Of course, the SMS records in the main space can still include the SMS records corresponding to SIM card 2 before it was bound. In other words, the SMS records of the electronic device will not be migrated while the SIM card isolation function is turned off.

[0253] The migration process described above may include: after the parallel space is bound to SIM card 2, the main space or the parallel space may use the communication provider to migrate the SMS records corresponding to SIM card 2 whose sending or receiving time is before the binding time to the data table or SMS database 1 corresponding to the parallel space, so that the main space no longer displays the SMS records corresponding to SIM card 2, but only displays the SMS records corresponding to SIM card 1, thereby effectively protecting user privacy data.

[0254] Of course, the data table corresponding to the parallel space or the SMS database 1 corresponding to the parallel space may not include the SMS records migrated from the main space, but only include the SMS records corresponding to the SIM card 2 after binding. In other words, the storage location of the SMS records before binding remains unchanged.

[0255] In other embodiments, before enabling the SIM card isolation function, the parallel space contains the messaging application 1 and SMS records. These SMS records include those corresponding to SIM card 1 and SIM card 2. The SMS records in the parallel space are identical to those in the main space. Therefore, after enabling the SIM card isolation function, the SMS records in the parallel space may no longer include those corresponding to SIM card 1. Similarly, after enabling the SIM card isolation function, the SMS records in the main space may no longer include those corresponding to SIM card 2. Based on this, SMS record isolation is achieved.

[0256] Specifically, the aforementioned parallel space can migrate the SMS records corresponding to SIM card 2 before the SIM card isolation function is enabled to the data table corresponding to the parallel space in the SMS database, or to the SMS database 1 corresponding to the parallel space. This ensures that when the parallel space loads SMS records through the data table corresponding to the parallel space or the SMS database 1 corresponding to the parallel space after the SIM card isolation function is enabled, only the SMS records corresponding to SIM card 2 are loaded.

[0257] Of course, SMS records in the parallel or main user space prior to enabling the SIM card isolation function can remain unchanged to avoid user confusion about why the SMS records have changed. Furthermore, generally speaking, enabling the SIM card isolation function indicates that the user does not need to isolate the use of the SIM card; the user may want to use two SIM cards simultaneously in a user space to view the SMS records corresponding to those SIM cards. Therefore, after enabling the SIM card isolation function, the user space can still display the SMS records corresponding to the unbound SIM cards.

[0258] It should be noted that before enabling the SIM card isolation function, the SMS records of electronic devices can be stored in the data table corresponding to the main space of the SMS database, or in the SMS database corresponding to the main space. Alternatively, they can be stored in a data table within the SMS database that is different from both the data tables corresponding to the main space and the parallel spaces, or in an SMS database that is different from both the SMS databases corresponding to the main space and the parallel spaces.

[0259] The above example demonstrates in detail the process of an electronic device sending SMS messages using SIM card 2 corresponding to the parallel space while the parallel space is running in the foreground. Additionally, users may also send SMS messages using the messaging application (i.e., messaging application 2) in the main space. Correspondingly, while the main space is running in the foreground, the electronic device can also send SMS messages using SIM card 1 corresponding to the main space. The process of sending SMS messages using SIM card 1 corresponding to the main space is similar to the parallel space SMS sending process described above and will not be repeated here.

[0260] In this embodiment, users can set the SIM card corresponding to their user space according to their own usage needs or habits, so that the electronic device can manage the SIM cards corresponding to different user spaces in isolation. When a user sends a text message in any user space (such as user space 1), the electronic device can directly use the SIM card corresponding to user space 1 to send the text message without the user having to select a SIM card. This can effectively improve the efficiency of sending text messages and prevent users from sending text messages incorrectly due to not knowing or forgetting to select a SIM card. It meets the user's need to use only a specific SIM card for text messaging services in a specific user space, thereby improving user satisfaction. In addition, it also makes it impossible for users to perceive the text message records of SIM cards that do not correspond to user space 1, thus protecting the user's privacy.

[0261] Receive SMS:

[0262] In this embodiment, the main space can receive SMS messages whose recipient number (i.e., the recipient's number) is any SIM card number on the electronic device (or, in short, receive SMS messages from any SIM card). When the main space receives an SMS message from a SIM card, it determines the user space corresponding to that SIM card and saves the SMS message to the corresponding user space. This allows the corresponding user space to display the SMS message, while user spaces without a corresponding relationship to that SIM card do not display it. This achieves isolated management of SIM cards, meeting the user's need to display only SMS data from a specific SIM card in specific scenarios, effectively protecting privacy data, and satisfying the user's personalized communication needs. Specifically, the SMS receiving process may include steps S701-S711 as shown in Figure 13.

[0263] S701, Receive SMS message 2 sent by the sender.

[0264] S702, Telecom service sends SMS 2.

[0265] SMS 2 includes the sender's number, the recipient's SIM card ID (or target SIM card ID), and the SMS content.

[0266] For example, after receiving SMS 2 from an external device, the telecom service can send broadcast message 1, which includes SMS 2.

[0267] In some embodiments, after receiving SMS 2, the telecom service can block SMS 2 if it determines that the sender is a spam number, such as by adding it to the spam list. Accordingly, the telecom service would not need to perform the steps described below.

[0268] S703, Information Application 2 in the main space receives SMS messages 2.

[0269] For example, after the Telecom service broadcasts SMS 2, an application (including the messaging application 2) that has registered to listen to the Telecom service can receive the broadcast message 1, that is, receive SMS 2.

[0270] In some embodiments, since the operation of the parallel space depends on the main space, even if the electronic device only displays the interface of the parallel space and not the interface of the main space, the main space is still running. In other words, the main space of the electronic device is always running (either in the foreground or in the background) during the operation of the electronic device. Therefore, the electronic device can receive SMS messages from any SIM card through the main space, such as the main space's messaging application 2, thereby avoiding the situation where SMS messages cannot be received due to the parallel space not running.

[0271] S704, Information Application 2 sends request 4 to the card isolation monitoring module.

[0272] Request 4 is used to query the card isolation status; for details, please refer to the relevant introduction of Request 1 above.

[0273] S705, the card isolation monitoring module responds to the above request 4 and returns information 2 to information application 2, which includes the ID of the SIM card corresponding to the parallel space.

[0274] The description of information 2 can be found in the description of information 1 in Figure 7 above.

[0275] S706, Information Application 2 determines the user space associated with SMS 2 based on the recipient's SIM card ID and the SIM card ID corresponding to the parallel space.

[0276] In this embodiment, if the ID of the receiver's SIM card matches the ID of the SIM card corresponding to the parallel space, the information application 2 can determine that SMS 2 was received by the SIM card corresponding to the parallel space, and SMS 2 is associated with the parallel space (or alternatively described as SMS 2 belonging to the parallel space). If the ID of the receiver's SIM card does not match the ID of the SIM card corresponding to the parallel space, the information application 2 can determine that SMS 2 was received by the SIM card corresponding to the main space, and SMS 2 is associated with the main space.

[0277] In some embodiments, after the electronic device has enabled SIM card isolation, the card isolation monitoring module returns the ID of the SIM card corresponding to the parallel space. However, the electronic device may not have enabled SIM card isolation, in which case the SIM card ID returned by the card isolation monitoring module will not be the ID of SIM card 1 or SIM card 2, but a specific value. Accordingly, if the information application 2 determines that the SIM card ID is a specific value, it can determine that the SIM card isolation function is not enabled.

[0278] Optionally, if it is determined that the SIM card isolation function is not enabled, the messaging application 2 can determine the user space associated with the SMS 2 according to the preset rules described above.

[0279] In some embodiments, the information application 2 can also determine the user space associated with SMS 2 through other means. For example, after the SIM card is bound to the parallel space, the card isolation monitoring module can directly record the correspondence between each user space and the SIM card ID. The information application 2 can directly query the parallel space corresponding to the SIM card ID of the recipient of SMS 2 through the card isolation monitoring module, thereby obtaining the user space associated with SMS 2, without having to determine the user space associated with SMS 2 by comparing whether the recipient's SIM card ID is consistent with the SIM card ID corresponding to the parallel space.

[0280] S707, Information Application 2 sends Request 5 to the communication provider. Request 5 is used to trigger the saving of SMS 2 to the data table corresponding to the user space associated with SMS 2 in the SMS database.

[0281] S708. In response to request 5, the communication provider saves SMS 2 to the data table corresponding to the user space associated with SMS 2 in the SMS database.

[0282] In some embodiments, if the saving is successful, the communication provider returns a save success response message to the messaging application 2. If the saving fails, the communication provider returns a save failure response message to the messaging application 2, triggering the messaging application 2 to resend the aforementioned request 5 to the communication provider.

[0283] It should be noted that the data table corresponding to the user space mentioned above is only one possible implementation of the storage location corresponding to the user space. This storage location can also be other locations, such as the SMS database corresponding to the user space.

[0284] The process of information application 2 saving SMS 2 to the SMS database can be referred to as the process of information application 1 saving SMS 1 to the SMS database described above, and will not be repeated here.

[0285] After receiving SMS 2, if SMS 2 is associated with the main space, the user can view it through the main space. If SMS 2 is associated with a parallel space, the user can view it through the parallel space. The following will use the example of SMS 2 being associated with a parallel space to illustrate the viewing process.

[0286] S709, Receive the operation of information application 1.

[0287] S710. In response to an operation on the messaging application 1, the messaging application 1 is launched, and the corresponding SMS messages in the parallel space are read from the SMS database. Based on the SMS messages in the parallel space, the SMS interface 3 is displayed, which includes an SMS list. If the user space associated with SMS 2 is a parallel space, the SMS list includes the SMS entries corresponding to SMS 2.

[0288] S711. In response to a click operation on the SMS entry corresponding to SMS 2, the messaging application 1 displays the SMS interface 3, which displays SMS 2.

[0289] For example, during startup, the messaging application 1 can read SMS messages corresponding to the parallel space from the data table corresponding to the parallel space in the SMS database or from the SMS database 1 corresponding to the parallel space. This SMS data may include SMS messages received or sent based on the SIM card corresponding to the parallel space. Then, the messaging application 1 can display an SMS list (or alternatively, an SMS list consisting of SMS messages corresponding to the parallel space), allowing the user to see the SMS information corresponding to the SIM card in the parallel space. Furthermore, the user can select an SMS item to view the specific information of the SMS message, i.e., view the SMS history.

[0290] Taking the simultaneous operation of a parallel space and a main space on the foreground of an electronic device as an example, in response to a click on the icon of the information application 1 on the desktop of the parallel space shown in the left part of Figure 14(a), the electronic device launches the information application 1. After launch, the information application 1 displays the initial SMS interface (i.e., SMS interface 3) shown in the left part of Figure 14(b). The SMS interface 3 displays an SMS list, which can include entries of SMS messages corresponding to the SIM card 2 in the parallel space, such as SMS entry 80 corresponding to received SMS 2. Later, when the user wants to view the specific content of SMS 2, the user can click on SMS entry 80 corresponding to SMS 2, and the electronic device displays an interface including SMS 2, allowing the user to view the specific content of SMS 2. Furthermore, by comparing the SMS list displayed in the parallel space shown on the left and the SMS list displayed in the main space shown on the right in Figure 14(b), the SMS list displayed in the parallel space includes SMS entry 80 corresponding to SMS 2, but the SMS list displayed in the main space does not include SMS entry 80 corresponding to SMS 2. This achieves isolation of SMS messages corresponding to different SIM cards, so that when only the main space is running in the foreground, the user cannot view SMS 2 through the main space.

[0291] In this embodiment, after receiving SMS 2 sent by a user, the electronic device can determine the user space associated with SMS 2 based on the SIM card ID of the recipient of SMS 2, and then save SMS 2 to the storage location corresponding to the user space associated with SMS 2, such as the data table corresponding to the user space in the SMS database, or the SMS database corresponding to the user space. This allows the user space to display SMS 2, while another user space cannot display SMS 2, thus achieving isolated management of SMS reception by different SIM cards, protecting privacy data, and meeting the user's need to receive SMS only with specific SIM cards in specific scenarios.

[0292] It is understandable that the above S709-S711 only describes one possible process for displaying SMS 2 in the parallel space; SMS 2 may also be displayed in other ways. For example, if the sender of SMS 2 is "Xiaoming," and the parallel space receives SMS 2 while displaying an interface containing SMS records including "Xiaoming," and the recipient's number for SMS 2 is the SIM card number corresponding to the parallel space, then the parallel space can directly display SMS 2 on the interface. Alternatively, SMS 2 may also be associated with the main space, allowing the user to view SMS 2 through the main space, a process similar to the above-described process of viewing SMS 2 through the parallel space.

[0293] The above describes the process of a user viewing SMS 2 after it has been received. After receiving SMS 2, the electronic device can also send SMS notifications. The following section will further explain how electronic devices can send SMS notifications, focusing on the section on hiding SMS notifications.

[0294] Hide SMS notifications:

[0295] While the SIM card isolation function is enabled, users may want their electronic devices to stop pushing SMS notifications related to the parallel space after it is disabled. This would prevent frequent SMS notifications from interfering with the user's use of the main space and would also prevent the leakage of SMS messages associated with the parallel space, thus protecting user privacy. Based on this, after confirming that SMS 2 is associated with the user space, the electronic device can determine whether to display the notification message corresponding to SMS 2 based on the usage of that user space, thereby determining whether to send an SMS notification reminder. The process of determining whether to display the notification message will be further explained below with reference to Figure 15.

[0296] S801. When the SMS message 2 received by the aforementioned electronic device is associated with the parallel space, the information application 2 sends a request 6 to the card isolation monitoring module. Request 6 is used to query the status of the information hiding function.

[0297] The status indicator for the information hiding function shows whether it is enabled or disabled, including an enabled state and a disabled state. An enabled state means that if a message belonging to the parallel space is received and the parallel space is not in use, no message notification will be sent. A disabled state means that if a message belonging to the parallel space is received, a message notification will be sent regardless of whether the parallel space is in use. The status of the information hiding function can be set using the switch control 45 corresponding to the information hiding function shown in Figure 4(b) or (c), as described above.

[0298] S802, the card isolation monitoring module sends the status information of the hidden function to the information application 2.

[0299] For example, the card isolation monitoring module can return status bit 1 to the information application 2, which indicates the status of the hiding function. Status bit 1 can be either 0 or 1. 0 indicates the hiding function is enabled, and 1 indicates it is disabled.

[0300] S803, Information Application 2 sends Request 7 to the UMS service. Request 7 is used to query the status of the parallel space.

[0301] Request 7 can carry the identifier of the parallel space, such as userid. The status of the parallel space can include a used status (or open status) and an unused status (or closed status).

[0302] In some embodiments, users can close the parallel space by using the exit control shown in Figure 1D(c) or the destroy parallel space control shown in Figure 1F, which puts the parallel space into an unused state. Alternatively, the parallel space can be switched to background operation by other means, such as the swipe-up gesture described above.

[0303] The S804 and UMS services send parallel space status information to the card isolation listening module.

[0304] For example, the UMS service can return status bit 2 to the information application 2, which indicates the status of the parallel space. Status bit 2 can be either 0 or 1. 0 indicates the parallel space is in use, and 1 indicates it is not in use.

[0305] S805, Message application 2 sends request 8 to Contact application 1 in the parallel space. Request 8 includes the sender's number of SMS 2.

[0306] In this embodiment of the application, since SMS 2 (or the second SMS) is associated with the parallel space, it is necessary to query the contact information of the sender number of SMS 2 from the parallel space. Therefore, the information application 2 can send a request 8 to the contact application 1 in the parallel space to query whether the sender is a contact in the parallel space.

[0307] S806. In response to request 8, contact application 1 queries contact database 1 for the name of contact 2 corresponding to the sender number of SMS 2.

[0308] S807, Contacts application 1 sends the name of contact 2 to messaging application 2.

[0309] S808. When the parallel space is in use, the information application 2 sends a request 9 to the notification center.

[0310] Request 9 includes the names of SMS 2 and Contact 2. For example, Request 9 may include one or more of the SMS content of SMS 2, the name of Contact 2, or the sender's number.

[0311] In this embodiment, when the parallel space is in use, it indicates that the user is currently using the parallel space. Therefore, regardless of whether the information hiding function is enabled, SMS notifications can be sent normally. The information application 2 can directly send request 9 to the notification center to trigger the notification center to generate the corresponding notification message, so that the user can be informed of SMS 2 in a timely manner.

[0312] In some embodiments, the contact database 1 may not contain a contact whose number is the sender's number, meaning the name of contact 2 corresponding to the sender's number was not found. In this case, contact application 1 can return the sender's number (or second number) or other content, such as a null value, to indicate that no contact exists whose number is the sender's number. Accordingly, the above request 9 also does not include the name of contact 2.

[0313] S809. In response to request 9, the notification center displays the notification message corresponding to SMS 2.

[0314] For example, the notification message may include object 1 (icon 91 in notification message 90 shown in Figure 16A or icon 93 in notification message 92 shown in Figure 16B). Object 1 (or the first object) indicates that the notification message belongs to the parallel space, so that the user can intuitively know that SMS 2 has been received in the parallel space. This object 1 can be set according to needs, and can be the icon (or the first icon) shown in Figure 16A or Figure 16B, or text, as long as it can indicate that the notification message belongs to the parallel space.

[0315] Furthermore, the display position of the notification message mentioned above is merely an example; it can be displayed not only at the top of the current screen, but also on the left, right, or bottom, and this application does not limit it. Additionally, the notification message can be displayed not only on the screen but also in the status notification bar.

[0316] In some embodiments, request 9 may carry a flag 2, allowing the notification center to determine whether to generate a notification message for parallel space based on flag 2. Optionally, flag 2 may be isParallelSpaceNotify. In one case, the notification center can determine whether to generate a notification message for parallel space (or describe it as a notification message associated with parallel space) based on whether request 9 carries isParallelSpaceNotify. If request 9 carries isParallelSpaceNotify, it is determined that a parallel space SMS notification message will be generated, and correspondingly, the notification message corresponding to SMS 2 may include object 1. Otherwise, the notification message corresponding to SMS 2 may not include object 1.

[0317] In another scenario, the notification center can determine whether to generate a parallel space notification message based on the value of `isParallelSpaceNotify` carried in request 9. If the value of `isParallelSpaceNotify` in request 9 is true, a parallel space SMS notification message will be generated, and correspondingly, the notification message for SMS 2 mentioned above can include object 1. Otherwise, the notification message for SMS 2 mentioned above may not include object 1.

[0318] Alternatively, the aforementioned marker 2 could be an identifier for the user space. If SMS 2 is associated with a parallel space, then request 9 would carry the identifier of the parallel space.

[0319] In some embodiments, to protect privacy, the notification message may not include the specific content of SMS 2, as shown in notification message 90 in Figure 16A above. Alternatively, the notification message may include the specific content of SMS 2 and the name of contact 2, as shown in notification message 92 in Figure 16B, to allow the user to quickly learn about the status of SMS 2. In summary, the notification message may include one or more of the following: the content of SMS 2, the name of contact 2, and the sender's number; or, the notification message may only include a preset notification message (such as "1 notification" in the notification message shown in Figure 16A above).

[0320] In some embodiments, the notification message may not include object 1. For example, when the parallel space is in use, the notification message corresponding to SMS 2 may also not include object 1.

[0321] S810. When the parallel space is in an unused state and the information hiding function is enabled, the Contacts application 1 does not send a request 9 to the notification center.

[0322] In this embodiment, when the parallel space is in an unused state and the information hiding function is enabled, it indicates that during the main space's operation in the foreground, if an SMS message is sent to the SIM card bound to the parallel space, the electronic device can choose not to send an SMS notification. This avoids interference from SMS notifications from the SIM card bound to the parallel space, preventing user privacy leaks and protecting user privacy. Specifically, during the main space's display, if the electronic device receives SMS message 2 from SIM card 2 bound to the parallel space, the electronic device will not display the notification message corresponding to SMS message 2. This ensures that the user is unaware that the electronic device received SMS message 2 from SIM card 2 while using the main space, preventing interference from SMS message 2 and preventing the leakage of SMS message 2's content, thus achieving isolated management of the SIM card.

[0323] In addition, received text messages are saved in the parallel space, allowing users to view them at appropriate times as needed, thus preventing the loss of text message 2. Specifically, after switching from the main space to the parallel space, users can view the received text message 2 through the information application 2 in the parallel space.

[0324] In some embodiments, even when the parallel space is unused and the information hiding function is enabled, the Contacts application 1 can still send request 9 to the notification center to trigger the notification center to display the notification message corresponding to SMS 2. However, this notification message may only include preset prompt information, or it may not include the first information, such as the name of Contact 2 mentioned above. For details, please refer to the process of displaying a notification message when the parallel space is unused and the information hiding function is disabled, as described below.

[0325] In some embodiments, when the parallel space is not in use, the electronic device can directly hide the notification message corresponding to SMS 2, regardless of whether the information hiding function is enabled. Alternatively, the displayed notification message may only include preset prompts, or the notification message may not include the name of the aforementioned contact 2, etc.

[0326] S811. When the parallel space is in an unused state and the information hiding function is turned off, the messaging application 2 sends a request 9 to the notification center. Request 9 includes SMS 2.

[0327] For example, request 9 in S811 may include the SMS content of SMS 2 and / or the sender's number.

[0328] In this embodiment, when the parallel space is unused and the information hiding function is disabled, it indicates that during the main space's operation in the foreground of the electronic device, if there are SMS messages sent to the SIM card bound to the parallel space, and the user still wants the electronic device to display the SMS message status received by the SIM card bound to the parallel space, the electronic device can continue to send SMS notifications to ensure the user is promptly informed of the SMS message reception status, thus meeting different user needs. However, to protect user privacy, the messaging application does not send the contact information of the sender of SMS messages received by the SIM card bound to the parallel space (such as SMS message 2 mentioned above) to the notification center.

[0329] Understandably, when the parallel space is not in use, i.e., when the parallel space is not running in the foreground or background, the main space cannot query data in the parallel space, such as the contact data mentioned above. Correspondingly, the main space does not need to send the contact information of the sender of SMS 2 to the notification center. Since Message Application 2 does not need to send the contact information of the sender of SMS 2 to the notification center, Message Application 2 also does not need to query contact information from the parallel space; therefore, steps S805-S807 are optional.

[0330] S812, In response to request 9, the notification center displays the notification message corresponding to SMS 2.

[0331] The notification message corresponding to SMS 2 may only include a preset prompt (refer to "1 notification" in the notification message shown in Figure 16A above). Alternatively, the notification message may include the specific content of SMS 2, but not the first information, such as the name of contact 2 mentioned above, thereby protecting user privacy while providing SMS notification reminders and preventing the leakage of content in parallel spaces. Optionally, the first information may also include other information, such as the sender's number.

[0332] S812 can refer to the relevant content of S809 mentioned above.

[0333] In some embodiments, in response to request 9, the notification center displays the notification message corresponding to SMS 2 on the main space interface currently displayed on the electronic device. When a user wants to view SMS 2, the user can trigger the electronic device to open a parallel space. In response to the user's operation of opening the parallel space, the electronic device switches the parallel space to the foreground display, such as displaying the desktop of the parallel space. The icon of the aforementioned information application 1 is present on this desktop. In response to the user's click operation on the icon of the parallel space, the electronic device displays a list of SMS messages, which may include the entry corresponding to SMS 2. Alternatively, it may be described as the electronic device displaying an interface including SMS 2 in response to the user's click operation on the icon of the parallel space.

[0334] In some embodiments, in response to request 9, the notification center displays the notification message corresponding to SMS 2 on the interface of the main space currently displayed on the electronic device. When the user wants to view SMS 2, the user can click on the notification message of SMS 2. If SMS 2 belongs to a parallel space, the notification center can trigger the electronic device to switch the parallel space to the foreground display to show the SMS interface of application 1 containing SMS 2, realizing automatic jump from the main space to the parallel space, thereby enabling quick viewing of SMS 2.

[0335] For example, when the parallel space is not enabled, the notification center can directly send a request carrying the sender's number to the messaging application 1 in the parallel space. In response to this request, the parallel space displays a text message interface including text message 2, enabling quick viewing of text message 2. Alternatively, when the parallel space is not enabled, the notification center can first trigger the electronic device to run the parallel space, and then send a request carrying the sender's number to the messaging application 1 in the parallel space to trigger the display of a text message interface including text message 2.

[0336] Optionally, authentication is required before switching from the main space to the parallel space to ensure security.

[0337] For example, when a user clicks on notification message 94 displayed in the main space as shown in Figure 17(a), the electronic device can display the authentication interface as shown in Figure 17(b). After successful authentication, the electronic device displays the interface 95 of information application 1 in the parallel space as shown in Figure 17(c). This interface 95 includes SMS records 96, which can be SMS 2.

[0338] In some embodiments, after receiving SMS 2, the unread flag of messaging application 1 can also be updated. For example, if the unread flag is a number, the number can be incremented by 1. If the parallel space is in an unused state, messaging application 2 can update flag 3, such as incrementing flag 3 by 1. Flag 3 indicates the number of SMS messages associated with the parallel space received while the parallel space was not active. Then, when the parallel space is in use, messaging application 1 in the parallel space can read flag 3 and update the unread flag of messaging application 1's icon. Referring to the "+1" on messaging application 1 shown in Figure 16A or Figure 16B, it indicates that there is an unread SMS message.

[0339] It should be noted that the aforementioned display of the unread mark is only one possible implementation of the electronic device displaying a first notification message indicating the presence of a text message for SIM card 2 after switching the parallel space to the foreground. Other implementations are also possible. For example, while displaying the main system interface (or second interface), upon receiving text message 2 associated with the subsystem, if the subsystem is not enabled and the message hiding function is enabled, the sender's number of text message 2 is not displayed. Subsequently, in response to the user's input on the second interface (which can be considered an example of a second operation), the electronic device displays the subsystem's desktop (which can be considered an example of a fourth interface) and displays the first notification message on the desktop, indicating that the electronic device received a text message associated with the subsystem while the subsystem was not enabled. Optionally, the second operation can be an operation on the subsystem's icon on the main system's desktop, a gesture operation, a voice operation, or an operation on the access controls provided by the main system's settings application, etc.

[0340] In some embodiments, after receiving the above-mentioned SMS 2, if the Parallel Space is running in the background, indicating that the user is not currently using the Parallel Space in the foreground, the electronic device may not display the notification message corresponding to SMS 2. The specific process is similar to the process described above of the electronic device determining whether to display the notification message corresponding to SMS 2 when the Parallel Space is not in use.

[0341] The above describes the scenario where received SMS 2 is associated with a parallel space. However, there's also the possibility that SMS 2 might not be associated with a parallel space, but rather with the main space. The following section will describe the process of an electronic device displaying the notification message corresponding to SMS 2 when the user space associated with SMS 2 is the main space.

[0342] S813. When the SMS message 2 received by the aforementioned electronic device is associated with the main space, the messaging application 2 sends a request 10 to the contact application 2 in the parallel space. The request 10 includes the sender's number of the SMS message 2.

[0343] S814. In response to request 10, contact application 2 queries contact database 2 for the name of contact 3 corresponding to the sender number of SMS 2.

[0344] S815, Contacts application 2 sends the name of contact 3 to messaging application 2.

[0345] The process of querying the contact person corresponding to the sender number of SMS 2, as described in S813-S815, can be referred to the relevant process in S805-S808 above, and will not be repeated here.

[0346] S816, Information Application 2 sends Request 11 to Notification Center. Request 11 includes the name of Contact 3 and SMS 2.

[0347] S817 In response to request 11, the notification center displays the notification message corresponding to SMS 2.

[0348] S816-S817 can refer to the process of displaying notification messages described in S808-S809 above. However, it is understandable that when SMS 2 belongs to the main space, displaying the notification message corresponding to SMS 2 does not require carrying an object indicating that SMS 2 belongs to the main space.

[0349] In some embodiments, the process of displaying the notification message when SMS 2 is associated with the main space, as described in S813-S817 above, can be performed while the main space is running in the foreground. Running the main space in the foreground includes the electronic device displaying only the interface of the main space, and / or the electronic device simultaneously displaying the interface of the main space and the interface of the parallel space, as shown in Figure 1A above. In other words, when the main space is running in the background, the electronic device may not display the notification message corresponding to SMS 2.

[0350] In addition, when the main space is running in the background, it indicates that the electronic device only displays the interface of the parallel space. In order to protect user privacy, the above request 11 may not include the name of contact 3. Accordingly, the above step of querying contact 3 is also an optional step.

[0351] In some embodiments, the notification message may be displayed as a pop-up window. While the main system is running in the foreground, if an SMS message associated with a subsystem is received, and the subsystem is active but not visible in the foreground (indicating the subsystem is running in the background), the electronic device may display a first pop-up window. This first pop-up window includes a notification message and a first icon, thereby reminding the user that an SMS message associated with the subsystem has been received. The notification message indicates the presence of new information. For example, the notification message may include one or more of the following: the SMS message, the sender's number of the SMS message, and contact information corresponding to the sender's number within the subsystem. Alternatively, the notification message may include a preset prompt message, such as "1 notification".

[0352] If an SMS message associated with the main system is received, and the subsystem is active but not visible in the foreground, the electronic device can display a second pop-up window. This second pop-up window includes a notification message but not the first icon, thus notifying the user of the SMS message associated with the main system. Similarly, the notification message may include one or more of the following: the SMS message, the sender's number, and the contact information corresponding to that sender's number within the subsystem. Alternatively, the notification message may include a preset prompt message, such as "1 notification".

[0353] It should be noted that, as shown in Figure 16A above, the notification message may not include the specific content of SMS 2. Therefore, the main space also needs to query the contact person corresponding to the sender of SMS 2. Thus, querying the contact person corresponding to the sender of SMS 2 is an optional step. Correspondingly, the request from Message Application 2 to the notification center may also not include the specific content of SMS 2.

[0354] In some embodiments, when SMS 2 is associated with the main space, the user can also trigger the electronic device to directly display an interface including SMS 2 by clicking on the displayed notification message. For example, in response to the user's click operation on the notification message corresponding to SMS 2, the notification center can send a request carrying the sender's number of SMS 2 to the messaging application 2 in the main space. Then, in response to the request, the messaging application 2 displays an SMS interface including SMS 2, enabling quick viewing of SMS 2.

[0355] In some embodiments, when SMS 2 belongs to the main space, regardless of whether the main space is running in the foreground or the background, the electronic device can directly update the unread mark on the icon of the messaging application 2.

[0356] In this embodiment, after receiving SMS 2 corresponding to SIM card 2, if the subsystem is in an unused state and the information hiding function is enabled, indicating that the user does not want to display notification messages about SMS 2 when the subsystem is not in use, the electronic device can stop displaying the notification message corresponding to SMS 2. This avoids frequently displaying unnecessary notification messages and prevents notification messages from interfering with the user's use of the main space. Furthermore, it prevents the leakage of user data in the parallel space and also prevents the leakage of SIM card 1, protecting user privacy.

[0357] It is understandable that after receiving SMS 2, the process of hiding the SMS notification described above is optional. That is, the electronic device can choose not to display the notification message corresponding to SMS 2 upon receiving it. Furthermore, the SMS sending process described above can also be optional; that is, the electronic device can choose not to use the SMS sending process described above to send the SMS, or the electronic device may not support sending SMS. Similarly, the SMS receiving process described above can also be optional; that is, the electronic device can choose not to use the SMS receiving process described above to process the received SMS, or the electronic device may not support receiving SMS.

[0358] In addition, the above example of displaying the application interface by manipulating the application icon is just one example. Users can also trigger the electronic device to display the interface they need through other operations, such as gestures and voice.

[0359] It should be noted that before the parallel space is bound to SIM card 2, if the main space receives SMS message 3 (or the first SMS message) from SIM card 2, it can display the notification message of SMS message 3 without needing to determine whether the parallel space is enabled or whether the message hiding function is enabled. The sender's number of SMS message 3 from SIM card 2 can be used as the first number, and the notification message of SMS message 3 can be used as an example of the first message from the first number.

[0360] The operations performed by the modules or applications described above are merely examples; these operations could also be performed by other modules or applications, and this application does not impose any restrictions on the entity performing the operation. Furthermore, the operations performed by the aforementioned modules or applications are actually executed within the user space to which the modules or applications belong. For example, the information application 1 querying contacts through the contact application 1 is a direct query of contacts within a parallel space. However, in general, all of the above operations are performed by the electronic device.

[0361] In some embodiments, the "security watermark" shown in the accompanying drawings (Figure 1A) is merely for the purpose of distinguishing the interface between the parallel space and the main space. In practical applications, the interface of the parallel space may or may not have a "security watermark" or similar indicative information; this application does not impose any restrictions on this.

[0362] In some embodiments, the above describes the scheme of this application with a parallel space associated with SIM card 2 and a main space associated with SIM card 1. The parallel space can also be associated with SIM card 1 and the main space with SIM card 2. In other words, the parallel space (i.e., the subsystem) can be associated with the first SIM card of the electronic device, and the main space can be associated with the second SIM card of the electronic device. The first SIM card and the second SIM card are different; the first SIM card is SIM card 1, and the second SIM card is SIM card 2; or, the first SIM card is SIM card 2, and the second SIM card is SIM card 1.

[0363] The above primarily describes the solutions provided by the embodiments of this application from a methodological perspective. It is understood that, in order to achieve the above functions, the electronic device includes hardware structures and / or software modules corresponding to the execution of each function. Based on the units and algorithm steps of the various examples described in the embodiments disclosed in this application, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by a computer driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solutions of the embodiments of this application.

[0364] This application provides embodiments for dividing an electronic device into functional modules based on the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into a single processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the unit division in this application embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used.

[0365] Figure 18 shows a schematic diagram of an electronic device provided in an embodiment of this application. This electronic device 1800 can be used to implement the methods performed by the electronic devices described in the above method embodiments. For example, the electronic device 1800 may include a processing unit 1801, a communication unit 1802, and a display unit 1803. The processing unit 1801 is used to support the electronic device 1800 in performing the processing functions of the electronic device described in any one of Figures 1A to 17. The communication unit 1802 is used to support the electronic device 1800 in performing the communication functions of the electronic device described in any one of Figures 1A to 17. The display unit 1803 is used to support the electronic device 1800 in performing the display functions of the electronic device described in any one of Figures 1A to 17.

[0366] Optionally, the electronic device 1800 shown in FIG18 may further include a storage unit (not shown in FIG18) storing a program or instructions. When the processing unit 1801 executes the program or instructions, the electronic device 1800 shown in FIG18 can perform the method described in the above-described method embodiments.

[0367] The technical effects of the electronic device 1800 shown in Figure 18 can be referred to the technical effects described in the above method embodiments, and will not be repeated here. The processing unit 1801 involved in the electronic device 1800 shown in Figure 18 can be implemented by a processor or processor-related circuit components, and can be a processor or processing module. The communication unit 1802 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver module. The display unit 1803 can be implemented by display screen-related components.

[0368] This application also provides a chip system, as shown in FIG19, which includes at least one processor 1901 and at least one interface circuit 1902. The processor 1901 and the interface circuit 1902 are interconnected via lines. For example, the interface circuit 1902 can be used to receive signals from other devices. As another example, the interface circuit 1902 can be used to send signals to other devices (e.g., the processor 1901). Exemplarily, the interface circuit 1902 can read instructions stored in a memory and send those instructions to the processor 1901. When the instructions are executed by the processor 1901, the electronic device can perform the various steps performed by the electronic device in the above embodiments. Of course, the chip system may also include other discrete devices, and this application does not specifically limit this.

[0369] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0370] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application does not specifically limit the type of memory or the arrangement of the memory and processor.

[0371] For example, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0372] It should be understood that each step in the above method embodiments can be completed by integrated logic circuits in the processor hardware or by instructions in software form. The method steps disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0373] This application also provides a computer-readable storage medium storing computer instructions that, when executed on an electronic device, cause the electronic device to perform the methods described in the above-described method embodiments.

[0374] This application provides a computer program product, which includes a computer program or instructions that, when run on a computer, cause the computer to perform the methods described in the above-described method embodiments.

[0375] In addition, this application also provides an apparatus, which may specifically be a chip, component or module. The apparatus may include a connected processor and a memory. The memory is used to store computer execution instructions. When the apparatus is running, the processor can execute the computer execution instructions stored in the memory to cause the apparatus to perform the methods in the above-described method embodiments.

[0376] In this embodiment, the electronic device, computer-readable storage medium, computer program product or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0377] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0378] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The embodiments can be combined with or referenced to each other without conflict. The apparatus embodiments described above are merely illustrative; for example, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0379] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0380] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0381] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0382] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. An information hiding method, characterized in that, Applied to electronic devices, the electronic devices including a first SIM card and a second SIM card; The method includes: During the display of the first interface of the main system, a first SMS message is received from the first number to the first SIM card; Display the first information of the first number; In response to a first user input, the subsystem is associated with the first SIM card; During the display of the second interface of the main system, a second SMS message is received from the second number to the first SIM card; When the subsystem is not enabled and the first hiding function is enabled, the first information of the second number is not displayed; The system receives a second user input and displays a third interface of the first information application of the subsystem; wherein the third interface includes the second SMS message.

2. The method according to claim 1, characterized in that, The method further includes: displaying a fourth interface of the subsystem before displaying a third interface of the first information application of the subsystem; wherein the fourth interface includes a first prompt message indicating that there is a text message for the first SIM card.

3. The method according to claim 2, characterized in that, The fourth interface is the desktop of the subsystem, and the first prompt information is the unread mark on the icon of the first information application in the desktop of the subsystem; the unread mark includes the number of SMS messages received by the electronic device from the first SIM card associated with the subsystem while the subsystem is not turned on.

4. The method according to any one of claims 1 to 3, characterized in that, The first information includes the contact information corresponding to the second number in the contact information within the subsystem.

5. The method according to any one of claims 1 to 4, characterized in that, The method further includes: after associating the subsystem with the first SIM card, displaying the fifth interface of the main system; When the subsystem is on and not visible in the foreground, a third SMS message is received to the first SIM card, and a first pop-up window is displayed. The first pop-up window includes a first notification message and a first icon. The first notification message indicates that there is new information, and the first icon indicates that there is new information in the subsystem. When the subsystem is on and not visible in the foreground, a fourth SMS message is received for the second SIM card, and a second pop-up window is displayed. The second pop-up window includes a second notification message, which indicates that new information has been received.

6. The method according to claim 5, characterized in that, The sender number of the third text message is the same as that of the fourth text message; The method further includes: after displaying the first pop-up window, in response to an operation on the first pop-up window, displaying a sixth interface of the first information application of the subsystem, the sixth interface including the third SMS message but not the fourth SMS message.

7. The method according to any one of claims 1 to 6, characterized in that, Prior to associating the subsystem with the first SIM card in response to a first user input operation, the method further includes: In response to a user's input to enable the subsystem in the main system, the subsystem is enabled after successful authentication. Before receiving a second SMS message from a second number to the first SIM card during the display of the second interface of the main system, the method further includes: In response to a third operation input by the user in the subsystem, the main system is switched to display.

8. The method according to any one of claims 1 to 7, characterized in that, The third interface includes a first sending control and the SMS records of the first SIM card, but does not include the SIM card option control and the SMS records of the second SIM card. The second text message belongs to the text message record of the first SIM card; The first sending control is used to trigger the sending of a text message using the first SIM card; The method further includes: Before associating the subsystem with the first SIM card in response to the first operation of user input, a seventh interface of the second information application in the main system is displayed in response to the fourth operation of user input; wherein, the seventh interface includes a SIM card option control and a second sending control, SMS records of the first SIM card and SMS records of the second SIM card; the SIM card option control is used to trigger switching of the SIM card for sending SMS messages.

9. The method according to claim 8, characterized in that, After the subsystem is associated with the first SIM card, the SMS records of the first SIM card are stored in a first storage location, and the SMS records of the second SIM card are stored in a second storage location; wherein the second storage location is different from the first storage location.

10. The method according to claim 9, characterized in that, The first storage location is a first data table in the SMS database of the electronic device, and the second storage location is a second data table in the SMS database; the first data table and the second data table are different. Alternatively, the first storage location may be a second SMS database in the electronic device, and the second storage location may be a first SMS database in the electronic device, wherein the second SMS database is different from the first SMS database.

11. The method according to any one of claims 8 to 10, characterized in that, The third interface includes a first contact control, which is used to trigger the display of contact information within the subsystem; The seventh interface includes a second contact control, which is used to trigger the display of contact information in the main system; The contact information in the subsystem is different from the contact information in the main system.

12. The method according to claim 11, characterized in that, The contact information in the subsystem includes the first number and the first contact name corresponding to the first number, and the contact information in the main system includes the first number and the second contact name corresponding to the first number, wherein the first contact name and the second contact name are different; The contact information in the subsystem includes the second number, while the contact information in the main system does not include the second number.

13. An electronic device, characterized in that, The electronic device includes a memory, a display screen, and one or more processors; the memory, the display screen, and the processors are coupled; the memory is used to store a computer program, the computer program including computer instructions; the display screen is used to display an image generated by the processor; when the processor executes the computer instructions, it causes the electronic device to perform the method as described in any one of claims 1 to 12.

14. A computer-readable storage medium, characterized in that, Includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1 to 12.

15. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 12.

Images