WO2022191455A1

WO2022191455A1 - Electronic device for performing file redaction, and operation method thereof

Info

Publication number: WO2022191455A1
Application number: PCT/KR2022/002139
Authority: WO
Inventors: 길영진; 서성종; 이우중; 김재욱
Original assignee: 삼성전자 주식회사
Priority date: 2021-03-10
Filing date: 2022-02-14
Publication date: 2022-09-15
Also published as: KR20220126903A

Abstract

Disclosed is an electronic device comprising a processor and a memory connected to the processor and storing instructions, wherein the instructions are configured to, when executed by the processor, cause the processor to, in response to a file generation request from an application: request a media provider to generate a file through a fuse, request a file system to generate the file through the media provider, generate the file through the file system, and store configuration information indicating the scope of sensitive information and access authority of the file in a metadata block and/or a designated area of the file. Various other embodiments understood through the specification are also possible.

Description

Electronic device performing file redaction and operating method thereof

Embodiments disclosed in this document relate to an electronic device that performs file redaction and an operating method thereof.

A user-space process can read a file through the kernel-space file system. In this case, if the process of the user area does not have access to the specific area of the file, file redaction may be performed on the specific area of the file. Here, the file redacting may refer to a function of processing data of a specific area among data of a file and providing it to a process.

For file redaction when reading a file, communication between processes, mode switching, a database for a file redaction area, or a combination thereof is required.

Accordingly, a database for communication between processes, switching of modes, and a file redaction area may cause overhead to the electronic device.

An electronic device according to an embodiment disclosed in this document includes a processor and a storage connected to the processor and storing instructions, and the instructions, when executed by the processor, cause the processor to In response to the file creation request: requesting a media provider to create a file via the first file system, requesting a second file system to create the file via the media provider, and via the second file system and create a file, and store setting information indicating access rights of the file and the scope of sensitive information in a designated area of the file and/or a metadata block of the storage.

In a method of operating an electronic device according to an embodiment disclosed in this document, in response to a file creation request from an application of the electronic device: a first file system of the electronic device sends a file to a media provider of the electronic device requesting creation, the media provider requesting the second file system of the electronic device to create the file, the second file system creating the file, and the second file system generating the file. The method may include storing setting information indicating the access right of the file and the range of sensitive information in a designated area of the file and/or in a metadata block of storage of the electronic device.

A non-transitory computer-readable recording medium according to an embodiment disclosed in this document, when executed by a processor, causes the processor to: in response to a file creation request from an application: to a media provider through a first file system request creation of a file, request creation of the file from a second file system through the media provider, create a file through the second file system, access right of the file, and scope of sensitive information It may include instructions for storing the indicated setting information in a designated area and/or meta data block of the file.

The technical problems to be achieved in the various embodiments of this document are not limited to the technical problems mentioned above, and other technical problems not mentioned are clear to those of ordinary skill in the art to which the present disclosure belongs from the description below. will be able to be understood

According to the embodiments disclosed in this document, an overhead for file redaction can be reduced when reading a file.

Effects that can be obtained in various embodiments of the present disclosure are not limited to the above-mentioned effects, and other effects not mentioned are clearly to those of ordinary skill in the art to which the present disclosure belongs from the description below. can be understood

1 is a block diagram of an electronic device in a network environment, according to various embodiments of the present disclosure.

2 is a diagram illustrating a configuration of an electronic device according to an embodiment of the present disclosure.

3A is a diagram illustrating a processing sequence of a file creation operation between components of an electronic device according to an embodiment of the present disclosure.

3B is a diagram illustrating a processing sequence of a file creation operation between a media provider, a file system, and a memory according to an embodiment of the present disclosure.

4 is a diagram illustrating a processing sequence of a file open operation between components of an electronic device according to an embodiment of the present disclosure.

5 is a diagram illustrating a processing sequence of a file read operation between components of an electronic device according to an embodiment of the present disclosure.

6 is a flowchart illustrating a file creation operation of the electronic device 101 according to an embodiment of the present disclosure.

7 is a flowchart illustrating a file open operation of the electronic device 101 according to an embodiment of the present disclosure.

8 is a flowchart illustrating a file read operation of the electronic device 101 according to an embodiment of the present disclosure.

In connection with the description of the drawings, the same or similar reference numerals may be used for the same or similar components.

1 is a block diagram of an electronic device 101 in a network environment 100 according to various embodiments of the present disclosure. Referring to FIG. 1 , in a network environment 100 , an electronic device 101 communicates with an electronic device 102 through a first network 198 (eg, a short-range wireless communication network) or a second network 199 . It may communicate with the electronic device 104 or the server 108 through (eg, a long-distance wireless communication network). According to an embodiment, the electronic device 101 may communicate with the electronic device 104 through the server 108 . According to an embodiment, the electronic device 101 includes a processor 120 , a memory 130 , an input module 150 , a sound output module 155 , a display module 160 , an audio module 170 , and a sensor module ( 176), interface 177, connection terminal 178, haptic module 179, camera module 180, power management module 188, battery 189, communication module 190, subscriber identification module 196 , or an antenna module 197 . In some embodiments, at least one of these components (eg, the connection terminal 178 ) may be omitted or one or more other components may be added to the electronic device 101 . In some embodiments, some of these components (eg, sensor module 176 , camera module 180 , or antenna module 197 ) are integrated into one component (eg, display module 160 ). can be

The processor 120, for example, executes software (eg, a program 140) to execute at least one other component (eg, a hardware or software component) of the electronic device 101 connected to the processor 120. It can control and perform various data processing or operations. According to an embodiment, as at least part of data processing or operation, the processor 120 stores a command or data received from another component (eg, the sensor module 176 or the communication module 190 ) into the volatile memory 132 . may be stored in , process commands or data stored in the volatile memory 132 , and store the result data in the non-volatile memory 134 . According to an embodiment, the processor 120 is a main processor 121 (eg, a central processing unit or an application processor) or a secondary processor 123 (eg, a graphic processing unit, a neural network processing unit) a neural processing unit (NPU), an image signal processor, a sensor hub processor, or a communication processor). For example, when the electronic device 101 includes the main processor 121 and the sub-processor 123 , the sub-processor 123 uses less power than the main processor 121 or is set to be specialized for a specified function. can The auxiliary processor 123 may be implemented separately from or as a part of the main processor 121 .

