CN112363988A

CN112363988A - File sharing method, mobile terminal and storage medium

Info

Publication number: CN112363988A
Application number: CN202011268311.8A
Authority: CN
Inventors: 杨志刚; 洪帆
Original assignee: Shenzhen Microphone Holdings Co Ltd
Current assignee: Shenzhen Microphone Holdings Co Ltd; Shenzhen Transsion Holdings Co Ltd
Priority date: 2020-11-13
Filing date: 2020-11-13
Publication date: 2021-02-12

Abstract

The application relates to a file sharing method, which is applied to a mobile terminal and comprises the following steps: receiving a sharing operation aiming at least one file; determining a sharing strategy of at least one file according to the attribute of the at least one file and/or the authority information of the operation; and sharing at least one file according to the sharing strategy. Through the mode, the sharing content can be managed and controlled from the sharing end, and the safe sharing of the file can be quickly and conveniently realized.

Description

File sharing method, mobile terminal and storage medium

Technical Field

The application relates to the technical field of communication terminals, in particular to a file sharing method, a mobile terminal and a storage medium.

Background

With the rapid development of terminal technology, mobile terminals such as mobile phones and tablet computers can rapidly share files through multiple channels such as mails, applications, face-to-face transmission and the like. In order to ensure the security of the shared file, the user needs to check and check the file information manually before sharing, and the operation is complicated and easy to make mistakes. In the prior art, some applications set a withdrawal function, and withdraw shared characters or files to save loss caused by wrong sharing operation, and if the other party checks or saves the characters or files when withdrawing, the security of shared information cannot be guaranteed.

The foregoing description is provided for general background information and is not admitted to be prior art.

Disclosure of Invention

In view of the above technical problems, the present application provides a file sharing method, a mobile terminal and a storage medium, which can quickly and conveniently realize secure sharing of files.

In order to solve the technical problem, the present application provides a file sharing method applied to a mobile terminal, including:

receiving a sharing operation aiming at least one file;

determining a sharing strategy of the at least one file according to the attribute of the at least one file and/or the authority information of the sharing operation;

and sharing the at least one file according to the sharing strategy.

Optionally, the attribute comprises at least one of a size, a name, a content, a type, a suffix name, a location, a creation time, a modification time, a hidden attribute, a read-only attribute, an encryption attribute, a compression attribute.

Optionally, the determining the sharing policy of the at least one file according to the attribute of the at least one file and/or the authority information of the sharing operation includes:

if the attribute of the file is a preset attribute, determining a sharing strategy of the at least one file according to a risk level corresponding to the preset attribute; and/or the presence of a gas in the gas,

and if the attribute of the file is not the preset attribute, displaying a selection popup window with the newly added attribute of the file as the preset attribute.

Optionally, before the receiving the sharing operation for the at least one file, the method further includes:

and setting the risk level of the preset attribute, wherein different risk levels correspond to different sharing strategies.

Optionally, a risk ranking table is generated according to the preset attributes.

Optionally, the preset attribute is a preset suffix name, and the determining the sharing policy of the file according to the preset attribute includes:

retrieving whether a suffix name of the file is included in the risk level table;

if yes, determining the risk level of the file, and determining the sharing strategy of the file according to the risk level of the file; and/or the presence of a gas in the gas,

and if not, displaying a selection popup window for setting the risk level corresponding to the suffix name.

Optionally, the determining the sharing policy of the file according to the preset attribute further includes:

retrieving whether the file name is included in the risk level table;

and if not, displaying a selection popup window for setting the risk level corresponding to the file name.

Optionally, the authority information of the sharing operation includes a user type, and the determining the sharing policy of the at least one file according to the attribute of the at least one file and/or the authority information of the sharing operation further includes:

determining sharing permission according to the type of the user executing the sharing operation;

and determining a sharing strategy of the file according to the sharing authority and/or the risk level of the file.

Optionally, the sharing policy includes at least one of:

refusing to share the file when the risk level of the attribute of the file is high risk;

sharing the file for a limited number of times when the risk level of the attribute of the file is medium risk;

when the risk level of the attribute of the file is low risk, allowing the file to be shared;

when the user authority of the sharing operation is high, allowing to share the high-risk file, the middle-risk file and the low-risk file;

