JP2007226773A - Method and device for changing user interface element on wireless device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To allow a UI skin package content provider to easily generate a new UI resource for a new/different mobile device for download and installation of a UI skin package to a mobile device of a user. <P>SOLUTION: A resource profile is defined by a device manufacturer for each model of mobile device. The resource profile specifies a composition, a format, and an appearance of one or more user interface elements displayed/executed by the mobile device. The resource comprises a file, a link to the file, and/or a data/program object associated with the configurable aspect of a user interface for each mobile device. The resource is provided in the form of a downloadable UI content package consisting of a description file and a resource file. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  Embodiments of the present invention generally relate to communication networks, and more particularly to user interface authoring tools and generation systems for mobile communication devices.

  Wireless mobile technology has evolved beyond simple point-to-point cell phones, leading to the proliferation of mobile devices, accessing data from a variety of different sources, and processing many different types of content data Is more possible than ever. Mobile services have been developed that allow users to download and use various types of data and programs, such as games, music, video clips, etc., on their mobile devices. This has expanded mobile phones beyond just communication devices, but has resulted in the development of various different types of mobile devices to utilize these different applications and services as a processing platform for a variety of different tasks. ing. For example, users can access cellular and web services, cellular phones, web-enabled mobile phones, home PCs, notebook computers, personal digital assistants (PDAs), mobile phones to access communications and Internet services. Game consoles, electronic mail (e-mail) devices, media playback devices, and any other type of network-enabled computer. Not only are new types of devices being developed, but now known devices, such as mobile phones, are also becoming increasingly integrated devices, bringing more capabilities together and combining phones / cameras. Like MP3 player devices, it integrates functions beyond their simple core functions.

  The widespread use of different services and devices on wireless networks has greatly expanded the different access protocols and user interfaces available on phones and similar devices. To help users manage their mobile and network devices, wireless devices and communication services are equipped with various forms of customization capabilities. For example, certain mobile phone service providers and equipment suppliers offer user interface (UI) customization capabilities that allow users to create custom ring tones, background displays (wallpaper), menu configurations, etc. Now it is possible to tailor their phone or mobile device to their preferences. The ability to change or customize the color, font, sound, and function of a device UI, commonly referred to as a “UI skin,” can significantly increase the marketability of the device.

  However, current UI customization schemes have certain drawbacks. For example, many customized features may be embedded deeply within a native UI or mobile device browser, which can be difficult or time consuming for the user, allowing many users Prevents the maximum use of customized features. Furthermore, current UI customization proposals are typically limited to the basic user interface of individual devices and are limited to allowing customization of just a few parameters of the device. . However, many mobile devices can now perform many different tasks, and even download and execute application programs. Current device customization features typically allow users to customize features related to the execution of downloadable application programs or utilities, as well as comprehensive customization across all of the functions that can be integrated into the device. I can't do that either.

  Most device manufacturers provide one default user interface per device model. Third party vendors often develop and provide customized features, called “UI skin packages”. For these third party content providers, providing customized features can involve many labor intensive or overhead tasks. Each device model on the market may have a unique UI format and specification. As new hardware is constantly being developed and released, new resource files must be written and maintained for each new specification of the mobile device. Currently, UI skin content providers typically have to obtain descriptors or profile parameters individually from the device manufacturer and compile them into resource files for each device UI. This is often a time consuming process and is very prone to errors due to the large amount of detailed data handled.

  Thus, UI skin package content providers can easily create new UI resources for new or different mobile devices and obtain these UI skin packages to download and install on the user's mobile device There is a need for a mobile device UI configuration system.

  In addition, under new network models, content data and even services or applications may be provided to end users by different third party companies other than the major service providers. Use of such third party content may utilize system resources that are not provided and maintained by the third party content provider, but are performed by the primary service provider. ing. However, because major service providers do not necessarily control the distribution and use of this third party content by the end user, the service provider monitors such usage and You may not be able to charge for distribution and use.

  Therefore, there is a need for a system that allows major service providers to charge and collect usage fees based on content provided by third parties to end users in the network.

  Embodiments of a mobile device user interface authoring tool and a modified resource application programming interface (API) are described. The aspects of one or more embodiments described herein may be implemented on one or more computers or computers that execute software instructions. The computers are in a network configuration and can be a client-server configuration or similar distributed computer network. Embodiments are directed to network systems that incorporate telecommunications or similar wireless network systems.

  A resource profile is defined by the device manufacturer for each model of mobile device. A resource profile specifies the composition, format, and appearance of one or more user interface elements that the mobile device displays or executes. The user interface authoring process performed by the content supplier maintains a common database of resources for each mobile device model. Resources comprise data or program objects associated with files, links to files, and / or configurable aspects of the user interface for each mobile device. Customizable aspects or items of the user interface are extracted from the selected resource profile and generate a description file for these aspects using the appropriate common resources. A resource provided by the common resource database is converted into a format specified by the resource profile, and a UI package generation unit generates a downloadable UI content package including a description file and a converted resource file. The mobile device handset includes UI content package data from a UI content server or a resource API for downloading locally stored UI content. The resource API incorporates a number of different plug-in content engines and engine selector components that allow application programs running on mobile handsets to access resources without requiring application modifications. Enable.

