CN113938890B - Data sharing method and terminal equipment - Google Patents

Abstract

The application relates to the technical field of terminals, and discloses a data sharing method and terminal equipment, which are used for solving the problem that user data sharing based on a user space file system Fuse cannot be realized in the prior art. The method comprises the following steps: displaying a user group creation page; based on the user operation of creating the page in the user group, obtaining a plurality of users input by the user; and combining the multiple users into the same user group, and authorizing the access authority of the user space file system Fuse of any user in the user group to other users in the user group. The method provides a user group concept, and in the aspect of operating data in the Fuse system, a plurality of users operate according to the identity of the user group, and different users are subdivided in the user space, so that the data sharing in the same user group and the Fuse system can be realized.

Description

Data sharing method and terminal device

Technical Field

The present application relates to the field of terminal technology, and in particular to a data sharing method and terminal device.

Background technique

The same terminal device can support different users. In order to protect user data, Android proposed Fuse (Filesystem in Userspace). In Fuse, each user's data is placed in the kernel layer and managed and maintained by Fuse.

For example, multiple users are created on an Android mobile device, including User 1 and User 2, but each user can only access his own data, and user data sharing based on the Fuse file system cannot be achieved currently.

Summary of the invention

The purpose of the present application is to provide a data sharing method and terminal device to solve the problem that user data sharing based on the Fuse file system cannot be realized in the prior art.

In a first aspect, the present application provides a data sharing method, the method comprising:

Display the user group creation page;

Based on the user operation on the user group creation page, obtaining multiple users input by the user;

The multiple users are merged into the same user group, and the access rights of the user space file system Fuse of any user in the user group are authorized to other users in the user group.

In a possible implementation manner, authorizing the Fuse access rights of any user in the user group to other users in the user group includes:

Create a common media provider component MediaProvider for the user group, and create a corresponding connection component connection and Fuse process for each user;

The method further comprises:

Send a data operation request of any first user in the user group to the second user to the MediaProvider, and the MediaProvider stores the data operation request in the pending instruction queue of the connection of the second user; wherein the Fuse process of the second user is used to obtain the data operation request from the pending instruction queue and return the execution result to the result queue of the connection of the second user after execution;

Receive an execution result for the data operation request returned by the MediaProvider, where the execution result is obtained by the MediaProvider from a result queue of the second user's connection.

In a possible implementation, creating a common MediaProvider for the user group includes:

Select a master user from the user group, and the remaining users serve as slave users;

Create a MediaProvider for the primary user;

For any slave user in the user group, before creating the MediaProvider of the slave user, query the user group to which the slave user belongs;

If the user group to which the slave user belongs is found, the MediaProvider of the master user is bound to the slave user.

In a possible implementation, the data operation request stores the operated data object;

Before sending a data operation request of any first user in the user group to the second user to the MediaProvider, the method further includes:

It is determined that the first user has access rights to the data object of the second user.

In a possible implementation manner, if the first user does not have access rights to the data object of the second user, a prompt message indicating that the user has no right to operate the data object is output.

In a possible implementation manner, determining the access permission of the first user to the second user includes:

Display the permission setting interface;

Based on user operations on the first user and the second user in the permission setting interface, the first user's access rights to the second user are determined.

In a possible implementation manner, the first user's access permission to the second user includes a picture library of the second user's instant messaging tool or a picture library of the second user's picture application.

In a possible implementation, the method further includes:

In response to a cancellation request to cancel the user group, deleting the user group; and,

After restarting the terminal device, create corresponding MediaProvider, connection, and Fuse processes for each user.

In a second aspect, the present application provides a terminal device, including:

Display, processor and memory;

The display is used to display a QR code;

The memory is used to store the processor executable instructions;

The processor is configured to execute the instructions to implement the data sharing method as described in any one of the first aspects above.

In a third aspect, the present application provides a computer-readable storage medium. When instructions in the computer-readable storage medium are executed by a terminal device, the terminal device can execute the data sharing method as described in any one of the first aspects above.

In a fourth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the data sharing method as described in any one of the first aspects above.

The technical solution provided by the embodiments of the present application brings at least the following beneficial effects:

In the embodiment of the present application, a user group creation page is displayed; and based on the user operation on the user group creation page, multiple users input by the user are obtained; then the multiple users are merged into the same user group, and the access rights of the user space file system Fuse of any user in the user group are authorized to other users in the user group, thereby realizing data sharing within the same user group, data sharing in the Fuse system, and data sharing between specified users in a multi-user system.

