Remote media call center

[0001] 1. Technical Field

[0002] The present invention relates to electronic media acquisition, indexing, storage, association, and communication. In particular, the present invention relates to enhancing existing services including call centers, news services, and police and other emergency services with electronic media obtained from a variety of sources in a uniform or ad-hoc manner.

[0003] 2. Background Information

[0004] The technologies supporting and incorporated into consumer electronics devices, driven by strong market demand, have matured rapidly and become quite powerful in a short time period. In cellular telephony, for instance, portable phones have quickly evolved from cumbersome heavy devices to miniature lightweight all purpose communicators. The level of technology integration and sophistication in portable phones has risen to the point where cell phones now incorporate digital cameras, voice annotation, email, calendaring, and appointment functions in a single package.

[0005] Similarly, miniaturization, sensitivity, and resolution advances have benefited security cameras, microphones, motion sensors, proximity sensors and other types of sensing equipment. As an example, inexpensive security cameras, less than an inch and a half in diameter, are available that provide color video and wireless image transmission to a remote surveillance location. Similarly, small high sensitivity microphones are available to supplement security images with real time audio feedback, and 3-mega pixel digital cameras are commonplace.

[0006] In other settings, however, technology has not had such a dramatic impact. For example, an emergency call center (e.g., a 911 call center) typically has limited technological resources that it can draw upon to handle emergency calls. Some call centers may only include a telephone interface to handle incoming calls, a radio dispatch interface to alert the relevant authorities, and a call routing system to direct incoming calls to the appropriate operators. As another example, an appliance maintenance hotline may simply include a telephone interface to handle incoming calls, a technician that responds to the telephone calls, and a pre-generated service manual stored on a local machine that the technician may consult while handling the call.

[0007] As a result, individuals often experience a frustrating disconnect between the capabilities associated with the devices they use on a daily basis, and services that they turn to for help or for information. In many instances individuals have the capability to capture media that would greatly improve the service they could receive from a call center, but call centers are unprepared to accept and incorporate the media into their processes. The technology gap renders call centers and other services exasperating and sometimes annoying to use. More importantly, however, the call centers and other services are less effective than they otherwise could be, and therefore, as an example, less adept at rendering aid, disseminating information, and protecting citizens through law enforcement related activities.

[0008] There is a need for addressing the problems noted above and other previously experienced.

[0009] Methods and systems consistent with the present invention provide a call center processing system. The call center processing system provides features (based on the particular implementation of the call center) that enhance the capabilities of traditional call centers. In one implementation, the call center includes a network infrastructure interface for receiving an incident report from an external network, a media database, and a processing system. The processing system may include a memory including a media aggregation program, and a processor that executes the media aggregation program.

[0010] The media aggregation program is not limited to any particular implementation or feature set. In one implementation, for example, the media aggregation program may include instructions for accepting media associated with the incident report, obtaining classification information from the external network, and obtaining incident information from the incident report. The aggregation program may also include instructions for building a media record from the incident information and the classification information, and storing the media record and the media in the media database. The media may include cell phone camera pictures, security camera video, microphone audio output, and other types of information obtained from a wide variety of sensors.

[0011] In many instances, the third party that submits the incident report also submits the first piece or pieces of related media (e.g., a cell phone camera image). However, the media aggregation program may also aggregate related media obtained from other sources. For example, the media aggregation program may also include instructions for accepting supplemental sensor media from other sensors than those by the initial submitter of the incident report and for aggregating the supplemental sensor media in the media database, optionally indexed or associated with selected incident or classification information.

[0012] Methods and systems consistent with the present invention also provide a call center investigation tool. The investigation tool may be implemented, for example, using a media database in cooperation with an investigation program. Generally, the investigation program responds to a user interface and provides search and report generation capability. For example, in one implementation, the investigation program may include instructions for accepting incident search parameters, initiating execution of an incident search in the media database based on the search parameters, and displaying a selection interface comprising media record indicia associated with matching media records returned from the incident search. The investigation program may further include instructions for displaying an investigation report interface, and accepting report components for building an investigation report in the report interface. The investigation report may include selected media records and other information relating to the incident.

[0013] In other implementations, the investigation tool includes additional or different capabilities. As one example, the investigation tool may also display an area map of the location where an incident occurred, along with incident indicia that graphically indicates the incident location. In other implementations, the investigation tool may also respond to a locator icon, as one example, a security camera icon. In response to activation of the security camera icon, the investigation program may then display sensor indicia on the area map that graphically indicate locations from which supplemental media have been obtained.

[0033] FIG. 1 shows a call center processing system 100 (“call center 100”) in communication with external networks 102 and media sensors in place in a geographical area 104. The call center 100 includes a processor 106 coupled to a network infrastructure interface 108, a memory 110, and a media database 112. The processor 106 executes programs out of the memory 110. The memory 110 holds, during processing, incident reports 114 and classification information 115. The memory 110 also holds in whole or in part processing programs including a media aggregation program 116. The media database 112 includes media records 118 that index the media 120. A display 146 provides a visual interface to the processing system 100, and, for example, presents a call center user interface 148 to the operator of the call center 100.

[0034] Included in the external networks 102 are a Public Switched Telephone Network (PSTN) 122 and a dedicated data network 124. The PSTN 122 primarily handles telephone communications between landline and mobile subscribers. To that end, the PSTN 122 may communicate with wireless base stations that bi-directionally communicate with mobile subscribers. While a significant amount of the traffic on the PSTN 122 is voice data for telephone conversations, the PSTN 122 may also support bi-directional communication of data encoded and decoded, for example, by modems or other data network interfaces to the PSTN 122.

[0035] The dedicated data network 124 primarily handles general purpose data transfers between a source and a destination. While the dedicated data network 124 may carry digitized voice samples supporting telephone conversations, its role is more general purpose in nature. Thus, the dedicated data network 124 may represent a local or wide area computer network, including the Internet, over which data of any sort may propagate.

[0036] As will be explained in more detail below, the external networks 102, regardless of implementation, support the communication of media to and from media sensors external to the call center 100. The media may take many forms, including audio and visual data that conveys information about a location in a geographical area. Generally, the media conveys information about a geographical area or incidents that have occurred, are occurring, or that may occur in the geographical area. To that end, the media may include individual images, an image slideshow of individual images captured at pre-selected intervals, a video stream (e.g., security camera footage), an audio stream, motion sensor detections, proximity sensor detections, and other informative data that conveys information about a geographical area. The media may be live, or stored and retrieved upon demand, for example, from the security company 142.

[0037] The external networks 102 communicate with media sensors in the geographical area 104. FIG. 1 shows a particular example of a geographical area 104 that extends over several blocks from Adams Street to Monroe Street and from Clinton Street to Canal Street. The media sensors include: the mobile cell phones 126 and 128; the security cameras 130, 132, and 134; the motion sensor 136; the proximity sensor 138; and the microphone 140.