An embodiment of a user interface modification system in a wireless network is illustrated by way of example and not limitation in the accompanying drawing figures. In the drawings, like reference numerals indicate like elements.
(Detailed explanation)
FIG. 1 illustrates a communication network system 100 that implements one or more embodiments of a mobile device UI authoring tool. In system 100, a service provider's server computer provides network access to one or more mobile devices, such as mobile phones 108 and 109. In one embodiment, mobile devices 108 and 109 are cellular phones, and network 110 is a comprehensive telecommunications network that includes both a cellular phone network and the Internet. The network 110 may also include one or more wide area networks (WAN), local area networks (LAN), or any combination thereof. The server computer can be a wireless service provider or an internet service provider, or a combination of both. Mobile devices 108 and 109 communicate with each other and with other mobile devices through the wireless portion of network 110, through the cellular network. The mobile device can also be configured to communicate with one or more client and / or server computers that are directly or indirectly coupled to the network 110. Mobile devices 108 and 109 may represent devices of different manufacturers, different models of devices manufactured by the same manufacturer, or any type of device having different user interface elements.

  As shown in the system 100, a server computer 102 operated by a service provider or third party vendor is a content provider server computer, which includes content data, application programs, diagnostic tools, program components, Alternatively, any other content or executable object is provided to the mobile device 108. The content provider computer can be a World Wide Web (WWW) server, storing data in the form of web pages, and these pages as hypertext markup language (HTML) files, the Internet. 110 to mobile devices 108 and 109, or other client computers on the network. For example, server 102 may execute a web server process to serve web pages over network 110. In this embodiment, one or more mobile devices execute a web browser program that is served by a server computer 102 and any other available content provider or auxiliary server such as computer 106. To access.

  Any or all of the client computers in system 100 may be workstation computers, or they may be computers such as notebook computers, personal digital assistants, and the like. The client computer also has sufficient user input and processing capabilities to access the mobile communications device, game console, or Internet network 110 and execute or access application programs. If there is, it may be embedded in the same computer. Mobile devices 108 and 109 can be coupled to network 110 by wired connections, wireless connections, or any combination thereof.

  In a typical implementation, multiple mobile devices of various types and make can be interconnected through the network 110. Each mobile device can be characterized by a different user interface, since strict industry standards have not yet been written that specify a uniform user interface between different possible mobile devices. In general, each manufacturer of a mobile device can have some form of user interface, but even devices provided by the same manufacturer can feature very different user interfaces. . As users can customize their user interface, the user interface style variation will increase even further.

  In one embodiment, it is the content provider that operates the server computer 102 and provides a customized user interface for a number of different manufacturers and types of mobile devices, such as cell phones 108 and 109. Can be generated. For discussion purposes, the customized user interface is referred to as a “UI skin”. In general, UI skins modify the device's “look and feel,” such as background, title bar, buttons, alarm sounds, etc., by modifying the display and / or sound output aspects of the device. That is, it enables the user to customize the application program environment. Some programs make automatic skin changes for the user when the user starts the program or uses some part of the program. Alternatively, the UI skin can be downloaded by the user and installed on the mobile device to modify the default UI or to permanently change the device UI. UI skins can be developed by third party vendors, device manufacturers, application designers, and the like. In general, different classes of UI skins can be developed for different types of mobile devices and different make mobile devices.

  As shown in FIG. 1, it is the content provider that runs the server computer 102 and executes the user interface authoring tool 104 to provide content for each mobile device when requested by the user of the mobile device. Generate the package and download the user interface to the appropriate mobile device. A database or data store 120 coupled to the server computer 102 can store various resource profiles and resource files for different mobile devices. Alternatively, resource profiles and other associated data files can be stored in a remote data store, such as data store 112 maintained by workstation 106.

  In one embodiment, when the mobile devices 108 and 109 are handed to the user, a default user interface is associated with the particular screen configuration, size, color scheme, font, menu scheme, keypad button assignment, call Set UI skin consisting of sound selection. However, many different aspects of the mobile device can also be customized, such as menu formatting and display, commands, subwindows, etc. The content provider 102 can provide a customized UI, which allows the user to change certain aspects of the UI skin. A resource file that specifies parameters that can be changed is stored in the data store 120 or the data store 122.

  In system 100, user interface descriptor information with customizable UI elements is downloaded to a mobile device such as 108 or 109. In one embodiment, the UI descriptor information includes screen parameter definitions (eg, size, aspect ratio, icon definitions, etc.), images, video clips, music or other audio clips, ring tones, games, small applications (applets). , Utilities, diagnostic tools, or any other similar data or application, all referred to as “UI content objects”. UI content objects can be provided by a number of different content providers, such as content provider 102 or 106. Typically, customized UI content is downloaded on demand, such as when a user requests a UI upgrade or modification from a particular content provider. Alternatively, UI skin content can be pushed to users from content providers based on periodic subscription arrangements, trials, or similar mechanisms. In one embodiment, a UI content object is generated and made available for downloading through a user interface authoring tool 104 that is executed by the server computer 102. The user interface authoring tool 104 may be a program or a set of programs, or a hardware circuit, or any combination thereof that embodies instructions executed by one or more processing units in a server. Can be represented.

  FIG. 2 is a functional block diagram of a user interface authoring system, under an embodiment. The UI authoring system allows content providers to create content packages that embody UI skins for distribution and download to mobile devices over the network. The content package for each UI skin contains specific information in its device model, device manufacturer, operating system, application program, and other relevant information about the mobile device.

  The system shown in FIG. 2 uses resource profile information for each mobile device model when generating UI skin package data specified for each mobile device from common resource data. The device model generally refers to a device make (manufacturer) and a specific model, model, or version of the device specified by the manufacturer. Through the use of a UI authoring tool, the content creator creates a UI skin content package for each possible model for mobile devices used on the network without having to prepare a separate resource file for each model. be able to.

  User interface specifications for each mobile device are prepared by the device manufacturer and stored in the resource profile database 204. The user interface specification generally describes all relevant aspects of the UI element with respect to the device and any application program that can be specified on the device. A resource profile is associated with each model or model of mobile device. For this reason, as shown in FIG. 2, a certain resource profile is prepared for the device A, and a certain resource file is prepared for the device B. Referring to FIG. 1, these correspond to the resource profiles of mobile devices 108 and 109, respectively. The composition and format of the resource profile will be described in more detail below with reference to FIG.

  The common resource depot 202 contains resources as indicated by resource A, resource B, and resource C. Resources comprise data or program objects associated with files, links to files, and / or configurable aspects of the user interface for each mobile device. Thus, each resource in the resource depot 202 (also referred to as a “resource file”) is a file, location, directory, link, document, or configuration or customizable mobile device aspect information or Represents a similar object that contains or references a data element. All of the relevant information about the mobile device is stored in the resource file, and all the resource files for different possible mobile device models are stored in the common resource depot 202. The resource file can contain various types of data objects related to user interface elements of the mobile device, such as image files, sound files, screen layouts, icons, movies, and the like. The common resource depot 202 may be implemented as a database stored in a data store 120 maintained by the content provider 102 or a data store 112 maintained by a separate server 106.

  The profile selector 205 selects the resource profile 204 according to the device model selected by the content provider. The resource 202 corresponding to the model is then converted by the resource converter 206. The resource converter 206 performs various different types of conversion operations, such as file format conversion (eg, PGN to JPEG), color format change (eg, black and white to 8-bit color), etc. Can be configured. The resource converter 206 converts each resource into a format corresponding to the resource profile. The screen previewer component 208 provides a convenience function for trial display of the device user interface based on the resource file.

  The description editor component 210 creates a description file 212 based on the selected resource profile 204 and resource file 202. The description file 212 specifies resources and file types, and file path names. The conversion resource output from the description file 212 and the resource converter 206 is processed by the package generation component 214. The package generation unit 214 takes in resources and descriptions and creates a UI content package 216. The UI content package contains the UI skin of the target mobile device and further contains images or data of various UI elements, such as image files, movie files, and / or audio files. The UI content package includes appropriate conversion resources and description files.

  The package generator may produce UI content packages in a variety of different formats, such as archive files, encrypted files, or files containing auxiliary information as provided by auxiliary content providers. Can be configured. In one embodiment, the resource profile 204 is a file or data object provided by the device manufacturer for each mobile device.

  FIG. 3 is an example of a possible resource profile format for a mobile device, according to one embodiment. The resource profile specifies the format, format, size, placement, and various other parameters for each user interface element of the device. In the example shown in FIG. 3, the resource profile of device A includes a number of items, each of which is referenced by a unique item ID. That is, for example, item 1 is a flash file, which is displayed in a 240 × 240 pixel space at positions 0 and 10 on the screen 2 of the device. Similarly, item 2 is a 24 × 24 size PNG file displayed at position 5.0, and so on. Similarly, device B has a large number of UI elements specified by a large number of items as shown in the figure. FIG. 3 shows an example format for a device resource profile, and many other types of resource file formats are possible depending on the device model and manufacturer's specifications. The resource 202 is converted into a format corresponding to the appropriate resource profile 204. That is, if the resource is an image, it is converted into an appropriate size and file format according to the resource profile.

  FIG. 4 is a flowchart illustrating a method for generating and downloading a UI skin according to one embodiment. The method starts at step 401 where a resource profile suitable for the device is selected and retrieved from the resource profile 204. In step 402, the profile selector extracts customizable items in the UI element. Not all UI elements are customizable, and the process only deals with customizable UI elements. Next, in step 404, the description editor generates a description file. At this point, the resource converter, in step 406, converts the image size and resource file format according to the profile. Next, in step 408, the package generation unit creates a UI content package. Next, in step 408, the package generation unit creates a UI content package. Then, in step 410, the UI content package can be downloaded to the target mobile device.

  With the systems and methods shown in FIGS. 2-4, the UI authoring tool allows the content creator to create a UI for each possible mobile device model without requiring separate resource file preparation for each device. Allows you to create skin content packages. Through the use of predefined resource profiles and appropriate editing and conversion components, a common resource file database can be used to generate different UI content packages for each mobile device in the network.

  In one embodiment, the mobile device executes an application 122 that utilizes resources provided by the content provider. The application can be an object that is displayed on the screen of the mobile device, or an object that is played through the playback device (audio or video) of the mobile device, or an executable module (applet) that the mobile device executes. But you can. Resources comprising UI content packages that are downloaded to mobile devices for use by applications can be provided by an external content provider, as shown in FIG. Alternatively, the UI content package may be installed in advance on the mobile device itself.

