JP2010238254A - Method and apparatus for providing content to mobile terminal - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method and an apparatus for providing content to a mobile terminal. <P>SOLUTION: The method for providing content to a mobile terminal includes the steps of: receiving data at the mobile terminal; classifying the content data in accordance with classification data comprised within the content data; storing the content data within the mobile terminal; creating an access object whereby the content data may be accessed; and associating the access object with further access objects having similar classification codes. This method has a significant effect in simplifying the provision of content to mobile terminals. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to the field of providing content to a mobile terminal, and more particularly to the classification and storage of content data in the mobile terminal.

  It is already possible to use a mobile handset that uses wireless technology to browse remote content for communication links. This content is available via the Internet, but can also be created for a mobile phone handset using, for example, a wireless application protocol (WAP). A user typically opens such a session by opening a browser on the terminal and entering the address of the content he wishes to access, or more simply selecting a bookmark that provides a shortcut to the address. This bookmark is input and stored in advance. It is convenient to follow the well-established URL (Uniform Resource Locator) format.

Such browsing behavior is different from other forms of use of the handset, ie local use such as local address book content management or local game play, ie use without connection.
This means of accessing remote content has many drawbacks for the user in terms of ease of use. First of all, URL input is a rather cumbersome and error-prone task, especially for small mobile handsets that typically do not have a regular-sized QWERTY layout keyboard. If a bookmark is used, there is a risk that the bookmark will expire and it is difficult to manage within the small screen user interface (if the handset has such a feature) Disadvantages include the need for users to create categories and remember the meaning of these categories, and the remote content owner's means of presenting or transferring content to the user is compelling.
This is only achieved by the user visiting or bookmarking the site, ie sending a message containing the bookmark to the user. Such things or transmissions are generally considered to be intrusive and annoying.

  The present invention provides a solution to the ease of use problem and also finds the appropriate remote content when the user needs it, and the appropriate service in a way that the remote content owner is simple, attractive and intrusive. Presents a greatly improved means for presenting.

  According to a first aspect of the present invention, a method for providing content to a mobile terminal is provided. In this method, data is received by the mobile terminal, the content data is classified according to the classification data in the content data, the content data is stored in the mobile terminal, and the content data is accessible. It consists of creating an object and associating the access object with a further access object having a similar classification code.

In accordance with a second aspect of the present invention, a content installation module for a mobile terminal is provided. When used, this module classifies the content data according to the classification data in the content data and creates an access object for accessing the content data.
This access object is associated with a further access object having similar classification data. The access object may be content data or a hyperlink to content data.
Access objects are preferably stored in a hierarchical tree structure. When receiving content data with a new classification code, the hierarchical tree structure expands.

  A computer software program that implements the first and second aspects of the present invention may be provided on a computer readable data carrier. The content data may be content for display by a terminal such as text, audio, video, etc., or may be an object that can be executed by the terminal. Objects that can be dealt with by a terminal are, for example, JAVA (registered trademark) applets and MIDlets.

  The invention will now be described, by way of example only, with reference to the following drawings.

FIG. 1 is a schematic view of a portable terminal of the present invention. FIG. 2 is a schematic diagram of a process in which content is provided to a mobile terminal. FIG. 3 is a schematic diagram of a process in which data content is displayed on the display device 110 of the mobile terminal 100. FIG. 4 is a schematic diagram representing local or remote content on a mobile terminal.