Other features and advantages of the present application will be described in the subsequent description, and partly become apparent from the description, or understood by practicing the present application. The purpose and other advantages of the present application can be realized and obtained by the structures specifically pointed out in the written description, claims, and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. Obviously, the drawings introduced below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

FIG1 is a schematic diagram of a process flow of each user independently accessing data provided by an embodiment of the present application;

FIG2 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application;

FIG3 is a software structure block diagram of a terminal device provided in an embodiment of the present application;

FIG4 is a schematic diagram of an application scenario provided by an embodiment of the present application;

FIG5 is a schematic diagram of a flow chart of a data sharing method provided in an embodiment of the present application;

FIG6 is a schematic diagram of creating multiple users according to an embodiment of the present application;

FIG7 is a schematic diagram of a user group creation page provided in an embodiment of the present application;

FIG8 is a schematic diagram of the architecture of data sharing management between designated users provided in an embodiment of the present application;

FIG9 is a schematic diagram of a process for creating a shared MediaProvider according to an embodiment of the present application;

FIG10 is a schematic diagram of a process of multiple users sharing data according to an embodiment of the present application;

FIG11 is a schematic diagram of a permission setting page provided in an embodiment of the present application.

Detailed ways

In order to make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Among them, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

Furthermore, in the description of the embodiments of the present application, unless otherwise specified, “/” means or. For example, A/B can mean A or B. The “and/or” in the text is merely a description of the association relationship between associated objects, indicating that three relationships may exist. For example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, “plurality” refers to two or more than two.

In the following, the terms "first", "second", and "second" are used for descriptive purposes only and should not be understood as suggesting or implying relative importance or implicitly indicating the number of technical features indicated. Therefore, the features defined as "first", "second", and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present application, unless otherwise specified, "multiple" means two or more.

Below, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

1) Multi-user system: It can support multiple users to use the system. Usually, the first user registered in the system is the system administrator. The settings of different users are different, and the applications and application data installed by different users are also different. However, the hardware-related settings in the system are shared, such as network settings.

2) MediaProvider (Media Provider Component): A system service that uniformly scans and controls media files in all directories of the system under the Android system. The media here include pictures, videos, music, etc.

3) Fuse (Filesystem in Userspace): It is a module used in Linux (GNU/Linux) to mount certain network spaces, such as SSH (Secure Shell), to the local file system. Related content can be found on SourceForge. It has a simple API (Application Programming Interface) library that can be accessed by non-privileged users, and can be implemented safely and stably.

In the prior art, the same terminal device can support different users. In order to protect user data, Android proposed Fuse (Filesystem in Userspace). In Fuse, each user's data is placed in the kernel layer and managed and maintained by Fuse.

Referring to FIG. 1 , a schematic diagram of the process of each user accessing data independently is shown. Multiple users are created on an Android mobile device, including user 1 and user 2, but each user can only access his own data, and user data sharing based on the Fuse file system cannot be realized at present. Specifically as shown in FIG. 1 : The Android phone includes user 1 and user 2. User 1 is created first, so user 1 is the administrator. User 1's application data is stored in data/user/0, and user 2's application data is stored in data/user/1/. There are also two targets in the Fuse system, where storage/emulated/0 corresponds to user 1's data/user/0, and storage/emulated/2 corresponds to user 2's data/user/1/. User 1 corresponds to three components, namely MediaProvider1, connection1, and Fuse process 1, and user 2 corresponds to three main components, namely MediaProvider2, connection2, and Fuse process 2. User 1 implements operations on user 1's data through its own MediaProvider1, connection1, and Fuse process 1. Similarly, user 2 implements access to user 2's data through MediaProvider2, connection2, and Fuse process 2. Fuse can isolate different users, but it is difficult for Fuse to meet the needs of some special scenarios, such as sharing pictures. Therefore, how to realize data sharing in the Fuse system needs to be solved.

In view of this, the present application proposes a data sharing method, in which the concept of user group is proposed. When operating data in the Fuse system, multiple users operate as user groups, and different users are further divided in the user space, thereby realizing data sharing in the Fuse system within the same user group.

