Pre-authenticated communication within a secure computer network
AssigneeExpand Beyond Corporation
InventorDerek M. Ferguson
Life of this patent
Estimating the term…
Loading patent…
AssigneeExpand Beyond Corporation
InventorDerek M. Ferguson
Estimating the term…
A method for securing communications within a computer network that includes wireless devices is presented. The method involves the use of a middleware server, which allows ill-performing and potentially insecure communications protocols to be off-loaded onto a more powerful machine running in a more secure environment, e.g., within a company's Intranet. The method can be practiced with any symmetric encryption algorithm, and can be combined with additional security methods, such as asymmetric encryption methods.
A method for secure network communication between a client and an internal server, the method comprising the steps of:
A method for secure network communication between a client and an internal server using a middleware server, the method comprising the steps of:
A secure network communication system, comprising:
A secure network communication system, comprising:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
Backward citations are indexed for grants only.
Wherein the data content is protected, e.g. by encrypting or encapsulating the payload: wherein the sending and receiving network entities apply…
Wherein the data content is protected, e.g. by encrypting or encapsulating the payload: wherein the sending and receiving network entities apply…
Protecting confidentiality, e.g. by encryption: of the user plane, e.g. user's traffic
Security arrangements; Authentication; Protecting privacy or anonymity: authentication
Term end not estimated
The invention generally relates to the field of secure network communications. The invention relates more specifically to a method for pre-authenticating communications between a client and a middleware server in a network.
Recently, technology has been developed that allows for wireless devices, such as personal digital assistants (PDAs), cell phones, and two-way pagers, to access computer networks; computer networks are no longer physically limited to a hard-wired environment. In the past, database or systems administrators for a computer network have been forced to work within the physical confines of a secure office computer network at a company or other organization. Access to a computer network through a wireless device allows the administrator to monitor and manage the computers within the network remotely. If the administrator does not happen to be physically near in the event of a crisis, then wireless access translates directly into a quicker response to problems and less downtime. This is extremely valuable to companies, such as banks, auction houses, brokerage firms, etc., which must keep their systems running uninterrupted in order to prevent a loss of revenue.
Thus, wireless devices provide an excellent solution to many old problems in systems and database administration, but they also introduce a new problem: how can communications within a network that includes wireless devices be kept secure? For a system or database to be administrated or managed remotely, communications within the network must be kept secure at all times and in all places to avoid a leak of confidential information. The difficulties of keeping a computer network secure are increased dramatically when wireless communications are allowed between computers within the network.
The foregoing and other objects, advantages, and features of the present invention will be apparent from the following detailed description and the accompanying drawings, in which:
FIG. 1 is a block diagram of the overall structure of a secure computer network in accordance with an embodiment of the present invention;
FIG. 2 is a block diagram of a client side within a secure computer network in accordance with an embodiment of the present invention;
While the present invention is susceptible to various modifications and alternative forms, certain preferred embodiments are shown by way of example in the drawings and will be described in detail herein. It should be understood, however, that the description is not intended to limit the invention to the particular forms described; on the contrary, the description is intended to cover all modifications, alternatives, and equivalents falling within the spirit and scope of the invention defined by the appended claims.
It is relatively simple for a company to maintain a secure network (or “Intranet”) within its office if that network does not connect to any computers outside the office. In particular, most computer network security problems would be eliminated if the Intranet of a company did not connect to the Internet, or to other outside, non-secure network. Nevertheless, most businesses consider a connection to the Internet to be indispensable because of the efficiencies created in communication with customers and clients through electronic mail and the World Wide Web. Even greater efficiencies are available when network connections are extended to wireless devices, although wireless devices present a special challenge because of the limited computing resources that are available on most wireless devices. In the present invention, the middleware server, which is located within the secured company Intranet, is used to perform the most resource intensive operations of the method, effectively freeing up the computing resources of the clients to perform other functions, such as systems or database administration.
The present invention is used for securing communications within a computer network that includes a plurality of clients connected to an Intranet through a non-secure network such as the Internet. In FIG. 1, the overall structure of a secure computer network is shown schematically. In general, data transferred within the secure computer network is transmitted and received through the Internet 130 (or a VPN Tunnel 140 within the Internet 130) between a client side 120 (or a VPN client side 110) and an Intranet 160. FIG. 2 shows an embodiment of a typical client side 120, and FIG. 3 shows an embodiment of a typical VPN client side 110.