CN117296346A - Hypergraphic custom communication group with isomorphic structure - Google Patents

Abstract

Some embodiments include an electronic device of a first institution configured to establish communication with a second institution via an interoperable communications network. The electronic device may include a processor configured to create an isomorphic structure including first and second node elements in a hierarchical structure. The processor may instantiate an interactive visual diagram (IVC) for the activated isomorphic structure, wherein first and second node elements correspond to first and second communication group identifiers (IDs). The processor may send a first invitation including an instantiated IVC for the activated homogeneous structure, and in response to the first invitation being accepted, instantiate the first communication group corresponding to the first communication group ID and the first communication group corresponding to the A second communication group of two communication group IDs, wherein the first member and the second member are peers corresponding to the first node element of the activated homogeneous structure.

Description

Isomorphic structured hypergraph custom communication group

Technical field

Embodiments relate generally to custom communication groups, and more particularly to hypergraph custom communication groups utilizing homogeneous structures.

Background technique

Modern emergency management principles require a coordinated multi-agency, multi-disciplinary response framework. These principles are incorporated into the U.S. Department of Homeland Security’s National Response Framework (NRF) and its corresponding policies and guidance, such as the National Incident Management System (NIMS), the National Emergency Communications Plan (NECP), and the National Infrastructure Protection Plan (NIPP). Although these principles are defined, implementing them when responding to emergencies can be difficult.

Contents of the invention

An incident communications network enables interoperable communications between communications resources controlled by multiple organizations or individuals during an incident involving emergency or pre-planned multi-organization communications, where the communications resources are controlled by administrators within the organization or by Personal control. The incident communications network includes an Interoperability Workstation (IWS) controller, which controls communications resources and enables users to control and interface with the incident communications network.

