(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2007/0282908 A1
`Van der Meulen et al.
`(43) Pub. Date:
`Dec. 6, 2007
`
`US 20070282908A1
`
`(54) TECHNIQUES FOR MANAGING MEDIA
`CONTENT
`
`(75) Inventors:
`
`Pieter S. Van der Meulen, Los
`Altos, CA (US); Matt W.
`Crowley, Los Altos, CA (US)
`
`Correspondence Address:
`KACVINSKY LLC
`CFO INTELLEVATE
`P.O. BOX S2OSO
`MINNEAPOLIS, MN 55402
`
`(73) Assignee:
`
`PALM, INC.
`
`(21) Appl. No.:
`
`y x- - -
`
`11A47533
`
`9
`
`(22) Filed:
`
`Jun. 5, 2006
`
`Publication Classification
`
`(51) Int. Cl.
`(2006.01)
`G06F 7/00
`(52) U.S. Cl. .................................................... 707/104.1
`(57)
`ABSTRACT
`Various media management techniques are described. A
`mobile computing device may comprise a metadata infor
`mation database to store metadata, a media object database
`to store media objects, and a media content manager to
`couple to the metadata information database and the media
`object database. The media content manager may comprise
`a metadata manager to retrieve and associate metadata from
`the metadata information database with different media
`objects. The media content manager may further comprise a
`media object classifier to classify the media objects into
`hierarchical categories based on the metadata. The media
`content manager may still further comprise an album gen
`erator to generate a media album representing a hierarchical
`category. Other embodiments may be described and
`claimed.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Text
`Module
`14&
`
`
`
`
`
`Audio
`Module
`146
`
`Processing
`System
`148
`
`N
`
`Beamed
`Media
`Objects
`
`Operating System 130
`
`Metadata
`Manager
`104
`
`Media
`Object
`Classifier
`106
`
`Media
`Album
`Generator
`108
`
`Media Content Manager 102
`
`Map
`Generator
`112
`
`Metadata
`information
`Database
`122
`
`
`
`Abunt
`Dane
`124
`
`User
`Preference
`Database
`126
`
`Map
`Information
`Database
`128
`
`MemoryWeb Ex. 2019
`Apple v. MemoryWeb – IPR2022-00032
`
`

`

`Patent Application Publication
`
`Dec. 6, 2007 Sheet 1 of 6
`
`US 2007/0282908A1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`opny
`
`?Inpow
`
`994
`
`MemoryWeb Ex. 2019
`Apple v. MemoryWeb – IPR2022-00032
`
`

`

`Patent Application Publication
`
`Dec. 6, 2007 Sheet 2 of 6
`
`US 2007/0282908A1
`
`
`
`200
`
`receive multiple media objects
`202
`
`associate metadata with each media object
`204
`
`organize the media objects into hierarchical categories
`based on the metadata associated with each media object
`206
`
`display an image to represent each media object in a
`media album
`ar
`AV
`
`FIG. 2
`
`MemoryWeb Ex. 2019
`Apple v. MemoryWeb – IPR2022-00032
`
`

`

`Patent Application Publication
`
`US 2007/0282908A1
`
`
`
`g?ç Kjouaw
`
`CIS
`
`
`
`
`
`MemoryWeb Ex. 2019
`Apple v. MemoryWeb – IPR2022-00032
`
`

`

`Patent Application Publication
`
`Dec. 6, 2007 Sheet 4 of 6
`
`US 2007/0282908A1
`
`
`
`
`
`7 "SOI
`
`MemoryWeb Ex. 2019
`Apple v. MemoryWeb – IPR2022-00032
`
`

`

`Patent Application Publication
`
`Dec. 6, 2007 Sheet 5 of 6
`
`US 2007/0282908A1
`
`
`
`N
`s
`
`o
`
`S.
`
`:
`
`MemoryWeb Ex. 2019
`Apple v. MemoryWeb – IPR2022-00032
`
`

`

`Patent Application Publication
`
`Dec. 6, 2007 Sheet 6 of 6
`
`US 2007/0282908A1
`
`|
`
`
`
`
`
`MemoryWeb Ex. 2019
`Apple v. MemoryWeb – IPR2022-00032
`
`

`

`US 2007/0282908 A1
`
`Dec. 6, 2007
`
`TECHNIQUES FOR MANAGING MEDIA
`CONTENT
`
`BACKGROUND
`0001. A mobile computing device such as a smartphone
`may incorporate various components into a single integrated
`device having a smaller form factor to enhance mobility and
`convenience. For example, the mobile computing device
`may have one or more radio transceivers and antennas for
`Voice and/or data communications, one or more processors
`and memory units for computing operations, and various
`input/output devices, such as a digital camera, digital video
`camera, microphone, speaker, display, touch screen display,
`thumb board, keypad, and so forth. In addition, a mobile
`computing device may store and execute a growing number
`of system and application programs to Support and utilize
`the various hardware components.
`0002. As a result of such enhanced capabilities, mobile
`computing devices are becoming increasingly used to create,
`store, and reproduce media content, including pictures,
`images, graphics, video files, audio files, and so forth.
`Furthermore, additional media content may be transferred to
`the mobile computing device from other devices using its
`communications capabilities. Memory resources are also
`decreasing in cost and therefore are readily available to store
`the media content. Consequently, mobile computing devices
`may be used to store increasing Volumes of media content.
`A user may have some difficulty, however, organizing and
`navigating the ever increasing volumes of media content.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0003 FIG. 1 illustrates one embodiment of a media
`content module.
`0004 FIG. 2 illustrates one embodiment of a logic dia
`gram.
`0005 FIG. 3 illustrates one embodiment of a radio sys
`tem.
`0006 FIG. 4 illustrates one embodiment of a processing
`system.
`0007 FIG. 5 illustrates one embodiment of a mobile
`computing device.
`0008 FIG. 6 illustrates one embodiment of a communi
`cations system.
`
`DETAILED DESCRIPTION
`
`0009 Various embodiments may be directed to media
`management techniques in general. More particularly, vari
`ous embodiments may be directed to media management
`techniques Suitable for mobile computing devices. As
`mobile computing devices are used to store increasing
`Volumes of media objects, it may become increasingly
`difficult to manage the media objects. For example, a user
`may need to manually organize related media objects. A user
`may then need to traverse a large number of media objects,
`Sometimes using nested menu sets, in order to locate a
`desired media object. To potentially solve these and other
`problems, various embodiments may use media manage
`ment techniques to automatically organize media objects to
`facilitate visual inspection and navigation of the media
`objects. This may allow a user to quickly traverse the
`volumes of media objects in order to locate a desired media
`object.
`
`0010. In one embodiment, for example, certain informa
`tion in the form of metadata may be associated with various
`media objects. The metadata may be used to automatically
`group a set of media objects into predefined categories. The
`groupings may be arranged in a hierarchical manner based
`on a set of heuristics and/or user preferences. In some cases,
`an electronic map may be generated with a visual indicator
`of a location associated with a given set of media objects. In
`this manner, a user may realize improved navigation through
`Volumes of media objects when attempting to access a
`particular media object or group of media objects. Accord
`ingly, a user may directly benefit from enhanced products or
`services.
`0011. In one embodiment, for example, a mobile com
`puting device may include a media content module to
`perform media management operations. The media content
`module may include a media content manager coupled to a
`media object database and a metadata information database.
`The media object database may store various types of media
`objects. Such as audio files, video files, image files, and so
`forth. The metadata information database may store various
`types of metadata information, Such as a time, date, location,
`user identifier, device identifier, media identifier, location
`identifier, and other types of information relevant or desir
`able for a given media object. The media content manager
`may include a metadata manager to retrieve metadata from
`the metadata information database, and associate the
`retrieved metadata with different media objects. A media
`object classifier may be used to classify the media objects
`into hierarchical categories based on the metadata. An album
`generator may be used to generate a media album repre
`senting each hierarchical category, or a media album col
`lection representing a set of media albums. A map generator
`may be used to generate an electronic map with an image or
`metadata information representing a media object, media
`album, media album collection, or hierarchical category.
`Other embodiments are described and claimed.
`0012 Various embodiments may comprise one or more
`elements. An element may comprise any structure arranged
`to perform certain operations. Each element may be imple
`mented as hardware, Software, or any combination thereof,
`as desired for a given set of design parameters or perfor
`mance constraints. Although an embodiment may be
`described with a limited number of elements in a certain
`topology by way of example, the embodiment may include
`more or less elements in alternate topologies as desired for
`a given implementation. It is worthy to note that any
`reference to “one embodiment' or “an embodiment’ means
`that a particular feature, structure, or characteristic described
`in connection with the embodiment is included in at least
`one embodiment. The appearances of the phrase “in one
`embodiment in various places in the specification are not
`necessarily all referring to the same embodiment.
`0013. It is worthy to note that some embodiments may be
`described using the expression “coupled' and “connected
`along with their derivatives. These terms are not intended as
`synonyms for each other. For example, Some embodiments
`may be described using the terms “connected” and/or
`“coupled to indicate that two or more elements are in direct
`physical or electrical contact with each other. The term
`“coupled, however, may also mean that two or more
`elements are not in direct contact with each other, but yet
`still co-operate or interact with each other. With respect to
`software elements, for example, the term “coupled may
`
`MemoryWeb Ex. 2019
`Apple v. MemoryWeb – IPR2022-00032
`
`

`

`US 2007/0282908 A1
`
`Dec. 6, 2007
`
`refer to interfaces, message interfaces, application program
`interfaces (API), exchanging messages, and so forth.
`0014 FIG. 1 illustrates one embodiment of a media
`content module. FIG. 1 illustrates a media content module
`100. Media content module 100 may perform media man
`agement operations to manage media content for a device.
`Media content module 100 may be implemented with any
`number of electronic systems, devices, or components. In
`one embodiment, for example, media content module 100
`may be implemented with a mobile computing device. A
`mobile computing device may comprise any portable device
`having processing capabilities and communication capabili
`ties. In some cases, a mobile computing device may have a
`form factor Suitable for Support and operation using a single
`human hand. An example of a mobile computing device
`suitable for use with media content module 100 may be
`described in more detail later with reference to FIG. 5,
`although the embodiments are not necessarily limited to this
`example.
`0015. As shown in FIG. 1, mobile content module 100
`may comprise a media content manager 102. Media content
`manager 102 may perform various media management
`operations for media information, media content, media
`objects, media files, and so forth. Some examples of media
`management operations may include organizing media con
`tent, navigating media content, displaying media content,
`communicating media content, reproducing media content,
`collecting media content, reproducing media content, modi
`fying media content, and so forth.
`0016. As further shown in FIG. 1, media content manager
`102 may be coupled to various databases, including a media
`object database 120, a metadata information database 122,
`an album database 124, a user preference database 126, and
`a map information database 128. Media content manager
`102 may also be coupled to an operating system 130 that
`includes, among other things, a user interface 132. Media
`content manager 102 and operating system 130 may be
`coupled to a display 160. Furthermore, the above elements
`may all be coupled to various elements typically included in
`a mobile computing device. Such as a media source node
`140, a video module 142, a text module 144, an audio
`module 146, a processing system 148, a radio system 150,
`and so forth. It may be appreciated that media content
`module 100 may be implemented with more or less elements
`than shown in FIG. 1 and still fall within the scope of the
`embodiments. The embodiments are not limited in this
`COInteXt.
`0017. In various embodiments, media object database
`120 may store various media objects. A media object may
`generally refer to a conceptual entity approximately corre
`sponding to a contiguous block computer memory of a
`specific size at a specific location. Examples of media
`objects may include various discrete or defined sets of media
`information, Such as text information, alphanumeric infor
`mation, audio information, graphics information, image
`information, animation information, video information,
`symbol information, icon information, and so forth. The
`media information may sometimes be stored as files, such as
`audio files, video files, image files, and so forth. The
`embodiments are not limited in this context.
`0018. In various embodiments, some media objects may
`be received from media source node 140. Media source node
`140 may comprise any hardware or software element
`capable of creating, storing and/or delivering media objects
`
`to media content manager 102. Examples of media Source
`node 140 may include a digital versatile disc (DVD) device,
`a video home system (VHS) device, a digital VHS device,
`a personal video recorder, a computer, a gaming console, a
`Compact Disc (CD) player, computer-readable or machine
`readable memory, a digital camera, camcorder, video Sur
`veillance system, teleconferencing system, telephone sys
`tem, medical and measuring instruments, scanner system,
`copier system, television system, digital television system,
`set top boxes, personal video records, server systems, com
`puter systems, personal computer systems, digital audio
`devices (e.g., MP3 players), and so forth. It is worthy to note
`that media source node 140 may be internal or external to a
`mobile computing device using media content manager 102.
`depending upon a given implementation. When media
`Source node 140 is external to a mobile computing device,
`the media objects may be communicated between media
`Source node 140 and the mobile computing device over any
`suitable wired or wireless communications media. The
`embodiments are not limited in this context.
`0019. In various embodiments, metadata information
`database 122 may store various types of metadata informa
`tion. Metadata information may generally refer to structure
`encoded data that describe characteristics of information
`bearing entities to aid in the identification, discovery, assess
`ment and management of described entities. In one embodi
`ment, for example, metadata information database 122 may
`store metadata information that may be descriptive of or
`provide context for, any media objects stored be media
`object database 120. Examples of metadata information
`relevant to media objects may include, but are not limited to,
`date information, time information, user identification infor
`mation, device identification information, location informa
`tion, event information, copyright information, content
`information, context information, owner information, legal
`rights information, media format information, and so forth.
`The metadata information may be gathered at the time of
`capture. Such as when a media object is created (e.g., taking
`a picture) or received (e.g., from a media broadcasting
`device). The metadata information may also be gathered
`before or after a media object has been created or received.
`The embodiments are not limited in this context.
`0020. In various embodiments, album database 126 may
`store various media albums and media album collections. A
`media album may comprise a set of media objects from a
`defined category. A media album collection may comprise a
`set of media albums. Each media album and media album
`collection may be automatically generated and populated in
`accordance with a given set of rules and/or heuristics. Each
`media object may have a visual content indicator to allow a
`user to visually identify the content for a media object.
`Examples of visual content indicators may comprise an
`image, symbol, character, icon, text, number, or other
`desired information to convey information about the media
`object. A media album may display the visual content
`indicators as a common group, thereby allowing a user to
`quickly scan through the media objects for a given media
`album. A media album collection provides similar informa
`tion regarding multiple media albums by decreasing the size
`of the visual content indicators to accommodate the avail
`able space of a given display, such as display 160, for
`example.
`0021. A media album may represent a set of media
`objects within the same defined category. The categories
`
`MemoryWeb Ex. 2019
`Apple v. MemoryWeb – IPR2022-00032
`
`

`

`US 2007/0282908 A1
`
`Dec. 6, 2007
`
`may include categories defined by a user or default catego
`ries. A user may define any number of categories. For
`example, assume a user defines a category named “cruise
`vacation.” All media objects such as digital pictures classi
`fied within the “cruise vacation' category may be organized
`or stored within the same media album. In some cases, the
`categories may be related. In one embodiment, for example,
`the categories may be hierarchical in nature, where certain
`categories are Subordinate to other categories. For example,
`more specific media albums named “2005 cruise vacation
`and “2006 cruise vacation” may be subordinate to, or
`Sub-categories of the more general media album named
`“cruise vacation.” Furthermore, the more general media
`album named "cruise vacation' may also comprise a media
`album collection since it includes multiple media albums
`“2005 cruise vacation and “2006 cruise vacation.
`0022. In some embodiments, album database 124 may
`store the actual media objects for a given media album or
`media album collection. Alternatively, album database 124
`may store a data structure or data format for a given album
`or media album collection, while the actual media objects
`remain as part of media object database 120. The embodi
`ments are not limited in this context.
`0023. In various embodiments, user preference database
`126 may store various user profiles. A user profile may
`include a set of user preferences to define the type of
`metadata information to be associated with a given media
`object. For example, a user may define various categories,
`category names, a name format for a media object, a name
`format for a media album or media album collection, a
`minimum media album size or media album collection size,
`a maximum media album size or media album collection
`size, a default map, a default city, a default map provider,
`certain metadata fields to include with a given media object
`or class of media objects, and other desired user defined
`information. The embodiments are not limited in this con
`text.
`0024. In various embodiments, map information database
`128 may store digital map information. Digital map infor
`mation used by a mapping application to create an electronic
`map. The digital map information may be collected at the
`data-gathering Survey level using, for example, a Geo
`graphic Information System (GIS). The digital map infor
`mation may be provided by any number of map data
`providers, such as a NAVTEQTM Corporation, Tele Atlas
`NV, and others. The digital map information may also be
`provided by various online mapping databases, such as
`electronic maps provided by GoogleTM Inc. or Yahoo!TM
`Inc., for example.
`0025. In one embodiment, for example, the digital map
`information may include map address information and loca
`tion information. The map address information may refer to
`any information used to uniquely identify a place. Such as a
`commercial building, personal residence, point of interest,
`and so forth. Examples of map address information may
`include country, state, Zip code, county, Street name, Street
`number, and so forth. The location information may refer to
`any information used to uniquely identify a physical location
`for an address, such as latitude coordinates, longitude coor
`dinates, altitude or elevation information, and so forth. The
`map address information and location information may have
`any desired level of granularity and detail as desired for a
`given implementation.
`
`0026. In various embodiments, media content manager
`102 may include a metadata manager 104. Metadata man
`ager 104 may be arranged to retrieve metadata information
`from metadata information database 122. Metadata manager
`104 may associate the retrieved metadata information with
`different media objects stored by media object database 120
`and/or album database 124. Metadata manager 104 may
`register or populate user data fields associated with each
`media object with certain metadata information. The user
`data fields may comprise predefined user data fields, user
`defined user data fields, user data fields automatically gen
`erated by metadata manager 104 using a set of rules or
`heuristics, or other types of user data fields. The type of
`metadata to associate with a particular media object may be
`indicated by a set of user preferences stored with a user
`profile in user preference database 126. Metadata manager
`104 may store the media objects and associated metadata
`using any desired data structure or data format in media
`object database 120.
`0027. In one embodiment, for example, metadata man
`ager 104 may automatically register metadata information
`into predefined user data fields typically associated with a
`given media standard or format. For example, assume media
`Source node 140 comprises a digital camera used to generate
`a Joint Photographic Experts Group (JPEG) image. Meta
`data manager 104 may embed various pieces of metadata
`information directly into the JPEG image, such as a current
`date and/or time, shooting conditions (e.g. whether a flash
`was used), camera settings (e.g., shutter, aperture, focal
`length), and so forth. Metadata manager 104 may also
`associate other metadata information with a JPEG image,
`Such as an author, a title, a copyright notice, global posi
`tioning system (GPS) data, and so forth. Metadata manager
`104 may embed or associate the desired metadata with the
`JPEG image in accordance with the Exchangeable Image
`File Format (EXIF). Some EXIF field names and descrip
`tions may be provided in Table 1 as follows:
`
`Name
`
`NewSubfileType
`ImageWidth
`Image:Length
`BitsPerSample
`Compression
`PhotometricInterpretation
`Image:Description
`Make
`Model
`StripOffsets
`Orientation
`SamplesPerPixel
`RowsPerStrip
`StripByteCounts
`XResolution
`YResolution
`PlanarConfiguration
`ResolutionJnit
`TransferFunction
`Software
`DateTime
`Artist
`HostComputer
`
`WhitePoint
`Primary Chromaticities
`JPEGInterchangeFormat
`
`TABLE 1.
`
`Description
`
`Subfile type
`mage width
`mage height
`Number of bits per component
`Compression scheme
`Pixel composition
`mage title
`Manufacturer of image input equipment
`Model of image input equipment
`mage data location
`Orientation of image
`Number of components
`Number of rows per strip
`Bytes per compressed strip
`mage resolution in width direction
`mage resolution in height direction
`mage data arrangement
`Onit of X and Y resolution
`Transfer function
`Software used
`File change date and time
`Person who created the image
`The computer and/or operating
`system in use
`White point chromaticity
`Chromaticities of primaries
`Offset to JPEG SOI
`
`MemoryWeb Ex. 2019
`Apple v. MemoryWeb – IPR2022-00032
`
`

`

`US 2007/0282908 A1
`
`Dec. 6, 2007
`
`TABLE 1-continued
`
`TABLE 1-continued
`
`Name
`PEGInterchangeFormatLength
`YCbCrCoefficients
`
`YCbCrSubSampling
`YCbCrPositioning
`
`ExposureTime
`FNumber
`ExposureProgram
`SpectralSensitivity
`SOSpeed Ratings
`OECF
`Exilfversion
`DateTimeOriginal
`
`DateTimeDigitized
`
`ComponentsConfiguration
`CompressedBitsPerPixel
`ShutterSpeedValue
`ApertureValue
`Brightness Value
`ExposureBias Value
`MaxApertureValue
`SubjectDistance
`Metering Mode
`LightSource
`Flash
`FocalLength
`SubjectArea
`MakerNote
`UserComment
`SubSecTime
`SubSecTimeOriginal
`SubSecTimeDigitized
`FlashpixVersion
`ColorSpace
`PixelXDimension
`Pixel YDimension
`Related SoundFile
`interoperabilityTag
`Flash Energy
`SpatialFrequency Response
`FocalPlaneXResolution
`FocalPlaneYResolution
`FocalPlaneResolution Unit
`SubjectLocation
`ExposureIndex
`SensingMethod
`File:Source
`SceneType
`CFAPattern
`CustomRendered
`ExposureMode
`WhiteBalance
`DigitalZoom Ratio
`Focal LengthIn35 mmFilm
`SceneCaptureType
`GainControl
`Contrast
`Saturation
`Sharpness
`DeviceSetting Description
`SubjectIDistanceRange
`ImageOniqueID
`RelatedImageFile:Format
`RelatedImageWidth
`RelatedImage:Length
`GPSVersionID
`GPSLatitudeRef
`GPSLatitude
`
`Description
`
`Name
`
`Description
`
`Bytes of JPEG data
`Color space transformation
`matrix coefficients
`Subsampling ratio of Y to C
`Y and C positioning
`Pair of black and white reference values
`Copyright holder
`Exif IFD Pointer
`GPSInfo IFD Pointer
`Exposure time
`F number
`Exposure program
`Spectral sensitivity
`SO speed ratings
`Optoelectric coefficient
`Exif Version
`Date and time original image
`was generated
`Date and time image was
`made digital data
`Meaning of each component
`image compression mode
`Shutter speed
`Aperture
`Brightness
`Exposure bias
`Maximum lens aperture
`Subject distance
`Metering mode
`Light source
`Flash
`Lens focal length
`Subject area
`Manufacturer notes
`User comments
`DateTime subseconds
`DateTimeOriginal Subseconds
`DateTimeDigitized subseconds
`Supported Flashpix version
`Color space information
`Valid image width
`Valid image height
`Related audio file
`interoperability IFD Pointer
`Flash energy
`Spatial frequency response
`Focal plane X resolution
`Focal plane Y resolution
`Focal plane resolution unit
`Subject location
`Exposure index
`Sensing method
`File source
`Scene type
`CFA pattern
`Custom image processing
`Exposure mode
`White balance
`Digital Zoom ratio
`Focal length in 35 mm film
`Scene capture type
`Gain control
`Contrast
`Saturation
`Sharpness
`Device settings description
`Subject distance range
`Unique image ID
`File format of image file
`Image width
`Image height
`GPS tag version
`North or South Latitude
`Latitude
`
`PSLongitudeRef
`PSLongitude
`PSAltitudeRef
`PSAltitude
`PSTimeStamp
`PSSatellites
`PSStatus
`PSMeasureMode
`PSDOP
`PSSpeed Ref
`PSSpeed
`PSTrackRef
`PSTrack
`PSImgDirectionRef
`PSImgDirection
`PSMapIDatum
`PSDestLatitudeRef
`PSDestLatitude
`PSDestLongitudeRef
`PSDestLongitude
`PSDestBearingRef
`PSDestBearing
`PSDestDistanceRef
`PSDestDistance
`PSProcessingMethod
`PSA reanformation
`PSDateStamp
`PSDifferential
`
`East or West Longitude
`Longitude
`Altitude reference
`Altitude
`GPS time (atomic clock)
`GPS satellites used for measurement
`GPS receiver status
`GPS measurement mode
`Measurement precision
`Speed unit
`Speed of GPS receiver
`Reference for direction of movement
`Direction of movement
`Reference for direction of image
`Direction of image
`Geodetic Survey data used
`Reference for latitude of destination
`Latitude of destination
`Reference for longitude of destination
`Longitude of destination
`Reference for bearing of destination
`Bearing of destination
`Reference for distance to destination
`Distance to destination
`Name of GPS processing method
`Name of GPS area
`GPS date
`GPS differential correction
`
`It may be appreciated that the EXIF user data format in
`general and the fields provided in Table 1 in particular are
`provided by way of example only. Any number of user data
`formats and fields for metadata information may be defined
`as desired for a given implementation. The embodiments are
`not limited in this context.
`0028. In various embodiments, media content manager
`102 may include a media object classifier 106 coupled to
`metadata manager 104. Media object classifier 106 may be
`arranged to classify the media objects into categories based
`on the metadata information associated with the media
`objects. In some cases, for example, the categories may be
`arranged as hierarchical categories. Media object classifier
`106 may search media object database 120 to organize the
`stored media objects by the associated metadata. Media
`object classifier 106 may organize the media objects into
`various predefined categories, user-defined categories as
`indicated by a set of user preferences, or categories auto
`matically generated by media object classifier 106 using a
`set of rules or heuristics. In the latter case, for example,
`media object classifier may create a new category when user
`data fields for two or more media objects have common
`metadata.
`0029. By way of example, assume that a set of media
`objects have a user data field with date information such as
`a month and year. Further assume that month and year
`categories have been defined for media object classifier 106.
`Media object classifier may then search media object data
`base 120 and classify a first set of media objects having a
`user data field with a date of “January 2006 into a first
`category labeled “January 2006, a second set of media
`objects having a user data field with a date of “February
`2006’ into a second category labeled “February 2006, and
`so forth for each month of the year 2006.
`0030. In various embodiments, media content manager
`102 may include an album generator 108 coupled to media
`
`MemoryWeb Ex. 2019
`Apple v. MemoryWeb – IPR2022-00032
`
`

`

`US 2007/0282908 A1
`
`Dec. 6, 2007
`
`object classifier 106. Album generator 108 may be arranged
`to generate a media album representing a hierarchical cat
`egory. Album generator 108 may also be arranged to gen
`erate a media album collection comprising multiple media
`albums. Album generator 108 may retrieve a set of media
`album parameters used to generate one or more media
`albums or media album collections. The media album
`parameters may be retrieved from a set of user preferences
`stored with a user profile, for example. Examples of media
`album parameters include a maximum album size, minimum
`album size, priority level, media album image, media album
`identifier, and so forth. In accordance with the media album
`parameters, album generator 108 may automatically orga
`nize media objects into one or more media albums 162-1-S
`based on the hierarchical categories used by media object
`classifier 106. Furthermore, album generator 108 may auto
`matically organize multiple media albums 161-1-S into one
`or more media album collections 164-1-t. Album generator
`108 may store the media albums 162-1-S and media album
`collections 164-1-t in album database 124. It may be appre
`ciated that the media objects may be moved or copied from
`media object database 120 to album database 124, or alter
`natively, remain in media object database 120 with the
`appropriate lists, references, or pointers for each media
`album 162-1-S and media album collections 164-1-1 stored
`in album database 124. The embodiments are not limited in
`this context.
`0031. In various embodiments, media content manager
`102 may be coupled to a user interface application 132 and
`a display 160. In one embodiment, for example, user inter
`face application 132 may be implemented as a graphics user
`interface (GUI) application. User interface application 132
`may display multiple visual content indicators (e.g., thumb
`nail images) for the hierarchical categories grouped in a
`media album 162-1-S on display 160. User interface appli
`cation 312 may also display multiple media albums for the
`hierarchical categories grouped in one or more media album
`collections 164-1-t on display 160.
`0032. As previously described, each media object may be
`represented using a visual content indicator, such as an
`image, icon, symbol, or other visually descriptive indicator.
`In one embodiment, for example, the metadata for each
`media object may include a thumbnail image to assista user
`to visually recognize a content for a given media album.
`User interface application 132 may display each media
`album 162-1-S with a collection of thumbnail images rep
`resenting the underlying set of media objects that form the
`media album 162-1-S. In this manner, a user may navigate
`between media albums 162-1-S by visually searching the
`thumbnail images.
`0033. Furthermore, user interface application 1