US 7,827,239 B2Grant
Dynamic media content for collaborators with client environment information in dynamic client contexts
Issue Date:2010-11-02
•1 Claims
•16 Drawing Sheets
Abstract
Delivering dynamic media content to collaborators, including providing collaborative event media content, where the collaborative event media content further comprises a grammar and a structured document; acquiring data representing a client's environmental condition; storing, in the context server in a data structure comprising a dynamic client context for the client, the data representing a client's environmental condition; detecting an event in dependence upon the dynamic client context; identifying one or more collaborators in dependence upon the dynamic client context and the event; selecting from the structured document a classified structural element in dependence upon an event type and a collaborator classification; and transmitting the selected structural element to the collaborator.
Metadata
Assignee
- International Business Machines Corporation
Inventors
- William Kress Bodin
- Derral Charles Thorson
Application Information
Application Number:US 10/832,035
Filing Date:2004-04-26
Priority Date:2004-04-26
Art Unit:2445
Classifications
IPC:
G06F15/16
Patent Drawings (16 sheets)
Description
BACKGROUND OF THE INVENTION
[0001] 1. Field of the Invention
[0002] The field of the invention is data processing, or, more specifically, methods, systems, and products for delivering dynamic media content for collaborators.
[0003] 2. Description of Related Art
[0004] Technology today includes the capability of sensing client locations and retaining persistent data describing clients, devices and persons, and the environments in which they reside, work, and travel. Technology provides the capability of detecting changes in clients' environments including their locations. Current technology provides the capability of structuring information needed to respond meaningfully to such changes, including, for example, the capabilities of the SGML (Standard Generalized Markup Language), XML (extensible Markup Language), and HTML (HyperText Markup Language).
[0005] For any particular response, however, there is a wide variety of collaborator purpose, organizational affiliation, technical knowledge, security authorization, and so on, across almost any dimension in which responders may vary. Targeting content for such a heterogeneous set of collaborators is typically a manual process today in which providers create wholly separate presentations for each type of collaborator, and the content of each such presentation is reduced to the lowest common denominator of any particular group. There is a substantial need for improved coordination in responding to changes in clients' locations and environments as well as improvements in multimedia presentation systems useful by responding collaborators.
SUMMARY OF THE INVENTION
[0006] Methods, systems, and computer program products are described for delivering dynamic media content to collaborators that include providing collaborative event media content, where the collaborative event media content further comprises a grammar and a structured document; acquiring data representing a client's environmental condition; storing, in the context server in a data structure comprising a dynamic client context for the client, the data representing a client's environmental condition; detecting an event in dependence upon the dynamic client context; identifying one or more collaborators in dependence upon the dynamic client context and the event; selecting from the structured document a classified structural element in dependence upon an event type and a collaborator classification; and transmitting the selected structural element to the collaborator.
[0007] In some embodiments, acquiring data representing a client's environmental condition includes receiving asynchronously from environmental sensors data representing a client's environmental condition. In some embodiments, the dynamic client context includes network addresses for environmental sensors for a client and acquiring data representing a client's environmental condition includes the context server's polling of the environmental sensors for the client. In typical embodiments, detecting an event in dependence upon the dynamic client context includes detecting a change in a value of a data element in the dynamic client context and applying an event detection rules base to the dynamic client context.
[0008] In typical embodiments, providing collaborative event media content includes creating, in dependence upon original media content, a structured document, where the structured document includes one or more structural elements, and creating a grammar for the collaborative event media content, where the grammar includes grammar elements each of which includes an identifier for at least one structural element of the structured document.
[0009] Such embodiments typically also include classifying a structural element of the structured document according to a presentation attribute. In such embodiments, classifying a structural element typically includes identifying a presentation attribute for the structural element; identifying a classification identifier in dependence upon the presentation attribute; and inserting the classification identifier in association with the structural element in the structured document.
[0010] In many embodiments, identifying collaborators includes identifying a collaborator in dependence upon collaborator presence on a instant messaging network. In many embodiments, identifying one or more collaborators in dependence upon the identified event includes identifying a collaborator in dependence upon client location. In typical embodiments, transmitting the selected structural element to the collaborator includes selecting a data communications protocol for communications with a collaborator; inserting the selected structural element in a data structure appropriate to the data communications protocol; and transmitting the data structure to the collaborator according to the data communications protocol.
[0011] The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular descriptions of exemplary embodiments of the invention as illustrated in the accompanying drawings wherein like reference numbers generally represent like parts of exemplary embodiments of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS
[0012] FIG. 1 sets forth a block diagram of an exemplary system operable according to embodiments of the present invention to deliver dynamic media content to collaborators.
[0013] FIG. 2 sets forth data structure diagrams illustrating exemplary data structures useful in various embodiments of the present invention to deliver dynamic media content to collaborators.
[0014] FIG. 3 sets forth a data flow diagram illustrating an exemplary method for providing collaborative event media content.
[0015] FIG. 4 sets forth an exemplary data structure in which a grammar may be implemented according to embodiments of the present invention.
[0016] FIG. 5 is a data flow diagram illustrating a further method for providing collaborative event media content.
[0017] FIG. 6 sets for a data flow diagram illustrating an exemplary method for classifying a structural element.
[0018] FIG. 7 sets forth a data flow diagram illustrating an exemplary method for classifying a structural element.
[0019] FIG. 8 sets forth a data flow diagram illustrating a further exemplary method for classifying a structural element.
[0020] FIG. 9 sets forth a data flow diagram illustrating another exemplary method for classifying a structural element.
[0021] FIG. 10 sets forth a data flow diagram illustrating a further exemplary method for classifying a structural element.
[0022] FIG. 11 sets forth a flow chart illustrating an exemplary method for delivering dynamic media content to collaborators.
[0023] FIG. 12 sets a forth flow chart illustrating an exemplary method for detecting an event in dependence upon a dynamic client context.
[0024] FIG. 13 sets forth a data flow diagram illustrating a further exemplary method for selecting classified structural elements and transmitting them to a collaborator.
[0025] FIG. 14 sets forth a flow chart illustrating an exemplary method for generating a dynamic client context for a client.
[0026] FIG. 15 sets forth a flow chart illustrating an exemplary method for generating a dynamic client context for a client.
DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS
Introduction
[0027] The present invention is described to a large extent in this specification in terms of methods for creating a voice response grammar from a presentation grammar. Persons skilled in the art, however, will recognize that any computer system that includes suitable programming means for operating in accordance with the disclosed methods also falls well within the scope of the present invention. Suitable programming means include any means for directing a computer system to execute the steps of the method of the invention, including for example, systems comprised of processing units and arithmetic-logic circuits coupled to computer memory, which systems have the capability of storing in computer memory, which computer memory includes electronic circuits configured to store data and program instructions, programmed steps of the method of the invention for execution by a processing unit.
[0028] The invention also may be embodied in a computer program product, such as a diskette or other recording medium, for use with any suitable data processing system. Embodiments of a computer program product may be implemented by use of any recording medium for machine-readable information, including magnetic media, optical media, or other suitable media. Persons skilled in the art will immediately recognize that any computer system having suitable programming means will be capable of executing the steps of the method of the invention as embodied in a program product. Persons skilled in the art will recognize immediately that, although most of the exemplary embodiments described in this specification are oriented to software installed and executing on computer hardware, nevertheless, alternative embodiments implemented as firmware or as hardware are well within the scope of the present invention.
Delivering Dynamic Media Content to Collaborators
[0029] Exemplary methods, systems, and products are described for delivering dynamic media content to collaborators with reference to the accompanying drawings, beginning with FIG. 1 . FIG. 1 sets forth a block diagram of an exemplary system operable according to embodiments of the present invention to deliver dynamic media content to collaborators. The system of FIG. 1 operates generally to deliver dynamic media content to collaborators by providing collaborative event media content (266), where collaborative event media content generally includes a grammar and a structured document; generating a dynamic client context (236) for a client (154); detecting an event (168) in dependence upon the dynamic client context (236); identifying one or more collaborators (182) in dependence upon a dynamic client context (236) and the event (168); selecting from a structured document in the collaborative event media content (266) a classified structural element in dependence upon an event type and a collaborator classification; and transmitting the selected structural element to the collaborator.
[0030] The system of FIG. 1 includes environmental sensors (156) and location sensors (158) that provide data describing a client (154) and the client's environment. Environmental sensors are any sensor capable of detecting or measuring in electronic form one or more environmental conditions of a client, including factors and variables near the client's physical location. Examples of environmental sensors include smoke detectors, thermometers, barometers, motion detectors, light sensors, metal detectors, chemical sensors, and so on, as will occur to those of skill in the art Location sensors are any mechanism capable of indicating in electronic form at least a useful approximation of the client's physical location. Examples of location sensors include GPS (Global Positioning System) receivers, network routers configured with their own physical locations, and network routers configured with clients' physical locations.
[0031] The system of FIG. 1 also includes clients (154) that operate by acquiring data that describes the client and the client's environment and communicates that data to a context server (160) for storage in a dynamic client context. Clients are any automated computing machinery capable of communicating client location and client environmental data to a context server, including, for example, personal computers, laptops, personal digital assistants (“PDAs”), network-enabled mobile telephones, and so on, as will occur to those of skill in the art. There is no requirement that a client be associated with a person, although they often are. On the other hand, however, a client may be the computer operating a security system in a building with smoke detectors, thermometers, and motion sensors. Context server (160) is any data communications server capable of accepting data communications messages from clients and providing data processing services in response to such messages. Such messages may be communicated according to any useful data communications protocol as will occur to those of skill in the art, including for example HTTP (the HyperText Transport Protocol), and the messages may include, for example, HTTP ‘REQUEST’ messages and HTTP ‘POST’ messages.
[0032] Data processing services provided by context server (160) include detecting an event (168) in dependence upon the dynamic client context (236). Detecting an event may be carried out by detecting a change in a value of a data element in a dynamic client context (236) and applying an event detection rules base (164) to the dynamic client context. Context server (160) includes an event generator (166), a software module programmed to create an event object (168) and hand it off to action engine (170) when an event is detected.
[0033] An event is a change in one or more values of data elements in a dynamic client context that meet event criteria such as threshold requirements or rules in a rules base. A mere change in the value of a data element may not be enough to constitute an event. A change in environmental temperature from 72 degrees Fahrenheit to 73 degrees Fahrenheit, for example, may generally be ignored by an event generator. Consider the following event generation rule, however:
-
- [0034] IF a client's physical location is in a building
- [0035] AND IF the temperature in the building exceeds 105 degrees Fahrenheit
- [0036] AND IF a smoke detector in the building is activated
- [0037] THEN event type is set to ‘FIRE’
[0038] In this example, the client's physical location, the environmental temperature for the client, and the status of the smoke detector where the client is located are all stored in data elements in a dynamic client context for the client. In this example, event generator applies the exemplary rule from rules base (164) and receives a return event type of ‘FIRE,’ which event generator (166) is programmed to pass to an object oriented parameterized event creation factory method in an event factory object. The event factory instantiates and returns an object of a concrete event class named, for example, fireEvent, derived from an abstract event class. The abstract class declares member data elements and member methods needed by all concrete event classes in the system. Each concrete event class is then augmented with member data elements and member methods as needed to address particular kinds of events, fires, automobile accidents, hazardous materials spills identified by chemical sensors, firearms presence identified by metal detectors, burglaries identified by motion detectors, and so on. Exemplary concrete event class names therefore may include not only fireEvent, but also carWreckEvent, hazMatEvent, gunEvent, burglaryEvent, and so on, as will occur to those of skill in the art.
[0039] When an event generator instantiates an event object, the event generator typically may include in the event object a reference to one or more dynamic client context objects, including the current dynamic client context object whose changes in data values triggered the event, but also one or more previous dynamic client context objects so that an action engine may have previous data values as needed. Alternatively, a concrete event class may include all the data elements needed for action preparation, so that only the data values are loaded from the pertinent dynamic client contexts rather than including the dynamic client contexts themselves, object built from them, or object oriented references or pointers to them.
[0040] Event (168), by the time it arrives in action engine (170) contains all the data needed to identify the type of event and develop actions in response to the event, including data from or references to, objects built from pertinent dynamic client contexts (236). Action engine (170) is programmed to apply collaborator selection rules (186) to the event type identified in event (168) to assemble from collaborator profile database (184) a list (176) of collaborators for the event. Collaborator profiles are data structures such as records in a collaborator profile database (184) that include data elements describing a collaborator, including, for example, collaborator name, collaborator identification code, collaborator physical address, collaborator type (EMS, police, wife, accountant, lawyer, HazMat Responder, and so on), and a list of one or more event types in which a collaborator may collaborate. Examples of collaborator selection rules include the following:
-
- [0041] Select collaborators according to event type.
- [0042] Select only collaborators that are currently ‘present’ for receipt of instant messages on an instant messaging service.
- [0043] If, for an event type, there is more than one collaborator of a collaborator type, select all collaborators of that type.
- [0044] If, for an event type, there is more than one collaborator of a collaborator type, select the first collaborator of that type found in the collaborator profile database.
- [0045] If, for an event type, there is more than one collaborator of a collaborator type, select the collaborator of that type whose physical location is closest to the client's.
[0046] The collaborator list (176) is installed in instant messaging server (174) so that all collaborators in the list are ‘present’ for instant messaging and all collaborators on the list are joined in a messaging session so that any messages from any collaborator is seen immediately on the communications devices of all collaborators (182). Examples of instant messaging protocols useful with various embodiments of the present invention include the Instant Messaging and Presence Protocol (“IMPP”) specified by the IMPP Working Group of the Internet Engineering Task Force and the Mitre Corporation's Simple Instant Messaging and Presence Service (“SIMP”). Such instant messaging services generally define and support ‘presence services’ that provide indications whether an instant messaging client is on-line. Such services also allow users, in this case collaborators, to subscribe to one another's messaging, so that messages to one collaborator are also communicated to other subscribing collaborators. Action engine (170), in providing the list (176) of collaborators for an event (168) to the instant messaging service (174), effects a mutual subscription among the collaborators so listed, so that messages among the collaborators are communicated to all collaborators for that event.
[0047] Collaborators (182) are effectively represented in the system of FIG. 1 by their communications devices, which again may or may not be associated directly with a particular person. A ‘collaborator’ may be, for example, a console in a 911 service staffed by more than one person, or a passive, unmanned display device may be registered as a collaborator for an event type. It is generally expected, however, that a collaborator is a person participating, collaborating, in responding to an event by use of a data communications device connected to an instant messaging session that is established for the purpose of helping collaborators so respond.
[0048] In the system of FIG. 1 , action engine (170) is programmed to request of action server (178) an action list for an event type. Action server (178) operates an action factory (not shown) that generates from concrete action classes (180) one or more action objects, places references to the action object in a list object (172), and returns the list object (172) to action engine (170). Action engine (170) then proceeds generally to execute the actions identified in the list (172). Examples of actions include transmitting to collaborators a description of the event that triggered the current action list, transmitting to collaborators data from a pertinent dynamic client context, transmitting to collaborators Materials Data Sheets for use in HazMat responses, transmitting to collaborators maps showing a client's physical location, transmitting to collaborators travel directions to a client's physical location, and so on as will occur to those of skill in the art.
[0049] The system of FIG. 1 includes a voice response server (104) through which collaborators (182) may issue presentation control instructions to action engine (170). Presentation control instructions represent instructions or requests from collaborators for particular collaborative event media content. A collaborator may, for example, request a map of the neighborhood of a client's physical location, directions from the collaborator's present location to the client's location, Materials Data Sheets for hazmat responses, and so on. Voice response server (104) creates presentation control instructions for action engine (170), for example, by receiving through a VOIP (Voice Over Internet Protocol) channel from a collaborator a key phrase and optional parameters for invoking a presentation action and parsing the key phrase and parameters against a grammar into a presentation control instruction.
[0050] For further explanation, FIG. 2 sets forth data structure diagrams illustrating exemplary data structures useful in various embodiments of the present invention to deliver dynamic media content to collaborators. The exemplary data structures of FIG. 2 include a client record (154) representing a client. As discussed above, a client is any automated computing machinery capable of communicating client location and client environmental data to a context server, including, for example, personal computers, laptops, personal digital assistants (“PDAs”), network-enabled mobile telephones, and so on, as will occur to those of skill in the art. The client record (154) of FIG. 2 includes a clientID field (670) that uniquely identifies the client and an IP address field (673) that includes a network address of the client.
[0051] The exemplary data structures of FIG. 2 also include a dynamic client context record (236) that represents the client and the client's surrounding environment. The dynamic client context record (236) of FIG. 2 includes a client ID (670) identifying the client and a location field (554) containing the location of the client. The location of the client may be represented as a set of coordinates, a physical address, a building and room number, or any other representation of client location that will occur to those of skill in the art. The dynamic client context record (236) of FIG. 2 includes a data storage for three sets of environmental IDs (672, 676, 680) and their corresponding environmental values (674, 678, 682). Environmental IDs uniquely identify a particular environmental condition such as temperature, humidity, barometric pressure and so on as will occur to those of skill in the art. Environmental values (674, 678, 682) represent the current state of the environmental conditions. Environmental values are typically measured in electronic form by one or more environmental sensors and reported to a client. Examples of environmental sensors include smoke detectors, thermometers, barometers, motion detectors, light sensors, metal detectors, chemical sensors, and so on, as will occur to those of skill in the art. Although the dynamic client context (236) of FIG. 2 includes data storage for only three environmental IDs and their corresponding values there is no such limitation in the scope of the present invention. In fact, dynamic client contexts according to the present invention often contain values for many kinds of environmental conditions and therefore there is no limitation on the number of environmental conditions that can be represented in a dynamic client context as will occur to those of skill in the art.
[0052] The exemplary data structures of FIG. 2 also include an event record (168) representing a change in one or more values of data elements in a dynamic client context that meet event criteria such as threshold requirements or rules in a rules base. The event record (168) of FIG. 2 includes an event ID (684) uniquely identifying the event and an event type (686) that identifies the kind of event represented by the event record. Examples of event types include ‘fire,’ ‘rain,’ ‘thunder’ and so on as will occur to those of skill in the art.
[0053] The data structures of FIG. 2 include an exemplary collaborator profile (183) representing a collaborator. As discussed above, collaborators can be persons, devices, or processes and are often represented by their communications devices. A ‘collaborator’ may be, for example, a console in a 911 service staffed by more than one person, or a passive, unmanned display device may be registered as a collaborator for an event type. It is generally expected, however, that a collaborator is a person participating, collaborating, in responding to an event by use of a data communications device connected to an instant messaging session that is established for the purpose of helping collaborators so respond. The collaborator profile (183) of FIG. 2 includes a collaborator ID (243) uniquely identifying the collaborator (244). The exemplary collaborator profile (183) of FIG. 2 includes data storage for a classification (244) for the collaborator. A collaborator classification is type code describing the collaborator and used to both select the collaborator in response to an event as well as to select structural elements of collaborative event media content to present to the collaborator. The exemplary collaborator profile (183) of FIG. 2 includes the collaborators current location (688) and data storage for one or more display device IDs (690) identifying one or more display devices available to the collaborator on which structural element of collaborative event media content can be displayed to the collaborator. The exemplary collaborator profile (183) also includes an eventTypeList (681) that includes event types for collaborator selection as discussed in more detail below.
[0054] The exemplary data structures of FIG. 2 includes collaborative event media content (266) representing media content available for dynamic delivery to a collaborator in response to an event. The collaborative event media content of FIG. 2 includes a structured document (122) which includes a plurality of structural elements (402) and classification identifies (708) for the structural elements. Examples of structural elements include pages, paragraphs, bullet points, graphical images, and so on as will occur to those of skill in the art. A classification identifier is an identifier that classifies a structural element for a particular collaborator. That is, classification identifiers are used to select particular structural elements for delivery to particular collaborators.
[0055] The collaborative event media content includes a grammar (258) associated with the structured document (122) that includes grammar elements (316) and structural element identifiers (318). A grammar (258) is a data structure associating key phrases with presentation actions that facilitates a collaborator navigating the structured document (122) of collaborative event media content using speech commands. In the example of FIG. 2 , the grammar (258) includes grammar elements (316) each of which includes an identifier (318) for at least one structural element (402) of the structured document (122).
Providing Collaborative Event Media Content
[0056] For further explanation, FIG. 3 sets forth a data flow diagram illustrating an exemplary method for providing collaborative event media content that includes creating (304), in dependence upon original media content (108), a structured document (122). In the example of FIG. 3 , the structured document (122) includes one or more structural elements (402). Examples of structural elements include pages, paragraphs, slides, bullets points, graphic images, video clips and so on as will occur to those of skill in the art. In the method of FIG. 3 , creating (304) a structured document (122) includes inserting (320) in the structural document (122) structural element identifiers (322) for the structural elements (402). A structural element identifier (302) is an identifier such as for example a tag in an XML document or other identifier in a structured document that identifies a structural element.
[0057] The method of FIG. 3 also includes creating (310) a grammar (258) for the collaborative event media content (266). A grammar (258) is a data structure associating key phrases with presentation actions that facilitates a collaborator navigating the structured document (122) of the collaborative event media content (266) using speech commands. A presentation action is an action controlling the display of one or more structural elements of a structured document. For example, a grammar may include a key phrase ‘next bullet’ that is associated with a presentation action that searches the structured document for the next structural element identified as a bullet point and displays that structural element. In such and example, to invoke the display of the next bullet point of the structured document, a collaborator need only speak the key phrase ‘next bullet.’
[0058] For further explanation FIG. 4 sets forth an exemplary data structure (258) in which a grammar may be implemented according to embodiments of the present invention. The grammar of FIG. 4 includes several grammar elements (502-514) for a content type. A content type represents the kind of media to be directed with spoken key phrases of the grammar. In this example, the content type is taken as a word processing document having structural elements that include pages, paragraphs, bullets, titles, subtitles, and so on, and the data structure includes a column for an identifier (318) of a structural element, a column for a key phrase (516) for formulating a presentation control instruction for invoking a presentation action to display the collaborative media content, and a column for a presentation action identifier (518) representing a presentation action. The exemplary data structure of FIG. 4 also includes a column for a data indication whether a presentation control instruction requires a parameter. The exemplary grammar entries for presentation action identifiers PgDn (502), PgUp (504), nextParagraph (508), and prevBullet (512) have parameter (520) values of ‘null,’ signifying that a voice response server parsing their key phrases into presentation control instructions is not to parse a parameter for a presentation control instruction. The exemplary grammar entries for presentation action identifiers goToPage (506), nextHeading (510), and goToSubtitle (514), however, have parameter (520) values of ‘integer’ and ‘string,’ signifying that a voice response server parsing their key phrases into presentation control instructions is to seek to parse for each of them respectively an integer parameter, a string parameter, and a string parameter.
[0059] Creating a grammar (258) such as the grammar of FIG. 4 typically includes identifying the content type of at least a portion of the original media content and associating, in dependence upon the content type, a key phrase with a presentation action. Identifying the content type of at least a portion of the original media content can be carried out by identifying the content type in dependence upon a filename extension, in dependence upon document header elements, or any other way of identifying the content type that will occur to those of skill in the art.
[0060] Methods of providing collaborative event media content are further explained with an exemplary use case. Consider the following example of a structured document:
[0061]
| <document> | |
| <page id=“1”> | |
| <p id=“1”>a paragraph</p> | |
| <p id=“2”>another paragraph</p> | |
| <image id=“1”>a graphic image</image> | |
| </page> | |
| <page id=“2”> | |
| <p id=“3”>a paragraph</p> | |
| <p id=“4”>another paragraph</p> | |
| <image id=“2”>another graphic image</image> | |
| </page> | |
| </document> | |
[0062] And assume that this exemplary structured document is associated in a providing collaborative event media content with the following grammar:
[0063]
| TABLE 1 | ||||
|---|---|---|---|---|
| Grammar | ||||
| Presentation | Structural | |||
| Action | Element | |||
| Key Phrase | Identifier | Identifier | Parameter | |
| page down | PgDn | <page> | null | |
| page up | PgUp | <page> | null | |
| go to page | goToPage | <page> | integer | |
| next paragraph | nextParagraph | <p> | null | |
| go to paragraph | goToParagraph | <p> | integer | |
| next image | nextImage | <image> | null | |
| go to image | goToImage | <image> | integer | |
[0064] In this example, collaborative event media content is transmitted to a collaborator and the first page of the structured document is displayed on a collaborator's communications device such as for example a voice response server enabled PDA. When the collaborator speaks the words “page down,” a voice response server on the PDA parses the speech into a presentation control instruction having a presentation control identifier named “PgDn” and communicates the presentation control instruction to display the next page, in this example, page 2 of the example structured document. Similarly, when the first page of the structured document is displayed, a collaborator's speaking the words “go to paragraph 4” results in changing the display to show paragraph 4 on the second page of the document. And, when the first page is on display for the collaborators the collaborator speaks the words “next image,” a collaborator's display device changes the display to show image 2 on the second page of the document.
Classifying Structural Elements in Collaborative Event Media Content
[0065] FIG. 5 is a data flow diagram illustrating a further method for providing collaborative event media content (266). The method of FIG. 5 includes creating (304), in dependence upon an original media content (108), a structured document (122) comprising one or more structural elements (402), as explained in above. The method of FIG. 5 also includes classifying (330) a structural element (402) of the structured document (122) according to a presentation attribute (352). Presentation attributes are generic selection criteria for displaying appropriate structural elements of collaborative event media content to collaborators. Examples of presentation attributes include collaborator's company names, department names, security levels, technical levels, and so on. The method of FIG. 5 also includes creating (310) a grammar (258) for the structured document (122) as described above with reference to FIGS. 3 and 4 .
[0066] For further explanation, FIG. 6 sets for a data flow diagram illustrating an exemplary method for classifying a structural element. The method of FIG. 6 includes identifying (702) a presentation attribute (352) for the structural element (402); identifying (704) a classification identifier (708) in dependence upon the presentation attribute (352); and inserting (706) the classification identifier (708) in association with the structural element (402) in the structured document (122). As discussed above with reference to FIG. 5 , presentation attributes are generic selection criteria for displaying appropriate structural elements of collaborative event media content to collaborators. Examples of presentation attributes include collaborator's company names, department names, security levels, technical levels, and so on. A classification identifier (708) identifies a collaborators classification. Examples of classifications include any supported data codes describing collaborator classification, including, for example “company=IBM,” “department=marketing,” “technical level=3,” “security level=2,” and others as will occur to those of skill in the art.
[0067] For further explanation, FIG. 7 sets forth a data flow diagram illustrating an exemplary method for classifying a structural element in a structured document in which identifying (702) a presentation attribute (352) for the structural element (402) includes selecting (710) a presentation attribute (352) from a list (712) of supported presentation attributes (352). The presentation attribute list (712) of FIG. 7 includes two columns, one column for presentation attributes (352) and another column for associated classification identifiers (708). In the method of FIG. 7 , identifying (704) a classification identifier (708) is carried out by identifying a classification identifier (708) associated with the presentation attribute (352) on the list (712). In the method of FIG. 7 , inserting (706) the classification identifier (708) includes manually editing (712) the structured document (122) to insert classification identifiers in appropriate locations to classify structural elements in a structured document. For example, a paragraph to be viewed only by collaborators who are members of the marketing department may be classified by tagging the paragraph with <mkt> </mkt>.
[0068] For further explanation, FIG. 8 sets forth a data flow diagram illustrating a further exemplary method for classifying a structural element in a structured document (122) in which identifying (702) a presentation attribute (352) for the structural element (402) includes selecting (710) a presentation attribute (352) from a list (712) of supported presentation attributes (352), the presentation attribute (352) having an associated classification identifier (708). In the method of FIG. 8 , identifying (704) a classification identifier (708) includes inserting (716) the classification identifier (708) in a data structure (717) in association with a structural element identifier (322) for the structural element (402). In the method of FIG. 8 , inserting (706) the classification identifier (708) in the structured document (122) includes reading (714) the classification identifier (708) from the data structure (717) in dependence upon the structural element identifier (322).
[0069] For further explanation, FIG. 9 sets forth a data flow diagram illustrating another exemplary method for classifying a structural element in a structured document that includes providing a list (712) of supported presentation attributes (352) including at least one keyword (802) and at least one indication of structural insertion scope (804) for each presentation attribute (352). In the method of FIG. 9 , identifying (702) a presentation attribute (352) for the structural element (402) includes selecting (710) a presentation attribute (352) from the list (712) in dependence upon a keyword (806) from the structured document (122). In the method of FIG. 9 , identifying (704) a classification identifier (708) is carried out by identifying a classification identifier (708) associated with the presentation attribute (352) on the list (712). In the method of FIG. 9 , inserting (706) the classification identifier (708) is carried out by inserting the classification identifier (708) in the structured document (122) according to a structural insertion scope (804) for the selected presentation attribute (352).
[0070] FIG. 10 sets forth a data flow diagram illustrating a further exemplary method for classifying a structural element (402) in a structured document (122) that includes providing a list (712) of supported presentation attributes (352) including at least one data pattern (810) and at least one indication of structural insertion scope (804) for each presentation attribute (352). In the method of FIG. 10 , identifying (702) a presentation attribute (352) for the structural element (402) includes selecting (814) a presentation attribute (352) from the list (712) in dependence upon a data pattern (812) from the structured document (122). In the method of FIG. 10 , identifying (704) a classification identifier (708) is carried out by identifying a classification identifier (708) associated with the presentation attribute (352) on the list (712). In the method of FIG. 10 , inserting (706) the classification identifier (708) is carried out by inserting the classification identifier (708) in the structured document (122) according to a structural insertion scope (804) for the selected presentation attribute (352).
[0071] Methods of providing collaborative event media content are further explained with an exemplary use case. Consider the following example of a structured document:
[0072]
| <document> | |
| <page id=“1”> | |
| <p id=“1”> | |
| a paragraph on an introductory subject | |
| </p> | |
| </page> | |
| <page id=“2”> | |
| <p id=“2”> | |
| a map paragraph on a particular subject | |
| </p> | |
| <tech level=“2”> | |
| <p id=“2”> | |
| a more technical paragraph on the same subject | |
| </p> | |
| </tech> | |
| <security level=“2”> | |
| <p id=“2”> | |
| a more secret paragraph on the same subject | |
| </p> | |
| </security> | |
| <dept id=“marketing”> | |
| <p id=“2”> | |
| a paragraph on the same subject with added detail | |
| regarding marketing | |
| </p> | |
| </dept> | |
| <company id=“IBM”> | |
| <p id=“2”> | |
| a paragraph on the same subject with added detail | |
| pertinent to a collaborator's company | |
| </p> | |
| </company> | |
| <p id=“3”> | |
| a paragraph on a further subject | |
| </p> | |
| ... ... ... | |
| </page> | |
| <page id=“3”> | |
| ... ... ... | |
| </page> | |
| ... ... ... | |
| </document> | |
[0073] This example is generally discussed assuming that this exemplary structured document is associated with a grammar that includes presentation action identifiers for paragraphs. In this example, when context changes for a client identify an event, a set of collaborators are identified and structural elements of the structured document of collaborative even media content are transmitted to the identified collaborators. In this example when a structural element of the first page of the structured document is transmitted to a collaborator and the collaborator speaks the words “next page,” a voice response server parses the speech into a presentation control instruction with a presentation action identifier named “PgDn” and communicates the presentation control instruction to display the next page, in this example, page 2 of the structured document.
[0074] Assume further that there are five collaborators selected in dependence upon the event created by changed client contexts and note that there are five different versions of paragraph 2 on page two of the structured document. In this example, a first version of paragraph 2 bears a structural identifier <p></p> identifying it as a paragraph, but this first version of paragraph 2 bears no classification identifier. In this example, the unclassified version of paragraph 2 is displayed to all collaborators having either the lowest technical classifications, the lowest security classifications, or no particular technical or security classifications at all. Moreover, an example, where there were only one version of paragraph 2, all collaborators would be presented with that one version.
[0075] In this example, a second version of paragraph 2 is classified with a classification identifier <tech level=“2”>. In this example, the second version of paragraph 2 is displayed to collaborators having collaborator classification indicating technical level 2. That is, when a collaborator having technical level 2 in the collaborators profile classifications is selected in dependence upon events created by changed client contexts, rather than displaying an unclassified version of paragraph 2, the second version of paragraph 2 classified <tech level=“2”> is displayed to such a collaborator.
[0076] Similarly, a collaborator having a profile classification representing a heightened security authorization, security level 2, is shown the version of paragraph 2 classified by the classification identifier <security level=“2”>. A collaborator having a collaborator profile classification identifying the collaborator as a member of the marketing department is shown the version of paragraph 2 classified by the classification identifier <dept id=“marketing”>. A collaborator having a profile classification identifying the collaborator as an employee of IBM is shown the version of paragraph 2 classified by the classification identifier <company id=“IBM”>.
[0077] For purposes of clarity of explanation, the structural elements in this example are shown with only one classification per element. Persons of skill in the art will recognize, however, that it is well within the scope of the present invention for a structural element of a structured document to be classified with any number of classification identifiers.
Delivering Dynamic Media Content to Collaborators
[0078] For further explanation, FIG. 11 sets forth a flowchart illustrating an exemplary method for delivering dynamic media content to collaborators that includes providing (232) collaborative event media content (266). In the method of FIG. 11 , the collaborative event media content (266) includes a grammar (258) and a structured document (122). In the method of FIG. 11 , providing (232) collaborative event media content (266) is carried out by creating, in dependence upon original media content, a structured document and creating a grammar for the collaborative event media content (266) as discussed in more detail above with reference to FIGS. 3-10 .
[0079] The method of FIG. 11 includes generating (234) a dynamic client context (236) for a client. In the method of FIG. 11 , generating (234) a dynamic client context (236) is carried out by acquiring data that describes the client and the client's environment and storing the data describing the client and the client's environment in a context server.
[0080] The method of FIG. 11 includes detecting (238) an event (168) in dependence upon the dynamic client context (206). For further explanation of detecting events, FIG. 12 sets a forth flow chart illustrating an exemplary method for detecting (238) an event (168) in dependence upon a dynamic client context (236). The method of FIG. 12 includes detecting (256) a change in a value of a data element in the dynamic client context (236) and applying (262) rules from event detection rules base (164) to the dynamic client context (164) to determine whether an event has occurred.
[0081] In the method of FIG. 12 , detecting (256) a change in a value of a data element in the dynamic client context (236) is carried out by comparing data values in a current dynamic client context (236) with corresponding values from a previous dynamic client context (235) for the same client. If there is any change (256), the method of FIG. 12 proceeds by applying (262) rules from a rules base (164) to determine whether the context data as changed represents an event. If there is no change in the context data (260), the method of FIG. 12 proceeds by saving (268) the current dynamic client context as a previous dynamic client context and continuing to generate (234) dynamic client contexts as client data comes in. If an event is recognized according to the rules from the rules base, the method of FIG. 12 creates an event object (168) of an event type (242).
[0082] As mentioned above, the method of FIG. 12 may create an event object by passing an event type identified by the rules base to an object oriented parameterized event creation factory method in an event factory object. Such an event factory instantiates and returns an object of a concrete event class named, for example, fireEvent, carWreckEvent, hazMatEvent, gunEvent, burglaryEvent, and so on, as will occur to those of skill in the art, derived from an abstract event class. The abstract class declares member data elements and member methods needed by all concrete event classes in the system. Each concrete event class is augmented with member data elements and member methods as needed to address particular kinds of events, fires, automobile accidents, hazardous materials spills identified by chemical sensors, firearms presence identified by metal detectors, burglaries identified by motion detectors, and so on.
[0083] When an event generator instantiates an event object, the event generator typically may include in the event object a reference to one or more dynamic client context objects, including the current dynamic client context object whose changes in data values triggered the event, but also one or more previous dynamic client context objects so that an action engine may have previous data values as needed. Alternatively, a concrete event class may include all the data elements needed for action preparation, so that only the data values are loaded from the pertinent dynamic client contexts rather than including the dynamic client contexts themselves, object built from them, or object oriented references or pointers to them.
[0084] Again referring to FIG. 11 : The method of FIG. 11 includes identifying (240) one or more collaborators (182) in dependence upon the dynamic client context (236) and the event (168). As mentioned above in connection with the description of the system of FIG. 1 , event (168) contains not only its event type (242), but also all the data needed to develop actions in response to the event, including data from or references to objects built from pertinent dynamic client contexts (236). Identifying collaborators typically is carried out by applying collaborator selection rules to the event type (242) to identify from a collaborator profile database a collaborator for the event. Collaborator profiles are data structures, such as those shown for example at reference (182) on FIG. 2 , often implemented as records in a collaborator profile database (184) that include data elements describing a collaborator, including, for example, collaborator name, collaborator identification code, collaborator physical location, collaborator type or classification code (EMS, police, wife, accountant, lawyer, HazMat Responder, and so on), and a list (681 on FIG. 2 ) of one or more event types in which a collaborator may collaborate. Collaborator selection rules are implemented to identify collaborators on the basis of event type, collaborator presence on a instant messaging network, client location, collaborator location, and collaborator type or classification.
[0085] The method of FIG. 11 includes selecting (246) from the structured document (122) a classified structural element (402) in dependence upon an event type (242) and a collaborator classification (244). Selecting a classified structural element can be carried out by selecting a classified structural element having an associated classification identifier that corresponds to the collaborator classification. Alternatively, selecting a classified structural element can be carried out by selecting a classified structural element in dependence upon characteristics of a collaborator's display device. In such examples, the selected structural element has an associated classification identifier that corresponds to a display device ID stored in the collaborator's profile. Selecting structural elements in dependence upon the device characteristics of the display device advantageously facilitates selecting structural elements that are most compatible with the collaborator's display device.
[0086] The method of FIG. 11 includes transmitting (248) the selected structural element (402) to the collaborator (182). In the method of FIG. 11 transmitting (248) the selected structural element (402) to the collaborator (182) is carried out by: selecting a data communications protocol for communications with a collaborator; inserting the selected structural element in a data structure appropriate to the data communications protocol; and transmitting the data structure to the collaborator according to the data communications protocol.
[0087] For Further explanation FIG. 13 sets forth a data flow diagram illustrating a further exemplary method for selecting classified structural elements and transmitting them to a collaborator. The method of FIG. 13 enables delivery of collaborative event media content to collaborators according to a wide variety of organizational membership, technical knowledge, security authorization, and so on, across almost any dimension in which participants may vary. Such delivery is accomplished generally in methods and systems according to embodiments of the present invention: by use of structured, classified collaborative event media content, which typically is made up of a grammar and a structured document. Using such documents as a source of presentation content, collaborative event media content is delivered by selecting from a structured document classified structural elements for delivery to particular collaborators according to the classification identifiers in the document and collaborator classifications or type codes from collaborator profiles.
[0088] The method of FIG. 13 includes providing (450) collaborative event media content (266) for use in responding to events generated by changes in dynamic client contexts. In the method of FIG. 13 , the collaborative event media content (266) includes a grammar (258) and a structured document (122), and providing (450) collaborative event media content (266) is carried out by as described in detail above with reference to FIGS. 3-10 .
[0089] The method of FIG. 13 also includes creating (462) a presentation control instruction (460). A presentation control instruction is an instruction to an action engine (170) to carry out a particular presentation action such as, for example, ‘display next page,’ ‘display next slide,’ ‘display paragraph 5,’ ‘send a map of client's location,’ ‘send travel directions to client's location,’ and so on as will occur to those of skill in the art. More particularly, in collaborative event media content delivery, presentation actions are carried out by presenting to a particular collaborator a version of a particular structural element, such as a paragraph, a slide, a map, and so on, according to collaborator classifications such as organization name, security authorization, technical expertise level, and so on. In the method of FIG. 13 , an exemplary presentation control instruction (460) includes a presentation action identifier (518) and one or more optional parameters (520).
[0090] In the method of FIG. 13 , creating the presentation control instruction is carried out by receiving (464) from a collaborator (182) a key phrase (516) and optional parameters (520) for invoking a presentation action and parsing (466) the key phrase (516) and parameters (520) against a grammar (258) into a presentation control instruction (460). The grammar (258) used in the voice response server (104) may be developed specially for voice response service or may be the same grammar (258) used in the collaborative event media content with the structured document (122).
[0091] In this example, receiving (464) a key phrase (516) is carried out by use of a Voice Over Internet Protocol (“VOIP”) link (130) that carries the speech of at least one collaborator (182) from the collaborator's communications device to a voice response server (104). A VOIP link is a kind of computer hardware and software that uses an internet protocol network instead of a traditional telephone network as the transmission medium for speech. VOIP is sometimes referred to as ‘IP telephony’ or ‘Voice Over the Internet’ (“VOI”). Examples of user client devices include any computer equipment capable of converting input speech to digital data and transmitting it over the internet protocol to a voice response server, including handheld wireless devices, personal digital assistants, personal computers, laptop computers, and the like.
[0092] The method of FIG. 13 also includes receiving (458) a presentation control instruction (460) in an action engine (170) and selecting (452) from a structured document (122) a classified structural element (402) in dependence upon collaborator classifications (210) of a collaborator (182). In the method of FIG. 13 , selecting (452) a classified structural element (402) is carried out by selecting a classified structural element (402) in dependence upon the presentation action identifier (518) and the parameters (520) from the presentation control instruction (460). In the method of FIG. 13 , selecting (452) a classified structural element (402) also includes selecting a classified structural element having an associated classification identifier (708) that corresponds to the collaborator classification (210).
[0093] For further explanation, consider an example using the following exemplary structured document:
[0094]
| <collaborativeEventMediaContent> | |
| <Grammar> | |
| <grammarElement> | |
| <contentType id=“WP”> | |
| <keyPhrase>page down</keyPhrase> | |
| <presentationAction id=“PgDn”> | |
| <structuralElementIdentifier id=“page”> | |
| </grammarElement > | |
| </Grammar> | |
| <structuredDocument> | |
| <page id=“1”> | |
| <p id=“1”> a paragraph </p> | |
| <p id=“2”> another paragraph </p> | |
| </page> | |
| <page id=“2”> | |
| <p id=“2”>a paragraph on a particular subject</p> | |
| <tech level=“2”> | |
| <p id=“2”>a more technical paragraph, same | |
| subject</p> | |
| </tech> | |
| <company id=“IBM”> | |
| <p id=“2”>a paragraph, same subject with added detail | |
| pertinent to a user's company</p> | |
| </company> | |
| <p id=“3”>a paragraph on some other subject</p> | |
| ... ... ... | |
| </page> | |
| </structuredDocument> | |
| </collaborativeEventMediaContent> | |
[0095] In this example, assume that a first collaborator has in a collaborator profile collaborator classifications indicating that the collaborator is an IBM employee and a second collaborator has collaborator classifications indicating that the collaborator has technical ability level ‘2’. In this example, an action engine receives (458) a presentation control instruction (460) to move to the display to the second page of the structured document. The action engine then selects (452) from the structured document (256) for the first collaborator the structural element identified as a version of page two and classified as:
[0096]
and for the second collaborator the structural element identified as a version of page two and classified as:
| <company id=“IBM”> | |
| <p id=“2”>a paragraph, same subject with added detail pertinent to a | |
| collaborator's company</p> | |
| </company> | |
and for the second collaborator the structural element identified as a version of page two and classified as:
[0097]
| <tech level=“2”> | |
| <p id=“2”>a more technical paragraph, same subject</p> | |
| </tech> | |
[0098] The method of FIG. 13 also includes transmitting (248) the selected structural element (456) to the collaborator (182). In the method of FIG. 13 , transmitting (248) the selected structural element (456) to the collaborator may be carried out, for example, by selecting a data communications protocol for the presentation, inserting the selected structural element (without its classification identifiers) in a data structure appropriate to the data communications protocol, and transmitting the data structure to the collaborator according to the data communications protocol. If, for example, the data communications protocol is selected as HTTP, a data structure appropriate to the data communications protocol is an HTML document in an HTTP RESPONSE message. In such an example, transmitting (248) the selected structural element (456) to the collaborator may be carried out, for the two exemplary versions of page two selected above, by the following HTTP RESPONSE messages:
[0099]
and for the second collaborator the structural element identified as a version of page two and classified as:
| HTTP/1.1 200 OK |
| Date: |
| Content-Type: text/xml |
| Content-Length: 128 |
| <html><body><p id=“2”>a paragraph, same subject with added detail |
| pertinent to a collaborator's company</p> </body></html> |
and for the second collaborator the structural element identified as a version of page two and classified as:
[0100]
respectively, the first sent to the communications device of the first collaborator and the second sent to the communications device of the second collaborator. Note that in both transmissions, the classification identifiers are omitted, <company id=“IBM”> and <tech level=“2”> respectively.
| HTTP/1.1 200 OK | |
| Date: | |
| Content-Type: text/xml | |
| Content-Length: 103 | |
| <html><body><p id=“2”>a more technical paragraph, same | |
| subject</p></body></html> | |
respectively, the first sent to the communications device of the first collaborator and the second sent to the communications device of the second collaborator. Note that in both transmissions, the classification identifiers are omitted, <company id=“IBM”> and <tech level=“2”> respectively.
[0101] This example of transmitting (248) a selected structural element (456) to a collaborator (182) is expressed in terms of HTML and HTTP, a stateless, asynchronous protocol. Many embodiments will statefully hold open a data communications connection, such as a TCP/IP connection, between a presentation server and a collaborator communication device. A Stateful Java Enterprise Session Bean™ may be used, for example, to hold open a TCP/IP connection implemented with a Java socket object. Readers of skill in the art will recognize therefore that HTML and HTTP are used for explanation, not for limitation. In fact, any presentation application using any appropriate data communications protocol useful for multi-media presentations may be used to present structural elements to collaborators according to embodiments of the present invention. Such application may be obtained off-the-shelf commercially or they may be specially developed for particular presentations or kinds of presentation. An example of such an application available commercially is Microsoft NetMeeting™. Examples of other data communications protocols useful with various embodiments of the present invention include the Session Initiation Protocol specified in the IETF's RFC 2543, the Real Time Streaming Protocol as specified in the IETF's RFC 2326, the Real Time Transport Protocol of RFC 1889, and the World Wide Web Consortium's VoiceXML protocol specified in the 2003 document entitled “Voice Extensible Markup Language (VoiceXML) Version 2.0”.
[0102] For further explanation, FIG. 14 sets forth a flow chart illustrating an exemplary method for generating a dynamic client context (236) for a client that includes providing (550) data (554) identifying a client's location and storing (552), in the context server (160) in a data structure comprising a dynamic client context (236) for the client (154), the data (554) identifying the client's location. In the method of FIG. 14 , providing (550) to a context server (160) data identifying a client's location may be carried out by GPS coordinates from a GPS receiver (560) and storing (552) the data identifying the client's location may be carried out by storing the GPS coordinates in the dynamic client context (236) for the client (154).
[0103] In the method of FIG. 14 , providing (220) to a context server (160) data identifying a client's location may also be carried out by querying (558) a router for a physical address of the router; and storing (552) the data identifying the client's location may be carried out by storing the physical address of the router (558) in the dynamic client context (236) for the client (154). Router (558) may, for example, provide a wireless access point (560) to an internet, a so-called Wi-Fi connection or ‘hotspot,’ through which portable computers effect wireless connection to the World Wide Web, for example. For such connections, the client may not be configured with its physical address and so therefore advantageously may query the router through the OSI link layer, through an ARP (Address Resolution Protocol) query, for example, for the physical address of the router. This method is useful for 802.11b-type wireless connections, for example, because in order to effect such connections, the client must be located physically close enough to the router so that the router's physical address is a good approximation for the physical address of the client.
[0104] In the method of FIG. 14 , providing (550) to a context server (160) data identifying a client's location may be carried out by querying a router (558) for a physical address of the client (154) and storing (552) the data identifying the client's location may be carried out by storing (552) the physical address of the client (154) in the dynamic client context (236) for the client (154). Router (558) may, for example, provide a wired (561) network connection for a client (154), in which case the physical location of the router, even if it is known, may provide inadequate precision in locating clients connected to it. Such clients could be anywhere in a large building, anywhere in a large campus of buildings, almost anywhere with relation to the router.
[0105] Internet protocol routers typically maintain ARP caches for use in resolving network addresses to link layer addresses. For efficient link layer address resolution, a router typically stores recently resolved network addresses in association with their corresponding link layer addresses in an ARP cache. To resolve link layer addresses into physical addresses, an ARP cache may be modified according to embodiments of the present invention to include also physical addresses of clients connected to a network through a router.
[0106] An example of an ARP cache modified according to embodiments of the present invention is shown in Table 2. Routers may serve more than only port on more than one LAN, but for ease of explanation, Table 2 illustrates an ARP cache for a single LAN on a single port on a single router. Table 2 associates network layer addresses and link layer addresses in two entry types, dynamic and static. Static ARP cache entries remain in the cache. Dynamic entities store ‘learned addresses’ entered automatically by the router in response to ARP queries or DHCP (Dynamic Host Configuration Protocol) offer messages, for example, and dynamic entries are ‘aged’ for an ‘aging time.’ That is, dynamic ARP cache entries time out according to the cache's aging time and are then deleted from the ARP cache. Because dynamic ARP cache entries time out, ARP cache entries for resolving link layer addresses into physical locations advantageously are typically created as static ARP cache entries.
[0107]
| TABLE 2 | |||
|---|---|---|---|
| Exemplary ARP Cache | |||
| Network Layer | |||
| Address | Link Layer Address | Physical Address | Type |
| 199.199.40.1 | 00 00 0c 1a eb c5 | 504 Lavaca | Static |
| 00 dd 01 07 57 15 | Bldg 1, Rm 5 | Static | |
| 10.57.10.32 | 00 60 8c 0e 6c 6a | 302 Congress | Static |
| 199.199.40.124 | 00 11 2c 1c ef c4 | Dynamic | |
[0108] Table 2 includes three static ARP cache entries that resolve client's link layer addresses to physical addresses. Note that the second such entry remains in the cache even though the DHCP of its network address has expired. It remains in the cache because the link layer address is unique to a device connected to the routers, and the method of FIG. 14 therefore will resolve that client's physical address given its link layer address regardless whether that client has a current network address. A client may query a router for the client's physical address by use of new or modified request/response messages in the Internet Control Message Protocol (‘ICMP’), the Internet Protocol (‘IP’), the link layer itself as in a new or modified Ethernet message type, and in other ways as will occur to those of skill in the art.
[0109] For further explanation, FIG. 15 sets forth a flow chart illustrating another exemplary method for generating a dynamic client context (236) for a client that includes acquiring (572) data (547) representing a client's environmental condition and storing (576), in the context server (160) in a data structure comprising a dynamic client context (236) for the client (154), the data (574) representing a client's environmental condition. In the method of FIG. 15 , acquiring data representing a client's environmental condition may be carried out by receiving asynchronously from environmental sensors data representing a client's environmental condition. In the method of FIG. 15 , the dynamic client context may include network addresses for environmental sensors for a client and acquiring data representing a client's environmental condition may be carried out by the context server's polling of the environmental sensors for the client.
[0110] It will be understood from the foregoing description that modifications and changes may be made in various embodiments of the present invention without departing from its true spirit. The descriptions in this specification are for purposes of illustration only and are not to be construed in a limiting sense. The scope of the present invention is limited only by the language of the following claims.
Claims
What is claimed is:
1. A method for delivering dynamic media content to collaborators, the method comprising:
providing collaborative event media content, wherein the collaborative event media content further comprises a grammar and a structured document including:
creating, in dependence upon original media content, a structured document, the structured document further comprising one or more structural elements;
creating a grammar for the collaborative event media content, wherein the grammar includes grammar elements each of which includes an identifier for at least one structural element of the structured document; and
classifying a structural element of the structured document according to a presentation attribute including identifying a presentation attribute for the structural element; identifying a classification identifier in dependence upon the presentation attribute; and inserting the classification identifier in association with the structural element in the structured document;
wherein the grammar comprises a data structure associating key phrases with presentation actions that facilitates a collaborator navigating the structured document of collaborative event media content using speech commands;
and wherein the method further comprises:
acquiring data representing a client's environmental condition including receiving asynchronously from environmental sensors data representing a client's environmental condition;
storing, in a context server in a data structure comprising a dynamic client context for the client, the data representing a client's environmental condition,
wherein dynamic client context includes network addresses for environmental sensors for a client and wherein acquiring data representing a client's environmental condition further comprises the context server's polling of the environmental sensors for the client;
and wherein the method further comprises:
detecting an event in dependence upon the dynamic client context including detecting a change in a value of a data element in the dynamic client context;
identifying one or more collaborators in dependence upon the dynamic client context and the event including identifying a collaborator in dependence upon collaborator presence on a instant messaging network; and
selecting from the structured document a classified structural element in dependence upon an event type and a collaborator classification; and
transmitting the selected structural element to the collaborator including selecting a data communications protocol for communications with a collaborator, inserting the selected structural element in a data structure appropriate to the data communications protocol, and transmitting the data structure to the collaborator according to the data communications protocol.
Patent Citations (161)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3644674(A) | 1972-02-01 | Mitchell et al. | Applicant |
| US4941187(A) | 1990-07-01 | Slater | Applicant |
| US5119465(A) | 1992-06-01 | Jack et al. | Applicant |
| US5181162(A) | 1993-01-01 | Smith et al. | Applicant |
| US5327176(A) | 1994-07-01 | Forler et al. | Applicant |
| US5388185(A) | 1995-02-01 | Terry et al. | Applicant |
| US5428400(A) | 1995-06-01 | Landis et al. | Applicant |
| US5649223(A) | 1997-07-01 | Freeman | Applicant |
| US5724416(A) | 1998-03-01 | Folandare et al. | Applicant |
| US5745682(A) | 1998-04-01 | Keenan | Applicant |
| US5748186(A) | 1998-05-01 | Raman | Applicant |
| US5748725(A) | 1998-05-01 | Kubo | Applicant |
| US5774879(A) | 1998-06-01 | Custy et al. | Applicant |
| US5787175(A) | 1998-07-01 | Carter | Applicant |
| US5881373(A) | 1999-03-01 | Elofsson et al. | Applicant |
| US5901230(A) | 1999-05-01 | Walker | Applicant |
| US5917480(A) | 1999-06-01 | Tafoya et al. | Applicant |
| US5983227(A) | 1999-11-01 | Nazem et al. | Applicant |
| US6029043(A) | 2000-02-01 | Ho et al. | Applicant |
| US6049332(A) | 2000-04-01 | Boetje et al. | Applicant |
| US6052730(A) | 2000-04-01 | Felciano et al. | Applicant |
| US6058416(A) | 2000-05-01 | Mukherjee et al. | Applicant |
| US6092155(A) | 2000-07-01 | Olnowich | Applicant |
| US6119147(A) | 2000-09-01 | Toomey et al. | Applicant |
| US6138040(A) | 2000-10-01 | Nicholls et al. | Applicant |
| US6161112(A) | 2000-12-01 | Cragun et al. | Applicant |
| US6163768(A) | 2000-12-01 | Sherwood et al. | Applicant |
| US6172640(B1) | 2001-01-01 | Durst et al. | Examiner |
| US6212275(B1) | 2001-04-01 | Akhteruzzaman | Applicant |
| US6243454(B1) | 2001-06-01 | Eslambolchi | Applicant |
| US6243464(B1) | 2001-06-01 | Eslambolchi | Applicant |
| US6249281(B1) | 2001-06-01 | Chen et al. | Applicant |
| US6266691(B1) | 2001-07-01 | Watanabe et al. | Applicant |
| US6269336(B1) | 2001-07-01 | Ladd et al. | Applicant |
| US6269398(B1) | 2001-07-01 | Leong et al. | Applicant |
| US6304283(B1) | 2001-10-01 | Kitagawa | Applicant |
| US6314402(B1) | 2001-11-01 | Monaco et al. | Applicant |
| US6324499(B1) | 2001-11-01 | Lewis et al. | Applicant |
| US6349136(B1) | 2002-02-01 | Light et al. | Applicant |
| US6366578(B1) | 2002-04-01 | Johnson | Applicant |
| US6393460(B1) | 2002-05-01 | Gruen et al. | Applicant |
| US6446096(B1) | 2002-09-01 | Holland et al. | Applicant |
| US6448980(B1) | 2002-09-01 | Kumar et al. | Applicant |
| US6452915(B1) | 2002-09-01 | Jorgensen | Applicant |
| US6470384(B1) | 2002-10-01 | O'Brien et al. | Applicant |
| US6493671(B1) | 2002-12-01 | Ladd et al. | Applicant |
| US6505195(B1) | 2003-01-01 | Ikeda et al. | Applicant |
| US6636238(B1) | 2003-10-01 | Amir et al. | Applicant |
| US6647531(B2) | 2003-11-01 | Isaac et al. | Applicant |
| US6658414(B2) | 2003-12-01 | Bryan et al. | Applicant |
| US6665715(B1) | 2003-12-01 | Houri | Examiner |
| US6681247(B1) | 2004-01-01 | Payton | Applicant |
| US6717593(B1) | 2004-04-01 | Jennings | Applicant |
| US6725199(B2) | 2004-04-01 | Brittan et al. | Applicant |
| US6725256(B1) | 2004-04-01 | Albal et al. | Applicant |
| US6766368(B1) | 2004-07-01 | Jakobson et al. | Applicant |
| US6799208(B1) | 2004-09-01 | Sankaranarayan et al. | Applicant |
| US6819338(B2) | 2004-11-01 | Heasman et al. | Applicant |
| US6829745(B2) | 2004-12-01 | Yassin et al. | Applicant |
| US6879968(B1) | 2005-04-01 | Kojima et al. | Applicant |
| US6931254(B1) | 2005-08-01 | Egner et al. | Applicant |
| US6981263(B1) | 2005-12-01 | Zhang et al. | Applicant |
| US7000183(B1) | 2006-02-01 | Crawford, Jr. | Applicant |
| US7003550(B1) | 2006-02-01 | Cleasby et al. | Applicant |
| US7058890(B2) | 2006-06-01 | George et al. | Applicant |
| US7079712(B1) | 2006-07-01 | Silverbrook et al. | Applicant |
| US7099920(B1) | 2006-08-01 | Kojima et al. | Applicant |
| US7149694(B1) | 2006-12-01 | Harb et al. | Applicant |
| US7162692(B2) | 2007-01-01 | Bodin et al. | Applicant |
| US7174557(B2) | 2007-02-01 | Sanghvi et al. | Applicant |
| US7249157(B2) | 2007-07-01 | Stewart et al. | Applicant |
| US7283621(B2) | 2007-10-01 | Quinton | Applicant |
| US7287093(B2) | 2007-10-01 | Lynch et al. | Examiner |
| US7287221(B2) | 2007-10-01 | Bodin et al. | Applicant |
| US7299405(B1) | 2007-11-01 | Lee et al. | Applicant |
| US7313595(B2) | 2007-12-01 | Rust | Applicant |
| US7334050(B2) | 2008-02-01 | Zondervan et al. | Applicant |
| US7395505(B1) | 2008-07-01 | Khosla et al. | Applicant |
| US7426538(B2) | 2008-09-01 | Bodin et al. | Applicant |
| US7428698(B2) | 2008-09-01 | Bodin et al. | Applicant |
| US7430707(B2) | 2008-09-01 | Bodin et al. | Applicant |
| US7487208(B2) | 2009-02-01 | Bodin et al. | Applicant |
| US7487209(B2) | 2009-02-01 | Bodin et al. | Applicant |
| US7487451(B2) | 2009-02-01 | Bodin et al. | Applicant |
| US7519659(B2) | 2009-04-01 | Bodin et al. | Applicant |
| US7519683(B2) | 2009-04-01 | Bodin et al. | Applicant |
| US7519904(B2) | 2009-04-01 | Bodin et al. | Applicant |
| US7567908(B2) | 2009-07-01 | Bodin et al. | Applicant |
| US7571380(B2) | 2009-08-01 | Bodin et al. | Applicant |
| US7603112(B2) | 2009-10-01 | Huomo et al. | Examiner |
| US7634412(B2) | 2009-12-01 | Bodin et al. | Applicant |
| US2001/0032218(A1) | 2001-10-01 | Huang | Applicant |
| US2001/0041973(A1) | 2001-11-01 | Abkowitz et al. | Applicant |
| US2001/0054048(A1) | 2001-12-01 | Kelsey | Applicant |
| US2002/0032564(A1) | 2002-03-01 | Ehsani et al. | Applicant |
| US2002/0035976(A1) | 2002-03-01 | Nakamura et al. | Applicant |
| US2002/0087416(A1) | 2002-07-01 | Knutson | Applicant |
| US2002/0087974(A1) | 2002-07-01 | Sprague | Applicant |
| US2002/0095454(A1) | 2002-07-01 | Reed et al. | Applicant |
| US2002/0129354(A1) | 2002-09-01 | Bryan et al. | Applicant |
| US2002/0133500(A1) | 2002-09-01 | Arlein et al. | Applicant |
| US2002/0138331(A1) | 2002-09-01 | Hosea et al. | Applicant |
| US2002/0147782(A1) | 2002-10-01 | Dimitrova et al. | Applicant |
| US2002/0152301(A1) | 2002-10-01 | Garrett et al. | Applicant |
| US2002/0188451(A1) | 2002-12-01 | Guerra et al. | Applicant |
| US2003/0023435(A1) | 2003-01-01 | Josephson | Applicant |
| US2003/0028871(A1) | 2003-02-01 | Wang et al. | Applicant |
| US2003/0037301(A1) | 2003-02-01 | Rising, III | Applicant |
| US2003/0041238(A1) | 2003-02-01 | French et al. | Applicant |
| US2003/0065712(A1) | 2003-04-01 | Cheung et al. | Examiner |
| US2003/0071833(A1) | 2003-04-01 | Dantzig et al. | Applicant |
| US2003/0099343(A1) | 2003-05-01 | Dezonno | Applicant |
| US2003/0158969(A1) | 2003-08-01 | Gimson et al. | Applicant |
| US2003/0208473(A1) | 2003-11-01 | Lennon | Applicant |
| US2004/0006595(A1) | 2004-01-01 | Yeh et al. | Applicant |
| US2004/0107404(A1) | 2004-06-01 | Burns et al. | Applicant |
| US2004/0141016(A1) | 2004-07-01 | Fukatsu et al. | Applicant |
| US2004/0193425(A1) | 2004-09-01 | Tomes | Applicant |
| US2004/0204979(A1) | 2004-10-01 | Eisenberg et al. | Applicant |
| US2004/0205081(A1) | 2004-10-01 | Chao | Applicant |
| US2004/0205114(A1) | 2004-10-01 | Kinoshita | Applicant |
| US2004/0205132(A1) | 2004-10-01 | Czerwonka | Applicant |
| US2004/0205452(A1) | 2004-10-01 | Fitzsimons et al. | Applicant |
| US2004/0205572(A1) | 2004-10-01 | Fields et al. | Applicant |
| US2004/0205629(A1) | 2004-10-01 | Rosenholtz et al. | Applicant |
| US2005/0025136(A1) | 2005-02-01 | Anschutz et al. | Applicant |
| US2005/0131944(A1) | 2005-06-01 | Patrick et al. | Applicant |
| US2005/0132271(A1) | 2005-06-01 | Bodin et al. | Applicant |
| US2005/0132273(A1) | 2005-06-01 | Bodin et al. | Applicant |
| US2005/0132274(A1) | 2005-06-01 | Bodin et al. | Applicant |
| US2005/1013227 | 2005-06-01 | Bodin at al. | Applicant |
| US2005/0154970(A1) | 2005-07-01 | Bodin et al. | Applicant |
| US2005/0154975(A1) | 2005-07-01 | Bodin et al. | Applicant |
| US2005/0165900(A1) | 2005-07-01 | Bodin et al. | Applicant |
| US2005/0171780(A1) | 2005-08-01 | Schmid et al. | Applicant |
| US2005/0240603(A1) | 2005-10-01 | Bodin et al. | Applicant |
| US2005/0240659(A1) | 2005-10-01 | Bodin et al. | Applicant |
| US2005/0240808(A1) | 2005-10-01 | Jones et al. | Applicant |
| US2005/0240909(A1) | 2005-10-01 | Tersigni | Applicant |
| US2006/0010365(A1) | 2006-01-01 | Bodin et al. | Applicant |
| US2006/0010370(A1) | 2006-01-01 | Bodin et al. | Applicant |
| US2006/0014546(A1) | 2006-01-01 | Bodin et al. | Applicant |
| US2006/0015557(A1) | 2006-01-01 | Bodin et al. | Applicant |
| US2006/0080614(A1) | 2006-04-01 | Lentz | Applicant |
| US2006/0277465(A1) | 2006-12-01 | Pandit et al. | Applicant |
| US2007/0250602(A1) | 2007-10-01 | Bodin et al. | Applicant |
| US2007/0266097(A1) | 2007-11-01 | Harik et al. | Applicant |
| US2008/0172227(A1) | 2008-07-01 | Bodin et al. | Applicant |
| US2008/0177837(A1) | 2008-07-01 | Bodin et al. | Applicant |
| US2008/0177838(A1) | 2008-07-01 | Bodin et al. | Applicant |
| US2008/0177866(A1) | 2008-07-01 | Bodin et al. | Applicant |
| US2008/0178078(A1) | 2008-07-01 | Bodin et al. | Applicant |
| US2008/0235028(A1) | 2008-09-01 | Bodin et al. | Applicant |
| US2008/0259910(A1) | 2008-10-01 | Bodin et al. | Applicant |
| US2008/0263435(A1) | 2008-10-01 | Bodin et al. | Applicant |
| US2008/0282168(A1) | 2008-11-01 | Bodin et al. | Applicant |
| US2009/0037820(A1) | 2009-02-01 | Bodin et al. | Applicant |
| US2009/0048829(A1) | 2009-02-01 | Bodin et al. | Applicant |
| US2009/0099842(A1) | 2009-04-01 | Bodin et al. | Applicant |
| WO1/20481 | 2001-03-01 | Applicant | |
| WO1/24462(A1) | 2001-04-01 | Applicant |
Non-Patent Literature (101)
- U.S. Appl. No. 10/285,615, filed Oct. 31, 2002, Bates.Applicant
- Engelbart; Authorship Provision in Augment; IEEE Cat. No. 84CH2017-2; Spring 1984; p. 465-472; IEEE Comput. Soc. Press, Silver Spring, MD; USA.Applicant
- Websgebg et al; Real-time Content-Based Processing of Multicast Video; Cat. No. 98CH36284; 1998; pp. 882-886, vol. 1; IEEE, Piscataway, NJ, USA; USA.Applicant
- Kim et al; An Extended Object Composition Model for Distributed Multimedia Services; Cat. No. 98CH36284; Jan. 2002; pp. 279-286, vol. 1; IEEE, Piscataway, NJ, USA; USA.Applicant
- Agawa et al.; Image Analysis for Face Modeling and Facial Image Reconstruction; SPIE; 1990; pp. 1184-1197; vol. 1360, pt 2; US.Applicant
- Kim et al.; An Extended Object Composition Model for Distributed Multimedia Supports in World-Wide Web; INSPEC AN B9810-6210R-071, C9810-6130M-080; 1997; pp. 159-174; Singapore.Applicant
- U.S. Appl. No. 10/285,615, filed Oct. 2002, Bates.Applicant
- U.S. Appl. No. 12/331,524, filed Dec. 2008, Bodin et al.Applicant
- W3C, “XHTML+Voice Profile 1.0,” Dec. 21, 2001, pp. 1-20.Applicant
- W3C, “Speech Synthesis Markup Language Version 1” Dec. 2, 2002, downloaded pp. 1-36.Applicant
- IBM, “IBM WebShere Voice Server 2.0 Implementation Guide.” IBM Redbook, May 2002, title page, copyright page, and pp. 251-276 and 291-292.Applicant
- Christian, et al. “A Comparison of Voice controlled and Mouse Controlled Web Browsing,” Assets 2000, 72-79, Arlington, VA, 2000, downloaded from: http://citeseer.its.psu.edu/373105.html, downloaded pages including CiteSeer bibliography, 1-10.Applicant
- Karl, et al., “Speech-Activated versus Mouse-Activated Commands for Word Processing Applications: An Empirical Evaluation,” Intl J. Man-Machine Studies, vol. 39, pp. 667-687, 1993, downloaded from http://hcilcs.umd.edu/trs/92-09/92-09.html, downloaded pp. 1-17.Applicant
- Damiani, et al. “A Fine-Grained Access Control System for XML Documents,” ACM Transactions on Information and System Security, vol. 5, No. 2. May 2002, pp. 169-202.Applicant
- Kudo, et al., “XML Document Security based on Provisional Authorization,” CSS'00 Athens, Greece, copyright 2000, pp. 87-96.Applicant
- Begel, et al., “SpeedNav: Document Navigation By Voice”, University of California, Berkeley, Oct. 9, 2002.Applicant
- Goose, et al., “Streaming Speech: A Framework for Generating and Streaming 3-D Text-To-Speech and Audio Presentations to Wireless PDAs as Specified Using Extensions to SMIL”, WWW2002, May 2002, p. 1-16, Honolulu, Hawaii; USA.Applicant
- Freire,et al., “Webviews: Accessing Personalized Web Content and Services”, Proceedings of the 10th International Conference on World Wide Web, May 2001, ACM Press, p. 576-586, Hong Kong.Applicant
- Wensbeng, et al; Real-time Content Based Processing of Multicast Video; Cat. No. 98CH36284; 1998; pp. 882-886, vol. 1; IEEE. Piscataway, NJ; USA.Applicant
- Kim at al; An Extended Object Composition Model for Distributed Multimedia Services; Cat. No. 98CH36284; Jan 2002: pp. 279-286, vol. 1; IEEE, Piscataway, NJ; USA.Applicant
- Agawa et al. “Image Analysis for Face Modeling and Facial Image Reconstruction” SPIE: 1990; pp. 1184-1197; vol. 1360, pt 2; USA.Applicant
- Capra, et al., “WebContext: Remote Access to Shared Context”, ACM International Conference Proceeding Series, vol. 15, Proceedings of the 2001 Workshop on Perceptive User Interfaces, 2001, p. 1-9.Applicant
- Corcoran, et al., “Home Network Infrastructure for HandheldiWearable Appliances”, IEEE Transactions on Consumer Electronics, Aug. 2002, vol. 48, Issue 3, p. 490-495.Applicant
- Komlodi et al., “Key Frame Preview Techniques for Video Browsing”, ACM 2002, pp. 118-125.Applicant
- Cruz, et al. “A Visual Approach to Multimedia Querying and Presentation” ACM 1997. pp. 109-119.Applicant
- Shumate. “Hyperizons”, Google 1997, pp. 1-3.Applicant
- Chigona at al, “Contextualized Preview of Image Map Links”, ACM 2002, pp. 150-158.Applicant
- Rao et al., Evolution of Mobile Location-Based Services. Commun. ACM 46, 12 (Dec. 2003), pp. 61-65.Applicant
- Sripanidkulchai, et al., “Efficient content location using interest-based locality in peer-to-peer systems.” Infocom 2003. Twenty-Second Annual Joint Conference of the IEEE Computer and Communications Societies. IEEE, vol. 3, pp. 2166-2176, 30 Mar.-3 Apr. 2003.Applicant
- Kimbrough et al., “Deontic Logic 2: On Original Generation of Structure in Legal Documents”. Proceedings of the 9th International Conference Artificial Intelligence and Law, Jun. 2003, pp. 152-161.Applicant
- Adelberg, Brad, “NoDoSE—A Tool for Semi-Automatically Extracting Structured and Semistructure Data from Text Documents”, ACM SIGMOD Record, vol. 27, Issue 2, Jun. 1998, pp. 283-294.Applicant
- Notice of Allowance Dated Sep. 29, 2008 0in U.S. Appl. No. 10/733,954.Applicant
- Office Action Dated Jan. 12, 2006 in U.S. Appl. No. 10/734,764.Applicant
- Office Action Dated Jun. 27, 2006 in U.S. Appl. No. 10/734,764.Applicant
- Final Office Action Dated Apr. 18, 2007 in U.S. Appl. No. 10/734,764.Applicant
- Office Action Dated Jan. 12, 2006 in U.S. Appl. No. 10/733,947.Applicant
- Office Action Dated Jun. 27, 2006 in U.S. Appl. No. 10/733,947.Applicant
- Final Office Action Dated Dec. 14, 2006 in U.S. Appl. No. 10/733,947.Applicant
- Office Action Dated May 4, 2007 in U.S. Appl. No. 10/733,941.Applicant
- Final Office Action Dated Oct. 10, 2007 in U.S. Appl. No. 10/733,941.Applicant
- Office Action Dated Jun. 12, 2008 in U.S. Appl. No. 10/733,941.Applicant
- Final Office Action Dated Dec. 5, 2008 in U.S. Appl. No. 10/733,941.Applicant
- Notice of Allowance Dated Aug. 6, 2009 in U.S. Appl. No. 10/733,941.Applicant
- Office Action Dated Jan. 10, 2006 in U.S. Appl. No. 10/733,937.Applicant
- Final Office Action Dated Jun. 1, 2006 in U.S. Appl. No. 10/733,937.Applicant
- Office Action Dated Jan. 30, 2006 in U.S. Appl. No. 10/733,943.Applicant
- Final Office Action Dated Jun. 28, 2006 in U.S. Appl. No. 10/733,943.Applicant
- Office Action Dated Feb. 27, 2006 in U.S. Appl. No. 10/733,942.Applicant
- Notice of Allowance Dated Jul. 19, 2006 in U.S. Appl. No. 10/733,942.Applicant
- Office Action Dated Mar. 8, 2006 in U.S. Appl. No. 10/756,159.Applicant
- Final Office Action Dated Aug. 31, 2006 in U.S. Appl. No. 10/756,159.Applicant
- Notice of Allowance Dated Jun. 19, 2007 in U.S. Appl. No. 10/756,159.Applicant
- Office Action Dated Sep. 30, 2008 in U.S. Appl. No. 10/756,126.Applicant
- Notice of Allowance Dated Mar. 23, 2009 in U.S. Appl. No. 10/756,126.Applicant
- Office Action Dated Aug. 3, 2006 in U.S. Appl. No. 10/756,107.Applicant
- Office Action Dated Feb. 1, 2007 in U.S. Appl. No. 10/756,107.Applicant
- Final Office Action Dated Sep. 6, 2007 in U.S. Appl. No. 10/756,107.Applicant
- Office Action Dated Feb. 20, 2008 in U.S. Appl. No. 10/756,107.Applicant
- Notice of Allowance Dated Jun. 27, 2008 in U.S. Appl. No. 10/756,107.Applicant
- Final Office Action Dated Sep. 21, 2006 in U.S. Appl. No. 10/756,110.Applicant
- Office Action Dated Mar. 10, 2006 in U.S. Appl. No. 10/756,110.Applicant
- Office Action Dated Mar. 8, 2006 in U.S. Appl. No. 10/756,145.Applicant
- Final Office Action Dated Jan. 18, 2007 in U.S. Appl. No. 10/756,145.Applicant
- Office Action Dated Sep. 6, 2007 in U.S. Appl. No. 10/756,145.Applicant
- Notice of Allowance Dated May 19, 2008 in U.S. Appl. No. 10/756,145.Applicant
- Office Action Dated Mar. 8, 2006 in U.S. Appl. No. 10/756,146.Applicant
- Final Office Action Dated Jan. 18, 2007 in U.S. Appl. No. 10/756,146.Applicant
- Office Action Dated Mar. 22, 2006 in U.S. Appl. No. 10/756,158.Applicant
- Final Office Action Dated Aug. 29, 2006 in U.S. Appl. No. 10/756,158.Applicant
- Office Action Dated Mar. 31, 2008 in U.S. Appl. No. 10/887,516.Applicant
- Notice of Allowance Dated Sep. 24, 2008 in U.S. Appl. No. 10/887,516.Applicant
- Office Action Dated Dec. 19, 2006 in U.S. Appl. No. 10/887,517.Applicant
- Final Office Action Apr. 23, 2007 in U.S. Appl. No. 10/887,517.Applicant
- Notice of Allowance Dated May 19, 2008 in U.S. Appl. No. 10/887,517.Applicant
- Office Action Dated Jul. 25, 2006 in U.S. Appl. No. 10/887,518.Applicant
- Final Office Action Dated Apr. 11, 2007 in U.S. Appl. No. 10/887,518.Applicant
- Office Action Dated Jun. 28, 2006 in U.S. Appl. No. 10/887,430.Applicant
- Final Office Action Dated Dec. 5, 2006 in U.S. Appl. No. 10/887,430.Applicant
- Office Action Dated Jul. 10, 2008 in U.S. Appl. No. 10/887,429.Applicant
- Notice of Allowance Dated Dec. 11, 2008 in U.S. Appl. No. 10/887,429.Applicant
- Office Action Dated Apr. 4, 2008 in U.S. Appl. No. 10/832,006.Applicant
- Notice of Allowance Dated Dec. 2, 2008 in U.S. Appl. No. 10/832,006.Applicant
- Office Action Dated Aug. 6, 2008 in U.S. Appl. No. 10/832,035.Applicant
- Notice of Allowance Dated Feb. 8, 2010 in U.S. Appl. No. 10/832,035.Applicant
- Office Action Dated Jan. 23, 2008 in U.S. Appl. No. 10/832,004.Applicant
- Notice of Allowance Dated Dec. 2, 2008 in U.S. Appl. No. 10/832,004.Applicant
- Office Action Dated Apr. 9, 2007 in U.S. Appl. No. 10/889,786.Applicant
- Office Action Dated Sep. 10, 2007 in U.S. Appl. No. 10/889,786.Applicant
- Office Action Dated Mar. 24, 2008 in U.S. Appl. No. 10/889,786.Applicant
- Final Office Action Dated Dec. 23, 2008 in U.S. Appl. No. 10/889,786.Applicant
- Office Action Dated Feb. 28, 2008 in U.S. Appl. No. 10/889,817.Applicant
- Office Action Dated Aug. 26, 2008 in U.S. Appl. No. 10/889,817.Applicant
- Final Office Action Dated Feb. 27, 2009 in U.S. Appl. No. 10/889,817.Applicant
- Office Action Dated Jun. 1, 2007 in U.S. Appl. No. 10/889,787.Applicant
- Office Action Dated Oct. 17, 2007 in U.S. Appl. No. 10/889,787.Applicant
- Notice of Allowance Dated May 5, 2008 in U.S. Appl. No. 10/889,787.Applicant
- Office Action Dated Aug. 17, 2006 in U.S. Appl. No. 10/832,005.Applicant
- Final Office Action Dated Jan. 24, 2007 in U.S. Appl. No. 10/832,005.Applicant
- Office Action Dated Jan. 25, 2008 in U.S. Appl. No. 10/889,818.Applicant
- Notice of Allowance Dated Jul. 16, 2008 in U.S. Appl. No. 10/889,818.Applicant
- Notice of Allowance Dated Apr. 16, 2009 in U.S. Appl. No. 12/171,779.Applicant