U.S. Patent Nos. 7,643,445, issued on January 5, 2010, entitled Interoperable Communications System and Method of Use, and U.S. Patent Nos. 7,643,445, issued on November 27, 2012, entitled U.S. Patent No. 8,320,874, System and Method for Establishing an Incident Communications Network, describes a method for providing an interoperable communications system that includes multiple otherwise separate or distinct communications systems ( Systems and methods for "interoperable systems", also known as incident communication networks, which address deficiencies of existing technology systems. The '445 and '874 patents specifically describe methods for establishing an incident communications network that enables reliable communication between communications resources controlled by multiple organizations during an incident involving emergency or pre-planned multi-organization communications. Interoperable communications where communications resources are controlled by administrators within the organization.

In addition, the U.S. Patent Law entitled Mobile Interoperability Workstation Controller Having Video Capabilities within an Incident Communications Network, issued on January 29, 2013, is also incorporated herein by reference in its entirety. Patent No. 8,364,153 (the "Mobile IWC Patent") expands on the concepts of the '445 and '874 patents. That said, the mobile IWC patent includes enhanced video capture and streaming capabilities integrated with incident information and events to facilitate improved management and analysis of incidents or events employing an incident communications network.

U.S. Patent 8,811,940 entitled Dynamic Asset Marshalling Within an Incident Communications Network, issued on August 19, 2014 (the "Marshalling Patent"), which extends '445, is also incorporated by reference in its entirety. and the concept of the '874 patent. That is, the grouping patent provides systems and methods for grouping resources into an incident communication network based on various factors, such as the type of resource being grouped and the type of incident.

As extended by U.S. Patent 8,929,851 entitled System and Method for Establishing an Incident Communications Network, issued January 6, 2015 (the "'851 Patent"), which is incorporated by reference in its entirety. Concepts from the '445 and '874 patents, the grouping patent and the mobile IWC patent.

Incident communications networks are described in the '445, '874 and '851 patents, the marshalling patent and the mobile IWC patent, which are incorporated herein by reference.

Some embodiments include systems, methods, and computer program products for instantiating hypergraphic custom communication groups based on homogeneous structures activated during an incident. For example, an agency or organization can create isomorphic structures, such as an Incident Command System (ICS) structure for chemical and/or biological disasters. In the event of an accident associated with an isomorphic structure (e.g., mass casualty chemical and/or biological catastrophic event), some embodiments enable a first agency IWS to instantiate an instance of the isomorphic structure and create a corresponding An instantiation of a structure that instantiates two or more communication groups (eg, SIP protocol sessions) of node elements. The first agency can invite the second agency to instantiate the second agency's corresponding isomorphic structure (e.g., a mass casualty chemical and/or biological catastrophic event), which enables members of the second agency to communicate with the second agency via the corresponding communication group created. communicate with its corresponding peer in the first organization.

Some embodiments include a system for a first mechanism, such as an IWS including a transceiver and a processor coupled to the transceiver. The processor establishes communication with the second mechanism via the transceiver over the interoperable communications network. The processor creates an isomorphic structure including first and second node elements in the hierarchy and instantiates a temporal instance of the isomorphic structure. The processor instantiates an interactive visual chart (IVC) for an instantiation-time instance of the homogeneous structure, wherein a first node element corresponds to a first communication group identifier (ID) and a second node element corresponds to a second communication group ID. The processor sends via the transceiver a first invitation including an instantiated IVC for an activated time instance of the homogeneous structure, and in response to the first invitation being accepted, instantiates a first communication group corresponding to the first communication group ID and A second communication group corresponding to the second communication group ID. The first communication group includes a first member of a first organization and a second member of a second organization, wherein the first member and the second member are peers corresponding to a first node element of an activated temporal instance of the isomorphic structure . The activated isomorphic structure may be an Incident Command System (ICS) structure.

To populate the time-instantiated IVC for activation of the homogeneous fabric with members of the first organization, the processor sends, via the transceiver, a second invitation to the first device of the first member of the first organization to accept the request corresponding to the first The function of the node element. In response to the second invitation being accepted, the processor assigns a first communication group ID corresponding to the first node element to the first device or the first member. For example, assignments can change as work shifts change. The processor sends a third invitation to the first member's first device via the transceiver to continue accepting functionality corresponding to the first node element (eg, whether to continue working at the same location for another work shift). In response to the third invitation being rejected (eg, the first member utilizes a work shift change assignment), the processor sends a fourth invitation to another device of another member of the first organization to accept functionality corresponding to the first node element. In response to the fourth invitation being accepted (eg, another member replaces the first member), the processor reassigns the first communications group ID corresponding to the first node element to another device or to another member.

Some embodiments include a graphical user interface (GUI) coupled to the processor, wherein the GUI includes hypergraphical selectable items corresponding to one or more created isomorphic structures including the isomorphic structures. The processor receives a first selection of a first hypergraphic selectable item corresponding to the isomorphic structure via the GUI and activates a temporal instantiation of the isomorphic structure. The processor receives, via the GUI, a selection of a second hypergraph selectable item corresponding to a first node element of an instantiated IVC for an activated temporal instantiation of the isomorphic structure. In response to receiving a selection of the second hypergraphic selectable item, the processor sends, via the transceiver, a second invitation to the first device of the first member of the first organization to accept functionality corresponding to the first node element. In response to the second invitation being accepted, the processor assigns the first communication group ID to the first device or the first member. The first communication group ID may correspond to: a push-to-talk radio network, a mobile push-to-talk network, a voice or video conference call network.

In some embodiments, the processor instantiates a parallel session that includes peer members from a first organization and a third organization coupled to the interoperability communications network, wherein the peer members correspond to an activated time instance of the homogeneous structure. The corresponding node element in the hierarchy.

In some embodiments, the processor creates a member directory that includes a first organization subdirectory, publishes the first organization subdirectory, receives a second organization subdirectory, and updates the members directory to include the second organization subdirectory. In some embodiments, the processor publishes one or more incident types supported by the first agency, receives incident types supported by the second agency, and updates the member directory to include incident types supported by the second agency.

Other embodiments, features and advantages, as well as the structure and operation of various embodiments are described in detail below with reference to the accompanying drawings. It is noted that the embodiments presented here are for illustrative purposes only. Other embodiments will be apparent to those skilled in the relevant art(s) based on the teachings contained herein.

Description of drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description serve to explain the principles of the invention.

Figure 1A illustrates an example system for establishing an interoperability communication group during an incident, in accordance with some embodiments of the present disclosure.

Figure IB illustrates an example system for a homogeneously structured hypergraph custom communication group during an incident, in accordance with some embodiments of the present disclosure.

Figure 2 illustrates an example system for instantiating a predefined communication group during an incident in accordance with some embodiments of the present disclosure.

3 illustrates an example system for instantiating a homogeneous structured hypergraph custom communication group during an incident in accordance with some embodiments of the present disclosure.

4 illustrates an example method for instantiating a hypergraph custom communication group of a homogeneous structure during an incident, in accordance with some embodiments of the present disclosure.

Figure 5 illustrates an example method for populating a hypergraphic interactive visual chart (IVC) of an isomorphic structure during an incident, in accordance with some embodiments of the present disclosure.

Figure 6 illustrates an example computer system for implementing certain embodiments or portions thereof.

Figure 7 illustrates an example incident command system (ICS) structure for hospital use in accordance with some embodiments, or portion(s) thereof.

8 illustrates an example block diagram of a system for establishing a homogeneously structured hypergraph custom communication group during an incident, in accordance with some embodiments of the present disclosure.

Detailed ways

Some embodiments include a system, method, and computer program product that instantiates a homogeneously structured hypergraph custom communication group during an incident, wherein the communication group enables communication between peers in different organizations, wherein Communication groups correspond to activated time-instantiated node elements of the isomorphic structure.

FIG. 1A illustrates an example system 100A for establishing an interoperability communication group during an incident, in accordance with some embodiments of the present disclosure. System 100A includes Organization 1's interoperability workstation (IWS) 110 and Organization 2's IWS 180. In the event of an incident (eg, explosion), IWS 110 may send an invitation message 165 to Agency 2's IWS 180 to invite Agency 2, including one or more of Agency 2's communication resources, to join the communication group. The one or more communication resources (eg, smartphone device, land mobile radio not shown) are communicatively coupled to IWS 180 . If IWS 180 accepts invitation message 165 (eg, by sending an accept message (not shown) to IWS 110 ), then connections 175 and 177 to interoperability network 170 (eg, an IP network) are established between Organization 1 and Organization 2 Communication group (e.g., SIP protocol-based session). In one example, Institution 1 and Institution 2 may be Hospital 1 and Hospital 2.

The expanded framework for emergency management includes the Incident Command System (ICS) promulgated by the U.S. Department of Homeland Security-Federal Emergency Management Agency (FEMA). ICS proposes a hierarchical organizational command structure composed of rules premised on functional domains, where functions, purposes, or other distinctions define nodes, subnodes, and nodes of subnodes to infinity. In order to adopt ICS, the organization's capabilities and functions must conform to the generalized ICS node structure, its hierarchical relationships, and defined functional divisions. When they cannot, the organization can modify its ICS node structure and organizational relationships to best fit the organization's functions. Divisions and abilities.

Figure 7 illustrates an example ICS structure 700 for hospital use in accordance with certain embodiments or portion(s) thereof. The ICS structure of Example 700 is a isomorphic structure. Example 700 is a node that includes one or more node elements. Example 700 includes the highest level node element, Incident Commander 710, and below the command level there are defined functional node elements, which may be departments such as Public Information Officer 720, Logistics Director 740, and Planning Director 730. There are defined positions in each node element, such as supervisor, team leader, director and other position names that describe the function or purpose of the work. The connections of node elements to other node elements in a hierarchical relationship or grouping are further defined by the general scope of the control rules, which establish the multiple preferred affiliations that may exist from a node element to its child nodes in a dynamic cascade structure. Some departments include various sub-departments or branches, and some branches include various sub-branches or units. Relationship structures can be further divided and made different. Some of these can be divided into organizational units called teams, task forces, and specialists.

Morphologically speaking, ICS structures and construction rules can be conceptualized translationally as generating different vertices (e.g., ICS nodes) and connecting edges (e.g., ICS node hierarchical relationships) of isomorphic structures. The parent-child relationship between ICS nodes is created through hierarchical command rules, under which an ICS node is subordinate to its superior node. Each ICS node includes at least one node element (eg, a control element) defined as a command or high-level location, and all other location node elements that are members of the ICS node are directly or subordinate to the control element. In addition, there may be other subordinate node elements with control functions that control a subset of the location node elements and thus have their own control elements.

As mentioned above, the construction rules of an ICS generate different isomorphic instances (eg, example 700) of the ICS structure when created by different organizations or groupings of organizations. These instantiations are sufficiently similar in other disparate organizations or groups of organizations to enable general functionality or special functionality from one disparate organization to another (e.g., including, but not limited to, Incident Commander 710, Public Information Officer 720 , planning director 730, logistics director 740 node elements) for coordination or joint operations.

The ICS structure and its various ICS nodes and node elements can be developed by each agency or organization in accordance with ICS construction guidelines as part of or in addition to the organization's emergency planning. An organization's emergency planning consists of standard operating procedures (SOPs), associated checklists, reports, and actions to be taken in response to various emergencies. ICS implementation is the command and control layer of the organization, which enables SOPs to be directed, executed and monitored. In practice, an organization's ICS structure is adopted in a pre-planned form (e.g., pre-planned incident ICS). In some cases, there is no pre-planned ICS.

In many cases, when ICS is adopted and used in emergencies, the instantiated ICS structure is often handwritten using greased boards, whiteboards, chart paper, and other manual means to represent and visualize the command structure implemented. In some cases, computer software drawing tools output to visually represent ICS structures. In order to assess and make decisions, as well as to execute command instructions and execute functions, communication and information coordination laterally from the field to the headquarters, from the command to the field, and between peer ICS node elements are essential. As the ICS structure expands, the ability to effectively establish formal communications and information sharing groups becomes increasingly difficult and time-consuming, and in many cases is not well defined. The problem of establishing appropriately defined communication and information sharing groups to respond to emergencies is widely known and documented in the field, and remains a significant unsolved issue. Furthermore, current approaches are insufficient because instantiated ICS are non-permanent and can change during an incident. The assignment of personnel to node elements may change. Additionally, certain functional domains represented by one or more ICS nodes may change state from inactive, active, or deactivated in response to and recovery from emergencies based on changing circumstances, conditions, and other factors. Handwritten diagrams, or even computer software drawing tools, cannot solve this major unsolved problem.

Some embodiments include systems, methods, and computer programming products that automatically establish defined communication and information sharing groups that are enabled or activated in response to an emergency transaction or event. This is achieved by associating membership assigned to node elements within an adopted or instantiated isomorphic structure (e.g., ICS structure) as the basis for group identity and membership, and further enabling as a superset or sub-set of ICS nodes Set of other defined communication groups. By doing so, people assigned membership to ICS nodes and locations within them are automatically grouped into defined communication groups.

FIG. 1B illustrates an example system 100B for homogeneously structured hypergraphic custom communication groups during an incident, in accordance with some embodiments of the present disclosure. For convenience and not limitation, system 100B may be described with elements of other figures within this disclosure. System 100B includes Hospital 1's IWS 110 and Hospital 2's IWS 180. As described in Figure 1A, when an incident occurs, IWS 110 may send an invitation message 165 to IWS 180. After IWS 180 responds with an Accept message, a communication group (eg, a SIP session) is established between Hospital 1 and Hospital 2. IWS 110 determines which communication resources of Hospital 1 can join the communication group, and IWS 180 determines which communication resources of Hospital 2 can join the communication group. Communication occurs via connection 175 , interoperability network 170 and connection 177 .

Hospital 1's IWS 110 may include a graphical user interface (GUI) that includes a member directory 120 that includes information about groups of personnel from Hospital 1 130, Hospital 2 150, local police 155, and an isomorphic structure 160. In some embodiments, homogeneous structures 160 may be nodes, and may include example 700 of FIG. 7 . As an example, Hospital 1 130 includes Hospital Security 135, which may include names, contact information, etc. of personnel who provide hospital security functions. Hospital Office of Emergency Management (OEM) 140 may include groups such as Directors 142, Planning 144, and Public Information 146, each of which may include one or more names and contact information for the corresponding personnel. Hospital 2's IWS 180 may include its respective personnel in the membership directory 182 . Hospital 1 and Hospital 2 may publish their respective directories to institutions and/or organizations with which they have relationships (eg, trusted relationships between trusted parties). Accordingly, member directory 120 may include Hospital 2 personnel information published by Hospital 2 and represented by Hospital 2 150 . Additionally, Hospital 1 and Hospital 2 can publish and share their incident types that define a homogeneous structure for emergencies.

Isomorphic structures 160 (eg, ICS structures) may be dynamically scalable and morphologically flexible. Within an agency or organization, such as local public safety or a hospital, a homogeneous structure 160 may be created to facilitate a well-organized and structured emergency response. The same construct can apply to a joint or unified command environment, where two or more agencies or organizations work together under an ICS structure and coordinate with each other in an emergency-driven context. For example, Hospital 2's homogeneous structure 186 may have the same configuration as Hospital 1's homogeneous structure 160 so that hospitals can work together during an emergency.

Figure 2 illustrates an example system 200 for instantiating a predefined communication group during an incident in accordance with some embodiments of the present disclosure. For convenience and not limitation, system 200 may be described with elements from other figures in this disclosure. Member directory 120 may also include personnel (eg, members) from other agencies, such as state police 250 , a favorites list 210 of frequently contacted personnel, and incident types 220 . Some incident types include hospital fire224 and active shooter226. Selecting active shooter 226 on the GUI of IWS 110 can instantiate a predefined communication group, which includes sending invitation messages 230, 240, and 250 to hospital security 260, local police 270, and state police 280. After hospital security 260, local police 270, and state police 280 accept their respective invitations, a secure communications group can be established over interoperable network 170 via connections 175, 265, 275, and 285.

3 illustrates an example system 300 for instantiating a homogeneously structured hypergraph custom communication group during an incident in accordance with some embodiments of the present disclosure. For convenience and not limitation, system 300 may be described with elements in other figures in this disclosure. System 300 may include other types of incidents that may be based on isomorphic structure 160 , such as mass casualty biological and chemical 320 . The types of specialists and specialized units required for chemical and biological decontamination and treatment are different from the emergencies that require a medical response to crushes and burns. When an incident occurs, a time instance of Mass Casualty Biochemical 320 shown as 10-29 Mass Casualty Biochemical Incident 330 may be created or instantiated. The instantiated instance, ie, 10-29 mass casualty biochemical accident 330, may be represented by an interactive visual diagram (IVC) 335. In some embodiments, IVC 335 represents a node, and the rectangles therein represent node elements. Rectangles can be an optional item of IVC 335. Although shown as a rectangle, selectable items can have different shapes and/or sizes.

IVC 335 can be populated by people from member directory 120 . For example, incident commander node element 360 (which may be incident commander 710 of FIG. 7 ) may be populated by personnel from the hospital OEM director 142 section of member directory 120 , as shown by dashed line 365 . Public Information Officer node element 370 (which may be Public Information Officer 720 of FIG. 7 ) may be populated by personnel from the Hospital OEM-Public Information 146 section, as indicated by dashed line 385 . And the planning director node element 380 (which may be the planning director 730 of FIG. 7 ) may be populated by personnel from the hospital OEM-Planning 144 portion, as shown by dashed line 375 . More details about padding are described in Figure 5.

10-29 The instantiation of the mass casualty biochemical incident 330 also includes the creation of two or more peer communication groups between agencies and/or organizations that include isomorphic structures corresponding to the isomorphic structure 160 . In example system 100B of FIG. 1B , hospital 2 includes isomorphic structure 186 , which is a isomorphic structure corresponding to isomorphic structure 160 . The IWS110 of Hospital 1 can send the invitation message 10-29 Mass casualty biochemical accident invitation 340 to the IWS180 of Hospital 2. After IWS 180 accepts the invitation by sending an accept message (not shown), two or more peer communication groups may be instantiated, with communication occurring via interoperability network 170 (not shown). The IWS 180 may create the IVC 350 based on the homogeneous structure 186 of the system 100B and populate the corresponding functions of the IVC 350 with appropriate hospital 2 personnel as reflected in the member directory 182 .

In some embodiments, when 10-29 Mass Casualty Biochemical Incident 330 (e.g., node) is instantiated, each node element (e.g., each function represented by a selectable item such as a rectangle) of IVC 335 may ) instantiates the communication group. Two or more communication groups can be instantiated in parallel. The instantiated peer communication group (e.g., peer talk group or parallel communication session) may include the following: Incident Commander Communication Group, whose membership includes Hospital 1 personnel assigned to Incident Commander Node Element 360 and Hospital 2 personnel for Commander Node Element 352; the Public Information Officer Communications Group, whose membership includes Hospital 1 personnel assigned to Public Information Officer Node Element 370 and Hospital 2 personnel assigned to Public Information Officer Node Element 354; and Planning Director Communications A group whose membership includes Hospital 1 personnel assigned to Planning Director node element 380 and Hospital 2 personnel assigned to Planning Director node element 356 . Subsequently, Incident Commander personnel from Hospital 1 and Hospital 2 can communicate through the Incident Commander Communications Group.

