Pervasive, user-centric network security enabled by dynamic datagram switch and an on-demand authentication and encryption scheme through mobile intelligent data carriers

[0001] 1. Field of the Embodiments

[0002] The present disclosure relates in general to digital network communications. Specifically, the present disclosure relates to secure data transmission and secure provision of remote application services in an open or closed network setting. More specifically, methods and integrated systems are provided in various embodiments for improving security, efficiency, access control, administrative monitoring, and reliability as well as integrity of data transmission and remote application sharing over a network. The disclosed methods and systems employ a datagram schema that enables dynamic datagram switching in network transactions that supports a multitude of applications and network services. Mobile intelligent data carriers are provided in various embodiments that allow for implementation of an authentication and encryption scheme that is transparent to a user. The pervasive, user-centric network security enabled by the disclosed methods and systems may be advantageously deployed in, among other things, the financial and banking environment, the national security and military information technology (IT) systems, the healthcare management networks, the IT infrastructure for legal and other professional consultation services, and various online commercial transaction systems. The systems and methods according to this disclosure may be implemented in connection with biometric and other suitable authentication means.

[0003] 2. Description of the Related Art

[0004] The digital revolution, accompanied by globalization, is transforming people's life in an unprecedented way. The growth and evolution of the Internet fuels the expansion of the existing businesses while fostering the emergence of new enterprises cross nation lines. In today's global economy, the viability of a business or research institution turns in a large part on its efficiency in processing and managing information. Data transmission and management is thus playing an increasingly vital role in a variety of industries. Not unexpectedly, engineers and business visionaries have been faced with a significant challenge to institute secure network systems that enable stable and efficient data transmission, effective access control, and remote sharing and management of application resources among distributed computers in service to multiple users.

[0005] Various network configurations have been in use in institutional IT infrastructures. Ethernet, token ring, and client-server architecture, for example, are widely adopted. Related technologies for data encryption and compression are similarly known and have been utilized to facilitate secure data transmission. However, the existing network systems frequently suffer from such problems as interception of data transactions and loss of network connections, among other things. Often, once a connection is lost, it is difficult to quickly restore it, let alone to accurately reestablish the parameters of the lost connection thereby ensuring the integrity of the reconnection. Inevitably in these situations, data may be lost and data transmission will need to start over. And yet, sometimes, the loss may be permanent if one cannot trace and gather a threshold level of information to allow rescue. This lack of stability greatly compromises the fidelity of data transmission and thus poses a fatal problem for distributive data processing and management. Significant costs are incurred in coping with such failure in an institutional setting. In fact, an entire industry can be disadvantaged by such a problem, as manifested in the difficulties encountered in the recent years by on-line electronic businesses.

[0006] The problem of instable—hence unreliable—network communications is compounded by a want of comprehensive, robust, user-friendly, and cost-efficient network security solutions for safeguarding information dissemination and application management in a distributive enterprise IT environment. Consequently, the private businesses and public institutions alike suffer significant financial losses from security breaches and uncoordinated information and application management. A great deal of money is also wasted on inefficient IT security solutions.

[0007] Drawbacks of the current network security solutions are manyfold. In the main, four aspects are noteworthy: First, there is lacking an integrated system that can secure an entire network without severely limiting business growth. Organizations are forced to employ a multiplicity of products from different vendors to fulfill different security functions. Each of these products only solves a discreet aspect of the overall network security needs. For example, a firewall does not encrypt data being transmitted across the Internet; an Intrusion Detection System (IDS) cannot validate and ensure that the person who enters an authorized login name and password to open a Virtual Private Network (VPN) connection is in fact the intended user; and, a VPN doesn't help an IT department monitor user rights and access policies. Thus, no existing system or method is capable of singularly protecting every aspect of a network. Resorting to multiple security products from competing vendors, public and private enterprises alike are faced, at the minimum, with the problem of incompatibility. Maintaining a fluctuating number of peripheral security devices and software packages can also be extremely complex and overly expensive. And, on the whole, such patchwork solution is less than effective in protecting institutional IT framework.

[0008] Secondly, the existing focus is on securing devices and data. Such system-centric approach fails to safeguard the point of access from individual users who use the devices. This inherent problem with the current approach will become more and more conspicuous as the number of devices and degree of user mobility increases—an inevitable as the world is transitioning into pervasive computing.

[0009] To appreciate the inherent flaws in the system-centric systems, one can consider the various scenarios of cyber-crimes. It is understood by an ordinary Internet user today that every single form of cyber-crime involves the attempt of the attacker to disguise its identity, whether masquerading as someone else or covering its trail over the routings. One reason why such attack too often succeeds is because the techniques used to establish and verify the user's identity today are fallible. For example, most passwords are easy to break; they are often too obvious or are stored on a device that can be easily compromised. The existing infrastructure supporting digital certificates and public/private keys is also relatively easy to abuse. Therefore, the existing ways for identifying the users of a network device and securing the device vis-à-vis these users—hence system-centric—presents inherent security liabilities. A high level of security can never be achieved when the identity of those who attempt to access the protected network cannot be effectively pinpointed. A major paradigm shift thus seems warranted for better network security. That is, the focal point needs to shift from protecting the devices and data to protecting the users. A true user-centric scheme for establishing and validating user identities—thereby enabling mobile access and event-based, user-centric security—is desirable.

[0010] Third, the existing IT security solutions are too complex for ordinary users. Average users are expected to perform complicated security procedures, which often result in errors and security lapses in the enterprise IT environment. For example, VPNs are not plug'n'play straightforward to install, operate, or maintain. Encrypting emails involves extra work so very few ever bother to do it. Even selecting and remembering a good password is too much trouble for most average users. Relying on people who are not IT experts to perform complicated security procedures simply doesn't work. An ordinary user may find ways to bypass the security procedures or outright ignore them. Further, for many IT departments, maintaining and operating a deluge of software patches may drain the available resources and exceed their capacities. Therefore, an effective yet simple security paradigm is in need.

[0011] And finally, like in any other fields, certain inertia exists in the IT security industry. Changes and new methodologies to some extent are resisted. The existing way of doing things prevails and dominates the market of network security solutions, both on the provider and the consumer side. In this regard, the VPN is a useful example. Originally it was designed to provide a secure tunnel between two secure environments. The technology was then modified to meet the needs of remote or mobile users. It now relies on non-technical users to execute complex IT security procedures. Consequently, although the VPN still creates secure tunnels through the Internet, the client end can be easily—and frequently is—compromised. Such adherence to the existing technologies—and the band-aid approach connected thereto—leaves the users with dissatisfactory solutions and at the same time significantly sets back the development of true innovative systems and methods for securing network communications.

[0012] For the aforementioned reasons, there is a need for a new network security paradigm that delivers the desired reliability, efficiency, and user-friendliness. The kind of security solution that can sustain the needs of distributive IT framework and support pervasive computing and information processing must address the fallacies of the existing systems. A skilled network engineer or a learned user of business IT networks will be able to appreciate the importance of better IT security solutions. To that end, a brief review of the history of institutional computing and IT networks will be useful.

[0013] The first computers were mainframes. These complex monolithic devices required a protected environment to function properly. They could only be operated by skilled technicians who were charged with highly specialized knowledge. Access to them was limited and they offered limited connectivity with other devices. As a result, they were easy to secure.

[0014] The advent of the personal computer (PC), the evolution of networking technology and, particularly, the recent explosive growth of the Internet transformed the way people use and relate to computers. The size of the computer devices decreased. These machines became easily moveable. The user-friendly graphical interfaces made it possible for non-technical individuals to operate them. The computers were connected to create computer networks, allowing for fast and easy information and application sharing. The Internet brought the network connectivity to its acme—the true global connectivity that is affordable to the mass. In addition to the desktop and laptop PCs, personal digital assistant (PDAs), Tablet PCs, and mobile phones grew popular with people who need network access while not in their home or office.

[0015] The rapid advance of technologies and expansion of business needs as such presented an unprecedented challenge for the IT departments around the world. An ever-increasing amount of data—accessible from a vast number of devices—needs to be protected. And, such protection must be instituted against the backdrop of the broadband “always-on” connections. Also noteworthy is the regulatory initiative in various countries addressing privacy and information ownership concerns over the Internet. Clearly, a network security solution that is technically robust and comprehensive business-wise is needed, especially in view of the next inevitable phase of the IT evolution, one marked by pervasive computing. All analog devices are being and will be replaced by digital counterparts. Televisions, telephones, CDs and DVDs, cameras, video cameras, and computer game platforms alike will—if not already—all support Internet access. As data access becomes possible everywhere and all the time, the need for protecting proprietary corporate data and sensitive private information becomes more pressing and, the level of difficulty in meeting such needs correspondingly elevates.

[0016] In sum, reflecting on the evolution of the organizational IT infrastructure and the current deficiencies in secure network communications, one of ordinary skilled will appreciate the need for systems and methods that improve the security, stability, efficiency, and flexibility of network data transmission and, connected thereto, the need for a new network paradigm for secure and reliable enterprise information management and application sharing.

[0017] It is therefore an object of this disclosure to provide systems and methods for improving the reliability, flexibility, simplicity, and efficiency of secure data transmission and application sharing over a network. Particularly, the methods and systems disclosed herein enable an improved client-server architecture that supports secure, flexible network connections and reliable, efficient network transactions among multiple users. This IT network platform delivers pervasive security—i.e., security on demand with variegated network connecting devices—and it is user-centric—secures the users not the devices the users use to connect to the network. In certain embodiments, the pervasive and user-centric security may be instituted with the presently disclosed systems and methods anytime, anywhere, using any network device.

[0018] A datagram schema is provided in certain embodiments, which allows for the implementation of dynamic datagram switching in support of a multitude of applications and network services. In other embodiments, various mobile intelligent data carriers are provided, allowing for the implementation of an authentication and encryption scheme that is transparent to a user. The pervasive, user-centric network security according to this disclosure may be advantageously deployed in any enterprise IT environment around the world where a distributive computer network is used, including, for example, governments, militaries, manufacturers, and in financial service, insurance, consulting, healthcare, and pharmaceutical industries. According to various embodiments, this IT security platform may facilitate a broad array of business operations, including, inter alia, inventories, sales, customer services, marketing and advertisement, teleconferencing, and remote sharing of a variety of applications. The systems and methods of this disclosure may be implemented in connection with biometric and other suitable authentication methodologies in certain embodiments.