[0038] A security company premise 142 is also present and may represent one or more security companies that install, monitor, and maintain the security cameras 130-134 or any other media sensor or the media captured by the sensors. Thus, the security company 142 may, for example, store recordings obtained from the media sensors for a pre-selected time before deleting the recordings from storage.

[0039] Note also that FIG. 1 shows an incident location 144 near the intersection of Canal Street and Monroe Street. The incident location specifies an approximate or exact spatial location at which an event of interest has occurred (e.g., a robbery, a broken water main, or any other incident).

[0040] The elements illustrated in FIG. 1 interoperate as explained in more detail below. Before setting forth any additional explanation, however, it is noted that all of the discussion below, regardless of the particular implementation being described, is exemplary in nature, rather than limiting. For example, although selected aspects, features, or components of the implementations are depicted as being stored in the memory 110 and media database 112, all or part of systems and methods consistent with the present invention may be stored on or read from other machine-readable media, for example, secondary storage devices such as hard disks, floppy disks, and CD-ROMs; a signal received from a network; or other forms of ROM or RAM either currently known or later developed.

[0041] Furthermore, although specific components of call center processing systems and investigation tools will be described, methods, systems, and articles of manufacture consistent with the processing systems and investigation tools may contain additional or different components. For example, the processor 106 may be a microprocessor, microcontroller, application specific integrated circuit (ASIC), discrete logic, or a combination of other types of circuits acting as explained above. Similarly, the memory 110 may be DRAM, SRAM, Flash or any other type of memory. With regard to databases, they may be separately stored and managed, incorporated into a single database, or generally logically and physically organized in many different ways. Furthermore, the databases may more generally represent data files that may be searched using techniques other than relational database queries, for example. The individual programs discussed below may be parts of a single program, separate programs, or distributed across several memories and processors.

[0042] In addition, the media sensors 126-140 may vary widely in design and implementation. For that reason, the media sensors 126-140 are not limited to the examples given above. Instead the media sensors more generally encompass devices that gather information about the geographical area 104 or incidents occurring in the geographical area 104. Thus, for example, a media sensor may take the form not only of a visible wavelength video camera, but also an infrared video camera. Other media sensors may also be employed, including vibration detectors, laser interferometers, and so forth.

Media Aggregation and Indexing

[0043] Returning to FIG. 1, the geographical area 104 encompasses several city blocks. The geographical area 104 may be of arbitrary shape and size, however. As examples, the geographical area 104 may extend over urban or rural areas that include many apartment buildings, homes, high rise office buildings, streets, businesses, and other establishments. Similarly, the geographical area 104 may instead focus more tightly on individual buildings, homes, streets, sporting arenas, or other establishments.

[0044] Regardless of the size and shape of the geographical area 104, incidents of interest may occur anywhere within the geographical area 104. For example, FIG. 1 shows an incident location 144 near the corner of Canal and Monroe Streets. Generally, the incident location 144 spatially specifies where an incident of interest has occurred. Thus, as examples, the incident location 144 may represent the intersection at which a pedestrian was hit by a cab, where a mugging took place, where an electrical wire has broken, or where any other incident of interest has occurred.

[0045] Typically, a third party (e.g., a person without any particular connection to the call center 100) may witness or experience the incident. In response, the third party may contact the call center to report the incident or to request assistance at the incident location 144. For example, when the incident is a mugging, the third party may witness the mugging and contact the call center 100 to obtain police assistance. To that end, the third party communicates with the call center 100 through the external networks 102. As one example, the third party may carry the cell phone 126, and place a wireless call to the call center 100 through the PSTN 122.

[0046] At the call center 100, the network infrastructure interface 108 communicates with the external networks 102 to receive an incident report 114 from the third party. Additionally, the media aggregation program 116 accepts media from the third party relating to the incident. As one example, the cell phone 126 may include a digital camera and a microphone that has captured visual or aural media showing the incident itself, showing the incident location 144 before, during, or after the incident, or showing a nearby location before, during, or after the incident. The third party may then instruct the cell phone 126 to transmit the media to the call center 100 in conjunction with the incident report. Additionally, the third party may provide classification information to the call center 100. The classification information and the incident report are discussed in more detail below.

[0047] When the call center receives the media, the classification information, and the incident report, the media aggregation program 116 obtains incident information, that generally may be selected from the incident report. The aggregation program 116 employs the incident information and classification information in building a media record for the incident. The aggregation program 116 stores the media record and the media received in the media database 112. As a result, the call center 100 begins to compile not only initial information concerning reported incidents, but also many different types of media over time that may help illustrate, explain, and understand the incident or the geographical area 104.

[0048] As will be explained in more detail below, the call center 100 may subsequently accept supplemental sensor media and aggregate the supplemental sensor media with the data already present in the media database 112. The supplemental sensor media may arrive at the call center 100 from any external media sensor, including the media sensors 126-140. As examples, the security camera 134 may provide video footage to the call center 100, or the motion sensor 136 may provide a detection signal to the call center 100 that indicates at what times the motion sensor 136 detected motion in its coverage area.

[0049] The call center 100 stores the supplemental media in the media database 112. For each sensor from which supplemental media arrives, the call center 100 may also receive or obtain supplemental incident information and characteristic information associated with the sensor. Thus, the call center 100, when storing the supplemental media in the media database, may also prepare a supplemental media record prepared in accordance with the supplemental incident information. As a result, the media 120 in the media database is indexed and searchable and enhances the call center 100 with a multimedia searchable support database for incident reporting and investigation. In other words, the call center 100 is not limited to short voice recordings (e.g., for a 911 call center), but has expanded capability to handle any type of media that may help interpret, explain, or investigate individual incidents.

[0050] Although the incident example presented above was a mugging reported to an emergency call center 100, the call center 100 is not limited to any particular need or use. In other implementations, the call center may represent a service center, a news agency, or another information service. In the context of a service center, for example, the third party may place an incident report to obtain technical support for a malfunctioning refrigerator. The third party may then provide media with the incident report to show pictures, video, or audio media that relate to the incident. For example, the media may show a picture of a malfunctioning automatic ice maker. In cases in which the appliance is network ready and accessible, the appliance may itself provide supplemental media (e.g., temperature, motor speed, or power consumption sensor readings) to the call center to assist with the troubleshooting process. As another example, a home owner may transmit media (e.g., a digital picture of a home cable box) to a cable television installation service in order to assist an installation technician with determining what cabling, hardware, or other installation requirements need to be met at the home in order to deliver the cable television service.

[0051] As noted above, the call center 100 aggregates the media it receives in the media database 112. The media is indexed, for example, using media records 118, to provide a searchable research and investigation database for related media. A media record 118 may be implemented in many different ways, and may, for example, incorporate information obtained from the incident report 114 or classification information.

[0052] With regard to FIG. 2, that figure shows one example implementation for an incident report 114, classification information 115, and the media record 118. As an introduction, the incident report 114, classification information 115 and media record 118 are generally implemented as multi-bit data fields that may include multi-bit subfields to represent the information explained below. The incident report 114 includes incident information that characterizes or describes the incident of interest or the geographical region 104. For example, as shown in FIG. 2, the incident report 114 includes an incident type field 202, an incident location field 204, and an incident time field 206. The incident report 114 also includes an incident description field 208, and incident parties field 210.

[0053] The classification information 115 includes a name field 212, a contact information field 214, a media information field 216, and a submitter characteristics field 218. The classification information 115 thereby characterizes the media sensor and optionally the third party providing media to the call center 100.

[0054] The media record 118 serves as an index into the media 120 stored in the media database 112. As shown, the media record 118 includes the incident report 114 and the classification information 115. The media record 118 may also include a media type field 220, a media description field 222, a media length field 224, and a media pointer field 226.

[0055] More specifically, with regard to the incident report 114, the incident type field 202 specifies the nature of the incident. The incident type 202 may, as examples, encode that the incident is a mugging, robbery, murder, general interest event, mechanical service call for a refrigerator, automobile, or trash compactor, or any other incident for which a third party might contact the call center 100.

[0056] The incident location field 204 specifies a spatial position for the incident location 144. To that end, the incident location field 204 may include, as examples, GPS coordinates, a street address or intersection, city, state, zip code, country, or a more general description of the incident location 144 (e.g., “near Union Station in Chicago”).

[0057] The incident time field 206 specifies the incident temporally. Thus, the incident time field 206 may include a date stamp, a time stamp, or the like.

[0058] The incident description field 208 provides a field in which an informative narrative of the incident may be stored. The narrative describe, as examples, the geographical location 144, weather conditions at the time, the nature or extent of the incident (e.g., the number of individuals mugged), and names and addresses of witnesses. The narrative may also include, as additional examples, the lighting conditions at the incident location 104, the nature, amount, or characteristic of property stolen, damaged, or malfunctioning, or any other indicia the describe the incident or its surroundings.

[0059] The incident parties field 210 identifies the individuals affected or acting in relation to the incident. As examples, the incident parties field 210 may set forth a name, address, and telephone number of a mugging victim or an appliance owner. The incident parties field 210 may also specify a description, identity, and contact information (when known or available) for a suspect in the incident. For example, the incident parties 210 may give a description of a mugger.

[0060] With regard next to the classification information 115, the name field 212 specifies an identifier for the source of the media that the call center 100 received. For example, the named may provide the name of the third party carrying the cell phone 126. Alternatively, for automated sensors that deliver media to the call center 100, the name 212 may specify a convenient reference label for the sensor (e.g., “Canal Street Camera 27”), a serial number, or other naming indicia.

[0061] The contact information field 214 provides access information for the person or sensor providing media to the call center 100. For example, the contact information field 214 may specify a home address, phone number, email address, or fax number. Similarly, the contact information field 214 may specify a physical location or an Internet Protocol, Ethernet, or other network address.

[0062] The media information field 216 provides a descriptor of the type of media provided to the call center 100. The media information field 216 may, as examples, denote image frames, video, audio, motion sensor response data, or the like. The media information field 216 may also set forth technical specifications of the sensor the captured the media. As examples, the technical specifications may encompass information including image resolution, frames-per-second, sample rate, color depth, encoding format, and the like.

[0063] The submitter characteristics field 218 provide a description of the individual and the sensors that send media to the call center 100. For the individual, the description may encompass variables such as age, sex, height, race, nationality, or medical conditions (if known) relating, as examples, to audio or visual impairment. For the sensor, the description may include sensor age, installation date, last service date, and other related information.

[0064] With respect to the media record 118, the media record 118 may incorporate all or part of the incident report 114 and all or part of the classification information 115. The media record 118 may also provide additional data fields, including, as examples, the media type field 220, media description field 222, media length field 224, and a media pointer field 226.

[0065] The media type field 220 indicates what form the submitted media takes. As examples, the media type may specify a digital camera image, an image slideshow, video footage, audio recording, vibration sensor reading, or another type of sensor output.

[0066] The media description field 222 provides a field supporting an informative account of the media. The media description field 222 may, for example, constitute a text based description of the content of the media, its quality, its temporal or physical proximity to one or more geographical areas, or other indicia or descriptors that help characterize the information provided in the media.

[0067] The media length field 224 sets forth a temporal duration for the media. Thus, the media length field 224 may give a duration in hours, minutes, and seconds for the media, as an example. Alternatively, the media length may specify a number of images, video frames, audio samples, or other related measures.

[0068] The media pointer field 226 provides a reference into the media database 112. The reference locates the media associated with the media record in the media database 112. As a result, the call center may employ the media pointer field 226 to quickly find and retrieve the associated media.

[0069] Additional or fewer fields may be present in the incident report 114, classification information 115, and media record 118. Thus, the incident report 114, classification information 115, and media record 118 may be tailored to the particular implementation desired.

[0070] Either the incident report 114 or the classification information 115 or both may be transmitted electronically to the call center 100. Alternatively, an operator at the call center 100 may manually complete some or all of the incident report 114 or the classification information 115 based on information received, for example, from a live caller reporting an incident.

[0071] As noted above, the aggregation program 116 in the call center 100 receives media and responsively builds the media database 112. Turning next to FIG. 3, that figure summarizes a flow diagram of one iteration of the steps taken by the aggregation program 116.

[0072] The aggregation program 116 obtains an incident report (Step 302). The incident report sets forth underlying information about the incident and provides one source of information for compiling and indexing the media 120 in the media database 112. In addition to the incident report itself, the aggregation program 116 accepts the media submitted with the incident report (Step 304), for example, by a third party. Furthermore, the aggregation program obtains classification information for the third party (Step 306).

[0073] The incident information for the incident report, the classification information, or both may originate from the third party, may be obtained using an automated menu selection tree, or may be obtained from an independent source connected to the external networks 102. For example, the call center 100 may prompt a caller to make touchtone menu selections through a tree of options, to provide a convenient mechanism for obtaining the information noted above. Thus, as one example, the menu tree may include a first level of choices for incident type 202, a second level of choices for incident time 206, a third level of choices for contact information 214, and a fourth level of choices for media information 216. In addition, the third party operating the sensor (e.g., the cell phone, Personal Data Assistant (PDA), digital camera, and so forth) may originate all or some of the classification or incident information. For example, an interactive application on a cell phone or PDA may prompt the third party for classification or incident information, and transmit that information along with the media itself to the call center 100.

[0074] In preparation for adding the received media to the media database 112, the aggregation program 116 selects, depending on the particular implementation, some or all of the incident information from the incident report 114 (Step 308). For example, the aggregation program 116 may select the incident type 202, incident location 204, and incident description 208 as information to be included in a media record. The aggregation program 116 then prepares the media record (Step 310). The media record and the media itself are stored in the media database 112 (Step 312).

[0075] Additionally, in a manner described in more detail below, the aggregation program 116 may accept supplemental media from other sensors (Step 314). In a manner similar to that noted above with regard to third party media, the aggregation program 116 obtains supplemental classification information for the supplemental sensors (Step 316). The aggregation program 116 responsively builds a media record (Step 318) and stores the media record with the supplemental media in the media database 112 (Step 320).

Media Alerts

[0076] In another implementation, the call center 100 employs the media and incident information received to provide a localized alerting service to subscriber entities. The subscriber entities may be individuals, businesses, an electronic display or notifier, or other services that subscribe to the alerting service, with or without paying a fee. Generally, the subscriber entities may be any individual, device, or service for which the call center evaluates whether to send an incident alert. Whether an incident alert is sent may depend on may factors, including information provided by the subscriber entity that specifies what incidents are of interest, the severity level of the incident (e.g., a mugging, rape, or murder may always warrant an incident alert), the location or proximity of the incident (e.g., close to home, school, or work), the relationship (e.g., a son, mother, or friend) of the subscriber entity to parties involved in the incident (e.g., as noted in the incident parties field 210), or any other criteria.

[0077] As shown in FIG. 4, the call center 400 may incorporate dispatch services. For example, the memory 110 may optionally incorporate a dispatch program 402, a subscriber entity database 404 that stores entity records 406, and a subscriber location database 408 that stores location records 410. Alternatively, the call center 100 may communicate over the external networks 102 to make inquiries to a subscriber location provider 412 that may itself maintain a subscriber location database 414 that stores location records 416. An incident coverage area 418 is illustrated that encompasses a geographical region around the incident location 144.

[0078] In operation, the call center 400 receives an incident report that sets forth pertinent information about the incident. Based on the incident information, the call center 400 may determine that an incident alert should be issued to subscriber entities. The call center 400 may make the determination based on the type of incident (e.g., a violent act that may automatically qualify for alerting), and optionally based on the types of incidents for which the subscriber entities have indicated that they should be alerted.

[0079] The call center 400 exercises control over which subscriber entities it will alert. For example, as shown in FIG. 4, the call center 400 may alert the subscriber entities in the incident coverage area 418. Although the incident coverage area 418 is shown as circular (i.e., defined by a pre-selected radius), the coverage area 418 may be more generally specified both in terms of size and shape. As examples, the incident coverage area 418 may be polygonal, arcuate, or bounded by a pre-selected number of streets, buildings, or other geographical features.

[0080] In order to determine which subscribers qualify for an incident alert, the call center 400 may search the subscriber entity database 404. The subscriber entity database 404 stores the entity records 406 that will be described in more detail below. Thus, in one implementation, based on the search results from the subscriber entity database 404, the call center 400 obtains a selection of subscriber entities for which to potentially send an incident alert.

[0081] Because, in one implementation, the alerting service is localized, the call center 400 determines the incident coverage area 418 with respect to the incident location 142. The incident coverage area may be different for each subscriber entity, or may be consistent among all subscriber entities. Thus, the incident coverage area 418 serves as a boundary, within which subscriber entities may be alerted.

[0082] In order to determine whether any particular subscriber entity lies within the coverage area 418, the call center 400 may consult, for example, the subscriber location database 408. Alternatively, the call center 400 may communicate with the external subscriber location provider 412. In either case, the call center 400 queries a subscriber location database for a location record matching a particular subscriber entity. Because the location records are consistently updated with the subscriber location, the call center 400 may determine if the subscriber entity is within the coverage area 418.

[0083] Turning briefly to FIG. 5, that figure shows examples of an entity record 406 and a location record 410, 416. The entity record 406 incorporates information about a subscriber entity and their alerting preferences. In one implementation, the entity record 406 includes an entity ID field 502 and an alert parameters field 504.

[0084] The entity ID 502 provides an identifier for the subscribing entity. The entity ID 502 may be a name, address, identification number, serial number, or any other indicia that specifies a particular subscriber entity.

[0085] The alert parameters field 504 specifies alert constraints, preferences, or other considerations that apply to the subscribing entity. For example, the alert parameters field 504 may indicate the incident types to alert on, a desired coverage area 418, acceptable times for alerting the subscribing entity, what type of media to send to the subscribing entity, and other characteristics that tailor the alerting service to the subscribing entity.

[0086] The location record 410 includes information that physically places a subscriber entity. The location record 410 may include an entity ID field 506 and a location field 508. The entity ID field 506 may be implemented as noted above with regard to the entity ID 502.

[0087] The location field 508 includes position information that locates the subscribing entity. The location field 508 may, as examples, include GPS location coordinates, longitude and latitude data, address information, approximate triangulation coordinates based on cell phone use, or any additional information known about or provided by the subscribing entity (e.g., current on the 35th floor of an apartment building).

[0088] With regard again the FIG. 4, when the subscriber entity is within the coverage area 418, the call center 400 prepares and transmits an incident alert to the subscriber entity. To that end, the call center 400 may transmit data over the external networks 102, including, as examples, transmitting data via the radio data service (RDS) spectrum in the FM radio band, transmitting data packets through a computer network, or by transmitting data through an existing telephone infrastructure.

[0089] As shown in FIG. 4, a cell phone owner carrying the cell phone 126 is present in the coverage area 418. The call center 400 may therefore transmit an incident alert to the call phone 126 to alert the owner, for example, of a mugging that occurred nearby at Canal Street and Monroe Street. Note also that the security camera 134, the motion sensor 136, and the proximity detector 138 are also within the coverage area 418, and may also receive the incident alert if they too are subscriber entities. The subscriber entities need not be the same entities that provide media to the call center 100 or the call center 400.

[0090] Turning briefly to FIG. 6, that figure shows one example of an incident alert 600. The incident alert conveys information to the subscriber units within the coverage area 418 that is related to the incident reported to the call center 400. As shown in FIG. 6, the incident alert includes an entity ID field 602, an alert description field 604, and an alert media field 606.

[0091] The entity ID field 602 may be implemented as noted above with regard to the entity ID field 502. The entity ID field 602 thus serves, for example, as a verification to the recipient of whether the recipient was actually the intended receiver for the incident alert 600.

[0092] The alert description field 604 provides information characterizing the incident that gave rise to the incident alert 600. To that end, the alert description field 604 may include a text based description of the incident (e.g., “mugging alert”, “hit and run at Canal and Monroe”, “assault”), a graphical icon for the incident type, or any other explanatory description or indicia for the incident type.

[0093] The alert media field 606 delivers media to the subscriber entity from the media database 112. Thus, for example, the alert media field 606 encodes a picture taken by a cell phone, a series of such pictures, video frames, audio recordings, motion sensor activation indicators, or any other type of media received by and stored in the media database 112. As a result, a subscriber entity may obtain a wide variety of multi-media information related to the incident.

[0094] With regard to FIG. 7, that figure shows one particular example of the media delivered in the alert media field 606. More specifically, FIG. 7 shows an incident map 700. The incident map 700 depicts the area around the incident, and locates the incident using the location icon 702. Optionally, the incident map 700 may also display the approximate subscriber location 704. As a result, the subscriber unit gains a visual understanding of where the incident has occurred, and may take appropriate action.