The inventive concept of the present application can be summarized as follows: in the embodiment of the present application, a user group creation page is displayed; and based on the user operation on the user group creation page, multiple users input by the user are obtained; then the multiple users are merged into the same user group, and the access rights of the user space file system Fuse of any user in the user group are authorized to other users in the user group. Therefore, in the embodiment of the present application, the scheme can be implemented in the terminal device system, so that data sharing in the Fuse system within the same user group and data sharing between designated users in a multi-user system can be realized.

After introducing the inventive concept of the present application, the terminal device provided by the present application is described below. FIG. 2 shows a schematic diagram of the structure of a terminal device 200. It should be understood that the terminal device 200 shown in FIG. 2 is only an example, and the terminal device 200 may have more or fewer components than those shown in FIG. 2, may combine two or more components, or may have different component configurations. The various components shown in FIG. 2 may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.

Fig. 2 exemplarily shows a hardware configuration block diagram of a terminal device 200 according to an exemplary embodiment. As shown in Fig. 2 , the terminal device 200 includes: a radio frequency (RF) circuit 210, a memory 220, a display unit 230, a camera 240, a sensor 250, an audio circuit 260, a wireless fidelity (Wi-Fi) module 270, a processor 280, a Bluetooth module 281, and a power supply 290 and other components.

The RF circuit 210 can be used to receive and send signals during the process of sending and receiving information or making calls. It can receive downlink data from the base station and hand it over to the processor 280 for processing; it can send uplink data to the base station. Generally, the RF circuit includes but is not limited to antennas, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer and other devices.

The memory 220 can be used to store software programs and data. The processor 280 executes various functions and data processing of the terminal device 200 by running the software programs or data stored in the memory 220. The memory 220 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage device. The memory 220 stores an operating system that enables the terminal device 200 to run. In the present application, the memory 220 can store an operating system and various application programs, and can also store program codes for executing the method described in the embodiments of the present application.

The display unit 230 may be used to receive input digital or character information and generate signal input related to user settings and function control of the terminal device 200. Specifically, the display unit 230 may include a touch screen 231 disposed on the front of the terminal device 100, which may collect user touch operations on or near it, such as clicking a button, dragging a scroll box, etc.

The display unit 230 may also be used to display information input by a user or information provided to a user and a graphical user interface (GUI) of various menus of the terminal device 200. Specifically, the display unit 230 may include a display screen 232 disposed on the front of the terminal device 200. The display screen 232 may be configured in the form of a liquid crystal display, a light emitting diode, or the like.

The touch screen 231 may be covered on the display screen 232, or the touch screen 231 and the display screen 232 may be integrated to realize the input and output functions of the terminal device 200, and the integrated touch screen may be referred to as a touch display screen. In the present application, the display unit 230 may display the application and the corresponding operation steps.

The camera 240 can be used to capture still images or videos. The object is projected onto the photosensitive element through the lens to generate an optical image. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transmitted to the processor 280 for conversion into a digital image signal.

The terminal device 200 may further include at least one sensor 250, such as an acceleration sensor 251, a distance sensor 252, a fingerprint sensor 253, and a temperature sensor 254. The terminal device 200 may also be configured with other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, a light sensor, and a motion sensor.

The audio circuit 260, the speaker 261, and the microphone 262 can provide an audio interface between the user and the terminal device 200. The audio circuit 260 can transmit the electrical signal converted from the received audio data to the speaker 261, which is converted into a sound signal for output. The terminal device 200 can also be configured with a volume button for adjusting the volume of the sound signal. On the other hand, the microphone 262 converts the collected sound signal into an electrical signal, which is received by the audio circuit 260 and converted into audio data, and then the audio data is output to the RF circuit 210 to be sent to, for example, another terminal device, or the audio data is output to the memory 220 for further processing.

Wi-Fi is a short-range wireless transmission technology. The terminal device 200 can help users send and receive emails, browse web pages, and access streaming media through the Wi-Fi module 270, which provides users with wireless broadband Internet access.

The processor 280 is the control center of the terminal device 200. It uses various interfaces and lines to connect various parts of the entire terminal device. It executes various functions of the terminal device 200 and processes data by running or executing software programs stored in the memory 220 and calling data stored in the memory 220. In some embodiments, the processor 280 may include one or more processing units; the processor 280 may also integrate an application processor and a baseband processor, wherein the application processor mainly processes an operating system, a user interface, and an application program, and the baseband processor mainly processes wireless communications. It is understandable that the above-mentioned baseband processor may not be integrated into the processor 280. In this application, the processor 280 can run an operating system, an application program, a user interface display and a touch response, as well as the data sharing method described in the embodiment of the present application. In addition, the processor 280 is coupled to the display unit 230.

