# US 2008/0189773 A1 · Securing User Logins with Wv Bindings and Transports > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2008/0189773 A1 - Document ID: US20080189773A1 - Status: Published application - Kind: A1 - Application number: 12/088,456 - Filed: 2006-09-29 - Published: 2008-08-07 - Earliest claimed: 2005-09-30 - Inventors: Nick Maiorano; Sylvain Legault; Patrice Hebert; Gaetan Vachon - Web page: https://patentgrep.com/patent/US20080189773A1 ## CPC - H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)} - H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)} - H04L 51/04: Real-time or near real-time messaging, e.g. instant messaging [IM] - H04L 63/0884: {by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity} - H04L 63/10: {for controlling access to devices or network resources} - H04L 63/205: {involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved (negotiation of communication capabilities H04L69/24)} - H04L 69/18: Multiprotocol handlers, e.g. single devices capable of handling multiple protocols - H04L 51/066: Format adaptation, e.g. format conversion or compression - H04L 51/58: Message adaptation for wireless communication - H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)} - H04L 2209/80: Wireless - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract There is disclosed a method and system for communicating a secure login request between a mobile client and a destination server providing access to a service, the method to be implemented by a disclosed gateway adapted to communicate with both the mobile client and the destination server. The gateway may also implement appropriate protocol conversions between otherwise incompatible client and server pairs. Wireless instant messaging, email and other such services are considered as exemplary services for the disclosed method, system and gateway. ## Claims ### Claim 1 A computer implemented method for communicating a secure login request between a mobile client and a destination server providing access to a service, the method to be implemented by a gateway adapted to communicate with both the mobile client and the destination server, the method comprising the steps of: a) receiving a login request from the mobile client requesting access to the service, said request comprising login information required to gain access to the service; b) extracting said login information from said login request; c) determining a secure login procedure supported by the destination server; and d) communicating said login information to the destination server in accordance with said secure login procedure. ### Claim 2 (depends on 1) The computer implemented method of claim 1, wherein said secure login procedure comprises at least one of a secure 4-way login procedure and a secure 2-way login procedure. ### Claim 3 (depends on 2) The computer implemented method of claim 2, wherein said secure 2-way login procedure comprises at least one of a 2-way login over HTTPS, a 2-way login over a VPN and a 2-way login over a leased line. ### Claim 4 (depends on 1) The computer implemented method of claim 1, wherein said receiving step comprises receiving said login request in accordance with a client-supported secure login procedure that is different from said secure login procedure supported by the destination server. ### Claim 5 (depends on 4) The computer implemented method of claim 4, wherein said client-supported secure login procedure comprises a secure 2-way login procedure, said secure 2-way login procedure comprising at least one of a 2-way login over HTTPS, a 2-way login over a VPN and a 2-way login over a leased line. ### Claim 6 (depends on 4) The computer implemented method of claim 4, the method further comprising the step after step d) of: e) receiving a login result from the destination server in accordance with said secure login procedure and communicating said login result to the mobile client in accordance with said client-supported secure login procedure. ### Claim 7 (depends on 1) The computer implemented method of claim 1, the method further comprising the step after step a) of determining a protocol supported by the destination server and communicating said login information to the destination server in accordance with said protocol. ### Claim 8 (depends on 7) The computer implemented method of claim 7, wherein said protocol comprises a binding/transport combination selected from any one of SMS/SMPP, SMS/HTTP, SMS/HTTPS, XML/HTTP, XML/HTTPS, BXML/HTTP and BXML/HTTPS. ### Claim 9 (depends on 8) The computer implemented method of claim 8, said receiving step comprising receiving said login request over a client-supported protocol that is different from said protocol supported by the destination server. ### Claim 10 (depends on 1) The computer implemented method of claim 1, wherein the mobile client comprises an IM client and the destination server comprises an IM server. ### Claim 11 (depends on 1) The computer implemented method of claim 1, wherein the mobile client comprises an email client and the destination server comprises an email server. ### Claim 12 (depends on 1) The computer implemented method of claim 1, wherein said login information comprises a user password required to gain access to the service. ### Claim 13 A computer implemented method for communicating a login request between a mobile client and a plurality of servers, each of the servers providing access to at least one of a plurality of services, the method to be implemented by a gateway adapted to communicate with both the mobile client and the servers, the method comprising the steps of: a) receiving a login request from the mobile client requesting access to a service; b) determining based on said request a destination server selected from said servers providing access to said service; c) determining a secure login procedure supported by said destination server; and d) communicating said login request to said destination server in accordance with said secure login procedure. ### Claim 14 (depends on 13) The computer implemented method of claim 13, wherein said secure login procedure comprises at least one of a secure 4-way login procedure and a secure 2-way login procedure. ### Claim 15 (depends on 13) The computer implemented method of claim 13, wherein said secure 2-way login procedure comprises at least one of a 2-way login over HTTPS, a 2-way login over a VPN and a 2-way login over a leased line. ### Claim 16 (depends on 13) The computer implemented method of claim 13, wherein said receiving step comprises receiving said login request in accordance with a client-supported secure login procedure that is different from said secure login procedure supported by said destination server. ### Claim 17 (depends on 16) The computer implemented method of claim 16, the method further comprising the step after step d) of: e) receiving a login result from said destination server in accordance with said secure login procedure and communicating said login result to the mobile client in accordance with said client-supported secure login procedure. ### Claim 18 (depends on 16) The computer implemented method of claim 16, wherein said client-supported secure login procedure comprises a secure 2-way login procedure, said secure 2-way login procedure comprising at least one of a 2-way login over HTTPS, a 2-way login over a VPN and a 2-way login over a leased line. ### Claim 19 (depends on 13) The computer implemented method of claim 13, the method further comprising the step after step b) of determining a protocol supported by said destination server and communicating said login information to said destination server in accordance with said protocol. ### Claim 20 (depends on 19) The computer implemented method of claim 19, said receiving step comprising receiving said login request over a client-supported protocol that is different from said protocol supported by said destination server. ### Claim 21 (depends on 13) The computer implemented method of claim 13, wherein the mobile client comprises an IM client and said service comprises an IM service. ### Claim 22 (depends on 13) The computer implemented method of claim 13, wherein the mobile client comprises an email client and said service comprises an email service. ### Claim 23 A gateway for communicating a login request between a mobile client and a plurality of servers, each of the servers providing access to at least one of a plurality of services, the gateway comprising: a first interface for communicating with the mobile client and adapted to receive a login request therefrom for access to one of the services; a gateway module in operative communication with said first interface, said module interpreting said login request to determine a destination server selected from said servers providing access to said one of the services and to establish a secure login procedure supported by said destination server; and a second interface for communicating said login request to said destination server in accordance with said secure login procedure. ### Claim 24 (depends on 23) The gateway of claim 23, wherein said secure login procedure comprises at least one of a secure 4-way login procedure and a secure 2-way login procedure. ### Claim 25 (depends on 23) The gateway of claim 23, wherein said login request is received from the client via said first interface in accordance with a client-supported secure login procedure that is different from said secure login procedure supported by said destination server. ### Claim 26 (depends on 23) The gateway of claim 23, said gateway module further determining a protocol supported by said destination server and communicating said login request to said destination server via said second interface in accordance with said protocol. ### Claim 27 (depends on 26) The gateway of claim 26, wherein said login request is received from the client via said first interface in accordance with a client-supported protocol that is different from said protocol supported by said destination server. ### Claim 28 (depends on 23) The gateway of claim 23, wherein the mobile client comprises an IM client and said one of said services comprises an IM service. ### Claim 29 (depends on 28) The gateway of claim 28, wherein said IM client and said destination server are configured to comply with at least one of OMA IMPS 1.1 standards and OMA IMPS 1.2 standards. ### Claim 30 (depends on 23) The gateway of claim 23, wherein the mobile client comprises an email client and said one of said services comprises an email service. ### Claim 31 A secure login system for providing access to at least one of a plurality of services, the system comprising: a plurality of ground end systems each comprising at least one server for providing access to at least one of a plurality of services; at least one mobile device comprising at least one mobile client for requesting access to at least one of said services; and a gateway, said gateway comprising: a first interface for communicating with said mobile client and adapted to receive a login request therefrom for access to one of the services; a gateway module in operative communication with said first interface, said module interpreting said login request to determine a destination server selected from said servers providing access to said one of the services and to establish a secure login procedure supported by said destination server; and a second interface for communicating said login request to said destination server in accordance with said secure login procedure. ### Claim 32 (depends on 31) The system of claim 31, wherein said secure login procedure comprises at least one of a secure 4-way login procedure and a secure 2-way login procedure. ### Claim 33 (depends on 31) The system of claim 31, wherein said login request is received from the client via said first interface in accordance with a client-supported secure login procedure that is different from said secure login procedure supported by said destination server. ### Claim 34 (depends on 31) The system of claim 31, said gateway module further determining a protocol supported by said destination server and communicating said login request to said destination server via said second interface in accordance with said protocol. ### Claim 35 (depends on 34) The system of claim 34, wherein said login request is received from the client via said first interface in accordance with a client-supported protocol that is different from said protocol supported by said destination server.