[0095] FIG. 8 provides a flow diagram 800 that summarizes the steps taken by the dispatch program 402 when providing the incident alerting service. The dispatch program 402 analyzes incident information to determine an incident location 144 (Step 802). The dispatch program 402 then queries the subscriber entity database 404 to identify subscriber entities that may receive an incident alert (Step 804).

[0096] In addition, the dispatch program 402 determines an incident coverage area 418 around the incident location 144 (Step 806). The incident coverage area 418 may be a pre-configured parameter stored in the memory 110, an operator selectable parameter, or may be specified by each subscriber entity. For localized alerts, the coverage area 418 may encompass 1 to 100 square miles, 1-50 square miles, 1-10 square miles, 1-2 square miles, or another localized area.

[0097] The dispatch program 402 also determines where subscriber entities are located, and whether they are within the coverage area 418 (e.g., by querying the subscriber location provider 412) (Step 808). When there are subscriber entities within the coverage area 418 that are selected to receive an incident alert for the incident reported in the incident information, the dispatch program 402 proceeds to prepare an incident alert 600 (Step 810) and subsequently initiates its transmission (Step 812).

Contextual Media Capture, Aggregation

[0098] FIG. 9 illustrates a call center processing system 900, in communication with external networks and media sensors, that collects and preserves supplemental media from sensors external to the call center processing system 900. The call center 900 includes a media collection program 902 and a media preservation program 904 executing from the memory 110.

[0099] In addition, the call center 900 includes a sensor database 906 that stores sensor records 908, and a subscriber location database 910 that stores location records 912. Alternatively, the call center 900 may communicate over the external networks 102 to make inquiries to a sensor location provider 914. The sensor location provider 914 may itself maintain a sensor location database 916 that stores location records 918. Furthermore, the call center 900 may communicate, as explained below, with one or more third party sensor control entities such as the security company 142. FIG. 9 also illustrates a sensor coverage area 920 that encompasses a geographical region around the incident location 144.

[0100] In operation, the call center 900 receives an incident report that sets forth pertinent information about an incident that has occurred. Based on the incident information, the call center 900 may determine that selected external sensors should be activated. The external sensors may then either transmit their media to the call center 900, or have their media preserved as explained below. In a manner similar to the call center 400 in FIG. 4, the call center 900 may make the determination based on the type of incident (e.g., a violent act), incident location, or other pre-selected criteria.

[0101] With regard to collecting additional media, the call center 900 selectively activates external sensors or requests media from additional sensors. For example, as shown in FIG. 9, the call center 900 may activate one or more of the sensors 130, 134, 136, and 138 that are positioned in the sensor coverage area 920. Although the sensor coverage area 920 is shown as rectangular, the coverage area 920 may be more generally specified both in terms of size and shape. As examples, the sensor coverage area 920 may be polygonal, arcuate, or bounded by a pre-selected number of streets, buildings, or other geographical features.

[0102] In order to determine which sensors to activate and from which to collect media, the call center 900 may search the sensor entity database 906. The sensor database 906 stores the sensor records 908. The sensor records 908 may take the same or similar form as the entity records 406. In other words, the sensor records 902 may identify a sensor (e.g., by location, IP address, serial number, and the like), and provide collection parameters that specify the capabilities of the sensor, as explained above with regard to FIG. 2. Accordingly, in one implementation, based on the search results in the sensor database 906, the call center 900 may obtain a selection of sensors (e.g., the cameras 130 and 134) from which to collect supplemental media or to instruct to preserve their media.

[0103] Because the media collection is localized, in one implementation, the call center 900 determines the sensor coverage area 920 with respect to the incident location 142. The sensor coverage area 920 may be different for each sensor, or may be consistent among all sensors. The sensor coverage area 920 may be a pre-configured parameter stored in the memory 110, an operator selectable parameter, or may be specified by each sensor. For localized collection, the sensor area 920 may encompass 1 to 100 square miles, 1-50 square miles, 1-10 square miles, 1-2 square miles, or another localized area. Thus, the sensor coverage area 920 serves as a boundary, within which additional media may be collected from sensors.

[0104] In order to determine whether any particular sensor lies within the sensor coverage area 920, the call center 900 may consult, for example, the sensor location database 910. Alternatively, the call center 900 may communicate with the external sensor location provider 914. In either case, the call center 900 queries a subscriber location database for a location record matching a particular sensor. Because the location records are consistently updated with the sensor location (and many sensors will never move), the call center 900 may determine if the sensor is within the sensor coverage area 920.

[0105] The location records 912 and 918 may provide the same or similar information as the location records 410 and 416 shown in FIG. 4 and shown in more detail in FIG. 5. Thus, the location records 912 and 918 serve to physically locate each sensor represented in the sensor database 906.

[0106] In some instances, the sensors may provide supplemental media directly to the call center 900 through the external networks 102. However, in other instances the security company 142 may instead forward the media obtained from the sensors to the call center 900. Thus, the call center 900 may selectively transmit a sensor activation instruction directly to the sensors, to the security company 142, or both. The security company 142 may locally process the activation instruction and take the requested action, or may in turn forward the activation instruction to the sensors.

[0107] Turning briefly to FIG. 10, that figure shows one example of a sensor activation instruction 1000. As illustrated, the sensor activation instruction 1000 includes a sensor ID field 1002, and a capture parameters field 1004. In a manner similar to the entity ID field 602, the sensor ID field 1002 may serve, for example, as a verification to the sensor that it was actually the intended receiver for the sensor activation instruction 1000.

[0108] The capture parameters field 1004 provides information characterizing the nature and extent of the media that the call center 900 is requesting the sensor to provide. As examples, the capture parameters field 1004 may specify that a video camera should turn on and begin transmitting video footage, that a microphone sensor should activate and transmit sampled audio back to the call center 900, or that the sensor should otherwise activate and perform a sensing operation. The capture parameters field 1004 may further specify a duration for the media capture or the delivery of media already obtained. The capture parameters field 1004 may also specify the resolution, sampling rate, image capture rate, camera angle, panning sweep angle, or other media acquisition parameters for the sensor of interest.

[0109] Supplemental media, transmitted by sensors, arrives at the call center 900. In response, the call center 900 receives the supplemental media, obtains a characterization of the media, and stores the supplemental media in the media database 112 as described above, for example, with respect to FIGS. 1-3. Thus, the call center 900 acts to automatically aggregate media that may relate to a reported incident, and stores the media in a conveniently accessible and searchable form in the media database 112.

[0110] FIG. 11 provides a flow diagram 1100 that summarizes the steps taken by the collection program 902 when collecting supplemental media. The collection program 902 analyzes incident information to determine an incident location 144 (Step 1102). The collection program 902 then queries the sensor database 906 to identify sensors that may be able to provide additional media relating to the incident (Step 1104).

[0111] In addition, the collection program 902 determines a sensor coverage area 920 around the incident location 144 (Step 1106). The collection program 902 also determines where the sensors are located, and whether they are within the coverage area 920 (e.g., by querying the sensor location database 910) (Step 1108). When there are sensors within the coverage area 920 that are selected to provide supplemental media, the collection program 902 proceeds to prepare a sensor activation instruction 1000 (Step 1110) and subsequently initiates its transmission (Step 1112).