In general, regardless of the origin of the UI content package, the resources referenced by the descriptor file and used by the application are in some way referenced by the application and then retrieved and converted to the appropriate format for use by the application. It must be. In one embodiment, the content server performs the necessary resource search and conversion operations and downloads the resources directly to the mobile device. In this embodiment, resource file 204 specifies the appropriate format required. In another embodiment, the mobile device handset itself incorporates components that facilitate the download and conversion of resource files or data objects from common UI package content for use in resident application programs. is doing.
In one embodiment based on a resource API, the mobile device in the network 100 is configured to convert the file format from the common UI package directly to the handset itself. As shown in FIG. 1, a mobile device (also referred to as a “handset”) runs one or more application programs 122 or software modules to execute or provide resources provided by a UI content package. Configured to access. The application can be any program that can reproduce or perceive images, videos, sound files, etc. of resources provided by the UI content package. The UI content package is UI content that can be authored or provided by the content server 102, or alternatively produced and provided, as illustrated and described with reference to FIGS. There may be.

  FIG. 5 is a block diagram of a mobile device that includes resources configured to download resources for a UI content package, under an embodiment. The mobile handset 502 executes an application program 506 that uses one or more resources for the UI content package. Mobile handset 502 also has a resource application program interface (API). The application 506 refers to the UI resource by the resource ID number, not by the direct file name or directory (storage location) path. The resource API thus provides a level of resource reference abstraction and increases the portability of resources in the system. Application 506 can be a software program or utility that modifies the appearance or functionality of the mobile device, or it can be a program that, when executed, provides a service or some other functionality to the user.

  Through the resource API functionality, the mobile device can change the UI skin of the application 506 with the UI content package. The UI content package is downloaded from the UI content server or pre-installed in the mobile handset and does not require modification of the application itself. Applications can also access resources of various file types without requiring modifications or implementation changes. The resource file can be located on the handset itself or on a server computer that is coupled to the mobile handset through a network. By converting the resource format through the resource API, different UI specifications can be accommodated for each device without requiring modification of the application or UI content package.

  As shown in FIG. 5, the resident application 506 is functionally coupled to a resource API 508 that includes a package selector 510, a description file parser 512, an engine selector 520, and a flash engine 514, PNG. It contains a number of functional components, such as one or more engines such as a (portable network graphics) engine 516, a joint photographic experts group (JPEG) engine 518, and any other similar engine. These engines process applicable resources using the appropriate playback format depending on the type of data or program elements in the resource. That is, for example, the resource is an applet, and the flash engine 514 is called. If the resource is a photograph, the JPEG engine is called.

  The actual UI content package to download is typically selected by the user of the mobile device. The setting application 504 sets UI content package data in the application program, and the user can change the UI content by changing the setting application 504. As shown in FIG. 5, the selection of the setting application 504 is input to the package selector module 510 in the resource API 502.

  Mobile handset 502 also includes a data storage component 522, which can be implemented as any type of fixed, removable, or on-board memory device. One or more user interface content packages 524 and 522 may be stored in this data storage. Each user interface content package contains a description file 526 and one or more resources 528 and 530. UI content packages stored on the mobile handset data storage 522 are typically pre-installed on the handset by the device manufacturer or a third party entity that provided configuration support. UI content packages can also be provided by external sources over network 538, such as from a UI content server, such as content server 540 that houses UI content package 542. Such a content server can correspond to either server 102 or server 106 of FIG. Each UI content package 542 provided by an external content provider server also contains a description file and one or more resources, the content of which is described in more detail below with reference to FIG.

  The description file parser 512 selects a description file suitable for the package selected by the package selector 506. In general, a description file describes information on a resource file contained in a UI content package. The description file contains references to one or more resources that are downloaded to the application 506. The description file 526 can also refer to resources contained in the same UI content package, or resources in other content packages that are pre-installed in the mobile handset or on an external server computer Can also be referred to. In the example shown in FIG. 5, the description file 526 includes a resource A 528 and a resource B 530 accommodated in a UI content package A 524 resident in the data storage 522 of the mobile device, and a resource C 536 provided by the UI resource server 534. refer. Resource server 534 represents a server computer or network resource that provides resources that are not packaged in a UI content package, such as UI content package 542. Such a resource server corresponds to either the server 102 or the server 106 of FIG.

  Resource API 508 retrieves each resource referenced by the description file selected for the UI content package selected by package selector 510 and description file parser 512. The resource API engine selector component 520 selects the appropriate engine and converts each resource file into a format or embodiment compatible with the application 506. The application dictates the format of the resource with respect to parameters such as image size, color, and position.

  6 is a more detailed view of user interface content packages and resource references for the mobile device of FIG. As shown in FIG. 6, the user interface content package A 524 contains a description file 526. The description file contains a number of item entries 601. Each item entry consists of certain items of information about individual resources, such as identifier (ID), path (location), and file type, among other parameters. That is, as shown in FIG. 6, three example entries are shown for resources A, B, and C. Resource A is a flash object, resource B is a PNG object, and resource C is a JPEG object.

  The path parameter specifies the location of the resource and can be implemented as a pointer or a link to a storage location. In general, the application 506 on the mobile device pulls resources by ID, not location. The description resource API accesses the appropriate description file that correlates the proper resource location to the resource ID for upload to the application. Thus, the resource API 508 represents an interface abstracted between the application and the actual resource. As illustrated graphically in FIG. 6, the path element of each item descriptor effectively points to the location of the corresponding resource. That is, as shown, link “resource A” points to resource A 528, link “resource B” points to resource B 530, and link “resource C” re-points resource A 536. The resources referenced by the description file can be contained in the same UI content package as the description file, as for resources A and B, or they can be stored in a separate UI as shown in FIG. It can be provided by a content package (either in the mobile handset or in an external UI content server 540) or by an external UI resource server 536. The selected resource is then input to the engine selector component 520 of the resource API 502 for processing by the appropriate engine.

  FIG. 7 is a flowchart illustrating a method for downloading resources to a mobile device through a resource API on the mobile device, according to one embodiment. In step 701, the setting application sets or changes the setting value of the UI package file path. In step 702, an application on the mobile device requests a resource by specifying a resource ID (eg, ID_1). Package selector 510 and description file parser 512 use the package file path and resource ID number to locate the appropriate UI content package that contains the referenced resource. As shown in block 704, the resource API selects and reads a description file for the selected UI content package. One or more resources may be contained within a single UI content package specified by the package selector, or contained within a different content package either inside or outside the mobile device. There may be. In step 706, the description file refers to the resource file indicated by the UI content package or resource server, or other external source. This reference step is functionally illustrated in FIG.

  After the selected resources are properly referenced and located, in step 708 they are retrieved by the resource API and input to the engine selector for processing by the appropriate engine. Other UI content packages, such as 542, can be specified by the package selector, as shown in block 710, in which case these resources are also searched. Then, in step 712, the resource API uploads all referenced resources to the application. As the process of FIG. 7 illustrates, an application can gain access to local or external resources by simply specifying the resource ID, not the location of the resource. In this way, resources can be changed by using different content packages or implementations in an updatable UI resource server without requiring any changes to the application program 506 itself. Further, the elements of the resource API 508 can be modified or updated without requiring changes to the application program. For example, different or new versions of the engine can be implemented in the resource API for different types of data objects or programs by adding or modifying engine components.

  Although the UI authoring system and mobile handset system embodiments described herein have been described with respect to a network of mobile communication devices such as cellular phones, alternative embodiments can be configured using UI skins or descriptor files. Note that any type of computing device with a user interface that can be modified can be targeted. Such devices can be wired or wireless computers, workstations, embedded processing devices, and the like. There is also an embodiment that can be realized in a user interface module provided in machinery such as a UI interface in a car, an airplane, a ship, or the like.

  FIG. 8 illustrates a communication network system 800 that implements one or more embodiments of a content distribution and billing system. In the system 800, a service provider server computer 802 provides network access to one or more mobile devices, such as a mobile telephone 808. In one embodiment, mobile device 808 is a cellular phone, and network 810 is a comprehensive telecommunications network that includes both a cellular phone network and the Internet. The network 810 may also include one or more wide area networks (WAN), local area networks (LAN), or any combination thereof. Server computer 802 may be a wireless service provider or an Internet service provider, or a combination of both. The mobile device 808 communicates with other mobile devices through the wireless portion of the network 810, such as other cellular telephones through the cellular network. The mobile device 808 may also be configured to communicate with one or more client and / or server computers that are directly or indirectly coupled to the network 810.

  In one embodiment, the computers 811, 814, and 818 are content provider servers that transfer content data, application programs, diagnostic tools, program components, or any other content or executable object. 808. One or more of the content provider's computers is a World Wide Web (WWW) server that stores data in the form of web pages, and these pages as hypertext markup language (HTML) files, Send to the mobile device 808 or other client computer on the network over the Internet 810. For example, the server 818 executes a web server process 816 to distribute web pages across the network 810. In this embodiment, mobile device 808 executes a web browser program and accesses web pages distributed by server computer 818 and any available content provider, or auxiliary servers 811 and 814.

  In a typical implementation, the mobile device user 808 pays the service provider 802 each time or monthly fee to use the network 808. This fee typically covers the associated usage fees for communication with other mobile device users and the use of required features associated with subscription plans such as messaging, diagnostics, tools, programs, and the like. In the embodiment shown in FIG. 8, content provider servers 811, 814, and 818 provide content to mobile device users 808 that are not included in the service provider plan. These servers are typically operated by third parties that provide supplemental content or programs to users who need some use of the network resources provided by service provider 802.

  In one embodiment, server 802 in network system 800 executes server-side content setting and charging system 804. A client version of this process can also be run on the mobile device 808. Server process 804 can represent one or more executable program modules and is stored in network server 803 and executes locally within the server. However, alternatively, it may be stored on a remote storage or processing device coupled to server 802 or network 810 and accessed and executed locally by server 802. In yet another alternative embodiment, the content configuration and billing server 804 can also be implemented in a plurality of different program modules, each of which can be two or more distributed coupled to the network 810, either separately or separately. It can also be executed by a server computer. The server computer 802 also maintains a billing database 806 that is accessed by the content setting and billing process 804.

  A user of mobile device 808 can download content objects from one or more content providers. The downloaded content uses resources provided by the service provider 802, but is not directly controlled by the service provider. Content setting and billing process 804 facilitates billing associated usage fees for use of downloaded content. The system usage fee is set by the wireless operator. If the user simply downloads the content object from the content provider, there is no usage fee. However, if the user executes, visually or otherwise accesses the content object on his or her mobile device, the usage fee is typically charged by the service provider to the content provider. In one embodiment, the content provider charges a content sponsor. The content sponsor provides advertisements or other auxiliary data related to the content provided by the content provider.

  Any or all of the client computers in system 800 may be workstation computers, or they may be computing devices such as notebook computers, personal digital assistants, and the like. The client computer is within a similar computing device that provides access to a mobile communication device, game console, or Internet network 810 and sufficient user input and processing power to execute or access application programs. It may be embodied in. Client computers 811, 814 and 818 may be coupled to network 810 through wired connections, wireless connections, or any combination thereof.

  FIG. 9 is a functional block diagram of a content distribution and billing system, under an embodiment. Download content to mobile device 920. In one embodiment, the content comprises images, video clips, music or other sound clips, ring tones, games, small applications (applets), utilities, diagnostic tools, or any other similar data or application All of them are called “content objects”. Content can be provided by a number of different content providers, such as content providers A and B in FIG. Typically, content is downloaded on demand, such as when a user requests content from a particular content provider. Alternatively, content providers can push to users based on periodic subscription arrangements, trials, or similar mechanisms. Generally, a user does not incur a usage fee simply by downloading content.

  In one embodiment, the content incorporates one or more advertising messages in a graphic image, streaming video, audio clip, text message or similar form or combination thereof. Advertising messages are typically provided free of charge and can be incorporated into content data or associated with content through a similar mechanism that links tags or advertising messages with individual content data objects. Advertising messages can be created by the same content provider as the associated content data, or can be provided by a separate content provider, such as a content sponsor or advertising server.

  Each content provider operates a content distribution server to package and send content objects to the mobile device 920. That is, as shown in system 900, content provider A 902 has a content distribution server 904 that downloads content data object 901 to mobile device 920, and content provider B 906 moves content data object 903. It has a content distribution server 908 for downloading to the device. The mobile device 920 includes a content downloader module 922 for receiving content data objects. Once the content has been received, depending on the file format of the content, for example, depending on the audio clip, video clip, ringing tone, applet, etc., the user will recognize it visually, listen, execute, or otherwise be able to. When the user uses, executes, or otherwise recognizes the downloaded content data, the associated advertisement message is also played or executed. In this way, the user will always see or listen to the advertisement when using the content. By viewing the advertisement, a usage fee is generated and charged by the wireless service provider 910.

  In one embodiment, wireless service provider 910 provides authoring tools to content providers 902 and 906. The authoring tool allows content providers to create content packages that embody content and advertising messages and download them to mobile devices. The content package includes information about the content provider, such as the provider identifier, location, security mechanism, etc. The content package also includes any information regarding content data provided by the content provider and any other relevant data such as auxiliary data or linked advertising messages. The content package can also include information regarding compatible target mobile devices, such as manufacturer, model, specification, operating parameters, and the like. The authoring tool allows the service provider 910 to direct or control the distribution of distributed content and to establish a trigger (such as watching an advertisement) that indicates when to collect usage fees. .

  The mobile device 920 includes a content setting module 924, and sets and cancels content data for the system software on the mobile device 920. In one embodiment, by downloading and using, the system software accesses or executes the content data object, thereby “setting” the content. The content setting module detects whether the content data is being used by determining whether the associated advertisement message is being reproduced. Then, it is assumed that the user has viewed the advertisement. If the content data has not been used or accessed yet and has just been downloaded, it is defined as “unset”. The content setting module 924 also defines content setting information and sends this information to the wireless service provider. Content settings information includes information about content data objects, content identifier, content type (eg, video, audio, text, etc.), file size, encryption or compression method, and other similar parameters. Such information can be included. The content setting information is typically stored in the form of a database or spreadsheet table in the mobile device's memory and can be accessed by the content setting module 924.

  FIG. 10 is an example of a content setting information table according to an embodiment. A column 1002 of the table 1000 includes a description of the content setting information item, and includes a content ID, a content provider ID, and the like. An example of values related to each item is illustrated in a column 1004 of the table 1000.

  As shown in FIG. 9, a wireless service provider 910 that supports a mobile device 920 maintains a computer system that includes a content configuration information collection server 912 and a billing database 914. The content setting information collection server 912 embodies a part of the content setting and charging process 904 shown in FIG. The content setting information is sent to the content setting information collection server 912 by the content setting module 924 on the mobile device 920. Next, this server registers content setting status information in the accounting database 914. Then, the charging database is used to collect the appropriate system usage fee for the content provider based on the charging information stored in the charging database. Typically, if the content setting status is “set” in the content data, the content provider that sent the content to the mobile device is charged.

  The usage fee associated with the use of content data provided by the content provider can be set to virtually any value that is determined by the wireless service provider. The usage fee can be based on various subject models, such as a standard fee for all downloads by the content provider, a fee per download, or any similar method. If a separate content sponsor or advertiser is the sponsor of the content, the content provider can communicate the usage fee or deduct some or all of the usage fee from the sponsor. Typically, content is provided free of charge to mobile device users, so the cost of use will be borne by the content provider and / or content sponsor. However, in some cases, usage fees may be distributed with mobile device users in whole or in part depending on subscriptions or fee arrangements between content providers, wireless service providers, and users.

  FIG. 11 is a flowchart illustrating a usage fee billing method in a content setting and distribution system according to an embodiment. The method begins at step 1101 where a content provider packages content to be downloaded using an authoring tool provided by a wireless service provider. In step 1102, the user downloads content data from the wireless service provider to his or her mobile device. A content downloader on the mobile device controls the download of the content. If the user simply downloads the content, there is no usage fee. When the downloaded content is used, in step 1104, the content setting module on the mobile device sets the downloaded content data and defines the content setting status information. In step 1106, the content setting module on the mobile handset sends content setting status information to the content setting information collection server of the wireless service provider. In step 1108, the content setting information collection server registers the content setting status information in the accounting database. At a predetermined time, the wireless service provider charges the appropriate content provider in step 1110 based on the settlement information in the charging database.

  The aspects of the UI authoring and mobile handset system described herein can be implemented as functionality that is programmed into any of a variety of circuits that include a field programmable gate array (FPGA), Includes programmable array logic (PAL) devices, programmable logic devices (PLD) such as electrically programmable logic and memory devices, standard cell based devices, and application specific integrated circuits (ASICs). In addition, other possibilities for implementing aspects of the method include a microcontroller having a memory (such as an EEPROM), an embedded microprocessor, firmware, software, and the like. Further, the foregoing method aspects include software-based circuit emulation, discrete logic (continuous and combined), custom devices, fuzzy (neural) devices, quantum devices, and micros having any hybrid of the above device types. It can also be embodied in a processor. The underlying device technology includes various component types such as metal oxide semiconductor field effect transistor (MOSFET) technology such as complementary metal oxide semiconductor (CMOS), bipolar technology such as emitter coupled logic (ECL), It can be provided in polymer technology (eg, silicon conjugated polymers and metal conjugated polymer-metal structures), mixed analog and digital, and the like.

  It should be noted that the various functions disclosed herein may relate to their behavior, register transfer, logical components, and / or other characteristics, as hardware, firmware, and / or data, and / or various machine readable or computer readable. Note that the description can be made using any number of combinations of instructions embodied in the possible medium. Computer readable media that can embody such formatted data and / or instructions are not limited to various forms of non-volatile storage media (eg, optical, magnetic, or semiconductor storage media), and It includes a carrier wave that can be used to transfer such formatted data and / or instructions over a wireless, optical, or wired signaling medium or any combination thereof. Examples of the transfer of such formatted data and / or instructions over a carrier wave include, but are not limited to, the Internet and / or other computer networks over one or more data transfer protocols (eg, HTTP, FTP, SMTP, etc.). Including forwarding (upload, download, email, etc.).

  Unless the context clearly indicates otherwise, the words “comprising”, “comprising” and the like are to be interpreted in an inclusive rather than an exclusive or exhaustive sense throughout the specification and claims. Shall. In other words, it means “including but not limited to”. Words using the singular or plural also include plural and singular, respectively. In addition, the words “here”, “below”, “first”, “after”, and words of similar significance refer to the entire application, not to any particular part of the application. I will do it. Where the term “or” is used in reference to a list of two or more items, this term shall apply to all of the following interpretations of that term. Any of the items in the list, all of the items in the list, and any combination of items in the list.

  The above description of exemplary embodiments for UI authoring and mobile handset systems is not intended to be exhaustive or to limit the embodiments to the disclosed forms or instructions themselves. Although specific embodiments and examples of UI authoring systems have been described herein for purposes of illustration, it will be appreciated by those skilled in the art that various equivalent modifications may be made within the scope of the described embodiments. Is possible.

  The elements and actions of the various embodiments described above can be combined to provide further embodiments. In light of the above detailed description, these and other changes can be made to the disclosed system.

  In general, in the following claims, the terminology used should not be construed as limiting the described system to the specific embodiments disclosed in the specification and the claims. Should be construed to include all operations and processes operating under. Accordingly, the described system is not limited to the disclosure, but rather the scope of the method specified is to be determined entirely by the claims.

  While certain aspects of the UI authoring and mobile handset system may be presented in the form of certain claims, the inventor contemplates aspects of the present methodology in any number of claim forms. . For example, although only one aspect of the system is specified as embodied in a machine-readable medium, other aspects can be embodied in a machine-readable medium as well. Accordingly, the inventor retains the right to pursue additional such claims for additional aspects of the described system and method even after filing this application. And