[0019] The present disclosure thus provides a network security platform that is distinctive compared to the existing patchwork solutions. A holistic approach is taken and a single solution is provided that allows organizations to protect the entire network, even as the network dynamically extends its resources to users anywhere in the world and through any connection device or application interface. The network security platform of this disclosure focuses on securing the user, not the various network devices used by the user. Such user-centric scheme affords unprecedented simplicity and flexibility, which, in turn, lends improved user-friendliness to the network security platform according to this disclosure. The enhanced security is transparent to the user. And yet, the professionals in the IT departments are charged with the complete control over all user access. The user activities may be effectively monitored as needed.

[0020] In accordance with this disclosure, there is provided, in one embodiment, a system of secure network connectivity between one or more users and at least one network server. The secure network connectivity is user-centric and supports pervasive security. The term user-centric means that the system secures the one or more users instead of one or more devices employed by the users to connect to the network server. The pervasive security is security on demand, using one or more connecting devices. The system comprises: (A) at least one intelligent data carrier, issued to the one or more user, wherein the intelligent data carrier comprises at least (i) one memory, capable of storing digital information, (ii) one input-output apparatus, capable of inputting and outputting digital information, and (iii) one processor, capable of processing the digital information stored in the memory and connecting to a computer device thereby transmitting the digital information via the input-output apparatus. The intelligent data carrier is capable of establishing the identities of the one or more user through an authentication and encryption scheme; and (B) a dynamic datagram switch for dynamic allocation and swapping of datagrams for a multiplicity of applications in service to the one or more users.

[0021] According to one embodiment, the intelligent data carrier is mobile. According to another embodiment, the intelligent data carrier is selected from the group consisting of USB key, Compact Flash, Smart Media, Compact Disk, DVD, PDA, firewire device, token device.

[0022] According to yet another embodiment, the authentication and encryption scheme comprises the following sequential steps: a) a request being caused to forward from the intelligent data carrier to the network server that the intelligent data carrier be authenticated; b) the network server presenting to the intelligent data carrier a plurality of authentication methods; c) the intelligent data carrier selecting one authentication method from the plurality through an event; d) the network server sending the intelligent data carrier a demand, based on the selected method, for authentication data from the intelligent data carrier; e) the network server transforming the authentication data received from the intelligent data carrier into one or more data authentication object, each of data authentication objects is a data vector object, capable of being analyzed using one or more classifiers; f) the network server analyzing the data authentication object, according to the one or more classifiers, thereby determining the result of the authentication; and g) the network server sending the result to the intelligent data carrier, indicating a successful or failed authentication attempt.

[0023] According to a further embodiment, the event in step c) is a click of a mouse, a touch on a screen, a keystroke, a touch on a screen, an utterance, or any suitable notification means. According to still a further embodiment, the demand in step e) comprises at least one of a pseudo random and true random password. The pseudo random password is generated based on a mathematically pre-calculated list, and a true random password is generated by sampling and processing a source of entropy outside of the system.

[0024] According to another embodiment, the randomization is performed with at least one seed from an indeterministic source, which is a source that is not capable of being predicted from the parameters surrounding the network server or the intelligent data carrier. According to yet another embodiment, the randomization is performed with one or more random generators and one or more independent seeds.

[0025] According to a further embodiment, the analyzing in step f) comprises one or more analysis rules. In a still further embodiment, the one or more analysis rule comprises classification according to the one or more classifiers of step e).

[0026] According to another embodiment, the randomization in data vector objects is performed in connection with the one or more classifiers.

[0027] According to yet another embodiment, the classification comprises speaker verification, wherein the data object vector involves two classes, the target speaker and the impostor. Each speaker is characterized by a probability density function. The determining in step f) is a binary decision problem.

[0028] According to a further embodiment, the one or more classifiers in step e) comprise a super classifier. More than one data vector objects exist for event level authentication. The determining in step (f) is based on superior or random sum computed from the data vector objects.

[0029] According to a still further embodiment, the super classifier is used for physical biometrics, which comprises at least one of voice recognition, fingerprints, handprints, blood vessel patterns, DNA tests, retinal or iris scan, and face recognition.

[0030] According to another embodiment, the super classifier is used for performance biometrics, which comprises habits or patterns of individual behaviors.

[0031] According to yet another embodiment, the determining of step f) is performed by computing the sum, superiority, or probability from one or more data authentication objects, based on the one or more classifiers of step e).

[0032] According to a further embodiment, the authentication and encryption scheme comprises asymmetrical and symmetrical multi-cipher encryption. In a still further embodiment, the encryption uses at least one of output feedback, cipher feedback, cipher block chaining, and cipher forwarding.

[0033] According to another embodiment, the authentication and encryption scheme uses Secure Key Exchange (SKE). In yet another embodiment, SKE employs a public key system. In still another embodiment, SKE employs Elliptic Curve Cryptosystem (ECC) private keys. In a further embodiment, the encryption is based on Advanced Encryption Standard (AES) Rijndael.

[0034] According to a still further embodiment, the multiplicity of applications is selected from the group consisting of window-based remote terminal server applications, applications on 3270/5250 terminal emulators for mainframe, digital video, audio, and text based communications, and directly embedded applications. In another embodiment, the directly embedded applications are selected from the group consisting of database applications, data analysis tools, Custom Relation Management (CRM) tools, and Enterprise Resource Planning (ERP) packages, and any combination thereof.

[0035] According to another embodiment, the dynamic datagram switch comprises a datagram schema and a parser. The datagram schema comprises two or more datagrams, belonging to one or more datagram types. The datagram is capable of carrying information for managing and controlling network connections and network data transmission. Each datagram type comprises a plurality of functions. The parser is capable of parsing the one or more datagram types.

[0036] According to yet another embodiment, the datagram schema comprises at least one major datagram type and within the one major datagram type, at least one minor datagram type.

[0037] According to still another embodiment, the parser is capable of parsing a matrix of datagram types. In a further embodiment, the matrix comprises a first multiplicity of major datagram types and in each major datagram type of the first multiplicity, a second multiplicity of minor datagram types. In a still further embodiment the first multiplicity is 256 and the second multiplicity is 256.

[0038] According to another embodiment, the major datagram type is selected from the group consisting of (i) the server messages and connection control datagram, capable of authenticating and controlling user connections, (ii) the content datagram, capable of managing the transmission of the content data, (iii) the broadcast datagram, capable of managing the real-time point-to-point, point-to-multipoint, and multipoint-to-multipoint data transmission, and (iv) the connection proxy datagram, capable of passing proxy data between the network server and the intelligent data carrier.

[0039] In yet another embodiment, the server messages and connection control datagram comprises minor datagram types such as: (i) the authentication request datagram, capable of initiating an authentication request, (ii) the authentication reply datagram, capable of sending a response upon a request of authentication, and (iii) the authentication result datagram, capable of sending the result of an authentication session.

[0040] In still another embodiment, the content datagram comprises minor datagram types such as: (i) the normal content datagram, capable of transmitting the content data, (ii) the remote logging datagram, capable of communicating with the network server and establishing a login session, and (iii) the remote data collector datagram, capable of transmitting data from a remote connection.

[0041] In a further embodiment, the content datagram further comprises minor datagram types such as: (iv) the content approval request datagram, capable of requesting verification of the content data transmitted, and (v) the content approval reply datagram, capable of responding to a request of verification of the content data transmitted.

[0042] In a still further embodiment, the connection proxy datagram comprises minor datagram types such as: (i) proxy data to server, capable of passing proxy data to the network server from the intelligent data carrier, and (ii) proxy data from server, capable of passing the proxy data from the network server to the intelligent data carrier.

[0043] According to another embodiment, each datagram in the datagram schema has a generic layout comprising (A) the header fields for (i) the major datagram type, (ii) the minor datagram type, (iii) the datagram length, and (iv) the datagram checksum, and (B) the datagram payload, carrying the content data in transmission. In yet another embodiment, the datagram comprises one or more additional header fields.

[0044] According to still another embodiment, the major datagram type is the instant message type and the minor datagram type is selected from the group consisting of the file transmission type, the audio-video transmission type, the instant mail message type, and the remote data collection type.

[0045] According to a further another embodiment, each datagram in the datagram schema is carried within a TCP packet. In a still further embodiment, the generic layout of the datagram follows a TCP header.

[0046] According to another embodiment, the system of secure network connectivity further comprises one or more radar connector, capable of monitoring and controlling network connections. In yet another embodiment, the radar connector is further capable of detecting the lost connection and initializing contact to the network server thereby reestablishing the connection. According to still another embodiment, in the system of secure network connectivity, the network server and the intelligent data carrier each is connected to one radar connector.

[0047] According to a further embodiment, the system of secure network connectivity further comprises one or more injector, capable of connecting one or more existing networks to the network server and transmitting data between the existing network and the intelligent data carrier via the network server. The existing network is wired or wireless, with one or more digital devices. In a still further embodiment, the digital device is at least one of a computer, a Personal Digital Assistant (PDA), a digital mobile phone, a digital audio-video player, and a digital camera. In another embodiment, the one or more injector each is connected to a radar connector.

[0048] In accordance with the present disclosure, there is provided, in another embodiment, a client-server communication system, which comprises at least one server and at least one client. Each client is an intelligent data carrier, which comprises at least (i) one memory, capable of storing digital information, (ii) one input-output apparatus, capable of inputting and outputting digital information, and (iii) one processor, capable of processing the digital information stored in the memory and connecting to a computer device thereby transmitting digital information via the input-output apparatus. The intelligent data carrier is capable of establishing the identities of one or more user through an authentication and encryption scheme for secure data transmission between the server and the client.