[0112] The call center 900 also processes the supplemental media received from the sensors. Accordingly, the collection program 902 may receive the supplemental media (step 1114) and store the supplemental media in the media database 112 (Step 1116). In one implementation, the collection program 902 may itself perform these operations, while in other instances, the media aggregation program 116 may perform the reception, indexing, and storage operations.

Media Preservation

[0113] Additionally or alternatively, the call center 900, using the media preservation program 904, may act to preserve media that might otherwise be discarded, destroyed, overwritten, or otherwise lost. In this aspect, the call center 900 may optionally employ a localized preservation coverage area that differs from the sensor coverage area 920. For example, the call center 900 may use a preservation coverage area that encompasses more sensors so that additional supplemental media is preserved for future analysis.

[0114] To that end, instead of or in addition to transmitting a sensor activation instruction 1000, the call center 900 may transmit a media preservation instruction. Turning briefly to FIG. 12, that figure shows one example of a media preservation instruction 1200.

[0115] As illustrated, the preservation instruction 1200 includes a post-incident media retention specifier 1202 and a pre-incident media retention specifier 1204. The post-incident media retention specifier 1202 includes a retention duration 1206 and a retention extent 1208. Similarly, the pre-incident media retention specifier 1204 includes a retention duration 1210 and a retention extent 1212. The post-incident media retention specifier 1202 sets forth conditions on retention of media acquired by a sensor after the incident occurrence, while the pre-incident media retention specifier 1204 sets forth conditions on retention of media acquired by a sensor before the incident occurrence.

[0116] Each of the retention durations 1206 and 1210 specifies, for example, a duration (e.g., an amount of time) that the sensor should retain the media recorded by the sensor. Alternatively, the preservation program 904 may transmit the preservation instruction 1200 to the security company 142 or any other entity responsible for the sensors 126-140. The retention durations 1206 and 1210 may be expressed in terms of a number of months, weeks, days, hours, sample periods, frames, or any other unit or duration. The duration may be an absolute measure, or relative to a specific time and date (e.g., the incident time and date) also provided in the preservation instruction 1200.

[0117] For example, if the retention duration 1206 is 3 days and 12 hours, then the preservation instruction informs the sensor to retain the media that it obtained after the incident occurred for at least 3 days at 12 hours. Similarly, if the retention duration 1210 is 1 week, then the preservation instruction informs the sensor to retain the media that it obtained before the incident occurred for at least 1 week.

[0118] In addition to the retention duration, the preservation instruction may also specify the extent (e.g., quantity or length) of media to retain. An extent may be specified in terms of time, samples, images, sensor readings, or any other measure. For example, if the retention extent 1208 is 20 minutes, then the preservation instruction has informed the sensor to retain fifteen minutes of media that it obtained after the incident occurred. Continuing the example above, the sensor will retain those 20 minutes for at least 3 days at 12 hours. Similarly, if the retention extent 1210 is 320 samples, then the preservation instruction has informed the sensor to retain 320 samples (e.g., audio samples, still images, or frames of video) of the media that it obtained before the incident occurred. Continuing the example above, the sensor will retain the 320 samples for at least 1 week.

[0119] Turning briefly to FIG. 13, that figure illustrates a timeline 1300 graphically illustrating the application of the retention extents 1208 and 1212 to media captured by a sensor. Specifically, FIG. 13 shows the time extent 1302 of media captured by, for example, the security camera 132. The incident occurrence time is labeled as time 0. As shown, the post-incident retention extent (specified in a preservation instruction) is 20 minutes of video, while the pre-incident retention extent (also specified in the preservation instruction) is 320 frames.

[0120] FIG. 14 provides a flow diagram 1400 that summarizes the steps taken by the preservation program 904 when preserving media that may be useful in analyzing incidents. The preservation program 904 analyzes incident information to determine an incident location 144 (Step 1402). In addition, the preservation program 904 determines a preservation coverage area around the incident location 144 (Step 1404).

[0121] The preservation program 904 then queries the sensor database 906 to identify sensors that may have worthwhile media recordings relating to the incident (Step 1406). The preservation program 904 also determines where the sensors are located, and whether they are within the preservation area (e.g., by querying the sensor location database 910) (Step 1408).

[0122] When there are sensors within the preservation coverage area, the preservation program 904 proceeds to prepare a preservation instruction 1200 (Step 1410). The preservation program 904 subsequently initiates transmission of the preservation instruction (Step 1412).

Call Center User Interface

[0123] As noted above with reference to FIG. 1, the call centers may include a user interface 148 to aid in the operation of any of the functions described above. Turning to FIG. 15, that figure shows one example of the user interface 148. The user interface 148 includes a third party information window 1502, an audio playback button 1504, and a media display window 1506. The user interface 148 also includes routing buttons including an officer routing button 1508 and a citizen routing button 1510. A media description text box 1512 provides a time, date, location, and general media information display.

[0124] In addition, the user interface 148 includes a map display 1514, and locator controls including a cell phone display button 1516 and a security camera display button 1518. The map display 1514 includes sensor location indicia for two security cameras labeled C1 and C2, and for two cell phones labeled P1 and P2. The zoom in, zoom reset, and zoom out buttons 1520, 1522, and 1524 control the zoom level of the map display 1514.

[0125] An incident category button 1526 and an incident description text box 1528 are also present. The user interface 148 includes a police notification button 1530 and a fire department notification button 1532, as well as an end-call button 1534. An alert radius selection button 1536 and a send-alert button 1538 are provided, as are characteristic buttons, including the fleeing suspect button 1540, fleeing car button 1542, car accident button 1544, and a vandalism button 1546. A clear description button 1548 is additionally present.

[0126] The third party information window 1502 displays information about the present caller or media sensor providing media to the call center. As examples, the information window 1502 may display call identification and location data. The audio playback button 1504 provides a convenient mechanism for playing any audio portion of the media that is arriving, while the media display window 1506 displays images, video, or other sensor readings obtained from an image sensor. For example, the media display window 1506 may display the images captured by a digital camera enabled cell phone.

[0127] The officer routing button 1508 provides an interface that allows the call center operator to immediately transmit information about the current incident to a police officer. Similarly, the citizen routing button 1510 provides a mechanism that allows the call center operator immediately transmit an incident alert to subscriber entities. As noted above, the media description text box 1512 provides a time, date, location, and media information display for the current incident and its associated media.

[0128] The map display 1514 provides a window in which a local map (with respect to the incident location 144 or any other selected address or coordinate) may be displayed, including location indicia specifying the incident location 144, and sensor location indicia such as the camera icons C1 and C2 and the cell phone icons P1 and P2. The sensor indicia may be displayed or removed from the map display 1514 by using the cell phone display button 1516 and the security camera display button 1518. As explained above, the Zoom in button 1520, Zoom reset button 1522, and the Zoom out button 1524 controls the zoom level of the map display 1514.