The Bluetooth module 281 is used to exchange information with other Bluetooth devices having Bluetooth modules through the Bluetooth protocol. For example, the terminal device 200 can establish a Bluetooth connection with a wearable electronic device (such as a smart watch) that also has a Bluetooth module through the Bluetooth module 281 to exchange data.

The terminal device 200 also includes a power supply 290 (such as a battery) for supplying power to various components. The power supply can be logically connected to the processor 280 through a power management system, so that the power management system can manage functions such as charging, discharging, and power consumption. The terminal device 200 can also be configured with a power button for turning on and off the terminal device, as well as locking the screen and other functions.

FIG. 3 is a software structure block diagram of the terminal device 200 according to an embodiment of the present application.

The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system can be divided into four layers, from top to bottom: application layer, application framework layer, Android runtime and system library, and kernel layer.

The application layer can include a series of application packages.

As shown in FIG. 3 , the application package may include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

As shown in FIG. 3 , the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

Content providers are used to store and retrieve data and make it accessible to applications. The data may include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, short messages, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a short message notification icon can include a view for displaying text and a view for displaying images.

The phone manager is used to provide communication functions of the terminal device 200, such as management of call status (including connection, disconnection, etc.).

The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, etc.

The notification manager enables applications to display notification information (such as message summaries and message contents) in the status bar. It can be used to convey notification-type messages and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, the terminal device vibrates, the indicator light flashes, etc.

Android Runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

The system library may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

A 2D (animation mode) graphics engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

The terminal device 200 in the embodiment of the present application may be an electronic device including but not limited to a mobile phone, a mobile terminal, a desktop computer, a mobile computer, a tablet computer, a home vital sign data collection device (such as a blood pressure monitor), a television, and the like.

The following is a brief introduction to the application scenarios to which the technical solutions of the embodiments of the present application can be applied. It should be noted that the application scenarios introduced below are only used to illustrate the embodiments of the present application and are not limited. In specific implementation, the technical solutions provided by the embodiments of the present application can be flexibly applied according to actual needs.

FIG4 shows a schematic diagram of an application scenario provided by an embodiment of the present application. The application scenario diagram includes: user A, application 401, terminal device 402, application 403, and user B. Among them:

User A uses application 401 to obtain data and stores the data in the external storage of user A in terminal device 402. User B can access the data stored in the external storage of user A by using application 403 in terminal device 401. For example, user A installs application 401 in terminal device 402 and takes a photo with application 401, which is stored in the file directory of user A. Application 403 installed by user B in terminal device 402 can view the photo.

Of course, the method provided in the embodiment of the present application is not limited to the application scenario shown in Figure 4, and can also be used in other possible application scenarios, which are not limited by the embodiment of the present application. The functions that can be implemented by each device in the application scenario shown in Figure 4 will be described in the subsequent method embodiments, and no further details will be given here.

To further illustrate the technical solution provided by the embodiments of the present application, a detailed description is given below in conjunction with the accompanying drawings and specific implementation methods.

Referring to FIG5 , a flow chart of a data sharing method is provided in an embodiment of the present application. As shown in FIG5 , the method includes the following steps:

In step 501, a user group creation page is displayed.

In a possible implementation, to display the user group creation page, multiple users need to be created first. As shown in FIG6 , user 1 and user 2 are created, and user 1 is created first, so user 1 is the administrator. Therefore, the application data of user 1 is stored in data/user/0, and the application data of user 2 is stored in data/user/1/. There are also two directories in the Fuse system, where storage/emulated/0 corresponds to data/user/0 of user 1, and storage/emulated/2 corresponds to data/user/1/ of user 2.

After creating multiple users, a user group selection function is preset on the device to display a user group creation page, as shown in Figure 7, where multiple created users can be displayed on the page. Then in step 502, multiple users input by the user are obtained based on the user operation on the user group creation page.

In a possible implementation, the user can select the user with whom to share data in the user group creation interface, and the selection method can be to touch the screen according to the prompt, or to select by pressing a button, or to select by searching for a specified user, which is not limited in this application. As shown in FIG. 7 , the user selects user 1 and user 2 to share data by touching the screen.

