Abstract: A radio communication system (100) has distributed operational control. Multiple autonomously operable computer workstations (120) are linked to a radio communication database (175) via a computer network (130). A local database (211), corresponding to a view of the radio communication database (175), is stored on each computer system (120). A radio system console operator interface (206) is configured according to information in the local database (211), and is operated to perform operational control of a portion of the radio communication system (100). Data consistency of the information stored in the local database (211) is automatically maintained.

Abstract: A computer system (110) has a multi-processing software application operating (200) thereon. There are multiple client processes (221-228) concurrently operating as components of the multi-processing software application (200). Termination of the multi-processing software application (200) results from individual decisions made at each client process (221-228). If a particular client process determines that another client process is inoperable (530), the particular client process continues operation when the inoperable process is designated non-mandatory (550, 510), and terminates operation when the inoperable process is designated mandatory (550, 580, 598). Furthermore, when the inoperable process is designated single-instance mandatory and belongs to a particular process class, the particular client process continues operation unless it is the only member of the process class operating (580, 590, 595, 598).

Abstract: A multi-processing software system (200) has multiple operating processes (221, 222, 223, 224, 225, 226, 227, 228) that communicate with each other using messages. Each process has a corresponding process class (410, 411, 412, 413). Each message is assigned a message type (450, 451, 452, 453), and messages types are mapped (400) to least one process class. A particular message is routed to processes having a process class corresponding to the one or more process classes mapped to the message type of the particular message.