Superstar Architecture

Tag : TCP/IP

Jul, 2022

Superstar Architecture

Compositor generates a link layer frame of the OSI model and TCP/IP (Modernized version). It encapsulates information into the frame of the Ethernet from the network, transport and application layers. It forms a Z-frame similar to the PDH T-carrier used in North America and Japan. This frame is needed to encapsulate TCP/IP levels into the system of the ISS Zvezda module. Compositor replaces the OUI fields of the sender’s MAC address to work on its network. It automatically selects OUI, according to the NIC in the MIB database, to forward Ethernet frames in its network. It solves the duplex problem by increasing the frame. There are many Z-frame hierarchies used in private and public networks, as well as defense networks. All of them depend on the frame size. Two multiplexing methods are used at the same time: FDM and TDM. Compositor sees the WAN as Local Network. This is done through a large database of NIC devices.

Compositor Software was the first company in the world to achieve the Super-Zvezda architecture. In addition to Z = 4, 8 … 128, top-level architectures Z = 256, 512 … 16384 have become available. The frame value in model Z = 16384 is 2 Gbit. This allows you to transmit at a speed of 10.9 Tbit/s when the modem speed of 32000 omega is reached. Charters of top-level Z models are used for communication in networks (in descending order): Black Box, PRO, NASA-Roscosmos, CERN, Quantum Physicists, Electronic Engineers, Architects. These architectures are implemented as applications for macOS and Android. The 64-bit native ARMv8 architecture is used. Accordingly, the NIM (Nuclear Instrumentation Module) charter gives a presence in virtual reality not only at the geographical location level, but also allows you to transfer to remote points visual environmental information collected as 3D models of objects, textures and their animation in real time directly on the client machine. This allows you to collect information about the remote location without significant resources other than a smartphone. Compositor charter carries out a pair set, similar to the domino principle. This is how a Multiple Spanning-Tree network is formed from remote objects combined into a Compositor VLAN VR network. Dialing in the network is carried out by metrics and solves the problem of building a network topology from the root device to the final devices in the circuit. Division into branches of the tree goes according to classes that depend on the autonomy time of the speaker of the autonomous system. By increasing the flow rate of the Z-frame to 10.9 Tbit/s, it is possible to solve the duplex problem, which allows you to form upstream streams much faster than with low-level frames. Each neighboring device in the Compositor VLAN device tree forms a point-to-point pair that uses a closed trunk tunnel over the IP protocol using TDMoIP technology. This is a generic tunnel that allows you to transfer all important information about human activity to a neighboring device on the network, over an upstream to the root server to which the alert interface is connected.

Architects, Black Box, CERN, Electronic Engineers, FDM, ISS, NASA-Roscosmos, OSI, PDH, PRO, Quantum Physicists, T-carrier, TCP/IP, TDM, Zvezda

Feb, 2020

By ruslany

Compositor v3 RTOS – analog radio interface for IPv6 Protocol

Compositor v3 Hypervisor Radio Shack software updated to RTOS. Now, Compositor RTOS v3.0.3 supports numerous new features, such as:

Protocols implemented:
- RTC8k = IS-IS Level-2
- FF8 = ARP (Address Resolution Protocol)
- TC25 = VLAN (IEEE 802.1aq)
Hierarchies added:
- AI-RT1024 = SDH STM-x
- N9000 = PDH E1
Other features:
- TCP/IP protocols stack implemented
- TCP/IP window added
- EUI48 table added
- BPM now is the network field parameter of IP-address
- Network field includes 2^13 to define as IPv6-address
- All modules renamed to reflect new functionality

Compositor v3.0.3 RTOS

The main reason I made the update is to reveal the FF8 (ARP) and TC25 (VLAN) protocols work. That is why the working routine in Compositor RTOS v3.0.3 looks as following:

At the beginning, I set the time to reach the destination point, where the network deployed. I make this by setting deployment time in degrees from -180 to 180, which is the range from 0 to 60 minutes. Then I set the IP-address of destination interface the following way: the part of IP-address, pointing on the interface ID is set stochastically or manually. Multiplier in IPv4 sets the second field, which is the part of network and host. That is why the highest network for Compositor RTOS in IPv4 is 255.4.0.0. When I’ve reached the destination network and I’ve got the closed feedback loop on the loop-back interface output, I define the autonomous system type, which it belongs. I do this by enabling VLAN and ARP protocols and resolving the assignment of IPv4-addresses to the network devices of this autonomous system. I look into the IPv4-addresses of next-hops and reveal the number of such next-hops before returning to the first hop. The more hops IS-IS Level-2 protocol makes, the larger a metric of the destination network (autonomous system). This way I reveal all peers of the destination network.