[0049] According to another embodiment, the secure data transmission through the client-server communication system supports user centric and pervasive security. The user-centric security refers to securing one or more users instead of one or more devices employed by the users to connect to the network server. The pervasive security is security on demand, using one or more connecting devices.

[0050] According to yet another embodiment, the intelligent data carrier used in the client-server communication system is mobile. In still another embodiment, the intelligent data carrier is selected from the group consisting of USB key, Compact Flash, Smart Media, Compact Disk, DVD, PDA, firewire device, token device.

[0051] According to still another embodiment, the server in the client-server communication system further comprises a dynamic datagram switch for dynamic allocation and swapping of datagrams for a multiplicity of applications in service to one or more clients. In a further embodiment, the dynamic datagram switch comprises a datagram schema and a parser. The datagram schema comprises two or more datagrams, belonging to one or more datagram types. The datagram is capable of carrying information for managing and controlling network connections and network data transmission. The parser is capable of parsing a plurality of datagram types.

[0052] According to a still further embodiment, the client-server communication system further comprises one or more injector, capable of connecting the server to one or more existing networks and transmitting data between the existing networks and the client via the server. The existing network is wired or wireless, which comprises one or more digital devices. In another embodiment, the digital device is a computer, a Personal Digital Assistant (PDA), a mobile phone, a digital audio-video player, and a digital camera. According to yet another embodiment, in the client-server communication system, each server, client, and injector is further connected to a radar connector, capable of monitoring and controlling network connections. In still another embodiment, the radar connector is further capable of detecting the lost connection and initializing contact to the network server thereby reestablishing the connection.

[0053] According to a further embodiment, the server in the client-server communication system further comprises an encrypted virtual file system, capable of secure storage of data in a virtual file system for each client.

[0054] In accordance with the present disclosure, there is provided, in yet another embodiment, an intelligent data carrier, which comprises at least (i) one memory, capable of storing digital information, (ii) one input-output apparatus, capable of inputting and outputting digital information, and (iii) one processor, capable of processing the digital information stored in the memory and connecting to a computer device thereby transmitting digital information via the input-output apparatus. The intelligent data carrier is capable of establishing the identities of one or more user through an authentication and encryption scheme for secure data transmission in a network.

[0055] According to another embodiment, the secure data transmission using the intelligent data carrier is characterized by user centric and pervasive security. The user-centric security refers to securing one or more users instead of one or more devices employed by the users to connect to the network server. The pervasive security is security on demand, using one or more connecting devices. In yet another embodiment, the intelligent data carrier is mobile. In still another embodiment, the intelligent data carrier is selected from the group consisting of USB key, Compact Flash, Smart Media, Compact Disk, DVD, PDA, firewire device, token device.

[0056] In accordance with the present disclosure, there is provided, in still another embodiment, the method for establishing user-centric, pervasive network security. The method comprises issuing to each of the one or more users an intelligent data carrier; and providing a dynamic datagram switch for dynamic allocation and swapping of datagrams for a multiplicity of applications in service to the one or more users. In various embodiments, the method performs authentication, encryption, and randomization in connection to data vector objects, in the same manner as that in the aforementioned system of secure network connectivity. Super classifiers are used, particularly in certain embodiments, for physical biometrics, which comprises at least one of voice recognition, fingerprints, handprints, blood vessel patterns, DNA tests, retinal or iris scan, and face recognition. And, in other embodiment, super classifiers are used for performance biometrics, which comprises habits or patterns of individual behaviors.

[0057] According to another embodiment, the dynamic datagram switch used in the method of establishing user-centric, pervasive network security comprises a datagram schema and a parser. The datagram schema comprises two or more datagrams, belonging to one or more datagram types. The datagram is capable of carrying information for managing and controlling network connections and network data transmission. The datagram type comprises a plurality of functions. The parser is capable of parsing the one or more datagram types.

[0058] According to yet another embodiment, the datagram schema comprises at least one major datagram type and within the one major datagram type, at least one minor datagram type. According to still another embodiment, the parser is capable of parsing a matrix of a first multiplicity of major datagram types and in each major datagram type of the first multiplicity, a second multiplicity of minor datagram types.

[0059] According to a further embodiment, the datagram in the datagram schema has a generic layout, which comprises (A) the header fields for (i) the major datagram type, (ii) the minor datagram type, (iii) the datagram length, and (iv) the datagram checksum, and (B) the datagram payload, carrying the content data in transmission. In a still further embodiment, the datagram comprises one or more additional header fields. According to another embodiment, each datagram in the datagram schema is carried within a TCP packet. In yet another embodiment, the generic layout of the datagram follows a TCP header.

[0060] According to yet another embodiment, the method further comprises providing one or more radar connector, capable of monitoring and controlling network connections, wherein the network server and the intelligent data carrier each is connected to one the radar connector. In still another embodiment, the radar connector is further capable of detecting the lost connection and initializing contact to the network server thereby reestablishing the connection.

[0061] According to a further embodiment, the method further comprises providing one or more injector, capable of connecting one or more existing networks to the network server and transmitting data between the existing network and the intelligent data carrier via the network server. The existing network is wired or wireless, which comprises one or more digital devices. In still a further embodiment, the digital device is a computer, a Personal Digital Assistant (PDA), a digital mobile phone, a digital audio-video player, and a digital camera. In another embodiment, the one or more injector each is connected to a radar connector.

[0062] In accordance with the present disclosure, there is provided, in a further embodiment, a method for target delivering one or more applications to an authorized user. The method comprises: (A) issuing to the user an intelligent data carrier, which has at least one memory, one input-output apparatus, and one processor, which is capable of establishing the identities of the user through an authentication and encryption scheme; and (B) providing a computer device connecting to a network on which a network server sits. The intelligent data carrier is capable of docking to the connecting device and being authenticated by the network server based on the authentication and encryption scheme. The one or more applications are capable of being launched off the intelligent data carrier once the user is successfully authenticated.

[0063] According to another embodiment, the one or more application is preloaded on the intelligent data carrier or installed on the network server.

[0064] According to yet another embodiment, the computer device is connected to the network via wired or wireless means. In still another embodiment, the computer device is at least one of a desktop or laptop computer, a personal digital assistant (PDA), a digital mobile phone, a digital TV, and any network-enabled digital audio-video device.

[0065] According to a further embodiment, the one or more applications are selected from the group consisting of database applications, data analysis tools, Customer Relation Management (CRM) tools, Enterprise Resource Planning (ERP) packages, window-based remote terminal server applications, applications on 3270/5250 terminal emulators for mainframe, digital video, audio, and text based communications, and any combination thereof.

[0066] According to a still further embodiment, the intelligent data carrier is mobile. In another embodiment, the intelligent data carrier is selected from the group consisting of USB key, Compact Flash, Smart Media, Compact Disk, DVD, PDA, firewire device, token device.

[0067] According to yet another embodiment, the method for target delivering user applications further comprises a dynamic datagram switch for dynamic allocation and swapping of datagrams for a multiplicity of applications in service to one or more authorized users.

[0068] In accordance with the present disclosure, there is provided, in a still further embodiment, a system of secure network connectivity between one or more users and at least one network server, wherein the secure network connectivity is user-centric and supports pervasive security. The system comprises at least one intelligent data carrier, issued to the one or more user. The intelligent data carrier comprises at least one memory, one IP apparatus, and one processor. It is capable of establishing the identities of the one or more user through an authentication and encryption scheme and supporting a multiplicity of applications in service to the one or more users. The authentication and encryption scheme comprises the following sequential steps: (a) a request being caused to forward from the intelligent data carrier to the network server that the intelligent data carrier be authenticated, (b) the network server presenting to the intelligent data carrier a plurality of authentication methods, (c) the intelligent data carrier selecting one authentication method from the plurality through an event, (d) the network server sending the intelligent data carrier a demand, based on the selected method, for authentication data from the intelligent data carrier, (e) the network server transforming the authentication data received from the intelligent data carrier into one or more data authentication object, wherein each data authentication object is a data vector object, capable of being analyzed using one or more classifiers, (f) the network server analyzing the data authentication object, according to the one or more classifiers, thereby determining the result of the authentication, and (g) the network server sending the result to the intelligent data carrier, indicating a successful or failed authentication attempt.

[0069] In accordance with the present disclosure, there is provided, in another embodiment, a method for establishing user-centric, pervasive network security. The method comprises issuing to each of the one or more users an intelligent data carrier. The intelligent data carrier comprises at least one memory, one IP apparatus, and one processor. It is capable of establishing the identities of the one or more user through an authentication and encryption scheme and supporting a multiplicity of applications in service to the one or more user. The authentication and encryption scheme comprises a series of aforementioned steps.

[0070] In accordance with the present disclosure, there is provided, in yet another embodiment, a client-server communication system. The communication system comprises at least one server and at least one client. Each client is an intelligent data carrier that comprises at least one memory, one IO apparatus, and one processor. The intelligent data carrier is capable of establishing the identities of the one or more user through an authentication and encryption scheme and supporting a multiplicity of applications in service to the one or more user. The authentication and encryption scheme comprises a series of aforementioned steps.

[0071] According to certain embodiments, the dynamic allocation and swapping in the dynamic datagram switch employed in the secure network system and method is performed in real time. According to other embodiments, the dynamic allocation and swapping comprises the use of memory pointers of two or more datagrams.

Brief Discussions Of Relevant Terms

[0080] The following terms, network, client, server, data, data vector object (also referred to as data object vector, object vector), classifier, decision-making, deterministic analysis, object based deterministic analysis (also referred to as object analysis), random number, random number generator, seed, randomization, probability, probability density function, authentication, private key, public key, Elliptic Curve Cryptography (ECC), ECC signature, parser, packet, header, TCP, UDP, firewall, Universal Serial Bus (USB), Apple Serial Bus (ASB), Serial Port, Parallel Port, token, firewire, as well as other relevant terms throughout the present disclosure, are to be understood consistently with their typical meanings established in the relevant art, i.e. the art of mathematics, computer sciences, information technology (IT), physics, statistics, artificial intelligence, digital networks, network communications, Internet technologies, cryptography, encryption and decryption, compression and decompression, classification theories, prediction modeling, decision making, voice recognition, and biometrics.

