US20070291789A1 - Secure transmission system and method - Google Patents

Abstract

A method is provided for transmitting information from a user to a first network entity over a communications network. The user enters information into a browser executed at a user terminal. The browser generates a first message comprising the information using a first communication protocol for dispatch over the network via a network port, the first message including an identifier of the first network entity. A client executed at the user terminal receives the first message before the first message reaches the network port. The first message is wrapped in a second message of a second communication protocol used for transmitting messages between the client and a second network entity. The second message is transmitted to the second network entity over the communications network. The first message is unwrapped from the second message at the second network entity, the identifier of the first network entity translated to a network address of the first network entity and the first message is transmitted to the first network entity over the communications network.

Description

RELATED APPLICATION
• This application claims priority under 35 U.S.C. § 119 or 365 to Great Britain Application No. GB 0608752.2, filed May 3, 2006. The entire teachings of the above application are incorporated herein by reference.
FIELD OF INVENTION
• This invention relates to a secure transmission system and method, particularly but not exclusively for use in a peer-to-peer telecommunications system.
BACKGROUND OF THE INVENTION
• Peer-to-peer telecommunications systems allow the user of a device, such as a personal computer, to make telephone calls across a computer network such as the Internet. These systems are beneficial to the user as they are often of significantly lower cost than traditional telephony networks, such as fixed line or mobile networks. This may particularly be the case for long distance calls. These systems may utilise voice over internet protocol (“VoIP”) over an existing network (e.g. the Internet) to provide these services, although alternative protocols can also be used. To use a peer-to-peer telephony service, the user must install and execute client software on their device. The client software provides the VoIP connections as well as other functions such as registration and authentication.
• Some calls in a peer-to-peer telephony network may be free to the user, such as calls to other user of the same peer-to-peer system. However, other calls, such as to fixed line telephones or mobiles, may require the user to pay for the service. This therefore requires the user to provide sensitive information to the system, and hence requires a high level of security for transmissions of such data. Many peer-to-peer telephone systems operate a pre-paid account system. In these systems, the user must securely transfer sensitive information to a payment service provider in order to credit their account, and this credit is then used during the calls made. Once the credit runs out, the user must again securely transfer sensitive information to the payment service provider to credit more money into their account in order to continue using the service. In alternative systems, the user may be invoiced for the amount of calls they have made over a period of time, or may be required to make a fixed payment regardless of the number of calls made.
• In existing peer-to-peer telephony systems, the user can securely transfer sensitive data to a payment service provider by opening a web browser program and navigating to the site of the telephony system operator. From this web page the user can select links to make a payment to their account. The user can then enter credit card or other payment information into the web page. The web browser can use known secure protocols for sending the sensitive information to a payment service provider. The disadvantage of this method is that it requires the user to open a separate program on their terminal (i.e. a web browser) in order to make a payment. The user may also be required to proceed through several clicks of the webpages before reaching the correct page. Furthermore, the user must have access to the World Wide Web in order to make such a payment. However, in some circumstances the user may be blocked from accessing the web for security reasons, but would otherwise still be able to use the peer-to-peer telephony service.
• From a usability perspective, it would be desirable for the user of the telephony system to be able to make secure payments for services directly from the client software running on the user's terminal. This is because the user directly associates the client program with the telephony service. Furthermore, by allowing secure payment from within the client program, this avoids the need for the user to open other programs in order to securely transmit sensitive information for the service. For example, as discussed hereinbefore, if the user needs to transmit the sensitive information over the Internet, the user may be required to open a browser on his or her terminal and then enter the correct address of the web site through which they should pay before they can enter any payment details. This process can be prone to user error, and hence frustration on the part of the user. In addition, some users may also be suspicious of entering sensitive information on web site pages, and may have a greater level of trust in the client software provided by the operator of the telephony service. The client, however, already knows the identity of user, and this information can therefore be passed to the payment provider without having to prompt the user for an additional username and password, thereby making the payment process more straightforward for the user.
• However, any information transmitted over the network related to sensitive information must be secure. In particular, sensitive information should not be sent unencrypted. A conventional way of sending sensitive information is using a hypertext transfer protocol (“HTTP”) message format, such as HTTP secure (“HTTPS”), which encrypts data using a version of the secure socket layer (“SSL”) or transport layer security (“TLS”) protocols. However, any HTTP messages sent from the client software are easy to detect and block resulting in a failure to deliver the HTTP message and thus the encrypted data. The detection and blocking of HTTP messages may be done by third parties or firewalls. For example, some companies see the ability to access arbitrary webpages as a security risk and may therefore block HTTP. However, the telephony service provider does not pose a security risk as its content would be obtained from trusted sources. Furthermore, some companies or third parties may wish to block the peer-to-peer telephony service itself. Whilst the actual telephony traffic may be difficult to detect, the client may make specific HTTP requests to perform its tasks. These requests can therefore be detected and allow the terminal running the client to be determined, and the requests blocked.
SUMMARY OF THE INVENTION
• There is therefore a need for a secure transmission system and method in a network, such as the Internet, that enables the transmission of sensitive information from a local client to a web-based service provider.
• According to one aspect of the present invention there is provided a method of transmitting information from a user to a first network entity over a communications network, comprising the steps of: the user entering information into a browser executed at a user terminal; the browser generating a first message comprising the information using a first communication protocol for dispatch over the network via a network port, the first message including an identifier of the first network entity; receiving the first message at a client executed at the user terminal before the first message reaches the network port; wrapping the first message in a second message of a second communication protocol used for transmitting messages between the client and a second network entity; transmitting the second message to the second network entity over the communications network; and unwrapping the first message from the second message at the second network entity, translating the identifier of the first network entity to a network address of the first network entity and transmitting the first message to the first network entity over the communications network.
• In one embodiment the method further comprises the step of encrypting the information in the first message after receiving the first message at the client. In another embodiment the method further comprises the step of receiving the first message transmitted by the second network entity at the first network entity. In another embodiment the method further comprises the step of decrypting the information in the first message, after it is received at the first network entity. In another embodiment the step of encrypting is performed using an encryption key provided by the first network entity. In another embodiment the method further comprises the step of the first network entity periodically transmitting the encryption key to the second network entity.
• In another embodiment the method further comprises the steps of: transmitting a third message to the second network entity from the first network entity, responsive to receiving the first message; receiving the third message at the second network entity and, responsive thereto, fetching a webpage from a server; wrapping the webpage in a fourth message of the second communication protocol; transmitting the fourth message to the client over the communications network; unwrapping the webpage from the fourth message at the client and passing the webpage to the browser; and displaying the webpage to the user in the browser. Preferably, the third message is a redirect message.
• In another embodiment the step of wrapping the first message in a second message of a second communication protocol comprises the step of adding a header and a footer to the first message.
• Preferably, the first communication protocol is a hypertext transfer protocol. Preferably, the first network entity is a payment service provider. Preferably, the communications network is the Internet. Preferably, the second network entity is a Skype backend server. Preferably, the information is payment information.
• According to another aspect of the present invention there is provided a system for transmitting information from a user to a first network entity over a communications network, comprising: a browser executed at a user terminal, the browser comprising means for receiving information entered by the user, and means for generating a first message comprising the information using a first communication protocol for dispatch over the network via a network port, the first message including an identifier of the first network entity; a client executed at the user terminal comprising means for receiving the first message at the client before the first message reaches the network port, means for wrapping the first message in a second message of a second communication protocol used for transmitting messages between the client and a second network entity, and means for transmitting the second message to the second network entity over the communications network; and the second network entity comprising means for unwrapping the first message from the second message at the second network entity, means for translating the identifier of the first network entity to a network address of the first network entity, and means for transmitting the first message to the first network entity over the communications network.
• In one embodiment the client further comprises means for encrypting the information in the first message after receiving the first message at the client. In another embodiment the first network entity further comprises means for receiving the first message transmitted by the second network entity. In another embodiment the first network entity further comprises means for decrypting the information in the first message, after it is received at the first network entity. In another embodiment the encryption is performed using an encryption key provided by the first network entity. In another embodiment the first network entity further comprises means for periodically transmitting the encryption key to the second network entity.
• In another embodiment the first network entity further comprises means for transmitting a third message to the second network entity, responsive to receiving the first message. In another embodiment the second network entity further comprises means for receiving the third message and, responsive thereto, fetching a webpage from a server, means for wrapping the webpage in a fourth message of the second communication protocol, and means for transmitting the fourth message to the client over the communications network. In another embodiment the client further comprises means for unwrapping the webpage from the fourth message and passing the webpage to the browser. In another embodiment the browser further comprises means for displaying the webpage to the user. Preferably, the third message is a redirect message.
• In another embodiment the means for wrapping the first message in a second message of a second communication protocol comprises means for adding a header and a footer to the first message.
• Preferably, the first communication protocol is a hypertext transfer protocol. Preferably, the first network entity is a payment service provider. Preferably, the communications network is the Internet. Preferably, the second network entity is a Skype backend server. Preferably, the information is payment information.
• According to another aspect of the present invention there is provided a user terminal comprising: a browser executed at the user terminal, the browser comprising means for receiving information entered by a user, and means for generating a first message comprising the information using a first communication protocol for dispatch over a communications network via a network port, the first message including an identifier of a first network entity; and a client executed at the user terminal comprising means for receiving the first message at the client before the first message reaches the network port, means for wrapping the first message in a second message of a second communication protocol used for transmitting messages between the client and a second network entity, and means for transmitting the second message to the second network entity over the communications network.
• According to another aspect of the present invention there is provided a network entity comprising: means for unwrapping a first message of a first communication protocol from a second message of a second communication protocol transmitted by a client executed at a user terminal to the network entity over a communications network, the first message including an identifier of a further network entity; means for translating the identifier of the further network entity to a network address of the further network entity; and means for transmitting the first message to the further network entity over the communications network.
• According to another aspect of the present invention there is provided a computer program product comprising program code means which when loaded into a computer controls the computer to carry out the method above.
BRIEF DESCRIPTION OF THE DRAWINGS
• For a better understanding of the present invention and to show how the same may be put into effect, reference will now be made, by way of example, to the following drawings in which:
• FIG. 1 shows a peer-to-peer telephony system with the secure transfer of information to a payment service provider;
• FIG. 2A shows the messages exchanged in the system ofFIG. 1 for the maintenance of key information;
• FIG. 2B shows the messages exchanged in the system ofFIG. 1 for the initiation of a payment;
• FIG. 2C shows the messages exchanged in the system ofFIG. 1 for the secure transfer of payment information;
• FIG. 2D shows the messages exchanged in the system ofFIG. 1 for the transmission of a completed payment result;
• FIG. 2E shows the messages exchanged in the system ofFIG. 1 for the transmission of a uncompleted payment result;
• FIG. 3 shows the structure of the messages sent in the secure transfer of payment information;
• FIG. 4 shows a flowchart outlining the operations performed at the user terminal; and
• FIG. 5 shows the page flow for the operations performed inFIG. 2B-2D.
DETAILED DESCRIPTION OF THE INVENTION
• Reference will first be made toFIG. 1, in which is shown a peer-to-peer telephony system100 with the secure transfer of information to a payment service provider.
• A user terminal102 is shown connected to anetwork104. The user terminal may be, for example, a personal computer, personal digital assistant, a suitably enabled mobile phone or other device able to connect to thenetwork104. The user terminal102 is connected to thenetwork104 via anetwork port105, and may be via a cable (wired) connection or a wireless connection. Thenetwork104 may be a network such as the Internet.
• Auser106 of user terminal102 can make a telephone call tosecond user108 of asecond user terminal110 across thenetwork104. The user terminal is running aclient112, provided by the operator of the peer-to-peer telephony system. Theclient112 is a software program executed on a local processor in the user terminal102. To initiate the call, theuser106 can click on the contact listed for thesecond user108 displayed in theclient112, or can alternatively type in a telephone number or username for thesecond user108. Theclient112 then sets up the call to thesecond user108. The telephone call may be made using VoIP, in accordance with methods known in the art, such as disclosed in WO 2005/009019. The telephone call may comprise voice, video, instant messaging (“IM”), or a combination thereof.
• Thesecond user terminal110 may be directly connected to the network104 (as shown inFIG. 1), or may be connected to a different network such as the public switched telephone network (“PSTN”) or a mobile network (not shown inFIG. 1). If the second user terminal is connected to thenetwork104, then it may be running aclient program114 provided by the operator of the telephony system, similar to theclient112 running on the first user terminal102. If connected to the PSTN, the second user terminal may be a fixed line telephone, and if connected to a mobile network, the second user terminal may be a mobile telephone.
• In order to be able to make telephone calls, theuser106 must be suitably registered and authenticated. Furthermore, theuser106 must also be able to pay for the telephone services. Sensitive payment information therefore needs to be transferred from theuser106 to a payment service provider (“PSP”) across thenetwork104. As the payment information is of a sensitive nature, the payment system needs to be very secure. If there is sensitive information flowing though the telephony system servers, then the system must comply with payment card industry (“PCI”) rules enforced by credit card companies. Complying with these rules is expensive and takes time. In addition, if the servers of the telephony system are storing sensitive payment information, then they are likely to become a target for attack by hackers. There is therefore significant benefit in reducing the number of system entities that are exposed to sensitive information and need to be PCI compliant. Furthermore, the secure transmission of the sensitive information needs to be as simple and usable as possible from the point of view of the user.
• As stated previously, it is significantly simpler for the user of the telephony system to be able to securely pay for services directly using theclient112 running on the user terminal102. In addition, this allows the client to be the only part of the telephony system that needs to be PCI compliant. As will be described hereinafter, the rest of the system just sees encrypted information, and has no knowledge of the information content. Therefore, the rest of the system is not directly dealing with sensitive information and does not need to be PCI compliant. The expense of making the client PCI compliant is an order of magnitude cheaper than maintaining a secure server environment.FIG. 1 shows the entities in thesystem100 that allow theuser106 to securely pay for telephony services through theclient112. Theuser106 makes the payment to apayment service provider116. ThePSP116 is a private network that is connected to network104, and may comprise aPSP proxy118 and aPSP web application120. ThePSP proxy118 is a software program running on a processor in a server, which is connected between thePSP web application120 and thenetwork104, and is responsible for decrypting information before it is presented to thePSP web application120. ThePSP web application120 is a software application executed on a processor in a server. ThePSP proxy118 andPSP web application120 may be located on separate servers, or may be running on the same server. ThePSP116 may be operated by a different operator than the telephony service.
• Also connected to thenetwork104 are aSkype backend server122 and aSkype web application124. TheSkype backend server122 and theSkype web application124 may be located within theprivate network128 of the operator of the telephony system. TheSkype backend server122 and theSkype web application124 may be geographically co-located, or may be geographically separated. TheSkype backend server122 is located between theSkype web application124 and thenetwork104, and is responsible for exchanging messages between theSkype web application124 and theclient112. TheSkype backend122 and theclient112 communicate using a proprietary Skype protocol, and do not use HTTP. This is to avoid the detection and blocking of HTTP messages by third parties and firewalls, as discussed previously. Furthermore, theSkype backend122 also blocks HTTP.
• The user terminal102 hasweb browsing software130 installed on it, in addition to theclient112. Theweb browser130 is capable of being utilised as part of the user interface of theclient112, and can be controlled by theclient112 to display hypertext markup language (“HTML”) webpages to theuser106.
• The operation of thesystem100 shown inFIG. 1 will now be described with reference toFIGS. 2A-2E. Referring first toFIG. 2A, this figure shows the maintenance of cryptography key information at theclient112. In step S1, theSkype web application124 will periodically query thePSP web application120 for a new version of its public key. The message in step S1 is in the form of a HTTP Get request specifying the uniform resource locator (“URL”) of the key located at the PSP web application. In response to this request, thePSP web application120 will return the public key to theSkype web application124 in step S2. The above two steps are performed periodically and independently of any other operations to ensure that theSkype web application124 always has an up-to-date copy of the public key.
• Theclient112 periodically polls theSkype backend122 using the Skype protocol for a new version of the public key in step S3. TheSkype backend server122 forwards the request to theSkype web application124 in the form of an HTTP Get request specifying the URL of the key stored in the Skype web application in step S4. TheSkype web application124 returns the key to theSkype backend server122 in step S5, and this is passed to theclient112 in step S6 using the Skype protocol. The above four steps are performed periodically, without the user being aware of its operation, in order to ensure that the key information is always up to date in theclient112.
• Therefore, as a result of the steps performed inFIG. 2A, theclient112 has a recent copy of the public key of thePSP web application120 for use in the payment process, as described in more detail hereinbelow.
• FIG. 2B shows theuser106 initiating the payment process. In step S7, theuser106 clicks a button which may be labeled “Buy Skype Credit” (although other labeling is possible) displayed in theclient112, indicating to theclient112 that the payment process should be started. In step S8, theclient112 initiatesweb browser130 control, in which the client opens the web browser within the client user interface, and when complete a signal is returned to theclient112 in step S9.
• Associated with the button “Buy Skype Credit” is a URL, which may, for example, be of the form “nonsecure://skype/buycredit.html”. This is a request to retrieve the page “buycredit.html” from the server “skype”, so that the page “buycredit.html” may be displayed to theuser106 in theweb browser130. This request does not begin with the standard “http://”, but uses a marker string “nonsecure”. A request such as “nonsecure://skype/buycredit.html” has the same functionality as a standard HTTP request, but the string “nonsecure” allows theclient112 to intercept the request and determine what action to take. In other words, “nonsecure” acts as a marker for theclient112 to use when intercepting requests. When theclient112 sees an attempt to make a request using “nonsecure”, theclient112 knows that the request does not contain sensitive information, and that the request can be sent to the Skype backend server122 (a further marker is also used, “secure”, as will be described hereinafter).
• At step S110, theclient112 wraps the “nonsecure” request message into a Skype proprietary communication protocol message and this is sent to theSkype backend server122. On receipt of the message, theSkype backend server122 unwraps the “nonsecure” request from the Skype proprietary communication protocol. For security and maintainability reasons, the requests only contain references to arbitrary services, not actual server addresses and ports. For example, the request “nonsecure://skype/buycredit.html” only contains a reference to a server “skype”, and not an actual server address. TheSkype backend server122 therefore needs to resolve an arbitrary reference to a service name into a web server address. This is achieved by maintaining a table of correspondence between services and server addresses. Only theSkype backend server122 maintains the mapping table between references and server addresses. TheSkype backend122 resolves the message from theclient112 to obtain the web server address. For example, the reference to “skype” in “nonsecure://skype/buycredit.html” may be resolved to “http://webstore.skype.com”. TheSkype backend server122 then constructs a new HTTP request using the resolved address and the rest of the “nonsecure” request, resulting in, for example, “http://webstore.skype.com/buycredit.html”.
• This HTTP request is forwarded to the resolved location of theSkype web application124 in the form of the above HTTP Get request at step S11, and the requested page is returned by theSkype web application124 in step S12 in the form of HTML. TheSkype backend122 wraps the HTML response from the Skype web application in the Skype protocol and forwards the page to theclient112 in step S13, and this is then unwrapped from the Skype protocol and sent to theweb browser130 in step S14, and subsequently displayed to theuser106 in step S15.
• In step S16, theuser106 views the page in theweb browser130 window and clicks on a link which may be labeled “Get Started”. This link may be, for example, a link to the URL “nonsecure://skype/getstarted.html”. Theclient112 intercepts the web browser's attempt to make a “nonsecure” request (a type of HTTP Get request) to navigate to the linked webpage at step S17. Theclient112 wraps the “nonsecure” request message into a Skype proprietary communication protocol message and this is sent to theSkype backend122 in step S18. TheSkype backend122 unwraps the message and resolves the message from theclient112 to obtain the web server address in a similar manner to that described above with reference to step S10. TheSkype backend122 then creates a HTTP request from the resolved web server address and the unwrapped “nonsecure” request, for example “http://webstore.skype.com/getstarted.html”. The HTTP request is forwarded to the resolved address of theSkype web application124 in step S119. TheSkype web application124 returns the webpage “getstarted.html” to theSkype backend122 in step S20, which wraps the response in the Skype protocol and forwards it to theclient112 in step S21, and this is unwrapped and passed to theweb browser130 window in step S22 and displayed to theuser106 in step S23.
• The page displayed to theuser106 comprises a form to enter initial payment information. In step S24, theuser106 views the page and fills in the initial payment information, such as a billing address, email address and payment method and clicks “next”. The “next” button is associated with a URL, which may be, for example, “nonsecure://skype/initialform.html”. The web browser generates a type of HTTP Post request including the information entered into the form, such as “nonsecure://skype/initialform.html?address=x&method=y” (where “address=x” and “method=y” represents exemplary information entered by the user in the form), and transmits this message to thenetwork104 via thenetwork port105 in step S25. The HTTP Post request from theweb browser130 is received by the client112 (which detects the use of the “nonsecure” marker) before it can reach thenetwork port105. The client wraps the HTTP Post request in a Skype protocol message and this message is forwarded to theSkype backend server122 in step S26. Note that theclient112 may include other information in the message when it is wrapped in the Skype protocol, as discussed in more detail hereinafter with reference toFIG. 3.
• TheSkype backend server122 unwraps and resolves the HTTP Post request message. For example, “nonsecure://skype/initialform.html?address=x&method=y” may be resolved to a HTTP message of the form “http://webstore.skype.com/initialform.html?address=x&method=y”. TheSkype backend server122 then sends the resolved request to theSkype web application124 in step S27 to initiate the payment. TheSkype web application124 sends a message containing the initial payment information to thePSP web application120 in step S28 to initiate the payment at the PSP. In step S29 thePSP web application120 processes the information and returns the URL of a webpage containing the appropriate form for the payment method, such as a credit card information form. TheSkype web application124 receives the URL and creates a redirect header. The redirect header is sent to theSkype backend122 in step S30.
• TheSkype backend server122 resolves the address from the redirect header and sends a request to thePSP web application120 to obtain the required webpage in step S31. ThePSP web application120 then returns the webpage containing the form for the payment details (such as credit card information) in step S32. This webpage is subsequently forwarded to theclient112 using the Skype protocol in step S33, unwrapped and passed to theweb browser130 in step S34, and displayed to theuser106 in step S35.
• As a result of the procedure outlined inFIG. 2B, theuser106 has been presented with a form in theweb browser130, into which the user can enter credit card payment information. This payment information is sensitive, and therefore must be handled in a secure manner. The method in which this is performed can be seen with reference toFIG. 2C.
• In step S36, theuser106 enters the payment information (for example credit card number, expiry date or other information) into the HTML form presented in the web browser window and clicks a “Submit” button. The “Submit” button is associated with a URL, which may be, for example, “secure://somepsp/creditcardform.html”. Theweb browser130 then generates a type of HTTP Post request using a marker “secure” containing the payment information (in the form of postData) and the URL above in step S37. This HTTP Post request may be, for example, “secure://somepsp/creditcardform.html?cardno=1234&expirydate=01012010” (where “cardno=1234” and “expirydate=01012010” represents exemplary credit card information entered in the form. Note also that this is a POST request represented in GET notation for ease of reading). The HTTP Post request from theweb browser130 is intercepted by theclient112, and prevented from being sent into thenetwork104. In particular, the client detects the marker “secure”. This not only indicates to the client that it should intercept the message (as with “nonsecure”), but also that the information in the message should be encrypted.
• In step S38, the payment information, in the form of postData from the HTTP Post request, is encrypted using the public key of the PSP (provided to the client as outlined above with regards toFIG. 2A). The encryption is performed using a standard encryption algorithm as are known in the art. For example, if the postData were to comprise information such as “cardno=1234” and “expirydate=01012010”, this is encrypted to form a new HTTP Post request with, e.g., “payload=34214123ddasdas”. The client then creates a new HTTP Post request with the encrypted payload, for example “secure://somepsp/creditcardform.html?payload=34214123ddasdas”.
• Theclient112 then wraps the HTTP Post request including the encrypted payment information in the Skype protocol format. In addition, theclient112 includes further information in the Skype protocol message. The further information may include user information, such as the user's Skypename and the version of theclient112 they are running, and context information containing fraud-related information about the request context, such as the identity of the terminal and the user. The Skype protocol message is forwarded to theSkype backend server122 from theclient112 in step S39.
• Providing user information and context information in the Skype protocol message gives the advantage of additional security. This is because, in the case of ordinary Web access, it is easy to conceal the identity of the actual terminal that a request originates from, and this often happens unintentionally on the part of the user (due to the use of proxies). However, the information in the Skype protocol message ties the request to a specific terminal, which can allow for the use of greater fraud detection mechanisms. Furthermore, theclient112 already knows the identity of user, and this information can therefore be passed to the PSP web application without having to prompt the user for an additional username and password.
• TheSkype backend122 receives the Skype protocol message containing the encrypted payment information. TheSkype backend122 unwraps the Skype protocol message to leave the HTTP Post request comprising the encrypted payment information. TheSkype backend122 resolves the reference contained in the request to the server address of thePSP proxy118, for example resolving the reference to “somepsp” to “http://www.psp.com”. TheSkype backend122 then creates a new HTTP Post request message by combining the resolved server address of thePSP proxy118 with the encrypted payload from the “secure” message. For example, this may create a HTTP Post request such as http://www.psp.com/creditcardform.html?payload=34214123ddasdas. This HTTP Post request is sent from theSkype backend122 to thePSP Proxy118 in step S40. It should be noted that theSkype backend122 is not aware at any point of the actual contents of the request message. It does not decrypt the information, but merely “repackages” it into a new message. TheSkype backend122 therefore does not require PCI compliance. Furthermore, theSkype backend122 does not store the payment information, and is therefore not a target for hackers.
• The operation performed in steps S37, S39 and S40 can be seen further illustrated inFIG. 3, which shows an example of the structure of the messages received and sent in these steps. This shows theHTTP Post request302 using the “secure” marker from theweb browser130, comprising the reference to thePSP304 and theunencrypted postData306, as received at theclient112. The postData (the payment information) is encrypted to produce theencrypted payment information308. Theencrypted payment information308, the reference to thePSP304,user information310, andcontext312 are wrapped between aSkype protocol header314 andSkype protocol footer316 to form theSkype protocol message318. TheSkype protocol message318 is sent to theSkype backend122, where it is unwrapped and thePSP reference304 resolved to form anHTTP Post request320 comprising the server address of thePSP322 and theencrypted payment information308.
• Referring again toFIG. 2C, in step S41 the encrypted payment information in the HTTP Post request is decrypted by thePSP proxy118 to obtain the original payment information entered by theuser106. The decrypted payment information is then sent to thePSP web application120 in step S42 in the form of a HTTP Post request containing the decrypted payment information as postData and the URL of the PSP web application.
• ThePSP web application120 processes the payment information from theuser106. If, following the processing of the payment information, the payment is completed, then the operation shown inFIG. 2D is performed. If, on the other hand, the payment is not yet completed, then the operation shown inFIG. 2E is performed.
• Reference is first made toFIG. 2D, which, as mentioned above, shows the case in which the payment has been completed. In step S43, thePSP web application120 issues a redirect header in response to the completed payment. The redirect header is received at thePSP proxy118 and forwarded without any changes to theSkype backend122 in step S44. The Skype backend122 processes the redirect header, and, in step S45, sends an HTTP Get request to the URL of theSkype web application124 referred to in the redirect header. TheSkype web application124 returns a HTML webpage to theSkype backend122 in response in step S46. The HTML webpage is then forwarded to theclient112 in step S46, and onto theweb browser130 in step S48. Finally, theuser106 is displayed the results of the transaction in the web browser window in step S49.
• Reference is now made toFIG. 2E, which, as mentioned above, shows the case in which the payment has not yet been completed. This may occur if the user has entered their credit card details incorrectly, or in the case that the PSP requests additional information for fraud control purposes. In this instance thePSP web application120 generates a HTML webpage to be displayed to theuser106. The HTML page is sent to thePSP proxy118 in step S50, and forwarded unaltered to theSkype backend122 in step S51. The Skype backend122 forwards the HTML webpage to theclient112 in step S52, and onto theweb browser130 in step S53. Finally, theuser106 is displayed the HTML page from thePSP web application120 in the web browser window in step S54.
• FIG. 4 shows a flowchart summarising the operations performed at the user terminal102. In step S402, theuser106 chooses to make a payment from within theclient program112. In response to this, theclient112 opens aweb browser130 within the client user interface at step S404. A payment details form is fetched from thePSP116, and is presented to the user in step S406 in theweb browser130. In step S408 theuser106 enters the payment information into the form in theweb browser130. Theweb browser130 creates a HTTP Post request with the “secure” marker including the payment information (302 as shown inFIG. 3) and attempts to send this into thenetwork104 via thenetwork port105 in step S410. Theclient112 detects the “secure” marker and intercepts the HTTP Post request from theweb browser130 in step S412, thereby preventing it from being sent into thenetwork104. In step S414, theclient112 encrypts the payment information from the HTTP Post request. Then, in step S416, the client wraps the HTTP Post request with the encrypted payload in a Skype proprietary protocol message (318 inFIG. 3). Finally, in step S418, the client transmits the Skype protocol message containing the encrypted payment information to theSkype backend server122.
• FIG. 5 shows the page flow for the operations shown inFIGS. 2B-2D. The step numbers shown inFIG. 5 correspond to those as shown inFIGS. 2B-2D. InFIG. 5, “IE” refers to “Internet Explorer”, which is an example of a type ofweb browser130.
• While this invention has been particularly shown and described with reference to preferred embodiments, it will be understood to those skilled in the art that various changes in form and detail may be made without departing from the scope of the invention as defined by the appendant claims.