When I define ABR (area border router) of that network using IS-IS Level-2 protocol, I turn the VLAN and ARP protocols off and start to translate this device information into IPv6 network, by enabling TCP/IP protocols stack. This process allows merging IPv4 networks with IPv6 networks and to expand the influence of my database into IPv6 protocol.

802.1aq, Address Resolution Protocol, ARP, Compositor v3, EUI48, IPv4, IPv6, IS-IS Level-2, PDH, RTOS, SDH, TCP/IP, VLAN

Oct, 2019

By ruslany

Niagara project

This autumn has started from a very interesting project. While I continued working on Compositor v9.0.1 (current build a14), I felt a need to have such system as mobile real-time operation system (RTOS). Compositor v9.0.1 a14 consumes many resources at 192 kHz and I decided to sample it using Compositor v9.0.1 itself. At this time, the approach of middleware and dump was matured and I decided to make separate product for Compositor documentation development. Such manual will consist of all commands needed to operate the Niagara RTOS client. As the UNIX-like operating system, it will support most of the commands for routing protocols configuration, such as TCP/IP and VLAN. The prominent feature of this RTOS is that it is a software router, which runs on middleware, recorded with Compositor RTOS v9.0.1. If the middleware recorded on a feedback with z16 and z32 generics connected and they are in reverse, the system will give a resistance of 16 + 32 Ohm = 48 Ohm. This way, the generic networks accounted: in example above there will be corporate (z32) and state (z16) connection.

The middleware approach isn’t new, as any hardware router Niagara consists of MIB, the size of which is 769 kB, compounded with routing table and generic networks set. Such system works with MME driver using discretization frequency of 192 kHz and allows connecting the whole pool of Compositor RTOS v9.0.1 forwarding platform (which is 6559 MIB’s on a moment of writing) using a dump, which is also recorded on 192 kHz sample rate. The upper frequency of z128 generic is 150 GHz, but each middleware includes RAD96 fixation, that is why an effective range is extended up to 300 GHz.

Niagara is a client system that is why it demands calling an operator for configuring programming commands. I already reviewed NIM radio chat, which I call (No Internet Messenger) last year. It turns out that it is also an acronym for Nuclear Instrumentation Module.

Each command, presented in the full version of English and Russian documentation, should be made only through an operator and each middleware has its own operator, which depends on VLAN set and servers, connected to NIM. This way, you are requesting network topology and demand operator to execute other commands, and it decides if to make command or not.

At first, middleware ran in RAD96 sandbox, but now middleware and dump become a multifunctional products. The development period of Niagara project is 2001 – 2019 and not 2012 – 2019 as the host Compositor program. The reason for this is that Niagara consists of middleware and dump and they are including the Royalty routing tables. This is proved by Inaccessible Page file emission (track recording, which is a routing path). This track, made in 2001, is a part of IP emission. The period of 2010 to 2019 covered by the reference files of timeserver, which emission contains and it is responsible for routing path hops GPS positioning in present time.

Niagara v1.0 a3

That is why Ruslan Yusipov digital portrait with codename Niagara contains 18 years of art, which is a long background for 35 years old author. Older recordings exist, such as the audiocassette recording of Yamaha PSR-330 synthesizer direct signal, which is Ruslan Yusipov live performance at the age of 14, with the author voice accompaniment, that is why Niagara is 21 years development project from 1998 to present moment.

Ruslan Yusipov art is not limited by 6559 MIB’s emission and can be enriched by routing tables from the CD-archive. This way, at the year 2021 I account to receive database of 10000 MIB’s, which will allow adding more stochastic distributions for flows selection in Compositor v9.0.1 a15.

Compositor, IEEE802.1Q, Niagara, NIM, RAD96, radio chat, RTOS, Ruslan Yusipov, sandbox, TCP/IP

Tag : TCP/IP

Superstar Architecture