[0129] An incident category button 1526 provides a drop down list that may be employed to select pre-defined incident types (e.g., robbery, mugging, and the like) for the incident. The incident description text box 1528 provides an additional mechanism for specifying incident information and allows free form entry, for example, of a text description of the incident. When the incident warrants, the operator may dispatch the incident information and related media directly to a police station using the police notification button 1530, or directly to the fire department using the fire department notification button 1532. The end-call button 1534 provides an interface button that allows the operator to end the current incident call.

[0130] An alert radius selection button 1536 allows the operator to select an incident coverage area (in this determined by a radius selection), while the send-alert button 1538 initiates alerting subscriber entities as explained above with respect to FIG. 4-8. The user interface 148 allows the operator to specify additional incident information using the characteristic buttons, including the fleeing suspect button 1540, fleeing car button 1542, car accident button 1544, vandalism button 1546. The clear description button 1548 resets the characteristic information in the text box 1528 and the settings chosen by the characteristic buttons 1540-1546.

[0131] The user interface 148 shown in FIG. 15 provides one example of wide variety of designs that may be employed to ease interaction between the operator and the call center. Generally, the user interface 148 may be freely modified for any given implementation. For example, additional or fewer text boxes, drop down lists, selection buttons may be incorporated into the user interface 148 in order to configure the user interface 148 for any particular application.

Investigation Tool

[0132] The media collection, aggregation, and preservation functions of the call center provide significant enhancements to receiving, processing, and communicating incident reports. A further extension of the call center provides searching and authoring capabilities in the form of an investigation tool.

[0133] Turning to FIG. 16, that figure shows one example implementation of an investigation tool 1600. The investigation tool 1600, as shown, leverages the hardware and databases already present in the call center. Thus, the investigation tool, in one implementation, includes the processor 106, the network interface 108, and the memory 110. The memory 110 includes the media investigation program 1602, and optionally the other programs noted above, for example, the media aggregation program 116. The investigation program 1602 interacts with the operator and an investigation report database 1604 to prepare investigation reports 1606.

[0134] Additionally, the media database 112 is present, and includes the media records 118 and media 120. The investigation tool 1600 may also draw upon the resources provided by the subscriber entity database 404 as well as the subscriber location database 408. Similarly, the investigation tool 1600 may employ the sensor database 906 and the sensor location database 910 in operation. Generally, any of the databases 112, 906, 910, 404, 408 may be maintained offsite by a third party provider, or may be maintained locally, integrated into the investigation tool 1600.

[0135] In operation, the investigation tool 1600 retrieves and presents media histories and builds investigation reports. To that end, the investigation tool 1600 may retrieve and present chronological histories of delimited geographic areas by a selected region, filter by event types, entities of interest, and time range, as well as present the relevant information chronologically. Generally, the media investigation program 1602 coordinates the activities of the investigation tool 1600, and in response to operator input, prepares, presents, and stores the investigation reports 1606.

[0136] A display 146 provides a visual interface for the investigation tool 1600 operator. In that capacity, the display 146 presents the investigation tool user interface 1608. The user interface 1608 is described in more detail below with regard to FIG. 17, and is accompanied by a discussion of how the investigation tool 1600 responds to the user interface 1608.

[0137] As shown in FIG. 17, the user interface 1608 includes a search window 1704, a report match window 1706, and a report authoring window 1708. In addition, the user interface 1608 includes a media selection window 1710 and a map display window 1712. Additionally, locator icons are also present, and include a call phone display button 1714, a security camera display button 1716, a news media display button 1718, and a police display button 1720. Zoom in, zoom reset, and zoom out buttons 1722, 1724, and 1726 control the zoom level of the map display 1712.

[0138] The search window 1704 accepts incident search parameters as a precursor to initiating an incident search in the media database 112. In this example, the search parameters include a location parameter, a coverage area parameter (shown in FIG. 17 as a radius drop down list), and a temporal parameter (shown in FIG. 17 as the date range). The search parameters further include an incident type parameter (shown in FIG. 17 as a selectable checklist of incident types). The Search button initiates the incident search in the media database 112.

[0139] When the operator activates the Search button, the investigation program 1602 initiates a search for matching media in the media database 112. The search results are presented in the media selection window 1710. The media selection window 1710 provides a selection interface that the operator interacts with to select and view media, as well as add media to an investigation report. To that end, the media selection window 1710 displays a media record indicia for each matching piece of media in the media database 112. On example is labeled as the media record indicia 1728. The media record indicia provides a convenient visual representation for the media, and may be, as examples, a thumbnail image of a digital picture or a video frame, a waveform representing an audio recording, or any other type of visual cue.

[0140] As shown in FIG. 17, the media match M1 represents a digital camera image of an auto theft incident in Chicago Ill. Similarly, media match M2 is a security camera video of a robbery in Chicago Ill., while media match M3 represents an audio recording from a microphone nearby a theft incident in Glenview Ill. The media match M4 represents a cell phone camera image of a hit and run incident in Peoria Ill.

[0141] Note also that the investigation program 1602 populates the report match window 1706. In other words, the report match window 1706 includes individual selectable report entries 1732 that represent investigation reports 1606 that match the search parameters entered in the search window 1704. The operator may optionally select one of the report entries 1732 to edit, or to employ as the basis for a new investigation report 1606.

[0142] In that regard, the user interface 1608 also includes the report authoring window 1708 as an investigation report interface. The authoring window 1708 accepts report components 1734 including text entries, voice annotations, media attachments and other information that may be used to create an explanation, interpretation, statement, account, or description of an incident. For example, as shown in FIG. 17, the operator has selected the media M1, M3, and M7 and inserted that media as report components in the authoring window 1708. FIG. 17 also shows an automatic update report component 1736, including an automatic update filter that specifies match criteria. The match criteria may be the same or different than the incident search parameters. When an automatic update report component is present, the investigation program 1602 applies the filter against newly submitted media classification and characteristic information. Matching submitted media is then automatically associated with the investigation report. The filters may be maintained in a separate index for convenient access.

[0143] The user interface 1608 may also include Save/Load interface components that allow the operator to store and retrieve selected investigation reports 1606.

[0144] The map display window 1712 provides a window in which a local area map 1730 may be displayed, including indicia indicating the incident location 144 for any selected media record indicia. In addition, in response to operator selection of a locator icon 1714-1720, the investigation program 1602 displays location indicia on the area map to illustrate where particular sensors, individuals, or other entities were located during the incident.

[0145] As one specific example, the investigation program 1602 displays the camera cell phone indicia P1 and P2 on the area map 1730 when the locator icon 1714 is selected. The indicia P1 and P2 thus represent the location of individuals with camera enabled cell phones during an incident represented by a selected media record in the media selection window 1710. Similarly, the investigation program 1602 displays the video camera indicia C1 and C2 on the area map 1730 when the locator icon 1716 is selected.

