KR20050034498A - Mobile terminal with mobile platform supporting common management of resource - Google Patents

Abstract

The present invention relates to a mobile communication terminal equipped with a mobile platform that supports common management of resources for classifying terminal resources by group and MIME type and managing them through a common API.

A mobile communication terminal equipped with a mobile platform supporting common management of resources of the present invention includes a handset hardware (H / W), an operating system including a CPU core of a terminal supporting a wireless Internet environment and a modem chip processor for call processing. (OS) A mobile communication terminal equipped with a mobile platform comprising a layer module and an application layer module for executing an application on the platform, the mobile communication terminal is a group and MIME type of resources of the terminal having a specific data format Classified and stored according to the above, and the application layer module includes an API layer module including a resource management API for common management of terminal resources classified by the group and the MIME type, and then calls a corresponding function registered in the platform. Technical features to allow common management of resources .

Description

Mobile terminal with mobile platform supporting common management of resources

The present invention relates to a mobile communication terminal equipped with a mobile platform that supports common management of resources for classifying terminal resources by group and MIME type and managing them through a common API.

An API (Application Programming Interface) is a set of subroutines or functions that a program or an application can call to an operating system for processing, and refers to a set of functions that define functions such as an operating system and how to use the functions. That is, an application program can use various functions possessed by an operating system using an API.

The Windows API consists of more than 1000 functions, and application programmers can use various functions by calling the function simply by describing the function in the program. This set of functions is called an API.

Meanwhile, data stored in a terminal area while having a specific media format such as JPEG, SIS, MPEG4, MA2, MA3, and a phonebook managed by a terminal are collectively called a terminal resource.

In the existing terminal and the platform environment of the terminal, the resources of the terminal are individually managed one by one, and accordingly, the corresponding API is added whenever resources are added one by one.

However, managing the resources of the terminal individually in this manner is not suitable for the current terminal environment in which the environment of the terminal is highly developed.

Accordingly, the present invention is to solve the above-mentioned disadvantages and problems of the prior art, divide the resources of the terminal into groups, and manage each resource by group through the MIME type of each group to be managed as a formal API. It is an object of the present invention to provide a mobile communication terminal equipped with a mobile platform that supports common management of resources.

The above object of the present invention is to execute an application on a handset hardware (H / W), an operating system (OS) layer module, and a platform including a CPU chip of a terminal supporting a wireless Internet environment and a modem chip processor for call processing. A mobile communication terminal equipped with a mobile platform configured to include an application layer module, wherein the mobile communication terminal classifies and stores resources of a terminal having a specific data format according to a group and a MIME type, and the application layer module includes: Including the API layer module including a resource management API for common management of terminal resources classified by the group and the MIME type, calling the corresponding function registered in the platform to common management of resources of the terminal By a mobile terminal equipped with a mobile platform that supports management Is achieved.

In the present invention, the mobile communication terminal includes various mobile terminals such as a mobile phone, a cellular phone, a smart phone, a PDA, and an IMT-2000 terminal.

Details of the above object and technical configuration of the present invention and the resulting effects thereof will be more clearly understood from the following detailed description based on the accompanying drawings.

First, Figure 1 is a structural diagram of a mobile platform according to an embodiment of the present invention.

As shown, a mobile platform mounted on a mobile communication terminal includes a handset hardware (H / W) 10 including a modem chip processor and the like configured with a CPU core of a terminal supporting a wireless Internet environment and a hardware architecture for performing call processing. ), An operating system layer module 20 and an application layer module 30 for executing the application 40 on the platform.

The operating system layer module 20 is an operating system of a mobile communication terminal. For example, an operating system such as Real Time Execution (REX) or Pioneer Server OS (pSOS) is used in a terminal supporting multitasking using a Qualcomm modem chip. Say.

The application layer module 30 includes a handset application layer module 31, a runtime engine 32 that is a driving engine of the application 40, and an API layer module 33 including an API for common control of terminal resources. It is composed.

The handset application layer module 31 (HAL) is an abstraction layer for maintaining hardware independence of the platform, and supports upper layers to operate independently of the native system on the handset application layer module 31. For example, in the case of a domestic CDMA terminal, porting only the handset application layer module 31 onto the Qualcomm OS (REX) becomes a platform for the terminal, and porting only the handset application layer module 31 to the window environment emulates a window. Becomes

The API layer module 33 is a set of functions that the application 40 can call to the operating system for any processing. The API layer module 33 controls the handset hardware 10 through the handset application layer module 31 and each application. APIs substantially used at 40 are included.

