No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
[[File:BlueNet-Logo.png|thumb|BlueNet Logo]] | |||
BlueNet is a specific name given to the interactive network of [[HAL Computer System]] hubs operated by [[Solas Tempus]] located throughout the known galaxy. This network operates in multiple layers. Any given hub can act as a [[HAL 9000]] mainframe without the use of other nodes, though processes and information access may be limited. The use of the network as way to transmit and receive both information and task data allows any individual node with communications access to expand its capabilities. | BlueNet is a specific name given to the interactive network of [[HAL Computer System]] hubs operated by [[Solas Tempus]] located throughout the known galaxy. This network operates in multiple layers. Any given hub can act as a [[HAL 9000]] mainframe without the use of other nodes, though processes and information access may be limited. The use of the network as way to transmit and receive both information and task data allows any individual node with communications access to expand its capabilities. | ||
The key to the network is that while it operates largely over its own physical network of subspace relays and stations the layers can be established along any communication pathway and the BlueNet protocol allows the layers to be set up dynamically depending on network conditions. As a result the network can make use of encrypted links over standard subspace lines or even terrestrial radio transmission channels. [[:Category:Starfleet|Starfleet]] Command also has configured a dedicated subspace band to BlueNet so that it can operate within [[:Category:Starfleet|Federation]] space along side the normal subspace network. This is not the preferred mode of operation but can be required in some areas where BlueNet relay stations may be out of range or otherwise unreachable. | The key to the network is that while it operates largely over its own physical network of subspace relays and stations the layers can be established along any communication pathway and the BlueNet protocol allows the layers to be set up dynamically depending on network conditions. As a result the network can make use of encrypted links over standard subspace lines or even terrestrial radio transmission channels. [[:Category:Starfleet|Starfleet]] Command also has configured a dedicated subspace band to BlueNet so that it can operate within [[:Category:Starfleet|Federation]] space along side the normal subspace network. This is not the preferred mode of operation but can be required in some areas where BlueNet relay stations may be out of range or otherwise unreachable. | ||
In return for this access to the Federation subspace communications network Starfleet can access and use BlueNet in situations where they cannot access their own network, in these cases they operate entirely within the Communication Layer. | In return for this access to the Federation subspace communications network [[Starfleet]] can access and use BlueNet in situations where they cannot access their own network, in these cases they operate entirely within the Communication Layer. | ||
== Network Layers of Operation == | == Network Layers of Operation == | ||
Line 26: | Line 27: | ||
=== Autonomous Layer === | === Autonomous Layer === | ||
Within the other layers interactive and automated processes communicate managing data transfers between the layers. Prior to October of 2368 this was a largely predicable process. When the HAL 9000 AI attained self awareness and the shared-consciousness operates using a dynamic and ever-changing protocol along this layer. The layer cannot be accessed directly by the other three layers but requests from within this layer pull and push data with the other layers. This layer also cannot be accessed by command or console, rather the Communication Layer is monitored for where the AI needs to point its attention. | Within the other layers interactive and automated processes communicate managing data transfers between the layers. Prior to October of 2368 this was a largely predicable process. When the [[HAL 9000]] AI attained self awareness and the shared-consciousness operates using a dynamic and ever-changing protocol along this layer. The layer cannot be accessed directly by the other three layers but requests from within this layer pull and push data with the other layers. This layer also cannot be accessed by command or console, rather the Communication Layer is monitored for where the AI needs to point its attention. | ||
=== Temporal Awareness Layer === | === Temporal Awareness Layer === | ||
An important distinction between BlueNet and other communication networks is the awareness of the networking structure to temporal issues. The Temporal Awareness Layer of the network handles this. Solas Tempus operates in a variety of different time periods as required by active missions. Having a communication network capable of sending and receiving signals in a variety of time periods could give rise to serious problems of paradoxes where a network node in the future could contact a network node in the past and then make the past aware of a situation and thus change the outcome. This layer handles communications between time periods and processes signals ensuring that they will not cause a paradox, access to information in this layer is restricted to Temporal Operatives only. | An important distinction between BlueNet and other communication networks is the awareness of the networking structure to temporal issues. The Temporal Awareness Layer of the network handles this. [[Solas Tempus]] operates in a variety of different time periods as required by active missions. Having a communication network capable of sending and receiving signals in a variety of time periods could give rise to serious problems of paradoxes where a network node in the future could contact a network node in the past and then make the past aware of a situation and thus change the outcome. This layer handles communications between time periods and processes signals ensuring that they will not cause a paradox, access to information in this layer is restricted to [[Temporal Operatives]] only. | ||
[[Category:Solas Tempus]] | [[Category:Solas Tempus]] |
Latest revision as of 22:28, 8 January 2017
BlueNet is a specific name given to the interactive network of HAL Computer System hubs operated by Solas Tempus located throughout the known galaxy. This network operates in multiple layers. Any given hub can act as a HAL 9000 mainframe without the use of other nodes, though processes and information access may be limited. The use of the network as way to transmit and receive both information and task data allows any individual node with communications access to expand its capabilities.
The key to the network is that while it operates largely over its own physical network of subspace relays and stations the layers can be established along any communication pathway and the BlueNet protocol allows the layers to be set up dynamically depending on network conditions. As a result the network can make use of encrypted links over standard subspace lines or even terrestrial radio transmission channels. Starfleet Command also has configured a dedicated subspace band to BlueNet so that it can operate within Federation space along side the normal subspace network. This is not the preferred mode of operation but can be required in some areas where BlueNet relay stations may be out of range or otherwise unreachable.
In return for this access to the Federation subspace communications network Starfleet can access and use BlueNet in situations where they cannot access their own network, in these cases they operate entirely within the Communication Layer.
Network Layers of Operation
- Shared Data Layer
- Shared Computational Layer
- Node Update Layer
- Communication Layer
- Autonomous Layer
- Temporal Awareness Layer
At the first layer is the Shared Data Layer which is responsible for sharing information between all network nodes, regardless of hub and is primarily a transport layer sending data back and forth over the network as needed. Data updates for specific nodes to download are passed along to the Node Update Layer.
The second layer is the Shared Computational Layer which manages shared resources between the hubs and their nodes. In this layer a global process request queue is prioritized allowing computational resources to be shared over the entire network, should a node or hub become overloaded or require more processing power computational information can then be offloaded in part or as a whole to nodes who have processing power to spare. This is an autonomous action but can be accessed via voice commands for operations that need to specifically be offloaded remotely or remain as local processes.
Node Update Layer
Information is updated through another transport layer called the Node Update Layer which handles large bulk information transfers. Normally a request for information by a node is dynamically streamed to whatever node needs it and that node need only cache relevant information. Should a node need to actually store bulk data locally this transport layer is used as a dedicated channel to transmit and receive information on.
Communication Layer
While the Computational, Update, and Data layers are completely automated the Communication Layer is not and is used as a high bandwidth voice, video, and data communications band. This is primarily devoted to interpersonal communications between people at nodes - in contrast to other layers which are devoted to computers communicating over the network. There is linkage between the layers where a message on this layer can point to data which then needs to trigger a data-transfer along one of the other layers so that data is on-hand when the message is read.
Autonomous Layer
Within the other layers interactive and automated processes communicate managing data transfers between the layers. Prior to October of 2368 this was a largely predicable process. When the HAL 9000 AI attained self awareness and the shared-consciousness operates using a dynamic and ever-changing protocol along this layer. The layer cannot be accessed directly by the other three layers but requests from within this layer pull and push data with the other layers. This layer also cannot be accessed by command or console, rather the Communication Layer is monitored for where the AI needs to point its attention.
Temporal Awareness Layer
An important distinction between BlueNet and other communication networks is the awareness of the networking structure to temporal issues. The Temporal Awareness Layer of the network handles this. Solas Tempus operates in a variety of different time periods as required by active missions. Having a communication network capable of sending and receiving signals in a variety of time periods could give rise to serious problems of paradoxes where a network node in the future could contact a network node in the past and then make the past aware of a situation and thus change the outcome. This layer handles communications between time periods and processes signals ensuring that they will not cause a paradox, access to information in this layer is restricted to Temporal Operatives only.