when the user authority of the sharing operation is middle, the sharing of the high-risk files and the middle-risk files is refused, and the sharing of the low-risk files is allowed;

and when the user authority of the sharing operation is low, the sharing of the high-risk file, the middle-risk file and the low-risk file is refused.

Optionally, when the number of the files is one, the sharing the at least one file according to the sharing policy includes: the file is a medium-risk file, the sharing policy of the file is sharing for a limited number of times, optionally, when the sharing number of times of the file exceeds the limited number of times, a window including a sharing option is popped up, optionally, the sharing option includes determining to share and canceling to share, optionally, if a determining to share instruction is received, the file is shared and/or the risk level of the file is updated to be a low-risk file, optionally, if a canceling to share instruction is received, the file is canceled to share.

Optionally, when the number of the files is one, the sharing the at least one file according to the sharing policy further includes: the file is a low-risk file, the sharing policy of the file is allowed to be shared, optionally, when the file is shared for the first time, a query window is popped up, the query window is used for querying whether to set the risk level of the file, optionally, if so, a selection popup window for setting the risk level of the file is displayed, optionally, the file is a low-risk file, the sharing policy of the file is allowed to be shared, and when the file is not shared for the first time, the file is shared.

Optionally, when the number of the files is greater than one, the sharing the at least one file according to the sharing policy further includes:

and deleting the file which is rejected to be shared by the sharing strategy and/or repackaging the file which is allowed to be shared by the sharing strategy for sharing.

The application also provides a mobile terminal, which comprises a memory and a processor, wherein the memory is used for storing at least one program instruction, and the processor is used for realizing the file sharing method through loading and executing the at least one program instruction.

The present application further provides a computer storage medium having computer program instructions stored thereon; the computer program instructions, when executed by a processor, implement the file sharing method as described above.

As described above, the file sharing method, the mobile terminal and the storage medium of the present application, which are applied to the mobile terminal, include: receiving a sharing operation aiming at least one file; determining a sharing strategy of at least one file according to the attribute of the at least one file and/or the authority information of the operation; and sharing at least one file according to the sharing strategy. Through the mode, the sharing content can be managed and controlled from the sharing end, and the safe sharing of the file can be quickly and conveniently realized.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application. In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is a schematic hardware structure diagram of a mobile terminal implementing various embodiments of the present application;

fig. 2 is a communication network system architecture diagram according to an embodiment of the present application;

fig. 3 is a flowchart illustrating a file sharing method according to a first embodiment;

fig. 4 is a schematic specific flowchart of a file sharing method according to a first embodiment;

fig. 5 is a schematic diagram illustrating an effect of the file sharing method according to the first embodiment;

fig. 6 is a flowchart illustrating a file sharing method according to a second embodiment;

fig. 7 is a schematic diagram illustrating an effect of the file sharing method according to the second embodiment;

fig. 8 is one of the configuration diagrams of a mobile terminal shown according to the third embodiment;

fig. 9 is a second schematic structural diagram of the mobile terminal shown in fig. 8.

The implementation, functional features and advantages of the objectives of the present application will be further explained with reference to the accompanying drawings. With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, the recitation of an element by the phrase "comprising an … …" does not exclude the presence of additional like elements in the process, method, article, or apparatus that comprises the element, and further, where similarly-named elements, features, or elements in different embodiments of the disclosure may have the same meaning, or may have different meanings, that particular meaning should be determined by their interpretation in the embodiment or further by context with the embodiment.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context. Also, as used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes" and/or "including," when used in this specification, specify the presence of stated features, steps, operations, elements, components, items, species, and/or groups, but do not preclude the presence, or addition of one or more other features, steps, operations, elements, components, species, and/or groups thereof. The terms "or," "and/or," "including at least one of the following," and the like, as used herein, are to be construed as inclusive or mean any one or any combination. For example, "includes at least one of: A. b, C "means" any of the following: a; b; c; a and B; a and C; b and C; a and B and C ", again for example," A, B or C "or" A, B and/or C "means" any of the following: a; b; c; a and B; a and C; b and C; a and B and C'. An exception to this definition will occur only when a combination of elements, functions, steps or operations are inherently mutually exclusive in some way.

It should be understood that, although the steps in the flowcharts in the embodiments of the present application are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, in different orders, and may be performed alternately or at least partially with respect to other steps or sub-steps of other steps.