Additionally, IWS 110 may send invitations such as the 10-29 Mass Casualty Biochemical Incident to other organizations with corresponding isomorphic structures 160 (eg, not shown trusted parties such as other hospitals, state police, and/or other agencies) 340 invitation message. After the other organization accepts the invitation, the other organization instantiates and populates the corresponding IVC. Their personnel corresponding to the respective functions of the IVC 335 (eg, a node element such as the Incident Commander Node Element 360) may be included as members of the respective communications group instantiated by the 10-29 Mass Casualty Biochemical Incident 330. Accordingly, appropriate personnel may join the incident commander communication group (eg, talkgroup) and begin communicating with the incident commander, such as node element 360 and node element 352 . Therefore, the ability to instantiate multiple communication groups (e.g., multiple sessions in parallel) when instantiating an incident (e.g., 10-29 Mass Casualty Biochemical Incident 330) can save a lot of time and effort, especially with manually lubricated plates Or compared to the electronic bulletin board method.

In system 300, certain physicians at local fire stations and local hospitals may be grouped as described in the grouping patent to join the incident communications network. However, in this disclosure, the entirety of Hospital 1 and the entirety of Hospital 2 are defined within the activation event of their respective isomorphic structures (e.g., ICS structures), and then due to the isomorphic nature of the ICS structure, their respective ICS Activation incidents of the structure (e.g., 10-29 Mass Casualty Biochemical Incident 330 and IVC 335 and IVC 350) are targeted. Thereafter, peer communication groups that activate the incident across corresponding ICS structures may be instantiated (eg, two or more peer communication groups are instantiated substantially in parallel in time) to resolve the crisis. Additionally, membership within the peer communications group is fluid and determined by the appropriate agencies (e.g., Hospital 1 and Hospital 2) rather than by the joint command structure commander (e.g., personnel changes, transfers to different locations, People were promoted, some resigned, etc.). Although the isomorphic structure 160 may exist in the plan, it is not until 10-29 that the mass casualty chemical and biological incident 330 is instantiated and each institution (e.g., Hospital 1 and 2) activates its respective isomorphic structure incident (e.g., 10-29 Custom communication groups only exist for Mass Casualty Biological and Chemical Incidents 330, IVC 335 and IVC350). Even within each agency's instantiated incident ICS structure (e.g., 10-29 Mass Casualty Biochemical Incident 330, IVC 335 for Hospital 1), membership within the corresponding custom communication group can be fluid.