The secondary processor 123 may, for example, act on behalf of the main processor 121 while the main processor 121 is in an inactive (eg, sleep) state, or when the main processor 121 is active (eg, executing an application). ), together with the main processor 121, at least one of the components of the electronic device 101 (eg, the display module 160, the sensor module 176, or the communication module 190) It is possible to control at least some of the related functions or states. According to an embodiment, the auxiliary processor 123 (eg, image signal processor or communication processor) may be implemented as a part of another functionally related component (eg, camera module 180 or communication module 190). have. According to an embodiment, the auxiliary processor 123 (eg, a neural network processing device) may include a hardware structure specialized for processing an artificial intelligence model. Artificial intelligence models can be created through machine learning. Such learning may be performed, for example, in the electronic device 101 itself on which artificial intelligence is performed, or may be performed through a separate server (eg, the server 108). The learning algorithm may include, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning, but in the above example not limited The artificial intelligence model may include a plurality of artificial neural network layers. Artificial neural networks include deep neural networks (DNNs), convolutional neural networks (CNNs), recurrent neural networks (RNNs), restricted boltzmann machines (RBMs), deep belief networks (DBNs), bidirectional recurrent deep neural networks (BRDNNs), It may be one of deep Q-networks or a combination of two or more of the above, but is not limited to the above example. The artificial intelligence model may include, in addition to, or alternatively, a software structure in addition to the hardware structure.

The memory 130 may store various data used by at least one component (eg, the processor 120 or the sensor module 176 ) of the electronic device 101 . The data may include, for example, input data or output data for software (eg, the program 140 ) and instructions related thereto. The memory 130 may include a volatile memory 132 or a non-volatile memory 134 .

The program 140 may be stored as software in the memory 130 , and may include, for example, an operating system 142 , middleware 144 , or an application 146 .

The input module 150 may receive a command or data to be used by a component (eg, the processor 120 ) of the electronic device 101 from the outside (eg, a user) of the electronic device 101 . The input module 150 may include, for example, a microphone, a mouse, a keyboard, a key (eg, a button), or a digital pen (eg, a stylus pen).

The sound output module 155 may output a sound signal to the outside of the electronic device 101 . The sound output module 155 may include, for example, a speaker or a receiver. The speaker can be used for general purposes such as multimedia playback or recording playback. The receiver can be used to receive incoming calls. According to an embodiment, the receiver may be implemented separately from or as a part of the speaker.

The display module 160 may visually provide information to the outside (eg, a user) of the electronic device 101 . The display module 160 may include, for example, a control circuit for controlling a display, a hologram device, or a projector and a corresponding device. According to an embodiment, the display module 160 may include a touch sensor configured to sense a touch or a pressure sensor configured to measure the intensity of a force generated by the touch.

The audio module 170 may convert a sound into an electric signal or, conversely, convert an electric signal into a sound. According to an embodiment, the audio module 170 acquires a sound through the input module 150 , or an external electronic device (eg, a sound output module 155 ) connected directly or wirelessly with the electronic device 101 . The electronic device 102) (eg, a speaker or headphones) may output a sound.

The sensor module 176 detects an operating state (eg, power or temperature) of the electronic device 101 or an external environmental state (eg, a user state), and generates an electrical signal or data value corresponding to the sensed state. can do. According to an embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyro sensor, a barometric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an IR (infrared) sensor, a biometric sensor, It may include a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface 177 may support one or more specified protocols that may be used by the electronic device 101 to directly or wirelessly connect with an external electronic device (eg, the electronic device 102 ). According to an embodiment, the interface 177 may include, for example, a high definition multimedia interface (HDMI), a universal serial bus (USB) interface, an SD card interface, or an audio interface.

The connection terminal 178 may include a connector through which the electronic device 101 can be physically connected to an external electronic device (eg, the electronic device 102 ). According to an embodiment, the connection terminal 178 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

The haptic module 179 may convert an electrical signal into a mechanical stimulus (eg, vibration or movement) or an electrical stimulus that the user can perceive through tactile or kinesthetic sense. According to an embodiment, the haptic module 179 may include, for example, a motor, a piezoelectric element, or an electrical stimulation device.

The camera module 180 may capture still images and moving images. According to an embodiment, the camera module 180 may include one or more lenses, image sensors, image signal processors, or flashes.

The power management module 188 may manage power supplied to the electronic device 101 . According to an embodiment, the power management module 188 may be implemented as, for example, at least a part of a power management integrated circuit (PMIC).

The battery 189 may supply power to at least one component of the electronic device 101 . According to an embodiment, the battery 189 may include, for example, a non-rechargeable primary cell, a rechargeable secondary cell, or a fuel cell.

The communication module 190 is a direct (eg, wired) communication channel or a wireless communication channel between the electronic device 101 and an external electronic device (eg, the electronic device 102, the electronic device 104, or the server 108). It can support establishment and communication performance through the established communication channel. The communication module 190 may include one or more communication processors that operate independently of the processor 120 (eg, an application processor) and support direct (eg, wired) communication or wireless communication. According to an embodiment, the communication module 190 is a wireless communication module 192 (eg, a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 194 (eg, : It may include a local area network (LAN) communication module, or a power line communication module). A corresponding communication module among these communication modules is a first network 198 (eg, a short-range communication network such as Bluetooth, wireless fidelity (WiFi) direct, or infrared data association (IrDA)) or a second network 199 (eg, legacy It may communicate with the external electronic device 104 through a cellular network, a 5G network, a next-generation communication network, the Internet, or a computer network (eg, a telecommunication network such as a LAN or a WAN). These various types of communication modules may be integrated into one component (eg, a single chip) or may be implemented as a plurality of components (eg, multiple chips) separate from each other. The wireless communication module 192 uses subscriber information (eg, International Mobile Subscriber Identifier (IMSI)) stored in the subscriber identification module 196 within a communication network such as the first network 198 or the second network 199 . The electronic device 101 may be identified or authenticated.

The wireless communication module 192 may support a 5G network after a 4G network and a next-generation communication technology, for example, a new radio access technology (NR). NR access technology includes high-speed transmission of high-capacity data (eMBB (enhanced mobile broadband)), minimization of terminal power and access to multiple terminals (mMTC (massive machine type communications)), or high reliability and low latency (URLLC (ultra-reliable and low-latency) -latency communications)). The wireless communication module 192 may support a high frequency band (eg, mmWave band) to achieve a high data rate, for example. The wireless communication module 192 uses various techniques for securing performance in a high-frequency band, for example, beamforming, massive multiple-input and multiple-output (MIMO), all-dimensional multiplexing. It may support technologies such as full dimensional MIMO (FD-MIMO), an array antenna, analog beam-forming, or a large scale antenna. The wireless communication module 192 may support various requirements defined in the electronic device 101 , an external electronic device (eg, the electronic device 104 ), or a network system (eg, the second network 199 ). According to an embodiment, the wireless communication module 192 includes a peak data rate (eg, 20 Gbps or more) for realizing eMBB, loss coverage (eg, 164 dB or less) for realizing mMTC, or U-plane latency for realizing URLLC ( Example: Downlink (DL) and uplink (UL) each 0.5 ms or less, or round trip 1 ms or less) can be supported.

The antenna module 197 may transmit or receive a signal or power to the outside (eg, an external electronic device). According to an embodiment, the antenna module 197 may include an antenna including a conductor formed on a substrate (eg, a PCB) or a radiator formed of a conductive pattern. According to an embodiment, the antenna module 197 may include a plurality of antennas (eg, an array antenna). In this case, at least one antenna suitable for a communication method used in a communication network such as the first network 198 or the second network 199 is connected from the plurality of antennas by, for example, the communication module 190 . can be selected. A signal or power may be transmitted or received between the communication module 190 and an external electronic device through the selected at least one antenna. According to some embodiments, other components (eg, a radio frequency integrated circuit (RFIC)) other than the radiator may be additionally formed as a part of the antenna module 197 .

According to various embodiments, the antenna module 197 may form a mmWave antenna module. According to one embodiment, the mmWave antenna module comprises a printed circuit board, an RFIC disposed on or adjacent to a first side (eg, bottom side) of the printed circuit board and capable of supporting a designated high frequency band (eg, mmWave band); and a plurality of antennas (eg, an array antenna) disposed on or adjacent to a second side (eg, top or side) of the printed circuit board and capable of transmitting or receiving signals of the designated high frequency band. can do.

At least some of the components are connected to each other through a communication method between peripheral devices (eg, a bus, general purpose input and output (GPIO), serial peripheral interface (SPI), or mobile industry processor interface (MIPI)) and signal (eg commands or data) can be exchanged with each other.

According to an embodiment, the command or data may be transmitted or received between the electronic device 101 and the external electronic device 104 through the server 108 connected to the second network 199 . Each of the external

electronic devices

102 or 104 may be the same as or different from the electronic device 101 . According to an embodiment, all or part of the operations executed by the electronic device 101 may be executed by one or more external

electronic devices

102 , 104 , or 108 . For example, when the electronic device 101 needs to perform a function or service automatically or in response to a request from a user or other device, the electronic device 101 may perform the function or service itself instead of executing the function or service itself. Alternatively or additionally, one or more external electronic devices may be requested to perform at least a part of the function or the service. One or more external electronic devices that have received the request may execute at least a part of the requested function or service, or an additional function or service related to the request, and transmit a result of the execution to the electronic device 101 . The electronic device 101 may process the result as it is or additionally and provide it as at least a part of a response to the request. For this purpose, for example, cloud computing, distributed computing, mobile edge computing (MEC), or client-server computing technology may be used. The electronic device 101 may provide an ultra-low latency service using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 104 may include an Internet of things (IoT) device. The server 108 may be an intelligent server using machine learning and/or neural networks. According to an embodiment, the external electronic device 104 or the server 108 may be included in the second network 199 . The electronic device 101 may be applied to an intelligent service (eg, smart home, smart city, smart car, or health care) based on 5G communication technology and IoT-related technology.

2 is a diagram illustrating a configuration of an electronic device 101 according to an embodiment of the present disclosure. FIG. 2 may be described with reference to configurations of the electronic device 101 of FIG. 1 .

In an embodiment, the electronic device 101 is a program that may be executed by a processor (the processor 120 of FIG. 1 ), and includes an application 146 , a framework 210 , a kernel 230 , or a combination thereof. In an embodiment, the framework 210 may include a media provider 220. In an embodiment, the kernel 230 may include a file system in user space (FUSE) 240; may include file system 250. In one embodiment, the term 'fuse' refers to a program that enables a program running in user space to export a file system to kernel space. In an embodiment, a program that enables a program running in the user space to export a file system to the kernel space may be understood as a fuse 240. In an embodiment, the fuse 240 may include It is referred to as a first file system, and the file system 250 may also be referred to as a second file system.

In an embodiment, the application 146 and/or the framework 210 may refer to a program operating in a user space of the memory 130 (or virtual memory). In one embodiment, the application 146 , and/or the framework 210 may perform operations while the processor 120 is in user mode.

In an embodiment, the kernel 230 may refer to a program operating in a kernel space of the memory 130 (or virtual memory). In an embodiment, the kernel 230 may perform an operation while the processor 120 is in the kernel mode.

In an embodiment, when a program operating in the user area requests an operation from a program operating in the kernel area, the user mode may be switched to the kernel mode. In an embodiment, when a program operating in the kernel region provides a response to a request to a program operating in the user region, the kernel mode may be switched to the user mode.

In an embodiment, the application 146 may make a request to the fuse 240 and obtain a response to the request from the fuse 240 . In one embodiment, the application 146 may send and receive requests and/or responses directly to the fuse 240 . In one embodiment, the application 146 may indirectly send and receive requests and/or responses with the fuse 240 . For example, the application 146 may indirectly send and receive requests and/or responses to and from the fuse 240 through a virtual file system (VFS).

In an embodiment, the application 146 may perform an operation on a file through the fuse 240 . In an embodiment, the application 146 performs an operation of create, open, read, write, close, or a combination thereof through the fuse 240 . can do. In an embodiment, the file may include a photo, a video, or a combination thereof.

In an embodiment, the application 146 may generate a system call to request an operation on a file through the fuse 240 . In an embodiment, based on the system call, the processor 120 may change from the user mode to the kernel mode.

In one embodiment, fuse 240 forwards a request to media provider 220 based on a request from application 146 , and/or a designated area of memory 130 (eg, volatile memory 132 ). ) to process the request.

In an embodiment, the fuse 240 may transmit a request to the media provider 220 in the case of a file creation, open, and/or close request. In an embodiment, in the case of a file read and/or write request, the fuse 240 may access a designated area of the memory 130 (eg, the volatile memory 132 ) to process the request. In one embodiment, the fuse 240 reads the file by accessing a designated area (eg, the volatile memory 132) of the memory 130 based on information obtained from the file system 250 when the file is opened; and/or process write requests. In an embodiment, the information obtained from the file system 250 may include location and/or access information where the file is stored.

In one embodiment, the fuse 240 may identify the requested file's access right, sensitive information, scope, or a combination thereof. In an embodiment, the fuse 240 may identify the access right of the application 146 to the requested file. In an embodiment, the fuse 240 may identify whether the requested file includes sensitive information. In an embodiment, the fuse 240 may identify a range of an area in which sensitive information of the requested file is recorded on the memory 130 . In an embodiment, the sensitive information may include information based on an exchangeable image file format (EXIF). In an embodiment, the sensitive information may include a photographing location, a photographing time, a face tag, or a combination thereof.

In an embodiment, the fuse 240 may modify sensitive information of the requested file based on identifying the access right, sensitive information, scope, or a combination thereof of the requested file. In an embodiment, the fuse 240 may modify sensitive information of the requested file through the redaction filter 245 .

In an embodiment, the redaction filter 245 may modify the sensitive information of the requested file by changing the sensitive information to designated data (eg, 0 bit). In an embodiment, the redaction filter 245 may modify the sensitive information of the requested file by encrypting the sensitive information. In an embodiment, the redaction filter 245 may modify the sensitive information of the requested file by replacing the sensitive information with virtual information.

In an embodiment, the fuse 240 may provide a file in which sensitive information is modified to the application 146 .

In an embodiment, the media provider 220 may perform an operation on a file through the file system 250 based on a request from the fuse 240 . In one embodiment, the media provider 220 may generate a system call to request an operation on the file via the file system 250 based on a request from the fuse 240 . In an embodiment, the media provider 220 may perform an operation on the file through the file system 250 based on a request to create, open, and/or close the file from the fuse 240 .

In an embodiment, the media provider 220 may process a file creation, open, and/or close request through the file system 250 . In an embodiment, the media provider 220 may request the file system 250 to create, open, and/or close a file through a system call based on an input/output control function (eg, ioctl).

In an embodiment, the file system 250 may serve to organize files or data used in the application 146 . In an embodiment, the file system 250 may include a metadata block for identifying and managing data and a file data block for storing file data.

In an embodiment, the file system 250 includes a File Allocation Table (FAT), FAT32, NT File System (NTFS), Hierarchical File System (HFS), Journaled File System2 (JSF2), On-Disk Structure-ODS-5 (ODS). 5), UFS (Unix File System), ext2, ext3, ext4, or a file system of a combination thereof. In an embodiment, the storage 260 may be managed through a different file system 250 for each partition. In one embodiment, the storage 260 may correspond to the non-volatile memory 134 of the memory 130 .

In an embodiment, the file system 250 may allocate an area for storing a file in the storage 260 based on a file creation request. In one embodiment, file system 250 may store files in file data blocks of file system 250 . In an embodiment, the file system 250 may store meta information of a file in a meta data block and/or a file data block. In an embodiment, the meta information may include owner information of the file (eg, identification information of the application 146 ), access rights, a range of sensitive information, or a combination thereof.

In an embodiment, the file system 250 may check a location where the file is stored in the storage 260 based on the file open request. In an embodiment, the file system 250 may identify information (eg, a file descriptor) that can access the file based on the file open request. In an embodiment, the file system 250 may provide the location and/or access information where the file is stored to the media provider 220 . In an embodiment, the file system 250 may provide the location and/or access information where the file is stored to the fuse 240 . In an embodiment, the file system 250 may store the location and/or access information where the file is stored in the reference link of the fuse 240 .

In an embodiment, the file system 250 may read meta information of a file based on a request to open the file. In an embodiment, the file system 250 may identify the owner of the file based on meta information of the read file.