Claims (34)

1. A method of transmitting information from a user to a first network entity over a communications network, comprising the steps of:

the user entering information into a browser executed at a user terminal;

the browser generating a first message comprising the information using a first communication protocol for dispatch over the network via a network port, the first message including an identifier of the first network entity;

receiving the first message at a client executed at the user terminal before the first message reaches the network port;

wrapping the first message in a second message of a second communication protocol used for transmitting messages between the client and a second network entity;

transmitting the second message to the second network entity over the communications network; and

unwrapping the first message from the second message at the second network entity, translating the identifier of the first network entity to a network address of the first network entity and transmitting the first message to the first network entity over the communications network.

2. A method according toclaim 1, further comprising the step of encrypting the information in the first message after receiving the first message at the client.

3. A method according toclaim 2, further comprising the step of receiving the first message transmitted by the second network entity at the first network entity.

4. A method according toclaim 3, further comprising the step of decrypting the information in the first message, after it is received at the first network entity.

5. A method according toclaim 2, wherein the step of encrypting is performed using an encryption key provided by the first network entity.

6. A method according toclaim 5, further comprising the step of the first network entity periodically transmitting the encryption key to the second network entity.

7. A method according toclaim 1, further comprising the steps of:

transmitting a third message to the second network entity from the first network entity, responsive to receiving the first message;