FIG. 1 shows a portable terminal 100 suitable for use with the present invention. The portable terminal includes a radio antenna 105, a display device 110, and a user input device 120. Display device 110 displays a number of items consisting of or associated with hyperlinks, such as, for example, visible text or images.
When a hyperlink is selected using a user input device, the mobile terminal displays additional items associated with the hyperlink, such as an optional menu or data file.
Items associated with the hyperlink are stored locally in the mobile terminal or in the remote data store 210. The remote data store 210 is connected to the mobile terminal by the wireless communication network 200. The user is presented with a display as to whether the item is stored locally or remotely, while the local and remote items are presented to the user together on the display device. For example, the display device shows a menu with options of “News”, “Sports”, “Entertainment”, “Business”, “Games”, “Horoscope”.
Selection of the “News” menu presents a list of several headlines. This list of headlines is stored locally and downloaded from the content provider's data store 220.
The data store 220 is connected to the mobile terminal by the wireless communication network 200. Upon selecting one of these headlines, the mobile terminal connects to the remote data store 220 and downloads content (text, audio, video, etc.) associated with the selected headline. Many similar arrangements are provided for other menus. Some of this content is stored locally and others are stored remotely. The menu includes many submenus. For example, the “News” menu links to many headlines and / or many sub-menus, such as “Domestic News”, “Regional News”, “International News”, “Political News”, etc.
For example, if the user enters a birthday into the local base application, this information is provided to the remote application, creating a horoscope for this birthday. This horoscope can be stored locally on the mobile terminal, i.e. refer to the appropriate horoscope data stored in the remote data store by a local hyperlink.

A user interface (UI) for a portable terminal or the like is conveniently created using a markup language (ML). The markup language creates a user screen locally using the UI engine 150, which can create ML-compliant data that is provided to the browser 160 for display on the display device 110. is there.
The standard markup language used in portable terminals is HTML (Hypertext Markup Language) or WML (Wireless Markup Language).

It is clear from the above that it is necessary for the terminal to receive temporary updates of data content stored locally and with hyperlinks, along with any associated content, in order to reference content stored remotely. It is.
These updates need to be received over the wireless communication network 200 and installed in the mobile terminal, the content is stored correctly in the menu-based hierarchy, and the hierarchy can be accessed by the user. it can.

  FIG. 2 shows a schematic diagram of the process by which content is transmitted to the mobile terminal, where data content is transmitted to the mobile terminal 100 over the wireless communication network 200. Incoming data content is suitable for use on a mobile device (eg, content type (eg, content type (eg, error checking and / or error correction code)). Video, audio, text, etc.) is processed by the evaluation module 130 to ensure that the terminal has sufficient storage capacity to store content suitable for a particular mobile terminal or the like.

The content data is then processed by the installation module 140, and entries are made in the log file to assist with the management and deletion that follows the data content. Preferably, the content data includes one or more of the following features:
A unique identifier to simplify the deletion, modification or overwriting of content data.
A version number corresponding to the lowest version of the installation module 140 for the content data to operate smoothly.
A content category that allows the installer to place content in the menu structure and in the most appropriate location in the page. Reduced or hierarchical categories allow content to be referenced from multiple menus and submenus.
The start date and time before the content is no longer available to users.
Expiration date and time after the above content is no longer available to users.
A tag for displaying whether the user has the right to delete content.
A tag for displaying whether the user has the right to share content with other mobile terminals.
Local content such as visible content (text or images), animated graphics, other multimedia content such as audio and video, telephone numbers and descriptors, email addresses and descriptors, JavaScript components A data payload that can consist of logic elements for managing operations, links to newly installed pages, links to remote content, methods for installing pages into the user interface tree, and so on.
A digital rights management scheme that can be used to protect data payloads from unauthorized copying, sharing or overuse.

Examples of such data content are shown below in Annex A using XML (Extensible Markup Language), which provides much higher functionality than the more universally used HTML Have the ability.
Preferably, the installation module is implemented using XML and functionality updates are easily applied.
The nature and format of the content provided to the user terminal can be controlled directly by the terminal user, or the user can register one or more content providers with multiple interests. .
Local content can usually be provided free of charge, while the user is charged for access to the remote content, and once charged, the remote content is stored locally. Advertisements can be used to subsidize the cost of content equipment.
The types of links to possible content, such as remotely stored content, are virtually unlimited and news, sports, jokes, digital music (eg MP3 files), music information, network operators and terminal manufacturing support without restrictions • Access to services, games and online games, new user revenue and course details, phone number guidance, mobile commerce accounts.
Local content is displayed to represent differences from remote content through the use of different text fonts or colors or through the insertion of an icon next to the appropriate link. This communicates to the user that there is a cost or delay in transmission before accessing the content.

