{ "paper_id": "H01-1049", "header": { "generated_with": "S2ORC 1.0.0", "date_generated": "2023-01-19T03:31:31.686241Z" }, "title": "Listen-Communicate-Show (LCS): Spoken Language Command of Agent-based Remote Information Access", "authors": [ { "first": "Jody", "middle": [ "J" ], "last": "Daniels", "suffix": "", "affiliation": { "laboratory": "Lockheed Martin Advanced Technology Laboratories", "institution": "", "location": { "addrLine": "1 Federal Street", "postCode": "A&E 3W, 08102", "settlement": "Camden", "region": "NJ" } }, "email": "jdaniels@atl.lmco.com" }, { "first": "Benjamin", "middle": [], "last": "Bell", "suffix": "", "affiliation": { "laboratory": "Lockheed Martin Advanced Technology Laboratories", "institution": "", "location": { "addrLine": "1 Federal Street", "postCode": "A&E 3W, 08102", "settlement": "Camden", "region": "NJ" } }, "email": "bbell@atl.lmco.com" } ], "year": "", "venue": null, "identifiers": {}, "abstract": "Listen-Communicate-Show (LCS) is a new paradigm for human interaction with data sources. We integrate a spoken language understanding system with intelligent mobile agents that mediate between users and information sources. We have built and will demonstrate an application of this approach called LCS-Marine. Using LCS-Marine, tactical personnel can converse with their logistics system to place a supply or information request. The request is passed to a mobile, intelligent agent for execution at the appropriate database. Requestors can also instruct the system to notify them when the status of a request changes or when a request is complete. We have demonstrated this capability in several field exercises with the Marines and are currently developing applications of this technology in new domains.", "pdf_parse": { "paper_id": "H01-1049", "_pdf_hash": "", "abstract": [ { "text": "Listen-Communicate-Show (LCS) is a new paradigm for human interaction with data sources. We integrate a spoken language understanding system with intelligent mobile agents that mediate between users and information sources. We have built and will demonstrate an application of this approach called LCS-Marine. Using LCS-Marine, tactical personnel can converse with their logistics system to place a supply or information request. The request is passed to a mobile, intelligent agent for execution at the appropriate database. Requestors can also instruct the system to notify them when the status of a request changes or when a request is complete. We have demonstrated this capability in several field exercises with the Marines and are currently developing applications of this technology in new domains.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "Abstract", "sec_num": null } ], "body_text": [ { "text": "An LCS system listens for information requests, communicates both with the user and networked information resources, and shows a tailored visualization to the individual user. The LCS-Marine system employs a spoken language understanding system (SLS) for assisting the user in placing a request and mobile, intelligent agents for information access to implement the LCS paradigm. The SLS converses with the user to generate a request or to check status, amend, or cancel an existing request. Once sufficient information is obtained from the user, the SLS launches an agent to accomplish the requested task. The agent accesses the appropriate databases via whatever network services are available (including existing tactical communications networks). Once the agent's tasks are complete, it returns to the SLS, which generates an appropriate response to the user. The response may be visual, verbal, or a combination, depending on the available devices.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "INTRODUCTION", "sec_num": "1." }, { "text": "The LCS-Marine system consists of four major components: an SLS, a collection of agents for information access, real-world operational databases, and communications networks t o connect the user to the SLS and the agents to the databases. The underlying architecture for the system is the MIT Galaxy II conversational architecture [3] . It is a distributed, componentbased middleware product designed to be \u00d2plug and play\u00d3. Specialized servers handle specific tasks, such as translating audio data to text. All Galaxy II-compliant servers communicate with each other through a central server known as the Hub. The Hub manages flow control, handles traffic among distributed servers, and provides state maintenance.", "cite_spans": [ { "start": 331, "end": 334, "text": "[3]", "ref_id": "BIBREF2" } ], "ref_spans": [], "eq_spans": [], "section": "SYSTEM OVERVIEW", "sec_num": "2." }, { "text": "In the SLS, speech is sent from the Audio I/O server to the Recognizer. The top n recognitions are then parsed, prior context added, and processed using the Natural Language (NL) servers (Frame Construction and Context Tracking) t o verify the new input's validity and context. The Turn Manager (TM) determines how to proceed with the conversations and generates a response. NL (Language Generation) converts it t o text and the Synthesis server generates the verbal response. The audio server then speaks the waveform file to the user. We customize the various servers to work with domain specific issues and application-specific information and training. Figure 1 shows our LCS architecture. We have integrated an additional server into the architecture to support information access\u00d1an Agent server. The Agent server manages a collection of agents that can be tasked t o accomplish a variety of missions, including migration t o distant machines with possibly different operating systems t o gather information or to monitor and report events [2] .", "cite_spans": [ { "start": 1046, "end": 1049, "text": "[2]", "ref_id": "BIBREF1" } ], "ref_spans": [ { "start": 657, "end": 665, "text": "Figure 1", "ref_id": "FIGREF0" } ], "eq_spans": [], "section": "SYSTEM OVERVIEW", "sec_num": "2." }, { "text": "Typically, the Agent server receives its tasking from the TM and supplies the TM with information from the data source(s). For persistent tasks, the Agent server becomes the initiator of a dialogue to inform the user of specific events by passing agent reports to the TM. When a visual display is present, the Agent server will dispatch an agent to pass the updated information to the display machine.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "SYSTEM OVERVIEW", "sec_num": "2." }, { "text": "For the LCS-Marine application our agents had to interact with a logistics database that could be between one to one hundred miles away. We later describe how our agents were able to reach this live database over the tactical communication links available.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "SYSTEM OVERVIEW", "sec_num": "2." }, { "text": "Users interact with the LCS-Marine system using the voice capture device appropriate to their organization (telephone, cell phone, tactical radios, computer headsets, etc.).", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "SYSTEM OVERVIEW", "sec_num": "2." }, { "text": "Marines work in a dynamic, fluid environment where requirements and priorities are constantly subject to change.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "MARINE COMBAT SERVICE SUPPORT PROBLEM", "sec_num": "3." }, { "text": "Under current operations, it might take up to 72 hours before a Marine in a Combat Service Support Operations Center (CSSOC) can confirm with a requesting unit that their order i s in the logistics system. This is due to a lack of resources available to the tactical units as well as a difficulty in turning logistics data into information to enable timely analysis and decision making. For Marines conducting tactical operations, these restrictions and limited visibility into the supply chain hamper logistics planning, decision, execution, and assessment. Figure 2 shows the various echelons involved in tactical Marine logistics operations. It is noteworthy that tactical units have no organic means of accessing the logistical databases other than via radio contact with personnel at the CSSOC.", "cite_spans": [], "ref_spans": [ { "start": 559, "end": 567, "text": "Figure 2", "ref_id": "FIGREF1" } ], "eq_spans": [], "section": "MARINE COMBAT SERVICE SUPPORT PROBLEM", "sec_num": "3." }, { "text": "The focus of the LCS-Marine project is to provide Marines i n the field with this missing visibility into the supply chain. By using standard radio protocols and a common form, Marines can now converse with a system that understands their task and end goal and can assist them in getting both the information and supplies they need. Figure 3 shows a sample of the Rapid Request form, used when placing an order.", "cite_spans": [], "ref_spans": [ { "start": 333, "end": 341, "text": "Figure 3", "ref_id": "FIGREF2" } ], "eq_spans": [], "section": "MARINE COMBAT SERVICE SUPPORT PROBLEM", "sec_num": "3." }, { "text": "Supporting the LCS-Marine domain required understanding and using proper radio protocols to communicate. It required the system to understand call signs, military times, grid coordinates, and special ordinance nomenclature. Additionally, to fully support the dynamic environment, LCS-Marine needed the ability to understand and translate usages of the military phonetic alphabet. This alphabet is used to spell difficult or unusual words. For example, to give the point of contact for the request as Sergeant Frew, the user could say: \u00d2 P O C is Sergeant I spell Foxtrot Romeo Echo Whiskey over.\u00d3 LCS-Marine would convert the phonetic words to the proper letter combination. This way the vocabulary is potentially much larger than that used for system training.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "MARINE COMBAT SERVICE SUPPORT PROBLEM", "sec_num": "3." }, { "text": "Supporting the dynamic aspects of the Marine environment, the system is speaker independent. This is critical in applications where the user may change and there is no additional time for training the system for a new operator.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "MARINE COMBAT SERVICE SUPPORT PROBLEM", "sec_num": "3." }, { "text": "The recognizer is trained on the domain vocabulary, but not o n individual operator voices. The system also fully supports natural, conversational dialogue, i.e., the recognizer expects utterances at a normal rate of speech and the speaker does not need to enunciate each syllable.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "MARINE COMBAT SERVICE SUPPORT PROBLEM", "sec_num": "3." }, { "text": "It is important to note that the amount of time spent training personnel to use the LCS-Marine system is generally less than 10 minutes. After a short introduction, the user is shown a sample dialogue for familiarization. The user is also given information about meta-instructions \u00d0 how to start over or t o clear their previous statement \u00d0 before they begin operation.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "MARINE COMBAT SERVICE SUPPORT PROBLEM", "sec_num": "3." }, { "text": "To measure the effectiveness of the LCS paradigm under operational conditions\u00d1real users placing real requests, accessing a live database, and using existing communications links\u00d1we conducted a series of Integrated Feasibility Experiments (IFE). The IFEs ranged from a pilot study that featured scripted dialogue, replicated databases, and testing i n the lab with prior military personnel, to field experiments where active duty Marines used the system operationally over a series of days as their sole means of interaction with the logistics system for rapid requests. We tested the system\u00d5s support of placing and checking on requests for ammunition (Class V), fuels (Class III), and subsistence (Class I) supplies. More on the experimentation protocols can be found in [1] and [4] . Over the course of the IFE process we were able to experiment with differing server configurations as well as varying communications linkages between servers. The most recent IFE (December 2000) used the server layout shown in Figure 4 . The ideal configuration of the system would have a Marine using their organic communications system calling in to a remote location and communicating with the SLS there. This would not add any additional cost or hardware to the existing Marine infrastructure. This operational layout is depicted i n Figure 5 . Unfortunately, the current tactical radio, the Single Channel Ground and Airborne Radio System (SINCGARS), can create a large amount of channel noise, which alters or distorts the acoustic signal. Current recognizers can not yet compensate for this distortion, although there is active research into solving this problem.", "cite_spans": [ { "start": 773, "end": 776, "text": "[1]", "ref_id": "BIBREF0" }, { "start": 781, "end": 784, "text": "[4]", "ref_id": "BIBREF3" } ], "ref_spans": [ { "start": 1014, "end": 1022, "text": "Figure 4", "ref_id": "FIGREF3" }, { "start": 1325, "end": 1333, "text": "Figure 5", "ref_id": null } ], "eq_spans": [], "section": "OPERATIONAL EVALUATION", "sec_num": "4." }, { "text": "We used a second operational layout to test the system and get operator feedback on using a spoken language understanding interface. This layout is depicted in Figure 6 . In this layout, we required the user to beat the same location as the entire SLS system and the agents migrated over the SINCGARS data link to reach the logistics database. The recognizer still had t o contend with the issue of a noisy and dynamic background, but the acoustic distortion was eliminated.", "cite_spans": [], "ref_spans": [ { "start": 160, "end": 168, "text": "Figure 6", "ref_id": "FIGREF4" } ], "eq_spans": [], "section": "Rover\u00d5s", "sec_num": null } ], "back_matter": [ { "text": "We have built a system that integrates a spoken language understanding system with a mobile, intelligent agent system that allows users in a hostile acoustic environment to place and access data requests via a conversational interface. LCS-Marine is speaker independent and requires little training. The time to accomplish a task is significantly lower than the manual input method it seeks to enhance, but it can still be improved. Being able to rapidly access, insert, modify, and delete requests gives the users greater visibility into the supply system.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "CONCLUSION", "sec_num": "5." }, { "text": "Thanks to members of the LCS team: James Denny, Jerry Franke, Ray Hill, Bob Jones, Steve Knott, Dan Miksch, Kathy Stiller and Mike Thomas. This research was supported by DARPA contract N66001-98-D-8507 and Naval contract N47406-99-C-7033.", "cite_spans": [], "ref_spans": [], "eq_spans": [], "section": "ACKNOWLEDGMENTS", "sec_num": "6." } ], "bib_entries": { "BIBREF0": { "ref_id": "b0", "title": "Integrating a Spoken Language System with Agents for Operational Information Access", "authors": [ { "first": "J", "middle": [], "last": "Daniels", "suffix": "" } ], "year": 2000, "venue": "Proc.. o f Innovative Applications of Artificial Intelligence (IAAI-2000)", "volume": "", "issue": "", "pages": "", "other_ids": {}, "num": null, "urls": [], "raw_text": "Daniels, J. Integrating a Spoken Language System with Agents for Operational Information Access. In Proc.. o f Innovative Applications of Artificial Intelligence (IAAI- 2000), August, 2000, Austin, TX.", "links": null }, "BIBREF1": { "ref_id": "b1", "title": "Intelligent Mobile Agents in the Military Domain", "authors": [ { "first": "S", "middle": [], "last": "Mcgrath", "suffix": "" }, { "first": "D", "middle": [], "last": "Chac-N", "suffix": "" }, { "first": "K", "middle": [], "last": "Whitebread", "suffix": "" } ], "year": null, "venue": "Proc.. O f Autonomous Agents 2000 Workshop on Agents i n Industry", "volume": "", "issue": "", "pages": "", "other_ids": {}, "num": null, "urls": [], "raw_text": "McGrath, S., Chac-n, D., and Whitebread, K. Intelligent Mobile Agents in the Military Domain. In Proc.. O f Autonomous Agents 2000 Workshop on Agents i n Industry. Barcelona, Spain.", "links": null }, "BIBREF2": { "ref_id": "b2", "title": "Organization, Communication, and Control in the GALAXY-II Conversational System", "authors": [ { "first": "S", "middle": [], "last": "Seneff", "suffix": "" }, { "first": "R", "middle": [], "last": "Lau", "suffix": "" }, { "first": "J", "middle": [], "last": "Polifroni", "suffix": "" } ], "year": 1999, "venue": "Proc.. of Eurospeech \u00d498", "volume": "", "issue": "", "pages": "", "other_ids": {}, "num": null, "urls": [], "raw_text": "Seneff, S., Lau, R., and Polifroni, J. 1999. Organization, Communication, and Control in the GALAXY-II Conver- sational System. In Proc.. of Eurospeech \u00d498. Budapest, Hungary.", "links": null }, "BIBREF3": { "ref_id": "b3", "title": "A Three-tiered Evaluation Approach for Interactive Spoken Dialogue Systems", "authors": [ { "first": "K", "middle": [], "last": "Stibler", "suffix": "" }, { "first": "J", "middle": [], "last": "Denny", "suffix": "" } ], "year": 2001, "venue": "Proc.. of the Human Language Technology Conference HLT-2001", "volume": "", "issue": "", "pages": "", "other_ids": {}, "num": null, "urls": [], "raw_text": "Stibler, K., and Denny, J. A Three-tiered Evaluation Ap- proach for Interactive Spoken Dialogue Systems. In Proc.. of the Human Language Technology Conference HLT- 2001, Mar, 2001, San Diego, CA.", "links": null } }, "ref_entries": { "FIGREF0": { "type_str": "figure", "text": "The LCS-Marine architecture.", "uris": null, "num": null }, "FIGREF1": { "type_str": "figure", "text": "The Marine logistics ordering chain.", "uris": null, "num": null }, "FIGREF2": { "type_str": "figure", "text": "Partially Complete Rapid Request Form along with a portion of the database.", "uris": null, "num": null }, "FIGREF3": { "type_str": "figure", "text": "The physical LCS-Marine server layout.", "uris": null, "num": null }, "FIGREF4": { "type_str": "figure", "text": "The LCS-Marine actual operational layout.", "uris": null, "num": null } } } }