receiving the third message at the second network entity and, responsive thereto, fetching a webpage from a server;

wrapping the webpage in a fourth message of the second communication protocol;

transmitting the fourth message to the client over the communications network;

unwrapping the webpage from the fourth message at the client and passing the webpage to the browser; and

displaying the webpage to the user in the browser.

8. A method according toclaim 7, wherein the third message is a redirect message.

9. A method according toclaim 1, wherein the step of wrapping the first message in a second message of a second communication protocol comprises the step of adding a header and a footer to the first message.

10. A method according toclaim 1, wherein the first communication protocol is a hypertext transfer protocol.

11. A method according toclaim 1, wherein the first network entity is a payment service provider.

12. A method according toclaim 1, wherein the communications network is the Internet.

13. A method according toclaim 1, wherein the second network entity is a Skype backend server.

14. A method according toclaim 1, wherein the information is payment information.

15. A system for transmitting information from a user to a first network entity over a communications network, comprising:

a browser executed at a user terminal, the browser comprising means for receiving information entered by the user, and means for generating a first message comprising the information using a first communication protocol for dispatch over the network via a network port, the first message including an identifier of the first network entity;

a client executed at the user terminal comprising means for receiving the first message at the client before the first message reaches the network port, means for wrapping the first message in a second message of a second communication protocol used for transmitting messages between the client and a second network entity, and means for transmitting the second message to the second network entity over the communications network; and