[0081] The following terms, Secure Key Exchange (SKE), Advance Encryption Standard (AES), Public Key Infrastructure (PKI), Encrypted Virtual File Systems (EVFS), Virtual Private Network (VPN), Intrusion Detection System (IDS), Demilitarized Zone (DMZ), Personal Digital Assistant (PDA), USB key, USB token, USB dongle, Parallel Port dongle, Serial Port dongle, firewire device, token device, Smart Card, Smart Media, Compact Flash, Smart Digital Media, DVD, Compact Disk, Multiprotocol Label Switching Standard (MPLS), Lightweight Directory Access Protocol (LDAP), Electronic Data Exchange (EDI), Internet Relay Chat (IRC), Cyclic Redundancy Checksum (CRC), Terminal Identifier (TID), as well as other relevant terms throughout the present disclosure, are to be understood consistently with their typical meanings established in the IT industries, electronic or online commerce, and particularly the network security and any related fields.

[0082] A network, as used herein, refers to any group of networking enabled devices interconnected via fiber optic cables or any other medium that is suitable for transmitting digital and/or non-digital information over a distance. A network may be an open network, such as the Internet, or a closed network, such as an enterprise intranet system. The network-enabled device, also referred to as network-connecting device, connecting device, or device, may be a, computer, a digital mobile phone, a PDA, a digital camera, a digital audio-video communicator, or any other devices that may be connected to a network via wire or wireless means. The network-connecting device may be a client or a server as referred to in this disclosure. In one embodiment, the connecting device may also refer to a host computer for a mobile client such as an intelligent data carrier. See the discussion infra on the client as an intelligent data carrier. In certain embodiments, a network may include one or more such clients and one or more such servers. In other embodiments, a network also includes one or more injectors, discussed infra in the detailed description of this disclosure.

[0083] As used herein, a Virtual Private Network (VPN) applies security procedures and tunneling to achieve privacy in network transactions while sharing public network infrastructure such as the Internet. Tunneling refers to the transmission of the protected data—such as those proprietary to a business or private to an individual—through a public network. The routing nodes in the public network are unaware that the transmission is part of a private network. Tunneling is typically accomplished by encapsulating the private network data and protocol information within the public network transmission units so that the private network protocol information appears to the public network as data. Tunneling enables using the Internet to transmit data on behalf of a private network. Numerous tunneling protocols have been developed, among which some examples are the Point-to-Point Tunneling Protocol (PPTP), developed by Microsoft and several other companies; generic routing encapsulation (GRE), developed by Cisco Systems; and the Layer Two Tunneling Protocol (L2TP). Tunneling, and the use of a VPN, does not substitute for encryption in ensuring secure data transmission. Encryption may be used in connection to and within the VPN.

[0084] Biometrics, as used in the present disclosure, refers to the individual characteristics—physical or behavioral—that are used to establish user identities in order to authenticate a user and properly authorize or deny access to a protected institution network or a protected source of information. Physical biometrics comprises voice recognition (i.e., speaker verification), fingerprints, handprints, blood vessel patterns, DNA tests, retinal or iris scan, and face recognition, among other things. Performance biometrics comprises habits or patterns of individual behaviors.

[0085] Data, as used herein, refers to any information capable of being transmitted over a network. Data is used interchangeably in various embodiments with the term digital information or information. The content data refers to any data that is designated for transmission by a user over a network. For example, in a financial institution or a bank, the customer account information constitutes one type of content data that may be transmitted among one or more clients and servers used or operated by various authorized account managers and system administrators. The account payment information would be one type of content data in the context of EDI transactions. Another example of a different kind of content data is the inventory information on raw materials and finished products in a manufacturing facility; this data is often transmitted among clients and servers throughout such a facility for access by production engineers and business planning personnel. The transaction data—also referred to as the connection data—means, in the present disclosure, any information that depicts the state of the network connection between a client and a server and the data transmission between them. It comprises, e.g., the information on user authorization state and method of authentication, among other things.

[0086] Data Compression and encryption, as referred to in this disclosure, may be implemented according to the typical industry practice. A variety of specifications and algorithms for compression/decompression and encryption/decryption are well known in the art and many related products are publicly or commercially available; they may be utilized in the methods and systems according to the various embodiments of this disclosure.

[0087] A user interface, as used herein, refers to any kind of computer applications or programs that enables interactions with a user. A user interface may be a graphical user interface (GUI), such as a browser. Examples of such a browser include Microsoft Internet Explorer™ and Netscape Navigator™. A user interface also may be a simple command line interface in alternative embodiments. A user interface according to this disclosure may also include plug-in tools that extend the existing applications and support interaction with standard desktop applications such as Microsoft Office, ERP systems etc. Further, a user interface in certain embodiments may also refer to any point of information entry, such as, inter alia, a keypad, a PDA, a microphone, or any type of biometric input unit.

[0088] A radar connector, as used herein, refers to a module that is capable of monitoring and controlling the network connections. It may be connected to a client, a server, or an injector, according to the various embodiments of this disclosure. The radar connector in certain embodiments is further capable of detecting the lost connection and initializing contact to the server thereby reestablishing the connection. On the client side, it first looks to connect to a port; thereafter, it continuously monitors the network connections and when a loss of connection is detected, it attempts to reestablish the connection by calling the server. On the server side, the radar connector may remain active at all times, monitoring the state of connections between various clients and the network server.

[0089] Pervasive computing, as used in this disclosure, refers to the increased and widespread use of network computers or other digital devices in people's business and personal lives. The rapid growth of digital and web-enabled electronics (e.g., digital mobile phone, digital TVs, PDAs, etc.) and the omnipresence of the broadband Internet connections manifest the era of pervasive computing.

[0090] Pervasive security, as used in the various embodiments, refers to a network security platform that delivers security on demand, using one or more network connecting devices. Connected to the pervasive security, the user centric security according to certain embodiments of this disclosure refers to that the system secures the one or more users instead of one or more devices employed by the users to connect to the network server. The pervasive and user-centric security may be instituted in one embodiment using the systems and methods of this disclosure anywhere, anytime, using any network device.

[0091] Datagram is defined as “a self-contained, independent entity of data carrying sufficient information to be routed from the source to the destination computer without reliance on earlier exchanges between this source and destination computer and the transporting network.” See, Encyclopedia of Technology Terms, Whatis.Com, QUE, November 2001. Datagram and packet can be used interchangeably. Id.

[0092] The term “intelligent data carrier” is used interchangeably with the term “client” in various embodiments of this disclosure. An intelligent data carrier comprises at least (i) one memory, capable of storing digital information, (ii) one input-output apparatus, capable of inputting and outputting digital information, and (iii) one processor, capable of processing the digital information stored in the memory and connecting to a computer device thereby transmitting the digital information via the input-output apparatus. An intelligent data carrier is capable of establishing the identity of a user through an authentication and encryption scheme, according to certain embodiments of this disclosure. In one embodiment, the intelligent data carrier is mobile. The intelligent data carrier may be a USB key, a firewire device, Smart Card, Compact Disk, DVD, Smart Media, Compact Flash, PDA, Smart Digital Media, or a token device. A token device may be a software dongle such as a Serial Port dongle or a Parallel Port dongle, any onetime password generation device, or system access device. Other digital media reader may be implemented as intelligent data carriers according to this disclosure. They are capable of connecting to a variety of host devices through various ports or drives and in different manner. The intelligent data carrier bears all the data and faculties for establishing secure network connections on behalf of the user and launching applications on-demand, once the user is properly authenticated by the server. See infra the detailed discussion on a client as an intelligent data carrier.

A Client-Server-Injector Network Communication System

[0093] A client-server communication system is provided in one embodiment of this disclosure that includes one or more clients and one or more servers. Each client is an intelligent data carrier capable of supporting an authentication and encryption scheme for secure connections to a network server. See infra the discussion on a client as an intelligent data carrier. The system enables user centric security, as it authenticates and protects each user directly through an intelligent data carrier. No matter what kind of connecting devices or local host computers are used, a user may dock the intelligent data carrier to the host and launch an authentication session to connect to the target server. Thus, the focus point of access safeguard is not at the connecting device or local host machine but, rather, it is directly on the individual user who is issued an intelligent data carrier. The intelligent data carrier may be mobile; such mobility enhances the pervasiveness in the security solution afforded by the system. It is security on demand, using any connecting device or local host machine.

[0094] In another embodiment, an injector is included in the client-server communication system. The client-server-injector system enables convenient integration with existing network infrastructures and facilitates the overall security of data transmission and application sharing. See infra the detailed discussion on the injector connecting with the server and client. One or more clients, one or more servers, and one or more injectors may be instituted in such a network communication system. Each injector links to and communicates with one or more servers. Each server connects to and serves one or more clients. The multiple servers in the system may communicate with each other in managing data flows in the entire network.

[0095] FIG. 1 outlines the connections among an injector, a client, and a pair of peer servers. Each server, client, and injector has a radar connector, interfacing with the network. The radar connector constantly monitors the state of network connections. When a loss of connection is detected, the radar connector on the client side makes one or more attempts to reestablish the connection by calling the server. Since the client has recorded—and hence remembers—the parameters of the connection state for the most recent connection(s), the lost connection may be quickly restored with the desired accuracy. Consequently, the integrity of data transmission may be protected and the rate of failure may be reduced.

[0096] In addition to the radar connector, certain other modules and processes are common among the client, injector, and two peer servers depicted in FIG. 1. The permissions manager assigns and manages user permissions. The service facilitator ensures that specific applications or services are provided to the user as requested. A datagram parser engine is included in each client, server, and injector, as shown in FIG. 1. The parser engine constitutes the dynamic datagram switch of the system. See also, FIGS. 6, 7, and 8, a dynamic datagram switch and/or a frame parser is included in the client, server, and injector. The datagram switch operates in conjunction with the radar connector on both the client side and the server side to process multiple instances of datagram transmissions. The detailed discussion on the dynamic datagram switch is set forth below. The encryption engine processes encryption and decryption of the data transactions over the network. In the client, server, and injector system, the encryption engine is one level behind the radar connector that interfaces with the network. The parsing engine and the service facilitator implemented in both the servers and the injector enable the overall system to support a multitude of network services and applications as well as transmission of various types of data. Further details on these and other modules and processes are discussed in the separate sections below for the client, server, and injector.

