Evolving the Tactical Edge: Delivering Unified Capabilities (UC) and Mobile Enterprise Connectivity to the Deployed User

Networking of multi‐domain unified communications systems: Structure design and performance evaluation

“…The UC services of US military will be transformed from legacy technologies to a converged cloud‐based solution. Witherspoon et al pointed out that tactical gateway access nodes needed enhancements to allow tactical users to leverage central UC services when there is stable connectivity back to the core network but also continue to provide the UC services to tactical users when connectivity is unavailable . Eg, to guarantee local IM/Chat service continuity in the tactical environment, a local instance of the core IM/Chat server should be installed on the local branch.…”

“…Interworking between service nodes in central and branch domains is performed according to their service types. Eg, the IM servers in central and branch domains can be federated to provide IM communication between users in all domains of the system . In each domain, the service node can be hosted in a legacy server, or a cloud server running in an edge or core data center, and can be accessed by users via high speed network.…”

“…Witherspoon et al pointed out that tactical gateway access nodes needed enhancements to allow tactical users to leverage central UC services when there is stable connectivity back to the core network but also continue to provide the UC services to tactical users when connectivity is unavailable. 9 Eg, to guarantee local IM/Chat service continuity in the tactical environment, a local instance of the core IM/Chat server should be installed on the local branch. Federation could be established between the local instance and the core server in order to allow communications between their users.…”

“…The single domain SIP system is usually with centralized architecture and is not suitable for nation‐wide large UC system with many branches requiring high communications reliability . This is because, when the number of UC users is large, bottlenecks are likely to occur in the costly WAN links connecting center and branches, resulting in high transmission delay between remote branches and center.…”

“…The single domain SIP system is usually with centralized architecture and is not suitable for nation-wide large UC system with many branches requiring high communications reliability. 8,9 This is because, when the number of UC users is large, bottlenecks are likely to occur in the costly WAN links connecting center and branches, resulting in high transmission delay between remote branches and center. Hence, the multi-domain SIP system with distributed architecture is a better choice for the UC system of large enterprises, where the service continuity in branches in case of central system failure is important.…”