Method and device for managing network connection, equipment and medium
By detecting and managing network connection events in electronic devices, presenting a prompt page and allowing or prohibiting network connections according to user interaction, the problem of being unable to dynamically manage network connections in the prior art is solved, and the security and privacy of the device are improved.
Patent Information
- Application Number
- CN202311606812.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-11-28
- Publication Date
- 2025-05-30
AI Technical Summary
The prior art is difficult to dynamically manage network connection events in electronic devices during user use, resulting in the inability to remind and decide whether to allow applications to connect to the network in real time, affecting the security and privacy of the device.
By detecting network connection events in electronic devices, presenting a prompt page and receiving user interactions, managing network connection events based on user interactions, allowing or prohibiting network connections.
It realizes real-time detection and management of network connection events during user use, improves the security and privacy of electronic devices, and ensures the security of user data.
Smart Images

Figure CN120075303A_ABST
Abstract
Description
Technical Field
[0001] Exemplary implementations of the present disclosure generally relate to network management, and in particular, to methods, apparatuses, devices, and computer-readable storage media for managing network connections in electronic devices. Background Art
[0002] With the development of computer hardware and software technologies, users increasingly value the security and privacy functions of electronic devices. Applications on an electronic device may access certain sensitive data and transmit this data via a network to other remote devices. At this time, it is desirable to be able to inform the user of the electronic device in advance of potential network connections and risks. Summary of the Invention
[0003] In a first aspect of the present disclosure, a method for managing a network connection is provided. In this method, in response to detecting a network connection event in an electronic device, a prompt page indicating the network connection event is presented. An interaction with respect to the prompt page is received. The network connection event is managed based on the interaction.
[0004] In a second aspect of the present disclosure, an apparatus for managing a network connection is provided. The apparatus includes: a presenting module configured to present a prompt page indicating a network connection event in response to detecting a network connection event in an electronic device; a receiving module configured to receive an interaction with respect to the prompt page; and a managing module configured to manage the network connection event based on the interaction.
[0005] In a third aspect of the present disclosure, an electronic device is provided. The electronic device includes: at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions when executed by the at least one processing unit causing the electronic device to execute the method according to the first aspect of the present disclosure.
[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, having stored thereon a computer program, the computer program when executed by a processor causing the processor to implement the method according to the first aspect of the present disclosure.
[0007] It should be understood that the content described in this content section is not intended to limit the key features or important features of the implementations of the present disclosure, nor is it used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. Brief Description of the Drawings
[0008] In the following, in conjunction with the drawings and with reference to the following detailed description, the above and other features, advantages, and aspects of the various implementations of the present disclosure will become more apparent. In the drawings, the same or similar reference numerals denote the same or similar elements, where:
[0009] Figure 1 shows a block diagram of an application environment according to an exemplary implementation of the present disclosure;
[0010] Figure 2 shows a block diagram for managing network connections according to some implementations of the present disclosure;
[0011] Figure 3 shows an architecture diagram for managing network connections according to some implementations of the present disclosure;
[0012] Figure 4 shows a block diagram of a prompt page according to some implementations of the present disclosure;
[0013] Figure 5 shows a block diagram of a prompt page according to some implementations of the present disclosure;
[0014] Figure 6 shows a block diagram of a settings page according to some implementations of the present disclosure;
[0015] Figure 7 shows a block diagram for managing network connections based on network settings according to some implementations of the present disclosure;
[0016] Figure 8 shows a flowchart of a method for managing network connections according to some implementations of the present disclosure;
[0017] Figure 9 shows a block diagram of a device for managing network connections according to some implementations of the present disclosure; and
[0018] Figure 10 shows a block diagram of a device capable of implementing multiple implementations of the present disclosure. Detailed Implementation Modes
[0019] The implementations of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some implementations of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the implementations set forth herein. On the contrary, these implementations are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and implementations of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.
[0020] In the description of the implementation of the present disclosure, the term "including" and its similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "an implementation" or "the implementation" should be understood as "at least one implementation". The term "some implementations" should be understood as "at least some implementations". There may also be other explicit and implicit definitions hereinafter. As used herein, the term "model" may represent the association relationship between various data. For example, the above-mentioned association relationship can be obtained based on various technical solutions that are currently known and / or will be developed in the future.
[0021] It can be understood that the data involved in the present technical solution (including but not limited to the data itself, the acquisition or use of the data) should comply with the requirements of the corresponding laws, regulations and related provisions.
[0022] It can be understood that before using the technical solutions disclosed in the embodiments of the present disclosure, the types, usage scopes, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained through appropriate means in accordance with relevant laws and regulations.
[0023] For example, when responding to receiving an active request from the user, a prompt message is sent to the user to clearly prompt the user that the operation requested by it will require the acquisition and use of the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, an application program, a server or a storage medium that performs the operations of the technical solutions of the present disclosure according to the prompt message.
[0024] As an optional but non-limiting implementation, the manner of sending a prompt message to the user in response to receiving an active request from the user can be, for example, in the form of a pop-up window, and the prompt message can be presented in text in the pop-up window. In addition, the pop-up window can also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.
[0025] It can be understood that the above process of notifying and obtaining the user's authorization is only illustrative and does not limit the implementation of the present disclosure, and other ways that meet the relevant laws and regulations can also be applied to the implementation of the present disclosure.
[0026] The term "in response to" used herein represents the state in which the corresponding event occurs or the condition is satisfied. It will be understood that the execution timing of the subsequent actions executed in response to the event or condition and the time when the event occurs or the condition is established are not necessarily strongly correlated. For example, in some cases, the subsequent actions can be executed immediately when the event occurs or the condition is established; while in other cases, the subsequent actions can be executed after a period of time after the event occurs or the condition is established.
[0027] Example environment
[0028] See Figure 1 Describe an application environment according to an example implementation of the present disclosure. The Figure 1 shows a block diagram 100 of an application environment according to an exemplary implementation of the present disclosure. As Figure 1 shown, there may be various types of electronic devices 110, 112, …, and 114, etc. Various types of applications may be installed in the electronic device. Some applications may access sensitive data in the electronic device 110 and transmit this data to other remote devices 120 via the network 130. It should be understood that the network connection permission of the application is an important permission in security management. Users increasingly value the security and privacy functions of electronic devices. In some scenarios, users need to know when an application triggers a network connection action and decide whether to allow the application to connect to the network, so as to ensure that sensitive information in the device is not leaked.
[0029] Currently, technical solutions for presetting network connection permissions for each application have been proposed. For example, various rule controls can be performed on the inflow and outflow of network data from the device. However, the rules at this time are preset and cannot be dynamically set at any time during user use. This results in the inability to perform real-time access reminders and decisions. At this time, it is desirable to manage network connection events in a more flexible and effective manner.
[0030] Summary of managing network connections
[0031] To at least partially address the deficiencies in the prior art, according to an exemplary implementation of the present disclosure, a method for managing network connections is proposed. For ease of description, only the electronic device 110 is used as an example to describe the technical solution according to an example implementation of the present disclosure. The network connection management method can be executed at the electronic device 110. See Figure 2 Describe an overview according to an exemplary implementation of the present disclosure. Figure 2 shows a block diagram 200 for managing network connections according to some implementations of the present disclosure.
[0032] As Figure 2As shown, network connection events in the electronic device 110 can be detected. Here, the network connection event 210 can include various types. For example, it can include a connection event initiated by the electronic device 110, or a connection event initiated by other devices for connecting to the electronic device 110. In the case where a network connection event is detected, a prompt page 220 for indicating the network connection event can be presented. For example, the prompt page 220 can prompt the user of the electronic device 110: "A network connection event is detected. Do you allow this event?" The user can interact with the prompt page 220 through the controls 230 and 232 to inform whether to allow the network connection event.
[0033] The electronic device 110 can receive the interaction 240 for the prompt page and manage the network connection event based on the interaction 240. Specifically, in the case where an interaction with the control 230 is detected, the network connection event can be allowed; and in the case where an interaction with the control 232 is detected, the network connection event can be prohibited. Using the exemplary implementation of the present disclosure, during the user's use of the electronic device 110, in the case where a network connection event is detected, the user can be notified of the event in real time and asked whether to allow it. In this way, the user can be reminded before the network connection is about to be triggered, so that the user can make a decision in advance.
[0034] Detailed process of managing network connections
[0035] A summary of an example implementation according to the present disclosure has been described. Hereinafter, more information about managing network connections will be referred to Figure 3 for description. Figure 3 FIG. shows a block diagram of an architecture 300 for managing network connections according to some implementations of the present disclosure. As Figure 3 shown, the architecture 300 can be implemented at the electronic device 110. Specifically, a network management tool 320 can be deployed in the user space of the electronic device 110. Generally speaking, at block 322, the network management tool 320 can obtain intercepted network connection events from the kernel space and then present a prompt page to the user. In this way, the user can be reminded before the network connection is about to be triggered, so that the user can make a decision in advance.
[0036] It should be understood that the network connection events in the present disclosure include at least any one of the following: a connection event (e.g., connect event) initiated by the electronic device 110 for connecting to a remote device, and an acceptance event (e.g., accept event) received by the electronic device 110 from a remote device. For the sake of convenience of description, hereinafter, only the connection event will be used as an example to describe the specific details of an example implementation according to the present disclosure, and the acceptance event can be processed in a similar manner.
[0037] Refer to Figure 3 Describe the general process of managing network connections. As shown in block 312, when application 310 needs to actively establish a network connection, it can create a socket object. For example, it can create a socket of a protocol type such as AF_INET. Further, at block 314, the connect function can be used to connect to an external service. It should be understood that the above only describes the process of managing network connections by taking the connection event as an example. Alternatively and / or additionally, for the passive acceptance event of electronic device 110, the accept function can be used to receive an external network connection.
[0038] Further, as shown by arrow 340, a socket system call 330 can be executed to connect to an external service. As shown by arrow 350, the call result will be intercepted at block 332. Subsequently, the intercepted network connection event (connect or accept event) will be provided to network management tool 320, and this network management tool 320 can provide a prompt page to the user (for example, Figure 2 the prompt page 220 shown) to ask the user whether to allow this network connection event. Subsequently, as shown by arrow 346, network management tool 320 can return the user's interaction result (that is, whether to allow the network connection event) to the kernel space. As shown by arrow 352, socket system call 330 can determine whether to allow the network connection event of application 310 based on this interaction result. A judgment can be made in the socket system call. If the user selects "Allow", the subsequent connect or accept process will continue. If the user selects "Deny", a failure message will be directly returned to the networked application.
[0039] According to an example implementation of the present disclosure, network management tool 320 can receive network connection events intercepted by a security module in the electronic device. For example, the interception function can be implemented based on the Linux Security Module (LSM), which is a security framework standard under Linux and can provide a unified standard interface for different security modules. The network connection event can be intercepted based on the hook function provided by LSM. Using the example implementation of the present disclosure, it is not necessary to modify application 310, but the process of detecting network connection events and informing the user of such events can be achieved through network management tool 320. In this way, the security and privacy of electronic device 110 can be improved, thereby ensuring the security of user data.
[0040] According to an example implementation of the present disclosure, network management tool 320 can present as Figure 2The prompt page 220 shown. Interactions from the user with respect to the prompt page 220 can be received. In a case where it is determined that the received interaction indicates an allowed network connection event (e.g., the user presses the control 230), the network management tool 320 can enable the network interface in the electronic device to allow the network connection event. With an example implementation of the present disclosure, a network connection can be allowed only with user permission. In this way, the security of the electronic device 110 can be improved.
[0041] According to an example implementation of the present disclosure, in a case where it is determined that the received interaction indicates a non-allowed network connection event (e.g., the user presses the control 232), the network management tool 320 can disable the network interface in the electronic device 110 to prohibit the network connection event. With an example implementation of the present disclosure, the user is allowed to prohibit the network connection, thereby ensuring that various data at the electronic device 110 cannot be illegally accessed.
[0042] According to an example implementation of the present disclosure, the prompt page can further include more information. For example, the identity of the application associated with the network connection event can be provided, that is, the identity of the application installed in the electronic device that triggers the network connection event can be provided. See Figure 4 for more details, the Figure 4 block diagram 400 of a prompt page according to some implementations of the present disclosure is shown. As Figure 4 shown, assuming that the network management tool 320 detects that the application "APP1" is attempting to establish a network connection, the prompt page 410 can be provided.
[0043] Specifically, assuming that the user receives a prompt page regarding APP1 establishing a network connection during the use of APP2, the user can reject the request for APP1 to establish a network connection. Assuming that the user receives a prompt page regarding APP1 establishing a network connection during the use of APP1, the user can allow the request for APP1 to establish a network connection. With an example implementation of the present disclosure, it is convenient for the user to understand which application causes the current network connection event. In this way, more judgment bases can be provided to the user, thus facilitating the decision on whether to allow the network connection event.
[0044] According to an example implementation of the present disclosure, the prompt page can provide the user with more information to support the user in providing a more complex network connection management strategy. See Figure 5 for more details, the Figure 5 block diagram 500 of a prompt page according to some implementations of the present disclosure is shown. As Figure 5As shown, more controls for allowing or prohibiting network connections can be provided. Specifically, the management policy may include at least any one of the following: allowing this network connection, allowing all network connections of APP1, allowing network connections when APP1 is currently in use, rejecting this network connection, rejecting all network connections of APP1, rejecting the background network connections of APP1, and so on.
[0045] According to an example implementation of the present disclosure, in the case of determining that the interaction indicates an event of allowing all network connections for communicating with the application, the network interface in the electronic device can be enabled to allow all network connection events. Alternatively and / or additionally, in the case of determining that the interaction indicates not allowing all network connection events for communicating with the application, the network interface in the electronic device can be disabled to prohibit all network connection events. At this time, during subsequent use, when the application expects to establish a new network connection, a prompt message will not pop up again, thereby reducing the interference to the user's use and improving the user experience.
[0046] The user can interact with the prompt page 520 and then select the desired management policy. Suppose the user selects the control 530, then the network connection management tool will allow all network connections associated with APP1. In other words, the current network connection and all subsequent network connections (whether network connections actively initiated by APP1 or network connections expected to be passively received by APP1) are allowed. For another example, the user can select the control 532. At this time, the network connection management tool will allow each network connection when APP1 is in use and reject each network connection when APP1 runs in the background. In this way, the user is allowed to manage network connections in a manner more in line with their own expectations, thereby improving the convenience and security of using the electronic device 110.
[0047] According to an example implementation of the present disclosure, after the user has selected the desired management policy on the prompt page, the network connection can be established or prohibited according to the selected management policy. At this time, the status information of the network connection event can be provided to support the user to understand the current network connection status. Suppose the user allows the establishment of a network connection, then after the connection is successful, the user can be prompted: The network connection has been successfully established. Suppose the user does not allow the establishment of a network connection, then the user can be further prompted at the electronic device: You have prohibited APP1 from accessing the network, and the network connection has failed, and so on.
[0048] According to an example implementation of the present disclosure, the user is allowed to select whether to enable the above-described network connection management technical solution. Specifically, a setting control can be presented on the network settings page of the electronic device 110, and this setting control is used to set whether to allow the network management function to be enabled in the electronic device. The user can call this setting page to enable or disable the network management function. SeeFigure 6 Describe more details, the Figure 6 shows a block diagram 600 of a settings page according to some implementations of the present disclosure. Specifically, the settings page 610 may ask the user whether to allow access to the network management function. The user can interact with controls 620 and 622 to provide their customized information.
[0049] In the case of receiving the user's interaction with control 620, the interaction indicates that it is allowed to enable the network management function, and at this time, the method described above can be executed. Alternatively and / or additionally, in the case of receiving the user's interaction with control 622, the interaction indicates that it is not allowed to enable the network management function, and at this time, the network management function can be executed based on the network configuration of the electronic device 110. See Figure 7 Describe more details, the Figure 7 shows a block diagram 700 for managing network connections according to some implementations of the present disclosure.
[0050] As Figure 7 shown, at block 710, the user can modify the network access permissions of the electronic device 110 according to their own needs. For example, the user can set the permissions for a specific application. Specifically, it can be set to allow all network access, prohibit all network access, prohibit all network access when the application is used in the background, and so on. At block 712, the IP table (iptable) rules 714 of the electronic device 110 can be set according to the access permissions. During the execution of the application, as shown in block 720, the application can perform network access. As shown in block 722, the iptable rules can be consulted to determine whether to allow the network access. In the case of allowing access, at block 726, the relevant data packets of the application can be allowed to be routed to the specified destination; in the case of denying access, at block 724, the relevant data packets of the application can be discarded.
[0051] Using the example implementation of the present disclosure, the user is allowed to independently select whether to start the real-time network management function. In the case of not starting the real-time network management, it is possible to set in advance through the iptable to allow or deny a certain type of network access for a certain application. In this way, more flexibility can be provided for network control.
[0052] Using the exemplary implementation of the present disclosure, relevant system calls of the socket are intercepted using LSM or other means to obtain the network connection events of the application, thereby reminding the user that the application is connecting to the network in the city. In this way, after the application performs a network connection behavior, a pop-up window can be displayed to prompt the user that the application is attempting to connect to the network, allowing the user to choose to allow or deny. If the user chooses to allow, the application can connect to the network normally; if the user chooses to deny, the network connection operation of the application will fail. In this way, the network connection can be detected in real time and dynamically during the user's use of the electronic device, thereby improving the security of the electronic device.
[0053] Example process
[0054] Figure 8 A flowchart of a method 800 for managing network connections according to some implementations of the present disclosure is shown. At block 810, a network connection event in the electronic device is detected. If the event is detected, the method 800 proceeds to block 820. At block 820, a prompt page indicating the network connection event is presented. At block 830, an interaction with respect to the prompt page is received. At block 840, the network connection event is managed based on the interaction.
[0055] According to an example implementation of the present disclosure, managing the network connection event based on the interaction includes: in response to determining that the interaction indicates allowing the network connection event, enabling the network interface in the electronic device to allow the network connection event.
[0056] According to an example implementation of the present disclosure, managing the network connection event based on the interaction includes: in response to determining that the interaction indicates not allowing the network connection event, disabling the network interface in the electronic device to prohibit the network connection event.
[0057] According to an example implementation of the present disclosure, the prompt page further includes an identifier of an application associated with the network connection event, and the application is installed in the electronic device.
[0058] According to an example implementation of the present disclosure, managing the network connection event based on the interaction further includes at least any one of the following: in response to determining that the interaction indicates allowing all network connection events for communicating with the application, enabling the network interface in the electronic device to allow all network connection events; and in response to determining that the interaction indicates not allowing all network connection events for communicating with the application, disabling the network interface in the electronic device to prohibit all network connection events.
[0059] According to an example implementation of the present disclosure, detecting the network connection event includes: receiving a network connection event intercepted by a security module in the electronic device.
[0060] According to an example implementation of the present disclosure, the network connection event includes at least any one of the following: a connection event initiated by an electronic device to connect to a remote device, and an acceptance event received by the electronic device from the remote device.
[0061] According to an example implementation of the present disclosure, the method further includes: providing status information of the network connection event.
[0062] According to an example implementation of the present disclosure, the method further includes: presenting a setting control for setting whether to allow enabling a network management function in the electronic device; and in response to determining that the interaction with the setting control indicates allowing enabling the network management function, performing the method.
[0063] According to an example implementation of the present disclosure, the method further includes: in response to determining that the interaction indicates not allowing enabling the network management function, managing the network connection event based on the network configuration of the electronic device.
[0064] Example devices and equipment
[0065] Figure 9 A block diagram of an apparatus 900 for managing network connections according to some implementations of the present disclosure is shown. The apparatus includes: a presentation module 910 configured to present a prompt page indicating a network connection event in response to detecting a network connection event in the electronic device; a receiving module 920 configured to receive an interaction with the prompt page; and a management module 930 configured to manage the network connection event based on the interaction.
[0066] According to an example implementation of the present disclosure, the management module includes: an enabling module configured to enable a network interface in the electronic device to allow the network connection event in response to determining that the interaction indicates allowing the network connection event.
[0067] According to an example implementation of the present disclosure, the management module includes: a disabling module configured to disable a network interface in the electronic device to prohibit the network connection event in response to determining that the interaction indicates not allowing the network connection event.
[0068] According to an example implementation of the present disclosure, the prompt page further includes an identifier of an application associated with the network connection event, and the application is installed in the electronic device.
[0069] According to an example implementation of the present disclosure, the management module further includes: a long-term enabling module configured to enable a network interface in the electronic device to allow all network connection events in response to determining that the interaction indicates all network connection events that permit communication with the application; and a long-term disabling module configured to disable the network interface in the electronic device to prohibit all network connection events in response to determining that the interaction indicates all network connection events that do not permit communication with the application.
[0070] According to an example implementation of the present disclosure, the apparatus further includes: a receiving module configured to receive network connection events intercepted by a security module in the electronic device.
[0071] According to an example implementation of the present disclosure, the network connection events include at least any one of the following: a connection event initiated by the electronic device to connect to a remote device, and an acceptance event received by the electronic device from the remote device.
[0072] According to an example implementation of the present disclosure, the apparatus further includes: a providing module configured to provide status information of the network connection events.
[0073] According to an example implementation of the present disclosure, the apparatus further includes: a setting module configured to present a setting control for setting whether to allow enabling the network management function in the electronic device; and a calling module configured to call the apparatus in response to determining that the interaction with the setting control indicates allowing enabling the network management function.
[0074] According to an example implementation of the present disclosure, the apparatus further includes: a general management module configured to manage network connection events based on the network configuration of the electronic device in response to determining that the interaction indicates not allowing enabling the network management function.
[0075] Figure 10 A block diagram of a device 1000 capable of implementing multiple implementations of the present disclosure is shown. It should be understood that Figure 10 The illustrated computing device 1000 is merely exemplary and should not constitute any limitation on the functions and scope of the implementations described herein. Figure 10 The illustrated computing device 1000 can be used to implement the methods described above.
[0076] As Figure 10As shown, the computing device 1000 is in the form of a general-purpose computing device. The components of the computing device 1000 may include, but are not limited to, one or more processors or processing units 1010, a memory 1020, a storage device 1030, one or more communication units 1040, one or more input devices 1050, and one or more output devices 1060. The processing unit 1010 may be an actual or virtual processor and is capable of performing various processes according to the programs stored in the memory 1020. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing ability of the computing device 1000.
[0077] The computing device 1000 generally includes multiple computer storage media. Such media can be any available media accessible to the computing device 1000, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 1020 may be volatile memory (such as registers, caches, random access memory (RAM)), non-volatile memory (such as read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 1030 may be removable or non-removable media and may include machine-readable media, such as a flash drive, a magnetic disk, or any other medium that can be used to store information and / or data (such as training data for training) and can be accessed within the computing device 1000.
[0078] The computing device 1000 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in Figure 10 a disk drive for reading from or writing to a removable, non-volatile magnetic disk (such as a "floppy disk") and an optical disk drive for reading from or writing to a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 1020 may include a computer program product 1025 having one or more program modules configured to perform various methods or actions of various implementations of the present disclosure.
[0079] The communication unit 1040 enables communication with other computing devices through a communication medium. Additionally, the functions of the components of the computing device 1000 may be implemented in a single computing cluster or multiple computer machines that are capable of communicating through a communication connection. Thus, the computing device 1000 may operate in a networked environment using a logical connection to one or more other servers, network personal computers (PCs), or another network node.
[0080] The input device 1050 can be one or more input devices, such as a mouse, a keyboard, a trackball, etc. The output device 1060 can be one or more output devices, such as a display, a speaker, a printer, etc. The computing device 1000 can also communicate with one or more external devices (not shown) as needed through the communication unit 1040. The external devices such as a storage device, a display device, etc., communicate with one or more devices that enable a user to interact with the computing device 1000, or communicate with any device (e.g., a network card, a modem, etc.) that enables the computing device 1000 to communicate with one or more other computing devices. Such communication can be performed via an input / output (I / O) interface (not shown).
[0081] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, and the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided. The computer program product is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is provided, on which a computer program is stored, and when the program is executed by a processor, the method described above is implemented.
[0082] Aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and the combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.
[0083] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine such that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device is produced that implements the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause a computer, a programmable data processing device, and / or other devices to work in a specific manner. Thus, the computer-readable medium storing the instructions includes a manufacture, which includes instructions for implementing various aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.
[0084] Computer-readable program instructions may be loaded onto a computer, other programmable data processing apparatus, or other device, causing a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, such that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / acts specified in one or more boxes of the flowchart and / or block diagram.
[0085] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various implementations of the present disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a part of an instruction, which contains one or more executable instructions for implementing the specified logical function. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two consecutive blocks may in fact be executed substantially in parallel, or they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block of the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented by a dedicated hardware-based system that performs the specified functions or acts, or by a combination of dedicated hardware and computer instructions.
[0086] The various implementations of the present disclosure have been described above. The above description is exemplary, not exhaustive, and is not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The choice of terms used herein is intended to best explain the principles of the implementations, the practical application, or the improvement of the technology in the market, or to enable other ordinary skilled persons in the art to understand the various implementations disclosed herein.
Claims
1. A method for managing network connections, comprising: presenting a prompt page indicating the network connection event in response to detecting a network connection event in an electronic device; receiving an interaction with respect to the prompt page; and managing the network connection event based on the interaction.
2. The method according to claim 1, wherein managing the network connection event based on the interaction comprises: enabling a network interface in the electronic device to allow the network connection event in response to determining that the interaction indicates permission for the network connection event.
3. The method according to claim 1, wherein managing the network connection event based on the interaction comprises: disabling a network interface in the electronic device to prohibit the network connection event in response to determining that the interaction indicates non - permission for the network connection event.
4. The method according to claim 1, wherein the prompt page further comprises an identifier of an application associated with the network connection event, and the application is installed in the electronic device.
5. The method according to claim 4, wherein managing the network connection event based on the interaction further comprises at least any one of the following: enabling a network interface in the electronic device to allow all network connection events for communicating with the application in response to determining that the interaction indicates permission for all network connection events for communicating with the application; and disabling a network interface in the electronic device to prohibit all network connection events for communicating with the application in response to determining that the interaction indicates non - permission for all network connection events for communicating with the application.
6. The method according to claim 1, wherein detecting the network connection event comprises: receiving the network connection event intercepted by a security module in the electronic device.
7. The method according to claim 1, wherein the network connection event comprises at least any one of the following: a connection event initiated by the electronic device for connecting to a remote device, and an acceptance event received by the electronic device from a remote device.
8. The method according to claim 1, further comprising: providing status information of the network connection event.
9. The method according to claim 1, further comprising: presenting a setting control for setting whether to allow enabling a network management function in the electronic device; and executing the method in response to determining that the interaction with the setting control indicates permission to enable the network management function.
10. The method according to claim 9, further comprising: managing the network connection event based on the network configuration of the electronic device in response to determining that the interaction indicates non - permission to enable the network management function.
11. An apparatus for managing network connections, comprising: a presenting module configured to present a prompt page indicating the network connection event in response to detecting a network connection event in an electronic device; a receiving module configured to receive an interaction with respect to the prompt page; and a managing module configured to manage the network connection event based on the interaction.
12. An electronic device, comprising: at least one processing unit; and At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, causing the electronic device to perform the method according to any one of claims 1 to 10.
13. A computer-readable storage medium having stored thereon a computer program, the computer program, when executed by a processor, causing the processor to implement the method according to any one of claims 1 to 10.