8 illustrates an example block diagram of a system 800 for establishing a homogeneously structured hypergraph custom communication group during an incident, in accordance with some embodiments of the present disclosure. For convenience and not limitation, FIG. 8 may be described using elements of other figures in this disclosure. For example, system 800 may be IWS 110 or IWS 180 of Figure IB, or a mobile IWS (not shown). System 800 may include an incident controller 850 (e.g., one or more processors) that may execute instructions stored in memory (e.g., computer-readable media) to perform the following functions: a supervisory module 810, a graphical user interface ( GUI) 820, homogeneous structure communication group module 840, homogeneous structure incident module 860 and communication module 870. Communication module 870 may include one or more network interfaces, including but not limited to wireless or wired network interfaces and various networking protocols.

The homogeneous structure incident module 860 may include a software application module coupled to a database 830 , which may be a data store, in which a homogeneous structure (eg, ICS structure 160 ) is graphically represented in a hierarchical or logical grouping manner. ICS structure 160 may be an object to which a unique identification and naming convention may be assigned, where the object may be composed of at least one ICS node. Each ICS node may be related to another ICS node in a hierarchical relationship, where one ICS node is the parent node of one or more other child ICS nodes, or has no related subordinate ICS nodes. Each ICS node may be assigned or associated with one or more functional domains, geographic domains, or other defining characteristics. An ICS node (eg, ICS structure 160) may include one or more node elements (eg, node elements 360, 370, 380, 352, 354, 356), which may be objects with unique IDs and names. Each node element may include one or more locations with a unique ID and an associated name, which may be an organizational title, a job location, or any other relevant designation to which a person may be assigned.

Supervision module 810 may include various node elements that assign personnel (eg, Hospital 1 personnel) to instantiated isomorphic structures (eg, 10-29 Mass Casualty Biochemical Incident 330 represented by Interactive Visual Diagram (IVC) 335 ) function. For example, the supervisory module 810 may assign the hospital OEM-responsible person 142 to the incident commander node element 360 , as shown by dashed line 365 . Note that different types of incidents (such as fires) may result in different personnel being assigned to the incident commander's node element. Additional allocations may occur but are not shown to simplify system 300. Each node element (eg, incident commander node element 360, public information officer node element 370) may have associated properties including: function and functional description; assigned conditional qualifications, such as organizational membership, employment or employment status, Good standing, professional certifications, skills, security clearance level, personnel availability, proximity, age, health, language skills and/or any other qualification factors relevant to the performance of the functions assigned to the node element; when personnel may be assigned to slots or periods of time (e.g., specific shifts, temporary assignments); and/or identifying information (e.g., node assignment identification (ID)) of any person assigned to a node element assignment.

The node assignment ID assigned to any person assigned to a node element may include the following information about the assigned person: name; employer or membership affiliation with an organization (e.g., Hospital 1, local police); employer or member affiliation identification, such as an employee ID or badge number, or certification license number, personnel ID number or certification based on an accident and/or incident; Personally identifiable information, including Social Security number, driver's license number, passport number and/or other personally identifying information; Related to personal health data, including disease, disease or exposure susceptibility, and other health factors; and/or communications addressing and contact information for the assignee or assignee proposed to be a node element.

Examples of assignee communications addressing and contact information include, but are not limited to: member communications ID; telephone number and telephone session access code; land mobile radio or push-to-talk network user or device ID, channel ID, talk group, call sign and/or other identifiers; IP network user ID, network address including Uniform Resource Locator, SIP address and MAC, proxy address and other related network connection protocol or required addressing information including port ID, encryption type and/or or token; email address; text and SMS user ID; and/or social media user ID.

For node element assignments, one or more people may be assigned to each node element (eg, as a member) by the regulatory user via the graphical user interface (GUI) 820 of the regulatory module. For example, GUI 820 may display IVC 335 with node elements shown as rectangles in selectable item-system 300 . The Node Element Assignment may be a module of the Supervision Module 810 where the member's Node Assignment ID information may be entered and stored by the institution. The node assignment ID module may be electronically linked and retrieved to invoke or verify the assignee's node assignment ID information from a separate or existing database 830, registry, directory, or service that contains some or all such information.

Node element assignment may include one or more rules or process steps, including but not limited to the following: i) the institution may assign a member without prior permission or consent and send a notification to the member; ii) the institution may target the member The assignment is made to the member (or another person with authority) granting consent or acceptance of the assignment; iii) the institution sends a request to the proposed member (or another person with authority) seeking consent or acceptance of the assignment; iv) the institution sends a request to a or Invitations are sent to multiple intended assignees in response to invitations to accept or decline the assignment. See Figure 5. Transmission may include the transmission of a message in any form or reduction to human readable or interpretable form by any medium including oral, written, auditory or visual means and any medium including electronic transmission, posting of a message or invitation to receive to send messages or instructions.

A node element assignment may have a status such as pending, standby, active, paused, unqualified, unconfirmed, confirmed, provisional, or any other descriptive status it is in. Node element assignments can be: predetermined and assigned to a node element, or initiated when an ICS node (e.g., 10-29 Mass Casualty Biochemical Incident 330) or node element is activated. The status assigned to a node element may change based on any triggering event, including a status change initiated by an institution, or may be initiated automatically by a status change in an ICS node or ICS object.

For any ICS object, the isomorphic incident module 860 may include functions that assign or associate functions or operate emergency purposes or incident contexts, which may include the nature or type of the emergency or incident, the location or severity of the emergency or incident, The geographic scope or size of the emergency or incident, the declared status of the emergency, or the role or purpose assigned or delegated to the ICS object by another entity for the emergency or incident. For example, if a truck carrying toxic chemicals had an accident on the highway on October 29, and many people were affected, the isomorphic structure accident module 860 can convert an instance of Mass Casualty Biochemical 320 (10-29 Mass Casualties and Biological Accidents 330) are assigned to toxic chemical truck highway accidents.