In an embodiment, the file system 250 transfers the meta information of the file stored in the meta data block and/or the file data block of the storage 260 to a designated area (eg: It can be loaded into the volatile memory 132 .

In an embodiment, the file system 250 may determine a file flag (eg, read only, write only, read write) based on a file open request.

Hereinafter, file creation, open, and read operations will be described with reference to FIGS. 3A, 3B, 4, and 5 .

3A is a diagram illustrating a processing sequence of a file creation operation between components of the electronic device 101 according to an embodiment of the present disclosure. 3B is a diagram illustrating a processing sequence of a file creation operation between the media provider 220 , the file system 250 , and the storage 260 according to an embodiment of the present disclosure. 3A and 3B may be described with reference to configurations of the electronic device 101 of FIG. 1 .

In an embodiment, in operation 310 , the application 146 may request the fuse 240 to create a file. In an embodiment, the application 146 may request the fuse 240 to create a file through a system call. In an embodiment, the file creation request may include identification information (eg, ID (identification)) of the application 146 .

In an embodiment, in operation 320 , the fuse 240 may request the media provider 220 to create a file. In an embodiment, the fuse 240 may fetch a file creation request to the media provider 220 .

In an embodiment, in operation 330 , the media provider 220 may request the file system 250 to create a file. In an embodiment, the media provider 220 may request the file system 250 to create a file through a system call. In one embodiment, the media provider 220 may provide the file system 250 with a file creation request including identification information of the application 146 , access rights of the file, sensitive information, scope, or a combination thereof. have.

In one embodiment, the media provider 220 may lock the file while creating the file.

In an embodiment, in operation 340 , the file system 250 may create the file 340 . In an embodiment, the file system 250 may store the file 340 in an area of the storage 260 managed by the file system 250 . In one embodiment, file system 250 may store file 340 in a file data block of storage 260 .

In an embodiment, the file system 250 may store meta information of the file 340 . In an embodiment, the file system 250 may store the meta information of the file 340 in a meta data block and/or a file data block of the file system 250 . In an embodiment, the meta information may include owner information of the file (eg, identification information of the application 146 ), access rights, a range of sensitive information, or a combination thereof.

In one embodiment, the file system 250 includes the owner information, the access right of the file 340 , and/or the scope of the

sensitive information

343 and 345 as an extended attribute of the metadata block of the storage 260 . may be stored in area 349 and/or file data blocks. In one embodiment, the file system 250 stores owner information, access rights of the file 340, and/or sensitive information in the last file data block 347 of the file data blocks 341 in which the file 340 is stored. A range of (343, 345) can be stored.

In an embodiment, in operation 350 , the file system 250 may provide a file creation result (eg, a file descriptor) to the media provider 220 .

In one embodiment, the media provider 220 may unlock the file 340 .

In an embodiment, in operation 360 , the media provider 220 may provide the fuse 240 with the file creation result. In an embodiment, in operation 370 , the fuse 240 may provide the application 146 with a file creation result.

4 is a diagram illustrating a processing sequence of a file open operation between components of the electronic device 101 according to an embodiment of the present disclosure. FIG. 4 may be described with reference to configurations of the electronic device 101 of FIG. 1 .

In an embodiment, in operation 410 , the application 146 may request the fuse 240 to open a file. In an embodiment, the application 146 may request the fuse 240 to open the file through a system call. In an embodiment, the file open request may include identification information (eg, a file path) of the file 340 .

In an embodiment, in operation 420 , the fuse 240 may request the media provider 220 to open the file 340 . In an embodiment, the fuse 240 may fetch a file open request to the media provider 220 . In an embodiment, the fuse 240 may transmit a file open request including the reference link 445 to the media provider 220 .

In an embodiment, in operation 430 , the media provider 220 may request the file system 250 to open the file 340 . In an embodiment, the media provider 220 may request the file system 250 to open the file 340 through a system call. In an embodiment, the media provider 220 sends a file open request including a file path of the file 340 and/or a flag (eg, read only, write only, or read write) to the file system 250 . can provide

In an embodiment, the file system 250 may identify a location where the file 340 is stored and/or access information based on an open request for the file 340 . In one embodiment, the file system 250 may store the location and/or access information where the file 340 is stored in the reference link 445 of the fuse 240 .

In an embodiment, the file system 250 may determine a flag (eg, read only, write only, read write) of the file 340 based on the open request of the file 340 .

In an embodiment, the file system 250 may read meta information of the file 340 based on an open request of the file 340 . In an embodiment, the file system 250 may identify an owner of the file 340 and/or an access right of the file 340 based on the meta information of the file 340 .

In an embodiment, the file system 250 stores the meta data block and/or meta information of the file stored in the file data block in the storage 260 in a designated area (eg, in the memory 130 ) based on the file open request. It can be loaded into the volatile memory 132 . In an embodiment, when the application 146 does not have access to the file 340 , the file system 250 stores the metadata block and/or the metadata of the file stored in the file data block from the storage 260 . It may be loaded into a designated area of the memory 130 (eg, the volatile memory 132 ). In an embodiment, when the application 146 does not have access to the sensitive information of the file 340 , the file system 250 stores the metadata block and/or the metadata of the file stored in the file data block in memory. It can be loaded into a designated area of 130 (eg, volatile memory 132). In an embodiment, the file system 250 may load the access right of the file 340 , the range of sensitive information, or a combination thereof into a designated area of the memory 130 (eg, the volatile memory 132 ). .

In an embodiment, in operation 450 , the file system 250 may provide an open result (eg, a file descriptor) of the file 340 to the media provider 220 .

In an embodiment, in operation 460 , the media provider 220 may provide the fuse 240 with an open result of the file 340 . In an embodiment, in operation 470 , the fuse 240 may provide an open result of the file 340 to the application 146 .

5 is a diagram illustrating a processing sequence of a file read operation between components of the electronic device 101 according to an embodiment of the present disclosure. FIG. 5 may be described with reference to configurations of the electronic device 101 of FIG. 1 .

In an embodiment, in operation 510 , the application 146 may request the fuse 240 to read the file. In an embodiment, the application 146 may request the fuse 240 to read the file through a system call. According to an embodiment, the file open request may include information about a file descriptor of the file 340 , a read range, or a combination thereof.

In an embodiment, the fuse 240 may identify whether sensitive information exists in the file 340 . In an embodiment, the fuse 240 may identify whether sensitive information exists in the file 340 based on meta information (eg, a range of sensitive information) of the file 340 . In an embodiment, the fuse 240 may identify whether sensitive information exists in the read range of the file 340 .

In an embodiment, when sensitive information exists in the file 340 , the fuse 240 may identify whether the application 146 has an access right to the sensitive information of the file 340 . In an embodiment, the fuse 240 identifies whether or not the application 146 has an access right to the sensitive information of the file 340 based on the meta information (eg, access right of sensitive information) of the file 340 . can

In one embodiment, when the sensitive information does not exist in the file 340 or the application 146 has access to the sensitive information of the file 340, the fuse 240 sets the reference link 445. The file 340 may be read through. In this case, in operation 570 , the fuse 240 may provide the read file 340 to the application 146 .

In one embodiment, when sensitive information exists in the file 340 and the application 146 does not have access to the sensitive information of the file 340 , the fuse 240 establishes the reference link 445 . Through this, the sensitive information of the file 340 may be corrected, and the file 340 in which the sensitive information has been modified may be read.

In an embodiment, the redaction filter 245 may modify the sensitive information of the file 340 by changing the sensitive information to designated data (eg, 0 bits). In an embodiment, the redaction filter 245 may modify the sensitive information of the file 340 by encrypting the sensitive information. In an embodiment, the redaction filter 245 may modify the sensitive information of the file 340 by replacing the sensitive information with virtual information. In this case, in operation 570 , the fuse 240 may provide the file 340 in which the sensitive information is modified to the application 146 .

Referring to FIG. 6 , in operation 610 , the processor 120 of the electronic device 101 may generate a file 340 . In an embodiment, the processor 120 may create the file 340 through the file system 250 . In an embodiment, the file may include a photo, a video, or a combination thereof.

In an embodiment, in operation 620 , the processor 120 may store owner information of the file 340 . In an embodiment, the processor 120 may store identification information of the application 146 requesting creation of the file 340 as owner information of the file 340 .

In an embodiment, the processor 120 may store owner information of the file 340 through the file system 250 . In an embodiment, the processor 120 may store owner information of the file 340 in a metadata block of the file system 250 . In an embodiment, the processor 120 may store owner information of the file 340 in the extended attribute area 349 of the file system 250 .

In an embodiment, in operation 630 , the processor 120 may identify whether sensitive information exists in the file 340 . In an embodiment, the processor 120 may identify whether sensitive information exists in the file 340 based on tag information (eg, EXIF-based tag information) of the file 340 . In an embodiment, the sensitive information may include a photographing location, a photographing time, a face tag, or a combination thereof.

In an embodiment, if sensitive information exists in the file 340 in operation 630 , the processor 120 may perform operation 640 . In an embodiment, in operation 630 , if sensitive information does not exist in the file 340 , the processor 120 may end the operation according to FIG. 6 .

In an embodiment, in operation 640 , the processor 120 may store information about the access right of the file 340 . In an embodiment, the processor 120 may store information about the access right to the sensitive information of the file 340 .

In an embodiment, the processor 120 may store information about the access right of the file 340 in the extended attribute area 349 . In an embodiment, the processor 120 may store information about the access right of the file 340 in the last file data block 347 among the file data blocks 341 in which the file 340 is stored. In an embodiment, when the space of the extended attribute area 349 is insufficient, the processor 120 stores the file 340 in the last file data block 347 among the file data blocks 341 in which the file 340 is stored. Information about access rights can be stored. In an embodiment, when the space of the extended attribute area 349 allocated to the file 340 is insufficient, the processor 120 performs the last file data block 347 among the file data blocks 341 in which the file 340 is stored. ) may store information about the access right of the file 340 .

In an embodiment, in operation 650 , the processor 120 may store information on the range of sensitive information of the file 340 . In an embodiment, the processor 120 may store information about the access right to the sensitive information of the file 340 .

In an embodiment, the processor 120 may store information on the range of the

sensitive information

343 and 345 of the file 340 in the extended attribute area 349 . In an embodiment, the processor 120 includes information on the range of the

sensitive information

343 and 345 of the file 340 in the last file data block 347 among the file data blocks 341 in which the file 340 is stored. can be saved. In an embodiment, when the space of the extended attribute area 349 is insufficient, the processor 120 stores the file 340 in the last file data block 347 among the file data blocks 341 in which the file 340 is stored. Information on the range of the

sensitive information

343 and 345 may be stored. In an embodiment, when the space of the extended attribute area 349 allocated to the file 340 is insufficient, the processor 120 performs the last file data block 347 among the file data blocks 341 in which the file 340 is stored. ) in the file 340 may store information on the range of

sensitive information

343 and 345 .

Referring to FIG. 7 , in operation 710 , the processor 120 of the electronic device 101 may open a file 340 . In an embodiment, the processor 120 may open the file 340 through the file system 250 .

In an embodiment, the processor 120 may store the location and/or access information where the file 340 is stored in the reference link 445 of the fuse 240 .

In an embodiment, in operation 720 , the processor 120 may check owner information and access rights of the file 340 . In an embodiment, the processor 120 may check owner information and access rights of the file 340 based on the meta information of the file 340 . In an embodiment, the meta information of the file 340 may be stored in the extended attribute area 349 and/or the last file data block 347 of the file 340 .

In an embodiment, in operation 730 , the processor 120 may identify whether an access right exists in the application 146 requesting the file open. In an embodiment, the processor 120 may identify whether an access right to the file 340 exists in the application 146 requesting the file open based on the owner information and the access right.

In an embodiment, in operation 730 , if there is no access right to the file 340 , the processor 120 may perform operation 740 . In an embodiment, in operation 730 , if the access right to the file 340 exists, the processor 120 may end the operation according to FIG. 7 .

In an embodiment, in operation 740 , the processor 120 may load the sensitive information range and access right information of the file 340 . In one embodiment, the processor 120 may load the scope and access right information of the sensitive information of the file 340 stored in the extended attribute area 349 and/or the last file data block 347 of the file 340 . have.

Referring to FIG. 8 , in operation 810 , the processor 120 of the electronic device 101 may read the file 340 . In an embodiment, the processor 120 may read the file 340 through the fuse 240 . In an embodiment, the processor 120 may read the file 340 based on the reference link 445 of the fuse 240 .

In an embodiment, in operation 820 , the processor 120 may identify whether sensitive information exists in the file 340 . In an embodiment, the processor 120 may identify whether sensitive information exists in the file 340 based on meta information (eg, a range of sensitive information) of the file 340 through the fuse 240 . In an embodiment, the processor 120 may identify whether sensitive information exists in the file 340 based on meta information (eg, a range of sensitive information) of the loaded file 340 .

In an embodiment, if sensitive information exists in operation 820 , the processor 120 may perform operation 830 . In an embodiment, if sensitive information does not exist in operation 820 , the processor 120 may end the operation according to FIG. 8 .

In an embodiment, in operation 830 , the processor 120 may identify whether the access right of the application 146 requesting the file read exists. In an embodiment, the processor 120 may identify whether the access right of the application 146 exists based on the meta information (eg, the access right of sensitive information) of the file 340 through the fuse 240 . In an embodiment, the processor 120 may identify whether the access right of the application 146 exists based on meta information (eg, access right of sensitive information) of the loaded file 340 .

In an embodiment, if the access right of the application 146 does not exist in operation 830 , the processor 120 may perform operation 840 . In an embodiment, in operation 830 , if the access right of the application 146 exists, the processor 120 may end the operation according to FIG. 8 .

In an embodiment, in operation 840 , the processor 120 may process sensitive information of the file 340 . In an embodiment, the processor 120 may process sensitive information of the file 340 through the fuse 240 . In an embodiment, the processor 120 may process sensitive information of the file 340 through the redaction filter 245 of the fuse 240 .