FIG. 1 is a block diagram of a communication network system that implements an embodiment of a user interface authoring tool, under an embodiment. FIG. 2 is a functional diagram of a user interface authoring tool, under an embodiment. FIG. 3 is an example of a resource profile for a mobile device according to one embodiment. FIG. 4 is a flowchart illustrating a method for providing a user interface authoring tool according to one embodiment. FIG. 5 is a block diagram of a mobile device that includes a resource application program interface for downloading resources to a UI content package, under an embodiment. FIG. 6 is a more detailed view of the resource criteria for the mobile device of FIG. FIG. 7 is a flowchart illustrating a method for downloading resources to a mobile device through a resource application program interface on the mobile device according to one embodiment. FIG. 8 is a block diagram of a communication network system that implements an embodiment of a content distribution and billing system, under an embodiment. FIG. 9 is a functional diagram of a content distribution and billing system, under an embodiment. FIG. 10 is an example of a content setting information table according to an embodiment. FIG. 11 is a flowchart illustrating a method for charging a usage fee in a content setting and distribution system, according to one embodiment.

Explanation of symbols

110 Network 104 User Interface Authoring Tool 122 Application 202 Common Resource Depot 204 Resource Profile 205 Profile Selector 206 Resource Converter 208 Screen Previewer 210 Description Editor 212 Description File 214 Package Generation Unit 216 User Interface Content Package 302 Resource Profile Device A
304 Resource profile device B
502 Mobile handset 504 Setting application 506 Application 508 Resource API
510 Package Selector 512 Description File Parser 514 Flash Engine 516 PNG Engine 518 JPEG Engine 520 Engine Selector 522 Data Storage 524 User Interface Content Package A
526 DESC File 528 Resource A
530 Resource B
532 User Interface Content Package B
534 UI resource server 536 Resource C
538 Network 540 UI content server 542 UI content package 524 User interface content package A
526 Description file 528 Resource A
530 Resource B
520 Engine selector 534 UI resource server 536 Resource C
804 Content setting billing system 810 Network 816 Web server 902 Content provider A
904 Content distribution server 906 Content provider B
908 Content distribution server 912 Content setting information collection server 914 Billing DB
910 Wireless service provider 920 Mobile device 922 Content downloader 924 Content setting 1002 Description 1004 Setting