In the present invention, the API layer module 33 includes a resource management API for common management of terminal resources, in which resources of a terminal having a specific data format are classified according to groups and MIME types, and calls corresponding functions registered in the platform. In order to manage the resources of the terminal in common, a detailed description of the resource management API will be described later with reference to FIGS. 5 and 6.

Meanwhile, according to the present invention, in order to manage the resources of the terminal in common, the resources of the terminal are managed by being divided into a group as shown in FIG. 2 and a MIME type as shown in FIGS. 3 and 4.

2 is a resource group table according to an embodiment of the present invention.

The resources of a terminal collectively refer to data stored in the terminal area while having a specific media format such as JPEG, SIS, MPEG4, MA2, MA3, and a phonebook managed by the terminal. In the present invention, resources of the terminal are classified by groups.

Resource groups are divided into picture friends, music bells, photos, voices, phone books (phonebooks), call lists, character bells, multimedia, SMS lists, MMS lists, and terminal information.

In addition, the phone book is divided into individual phone book and group phone book, which are user setting areas, call list as outgoing call list and incoming call list, multimedia as live bell and live screen, SMS list as outgoing SMS list and incoming SMS. As a list, the MMS list is a record MMS list recorded by the originator, the receiver and the user, and the terminal information may be classified into a power on / off record, a black list, an alarm, and base station information (location information).

In addition, in order to manage the resources of the terminal in common in the present invention, the resources of the terminal are classified by MIME type as shown in FIGS. 3 and 4 as follows.

3 is a first table illustrating a MIME type classification for each resource according to an embodiment of the present invention, and FIG. 4 is a second table showing a MIME type classification for each resource according to an embodiment of the present invention.

As shown, resources of an image area classified as MIME types are classified into still images and animation images, and the still images are bmp, gif, jpeg, and png according to the image data format. Etc., and animated images are classified into animated bmp and sis. In this case, the animated bitmap image format is a format produced using a tool provided by the software development kit of the WIPI platform, and each image frame basically follows the bmp image format.

Next, resources in the sound area are MIME according to data formats such as CMX, Yamaha's MA1, MA2, MA3, MA5, MIDI format, MP3, QCELP (Qualcomm Code Excided Linear Prediction) -8K, 13K, and EVRC-8K. It is divided into types.

Next, as shown in FIG. 4, video resources are divided according to MPEG4 or H.264 video format, and an address book (phone book) is an individual phone book stored separately and a phone book for each group stored for each group. History) is divided into call list, SMS list and MMS list.

In addition, other resources classified by MIME type may include bell / character bell, power on / off record, black list of format including telephone number, alarm of format including time information, base station information of format including base station ID ( Location information).

Next, a table showing APIs for managing resources of a terminal classified as described above will be described with reference to FIGS. 5 and 6.

FIG. 5 is a first API table according to an embodiment of the present invention, and FIG. 6 is a second API table according to an embodiment of the present invention.

In order to manage the resources described with reference to FIGS. 2 to 4, a function of managing a resource group of a terminal, a function of managing terminal resource data, a security function of a terminal resource, and informing a user of arrival of a voice call or a message reception Visualization functions should be included.

The function of managing a resource group of the terminal acquires an amount of resources that a resource group of a specific terminal may have, a number of resources stored in a resource group of a specific terminal, and a name list of resources of the terminal resource group.

The function of managing the resource data of the terminal includes a function of obtaining a data format and a size of a specific resource from the platform of the terminal, writing data to the specific resource, reading the data, and deleting the resource. At this time, the function of managing the resource data is to set a specific state (power on, power off, idle, incoming) to a specific resource, and to know whether or not to set a specific state and ID for a specific resource, etc. It should include functions to do so.

In addition, the security function of the resource is to enable and disable the locking function for a specific resource. When the lock is set for a specific resource, a routine for inputting a password from the user should be able to be made at the application level. It should be able to determine the same by comparing the input password with the password set in the terminal resource.

Finally, the visualization function is for notifying the user of the arrival of a voice call or a message from a specific number. In the case of a voice call, a specific MMF data is registered as a character bell and a voice call from a specific number is received. It outputs the image and ring tone recorded in the MMF, or in the case of receiving a message, lights a specific image to notify the arrival of the message.