the second network entity comprising means for unwrapping the first message from the second message at the second network entity, means for translating the identifier of the first network entity to a network address of the first network entity, and means for transmitting the first message to the first network entity over the communications network.

16. A system according toclaim 15, wherein the client further comprises means for encrypting the information in the first message after receiving the first message at the client.

17. A system according toclaim 16, wherein the first network entity further comprises means for receiving the first message transmitted by the second network entity.

18. A system according toclaim 17, wherein the first network entity further comprises means for decrypting the information in the first message, after it is received at the first network entity.

19. A system according toclaim 16, wherein the encryption is performed using an encryption key provided by the first network entity.

20. A system according toclaim 19, wherein the first network entity further comprises means for periodically transmitting the encryption key to the second network entity.

21. A system according toclaim 15, wherein the first network entity further comprises means for transmitting a third message to the second network entity, responsive to receiving the first message.

22. A system according toclaim 21, wherein the second network entity further comprises means for receiving the third message and, responsive thereto, fetching a webpage from a server, means for wrapping the webpage in a fourth message of the second communication protocol, and means for transmitting the fourth message to the client over the communications network.

23. A system according toclaim 22, wherein the client further comprises means for unwrapping the webpage from the fourth message and passing the webpage to the browser.

24. A system according toclaim 23, wherein the browser further comprises means for displaying the webpage to the user.