It should be noted that step numbers such as S11 and S12 are used herein for the purpose of more clearly and briefly describing the corresponding content, and do not constitute a substantial limitation on the sequence, and those skilled in the art may perform S12 first and then S11 in specific implementation, which should be within the scope of the present application.

It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for the convenience of description of the present application, and have no specific meaning by themselves. Thus, "module", "component" or "unit" may be used mixedly.

The terminal may be implemented in various forms. For example, the terminal described in the present application may include a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and the like, and a fixed terminal such as a Digital TV, a desktop computer, and the like.

The following description will be given taking a mobile terminal as an example, and it will be understood by those skilled in the art that the configuration according to the embodiment of the present application can be applied to a fixed type terminal in addition to elements particularly used for mobile purposes.

Referring to fig. 1, which is a schematic diagram of a hardware structure of a mobile terminal for implementing various embodiments of the present application, the mobile terminal 100 may include: RF (Radio Frequency) unit 101, WiFi module 102, audio output unit 103, a/V (audio/video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 1 is not intended to be limiting of mobile terminals, which may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The following describes each component of the mobile terminal in detail with reference to fig. 1:

the radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the downlink information to the processor 110; in addition, the uplink data is transmitted to the base station. Typically, radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 can also communicate with a network and other devices through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000(Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex Long Term Evolution), and TDD-LTE (Time Division duplex Long Term Evolution).

WiFi belongs to short-distance wireless transmission technology, and the mobile terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 102, and provides wireless broadband internet access for the user. Although fig. 1 shows the WiFi module 102, it is understood that it does not belong to the essential constitution of the mobile terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.

The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, and the like.

The a/V input unit 104 is used to receive audio or video signals. The a/V input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, the Graphics processor 1041 Processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphic processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 may receive sounds (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, or the like, and may be capable of processing such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.

The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Optionally, the light sensor includes an ambient light sensor that may adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that may turn off the display panel 1061 and/or the backlight when the mobile terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.

The display unit 106 is used to display information input by a user or information provided to the user. The Display unit 106 may include a Display panel 1061, and the Display panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.

The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal. Alternatively, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near the touch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of a touch detection device and a touch controller. Optionally, the touch detection device detects a touch orientation of a user, detects a signal caused by a touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. Optionally, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like, and are not limited thereto.

Further, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although the touch panel 1071 and the display panel 1061 are shown in fig. 1 as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, and is not limited herein.

The interface unit 108 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and external devices.

The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a program storage area and a data storage area, and optionally, the program storage area may store an operating system, an application program (such as a sound playing function, an image playing function, and the like) required by at least one function, and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 109 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by operating or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor and a modem processor, optionally, the application processor mainly handles operating systems, user interfaces, application programs, etc., and the modem processor mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.

The mobile terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system.

Although not shown in fig. 1, the mobile terminal 100 may further include a bluetooth module or the like, which is not described in detail herein.

In order to facilitate understanding of the embodiments of the present application, a communication network system on which the mobile terminal of the present application is based is described below.

Referring to fig. 2, fig. 2 is an architecture diagram of a communication Network system according to an embodiment of the present disclosure, where the communication Network system is an LTE system of a universal mobile telecommunications technology, and the LTE system includes a UE (User Equipment) 201, an E-UTRAN (Evolved UMTS Terrestrial Radio Access Network) 202, an EPC (Evolved Packet Core) 203, and an IP service 204 of an operator, which are in communication connection in sequence.

Optionally, the UE201 may be the terminal 100 described above, and is not described herein again.

The E-UTRAN202 includes eNodeB2021 and other eNodeBs 2022, among others. Alternatively, the eNodeB2021 may be connected with other enodebs 2022 through a backhaul (e.g., X2 interface), the eNodeB2021 is connected to the EPC203, and the eNodeB2021 may provide the UE201 access to the EPC 203.

The EPC203 may include an MME (Mobility Management Entity) 2031, an HSS (Home Subscriber Server) 2032, other MMEs 2033, an SGW (Serving gateway) 2034, a PGW (PDN gateway) 2035, and a PCRF (Policy and Charging Rules Function) 2036, and the like. Optionally, the MME2031 is a control node that handles signaling between the UE201 and the EPC203, providing bearer and connection management. HSS2032 is used to provide registers to manage functions such as home location register (not shown) and holds subscriber specific information about service characteristics, data rates, etc. All user data may be sent through SGW2034, PGW2035 may provide IP address assignment for UE201 and other functions, and PCRF2036 is a policy and charging control policy decision point for traffic data flow and IP bearer resources, which selects and provides available policy and charging control decisions for a policy and charging enforcement function (not shown).

The IP services 204 may include the internet, intranets, IMS (IP Multimedia Subsystem), or other IP services, among others.

Although the LTE system is described as an example, it should be understood by those skilled in the art that the present application is not limited to the LTE system, but may also be applied to other wireless communication systems, such as GSM, CDMA2000, WCDMA, TD-SCDMA, and future new network systems.

Based on the above mobile terminal hardware structure and communication network system, various embodiments of the present application are provided.

First embodiment

Fig. 3 is a flowchart illustrating a file sharing method according to a first embodiment. Referring to fig. 3, a file sharing method applied to a mobile terminal includes:

step S11: receiving a sharing operation aiming at least one file;

step S12: determining a sharing strategy of at least one file according to the attribute of at least one file and/or the authority information of sharing operation;

step S13: and sharing at least one file according to the sharing strategy.

In this embodiment, the mobile terminal may be a PC, or may be a mobile terminal device having a display function, such as a smart phone, a tablet computer, an electronic book reader, or a portable computer. After the sharing operation aiming at least one file is received, a sharing strategy of the file is determined according to the file attribute, the user authority information for executing the sharing operation or the combination of the file attribute and the authority information of the operation, then the file is shared according to the determined sharing strategy, and the safety of the shared file is improved. The number of the files can be one or more, and after the sharing strategy of the files is determined, the files can be directly shared according to the sharing strategy aiming at the sharing of a single file; when a folder or a compressed file package containing multiple files is shared, different files may have multiple sharing strategies, so that the sharing strategy needs to be deleted as a file which is refused to be shared, and then the files which are allowed to be shared are repackaged and then shared, so that mistaken sharing of the files which need to be kept secret when the files are shared in batches is effectively avoided, time for checking the files manually is saved, and sharing efficiency is improved.

Optionally, the file attributes include size, name, content, type, suffix name, location, creation time, modification time, hidden attribute, read-only attribute, encryption attribute, compression attribute, etc., and the user may select a specific file attribute as an evaluation criterion of the risk level as desired. When the sharing strategy is determined according to the attribute of the file, the attribute of the file is acquired, and then whether the attribute is a preset attribute is searched, for example, whether the attribute is a preset type, whether the attribute has a preset suffix name, and the like. If the attribute of the file is the preset attribute, determining the risk level of the file according to the corresponding relation between the preset attribute and the risk level, and further determining the sharing strategy of the file. And/or if the attribute of the file is not the preset attribute, displaying a selection popup for setting the attribute of the file to be the preset attribute, and inquiring whether the user sets the attribute of the file to be the preset attribute.

Optionally, when the preset attribute is a preset file name, searching whether a keyword of the file name is included in the risk level table; if yes, determining the risk level of the file, and determining a sharing strategy of the file according to the risk level of the file; and/or if not, displaying a selection popup window for setting the risk level corresponding to the file name. When the preset attribute is the file size, searching whether the corresponding relation between the file size and the risk level exists in the risk level table or not, further determining the risk level of the file, and determining a sharing strategy of the file according to the risk level of the file; and if the size of the file is not in the risk grade table, displaying a selection popup window for setting the risk grade corresponding to the file name. When the preset attribute is the file content, searching whether the risk level table comprises keywords of the file content; if yes, determining the risk level of the file, and determining a sharing strategy of the file according to the risk level of the file; and/or if not, displaying a selection popup window for setting the risk level corresponding to the file name. When the preset attribute is the file type or the suffix name, searching whether the risk level table comprises the file type or the suffix name; if yes, determining the risk level of the file, and determining a sharing strategy of the file according to the risk level of the file; and/or if not, displaying a selection popup window for setting the risk level corresponding to the file name. When the preset attribute is the file position, searching whether the position range information of the file is included in the risk level table or not; if yes, determining the risk level of the file, and determining a sharing strategy of the file according to the risk level of the file; and/or if not, displaying a selection popup window for setting the risk level corresponding to the file name. When the preset attribute is the creation time or the modification time of the file, searching whether the creation time range or the modification time range of the file is included in the risk level table or not; if yes, determining the risk level of the file, and determining a sharing strategy of the file according to the risk level of the file; and/or if not, displaying a selection popup window for setting the risk level corresponding to the file name. When the preset attribute is a hidden attribute, a read-only attribute, an encryption attribute or a compression attribute of the file, searching whether the file is the hidden attribute, the read-only attribute, the encryption attribute or the compression attribute or not in the risk level table; if yes, determining the risk level of the file, and determining a sharing strategy of the file according to the risk level of the file; and/or if not, displaying a selection popup window for setting the risk level corresponding to the file name. The attributes can be freely combined to serve as risk level reference standards of the files, risk level classification of the shared files is refined, and file sharing efficiency is improved.

Optionally, before receiving a sharing operation for at least one file, setting a risk level of a preset attribute, and setting a risk level table according to the preset attribute of the file, where different risk levels correspond to different sharing policies. For example, when the preset attribute is a suffix name of a file, a correspondence between a specific suffix name and a risk level is set and a risk level table is created. The risk level can be set to be high, medium and low, a suffix name list including a high risk level, a suffix name list including a medium risk level and a suffix name list including a low risk level can be respectively created, and suffix names of different risk levels can be gathered to one risk level list. After the sharing operation is received, whether the suffix name of the file exists in the risk level table or not is searched according to the suffix name of the file, if yes, the risk level of the file is searched, and the sharing strategy of the file is determined according to the risk level of the file. And/or if the suffix name does not exist, displaying a selection popup window for setting the risk level corresponding to the suffix name, inquiring whether the user sets the shared risk level for the suffix name or not, and adding the risk level into the risk level table. Then, when the sharing strategy is determined according to the risk level of the file, the file can be divided into a high-risk file, a medium-risk file and a low-risk file according to different risk levels. The sharing policy of the high-risk file can be to refuse to share, the sharing policy of the medium-risk file can be to share for a limited number of times, for example, only one time is shared, and the sharing policy of the low-risk file can be to always allow to share.

Optionally, when the number of the files is one, sharing at least one file according to the sharing strategy, determining the sharing strategy of the file according to the preset attribute, if the file is a medium risk file and the sharing times of the file exceed the limited times, popping up a window comprising sharing options, wherein the sharing options comprise determining sharing and cancelling sharing; if a sharing determining instruction is received, sharing the file, and updating the risk level of the file into a low risk file; and/or canceling the sharing file if a sharing canceling instruction is received. If the file is a low-risk file, and if the sharing strategy of the file is to allow sharing and the file is to be shared for the first time, popping up an inquiry window, wherein the inquiry window is used for inquiring whether to set the risk level of the file, if so, displaying a selection popup window for setting the risk level of the file, and the user can set the risk level of the file attribute as required, so that the operation is convenient and fast.

Optionally, the operating permission information includes a user type, and the sharing policy of the file is determined according to the attribute of the file and/or the operating permission information by sharing at least one file according to the sharing policy, and further includes: determining the sharing authority of the user according to the type of the user executing the sharing operation; determining a file sharing strategy according to the sharing authority of the user and/or the risk level of the file; and sharing the file according to the sharing strategy. Determining a file sharing strategy according to the sharing authority of the user and/or the risk level of the file, wherein the file sharing strategy comprises the following steps: when the sharing authority of the user is high, allowing the high-risk file, the middle-risk file and the low-risk file to be shared; and/or refusing to share the high-risk files and the medium-risk files and allowing to share the low-risk files when the sharing authority of the user is medium; and/or refusing to share the high-risk file, the middle-risk file and the low-risk file when the sharing authority of the user is low.

Fig. 4 is a schematic specific flowchart of a file sharing method according to a first embodiment. Fig. 5 is a schematic diagram illustrating an effect of the file sharing method according to the first embodiment. Referring to fig. 4 and 5, in fig. 5(a), first, a shared risk level and a sharing policy thereof are set, a high risk file type is set as not allowing sharing outgoing, a medium risk file type is set as sharing outgoing risk reminder, a low risk file type is set as sharing outgoing non-reminder, then a specific file type is stored in different risk levels, a suffix name of a file can be input for identifier screening, or a corresponding file suffix name can be selected according to options such as a text file, a video file, an audio file, a picture file, an executable file, a program file, and the like, for example, files of the type of exe, txt, c, and cpp are set as high risk file types, and files of the type of doc and excel are set as medium risk file types.

In fig. 5(b), when the user sends out the file packet GPIO check, zip, the risk level corresponding to the suffix name of the file in the file packet is first retrieved, so as to determine the risk level of the file, and prompt the user whether the current file or the file packet contains a sensitive file that cannot be sent out. If the user has a high risk level of a suffix name for a file in the outgoing bundle that is prohibited from outgoing, e.g., c, the user is alerted that the current outgoing operation is not permitted, e.g., "ERROR! C, configuring a high risk file list 1', modifying the risk level in a security setting to be sent out, and creating a high risk file name list for packing the files again in a follow-up mode.

In fig. 5(c), if there is a file suffix name with a medium risk level in the file packet GPIO check.zip sent out by the user, e.g.. a.doc, the user is reminded of which files in the current file packet are files with medium risk, and a popup box asks the user whether to allow sending out, e.g. "going contains a medium risk file and allows sending out,. doc has configured a list of medium risk files 2", and does not send out if the user does not allow, and updates the list of medium risk files for subsequent repacking of the files; and/or, if the user allows sending, asking if this type of file is always allowed to be sent or only once; if only once; sending and not doing other operations; and/or if the user selects to always allow sending, after the file is sent out, the background modifies the risk level table to reduce the risk level of the file type to a low risk level.

In fig. 5(d), if a certain file in the file package sent by the user is not in the risk level table, the user is prompted with "no outgoing risk level is configured for the current file type, and is configured? ", after the user selects" yes "option, jump to the risk level setting interface and have selected the file type, with the risk level selected. And after the user finishes selecting the risk level, prompting the user whether to send the file according to the risk level. And if the file package sent out by the user is in a low risk level and the high risk file list or the medium risk file list is not empty, repacking the file package according to the information in the list, and deleting the files which cannot be sent out. If the high risk list and the medium risk list are both empty, the file package can be directly shared. And if the file type without the risk level is in the file package, inquiring whether the user needs to set the file type, if so, popping up a setting window, and/or if not, directly sending out the shared file. According to the method, on the premise of ensuring safe file sharing, a user can change and adjust the risk level table through the popup window, and the operation is simple and convenient.

Second embodiment

Fig. 6 is a flowchart illustrating a file sharing method according to a second embodiment. Fig. 7 is a schematic diagram illustrating an effect of the file sharing method according to the second embodiment. Referring to fig. 6 and 7, it is searched whether a file name is included in the risk level table; if yes, determining the risk level of the file, and determining a sharing strategy of the file according to the risk level of the file; and/or if not, displaying a selection popup window for setting the risk level corresponding to the file name. And after receiving the sharing operation aiming at least one file, when the preset attribute is the preset file name, carrying out a risk level outgoing process of the special file according to the file name. For a file which is not subjected to risk level setting according to a file name, firstly prompting a user whether to set the risk level of the file independently, inputting a file name keyword by the user to search a risk level table, and then setting the risk attribute of the file. In fig. 7(a), if a certain file in the file package sent by the user is not in the risk level table, for example, "platform standard. doc", then the user is prompted to "whether to set the risk level of the certain file alone? After the user sets the risk level table, the risk level table is updated, and whether the file can be sent out or whether the user is prompted to carry out the risk is judged according to the risk level. Optionally, in the security setting, the security attribute of the relevant file is selected first, and the risk level table is generated after setting, high risk-non-sharable outgoing prompt, medium risk-shared outgoing prompt, low risk-shared outgoing non-prompt. When a user shares a file, the system firstly prompts the user whether to set the outgoing permission of the special file or not, namely to set the risk level of the special file, if so, the user needs to input a file name in a search box to retrieve the corresponding file, and sets the risk level of the special file after selecting the special file, and sets the file as a special attribute file. In fig. 7(b), after the user finishes selecting, the files with special file attributes in the outgoing file package are detected, if the files with high risk level prompt the user that the files belonging to the high risk level cannot be outgoing, and are recorded in the high risk level list 1, if the files with medium risk level prompt the user whether the files belonging to the medium risk level need to be outgoing, if the files are not outgoing, the files are recorded in the medium risk level list 2, and/or if the files are selected to be outgoing, further inquiry is made whether the files are always outgoing, otherwise, the files are only outgoing in the outgoing, and if the files are selected to be always outgoing, the attributes of the special files are updated to be the low risk special files. Then, according to the information of the high risk level list and the medium risk level list, excluding the files in the list from the repackaged file package, and sending the repackaged file package out; and if the lists are empty, directly transmitting the files in the file packet needing transmitting. Through the mode, the sharing content can be managed and controlled from the sharing end, and the safe sharing of the file can be quickly and conveniently realized.

Third embodiment

Fig. 8 is one of the structural diagrams of the mobile terminal shown according to the third embodiment. Referring to fig. 8, the mobile terminal 80 of the present embodiment includes a memory 802 and a processor 806, wherein the memory 802 is configured to store at least one program instruction, and the processor 806 is configured to implement the file sharing method by loading and executing the at least one program instruction.

Referring to fig. 9, in actual implementation, the mobile terminal 80 includes a memory 802, a memory controller 804, one or more processors 806 (only one of which is shown), a peripheral interface 808, a radio frequency module 850, a positioning module 812, a camera module 814, an audio module 816, a screen 818, and a key module 860. These components communicate with one another via one or more communication buses/signal lines 822.

It is to be understood that the configuration shown in fig. 9 is merely exemplary, and that the mobile terminal 80 may include more or fewer components than shown in fig. 9, or have a different configuration than shown in fig. 9. The components shown in fig. 9 may be implemented in hardware, software, or a combination thereof.

The memory 802 may be used to store software programs and modules, such as program instructions/modules corresponding to the file sharing method in the embodiment of the present application, and the processor 806 executes various functional applications and data processing by operating the software programs and modules stored in the storage controller 804, that is, implementing the file sharing method described above.

The memory 802 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 802 may further include memory located remotely from the processor 806, which may be connected to the mobile terminal 80 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof. Access to the memory 802 by the processor 806, as well as possibly other components, may be under the control of a memory controller 804.

The peripheral interface 808 couples various input/output devices to the CPU and to the memory 802. The processor 806 executes various software, instructions within the memory 802 to perform various functions of the mobile terminal 80 as well as data processing.

In some embodiments, the peripheral interface 808, the processor 806, and the memory controller 804 may be implemented in a single chip. In other examples, they may be implemented separately from the individual chips.

The rf module 850 is used for receiving and transmitting electromagnetic waves, and implementing interconversion between the electromagnetic waves and electrical signals, so as to communicate with a communication network or other devices. The radio frequency module 850 may include various existing circuit elements for performing these functions, such as an antenna, a radio frequency transceiver, a digital signal processor, an encryption/decryption chip, a Subscriber Identity Module (SIM) card, memory, and so forth. The rf module 850 may communicate with various networks such as the internet, an intranet, a wireless network, or with other devices via a wireless network. The wireless network may comprise a cellular telephone network, a wireless local area network, or a metropolitan area network. The Wireless network may use various Communication standards, protocols, and technologies, including, but not limited to, Global System for Mobile Communication (GSM), Enhanced Mobile Communication (Enhanced Data GSM Environment, EDGE), wideband Code division multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), bluetooth, Wireless Fidelity (WiFi) (e.g., IEEE802.11a, IEEE802.11 b, IEEE802.1 g, and/or IEEE802.11 n), Voice over Internet Protocol (VoIP), world wide mail Access (Microwave for information, Access, Wi-15, Max), and any other suitable Protocol for short message Communication, and may even include those protocols that have not yet been developed.

The positioning module 812 is used for acquiring the current position of the mobile terminal 80. Examples of the positioning module 812 include, but are not limited to, a global positioning satellite system (GPS), a wireless local area network-based positioning technology, or a mobile communication network-based positioning technology.

The camera module 814 is used to take pictures or videos. The pictures or videos taken may be stored in the memory 802 and may be transmitted through the radio frequency module 850.

The audio module 816 provides an audio interface to the user, which may include one or more microphones, one or more speakers, and audio circuitry. The audio circuitry receives audio data from the peripheral interface 808, converts the audio data to electrical information, and transmits the electrical information to the speaker. The speaker converts the electrical information into sound waves that the human ear can hear. The audio circuitry also receives electrical information from the microphone, converts the electrical information to voice data, and transmits the voice data to the peripheral interface 808 for further processing. The audio data may be retrieved from the memory 802 or through the radio frequency module 850. In addition, the audio data may also be stored in the memory 802 or transmitted through the radio frequency module 850. In some examples, the audio module 816 may also include a headphone jack for providing an audio interface to headphones or other devices.

The screen 818 provides an output interface between the mobile terminal 80 and the user. Optionally, screen 818 displays video output to the user, the content of which may include text, graphics, video, and any combination thereof. Some of the output results are for some of the user interface objects. It is understood that the screen 818 may also include a touch screen. The touch screen provides both an output and an input interface between the mobile terminal 80 and the user. In addition to displaying video output to users, touch screens also receive user input, such as user clicks, swipes, and other gesture operations, so that user interface objects respond to these user input. The technique of detecting user input may be based on resistive, capacitive, or any other possible touch detection technique. Specific examples of touch screen display units include, but are not limited to, liquid crystal displays or light emitting polymer displays.

The key module 860 also provides an interface for user input to the mobile terminal 80, and the user may cause the mobile terminal 80 to perform different functions by pressing different keys.

The present application further provides a computer storage medium having computer program instructions stored thereon; the computer program instructions, when executed by the processor, implement the file sharing method as above.

Embodiments of the present application also provide a computer program product, which includes computer program code, when the computer program code runs on a computer, the computer is caused to execute the method as described in the above various possible embodiments.

An embodiment of the present application further provides a chip, which includes a memory and a processor, where the memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that a device in which the chip is installed executes the method described in the above various possible embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, a controlled terminal, or a network device) to execute the method of each embodiment of the present application.