FIG. 4 illustrates how local content and remote content are represented on a mobile terminal. FIG. 4a shows some links, some of which are local content (ie calendar data) and some are remote content (ie taxi service and date service). .
FIG. 4b shows the result of focusing on the date service link (ie, positioning a cursor or other selection device on the link without selecting the link). Once the link has been selected, the remote content must be downloaded and FIG. 4c shows the page shown while the remote content is acquired.
Preferably, this page is stored locally, but if it is stored remotely, it should be designed for downloading in the next smallest possible time. FIG. 4d shows a remote content page distributed to the mobile terminal.

FIG. 3 shows a schematic diagram of a process in which data content is shown on the display on the display device 110 of the mobile terminal 100. The data content is shown by the browser 160 through a representation of markup language compatible data.
The browser consists of a JAVA virtual machine (JVM) 162 to allow Java applets to be implemented in the terminal (or to provide a separate JVM). The user selects a hyperlinked data item using the user input device 120, and the UI engine interprets this selection, and the data item referenced by the hyperlink is stored locally (ie, the mobile device). Or whether it is stored remotely (ie, on a content server connected to the terminal by a wireless communication network).

If the data item is stored locally, the UI engine 150 sends a request to the content database system 170 comprising the database API 172, the database engine 174, and the database 176, and the database is stored in the storage device 178. The UI engine request is decrypted by the database API 172 and the decrypted request is passed to the database engine 174.
The database engine then queries the database 176 using the decrypted request, and the database returns raw content data regarding the original UI engine request to the database engine that forwards the data to the database API. The database API then places the raw content data in an XML wrapper and sends it to the UI engine. Due to the content data and other nature of the user's selection device (user preferences), the UI engine can send the content data directly to the browser 160 where the content is displayed to the user.
The UI engine sends one or more XSL (eXtended Style Language Extended Style Language) style sheets to the content data (data) before sending the data to the browser where the formatted data is displayed and presented to the user in the desired format. Apply to other formats suitable for display in browsers such as HTML, WML, etc.).

When the data item selected by the hyperlink selected by the user is stored remotely, the UI engine prompts the browser to send a request to the network location indicated by the selected hyperlink. Browser requests are sent over the protocol stack 182 required for accurate communication over the wireless communication network.
The protocol stack is a standard TCP / IP protocol and physical layer protocol that allows mobile devices to communicate with the Internet host and transport layer (eg third generation UMTS that allows mobile devices to access and communicate through a wireless communication network). Protocol). The mobile terminal establishes a communication link between a network access server (NAS) 310 and a radio interface 190 that routes browser requests to the appropriate content server 330 via the Internet 320.

The content server 320 confirms that the mobile terminal that generates the request can access the requested content (for example, a user registered in the server, sufficient credit in an account for purchasing the content, etc.). The content is then transmitted to the NAS via the Internet. The content is then transmitted through a wireless communication link to a mobile terminal that is received at the radio interface. The data content packet passes through the protocol stack from which the content is extracted and the content is sent to the browser.
Depending on the nature and format of the content, the browser can be displayed on the display device (either directly or by using additional functionality provided by the plug-in module) or displayed by the browser Causes the content data to be routed to the UI engine to have an XSL stylesheet applied to transform the content data into a format.

As the data is sent and / or received at the entity by the entity, some processing is performed, so that XML and XSL processing of the data is performed, for example, in the UI engine or browser, or in the separate XML processing module 180. Are known to be centrally processed or distributed among one or more of the entities described above.

  If the content is a MIDlet (Mobile Information Device Application) ID, the JVM will instantiate the style format without applying it to the MIDlet (or if it is remotely located, install the MIDlet And materialize).

