CN113938890B - Data sharing method and terminal equipment - Google Patents

Data sharing method and terminal equipment Download PDF

Info

Publication number
CN113938890B
CN113938890B CN202111080481.8A CN202111080481A CN113938890B CN 113938890 B CN113938890 B CN 113938890B CN 202111080481 A CN202111080481 A CN 202111080481A CN 113938890 B CN113938890 B CN 113938890B
Authority
CN
China
Prior art keywords
user
data
users
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.)
Active
Application number
CN202111080481.8A
Other languages
Chinese (zh)
Other versions
CN113938890A (en
Inventor
张亚芹
荆楠楠
孙哲
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hisense Mobile Communications Technology Co Ltd
Original Assignee
Hisense Mobile Communications Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hisense Mobile Communications Technology Co Ltd filed Critical Hisense Mobile Communications Technology Co Ltd
Priority to CN202111080481.8A priority Critical patent/CN113938890B/en
Publication of CN113938890A publication Critical patent/CN113938890A/en
Application granted granted Critical
Publication of CN113938890B publication Critical patent/CN113938890B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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; 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 equipment
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 device can support different users. To protect user data, android proposes Fuse (FILESYSTEM INUSERSPACE, user space file system). In the Fuse, data of each user is placed in the kernel layer, and management and maintenance are performed by the Fuse.
For example, a plurality of users including user 1 and user 2 are created on an Android (Android) mobile phone device, but each user can only access own data, and user data sharing based on a Fuse file system cannot be realized at present.
Disclosure of Invention
The application aims to provide a data sharing method and terminal equipment, which are used for solving the problem that user data sharing based on a 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:
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.
In a possible implementation manner, the authorizing the Fuse access right of any user in the user group to other users in the user group includes:
creating a common media provider component MediaProvider for the group of users, and creating a corresponding connection component connection and Fuse process for each user respectively;
The method further comprises the steps of:
transmitting a data operation request of any first user to a second user in the user group to the MediaProvider, and storing the data operation request to a to-be-executed instruction queue of 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 to-be-executed instruction queue, executing the data operation request, and then returning an execution result to a connection result queue of the second user;
And receiving an execution result returned by MediaProvider for the data operation request, wherein the execution result is obtained by querying a result queue of connection of the second user by MediaProvider.
In one possible implementation, creating a common MediaProvider for the group of users includes:
selecting one master user from the user group, and taking the rest users as slave users;
Creating MediaProvider for the primary user;
For any slave user in the user group, querying the user group in which the slave user is located before creating MediaProvider of the slave user;
If the user group where the slave user is located is queried, mediaProvider of the master user is bound to the slave user.
In one possible implementation, the data object of the operation is saved in the data operation request;
Before the data operation request of any first user in the user group to the second user is sent to MediaProvider, the method further includes:
Determining that the first user has access to the data object of the second user.
In one possible implementation, if the first user does not have access to the data object of the second user, a prompt for unauthorized operation of the data object is output.
In a possible implementation manner, determining the access right of the first user to the second user includes:
displaying a permission setting interface;
Based on user operations for the first user and the second user in the permission setting interface, access permissions of the first user to the second user are determined.
In one possible implementation, the access right of the first user to the second user includes a photo library of an instant messaging tool of the second user or a photo library of a photo application of the second user.
In one possible embodiment, the method further comprises:
deleting the user group in response to a revocation request to revoke the user group; and is combined with the other components of the water treatment device,
After restarting the terminal device, a corresponding MediaProvider, connection and Fuse process is created for each user, respectively.
In a second aspect, the present application provides a terminal device, including:
a display, a processor, and a memory;
The display is used for displaying the two-dimensional code;
the memory is configured to store the processor-executable instructions;
the processor is configured to execute the instructions to implement the data sharing method of any of the first aspects above.
In a third aspect, the present application provides a computer readable storage medium, which when executed by a terminal device, causes the terminal device to perform the data sharing method as in any of the first aspects above.
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 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, the page is created by displaying the 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 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, so that the data sharing in the same user group, the data sharing in the Fuse system and the data sharing among specified users in the multi-user system can be realized.
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 practice of the application. The objectives and other advantages of the application will be realized and attained by the structure particularly pointed out in the written description and claims thereof 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 that are needed 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 other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic flow chart of independent access of data 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 software structure block diagram of a terminal device according to an embodiment of the present application;
fig. 4 is a schematic view of an application scenario provided in an embodiment of the present application;
fig. 5 is a schematic flow chart 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 application;
FIG. 7 is a schematic diagram of a user group creation page according to an embodiment of the present application;
FIG. 8 is a schematic diagram of a data sharing management architecture between designated users according to an embodiment of the present application;
FIG. 9 is a schematic flow chart of creating common MediaProvider according to an embodiment of the present application;
fig. 10 is a schematic flow chart of multi-user sharing data according to an embodiment of the present application;
Fig. 11 is a schematic diagram of a permission setting page according to 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 more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Wherein the described embodiments are some, but not all embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Also, in the description of the embodiments of the present application, unless otherwise indicated, "/" means or, for example, A/B may represent A or B; the text "and/or" is merely an association relation describing the associated object, meaning that there may be three relations, e.g., a and/or B, may represent: the three cases where a exists alone, a and B exist together, and B exists alone, and furthermore, in the description of the embodiments of the present application, "plural" means two or more than two.
The terms "first", "second" are used in the following description for descriptive purposes only and are not to be construed as implying or implying a relative importance or implying that the number of technical features is indicated. Thus, a feature defining "a first", "a second", or "a second" may include one or more such feature explicitly or implicitly, and in the description of embodiments of the application, the meaning of "a plurality" is two or more, unless otherwise indicated.
In the following, some terms in the embodiments of the present application are explained for easy understanding by those skilled in the art.
1) Multi-user system: multiple users may be supported to use the system. Typically, the first user registered in the system is a system administrator user. The settings of different users are different from each other, and the applications and application data installed by different users are also different. But hardware-related settings in the system are common, such as network settings, etc.
2) MediaProvider (media provider component): and uniformly scanning and controlling one system service of the media files in all catalogues of the system under the android system. Media here includes pictures, video, music, etc.
3) Fuse (user space file system, FILESYSTEM IN Userspace): is a module in Linux (Uni-like operating system, GNU/Linu ×) for mounting certain network spaces, such as SSH (Secure Shell protocol), to a local file system, and related content can be found on SourceForge. The system has a simple API (application program interface, application Programming Interface) library, can be accessed by non-privileged 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 (FILESYSTEMIN USERSPACE, user space file system). In the Fuse, data of each user is placed in the kernel layer, and management and maintenance are performed by the Fuse.
Referring to fig. 1, a schematic flow chart of individual user independent access to data is shown. A plurality of users including user 1 and user 2 are created on Android (Android) mobile phone equipment, but each user can only access own data, and user data sharing based on a Fuse file system cannot be realized at present. As shown in fig. 1: the Android mobile phone comprises a user 1 and a user 2, wherein the user 1 is created earliest, and the user 1 is an administrator. 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/0. There are also two goals in the Fuse system, where store/emulated/0 corresponds to user 1's data/user/0 and store/emulated/2 corresponds to user 2's data/user/1/. User 1 corresponds to three components MediaProvider, connection1, and Fuse process 1, respectively, and user 2 corresponds to three main components MediaProvider, connection2, and Fuse process 2, respectively. User 1 realizes the operation to user 1 data through its own MediaProvider, connection1 and Fuse process 1, and similarly, user 2 realizes the data access to user 2 through MediaProvider, connection2 and Fuse process 2. Fuse achieves isolation of different users, but some special scenes such as scenes sharing pictures are difficult for Fuse to meet the scene requirement, so how to achieve data sharing in the Fuse system is to be solved.
In view of this, the present application provides a data sharing method, in which a user group concept is provided, in the aspect of operating data in a Fuse system, a plurality of users operate with identities of the user group, and different users are subdivided in a user space, so that data sharing in the same user group and in the Fuse system can be realized.
The inventive concept of the present application can be summarized as follows: in the embodiment of the application, the page is created by displaying the 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 combining the plurality of 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.
After the inventive concept of the present application is introduced, the terminal device provided by the present application will be described. Fig. 2 shows a schematic structure of a terminal device 200. It should be understood that the terminal device 200 shown in fig. 2 is only one example, and that the terminal device 200 may have more or fewer components than shown in fig. 2, may combine two or more components, or may have a different configuration of components. 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 hardware configuration block diagram of the terminal device 200 in accordance with an exemplary embodiment is illustrated in fig. 2. As shown in fig. 2, the terminal device 200 includes: radio Frequency (RF) circuitry 210, memory 220, display unit 230, camera 240, sensor 250, audio circuitry 260, wireless fidelity (WIRELESS FIDELITY, wi-Fi) module 270, processor 280, bluetooth module 281, and power supply 290.
The RF circuit 210 may be configured to receive and transmit signals during the process of receiving and transmitting information or communication, and may receive downlink data from the base station and then send the downlink data to the processor 280 for processing; uplink data may be sent to the base station. Typically, RF circuitry includes, but is not limited to, antennas, at least one amplifier, transceivers, couplers, low noise amplifiers, diplexers, and the like.
Memory 220 may be used to store software programs and data. The processor 280 performs various functions of the terminal device 200 and data processing by running software programs or data stored in the memory 220. Memory 220 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device. The memory 220 stores an operating system that enables the terminal device 200 to operate. The memory 220 may store an operating system and various application programs, and may also store program codes for performing the methods of embodiments of the present application.
The display unit 230 may be used to receive input digital or character information, generate signal inputs related to user settings and function controls of the terminal device 200, and in particular, the display unit 230 may include a touch screen 231 provided at the front of the terminal device 100, and may collect touch operations on or near the user, such as clicking buttons, dragging scroll boxes, and the like.
The display unit 230 may also be used to display information input by a user or information provided to the user and a graphical user interface (GRAPHICAL USER INTERFACE, GUI) of various menus of the terminal device 200. Specifically, the display unit 230 may include a display 232 provided on the front surface of the terminal device 200. The display 232 may be configured in the form of a liquid crystal display, light emitting diodes, or the like.
The touch screen 231 may cover 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 simply referred to as a touch display screen. The display unit 230 may display the application program and the corresponding operation steps in the present application.
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 onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive elements convert the optical signals to electrical signals, which are then transferred to the processor 280 for conversion to 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 gyroscopes, barometers, hygrometers, thermometers, infrared sensors, light sensors, motion sensors, and the like.
Audio circuitry 260, speaker 261, microphone 262 may provide an audio interface between a user and terminal device 200. The audio circuit 260 may transmit the received electrical signal converted from audio data to the speaker 261, and the electrical signal is converted into a sound signal by the speaker 261 to be output. The terminal device 200 may 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, which is output to the RF circuit 210 for transmission to, for example, another terminal device, or to the memory 220 for further processing.
Wi-Fi belongs to a short-range wireless transmission technology, and the terminal device 200 can help a user to send and receive e-mail, browse web pages, access streaming media and the like through the Wi-Fi module 270, so that wireless broadband internet access is provided 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; processor 280 may also integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a baseband processor that 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 and a touch response, and a data sharing method according to the embodiments of the present application. In addition, the processor 280 is coupled with the display unit 230.
The bluetooth module 281 is configured to interact with other bluetooth devices having bluetooth modules 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) also provided with a bluetooth module through the bluetooth module 281, thereby performing data interaction.
The terminal device 200 also includes a power supply 290 (e.g., a battery) that provides power to the various components. The power supply may be logically connected to the processor 280 through a power management system, so that functions of managing charging, discharging, power consumption, etc. are implemented through the power management system. The terminal device 200 may also be configured with a power button for powering on and off the terminal device, and locking a screen.
Fig. 3 is a software configuration block diagram of the terminal device 200 of the embodiment of the present application.
The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system may be divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun rows (Android runtime) and system libraries, and a kernel layer, respectively.
The application layer may include a series of application packages.
As shown in fig. 3, the application package may include applications for cameras, gallery, calendar, phone calls, maps, navigation, WLAN, bluetooth, music, video, short messages, etc.
The application framework layer provides an application programming interface (application programming interface, API) and programming framework for the application of the application layer. The application framework layer includes a number of 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 for managing window programs. The window manager can acquire 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 such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, 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, a display interface including a short message notification icon may include a view displaying text and a view displaying a picture.
The telephony manager is used to provide the communication functions of the terminal device 200. Such as the management of call status (including on, hung-up, etc.).
The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.
The notification manager allows the application to display notification information (e.g., message digest of short message, message content) in a status bar, can be used to convey notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, 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, a text message is prompted in a status bar, a prompt tone is emitted, the terminal equipment vibrates, and an indicator light blinks.
Android run time includes a core library 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 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. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.
The system library may include a plurality of functional modules. For example: surface manager (surface manager), media Libraries (Media Libraries), three-dimensional graphics processing Libraries (e.g., openGL ES), 2D graphics engines (e.g., SGL), etc.
The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.
Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. 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 (one way of animation) 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 home sign data acquisition device (such as a blood pressure monitor), a television, and the like.
The following description is made for some simple descriptions of application scenarios applicable to the technical solution of the embodiment of the present application, and it should be noted that the application scenarios described below are only used for illustrating the embodiment of the present application, but not limiting. In the specific implementation, the technical scheme provided by the embodiment of the application can be flexibly applied according to actual needs.
Fig. 4 shows a schematic application scenario provided by the embodiment of the present application. The application scene graph comprises: user a, application 401, terminal device 402, application 403, user B. Wherein:
User a obtains data using application 401 and stores the data in external storage of user a in terminal device 402, and user B can access the data stored in 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 picture with application 401, stored under user a's file directory, and user B's application 403 installed in terminal device 402 can view the picture.
Of course, the method provided by the embodiment of the present application is not limited to the application scenario shown in fig. 4, but may 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 together in the following method embodiments, which are not described in detail herein.
In order to further explain the technical solution provided by the embodiments of the present application, the following details are described with reference to the accompanying drawings and the detailed description.
Referring to fig. 5, a flow chart of a data sharing method according to an embodiment of the present application is shown in fig. 5, and the method includes the following steps:
in step 501, a user group creation page is displayed.
In one possible implementation, displaying the user group creation page first requires creation of multiple users, as shown in FIG. 6, creating user 1 and user 2, where user 1 was created earliest, then user 1 is the administrator. Thus, user 1's application data is stored in data/user/0, and user 2's application data is stored in data/user/1/0. Two directories also exist in the Fuse system, where store/emulated/0 corresponds to user 1's data/user/0 and store/emulated/2 corresponds to user 2's data/user/1/.
After the plurality of users are created, a user group selection function is preset on the device, and a user group creation page is displayed, as shown in fig. 7, at which time the created plurality of users may be displayed on the page. Thereafter, in step 502, a plurality of users input by the user are obtained based on the user operation of creating a page at the user group.
In one possible implementation manner, the user may select the user to share the data in the user group creation interface, and the selection manner may be selected according to a prompt touch screen, or may be selected by a key, or may be selected by searching for a designated user, which 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 combined 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, the multiple users are combined into the same user group, which may be implemented as shown in fig. 7, where the user selects user 1 and user 2 as users sharing data in fig. 7, then clicks a button for creating the user group, displays a page prompting that the user group is successfully created, i.e., combines user 1 and user 2 into the same user group, and then displays user group 1 including user 1 and user 2 on an interface of the user group.
Referring to fig. 8, an architecture diagram of data sharing management between designated users according to an embodiment of the present application is provided. In fig. 8, user 1 and user 2 share a media provider component MediaProvider, share a Fuse process access right, so that Data1 and Data2 of user 1 and user 2 are shared accessible. It follows that sharing data between different users requires creating a common MediaProvider for the group of users where the users are located.
In a possible implementation manner, taking two users to share data as an example, the data sharing method provided by the embodiment of the application is not only applicable to two users to share data, but also applicable to multiple users such as three users, four users and the like.
In one possible implementation, the Fuse access right of any user in the user group is authorized to other users in the user group, so that common MediaProvider needs to be created for the user group, and a corresponding connection process and a Fuse process are created for each user respectively so as to manage information of each user based on the connection process and the Fuse process of each user.
In a possible implementation manner, the common MediaProvider is created for the user group, and may be specifically implemented as the steps shown in fig. 9:
in step 901, a master user is selected from the group of users, the remaining users being 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, mediaProvider is created for the primary user.
In step 903, the user group in which the slave user is located is queried for any slave user in the user group before creating MediaProvider of the slave users.
Wherein the user group where the slave user is located can be queried according to the unique identification of the slave user.
If the user group of the slave user is queried in step 904, the MediaProvider of the master user is bound to the slave user.
In one possible implementation, after creating a common MediaProvider for the user group and creating a corresponding connection and Fuse process for each user, the implementation of data sharing may be implemented as follows: transmitting a data operation request of any first user to a second user in the user group to the MediaProvider, and storing the data operation request to a to-be-executed instruction queue of connection of the second user by the MediaProvider; and then, the Fuse process of the second user is used for acquiring the data operation request from the to-be-executed instruction queue and returning an execution result to a connection result queue of the second user after the data operation request is executed. MediaProvider obtaining an execution result from the query in the result queue of the connection of the second user. Thereafter, the result of the execution of the data operation request may be returned by MediaProvider to the user.
As shown in fig. 10: user 1 and user 2 share one 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 share user 1 data and user 2 data through MediaProvider, connection and Fuse process 1, and connection2 and Fuse process 2. The application of the user 1 wants to access storage/emulated/2, firstly, an operation request needs to be sent to MediaProvider, connection2 is established by MediaProvider and a Fuse process, and the operation request is stored in a to-be-executed instruction queue of the Connection. Because it is MediaProvider that the connection is established with the Fuse, this MediaProvider can provide applications with access to torage/emulated/0 and storage/emulated/2 data. Thereby realizing the shared access of the application to the storage/emulated/0 and the storage/emulated/2 under different users.
In one possible implementation, the part of the data content shared by the same user group, i.e. the data content shared to other users, is limited. For example, only the picture of the instant messaging tool of user 2 may be authorized for access by user 1 at the time of authorization. In order to realize the limitation of access rights, the data object of the save operation in the data operation request in the embodiment of the application. Before sending a data operation request from any first user in the user group to a second user to MediaProvider, it is further required to determine that the first user has access 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 implementation manner, determining the access right of the first user to the second user may be implemented as: firstly, displaying a permission setting interface to a user; then, based on user operations for the first user and the second user in the rights setting interface, access rights of the first user to the second user are determined.
As shown in fig. 11, in the rights setting interface of fig. 11, a user may determine an access right of the first user to the second user according to a prompt. Wherein the second user can choose to agree or disagree with the first user's access to the second user by means of a touch screen or a key.
In one possible implementation, the access right of the first user to the second user includes a photo library of an instant messaging tool of the second user or a photo library of a photo application of the second user. Thus, the first user can only access information in some of the second user's photo libraries, 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 can be further sent out, 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, respectively. Thus, the first user and the second user no longer share data.
Based on the previous description, the embodiment of the application creates a page by displaying the 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 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, so that the data sharing in the same user group, the data sharing in the Fuse system and the data sharing among specified users in the multi-user system can be realized.
The above-provided detailed description is merely a few examples under the general inventive concept and does not limit the scope of the present application. Any other embodiments which are extended according to the solution of the application without inventive effort fall within the scope of protection of the application for a person skilled in the art.
It will be appreciated by those skilled in the art that 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 flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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 modifications and variations can be made to the present application without departing from the spirit or scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims (9)