As illustrated in FIGS. 5 and 6, the API for performing the above functions includes a resource group list return API 301, a resource item number return API 302, a resource name list return API 303, and resource data. Format Return API 304, Resource Data Size Return API 305, Resource Data Return API 306, Resource Data Light API 307, Resource Data Delete API 308, Resource Registration API 309, Registration Resource Group List Return API 310, Register Resource Name Return API 311, Register Resource ID Return API 312, Resource Group Locked State Return API 313, Resource Locked State Return API 314, Resource Group Locked On / Off API 315, resource locked on / off API 316, password check API 317, carbell bell registration API 318, and resource storage free space return API 319.

The following describes each API in more detail.

First, the resource group list return (OEMC_termResGetSupportedGroups) API 301 returns a list of resource groups supported by the current terminal. The return value is "PHOTO \ 0SOUND \ 0 .. \ 0 \ 0", and all the terminals support the list. Contains a resource group, followed by two consecutive '\ 0' characters.

The prototype of the function is M_Int32 OEMC_termResGetSupportedGroups (M_Char * resGroup, M_Int32 bufSize). The parameter 'resGroup' is the name of a resource group and 'bufSize' indicates the size of the buffer.

At this time, if the resource group list is returned, '0' is returned. If it fails, 'M_E_ERROR' is returned. If it fails, 'M_E_SHORTBUF' is returned.

Next, the resource item count return (OEMC_termResGetCount) API 302 returns the number of resource items belonging to the resource group (resGroupName) in pdwCount and returns. The prototype of this function is M_Int32 OEMC_termResGetCount (M_Char * resGroupName, M_Uint32 * pdwCount). The parameter 'resGroupName' indicates the name of the resource group and 'pdwCount' indicates the number of resources.

At this time, if the resource item number is returned, '0' is returned. If it fails, 'M_E_ERROR' is returned. If the parameter passed is invalid, 'M_E_INVALID' is returned.

Next, the resource name list return (OEMC_termResGetList) API 303 returns a list of names of resources belonging to the resource group resGroupName. If the number of resources is 10, follow the format 'aszList = "mypic1 \ 0mypic2 \ 0 ... mypic10 \ 0 \ 0"'.

Resource names should not be duplicated within one resource group, especially for resource groups that have subgroups such as "PhoneBook" and "MULTIMEDIA". Should not be.

The prototype of the function is M_Int32 OEMC_termResGetList (M_Char * resGroupName, M_Char * aszList, M_Uint32 bufSize) .The parameter 'resGroupName' is the name of the resource group and 'aszList' is the NULL character ('\ 0'). Pointer to a list of names for the resource. The last name is followed by two NULL characters ('\ 0'). 'BufSize' refers to the buffer size of 'aszList'.

At this time, '0' is returned if the name list is successfully returned, 'M_E_ERROR' if it fails for unknown reasons, and 'M_E_SHORTBUF' if the size of the buffer that is passed is smaller than the returned string. In this case, 'M_E_INVALID' is returned.

On the other hand, if the resource group is "CALLHISTORY", "CALLHISTORY / SENT", "CALLHISTORY / RECEIVED", the resource name is a combination of call number and call time. do. For example, the name of a resource received from 011-1234-5678 at 1:20:30 on January 1, 2003 is configured as "01112345678_20030101132030". At this time, the time has a format of 24 hours.

Next, the resource data format return (OEMC_termResGetFormat) API 304 returns the data format of the resource corresponding to the given resource name among the resources belonging to the resource group (resGroupName) in 'rtnFormat', and the prototype is M_Int32 OEMC_termResGetFormat (M_Char * resGroupName, M_Char * resName, M_Char * rtnFormat, M_Uint32 rtnFormatSize).

Where 'resGroupName' is the resource group name, 'resName' is the name of the resource (the name obtained through the OEMC_termResGetList API) (303), 'rtnFormat' is the format of the data, rtnFormatSize 'indicates the buffer size of' rtnFormat '.

At this time, if the data format of the resource is successfully returned, '0' is returned. If it fails for an unknown reason, 'M_E_ERROR' is returned. If the buffer size is smaller than the returned string, 'M_E_SHORTBUF' is passed. If is wrong, 'M_E_INVALID' is returned.

Next, the resource data size return (OEMC_termResGetSize) API 305 returns the actual data size of the resource corresponding to the given resource name among the resources belonging to the resource group (resGroupName). The prototype is M_Int32 OEMC_termResGetSize (M_Char * resGroupName, M_Char * resName, M_Uint32 * pdwSize), where the parameter 'resGroupName' is the name of the resource group, 'resName' is the name of the resource (the name obtained through the OEMC_termResGetList API) (303), and 'pdwSize 'Is the size of the resource.

