Abstract: Decentralized systems and methods provide smart contracting when electronic information is exchanged between authorized and permitted user(s) where creating, uploading, accessing, viewing, editing, redlining, replying, printing, downloading, e-signing and or marking up are each stored as separate immutable blocks within the permission based blockchain allowing the system to securely track the version history and users activity to enforce legally binding and verification processes.

Abstract: Decentralized security methods and systems using a hybrid permission based blockchain with public key infrastructure (PKI) for storage, access, distribution, exchange and execution of electronic information including images, files, media between individuals and or nodes is more secure on connected devices and servers than traditional systems and software applications that are vulnerable to cyberattacks and theft. Email is a popular way of transferring documents and other forms of content. However, there does not exist a decentralized system to protect sensitive information against cyber attacks and theft such that the information can be shared, accessed, executed, and or distributed to other individual(s) and or systems—including save, upload, email, co-author, co-edit, redline, comment, markup, e-sign documents that automatically enforces legally binding and verification processes for and between individual(s) and or business(es).

Abstract: Decentralized security methods and systems using a hybrid permission based blockchain with public key infrastructure (PKI) for storage, access, distribution, exchange and execution of electronic information including images, files, media between individuals and or nodes is more secure on connected devices and servers than traditional systems and software applications that are vulnerable to cyberattacks and theft. Email is a popular way of transferring documents and other forms of content. However, there does not exist a decentralized system to protect sensitive information against cyber attacks and theft such that the information can be shared, accessed, executed, and or distributed to other individual(s) and or systems—including save, upload, email, co-author, co-edit, redline, comment, markup, e-sign documents that automatically enforces legally binding and verification processes for and between individual(s) and or business(es).

Abstract: A multiprotocol transport network (MPTN) gateway provides transparent interconnection of two or more SPTNs running different transport layer protocols to form an integrated heterogeneous MPTN. The MPTN gateway of the present invention has no dependencies on the particular transport protocols running on the SPTNs being interconnected as it utilizes a common transport provider (a Gateway Services Protocol Boundary (GSPB)) between the SPTN transport protocols and the gateway components. The MPTN gateway supports connections between end systems across multiple intermediate networks. The MPTN gateway provides automatic routing based on dynamic participation in the routing protocols of the interconnected SPTNs so that any number of gateways may be interconnected and in any topology desired. As the MPTN gateway has a general architecture and acquires routing information automatically, it supports not only other MPTN nodes and gateways but also non-MPTN nodes and gateways.

Abstract: The present invention is a general solution to the problem address incompatibility between application programs and transport services. The invention may be embodied in a method for mapping the application program address (program address) to the transport services address (transport Provider address). According to the method, a program address is registered in the network so that it becomes available to other programs that understand the address, even if they are running over a transport protocol that does not understand the address format. When a request is made that a connection be established between a program and a program partner or that a datagram be sent therebetween, the program address is mapped to the transport Provider address (if necessary). The program address is then conveyed to the program partner so that it knows who it is talking to.

Abstract: A Transport Layer Protocol Boundary (TLPB) architecture is described which will permit an application program to run over a non-native transport protocol without first generating a protocol compensation package tailored to the transport protocols assumed by the program's application programming interface and by the available transport provider. All transport functions required by the program are converted to standardized or TLPB representations. When a connection between the first application program and a second remote application is requested, the individual required TLPB transport functions are compared to corresponding functions supported by the transport provider. Compensations are invoked only where there is a mismatch. The node on which the remote application program runs is informed of the compensations so that necessary de-compensation operations can be performed before the data is delivered to the remote application program.