The above description is only a preferred embodiment of the present application, and not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application, or which are directly or indirectly applied to other related technical fields, are included in the scope of the present application.

Claims

1. A file sharing method is applied to a mobile terminal and is characterized by comprising the following steps:

receiving a sharing operation aiming at least one file;

and sharing the at least one file according to the sharing strategy.

2. The file sharing method according to claim 1, wherein the attribute includes at least one of a size, a name, a content, a type, a suffix name, a location, a creation time, a modification time, a hidden attribute, a read-only attribute, an encryption attribute, and a compression attribute, and the determining the sharing policy of the at least one file according to the attribute of the at least one file and/or the authority information of the sharing operation includes:

if the attribute of the file is a preset attribute, determining a sharing strategy of the file according to a risk level corresponding to the preset attribute; and/or the presence of a gas in the gas,

3. The method according to claim 2, wherein before receiving the sharing operation for the at least one file, the method further comprises:

setting risk levels of the preset attributes, wherein different risk levels correspond to different sharing strategies;

and generating a risk grade table according to the preset attribute.

4. The method according to claim 3, wherein the predetermined attribute is a predetermined suffix name, and the determining the sharing policy of the file according to the predetermined attribute comprises:

5. The method according to claim 3, wherein the preset attribute is a preset file name, and the determining the sharing policy of the file according to the preset attribute further comprises:

retrieving whether the file name is included in the risk level table;

6. The file sharing method according to any one of claims 1 to 5, wherein the permission information of the sharing operation includes a user type, and the determining the sharing policy of the at least one file according to the attribute of the at least one file and/or the permission information of the sharing operation further includes:

7. The file sharing method according to any one of claims 1 to 5, wherein the sharing policy includes at least one of:

8. The file sharing method according to any one of claims 1 to 5, wherein the sharing the at least one file according to the sharing policy includes at least one of:

when the number of the files is one, the files are middle risk files, and the sharing strategy of the files is limited times of sharing;

when the number of the files is one, the files are low-risk files, and the sharing strategy of the files is allowed to be shared;

and when the number of the files is more than one, deleting the files of which the sharing strategy is refused to share and/or repacking the files of which the sharing strategy is allowed to share for sharing.

9. A mobile terminal, comprising a memory and a processor, wherein the memory is configured to store at least one program instruction, and the processor is configured to implement the file sharing method according to any one of claims 1 to 8 by loading and executing the at least one program instruction.

10. A computer storage medium having computer program instructions stored thereon; the computer program instructions, when executed by a processor, implement a file sharing method as claimed in any one of claims 1 to 8.