At this time, if the resource data size is successfully returned, '0' is returned. If it fails for an unknown reason, 'M_E_ERROR' is returned. If the transmitted parameter is incorrect, 'M_E_INVALID' is returned.

Next, the resource data return (OEMC_termResReadData) API 306 returns real data of a resource corresponding to a given resource name among resources belonging to a resource group (resGroupName) in pData. The prototype is M_Int32 OEMC_termResReadData (M_Char * resGroupName , M_Char * resName, M_Byte * pData, M_Uint32 bufSize).

The parameter 'resGroupName' is the name of the group to which the resource is to be returned, 'resName' is the name of the resource to return the data to, 'pData' is the actual data of the resource, and 'bufSize' is pData Buffer size to hold.

At this time, if the data is successfully returned, '0' is returned. If it fails for an unknown reason, 'M_E_ERROR' is returned. If the size of the buffer is smaller than the returned data, 'M_E_SHORTBUF' is passed. In this case, 'M_E_INVALID' is returned.

Next, the resource data write (OEMC_termResWriteData) API 307 is an API for writing resource data (pData) having a specific format (resFormat) to the resource group (resGroupName). The prototype is M_Int32 OEMC_termResWriteData (M_Char * resGroupName, M_Char * resName , M_Char * resFormat, M_Byte * pData, M_Uint32 bufSize).

The parameter 'resGroupName' is the resource group name, 'resName' is the name of the resource, 'resFormat' is the format of the resource to write to, 'pData' is the data of the resource to write to, and 'bufSize' is pData Buffer size.

At this time, if the data write is successful, it returns' 0 ',' M_E_ERROR 'if it fails for unknown reasons,' M_E_INSUFSPACE 'if the storage space of the resource data is insufficient, and' 'M_E_INVALID', 'M_E_ACCESSDENY' for resources for which the user does not have permission to write, 'M_E_DUPNAME' for duplicate names, or 'M_E_NOTSUP' for resource groups that do not support writing, such as call list resource groups. Returns.

Next, the Resource Data Delete (OEMC_termResDeleteData) API 308 deletes a resource corresponding to a given resource name among resources belonging to a resource group (resGroupName). The prototype is M_Int32 OEMC_termResDeleteData (M_Char * resGroupName, M_Char * resName). The parameter 'resGroupName' indicates the name of the resource group containing the resource to be deleted, and 'resName' indicates the name of the resource to be deleted (the name obtained through the resource name list return API 303).

At this time, if the resource is successfully deleted, it returns '0', if it fails for unknown reasons, 'M_E_ERROR'; if the parameter passed is wrong, 'M_E_INVALID', or if the resource is not authorized by the user 'M_E_ACCESSDENY' is returned in the case, and 'M_E_NOTSUP' is returned in the case of a resource group in which the delete function is not supported.

Next, the resource registration (OEMC_termResRegisterData) API 309 is an API that sets a resource corresponding to a given resource name among resources belonging to a resource group (resGroupName) to a specific state (szStatus) of the terminal. The prototype is M_Int32 OEMC_termResRegisterData (M_Char * resGroupName, M_Char * resName, M_Char * szStatus).

The parameter 'resGroupName' refers to a resource group name to which a resource to be set belongs, 'resName' refers to a name of a resource to be set, and 'szStatus' refers to a specific state of a terminal to which the resource is to be set.

At this time, the status of the terminal indicated by 'szStatus' includes "IDLE" indicating a standby screen, "INCOMING" indicating a telephone reception screen, "POWERON" indicating a terminal driving screen, "POWEROFF" indicating a terminal ending screen, "BROWSERON" indicating a browser drive screen, "BROWSEROFF" indicating a browser end screen of a terminal, and the like.

The resource registration API 309 sets '0' if the resource is successfully set to a specific state of the terminal, 'M_E_ERROR' if it fails for an unknown reason, or 'M_E_INVALID' if the parameter passed is wrong. 'M_E_ACCESSDENY' if the user does not have permission to set, 'M_E_INVALIDSTATUS' if the resource and the terminal's specific state are not related to each other, or 'M_E_NOTSUP' if the resource is not supported. .

The resource registration API 309 does not operate on the call list resource group and the phonebook resource group.

Next, the registered resource group list return (OEMC_termResGetRegisteredGroup) API 310 returns a list of resource groups registered in the terminal specific state (szStatus), and the list is "PHOTO \ 0MUSICBELL \ 0 .. \ 0 \ 0" ( Resource group + "\ 0", followed by two consecutive '\ 0' characters).