In step 503, the multiple users are merged into the same user group, and the access rights of the user space file system Fuse of any user in the user group are authorized to other users in the user group.

In one possible implementation, merging the multiple users into the same user group can be specifically implemented as shown in FIG. 7 , where the user selects user 1 and user 2 in FIG. 7 as users for sharing data, and then clicks a button to create a user group, and a page prompting successful creation of the user group is displayed, i.e., user 1 and user 2 are merged into the same user group, after which the user group interface will display that user group 1 includes user 1 and user 2.

See Figure 8, which is a schematic diagram of the architecture of data sharing management between designated users provided in an embodiment of the present application. In Figure 8, user 1 and user 2 share a media provider component MediaProvider and a Fuse process access permission, so the data Data1 and Data2 of user 1 and user 2 can be shared and accessed. It can be seen that sharing data between different users requires creating a common MediaProvider for the user group to which the user belongs.

In a possible implementation, taking two users sharing data as an example, the data sharing method provided in the embodiment of the present application is not only applicable to two users sharing data, but also applicable to multiple users such as three users, four users, etc.

In a possible implementation, to authorize the Fuse access rights of any user in the user group to other users in the user group, it is necessary to create a common MediaProvider for the user group, and create corresponding connection and Fuse processes for each user so as to manage the information of each user based on the connection and Fuse processes of each user.

In a possible implementation, creating a common MediaProvider for the user group may be specifically implemented as follows:

In step 901, a primary user is selected from the user group, and the remaining users are secondary users.

Each user may be distinguished according to a unique identifier of the user, and the unique identifier of the user may be a user ID or a data ID.

In step 902, a MediaProvider is created for the primary user.

In step 903, for any slave user in the user group, before creating the MediaProvider of the slave user, the user group to which the slave user belongs is queried.

The user group to which the slave user belongs may be queried according to the unique identifier of the slave user.

In step 904, if the user group to which the slave user belongs is found, the MediaProvider of the master user is bound to the slave user.

In a possible implementation, after creating a common MediaProvider for the user group and creating a corresponding connection and Fuse process for each user, data sharing can be implemented as follows: a data operation request for a second user from any first user in the user group is sent to the MediaProvider, and the MediaProvider stores the data operation request in the pending instruction queue of the connection of the second user; then, the Fuse process of the second user is used to obtain the data operation request from the pending instruction queue and return the execution result to the result queue of the connection of the second user after execution. The MediaProvider obtains the execution result from the result queue of the connection of the second user. Afterwards, the execution result of the data operation request returned by the MediaProvider is given to the user.

As shown in Figure 10, user 1 and user 2 share a MediaProvider, and user 1 corresponds to connection1 and Fuse process 1, while user 2 corresponds to connection2 and Fuse process 2. User 1 and user 2 share user 1 data and user 2 data through MediaProvider, connection1 and Fuse process 1, and connection2 and Fuse process 2. If user 1's application wants to access storage/emulated/2, it must first send an operation request to MediaProvider, use MediaProvider to establish Connection2 with the Fuse process, and store the operation request in the connection's pending instruction queue. Because the same MediaProvider is used to establish a connection with Fuse, this MediaProvider can provide the application with access to storage/emulated/0 and storage/emulated/2 data. This enables applications under different users to share access to storage/emulated/0 and storage/emulated/2.

In a possible implementation, some data content shared by the same user group, that is, data content shared with other users, is limited. For example, during authorization, only user 1 may be authorized to access pictures of user 2's instant messaging tool. In order to implement access permission restrictions, the data object of the operation is saved in the data operation request in the embodiment of the present application. Before sending a data operation request of any first user in the user group to the MediaProvider for a second user, it is also necessary to determine whether the first user has access rights to the data object of the second user. If the first user does not have access rights to the data object of the second user, a prompt message indicating that the user has no right to operate the data object is output.

In a possible implementation, determining the access rights of the first user to the second user can be implemented as follows: first displaying a permission setting interface to the user; and then determining the access rights of the first user to the second user based on user operations for the first user and the second user in the permission setting interface.

As shown in Figure 11, in the permission setting interface of Figure 11, the user can determine the access rights of the first user to the second user according to the prompt. The second user can choose to agree or disagree with the first user's access to the second user by touching the screen or pressing a button.