As described above, the remote content has a content tag, and the content tag is easily incorporated into a page description as an HTML tag such as <categoryl> Sport </ categoryl>. In this case, the installation module 140 searches for a sports menu (i.e., submenu) where the content is accessible. In addition, content can be accessed from recently downloaded or additional menus for recently accessed content.
The installation module recognizes that football is a subset of sports, for example if the tag is football, and stores the content in the sports menu if there is no football submenu.

  If there is no dedicated sports menu, a link to the content is added to the General or Miscellaneous menu so that the user can access the content. Instead, the installation module prompts the user to create a sports menu and saves a link to new content within the menu. As a further alternative, the remote content is displayed in a random sequence.

  Further, the tag is inserted into content such as <categoryl> Sport </ categoryl> located at a location considered suitable for insertion of an advertisement by the content layout designer.

  Some contents have a plurality of tags such as “sports” and “advertisements”. In receiving this content, the installation module attempts to insert the content into the sports menu at the first point where an empty ad tag exists. If no such ad tag is found, the installer will try to insert the content at the end of the sports page. If multiple sports menus and submenus are found, the installer places the content at the top of the menu hierarchy. New content is installed in the menu created by the previous installation. If the content is an updated version of the previously downloaded content or its advanced version, the new content is inserted or overwritten on the previously downloaded content.

  Remote content installed by the user (even if the permission tag is not displayed to prevent the user from deleting it), by the expiration date of the expiration date, or via the network using the unique identifier of the content It is also deleted by the transmitted command. If new content is installed in order, the page will not be deleted or revoked, so it will not be deleted or revoked. The user can view all the contents installed in the handset, for example, in chronological order. Similarly, some or all of the installed contents can be deleted.

  Content is installed in one of two ways. The installation module keeps a record of the insertion (content and recipient page) so that the content can be deleted later, while inserting the received content into a page already on the database using a cut and paste scheme.

Alternatively, the received content is placed in a separate library and a link to the content is inserted into the target page. In the latter case, the UI engine builds that link to actively establish all pages. The advantage of using this method is that the page content is varied and more remote content can occur in the optimally positioned path depending on the user's choice.
For example, if a sports advertisement is received, but there is no sports page at that time, the installer will place the sports advertisement on a general or miscellaneous miscellaneous page. However, if a sports page is received and subsequently installed, the installer can then move the link for the sports advertisement to a more appropriate location.

As an alternative to putting received content into a location determined by a tag on the page description HTML, in another embodiment, the content data is placed in a predetermined fixed slot when the terminal is placed in the environment. An example of such a location is a fixed slice of the screen area, the top of the soft key area and the bottom of the main application pane. This area is specified by linking with the tab type.
For example, <category1> ScreenSpace </ category1>. Such slots are arbitrarily shaped (including non-rectangular) and are present at any screen position. The nature of the slot (shape, size, transparency) is native and can be controlled and changed by the use of an appropriate command channel. It can be seen that the array is expanded to include multiple slots.

The received content that produces such a tag type is located in that slot. A number of items of received content corresponding to the tag are displayed continuously or randomly. Alternatively, clearly the area behind the main application pane is also designed as a fixed slot. This location allows the material to be displayed faintly in the manner of a slight watermark on a piece of paper, but constantly present in the background in the middle of any or all pages.