The prototype of the registration resource group list return API 310 is M_Int32 OEMC_termResGetRegisteredGroup (M_Char * szStatus, M_Char * resGroupList, M_Int32 bufSize), and the parameter 'szStatus' indicates a specific state of a terminal where a group list to be returned is set. "IDLE", "INCOMING", "POWERON", "POWEROFF", "BROWSERON", "BROWSEROFF" ) ", And so on. 'ResGroupList' is a terminal resource group list having terminal resources registered in the specific terminal state as described above, and 'bufSize' refers to a buffer size of the terminal resource group list.

If the list of resource groups registered in a specific state of the terminal is successfully returned, '0' is returned. If the size of the buffer to contain the return value is small, 'M_E_SHORTBUF' is set. If the resource group set in the specific state does not exist In case of 'M_E_NORES', 'M_E_INVALID' is returned if the parameter passed is wrong.

Next, the registered resource name return (OEMC_termResGetRegisteredInfo) API 311 returns a resource name registered in the terminal specific state (szStatus) among resources belonging to the resource group (resGroupName), and the prototype is M_Int32 OEMC_termResGetRegisteredInfo (M_Char * resGroupName , M_Char * pResName, M_Int32 resNameSize, M_Char * szStatus).

The parameter 'resGroupName' is the resource group name, 'pResName' is the name of the resource (name obtained through OEMC_termResGetList (resource name list return API 303)), and 'resNameSize' is the size of the resource name buffer, 'szStatus' Refers to the terminal specific status, and the terminal specific status is "IDLE (standby screen)", "INCOMING (call incoming screen)", "POWERON (terminal drive screen)", "POWEROFF (terminal end screen)", "BROWSERON (browser) Drive screen) "and" BROWSEROFF (browser end screen) ".

The return value is '0' on success, 'M_E_ERROR' if unsuccessful for unknown reasons, 'M_E_INVALID' if the parameter passed is incorrect, 'M_E_ACCESSDENY' if the user does not have permission to set, and the resource 'M_E_INVALIDSTATUS' if there is no association between the UE-specific state and 'M_E_NORES' if there is no resource set in a specific state, or 'M_E_SHORTBUF' if the resource name buffer size is small, or a resource group whose registration function is not supported. In this case, 'M_E_NOTSUP' is used.

The registration resource name return API 311 also does not operate in the call list resource group and the phonebook resource group, as in the resource registration API 309.

Next, the registered resource ID return (OEMC_termResGetID) API 312 is a function that returns a specific ID when an ID corresponding to a resource corresponding to a given resource name is set among resources belonging to a resource group (resGroupName). In this case, the specific ID means a unique ID of a resource allocated by a network provider or a contents provider.

The prototype of the function is M_Int32 OEMC_termResGetID (M_Char * resGroupName, M_Char * resName, M_Char * szID, M_Uint32 idSize), the parameter 'resGroupName' is the resource group name, and 'resName' is the name of the resource (OEMC_termResGetList (resource name). Name obtained through the list return API 303), 'szID' indicates a specific resource ID, and 'idSize' indicates a buffer size of the resource ID.

At this time, if the ID is successfully returned, '0' is returned. If it fails for an unknown reason, 'M_E_ERROR' is set. If the buffer size passed is smaller than the returned string, 'M_E_SHORTBUF' is set. If not, it returns 'M_E_HASNOUID', 'M_E_INVALID' if the parameter passed is wrong, and 'M_E_NOTSUP' if the resource group has no ID assigned.

Here, as in the registration resource name return API 311 and the resource registration API 309, the call list resource group and the phone book resource group are not operated.

Next, the resource group locked state return (OEMC_termResGetGroupLockState) API 313 returns a state of whether the resource group is locked. The prototype is M_Int32 OEMC_termResGetGroupLockState (M_Char * resGroupName), and the parameter 'resGroupName' indicates the locked state. Resource group name to return.

In this case, 'MC_LOCK_GROUP' is returned if the group of the corresponding resource is set to all locked state, 'MC_UNLOCK_GROUP' is returned if the entire resource group is not locked, and if it fails for an unknown reason The parameter passed 'M_E_ERROR', 'M_E_NOTSUPPORTLOCK' if neither the resource group nor the resource supports locking, or 'M_E_NOTSUPPORTGLOCK' if the locking of individual resources is not supported without group locking. If the variable is invalid, 'M_E_INVALID' is returned.

Next, the resource lock status return (OEMC_termResGetLockState) API 314 returns a locked state of a resource corresponding to a given resource name among resources belonging to a resource group (resGroupName). The prototype is M_Int32 OEMC_termResGetLockState (M_Char * resGroupName, M_Char * resName), the parameter 'resGroupName' is the name of the resource group, and 'resName' is the name of the resource.

In this case, 'MC_LOCK_ PRIVATE' is returned if the resource is locked, 'MC_UNLOCK_PRIVATE' if the resource is not locked, and 'M_E_ERROR' if it fails for an unknown reason. , 'M_E_NOTSUPPORTLOCK' if the resource group and resource does not support locking, or 'M_E_NOTSUPPORTPLOCK' if the group's locking is supported but individual resources are not supported, or 'M_E_NOTSUPPORTPLOCK' if the parameter passed is invalid. M_E_INVALID 'is returned.

Next, the resource group lock on / off (OEMC_termResSetGroupLockState) API 315 sets / releases the lock of the resource group. The prototype is M_Int32 OEMC_termResSetGroupLockState (M_Char * resGroupName, M_Boolean bSet).

The parameter 'resGroupName' represents the resource group name, 'bSet' represents the lock on / off setting. It is 'TRUE' for lock setting and 'FALSE' for unlocking.

The return value is '0' on success, 'M_E_ERROR' on failure for unknown reason, 'M_E_NOTSUPPORTLOCK' if the resource group / resource does not support locking, and individual locking but not group locking. If not, use 'M_E_NOTSUPPORTGLOCK' or 'M_E_INVALID' if the parameter passed is incorrect.

Next, the resource lock on / off (OEMC_termResSetLockState) API 316 sets / unlocks a resource corresponding to a given resource name among resources belonging to a resource group (resGroupName). The prototype is M_Int32 OEMC_termResSetLockState (M_Char * resGroupName , M_Char * resName, M_Boolean bSet). '

The parameter 'resGroupName' is the resource group name, 'resName' is the name of the resource, 'bSet' is locked / unlocked. It is 'TRUE' when locked and 'FALSE' when unlocked.

The return value is '0' on success, 'M_E_ERROR' on failure for unknown reason, 'M_E_NOTSUPPORTLOCK' if the resource group / resource does not support locking, or group locking but not individual locking. If not, use 'M_E_NOTSUPPORTPLOCK' or 'M_E_INVALID' if the parameter passed is incorrect.

Next, the password check (OEMC_termResCheckPassword) API 317 checks if the resource corresponding to the given resource name of the given resource group (resGroupName) is locked and if the password (password) necessary to unlock the lock corresponds to the given szPassword. The prototype is M_Int32 OEMC_termResCheckPassword (M_Char * resGroupName, M_Char * resName, M_Char * szPassword).

The parameter 'resGroupName' of the function represents a resource group name, 'resName' represents a resource name, and 'szPassword' represents a password.

The return value is '0' on success, 'M_E_ERROR' if unsuccessful for unknown reasons, 'M_E_INVALIDRESGROUP' if the resource group passed is invalid, or 'M_E_INVALIDTERMRES' if the name of the passed resource is invalid. If the parameter is incorrect, use 'M_E_INVALID', 'M_E_NOTSUP' if the resource group does not support a password, or 'M_E_INCORRECTPASSWORD' if the password does not match.

In this case, when one password is applied to the entire resource group, the name of the resource is ignored. When one password is applied to all resource groups of the entire terminal, both the name of the resource group and the name of the resource are ignored.

Next, the Register Carbell Bell (OEMC_termResSetCharacbell) API 318 sets the MMF data to the character bell. The prototype is M_Int32 OEMC_termResSetCharacbell (M_Byte * pbData, M_Uint32 nLength, M_Char * resName, M_Int16 nCallerNum), and the M_er * parameter. Where 'pbData' is the MMF data, 'nLength' is the MMF data length, 'resName' is the name of the character, 'nCallerNum' is the number of called numbers to be set in the character, and 'szCallerNum' is the character. Called party list to be set.

When the 'nCallerNum' is 2, the called number list has two numbers, '011-444-1234' and '011-234-4567', such as "0114441234 \ 00112344567 \ 0 \ 0".

The return value is '0' on success, 'M_E_ERROR' on failure for unknown reason, 'M_E_NOTSUPPORTCBELL' on unsupported character string, 'M_E_INVALIDFORMAT' on unsupported format, or duplicate name. 'M_E_DUPNAME' is used, and 'M_E_TOOMANYPARAM' is used when more parameters are passed than the Carrick Bell called number supported by the terminal.

