CN113938890A - Data sharing method and terminal equipment - Google Patents
Data sharing method and terminal equipment Download PDFInfo
- Publication number
- CN113938890A CN113938890A CN202111080481.8A CN202111080481A CN113938890A CN 113938890 A CN113938890 A CN 113938890A CN 202111080481 A CN202111080481 A CN 202111080481A CN 113938890 A CN113938890 A CN 113938890A
- Authority
- CN
- China
- Prior art keywords
- user
- data
- users
- user group
- mediaprovider
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 58
- 230000008569 process Effects 0.000 claims description 19
- 230000004044 response Effects 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 19
- 239000010410 layer Substances 0.000 description 19
- 230000006870 function Effects 0.000 description 14
- 238000012545 processing Methods 0.000 description 12
- 238000004590 computer program Methods 0.000 description 9
- FFBHFFJDDLITSX-UHFFFAOYSA-N benzyl N-[2-hydroxy-4-(3-oxomorpholin-4-yl)phenyl]carbamate Chemical compound OC1=C(NC(=O)OCC2=CC=CC=C2)C=CC(=C1)N1CCOCC1=O FFBHFFJDDLITSX-UHFFFAOYSA-N 0.000 description 4
- 230000005236 sound signal Effects 0.000 description 4
- 230000003993 interaction Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000015572 biosynthetic process Effects 0.000 description 1
- 230000036772 blood pressure Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 239000012792 core layer Substances 0.000 description 1
- 238000007599 discharging Methods 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000009877 rendering Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000003786 synthesis reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/30—Security of mobile devices; Security of mobile applications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/604—Tools and structures for managing or administering access control systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
- H04M1/72463—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions to restrict the functionality of the device
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/03—Protecting confidentiality, e.g. by encryption
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Human Computer Interaction (AREA)
- Theoretical Computer Science (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Automation & Control Theory (AREA)
- Stored Programmes (AREA)
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; obtaining a plurality of users input by the users based on the user operation of creating the page in the user group; merging the 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, a plurality of users operate according to the identity of the user group on the level of operating data in the Fuse system, and different users are divided in the user space, so that the data sharing in the Fuse system can be realized within the same user group.
Description
Technical Field
The present application relates to the field of terminal technologies, and in particular, to a data sharing method and a terminal device.
Background
The same terminal equipment can support different users. To protect user data, android proposes Fuse (user space file system). In Fuse, data for each user is placed at the kernel level, managed and maintained by Fuse.
For example, a plurality of users are created on an Android (Android) mobile phone device, including user 1 and user 2, but each user can only access own data, and currently, user data sharing based on a Fuse file system cannot be realized.
Disclosure of Invention
The application aims to provide a data sharing method and terminal equipment, and the data sharing method and terminal equipment are used for solving the problem that user data sharing based on a Fuse file system cannot be achieved in the prior art.
In a first aspect, the present application provides a data sharing method, including:
displaying a user group creation page;
obtaining a plurality of users input by the users based on the user operation of creating the page in the user group;
merging the 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.
In a possible embodiment, the granting the access right of the Fuse of any user in the user group to other users in the user group includes:
establishing a shared media provider component Mediaprovider for the user group, and respectively establishing a corresponding connection component and a Fuse process for each user;
the method further comprises the following steps:
sending a data operation request of any first user in the user group to a second user to the MediaProvider, and storing the data operation request to a command queue to be executed of a connection of the second user by the MediaProvider; the Fuse process of the second user is used for acquiring the data operation request from the instruction queue to be executed, and returning an execution result to a result queue of connection of the second user after the data operation request is executed;
receiving an execution result returned by the MediaProvider for the data operation request, wherein the execution result is obtained by querying the MediaProvider from a result queue of the connection of the second user.
In one possible embodiment, creating a common MediaProvider for the user group includes:
selecting a master user from the user group, and taking the rest users as slave users;
establishing a MediaProvider for the master user;
for any slave user in the user groups, inquiring the user group in which the slave user is positioned before creating the MediaProvider of the slave user;
and if the user group where the slave user is located is inquired, binding the MediaProvider of the master user to the slave user.
In one possible implementation, the data object of the operation is saved in the data operation request;
before the sending the data operation request of any first user to the second user in the user group to the MediaProvider, the method further includes:
determining that the first user has access rights to the data object of the second user.
In a possible embodiment, if the first user does not have access right to the data object of the second user, a prompt message for operating the data object without right is output.
In one possible embodiment, determining the access right of the first user to the second user includes:
displaying an authority setting interface;
and determining the access authority of the first user to the second user based on the user operation aiming at the first user and the second user in the authority setting interface.
In a possible implementation manner, the access right of the first user to the second user comprises a picture library of the instant messaging tool of the second user or a picture library of a picture application of the second user.
In one possible embodiment, the method further comprises:
deleting the user group in response to an revocation request to revoke the user group; and the number of the first and second electrodes,
after restarting the terminal device, respectively creating corresponding MediaProvider, connection and Fuse processes for each user.
In a second aspect, the present application provides a terminal device, comprising:
a display, a processor, and a memory;
the display is used for displaying the two-dimensional code;
the memory to store the processor-executable instructions;
the processor is configured to execute the instructions to implement the data sharing method as described in any of the first aspects above.
In a third aspect, the present application provides a computer-readable storage medium, wherein instructions, when executed by a terminal device, enable the terminal device to perform the data sharing method according to any one of the first aspect.
In a fourth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements a data sharing method as described in any one of the first aspects above.
The technical scheme provided by the embodiment of the application at least has the following beneficial effects:
in the embodiment of the application, a page is created by displaying a user group; based on the user operation of creating the page in the user group, obtaining a plurality of users input by the user; and then merging the 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, thereby realizing the data sharing of the pair in the same user group, the Fuse system and the designated users in the multi-user system.
Additional features and advantages of the application will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the application. The objectives and other advantages of the application may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the embodiments of the present application will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic flowchart of independent data access by each user according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a terminal device according to an embodiment of the present application;
fig. 3 is a block diagram of a software structure of a terminal device according to an embodiment of the present disclosure;
fig. 4 is a schematic view of an application scenario provided in an embodiment of the present application;
fig. 5 is a schematic flowchart of a data sharing method according to an embodiment of the present application;
FIG. 6 is a schematic diagram of creating multiple users according to an embodiment of the present disclosure;
FIG. 7 is a schematic diagram of a user group creation page provided in an embodiment of the present application;
FIG. 8 is a block diagram illustrating an architecture for managing data sharing among designated users according to an embodiment of the present disclosure;
fig. 9 is a schematic flow chart of creating a shared MediaProvider according to an embodiment of the present application;
fig. 10 is a schematic flowchart illustrating data sharing among multiple users according to an embodiment of the present application;
fig. 11 is a schematic diagram of a permission setting page provided in an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. The embodiments described are some, but not all embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Also, in the description of the embodiments of the present application, "/" indicates or means, for example, a/B may indicate a or B; "and/or" in the text is only an association relationship describing an associated object, and means that three relationships may exist, for example, a and/or B may mean: three cases of a alone, a and B both, and B alone exist, and in addition, "a plurality" means two or more than two in the description of the embodiments of the present application.
The terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as implying or implying relative importance or otherwise implying any number of technical features indicated. Thus, a feature defined as "first," "second," or "second" may explicitly or implicitly include one or more of that feature, and in the description of embodiments of the application, "a plurality" means two or more unless stated otherwise.
Hereinafter, some terms in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.
1) The multi-user system comprises: multiple users may be supported using the system. Typically, the first user registered with the system is a system administrator user. The settings of different users are different, and the applications and application data installed by different users are also different. But the settings related to the hardware in the system are common, such as network settings, etc.
2) MediaProvider (media provider component): and uniformly scanning and controlling a system service of the media files in all directories of the system under the android system. The media herein includes pictures, videos, music, and the like.
3) Fuse (user space file system, file in Userspace): is a module in Linux (Uni-like x operating system, GNU/Linu x) for mounting some network spaces, such as SSH (Secure Shell), to a local file system, and related content can be found on SourceForge. The system has a simple API (Application Programming Interface) library, can be accessed by non-authorized users, can be safely implemented and has stability.
In the prior art, the same terminal equipment can support different users to use. To protect user data, android proposes Fuse (user space file system). In Fuse, data for each user is placed at the kernel level, managed and maintained by Fuse.
Referring to fig. 1, a schematic flow chart of independent access of data by each user is shown. A plurality of users are created on Android (Android) mobile phone equipment, including a user 1 and a user 2, but each user can only access own data, and currently, user data sharing based on a Fuse file system cannot be realized. As shown in fig. 1: the Android mobile phone comprises a user 1 and a user 2, wherein the user 1 is created at the earliest time, and then the user 1 is an administrator. The application data of the user 1 is stored in the data/user/0, and the application data of the user 2 is stored in the data/user/1. Two targets also exist in the Fuse system, wherein the storage/projected/0 corresponds to the data/user/0 of the user 1, and the storage/projected/2 corresponds to the data/user/1/of the user 2. User 1 corresponds to three components, namely MediaProvider1, connection1 and Fuse process 1, respectively, and user 2 corresponds to three main components, namely MediaProvider2, connection2 and Fuse process 2, respectively. User 1 realizes the operation of user 1 data through own MediaProvider1, connection1 and Fuse process 1, and similarly, user 2 realizes the data access to user 2 through MediaProvider2, connection2 and Fuse process 2. Fuse realizes the isolation of different users, but some special scenes such as a scene of sharing pictures are difficult to meet the requirements of the scene, so how to realize data sharing in a Fuse system is still to be solved.
In view of this, the present application provides a data sharing method, in which a user group concept is provided, and in a level of operating data in a Fuse system, a plurality of users operate with the identities of the user group, and different users are further divided in a user space, so that data sharing in the Fuse system can be realized within the same user group.
The inventive concept of the present application can be summarized as follows: in the embodiment of the application, a page is created by displaying a user group; based on the user operation of creating the page in the user group, obtaining a plurality of users input by the user; and then merging the plurality of users into the same user group, and authorizing the access right of the user space file system Fuse of any user in the user group to other users in the user group.
After the inventive concept of the present application is introduced, the terminal device provided in the present application will be described below. Fig. 2 shows a schematic structural diagram of a terminal device 200. It should be understood that the terminal apparatus 200 shown in fig. 2 is only an example, and the terminal apparatus 200 may have more or less components than those shown in fig. 2, may combine two or more components, or may have a different component configuration. 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.
A block diagram of a hardware configuration of a terminal device 200 according to an exemplary embodiment is exemplarily shown in fig. 2. 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.
The RF circuit 210 may be used for receiving and transmitting signals during information transmission and reception or during a call, and may receive downlink data of a base station and then send the downlink data to the processor 280 for processing; the uplink data may be transmitted to the base station. Typically, the RF circuitry 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.
The display unit 230 may be used to receive input numeric or character information and generate signal input related to user settings and function control of the terminal apparatus 200, and particularly, the display unit 230 may include a touch screen 231 disposed on the front surface of the terminal apparatus 100 and may collect touch operations of a user thereon or nearby, such as clicking a button, dragging a scroll box, and the like.
The display unit 230 may also be used to display information input by the user or information provided to the user and a Graphical User Interface (GUI) of various menus of the terminal apparatus 200. Specifically, the display unit 230 may include a display screen 232 disposed on the front surface 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 implement the input and output functions of the terminal device 200, and after the integration, the touch screen may be referred to as a touch display screen for short. The display unit 230 in this application can display the application programs and the corresponding operation steps.
The camera 240 may be used to capture still images or video. The object generates an optical image through the lens and projects the optical image to the photosensitive element. The photosensitive element may be a Charge Coupled Device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The light sensing elements convert the light signals into electrical signals which are then passed to a processor 280 for conversion into digital image signals.
The terminal device 200 may further comprise at least one sensor 250, such as an acceleration sensor 251, a distance sensor 252, a fingerprint sensor 253, a temperature sensor 254. The terminal device 200 may also be configured with other sensors such as a gyroscope, barometer, hygrometer, thermometer, infrared sensor, light sensor, motion sensor, and the like.
The audio circuitry 260, speaker 261, and microphone 262 may provide an audio interface between the user and the terminal device 200. The audio circuit 260 may transmit the electrical signal converted from the received audio data to the speaker 261, and convert the electrical signal into a sound signal by the speaker 261 and output the sound signal. The terminal device 200 may be further provided 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, converts the electrical signal into audio data after being received by the audio circuit 260, and then outputs the audio data to the RF circuit 210 to be transmitted to, for example, another terminal device, or outputs the audio data to the memory 220 for further processing.
Wi-Fi belongs to a short-distance wireless transmission technology, and the terminal device 200 can help a user to send and receive e-mails, browse webpages, access streaming media and the like through the Wi-Fi module 270, and provides wireless broadband internet access for the user.
The processor 280 is a control center of the terminal device 200, connects various parts of the entire terminal device using various interfaces and lines, and performs 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, processor 280 may include one or more processing units; the processor 280 may also integrate an application processor, which primarily handles operating systems, user interfaces, applications, etc., and a baseband processor, which primarily handles wireless communications. It will be appreciated that the baseband processor described above may not be integrated into the processor 280. The processor 280 may run an operating system, an application program, a user interface display, a touch response, and the data sharing method described in the embodiments of the present application. Further, the processor 280 is coupled with the display unit 230.
And the bluetooth module 281 is used for performing information interaction with other bluetooth devices having the bluetooth module through a bluetooth protocol. For example, the terminal device 200 may establish a bluetooth connection with a wearable electronic device (e.g., a smart watch) having a bluetooth module through the bluetooth module 281, so as to perform data interaction.
Fig. 3 is a block diagram of a software configuration of the terminal device 200 according to the embodiment of the present application.
The layered architecture divides the software into several layers, each layer having a clear role and division of labor. The layers communicate with each other through a software interface. In some embodiments, the Android system may be divided into four layers, an application layer, an application framework layer, an Android runtime (Android runtime) and system library, and a kernel layer, from top to bottom, respectively.
The application layer may include a series of application packages.
As shown in fig. 3, the application package may include applications such as camera, gallery, calendar, phone 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 application program of the application layer. The application framework layer includes a number of predefined functions.
As shown in FIG. 3, the application framework layers may include a window manager, content provider, view system, phone manager, resource manager, notification manager, and the like.
The window manager is used for managing window programs. The window manager can obtain the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.
The content provider is used to store and retrieve data and make it accessible to applications. The data may include video, images, audio, dialed and answered calls, browsing history and bookmarks, phone books, short messages, etc.
The view system includes visual controls such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying a picture.
The phone manager is used to provide a communication function of the terminal apparatus 200. Such as management of call status (including on, off, etc.).
The resource manager provides various resources, such as localized strings, icons, pictures, layout files, video files, etc., to the application.
The notification manager allows the application to display notification information (e.g., message digest of short message, message content) in the status bar, can be used to convey notification-type messages, and can automatically disappear after a short dwell without user interaction. Such as a notification manager used to inform download completion, message alerts, etc. The notification manager may also be a notification that appears in the form of a chart or scroll bar text at the top status bar of the system, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, text information is prompted in the status bar, a prompt tone is given, the terminal device vibrates, an indicator light flickers, and the like.
The Android Runtime comprises a core library and a virtual machine. The Android runtime is responsible for scheduling and managing an Android system.
The core library comprises two parts: one part is a function which needs to be called by java language, and the other part is a core library of android.
The application layer and the application framework layer run in a virtual machine. And executing java files of the application program layer and the application program framework layer into a binary file by the virtual machine. The virtual machine is used for performing the functions of object life cycle management, stack management, thread management, safety and exception management, garbage collection and the like.
The system library may include a plurality of functional modules. For example: surface managers (surface managers), Media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), and the like.
The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.
The media library supports a variety of commonly used audio, video format playback and recording, and still image files, among others. The media library may support a variety of audio-video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.
A 2D (an animation mode) graphics engine is a drawing engine for 2D drawing.
The kernel layer is a layer between hardware and software. The inner core layer at least comprises a display driver, a camera driver, an audio driver and a 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 household sign data acquisition device (such as a blood pressure monitor), a television, and the like.
Some brief descriptions are given below to application scenarios to which the technical solution of the embodiment of the present application can be applied, and it should be noted that the application scenarios described below are only used for describing the embodiment of the present application and are not limited. In specific implementation, the technical scheme provided by the embodiment of the application can be flexibly applied according to actual needs.
Fig. 4 is a schematic diagram illustrating an application scenario provided by an embodiment of the present application. The application scene graph comprises the following steps: user a, application 401, terminal device 402, application 403, user B. Wherein:
user a acquires data using application 401 and stores the data in terminal device 402 in the external storage of user a, and user B can access the data stored in the external storage of user a using application 403 at terminal device 401. For example, user a has installed the application 401 in the terminal device 402 and has taken a picture with the application 401, stored under the file directory of user a, and the application 403, which user B has installed in the terminal device 402, can view the picture.
Of course, the method provided in the embodiment of the present application is not limited to the application scenario shown in fig. 4, and may also be used in other possible application scenarios, and the embodiment of the present application is not limited. The functions that can be implemented by each device in the application scenario shown in fig. 4 will be described in the following method embodiments, and will not be described in detail herein.
To further illustrate the technical solutions provided by the embodiments of the present application, the following detailed description is made with reference to the accompanying drawings and the detailed description.
Referring to fig. 5, a schematic flowchart of a data sharing method provided in an embodiment of the present application is shown in fig. 5, where the method includes the following steps:
in step 501, a user group creation page is displayed.
In one possible embodiment, displaying the user group creation page first requires creating multiple users, as shown in FIG. 6, user 1 and user 2 are created, where user 1 was created first and user 1 is the administrator. Therefore, the application data of the user 1 is stored in the data/user/0, and the application data of the user 2 is stored in the data/user/1. Two directories also exist in the Fuse system, wherein the storage/organized/0 corresponds to the data/user/0 of the user 1, and the storage/organized/2 corresponds to the data/user/1/, of the user 2.
After creating the plurality of users, a user group selection function is preset on the device, and a user group creation page is displayed, as shown in fig. 7, where the created plurality of users can be displayed on the page. Then in step 502, a plurality of users input by the user is obtained based on the user operation of creating the page in the user group.
In a possible implementation manner, the user may select the user to share data in the user group creation interface, where the selection manner may be a touch screen selection according to a prompt, a button selection, or a manner of searching for a specific user, and this is not limited in the present application. As shown in fig. 7, the user selects user 1 and user 2 to share data by means of touch screen selection.
In step 503, the multiple users are merged into the same user group, and the access right of the user space file system Fuse of any user in the user group is granted to other users in the user group.
In one possible embodiment, the merging of the multiple users into the same user group may be implemented, as shown in fig. 7, in which the user selects user 1 and user 2 as the users sharing data in fig. 7, then clicks a button of creating the user group, displays a page indicating that the creating of the user group is successful, that is, merges user 1 and user 2 into the same user group, and then displays the user group 1 including user 1 and user 2 on the user group interface.
Referring to fig. 8, a schematic diagram of an architecture for managing data sharing among designated users according to an embodiment of the present application is provided. In fig. 8, user 1 and user 2 share one media provider component MediaProvider and share one Fuse process access right, and thus Data1 and Data2 of user 1 and user 2 are shareable to access. Therefore, sharing data among different users requires creating a common MediaProvider for the user group in which the user is located.
In a possible implementation manner, the data sharing method provided by the embodiment of the present application is not only applicable to sharing data by two users, but also applicable to multiple users such as three users and four users.
In a possible implementation manner, the access right of the Fuse of any user in the user group is authorized to other users in the user group, a common MediaProvider needs to be created for the user group, and a corresponding connection and Fuse process is created for each user, so that the information of each user is managed based on the connection and Fuse processes of each user.
In one possible implementation, creating a common MediaProvider for the user group may be specifically implemented as the steps shown in fig. 9:
in step 901, a master user is selected from the user group, and the remaining users are used as slave users.
Each user can be distinguished according to the unique identification of the user, and the unique identification of the user can be a user ID or a data ID.
In step 902, a MediaProvider is created for the master user.
In step 903, for any slave user in the user group, the user group in which the slave user is located is queried before the MediaProvider of the slave user is created.
Wherein, the user group in which the slave user is located can be queried according to the unique identification of the slave user.
In step 904, if the user group in which the slave user is located is queried, the MediaProvider of the master user is bound to the slave user.
In a possible implementation manner, after creating a common MediaProvider for the user group and creating a corresponding connection and Fuse process for each user, respectively, implementing data sharing may be implemented as: sending a data operation request of any first user in the user group to a second user to the MediaProvider, and storing the data operation request to a command queue to be executed of a connection of the second user by the MediaProvider; then, the Fuse process of the second user is used for obtaining the data operation request from the instruction queue to be executed and returning an execution result to a result queue of connection of the second user after the data operation request is executed. And querying the result queue of the connection of the second user by the MediaProvider to obtain an execution result. The execution result for the data operation request may then be returned by the MediaProvider to the user.
As shown in fig. 10: user 1 and user 2 share a MediaProvider, and user 1 corresponds to connection1 and Fuse process 1, and user 2 corresponds to connection2 and Fuse process 2. User 1 and user 2 realize sharing of user 1 data and user 2 data through MediaProvider, connection1 and Fuse process 1, and connection2 and Fuse process 2. The application of the user 1 wants to access storage/organized/2, first needs to send an operation request to the MediaProvider, establishes a Connection2 with the Fuse process by using the MediaProvider, and stores the operation request in a to-be-executed instruction queue of the Connection. Because the same MediaProvider is connected to Fuse, the MediaProvider can provide the application with access to the storage/organized/2 data and the storage/organized/0 data. Therefore, shared access of applications under different users to storage/organized/0 and storage/organized/2 is achieved.
In one possible embodiment, the data content shared by the same user group, i.e. shared to other users, is limited. For example, only pictures of the instant messenger of user 2 may be authorized for user 1 to access at the time of authorization. In order to realize the limitation of the access right, the data object of the operation is saved in the data operation request in the embodiment of the application. Before sending a data operation request of any first user to a second user in the user group to the MediaProvider, it is further required to determine that the first user has an access right to the data object of the second user. And if the first user does not have the access right to the data object of the second user, outputting prompt information for operating the data object without the right.
In a possible embodiment, determining the access right of the first user to the second user may be implemented as: firstly, displaying an authority setting interface to a user; then, based on user operations for the first user and the second user in the permission setting interface, the access permission of the first user to the second user is determined.
As shown in fig. 11, in the authority setting interface of fig. 11, a user may determine the access authority of the first user to the second user according to a prompt. The second user can select to approve or disapprove the access of the first user to the second user by means of a touch screen or keys.
In a possible implementation manner, the access right of the first user to the second user comprises a picture library of the instant messaging tool of the second user or a picture library of a picture application of the second user. Thus, the first user can only access some of the information in the picture library of the second user, and cannot access other information. The requirement of sharing pictures among different users can be met, and other privacy information of the users can be protected.
In a possible implementation manner, if the first user finishes accessing the data of the second user, a revocation request may also be issued, and the device deletes the user group in response to the revocation request of the user group; and, because the user group is deleted, after restarting the terminal device, respectively creating corresponding MediaProvider, connection and Fuse processes for each user. Thus, the first user and the second user no longer share data.
Based on the foregoing description, in the embodiments of the present application, a page is created by displaying a user group; based on the user operation of creating the page in the user group, obtaining a plurality of users input by the user; and then merging the 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, thereby realizing the data sharing of the pair in the same user group, the Fuse system and the designated users in the multi-user system.
The embodiments provided in the present application are only a few examples of the general concept of the present application, and do not limit the scope of the present application. Any other embodiments extended according to the scheme of the present application without inventive efforts will be within the scope of protection of the present application for a person skilled in the art.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such 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 intended to include such modifications and variations as well.
Claims (10)
1. A method for data sharing, the method comprising:
displaying a user group creation page;
obtaining a plurality of users input by the users based on the user operation of creating the page in the user group;
merging the 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.
2. The method of claim 1, wherein the granting the access right of the Fuse of any user in the user group to other users in the user group comprises:
establishing a shared media provider component Mediaprovider for the user group, and respectively establishing a corresponding connection component and a Fuse process for each user;
the method further comprises the following steps:
sending a data operation request of any first user in the user group to a second user to the MediaProvider, and storing the data operation request to a command queue to be executed of a connection of the second user by the MediaProvider; the Fuse process of the second user is used for acquiring the data operation request from the instruction queue to be executed, and returning an execution result to a result queue of connection of the second user after the data operation request is executed;
receiving an execution result returned by the MediaProvider for the data operation request, wherein the execution result is obtained by querying the MediaProvider from a result queue of the connection of the second user.
3. The method of claim 2, wherein creating a common MediaProvider for the user group comprises:
selecting a master user from the user group, and taking the rest users as slave users;
establishing a MediaProvider for the master user;
for any slave user in the user groups, inquiring the user group in which the slave user is positioned before creating the MediaProvider of the slave user;
and if the user group where the slave user is located is inquired, binding the MediaProvider of the master user to the slave user.
4. The method of claim 2, wherein the data object of the operation is saved in the data operation request;
before the sending the data operation request of any first user to the second user in the user group to the MediaProvider, the method further includes:
determining that the first user has access rights to the data object of the second user.
5. The method of claim 4, wherein if the first user does not have access to the data object of the second user, outputting a prompt for unauthorized operation of the data object.
6. The method of claim 4 or 5, wherein determining the access rights of the first user to the second user comprises:
displaying an authority setting interface;
and determining the access authority of the first user to the second user based on the user operation aiming at the first user and the second user in the authority setting interface.
7. The method of claim 6, wherein the access rights of the first user to the second user comprise a picture library of an instant messaging tool of the second user or a picture library of a picture application of the second user.
8. The method according to any one of claims 2-5, further comprising:
deleting the user group in response to an revocation request to revoke the user group; and the number of the first and second electrodes,
after restarting the terminal device, respectively creating corresponding MediaProvider, connection and Fuse processes for each user.
9. A terminal device, comprising:
a display, a processor, and a memory;
the display is used for displaying the two-dimensional code;
the memory to store the processor-executable instructions;
the processor is configured to execute the instructions to implement the data sharing method of any one of claims 1-8.
10. A computer-readable storage medium, comprising:
the instructions in the computer readable storage medium, when executed by the terminal device, enable the terminal device to perform the data sharing method of any one of claims 1-8.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111080481.8A CN113938890B (en) | 2021-09-15 | 2021-09-15 | Data sharing method and terminal equipment |
| CN202410294541.3A CN118400742A (en) | 2021-09-15 | 2021-09-15 | Data sharing method and terminal equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111080481.8A CN113938890B (en) | 2021-09-15 | 2021-09-15 | Data sharing method and terminal equipment |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410294541.3A Division CN118400742A (en) | 2021-09-15 | 2021-09-15 | Data sharing method and terminal equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113938890A true CN113938890A (en) | 2022-01-14 |
| CN113938890B CN113938890B (en) | 2024-04-30 |
Family
ID=79275899
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410294541.3A Pending CN118400742A (en) | 2021-09-15 | 2021-09-15 | Data sharing method and terminal equipment |
| CN202111080481.8A Active CN113938890B (en) | 2021-09-15 | 2021-09-15 | Data sharing method and terminal equipment |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410294541.3A Pending CN118400742A (en) | 2021-09-15 | 2021-09-15 | Data sharing method and terminal equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN118400742A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115129216A (en) * | 2022-06-29 | 2022-09-30 | 北京达美盛软件股份有限公司 | Cross-organization data configuration management method and system |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040039889A1 (en) * | 2002-08-20 | 2004-02-26 | Kevin Elder | Flexible remote data transfer and data synchronization |
| US20080208963A1 (en) * | 2006-10-19 | 2008-08-28 | Aviv Eyal | Online File Sharing |
| US20090254843A1 (en) * | 2008-04-05 | 2009-10-08 | Social Communications Company | Shared virtual area communication environment based apparatus and methods |
| US20150180914A1 (en) * | 2013-12-24 | 2015-06-25 | Dropbox, Inc. | Systems and methods for creating shared virtual spaces |
| CN105975876A (en) * | 2016-06-29 | 2016-09-28 | 北京小米移动软件有限公司 | File sharing method and device |
| CN106970978A (en) * | 2017-03-28 | 2017-07-21 | 联想(北京)有限公司 | Data sharing method and device |
| CN108196899A (en) * | 2017-12-07 | 2018-06-22 | 青岛海信移动通信技术股份有限公司 | A kind of method and device of the establishment of multi-user |
| US20180322137A1 (en) * | 2015-12-15 | 2018-11-08 | Hitachi Vantara Corporation | Team folder conversion and management |
| WO2020168692A1 (en) * | 2019-02-22 | 2020-08-27 | 全球能源互联网研究院有限公司 | Mass data sharing method, open sharing platform and electronic device |
| CN112464208A (en) * | 2020-11-25 | 2021-03-09 | 努比亚技术有限公司 | File access method, mobile terminal and computer readable storage medium |
| US20210089671A1 (en) * | 2019-09-20 | 2021-03-25 | International Business Machines Corporation | Credentials for consent based file access |
| CN112825072A (en) * | 2019-11-21 | 2021-05-21 | 青岛海信移动通信技术股份有限公司 | Communication terminal and data sharing method |
-
2021
- 2021-09-15 CN CN202410294541.3A patent/CN118400742A/en active Pending
- 2021-09-15 CN CN202111080481.8A patent/CN113938890B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040039889A1 (en) * | 2002-08-20 | 2004-02-26 | Kevin Elder | Flexible remote data transfer and data synchronization |
| US20080208963A1 (en) * | 2006-10-19 | 2008-08-28 | Aviv Eyal | Online File Sharing |
| US20090254843A1 (en) * | 2008-04-05 | 2009-10-08 | Social Communications Company | Shared virtual area communication environment based apparatus and methods |
| US20150180914A1 (en) * | 2013-12-24 | 2015-06-25 | Dropbox, Inc. | Systems and methods for creating shared virtual spaces |
| US20180322137A1 (en) * | 2015-12-15 | 2018-11-08 | Hitachi Vantara Corporation | Team folder conversion and management |
| CN105975876A (en) * | 2016-06-29 | 2016-09-28 | 北京小米移动软件有限公司 | File sharing method and device |
| CN106970978A (en) * | 2017-03-28 | 2017-07-21 | 联想(北京)有限公司 | Data sharing method and device |
| CN108196899A (en) * | 2017-12-07 | 2018-06-22 | 青岛海信移动通信技术股份有限公司 | A kind of method and device of the establishment of multi-user |
| WO2020168692A1 (en) * | 2019-02-22 | 2020-08-27 | 全球能源互联网研究院有限公司 | Mass data sharing method, open sharing platform and electronic device |
| US20210089671A1 (en) * | 2019-09-20 | 2021-03-25 | International Business Machines Corporation | Credentials for consent based file access |
| CN112825072A (en) * | 2019-11-21 | 2021-05-21 | 青岛海信移动通信技术股份有限公司 | Communication terminal and data sharing method |
| CN112464208A (en) * | 2020-11-25 | 2021-03-09 | 努比亚技术有限公司 | File access method, mobile terminal and computer readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115129216A (en) * | 2022-06-29 | 2022-09-30 | 北京达美盛软件股份有限公司 | Cross-organization data configuration management method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN118400742A (en) | 2024-07-26 |
| CN113938890B (en) | 2024-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113032766B (en) | Application authority management method and device | |
| CN113836540B (en) | Method, apparatus, storage medium and program product for managing application rights | |
| CN113835569A (en) | Terminal device, quick start method for internal function of application and storage medium | |
| CN114020379B (en) | Terminal equipment, information feedback method and storage medium | |
| CN113835928A (en) | Application backup and recovery method, device, storage medium, and program product | |
| CN113938890B (en) | Data sharing method and terminal equipment | |
| CN114035870A (en) | Terminal device, application resource control method and storage medium | |
| CN112825072B (en) | Communication terminal and data sharing method | |
| CN111600862B (en) | User account management method and device | |
| CN113642010B (en) | Method for acquiring data of extended storage device and mobile terminal | |
| CN113496039B (en) | Authority management method and terminal | |
| CN113835889A (en) | Method for acquiring input event and related device | |
| CN114595203A (en) | File synchronization method based on dual systems, terminal device and storage medium | |
| CN114675786A (en) | Large-capacity storage mounting method, device, terminal and medium | |
| CN111163220B (en) | Display method, communication terminal and computer storage medium | |
| CN111159734A (en) | Communication terminal and multi-application data inter-access processing method | |
| CN112000411A (en) | Mobile terminal and display method of recording channel occupation information thereof | |
| CN114007202A (en) | Method for establishing binding relationship and related equipment | |
| CN114154180A (en) | Data sharing method and terminal equipment | |
| CN114911394B (en) | Terminal equipment and one-hand operation method | |
| CN115981576B (en) | Method for sharing data, electronic device and storage medium | |
| CN112312509A (en) | Mobile terminal and network access method thereof | |
| CN118467073A (en) | Data processing method and device | |
| CN115297467A (en) | Data domain switching method, device, terminal equipment and medium | |
| CN115146257A (en) | Terminal device, function screening method and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Country or region after: China Address after: 266071 Shandong city of Qingdao province Jiangxi City Road No. 11 Applicant after: Qingdao Hisense Mobile Communication Technology Co.,Ltd. Address before: 266071 Shandong city of Qingdao province Jiangxi City Road No. 11 Applicant before: HISENSE MOBILE COMMUNICATIONS TECHNOLOGY Co.,Ltd. Country or region before: China |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |