Electrical computers and digital processing systems: multicomput – Computer-to-computer protocol implementing
Reexamination Certificate
2000-11-27
2004-06-29
Meky, Moustafa M. (Department: 2157)
Electrical computers and digital processing systems: multicomput
Computer-to-computer protocol implementing
C370S466000
Reexamination Certificate
active
06757734
ABSTRACT:
TECHNICAL FIELD
The present invention relates to a method of achieving communication by means of the wireless application protocol, WAP, between a first application in a first computer unit and a second application in a second computer unit, where the first application is a Windows® application.
The first computer unit includes a WinSock TCP base provider operating beneath Winsock SPI and a TCP/UDP/IP stack operating beneath the WinSock TCP base provider.
The first application includes the functionality of communicating by means of TCP/IP via the TCP/UDP/IP stack and the WinSock TCP base provider.
The present invention also relates to a computer program product that includes a program code, and a computer readable medium carrying a computer program code, which code, when executed by a computer unit, carries out functions possessed by a module in accordance with the inventive method.
DESCRIPTION OF THE BACKGROUND ART
For the sake of simplicity, a number of acronyms have been used in this description and in the accompanying Claims. Although these acronyms are well known to the person skilled in this art, the main parts of the compound terms will be explained for the sake of clarity.
WAP—Wireless Application Protocol, TCP—Transmission Check Protocol, UDP—User Datagram Protocol, IP—Internet Protocol, TDI—Transport Driver Interface, SPI—Service Provider Interface, LSP—Layered Service Provider, SOAP—Simple Object Access Protocol, POP3—Post Office Protocol version 3, IMAP4—Internet Message Access Protocol version 4, SMTP—Simple Mail Transfer Protocol, WSP Wireless Session Protocol, URI—Universal Resource Identifier, IIS—Internet Information Server.
It has long been known to use different protocols when communicating between two or more computer units. These protocols check how information shall be packed when transmitting information, how said information shall be forwarded during transport between the computer units, and how the information received shall be interpreted.
When an application in a computer unit shall communicate via a network, contact is established between the application and the hardware that connects the computer unit to the network via special modules or software products. The operating system Windows® includes a so-called WinSock API, thereby enabling a number of sockets or connections to be established in respect of such communication. WinSock API is comprised of an interface that includes a set of defined functions that enable such sockets to be formed.
These sockets can be adapted to operate in accordance with different protocols and beneath the WinSock layer there is found a so-called SPI which operates against a number of base providers (also called base protocols and base transport service providers) and layered service providers (also called layered protocols and layered transport service providers) which are adapted to receive or send information via specific protocol stacks. Different Windows® applications are adapted to communicate via specific protocols. The base providers normally used for communication over the global network Internet, and also within local networks such as an ethernet, include the so-called WinSock TCP base provider and WinSock UDP base provider.
A base provider operates against a so-called stack via an interface designated TDI. The stack constitutes the software that operates nearest the hard connection between the computer unit and the network, in other words the network interface card. Outgoing information is packed in the stack in the format that the information shall have when it is sent over the network, whereas incoming information is unpacked in a manner which enables it to be used by the computer unit. The stack used traditionally for communication over the Internet is called the TCP/UDP/IP stack and sometimes only the TCP/IP stack or the IP stack.
Because of the progressive increase in the use of wireless mobile telephones, it is desirable that communication between a computer unit and a mobile telephone can be established for the transmission of information. WAP is a protocol that has been created to enable such communication to be achieved efficiently, despite the low bandwidth that is often available for mobile telephones.
The various Windows® applications, base providers and stacks required for such communication are not adapted for WAP communication. For instance, a Windows® application, such as an IIS or a browser in a personal computer cannot communicate directly in accordance with WAP.
It is also known to establish gateways that can translate between WAP and a more readily handled protocol, such as HTTP. These gateways, for instance, may interpret information according to WAP and repack the information according to HTTP. This enables a WAP application to communicate with, e.g., a Windows® application.
However, the constant need to communicate via a gateway that has such a function has a limiting effect. Neither is security satisfactory in the case of such communications. When encryption is used, it is necessary for the gateway to decrypt the message and repack in order to again encrypt the message. This means that decrypted, sensitive information, is available on this gateway, which is unacceptable in many instances.
The necessity of acquiring, configuring and administering a separate WAP gateway is also troublesome in many practical applications.
It is also known that WAP servers that include server programs especially written for communication in accordance with WAP can be constructed. One example in this respect is the Nokia WAP Server.
Although such WAP servers can solve the security problems associated with gateways, they have the limitation that all information must be stored directly in the WAP server and not in the web server that would otherwise have been used.
In conjunction with the present invention, it will also be mentioned that it is known to use a so-called WinSock LSP to check an established socket. An LSP is placed between the WinSock SPI and the base provider and can be allotted different functions depending on what is desired. Such functions may be to reserve a given bandwidth for an established socket or to encrypt and decrypt information transmitted via a socket.
SUMMARY OF THE PRESENT INVENTION
Technical Problems
When considering the present standpoint of techniques as described above, and with a starting point from a method according to the aforesaid technical field, it will be seen that a technical problem exists in establishing communication between a WAP application and a Windows® application when the Windows® application is not adapted for communication with a WAP application.
Another technical problem is one of providing communication where unpacking and possible decryption do not take place on an intermediate gateway.
Another technical problem resides in providing communication that is not restricted by the access to gateways in the communications path that can interpret between WAP and, e.g., HTTP.
Another technical problem is one of providing so-called end-to-end security via WAP with encrypted communication that can only be unpacked by the receiver and where both the WAP application and the Windows® application are able to authenticate each other.
With respect to a Windows® application that is adapted to communicate via a known protocol, such as HTTP, POP3, IMAP4 or SMTP, a technical problem resides in communicating via the more effective WAP protocol instead, and therewith save bandwidth.
Another technical problem is one of translating between a WAP protocol and one or more protocols belonging to one or more different Windows® applications without the assistance of WAP gateways or proxies.
In conjunction with such a method, a technical problem resides in enabling authentication to be achieved efficiently and safely through the medium of the user name and password.
Another technical problem resides in achieving communication via WAP in respect of certain applications, without preventing other applications from communicating via TCP in a normal manner.
In respect of a computer unit
Hovmark Nils Torbjörn Alexander
Laven Lars Erik Mauritz
Persson Mats Jörgen
Resenius Lars Erik
Besha Richard G.
Columbitech AB
Meky Moustafa M.
Nixon & Vanderhye P.C.
LandOfFree
Method of communication does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method of communication, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method of communication will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3364734