For example, the Isomorphic Structural Incident Module 860 may include functionality to assign or associate a purpose or instantiated state to any ICS object (e.g., 10-29 Mass Casualty Biochemical Incident 330), including but not limited to the following: For operational purposes ;For training purposes;For regulatory purposes;As a template from which a different ICS object can be created by copying the object and the corresponding ICS nodes and node elements and associated properties that can be further edited and modified;As being processed and has not yet been designated as a completed draft ICS object; has been approved or adopted by one or more authorities; is in a state to be consistent with or subject to changes in existing laws, rules, policies, practices, customs or guidelines; has become obsolete due to time; subject to review due to time or review or other process; suspended before specified conditions are met; retired; and/or renewed.

For any grouping that includes an ICS object or any ICS node, node element, or ICS node or node element associated with an ICS object, the isomorphic incident module 860 may include functionality to assign an operating state, such as active, inactive, hung. Start, standby, deactivate, reactivate, or describe an ICS node (e.g., 10-29 Mass Casualty Biochemical Incident 330) or node element (e.g., Incident Commander node element 360, Public Information Officer node element 370, or Planning Director node element 380) other designations of functional status. The functionality of the isomorphic structure incident module 860 may be performed via the GUI 820.

The homogeneous structure communication group module 840 may include functionality to create two or more different communication groups in parallel from an ICS node (eg, 10-29 Mass Casualty Biochemical Incident Communication Group 330) via automated mechanisms and/or manual mechanisms. For example, the homogeneous structure communication group module 840 may associate node element assignments to node elements within an ICS node and assign a unique communication group identification (e.g., communication group ID) to the ICS node (e.g., 10-29 Mass Casualty Biochemical Incident 330 Communication Group ID001).

In some embodiments, the homogeneous communication group module 840 registers the communication group ID with the group communication network and obtains, requests, or establishes and assigns an individual user communication ID (eg, communication group user ID) for each member, where the group The communication network may be a push-to-talk radio network, a mobile push-to-talk network, a voice or video conferencing call network, and/or an interoperable communication network (e.g., interoperable network 170) in which more than one network communication medium may communicate with one or multiple other network communication media interconnections or bridges, such as, but not limited to, land mobile radio talkgroups connected or bridged to users of push-to-talk mobile clients.

In some embodiments, the homogeneous communication group module 840 uses and associates existing member communication IDs to communicate via an interoperable gateway, switching fabric, communication server, or between users coming from and to different network devices. A network for exchanging messages and communications to bridge existing user communication addresses and modalities. For example, the homogeneous communication group module 840 may create, register, and assign a unique proxy communication group user ID to each member that is relationally associated with an existing member communication ID.

The homogeneous structure communication group module 840 may include functionality capable of visually displaying communication group IDs and communication group user IDs associated with any GUI representation of an ICS object or ICS node (eg, IVC 335). The homogeneous structure communication group module 840 may initiate the communication group ID and communication group user at any stage of the instantiation of an ICS object or ICS node (e.g., 10-29 Mass Casualty Biohazard Communication Group 330) via a human user agency or an automated agency. Creation of IDs and/or creation of communication group IDs and communication group user IDs. For example, by using rules based on the occurrence of an event or a change in the condition or status of an event, where the occurrence of an event or a change in the condition or status of an event may be determined by any information communicated to or observed by the agency or agents of the agency. Information transmitted may include messages or notifications sent to the institution from third parties or systems indicating the occurrence of events or changes, including from mass notification systems, private notification systems, warning systems, alarm systems, analytics systems, sensor systems, or monitoring systems. information.

The homogeneous structure communication group module 840 may include functionality for sending a notification to a member notifying the member of the member communication ID assigned to the person, and the notification may include a URL address, a password, an authentication code, a token, or a password. keys to include the following: i) authenticate the identity of the member or the member's communications device; ii) assign encryption keys to or receive encryption keys for any communications session associated with the communications group ID; iii) access and communications Communication sessions associated with the group ID, sending and/or receiving communications and related information to and/or from other members, including but not limited to: audio data, video data and data content sent in or associated with the communication session; iv) Initiate a communication session associated with the communication group ID and invite other members to join the communication session; and/or be invited to participate in the communication session associated with the communication group ID.

The homogeneous structure communication group module 840 may include functionality to send notifications to members to inform members of the status of the communication group associated with the communication group ID (e.g., the status of the 10-29 Mass Casualty Biohazard Communication Group 330 communication group ID), This may include, but is not limited to: operational status, such as active, activated, inactive, deactivated, to indicate whether a communication session may be initiated, is being initiated, or may no longer be initiated; and/or a network login for a member's user communications endpoint status, network availability or presence, user availability or readiness, and/or changes therein.

The homogeneous communication group module 840 may include functionality for a communication endpoint device having a user interface display (such as a mobile push-to-talk client or a software dispatch console) to remotely register with the communication endpoint device and update the user interface to display , access or call the corresponding ICS communication group or its members. After a communications endpoint device is registered, the following updates may occur, including but not limited to the following: associated communications applications; local device or coupled network contact lists; directories or address books; and/or displays. The homogeneous structure communication group module 840 may update, change, or save GUI representations of groups and members on the endpoint device GUI, including icons, images, programmable objects, URIs, network links, UI controls, plug-ins, widgets, or textual representations , which displays the name or identity of the corresponding ICS communication group, and/or displays the membership of the ICS communication group. This change may be initiated through the functionality of the homogeneous fabric communication group module 840 to send commands to the communication endpoint application server or switch. In some examples, changes may be sent or retrieved from a file server or via a file service downloaded by the client device.

In some embodiments, the homogeneous structure communication group module 840 may relationally associate the ICS communication group ID with the ICS object ID or ICS node ID. ICS communication groups may be automatically assigned a name derived from the name assigned to the ICS object or ICS node, the associated incident type or incident, or a combination thereof.

The homogeneous structure communication group module 840 may include representing and displaying an ICS communication group (eg, the incident commander communication group including the incident commander node element 360 and the incident commander node element 352) as an ICS object (eg, IVC 335), ICS The functionality of an application object, application control, or network link in a GUI representation of a node (eg, IVC 335) or its subportions (eg, selectable icons of node elements 360, 370, 380). The representation and display of an ICS communication group enables the following functions: to change the status of an ICS communication group; to initiate an ICS communication group session (e.g., two or more ICS communication group sessions in parallel); and/or to participate as a member's communication endpoint An ICS communication group session in which a communication module (eg, communication module 870) is coupled to a homogeneous communication group module 840 and a GUI application (eg, GUI 820). In some embodiments, the communication session control becomes part of an application (eg, an application that displays an ICS communication group). In some examples, an external control or object, control, or application interface form is functionally, logically, or visually associated with an application (eg, an application that displays an ICS communication group). Examples of GUI 820 functionality include, but are not limited to: display, nesting, overlaying, or positional alignment of independent application windows, synchronizing, coordinating, or sorting views to the front or background, within the user's computer graphics display or across multiple screens Minimize and maximize views relative to other views.

The homogeneous fabric communication group module 840 may include functionality to enable an ICS communication group, which may include one or more ICS nodes, ICS node elements, and/or members. ICS communication groups may be formed in any logical combination, including but not limited to: equivalent grouping of ICS node locations or functional locations across one or more ICS nodes; exclusion of child or parent ICS nodes, or certain members of child or parent ICS nodes; Contains a child or parent ICS node, or certain members of a child or parent ICS node; groups node elements or members by common or shared or consecutive time periods, shifts, functions and/or responsibilities.

In some embodiments, the isomorphic structure incident module 860 can associate two or more ICS objects to form a new ICS object: the two or more ICS objects are logically related to one object designated as the parent object. connection; or each of the two or more ICS objects is designated as a node element or member of a third ICS object. In some examples, two or more ICS nodes associated with independent ICS objects can be associated and form a new ICS node: the two or more ICS nodes include one node designated as a parent node; or Each ICS node is designated as a node element or member of a third ICS node. In some embodiments, the ICS communication group may include a new parent-child ICS object relationship or a new parent-child ICS node relationship; and/or a new third ICS object or a new third ICS node.

4 illustrates a method 400 for instantiating a homogeneously structured hypergraph custom communication group during an incident, in accordance with some embodiments of the present disclosure. For convenience and not limitation, method 400 may be described using elements from other figures in this disclosure. For example, method 400 may be performed by system 800 of FIG. 8 or the example computer system 600 of FIG. 6 .

At 405, system 800 creates a member directory that includes a first organization subdirectory that includes corresponding first organization members. In system 100B, Hospital 1's IWS 110 creates member directory 120.

At 410, system 800 sends an invitation to the second organization via the interoperability communications network to establish secure communications. In system 100B, Hospital 1's IWS 110 sends an incident invitation message 165 to Hospital 2's IWS 180 to establish secure communications via interoperability network 170.

At 415, system 800 receives acceptance of the invitation. In system 100B, Hospital 1's IWS 110 receives an acceptance of the invitation from Hospital 2's IWS 180.

At 420, system 800 establishes secure communications with the second organization. In system 100B, Hospital 1's IWS 110 establishes secure communications with Hospital 2's IWS 180 via connection 175, interoperability network 170, and connection 177.

At 425, system 800 publishes the first organization subdirectory. In system 100B, IWS 110 publishes Hospital 1 data for member directory 120 . The IWS 180 receives the published Hospital 1 data and includes it in the member directory 182 .

At 430, the system 800 receives a second organization subdirectory that includes corresponding members of the second organization. In system 100B, IWS 180 publishes hospital 2 data for member directory 182.

At 435, system 800 updates the members directory to include the second organization subdirectory. In system 100B, IWS 110 receives the published Hospital 2 data and includes it in member directory 120, shown as Hospital 2 150. Hospital 2 150 may include many subsections and branches, which are not shown to simplify the illustration of system 100B.

At 440, the system 800 creates isomorphic structure(s) corresponding to the incident type (eg, Incident Command System (ICS) structure(s)), where the isomorphic structure includes node elements. In system 100B, IWS 110 creates an isomorphic structure 160 that includes node elements that appear as rectangles. System 300 includes accident types 220 , which include different types of accidents, including mass casualty biological and chemical 320 .

In some embodiments, system 800 issues incident types 220. In system 100B (or system 300 ), IWS 180 receives published incident type 220 and may determine that hospital 1 includes isomorphic structure 160 corresponding to mass casualty biochemical 320 . In some embodiments, Hospital 2 creates isomorphic structure 186 that corresponds to Hospital 1's isomorphic structure 160 . IWS 180 may also publish hospital 2 supported incident types (not shown). Thus, Hospital 1 may be aware that Hospital 2 includes isomorphic structure 186 corresponding to isomorphic structure 160 corresponding to mass casualty biochemical 320 . Therefore, when the 10-29 Mass Casualty Biochemical Incident 330 is instantiated, the IWS 110 of Hospital 1 is aware of the isomorphic structure 186 and sends an invitation message to the IWS 180 of Hospital 2.

At 445, the system 800 receives activation of the isomorphic structure via a hypergraphic selectable item on the graphical user interface (GUI). In system 300 , IWS 110 receives activation of isomorphic structure 160 . IWS110 activates and instantiates an incident specific to the incident type, namely 10-29 Mass Casualty Biological and Chemical Incident 330.

At 450, the system 800 instantiates an interactive visual diagram (IVC) for the activated isomorphic structure, where each node element of the isomorphic structure is assigned a unique communication group identifier (ID). In system 300, IWS 110 instantiates an IVC 335 corresponding to the activated 10-29 mass casualty biochemical incident 330, which is assigned a unique communications group ID. Additionally, node elements such as 360, 370, and 380 may each be assigned a unique communication group ID that also corresponds to the activated 10-29 Mass Casualty Biochemical Incident 330 (e.g., 10-29 Mass Casualty Biochemical Incident-Incident Commander Node element 001).

At 455, the system 800 populates the IVC for the activated homogeneous structure based on the first organization subdirectory. In system 300, IWS 110 accordingly populates IVC 335 with Hospital 1 personnel. Examples are shown by dashed lines 365, 375 and 385.

At 460, the system 800 sends an invitation to a second institution (eg, a second institution of one or more member institutions) that includes an instantiated IVC for the activated homogeneous structure. In the system 300, the IWS 110 sends the 10-29 mass casualty biochemical incident invitation 340 to the IWS 180, which includes the unique uniqueness of the 10-29 mass casualty biochemical incident 330 and the node elements (eg, node elements 360, 370, and 380) therein. Communication group ID.

At 465, system 800 receives acceptance of the invitation. In system 300, IWS 110 receives an accept message from IWS 180. IWS 180 may instantiate isomorphic structure 186 of example 100B and may generate IVC 350 . The IWS 180 can also populate the IVR 350 with hospital 2 personnel based on the member directory 182 .

At 470, system 800 instantiates two or more communication groups, where each communication group includes members from a first organization subdirectory and members from a second organization subdirectory. In a first of the two or more communication groups, a first member of the first organization and a second member of the second organization are peers corresponding to node elements of the activated homogeneous structure. In system 300, IWS 110 instantiates two or more communication groups substantially in parallel. A communication group may be formed corresponding to one of the selectable items of IVC 335. For example, at least three communication groups associated with the 10-29 Mass Casualty Biochemical Incident 330 unique communication group ID are formed. Incident Commander communications group including Hospital 1 personnel assigned to node element 360 and Hospital 2 personnel assigned to node element 352; public information including Hospital 1 personnel assigned to node element 370 and Hospital 2 personnel assigned to node element 354 and a Planning Director Communications Group that includes Hospital 1 personnel assigned to node element 380 and Hospital 2 members assigned to node element 356 .

In some embodiments in which IWS 110 determines that another organization (eg, hospital 3 or a fire department in a neighboring town) does not have a pre-planned homogeneous fabric (eg, ICS) corresponding to homogeneous fabric 160 , IWS 110 may send Structural Structure 160 and/or 10-29 Mass Casualty Biological and Chemical Incident 330 Invitation. Therefore, another organization can create an equivalent isomorphic structure and instantiate a corresponding incident, where people from the other organization can then join the parallel communication groups corresponding to IVC 335 and IVC 350.

Figure 5 illustrates a method 500 for populating a hypergraph IVC of a homogeneous structure during an incident, in accordance with some embodiments of the present disclosure. For convenience and not limitation, method 500 may be described using elements of other figures in this disclosure. For example, method 500 may be performed by system 800 of FIG. 8 or example computer system 600 of FIG. 6, or IWS 110 of system 300, or a mobile IWS (not shown). In addition to allowing for the initial assignment of personnel to the various node elements of the activated instantiation of the isomorphic structure, the method 500 also allows for the adjustments and adaptations required as personnel change over time as work shifts end/begin. Assignments are swapped from retiring personnel to new personnel taking on existing functions. In some embodiments, as the incident progresses (eg, escalation-method 500 adds additional personnel, or downgrades reduces personnel, or other incident status changes as described above with respect to system 800).