In an embodiment, the processor 120 may process the sensitive information of the file 340 by changing the sensitive information to designated data (eg, 0 bits) through the redaction filter 245 . In an embodiment, the processor 120 may process the sensitive information of the file 340 by encrypting the sensitive information through the redaction filter 245 . In an embodiment, the processor 120 may process the sensitive information of the file 340 by replacing the sensitive information with virtual information through the redaction filter 245 .

The electronic device 101 according to an embodiment of the present disclosure includes a processor 120 and a storage 260 connected to the processor 120 and storing instructions, wherein the instructions include the processor 120 . ), in response to a file creation request from the application 146 , the processor 120 generates a file to the media provider 220 via a first file system (eg, fuse 240 ). request, request creation of the file from a second file system (eg, file system 250) through the media provider 220, and access the second file system (eg, file system 250) It may be configured to create a file through the file and store setting information indicating the access right of the file and the range of sensitive information in a designated area of the file and/or the metadata block of the storage 260 .

In an embodiment, when the instructions are executed by the processor 120 , the processor 120 responds to a file open request from the application 146 : the first file system (eg, fuse ( 240)) to request the media provider 220 to open the file, and to open the file through the second file system (eg, file system 250) through the media provider 220. and to provide the location of the file and the location of the setting information to the first file system (eg, the fuse 240 ) through the second file system (eg, the file system 250 ).

In an embodiment, when the instructions are executed by the processor 120 , the processor 120 responds to a file read request from the application 146 : the first file system (eg, fuse ( 240)) to identify the setting information based on the location of the setting information, and to the file of the application 146 based on the setting information through the first file system (eg, fuse 240). identify an access right to the file system, process the sensitive information among areas of the file based on the identified access right through the first file system (eg, fuse 240), and process the sensitive information in the first file system (eg, fuse 240) : It may be configured to read the file in which the sensitive information is processed through the fuse 240 .

In an embodiment, when the instructions are executed by the processor 120 , the processor 120 may be configured to process the sensitive information by changing the sensitive information into designated data.

In an embodiment, when the instructions are executed by the processor 120 , the processor 120 is configured to process the sensitive information by encrypting the sensitive information.

In an embodiment, when the instructions are executed by the processor 120 , the processor 120 may be configured to process the sensitive information by replacing the sensitive information with virtual information.

In an embodiment, the designated area of the file may be a last file data block among file data blocks in which the file is stored.

In an embodiment, when the instructions are executed by the processor 120 , the processor 120 transmits the setting information to the metadata block through the second file system (eg, the file system 250 ). and store the setting information in the last file data block when the space of the extended attribute area is insufficient through the second file system (eg, the file system 250). .

In a method of operating the electronic device 101 according to an embodiment of the present disclosure, in response to a file creation request from an application 146 of the electronic device 101: a first file system ( Example: the operation of the fuse 240 ) requesting the media provider 220 of the electronic device 101 to create a file, and the media provider 220 , the second file system ( Example: an operation of requesting creation of the file from the file system 250 , an operation of the second file system (eg, file system 250 ) creating the file, and an operation of the second file system (eg, file) The system 250) stores the setting information indicating the access right of the file and the range of sensitive information in the designated area of the file and/or the metadata block of the storage 260 of the electronic device 101 may include

In an embodiment, in the method of operating the electronic device 101 according to an embodiment of the present disclosure, in response to a file open request from the application 146: the first file system (eg, fuse 240) The operation of requesting the media provider 220 to open the file, the operation of the media provider 220 opening the file through the file system, and the second file system (eg, a file system ( 250)) may include an operation of providing the location of the file and the location of the setting information to the first file system (eg, the fuse 240).

In an embodiment, in the method of operating the electronic device 101 according to an embodiment of the present disclosure, in response to a file read request from the application 146: the first file system (eg, the fuse 240) An operation of identifying the setting information based on the location of the setting information, the first file system (eg, fuse 240 ) grants access to the file of the application 146 based on the setting information An operation of identifying, an operation of the first file system (eg, fuse 240) processing the sensitive information among regions of the file based on the identified access right, and an operation of the first file system (eg, fuse 240) (240) may include an operation of reading the file in which the sensitive information is processed.

In an embodiment, the processing of the sensitive information may include processing the sensitive information by changing the sensitive information into designated data by the first file system (eg, fuse 240 ). .

In an embodiment, the processing of the sensitive information may include processing the sensitive information by encrypting the sensitive information.

In an embodiment, the operation of processing the sensitive information may include processing the sensitive information by replacing the sensitive information with virtual information.

In an embodiment, in the method of operating an electronic device according to an embodiment of the present disclosure, the second file system (eg, the file system 250 ) stores the setting information in an extended attribute area of the metadata block. and, when the second file system (eg, the file system 250 ) runs out of space in the extended attribute area, storing the setting information in the last file data block.

The non-transitory computer-readable recording medium according to an embodiment of the present disclosure includes, when executed by the processor 120 , the processor 120 in response to a file creation request from the application 146: a first file The system (eg, the fuse 240) requests the media provider 220 to create a file, and the second file system (eg, the file system 250) sends the file through the media provider 220. request creation of a file, create a file through the second file system (eg, file system 250), and send setting information indicating the access right of the file and the range of sensitive information to a designated area of the file and / Alternatively, it may include instructions to be stored in the meta data block of the storage 260 .

The storage device according to an embodiment of the present disclosure includes a non-volatile memory area (eg, non-volatile memory 134 ), and stores setting information indicating access rights of a file and a range of sensitive information in a designated area of the file. and/or stored in a meta data block of the non-volatile memory area (eg, the non-volatile memory 134 ).