In this case, the character bell refers to a bundle of image / ring data to be shown to the user when an incoming call is received from a specific number, and the MMF data is a data format having the title and the ringtone and the image data together. When the MMF data is set to the character bell using the character bell registration API 318, the images and the ringtones included in the MMF data are the same as those using the resource data light API 307 such as "PICTUREMATE" and "MUSICBELL ( Music bell) "is added to the resource group.

Next, the resource storage free space return (OEMC_termResGetFreeSpace) API 319 obtains the amount of free space, which is the remaining resource storage space, in bytes. The prototype is M_Int32 OEMC_termResGetFreeSpace (M_Int32 * pdwSize), and the parameter 'pdwSize' is The amount of space left.

The return value uses '0' on success and 'M_E_ERROR' if it fails for unknown reasons, and the resource storage free space return API 319 assumes that a group of all resources uses one storage space.

Through the resource management APIs described above, resources of terminals classified by groups and by MIME type may be commonly managed.

As those skilled in the art to which the present invention pertains may implement the present invention in other specific forms without changing the technical spirit or essential features, the embodiments described above should be understood as illustrative and not restrictive in all aspects. Should be. The scope of the present invention is shown by the following claims rather than the detailed description, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included in the scope of the present invention. do.

Accordingly, a mobile communication terminal equipped with a mobile platform supporting common management of resources of the present invention divides the resources of the terminal into groups, and a formal API for managing each resource by group through a MIME type for each group. By providing, new group can be managed effectively through MIME type by adding only group and MIME type without adding API when new resource is added, and resource management can be managed only by API extension without adding API when new resource is added. There is an effect that it is possible.

1 is a structural diagram of a mobile platform according to an embodiment of the present invention;

2 is a resource group table according to an embodiment of the present invention;

3 is a first table illustrating a MIME type classification for each resource according to an embodiment of the present invention;

4 is a second table showing a MIME type classification for each resource according to an embodiment of the present invention;

5 is a diagram showing a first API table according to an embodiment of the present invention;

6 is a second API table according to an embodiment of the present invention.

<Description of Symbols for Main Parts of Drawings>

10: handset hardware (H / W) 20: operating system layer module

30: application layer module 31: handset application layer module

32: Runtime Engine 33: API Layer Module

40: application

Claims (21)

