US7860887B2 - Cross-media storage coordination - Google Patents
Cross-media storage coordination Download PDFInfo
- Publication number
- US7860887B2 US7860887B2 US11/799,039 US79903907A US7860887B2 US 7860887 B2 US7860887 B2 US 7860887B2 US 79903907 A US79903907 A US 79903907A US 7860887 B2 US7860887 B2 US 7860887B2
- Authority
- US
- United States
- Prior art keywords
- data version
- media format
- media
- format
- data
- Prior art date
- Legal status (The legal status 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 status listed.)
- Expired - Fee Related, expires
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2308—Concurrency control
- G06F16/2315—Optimistic concurrency control
- G06F16/2329—Optimistic concurrency control using versioning
-
- G—PHYSICS
- G11—INFORMATION STORAGE
- G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
- G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
- G11B27/02—Editing, e.g. varying the order of information signals recorded on, or reproduced from, record carriers
- G11B27/031—Electronic editing of digitised analogue information signals, e.g. audio or video signals
- G11B27/034—Electronic editing of digitised analogue information signals, e.g. audio or video signals on discs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
- G06F16/2272—Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2358—Change logging, detection, and notification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
- G06F16/48—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
- G06F16/487—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
- G06F16/48—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
- G06F16/489—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using time information
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9538—Presentation of query results
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/231—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/234—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs
- H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
- H04N21/234336—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements by media transcoding, e.g. video is transformed into a slideshow of still pictures or audio is converted into text
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
- H04N21/2381—Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/435—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
- H04N21/84—Generation or processing of descriptive data, e.g. content descriptors
-
- Y—GENERAL 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
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/912—Applications of a database
- Y10S707/913—Multimedia
-
- Y—GENERAL 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
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99944—Object-oriented database structure
- Y10S707/99947—Object-oriented database structure reference
Definitions
- the present application relates generally to cross-media storage coordination services, as well as various systems, processes and devices for implementing such services.
- a method for cross media storage coordination includes but is not limited to storing a first data version of specified content based on a particular media format; storing at least a second data version of related content based on a different media format; providing a cross-reference between the first data version and the at least second data version to enable coordinated management by a designated user and/or an approved device for search and possible retrieval of the first data version and/or the at least second data version; and implementing communication access by one or more parties and/or the designated user via a communication type that is correlated with the first data version and/or the at least second data version.
- a computer program product related to communication coordination includes but is not limited to a signal bearing medium bearing at least one of one or more instructions for storing a first data version of specified content based on a particular media format; one or more instructions for storing at least a second data version of related content based on a different media format; one or more instructions for providing a cross-reference between the first data version and the at least second data version to enable coordinated management by a designated user and/or an approved device for search and possible retrieval of the first data version and/or the at least second data version; and one or more instructions for implementing communication access by one or more parties and/or the designated user via a communication type that is correlated with the first data version and/or the at least second data version.
- a method for media coordination includes but is not limited to transmitting a first data version of the multimedia data based on a particular media format to a storage facility; receiving from the storage facility a conversion reference identifying the first data version, the conversion reference identifying at least a second data version of the multimedia data; receiving a cross-reference between the first data version and the at least second data version to enable coordinated user or device management of the first data version and the another data version type; and implementing communication access by one or more parties and/or the designated user via a communication type that is correlated with the first data version and/or the at least second data version.
- a computer program product includes but is not limited to a signal bearing medium bearing at least one or more instructions for transmitting a first data version of the multimedia data based on a particular media format to a storage facility; one or more instructions for receiving from the storage facility a conversion reference identifying the first data version, the conversion reference identifying at least a second data version of the multimedia data; one or more instructions for receiving a cross-reference between the first data version and the at least second data version to enable coordinated user or device management of the first data version and the another data version type; and one or more instructions for implementing communication access by one or more parties and/or the designated user via a communication type that is correlated with the first data version and/or the at least second data version.
- related systems include but are not limited to circuitry and/or programming for effecting the herein-referenced method aspects; the circuitry and/or programming can be virtually any combination of hardware, software, and/or firmware configured to effect the herein-referenced method aspects depending upon the design choices of the system designer.
- a media system for one or more types of media includes but is not limited to a processor; a memory coupled to the processor; and a media engine coupled to the processor, the media engine configured to integrate a first data version of specified content with at least a second data version of related content; the media engine including a data store configured to store the first data version of specified content based on a particular media format and the at least second data version of related content based on a different media format, a reference module configured to provide a cross-reference between the first data version and the at least second data version to enable search and possible retrieval of the first data version and/or the at least second data version, and an access module configured to enable communication access by one or more parties and/or a designated user via a communication type that is correlated via at least the cross reference with the first data version and/or the at least second data version.
- a data store configured to store the first data version of specified content based on a particular media format and the at least second data version of related content based on a different media format
- a storage system for coordinating one or more types of media includes but is not limited to a processor; a memory coupled to the processor; a transceiver coupled to the processor, the transceiver configured to generate a responsive data packet using a media type appropriate for a recipient device; and a media engine coupled to the processor, the media engine configured to integrate one or more types of media, the media engine including: a data store module configured to store one or more different format versions of a received data packet; and a conversion module coupled to the processor, the conversion module configured to convert a first data version of specified content based on a particular media format to at least a second version of related content based on a different media format, wherein the conversion module provides a conversion reference to enable coordinated management of the first data version and the at least second data version without regard to media type.
- FIG. 1 is a block diagram of an exemplary computer architecture that supports the claimed subject matter of the present application.
- FIG. 2 is a block diagram of an exemplary system that supports the claimed subject matter of the present application.
- FIGS. 3A and 3B illustrate a flow diagram of exemplary method features in accordance with various embodiments of the subject matter of the present application.
- FIGS. 3C and 3D illustrate a flow diagram of exemplary method features in accordance with additional embodiments of the subject matter of the present application.
- FIG. 4 illustrates a flow diagram of exemplary method features in accordance with further embodiments of the subject matter of the present application.
- FIG. 5 is a block diagram of another exemplary system that supports the claimed subject matter of the present application.
- FIGS. 6A and 6B illustrate a flow diagram of exemplary method features in accordance with various embodiments of the subject matter of the present application.
- FIGS. 6C and 6D illustrate a flow diagram of exemplary method features in accordance with additional embodiments of the subject matter of the present application.
- FIG. 7A and 7B illustrate a flow diagram of exemplary method features in accordance with further embodiments of the subject matter of the present application.
- FIG. 1 includes a computer 100 , including a processor 1 10 , memory 120 and one or more drives 130 .
- the drives 130 and their associated computer storage media provide storage of computer readable instructions, data structures, program modules and other data for the computer 100 .
- Drives 130 can include an operating system 140 , application programs 150 , and program modules 160 .
- Computer 100 further includes user input devices 190 through which a user may enter commands and data.
- Input devices can include an electronic digitizer, a microphone, a keyboard and pointing device, commonly referred to as a mouse, trackball or touch pad. Other input devices may include a joystick, game pad, satellite dish, scanner, or the like.
- processor 110 can be connected to processor 110 through a user input interface that is coupled to a system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB).
- Computers such as computer 100 may also include other peripheral output devices such as speakers, which may be connected through an output peripheral interface 194 or the like.
- Computer 100 may operate in a networked environment using logical connections to one or more computers, such as a remote computer connected to network interface 196
- the remote computer may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and can include many or all of the elements described above relative to computer 100 .
- Networking environments are commonplace in offices, enterprise-wide area networks (WAN), local area networks (LAN), intranets and the Internet.
- computer 100 may comprise the source machine from which data is being migrated, and the remote computer may comprise the destination machine or vice versa.
- source and destination machines need not be connected by a network 108 or any other means, but instead, data may be migrated via any media capable of being written by the source platform and read by the destination platform or platforms.
- computer 100 When used in a LAN or WLAN networking environment, computer 100 is connected to the LAN through a network interface 196 or an adapter.
- computer 100 When used in a WAN networking environment, computer 100 typically includes a modem or other means for establishing communications over the WAN, such as the Internet or network 108 . It will be appreciated that other means of establishing a communications link between the computers may be used.
- computer 100 is connected in a networking environment such that processor 110 and/or program modules 160 can perform with or as a cross-media storage system with a media engine capable of instantiating a conversion module and/or logging module in accordance with embodiments herein.
- FIG. 2 illustrated is an exemplary block diagram for an embodiment of a cross-media communication coordination system 200 .
- the illustrated media system 200 includes a processor 210 , a memory 220 , coupled to the processor 210 .
- FIG. 2 also illustrates a transceiver 230 which can be configured to send a receive data packets in different formats, and send and receive one or more data packets holding the one or more types of media.
- Transceiver 230 can be configured to interface with various modes of communication (e.g., communication links) to send and receive data packets holding one or more types of media.
- FIG. 2 also illustrates media engine 240 accessible by processor 210 and by network 108 (see FIG. 1 ).
- Such accessibility to the media engine 240 may be provided through a communication link via network 108 to a communication source 232 , as well as to one or more computing devices 234 (e.g., personal communication device, mobile device, etc.) capable of receiving a responsive type of media communication in a suitable format.
- such accessibility to the media engine 240 may include a more direct (e.g., non-network) communication link to a communication source 236 , as well as to one or more computing devices 238 capable of receiving a responsive type of media communication in a suitable format.
- the communication source 232 , 236 may also be a destination computing device for a responsive type of media communication.
- the exemplary media engine 240 may be configured to integrate, manipulate, modify, identify and/or store one or more types of media.
- FIG. 2 further illustrates exemplary components within media engine 240 .
- media engine 240 includes modules, some or all of which can be implemented as program modules 160 , as shown in FIG. 1 .
- FIG. 2 illustrates a conversion module 250 disposed within media engine 240 .
- Disposed within conversion module 250 are several modules including reversion module 260 , tagging module 262 , conferencing module 266 , alternative media module 258 and coordination module 254 .
- Coordination module further illustrates a content storage formatting module 256 disposed within coordination module 254 .
- indexing module 270 and logging module 290 is also disposed within media engine 240 .
- Indexing module 270 illustrates an organization module 280 disposed within indexing module 270 .
- Conversion module 250 can be configured to convert one or more received data packets to a standardized data format.
- a standardized data format can include a format according to an accepted standard in an industry and/or a proprietary standard data format and/or a data format that is considered a standard for particular purpose, a particular industry, and/or a particular time period.
- Conversion module 250 can be configured to convert received data packets to an SGML-based data format and/or an ASCII-based text format.
- Conversion module 250 can also be configured for converting the one or more received data packets by removing data packet envelopes around core data packets.
- Reversion module 260 can be configured to enable a user of a computing device to respond to a data packet in a predetermined media type.
- Indexing module 270 can be configured to receive one or more data packets in a standardized data format and index the data packets to enable a search of the one or more data packets in a standardized data format.
- Logging module 290 can be coupled to the processor and configured to log the one or more received data packets. In one embodiment, logging module 290 can operate on either a converted or an original media type to enable manipulation of the received one or more data packets without regard to media type of the received one or more data packets.
- the logging module 290 can also be configured as a database for storing data packets as will be appreciated by one of skill in the art with the benefit of the present disclosure.
- Organization module 280 shown disposed within indexing module 270 , can be configured to receive data packets in the standardized data format and index the one or more data packets according to one or more of content, subject matter of data packets, media type, and source of the one or more data packets destination. Like logging module 290 , organization module can also be configured as a database according to system requirements. Depending on the type of data packets received, and the necessity thereof, some data packets can be appropriate for storing while others could be temporary type data packets.
- conversion module 250 further includes a coordination module 254 .
- Coordination module 254 can be configured to convert the one or more received data packets and/or a selected subset of the one or more received data packets to enable a user of the computing device to communicate using a predetermined media type.
- coordination module 254 is configured to include a content storage formatting module 256 .
- Content storage formatting module 256 can be configured for converting received data packets and/or a selected subset of the received data packets to a specified content storage format appropriate for including in a further communication to a predetermined computing device.
- conversion module 250 includes alternative media module 258 .
- Alternative media module 258 can be configured to convert the received data packets to a standardized media type for purposes of sending selected data packets to a conference group, to a sender, a mobile device, an archive, and/or to an output device.
- alternative media module 258 is further configured for converting the received data packets from an original media type to a media type appropriate for enabling a conference with one or more media types, which could include a simple text format, a visual format, a non-English language format, and/or a voice only format.
- conversion module 250 is coupled to indexing module 270 such that indexing module 270 indexes received data packets according to the alternative media type, which can be determined via alternative media module 258 , and/or a target destination for the received data packets.
- Conversion module 250 further includes a tagging module 262 .
- Tagging module 262 can be configured to create a conversion tag to enable a recipient server to convert a responsive data packet to the original media type or to another appropriate media type.
- conversion module 250 can include a conferencing module 258 configured for enabling a conference with multiple forms of media types.
- the media types in the conference can include image data and/or voice data and/or video and/or text data
- the conferencing module can be configured to enable conferencing with parties using a plurality of media types.
- FIGS. 1-2 are provide by way of example only, and are not intended to be limiting. Furthermore, it will be understood that the various process features and system components disclosed herein may be incorporated in different embodiment combinations depending on the circumstances.
- FIGS. 3A , 3 B and 3 C and 3 D an exemplary flow diagram illustrates the operation of various aspects of a cross-media communication coordination system in accordance with different embodiments.
- block 310 provides for receiving one or more data packets via one or more modes of communication (e.g., cross-media communication coordination system 200 receiving data packets via network 108 ).
- block 3102 Depicted within block 310 is optional block 3102 , which provides for receiving the one or more data packets from one or more of a wireless communications network, an internet connection, a plain old telephone service (POTS) network, and/or a satellite network (e.g., cross-media communication coordination system 200 receiving one or more data packets via network 108 wherein network 108 is a wireless network, internet, phone service or satellite network).
- POTS plain old telephone service
- satellite network e.g., cross-media communication coordination system 200 receiving one or more data packets via network 108 wherein network 108 is a wireless network, internet, phone service or satellite network.
- the data packets can be received over many different types of communications networks and be of vastly different types of media when received at media engine 240 .
- block 3104 Depicted within block 310 is optional block 3104 , which provides for receiving the one or more data packets at a server configured to receive the one or more modes of communication (e.g., cross-media communication coordination system 200 receiving the data packets at a server such as computer system 100 configured to receive different types of media communication via network 108 ).
- the server can be a computer system 100 or other appropriately configured server that receives digital data and is able to parse the data packets into appropriate parts for later conversion, if necessary.
- Block 3106 Depicted within block 310 is optional block 3106 , which provides for receiving the one or more data packets with a content storage format, the content storage format including one or more of encoded speech, encoded images, encoded instant messages, encoded text, compressed data, and/or encoded video (e.g., cross-media communication coordination system 200 receiving the data packets as different types of media communication via network 108 as encoded speech, encoded images, encoded instant messages, encoded text, compressed data, and/or encoded video).
- Block 320 illustrates an aspect for providing a data storage format for the one or more data packets (e.g., conversion module 250 converting the data packets into a data storage format to enable storing the data packets).
- block 3202 Depicted within block 320 is optional block 3202 , which provides for converting the one or more data packets to a content storage format using a Standard Generalized Markup Language (SGML) based markup language (e.g., conversion module 250 converting received data packets to SGML).
- SGML Standard Generalized Markup Language
- the converting data packets can be to SGML to enable a reduced data format, such as a data format appropriate for smart card usage, wireless phone usage, or another hypertext format.
- block 3204 provides for converting the one or more data packets to a data storage format capable of compression for storage.
- Block 330 provides for providing an identification tag to enable manipulation of one or more selected data packets (e.g., tagging module 262 and/or logging module 290 providing an identification tag for enabling manipulation of the data packets).
- Disposed within block 330 is optional block 3302 , which provides for determining the identification tag, the identification tag identifying the original communication type and the alternative communication type (e.g., tagging module 262 determining the identification tag according to communication type, which can include an original communication type and/or the alternative communication type).
- optional block 33022 Disposed within optional block 3302 is optional block 33022 which provides for associating the identification tag with a database listing each alternative communication type to which the one or more data packets can be converted (e.g., tagging module 262 and/or logging module 290 associating the identification tag with a database within media engine 240 ).
- Block 330 further provides in optional block 3304 for identifying a content storage format to which the data packets can be converted (e.g., content storage formatting module 256 identifying a content storage format to which the data packets can be converted).
- optional block 3304 Disposed within optional block 3304 is optional block 33042 , which provides for identifying a content storage format including one or more of a encoded speech, encoded images, encoded instant messages, encoded text, compressed data, and/or encoded video (e.g., content storage formatting module determining whether a content storage format should include encoded speech, encoded images, encoded instant messages, encoded text, compressed data, and/or encoded video).
- block 340 provides for converting the one or more selected data packets from an original communication type to an alternative communication type (e.g., conversion module 250 converting the one or more selected data packets from an original media type to an alternative media type).
- block 3402 Disposed within block 340 is optional block 3402 which provides for converting the one or more selected data packets according to an instruction received from one or more of a source of the one or more data packets and/or a recipient of the one or more selected data packets (e.g., conversion module 250 converting the one or more selected data packets according to a received instruction from a source over network 108 or a recipient over network 108 ).
- block 3404 which provides for converting the one or more selected data packets from the original communication type to a communication type appropriate for a conference communication, a transfer to an internal network of a source of the one or more data packets, a transfer to a security-enabled network, and/or a transfer to a personal communication device (e.g., conversion module 250 converting the selected data packets from the original communication via conferencing module 266 to a conference communication type or conversion module 250 converting the selected data packets for purposes of a transfer to an internal network via network interface 196 , or for purposes of a transfer over network 108 and/or to a personal communication device).
- conversion module 250 converting the selected data packets from the original communication via conferencing module 266 to a conference communication type
- conversion module 250 converting the selected data packets for purposes of a transfer to an internal network via network interface 196 , or for purposes of a transfer over network 108 and/or to a personal communication device.
- optional block 34042 Disposed within optional block 3404 is optional block 34042 which provides for converting the one or more selected data packets to a communication type operating with a reduced instruction set as compared to the original communication type to enable the transfer to the personal communication device (e.g., conversion module 250 converting the selected data packets to a communication type that uses a reduced instruction set appropriate for a personal communication device).
- Block 350 provides for integrating the one or more data packets after providing the identification tag to enable responsive communication via any one of the one or more modes of communication (e.g., conversion module 250 converting the data packets and then integrating the logged and converted data packets into an outgoing communication over network 108 ).
- conversion module 250 converting the data packets and then integrating the logged and converted data packets into an outgoing communication over network 108 .
- Another possible feature depicted in block 360 provides for indexing the one or more data packets according to one or more of content and/or subject matter and/or the one or more modes of communication and/or one or more sources of media communication (e.g., indexing module 270 indexing logged data packets logged via logging module 290 according to a subject matter of the data or according the type of media communication or source of media communication).
- indexing module 270 indexing logged data packets logged via logging module 290 according to a subject matter of the data or according the type of media communication or source of media communication.
- Depicted within block 360 is optional block 3602 which provides for indexing the one or more data packets according to a predetermined user-defined characterization (e.g., indexing module 270 indexing packets previously converted in conversion module 250 and/or logged in logging module 290 according to a predetermined user-defined characterization).
- indexing can be performed according to different predetermined characterizations in accordance with system requirements and/or user requirements.
- the exemplary flow diagram of FIG. 3C continues with block 3620 , 3630 , 3640 and 3650 which provide for various different possible indexing methods which may be provided separately or in combination in no particular order.
- block 3620 provides for indexing the one or more data packets according to a predetermined characterization of a source of the one or more data packets (e.g., indexing module 270 indexing the data packets according to a predetermined characterization of a source of the data packets).
- Block 3620 is followed by block 3630 which provides for indexing the one or more data packets according to a predetermined characterization of a content of the one or more data packets (e.g., indexing module 270 indexing the data packets according to a predetermined characterization of the content within the data packets).
- Block 3640 provides for indexing the one or more data packets according to a predetermined characterization of a mode of communication of the one or more data packets (e.g., indexing module 270 indexing the data packets according to a predetermined characterization of a mode of communication of the data packets).
- the modes of communication can include Internet communication, wireless communication, radio frequency communication, satellite communication and other modes of communication.
- Block 3650 provides for indexing the one or more data packets according to a predetermined characterization of a subject matter of the one or more data packets (e.g., indexing module 270 indexing the data packets according to a predetermined characterization of subject matter of the data packets, including indexing according to topic of the data packets, metadata describing the data in the data packets, a description of the subject matter from an outside source describing the data packet subject matter and the like).
- indexing module 270 or another program module determines a file extension of data within the data packet to enable indexing. For example, indexing can determine whether the data packets contain .jpg files, .wav files, .mp3 files, .doc files, .xml files and the like.
- Block 370 provides for determining a responsive type of media communication including the original communication type and/or the alternative communication type (e.g., transceiver determining a responsive type of communication based on a received communication over network 108 ).
- Disposed within block 370 is optional block 3702 which provides for converting the one or more data packets from the data storage format to another format suitable for the alternative communication type (e.g., conversion module 250 converting the data packets from a data storage format for storing the data to a responsive type of media communication for transmittal over network 108 ).
- Block 380 provides for logging the one or more data packets (e.g., logging module 290 logging the data packets received over network 108 and/or from within computer system 100 ).
- Block 3802 Disposed within block 380 is optional block 3802 which provides for logging the one or more data packets according to a source of the one or more data packets (e.g., logging module 290 logging the data packets received over network 108 and/or from within computer 100 ). Additional possible features depicted in blocks 38022 and block 38024 are illustrated within block 3802 .
- optional block 38022 provides for providing a record including a link to the source of the one or more data packets (e.g., logging module 290 logging the data packets and providing a record of the log wherein the record includes a link, such as an internet address or internal address to a source of the data packets).
- Optional block 38024 provides for enabling the source to choose a content storage format for a future communication (e.g., sending the source of the data packets an email or other communication or accepting the data packets conditionally upon a designation of a preferred content storage format for future communication).
- FIG. 4 an exemplary flow diagram illustrates another method embodiment that includes various possible features for providing cross-media communication coordination.
- block 410 provides for receiving one or more data packets (e.g., cross-media communication system 200 receiving data packets over network 108 ).
- Block 420 provides for determining an original media type associated with the one or more data packets (e.g., transceiver 240 and/or conversion module 250 determining an original media type of the data packets).
- Block 430 provides for converting one or more selected data packets using the original media type to a specified content storage format appropriate for including in a further communication to a predetermined computing device (e.g., conversion module 250 converting the original media type to a predetermined media type for sending over network 108 according to a computing device determined to be connected to network 108 ).
- a predetermined computing device e.g., conversion module 250 converting the original media type to a predetermined media type for sending over network 108 according to a computing device determined to be connected to network 108 ).
- block 4302 Depicted within block 430 is optional block 4302 , which provides for converting the one or more selected data packets to the alternative media type for purposes of sending the one or more selected data packets to a conference group, to a sender, a mobile device, an archive, and/or to an output device (e.g., conversion module 250 converting the original media type to an alternative media type for purposes of sending selected data packets to any of a number of media formats).
- an output device e.g., conversion module 250 converting the original media type to an alternative media type for purposes of sending selected data packets to any of a number of media formats.
- indexing module 270 indexing the one or more selected data packets according to the alternative media type and/or a target destination for the one or more selected data packets.
- block 4304 provides for providing a conversion tag to enable a recipient server to convert a responsive data packet to the original media type (e.g., conversion module 250 providing a conversion tag to enable a recipient server to convert responsive data back to an original media type).
- Block 430 further depicts optional block 4305 , which provides for converting the data packets to a Standard Generalized Markup Language (SGML) based data format and/or an ASCII-based text format (e.g., conversion module 250 converting data packets to an SGML-based format or an ASCII text format).
- SGML Standard Generalized Markup Language
- ASCII-based text format e.g., conversion module 250 converting data packets to an SGML-based format or an ASCII text format.
- Block 430 further depicts optional block 4306 , which provides for converting the one more selected data packets by removing one or more data packet envelopes around each core data packet (e.g., conversion module 250 converting data packets by removing envelopes around each core of a data packet).
- Block 430 further depicts optional block 4307 , which provides for comparing the received one or more data packets to an index of data packet types to enable one or more predictive stochastic processes to operate on the data packets prior to performing a lossy conversion process, the one or more predictive stochastic processes identifying one or more media types appropriate for display and/or execution on a mobile device (e.g., media engine 240 and processor 210 operating with conversion module 250 to compare received data packets to an index determined by indexing module 270 to enable one or more predictive stochastic processes to operate on the data packet prior to performing a lossy conversion process, the one or more predictive stochastic processes identifying one or more media types appropriate for display and/or execution on a mobile device).
- a mobile device e.g., media engine 240 and processor 210 operating with conversion module 250 to compare received data packets to an index determined by indexing module 270 to enable one or more predictive stochastic processes to operate on the data packet prior to performing a lossy conversion process, the one or more predictive stochastic processes
- Block 430 also depicts optional block 4308 which provides for converting the original media type to a predetermined media type to a media type appropriate for a mobile device, a telephonic device, and/or a video device (e.g., conversion module 250 converting an original media type to a predetermined media type to media type for a mobile device, telephone, and/or video device).
- a video device e.g., conversion module 250 converting an original media type to a predetermined media type to media type for a mobile device, telephone, and/or video device.
- Block 430 further depicts optional block 4309 , which provides for enabling a conference with multiple forms of media types including image data and/or voice data to enable conferencing with parties using a plurality of media formats (e.g., media engine 240 enabling a teleconference over network 108 with multiple forms of media types via conversion module 250 including image data and/or voice data to enable conferencing with parties using a plurality of media formats).
- media engine 240 enabling a teleconference over network 108 with multiple forms of media types via conversion module 250 including image data and/or voice data to enable conferencing with parties using a plurality of media formats.
- optional block 43092 Depicted within optional block 4309 is illustrated optional block 43092 which provides for enabling the conference with the plurality of media formats including at least one of simple text format, a visual format, a non-English language format, and a voice only format (e.g., conversion module 250 enabling the conference to take place with the plurality of media formats including at least one of simple text format, a visual format, a non-English language format, and a voice only format).
- FIG. 5 illustrated is an exemplary block diagram for an embodiment of a cross-media storage coordination system 500 .
- the illustrated media system 500 includes a processor 510 and a memory 520 , coupled to the processor 510 .
- FIG. 5 also illustrates a transceiver 530 which can be configured to send a receive data packets in different formats, and send and receive one or more data packets holding the one or more types of media.
- Transceiver 530 can be configured to interface with various modes of communication (e.g., communication links) to send and receive data packets holding one or more types of media.
- FIG. 5 also illustrates media engine 540 accessible by processor 510 and by network 108 (see FIG. 1 ).
- Such accessibility to the media engine 540 may be provided through a communication link via network 108 to a communication source 532 as well as to one or more computing devices 534 via network 108 , (e.g., personal communication device, mobile device, etc.) capable of receiving a responsive type of media communication in a suitable format.
- such accessibility to the media engine 540 may include a more direct (e.g., non-network) communication link to a communication source 536 , as well as to one or more computing devices 538 capable of receiving a responsive type of media communication in a suitable format.
- the communication source 532 , 536 may also be a destination computing device for a responsive type of media communication.
- the exemplary media engine 540 may be configured to integrate, manipulate, modify, identify and/or store one or more types of media.
- FIG. 5 further illustrates exemplary components within media engine 540 .
- media engine 540 includes modules, some or all of which can be implemented as program modules 160 , as shown in FIG. 1 .
- FIG. 5 illustrates an access module 512 , a reference module 514 , a data store 516 , a search engine 518 , logging module 590 , an indexing module 570 and a conversion module 550 disposed within media engine 540 .
- Access module 512 can be configured to operate with transceiver 530 to manage access to data packets and data versions stored or received by media engine 540 and/or stored in data store 516 .
- Search engine 518 can be coupled to data store 516 to provide search capabilities to search data packets and versions of data processed by processor 510 .
- Reference module 514 can be configured to provide a cross-reference for media storage purposes.
- conversion module 550 Disposed within conversion module 550 are several modules including reversion module 560 , tagging module 562 , conferencing module 566 , alternative media module 558 and coordination module 554 .
- Coordination module illustrates a content storage formatting module 556 disposed within coordination module 554 .
- Indexing module 570 illustrates an organization module 580 disposed within indexing module 570 .
- Conversion module 550 can be configured to convert one or more received data packets to a standardized data format.
- a standardized data format can include a format according to an accepted standard in an industry and/or a proprietary standard data format and/or a data format that is considered a standard for particular purpose, a particular industry, and/or a particular time period.
- Conversion module 550 can be configured to convert received data packets to an SGML-based data format and/or an ASCII-based text format.
- Conversion module 550 can also be configured for converting the one or more received data packets by removing data packet envelopes around core data packets.
- Reversion module 560 can be configured to enable a user of a computing device to respond to a data packet in a predetermined media type.
- Indexing module 570 can be configured to receive one or more data packets in a standardized data format and index the data packets to enable a search of the one or more data packets in a standardized data format.
- Logging module 590 can be coupled to the processor and configured to log the one or more received data packets. In one embodiment, logging module 590 can operate on either a converted or an original media type to enable manipulation of the received one or more data packets without regard to media type of the received one or more data packets.
- the logging module 590 can also be configured as a database for storing data packets as will be appreciated by one of skill in the art with the benefit of the present disclosure.
- Organization module 580 shown disposed within indexing module 570 , can be configured to receive data packets in the standardized data format and index the one or more data packets according to one or more of content, subject matter of data packets, media type, and source of the one or more data packets destination. Like logging module 590 , organization module can also be configured as a database according to system requirements. Depending on the type of data packets received, and the necessity thereof, some data packets can be appropriate for storing while others could be temporary type data packets.
- conversion module 550 further includes a coordination module 554 .
- coordination module 554 is configured to include a content storage formatting module 556 .
- Content storage formatting module 556 can be configured for converting received data packets and/or a selected subset of the received data packets to a specified content storage format appropriate for including in a further communication to a predetermined computing device.
- conversion module 550 includes alternative media module 558 .
- Alternative media module 558 can be configured to convert the received data packets to a standardized media type for purposes of sending selected data packets to a conference group, to a sender, a mobile device, an archive, and/or to an output device.
- alternative media module 558 is further configured for converting the received data packets from an original media type to a media type appropriate for enabling a conference with one or more media types, which could include a simple text format, a visual format, a non-English language format, and/or a voice only format.
- conversion module 550 is coupled to indexing module 570 such that indexing module 570 indexes received data packets according to the alternative media type, which can be determined via alternative media module 558 , and/or a target destination for the received data packets.
- Conversion module 550 further includes a tagging module 562 .
- Tagging module 562 can be configured to create a conversion tag to enable a recipient server to convert a responsive data packet to the original media type or to another appropriate media type.
- conversion module 550 can include a conferencing module 558 configured for enabling a conference with multiple forms of media types.
- the media types in the conference can include image data and/or voice data and/or video and/or text data
- the conferencing module can be configured to enable conferencing with parties using a plurality of media types.
- FIGS. 1-2 are provided by way of example only, and are not intended to be limiting. Furthermore, it will be understood that the various process features and system components disclosed herein may be incorporated in different embodiment combinations depending on the circumstances.
- FIGS. 6A , 6 B, 6 C and 6 D an exemplary flow diagram illustrates the operation of various aspects of a cross-media communication storage system in accordance with different embodiments.
- block 610 provides for storing a first data version of specified content based on a particular media format (e.g., cross-media storage system 500 storing data packets in data store 516 including a first data version of specified content).
- a particular media format e.g., cross-media storage system 500 storing data packets in data store 516 including a first data version of specified content.
- Block 620 provides for storing at least a second data version of related content based on a different media format (e.g., data store 516 storing the second data version).
- block 6202 Depicted within block 620 is block 6202 , which provides for storing at least a second data version of related content wherein the related content includes content substantially identical to the specified content of the first data version (e.g., data store 516 storing the second data version and the related content including content substantially identical to specified content of the first data version).
- Block 630 provides for providing a cross-reference between the first data version and the at least second data version to enable coordinated management by a designated user and/or an approved device for search and possible retrieval of the first data version and/or the at least second data version (e.g., data store 516 providing a cross-reference via reference module 514 providing the cross-reference to enable coordinated management by a user communicating via a network 108 , a communication source 532 or a computing device 534 ).
- Block 6302 for providing the cross-reference to enable user accessibility to both the first data version and the at least second data version (e.g., reference module 514 providing the cross-reference to enable a user accessibility to the data versions).
- block 33022 Depicted within block 6302 is illustrated block 33022 , which provides for enabling selective retrieval of the first data version, or the at least second data version, or both without altering respective media formats of the first data version and/or the at least second data version (e.g. transceiver 530 providing selective retrieval of a data version stored in data store 516 and/or previously converted via conversion module 550 ).
- Block 630 further includes block 63024 , which provides for enabling selective retrieval of the first data version and/or the at least second data version after conversion to one or more alternative media formats (e.g., transceiver 530 providing selective retrieval of the first data version and/or the at least second data version after stored in data store 516 after conversion via conversion module 550 to an alternative media format).
- alternative media formats e.g., transceiver 530 providing selective retrieval of the first data version and/or the at least second data version after stored in data store 516 after conversion via conversion module 550 to an alternative media format.
- block 330242 Depicted within block 33024 is block 330242 , which provides for storing the first data version and/or the at least second data version in the one or more alternative media formats (e.g., data store 516 storing a data version in an alternative format).
- alternative media formats e.g., data store 516 storing a data version in an alternative format
- block 33026 provides for enabling selective forwarding of the first data version and/or the at least second data version after conversion to an alternative media format (e.g., transceiver 530 forwarding a first data version or second data version after conversion module 550 converts to an alternative media format).
- an alternative media format e.g., transceiver 530 forwarding a first data version or second data version after conversion module 550 converts to an alternative media format.
- block 6302 Also depicted within block 6302 is optional block 63028 , which provides for enabling selective editing of the first data version and/or the at least second data version after conversion to an alternative media format (e.g., media engine cooperating with processor 510 to enable editing of a data version after conversion module 550 converts to an alternative media format).
- an alternative media format e.g., media engine cooperating with processor 510 to enable editing of a data version after conversion module 550 converts to an alternative media format.
- block 6302 Also depicted within block 6302 is optional block 63029 , which provides for storing the edited version in the alternative media format (e.g., data store 516 storing the edited version in the alternative media format).
- alternative media format e.g., data store 516 storing the edited version in the alternative media format
- block 6304 Depicted within block 630 is optional block 6304 which calls for providing the cross-reference based on subject matter of data in either the first data version and/or the at least second data version (e.g. reference module 514 providing the cross-reference based on subject matter of data in the first data version and/or the second data version).
- Block 630 further includes optional block 6306 , which calls for providing the cross-reference based on a source or origin of the first data version and/or the at least second data version (e.g., reference module 514 providing the cross reference based on a source or origin of the first data version and/or second data version).
- optional block 6306 calls for providing the cross-reference based on a source or origin of the first data version and/or the at least second data version (e.g., reference module 514 providing the cross reference based on a source or origin of the first data version and/or second data version).
- Block 6308 provides for providing the cross-reference based on one of more of the following aspects of the specified content and the related content: subject matter, topic, location, time, event, photos, author, creator, owner, individual identity, group identity, predetermined characterization, metadata, date, user and statistical characteristics (e.g., media engine 540 and reference module 514 providing a cross-reference based on an aspect of specified content and/or related content subject matter, topic, location, time, event, photos, author, creator, owner, individual identity, group identity, predetermined characterization, metadata, date, user and statistical characteristics).
- subject matter topic, location, time, event, photos, author, creator, owner, individual identity, group identity, predetermined characterization, metadata, date, user and statistical characteristics
- Block 640 provides for implementing communication access by one or more parties and/or the designated user via a communication type that is correlated with the first data version and/or the at least second data version (e.g. transceiver 530 implementing communication access for a user or party via a communication type correlated to the data version).
- a communication type that is correlated with the first data version and/or the at least second data version (e.g. transceiver 530 implementing communication access for a user or party via a communication type correlated to the data version).
- block 6402 Depicted within block 640 is block 6402 , which provides for implementing communication access by a single party to the first data version and/or the at least second data version (e.g., transceiver 530 with access module 512 implementing communication access).
- block 64022 Depicted within block 6402 is block 64022 which provides for implementing communication access by an originating party to the first data version and/or the at least second data version (e.g., transceiver 530 implementing communication access by an originating party to the first data version and/or the at least second data version). Also depicted within block 6402 is block 64024 which provides for implementing concurrent communication access by a single party to two or more data versions of the specified content or the related content (e.g., transceiver 530 implementing concurrent communication access by a single party to two or more data versions).
- block 6404 which provides for implementing communication access by multiple parties to the first data version and/or the at least second data version (e.g., transceiver 530 implementing concurrent communication access by multiple parties to the first data version and/or the second data version).
- block 6404 Depicted within block 6404 is optional block 64042 which provides for implementing concurrent communication access by multiple parties to two or more data versions of the specified content or the related content (e.g. transceiver 530 implementing concurrent communication access by multiple parties to two or more data versions of the specified content or the related content).
- transceiver 530 implementing concurrent communication access by multiple parties to two or more data versions of the specified content or the related content.
- block 650 provides for converting the first data version of the specified content from the particular media format to at least a second media format (e.g., conversion module 550 converting data version of the specified content of the from the particular media format to a second media format).
- block 650 Depicted within block 650 is optional block 6502 which provides for converting from the particular media format wherein the particular media format includes one or more of an image media format, a text messaging format, a video media format, an audio media format, a non-voice audio media format, a voice media format, a digital media format, and an analog media format (conversion module 550 converting from the particular media format).
- the particular media format includes one or more of an image media format, a text messaging format, a video media format, an audio media format, a non-voice audio media format, a voice media format, a digital media format, and an analog media format (conversion module 550 converting from the particular media format).
- block 6504 which provides for converting to the at least second media format wherein the at least second media format includes one or more of an image media format, a text messaging format, a video media format, an audio media format, a non-voice audio media format, a voice media format, a digital media format, and an analog media format (e.g. conversion module 550 converting to a second media format wherein the media format is one or more of an image media format, a text messaging format, a video media format, an audio media format, a non-voice audio media format, a voice media format, a digital media format, and an analog media format).
- the at least second media format includes one or more of an image media format, a text messaging format, a video media format, an audio media format, a non-voice audio media format, a voice media format, a digital media format, and an analog media format.
- Optional block 6506 provides for providing communication access to the at least second data version of the related content, wherein the at least second data version is accessible in the different media format and also accessible in the particular media format (e.g., transceiver 550 providing communication access to the at least second data version of the related content, wherein the second data version is accessible via transceiver 550 in a different media format from media engine 540 ).
- Block 670 provides for converting the first data version of selected content from the particular media format to one or more additional media formats (e.g., conversion module 550 converting the first data version of selected content from the particular media format to one or more additional media formats).
- block 670 Depicted within block 670 is optional block 6702 which provides for selecting such additional media format in response to a management request from the designated user and/or the approved device (e.g., computing device 532 , communication source 532 , and/or network 108 representing a designated user and/or approved device providing a management request to media engine 540 , media engine 540 responding to the management request by selecting an additional media format).
- the approved device e.g., computing device 532 , communication source 532 , and/or network 108 representing a designated user and/or approved device providing a management request to media engine 540 , media engine 540 responding to the management request by selecting an additional media format.
- block 670 Also depicted within block 670 is optional block 6704 , which provides for converting wherein the particular media format and/or the one or more additional media formats includes one or more of an image media format, a text messaging format, a video media format, an audio media format, a non-voice audio media format, a voice media format, a digital media format, and an analog media format (e.g., conversion module converting to/from a media format that includes an image media format, a text messaging format, a video media format, an audio media format, a non-voice audio media format, a voice media format, a digital media format, and an analog media format).
- conversion module converting to/from a media format that includes an image media format, a text messaging format, a video media format, an audio media format, a non-voice audio media format, a voice media format, a digital media format, and an analog media format.
- block 670 Also depicted within block 670 is optional block 6706 which provides for converting the at least second data version of the related content from the different media format to the particular media format (e.g., conversion module 550 converting a data format to a particular media format).
- optional block 67062 Depicted within optional block 6706 is shown optional block 67062 , which calls for providing communication access to the at least second data version of the related content, wherein the at least second data version is accessible in the different media format and also accessible in the particular media format (transceiver 530 and access module 512 providing access to a data version of related content, the data version being in either a particular media format or a different media format).
- block 680 provides for converting the at least second data version of related content from the different media format to one or more further media formats (e.g., conversion module 550 converting a data version of related content to a different media format).
- block 680 Depicted within block 680 is optional block 6802 which provides for converting from the different media format wherein the different media format includes one or more of an image media format, a text messaging format, a video media format, a voice media format, a digital media format, and an analog media format (e.g., conversion 550 converting from a different media format, the different media format including one or more of an image media format, a text messaging format, a video media format, a voice media format, a digital media format, and an analog media format).
- the different media format includes one or more of an image media format, a text messaging format, a video media format, a voice media format, a digital media format, and an analog media format.
- Block 680 further includes optional block 6804 which provides for selecting such further media format in response to a management request from the designated user and/or the approved device (media engine 540 receiving a management request via transceiver 540 from a designated user or device, such as computing device 532 that causes a selection of media format).
- Block 690 provides for converting one or more of the first data version and the at least second data version to a standardized storage format (e.g., conversion module 550 converting a data version to a standardized format).
- FIG. 7 an exemplary flow diagram illustrates another method embodiment that includes various possible features for providing cross-media storage.
- block 710 provides for transmitting a first data version of the multimedia data based on a particular media format to a storage facility (e.g., transceiver 530 transmitting a dataversion of multimedia data based on a particular media format to a storage facility, such as computing device 532 ).
- a storage facility e.g., transceiver 530 transmitting a dataversion of multimedia data based on a particular media format to a storage facility, such as computing device 532 ).
- Block 720 provides for receiving from the storage facility a conversion reference identifying the first data version, the conversion reference identifying at least a second data version of the multimedia data (e.g., transceiver 530 receiving from a storage facility a conversion reference produced by reference module 514 or conversion module 550 of a data version, the conversion reference identifying a second data version of multimedia data).
- transceiver 530 receiving from a storage facility a conversion reference produced by reference module 514 or conversion module 550 of a data version, the conversion reference identifying a second data version of multimedia data.
- Block 730 provides for receiving a cross-reference between the first data version and the at least second data version to enable coordinated user or device management of the first data version and the another data version type (e.g., transceiver 530 receiving a cross-reference between a first data version and another data version to enable coordination module 554 to coordinate user and/or device management of data version and type).
- transceiver 530 receiving a cross-reference between a first data version and another data version to enable coordination module 554 to coordinate user and/or device management of data version and type.
- block 730 Depicted within block 730 is optional block 7302 , which provides for converting a received data packet to an SGML-based data format and/or an ASCII-based text format (e.g., conversion module 550 converting a data packet received via transceiver 530 to an SGML or ASCII format).
- the converting data packets can be to SGML to enable a reduced data format, such as a data format appropriate for smart card usage, wireless phone usage, or another hypertext format.
- block 7304 which provides for converting a received data packet by removing one or more data packet envelopes around a core data packet (e.g., conversion module 550 converting a data packet received via transceiver 530 by removing data packet envelopes around a core data packet).
- block 7305 which provides for comparing a received data packet to an index of data packet types to enable one or more predictive stochastic processes to operate on the received data packet prior to performing the lossy conversion process, the one or more predictive stochastic processes identifying one or more media types appropriate for display and/or execution on a mobile device (e.g., indexing module 520 and organization module 560 comparing data packets to an index to enable predictive stochastic processes to operate on data packets prior to conversion module 550 performing a lossy conversion process).
- a mobile device e.g., indexing module 520 and organization module 560 comparing data packets to an index to enable predictive stochastic processes to operate on data packets prior to conversion module 550 performing a lossy conversion process.
- block 7306 provides for receiving the cross-reference to enable converting the multimedia data to a media type appropriate for a mobile device, a display device, a hardcopy output device, a telephonic device, an audio device, and/or a video device (e.g., transceiver 530 receiving a cross-reference to enable conversion module 550 to convert multimedia data to a media type appropriate for a mobile device, display device, hardcopy output device, telephone, audio device and/or voice device).
- transceiver 530 receiving a cross-reference to enable conversion module 550 to convert multimedia data to a media type appropriate for a mobile device, display device, hardcopy output device, telephone, audio device and/or voice device.
- optional 7307 which provides for receiving the cross-reference to enable converting the multimedia data to a media type appropriate for one or more of the following devices: storage, playback, duplication, output, retransmission, conversion, multifunction, still image, display, Morse code transmission, and compression (e.g., transceiver 530 receiving a cross-reference to enable conversion module 550 to convert multimedia data to a media type for storage, playback, duplication, output, retransmission, conversion, multifunction, still image, display, Morse code transmission, and compression).
- transceiver 530 receiving a cross-reference to enable conversion module 550 to convert multimedia data to a media type for storage, playback, duplication, output, retransmission, conversion, multifunction, still image, display, Morse code transmission, and compression.
- block 7308 which provides for receiving the cross-reference to enable converting a received data packet to the another data version type wherein the another data version type includes one or more of an image media type, a text messaging type, a video media type, an audio media type, a non-voice media type, a voice media type, a digital media type, and an analog media type (e.g., transceiver 530 receiving a cross-reference to enable conversion module 550 to convert multimedia data to a media type image media type, a text messaging type, a video media type, an audio media type, a non-voice media type, a voice media type, a digital media type, and an analog media type).
- transceiver 530 receiving a cross-reference to enable conversion module 550 to convert multimedia data to a media type image media type, a text messaging type, a video media type, an audio media type, a non-voice media type, a voice media type, a digital media type, and an analog media type
- the exemplary flow diagram illustrating a method in accordance with an embodiment continues with additional features. Specifically, the flow diagram continues with block 740 , which provides for implementing communication access by one or more parties and/or the designated user via a communication type that is correlated with the first data version and/or the at least second data version (e.g., transceiver 530 implementing communication access by a party or designated user via a communication type correlated with a data type).
- a communication type that is correlated with the first data version and/or the at least second data version
- block 740 Depicted within block 740 is optional block 7402 which provides for implementing concurrent communication access by multiple parties to two or more data versions of the multimedia data (e.g., implementing concurrent communication via transceiver 530 for multiple parties to two or more versions of multimedia data). Also depicted within block 740 is optional block 7404 , which provides for implementing concurrent communication access by a single party to two or more data versions of the multimedia data MISSING (e.g., implementing concurrent communication via transceiver 530 for a single party to two or more versions of multimedia data).
- block 750 which provides for initiating a search to locate the first data version and/or the at least second data version for possible retrieval by one or more parties and/or by the designated user (e.g., search engine 516 initiating a search to locate a first data version or second data version for possible retrieval via transceiver 530 for one or more parties or a designated user).
- search engine 516 initiating a search to locate a first data version or second data version for possible retrieval via transceiver 530 for one or more parties or a designated user.
- block 760 which provides for obtaining retrieval of the first data version and/or the at least second data version by one or more parties and/or by the designated user (e.g., transceiver 530 retrieving the first data version or second data version and providing the data to a designated user or one or more parties over network 108 or directly to a computing device).
- the designated user e.g., transceiver 530 retrieving the first data version or second data version and providing the data to a designated user or one or more parties over network 108 or directly to a computing device.
- block 760 Another possible feature depicted in block 760 is illustrated as optional block 7602 , which provides for obtaining retrieval of a responsive data packet using a media type appropriate for a destination device (e.g., transceiver 530 retrieving a responsive data packet via search engine 516 , the responsive data packet using a media type appropriate for a destination device, such as computing device 532 ).
- a media type appropriate for a destination device e.g., transceiver 530 retrieving a responsive data packet via search engine 516 , the responsive data packet using a media type appropriate for a destination device, such as computing device 532 .
- block 760 Also depicted within block 760 is optional block 7604 , which provides for obtaining retrieval of a responsive data packet using an original particular media type (e.g., transceiver 530 retrieving a responsive data packet via search engine 516 , the responsive data packet using an original media type).
- an original particular media type e.g., transceiver 530 retrieving a responsive data packet via search engine 516 , the responsive data packet using an original media type.
- optional block 7604 Depicted in optional block 7604 is optional block 76042 which provides for providing a conversion tag to enable a conversion of the responsive data packet to the original particular media type (e.g., providing via conversion module 550 and tagging module 562 a conversion tag to enable conversion module 550 to convert the responsive data packet to an original media type).
- the disclosed embodiments have relevance to a wide variety of applications and architectures in addition to those described above.
- the functionality of the subject matter of the present application can be implemented in software, hardware, or a combination of software and hardware.
- the hardware portion can be implemented using specialized logic; the software portion can be stored in a memory or recording medium and executed by a suitable instruction execution system such as a microprocessor.
- an implementer may opt for a mainly hardware and/or firmware vehicle; alternatively, if flexibility is paramount, the implementer may opt for a mainly software implementation; or, yet again alternatively, the implementer may opt for some combination of hardware, software, and/or firmware.
- any vehicle to be utilized is a choice dependent upon the context in which the vehicle will be deployed and the specific concerns (e.g., speed, flexibility, or predictability) of the implementer, any of which may vary.
- Those skilled in the art will recognize that optical aspects of implementations will typically employ optically-oriented hardware, software, and or firmware.
- a signal bearing medium examples include, but are not limited to, the following: a recordable type medium such as a floppy disk, a hard disk drive, a Compact Disc (CD), a Digital Video Disk (DVD), a digital tape, a computer memory, etc.; and a transmission type medium such as a digital and/or an analog communication medium (e.g., a fiber optic cable, a waveguide, a wired communications link, a wireless communication link, etc.)
- any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermedial components.
- any two components so associated can also be viewed as being “operably connected”, or “operably coupled”, to each other to achieve the desired functionality.
- operably couplable include but are not limited to physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.
- examples of such comprehensive devices and/or processes and/or systems might include, as appropriate to context and application, all or part of devices and/or processes and/or systems of (a) an air conveyance (e.g., an airplane, rocket, hovercraft, helicopter, etc.), (b) a ground conveyance (e.g., a car, truck, locomotive, tank, armored personnel carrier, etc.), (c) a building (e.g., a home, warehouse, office, etc.), (d) an appliance (e.g., a refrigerator, a washing machine, a dryer, etc.), (e) a communications system (e.g., a networked system, a telephone system, a Voice over IP system, etc.), (f) a business entity (e.g., an Internet Service Provider (ISP) entity such as Comcast Cable, Quest, Southwestern Bell, etc.); or (g) a wired/wireless services entity such as Sprint, Cingular, Nextel,
- ISP Internet Service Provider
Abstract
Description
Claims (52)
Priority Applications (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/799,039 US7860887B2 (en) | 2007-02-20 | 2007-04-30 | Cross-media storage coordination |
US13/136,664 US9008117B2 (en) | 2007-02-20 | 2011-08-05 | Cross-media storage coordination |
US14/686,738 US9760588B2 (en) | 2007-02-20 | 2015-04-14 | Cross-media storage coordination |
US15/693,344 US20170364544A1 (en) | 2007-02-20 | 2017-08-31 | Cross-media storage coordination |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/709,904 US9008116B2 (en) | 2007-02-20 | 2007-02-20 | Cross-media communication coordination |
US11/799,039 US7860887B2 (en) | 2007-02-20 | 2007-04-30 | Cross-media storage coordination |
Related Parent Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/709,904 Continuation US9008116B2 (en) | 2007-02-20 | 2007-02-20 | Cross-media communication coordination |
US11/709,904 Continuation-In-Part US9008116B2 (en) | 2007-02-20 | 2007-02-20 | Cross-media communication coordination |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12958447 Continuation | 2010-12-02 | ||
US92844710A Continuation | 2007-02-20 | 2010-12-09 |
Publications (2)
Publication Number | Publication Date |
---|---|
US20080201389A1 US20080201389A1 (en) | 2008-08-21 |
US7860887B2 true US7860887B2 (en) | 2010-12-28 |
Family
ID=39707563
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/799,039 Expired - Fee Related US7860887B2 (en) | 2007-02-20 | 2007-04-30 | Cross-media storage coordination |
US13/136,664 Expired - Fee Related US9008117B2 (en) | 2007-02-20 | 2011-08-05 | Cross-media storage coordination |
US14/686,738 Active US9760588B2 (en) | 2007-02-20 | 2015-04-14 | Cross-media storage coordination |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/136,664 Expired - Fee Related US9008117B2 (en) | 2007-02-20 | 2011-08-05 | Cross-media storage coordination |
US14/686,738 Active US9760588B2 (en) | 2007-02-20 | 2015-04-14 | Cross-media storage coordination |
Country Status (1)
Country | Link |
---|---|
US (3) | US7860887B2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100191756A1 (en) * | 2007-03-29 | 2010-07-29 | Kyoichi Terao | Content delivery apparatus, content delivery method, and content delivery program |
US20120246197A1 (en) * | 2011-03-24 | 2012-09-27 | Echostar Technologies L.L.C. | Handling User-Specific Information for Content During Content-Altering Operations |
US8959082B2 (en) | 2011-10-31 | 2015-02-17 | Elwha Llc | Context-sensitive query enrichment |
US9457949B1 (en) | 2013-10-18 | 2016-10-04 | William S. Hathaway, III | Personalized identification system for deceased bodies |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7860887B2 (en) | 2007-02-20 | 2010-12-28 | The Invention Science Fund I, Llc | Cross-media storage coordination |
US8127075B2 (en) * | 2007-07-20 | 2012-02-28 | Seagate Technology Llc | Non-linear stochastic processing storage device |
US20090248529A1 (en) * | 2008-04-01 | 2009-10-01 | Infosys Technologies Limited | System and method for providing value added services via wireless access points |
US8464242B2 (en) * | 2009-07-08 | 2013-06-11 | Tranxition Corporation | Virtualization of configuration settings |
WO2012093996A1 (en) * | 2011-01-04 | 2012-07-12 | Tranxition Corporation | Virtualization of configuration settings |
US8433797B2 (en) | 2011-04-11 | 2013-04-30 | Ringcentral, Inc. | User interface for accessing messages |
US8639754B2 (en) | 2011-09-30 | 2014-01-28 | Advanced Messaging Technologies, Inc. | System and method for providing a protocol for message data |
US20140114919A1 (en) * | 2012-10-19 | 2014-04-24 | United Video Properties, Inc. | Systems and methods for providing synchronized media content |
CN106649715B (en) * | 2016-12-21 | 2019-08-09 | 中国人民解放军国防科学技术大学 | A kind of cross-media retrieval method based on local sensitivity hash algorithm and neural network |
CN111954996B (en) * | 2017-12-19 | 2022-08-23 | 维我系统公司 | System and method for controlling electronic communications |
US11051050B2 (en) * | 2018-08-17 | 2021-06-29 | Kiswe Mobile Inc. | Live streaming with live video production and commentary |
Citations (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5446874A (en) | 1993-12-23 | 1995-08-29 | International Business Machines Corp. | Automated benchmarking with self customization |
US5721919A (en) * | 1993-06-30 | 1998-02-24 | Microsoft Corporation | Method and system for the link tracking of objects |
US20010042114A1 (en) | 1998-02-19 | 2001-11-15 | Sanjay Agraharam | Indexing multimedia communications |
US20020015418A1 (en) | 2000-07-25 | 2002-02-07 | Nec Corporation | Integrated messaging system |
US20020031092A1 (en) | 2000-09-11 | 2002-03-14 | Tetsuaki Wakabayashi | Switching apparatus, communication apparatus, and communication system |
US20030018793A1 (en) | 2001-07-19 | 2003-01-23 | Oscar Mora | Reliable transport layer protocol in low performance 8-bit microcontrollers |
US20030177276A1 (en) | 2002-03-13 | 2003-09-18 | Chaucer Chiu | Data exchange update and back-up system and method between dual operating systems of a computer |
US20040148362A1 (en) * | 2001-11-02 | 2004-07-29 | Lee Friedman | Systems and methods for managing and aggregating media formats |
US20040168205A1 (en) | 2001-05-15 | 2004-08-26 | Nesvadba Jan Alexis Daniel | Content analysis apparatus |
US20040187157A1 (en) | 2003-03-18 | 2004-09-23 | Yen-Hwong Chong | Multifunctional integrated multimedia viewer system |
US20040240562A1 (en) * | 2003-05-28 | 2004-12-02 | Microsoft Corporation | Process and system for identifying a position in video using content-based video timelines |
US20050010686A1 (en) * | 2003-05-01 | 2005-01-13 | Ntt Docomo, Inc. | Router and address indentification information management server |
US20050022252A1 (en) | 2002-06-04 | 2005-01-27 | Tong Shen | System for multimedia recognition, analysis, and indexing, using text, audio, and digital video |
US20050044316A1 (en) | 2003-04-03 | 2005-02-24 | Rajiv Kottomtharayil | System and method for dynamically sharing media in a computer network |
US20050055418A1 (en) | 2001-10-29 | 2005-03-10 | Sun Microsystems Inc | Method to manage high availability equipments |
US20050080755A1 (en) | 2000-01-27 | 2005-04-14 | Kazuyuki Aoyama | System for getting conversion rules |
US20050160070A1 (en) | 2003-12-30 | 2005-07-21 | Mashni Jeries G. | Systems engineering document prototyping system, program product, and related methods |
US20050197964A1 (en) * | 2004-03-02 | 2005-09-08 | Nokia Corporation | Downloading different versions of media files based on a type of download link |
US20050232166A1 (en) | 2004-04-14 | 2005-10-20 | Nierhaus Florian P | Mixed mode conferencing |
US20050262144A1 (en) | 2004-05-06 | 2005-11-24 | Chih-Wei Teng | Method and apparatus for indexing multimedia data |
US20060090082A1 (en) * | 2004-10-22 | 2006-04-27 | Apostolopoulos John G | Systems and methods for multiple level control of access of privileges to protected media content |
US20060101060A1 (en) | 2004-11-08 | 2006-05-11 | Kai Li | Similarity search system with compact data structures |
US20060167956A1 (en) * | 2005-01-27 | 2006-07-27 | Realnetworks, Inc. | Media content transfer method and apparatus (aka shadow cache) |
US20060173859A1 (en) | 2004-12-30 | 2006-08-03 | Samsung Electronics Co., Ltd. | Apparatus and method for extracting context and providing information based on context in multimedia communication system |
US7127261B2 (en) | 2002-02-22 | 2006-10-24 | Julian Van Erlach | Enhanced telecommunication services |
US7139555B2 (en) | 2003-08-01 | 2006-11-21 | Microsoft Corporation | Unified contact list |
US7280546B1 (en) * | 2002-11-25 | 2007-10-09 | Utstarcom, Inc. | Method and system for providing wireless internet protocol access |
US20080077694A1 (en) | 2006-07-20 | 2008-03-27 | Sun Microsystems, Inc. | Method and system for network security using multiple virtual network stack instances |
US20080282353A1 (en) * | 2004-06-29 | 2008-11-13 | Koninklijke Philips Electronics, N.V. | Securely Linked Media Carrying Different Versions of the Same Computer Code |
US20090086975A1 (en) * | 2007-09-28 | 2009-04-02 | Disney Enterprises, Inc. | Flexible format media content and method for providing same |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5404558A (en) | 1992-02-17 | 1995-04-04 | Sharp Kabushiki Kaisha | Data driven type information processor having a plurality of memory banks |
US7024100B1 (en) * | 1999-03-26 | 2006-04-04 | Matsushita Electric Industrial Co., Ltd. | Video storage and retrieval apparatus |
JP2001251351A (en) | 2000-03-02 | 2001-09-14 | Nec Corp | Input packet processing system for packet switch |
US7746496B2 (en) | 2000-03-28 | 2010-06-29 | Mongonet | Method and system for pay per use document transfer via computer network transfer protocols |
EP1391826A4 (en) * | 2001-05-18 | 2007-05-30 | Sony Corp | Information providing method, information providing system, and information server apparatus |
US7099951B2 (en) | 2001-05-24 | 2006-08-29 | Vixs, Inc. | Method and apparatus for multimedia system |
US20020194609A1 (en) * | 2001-06-18 | 2002-12-19 | Tran Thanh T. | Video client with dynamically allocable video buffer for efficiently streaming video |
US7159174B2 (en) * | 2002-01-16 | 2007-01-02 | Microsoft Corporation | Data preparation for media browsing |
JP3695447B2 (en) | 2002-02-27 | 2005-09-14 | 日立電線株式会社 | Virtual LAN connection device |
JP3986866B2 (en) | 2002-03-29 | 2007-10-03 | 松下電器産業株式会社 | Image processing apparatus and ultrasonic diagnostic apparatus |
US7295967B2 (en) * | 2002-06-03 | 2007-11-13 | Arizona Board Of Regents, Acting For And On Behalf Of Arizona State University | System and method of analyzing text using dynamic centering resonance analysis |
US20030236933A1 (en) | 2002-06-21 | 2003-12-25 | Daisuke Shigeta | Information processing apparatus, information equipment, information processing system, automatic backup method, data transmission and reception method, automatic backup program, data transmission and reception program, and record medium having the programs recorded thereon |
EP1725132A2 (en) * | 2004-03-18 | 2006-11-29 | Bodypoint Designs, Inc. | Pivoting side mount and quick release assembly for a pelvic stabilization device |
US7831900B2 (en) | 2004-10-26 | 2010-11-09 | Lg Electronics Inc. | Method for presenting multimedia messages |
JP4506506B2 (en) * | 2005-02-28 | 2010-07-21 | 沖電気工業株式会社 | Wireless access device and communication control method |
US20060206580A1 (en) | 2005-03-08 | 2006-09-14 | Johnson Oliver W Iii | Multimedia distribution apparatus and method |
US20070147262A1 (en) | 2005-12-22 | 2007-06-28 | Jeffrey Aaron | Methods, communication networks, and computer program products for storing and/or logging traffic associated with a network element based on whether the network element can be trusted |
US20070300295A1 (en) | 2006-06-22 | 2007-12-27 | Thomas Yu-Kiu Kwok | Systems and methods to extract data automatically from a composite electronic document |
US7860887B2 (en) | 2007-02-20 | 2010-12-28 | The Invention Science Fund I, Llc | Cross-media storage coordination |
-
2007
- 2007-04-30 US US11/799,039 patent/US7860887B2/en not_active Expired - Fee Related
-
2011
- 2011-08-05 US US13/136,664 patent/US9008117B2/en not_active Expired - Fee Related
-
2015
- 2015-04-14 US US14/686,738 patent/US9760588B2/en active Active
Patent Citations (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5721919A (en) * | 1993-06-30 | 1998-02-24 | Microsoft Corporation | Method and system for the link tracking of objects |
US5446874A (en) | 1993-12-23 | 1995-08-29 | International Business Machines Corp. | Automated benchmarking with self customization |
US20010042114A1 (en) | 1998-02-19 | 2001-11-15 | Sanjay Agraharam | Indexing multimedia communications |
US20050080755A1 (en) | 2000-01-27 | 2005-04-14 | Kazuyuki Aoyama | System for getting conversion rules |
US20020015418A1 (en) | 2000-07-25 | 2002-02-07 | Nec Corporation | Integrated messaging system |
US20020031092A1 (en) | 2000-09-11 | 2002-03-14 | Tetsuaki Wakabayashi | Switching apparatus, communication apparatus, and communication system |
US20040168205A1 (en) | 2001-05-15 | 2004-08-26 | Nesvadba Jan Alexis Daniel | Content analysis apparatus |
US20030018793A1 (en) | 2001-07-19 | 2003-01-23 | Oscar Mora | Reliable transport layer protocol in low performance 8-bit microcontrollers |
US20050055418A1 (en) | 2001-10-29 | 2005-03-10 | Sun Microsystems Inc | Method to manage high availability equipments |
US20040148362A1 (en) * | 2001-11-02 | 2004-07-29 | Lee Friedman | Systems and methods for managing and aggregating media formats |
US7127261B2 (en) | 2002-02-22 | 2006-10-24 | Julian Van Erlach | Enhanced telecommunication services |
US20030177276A1 (en) | 2002-03-13 | 2003-09-18 | Chaucer Chiu | Data exchange update and back-up system and method between dual operating systems of a computer |
US20050022252A1 (en) | 2002-06-04 | 2005-01-27 | Tong Shen | System for multimedia recognition, analysis, and indexing, using text, audio, and digital video |
US7280546B1 (en) * | 2002-11-25 | 2007-10-09 | Utstarcom, Inc. | Method and system for providing wireless internet protocol access |
US20040187157A1 (en) | 2003-03-18 | 2004-09-23 | Yen-Hwong Chong | Multifunctional integrated multimedia viewer system |
US20050044316A1 (en) | 2003-04-03 | 2005-02-24 | Rajiv Kottomtharayil | System and method for dynamically sharing media in a computer network |
US20050010686A1 (en) * | 2003-05-01 | 2005-01-13 | Ntt Docomo, Inc. | Router and address indentification information management server |
US20040240562A1 (en) * | 2003-05-28 | 2004-12-02 | Microsoft Corporation | Process and system for identifying a position in video using content-based video timelines |
US7139555B2 (en) | 2003-08-01 | 2006-11-21 | Microsoft Corporation | Unified contact list |
US20050160070A1 (en) | 2003-12-30 | 2005-07-21 | Mashni Jeries G. | Systems engineering document prototyping system, program product, and related methods |
US20050197964A1 (en) * | 2004-03-02 | 2005-09-08 | Nokia Corporation | Downloading different versions of media files based on a type of download link |
US20050232166A1 (en) | 2004-04-14 | 2005-10-20 | Nierhaus Florian P | Mixed mode conferencing |
US20050262144A1 (en) | 2004-05-06 | 2005-11-24 | Chih-Wei Teng | Method and apparatus for indexing multimedia data |
US20080282353A1 (en) * | 2004-06-29 | 2008-11-13 | Koninklijke Philips Electronics, N.V. | Securely Linked Media Carrying Different Versions of the Same Computer Code |
US20060090082A1 (en) * | 2004-10-22 | 2006-04-27 | Apostolopoulos John G | Systems and methods for multiple level control of access of privileges to protected media content |
US20060101060A1 (en) | 2004-11-08 | 2006-05-11 | Kai Li | Similarity search system with compact data structures |
US20060173859A1 (en) | 2004-12-30 | 2006-08-03 | Samsung Electronics Co., Ltd. | Apparatus and method for extracting context and providing information based on context in multimedia communication system |
US20060167956A1 (en) * | 2005-01-27 | 2006-07-27 | Realnetworks, Inc. | Media content transfer method and apparatus (aka shadow cache) |
US20080077694A1 (en) | 2006-07-20 | 2008-03-27 | Sun Microsystems, Inc. | Method and system for network security using multiple virtual network stack instances |
US20090086975A1 (en) * | 2007-09-28 | 2009-04-02 | Disney Enterprises, Inc. | Flexible format media content and method for providing same |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100191756A1 (en) * | 2007-03-29 | 2010-07-29 | Kyoichi Terao | Content delivery apparatus, content delivery method, and content delivery program |
US8086629B2 (en) * | 2007-03-29 | 2011-12-27 | Pioneer Corporation | Content delivery apparatus, content delivery method, and content delivery program |
US20120246197A1 (en) * | 2011-03-24 | 2012-09-27 | Echostar Technologies L.L.C. | Handling User-Specific Information for Content During Content-Altering Operations |
US9582505B2 (en) * | 2011-03-24 | 2017-02-28 | Echostar Technologies L.L.C. | Handling user-specific information for content during content-altering operations |
US8959082B2 (en) | 2011-10-31 | 2015-02-17 | Elwha Llc | Context-sensitive query enrichment |
US9569439B2 (en) | 2011-10-31 | 2017-02-14 | Elwha Llc | Context-sensitive query enrichment |
US10169339B2 (en) | 2011-10-31 | 2019-01-01 | Elwha Llc | Context-sensitive query enrichment |
US9457949B1 (en) | 2013-10-18 | 2016-10-04 | William S. Hathaway, III | Personalized identification system for deceased bodies |
US10238570B2 (en) | 2013-10-18 | 2019-03-26 | William S. Hathaway, III | Personalized identification system for deceased bodies |
Also Published As
Publication number | Publication date |
---|---|
US9008117B2 (en) | 2015-04-14 |
US20120093174A1 (en) | 2012-04-19 |
US9760588B2 (en) | 2017-09-12 |
US20150293963A1 (en) | 2015-10-15 |
US20080201389A1 (en) | 2008-08-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7860887B2 (en) | Cross-media storage coordination | |
US10972413B2 (en) | System and method for monitoring, blocking according to selection criteria, converting, and copying multimedia messages into storage locations in a compliance file format | |
US10079789B2 (en) | Shared attachments | |
US7668849B1 (en) | Method and system for processing structured data and unstructured data | |
US11429563B2 (en) | Prioritizing thumbnail previews based on message content | |
US10482277B2 (en) | Security application for data security formatting, tagging and control | |
KR20060102268A (en) | Selectable state machine user interface system | |
US20100161737A1 (en) | Techniques to manage electronic mail personal archives | |
EP2567509A1 (en) | Method for launching a contextualized on-the-fly conference | |
US20070203968A1 (en) | Portable device and method for entertainment interaction data | |
US20200412877A1 (en) | Identifier technique for communication interchange | |
US8135786B2 (en) | Message-based technique for sharing distribution list contents within electronic messaging systems | |
KR100836162B1 (en) | Method for managing details of conversations in mobile communication terminal and mobile communication terminal for the same | |
US9008116B2 (en) | Cross-media communication coordination | |
US20150046565A1 (en) | System and method for archiving messages | |
US20170364544A1 (en) | Cross-media storage coordination | |
US8745144B2 (en) | Persisting contact information in mailbox | |
US11468707B2 (en) | Automatic image classification in electronic communications | |
CN207053556U (en) | storing open platform based on data sharing | |
TWI416421B (en) | System and method for sending information | |
Pizano et al. | Integrated multimedia messaging concepts and applications | |
US9002486B1 (en) | Audio systems and methods | |
Al-Sultany et al. | Facilitating mobile communication with annotated messages | |
CN102073552B (en) | Digital resource packet structure verifying method and system | |
CN116186194A (en) | Information processing method, device, equipment and computer readable storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SEARETE LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:COHEN, ALEXANDER J.;JUNG, EDWARD K.Y.;LEVIEN, ROYCE A.;AND OTHERS;REEL/FRAME:019884/0050;SIGNING DATES FROM 20070613 TO 20070913 Owner name: SEARETE LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:COHEN, ALEXANDER J.;JUNG, EDWARD K.Y.;LEVIEN, ROYCE A.;AND OTHERS;SIGNING DATES FROM 20070613 TO 20070913;REEL/FRAME:019884/0050 |
|
AS | Assignment |
Owner name: THE INVENTION SCIENCE FUND I, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SEARETE LLC;REEL/FRAME:024930/0962 Effective date: 20100902 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
CC | Certificate of correction | ||
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552) Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20221228 |