At 505, system 800 receives activation of an isomorphic structure (eg, 10-29 Mass Casualty Biohazard) through selection of a hypergraphic selectable item on a graphical user interface (GUI). In system 300, IWS 110 may receive a selection of Mass Casualty Biochemical Incident 320, followed by specific details to generate a specific instance, 10-29 Mass Casualty Biochemical Incident 330. The IWS 110 may generate an IVC 335 corresponding to the instantiated 10-29 mass casualty biochemical incident 330.

At 510 , for a given node element of an activated isomorphic fabric (eg, an Incident Command System (ICS) fabric), the system 800 sends a first invitation to a first device of a first member in the first agency subdirectory to accept the corresponding The function of a given node element. In system 300 , IWS 110 may send a first invitation to a first device corresponding to one or more individuals of hospital OEM-owner 142 inviting them to accept assignment to incident commander node element 360 . In some embodiments, IWS 110 may send the first invitation to a first device corresponding to a selected one of the one or more persons corresponding to hospital OEM-lead 142 (eg, Jane Doe) to accept the Assignment of Incident Commander Node Element 360. The first invitation may include information regarding the supervision module 810 as described above and the isomorphic structure of the incident module 860 as described above regarding the isomorphic structure of the system 800 .

At 515, system 800 determines whether the invitation was accepted. In system 300, if Jane Doe accepts the invitation, method 500 proceeds to 520. Otherwise, method 500 advances to 546.

At 520, the system 800 assigns the communication group ID corresponding to the given node element to the members who accepted the invitation. In system 300, IWS 110 receives an acceptance from Jane Doe and assigns a unique communications group ID corresponding to 10-29 Mass Casualty Biochemical Incident 330 and node element 360 (eg, 10-29 Mass Casualty Biochemical Incident 330-Incident Commander Node element 001).

At 525, system 800 determines whether the timer or counter has expired. For example, a shift change may occur. In some embodiments, an incident may change status (eg, upgraded, degraded, inactive). If the timer or counter has expired, system 800 proceeds to 530. Otherwise, system 800 remains at 525.

At 530, the system 800 sends another invitation to the person to continue performing the function corresponding to the given node element. In system 300, IWS110 sends another invitation to Jane Doe asking if she will stay on the next shift as the incident commander.

At 535, system 800 determines whether another invitation was accepted. If another invitation is accepted, method 500 returns to 525. Otherwise, method 500 advances to 540.

At 540, when another invitation is not accepted (e.g., Jane Doe will not remain on the next shift as the incident commander), the system 800 sends another invitation to another device of another member in the first agency subdirectory. An invitation to accept the functionality corresponding to a given node element. In system 300 , assuming the incident has not become inactive, IWS 110 sends another invitation to a different person associated with hospital OEM-owner 142 to accept assignment to incident commander node element 360 . Method 500 returns to 515 to determine whether the invitation was accepted.

Various embodiments may be implemented in software, firmware, hardware, or combinations thereof. FIG. 6 illustrates an example computer system 600 in which the systems and devices described in various embodiments may be implemented as computer-readable code and/or text-readable code. After reading this specification, it will become apparent to those skilled in the relevant art how to implement embodiments using other systems and/or processing architectures. For example, IWS 110 or IWS 180 of systems 100B, 200, and 300 and system 800 of FIG. 8 may be implemented by computer system 600.

Computer system 600 includes one or more processors (also referred to as central processing units or CPUs), such as processor 604. The processor 604 is connected to a communications infrastructure 606, which may be a bus. One or more processors 604 may each be a graphics processing unit (GPU). In an embodiment, a GPU is a processor that is a specialized electronic circuit designed to handle math-intensive applications. GPUs can have parallel structures that are efficient for parallel processing of large blocks of data such as common math-intensive data in computer graphics applications, images, videos, etc.

Computer system 600 also includes user input/output device(s) 603 , such as a monitor, keyboard, pointing device, etc., which communicate with communications infrastructure 606 through user input/output interface(s) 602 . Computer system 600 also includes main or main memory 608, such as random access memory (RAM). Main memory 608 may include one or more levels of cache. Main memory 608 has control logic (ie, computer software) and/or data stored therein.

Computer system 600 may also include one or more secondary storage devices or memory 610. Secondary storage 610 may include, for example, a hard drive 612 and/or a removable storage device or drive 614. Removable storage drive 614 may be a floppy disk drive, tape drive, optical disk drive, optical storage device, tape backup device, and/or any other storage device/drive.

Removable storage drive 614 may interact with removable storage unit 618. Removable storage unit 618 includes a computer usable or readable storage device having computer software (control logic) and/or data stored thereon. Removable storage unit 618 may be a floppy disk, magnetic tape, optical disk, DVD, optical storage disk, and/or any other computer data storage device. Removable storage drive 614 reads from and/or writes to removable storage unit 618 in a well-known manner.

According to exemplary embodiments, secondary storage 610 may include other devices, instruments, or other methods for allowing computer programs and/or other instructions and/or data to be accessed by computer system 600 . Such a device, instrument, or other method may include, for example, removable storage unit 622 and interface 620. Examples of removable storage unit 622 and interface 620 may include program cartridges and cartridge interfaces (such as those found in video game devices), removable storage chips (such as EPROM or PROM) and associated sockets, memory sticks, and USB port, memory card and associated memory card slot, and/or any other removable storage unit and associated interface.

Computer system 600 may also include a communications or network interface 624. Communication interface 624 enables computer system 600 to communicate and interact with any combination of remote devices, remote networks, remote entities, etc. (individually and collectively referenced by reference numeral 628). For example, communication interface 624 may allow computer system 600 to communicate with remote device 628 via communication path 626, which may be wired and/or wireless, and may include any combination of LAN, WAN, Internet, etc. Control logic and/or data may be transmitted to and from computer system 600 via communication path 626 .

In embodiments, a tangible, non-transitory device or article of manufacture including a tangible, non-transitory computer usable or readable medium with control logic (software) stored thereon is also referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system 600, primary memory 608, secondary memory 610, and removable storage units 618 and 622, as well as tangible articles embodying any combination of the foregoing. When executed by one or more data processing devices (eg, computer system 600), such control logic causes such data processing devices to operate as described herein.

Based on the teachings contained in this disclosure, it will be apparent to those skilled in the relevant art(s) how to make and use embodiments of the invention using data processing devices, computer systems, and/or computer architectures. In particular, embodiments may operate with software, hardware, and/or operating system implementations other than those described herein.

in conclusion

It should be understood that the Detailed Description section, rather than the Summary and Abstract sections (if any), are intended for interpreting the claims. The Summary and Abstract sections, if any, may set forth one or more, but not all, example embodiments of the invention contemplated by the inventor(s) and, therefore, are not intended to limit the invention or the appended rights in any way Require.

While the invention is described herein with reference to example embodiments of example fields and applications, it is to be understood that the invention is not limited thereto. Other embodiments and modifications are possible and are within the scope and spirit of the invention. For example, without limiting the generality of this paragraph, embodiments are not limited to the software, hardware, firmware and/or entities shown in the figures and/or described herein. Furthermore, in addition to the examples described herein, embodiments (whether or not explicitly described herein) may have significant utility in fields and applications.

Embodiments are described herein with the aid of functional building blocks, which illustrate the implementation of specified functions and their relationships. For ease of description, the boundaries of these functional building blocks are arbitrarily defined here. Alternative boundaries can be defined as long as the specified functions and relationships (or their equivalents) are appropriately implemented. Furthermore, alternative embodiments may perform functional blocks, steps, operations, methods, etc., in an order different than that described herein.

The breadth and scope of the present invention should not be limited by any of the above-described example embodiments, but should be defined solely in accordance with the appended claims and their equivalents.

Claims (20)

1. A system for a first institution, comprising: transceiver; and One or more processors coupled to the transceiver, configured to: establishing communications with the second agency via the interoperable communications network via the transceiver; Create an isomorphic structure including the first node element and the second node element in the hierarchical structure; instantiate an interactive visual diagram (IVC) for an activated isomorphic structure, wherein a first node element corresponds to a first communication group identifier (ID) and a second node element corresponds to a second communication group ID; sending, via the transceiver, a first invitation including an instantiated IVC for the activated homogeneous structure; and In response to the first invitation being accepted, a first communication group corresponding to the first communication group ID and a second communication group corresponding to the second communication group ID are instantiated, wherein the first communication group includes a first member of the first organization and A second member of the second mechanism, wherein the first member and the second member are peers corresponding to the first node element of the activated isomorphic structure. 2. The system of claim 1, wherein the activated isomorphic structure includes an Incident Command System (ICS) structure. 3. The system of claim 1, wherein the one or more processors are further configured to: Populate the IVC of the isomorphic structure used for activation with members of the first institution. 4. The system of claim 3, wherein to populate an IVC for an activated homogeneous structure, the one or more processors are configured to: sending a second invitation via the transceiver to the first device of the first member of the first organization to accept functionality corresponding to the first node element; and In response to the second invitation being accepted, a first communications group ID is assigned to the first device or first member. 5. The system of claim 4, wherein the one or more processors are further configured to: sending a third invitation to the first device of the first member via the transceiver to continue accepting functionality corresponding to the first node element; in response to the rejection of the third invitation, sending a fourth invitation to another device of another member of the first organization to accept functionality corresponding to the first node element; and In response to the fourth invitation being accepted, the first communication group ID is reassigned to the other device or the other member. 6. The system of claim 1, further comprising: A graphical user interface (GUI) coupled to the one or more processors, wherein the GUI includes hypergraphical selectable items corresponding to one or more created isomorphic structures including isomorphic structures, wherein the one or The plurality of processors are configured to: receive, via the GUI, a first selection of a first hypergraphic selectable item of the hypergraphic selectable items corresponding to the isomorphic structure; and Activate isomorphic structures. 7. The system of claim 6, wherein the one or more processors are further configured to: receiving, via the GUI, a second selection of a second hypergraph selectable item corresponding to the first node element of the instantiated IVC for the activated isomorphic structure; responsive to receiving a second selection of the second hypergraphic selectable item, sending a second invitation via the transceiver to the first device of the first member of the first organization to accept functionality corresponding to the first node element; and In response to the second invitation being accepted, a first communications group ID is assigned to the first device or first member. 8. The system of claim 1, wherein the first communication group ID corresponds to: a push-to-talk radio network, a mobile push-to-talk network, a voice or video conferencing call network. 9. The system of claim 1, wherein the one or more processors are further configured to: A parallel session is instantiated, the parallel session including peer members from a first organization and a third organization coupled to the interoperability communications network, wherein the peer members correspond to respective node elements in a hierarchy of the activated homogeneous structure. 10. The system of claim 1, wherein the one or more processors are further configured to: Create a members directory that includes the first organization subdirectory; Publish the first institution subdirectory; receive a second institutional subdirectory; and Update the members directory to include the second institution subdirectory. 11. A method for a system of a first institution, comprising: establishing communications with the second organization via an interoperable communications network; Create an isomorphic structure including the first node element and the second node element in the hierarchical structure; instantiate an interactive visual diagram (IVC) for an activated isomorphic structure, wherein a first node element corresponds to a first communication group identifier (ID) and a second node element corresponds to a second communication group ID; sending a first invitation that includes an instantiated IVC for the activated isomorphic structure; and In response to the first invitation being accepted, a first communication group corresponding to the first communication group ID and a second communication group corresponding to the second communication group ID are instantiated, wherein the first communication group includes a first member of the first organization and A second member of the second mechanism, wherein the first member and the second member are peers corresponding to the first node element of the activated isomorphic structure. 12. The method of claim 11, wherein the activated isomorphic structure includes an Incident Command System (ICS) structure. 13. The method of claim 11, further comprising: Populate the IVC of the isomorphic structure used for activation with members of the first institution. 14. The method of claim 13, wherein populating the IVC of the homogeneous structure for activation includes: sending a second invitation to the first device of the first member of the first organization to accept functionality corresponding to the first node element; and In response to the second invitation being accepted, a first communications group ID is assigned to the first device or first member. 15. The method of claim 14, further comprising: sending a third invitation to the first device of the first member to continue accepting functionality corresponding to the first node element; in response to the rejection of the third invitation, sending a fourth invitation to another device of another member of the first organization to accept functionality corresponding to the first node element; and In response to the fourth invitation being accepted, the first communication group ID is reassigned to the other device or the other member. 16. The method of claim 11, further comprising: displaying an IVC for an instantiation of the activated isomorphic structure via a graphical user interface (GUI), the GUI including a hypergraphical selectable item corresponding to one or more isomorphic structures including the isomorphic structure; receiving, via the GUI, a first selection of a first of the hypergraphic selectable items corresponding to the isomorphic structure; and Activate isomorphic structures. 17. The method of claim 16, further comprising: receiving, via the GUI, a second selection of a second hypergraph selectable item corresponding to the first node element of the instantiated IVC for the activated isomorphic structure; in response to receiving a second selection of the hypergraphic selectable item, sending a second invitation to the first device of the first member of the first organization to accept functionality corresponding to the first node element; and In response to the second invitation being accepted, a first communications group ID is assigned to the first device or first member. 18. The method of claim 11, wherein the first communication group ID corresponds to: a push-to-talk radio network, a mobile push-to-talk network, a voice or video conferencing call network. 19. The method of claim 11, further comprising: A parallel session is instantiated, the parallel session including peer members from a first organization and a third organization coupled to the interoperability communications network, wherein the peer members correspond to respective node elements in a hierarchy of the activated homogeneous structure. 20. A non-transitory computer-readable medium storing instructions that, when executed by a processor of a first electronic device of a first mechanism, cause the processor to perform operations, the operations comprising: establishing communications with the second organization via an interoperable communications network; Create an isomorphic structure including the first node element and the second node element in the hierarchical structure; instantiate an interactive visual diagram (IVC) for an activated isomorphic structure, wherein a first node element corresponds to a first communication group identifier (ID) and a second node element corresponds to a second communication group ID; sending a first invitation that includes an instantiated IVC for the activated isomorphic structure; and In response to the first invitation being accepted, a first communication group corresponding to the first communication group ID and a second communication group corresponding to the second communication group ID are instantiated, wherein the first communication group includes a first member of the first organization and A second member of the second mechanism, wherein the first member and the second member are peers corresponding to the first node element of the activated isomorphic structure.