Claims (56)

A method for providing a customized user interface package to mobile devices over a network, comprising:
Storing a plurality of resource files in a common data store, each resource file comprising a data object representing an aspect of the mobile device user interface;
Selecting a resource profile from a plurality of resource files, wherein the resource profile specifies parameters related to a user interface aspect corresponding to at least one of the plurality of resource files;
Generating a description file describing the location of the resource and data objects related to the resource;
Converting the resource into a format corresponding to the resource profile;
Generating a user interface content package for download to the mobile device, the user interface content package including the description file and the converted resource;
With a method.   The method of claim 1, wherein the resource comprises one of an image, a video clip, and a sound clip.   3. The method of claim 2, wherein the resource profile comprises a plurality of user interface item specifications, wherein at least one of item location, item size, item file type, and item identifier. How to specify.   4. The method of claim 3, wherein the plurality of resource files are arranged in one or more databases, and the common data store is a persistent memory store of a server computer coupled to the network. There is a way.   5. The method of claim 4, wherein the resource comprises a link to a location that houses one user interface item of the plurality of user interface items.   The method of claim 1, wherein the mobile device comprises at least one of a cellular phone, a personal digital assistant device, a notebook computer, and a game console.   The method of claim 6, wherein the user profile information is provided by a manufacturer of the mobile device, and the user profile information relates to a specific model of the mobile device. A system that provides a customized user interface package to mobile devices over a network,
Storage means for storing a plurality of resource files in a common data store, each resource file comprising a data object representing an aspect of the mobile device user interface;
Means for selecting a resource profile from a plurality of resource files, wherein the resource profile specifies parameters related to a user interface aspect corresponding to at least one of the plurality of resource files; A selection means;
Means for generating a description file describing the location of the resource and data objects related to the resource;
Means for converting the resource into a format corresponding to the resource profile;
Means for generating a user interface content package for download to the mobile device, the user interface content package including the description file and the converted resource;
With a system.   9. The system of claim 8, wherein the resource comprises one of an image, a video clip, and a sound clip.   10. The system of claim 9, wherein the resource profile comprises a plurality of user interface item specifications, wherein at least one of item location, item size, item file type, and item identifier. Specify the system.   11. The system of claim 10, wherein the plurality of resource files are arranged in one or more databases, and the common data store is a persistent memory store of a server computer coupled to the network. There is a system.   12. The system of claim 11, wherein the resource comprises a link to a location that houses one user interface item of the plurality of user interface items.   9. The system of claim 8, wherein the mobile device comprises at least one of a cellular phone, a personal digital assistant device, a notebook computer, and a game console.   The system of claim 13, wherein the user profile information is provided by a manufacturer of the mobile device, and the user profile information relates to a specific model of the mobile device. When executed in the processing system,
Storing a plurality of resource files in a common data store, each resource file comprising a data object representing an aspect of the mobile device user interface;
Selecting a resource profile from a plurality of resource files, wherein the resource profile specifies parameters related to a user interface aspect corresponding to at least one of the plurality of resource files;
Generating a description file describing the location of the resource and data objects related to the resource;
Converting the resource into a format corresponding to the resource profile;
Generating a user interface content package for download to the mobile device, the user interface content package comprising the description file and the converted resource;
A computer readable medium comprising executable instructions for providing a customized user interface package to a mobile device over a network.   16. The medium of claim 15, wherein the resource comprises one of an image, a video clip, and a sound clip.   17. The medium of claim 16, wherein the resource profile comprises a plurality of user interface item specifications, wherein at least one of item location, item size, item file type, and item identifier. Specifies the medium.   18. The medium of claim 17, wherein the plurality of resource files are arranged in one or more databases, and the common data store is a persistent memory store of a server computer coupled to the network. There is a medium.   19. The medium of claim 18, wherein the resource comprises a link to a location that houses one user interface item of the plurality of user interface items.   The medium of claim 19, wherein the user profile information is provided by a manufacturer of the mobile device, and the user profile information relates to a specific model of the mobile device. A method for obtaining resources for use by an application on a mobile device,
Refers to a resource through the application by a resource identifier,
In the user interface content package, the location of the referenced resource is located, and the user interface content package comprises a description file containing a path specifying the location of the referenced resource;
Inputting the referenced resource into a processing engine to convert one or more resource data objects into a format compatible with the application;
With a method.   24. The method of claim 21, wherein the resource comprises one or more data objects including user interface elements of the mobile device.   24. The method of claim 21, wherein the resource comprises one of an image, a video clip, and a sound clip.   24. The method of claim 23, wherein the processing engine comprises at least one of a flash engine, a PNG engine, and a JPEG engine.   23. The method of claim 22, wherein the resource identifier is an alphanumeric reference code that does not directly indicate the location of the resource.   24. The method of claim 23, wherein the resource is contained within the user interface content package containing the description file.   24. The method of claim 23, wherein the resource is contained in a user interface content package residing on a server computer that is coupled to the mobile device over a network.   24. The method of claim 23, wherein the description file contains a descriptor that contains the resource identifier, a location of the resource specified by the resource identifier, and a file type of the resource specified by the resource identifier. Method.   24. The method of claim 21, wherein the mobile device comprises at least one of a cellular phone, a personal digital assistant device, a notebook computer, and a game console. An apparatus for acquiring resources for use by an application on a mobile device,
A data store for storing one or more user interface content packages, each user interface content package containing a description file and one or more resources;
A resource application programming interface,
Locating a resource specified by the application, the resource containing one or more data objects;
Converting the resource data object into a format compatible with the application;
Upload the resource to an application on the mobile device;
A resource application programming interface configured to:
Equipped with the device.   32. The apparatus of claim 30, wherein the resource comprises one or more data objects that include user interface elements of the mobile device.   32. The apparatus of claim 31, wherein the resource comprises one of an image, a video clip, and a sound clip.   35. The apparatus of claim 32, wherein the resource application programming interface includes a processing engine component comprising at least one of a flash engine, a PNG engine, and a JPEG engine.   32. The apparatus of claim 30, wherein an application specifies the resource through an alphanumeric reference that does not directly indicate the location of the resource.   35. The apparatus of claim 34, wherein the referenced resource is the user interface content package containing the description file and user interface content residing on a server computer coupled to the mobile device over a network. A device housed in one of the packages.   36. The apparatus of claim 35, wherein the description file contains a descriptor containing the resource identifier, the location of the resource specified by the resource identifier, and the file type of the resource specified by the resource identifier. apparatus.   38. The apparatus of claim 36, wherein the mobile device comprises at least one of a cellular phone, a personal digital assistant device, a notebook computer, and a game console. When executed in the processing system,
Refers to a resource through the application by a resource identifier,
In the user interface content package, the location of the referenced resource is located, and the user interface content package comprises a description file containing a path specifying the location of the referenced resource;
Inputting the referenced resource into a processing engine to convert one or more resource data objects into a format compatible with the application;
A computer readable medium comprising executable instructions for obtaining resources for use by an application on a mobile device.   40. The medium of claim 38, wherein the resource comprises one of an image, a video clip, and a sound clip.   40. The medium of claim 39, wherein the referenced resource is the user interface content package containing the description file and user interface content residing on a server computer coupled to the mobile device over a network. -Medium contained in one of the packages. A method of charging for use of a network supported by a service provider, comprising:
Providing an authoring tool to the content provider to define content data to be transmitted by a content provider to a user of a mobile device on the network, the content data comprising one or more associated advertisements Including messages,
Receiving content status information from the mobile device, wherein the content status information includes an indication of playing the one or more associated advertising messages on the mobile device;
Registering the content status information in the accounting database;
Charging the content provider for content indicating that the one or more associated advertising messages have been played;
With a method.   42. The method of claim 41, wherein the network is a cellular telephone network, the mobile device is a cellular phone, and the service provider is a cellular service provider.   42. The method of claim 41, wherein the content data comprises at least one of an audio clip, a video clip, a program, a text message, and a program executable on the mobile device.   42. The method of claim 41, wherein the one or more associated advertising messages are provided by an advertising sponsor.   45. The method of claim 44, wherein the advertising sponsor bears a portion of the usage fee on behalf of the content provider.   42. The method of claim 41, wherein the content status information includes at least one of a content identifier, a content provider identifier, a content type, and a viewing state of an associated advertisement. A server computer for charging a usage fee associated with the use of content data downloaded from a third-party content provider to a mobile communication device;
A content setting billing system configured to receive content setting status information from the mobile communication device, wherein the status information is set to one of setting or unsetting, and the setting is determined according to a trigger condition. A content configuration billing system representing content data used by the mobile communication device as shown;
A billing database configured to store the content setting status information and information related to the content provider;
Server computer with   48. The system of claim 47, wherein the trigger condition is transmission of an advertising message associated with the content data.   49. The system of claim 48, wherein the network is a cellular telephone network, the mobile device is a cellular phone, and the service provider is a cellular service provider.   50. The system of claim 49, wherein the content data comprises at least one of an audio clip, a video clip, a program, a text message, and a program executable on the mobile device.   50. The system of claim 49, wherein the one or more associated advertising messages are provided by an advertising sponsor.   52. The system of claim 51, wherein the advertising sponsor bears a portion of the usage fee on behalf of the content provider.   53. The system of claim 52, wherein the content status information includes at least one of a content identifier, a content provider identifier, a content type, and an associated advertisement viewing status. When executed in the processing system,
Providing an authoring tool to the content provider to define content data to be transmitted by a content provider to a user of a mobile device on the network, the content data comprising one or more associated advertisements Including messages,
Receiving content status information from the mobile device, wherein the content status information includes an indication of playing the one or more associated advertising messages on the mobile device;
Registering the content status information in the accounting database;
Billing the content provider for content indicating that the one or more associated advertising messages have been played;
A computer readable medium comprising executable instructions for charging for use of a network supported by a service provider.   55. The computer readable medium of claim 54, wherein the content data comprises at least one of an audio clip, a video clip, a program, a text message, and a program executable on the mobile device. Computer readable medium.   56. The computer readable medium of claim 55, wherein the content status information includes at least one of a content identifier, a content provider identifier, a content type, and a viewing status of an associated advertisement.

Images