Some UI technologies allow the user or operator to change the theme of the handset UI (sometimes represented as a UI skin). This is either in the handset, either by selecting from a pre-installed set of pre-installed skins and downloading a new skin to be installed on the handset from a local or remote network Alternatively, it can be achieved through a plug-in device that is a high-sensitivity skin (for example, a mutual hold, application number GB0128654.1 or a high-sensitivity skin product manufactured by Wildseed Ltd.).
The installation module is compatible with such a system and can take advantage of that system by forcing persistence in the UI class. Therefore, the installed download data remains present and visible after the skin change, although the appearance of that data is changed by the new skin application.
Optionally, the download data includes additional indicator tags to identify whether the item exists behind the new skin application and remains visible, and whether the new skin does not display content. Including.

  Download theme changes also include sound events as part or all of the content. Sound events subject to update, including message alert, battery status display, key press tone, game tone, cover open / close tone, start, without ring tone (which is already widely used) restrictions Special tone for displaying start-up while being adjusted by up / shutdown tones, signal level and radio adaptation alerts, time alarms, calendar events, error conditions, or prominent messages in the inbox Any combination of the above. These can be used alone or linked to graphical display events.

  Even if the user selects content to be downloaded, it is transmitted in response to the user's request unless the user requests that the transmission be deferred. However, if the content or network provider pushes the content to a mobile terminal, this preferably occurs in the background, for example at night or according to special usage, without inconvenience the user. When the user uses the mobile terminal, this content pushing is suspended.

  The distribution of installed content is unique (uniquely addressed) for a particular handset. Alternatively, some content is broadcast in a large number assigned to many handsets using known transmission techniques. Installed content is housed in a multimedia messaging system (MMS), including remote content that uses a unique MIME (Multipurpose Internet Mail Extension) as in x-vnd.3glab-triglet. It is preferably contained within a multimedia message such as an MMS. EMS (extended message transmission system) and WAP pushing are also adapted to the distribution function.

Mobile devices are not always within network radio adaptation (outside service areas, inside tunnels, etc.). By including a certain amount of visible local content, the user can be prevented from deviating to some extent.
For example, a news headline can be read without the user being able to follow a link to access more details. For example, a link that is inaccessible because the handset is out of network radio adaptation, the link is clearly visible, including a different color font or making the link unselectable. The user is informed in a visible manner.

This change is performed by the UI engine to receive an input signal from the radio subsection to inform the status of the wireless data link and make this signal a visible attribute of the link before delivering the content to the local browser. Used to correct. This modification can be done by changing the stored database, for example by changing the link text color of all remote links in all pages to gray. Alternatively, the text color of the remote link is quickly corrected before rendering.
In either case, it is necessary to distinguish between local content and remote content. By having the internet protocol address 127.0.0.1 used by the rules for specifying the local host for all local links, or the local link is the host name, eg / localdirectory / page. By negotiating to exclude html, this can be done by checking http: // on the links that are required in advance to point to non-local resources.

In addition to content such as text, audio, or video, the present invention can be used to install Java-based application programs on a mobile terminal. Java 2 Micro Edition (J2ME) provides one platform.
Through the platform, a Java (registered trademark) Virtual Machine (VM) is created in the mobile terminal. This is possible even with a terminal having a small capacity as compared with a personal computer. An application conforming to Java (registered trademark) is generally called an applet, but is executed in a VM.
The VM allows applets to function across many different platforms (as long as the platform can support the VM). The applet is properly constructed using J2ME and is compatible with various other Java®. Thus, such an applet is executed by a terminal from a mobile phone to a desktop personal computer.
Mobile terminals such as mobile phones have very different capabilities such as processor speed, memory, display size and the like. Mobile Information Device Profile (MIDP) has been identified to assist applet compatibility when running across these portable terminals. An applet conforming to MIDP is generally called a MIDlet.

  Mobile device users want to install or uninstall MIDlets as desired, while handset manufacturers and network operators want to supply handsets with pre-installed MIDlets .

