KR20060009717A - Data managing apparatus for mobile communication terminal - Google Patents

Abstract

The present invention relates to a data management system of a mobile communication terminal. In the related art, a data management method of a mobile communication terminal uses an embedded file system in which a developer directly manages an address of a physical memory, and thus, application programming dependent on a storage medium. Data management is possible only through the interface, and because it cannot support other types of file systems connected to the network or directly, it is difficult to share files when the mobile terminal is connected to a network device using a different type of file system. In addition, in order to exchange files, it is necessary to convert the data to be transmitted at the application level according to the file system of the transmission target, thereby complicating data exchange and reducing the real time. In view of the above problems, the present invention provides a file system manager that independently executes data input / output requests of an application to a medium, and a plurality of file systems that are media-dependent and used by the file system manager when necessary. Even when connecting to a network device using or directly connecting media using various file systems, data can be directly shared by simply mounting the corresponding file system to share files by flexibly connecting with various devices having various file systems. It can work.

Description

DATA MANAGING APPARATUS FOR MOBILE COMMUNICATION TERMINAL}

1 is a configuration diagram showing the configuration of a typical representative mobile communication terminal file system.

Figure 2 is a block diagram showing a system configuration of an embodiment of the present invention.

* Description of the symbols for the main parts of the drawings *

100: application 200: file system manager

300a to 300i: File system 350a and 350b: Device driver

400a, 400b: storage media

The present invention relates to a data management system of a mobile communication terminal. In particular, an abstracted file system manager independent of a storage medium and a file system responsible for physical input / output dependent on the medium are separated, and various file media are mounted to mount a necessary file system. And a data management system of a mobile communication terminal to provide a consistent approach to a file system.

The use of mobile terminals has been rapidly spreading, and many additional services have been developed to increase the efficiency of mobile terminals. In order to improve the functions of these mobile communication terminals, there is a need for a complex application that supports a large amount of data processing and various functions.

In particular, in accordance with the widespread acceptance of multimedia-related functions, a larger amount of physical memory management is required, and even an external memory should be managed by a mobile terminal operating system. In addition, data exchange with network equipment through a network function is also required.

Currently used mobile communication terminals use a file system developed for mobile communication terminals to store and read all kinds of data such as files and data. Currently, most of the methods of storing and reading files or data in a memory of a mobile communication terminal are a method of writing or reading data at a corresponding address using a physical address of the memory. As a result, developers of mobile terminal applications always have to consider the physical memory address where the data to be used or located is located, which leads to long development time and difficulty in debugging. In addition, since there is no consideration of other types of file systems, the compatibility is extremely low, and even when a device adopting another type of file system is connected, files cannot be shared.

1 illustrates a basic structure of an EFS (Embedded File System), which is a file system proposed by Qualcomm, which is applied to most mobile communication terminals using a communication chip of the company.

As shown, the application encapsulation layer, where the actual application software is located, is at the top layer, where device drivers with direct read and write control methods for physical memory are defined, and logical device interfaces (multiplexers) that selectively specify them are located. A device encapsulation layer is located at the lowest layer, and a service encapsulation layer is connected between the application encapsulation layer and the device encapsulation layer to connect them to each other to exchange physical data.

The service encapsulation layer includes an application programming interface (API) portion in which file processing functions used by an actual developer are defined, and an embedded file system (EFS) portion controlled by the application program interface to access physical memory of the device encapsulation layer. Is done.

The service encapsulation layer may be referred to as a nonvolatile memory storage server, and actual developers may manipulate the EFS using various EFS functions provided by the application programming interface to read and write a desired file or data into physical memory.

The EFS uses a physical address of a memory to manipulate a logical device interface of the device encapsulation layer, selects a desired device driver, and accesses and reads and writes desired data by accessing a physical memory controlled by the corresponding device driver. Since it is a dependent file system, when a different type of media and a file system supporting the same are connected to a mobile terminal through a network, the conventional EFS, which is dependent on the media, cannot support such a different type of file system. You cannot manage the files stored in it directly. Therefore, when data is to be transmitted to a file system different from the EFS of the mobile communication terminal, a separate file conversion application is executed to change the file structure or to transmit simple data to a network device using the different file system. Will require a complex process of recreating the file into its own file system, and new applications will be required to support this task.

This is an enormous burden for mobile communication terminals, which are increasingly required to be connected with many types of network equipment. Unless this is solved, data exchange can be performed by directly connecting devices using different file systems with mobile communication terminals. It is very difficult to share files in real time by connecting via a network connection.

As described above, since the data management method of the conventional mobile communication terminal uses an embedded file system in which a developer directly manages an address of a physical memory, data management is possible only through an application programming interface dependent on a storage medium. There is a problem that file sharing is difficult when the mobile terminal is connected to a network device using a different type of file system because it cannot support other types of file systems that are directly connected or connected directly. There is a problem in that data exchange is complicated and real-time is low, because the data to be transmitted is required to be converted according to the file system to be transferred.                         

In view of the above problems, the present invention provides an application managed by a developer and a user, a file system manager that independently executes data input / output requests of the application, and a medium-dependent device mounted and used by the file system manager if necessary. It is composed of multiple file systems, drivers connected to the file system, and physical storage media to connect the network devices using various file systems or directly connect the media using various file systems. It is an object of the present invention to provide a data management system of a mobile communication terminal capable of direct sharing.

