Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
  • H04L9/3226—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using a predetermined code, e.g. password, passphrase or PIN
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L63/00—Network architectures or network communication protocols for network security
  • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
  • H04L63/083—Network architectures or network communication protocols for network security for authentication of entities using passwords
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
  • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
  • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
  • H04L9/3271—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using challenge-response
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/06—Authentication
  • H04W12/068—Authentication using credential vaults, e.g. password manager applications or one time password [OTP] applications
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
  • H04L2209/80—Wireless

Definitions

• Embodiments of the present invention are directed to networking and more particularly to providing a credential to a network device in order to access a communication network.
• hotspots may be established in areas where users are not known in advance.
• Examples of hotspots may comprise hotels, coffee shops, campuses, and other public or private locations where digital device users may be interested in connecting to a communication network such as the Internet.
• these hotspots are wireless.
• the hotspots require the users to be authorized .
• the user is typically required to perform a login process before the user's digital device is allowed access to the hotspot.
• a common login process comprises opening a web browser and connecting to a captive portal website where a user name and password may be entered.
• Another process may require the. user to provide payment information. After confirmation of the payment, an access point will allow the user's digital device access to the hotspot.
• Such digital devices may include, for example, Wi-Ft VoIP phones, cameras, and MP3 players. These digital devices, typically, do not include a web browser or mechanism to enter credentials or payment information. As a result, it is difficult for these digital devices to use hotspots.
• One conventional solution to this problem is to pre-configure credentials into the digital device.
• the digital device must comprise enough memory to store all the credential information.
• Embodiments of the present invention provide systems and methods for providing a network credential in order to access a communication network.
• the network device may comprise an access point for the communication network.
• the digital device may need to obtain a network credential to provide to a network device.
• a credential engine of the digital device may generate a credential request to obtain the network credential.
• the credential request may be sent to a credential server.
• a credential request response may then be received by the credential engine and analyzed to retrieve the network credential.
• the credential request response may also comprise login procedural information.
• the digital device attempting to access the communication network may receive an authentication request from the network device upon attempting to access the communication network.
• An authentication record based on the authentication request is retrieved by an authentication record module of the digital device.
• the retrieval may be based on the login procedural information received in the credential request response.
• the credential is then provided within the authentication record and transmitted as an authentication response to the network device.
• the digital device Upon authentication by the network device, the digital device is provided access to the communication network.
• FlG. 1 is a diagram of an environment in which embodiments of the present invention may be practiced.
• FIG. 2 is a block diagram of an exemplary digital device.
• FIG. 3 is a flowchart of an exemplary method for providing network access to the digital device.
• FIG. 4 is a flowchart of an exemplary method for obtaining network credentials.
• FIG. 5 is a flowchart of an exemplary method for authenticating the digital device with the network device.
• FIG. 6 is a display of an exemplary network access authentication page, according to one embodiment of the present invention.
• FIG. 7 is a flow diagram of an exemplary process for providing network access to the digital device.
• FiG. 8 is a block diagram of an exemplary credential request.
• Embodiments of the present invention provide systems and methods for accessing a communication network via a hotspot.
• a digital device is associated with a user.
• a network device e.g., hotspot access point
• the authentication may comprise a request for a network credential from the digital device which is verified by the network device prior to granting access.
• the communication network comprises the Internet.
• FIG. 1 illustrates a diagram of an environment 100 in which embodiments of the present invention may be practiced.
• a user with a digital device 102 enters a hotspot.
• the digital device 102 may automatically transmit a credential request as a standard protocol over a network device 104.
• the credential request may be forwarded to a credential server 116 which, based on the information contained within the credential request, transmits a credential request response back to the digital device 102.
• the credential request response contains network credentials which the digital device 102 may provide to the network device 104, the authentication server 108, or the access controller 112 to obtain access to the communication network 114.
• a hotspot comprises the network device 104, the authentication server 108, the DNS server 110, and the access controller 112 which are coupled to the local area network 106 (e.g., a "walled garden").
• the network device 104 may comprise an access point which allows the digital device 102 to communicate with the authentication server 108, the DNS server 110, and the access controller 112 over the local area network 106.
• the digital device 102 may comprise a laptop, mobile phone, camera, personal digital assistant, or any other computing device.
• the authentication server 108 is a server that requires network credentials from the digital device 102 before allowing the digital device 102 access to communicate over the communication network 114.
• the network creder comprise a username, password, and login procedure information.
• the DNS server 110 provides DNS services over the local area network 106 and may relay requests to other DNS servers (not shown) across the communication network 114.
• the access controller 112 is an access device such as a router or bridge that can allow communication between devices operationally coupled to the network device 104 with devices coupled to the communication network 114.
• the hotspot in FIG. 1 depicts separate servers coupled to the local area network 106, those skilled in the art will appreciate that there may be any number of devices (e.g., servers, digital devices, access controllers, and network devices) coupled to the local area network 106.
• the local area network 106 is optional.
• the authentication server 108, the DNS server 110, and the access controller 112 are coupled directly to the network device 104.
• the authentication server 108, the DNS server 110, and the access controller 112 may be combined within one or more servers or one or more digital devices.
• FIG. 1 depicts wireless access, the digital device 102 may be coupled to the network device 104 wirelessly or over wires (such as lObaseT).
• the authentication server 108 may require the digital device 102 to provide one or more network credentials for access to the hotspot.
• the network credential may comprise, for example, a username and password for an account associated with the hotspot.
• network credentials other than a user name and password may be utilized.
• the digital device 102 may dynamically acquire the network credentials from the credential server 116.
• the digital device " J 02 may send a credential request comprising an identity of the digital device 102 (or the user of the digital device 102) and details about the network device 104 (e.g., name of the network device 104 or Wi-Fi service provider) to the credential server 116.
• the network device 104 may provide an IP address to which DNS queries may be submitted, for example, via DHCP (Dynamic Host Configuration Protocol).
• the credential request may be formatted as a standard protocol.
• the credential request may be formatted as a DNS request.
• the credential request may be a text record request (e.g., TXT), which comprises a standard record type such that the network infrastructure (e.g., the access controller 112) will not block the request.
• TXT text record request
• the network infrastructure e.g., the access controller 112
• the credential request is received by the DNS server 110 which may forward the credential request to the credential server 116 for the network credential.
• the credential server 116 may perform a lookup to determine the proper network credential(s) to send back to the DNS server 110 which forwards the network credential back to the requesting digital device 102.
• the proper network credential(s) are sent from the credential server 116 to the digital device 102 over the same path as the transmission of the credential request.
• Patent Application No. entitled "System and Method for Providing
• Network Credentials filed September 6, 2007.
• the credential request may be forwarded through any number of servers, including but not limited to DNS servers, prior to being received by the credential server 116.
• the credential request is forwarded directly from the network device 104 to the credential server 116.
• a credential request response from the credential server 116 may comprise the username, password and/or login procedure information.
• the login procedural information may comprise, for example, HTML form element names, submission URL, or submission protocol.
• the network credential response may be encrypted by the c ⁇ server 116 using an encryption key associated with the digital device 102 prior to transmission back to the digital device 102.
• the digital device 102 may submit the network credential (retrieved from the network credential response) to the network device 104 in an authentication response.
• the authentication response may be forwarded to an authentication server 108 for verification.
• the authentication server 108 may comprise an AAA server or RADIUS server.
• FIG. 1 is exemplary. Alternative embodiments may comprise more, less, or functionally equivalent components and still be within the scope of present embodiments.
• the functions of the various servers e.g., DNS server 110, credential server 116, and authentication server 108, may be combined into one or two servers. That if, for example, the authentication server 108 and the DNS server 110 may comprise the same server, or the functionality of the authentication server 108, the DNS server 110, and the access controller 112 may be combined into a single device.
• the exemplary digital device 102 comprises a processor 202, input/output (I/O) interface(s) 204, a communication network interface 206, a memory system 208, and a storage system 210.
• the I/O interfaces 204 may comprise interfaces for various I/O devices such as, for example, a keyboard, mouse, and display device.
• the exemplary communication network interface 206 is configured to allow the digital device 102 to allow communications with the communication network 114 and/or the local area network 106.
• the storage system 210 may comprise various databases or storage, such as, for example, a DDID storage 212 which stored a digital device identifier for the digital device 102.
• the storage system 210 comprises a plurality of modules utilized by embodiments of the present invention to access the hotspot.
• the storage system 210 comprises a network module 214, a credential engine 21 network access engine 218, and an encryption/decryption module 220.
• Alternative embodiments of the digital device 102 and/or the memory system 208 may comprise more, less, or functionally equivalent components and modules.
• the network module 214 may be configured to perform operations in order to access the local area network 106. In some embodiments, the network module 214 may receive and transmit communications associated with accessing the hotspot. The network module 214 may also perform a search for the communication network 114. For example, if the network module 214 determines that there is no access to the communication network 114, embodiments of the present invention herein may be practiced.
• the exemplary credential engine 216 is configured to obtain the network credential.
• the credential engine 216 may comprise a request module 222, a verification module 224, and a retrieval module 226.
• the exemplary request module 222 is configured to generate a credential request for the network credential.
• the credential engine 216 may also receive a credential request response (via the network module 214) and verify, via the verification module 224, that the credential request response is from the credential server 116.
• the exemplary retrieval module 226 is configured to analyze the credential request response to obtain the network credentials. The process for obtaining the network credential will be discussed in more details in connection with FIG. 4 below.
• the exemplary network access engine 218 is configured to receive an authentication request and provide an authentication response to the network device 104 comprising the network credential.
• the network access engine 218 may comprise an authentication record module 228, a field module 230, and a submit module 232.
• the exemplary authentication record module 228 is configured to identify an authentication record associated with the.digital device 102.
• the field module 230 identifies fields or elements in the authentication record and provides the proper element inputs (e.g., network credential) in the fields.
• the subrr module 232 is configured to automatically submit the authentication record to the network device 104 as the authentication response. The process for providing the authentication response is discussed in more details in connection with FIG. 5 below.
• the encryption/decryption module 220 is configured to encrypt or decrypt communications sent/received by the digital device 102.
• the credential request response may be encrypted by the credential server 116.
• the encryption/decryption module 220 will decrypt the credential request response.
• the encryption/decryption module 208 may establish a secure communication via SSL and/or https between the digital device 102 and the authentication server 108. It should be noted that, in accordance with some embodiments, the encryption/decryption module 220 may be optional or not required.
• step 302 the digital device 102 enters a hotspot.
• a user may turn on their digital device 102 in a coffee shop or hotel where communication network access (e.g., hotspot) is available.
• communication network access e.g., hotspot
• the digital device 102 may sense the hotspot.
• the network module 214 may automatically attempt to access the communication network 114.
• the network module 214 of the digital device 102 may query the network device 104 of the hotspot in step 304.
• the network device 104 comprises the access point for the hotspot.
• the network module 214 may receive one or more IP addresses associated with a central server (e.g., the DNS server 110) which may be associated with a service provider. Other information may also be received such as DNS records and gateway records.
• the IP addresses may be provided via DHCP.
• the network module 214 may attempt to access a known server to determine whether there is live connection to the communication network 114.
• the digital device 102 requests and obtains the network credential from the DNS server 110. The process of step 306 will be discussed in more details in connection with FIG. 4 below.
• the digital device 102 may provide an authentication response to the network device 104 in order to access the communication network 114 via the network device 104 in step 308.
• the process of step 308 will be discussed in more details in connection with FIG. 5 below.
• the network device 104 will then attempt to authenticate the digital device 102 by comparing the network credential received in the authentication response.
• the network device 104 may authenticate the network credential utilizing the authentication server 108.
• the network credential may be compared against a database of network credentials stored or associated with the authentication server 108.
• the digital device 102 will be granted access to the communication network in step 310.
• the authentication server 108 may instruct the access controller 112 to allow the digital device 102 access to the communication network 114.
• step 402 the network credential request is generated.
• the request module 222 may construct a string using a DNS structure that may already be on a platform of the digital device 102.
• the exemplary DNS string generated by the request module 222 is discussed in more details in connection with FIG. 8 below.
• the generated credential request is sent by the digital device 102.
• the digital device 102 utilizes one of the IP addresses (of the DNS server 110) received from the network device 104.
• the DNS string is then transmitted to the selected DNS IP address received by the network module 214.
• the digital device 102 receives the credential request response.
• the credential request response is received from the credential server 116 via the DNS server 110.
• the credential request response may be encrypted.
• the encryption/decryption module 220 will decrypt the credential request response.
• the credential request response is then verified in step 408.
• the credential request response is encrypted.
• the digital device 102 e.g., the verification module 2214 may decrypt the credential request response.
• the credential request response is digitally signed.
• the digital device 102 e.g., the verification module 224) may verify the authenticity of the credential request response by decrypting the digital signature or decrypting the credential request response.
• other mechanisms may be used by the verification module 224 to authenticate the credential request response.
• the network credentials may then be retrieved in step 410.
• the retrieval module 226 will analyze the credential request response to obtain the network credentials embedded therein.
• the retrieval module 226 identifies data within the retrieval module 226 (e.g., via delimited fields) and may retrieve a encryption key, a user name, a password, a form identifier, or the like.
• step 502 an authentication request is received from the network device 104 by the network module 214.
• the authentication record module 228 then identifies and retrieves an authentication record in step 504.
• the authentication request from the network device 104 may comprise HTML form element names associated with an authentication record in which the network credential may be provided.
• the authentication record module 228 may parse out the form(s)/authentication record(s) needed for logging in with the network device 104, for example, via the name or identifier (e.g., login form).
• the field module 230 determines field(s) or elements(s) within the authentication record that require an authentication input (e.g., network credential). According to exemplary embodiments, the field module 230 will analyze the authentication records identified and retrieved in step 504 to find input fields. As such, a list of these input fields may be generated (e.g., a linked list of forms and input fields).
• step 508 network credentials are associated with the determined field(s) or element(s).
• the field module 230 will associate a proper network credential with each input element. The association may be based on an input name or identifier found in the script of the HTML of the authentication request.
• the authentication record may comprise an input element requesting a username or an e-mail address.
• An authentication response comprising the authentication record is transmitted in step 510.
• a post is generated.
• the authentication record may comprise a plurality of hidden values used to identify the digital device 102 and session information in addition to network access credentials. Such information and values may include, for example, network device MAC address, session identifier, and other values which may be stored in hidden form elements.
• the authentication request may not be the first webpage presented by the network device 104.
• the first webpage may be a welcome webpage from the coffee shop. This welcome webpage may provide a plurality of login options.
• a unique fragment of a URL associated with the authentication request may be embedded on the first webpage.
• the digital device 102 e.g., the network module 2114 may skim t the webpage to find the fragment. Once the fragment is found, the digital device 102 will perform a get on this subsequent webpage (e.g., authentication request).
• the authentication page 600 may comprise a username field 602 and a password field 604.
• the username field 602 may be replaced with an e-mail field or any other field for providing a unique identifier associated with the digital device 102 or associated user.
• the field module 230 may automatically fill in the username field 602 and password field 604 with the network credentials.
• the authentication page 600 may also comprise an authenticate selector 606 (e.g., a submit selector or button).
• the authenticate selector 606 will submit the network credentials (e.g., user name and password) to the network device 104.
• the submit module 232 may automatically activate the authenticate selector 606 once the network credentials have been associated with their respective fields 602 and 604.
• FIG. 7 illustrates a flow diagram of an exemplary process for providing network access to the digital device 102.
• the digital device 102 e.g., network module 214
• the network device 104 may provide network configuration information in step 702.
• the network configuration information may comprise one or more IP address for access to the DNS server 110.
• a credential request is generated by the digital device 102.
• the request module 222 may generate the credential request.
• the credential request is sent to the DNS server 110 in step 706 using one of the IP addresses previously received from the network device 104.
• the credential server 116 is identified by the DNS server 110 in step 708.
• the credential server 116 then identifies the network credential needed based on the credential request in step 712.
• the credential request may comprise a unique identifier for the digital device 102. This unique identifier along with the location identifier may be compared against a table of such identifiers at the credential server 116 to determine the proper network credential.
• a credential request response is then generated in step 714 and sent back to the DNS server 110 in step 716.
• the DNS server 110 forwards the credential request response back to the digital device in step 718.
• the digital device 102 may then retrieve the network credentials from the credential request response in step 720.
• the retrieval module 226 will analyze the credential request response to retrieve the network credential embedded therein.
• the network credential may then be provided to the network device 104 in step 722.
• An exemplary method for providing the network credentials to the network device 104 is discussed in connection "with FIG. 5 above.
• the network device 104 Upon verifying the network credentials, the network device 104 provides network access to the digital device 102 in step 724.
• the request module 222 may generate the credential request 800.
• the credential request 800 may be a DNS string having a structure that comprise a location identifier 802, a sequence identifier 804, a signature 806, a digital device identifier (DDID) 808, a service set identifier (SSID) 810, and a version identifier 812.
• DDID digital device identifier
• SSID service set identifier
• the optional location identifier 802 may indicate a physical or geographic location of the digital device 102, the network device 104, the authentication server 108, or the access controller 112. In various embodiments, the location identifier 402 may be used by the credential server 116 to track the usage of hotspots, users of the digital device 102, as well as the digital device 102.
• the sequence identifier 804 may comprise any number or set of numbers used to correspond to a subsequent request to the credential server 116 to determine if the login is successful. That is, the sequence identifier 804 provides a correlation mechanism by which verification of the login process may be made by the credential server 116.
• the signature 806 comprises a cryptographic signature that is utilized to prevent spoofing.
• the signature 406 of the request from digital device 102 is verified by the credential server 116. If the signature 406 is not valid, then the request is rejected by the credential server 116.
• the DDID 808 comprises a unique identifier of the digital device 102.
• the DDID 808 may comprise a MAC address or any other universally unique identifier of the digital device 102.
• the DDID is retrieved from the DDID storage 212.
• the SSID 810 comprises an identifier of the network access point or Wi- Fi service provider.
• the SSID 810 may comprise the name of the service provider, or the name of the venue operating the network device 104.
• the version identifier 812 may identify the protocol or format of the credential request 800.
• a digital device may generate the credential request 800 and organize the data in a number of different formats. Each different format may be associated with a different version identifier.
• the components of the credential engine 216 and the network access engine 218 may be updated, reconfigured, or altered over time, which may affect the structure of the credential request 800.
• the credential server 116 may receive a plurality of credential requests 800 which are formatted differently. The credential server 116 may access the required information from each credential request based on the respective version identifier.
• the above-described functions and components can be comprised of instructions that are stored on a storage medium.
• the instructions can be retrieved and executed by a processor.
• Some examples of instructions are software, program code, and firmware.
• Some examples of storage medium are memory devices, tape, disks, integrated circuits, and servers.
• the instructions are operational when executed by the processor to direct the processor to operate in accord with embodiments of the present invention. Those skilled in the art are familiar with instructions, processor(s), and storage medium.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Security & Cryptography (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Computer Hardware Design (AREA)
• Computing Systems (AREA)
• General Engineering & Computer Science (AREA)
• Mobile Radio Communication Systems (AREA)
• Telephonic Communication Services (AREA)
• Data Exchanges In Wide-Area Networks (AREA)
• Storage Device Security (AREA)
• Information Transfer Between Computers (AREA)

Applications Claiming Priority (2)

Publications (2)

Family

ID=39157841

Family Applications (3)

Family Applications Before (1)

Family Applications After (1)

Country Status (3)

Families Citing this family (12)

Citations (3)

Family Cites Families (12)

• 2007
  • 2007-09-06 WO PCT/US2007/019463 patent/WO2008030526A2/en active Application Filing
  • 2007-09-06 JP JP2009527410A patent/JP5368307B2/ja not_active Expired - Fee Related
  • 2007-09-06 WO PCT/US2007/019462 patent/WO2008030525A2/en active Application Filing
  • 2007-09-06 EP EP07837822A patent/EP2062129A4/de not_active Withdrawn
  • 2007-09-06 EP EP07837823A patent/EP2062130A4/de not_active Withdrawn
  • 2007-09-06 JP JP2009527412A patent/JP5276593B2/ja not_active Expired - Fee Related
  • 2007-09-06 JP JP2009527411A patent/JP5276592B2/ja not_active Expired - Fee Related
  • 2007-09-06 EP EP07837824A patent/EP2060050A4/de not_active Withdrawn
  • 2007-09-06 WO PCT/US2007/019464 patent/WO2008030527A2/en active Application Filing

Patent Citations (3)

Non-Patent Citations (2)

Also Published As

Similar Documents

Legal Events