1. A method of data sharing, the method comprising:
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; the user creates a page in the user group to select the users needing to share the data, wherein the selection modes comprise: selecting according to a prompt touch screen, selecting by means of a key, and selecting by means of searching a designated user;
Combining the plurality of 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 authorizing the access authority of the Fuse of any user in the user group to other users in the user group includes: creating a common media provider component MediaProvider for the group of users, and creating a corresponding connection component connection and Fuse process for each user respectively;
The method further comprises the steps of: transmitting a data operation request of any first user to a second user in the user group to the MediaProvider, and storing the data operation request to a to-be-executed instruction queue of 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 to-be-executed instruction queue, executing the data operation request, and then returning an execution result to a connection result queue of the second user; and receiving an execution result returned by MediaProvider for the data operation request, wherein the execution result is obtained by querying a result queue of connection of the second user by MediaProvider.
2. The method of claim 1, wherein creating a common MediaProvider for the group of users comprises:
selecting one master user from the user group, and taking the rest users as slave users;
Creating MediaProvider for the primary user;
For any slave user in the user group, querying the user group in which the slave user is located before creating MediaProvider of the slave user;
If the user group where the slave user is located is queried, mediaProvider of the master user is bound to the slave user.
3. The method of claim 1, wherein the data object of the operation is saved in the data operation request;
Before the data operation request of any first user in the user group to the second user is sent to MediaProvider, the method further includes:
Determining that the first user has access to the data object of the second user.
4. A method according to claim 3, wherein if the first user does not have access to the data object of the second user, a prompt for unauthorized manipulation of the data object is output.
5. The method of claim 3 or 4, wherein determining the access rights of the first user to the second user comprises:
displaying a permission setting interface;
Based on user operations for the first user and the second user in the rights setting interface, access rights of the first user to the second user are determined.
6. The method of claim 5, wherein the first user's access rights 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.
7. The method according to any one of claims 1-4, further comprising:
deleting the user group in response to a revocation request to revoke the user group; and is combined with the other components of the water treatment device,
After restarting the terminal device, a corresponding MediaProvider, connection and Fuse process is created for each user, respectively.
8. A terminal device, comprising:
a display, a processor, and a memory;
The display is used for displaying the two-dimensional code;
the memory is configured to store the processor-executable instructions;
the processor is configured to execute the instructions to implement the data sharing method of any of claims 1-7.
9. A computer-readable storage medium, comprising:
The instructions in the computer-readable storage medium, when executed by a terminal device, enable the terminal device to perform the data sharing method as claimed in any one of claims 1-7.
CN202111080481.8A 2021-09-15 2021-09-15 Data sharing method and terminal equipment Active CN113938890B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111080481.8A CN113938890B (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

Publications (2)

Publication Number Publication Date
CN113938890A CN113938890A (en) 2022-01-14
CN113938890B true CN113938890B (en) 2024-04-30

Family

ID=79275899

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111080481.8A Active CN113938890B (en) 2021-09-15 2021-09-15 Data sharing method and terminal equipment

Country Status (1)

Country Link
CN (1) CN113938890B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
CN112464208A (en) * 2020-11-25 2021-03-09 努比亚技术有限公司 File access method, mobile terminal and computer readable storage medium
CN112825072A (en) * 2019-11-21 2021-05-21 青岛海信移动通信技术股份有限公司 Communication terminal and data sharing method

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7047377B2 (en) * 2002-08-20 2006-05-16 Gruintine Pueche, Inc. System and method for conducting an auction-based ranking of search results on a computer network
US20080208963A1 (en) * 2006-10-19 2008-08-28 Aviv Eyal Online File Sharing
KR101527993B1 (en) * 2008-04-05 2015-06-10 소우셜 커뮤니케이션즈 컴퍼니 Shared virtual area communication environment based apparatus and methods
US20150180980A1 (en) * 2013-12-24 2015-06-25 Dropbox, Inc. Systems and methods for preserving shared virtual spaces on a content management system
US10956371B2 (en) * 2015-12-15 2021-03-23 Hitachi Vantara Llc Team folder conversion and management
US11106813B2 (en) * 2019-09-20 2021-08-31 International Business Machines Corporation Credentials for consent based file access

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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
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

Also Published As

Publication number Publication date
CN113938890A (en) 2022-01-14

Similar Documents

Publication Publication Date Title
CN113032766B (en) Application authority management method and device
CN113835569A (en) Terminal device, quick start method for internal function of application and storage medium
CN113835928A (en) Application backup and recovery method, device, storage medium, and program product
CN113836540A (en) Method, apparatus, storage medium, and program product for managing application rights
CN112825072B (en) Communication terminal and data sharing method
CN113938890B (en) Data sharing method and terminal equipment
CN113642010B (en) Method for acquiring data of extended storage device and mobile terminal
CN111600862B (en) User account management method and device
CN111163220B (en) Display method, communication terminal and computer storage medium
CN113496039A (en) Authority management method and terminal
CN114595203A (en) File synchronization method based on dual systems, terminal device and storage medium
CN111159734A (en) Communication terminal and multi-application data inter-access processing method
CN114675786A (en) Large-capacity storage mounting method, device, terminal and medium
CN114449171A (en) Method for controlling camera, terminal device, storage medium and program product
CN114035870A (en) Terminal device, application resource control method and storage medium
CN115132305A (en) Data sharing method, data verification method and terminal equipment
CN114007202A (en) Method for establishing binding relationship and related equipment
CN114154180A (en) Data sharing method and terminal equipment
CN114020379B (en) Terminal equipment, information feedback method and storage medium
CN114911394B (en) Terminal equipment and one-hand operation method
CN115981576B (en) Method for sharing data, electronic device and storage medium
CN111258699B (en) Page display method and communication terminal
CN112114885B (en) Terminal, control equipment and service processing method
CN111142648B (en) Data processing method and intelligent terminal
CN113835889A (en) Method for acquiring input event and related device

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