The present invention for achieving the above object is an application for requesting data input and output required by the operation of the user and administrator in a consistent manner; A file system manager connected to the application to manage data input / output independently of a medium and to handle a mount request of a specific file system; A file system configured to be dependent on the medium to manage data input / output for a specific medium in accordance with a specific format; It is characterized in that it comprises a device driver connected to the file system if necessary to directly control the physical medium.

The file system includes a file system for managing a storage medium embedded in a mobile communication terminal, a file system for managing file input / output of a network device, and a file input / output of a corresponding device when a predetermined device is directly connected to the mobile communication terminal. And a file system to manage.                     

The file system manager manages the mount of the file system, and inputs and outputs logical data to the mounted file system so that data conversion between different file systems is automatically processed in the mounted file system.

Hereinafter, with reference to the accompanying drawings, the present invention configured as described above will be described in detail.

2 illustrates a configuration of a data management system according to an exemplary embodiment of the present invention. As shown in FIG. 2, an application 100 created by a developer and manipulated by a user, and a common file directly manipulated by the application 100 are illustrated in FIG. A media independent abstract file system manager 200 which manages to mount individual file systems while providing an input / output application programming interface (API), and is connected to the file system manager 200 to handle data input / output dependent on the medium. It consists of various file systems 300a to 300i, actual media control device drivers 350a and 350b connected to necessary file systems among the file systems 300, and physical storage media 400a and 400b.

The file system manager 200 includes a common file I / O API part and a mount manager that mounts a specific file system internally, and the abstract file system and the mount manager operate as a task and use the common file I / O API. It is configured to provide. This means that real-time I / O is guaranteed, and that data stored in other file system methods can be directly used.

The application 100 mounts a specific file system to be used by using the file system manager 200 and accesses data of each mounted file system through logical data input / output. Such a method can be implemented by modifying a heterogeneous access method applied in a Unix system to be applicable to a mobile communication terminal.

The file system manager 200 inputs and outputs logical data to the mounted file system 300, and the logical data input / output is converted into data suitable for a media dependent file system in the file system 300 and physically stored. The way is determined. In addition, the file system 300 converts the data retrieved according to the media-dependent file system into logical data and provides it to the file system manager 200. Therefore, the application 100 can use a consistent media approach regardless of data conversion between file systems. Through this, the application 100 can be very easily developed, and the probability of collision or error between file systems is reduced, thereby increasing application reliability.

The file system 300 is a file system (embedded file system (EFS) 300a, a data file management system (DFMS) 300b) that manages a storage medium 400a (i.e., a flash memory) embedded in a mobile communication terminal. ), And the file system 300c used in the network device, the file system (compact disk file system (CDFS) 300d, Windows file system used when connecting a device using a specific file system directly to the mobile communication terminal) (FAT16, FAT32) (300e, 300f), OS / 2 file system (HPFS) 300g, Linux file system (EXT2, EXT3) (300h, 300i), and the like.                     

In addition, device drivers 350a and 350b that may directly control a specific medium may be configured in association with the file systems 300a / 300b and 300d, if necessary. These are directly connected with the storage media 400a and 400b.

Since the data management system configured as described above cannot perform any data input / output unless a specific file system is mounted by the file system manager, a storage medium (flash memory, etc.) built in the mobile communication terminal is basically used when the mobile terminal is booted. EFS (300a) or DFMS (300b) can be mounted by default to use. When a device using another file system is connected or a use request is in use, the file system may be mounted to perform data input / output. Therefore, the application 100 can access the mounted file system in a consistent approach regardless of the medium and the specific file system.

As described above, the data management system of the mobile communication terminal according to the present invention includes an application managed by a developer and a user, a file system manager for independently executing a data input / output request of the application on a medium, and the file system manager if necessary. It is composed of a plurality of media-dependent file systems, drivers and physical storage media connected to the file system, thereby connecting a mobile communication terminal to a network device using various file systems or directly connecting a medium using various file systems. In this case, the data can be directly shared by simply mounting the corresponding file system, and the files can be shared in real time by flexibly connecting with various devices having various file systems. Sieve can be used as a storage medium of a mobile communication terminal.

Claims (5)

An application for requesting data input / output required by a user and an administrator in a consistent manner; A file system manager connected to the application to manage data input / output independently of a medium and to handle a mount request of a specific file system; A file system configured to be dependent on the medium to manage data input / output for a specific medium in accordance with a specific format; And a device driver connected to the file system and directly controlling a physical medium, if necessary. The method of claim 1, wherein the file system includes a file system for managing a storage medium embedded in a mobile communication terminal, a file system for managing file input / output of a network device, and a device directly connected to the mobile communication terminal. And a file system for managing file input / output of the device. The file system manager of claim 1, wherein the file system manager manages a mount of a file system and inputs and outputs logical data to and from the mounted file system so that data conversion between different file systems is automatically processed in the mounted file system. Data management system of a mobile communication terminal. The data management system of claim 1, wherein the file system manager comprises a common file input / output application programming interface accessible to the application and a mount manager for mounting a file system. The data management system of claim 1, wherein the file system manager automatically mounts an embedded file system (EFS) when the mobile terminal is booted.

Images