Client as an Intelligent Data Carrier

[0097] A client is any computer or digital device that is capable of connecting to a server computer or digital device through a network, wired or wireless. A client may also refer to computer software that calls and connects to a server. A client may take the form of an intelligent data carrier according to this disclosure. A client or intelligent data carrier may be formed by executing a software, firmware, or flash memory on a device that provides or connects to a user interface. The user interface allows a user to monitor the network transactions and control the data transmission once the user connects to a network server through the intelligent data carrier. For example, the user interface provides a login form for the user to login the network, which may require entries in a textual or object format. The user interface also allows a user to issue instructions for controlling the network transaction and data transmission.

[0098] An intelligent data carrier may be mobile according to one embodiment of this disclosure. In various embodiments, an intelligent data carrier may be a USB key, Compact Flash, Smart Media, Compact Disk, DVD, PDA, firewire device, token device such as Serial Port dongle or Parallel Port dongle, or any other alternative digital device or medium reader. Three main components may be included in an intelligent data carrier: a memory that is capable of storing digital information, an input-output apparatus that is capable of inputting and outputting digital information, and a processor that is capable of processing the digital information stored in the memory and connecting to a computer device—e.g., a network server—thereby transmitting the digital information via the input-output apparatus. The memory or the digital data storage of the intelligent data carrier may be any form of computer readable media, including, for example, CDs, floppy disks, DVDs, Erasable Programmable Read-Only Memory (EPROM), flash memories (Compact Flash, Smart Media, USB key), among other things. The input-output apparatus of the intelligent data carrier is capable of connecting to a host computer device via any kind of IO connection or port, including, for example, mouse ports, keyboard ports, serial ports (USB ports or ASB ports), parallel ports, infrared ports, and firewire connections (IEEE 1394), among other things. The IO connection may be wired or wireless in various embodiments. For example, in one embodiment, short-range wireless connection may be established between the intelligent data carrier and a host device pursuant to Bluetooth specification. See, www.bluetooth.org. The processor of the intelligent data carrier comprises an Application-Specific Integrated Circuit (ASIC) in one embodiment. The processor supports and controls the execution of the preloaded applications on the intelligent data carrier as well as the applications installed on the host computer device or those made available from the remote server. See infra for detailed discussions on application delivery.

[0099] The intelligent data carrier according to this disclosure is capable of establishing the identities of a user through an authentication and encryption scheme. The intelligent data carrier locates the server and presents itself to the server by initiating the authentication process. See infra the discussions on authentication and encryption. In the secure network system of this disclosure, each user is issued an intelligent data carrier that allows the user to connect to the network server and access the data and applications thereon. A user may use the intelligent data carrier to connect, disconnect, and reconnect to the server at will and as needed. The connection may be made from any network host device and at any time in one embodiment. The data access is private and secure with regard to each user. See infra the discussion on Encrypted Virtual File System. The intelligent data carrier of this disclosure thus affords great mobility and enhanced, user-centric security to network client-server communication systems.

[0100] Applications may be delivered to an intended user through an intelligent data carrier in a secure, controlled manner. In one embodiment, certain licensed applications may be preloaded to the intelligent data carrier that is issued to an authorized user, one who is registered with the server. The user may run the application off the intelligent data carrier upon proper authentication by the server, irrespective of what local host the intelligent data carrier is docked to. That is, for example, the user may insert a USB key to a computer—which is connected to the Internet—at one location and launch the application off the USB key once successfully connected to the server-also sitting on the Internet. The user may close the application and save the file onto the server or the USB key. The files are stored in an Encrypted Virtual File System (EVFS) connected to the network server. See infra the discussions on EVFS. When at another location, the user may launch the application—upon proper authentication by the server—off the USB key using a different computer host and continue working on the same file. Such secure, mobile, and user-centric connectivity between the intelligent data carrier and the network server thus provides a paradigm for managing and controlling not only data access but also application delivery.

[0101] In one embodiment, the intelligent data carrier (IDC) delivers standalone applications or operating systems. The user is issued IDC with applications and/or an operating system on the IDC that is read only and copy protected. The user may use the IDC to boot a host system that does not have an operating system or storage device installed thereon and to access server-based applications and preloaded applications on the IDC.

[0102] In another embodiment, the IDC is used to deliver applications and media content. The user is provided with an IDC containing the application that is copy protected and read only as well as a unique serial number to permit the initial installation of the application. When the install is completed, the IDC requests the system name, MAC number, processor serial number, or any other static system based information, so as to create an anti-copying code that is then stored on the IDC in the form of an encrypted code hidden from the user. This code ensures that the application is only installed on the original host device.

[0103] In yet another embodiment, the IDC is used for media specific distribution.

[0104] Each user is issued an IDC that works with one or more specific decoders authorizing access to specific digital media sources, such as DVD, CD, or MP3 data files. Such access and usage may be tracked by the server through the IDC.

[0105] The application delivery paradigm according to this disclosure may be especially useful for large software applications and valuable proprietary IT tools, such as specialized database applications, data analysis tools, and various Customer Relation Management (CRM) and Enterprise Resource Planning (ERP) packages, among other things. The controlled delivery directed to the individual user, coupled with the rigorous authentication and encryption safeguard as well as the centralized, yet user-friendly management of data and files makes this paradigm a practical rivalry to the existing software licensing schemes—e.g., enterprise licenses and floating licenses—for computer software applications.

[0106] Referring to FIG. 5, an intelligent data carrier implements a number of modules and processes according to one embodiment of this disclosure. For example, an Application Boot Loader allows System Integrators (SIs) and Original Equipment Manufacturers (OEMs) to create custom boot calls to applications that are stored on the intelligent data carrier or applications installed on the host computer. The Boot Loader may call a config file, a SYS file, or an executable file, among other things, to boot the application. The memory of the intelligent data carrier may be partitioned—by the SIs or OEMs—into user data storage, application data storage, and administrative config partition. The user data storage is read-and-write enabled. The application data storage is read-only. And the administrative config partition is hidden. This information is stored on the intelligent data carrier in such a way that it is not in the user's view nor directly accessible by the user. Additional modules are also included, including an On Device Authentication Client module for user authentication, a radar connector for monitoring and control of network connections, and an Encryption module, among other things.

[0107] FIG. 6 provides another illustration of a client according to one embodiment of this disclosure. Various modules and components are also depicted, as are the processes involved. For example, depending on the connection with the server, the client supports different type of communications, including, for example, messaging, streaming, and other custom communications. A datagram parser (service parser) is employed, corresponding to that of the datagram switch in the network server according to one embodiment. See infra the discussion on the server with a dynamic datagram switch. SKE and encryption is implemented in the client. See infra the discussion on authentication and encryption. Randomization is utilized in connection to the authentication and encryption scheme. See infra the discussion on randomization in the creation and analysis of data objects. Additionally, a radar connector is included as part of the client, linking the client to the server. The radar connector monitors the connections between the client and the server. The connection may be through a public network such as the Internet. It can also be established within a private, enterprise network, especially one that involves distributive computing.

Server with a Dynamic Datagram Switch

[0108] A server can be any computer or digital device that sits on an open—e.g., the Internet—or closed—e.g., an institutional environment—network that is capable of connecting to a client, authenticating the client, and providing data and application access to the client. The network may be wired, or in part or in whole wireless. The server defines the permissions or rights of the various clients or users in the system. The permissions may be compiled and issued based on the authenticated user identities—e.g., according to biometrics measurements—and the physical location—e.g., local host names, or the time of day, or any other detectable parameters. Once the client is successfully authenticated, the server accepts the connection from the client and allows access to the data that is owned by the user or that the user is authorized to access. The data files are in an EVFS that provides secure, private access to each user. See infra the discussion on EVFS. In other embodiments, the server may deliver applications to the authorized user once the connection is established, as discussed supra.

[0109] As shown in FIG. 7, a server according to one embodiment of this disclosure includes a set of modules and components, some of which are analogous to that included in the client, shown in FIG. 6. For example, SKE and encryption are implemented in the server. Randomization is also utilized in connection with the authentication and encryption scheme. As discussed supra, an EVFS is linked to the server, providing each client a virtual private file system for data access and storage. The EVFS links to the server via an EVFS interface. See infra for detailed discussions. Further, a radar connector is included as part of the server, interfacing with the radar connector at the client side. The network connection between the client and server with a radar connector on each side enables effective monitoring and control of the network connection. The radar connector may also detect lost connections and reestablish the connection when needed, according to another embodiment of this disclosure.

[0110] In certain embodiments, the data transmission between the client and the server is effectuated by a dynamic datagram switch based on a datagram schema. See infra Example 1. All the data—whether he content data or transaction data—destined for transport through the server is formatted into a datagram. Each datagram is carried within a TCP packet according to one embodiment. In alternative embodiments, other network protocols such as UDP, HTTP, and HTTPS may be used. Multiple datagram types are defined in the datagram schema according to one embodiment of this disclosure. A major datagram type may have a plurality of minor or sub types. A minor datagram type may further comprise lower level datagram subtypes in alternative embodiments. A set of methods and functions may be defined for each datagram type or subtype. Each datagram type or subtype is capable of supporting one or more specific applications and carrying one or more specific kinds of data. The various types may require different and specific privileges and/or permissions. Datagrams are processed in the server by the dynamic datagram switch. The dynamic datagram switch is capable of creating, allocating, and processing datagrams in real time. Datagram allocation and de-allocation are performed dynamically. In one embodiment, the same memory space is used when one datagram is de-allocated while another is allocated. Memory pointers are used for two or more datagrams. When one datagram is in service, its pointer points to the allocated memory. The use of memory pointer provides a high level of efficiency and speed in deploying multitudes of network applications and supporting network transmission of manifold content data, in service to one or more users. The switch of datagrams may be implemented, in certain embodiments, within a network connection through one port; and in alternative embodiments, the switch of datagrams maybe implemented in connection with multiple ports.