The electronic device according to various embodiments disclosed in this document may be a device of various types. The electronic device may include, for example, a portable communication device (eg, a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance device. The electronic device according to the embodiment of the present document is not limited to the above-described devices.

The various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, and should be understood to include various modifications, equivalents, or substitutions of the embodiments. In connection with the description of the drawings, like reference numerals may be used for similar or related components. The singular form of the noun corresponding to the item may include one or more of the item, unless the relevant context clearly dictates otherwise. As used herein, "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C", and "A , B, or C," each of which may include any one of the items listed together in the corresponding one of the phrases, or all possible combinations thereof. Terms such as "first", "second", or "first" or "second" may simply be used to distinguish an element from other elements in question, and may refer elements to other aspects (e.g., importance or order) is not limited. It is said that one (eg, first) component is “coupled” or “connected” to another (eg, second) component, with or without the terms “functionally” or “communicatively”. When referenced, it means that one component can be connected to the other component directly (eg by wire), wirelessly, or through a third component.

The term “module” used in various embodiments of the present document may include a unit implemented in hardware, software, or firmware, for example, and interchangeably with terms such as logic, logic block, component, or circuit. can be used A module may be an integrally formed part or a minimum unit or a part of the part that performs one or more functions. For example, according to an embodiment, the module may be implemented in the form of an application-specific integrated circuit (ASIC).

According to various embodiments of the present document, one or more instructions stored in a storage medium (eg, internal memory 136 or external memory 138) readable by a machine (eg, electronic device 101) may be implemented as software (eg, the program 140) including For example, the processor (eg, the processor 120 ) of the device (eg, the electronic device 101 ) may call at least one of the one or more instructions stored from the storage medium and execute it. This makes it possible for the device to be operated to perform at least one function according to the called at least one command. The one or more instructions may include code generated by a compiler or code executable by an interpreter. The device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-transitory' only means that the storage medium is a tangible device and does not contain a signal (eg, electromagnetic wave), and this term is used in cases where data is semi-permanently stored in the storage medium and It does not distinguish between temporary storage cases.

According to an embodiment, the method according to various embodiments disclosed in this document may be provided by being included in a computer program product. Computer program products may be traded between sellers and buyers as commodities. The computer program product is distributed in the form of a device-readable storage medium (eg compact disc read only memory (CD-ROM)), or via an application store (eg Play Store™) or on two user devices ( It can be distributed (eg downloaded or uploaded) directly, online between smartphones (eg: smartphones). In the case of online distribution, at least a portion of the computer program product may be temporarily stored or temporarily created in a machine-readable storage medium such as a memory of a server of a manufacturer, a server of an application store, or a relay server.

According to various embodiments, each component (eg, module or program) of the above-described components may include a singular or a plurality of entities, and some of the plurality of entities may be separately disposed in other components. . According to various embodiments, one or more components or operations among the above-described corresponding components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, a plurality of components (eg, a module or a program) may be integrated into one component. In this case, the integrated component may perform one or more functions of each component of the plurality of components identically or similarly to those performed by the corresponding component among the plurality of components prior to the integration. . According to various embodiments, operations performed by a module, program, or other component are executed sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations are executed in a different order, omitted, or , or one or more other operations may be added.

Claims

In an electronic device,

processor, and

and a storage connected to the processor and storing instructions, wherein the instructions, when executed by the processor, cause the processor to:

In response to a file creation request from the application:

requesting the media provider to create a file through the first file system;

requesting a second file system to create the file through the media provider;

and create a file through the second file system, and store setting information indicating an access right of the file and a range of sensitive information in a designated area of the file and/or a metadata block of the storage.
The method according to claim 1,

The instructions, when executed by the processor, cause the processor to:

In response to a file open request from the application:

requesting the media provider to open the file through the first file system;

open the file through the second file system through the media provider,

and provide the location of the file and the location of the setting information to the first file system through the second file system.
3. The method according to claim 2,

The instructions, when executed by the processor, cause the processor to:

In response to a file read request from the application:

identify the setting information based on the location of the setting information through the first file system;

Identifies the access right to the file of the application based on the setting information through the first file system,

processing the sensitive information among the areas of the file based on the identified access right through the first file system;

The electronic device is configured to read the file in which the sensitive information is processed through the first file system.
4. The method of claim 3,

The instructions, when executed by the processor, cause the processor to:

an electronic device configured to process the sensitive information by changing the sensitive information into designated data.
4. The method according to claim 3,

The instructions, when executed by the processor, cause the processor to:

An electronic device configured to process the sensitive information by encrypting the sensitive information.
4. The method according to claim 3,

The instructions, when executed by the processor, cause the processor to:

An electronic device configured to process the sensitive information by replacing the sensitive information with virtual information.
The method according to claim 1,

The designated area of the file is a last file data block among file data blocks in which the file is stored.
8. The method of claim 7,

The instructions, when executed by the processor, cause the processor to:

storing the setting information in an extended attribute area of the meta data block through the second file system;

and store the setting information in the last file data block when the space of the extended attribute area is insufficient through the second file system.
A method of operating an electronic device, comprising:

In response to a file creation request from an application on the electronic device:

requesting, by the first file system of the electronic device, a media provider of the electronic device to create a file;

requesting, by the media provider, to generate the file from a second file system of the electronic device;

creating the file by the second file system; and

and storing, by the second file system, setting information indicating the access right of the file and the range of sensitive information in a designated area of the file and/or in a metadata block of storage of the electronic device.
10. The method of claim 9,

In response to a file open request from the application:

an operation of the first file system requesting the media provider to open the file;

the media provider opening the file through the second file system; and

and providing, by the second file system, the location of the file and the location of the setting information to the first file system.
11. The method of claim 10,

In response to a file read request from the application:

identifying, by the first file system, the configuration information based on the location of the configuration information;

identifying, by the first file system, an access right to the file of the application based on the setting information;

processing, by the first file system, the sensitive information among the areas of the file based on the identified access right, and

and reading, by the first file system, the file in which the sensitive information is processed.
12. The method of claim 11,

The operation of processing the sensitive information,

and processing, by the first file system, the sensitive information by changing the sensitive information into designated data.
12. The method of claim 11,

The operation of processing the sensitive information,

and processing the sensitive information by encrypting the sensitive information.
10. The method of claim 9,

The designated area of the file is a last file data block among the file data blocks in which the file is stored.
A non-transitory computer-readable recording medium comprising:

When executed by a processor, the processor:

In response to a file creation request from the application:

requesting the media provider to create a file through the first file system;

requesting a second file system to create the file through the media provider;

A rain including instructions for creating a file through the second file system, and storing configuration information indicating the access right of the file and the scope of sensitive information in a specified area of the file and/or a metadata block of storage - A temporary computer-readable recording medium.