User:SPiZlE2014/sandbox

Introduction
In data security and communication security and Artificial Intelligence, the null expanding method protects databases and telecommunication devices from unwanted access and communications from unauthorized users. The fundamental operation of the method is using the physical constraints of a device such as all of a device's CPU time or the appropriated hardware architecture to securely control communication between devices. With the execution constant, security will be maintained with self-modifying code using DLL injection , classloaders , better known as run-time dynamic linking and loading. A communication device will now be able to determine if a connected device is using execution time for malicious activities and the inevitable hacking of a device.

Telecommunication Devices
When beginning a connection between devices, each device will have access to their own set of communication classes that vary in size and design. The device establishing the connection will be the first to receive one of these classes. Each device will from now on only use these classes to communicate which contain a communication protocol alongside the class's design protocol. Class designs will include arithmetic operations and superfluous code designed to be returned to the sending device with the correct arithmetic values and at the known timing coinciding with the CPU execution constant. If values received by a device are incorrect or the response is received outside the logical execution bound, the receiving device will cease all communications for security.

Trusted connections
For the method implementation to work a major effort is required in the telecommunication industry. Device operating systems, communication routing systems and all types of communication devices will need to adhere to the method standard and document execution and transfer timings in a database where users can update their devices.

Request for control
With mobile phones and other devices, the logical criteria requires a broader control synthesis to satisfy all operating options. This includes communication with a connected device while running other programs simultaneously. In some situations computers could use a more concrete implementation described later on this page, but for all devices the implementations are interchangeable.

Web Networking
//tbc

Web services network
This network controls routing to Type-A  computers in the null expanding architecture and controls the backlog of service-oriented data in the case all Type-A computers are in use or a transfer attempt fails. Type-A computers handle only one transfer at a time and are apart of large computer arrays to avoid a significant backlog of transfers.

Physical concurrency check
The Web services network retains, as a failsafe, a copy of data uploaded to the secure database network until it is confirmed both databases contain the data at which point the web services network will delete it's copy.

XI Arrays
XI Arrays are connected pairs of Type-A and Type-B computers protecting the secure network database from being compromised. This is accomplished by Type-B computers measuring the execution time of Type-A computers.

Type-A and Type-B computers
Type-B computers have access to pairs of Communication classes that vary in size and design. The pairs are propagated down the hierarchy and used to securely pass data and protect the network. One side of a pair will remain on the Type-B computer while the other is passed to the Type-A computer. The Type-A computer loads and executes it's class at runtime while it's  central processing unit operates at maximum capacity. The Type-B computer monitors that it receives class specific arithmetic values and that they are received at logical execution timings. A data transfer to the Type-B computer will now have a protected upload timing. All communication between Type-A and Type-B computers use user datagram protocol. If any arithmetic values are incorrect or if any data is passed out of its known timing, that Type-A computer will be blocked until it is deemed safe.

Type-X computers
Type-X computers extend the Type-A and Type-B relationship into a multitier architecture. Every Type-A array will have a matching Type-B array. Every Type-B array will have a matching Type-X array and so on. Once the Type-A and Type-B communications have completed, the same relationship will immediately resume between the Type-B and Type-X computers. The multitier protects against a Type-B computer receiving malicious code and being compromised by a Type-A computer.

Type-C computers
Type-C computers keep the network secure by providing a anti-virus service to the  medium used when data is physically transferred.

Pseudocode


Type B

Timer started

Class pair selected

Class pair-B loaded

Wait for ready command...

Ready command from Type-A received

Class pair-A sent

Class pair-B executed

Receives arithmetic value from Type-A

Compares value and time stamp

Randomizes value

Sends value to type-A

Receives arithmetic value from type-A

Compares value and time stamp

Receives data

Compares time stamp

Sends success command to Type-A

Passes data upstream (will become Type-A in the multitier)

Type A

Sends ready command

Receives class

Loads and executes class

Operate on value and send

Receives value

Operate on value and send

Sends data

Receives success command

Sends success command to Web services network