Proselytization network: Difference between revisions
From Halopedia, the Halo wiki
BaconShelf (talk | contribs) m (→Sources) |
BaconShelf (talk | contribs) mNo edit summary |
||
Line 7: | Line 7: | ||
==Overview== | ==Overview== | ||
[[File:H2_Communications_Module.png|150px|thumb|Covenant communications nodes were used to receive information from the proselytization network.]] | [[File:H2_Communications_Module.png|150px|thumb|Covenant communications nodes were used to receive information from the proselytization network.]] | ||
In contrast to its [[UNSC]] [[UNSC battle network|counterpart]], proselytization network was used by the Covenant for domestic, religious and military functions - as opposed to the humans' purely military use cases. The system was designed as a top-down tool for use by the [[San'Shyuum]] and [[Sangheili]] leadership on [[High Charity]] to transmit orders down the chain, but not to receive updates from subordinate nodes. Various methods were used across the network to spread its messages, depending on the importance of the message in question. Central leadership on High Charity could use [[superluminal communications]] links to broadcast orders via [[FLEETCOM (Covenant)|FLEETCOM]] to tithe-worlds and [[Covenant fleet|fleets]] directly, with these imperatives modified by local satraps and commanders spread via the use of less sophisticated [[Covenant comm node|comm nodes]].{{Ref/Book|Id=Enc22|Enc22|Page=217}} All star systems inhabited by the Covenant are fitted with regional [[coordination platform]]s - space stations managed by the [[Ministry of Concert]] to serve a variety of functions involved with the managing of the Covenant's day-to-day affairs with their ancillary functions including serving as nodes in the proselytization network.{{Ref/Book|Enc22|Page=224}} The battlenet is standard equipment aboard all Covenant vessels, which have both intra- and inter-ship battlenets.{{Ref/Novel|FS|Page=63}} | In contrast to its [[UNSC]] [[UNSC battle network|counterpart]], proselytization network was used by the Covenant for domestic, religious and military functions - as opposed to the humans' purely military use cases. The system was designed as a top-down tool for use by the [[San'Shyuum]] and [[Sangheili]] leadership on [[High Charity]] to transmit orders down the chain, but not to receive updates from subordinate nodes. Various methods were used across the network to spread its messages, depending on the importance of the message in question. Central leadership on High Charity could use [[superluminal communications]] links to broadcast orders via [[FLEETCOM (Covenant)|FLEETCOM]] to tithe-worlds and [[Covenant fleet|fleets]] directly, with these imperatives modified by local satraps and commanders spread via the use of less sophisticated [[Covenant comm node|comm nodes]].{{Ref/Book|Id=Enc22|Enc22|Page=217}}{{Ref/Book|HWF|Page=69}} All star systems inhabited by the Covenant are fitted with regional [[coordination platform]]s - space stations managed by the [[Ministry of Concert]] to serve a variety of functions involved with the managing of the Covenant's day-to-day affairs with their ancillary functions including serving as nodes in the proselytization network.{{Ref/Book|Enc22|Page=224}} The battlenet is standard equipment aboard all Covenant vessels, which have both intra- and inter-ship battlenets.{{Ref/Novel|FS|Page=63}} | ||
As a consequence of their generally lax computer security and its use in civil and military affairs, the proselytization network was often broadcast entirely on unencrypted channels - something able to be employed against the Covenant via the use of human [[artificial intelligence]] systems. These networks could be accessed by even the communications equipment inside a suit of [[MJOLNIR Powered Assault Armor/Mark V|Mark V MJOLNIR]] armor, with the AI [[Cortana]] able to access and gain information on Covenant force deployments several times throughout the [[Battle of Installation 04|campaign]] on [[installation 04]].{{Ref/Reuse|halo}}{{Ref/Level|CE|The Truth and Reconciliation}} The chaos introduced into the ranks of the [[Fleet of Particular Justice]] by the [[Flood]] outbreak was sufficient to overload the fleet's network, making it near-impossible to access information through it.{{Ref/Level|CE|Two Betrayals}} | As a consequence of their generally lax computer security and its use in civil and military affairs, the proselytization network was often broadcast entirely on unencrypted channels - something able to be employed against the Covenant via the use of human [[artificial intelligence]] systems. These networks could be accessed by even the communications equipment inside a suit of [[MJOLNIR Powered Assault Armor/Mark V|Mark V MJOLNIR]] armor, with the AI [[Cortana]] able to access and gain information on Covenant force deployments several times throughout the [[Battle of Installation 04|campaign]] on [[installation 04]].{{Ref/Reuse|halo}}{{Ref/Level|CE|The Truth and Reconciliation}} The chaos introduced into the ranks of the [[Fleet of Particular Justice]] by the [[Flood]] outbreak was sufficient to overload the fleet's network, making it near-impossible to access information through it.{{Ref/Level|CE|Two Betrayals}} |
Revision as of 07:33, July 24, 2022
- "I've hacked into the Covenant battlenet. They're actually broadcasting tactical data on unencrypted channels. We should show them who they're dealing with."
- — Cortana to John-117 on Installation 04.
The proselytization network[2], informally termed the Covenant battle network,[3] or Covenant battle net,[4] or simply the battlenet,[5] is the term for Covenant communication systems maintained to allow instantaneous contact between units, vessels and planets. It is the equivalent to the human COM systems. Following the defeat of the Covenant, various Covenant remnants have been shown to use the battle net or modifications of it for their own purposes.
Overview
In contrast to its UNSC counterpart, proselytization network was used by the Covenant for domestic, religious and military functions - as opposed to the humans' purely military use cases. The system was designed as a top-down tool for use by the San'Shyuum and Sangheili leadership on High Charity to transmit orders down the chain, but not to receive updates from subordinate nodes. Various methods were used across the network to spread its messages, depending on the importance of the message in question. Central leadership on High Charity could use superluminal communications links to broadcast orders via FLEETCOM to tithe-worlds and fleets directly, with these imperatives modified by local satraps and commanders spread via the use of less sophisticated comm nodes.[2][6] All star systems inhabited by the Covenant are fitted with regional coordination platforms - space stations managed by the Ministry of Concert to serve a variety of functions involved with the managing of the Covenant's day-to-day affairs with their ancillary functions including serving as nodes in the proselytization network.[7] The battlenet is standard equipment aboard all Covenant vessels, which have both intra- and inter-ship battlenets.[8]
As a consequence of their generally lax computer security and its use in civil and military affairs, the proselytization network was often broadcast entirely on unencrypted channels - something able to be employed against the Covenant via the use of human artificial intelligence systems. These networks could be accessed by even the communications equipment inside a suit of Mark V MJOLNIR armor, with the AI Cortana able to access and gain information on Covenant force deployments several times throughout the campaign on installation 04.[4][9] The chaos introduced into the ranks of the Fleet of Particular Justice by the Flood outbreak was sufficient to overload the fleet's network, making it near-impossible to access information through it.[10]
Near the end of the Human-Covenant War, during the Battle for Earth, a defected Huragok was captured by a squad of ODSTs, and the Huragok agreed to share information in the Covenant battlenet after interrogated by Sergeant Major Avery Junior Johnson.[11] Two days later, the battlenet fell into disarray again, this time following the Prophet of Truth's departure through the Portal at Voi at the close of the Battle of Voi.[12]
Sesa 'Refumee's heretic faction
Sesa 'Refumee heretic faction had its own battlenet, but the storm approaching the Threshold gas mine masked the arrival of the Arbiter's team and put the Heretics' battlenet into disarray.[13]
Jul 'Mdama's Covenant
During the Battle of Requiem in July 2557, Cortana monitored a new battlenet used by Jul 'Mdama's Covenant to learn more about the situation.[14] During the early stages of the battle, Cortana detected reports of Promethean resistance on the battlenet while John-117 fought through Requiem's core.[15]
During the Requiem Campaign in 2558, Jul 'Mdama's Covenant mainly used one of the shield world's Forerunner subnets to communicate rather than their battlenet.[16] Later, Dr. Catherine Halsey's comm signal was discovered to have bounced off into 'Mdama's battlenet after being traced to "Lockup."[17]
In October 2558, while Blue Team was on Argent Moon, Jul 'Mdama's battlenet suddenly lit up as a Covenant remnant fleet arrived at the station, causing the team to change their plan to scuttling Argent Moon. As the team made their way through the station, they picked up chatter on the battlenet about Jul 'Mdama's death in the Battle of Kamchatka.[18]
Banished
The Banished use a modified version of the Covenant battlenet to connect to different FOBs and important Banished facilities such as Outpost Tremonius. After the Master Chief took control of Outpost Tremonius, he inserted the Weapon into a terminal where she easily removed the location from the Banished system, securing it.[19] After the Master Chief secured each of the UNSC FOBs in the area, the Weapon removed them from the system as well, securing them. Each time an FOB was secured, the Weapon was able to secure data on Banished operations from the battlenet, including major bases and high-value Banished targets.[20]
Covenant battle network frequencies
These frequencies are most commonly used by the Covenant, but it seems that they occasionally utilize the UNSC D- and E- Bands.
- Covenant F-Band[21]
- Covenant G-Band[21]
- Covenant H-Band[21]
- Covenant I-Band[21]
- Covenant J-Band[21]
- Covenant K-Band[21]
List of appearances
- Halo: Combat Evolved (First mentioned)
- Halo: The Flood (Mentioned only)
- Halo: First Strike
- Halo 2 (Mentioned only)
- Halo: The Cole Protocol
- Halo 3: ODST (Mentioned only)
- Halo: Combat Evolved Anniversary (Mentioned only)
- Halo 4 (Mentioned only)
- Spartan Ops (Mentioned only)
- Halo 2: Anniversary
- Halo: New Blood (Mentioned only)
- Halo Infinite (Mentioned only)
Sources
- ^ Halo: Warfleet, page 77
- ^ a b Halo Encyclopedia (2022 edition), page 217
- ^ Halo: The Flood, page 38
- ^ a b Halo: Combat Evolved, campaign level Halo
- ^ Halo: First Strike, page 55
- ^ Halo: Warfleet, page 69
- ^ Halo Encyclopedia (2022 edition), page 224
- ^ Halo: First Strike, page 63
- ^ Halo: Combat Evolved, campaign level The Truth and Reconciliation
- ^ Halo: Combat Evolved, campaign level Two Betrayals
- ^ Halo 3: ODST, campaign level Coastal Highway
- ^ Halo Legendary Crate, Data Drop #2
- ^ Halo 2, campaign level The Arbiter
- ^ Halo 4
- ^ Halo 4, campaign level Forerunner
- ^ Spartan Ops, S104 Hairy Call
- ^ Spartan Ops, S109 The Hammer
- ^ Halo 5: Guardians, campaign level Blue Team
- ^ Halo Infinite, campaign level Outpost Tremonius
- ^ Halo Infinite
- ^ a b c d e f Halo: First Strike, page 297