WO2005048077A2 - Navigation pattern on a directory tree - Google Patents

Navigation pattern on a directory tree Download PDF

Info

Publication number
WO2005048077A2
WO2005048077A2 PCT/US2004/037718 US2004037718W WO2005048077A2 WO 2005048077 A2 WO2005048077 A2 WO 2005048077A2 US 2004037718 W US2004037718 W US 2004037718W WO 2005048077 A2 WO2005048077 A2 WO 2005048077A2
Authority
WO
WIPO (PCT)
Prior art keywords
node
user
nodes
directory
mobile
Prior art date
Application number
PCT/US2004/037718
Other languages
French (fr)
Other versions
WO2005048077A3 (en
Inventor
Zhaowei Charlie Jiang
Yingquing Lawrence Cui
Original Assignee
Yahoo! Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Yahoo! Inc. filed Critical Yahoo! Inc.
Publication of WO2005048077A2 publication Critical patent/WO2005048077A2/en
Publication of WO2005048077A3 publication Critical patent/WO2005048077A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/01Input arrangements or combined input and output arrangements for interaction between user and computer
    • G06F3/048Interaction techniques based on graphical user interfaces [GUI]
    • G06F3/0481Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
    • G06F3/0482Interaction with lists of selectable items, e.g. menus
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/954Navigation, e.g. using categorised browsing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/95Retrieval from the web
    • G06F16/958Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/7243User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages
    • H04M1/72439User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality with interactive means for internal management of messages for image or video messaging
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72406User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72427User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality for supporting games or graphical animations
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72445User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality for supporting Internet browser applications
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99944Object-oriented database structure
    • Y10S707/99945Object-oriented database structure processing
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99948Application of database or data structure, e.g. distributed, multimedia, or image

Definitions

  • the present invention relates generally to wireless mobile devices and more particularly to applications that offer navigation in a directory tree.
  • applications one type is a mobile photos application.
  • BACKGROUND Mobile-friendly technologies are advanced to provide a rich multimedia environment and enhance the wireless device users' experience.
  • An outcome of this evolution is the manifest closeness between the wireless universe and the internet domain, as well as the advent of wireless devices with multimedia capabilities.
  • the newest versions of mobile wireless devices such as digital mobile phones, pagers, personal digital assistants (PDAs), handsets, and any other wireless terminals, have multimedia capabilities including the ability to retrieve e-mail, and push and pull information via the Internet.
  • the present invention is based, in part, on the observation that a need exists for effective management of navigation in mobile devices, and that navigation patterns can be improved as described below. Accordingly, the navigation management concept is implemented providing a navigation pattern in a directory tree along with one or more context-specific action choices (menu or icons). For each selected item in the directory, the action choices can be different and tailored to that item.
  • context-specific action choices menu or icons
  • a method, a computer readable medium and a system are proposed as possible implementations of the navigation management concept. These implementations involve a mobile device that is typically capable of communicating with a server and other mobile devices.
  • the mobile devices are often wireless devices such as wireless camera phones and the content is photograph data (or simply one or more photos).
  • a method for managing navigation in mobile devices involves providing user interface in a mobile device, constructing a directory as a tree-shaped hierarchy of nodes, and providing the directory such that any node on the directory is selectable by a user via the user interface. This way, the navigation can flow up-down through the directory tree.
  • This method involves also associating a state and one or more action items with each node and saving the state of each node.
  • the state is an expanded or collapsed condition of the node, wherein if the state of a particular node is expanded additional nodes at a lower level of the hierarchy are presented to the user, otherwise if the state is collapsed only that particular node is presented and the other nodes are hidden.
  • this method there is the further step of providing in the user interface for any node selected by the user its associated one or more action items.
  • the one or more action items associated with that - node are action choices provided in the user interface either as icons or as menu items.
  • the number of action items associated with such node is determined by its nature, there being provided only action items that apply to such node. Then, overflow indicators are provided when the number of these action items exceeds a maximum number of action items that fit in the user interface, wherein the overflow indicators enable the user to scroll back a forth through all these action items.
  • a visible part of the directory provided to the user includes a top level of the tree-shaped hierarchy of nodes in a collapsed state. But as selected ones of these nodes are toggled they are expanded and more nodes, at a lower level of the hierarchy, are made visible and when toggled again these higher-level nodes are again collapsed.
  • the mobile devices are a wireless devices such as a wireless camera phones that download and run the Yahoo IPhotos program.
  • the directory is a mobile album.
  • the nodes in the tree-shaped hierarchy include a root node and any number of child nodes, such that any node that is childless is a leaf node which in the mobile album is a photo.
  • the approach described above can be implemented in a computer readable medium embodying a computer program with program code for providing the navigation.
  • the computer program is the client side of the mobile application program.
  • Other parts of a typical mobile application are the server side and networking service programs.
  • a system for providing the navigation management in a mobile device includes a processor, a screen for user interface, and a memory.
  • the memory embodies a client-side program with program code for causing the processor to perform the method steps as described above.
  • Figure 1 shows a wireless interconnection model using one of the many types of available bearer networks.
  • Figure 1 A shows another model of interaction, via bearer networks, between 3 rd -generation (3G)-enabled mobile devices and servers as well as other devices.
  • 3G 3 rd -generation
  • Figure 2 shows a mobile phone with features associated with the present invention.
  • Figure 3 illustrates the flow once users reach the Yahoo! Photos landing page.
  • Figures 4A-4D show the respective PC-based and mobile device-based registration and application buy flow diagrams.
  • Figures 5A and 5B show the screen flows for online albums and mobile albums, respectively.
  • Figure 5C parts (i) and (ii), describes setting up favorites for the mobile album slideshow.
  • Figure 5D shows flow diagrams for photos view, share and save.
  • Figure 5E illustrates the flow of restoring the mobile album from the server backup.
  • Figure 6 provides a simplified diagram to illustrate the back button feature.
  • Figure 7 is a screen shot of a mobile album showing a list of photos and action icons at the bottom of the screen.
  • the present invention contemplates a navigation pattern in a directory tree and implementation of this concept in mobile applications.
  • One such application is mobile photos, an example of which is referred to as the Yahoo! PhotosTM application.
  • Yahoo! and Yahoo! Photos are trademarks of Yahoo! Inc., Sunnyvale, CA. Any other trademarks are the property of their respective holders.
  • a client application is generally considered to be a downloadable application; namely, J2METM (JavaTM 2 platform, Micro Edition, by Sun Microsystems, Inc.), Yahoo! PhotosTM, or any other application that is downloadable to the mobile device.
  • the client Yahoo! Photos runs on a mobile phone, and more specifically, a mobile camera phone.
  • Wireless protocols the standards which govern communications of data between wireless devices and the Internet, utilize and support the enhanced capabilities of modem mobile ⁇ wireless devices and Internet content technologies.
  • Hypertext transfer protocol HTTP
  • WAP Wireless Application Protocol
  • M-services M-services
  • i-Mode i-Mode
  • Web clipping i-Mode
  • WAP appears to provide a proper framework for the content sharing. Therefore, adoption of standards such as WAP is suitable for the purpose of the present invention, and it is discussed in some detail below.
  • WAP is a specification suite defining a set of protocols for presentation and delivery of wireless information and telephony services on mobile wireless devices.
  • WAP services provide information access and delivery to WAP-enabled devices.
  • WAP was designed to empower users with easy and instant access to information and interactive services.
  • interoperability between WAP-enabled device is possible through any WAP-compliant infrastructure to deliver timely information and accept transaction and queries.
  • WAP can be built on any operating system, including PalmOS, EPOC, Windows CE, FLEXOS, OS/9, JAVA OS etc. Being air interface independent, WAP is designed to be scalable to new networks as they develop, allowing bearer independence and development of common solutions across disparate networks.
  • the term "WAP" is commonly used to refer to the wireless application environment (WAE) although it is WAE that includes the WAP suit of protocols and technologies. WAE provides the rich application environment which enables delivery of information and interactive services to mobile wireless devices.
  • WAE wireless application environment
  • An important aspect of the WAE is the WAP stack, namely the wireless protocol layers, as shown for example in Figure 1. At the bottom of the WAP stack 11 is a network layer, topped by the transport layer, the security layer, the transaction layer, and the session layer.
  • the network protocol layer supports network interface definitions, governing interface with the networks of wireless service providers (wireless bearers) such as short message service (SMS), code division multiple access (CDMA), cellular digital packet data (CDPD), general packet radio service (GPRS), high speed circuit-switched data (HSCSD), third generation (3G), GSM (global system for mobile communications), and unstructured supplementary service data (USSD) channel.
  • wireless service providers wireless bearers
  • SMS short message service
  • CDMA code division multiple access
  • CDPD cellular digital packet data
  • GPRS general packet radio service
  • HCSD high speed circuit-switched data
  • 3G third generation
  • GSM global system for mobile communications
  • USB unstructured supplementary service data
  • the wireless transport layer supports the wireless datagram protocol (WDP), and when operating over an IP (Internet protocol) network layer WDP is replaced with user datagram protocol/IP (UDP/IP).
  • WDP offers to the upper protocol layers a datagram service and transparent communication over the underlying bearer seivices.
  • WDP offers to the upper protocol layers a common interface to and ability to function independent of the type of bearer wireless network.
  • the wireless transport layer security provides a secure transport service to preserve the privacy, authentication and data integrity of the transport service at the layer below, as well as the ability to create and terminate secure connections between communicating applications.
  • the transaction protocol (WTP) layer provides transaction oriented protocol for the WAP datagram service, including, for example, request-response transactions.
  • the wireless session protocol (WSP) layer provides HTTP/1.1 functionality and features such as session suspend/resume.
  • the WSP provides the upper-level application lever of the WAE with an interface to connection and connectionless services operating above the transaction protocol and the datagram transport layers, respectively.
  • the WAE i.e., the wireless application environment
  • WML wireless markup language
  • WML script virtual machine a WML script virtual machine
  • WML script standard library a WML script standard library
  • TAT wireless telephony application interface
  • WAP content types WAP content types.
  • WAP micrc ⁇ browser also referred to as the "WAP browser”
  • WAP browser facilitates interaction between WAP/Web applications and WAP-enabled devices.
  • the micro-browser is a tag- based wireless browser application supporting wireless markup language (WML), and extensible transport hyperlink markup language (XTHML).
  • WML wireless markup language
  • XTHML extensible transport hyperlink markup language
  • the micro-browser uses the "card” metaphor for user interface, where user interactions are split into cards.
  • the WAP card metaphor provides a common interface to which all applications can conform, much like the desktop metaphor in PCs.
  • the micro-browser supports user actions, defined at tree levels (deck, card, and select & link options, i.e., ACCEPT, PREV, etc.) and default tasks (PREV, NOOP, etc.).
  • a deck of cards is split into a navigation card, variables card, and input elements card.
  • a navigation card is formed as a script encapsulated with the 'card' tags.
  • Figure 1 shows a wireless interconnection model 10 using one of the many types of available bearer networks 12.
  • the illustrated wireless mobile devices 100 are presumed to have sufficient local memory and Internet access capability to allow a user to download programs from servers 18 through the Internet 16 (and any other network such as LAN, WAN or
  • the illustrated server 18 can be the origin of downloadable programs as well as the origin, or destination, of content; although programs and content can originate at or be destined for different servers.
  • the web server 18 is the source of the Yahoo! Photos client side application as well as the source, and destination, of content, particularly photos (image data).
  • the downloaded program such as Yahoo! Photos, and with multimedia capabilities, including the ability to retrieve e-mail, and push and pull information via the Internet, network operators (or, more generally, service providers) add value propositions beyond voice or text offerings.
  • a server e.g., server 18
  • the server 18 operates as a repository for the data of photo images, and users can download from the server to their mobile devices data of previously captured photo images, as well as store and manipulate such images. Photos resident on one mobile device can be shared with another via the server 18 and the communication network(s) 12 and 16.
  • the mobile phones used to download the Yahoo! Photos client side program are WAP-enabled.
  • the WAP-enabled devices 100 support the WAP protocol and the server 18 typically supports the WWW (world-wide web) protocol.
  • the wireless application environment at the mobile device side 11 includes the micro-browser, a suite of WAP protocols at the network through session layers,
  • the micro-browser defines how WML documents and WML script applets should be interpreted and presented to the mobile device user.
  • the Micro-browser's WTA (wireless telephone application) functionality provides call control, phone book access and messaging within WML script applets to allow selective call forwarding or other secure telephony.
  • the wireless application
  • server-side Yahoo! Photos in addition to a standard web browser and WWW protocol stack (HTTP and TCP/IP).
  • gateway 14 is tasked with tracking subscriber 20 activities, controlling access and, in addition, functioning as the proxy for the mobile device 100, on the one hand, and for the server 18, on the other hand.
  • the gateway 14 is implemented, building on standard web proxy technology, to interconnect the services offered by the wireless service providers to the HTTP protocol so as to permit access to content on the wired Internet.
  • HTTP Hypertext Transfer Protocol
  • the gateway (13 & 14) translates requests from the WAP protocol to the WWW protocol, and vice versa; translating WML(/HTML) documents to HTML(/WML), resolving domain names in URLs and
  • WML documents are divided into a set of user interaction units, namely a deck of cards. Each user interaction unit is a card (or page), and the user can navigate between cards in one or more WML documents.
  • WAP-enabled proxy/gateway Another model of interaction between a WAP-enabled device, the WAP-enabled proxy/gateway, and the server, is the HTTP response/request transaction (protocol running on top of the Internet's TCP/IP suite of protocols).
  • This model is appropriate for the newer WAP 2.0 (with protocol stack not shown in Figure 1).
  • WAP 2.0 stack includes the IP, TCP (transmission control protocol), TLS, HTTP and WAE layers atop the network layer (all of which are profiled for wireless environment).
  • the wireless profile for the TLS protocol will permit interoperability for secure transactions.
  • FIG. 1 A Yet another model of interaction via bearer networks, between 3 rd -generation (3G)-enabled mobile devices and servers or other devices, is shown in Figure 1 A.
  • a 3G terminal supports higher-speed, wider-band wireless cellular service communications based on various technologies, including wide code division multiple access (W-CDMA), general packet radio service (GPRS), global system for mobile communications (GSM), enhanced data rates for global evolution (EDGE), unified threat management system (UMTS), and high speed circuit switched data (HSCSD).
  • W-CDMA wide code division multiple access
  • GPRS general packet radio service
  • GSM global system for mobile communications
  • EDGE enhanced data rates for global evolution
  • UMTS unified threat management system
  • HCSD high speed circuit switched data
  • a 3G terminal is equipped with cordless connections for local, short distance communications.
  • the communication protocols in the 3G terminal are comparable to the open system interconnection (OSI) protocols, layered in the OSI stack.
  • OSI open system interconnection
  • MMS multimedia messaging service
  • e-mail M-commerce
  • real-time video M-paid
  • MMS a store and forward messaging service capable of adding multimedia elements to SMS, including images, text, audio clips, and video clips.
  • MMS is synchronized across a common timeline, rather than being discrete like e-mail and SMS; it is akin to a presentation layer over e-mail and looking like a slide show with images.
  • the MMS message will appear with a new message alert. The picture message will open on the screen, the text will appear below the image and the sound will begin to play automatically.
  • Downloadable applications such as Yahoo! Photos and network games are likewise supported in the 3G terminal and interact with services such as MMS.
  • the originator can easily create a multimedia message, either using a built-in or accessory camera, or can use images and sounds stored previously in the phone (and possibly downloaded from a web site).
  • the mobile device is a WAP-enabled camera phone used for downloading photo applications such as the Yahoo! Photos.
  • FIG. 2 shows a mobile phone 100, not necessarily associated with any particular manufacturer, but with features suitable for the purpose of the present invention.
  • the mobile phone 100 has a camera feature with the camera lens 112 exposed for capturing images.
  • the mobile phone 100 also has a 5-point navigation key (also called game key) 114, and it features left, right, up, down and selection, or 'OK,' functions, substantially mimicking the operations of a mouse.
  • the main menu button 116 activates the menu display on the screen, and the main OK button 118 activates a menu selection.
  • the 'back' button 110 is shown as a hardware key whose position here is merely exemplary.
  • buttons on different devices may be arranged differently.
  • a 'back' soft-key is possible to implement a 'back' function of the WAP browser, which means that it would show up as an icon or menu item on the screen of the mobile phone.
  • the Yahoo! -enabled phone 100 supports wireless cellular service communications based on various technologies such as the GPRS and GSM.
  • This device is configured for supporting WAP communication protocols (at all layers of the WAP stack).
  • WAP communication protocols at all layers of the WAP stack.
  • Various services shown as being supported by these protocols include web browsing, SMS, MMS, e-mail, M-commerce, real-time video, and pre-paid.
  • the downloadable programs shown to interact with such services include the network games and Yahoo! Photos.
  • the mobile device functionality is preferably implemented using a platform, such as the
  • the J2METM platform which is tailored for a broad range of embedded devices including mobile phones.
  • the J2METM platform includes a set of standard Java APIs (application programming Interface), and provides a user interface, a security model, built-in network protocols (e.g., WAP, as shown in Figure 1), and support for networked and disconnected applications (Yahoo! Photos is a networked application).
  • WAP application programming Interface
  • WAP built-in network protocols
  • Yahoo! Photos is a networked application.
  • the J2METM platform defines configurations, profiles and optional packages as elements for building complete Java run time environments. Configurations are composed of a virtual machine and a minimal set of class libraries and provide the base functionality for a particular range of devices that share similar characteristics.
  • CLDC connected limited device configuration
  • CDC connected device configuration
  • devices with limited memory and processing capabilities e.g., mobile phones, two-way pagers, and PDAs
  • CDC connected device configuration
  • devices with better memory, processing and network bandwidth capabilities e.g., TV set-top boxes, residential gateways, in-vehicle telematics systems, and hi-end PDAs.
  • the configurations must be combined with a set of the high-level APIs, or profiles, that further define the application life cycle model, access to device-specific properties, and user interface.
  • MIDP mobile information device profile
  • J2METM can be further extended by combining various optional packages and their corresponding profiles to address specific market requirements, e.g., BluetoothTM, web services, wireless messaging, multimedia, and database connectivity.
  • any phone or other wireless mobile device can embody a variation of the present invention.
  • the mobile device is a smart handset, downloading application programs and implementing the navigation scheme are possible even though the communications with the service provider may be different in character.
  • the manufacturer provides the Yahoo [-enabled phone 100 with camera functionality ⁇ i.e., functionality for capturing images, and saving, displaying, manipulating, transmitting and receiving data of images — this camera functionality is independent from the Yahoo! Photos program. That is, data of the captured images reside in the mobile phone outside the Yahoo! Photos environment until such time that this data is introduced to the Yahoo! Photos environment by being first uploaded to the Yahoo! server and then downloaded to the local (mobile) Yahoo! Photos album, as will be later explained.
  • various client application programs are offered to the user on a default start-up or main menu screen or on a manufacturer-installed virtual vending machine screen.
  • Other selection items include, for example, the menu item for setting the sound.
  • These start up and vending screens show a menu with a list (or icons) of applications which the user can obtain by following an install procedure.
  • the menu provides links to various service web sites, including, for example, the Yahoo! Photos site.
  • the links are URLs
  • FIG 3 illustrates the flow once users reach the mobile application site, which, in this example, is the Yahoo! Photos landing page.
  • the URL for the landing page is obtained via a link from a promotional web page, through a web search, or from a bookmark (or favorites).
  • the flow is shown as originating on a user's PC (personal computer) and it commences with program information presented at the landing page 302 on the PC display.
  • the contents 303 and 304 of the landing page is presented to show the options available to the user based on whether or not the user has already purchased the Yahoo! Photos program. For instance, the landing page presents to the user the Yahoo!
  • Photos program name with the option of "how to get it now” 304, as well as upload information 306a, flash demo 306b, and pricing information 306d, say, "$2.99 monthly.”
  • upload information 306a say, "$2.99 monthly.
  • a query such as "would you like to buy it for $2.99?"
  • FIGS 4A-4D show the respective PC-based and mobile-based registration and buy flow diagrams.
  • the user confirms acceptance, assuming the user has an account on the server having signed in before, the user is prompted to provide the telephone number of the mobile phone. With that phone number, the server sends a short message embedded with a link to the mobile phone and causes the mobile phone to vibrate or, otherwise, signals the user with a message requesting confirmation of the purchase 326. With this confirmation 426 the server proceeds to send the program to the mobile phone.
  • registration can originate on the PC or the mobile phone.
  • the compatible phone list is reviewed 450 and the phone is deemed compatible, registration can go forward starting with the user entering the 10-digit mobile phone number 452.
  • the service provider dials the 10-digit phone number and requests confirmation from the user via that mobile phone 456.
  • the user is also prompted to follow the buy instructions 460 or follow the link to the vending machine 458.
  • the Yahoo! Photos client home page 268 is presented on the mobile screen.
  • a program such as Yahoo! Photos can be purchased directly via the mobile phone, as shown in Figure 4C. That is, the registration process originating from the mobile phone is launched from the menu page, e.g. Yahoo! I home pages 470 or 472. Beyond that, the link to (virtual) vendor machine page 462, download page 464, confirmation page 466 and home page 468 are similar to those in Figure 4B.
  • Figure 4D shows a first-time purchase flow.
  • the purchase can originate either at the PC or the mobile phone, starting with the respective landing page.
  • the landing page 480 is obtained via a standard browser.
  • the landing page 482 presents the WAP sites, assuming the mobile phone is WAP compliant and uses the micro-browser for linking to this and subsequent pages.
  • the product information i.e. Yahoo! Photos application
  • Download activation 488, progress update 490 and confirmation 492 are provided along the way when the application is loaded.
  • the application is then ready to launch on exiting the micro-browser 494.
  • the home page of Yahoo! Photos is displayed 498.
  • the mobile album is an album of photos stored locally on the mobile phone, so that the user need not go out over the network to obtain them.
  • the online album is an album of photos stored on the server in the user's account.
  • photo images can be captured and manipulated by the mobile phone outside the Yahoo! Photos environment. These photo images will not be available at the mobile or online albums until they are uploaded to the server, stored in the online album and then (selectively or in batch) downloaded to the mobile album, and vice versa.
  • selecting Online album' allows the user to access and manipulate photo images that have already been uploaded to the server from the user's PC or mobile phone and stored in the online album.
  • selecting 'mobile album' allows the user to access and manipulate photo images that have been already downloaded from the server into the mobile album.
  • the 'online album' option is selected from the Yahoo! Photos client program 'home' page (2.0), as shown in Figure 5A, it prompts the program to display the next page which is the 'sign-in' page (1.0). It requires the user to follow a sign-in procedure that typically includes providing a Yahoo! ID and user password. The sign-in procedure will, among others, bring up the user's account and relate it to the user's online albums. That is, the sign- in procedure allows the user to access his account via the Internet (and other proprietary network if applicable).
  • the next page is the 'my online albums' page (2.1).
  • this online albums page lists the names of photo albums available to the named user which are associated with the user's account. Of course, only albums that are on the server are listed, and if the selected album is empty the next page will display an indication to that effect (i.e., "this album is currently empty” at page; 2.1.6). Alternatively, if the album is not empty, selecting that album will bring up the next page, the 'photo list' page for that album (2.1.2).
  • a photo can be selected for downloading it from the server onto the mobile phone. Additionally, a selected photo can be opened or other actions can be invoked in relation to it. The other actions are presented in a menu that is shown on the screen as a pull-down menu, pop-up menu, or a menu superimposed on any part of the current page (in this example the menu is shown as a pull-down menu).
  • Such menu provides a number of selection items, each of each representing an action, including: 'save to mobile,' 'email photo,' 'screen saver,' 'thumbnails,' 'online albums,' and 'home.' Each selection brings up a page that corresponds to the selected action item. Two of the action items have already been discussed above, 'home' and Online album.' Selecting home, will lead the user back to the home page (2.0), and selecting online album, will lead the user to the aforementioned 'my online albums' page (2.1).
  • Selecting 'thumbnails' brings up a 'photo thumbs' page 2.1.1 that shows a group of thumbnail photo images from the selected album.
  • the number of photo thumb groups downloaded from the server depends on the memory size of the mobile phone (or whatever device is used).
  • the user can then thumbnail through the groups of photos in the album.
  • the groups of thumbnail photo images in this album are each loaded from the server. The user can then move between the images back and forth (scroll back and forth) and select any one of the photos in the 'thumbnails' page.
  • a selected thumbnail image will be enlarged in the next page, the Online photo' page (2.1.3).
  • each of the pages, 'photo list' (2.1.2), 'photo- thumbs' (2.1.1), and 'online photo' (2.1.3) includes the photo options menu feature.
  • these action items when 'save to mobile' is invoked from the 'photo list' page, 'photo thumbs' page, or 'online photo' page, it causes the selected photo image (previously downloaded from the server) to be saved in the mobile album on the mobile phone.
  • the 'added to mobile' page (2.1.7) is brought up in this case to show the photo being saved and to give an indication that saving is done.
  • 'email photo' action When 'email photo' action is invoked, the 'share as email' page comes up (2.1.5). This page shows the photo(s) selected for emailing and prompts the user for the email address.
  • a number of recently-used email addresses are provided.
  • 'email' is simply a transport mechanism which is presently used to send photos from camera phones. Other transport mechanisms may be developed and employed for this application.
  • a message pops up indicating that the email has been sent or, if not, that an error occurred. For example, a transmission will fail if the user is not authorized to upload photos to the selected e-mail.
  • An error message of this kind is a product of the upload security scheme in the Yahoo! Photos application program.
  • the selected photo When the 'screen saver' action is invoked, the selected photo will be used to populate the screen when the phone is idle, standing by, or starting up.
  • the 'screen saver' option is associated with screen saver page (2.1.4) which shows the selected photo and requires the user to select 'OK' or 'cancel' to add this photo to the screen saver photo roster.
  • a message pops up to indicate the status of the photo download.
  • the mobile album screen flow shown in Figure 5B, starts with the 'home' page (2.0) and selection of the mobile album brings up the 'mobile photo ' list page (3.1.1).
  • This page presents two action menus, 'open' and 'action.' Thus, selection of any of the listed photos can be followed by selecting 'open' or 'action.'
  • 'open' is selected the photo is shown on the screen in the 'photo thumbs' page (3.1.2).
  • a mobile photo action menu is provided.
  • This menu includes action items such as 'slide show,' 'move,' 'delete photo,' 'delete all' (photos), 'thumbnails,' 'history,' and 'home.'
  • thumbnails feature associated with the 'photo thumbs' page (3.1.2), works as described above with reference to the online album.
  • a photo selected on the mobile 'photo thumbs' page can be enlarged as shown in the next page, the 'mobile photo' page (3.1.3).
  • the menu for the 'photo thumbs' and 'mobile photo' pages includes a subset of the aforementioned mobile photo action menu.
  • the 'move' page comes up (3.2.1) when the 'move' action (referred to also as 'rearrange ' action) is selected from any one of the three pages (3.1.1, 3.1.2 and 3.1.3).
  • the program displays a group of photos (thumbnails) and the user can rearrange the photos using the 5-point navigation key, as well as choose to drop a photo or save it (Figure 5D shows flow diagrams for photos view, share and save).
  • the user has the option of deleting or canceling the delete action (as shown in pages 3.2.5 and 3.2.4).
  • the 'delete' page shows the photo selected for deletion to allow the user to change their mind.
  • the 'mobile album empty' page is displayed (3.1.4). It allows the user to select the home page or select the answer to any one of the queries, such as "where are my photos?" and "what is the mobile album?.” Selection of the latter will bring up the 'about' page (3.1.4.1), and in this page pressing 'OK' provides user access to the online album(s). Selection of the former brings up the 'restore album' page 3.1.4.2.
  • the "restore" function is explained in more detail below.
  • the server associates the user's identification with his historical record so that the application program can record (backup) the photo in the server each time the user saves a photo to the mobile album.
  • This historical record serves as a backup that allows the user to restore his album if the Yahoo! Photos program is erased, for any reason, from the mobile phone memory and the user then reloads this program.
  • This history feature is useful to reduce the navigation for restoring the mobile album since the server maintains this information in the user's client account.
  • every photo from the user's online album that is saved to the mobile album is 'remembered' by the server.
  • the page traversal path is not predictive the history is recorded accurately and fully.
  • each mobile phone device is distinct, and a user may have more than one device, each device can in principle have its own distinct historical record. However, it can be arranged when the user first establishes or later updates his account that the user's Yahoo! ID is associated with a plurality of mobile phones and, upon signing in, the user can have access to his historical record from any one of these mobile phones.
  • the historical record provides a mobile album backup for restoring that album.
  • the user when the user reloads the application, it will query the user as to whether the user wishes to restore any of the mobile album photos. That is, when the user selects the query "where are my photos?" (in page 3.1.4) the 'restore album' page is displayed (3.1.4.2). As with the previous page (3.1.4), this page allows the user to go to the 'home' page (2.0) and, this time via 'OK', it allows the user to go to the next mobile 'restore album' page (3.1.4.2.1) for a historical photo download list (of photos previously downloaded to the mobile phone).
  • Figure 5E illustrates in more detail the flow of restoring the mobile album from the server backup. Specifically, after traversing the 'home' and 'mobile album empty' pages (2.0 and 3.1.4), the user lends on the 'restore album' page (3.1.4.2). On selecting the 'OK' option, if the user is logged in the Yahoo! Photos server responds with the download history list of photos (steps 33, 35). This response prompts the mobile device to bring up the 'restore album' page (3.1.4.2.1) with the download history list of, say, 20 last photos that were added to the mobile album. From this historical list, the photos can be picked (see, e.g., checkmarks) and then the selected photos can be restored to the mobile album using the save/cancel menu options. The selected photos are then downloaded from the server in a batch process (step 37). The mobile album is then available for user access via 'mobile album' page (3.1.1).
  • the pages can be traversed forward as described above and they can be traversed backwards using the "back button” feature.
  • Figure 6 provides a simplified diagram to illustrate the "back button” feature.
  • the "back a level” mode allows hierarchical backwards sequence traversal one level each time the 'back' button is touch activated or clicked (hereafter “clicked”).
  • the "back in sequence” mode allows sequential backwards one page each time the 'back' button is pressed.
  • back a level takes the application from a photo page (e.g., 6) one level up to the list of photos page (3); and from there one more level up to the list of albums page (2) and one more level up to the home page (1).
  • the back in sequence mode functions to take the application from the current photo page (6) to the former photo page (5), rather than up one level (3), when the back button is touched. Additional activations of the back button will traverse through all the pages in reverse sequence.
  • the navigation feature provides backwards traversal through pages as described above the navigation feature as described in more detail below provides up-down traversal within these pages, particularly photo pages.
  • the relevant and effective method involves collapsing and expanding and following the hierarchy presented in these pages.
  • this type of navigation pattern improves the user interface in the context of mobile application. Moreover, with this type of navigation there is room left for an action menu or action icons that are context specific. Therefore, this directory navigation feature addresses the challenge of navigating a directory tree while simultaneously providing multiple context sensitive action choices for a selected item.
  • the directories are structured as well as presented in a tree-like hierarchical format. For example, in mobile photos application such as the client Yahoo! Photos, the directory is the mobile albums. In other possible implementations, the directory points to the mobile albums. Either way, the directory is structured as a tree-like hierarchy. In the hierarchical tree-shaped directory each item is a node. In the context of the client Yahoo!
  • a node is, an item in the mobile albums list.
  • the directory navigation employs node collapsing and expansion. For each node, the state of either expanded or collapsed is remembered so that when the very same node is clicked, the right action can be taken accordingly. Clicking on the node functions as a toggle between the collapsed and expanded states.
  • FIG. 7 is a screen shot of a mobile album showing a list of photos along with action icons (at the bottom of the screen).
  • the list of photos includes, for example: - aphotos alex.jpg alhambra.jpg derrick&Kevin.jpg greece.jpg more + animals + my garden + my kids
  • Clicking 'aphotos' album again collapses that node back to: + aphotos + animals + my garden + my kids
  • action icons are graphically presented. These icons are provided for users to take actions specific to the selected item.
  • the first icon on the left allows the user to bring up the selected photo.
  • the left/right arrows allow the user to scroll left or right to reveal additional icons of action choices.
  • the number of action icons is determined by the nature of the item selected. Preferably, only actions that apply to the item are made available. This, of course, saves space on the screen.
  • the navigation scheme improves user interface.
  • the visual and interaction design as described herein should accommodate various types of mobile devices, including, for example, those listed in the table below.
  • the following keys are available on the mobile devices: Up; Down; Left; Right; Select OK; Left Soft key; Right Soft key; and Back. If a device does not have an obvious select key, it is assumed that the MIDP (mobile information device profile) implementation will automatically provide a select option at one of the soft keys or in one of the soft key menus.
  • MIDP mobile information device profile
  • Back 'Back' button links back to previous screen. Does NOT link one level up in the navigation tree, unless that is the previous screen. Does not link back to confirmation or error popups.
  • data previously entered into fields may not be shown when user navigates back to a page. However, actual implementations may differ based on the technical constraints.
  • the first item on a page is pre-selected (default item) unless the user Selection has performed some action, like viewing or renaming an image.
  • labels that may appear on a soft key are restricted to 7 characters.
  • Menu-only items are restricted to 14 characters.
  • OK Performs the default action for a screen or for a selected item. Moves the user forward in a task, (e.g., opens an album or photo.)
  • Back label should be used only for the Back function described above. If possible, Back should always map only to the device back button.
  • CONFIRMATION POPUP One type of global elements, presented as “Confirm Popup” screens, are used for displaying a confirmation to the user.
  • the confirmation popup screens contain simple text such as "Done” or “Saved”, and they disappears automatically after a short time.
  • the "in progress" screen informs the user that the application is waiting for a response from the server or is processing a request.
  • Each device has a default screen with text and a moving graphic, and, alternatively, it is replaced with a Yahoo! Canvas screen.
  • the online album pages are made available to the user in forward and backwards traversal; each page having default selection items associated with it.
  • the forward traversal starts, of course, with the home page (2.0).
  • the following tables outline for each page separately the default selection items available in that page for screen flows.
  • Default One thumbnail is always selected. Selection is indicated by 2 pixel black border. Selection When scrolling to a page either (1) or (4) is selected. When returning from a list view, full-screen view, or action screen the last selected image is selected.
  • Default One item is always selected. Selection When returning from a thumbnail view, full-screen view, or action screen the last selected image is selected. After deleting, the image in the spot that contained the deleted image is selected.
  • the mobile album pages are made available to the user in forward and backwards traversal; each page having default selection items associated with it.
  • the forward traversal starts, of course, with the home page (2.0).
  • the following tables outline for each page separately the default selection items available in that page for screen flows.
  • Default One thumbnail is always selected. Selection is indicated by 2 pixel Selection border.
  • the last selected image is selected. After deleting, the image in the spot that contained the deleted image is selected. After Moving, the last moved image is selected.

Abstract

Navigation management occurs in a mobile device during a directory up-down scroll and it involves a user interface and a directory (e.g. mobile directory of photos). The directory is a tree-shaped hierarchy of nodes such that any node on the directory is selectable by a user via the user interface. This way navigation can flow up-down through the directory. Additionally, the navigation management involves associating a state and one or more action items with each node and saving the state. The state is an expanded or collapsed condition of the node. If the state of a particular node is expanded, additional nodes at a lower level of the hierarchy are presented to the user. If its state is collapsed only that particular node is presented and the other nodes are hidden. The user interface includes for any node selected by the user its associated one or more action items.

Description

NAVIGATION PATTERN ON A DIRECTORY TREE
REFERENCE TO PRIOR APPLICATIONS
This application claims the benefit of and incorporates by reference U.S. Patent Application 10/959,917, entitled "NAVIGATION PATTERN ON A DIRECTORY TREE," filed October 5, 2004, and U.S. Provisional Application 60/518,898 entitled "BACK BUTTON IN MOBILE APPLICATION," U.S. Provisional Application 60/518,858, entitled "NAVIGATION PATTERN ON A DIRECTORY TREE," U.S. Provisional Application 60/518,857, entitled "BACKUP AND RESTORE IN MOBILE APPLICATIONS," and U.S. Provisional Application 60/518,897, entitled "UPLOAD SECURITY SCHEME," all of which were filed November 10, 2003. FIELD OF THE INVENTION
The present invention relates generally to wireless mobile devices and more particularly to applications that offer navigation in a directory tree. Among such applications, one type is a mobile photos application.
BACKGROUND Mobile-friendly technologies are advanced to provide a rich multimedia environment and enhance the wireless device users' experience. An outcome of this evolution is the manifest closeness between the wireless universe and the internet domain, as well as the advent of wireless devices with multimedia capabilities. The newest versions of mobile wireless devices such as digital mobile phones, pagers, personal digital assistants (PDAs), handsets, and any other wireless terminals, have multimedia capabilities including the ability to retrieve e-mail, and push and pull information via the Internet.
However, because mobile devices typically have limited display size and an awkward navigation mechanism, it is always a challenge to navigate up/down a directory tree while simultaneously providing multiple action choices for a selected item. Hence, with a limited memory capacity, screen space and user interface capability, there is a need to optimize the mechanism for navigating a directory tree (a tree-shaped directory) and for taking context - sensitive actions. The directory navigation approach presented here proposes a solution to this and related problems. SUMMARY
The present invention is based, in part, on the observation that a need exists for effective management of navigation in mobile devices, and that navigation patterns can be improved as described below. Accordingly, the navigation management concept is implemented providing a navigation pattern in a directory tree along with one or more context-specific action choices (menu or icons). For each selected item in the directory, the action choices can be different and tailored to that item.
The principles of the proposed directory tree navigation management apply equally well to any mobile application although it is illustrated here with reference to a mobile photos application program implemented as the client-side Yahoo IPhotos program.
For the purpose of this invention, as embodied and broadly described herein, a method, a computer readable medium and a system are proposed as possible implementations of the navigation management concept. These implementations involve a mobile device that is typically capable of communicating with a server and other mobile devices. The mobile devices are often wireless devices such as wireless camera phones and the content is photograph data (or simply one or more photos).
In one embodiment, a method for managing navigation in mobile devices involves providing user interface in a mobile device, constructing a directory as a tree-shaped hierarchy of nodes, and providing the directory such that any node on the directory is selectable by a user via the user interface. This way, the navigation can flow up-down through the directory tree. This method involves also associating a state and one or more action items with each node and saving the state of each node. The state is an expanded or collapsed condition of the node, wherein if the state of a particular node is expanded additional nodes at a lower level of the hierarchy are presented to the user, otherwise if the state is collapsed only that particular node is presented and the other nodes are hidden. In this method there is the further step of providing in the user interface for any node selected by the user its associated one or more action items.
For any node that is selectable by the user, the one or more action items associated with that - node are action choices provided in the user interface either as icons or as menu items. Moreover, for any node selectable by the user during the up-down navigation the number of action items associated with such node is determined by its nature, there being provided only action items that apply to such node. Then, overflow indicators are provided when the number of these action items exceeds a maximum number of action items that fit in the user interface, wherein the overflow indicators enable the user to scroll back a forth through all these action items.
In a typical operation, initially, a visible part of the directory provided to the user includes a top level of the tree-shaped hierarchy of nodes in a collapsed state. But as selected ones of these nodes are toggled they are expanded and more nodes, at a lower level of the hierarchy, are made visible and when toggled again these higher-level nodes are again collapsed.
Typically also, the mobile devices are a wireless devices such as a wireless camera phones that download and run the Yahoo IPhotos program. Thus, with Yahoo IPhotos programs, the directory is a mobile album. In this case, the nodes in the tree-shaped hierarchy include a root node and any number of child nodes, such that any node that is childless is a leaf node which in the mobile album is a photo.
The approach described above can be implemented in a computer readable medium embodying a computer program with program code for providing the navigation. The computer program is the client side of the mobile application program. Other parts of a typical mobile application are the server side and networking service programs.
A system for providing the navigation management in a mobile device includes a processor, a screen for user interface, and a memory. The memory embodies a client-side program with program code for causing the processor to perform the method steps as described above.
As can be understood from these examples, by introducing the navigation capability to the system, the present invention makes the interface more user friendly. Such advantages will be appreciated by those of ordinary skill in the art from the description and practice of the invention disclosed herein.
BRIEF DESCRIPTION OF THE DRAWINGS
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve _ to explain the principles of the invention. Wherever convenient, same or similar numbers or designations are used throughout the drawings to refer to the same or like elements. Figure 1 shows a wireless interconnection model using one of the many types of available bearer networks.
Figure 1 A shows another model of interaction, via bearer networks, between 3rd-generation (3G)-enabled mobile devices and servers as well as other devices.
Figure 2 shows a mobile phone with features associated with the present invention.
Figure 3 illustrates the flow once users reach the Yahoo! Photos landing page.
Figures 4A-4D show the respective PC-based and mobile device-based registration and application buy flow diagrams.
Figures 5A and 5B show the screen flows for online albums and mobile albums, respectively.
Figure 5C, parts (i) and (ii), describes setting up favorites for the mobile album slideshow.
Figure 5D shows flow diagrams for photos view, share and save.
Figure 5E illustrates the flow of restoring the mobile album from the server backup.
Figure 6 provides a simplified diagram to illustrate the back button feature.
Figure 7 is a screen shot of a mobile album showing a list of photos and action icons at the bottom of the screen.
DETAILED DESCRIPTION OF THE INVENTION
The present invention contemplates a navigation pattern in a directory tree and implementation of this concept in mobile applications. One such application is mobile photos, an example of which is referred to as the Yahoo! Photos™ application. Yahoo! and Yahoo! Photos are trademarks of Yahoo! Inc., Sunnyvale, CA. Any other trademarks are the property of their respective holders.
Indeed, although it can be implemented in various applications, for clarity and for illustration, the approach contemplated by the present invention is described here in the context of the Yahoo! Photos application. Thus it is useful to provide a description of the Yahoo! photos program in which an instance of the directory navigation is embodied. The description of this application precedes the details of the navigation to give it proper context. The server side of this application is the "server Yahoo! Photos," and the client side of this application is the mobile client application, or "client Yahoo! Photos." A client application is generally considered to be a downloadable application; namely, J2ME™ (Java™ 2 platform, Micro Edition, by Sun Microsystems, Inc.), Yahoo! Photos™, or any other application that is downloadable to the mobile device. In the example here, the client Yahoo! Photos runs on a mobile phone, and more specifically, a mobile camera phone.
THE WIRELESS COMMUNICATION ENVIRONMENT
WIRELESS COMMUNICATION PROTOCOLS
Wireless protocols, the standards which govern communications of data between wireless devices and the Internet, utilize and support the enhanced capabilities of modem mobile^ wireless devices and Internet content technologies. Hypertext transfer protocol (HTTP) is an often used standard, and other standards include the Wireless Application Protocol (WAP), M-services, i-Mode and Web clipping. Although other protocols are also possible, WAP appears to provide a proper framework for the content sharing. Therefore, adoption of standards such as WAP is suitable for the purpose of the present invention, and it is discussed in some detail below.
The adoption of WAP builds on existing Internet standards and protocols adapted for use in wireless communication networks and addresses the unique characteristics of mobile wireless devices (with limited computing, memory, display, user interface, and power capabilities). WAP is a specification suite defining a set of protocols for presentation and delivery of wireless information and telephony services on mobile wireless devices. WAP services provide information access and delivery to WAP-enabled devices. WAP was designed to empower users with easy and instant access to information and interactive services. Thus, interoperability between WAP-enabled device is possible through any WAP-compliant infrastructure to deliver timely information and accept transaction and queries.
WAP can be built on any operating system, including PalmOS, EPOC, Windows CE, FLEXOS, OS/9, JAVA OS etc. Being air interface independent, WAP is designed to be scalable to new networks as they develop, allowing bearer independence and development of common solutions across disparate networks. The term "WAP" is commonly used to refer to the wireless application environment (WAE) although it is WAE that includes the WAP suit of protocols and technologies. WAE provides the rich application environment which enables delivery of information and interactive services to mobile wireless devices. An important aspect of the WAE is the WAP stack, namely the wireless protocol layers, as shown for example in Figure 1. At the bottom of the WAP stack 11 is a network layer, topped by the transport layer, the security layer, the transaction layer, and the session layer.
Briefly, the network protocol layer supports network interface definitions, governing interface with the networks of wireless service providers (wireless bearers) such as short message service (SMS), code division multiple access (CDMA), cellular digital packet data (CDPD), general packet radio service (GPRS), high speed circuit-switched data (HSCSD), third generation (3G), GSM (global system for mobile communications), and unstructured supplementary service data (USSD) channel. The wireless transport layer supports the wireless datagram protocol (WDP), and when operating over an IP (Internet protocol) network layer WDP is replaced with user datagram protocol/IP (UDP/IP). WDP offers to the upper protocol layers a datagram service and transparent communication over the underlying bearer seivices. In other words, WDP offers to the upper protocol layers a common interface to and ability to function independent of the type of bearer wireless network. The wireless transport layer security (WTLS) provides a secure transport service to preserve the privacy, authentication and data integrity of the transport service at the layer below, as well as the ability to create and terminate secure connections between communicating applications. The transaction protocol (WTP) layer provides transaction oriented protocol for the WAP datagram service, including, for example, request-response transactions. The wireless session protocol (WSP) layer provides HTTP/1.1 functionality and features such as session suspend/resume. The WSP provides the upper-level application lever of the WAE with an interface to connection and connectionless services operating above the transaction protocol and the datagram transport layers, respectively.
The WAE (i.e., the wireless application environment) is further fashioned with a wireless markup language (WML) micro-browser, a WML script virtual machine, a WML script standard library, a wireless telephony application interface (TAT), and WAP content types. The WAP micrcπbrowser also referred to as the "WAP browser," facilitates interaction between WAP/Web applications and WAP-enabled devices. The micro-browser is a tag- based wireless browser application supporting wireless markup language (WML), and extensible transport hyperlink markup language (XTHML). The micro-browser uses the "card" metaphor for user interface, where user interactions are split into cards. The WAP card metaphor provides a common interface to which all applications can conform, much like the desktop metaphor in PCs. The micro-browser supports user actions, defined at tree levels (deck, card, and select & link options, i.e., ACCEPT, PREV, etc.) and default tasks (PREV, NOOP, etc.). For example, a deck of cards is split into a navigation card, variables card, and input elements card. A navigation card is formed as a script encapsulated with the 'card' tags. The following example of a card includes the type of interaction (DO TYPE="ACCEPT") and link (GO UR ="#eCARD").
<CARD> <D0 TYPE="ACCEPT"> <Gθ URL="#eCARD"/> </DO WELCOME! </CARD>
WIRELESS COMMUNICATION INFRASTRUCTURE
Figure 1 shows a wireless interconnection model 10 using one of the many types of available bearer networks 12. The illustrated wireless mobile devices 100 are presumed to have sufficient local memory and Internet access capability to allow a user to download programs from servers 18 through the Internet 16 (and any other network such as LAN, WAN or
Ethernet network) and store them in the local memory. Thus, wireless subscribers can gain fast access to content in these or other servers via the Internet through various downloadable applications. Note that the illustrated server 18 can be the origin of downloadable programs as well as the origin, or destination, of content; although programs and content can originate at or be destined for different servers. For the purpose of this illustration, the web server 18 is the source of the Yahoo! Photos client side application as well as the source, and destination, of content, particularly photos (image data). Using the downloaded program, such as Yahoo! Photos, and with multimedia capabilities, including the ability to retrieve e-mail, and push and pull information via the Internet, network operators (or, more generally, service providers) add value propositions beyond voice or text offerings.
Indeed, with this capability, users can capture photo images in their mobile devices, store and manipulate the captured images, and upload data of the captured images to a server (e.g., server 18). Thus, the server 18 operates as a repository for the data of photo images, and users can download from the server to their mobile devices data of previously captured photo images, as well as store and manipulate such images. Photos resident on one mobile device can be shared with another via the server 18 and the communication network(s) 12 and 16.
5 In this wireless interconnect model, the mobile phones used to download the Yahoo! Photos client side program are WAP-enabled. As shown in Figure 1, the WAP-enabled devices 100 support the WAP protocol and the server 18 typically supports the WWW (world-wide web) protocol. In particular, the wireless application environment at the mobile device side 11 includes the micro-browser, a suite of WAP protocols at the network through session layers,
10 and the downloadable (client-side) Yahoo! Photos application program. The micro-browser defines how WML documents and WML script applets should be interpreted and presented to the mobile device user. The Micro-browser's WTA (wireless telephone application) functionality provides call control, phone book access and messaging within WML script applets to allow selective call forwarding or other secure telephony. The wireless application
15 environment at the server side 13 includes the server-side Yahoo! Photos in addition to a standard web browser and WWW protocol stack (HTTP and TCP/IP).
To enable web-based access to content, service providers deploy wireless data through the carrier network 12 while controlling the data communications to their subscribers and tracking the billable activity. Typically, the gateway 14 is tasked with tracking subscriber 20 activities, controlling access and, in addition, functioning as the proxy for the mobile device 100, on the one hand, and for the server 18, on the other hand. The gateway 14 is implemented, building on standard web proxy technology, to interconnect the services offered by the wireless service providers to the HTTP protocol so as to permit access to content on the wired Internet.
25 One model of interaction between a WAP-enabled device, the WAP-enabled proxy/gateway, and the server, is the Hypertext Transfer Protocol (HTTP) 1.1 response/request transaction, where HTTP 1.1 is profiled for the wireless environment. The gateway (13 & 14) translates requests from the WAP protocol to the WWW protocol, and vice versa; translating WML(/HTML) documents to HTML(/WML), resolving domain names in URLs and
30.. providing a control point for managing access. From the WAP-enabled gateway with encoders/decoders, the URL requests or WML documents (possibly in encoded form) can be sent encoded/decoded to add security to the user interaction. Note that, unlike the flat structure of HTML documents, WML documents are divided into a set of user interaction units, namely a deck of cards. Each user interaction unit is a card (or page), and the user can navigate between cards in one or more WML documents.
Another model of interaction between a WAP-enabled device, the WAP-enabled proxy/gateway, and the server, is the HTTP response/request transaction (protocol running on top of the Internet's TCP/IP suite of protocols). This model is appropriate for the newer WAP 2.0 (with protocol stack not shown in Figure 1). Unlike the above-mentioned, and illustrated, WAP stack 11, WAP 2.0 stack includes the IP, TCP (transmission control protocol), TLS, HTTP and WAE layers atop the network layer (all of which are profiled for wireless environment). For example, the wireless profile for the TLS protocol will permit interoperability for secure transactions.
Yet another model of interaction via bearer networks, between 3rd-generation (3G)-enabled mobile devices and servers or other devices, is shown in Figure 1 A. As shown, a 3G terminal supports higher-speed, wider-band wireless cellular service communications based on various technologies, including wide code division multiple access (W-CDMA), general packet radio service (GPRS), global system for mobile communications (GSM), enhanced data rates for global evolution (EDGE), unified threat management system (UMTS), and high speed circuit switched data (HSCSD). A 3G terminal is equipped with cordless connections for local, short distance communications. The communication protocols in the 3G terminal are comparable to the open system interconnection (OSI) protocols, layered in the OSI stack.
Various services are supported by these protocols, including web browsing, short message service (SMS), multimedia messaging service (MMS), e-mail, M-commerce, real-time video, and pre-paid. The MMS, for example, is a store and forward messaging service capable of adding multimedia elements to SMS, including images, text, audio clips, and video clips. MMS is synchronized across a common timeline, rather than being discrete like e-mail and SMS; it is akin to a presentation layer over e-mail and looking like a slide show with images. On a compatible phone, the MMS message will appear with a new message alert. The picture message will open on the screen, the text will appear below the image and the sound will begin to play automatically.
Downloadable applications such as Yahoo! Photos and network games are likewise supported in the 3G terminal and interact with services such as MMS. The originator can easily create a multimedia message, either using a built-in or accessory camera, or can use images and sounds stored previously in the phone (and possibly downloaded from a web site). However, for simplicity, the following description assumes that the mobile device is a WAP-enabled camera phone used for downloading photo applications such as the Yahoo! Photos.
Figure 2 shows a mobile phone 100, not necessarily associated with any particular manufacturer, but with features suitable for the purpose of the present invention. For example, to accommodate the Yahoo! Photos application, the mobile phone 100 has a camera feature with the camera lens 112 exposed for capturing images. The mobile phone 100 also has a 5-point navigation key (also called game key) 114, and it features left, right, up, down and selection, or 'OK,' functions, substantially mimicking the operations of a mouse. The main menu button 116 activates the menu display on the screen, and the main OK button 118 activates a menu selection. The 'back' button 110 is shown as a hardware key whose position here is merely exemplary. Namely, the physical placement of the 'back' button is device dependent, where it is anticipated that buttons on different devices may be arranged differently. A 'back' soft-key is possible to implement a 'back' function of the WAP browser, which means that it would show up as an icon or menu item on the screen of the mobile phone. ,
As further shown in Figure 2, the Yahoo! -enabled phone 100 supports wireless cellular service communications based on various technologies such as the GPRS and GSM. This device is configured for supporting WAP communication protocols (at all layers of the WAP stack). Various services shown as being supported by these protocols, include web browsing, SMS, MMS, e-mail, M-commerce, real-time video, and pre-paid. The downloadable programs shown to interact with such services include the network games and Yahoo! Photos.
The mobile device functionality is preferably implemented using a platform, such as the
J2ME™ platform, which is tailored for a broad range of embedded devices including mobile phones. The J2ME™ platform includes a set of standard Java APIs (application programming Interface), and provides a user interface, a security model, built-in network protocols (e.g., WAP, as shown in Figure 1), and support for networked and disconnected applications (Yahoo! Photos is a networked application). With the J2ME™ platform, applications are written once for a wide range of device. Applications leveraging each device's native capabilities are then downloaded dynamically. The J2ME™ platform defines configurations, profiles and optional packages as elements for building complete Java run time environments. Configurations are composed of a virtual machine and a minimal set of class libraries and provide the base functionality for a particular range of devices that share similar characteristics. Current configurations include connected limited device configuration (CLDC) for devices with limited memory and processing capabilities (e.g., mobile phones, two-way pagers, and PDAs) and connected device configuration (CDC) for devices with better memory, processing and network bandwidth capabilities (e.g., TV set-top boxes, residential gateways, in-vehicle telematics systems, and hi-end PDAs). However, in order to provide a complete runtime environment targeted at specific device categories, the configurations must be combined with a set of the high-level APIs, or profiles, that further define the application life cycle model, access to device-specific properties, and user interface.
One example of profiles is the mobile information device profile (MIDP) which is designed for mobile phones and entry-level PDAs. MIDP offers a core application functionality required by mobile applications, including user interface, network connectivity, local data storage, and application management. The J2ME™ can be further extended by combining various optional packages and their corresponding profiles to address specific market requirements, e.g., Bluetooth™, web services, wireless messaging, multimedia, and database connectivity.
THE NAVIGATION IN THE CONTEXT OF MOBILE YAHOO! PHOTOS
Note that the example here focuses on the camera phone, but the principles of the present invention are not limited to camera phones. Any phone or other wireless mobile device can embody a variation of the present invention. When the mobile device is a smart handset, downloading application programs and implementing the navigation scheme are possible even though the communications with the service provider may be different in character.
It should be mentioned that, although the manufacturer provides the Yahoo [-enabled phone 100 with camera functionality ~ i.e., functionality for capturing images, and saving, displaying, manipulating, transmitting and receiving data of images — this camera functionality is independent from the Yahoo! Photos program. That is, data of the captured images reside in the mobile phone outside the Yahoo! Photos environment until such time that this data is introduced to the Yahoo! Photos environment by being first uploaded to the Yahoo! server and then downloaded to the local (mobile) Yahoo! Photos album, as will be later explained.
On mobile devices, various client application programs are offered to the user on a default start-up or main menu screen or on a manufacturer-installed virtual vending machine screen. Other selection items include, for example, the menu item for setting the sound. These start up and vending screens show a menu with a list (or icons) of applications which the user can obtain by following an install procedure. The menu provides links to various service web sites, including, for example, the Yahoo! Photos site. The links, of course, are URLs
(Uniform Resource Locator) ~ i.e., the world wide web address of a site on the Internet, and on the Yahoo! -enabled phone, at least one such menu item is the link for downloading the Yahoo! Photos application.
Figure 3 illustrates the flow once users reach the mobile application site, which, in this example, is the Yahoo! Photos landing page. The URL for the landing page is obtained via a link from a promotional web page, through a web search, or from a bookmark (or favorites). The flow is shown as originating on a user's PC (personal computer) and it commences with program information presented at the landing page 302 on the PC display. The contents 303 and 304 of the landing page is presented to show the options available to the user based on whether or not the user has already purchased the Yahoo! Photos program. For instance, the landing page presents to the user the Yahoo! Photos program name with the option of "how to get it now" 304, as well as upload information 306a, flash demo 306b, and pricing information 306d, say, "$2.99 monthly." To buy the application the user clicks on the application name, Yahoo! Photos, or on "how to get it now." Subsequent to the registration 400A- a query (such as "would you like to buy it for $2.99?") prompts the user to accept/reject the offer 320. Then, for the purpose of implementing upload security, the user is prompted to establish upload opt-in parameters 500, as will be later explained.
If the user accepts the offer to buy the application, the order is confirmed 322 and the application is downloaded into the mobile phone, becoming resident on the mobile phone. Figures 4A-4D show the respective PC-based and mobile-based registration and buy flow diagrams. Incidentally, as shown in Figures 3 and 4A, if the user confirms acceptance, assuming the user has an account on the server having signed in before, the user is prompted to provide the telephone number of the mobile phone. With that phone number, the server sends a short message embedded with a link to the mobile phone and causes the mobile phone to vibrate or, otherwise, signals the user with a message requesting confirmation of the purchase 326. With this confirmation 426 the server proceeds to send the program to the mobile phone.
As shown in Figures 4B and 4C, registration can originate on the PC or the mobile phone. In the PC-based registration process, once, the compatible phone list is reviewed 450 and the phone is deemed compatible, registration can go forward starting with the user entering the 10-digit mobile phone number 452. The service provider dials the 10-digit phone number and requests confirmation from the user via that mobile phone 456. The user is also prompted to follow the buy instructions 460 or follow the link to the vending machine 458. Once the download takes place the Yahoo! Photos client home page 268 is presented on the mobile screen. Alternatively, rather than indirectly via the PC, a program such as Yahoo! Photos can be purchased directly via the mobile phone, as shown in Figure 4C. That is, the registration process originating from the mobile phone is launched from the menu page, e.g. Yahoo! I home pages 470 or 472. Beyond that, the link to (virtual) vendor machine page 462, download page 464, confirmation page 466 and home page 468 are similar to those in Figure 4B.
Figure 4D shows a first-time purchase flow. As can be seen, the purchase can originate either at the PC or the mobile phone, starting with the respective landing page. Note that in the PC- based process the landing page 480 is obtained via a standard browser. In the mobile-based process, the landing page 482 presents the WAP sites, assuming the mobile phone is WAP compliant and uses the micro-browser for linking to this and subsequent pages. Then, for a first time purchaser the product information (i.e. Yahoo! Photos application) is introduced along with price and links to terms of use and buy/cancel selection buttons (icons) 486. Download activation 488, progress update 490 and confirmation 492 are provided along the way when the application is loaded. The application is then ready to launch on exiting the micro-browser 494. After being invoked, the home page of Yahoo! Photos is displayed 498.
Once the Yahoo! Photos program is resident on the mobile phone it can be invoked from the landing page or menu page (using the menu button on the phone to bring up the menu or using the default menu if Yahoo! Photos is presented as one of the default menu options). Invocation of the Yahoo! Photos application allows, among others, user access and manipulation of the user's mobile album as well as online albums in the user account. Figures 5A and 5B show the screen flows for online albums and mobile albums, respectively.
Invocation of Yahoo! Photos prompts this program to display the 'home' page 2.0 with two main options: mobile album, and online album (as shown in Figures 6 A and 6B). The mobile album is an album of photos stored locally on the mobile phone, so that the user need not go out over the network to obtain them. The online album is an album of photos stored on the server in the user's account. As mentioned before, photo images can be captured and manipulated by the mobile phone outside the Yahoo! Photos environment. These photo images will not be available at the mobile or online albums until they are uploaded to the server, stored in the online album and then (selectively or in batch) downloaded to the mobile album, and vice versa. Accordingly, selecting Online album' allows the user to access and manipulate photo images that have already been uploaded to the server from the user's PC or mobile phone and stored in the online album. Likewise, selecting 'mobile album' allows the user to access and manipulate photo images that have been already downloaded from the server into the mobile album.
Then, if the 'online album' option is selected from the Yahoo! Photos client program 'home' page (2.0), as shown in Figure 5A, it prompts the program to display the next page which is the 'sign-in' page (1.0). It requires the user to follow a sign-in procedure that typically includes providing a Yahoo! ID and user password. The sign-in procedure will, among others, bring up the user's account and relate it to the user's online albums. That is, the sign- in procedure allows the user to access his account via the Internet (and other proprietary network if applicable).
The next page is the 'my online albums' page (2.1). For the specific user, this online albums page lists the names of photo albums available to the named user which are associated with the user's account. Of course, only albums that are on the server are listed, and if the selected album is empty the next page will display an indication to that effect (i.e., "this album is currently empty" at page; 2.1.6). Alternatively, if the album is not empty, selecting that album will bring up the next page, the 'photo list' page for that album (2.1.2). In the 'photo list' page, a photo can be selected for downloading it from the server onto the mobile phone. Additionally, a selected photo can be opened or other actions can be invoked in relation to it. The other actions are presented in a menu that is shown on the screen as a pull-down menu, pop-up menu, or a menu superimposed on any part of the current page (in this example the menu is shown as a pull-down menu).
Such menu (hereafter "photo options menu") provides a number of selection items, each of each representing an action, including: 'save to mobile,' 'email photo,' 'screen saver,' 'thumbnails,' 'online albums,' and 'home.' Each selection brings up a page that corresponds to the selected action item. Two of the action items have already been discussed above, 'home' and Online album.' Selecting home, will lead the user back to the home page (2.0), and selecting online album, will lead the user to the aforementioned 'my online albums' page (2.1).
Selecting 'thumbnails' brings up a 'photo thumbs' page 2.1.1 that shows a group of thumbnail photo images from the selected album. Note that the number of photo thumb groups downloaded from the server depends on the memory size of the mobile phone (or whatever device is used). With this feature, the user can then thumbnail through the groups of photos in the album. The groups of thumbnail photo images in this album are each loaded from the server. The user can then move between the images back and forth (scroll back and forth) and select any one of the photos in the 'thumbnails' page. A selected thumbnail image will be enlarged in the next page, the Online photo' page (2.1.3).
As can be seen, each of the pages, 'photo list' (2.1.2), 'photo- thumbs' (2.1.1), and 'online photo' (2.1.3), includes the photo options menu feature. Among these action items, when 'save to mobile' is invoked from the 'photo list' page, 'photo thumbs' page, or 'online photo' page, it causes the selected photo image (previously downloaded from the server) to be saved in the mobile album on the mobile phone. The 'added to mobile' page (2.1.7) is brought up in this case to show the photo being saved and to give an indication that saving is done.
When 'email photo' action is invoked, the 'share as email' page comes up (2.1.5). This page shows the photo(s) selected for emailing and prompts the user for the email address. In this implementation, a number of recently-used email addresses are provided. Incidentally, 'email' is simply a transport mechanism which is presently used to send photos from camera phones. Other transport mechanisms may be developed and employed for this application. Then, when the photo is emailed from the mobile phone to the selected e-mail address, a message pops up indicating that the email has been sent or, if not, that an error occurred. For example, a transmission will fail if the user is not authorized to upload photos to the selected e-mail. An error message of this kind is a product of the upload security scheme in the Yahoo! Photos application program.
When the 'screen saver' action is invoked, the selected photo will be used to populate the screen when the phone is idle, standing by, or starting up. The 'screen saver' option is associated with screen saver page (2.1.4) which shows the selected photo and requires the user to select 'OK' or 'cancel' to add this photo to the screen saver photo roster. A message pops up to indicate the status of the photo download.
Going back to the mobile album is possible with the photo options menu via the 'home' page, using the 'home' option as discussed above. Another way for getting to the mobile album or any other previous page is with the "back" action using the 'back' button, as will be later explained. Also, as mentioned above, when the Yahoo! Photos application is invoked from the landing/menu page, the 'home' page (2.0) presents the 'mobile album' as one of the selection items. Accordingly, the mobile album can be directly accessed via the 'home' page.
The mobile album screen flow, shown in Figure 5B, starts with the 'home' page (2.0) and selection of the mobile album brings up the 'mobile photo ' list page (3.1.1). This page presents two action menus, 'open' and 'action.' Thus, selection of any of the listed photos can be followed by selecting 'open' or 'action.' As before, when 'open' is selected the photo is shown on the screen in the 'photo thumbs' page (3.1.2). When 'actions' is selected, a mobile photo action menu is provided. This menu includes action items such as 'slide show,' 'move,' 'delete photo,' 'delete all' (photos), 'thumbnails,' 'history,' and 'home.'
Except for the photos being local (at the mobile album), the thumbnails feature, associated with the 'photo thumbs' page (3.1.2), works as described above with reference to the online album. A photo selected on the mobile 'photo thumbs' page can be enlarged as shown in the next page, the 'mobile photo' page (3.1.3). The menu for the 'photo thumbs' and 'mobile photo' pages includes a subset of the aforementioned mobile photo action menu.
When the slide show is invoked from such a menu the 'mobile slide show' page comes up (3.3). While this feature is active, the slide show will scroll through the mobile album photos, showing each photo for a certain period. The slide show will go on until the user selects 'stop' on the bottom of the page. If the user selects 'actions' a slide show menu gives the user the options of 'pause,' 'show,' 'normal,' and 'fast.' The 'pause' option is selected for pausing the slide show; 'slow' will slow down the slide show, 'speed' will speed up the slide show, and 'normal' will bring it to normal speed. (Figure 5C, parts (i) and (ii), describes setting up favorites for the mobile album slideshow; part (i) describes the process in the mobile device, and part (ii) describes the process originating at the PC).
As further shown in Figure 5B, the 'move' page comes up (3.2.1) when the 'move' action (referred to also as 'rearrange ' action) is selected from any one of the three pages (3.1.1, 3.1.2 and 3.1.3). In this page, the program displays a group of photos (thumbnails) and the user can rearrange the photos using the 5-point navigation key, as well as choose to drop a photo or save it (Figure 5D shows flow diagrams for photos view, share and save). When the 'delete' or 'delete all' actions are selected, the user has the option of deleting or canceling the delete action (as shown in pages 3.2.5 and 3.2.4). The 'delete' page shows the photo selected for deletion to allow the user to change their mind. When all the photos are deleted, or when the mobile album is empty to begin with, the 'mobile album empty' page is displayed (3.1.4). It allows the user to select the home page or select the answer to any one of the queries, such as "where are my photos?" and "what is the mobile album?." Selection of the latter will bring up the 'about' page (3.1.4.1), and in this page pressing 'OK' provides user access to the online album(s). Selection of the former brings up the 'restore album' page 3.1.4.2. The "restore" function is explained in more detail below.
Note that, when the user signs in, the server associates the user's identification with his historical record so that the application program can record (backup) the photo in the server each time the user saves a photo to the mobile album. This historical record serves as a backup that allows the user to restore his album if the Yahoo! Photos program is erased, for any reason, from the mobile phone memory and the user then reloads this program. This history feature is useful to reduce the navigation for restoring the mobile album since the server maintains this information in the user's client account.
It is important to note that although the history feature is described in the context of the Yahoo! Photos program, it is useful in any mobile device application where backup is desired. Thus, although this feature is implemented for the Yahoo! Photos application, it can be implemented more generically for other applications.
In the Yahoo! Photos context, every photo from the user's online album that is saved to the mobile album is 'remembered' by the server. Preferably, since the page traversal path is not predictive the history is recorded accurately and fully. This is made possible with the association of the user's Yahoo! ID to a user's historical record on the server that records all photos saved by the user to the mobile album. Moreover, since each mobile phone device is distinct, and a user may have more than one device, each device can in principle have its own distinct historical record. However, it can be arranged when the user first establishes or later updates his account that the user's Yahoo! ID is associated with a plurality of mobile phones and, upon signing in, the user can have access to his historical record from any one of these mobile phones. Thus, in a situation where the Yahoo! Photos program is deleted somehow or photos in the mobile album are erased for some reason the historical record provides a mobile album backup for restoring that album.
To that end, when the user reloads the application, it will query the user as to whether the user wishes to restore any of the mobile album photos. That is, when the user selects the query "where are my photos?" (in page 3.1.4) the 'restore album' page is displayed (3.1.4.2). As with the previous page (3.1.4), this page allows the user to go to the 'home' page (2.0) and, this time via 'OK', it allows the user to go to the next mobile 'restore album' page (3.1.4.2.1) for a historical photo download list (of photos previously downloaded to the mobile phone).
Figure 5E illustrates in more detail the flow of restoring the mobile album from the server backup. Specifically, after traversing the 'home' and 'mobile album empty' pages (2.0 and 3.1.4), the user lends on the 'restore album' page (3.1.4.2). On selecting the 'OK' option, if the user is logged in the Yahoo! Photos server responds with the download history list of photos (steps 33, 35). This response prompts the mobile device to bring up the 'restore album' page (3.1.4.2.1) with the download history list of, say, 20 last photos that were added to the mobile album. From this historical list, the photos can be picked (see, e.g., checkmarks) and then the selected photos can be restored to the mobile album using the save/cancel menu options. The selected photos are then downloaded from the server in a batch process (step 37). The mobile album is then available for user access via 'mobile album' page (3.1.1).
Note that the pages shown in Figures 5A-5E and discussed herein are exemplary rather than exhaustive, and they do not necessarily include all possible pages (or user interaction cards) that a photo application such as Yahoo! Photos presents. Moreover, the reference designations (call-out numbers) typically refer to the pages themselves rather than any portion of their content. Where applicable, similar pages appear in different figures with the same call-out numbers, e.g., home page 2.0, although their respective contents can vary slightly.
As to navigating through the pages on the mobile phone, the pages can be traversed forward as described above and they can be traversed backwards using the "back button" feature. Figure 6 provides a simplified diagram to illustrate the "back button" feature. As can be seen, the "back a level" mode allows hierarchical backwards sequence traversal one level each time the 'back' button is touch activated or clicked (hereafter "clicked"). The "back in sequence" mode allows sequential backwards one page each time the 'back' button is pressed. For example, in back a level mode, back a level takes the application from a photo page (e.g., 6) one level up to the list of photos page (3); and from there one more level up to the list of albums page (2) and one more level up to the home page (1). As can be further seen in this example, the back in sequence mode functions to take the application from the current photo page (6) to the former photo page (5), rather than up one level (3), when the back button is touched. Additional activations of the back button will traverse through all the pages in reverse sequence.
It makes no difference if the "back button" feature is used while in the online album or mobile album part of the application. The principles apply equally well to both situations. Either way, the steps (pages traversed) are remembered, and they can be recorded server side, locally, or both on the server side and locally.
Notably, while the "back button" feature provides backwards traversal through pages as described above the navigation feature as described in more detail below provides up-down traversal within these pages, particularly photo pages. For the type of navigation which involves up-down traversal within the aforementioned pages the relevant and effective method involves collapsing and expanding and following the hierarchy presented in these pages.
Because mobile devices typically have limited display size and an awkward navigation mechanism, this type of navigation pattern improves the user interface in the context of mobile application. Moreover, with this type of navigation there is room left for an action menu or action icons that are context specific. Therefore, this directory navigation feature addresses the challenge of navigating a directory tree while simultaneously providing multiple context sensitive action choices for a selected item. To that end, the directories are structured as well as presented in a tree-like hierarchical format. For example, in mobile photos application such as the client Yahoo! Photos, the directory is the mobile albums. In other possible implementations, the directory points to the mobile albums. Either way, the directory is structured as a tree-like hierarchy. In the hierarchical tree-shaped directory each item is a node. In the context of the client Yahoo
Iphotos application, a node is, an item in the mobile albums list. In this context, the directory navigation employs node collapsing and expansion. For each node, the state of either expanded or collapsed is remembered so that when the very same node is clicked, the right action can be taken accordingly. Clicking on the node functions as a toggle between the collapsed and expanded states.
The following example of collapsing and expansion will make it clearer. When the directory (hierarchical tree-shaped directory of nodes) is displayed it essentially take the following exemplary form:
+ aphotos + animals + my garden + my kids
Clicking 'aphotos' album expands that node to provide the a list of items in that node. Figure 7 is a screen shot of a mobile album showing a list of photos along with action icons (at the bottom of the screen). The list of photos includes, for example: - aphotos alex.jpg alhambra.jpg derrick&Kevin.jpg greece.jpg more + animals + my garden + my kids Clicking 'aphotos' album again collapses that node back to: + aphotos + animals + my garden + my kids Then, as further shown, when an item within a directory tree is chosen, action icons are graphically presented. These icons are provided for users to take actions specific to the selected item. For example, the first icon on the left allows the user to bring up the selected photo. Also, if the number of icons exceeds the space limit of the screen the left/right arrows allow the user to scroll left or right to reveal additional icons of action choices. The number of action icons is determined by the nature of the item selected. Preferably, only actions that apply to the item are made available. This, of course, saves space on the screen. Thus, in view of the above, the navigation scheme improves user interface.
IMPLEMENTATION DETAILS
Additional implementation details associated with the foregoing description are provided below. These implementation details include an initial list of devices, soft key mapping, labels, global elements and screen flows tables for the online albums and mobile albums. These details are described in the following pages.
POSSIBLE MOBILE DEVICES
The visual and interaction design as described herein should accommodate various types of mobile devices, including, for example, those listed in the table below.
VENDOR MODEL USABLE PIXEL DIMENSIONS Audiovox 8450 128 112 Samsung A660 128 x 146 (without Soft key) 128 x 131 (with Soft key: 15) Sanyo RL2000 (7200) 120 x 112 (include soft key) Sanyo RL2500 (5400) 132 (W) x 160 (H) including Soft key Sanyo 5500 132(w) x 160(h) including Soft key Sony Ericsson T608 128 x 114 pixels Toshiba 9950 261 x 240 Hitachi SH-P300 120wx l30h LG 5350 120x96 Samsung A500 128 x 146 (without Soft key) 128x131 (with Soft key:15) Samsung N400 128 x 114 (without Soft key) 128x102 (with Soft key:12) Samsung A600 128 x 146 (without Soft key) 128 x 131 (with Soft key: 15) Samsung VGA1000 (A620) 128 x 146 (without Soft key) 128 x 131 (with Soft key:15 ) Sanyo 4900 120 x 112 includes Soft key Sanyo 5300 132x160 (includes soft key) Sanyo 8100 128 x 120 (with soft key) 120 x 112 (without Soft key)
SOFT KEY MAPPING
For the purpose of this invention, the following keys are available on the mobile devices: Up; Down; Left; Right; Select OK; Left Soft key; Right Soft key; and Back. If a device does not have an obvious select key, it is assumed that the MIDP (mobile information device profile) implementation will automatically provide a select option at one of the soft keys or in one of the soft key menus.
KEY MAPPING
Up Scrolls the cursor up, or selects the previous item in a list.
Down Scrolls the cursor down, or selects the next item in a list.
Left Scrolls the cursor left if possible.
Right Scrolls the cursor right if possible.
Select LINK OR BUTTON: Go to appropriate screen EXCLUSIVE LIST (Radio buttons): Selects the radio button. MULTIPLE LIST (Checkboxes): Checks and un-checks the checkboxes. TEXTBOX: Takes the user to the text editor TEXT STRING: Does nothing
Two Soft keys Soft key functionality varies greatly among devices. The ordering and positioning of options can't be controlled with any degree of accuracy; the order shown indicates only the relative importance of the options. In the examples presented herein, options are assigned a type (BACK, EXIT, ITEM) The following layout is preferred: Item 1 : primary soft key Item 2: If no others are present, secondary soft key should have item 2 as its label. If additional items are available they should be listed in priority order in the menu, which is accessed via the secondary soft key. Primary soft key should have the same function as the 'Enter'/'OK' key
Back 'Back' button links back to previous screen. Does NOT link one level up in the navigation tree, unless that is the previous screen. Does not link back to confirmation or error popups. When technical constraints exist, data previously entered into fields may not be shown when user navigates back to a page. However, actual implementations may differ based on the technical constraints.
Default In general, the first item on a page is pre-selected (default item) unless the user Selection has performed some action, like viewing or renaming an image.
Misc. keys If arrow buttons on the side of the phone are available they should scroll down an entire page in a list or thumbnail screen. Image names should appear bold/strong when displayed on an instructional screen, e.g. 2.1.4. Normal text should be used for lists of images. In this document any underlined item is a link. Actual presentation of links, whether underlined or other, is determined by the device.
SOFT KEY & MENU LABELS
In a representative implementation, labels that may appear on a soft key are restricted to 7 characters. Menu-only items are restricted to 14 characters. COMMON LABELS
OK Performs the default action for a screen or for a selected item. Moves the user forward in a task, (e.g., opens an album or photo.)
Cancel Used in addition to "Back" when an action was initiated and can be cancelled. Cancel usually performs same action as back, but is displayed to increase user confidence that the action was cancelled.
Edit When possible, "Edit" links to a textbox editing screen.
Open Opens a folder, message, file, etc. Should not be used for links not associated with files, folders, etc.
Back "Back" label should be used only for the Back function described above. If possible, Back should always map only to the device back button.
Home Links to the home screen of the MIDlet.
GLOBAL ELEMENTS
CONFIRMATION POPUP One type of global elements, presented as "Confirm Popup" screens, are used for displaying a confirmation to the user. The confirmation popup screens contain simple text such as "Done" or "Saved", and they disappears automatically after a short time.
IN PROGRESS SCREEN
The "in progress" screen informs the user that the application is waiting for a response from the server or is processing a request. Each device has a default screen with text and a moving graphic, and, alternatively, it is replaced with a Yahoo! Canvas screen.
SCREEN FLOWS: ONLINE ALBUMS
As described above, the online album pages are made available to the user in forward and backwards traversal; each page having default selection items associated with it. The forward traversal starts, of course, with the home page (2.0). The following tables outline for each page separately the default selection items available in that page for screen flows.
Figure imgf000025_0001
Figure imgf000025_0002
Figure imgf000026_0001
2.1.1 Photos Thumbs
Default One thumbnail is always selected. Selection is indicated by 2 pixel black border. Selection When scrolling to a page either (1) or (4) is selected. When returning from a list view, full-screen view, or action screen the last selected image is selected.
Actions Label Function Pref. Type i Priority Location Open Opens 2.1.3 Online Photo ! Primary TEM NOTE: pressing 1,2,3, or j Soft key, 4 opens the photo j OK Button currently in that position. '' Add to j Saves image to mobile Menu ITEM 2 Mobile ■ album and opens 2.1.7 Album 1 Added to Mobile , Screen ; Links to 2.1.4 Save as Menu ITEM" 3 Saver I Screensaver Email 1 Links to 2.1.5 Share as Menu ITEM 3 Photo j Email Photo ! Links to 2.1.2 Photo List Menu SCREEN 1 List Online Links to 2.1 My Online Menu SCREEN 2 Albums ! Albums Home 1 Links to 2.6 J2ME Client Menu SCREEN 3 Home Back i Previous screen Back BACK 1 button
Up Arrow When (3) or (4) is selected, jumps up to (1) or (2). When (1) or (2), moves up one row.
Down When (1) or (2) is selected, jumps down to (3) or (4).
Arrow When (3) or (4), moves down one row.
Left Arrow Cycle through all thumbs on the screen, (4)-(l) then to the row above. Rows are added one at a time, so the top row shifts down when a new row is loaded.
Right Cycle through all thumbs on the screen, (l)-(4) then to the row below. Rows are added Arrow one at a time, so the bottom row shifts up when a new row is loaded.
Comments List loops back to beginning when user reaches last image. When looping to the beginning, the full screen refreshes with 2 rows of images. Each photo is surrounded by 2 pixels of white space. The selected photo has a 2 pixel black border. 2.1.2 Photo List
Default One item is always selected. Selection When returning from a thumbnail view, full-screen view, or action screen the last selected image is selected. After deleting, the image in the spot that contained the deleted image is selected.
Actions Label Function Pref. Type ' Priority Location Open Opens 2.1.3 Online Primary ITEM 1 Photo Soft key, OK Button Add to Saves image to Menu ITEM ' 2 " " " Mobile mobile album Album Screen Links to 2.1.4 Save Menu ITEM 3 Saver as Screensaver Email Links to 2.1.5 Share Menu ITEM 3 Photo as Email Thumbnails 1 Links to 2.1.1 Photo Menu SCREEN 1 Thumbs Online Links to 2.1 My Menu SCREEN "2 Albums Online Albums Home Links to 2.0 J2ME Menu SCREEN "3 " Client Home Back Previous screen Back "BACK' " 1
Up Arrow Jumps to previous item in list. If top item is selected, does nothing.
Down Jumps to next item in list. If last item is selected, does nothing. Arrow
Left Arrow
Right Arrow
Comments File extensions are displayed. Items are displayed in order specified by the Yahoo! Photos system. User cannot rename, delete, or move photos.
2.1.3 Online. Photo Default Selection Actions Label Function Pref. Type Priority Location Done Links to 2.1.1 or 2.1.2 Primary SREEN Pi Softkey Add to i Saves image to mobile Menu ϊ iTEM Ϊ 2 " Mobile ; album Album Screen Links to 2.1.4 Save as ; Menu ITEM ! 3 . Saver Screensaver Email Links to 2.1.5 Share as Menu ITEM ' 3 Photo_ Email Online ; Links to 2.1 My , Menu SCREEN Albums Online Albums j Home ! Links to 2.0 J2 E μ^nu SCREEN j 3 j Client Home ! Back : Previous screen j Back BACK f 1 Up Arrow Down Arrow Left Arrow Jumps to previous image in gallery- Right Arrow Jumps to next image in gallery. Comments Image should be as large as possible on any particular screen.
Figure imgf000029_0001
2.1.5 Share as Email Default Text entry field Selection Actions 1 Label Function Pref. Type Priority Location | Send Send. Sends email to Secondary ITEM 1 recipients and user Soft key with link to image 1 on web. Confirmation pops up for a moment, then user is returned to 2.1.1, 2.1.2, or 2.1.3. If email address was not formed correctly an error appears. ' Edit/Pick/OK Opens textbox for . Primary 1 editing, toggles state ■ Soft key, of checkbox, or OK Button 1 sends. Back Previous screen • Back BACK 1__ __ , Up Arrow - Down - Arrow Left Arrow - Right - Arrow Comments
Figure imgf000030_0001
SCREEN FLOWS: MOBILE ALBUM
AS with the online album, the mobile album pages are made available to the user in forward and backwards traversal; each page having default selection items associated with it. Here again, the forward traversal starts, of course, with the home page (2.0). The following tables outline for each page separately the default selection items available in that page for screen flows.
3.1.1 Mobi e Photo List
Figure imgf000031_0001
3.1.2 Mobile Photo Thumbs
Default One thumbnail is always selected. Selection is indicated by 2 pixel Selection border. When returning from a list view, full-screen view, or action screen the last selected image is selected. After deleting, the image in the spot that contained the deleted image is selected. After Moving, the last moved image is selected.
Actions Label i Function Pref. Type Priorit Location Open Opens 3.1.3 Mobile Primary ""ITEM"" 1 Photo Softkey, NOTE: pressing OK i 1,2,3, or 4 opens the Button ; photo currently in that position. Slideshow Links to 3.3 Mobile Menu ITEM 2 Slideshow, starting : show with current photo Move ' Links to 3.2.1 Move Menu ITEM 4 Delete Links to 3.2.4 Delete Menu ITEM 4 Photo List Links to 3.1.1 Menu SCREEN 1 Mobile- Photo List Home : Links to 2.0 J2ME Menu SCREEN 2 : Client Home Back __ Previous screen Back BACK _ _ 1
Up Arrow When (3) or (4) is selected, jumps up to (1) or (2). When (1) or (2), moves up one row.
Down When (1) or (2) is selected, jumps down to (3) or (4). Arrow When (3) or (4), moves down one row.
Left Arrow Cycle through all thumbs on the screen, (4)-(l) then to the row above. Rows are added one at a time, so the top row shifts down when a new row is loaded.
Right Cycle through all thumbs on the screen, (l)-(4) then to the row below. Arrow Rows are added one at a time, so the bottom row shifts up when a new row is loaded.
Comments List loops back to beginning when user reaches last image. When looping to the beginning, the full screen refreshes all 4 images. When an image is deleted all other images move to fill the empty space Each photo is surrounded by 2 pixels of white space. The selected photo has a 2 pixel border. 3.1.3 Mobile Photo Default - Selection Actions ; Label Function Pref. Type 1 Priority , ' Location j ι < Done Album. Links to most ; Primary ' ITEM ! 1 recent view of album Soft key, ■ , ' - 3.1.1 or 3.1.2 - with . OK ' ! most recently viewed j Button j i 1 image selected. ! i j ι Slideshow Links to 3.3 Mobile ' Menu j ITEM 2 Slideshow, starting [ show with current ! . photo ' Move Links to 3.2.1 Move Menu ITEM 4 Delete Links to 3.2.4 Delete Menu ITEM 4 Home Links to 2.0 J2ME ; Menu ' SCREEN 2 Client Home Back Previous screen ; Back ' BACK 1 ι Up Arrow - Down - Arrow Left Arrow Jumps to previous image in gallery. When first image is reached, loops to end. Right Jumps to next image in gallery. When last image is reached, loops to Arrow beginning. Comments Image should be as large as possible on any particular screen .
Figure imgf000033_0001
Figure imgf000034_0001
Figure imgf000034_0002
3.1.4.2.1 Restore Mobile Album Default Selection Actions i Label Function Pref. Type ! Priority Location Pick Toggles state of Primary ITEM ' 1 checkbox Soft key, OK Button Save Downloads all Secondary SCREEN , 1 selected images to Soft key Mobile Album Back Previous screen Back BACK 1 Up Arrow Jumps to previous item in list. If top item is selected, does nothing. Down Jumps to next item in list. If last item is selected, does nothing. Arrow Left Arrow May toggle state of checkbox. Right May toggle state of checkbox. Arrow Comments This screen lists a close approximation of the items downloaded to a particular phone using a particular account. When the user has selected the photos he wishes to restore and presses "Save" all the images are downloaded to the mobile album. If the Mobile Album already has photos in it, restored photos are added at the bottom of the list.
Figure imgf000035_0001
Figure imgf000036_0002
Figure imgf000036_0003
Figure imgf000036_0001
Figure imgf000037_0001
Figure imgf000037_0002
Although the present invention has been described in accordance with the embodiments shown, variations to the embodiments would be apparent to those skilled in the art and those variations would be within the scope and spirit of the present invention. Accordingly, it is in tended that the specification and embodiments shown be considered exemplary only, with a true scope of the invention being indicated by the following claims and equivalents.

Claims

WHAT IS CLAIMED IS:
1. A method for managing navigation in mobile devices, comprising: providing user interface in a mobile device; constructing a directory as a tree-shaped hierarchy of nodes; providing the directory such that any node on the directory is selectable by a user via the user interface, whereby navigation can flow up-down through the directory; associating a state and one or more action items with each node; saving the state of each node, the state being an expanded or collapsed condition of the node, wherein if the state of a particular node is expanded additional nodes at a lower level of the hierarchy are presented to the user, otherwise if the state is collapsed only that particular node is presented and the other nodes are hidden; and for any node selected by the user providing in the user interface its associated one or more action items.
A method as in claim 1, wherein the directory is a mobile album.
3. A method as in claim 2, wherein the nodes in the tree-shaped hierarchy include a root node and any number of child nodes, and wherein any node that is childless is a leaf node which in the mobile album is a photo.
4. A method as in claim 1, wherein for any node that is selected by the user, the one or more action items associated with that node are action choices provided in the user interface either as icons or as menu items.
5. A method as in claim 1, wherein for any node selectable by the user during the up- down navigation the number of action items associated with such node is determined by its nature, there being provided only action items that apply to such node.
6. A method as in claim 5, further comprising providing overflow indicators when the number of these action items exceeds a maximum number of action items that fit in the user interface, wherein the overflow indicators enable the user to scroll back a forth through all these action items.
7. A method as in claim 1, wherein, initially, a visible part of the directory provided to the user includes a top level of the tree-shaped hierarchy of nodes in a collapsed state, but as selected ones of these nodes are toggled they are expanded and more nodes, at a lower level of the hierarchy, are made visible and when toggled again these higher-level nodes are again collapsed.
8. The method of claim 1, wherein the mobile device is a wireless device.
9. A computer readable medium embodying a computer program with program code for managing navigation in mobile devices, comprising: program code for providing user interface in a mobile device; program code for constructing a directory as a tree-shaped hierarchy of nodes; program code for providing the directory such that any node on the directory is selectable by a user via the user interface, whereby navigation can flow up-down through the directory; program code for associating a state and one or more action items with each node; saving the state of each node, the state being an expanded or collapsed condition of the node, wherein if the state of a particular node is expanded additional nodes at a lower level of the hierarchy are presented to the user, otherwise if the state is collapsed only that particular node is presented and the other nodes are hidden; and program code for providing in the user interface for any node selected by the user its associated one or more action items.
10. A computer readable medium as in claim 9, wherein the directory is a mobile album.
11. A computer readable medium as in claim 10, wherein the nodes in the tree-shaped hierarchy include a root node and any number of child nodes, and wherein any node that is childless is a leaf node which in the mobile album is a photo.
12. A computer readable medium as in claim 9, wherein for any node that is selected by the user, the one or more action items associated with that node are action choices provided in the user interface either as icons or as menu items.
13. A computer readable medium as in claim 9, wherein for any node selectable by the user during the up-down navigation the number of action items associated with such node is determined by its nature, there being provided only action items that apply to such node.
14. A computer readable medium as in claim 13, further comprising program code for providing overflow indicators when the number of these action items exceeds a maximum number of action items that fit in the user interface, wherein the overflow indicators enable the user to scroll back a forth through all these action items.
15. A computer readable medium as in claim 9, wherein, initially, a visible part of the directory provided to the user includes a top level of the tree-shaped hierarchy of nodes in a collapsed state, but as selected ones of these nodes are toggled they are expanded and more nodes, at a lower level of the hierarchy, are made visible and when toggled again these higher-level nodes are again collapsed.
16. The computer readable medium of claim 9, wherein the mobile device is a wireless device.
17. A system for providing management of navigation in a mobile device, comprising: a processor; a screen for user interface; and a memory embodying a client-side program with program code for causing the processor to perform steps, including: providing the user interface; constructing a directory as a tree-shaped hierarchy of nodes; providing the directory such that any node on the directory is selectable by a user via the user interface, whereby navigation can flow up-down through the directory; associating a state and one or more action items with each node; saving in the memory the state of each node, the state being an expanded or collapsed condition of the node, wherein if the state of a particular node is expanded additional nodes at a lower level of the hierarchy are presented to the user, otherwise if the state is collapsed only that particular node is presented and the other nodes are hidden; and for any node selected by the user providing in the user interface its associated one or more action items.
18. A system as in claim 17, wherein the directory is a mobile album.
19. A system as in claim 18, wherein the nodes in the tree-shaped hierarchy include a root node and any number of child nodes, and wherein any node that is childless is a leaf node which in the mobile album is a photo.
20. A system as in claim 17, wherein for any node that is selected by the user, the one or more action items associated with that node are action choices provided in the user interface either as icons or as menu items.
21. A system as in claim 17, wherein for any node selectable by the user during the up- down navigation the number of action items associated with such node is determined by its nature, there being provided only action items that apply to such node.
22. A system as in claim 21, wherein the client-side program has further program code for causing the processor to perform the further step of providing overflow indicators when the number of these action items exceeds a maximum number of action items that fit in the user interface, wherein the overflow indicators enable the user to scroll back a forth through all these action items.
23. A system as in claim 17, wherein, initially, a visible part of the directory provided to the user includes a top level of the tree-shaped hierarchy of nodes in a collapsed state, but as selected ones of these nodes are toggled they are expanded and more nodes, at a lower level of the hierarchy, are made visible and when toggled again these higher-level nodes are again collapsed.
24. The system of claim 17, wherein the mobile device is a wireless device.
25. The system of claim 17, wherein the mobile device is a wireless camera phone.
PCT/US2004/037718 2003-11-10 2004-11-10 Navigation pattern on a directory tree WO2005048077A2 (en)

Applications Claiming Priority (10)

Application Number Priority Date Filing Date Title
US51885703P 2003-11-10 2003-11-10
US51889803P 2003-11-10 2003-11-10
US51885803P 2003-11-10 2003-11-10
US51889703P 2003-11-10 2003-11-10
US60/518,897 2003-11-10
US60/518,857 2003-11-10
US60/518,898 2003-11-10
US60/518,858 2003-11-10
US10/959,917 2004-10-05
US10/959,917 US7343568B2 (en) 2003-11-10 2004-10-05 Navigation pattern on a directory tree

Publications (2)

Publication Number Publication Date
WO2005048077A2 true WO2005048077A2 (en) 2005-05-26
WO2005048077A3 WO2005048077A3 (en) 2006-06-29

Family

ID=34557821

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2004/037718 WO2005048077A2 (en) 2003-11-10 2004-11-10 Navigation pattern on a directory tree

Country Status (2)

Country Link
US (1) US7343568B2 (en)
WO (1) WO2005048077A2 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7343568B2 (en) 2003-11-10 2008-03-11 Yahoo! Inc. Navigation pattern on a directory tree
US7797529B2 (en) 2003-11-10 2010-09-14 Yahoo! Inc. Upload security scheme
US7840646B2 (en) 2003-10-08 2010-11-23 Yahoo! Inc. Learned upload time estimate module

Families Citing this family (95)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6671757B1 (en) 2000-01-26 2003-12-30 Fusionone, Inc. Data transfer and synchronization system
US7505762B2 (en) * 2004-02-27 2009-03-17 Fusionone, Inc. Wireless telephone data backup system
US8620286B2 (en) 2004-02-27 2013-12-31 Synchronoss Technologies, Inc. Method and system for promoting and transferring licensed content and applications
US8156074B1 (en) 2000-01-26 2012-04-10 Synchronoss Technologies, Inc. Data transfer and synchronization system
US7895334B1 (en) 2000-07-19 2011-02-22 Fusionone, Inc. Remote access communication architecture apparatus and method
US8073954B1 (en) 2000-07-19 2011-12-06 Synchronoss Technologies, Inc. Method and apparatus for a secure remote access system
US7818435B1 (en) 2000-12-14 2010-10-19 Fusionone, Inc. Reverse proxy mechanism for retrieving electronic content associated with a local network
US8615566B1 (en) 2001-03-23 2013-12-24 Synchronoss Technologies, Inc. Apparatus and method for operational support of remote network systems
JP4178544B2 (en) * 2002-08-20 2008-11-12 カシオ計算機株式会社 DATA COMMUNICATION DEVICE, DATA COMMUNICATION SYSTEM, MOVIE DOCUMENT DISPLAY METHOD, AND MOVIE DOCUMENT DISPLAY PROGRAM
WO2005010715A2 (en) 2003-07-21 2005-02-03 Fusionone, Inc. Device message management system
US7584225B2 (en) * 2003-11-10 2009-09-01 Yahoo! Inc. Backup and restore mirror database memory items in the historical record backup associated with the client application in a mobile device connected to a communion network
US20050102638A1 (en) * 2003-11-10 2005-05-12 Jiang Zhaowei C. Navigate, click and drag images in mobile applications
US8286203B2 (en) 2003-12-19 2012-10-09 At&T Intellectual Property I, L.P. System and method for enhanced hot key delivery
EP1759521B1 (en) 2004-05-12 2016-06-29 Synchronoss Technologies, Inc. Advanced contact identification system
US9542076B1 (en) 2004-05-12 2017-01-10 Synchronoss Technologies, Inc. System for and method of updating a personal profile
US8127229B2 (en) * 2004-08-31 2012-02-28 Access Co., Ltd. Controlling focus, and movement of the focus, between focus items in a multi-frame document
US8402384B2 (en) * 2004-11-09 2013-03-19 Research In Motion Limited Dynamic bar oriented user interface
US7984388B2 (en) * 2004-12-10 2011-07-19 International Business Machines Corporation System and method for partially collapsing a hierarchical structure for information navigation
KR20060133389A (en) * 2005-06-20 2006-12-26 엘지전자 주식회사 Method and apparatus for processing data of mobile terminal
US20070045961A1 (en) * 2005-08-31 2007-03-01 Morris Robert P Method and system providing for navigation of a multi-resource user interface
US7676394B2 (en) 2005-09-14 2010-03-09 Jumptap, Inc. Dynamic bidding and expected value
US10038756B2 (en) 2005-09-14 2018-07-31 Millenial Media LLC Managing sponsored content based on device characteristics
US8532633B2 (en) 2005-09-14 2013-09-10 Jumptap, Inc. System for targeting advertising content to a plurality of mobile communication facilities
US8688671B2 (en) * 2005-09-14 2014-04-01 Millennial Media Managing sponsored content based on geographic region
US10592930B2 (en) 2005-09-14 2020-03-17 Millenial Media, LLC Syndication of a behavioral profile using a monetization platform
US10585942B2 (en) * 2005-09-14 2020-03-10 Millennial Media Llc Presentation of search results to mobile devices based on viewing history
US20110313853A1 (en) 2005-09-14 2011-12-22 Jorey Ramer System for targeting advertising content to a plurality of mobile communication facilities
US9703892B2 (en) 2005-09-14 2017-07-11 Millennial Media Llc Predictive text completion for a mobile communication facility
US10911894B2 (en) 2005-09-14 2021-02-02 Verizon Media Inc. Use of dynamic content generation parameters based on previous performance of those parameters
US7945642B1 (en) * 2005-10-06 2011-05-17 Sprint Spectrum L.P. Method and system for providing software to a machine
US9573067B2 (en) * 2005-10-14 2017-02-21 Microsoft Technology Licensing, Llc Mass storage in gaming handhelds
US8402503B2 (en) 2006-02-08 2013-03-19 At& T Intellectual Property I, L.P. Interactive program manager and methods for presenting program content
TW200732927A (en) * 2006-02-23 2007-09-01 Accfast Technology Corp Design method and apparatus for user interface and recording media for storing descriptive program thereof
US8564544B2 (en) * 2006-09-06 2013-10-22 Apple Inc. Touch screen device, method, and graphical user interface for customizing display of content category icons
US8106856B2 (en) 2006-09-06 2012-01-31 Apple Inc. Portable electronic device for photo management
US20080086703A1 (en) * 2006-10-06 2008-04-10 Microsoft Corporation Preview expansion of list items
JP2010525621A (en) * 2007-02-09 2010-07-22 モバイル・コンプリート・インコーポレイテッド Interactive recording of virtual devices
KR100978833B1 (en) * 2007-02-26 2010-08-30 삼성전자주식회사 Apparatus and method of implementing user interface for group communication
WO2008131948A1 (en) * 2007-05-01 2008-11-06 Nokia Corporation Navigation of a directory structure
US20080295030A1 (en) * 2007-05-22 2008-11-27 Honeywell International Inc. User interface for special purpose controller
US20080294274A1 (en) * 2007-05-22 2008-11-27 Honeywell International Inc. Special purpose controller interface with breadcrumb navigation support
DE602007013628D1 (en) * 2007-07-13 2011-05-12 Ericsson Telefon Ab L M ROUTING A CALL OF A FIXED TELEPHONE NUMBER OF A UMA PARTICIPANT IN A TELECOMMUNICATIONS NETWORK
ATE495622T1 (en) * 2007-07-27 2011-01-15 Research In Motion Ltd DEVICE AND METHOD FOR COORDINATION OF WIRELESS SYSTEMS
US7975262B2 (en) * 2007-08-16 2011-07-05 Microsoft Corporation Error tracing with context history
US7739272B1 (en) 2007-09-18 2010-06-15 Google Inc. Searching for user interface objects
KR101328958B1 (en) * 2007-10-19 2013-11-13 엘지전자 주식회사 Mobile terminal and mehod of uploading data therein
KR101455983B1 (en) * 2007-10-19 2014-11-03 엘지전자 주식회사 Mobile terminal and mehod of displaying information therein
US20090113333A1 (en) * 2007-10-26 2009-04-30 Palm, Inc. Extendable Toolbar for Navigation and Execution of Operational Functions
US8181111B1 (en) 2007-12-31 2012-05-15 Synchronoss Technologies, Inc. System and method for providing social context to digital activity
US8572033B2 (en) 2008-03-20 2013-10-29 Microsoft Corporation Computing environment configuration
US7912927B2 (en) * 2008-03-26 2011-03-22 Microsoft Corporation Wait for ready state
US20090248737A1 (en) * 2008-03-27 2009-10-01 Microsoft Corporation Computing environment representation
US7957718B2 (en) * 2008-05-22 2011-06-07 Wmode Inc. Method and apparatus for telecommunication expense management
US8490021B2 (en) * 2008-06-20 2013-07-16 Microsoft Corporation User interface for navigating large scale hierarchical namespaces
US9582292B2 (en) * 2008-10-07 2017-02-28 Microsoft Technology Licensing, Llc. Merged tree-view UI objects
US9442945B2 (en) * 2008-10-14 2016-09-13 Hewlett-Packard Development Company, L.P. File system manager using tagging organization
US8065361B2 (en) 2009-02-27 2011-11-22 Research In Motion Limited Apparatus and methods using a data hub server with servers to source and access informational content
CN101989209A (en) * 2009-08-05 2011-03-23 鸿富锦精密工业(深圳)有限公司 Method for starting user operation interface in electronic device
WO2011037558A1 (en) 2009-09-22 2011-03-31 Apple Inc. Device, method, and graphical user interface for manipulating user interface objects
US8780069B2 (en) 2009-09-25 2014-07-15 Apple Inc. Device, method, and graphical user interface for manipulating user interface objects
US8255006B1 (en) 2009-11-10 2012-08-28 Fusionone, Inc. Event dependent notification system and method
US8698762B2 (en) 2010-01-06 2014-04-15 Apple Inc. Device, method, and graphical user interface for navigating and displaying content in context
US20110179383A1 (en) * 2010-01-18 2011-07-21 Robert Paul Morris Methods, systems, and computer program products for automatically selecting objects in a plurality of objects
US20110179364A1 (en) * 2010-01-18 2011-07-21 Robert Paul Morris Methods, systems, and computer program products for automating operations on a plurality of objects
US20110179390A1 (en) * 2010-01-18 2011-07-21 Robert Paul Morris Methods, systems, and computer program products for traversing nodes in path on a display device
US9232043B2 (en) * 2010-03-03 2016-01-05 Lg Electronics Inc. Mobile terminal and control method thereof
US20120032885A1 (en) * 2010-08-03 2012-02-09 Nokia Corporation Reversing actions
US8943428B2 (en) 2010-11-01 2015-01-27 Synchronoss Technologies, Inc. System for and method of field mapping
USD665400S1 (en) * 2011-02-25 2012-08-14 Microsoft Corporation Display screen with graphical user interface
JP5776313B2 (en) * 2011-04-28 2015-09-09 株式会社リコー Conference equipment
US8935237B2 (en) 2011-09-09 2015-01-13 Facebook, Inc. Presenting search results in hierarchical form
US10289267B2 (en) 2011-09-09 2019-05-14 Facebook, Inc. Platform for third-party supplied calls-to-action
US20130067417A1 (en) * 2011-09-09 2013-03-14 Rasmus Mathias Andersson Presenting Hierarchical Information Items
JP2013097535A (en) * 2011-10-31 2013-05-20 Toshiba Corp Electronic apparatus and display control method
US9912713B1 (en) 2012-12-17 2018-03-06 MiMedia LLC Systems and methods for providing dynamically updated image sets for applications
US9298758B1 (en) 2013-03-13 2016-03-29 MiMedia, Inc. Systems and methods providing media-to-media connection
US9465521B1 (en) 2013-03-13 2016-10-11 MiMedia, Inc. Event based media interface
US9183232B1 (en) 2013-03-15 2015-11-10 MiMedia, Inc. Systems and methods for organizing content using content organization rules and robust content information
US10257301B1 (en) 2013-03-15 2019-04-09 MiMedia, Inc. Systems and methods providing a drive interface for content delivery
US9405442B1 (en) 2013-09-04 2016-08-02 Ca, Inc. List control with zoom operation
US9442944B2 (en) 2013-11-12 2016-09-13 Dropbox, Inc. Content item purging
US11449542B2 (en) 2015-02-11 2022-09-20 AVAST Software s.r.o. Systems and methods for identifying unwanted photos stored on a device
US20170357672A1 (en) 2016-06-12 2017-12-14 Apple Inc. Relating digital assets using notable moments
AU2017100670C4 (en) 2016-06-12 2019-11-21 Apple Inc. User interfaces for retrieving contextually relevant media content
DK201670608A1 (en) 2016-06-12 2018-01-02 Apple Inc User interfaces for retrieving contextually relevant media content
US10496734B2 (en) 2016-09-26 2019-12-03 Microsoft Technology Licensing, Llc Intelligent navigation via a transient user interface control
US10725720B2 (en) 2016-09-26 2020-07-28 Microsoft Technology Licensing, Llc Navigation in augmented reality via a transient user interface control
DK180171B1 (en) 2018-05-07 2020-07-14 Apple Inc USER INTERFACES FOR SHARING CONTEXTUALLY RELEVANT MEDIA CONTENT
US11243996B2 (en) 2018-05-07 2022-02-08 Apple Inc. Digital asset search user interface
US11086935B2 (en) 2018-05-07 2021-08-10 Apple Inc. Smart updates from historical database changes
US10803135B2 (en) 2018-09-11 2020-10-13 Apple Inc. Techniques for disambiguating clustered occurrence identifiers
US10846343B2 (en) 2018-09-11 2020-11-24 Apple Inc. Techniques for disambiguating clustered location identifiers
JP7330734B2 (en) * 2019-04-04 2023-08-22 キヤノン株式会社 Image processing device and its control method and program
DK201970535A1 (en) 2019-05-06 2020-12-21 Apple Inc Media browsing user interface with intelligently selected representative media items
DK181076B1 (en) 2020-02-14 2022-11-25 Apple Inc USER INTERFACES FOR TRAINING CONTENT

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030142953A1 (en) * 2002-01-31 2003-07-31 Fuji Photo Film Co., Ltd. Album generation program and apparatus and file display apparatus
US20040023686A1 (en) * 2002-07-31 2004-02-05 Lavaflow, Llp Method of and apparatus for outputting a picture file

Family Cites Families (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5806072A (en) * 1991-12-20 1998-09-08 Olympus Optical Co., Ltd. Electronic imaging apparatus having hierarchical image data storage structure for computer-compatible image data management
US5481710A (en) * 1992-09-16 1996-01-02 International Business Machines Corporation Method of and system for providing application programs with an undo/redo function
US5574906A (en) * 1994-10-24 1996-11-12 International Business Machines Corporation System and method for reducing storage requirement in backup subsystems utilizing segmented compression and differencing
CA2220345C (en) * 1995-05-08 2001-09-04 Compuserve Incorporated System for electronic messaging via wireless devices
US6021433A (en) * 1996-01-26 2000-02-01 Wireless Internet, Inc. System and method for transmission of data
US6167426A (en) * 1996-11-15 2000-12-26 Wireless Internet, Inc. Contact alerts for unconnected users
US6832084B1 (en) * 1998-01-07 2004-12-14 Microsoft Corporation Wireless database environment
US6721713B1 (en) * 1999-05-27 2004-04-13 Andersen Consulting Llp Business alliance identification in a web architecture framework
WO2001017227A1 (en) * 1999-08-31 2001-03-08 Shutterfly, Inc. Distributing images to multiple recipients
US6657702B1 (en) * 1999-08-31 2003-12-02 Shutterfly, Inc. Facilitating photographic print re-ordering
US6671735B1 (en) * 2000-01-28 2003-12-30 Qualcomm Incorporated System and method for using an IP address as a wireless unit identifier
US20020087546A1 (en) * 2000-01-31 2002-07-04 Michael Slater Apparatus, methods, and systems for digital photo management
US6560618B1 (en) * 2000-03-22 2003-05-06 International Business Machines Corporation On-demand generation, packaging, and delivery of archive files
US6741855B1 (en) * 2000-03-24 2004-05-25 Sun Microsystems, Inc. Method and apparatus for remotely managing data via a mobile device
GB2360671B (en) * 2000-03-25 2003-09-03 Hewlett Packard Co Providing location data about a mobile entity
EP1354263A2 (en) * 2000-07-07 2003-10-22 Openwave Systems Inc. Graphical user interface features of a browser in a hand-held wireless communication device
US7117519B1 (en) * 2000-07-26 2006-10-03 Fotomedia Technologies Llc Method and system for selecting actions to be taken by a server when uploading images
US6453361B1 (en) * 2000-10-27 2002-09-17 Ipac Acquisition Subsidiary I, Llc Meta-application architecture for integrating photo-service websites
FI20002823A (en) * 2000-12-21 2002-06-22 Nokia Corp Data Transmission
EP1220507A1 (en) * 2000-12-22 2002-07-03 Sun Microsystems, Inc. Creating web content in a client and server system
US7197531B2 (en) * 2000-12-29 2007-03-27 Fotomedia Technologies, Llc Meta-application architecture for integrating photo-service websites for browser-enabled devices
US20020156921A1 (en) * 2001-04-19 2002-10-24 International Business Machines Corporation Automatic backup of wireless mobile device data onto gateway server while device is idle
US7433710B2 (en) * 2001-04-20 2008-10-07 Lightsurf Technologies, Inc. System and methodology for automated provisioning of new user accounts
US20020198991A1 (en) * 2001-06-21 2002-12-26 International Business Machines Corporation Intelligent caching and network management based on location and resource anticipation
US7469153B2 (en) * 2001-08-30 2008-12-23 Nokia Corporation Mobile telecommunications device browser
JP4749628B2 (en) * 2001-09-07 2011-08-17 パナソニック株式会社 Album creating apparatus, album creating method, and album creating program
KR20030049105A (en) * 2001-12-14 2003-06-25 에스케이텔레텍주식회사 Method for storing backup data on the network and cellular-phone implementing the same
JP4067322B2 (en) * 2002-03-19 2008-03-26 富士フイルム株式会社 Image management server, image print server, and image service system
JP4662679B2 (en) * 2002-09-06 2011-03-30 ソニー株式会社 Information processing apparatus and method, information processing system, and program
US20040155909A1 (en) * 2003-02-07 2004-08-12 Sun Microsystems, Inc. Scroll tray mechanism for cellular telephone
TWM241908U (en) * 2003-09-09 2004-08-21 High Tech Comp Corp Rotatable image catching device
US7840646B2 (en) * 2003-10-08 2010-11-23 Yahoo! Inc. Learned upload time estimate module
US20050102638A1 (en) * 2003-11-10 2005-05-12 Jiang Zhaowei C. Navigate, click and drag images in mobile applications
US7343568B2 (en) 2003-11-10 2008-03-11 Yahoo! Inc. Navigation pattern on a directory tree
US7797529B2 (en) * 2003-11-10 2010-09-14 Yahoo! Inc. Upload security scheme

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030142953A1 (en) * 2002-01-31 2003-07-31 Fuji Photo Film Co., Ltd. Album generation program and apparatus and file display apparatus
US20040023686A1 (en) * 2002-07-31 2004-02-05 Lavaflow, Llp Method of and apparatus for outputting a picture file

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7840646B2 (en) 2003-10-08 2010-11-23 Yahoo! Inc. Learned upload time estimate module
US7343568B2 (en) 2003-11-10 2008-03-11 Yahoo! Inc. Navigation pattern on a directory tree
US7797529B2 (en) 2003-11-10 2010-09-14 Yahoo! Inc. Upload security scheme

Also Published As

Publication number Publication date
WO2005048077A3 (en) 2006-06-29
US20050102635A1 (en) 2005-05-12
US7343568B2 (en) 2008-03-11

Similar Documents

Publication Publication Date Title
US7343568B2 (en) Navigation pattern on a directory tree
US7584225B2 (en) Backup and restore mirror database memory items in the historical record backup associated with the client application in a mobile device connected to a communion network
US20050197141A1 (en) &#39;Back&#39; button schema in mobile applications
US9021249B2 (en) Upload security scheme
US20050102638A1 (en) Navigate, click and drag images in mobile applications
US7113981B2 (en) Cellular telephone download locker
US8959330B2 (en) Dynamic improvement of internet browser appearance and connectivity
US8438287B2 (en) System and method for management of mobile device
KR101253792B1 (en) A method of automatically building a customised software application for a specific type of wireless computing device
US8611873B2 (en) Advanced contact identification system
KR101026604B1 (en) Method and system for a hosted mobile management service architecture
US20090164564A1 (en) System and methods for mobilizing web content
US20060248447A1 (en) Indicating loading status of information from a computer network
BRPI0514070A2 (en) method for navigating information on the mobile terminal, method for providing and accessing menu functions on the electronic device display, graphical user interface, computer program product, and method for providing a graphical user interface for the terminal device
US20090213228A1 (en) Method For Specifying Image Handling For Images On A Portable Device
EP2353281A1 (en) Method of operating a mobile electronic device and mobile electronic device
JP2007299276A (en) Information supply method, server and mobile communication terminal
US20080263140A1 (en) Network System, Server, Client, Program and Web Browsing Function Enabling Method
Jiang et al. Back'button schema in mobile applications
Jiang et al. Back'button in mobile applications
WO2006001926A1 (en) `back`button schema in mobile applications
JP4102917B2 (en) Information terminal device and download processing program thereof
JP2003143319A (en) Apparatus and method for creating template
WO2009036301A1 (en) System and method for mobilizing web content
JP4794750B2 (en) Data display device and data display method

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase