Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Basic Functional Capabilities for a Military Message Processing Service

IP.com Disclosure Number: IPCOM000128630D
Original Publication Date: 1974-Dec-31
Included in the Prior Art Database: 2005-Sep-16
Document File: 31 page(s) / 94K

Publishing Venue

Software Patent Institute

Related People

Ronald Tugender: AUTHOR [+4]

Abstract

I 2. Current Military Record Communication Summary 3 3. Overview of Automated Military Message Service 5 Creation 5 Coordination 5 Release 6 Transmission 6 Delivery 7 Reception 7 Archival 7 4. Automated Military Message Service Definitions 9 Primitive Definitions 9 Text Item 9 Date 10 Time 10 Name 10 Title 11 Organization 11 Priority 11 Security Classification 12 Special Handling 12 Message Type 13 Signoff 13 Version Number 14 Compound Definitions 14 User-ID 15 Reviewer Is Address 15 Recipient 16 Date-Time 16 Message-[D 16 Message 17 5. Military Message Service Functional Specifications 21 Preparation Phases 21 Dramatis Personae 21 Available Capabilities 23 User Characterizations During Preparation 31 Post -Preparation Phases 38 Transmission 38 Delivery 39 Reception 41 Archival 44 Administrative Functions 44 Appendix 47

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 4% of the total text.

Page 1 of 31

THIS DOCUMENT IS AN APPROXIMATE REPRESENTATION OF THE ORIGINAL.

Basic Functional Capabilities for a Military Message Processing Service

Ronald Tugender Donald R. Oestreicher

ARPA ORDER NO. 2223

ISIIRR-74-23 May 1975

INFORMATION SCIENCES INSTITUTE

46 76 Admiralty WaylMarina del ReylCalilornia 90291 UNIVERSITY oF SOUTHERN CALIFORNIA fl- (213) 822-1511

THIS RESEARCH IS SUPPORTED BY THE ADVANCED RESEARCH PROJECTS AGE-NCY UNDER CONTRACT NO. DAHC15 72 C 0308, ARPA ORDER NO. 2223 PROGRAM CODE NO. 3D30 AND 3PIO.

VIEWS AND CONCLUSIONS CONTAINED JN THIS STUDY ARE THE AUTHOR'S AND SHOULD NOT BE INTERPRETED AS REPRESENTING THE OFFICIAL OPINION OR POLICY OF ARPA, THE U.S. GOVERNMENT OR ANY OTHER PERSON OR AGENCY CONNECTED WITH THEM.

THIS DOCUMENT APPROVED FOR PUBLIC RELEASE AND SALE: DISTRIBUTION IS UNLIAITED.

CONTENTS

Preface V

1. Introduction I 2. Current Military Record Communication Summary 3

3. Overview of Automated Military Message Service 5 Creation 5 Coordination 5 Release 6 Transmission 6 Delivery 7 Reception 7 Archival 4. Automated Military Message Service Definitions 9 Primitive Definitions 9 Text Item 9 Date 10 Time 10 Name 10 Title 11 Organization 11 Priority 11 Security Classification 12 Special Handling 12 Message Type 13 Signoff 13 Version Number 14 Compound Definitions 14 User-ID 15 Reviewer Is Address 15 Recipient 16 Date-Time 16 Message-[D 16 Message 5. Military Message Service Functional Specifications 21 Preparation Phases 21 Dramatis Personae 21 Available Capabilities 23 User Characterizations During Preparation 31 Post -Preparation Phases 38 Transmission 38 Delivery 39 Reception 41 Archival 44 Administrative Functions 44

Appendix 47

Bibliography 51

PREFACE

University of Southern California Page 1 Dec 31, 1974

Page 2 of 31

Basic Functional Capabilities for a Military Message Processing Service

This document is one of a series describing an experimental message service being developed for the Advanced Research Projects Agency of the Department of Defense, part of a larger effort directed at the problems of the military message processing community. The goal of this larger effort is to design and prove the efficacy of a system for automated message handling. This document should provide the basis for discussion and refinement of the concept with representatives of several military message environments.

The message service described herein has been designed to be part of a new military command and control capability. This work is a fresh look at these problems, Independent of the constraints of current command and control systems, although interim use will require interfacing to existing systems, including AUTODIN and the ARPANET message protocol.

The main goal of this document is to describe the functional capabilities necessary to support military message processing (details of implementation are addressed elsewhere, and are considered beyond the scope of this description). This document is not directed at any particular ...