Including a handset hardware (H / W), an operating system (OS) layer module including a CPU chip of a terminal supporting a wireless Internet environment, and a modem chip processor for call processing, an application layer module for executing an application on a platform In the mobile communication terminal equipped with a mobile platform is configured, The mobile communication terminal classifies and stores the resources of the terminal having a specific data format according to the group and the MIME type, The application layer module may include an API layer module including a resource management API for common management of terminal resources classified according to the group and the MIME type, and call the corresponding function registered in the platform to commonly manage the resources of the terminal. A mobile communication terminal equipped with a mobile platform for supporting common management of resources, characterized in that to enable. The method of claim 1, The API layer module, Includes a resource group list return API for returning a list of resource groups supported by the current terminal, The resource group list return API uses a parameter including a name of a resource group and a size of a buffer in which a return value is to be stored. A mobile communication terminal equipped with a mobile platform that supports common management of resources. The method of claim 1, The API layer module, It includes a resource item number return API for returning the number of resource items belonging to a specific resource group, The resource item number return API uses a parameter including a name of a resource group and the number of corresponding resources, the mobile communication terminal equipped with a mobile platform supporting common management of resources. The method of claim 1, The API layer module, Includes a resource name return API to return a list of names of resources belonging to a specific resource group. The resource name list return API uses a parameter including a name of a resource group, a name for each resource, and a size of a buffer to store a return value. Mobile communication terminal. The method of claim 4, wherein If the resource group for which the name list is to be returned is a call list, The name of the resource group which is a parameter of the resource name list return API is a combination of a call / call number and a call / call time. The mobile communication terminal equipped with a mobile platform that supports common management of resources. The method of claim 1, The API layer module, Includes a resource data format return API for returning the data format of a specific resource. The resource data format return API uses parameters including a name of a resource group including a resource for which the format is to be returned, a name of the corresponding resource, a data format, and a buffer size. Mobile communication terminal equipped with a mobile platform. The method of claim 1, The API layer module, Includes a resource data size return API for returning the data size of a specific resource. The resource data size return API supports a common management of resources, using parameters including a name of a resource group including a resource to return the size of data, a name of the corresponding resource, and a size of the resource data. Mobile communication terminal equipped with a mobile platform. The method of claim 1, The API layer module, Contains resource data return APIs for returning specific resource data, The resource data return API uses a parameter including a name of a resource group containing a resource to return data, a name of the resource, actual data of the resource, and a size of a buffer to hold the data. Mobile communication terminal equipped with a mobile platform that supports common management. The method of claim 1, The API layer module, Includes a resource data write API for writing resource data in a specific format to a specific resource group. The resource data write API uses a parameter including a resource group name, a resource name, a format of resource data to be written, resource data to be written, and a size of a buffer to hold the resource data. Mobile communication terminal equipped with a mobile platform that supports management. The method of claim 1, The API layer module, Includes a resource data deletion API for deleting resource data contained in a specific resource group. The resource data deletion API uses a parameter including a resource group name and a name of a resource to be deleted, the mobile communication terminal equipped with a mobile platform supporting common management of resources. The method of claim 1, The API layer module, It includes a resource registration API for registering resources included in a specific resource group in a specific state of the terminal, The resource registration API is a mobile communication terminal equipped with a mobile platform that supports common management of resources, characterized in that it uses a parameter including the name of the resource group, the name of the resource, the specific state of the terminal to register the resource. The method of claim 1, The API layer module, Includes a registered resource group list return API for returning a list of resource groups registered in a specific state of the terminal, The registered resource group list return API includes a specific state of a terminal in which the resource group to be returned is registered, a resource group list of a terminal having resources of a terminal registered in the specific terminal state, and a size of a buffer to hold a terminal resource group list. A mobile communication terminal equipped with a mobile platform that supports common management of resources, characterized in that using a parameter. The method of claim 1, The API layer module, Includes a registered resource name return API for returning a resource name registered in a specific state of a terminal among resources belonging to a specific resource group. The registration resource name return API uses a parameter including a resource group name including the resource to be returned, a name of the resource, a size of a buffer to contain the resource name, and a specific state of a terminal in which the resource to be returned is registered. A mobile communication terminal equipped with a mobile platform that supports common management of resources. The method of claim 1, The API layer module, Includes a registered resource ID return API for returning an identifier (ID) set for a resource corresponding to a given resource name among resources belonging to a resource group. The registered resource ID return API uses a parameter including a name of the resource group, a name of a corresponding resource, an identifier (ID) of the resource, and a size of a buffer to hold the identifier (ID). Mobile communication terminal equipped with a mobile platform that supports common management. The method of claim 1, The API layer module, Includes the resource group locked state return API to return the locked state of a specific resource group. The resource group locked state return API uses a name of a resource group as a parameter, and whether the resource group is locked is included in a return value. The mobile communication terminal equipped with a mobile platform that supports common management of resources. The method of claim 1, The API layer module, Includes a resource locked state return API for returning the locked state of a specific resource in a specific resource group. The resource locked state return API uses a parameter including a resource group name and a resource name, and whether the resource is locked is included in a return value. Terminal. The method of claim 1, The API layer module, Includes resource group lock on / off API for enabling and releasing the lock state of a specific resource group. The resource group locked setting / release API is a mobile communication terminal equipped with a mobile platform that supports common management of resources, characterized in that it uses a parameter including a resource group name, lock setting / release. The method of claim 1, The API layer module, Includes resource lock on / off APIs for setting and releasing locks for specific resources. The resource lock setting / release API is a mobile communication terminal equipped with a mobile platform that supports common management of resources, using a parameter including a resource group name, resource name, lock setting / release. The method of claim 1, The API layer module, It includes a password check API for checking whether a password required for unlocking a resource corresponding to a specific resource name of a specific resource group is identical to a given password. The password check API is a mobile communication terminal equipped with a mobile platform that supports the common management of resources, characterized in that using the parameters including the name of the resource group, resource name, password. The method of claim 1, The API layer module, As a character bell which is a combination of an image and a ringtone to be displayed on a terminal when a call is received from a specific number, it includes a character bell registration API for setting specific MMF data. The character registration API uses a parameter including MMF data to be set, a length of the MMF data, a name of a character bell resource, the number of called numbers to be set in a character bell, and a list of called numbers to be set in a character bell. A mobile communication terminal equipped with a mobile platform that supports common management of resources. The method of claim 1, The API layer module, Resource storage free space return API for returning the free space size of the resource storage space remaining in the terminal, The resource storage free space return API is a mobile communication terminal equipped with a mobile platform that supports common management of resources, characterized in that the size of the remaining space as a parameter.