In addition, service and content providers want to place MIDlets on their mobile terminals when users want to pay to access additional MIDlets or other forms of content.

  For example, the MIDlet is embodied by the user selecting the highlighted icon or text portion using the keypad of the mobile terminal. The MIDlet is then executed in the Java VM in response to user input or data received from an external source. An example of the external source is a data base stored in a terminal or on a remote server.

  Within a more advanced environment, a MIDlet is instantiated by entering the name of the MIDlet on the command line. Obviously, this form may be inappropriate for portable terminals with limited keypads, but in this case a more suitable mechanism for implementing MIDLet is provided. For example, it may be a hyperlink icon or a text label. As mentioned above, this allows a hyperlink for the MIDlet to be inserted somewhere in the UI. The MIDlet provides an identification (ID) tag, which is used as a basis for recognizing hyperlinks.

  The MIDlet may be installed in a specific part in the terminal, or the ID of the MIDlet at a location where the terminal is away may be accumulated. If the ID of a remote MIDlet is selected, the terminal downloads the MIDlet, installs and executes the MIDlet (if the user does not have sufficient access rights, the MIDlet will execute once The MIDlet will be uninstalled or deleted).

  The use of the method outlined above in connection with installing content can be used to install a MIDlet and provides many different benefits to the user. For example, the user can access the desired MIDlet directly from a convenient point in the UI, rather than having to navigate to a specific MIDlet page or service, the user can access the content along with the associated MIDlet. Allows linking. It also makes it easier for users to have a MIDlet provided by the installation of an ID item, which leads to the MIDlet portal, manages the download process, and runs the MIDlet as a separate program. Convenient. It also makes it easier for developers and operators to promote new MIDlet-based applications and services. This is because it is necessary to install the appropriate MIDlet ID in the user's UI rather than having to install the MIDlet itself.

  Furthermore, in a similar manner, if the network range is a range where the mobile terminal cannot be used, the ID hyperlink “grays out” to indicate that the MIDlet cannot be used. A MIDlet may have a “category tag”. The “category tag” defines the optimal location where MIDlets are stored in the UI or where the UI is placed in a pre-fixed slot. The MIDlet (or these IDs) may include a tag that allows (or prohibits) the user from deleting and / or distributing the MIDlet. The MIDlet ID may also be installed on a page that has been previously installed by downloading content (see above) at a remote location.

  While it is possible to install a MIDlet ID for a MIDlet located at a remote location without having to install the MIDlet itself, the MIDlet ID for the MIDlet accumulated in a specific part is installed with the corresponding MIDlet And need to be uninstalled.

  In contrast to the above method, where content at a remote location can take a variety of forms, the downloaded data is Java code content. It is typically the Java (registered trademark) archive (JAR) format. The present invention can be used to install a set of MIDlets. A set of MIDlets includes a plurality of MIDlets in the UI of the mobile terminal.

  The present invention is suitable for various mobile terminal applications, and is not limited to mobile phones. Even before the mobile use of data stored on the Internet and in remote locations became available, a personal digital assistant (PDA) with mobile communication capabilities (eg, Rim Blackberry Nokia 9210 Communicator ( RIM BlackBerry Nokia 9210 Communicator, Palm i705, etc.) or a mobile phone with features not previously seen (eg Nokia 5510 & 7650 or Ericsson T65) ) Is possible. In the future, mobile devices will continue to develop, their functions will expand, and the boundaries between PDAs and mobile phones will decrease. The present invention is applicable to all such devices, and is also applicable to laptops or portable computers with modems that allow mobile communication.

  The present invention is substantially applicable to wireless communication networks. For example, second generation digital cellular phone networks (ie, GSM, D-AMPS), 2.5 generation networks (GPRS, HSCSD, EDGE), and third generation UMTS networks. In buildings and campuses, other technologies (whether wireless or optical systems) such as Bluetooth or wireless LAN can be used.

  Computer software, UI engines and / or installation modules for performing the above methods can be provided on a data carrier such as a floppy disk, CD-ROM, non-volatile memory card.

Annex A
<? xml version = .0 # 62;
<triglet>