In a possible implementation, the first user's access rights to the second user include the picture library of the second user's instant messaging tool or the picture library of the second user's picture application. In this way, the first user can only access information in some picture libraries of the second user, but cannot access other information. This can meet the need of sharing pictures between different users and protect other privacy information of users.

In a possible implementation, if the first user ends accessing the second user's data, a revocation request may be issued, and the device deletes the user group in response to the revocation request of the user group; and, since the user group is deleted, after restarting the terminal device, a corresponding MediaProvider, connection, and Fuse process are created for each user. Thus, the first user and the second user no longer share data.

Based on the foregoing description, the embodiment of the present application displays a user group creation page; and based on the user operations on the user group creation page, obtains multiple users input by the user; then merges the multiple users into the same user group, and authorizes the access rights of the user space file system Fuse of any user in the user group to other users in the user group, thereby realizing data sharing within the same user group, in the Fuse system, and data sharing between specified users in a multi-user system.

Similar parts between the embodiments provided in this application can be referenced to each other. The specific implementation methods provided above are only a few examples under the general concept of this application and do not constitute a limitation on the protection scope of this application. For those skilled in the art, any other implementation methods expanded based on the scheme of this application without creative work belong to the protection scope of this application.

Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

The present application is described with reference to the flowchart and/or block diagram of the method, device (system), and computer program product according to the present application. It should be understood that each process and/or box in the flowchart and/or block diagram, as well as the combination of the process and/or box in the flowchart and/or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one process or multiple processes in the flowchart and/or one box or multiple boxes in the block diagram.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.

Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims (9)

1. A data sharing method, characterized in that the method comprises: Display the user group creation page; Based on the user operation on the user group creation page, multiple users input by the user are obtained; the user selects the user with whom to share data on the user group creation page, and the selection method includes: selecting by touching the screen according to the prompt, selecting by pressing a button, and selecting by searching for a specified user; Merge the multiple users into the same user group, and authorize the user space file system Fuse access rights of any user in the user group to other users in the user group; wherein, authorizing the Fuse access rights of any user in the user group to other users in the user group includes: creating a common media provider component MediaProvider for the user group, and creating a corresponding connection component connection and Fuse process for each user; The method further includes: sending a data operation request of any first user in the user group to the MediaProvider for a second user, and the MediaProvider storing the data operation request in a pending instruction queue of the connection of the second user; wherein the Fuse process of the second user is used to obtain the data operation request from the pending instruction queue and return the execution result to the result queue of the connection of the second user after execution; and receiving the execution result of the data operation request returned by the MediaProvider, wherein the execution result is obtained by the MediaProvider from the result queue of the connection of the second user. 2. The method according to claim 1, wherein creating a common MediaProvider for the user group comprises: Select a primary user from the user group, and the remaining users serve as secondary users; Create a MediaProvider for the primary user; For any slave user in the user group, before creating the MediaProvider of the slave user, query the user group to which the slave user belongs; If the user group to which the slave user belongs is found, the MediaProvider of the master user is bound to the slave user. 3. The method according to claim 1, characterized in that the data object to be operated is saved in the data operation request; Before sending a data operation request of any first user in the user group to the second user to the MediaProvider, the method further includes: It is determined that the first user has access rights to the data object of the second user. 4. The method according to claim 3 is characterized in that if the first user does not have access rights to the data object of the second user, a prompt message indicating that the user has no right to operate the data object is output. 5. The method according to claim 3 or 4, characterized in that determining the access rights of the first user to the second user comprises: Display the permission setting interface; Based on user operations on the first user and the second user in the permission setting interface, access rights of the first user to the second user are determined. 6 . The method according to claim 5 , wherein the access permission of the first user to the second user includes a picture library of an instant messaging tool of the second user or a picture library of a picture application of the second user. 7. The method according to any one of claims 1 to 4, characterized in that the method further comprises: In response to a cancellation request to cancel the user group, deleting the user group; and, After restarting the terminal device, create corresponding MediaProvider, connection, and Fuse processes for each user. 8. A terminal device, comprising: Display, processor and memory; The display is used to display a QR code; The memory is used to store the processor executable instructions; The processor is configured to execute the instructions to implement the data sharing method according to any one of claims 1 to 7. 9. A computer-readable storage medium, comprising: When the instructions in the computer-readable storage medium are executed by a terminal device, the terminal device is enabled to execute the data sharing method according to any one of claims 1 to 7.