[0111] The dynamic datagram switch has a datagram parser engine with a parser, which filters the datagrams based on their major and minor types. For example, data are first read from the socket and are appended to the in-queue for that socket. The parser engine then checks to see whether that socket has a complete datagram in the queue. If not, it goes back to sleep and waits for the next packet to arrive at the socket. If yes, it removes the completed datagram from the socket's in-queue and sends it to a decryption and parsing unit to be decrypted and parsed. The parser engine then asks whether the datagram passes decryption and validation. If no, it checks to see whether the datagram show any signs of alternation or injection. If no, the datagram is discarded. If yes, the datagram is discarded and the user who sends the datagram is disconnected. If the datagram is successfully decrypted and validated, the parser engine then tries to determine the intended recipient of the datagram. If it is intended for another connected server, the datagram is then forwarded to the peer parser engine on that connected server. If it is targeted for the local server, the datagram is then passed on to the local parser. If parser then checks whether the sender has the permission to send that particular type of datagram. This is performed using the object classifier in one embodiment. See infra Example 2 and the discussion on authentication and encryption. If no, the datagram is discarded and a log file is created. If yes, the parser further checks to see whether the sender has permissions to send the datagram and whether the recipient has the permission to receive the datagram. If no, and if the negative permission is permanent, then the datagram is discarded and a log file is created. If no, but if the negative permission is temporary, then the datagram may be stored for later retrieval and processing. If the sender has permissions to send the datagram and the recipient has the permission to receive the datagram, the parser then proceeds to determine the datagram type. FIG. 3 shows the relevant processes and steps in a parser according to one embodiment. Each datagram type has a corresponding processing engineer, such as instant messaging engine, broadcast engine, connection proxy engine, etc. Peering engine refers to the peer parser engine residing at another connected server. User logons and logoffs are broadcasted to all peers. User access to each peer servers may be coordinated and managed as desired. For example, an existing connection the user has to a server may be terminated when the user is successfully authenticated by and connected to a peer server that grants higher level of access privilege. The permission engine manages and records the permissions for all the users. Other modules or processes may be included in other embodiments that provide various functionalities as needed, including, for example, the VPN tunneling engine.

[0112] In one embodiment, the server may dynamically process a matrix of datagram types. The matrix comprises a first predetermined number (e.g., 256) of major datagram types—each of which having a second predetermined number (e.g., 256) minor datagram types. In alternative embodiments, the parser is capable of parsing a matrix of datagram types that has more than two dimensionalities or levels. The parsing may be implemented, therefore, according to the datagram types and fields and the layers thereof. The appropriate functions or methods may be executed for each datagram once the datagram is properly parsed out, according to the generic layout of the datagram. FIG. 4 provides a generic layout of the datagrams in one embodiment of this disclosure. The datagram layout includes the payload and the header fields such as the major datagram type, the minor datagram type or subtype, the datagram length, and the datagram checksum. The payload carries the content data in transmission. Additional header fields may be included for different datagram types.

[0113] Referring to Example 1 infra, in one embodiment, the major datagram types include, among other things: the server messages and connection control datagram, capable of authenticating and controlling user connections; the content datagram, capable of managing the transmission of the content data; the broadcast datagram, capable of managing the real-time point-to-point, point-to-multipoint, and multipoint-to-multipoint data transmission; and the connection proxy datagram, capable of passing proxy data between the network server and the intelligent data carrier. The server messages and connection control datagram includes minor datagram types such as: the authentication request datagram, capable of initiating an authentication request; the authentication reply datagram, capable of sending a response upon a request of authentication; and the authentication result datagram, capable of sending the result of an authentication session. The content datagram includes minor datagram types such as: the normal content datagram, capable of transmitting the content data; the remote logging datagram, capable of communicating with the network server and establishing a login session; and the remote data collector datagram, capable of transmitting data from a remote connection; the content approval request datagram, capable of requesting verification of the content data transmitted; and the content approval reply datagram, capable of responding to a request of verification of the content data transmitted. The connection proxy datagram includes minor datagram types such as: proxy data to server, capable of passing proxy data to the network server from the intelligent data carrier; and proxy data from server, capable of passing the proxy data from the network server to the intelligent data carrier. Another example of major datagram type is the instant message type. It includes minor datagram types such as the file transmission type, the audio-video transmission type, the instant mail message type, and the remote data collection type.

Injector Connecting with Server and Client

[0114] In one embodiment, the secure network system of this disclosure includes an injector, which is capable of connecting the server to an existing network infrastructure and applications. It can be software or firmware that provides network connectivity. The injector converts physical connection data into logical network resources. It allows convenient integration with the existing networks and reduces the need to modify the existing IT infrastructures.

[0115] Referring to FIG. 8, an injector in one embodiment includes similar modules and processes as that in a client (FIG. 6) or a server (FIG. 7). For example, SKE and encryption is implemented in the injector. Randomization is also utilized in connection to the authentication and encryption scheme. Like the server, the injector is also linked to an EVFS, providing the users a virtual private file system for accessing data from the other connecting networks. The EVFS links to the injector via a Virtual File System (VFS) interface. The injector, like the client and the server, also supports different types of communications, including, for example, messaging, streaming, and other custom communications.

[0116] Moreover, the injector employs a dynamic datagram switch. The datagram switch includes a datagram parser (service parser or frame parser), corresponding to the datagram switch in the network server. A radar connector is also included as part of the injector, interfacing with the radar connector at the server side. The radar connector monitors and controls the network connection between the injector and the server. The radar connector may also detect lost connections and reestablish the connection when needed, according to another embodiment.

Authentication and Encryption

[0117] In various embodiments of this disclosure, the secure network system may employ a variety of authentication and encryption methods, including, for example, an encrypted or non-encrypted ASCII string, a single classifier model, or a super classifier model. Symmetrical and asymmetrical multi-cipher encryption may be used. Encryption may be altered over time by output feedback, cipher feedback, cipher block chaining, cipher forwarding, or any other method that alters the cipher and/or key in a manner that both the encryption or decryption engine can predict or reproduce. In certain embodiments, Secure Key Exchange (SKE) is employed. SKE is based on the generation of random key pairs that are only used once and thereafter discarded. SKE ensures that no keys are stored on any device or system except the public-private key pair owned or controlled by the server. It differs from Public Key Infrastructure (PKI), which requires a public key storage system to serve multiple users. The omission of an intermediate public key storage system—a typical target for network hackers—allows for enhanced network security.

[0118] The SKE module in the secure network system according to certain embodiments use various public key systems, such as the Commercial off the Shelf (COTS) systems. In one embodiment, Advanced Encryption Standard (AES) Rijndael is used. See, Federal Information, Processing Standards Publication 197, Announcing the Advanced Encryption Standard, November 2001, (http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf). See also, http://csrc.nist.gov/CryptoToolkit/aes/; http://csrc.nist.gov/CryptoToolkit/aes/rijndael/; and http://csrc.nist.gov/CryptoToolkit/aes/rijndael/rijndael-ip.pdf. In another embodiment, a 163 bit Elliptic Curve Cryptography (ECC) key may be used. The ECC technology is known. See, e.g., Tatsuaki Okamoto et al., PSEC: Provably Secure Elliptic Curve Encryption Scheme, (Submission to P1363a), March 1999 (http://grouper.ieee.org/groups/1363/P1363a/contributions/psec.pdf). See also, http://world.std.com/˜dpj/elliptic.html; http://csrc.nist.gov/cryptval/dss/fr000215.html. And, in alternative embodiments, various encryption methods may be employed on a random base and in combination. For example, the alternative ciphers include, among others: Gost, Cast128, Cast256, Blowfish, IDEA, Mars, Misty 1, RC2, RC4, RC5, FROG, SAFER, SAFER-K40, SAFER-SK40, SAFER-K64, SAFER-SK64, SAFER-K128, SAFER-SK128, TEA, TEAN, Skipjack, SCOP, Q128, 3Way, Shark, Square, Single DES, Double DES, Triple DES, Double DES16, Triple DES 16, TripleDES24, DESX, NewDES, Diamond II, Diamond II Lite and Sapphire II. The alternative hashes include, among others: MD4, SHA, SHA-2, RipeMD128, RipeMD160, RipeMD256, RipeMD320, Haval (128, 160, 192, 224 and 256 bits) with Rounds, Snefru, Square, Tiger, and Sapphire II (128, 160, 192, 224, 256, 288 and 320 bits).

[0119] According to various embodiments, the authentication may be based on data at the event level—an authenticating event such as a mouse click, a keystroke, a touch on a screen, or an utterance—or data generated pre- or post-event, or any combination thereof. The use of a super classifier involves three aspects, the classification (see infra Appendix 1), analysis (see infra Appendix 2), and decision (see infra Appendix 3). A super classifier function is a feature extraction of know or unknown vector (input) data, which can be binary or non-binary. See, e.g., appendix 3. In one embodiment, an object vector based super classifier is used. See infra, Example 2. Randomization is applied in the super classifier based object analysis according to one embodiment of this disclosure as discussed in the next section.