[0146] The magnification of the area map 1712 may be adjusted, or the area map 1712 may be scrolled or re-centered using additional buttons on the user interface 1606. For example, the Zoom in button 1722, Zoom reset button 1724, and the Zoom out button 1726 will control the zoom level of the map display 1712.

[0147] The user interface 1606 shown in FIG. 17 provides one example of wide variety of designs that may be employed to ease interaction between the operator and the investigation tool 1600. Generally, the user interface 1606 may be freely modified for any given implementation. For example, additional or fewer text boxes, drop down lists, or selection buttons may be incorporated into the user interface 1606 in order to configure the user interface 1606 for any particular application.

[0148] Turning next to FIG. 18, that figure shows a flow diagram 1800 of the steps taken the media investigation program 1602 executed by the call center instigation tool shown in FIG. 17. The investigation program 1602 accepts incident search parameters including, as examples, incident location, type, subject, and time or date (Step 1802). An incident search is initiated based on the search parameters (Step 1804). Responsive to the search, the investigation program 1602 displays a selection interface (e.g., the media selection window 1710) that includes media record indicia 1728 associated with matching media records returned from the incident search (Step 1806).

[0149] In addition, the investigation program 1602 displays an investigation report interface (e.g., the report authoring window 1708) (Step 1808) in preparation for building an investigation report 1606. The investigation program 1602 also displays, based on a media record indicia selection, an area map (Step 1810) that shows the geographical region near a selected incident, and the incident location indicia 144 (Step 1812).

[0150] Furthermore, the investigation program 1602 also displays the locator icons 1714-1720 on the user interface 1606 (Step 1814). Thus, the investigation program 1602 may respond to the locator icons 1714-1720, for example, to display sensor indicia (P1, P2, C1, C2) on the area map (Step 1816). The sensor indicia may thus help the operator locate where sensors were located that submitted supplemental media to the call center.

[0151] Through the report interface, the investigation program 1602 accepts report components for building an investigation report 1606 (Step 1818). The report components may include text, video, audio, sensor readings, or any other type of media present in the media database 112. Thus, the investigation report 1606 may provide a multi-media presentation that describes, records, explains, or otherwise annotates an incident.

[0152] At any point, the operator may choose to save the incident report. In response, the investigation program 1602 stores the investigation report in the investigation report database 1604. The investigation report may be subsequently retrieved, viewed, and edited.

[0153] In certain instances, the call centers and investigation tool may communicate, through the network infrastructure interface 108, with ad-hoc sensor networks. An ad-hoc sensor network includes a loose connection of sensors that may pass data between nodes in the sensor network, yet that may or may not bear any relation to one another, operate under common control, or under common conditions. Returning to FIG. 16, that figure shows one example of an ad-hoc sensor network 1650.

[0154] The ad-hoc sensor network 1650 includes intermediate nodes 1652, 1654, 1656, 1658, 1660, and two principal nodes 1662 and 1664. The principal node 1654 may represent a gateway between the remaining intermediate nodes 1652, and another entity, for example, the investigation tool. There may be any number of intermediate nodes 1652 and principal nodes 1654, and they may be implemented in a variety of manners, including as receive and relay nodes, network traffic processing systems, gateways, routers, and the like.

[0155] While the investigation tool 1600 and the call centers 100, 400, 900 are particularly useful in emergency service and law enforcement environments, their capabilities renders them suitable for many different fields, business areas, and processes. More generally, the investigation tool 1600 and the call centers 100, 400, 900 may be employed to associate media with any pre-selected internal or external business process. As examples, investigation tool 1600 and the call centers 100, 400, 900 may be applied in the context of insurance claim adjustment, technical support, merchandise return, fraud detection, or any other business process that may be enhanced through multi-media support, gathering, or dissemination.

[0156] For example, in the context of insurance claim adjustment, the media may relate to digital images (e.g., a cell phone camera picture of an intersection at which an accident occurred) and audio recordings obtained from accident sites. In a technical service environment, the media may relate to digital images and sensor readings obtained from electromechanical equipment (e.g., a digital camera picture of the cable connections on the back of a personal computer).

[0157] Thus, the investigation tool or call center operator (whether a human, or an automated media evaluation program), may view incoming incident reports or search the media database for existing incident reports, and take appropriate action. As one example, the operator may forward the incident report or media to a selected business function, additionally or alternatively triggering a workflow process.

[0158] For instance, in the context of insurance claim adjustment, the operator may recognize the incident report as a car accident. In response, the operator may optionally gather supplemental sensor media, and forward the incident report and related media to a claims agent. The incident report and media may be first placed in an investigation report prepared by the operator as explained above. The claims agent may then review and modify the incident report, and initiate steps to handle any potential claim. For example, the claims agent may contact the customer involved in the accident, make arrangements for a rental car, begin to complete documentation for the claims, and initiate or execute any other business function.

[0159] As another example, in the context of a technical service center, the operator may view an incident report and its associated media as an initial step in determining the subject matter of the incident. One determined, the operator may then forward the incident report, media, or investigation report to a technical service agent that is skilled with regard to the subject matter. To that end, the user interfaces may include interface components similar to the routing buttons 1508, 1510 that initiate transmission of the data to any particular individual.

[0160] In this regard, the operator or the technical service agent may also study the related media to determine whether a service call is warranted. Additionally, the operator or the technical service agent may also determine what tools should be obtained for the service call, and initiate obtaining such tools. Note also that if a service call is not warranted (e.g., the third party may safely perform the service), then the operator or the technical service agent may prepare an incident alert that responds to the third party with self-service instructions, directions, supporting media (e.g., a repair diagram or video), and other helpful or instructive data.

[0161] FIG. 19 summarizes the steps explained above. In particular, the operator ascertains the incident subject matter (Step 1902). To that end, as examples, the operator may analyze an incident report or its related media, or search the existing media database 112 with the investigation tool 1600. Subsequently, the operator routes the incident data to a selected processing entity or processing system (Step 1904). For example, the operator may send the incident report, related media, or an investigation report to an insurance agent, technical service agent, law, enforcement agency, sales agent, product design department, research and development department, phone or cable company representative, process or fabrication assembly line, or any other processing entity or processing system.

[0162] The incident information arrives at the processing entity or processing system, where it is analyzed (Step 1906). The analysis may trigger any number of related business processes, as examples, obtaining parts and equipment for service, scheduling a visit by an insurance agent, or responsively communicating with the third party that submitted the incident report. For instance, the business entity may then prepare a responsive incident alert for the third party and initiate the transmission of the incident alert (Step 1908).

[0163] The call centers and investigation tools described above thereby reconnect technology knowledgeable individuals with the services that they turn to for help or for information. The services thereby become more amenable to interaction with the individual. In addition, the call centers and investigation tools achieve significantly expanded capability, through multi-media integration, for rendering aid, disseminating information, and protecting citizens through law enforcement related activities.

[0164] It is therefore intended that the foregoing detailed description be regarded as illustrative rather than limiting, and that it be understood that it is the following claims, including all equivalents, that are intended to define the spirit and scope of this invention.