<ID> 1234-83745-5554-gjy </ ID>
<category>
Sports
<class>
Advert
</ class>
</ category>
<start> 2002-01-13 06:30:00 +0000 </ start>
<expire> 2002-01-17 17:30:00 +0000 </ expire>
<right>
<no_delete />
<no_share />
</ rights>
<html>
<body>
<li><a
href = sect ttp: //www.tickets4sale2u.com/special/wim/ # 62; Click
for great Wimbledon ticket offer! </a></li>
</ body>
</ html>
</ triglet>

Claims (28)

A method of providing content data to a mobile terminal, the method comprising:
(A) receiving content data in the portable terminal;
(B) classifying the content data according to the classification data in the content data;
(C) storing content data in the portable terminal;
(D) creating an access object that allows access to the content data;
(E) associating said access object with a further access object having a similar classification code.   The method of claim 1, wherein the access object is displayed on a display screen associated with a mobile terminal.   The method of claim 2, wherein the access object is displayed within a predetermined section of the display screen. One or more access objects are displayed on the display screen, and each of the one or more access objects is
(I) local control commands,
(Ii) content data stored in the portable terminal, or
(Iii) content data stored remotely from the portable terminal;
4. The method according to claim 2, wherein the method is associated with any one of the following.   The appearance of an access object associated with remotely stored content data is modified to display whether the mobile terminal is connected to a device where remotely stored content data is stored. The method according to claim 4.   6. A method according to claim 4 or 5, wherein the access object comprises data indicating whether the associated content data is made available to other terminals.   7. A method according to claim 1, wherein the access object consists of a first time value and is not displayed until the first time value is obtained.   8. A method as claimed in any preceding claim, wherein the access object comprises a second time value and the access object is displayed until the second time value is obtained.   9. A method as claimed in any preceding claim, wherein step (e) comprises creating a hierarchical tree structure to store the one or more access objects.   The method of claim 9, wherein step (e) further comprises expanding the hierarchical tree structure when content data comprising a new classification code is received.   10. The method according to claim 1, wherein the access object in step (d) comprises content data.   11. The method according to claim 1, wherein the access object created in step (d) comprises a hyperlink.   The method of claim 12, wherein the created access object comprises a hyperlink associated with content data.   The method of claim 13, wherein the content data is audio data.   The method of claim 12, wherein the created access object comprises a hyperlink associated with an executable object.   16. The method of claim 15, wherein the executable object is a MIDlet.   11. A method as claimed in any preceding claim, wherein the access object created in step (d) comprises a local control command.   17. A method according to any of claims 2 to 16, wherein the terminal displays a user interface page by displaying one or more access objects.   The method of claim 17, wherein the user interface page is updated by inserting one or more additional access objects.   19. A method according to claim 17 or 18, wherein the user interface page is updated by deleting one or more further access objects. A content installation module for mobile devices,
The module classifies the content data according to the classification data configured in the content data when used, and creates an access object for accessing the content data,
A content installation module, wherein the access object is associated with a further access object having similar classification data.   The content installation module of claim 20, wherein the module further displays an access object on a display screen associated with the mobile terminal.   The content installation module of claim 21, wherein the module displays the access object within a predetermined section of the display screen. The module displays one or more access objects on a display screen, and each of the one or more access objects includes:
(I) local control commands,
(Ii) content data stored in the portable terminal, or
(Iii) content data stored remotely from the portable terminal;
23. The content installation module according to claim 21, wherein the content installation module is associated with any one of the above.   The module modifies the appearance of an access object associated with remotely stored content data to indicate whether the mobile terminal is connected to a device where remotely stored content data is stored; 24. A content installation module according to claim 23.   25. A content installation module according to any of claims 20 to 24, wherein the module stores one or more access objects in a hierarchical tree structure.   26. The content installation module of claim 25, wherein the module expands the hierarchical tree structure when content data comprising a new classification code is received.   A data carrier comprising computer-executable code for performing the method according to any of claims 1 to 20.

Images