[0120] Authentication is performed each time when a client or an intelligent data carrier attempts to connect to a network server. According to one embodiment, an authentication and encryption scheme is enabled in the intelligent data carrier. A series of steps constitute such scheme. First, the user sends, via the client or the intelligent data carrier a request to the network server, requesting to be authenticated. The initiation of an authentication session is thus from the client or the intelligent data carrier. Second, the server sends to the intelligent data carrier a list or set of authentication methods that are available, from which the user selects one through an event—e.g., a click of mouse, a touch on a screen, an utterance, a keystroke, or any other suitable notification means. Input from a digitizer such as a camera or biometric device would be another example of suitable notification means. Third, based on the selected authentication method, the server sends the intelligent data carrier a demand for authentication data. The demand may be for a password, true random or pseudo-random in various embodiments. The pseudo random password is generated based on a mathematically pre-calculated list, and a true random password is generated by sampling and processing a source of entropy outside of the system. Fifth, the server transforms the authentication data received from the intelligent data carrier into one or more data objects or object vectors. Sixth, the server performs the object analysis on the data object, using one or more classifiers or a super classifier. A super classifier based on biometrics measurements may be used. And finally, the result of the analysis or the decision based on the classifier is sent from the server to the intelligent data carrier, which either affirms the proper authentication of the user thereby permitting the connection of the intelligent data carrier to the server or declares that the authentication attempt failed.

Randomization in the Creation and Analysis of Data Vector Objects

[0121] Randomization techniques are well known in the field of theoretical and applied mathematics. They are often applied in the decision-making processes where no apparent common denominator exists. The use of randomization is facilitated by the vast computing power available today. Randomization typically involves the use of a seed. Random number generators generate pools of random numbers based on the supply of one or more seeds. Depending on the characteristics of the seed, randomization may be classified into pseudo random or true random. Most random generators are pseudo-random number generators. They are based on a mathematical pre-calculated list, one that can be compromised. By contrast, true random numbers are usually generated by sampling and processing a source of entropy outside the computer systems or network involved. One must figure out the source of the entropy and how the entropy generated the seed in order to break a true randomizer.

[0122] Randomization may be used in computer or network security. The current application of randomization in data security is largely in a static manner. For example, a random number may be generated by a client, a server, or a like unit, and subsequently passed onto a computer by the user. If the number matches a number within the random number “frame” allowed by the system specific random generator, the user will be granted access. This is similar to a Public Key Infrastructure (PKI) where two secretly generated keys are matched and validated at a system shared validation point. One problem with this paradigm is that the shared validation point may be compromised relatively easily: At the system shared validation point is a random generator that contains a frame of numbers (or any desired output combination such as alpha digits) based on a given seed. Although the random generator seems to generate an infinite number of random numbers, the total number of random numbers to be generated is pre-determined once the generator is created (seeded). That is, what is random is only the order in which the random numbers are generated; such randomization is static. Therefore, each random number is theoretically predictable.

[0123] Randomization according to certain embodiment of this disclosure is utilized in a non-static manner. Randomization is implemented in data objects through one or more classifiers or super classifiers. See infra Example 2. A true random generator is seeded to provide random numbers for the analysis of data vector objects. In one embodiment, the object analysis involves a number of steps in which true random numbers are used: First, the server generates a true random number based on the seed. Second, the client receives the random number, which becomes a private key 1 (PK1) of the user. Third, at the event level, the client executes the random number by a suitable means, such as a click of mouse, a touch on a screen, a keystroke, or an utterance. The execution of the event may be based on a predetermined recording time. Fourth, the event level act transforms the original PK1 into a data object PK1, which is a different data image (such as a phonetic image) compared to the original PK1. The data object is then sent to the server. In some embodiments, multiple data objects (or an object encompassing multiple data images) are derived as more than one data images may be obtained from multiple such events. These data objects may be used for the subsequent classification and decision analysis. Fifth, N classifiers are selected based on the features extracted from the data objects (see also, FIG. 2 and Example 2 infra), either randomly or via a predetermined rule. And, respectively, a random or superior sum may be calculated from the N classifiers. Sixth, the data object PK1, at the server, uses a seed to generate another true random number, which becomes the private key 2 (PK2). PK2 becomes the rule set for the object analysis and the object based decision-making. See infra, Examples 3, 4, and 5. The classifier models might differ in the various embodiments, depending on the type of object analyses required. And finally, the resulting decision from the analysis is posted to the server and sent to the client, signifying a successful or failed authentication session.

[0124] Thus, two separate private keys are generated based on true random values. These two keys do not contain any information based on the initial random number, because the data object transforms the number into a value or a data image, based on entropy outside the computer at the event level. It is therefore outside the environment of the randomizer or random generator and becomes non-static. Since what is used for the randomization-based object transformation is itself a key, it becomes possible to match the two unknowns (private keys) and make them known. In alternative embodiments, more than two private keys may be similarly generated and used. Moreover, any numbers of private keys may be generated by the object in the classifier, and thereby makes the number of private keys unknown.

[0125] According to this embodiment, randomization is implemented for both (i) challenging to the authenticator (i.e., the user or the client) based on a true random generator and (ii) selecting the object analysis to be performed and performing the selected analysis.

[0126] A typical pre-programmed random generator may take the following form:

[0127] $y_{i+1}=\frac{1}{N}\sum _{j=1}^N\frac{\left(a_j{x}_{i,j}+c_j\right)\mathrm{mod}{m}_j}{m_j}$
See, e.g., Numerical Recipes, W.H. Press et al., Cambridge University Press. Whether simple linear congruential generators or improved generators are used, multiple random generators may be employed—thereby creating a combinatorial problem—so as to prevent the calculation of the seed from, for example, observing a number of random numbers generated in sequence. In certain embodiments, the least significant digits are truncated in the sequence, in order to minimize the revelation of potential hints. In other embodiments, besides the seed, the generator specific constants a, c and m are also provided according to the above formula. When the constants are chosen using some noise input, this approach will result in more robust randomizers. It is noted that the constants a and m may not be chosen arbitrarily; a table with a large number of possible values may be created. In still other embodiments, a number of pre-chosen random generators may be used in connection with N independent seeds. A simple sum may be used as follows:

[0128] $y_{i+1}=\frac{1}{N}\sum _{j=1}^N\frac{\left(a_j{x}_{i,j}+c_j\right)\mathrm{mod}{m}_j}{m_j}$

[0129] An example of a useful algorithm for combining two linear congruential generators with a combined period of about 2.3×10¹⁸ is the ran2 described in Numerical Recipes. The algorithm may be modified using two independent seeds. It may be further modified using 3 or N generators. According to certain embodiments, at least one seed is obtained from an indeterministic source, which a perpetrator does not have easy access to. The indeterministic source may be anything outside of the randomizer and beyond the network system of interest, such as, e.g., the use of an external device, external occurrence, a third party, and bits derived from the recent history of the computer, among other things.

[0130] When one specific classifier is used in the analysis of an object-based vector, the predictability may be relatively high such that it is easy for a perpetrator to solve the classifier and the seed. In certain embodiments, an ensemble of classifiers—i.e., multi classifiers or super classifier—are used, where lower predictability may be achieved. The dimensionality of the feature vectors may be reduced as the variations that are not class discriminative are discarded. See infra, Appendices 1 and 2.

[0131] Therefore, true randomization according to this embodiment improves the protection on data access. The enhanced network security is achieved when randomization is utilized in the creation of a data object as well as the object analysis. Such objects are based on specific values—such as those of biometrics measurements—that are only known by the user at the event level; therefore, the improved security according to the present disclosure focus individually on the user—hence user centric—rather than the devices. The data objects transformed at the event level—based on biometrics—in a true randomized manner and analyzed in a super classifier, according to this embodiment, provides a superior foundation for establishing and verifying the user identities.

Encrypted Virtual File System (EVFS)

[0132] An EVFS according to the various embodiments of this disclosure is a per-user (or group of user), per-client virtual file system, also referred to as a file repository. It is a server-based file system or file and data storage facility, which allows the users of a network system to store files or data away from their local hosts or client carriers. An EVFS may be useful when, for example, the storage capacity is deficient at the local host. Examples of the use and implementation of EVFSs are shown at various web sites, for example, www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/windows2000serv/deploy/confeat/nt5efs.asp; www.serverwatch.com/tutorials/article.php/2106831; and www.freebsddiary.org/encrypted-fs.php.

[0133] According to one embodiment of this disclosure, the server of the secure network system is connected to an EVFS through an EVFS interface, as shown in FIG. 7. The EVFS comprises a user directory, a per-user file database, and file storage. The user directory contains relevant information for all the users, including password, login parameters, biometric profile, physical or geographic location, online and offline status, public ECC key used to encrypt files which are stored in the EVFS. The users are the individuals who have connected to the network server through a client or an intelligent data carrier and have used or are using certain applications supported by the network. The applications may be delivered and run off the intelligent data carrier according to one embodiment of this disclosure. The applications may also run on a host computer or device to which the intelligent data carrier or the client is connected. Or, alternatively, the applications may run remotely on the server on behalf of the client.

[0134] The server uses a user directory interface—which resides in the server—to access the user directory. The file storage is a digital medium that has stored thereon the files and any other digital information of interest to the users. It may be any kind of computer memories. This is the physical location where the files or data generated from or modified by the applications the user runs off the intelligent data carrier, the host computer, or remotely on the server are stored. The file storage may be optimized for speed and convenient access according to certain embodiments of this disclosure.

[0135] The per-user file database contains user file information such as the original file name, date and time, and an encrypted representation of the encryption key used to encrypt the file. All files stored within the EVFS are assigned true random names as well as true random encryption keys; they are mixed among each other in the file storage. The data access is private and secure with respect to each user. Each individual user may only see and access those files or data that the user has ownership of or that the user has obtained the permissions to access. The level of access the user has with respect to each file or document is controlled by the server. That is, a user may only be permitted to read and edit a file, but not to move or copy it off the server—or the intelligent data carrier if the application is run off the intelligent data carrier—in certain embodiments. As such, each user virtually has a private database—hence per-user database—connected to the server.

[0136] The EVFS used in the secure network system disclosed herein provides enhanced protection to the data and application belonging to each user. In case of physical compromises, i.e., the intelligent data carrier is lost or stolen, the data stored in the EVFS will be unreadable—or not in view—to anyone but the properly authenticated user, the owner of the file who has the access to the private ECC encryption key that can unlock the file.

[0137] The provision of EVFS thus enhances the user-centric aspect of the secure network system according to the various embodiments of this disclosure. Along with encryption, authentication, and other features discussed throughout the present disclosure, the EVFS enables the secure delivery and stand-alone operation of applications through an intelligent data carrier.