25. A system according toclaim 21, wherein the third message is a redirect message.

26. A system according toclaim 15, wherein the means for wrapping the first message in a second message of a second communication protocol comprises means for adding a header and a footer to the first message.

27. A system according toclaim 15, wherein the first communication protocol is a hypertext transfer protocol.

28. A system according toclaim 15, wherein the first network entity is a payment service provider.

29. A system according toclaim 15, wherein the communications network is the Internet.

30. A system according toclaim 15, wherein the second network entity is a Skype backend server.

31. A system according toclaim 15, wherein the information is payment information.

32. A user terminal comprising:

a browser executed at the user terminal, the browser comprising means for receiving information entered by a user, and means for generating a first message comprising the information using a first communication protocol for dispatch over a communications network via a network port, the first message including an identifier of a first network entity; and

a client executed at the user terminal comprising means for receiving the first message at the client before the first message reaches the network port, means for wrapping the first message in a second message of a second communication protocol used for transmitting messages between the client and a second network entity, and means for transmitting the second message to the second network entity over the communications network.

33. A network entity comprising:

means for unwrapping a first message of a first communication protocol from a second message of a second communication protocol transmitted by a client executed at a user terminal to the network entity over a communications network, the first message including an identifier of a further network entity;

means for translating the identifier of the further network entity to a network address of the further network entity; and

means for transmitting the first message to the further network entity over the communications network.

34. A computer program product comprising program code means which when loaded into a computer controls the computer to carry out the method ofclaim 1.

Images