[0138] The various embodiments are further described by the following examples, which are illustrative of the disclosed embodiments but do not limit the same in any manner.

[0139]

Data Gram Examples
	Instant Message types
	Instant Message
	Remote logging
	Remote data-collection
	Execute remote command
	File Transmission
	Audio-video communication
	EDI transaction
	Broadcast types
	Non real-time point-to-multipoint transmission
	Non real-time multipoint-to-multipoint transmission
	Channel-based chat (IRC style)
	Real-time point-to-point transmission
	User-to-user chat
	Audio-video conference
	Real-time point-to-multipoint transmission (broadcast)
	Audio-video broadcast
	Real-time multipoint-to-multipoint transmission
	Audio-video conference
	User Directory Types
	Query
	Update
	Content Filter Control
	Filter status
	Filter statistics
	Filter update (add/remove rules)
	Filter set
	Filter reset
Mandatory Datagram Fields
The beginning of each datagram may be laid out as follows:
Byte	Populated
size	by	Content
1	Client	Datagram major type
1	Client	Datagram minor type (sub type)
8	Server	Datagram received at server (timestamp)
4	Server	Data gram originator (Client-ID of sender)
1	Client	Signature/CRC type
n	Client	Signature/Checksum field
		(e.g., ECC Signature, MD4, MD5, SHA,
		SHA1 etc.)
Additional header fields may be appended to the aforementioned
fields, depending on the type of the datagram. The additional header
fields are typically populated by the client, and may be validated
by the server.
	Major Type 0; Server Messages And Connection Control
	The datagram type is used for the server to send messages,
	error notifications, and server-client specific information over
	the network connection.
	Subtype 1: Authentication Request
	Upon connecting to the server, the server may issue a Type 0, 1
	datagram, requiring the client to identify itself. This datagram
	informs the connected client on the authentication method required
	to be authenticated by the server.
Subtype 2: Authentication Reply
This datagram is used by the client to validate the user.
A plurality of authentication methods may be used in connection to as
these subtypes of datagrams, exemplified in the following list:
0	Username and password
1	Username and password + x.509 Client certificate
	signature (see, e.g., www.webopedia.com/TERM/X/X_509.html)
2	Username and password + ECC signature
3	Password
4	Password + x.509 Client certificate signature
5	Password + ECC signature
6	One-time password (S-Key style, predefined, ordered list
	of passwords)
7	One-time password + x.509 Client certificate signature
8	One-time password + ECC signature
9	Voicekey
10	Voicekey + x.509 Client certificate signature
11	Voicekey + ECC signature
12	Biometric hash
13	Biometric hash + x.509 certificate signature
14	Biometric hash + ECC signature
15	x.509 Client certificate (signature)
16	ECC signature
17	Content Transfer (TID)
The specific authentication method used determines the number
of additional data fields in these datagrams. The examples of
various fields when certain methods are used are shown below:
Byte Size	Description
Method 0
1	Length of UserName field
n	Usrname
1	Length of Password field
n	Password
Method 1
1	Length of UserName field
n	Username
1	Length of Password field
n	Password
n	x.509 signature on username and password fields
Method 2
1	Length of UserName field
n	Username
1	Length of Password field
n	Password
n	ECC signature on username and password fields
Method 8
1	Length of password field
n	One-time Password
n	ECC Client certificate signature
Method 11
1	Length of ECC signature
n	ECC signature on Voicekey data
n	Voicekey data
Method 12
n	Biometric hash
Method 14
1	Length of ECC signature
n	ECC signature on Biometric hash
n	Biometric hash
Method 16
n	ECC signature on Challenge
Subtype 3: Authentication Result
After the authentication request is processed, the client
will receive a 0, 3 datagram which delivers the
authentication result. This datagram has certain static fields:
Byte Size	Description
1	1 = Granted, 0 = Denied
For successful authentication, additional fields may be included:
Byte Size	Description
1	User Profile sent
4	If profile sent, indicates length of profile field
n	Mime-encoded User Profile
Subtype 4: Generic Error
If the server encounters any error during a client session,
this type of datagram captures the error. The fields included are:
	Byte Size	Description
	n	Error message
Subtype 5: Invalid Datagram
If the datagram passed to the server are considered invalid for any
reason, this type of datagram will contain the reason in its payload.
Byte Size	Description
n	Error description
Subtype 6: Improper Permissions
This datagram denotes that the network access is denied.
	Byte Size	Description
	1	Major Type
	1	Minor Type
	n	Error Message
Subtype 7: Keep-Alive
This datagram is sent by the server and/or the client to each
other in a predetermined interval, to keep the TCP connection
open. This is useful when the system is running through
various proxy-firewalls (e.g., FW-1) or running over a
dial-up connection (e.g., through a dial-up router).
This type of datagram is also useful for the server to
request that the client return a keep-alive datagram,
so as to detect whether the client is alive. The server may
disconnect when no response is received from the client.
Byte Size	Description
0, 1	0 = No answer needed; 1 = Please reply
Major Type 1: Content Datagram
Subtype 1: Normal Content Datagram
This datagram contains the actual content data to be transmitted.
Byte size	Content
4	Final Recipient-ID
n	Mime encoded data
Subtype 2: Remote Logging
This datagram contains log-entries from a
connecting device, with a “log-collector” client
installed, destined for a logging server, which may itself be
a client to another network, according to certain embodiments.
Byte Size	Content
8	Final Recipient-ID
n	Mime encoded log-data
Subtype 3: Remote Data-Collector
This datagram represents a query for a client from the
“Remote Data Collector” engine at the server, to
acquire data from the client for establishing the connection.
Byte Size	Content
8	Final Recipient-ID
1	Data gram type (query or answer)
n	Mime encoded data
Subtype 4: Content Approval Request
This datagram is used for requesting approval of the content
data transmitted, such as, signing off documents, expense
reports, and approving an electronic financial transaction.
Byte Size	Content
8	Final Recipient-ID
n	Mime encoded and XML formatted content for approval
Subtype 5: Content Approval Reply
This datagram is used to reply to Content Approval Requests (Subtype 4).
Byte Size	Content
8	Final Recipient-ID
1	Approve or reject
1	Length of signature field
n	ECC Signature on the data-field of the “Type 8”
	packet.
	Major Type 2: Broadcast Datagram
	This type of datagrams is used for a variety of conferencing
	and broad-casting applications. A number of subtypes may be
	implemented, including: non real-time point-to-multipoint
	transmission; real-time point-to-point transmission (e.g.,
	user-to-user chat, audio-video conference); real-time point-to-
	multipoint transmission (e.g., stock ticker, audio-video
	broadcast); real-time multipoint-to-multipoint transmission
	(e.g., audio-video conference).
	Major Type 3: Connection Proxy
	The Connection Proxy datagrams are used to carry raw
	connection data and send the same from an embedded or built-in
	application on the client to a network server.
	Proxy Connections are typically requested over a control-
	channel, i.e., the first connection to the server, and established
	when a new connection to the server is opened upon the request,
	which is successfully processed. A “Proxy Connection-ID” is
	then given, also used for authentication purposes. In alternative
	embodiments, the Proxy Connections may be established over the
	control-channel directly. This supports data transmission via a
	single connection. It lightens the load on the server and client
	if the proxy connection carries very little data, such as the
	case when a Terminal Server or telnet connection is used.
Connection types
Different types of connection protocols may be used.
	0:	TCP
	1:	UDP
Subtype 1: Proxy data from client
These datagrams carry the actual data for the proxy
connection, coming form the client end. One user may
have one or more proxy connection open at the same time.
A Connection ID (CID) field is included to identify each connection.
Byte Size	Description
2	Proxy ID Connection
n	Data
Subtype 2: Proxy data to client
These are the connection data coming back from the proxy connection
to the client (or the owner of the connection). No other field than
the actual data is included, since the proxy connection only sends to
and receives connection data to the owner of the connection. In order
for the client to identify which remote connection (i.e., server)
responded, the CID is included in the originator field of the datagram.
Byte Size	Description
N	Data
Type	Sender	Description
0:	Server	Remote Socket Connected.
1:	Server	Remote Socket Disconnected.
2:	Client	Disconnect Remote Socket but keep Proxy
		Connection (CID).
3:	Client	Terminate Proxy Socket Connection (complete
		teardown).
4:	Server	Proxy Socket Terminated (complete teardown).

[0140] Referring to FIG. 2, an object vector super classifier (also may be referred to as multi classifiers) is shown. More than one data object vectors exist for event level authentication. The classification decisions are derived based on superior or random sum computed from the data vector objects, including Object Vector 1, 2, and 3 in FIG. 2. Here, each object vector is connected to one or more classifiers from classifiers 1 to N. Therefore, when super classifier is used according to one embodiment of this disclosure, feature extractions may be made from the object vector and then transformed into a set of classifiers and hence, collectively, a super classifier. Such event specific transform is advantageous due to its relatively simple distributions characterizing event-based features.

[0141] Biometrics provides a useful example for user authentication using super classifiers. In certain embodiments of this disclosure, the super classifier is used for physical biometrics, which comprises voice recognition, fingerprints, handprints, blood vessel patterns, DNA tests, retinal or iris scan, and face recognition, among other things. In other embodiments, the super classifier is used for performance biometrics, which comprises habits or patterns of individual behavior.

[0142] Further, as discussed supra, randomization can be implemented, according to one embodiment of this disclosure, in an authentication session at the event level. And, transferring the vectors derived as such into objects increases the likelihood at the analysis level to identify and derive binary structures. When adding such binary structures to a super classifier, the authentication session may be measured with an advantageously high probability rate.

[0143] It is to be understood that the description, specific examples and data, while indicating exemplary embodiments, are given by way of illustration and are not intended to limit the various embodiments of the present disclosure. All references cited herein for any reason, are specifically and entirely incorporated by reference. Various changes and modifications within the present disclosure will become apparent to the skilled artisan from the description and date contained herein, and thus are considered part of the various embodiments of this disclosure.