EP4229892A1 - Enhanced mechanism for out-of-band activation and provisioning of mobile devices for openroaming networks - Google Patents

Enhanced mechanism for out-of-band activation and provisioning of mobile devices for openroaming networks

Info

Publication number
EP4229892A1
EP4229892A1 EP21881204.8A EP21881204A EP4229892A1 EP 4229892 A1 EP4229892 A1 EP 4229892A1 EP 21881204 A EP21881204 A EP 21881204A EP 4229892 A1 EP4229892 A1 EP 4229892A1
Authority
EP
European Patent Office
Prior art keywords
openroaming
idp
profile
idps
circuitry
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
EP21881204.8A
Other languages
German (de)
French (fr)
Other versions
EP4229892A4 (en
Inventor
Necati Canpolat
Seemab KADRI
Muthaiah Venkatachalam
Ofer Hareuveni
Ido Ouzieli
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corp filed Critical Intel Corp
Publication of EP4229892A1 publication Critical patent/EP4229892A1/en
Publication of EP4229892A4 publication Critical patent/EP4229892A4/en
Pending legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0823Network architectures or network communication protocols for network security for authentication of entities using certificates
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0892Network architectures or network communication protocols for network security for authentication of entities by using authentication-authorization-accounting [AAA] servers or protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1069Session establishment or de-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40Support for services or applications
    • H04L65/401Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
    • H04L65/4015Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference where at least one of the additional parallel sessions is real time or time sensitive, e.g. white board sharing, collaboration or spawning of a subconference
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06Authentication
    • H04W12/069Authentication using certificates or pre-shared keys
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W12/00Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30Security of mobile devices; Security of mobile applications
    • H04W12/35Protecting application or service provisioning, e.g. securing SIM application provisioning
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10Small scale networks; Flat hierarchical networks
    • H04W84/12WLAN [Wireless Local Area Networks]

Definitions

  • This disclosure generally relates to systems and methods for wireless communications and, more particularly, to a mechanism for out-of-band activation and provisioning of mobile devices for OpenRoaming networks.
  • Wireless devices are becoming widely prevalent and are increasingly requesting access to wireless channels.
  • the Institute of Electrical and Electronics Engineers (IEEE) is developing one or more standards that utilize Orthogonal Frequency-Division Multiple Access (OFDMA) in channel allocation.
  • OFDMA Orthogonal Frequency-Division Multiple Access
  • FIG. 1 is a network diagram illustrating an example network environment for out-of-band activation and provisioning, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 2 depicts an illustrative schematic architecture and device association using OpenRoaming, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 3 depicts an illustrative process for device pre-provisioning using OpenRoaming, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 4 depicts an illustrative schematic architecture and device association using OpenRoaming with multiple different identity providers (IDPs), in accordance with one or more example embodiments of the present disclosure.
  • IDPs identity providers
  • FIG. 5 depicts an illustrative process for device pre-provisioning using OpenRoaming and multiple different IDPs, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 6 illustrates a flow diagram of illustrative process for an out-of-band activation and provisioning system, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7 illustrates a functional diagram of an exemplary communication station that may be suitable for use as a user device, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 8 illustrates a block diagram of an example machine upon which any of one or more techniques (e.g., methods) may be performed, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 9 is a block diagram of a radio architecture in accordance with some examples.
  • FIG. 10 illustrates an example front-end module circuitry for use in the radio architecture of FIG. 9, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 11 illustrates an example radio IC circuitry for use in the radio architecture of FIG. 9, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 12 illustrates an example baseband processing circuitry for use in the radio architecture of FIG. 9, in accordance with one or more example embodiments of the present disclosure.
  • OpenRoaming refers to a global Wi-Fi network of Wi-Fi networks where mobile devices can automatically and securely connect.
  • Wi-Fi access network providers may include retailers, restaurants, enterprises, Internet service providers, and the like.
  • APNs Wi-Fi access network providers
  • Wi-Fi networks may become unavailable, while other Wi-Fi networks may become available.
  • the device may be presented with the option to join the other Wi-Fi network.
  • Wi-Fi mobility lacks the cellular concept of roaming, in which a device that is outside of a coverage area of a cellular provider automatically may access a network provided by a different cellular provider (e.g., due to agreements in place between the cellular providers). Accordingly, the processes for a mobile device to switch to different Wi-Fi access networks as the device changes locations are more cumbersome than cellular roaming techniques.
  • OpenRoaming is a mechanism for allowing Wi-Fi-enabled devices to join Wi-Fi access networks without the need to re-register and re-enter credentials each time.
  • OpenRoaming addresses the challenges of Wi-Fi roaming by bringing together ANPs and identity providers (IDPs) under a public key infrastructure (PKI)-based trust model.
  • IDPs identity providers
  • PKI public key infrastructure
  • An ANP may securely connect with IDPs using the PKI model under OpenRoaming.
  • OpenRoaming creates an automatic plug-and-play architecture through a cloud-based roaming framework using PKI.
  • An IDP goes thru IDP onboarding process with OpenRoaming cloud, and it also registers with OpenRoaming domain name service (DNS) for auto-discovery.
  • DNS OpenRoaming domain name service
  • an OpenRoaming connector supports ANP onboarding to the OpenRoaming cloud.
  • a mobile client device e.g., station device
  • ANP queries the OpenRoaming DNS to find out where to route the authentication.
  • the client device automatically may identify and join Wi-Fi networks available at any physical location through use of the OpenRoaming profile.
  • the present disclosure defines an out-of-band mechanism for OpenRoaming account activation and provisioning of mobile devices to enable an out-of-box OpenRoaming ready solution.
  • Hotspot 2.0 Online Sign Up has not scaled up over ten years due to deployment complexity and device implementation challenges.
  • Captive portal mechanism is a manual process with tedious use involvements.
  • Example embodiments of the present disclosure relate to systems, methods, and devices for a mechanism for out-of-band activation and provisioning of mobile devices for OpenRoaming networks.
  • an application on a client device e.g., station device
  • a SIM card e.g., such as a laptop, tablet, or smartphone without a cellular SIM card
  • an OpenRoaming provisioning portal may generate OpenRoaming profiles based on IDP-provided tokens, and may provision the profile on the client device.
  • the client device may establish an account using OpenRoaming provisioning (e.g., using a web-based provisioning portal).
  • the client device may receive a list of available IDPs from the web-based provisioning portal, and may select an IDP with which to establish OpenRoaming account. If the user has already established account with the IDP, it can be used for OpenRoaming. If not, user goes through and account establishment with the IDSP (e.g., username, password, and/or certificate).
  • IDSP e.g., username, password, and/or certificate.
  • the OpenRoaming profile of the client device may be provisioned for future connection, allowing the client device to automatically join Wi-Fi OpenRoaming networks (e.g., in the background of the client device without requiring user inputs) because the OpenRoaming profile may be used to discover the OpenRoaming networks and dynamically identify the IDP that will perform the authentication. .
  • the client device may connect to the ANP’s network using the OpenRoaming profile because the ANP identifies the IDP through OpenRoaming DNS, and it forwards the authentication to the IDP (e.g., using Remote Authentication Dial-In User Service - Radius - RADSec).
  • the client device may be granted access to the Internet.
  • OpenRoaming provisioning portal provides oAuth support for IDPs interested in joining OpenRoaming and the portal interfaces between the mobile device and IDPs to get authorization token from IDS and provision the OpenRoaming profile on the mobile device for future connections.
  • an out-of-band activation and provisioning system may enable an end-to-end out-of-box mobile device OpenRoaming readiness capability and user experience by: Pre-configuring the devices for activation, enabling a provisioning Web Server for account activation and establishment, routing the provisioning to participating IDPs, provisioning devices when the system has a network access, and facilitating out-of-box provisioning of devices when the system has network access.
  • the proposed solutions herein may be integrated in mobile devices to enable seamless, simple Wi-Fi connectivity and roaming capability using OpenRoaming. The above descriptions are for purposes of illustration and are not meant to be limiting. Numerous other examples, configurations, processes, algorithms, etc., may exist, some of which are described in greater detail below. Example embodiments will now be described with reference to the accompanying figures.
  • FIG. 1 is a network diagram illustrating an example network environment of out-of-band activation and provisioning for OpenRoaming, according to some example embodiments of the present disclosure.
  • Wireless network 100 may include one or more user devices 120 and one or more access points(s) (AP) 102, which may communicate in accordance with IEEE 802.11 communication standards.
  • the user device(s) 120 may be mobile devices that are non- stationary (e.g., not having fixed locations) or may be stationary devices.
  • the user devices 120 and the AP 102 may include one or more computer systems similar to that of the functional diagram of FIG. 7 and/or the example machine/system of FIG. 8.
  • One or more illustrative user device(s) 120 and/or AP(s) 102 may be operable by one or more user(s) 110. It should be noted that any addressable unit may be a station (STA). An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of-service (QoS) STA, a dependent STA, and a hidden STA. The one or more illustrative user device(s) 120 and the AP(s) 102 may be STAs.
  • STA station
  • An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of-service (QoS) STA, a dependent STA, and a hidden STA.
  • QoS quality-of-service
  • the one or more illustrative user device(s) 120 and/or AP(s) 102 may operate as a personal basic service set (PBSS) control point/access point (PCP/AP).
  • PBSS personal basic service set
  • PCP/AP control point/access point
  • the user device(s) 120 (e.g., 124, 126, or 128) and/or AP(s) 102 may include any suitable processor- driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static device.
  • user device(s) 120 and/or AP(s) 102 may include, a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabookTM computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (loT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA
  • the term “Internet of Things (loT) device” is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection.
  • An loT device may have a passive communication interface, such as a quick response (QR) code, a radiofrequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like.
  • QR quick response
  • RFID radiofrequency identification
  • An loT device can have a particular set of attributes (e.g., a device state or status, such as whether the loT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an loT network such as a local ad-hoc network or the Internet.
  • a device state or status such as whether the loT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.
  • loT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the loT network.
  • loT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc.
  • the loT network may be comprised of a combination of “legacy” Internet- accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.).
  • “legacy” Internet- accessible devices e.g., laptop or desktop computers, cell phones, etc.
  • devices that do not typically have Internet-connectivity e.g., dishwashers, etc.
  • the user device(s) 120 and/or AP(s) 102 may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3 GPP standards.
  • Any of the user device(s) 120 may be configured to communicate with each other via one or more communications networks 130 and/or 135 wirelessly or wired.
  • the user device(s) 120 may also communicate peer-to-peer or directly with each other with or without the AP(s) 102.
  • Any of the communications networks 130 and/or 135 may include, but not limited to, any one of a combination of different types of suitable communications networks such as, for example, broadcasting networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and/or public networks.
  • any of the communications networks 130 and/or 135 may have any suitable communication range associated therewith and may include, for example, global networks (e.g., the Internet), metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), or personal area networks (PANs).
  • any of the communications networks 130 and/or 135 may include any type of medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, microwave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof.
  • coaxial cable twisted-pair wire
  • optical fiber a hybrid fiber coaxial (HFC) medium
  • microwave terrestrial transceivers microwave terrestrial transceivers
  • radio frequency communication mediums white space communication mediums
  • ultra-high frequency communication mediums satellite communication mediums, or any combination thereof.
  • Any of the user device(s) 120 (e.g., user devices 124, 126, 128) and AP(s) 102 may include one or more communications antennas.
  • the one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the user device(s) 120 (e.g., user devices 124, 126 and 128), and AP(s) 102.
  • suitable communications antennas include Wi-Fi antennas, Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi- omnidirectional antennas, or the like.
  • the one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the user devices 120 and/or AP(s) 102.
  • Any of the user device(s) 120 may be configured to perform directional transmission and/or directional reception in conjunction with wirelessly communicating in a wireless network.
  • Any of the user device(s) 120 e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform such directional transmission and/or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays or the like). Each of the multiple antenna arrays may be used for transmission and/or reception in a particular respective direction or range of directions.
  • Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional transmission towards one or more defined transmit sectors. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional reception from one or more defined receive sectors.
  • MIMO beamforming in a wireless network may be accomplished using RF beamforming and/or digital beamforming.
  • user devices 120 and/or AP(s) 102 may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming.
  • any of the user devices 120 may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the user device(s) 120 and AP(s) 102 to communicate with each other.
  • the radio components may include hardware and/or software to modulate and/or demodulate communications signals according to pre-established transmission protocols.
  • the radio components may further have hardware and/or software instructions to communicate via one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards.
  • the radio component in cooperation with the communications antennas, may be configured to communicate via 2.4 GHz channels (e.g. 802.11b, 802.11g, 802.1 In, 802.1 lax), 5 GHz channels (e.g. 802.1 In, 802.1 lac, 802.1 lax), or 60 GHZ channels (e.g. 802. Had, 802. Hay). 800 MHz channels (e.g. 802.11ah).
  • the communications antennas may operate at 28 GHz and 40 GHz. It should be understood that this list of communication channels in accordance with certain 802.11 standards is only a partial list and that other 802.11 standards may be used (e.g., Next Generation Wi-Fi, or other standards).
  • non-Wi-Fi protocols may be used for communications between devices, such as Bluetooth, dedicated short-range communication (DSRC), Ultra- High Frequency (UHF) (e.g. IEEE 802.1 laf, IEEE 802.22), white band frequency (e.g., white spaces), or other packetized radio communications.
  • the radio component may include any known receiver and baseband suitable for communicating via the communications protocols.
  • the radio component may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, and digital baseband.
  • LNA low noise amplifier
  • A/D analog-to-digital
  • OpenRoaming may be performed according to FIGs. 2-6, using an OpenRoaming provisioning system 150.
  • the OpenRoaming provisioning system 150 may provision and automatically connect the one or more user devices 120 to Wi-Fi networks (e.g., a Wi-Fi network provided by the AP 102).
  • FIG. 2 depicts an illustrative schematic architecture and device association 200 using OpenRoaming, in accordance with one or more example embodiments of the present disclosure.
  • user devices 202 may connect to an OpenRoaming Wi-Fi network provided by an ANP 204.
  • the ANP 204 may exchange ANP onboarding data 206 with an OpenRoaming cloud 208, which may communicate with one or more IDPs 210.
  • the OpenRoaming cloud 208 and the one or more IDPs 210 may exchange IDP onboarding data 212.
  • the one or more IDPs 210 also may provide IDP registration data 213 to a DNS server 214 for future identification.
  • the ANP 204 may query DNS for IDP discoverya 216. As explained further below with respect to FIG.
  • the ANP 204 may authenticate 218 the user devices 202 to the one of the OpenRoaming IDPs 210 by using a provisioned OpenRoaming profile of the user devices 202 and selected IDPs of the one or more IDPs 210 as identified based on the IDP registration data 213.
  • the OpenRoaming cloud 208 may connect ANPs to IDPs so to provide OpenRoaming in which the user devices 202 may connect automatically to Wi-Fi networks.
  • the OpenRoaming provisioning system 150 of FIG. 1 may include at least some of the architecture shown in FIG. 2.
  • the user devices 202 may be pre-configured with an OpenRoaming activation flag. During a system set up, or when the user devices 202 are connected to the Internet, the user devices 202 may present a user prompt to a user to activate OpenRoaming. When OpenRoaming is activated on the user devices 202, an OpenRoaming web server (e.g., as shown in FIG. 3) may be enabled for OpenRoaming activation and account establishment.
  • an OpenRoaming web server e.g., as shown in FIG. 3
  • the user devices 202 may accept terms and conditions for OpenRoaming, and may allow a user to provide a username, password, and/or certificate, along with any other account details, to generate a user-specific OpenRoaming profile with which the user devices 202 may be provisioned.
  • the user devices 202 may use the provisioned OpenRoaming profile to establish future Wi-Fi connections.
  • FIG. 3 depicts an illustrative process 300 for device pre-provisioning using OpenRoaming, in accordance with one or more example embodiments of the present disclosure.
  • the process 300 may include a client device 302 (e.g., similar to the user devices 202 of FIG. 2), an ANP 304, the Internet 306, a DNS server 308, an OpenRoaming web server 310, and one or more IDPs 312.
  • a pre-provisioning process 318 for the client device 302 may include the client device 302 establishing Internet access 320 with the Internet 306.
  • the client device 302 may establish an OpenRoaming account by using the Internet 306 to access the OpenRoaming web server 310, which may display an IDP list 322 (e.g., of the one or more IDPs 312, as established based on the IDP registration data 213 of FIG. 2).
  • the client device 302 may select one or more of the IDPs presented as available.
  • the client device 302 may be directed to the selected IDP of the one or more IDPs 312, where the client device 302 and the one of the IDPs 312 may establish an OpenRoaming account 326 (e.g., a username and password, and/or certificate).
  • an OpenRoaming profile 326 may be generated and installed on the client device 302 for the selected IDP, and provisioned for establishing a future Wi-Fi connection.
  • the client device 302 may join an OpenRoaming ANP 328 Wi-Fi network, and the ANP 304 may look up, at the DNS server 308, the address 330 of the IDP used in the OpenRoaming account 326. Once the ANP 304 identifies the IDP address 330, the ANP 304 may perform extensible authentication protocol (EAP) authentication with the IDP 312. As a result, the client device 302 may be granted network access to the Internet 306.
  • EAP extensible authentication protocol
  • the pre -pro visioning process 318 may set an OpenRoaming activation flag on the client device 302.
  • a device identifier of the client device 302 may be used to establish the OpenRoaming account 326.
  • the OpenRoaming web server 310 may verify the device identifier, display the terms and conditions of the OpenRoaming, and the user of the client device 302 may accept the terms and conditions.
  • the OpenRoaming web server 310 may redirect the account activation/establishment to the selected IDP.
  • the client device 302 may provide the username and password, along with contact or other account information, and the IDP may generate the OpenRoaming profile 326 for the user and may install the OpenRoaming profile 326 on the client device 302 (e.g., using operating system- provided application programming interfaces, etc.).
  • the client device 302 may be ready for OpenRoaming “out-of- the box.”
  • the WiFi connection may be established using the OpenRoaming account 326 automatically.
  • the client device 302 may identify an OpenRoaming Wi-Fi network, and the client device 302 may perform authentication and association using the OpenRoaming ANP 304, without the need for user interaction, as the ANP 304 may route the authentication to the specified IDP of the OpenRoaming account 326.
  • the IDP may authenticate the user based on the OpenRoaming account 326, allowing the client device 302 to access the Wi-Fi network provided by the ANP 304 without the user needing to select the network and provide credentials. In this manner, when a user purchases a new device (e.g., without a SIM card), the device is ready for OpenRoaming activation and out-of-band provisioning.
  • a new device e.g., without a SIM card
  • FIG. 4 depicts an illustrative schematic architecture and device association 400 using OpenRoaming with multiple different IDPs, in accordance with one or more example embodiments of the present disclosure.
  • the schematic architecture of FIG. 2 may be modified to support multiple IDPs, including IDPs that can and cannot perform OpenRoaming provisioning.
  • Part of the OpenRoaming provisioning may be supported in the user devices 202, and part may be implemented in the OpenRoaming provisioning web portal 402.
  • a web portal 402 e.g., having oAuth support
  • provisioning may allow for IDPs without provisioning capabilities, but having oAuth authentication, may be supported.
  • the user devices 202 may be re-directed (e.g., by an application) to the web portal 402.
  • the provisioning process may be re-directed (e.g., via the web portal 402) to the IDP to provision the OpenRoaming account 326 of FIG. 3 (e.g., using an application programming interface).
  • the web portal 402 may authenticate 406 (e.g., using oAuth) to the IDPs without provisioning capabilities.
  • the web portal 402 may obtain an authorized oAuth token, and may generate an OpenRoaming profile (the OpenRoaming account 326) using the authorized token, then may provision the OpenRoaming profile on the user devices 202.
  • the OpenRoaming provisioning system 150 of FIG. 1 may include at least some of the architecture shown in FIG. 4.
  • the user devices 202 may use a provisioning application to establish an OpenRoaming activation flag during an operating system setup or update.
  • the application may determine whether an OpenRoaming profile has been established for the user devices 202. If so, the activation may be skipped.
  • the application may trigger OpenRoaming activation by prompting a user to enable OpenRoaming.
  • the application may re-direct the user devices 202 to the web portal 402 for the provisioning process.
  • the provisioning web portal 402 may display the OpenRoaming terms and conditions to the user devices 202, and when accepted by a user, the OpenRoaming cloud 208 may display the OpenRoaming IDP list to the user devices 202.
  • the web portal 402 may initiate the oAuth process with the selected IDP.
  • the web portal 402 re-directs the user devices 202 to the provisioning portal of the selected IDP, where the user devices 202 may provide credentials (e.g., username and password), and the IDP portal may generate and provision the OpenRoaming profile on the user devices 202.
  • the provisioning process for multiple different IDPs is shown in FIG. 5.
  • FIG. 5 depicts an illustrative process 500 for device pre-provisioning using OpenRoaming and multiple different IDPs, in accordance with one or more example embodiments of the present disclosure.
  • the process 500 may include a client device 502 (e.g., similar to the user devices 202 of FIG. 2), an ANP 504, the Internet 506, a DNS server 508, an OpenRoaming web server 510, and two or more IDPs 512.
  • a pre-provisioning process 518 for the client device 502 may include the client device 502 establishing Internet access 520 with the Internet 506.
  • the client device 502 may establish an OpenRoaming account by using the Internet 506 to access the OpenRoaming web server 510, which may display an IDP list 522 (e.g., of the two or more IDPs 512, as established based on the IDP registration data 213 of FIG. 2).
  • the client device 502 may select one or more of the IDPs presented as available.
  • the client device 502 may be re-directed 525 to the provisioning portal of the selected IDP of the one or more IDPs 512, where the client device 502 and the selected IDP may establish an OpenRoaming account 526 (e.g., a username and password).
  • the OpenRoaming profile 326 may be installed on the client device 502 for the IDP, and provisioned for establishing a future Wi-Fi connection.
  • the selected IDP may provide an authorization token to the web server 510 to be used to authorize the user (e.g., using oAuth) by generating a profile (e.g., the OpenRoaming account 326 of FIG. 3) with the token at step 530.
  • the web server 510 may install the OpenRoaming profile on the client device 502 for the IDP (e.g., using an operating system application programming interface for delivery).
  • the client device 502 may join an OpenRoaming ANP 540 Wi-Fi network, and the ANP 504 may look up, at the DNS server 508, the address 550 of the IDP used in the OpenRoaming profile 326. Once the ANP 504 identifies the IDP address 550, the mobile device 502 may perform EAP authentication with the IDP. The IDP 502 then may signal the ANP 504 about the successful authentication of the device 502). As a result, the client device 502 may be granted network access to the Internet 506.
  • FIG. 6 illustrates a flow diagram of illustrative process 600 for an out-of-band activation and provisioning system, in accordance with one or more example embodiments of the present disclosure.
  • a device e.g., the user device(s) 120 and/or the AP 102 of FIG. 1, the user devices 202 of FIG. 2, the OpenRoaming cloud 208 of FIG. 2, the client device 302 of FIG. 3, the web server 310 of FIG. 3, the client device 502 of FIG. 5, and/or the web server 510 of FIG. 5) may determine that a client device (e.g., a client device not having a cellular SIM) may have an Internet connection.
  • the client device may have a provisioning application for OpenRoaming that determines when the client device has an Internet connection.
  • the device may activate an OpenRoaming process based on the detected Internet connection.
  • the client device application may redirect the client device to the device for OpenRoaming device provisioning.
  • the device may present to the client device a list of IDPs available for selection and with which to generate an OpenRoaming profile.
  • the device may receive, from the client device, a user selection of an IDP from the list of IDPs.
  • the client device may be re-directed by the device to the provisioning portal of the selected IDP of the one or more IDPs at block 610 (e.g., an optional step depending on whether the selected IDP has a provisioning capability for OpenRoaming).
  • the selected IDP may provide an authorization token to the device to be used to authorize the user (e.g., using oAuth) by generating a profile (e.g., the OpenRoaming account 326 of FIG. 3) with the token at block 612.
  • the device or the IDP portal may generate the OpenRoaming profile for the client device.
  • the client device receives a user selection of an IDP with a provisioning capability
  • the client device and the selected IDP may establish an OpenRoaming account (e.g., a username and password).
  • the device may install the OpenRoaming profile on the client device to be provisioned for establishing a future Wi-Fi connection.
  • FIG. 7 shows a functional diagram of an exemplary communication station 700, in accordance with one or more example embodiments of the present disclosure.
  • FIG. 7 illustrates a functional block diagram of a communication station that may be suitable for use as an AP 102 (FIG. 1) or a user device 120 (FIG. 1) in accordance with some embodiments.
  • the communication station 700 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.
  • HDR high data rate
  • the communication station 700 may include communications circuitry 702 and a transceiver 710 for transmitting and receiving signals to and from other communication stations using one or more antennas 701.
  • the communications circuitry 702 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals.
  • the communication station 700 may also include processing circuitry 706 and memory 708 arranged to perform the operations described herein.
  • the communications circuitry 702 and the processing circuitry 706 may be configured to perform operations detailed in the above figures, diagrams, and flows.
  • the communications circuitry 702 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium.
  • the communications circuitry 702 may be arranged to transmit and receive signals.
  • the communications circuitry 702 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc.
  • the processing circuitry 706 of the communication station 700 may include one or more processors.
  • two or more antennas 701 may be coupled to the communications circuitry 702 arranged for sending and receiving signals.
  • the memory 708 may store information for configuring the processing circuitry 706 to perform operations for configuring and transmitting message frames and performing the various operations described herein.
  • the memory 708 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer).
  • the memory 708 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flashmemory devices and other storage devices and media.
  • the communication station 700 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • PDA personal digital assistant
  • laptop or portable computer with wireless communication capability such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
  • the communication station 700 may include one or more antennas 701.
  • the antennas 701 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals.
  • a single antenna with multiple apertures may be used instead of two or more antennas.
  • each aperture may be considered a separate antenna.
  • MIMO multiple-input multiple-output
  • the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.
  • the communication station 700 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements.
  • the display may be an LCD screen including a touch screen.
  • the communication station 700 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • DSPs digital signal processors
  • some elements may include one or more microprocessors, DSPs, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio- frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements of the communication station 700 may refer to one or more processes operating on one or more processing elements.
  • Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein.
  • a computer-readable storage device may include any non-transitory memory mechanism for storing information in a form readable by a machine (e.g., a computer).
  • a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media.
  • the communication station 700 may include one or more processors and may be configured with instructions stored on a computer-readable storage device.
  • FIG. 8 illustrates a block diagram of an example of a machine 800 or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed.
  • the machine 800 may operate as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine 800 may operate in the capacity of a server machine, a client machine, or both in server-client network environments.
  • the machine 800 may act as a peer machine in peer- to-peer (P2P) (or other distributed) network environments.
  • P2P peer- to-peer
  • the machine 800 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a wearable computer device, a web appliance, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station.
  • PC personal computer
  • PDA personal digital assistant
  • STB set-top box
  • mobile telephone a wearable computer device
  • web appliance e.g., a web appliance
  • network router e.g., a network router, a switch or bridge
  • any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station.
  • the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (Sa
  • Examples, as described herein, may include or may operate on logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations when operating.
  • a module includes hardware.
  • the hardware may be specifically configured to carry out a specific operation (e.g., hardwired).
  • the hardware may include configurable execution units (e.g., transistors, circuits, etc.) and a computer readable medium containing instructions where the instructions configure the execution units to carry out a specific operation when in operation. The configuring may occur under the direction of the executions units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is operating.
  • the execution units may be a member of more than one module.
  • the execution units may be configured by a first set of instructions to implement a first module at one point in time and reconfigured by a second set of instructions to implement a second module at a second point in time.
  • the machine 800 may include a hardware processor 802 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 804 and a static memory 806, some or all of which may communicate with each other via an interlink (e.g., bus) 808.
  • the machine 800 may further include a power management device 832, a graphics display device 810, an alphanumeric input device 812 (e.g., a keyboard), and a user interface (UI) navigation device 814 (e.g., a mouse).
  • the graphics display device 810, alphanumeric input device 812, and UI navigation device 814 may be a touch screen display.
  • the machine 800 may additionally include a storage device (i.e., drive unit) 816, a signal generation device 818 (e.g., a speaker), an enhanced OpenRoaming device 819, a network interface device/transceiver 820 coupled to antenna(s) 830, and one or more sensors 828, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor.
  • a storage device i.e., drive unit
  • a signal generation device 818 e.g., a speaker
  • an enhanced OpenRoaming device 819 e.g., a network interface device/transceiver 820 coupled to antenna(s) 830
  • sensors 828 such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor.
  • GPS global positioning system
  • the machine 800 may include an output controller 834, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)).
  • IR infrared
  • NFC near field communication
  • peripheral devices e.g., a printer, a card reader, etc.
  • the operations in accordance with one or more example embodiments of the present disclosure may be carried out by a baseband processor.
  • the baseband processor may be configured to generate corresponding baseband signals.
  • the baseband processor may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with the hardware processor 802 for generation and processing of the baseband signals and for controlling operations of the main memory 804, the storage device 816, and/or the enhanced OpenRoaming device 819.
  • the baseband processor may be provided on a single radio card, a single chip, or an integrated circuit (IC).
  • the storage device 816 may include a machine readable medium 822 on which is stored one or more sets of data structures or instructions 824 (e.g., software) embodying or utilized by any one or more of the techniques or fimctions described herein.
  • the instructions 824 may also reside, completely or at least partially, within the main memory 804, within the static memory 806, or within the hardware processor 802 during execution thereof by the machine 800.
  • one or any combination of the hardware processor 802, the main memory 804, the static memory 806, or the storage device 816 may constitute machine- readable media.
  • the enhanced OpenRoaming device 819 may carry out or perform any of the operations and processes (e.g., process 600) described and shown above (e.g., in FIGs. 2-6).
  • machine-readable medium 822 is illustrated as a single medium, the term “machine-readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 824.
  • machine-readable medium may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 824.
  • Various embodiments may be implemented fully or partially in software and/or firmware.
  • This software and/or firmware may take the form of instructions contained in or on a non- transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein.
  • the instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like.
  • Such a computer- readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc.
  • machine-readable medium may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 800 and that cause the machine 800 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding, or carrying data structures used by or associated with such instructions.
  • Non-limiting machine-readable medium examples may include solid-state memories and optical and magnetic media.
  • a massed machine-readable medium includes a machine-readable medium with a plurality of particles having resting mass.
  • massed machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD- ROM disks.
  • semiconductor memory devices e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)
  • EPROM electrically programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • the instructions 824 may further be transmitted or received over a communications network ZZ26 using a transmission medium via the network interface device/transceiver ZZ20 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).
  • transfer protocols e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.
  • Example communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), plain old telephone (POTS) networks, wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, among others.
  • the network interface device/transceiver ZZ20 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 826.
  • the network interface device/transceiver 820 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multipleinput multiple-output (MIMO), or multiple-input single-output (MISO) techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine 800 and includes digital or analog communications signals or other intangible media to facilitate communication of such software.
  • the operations and processes described and shown above may be carried out or performed in any suitable order as desired in various implementations. Additionally, in certain implementations, at least a portion of the operations may be carried out in parallel. Furthermore, in certain implementations, less than or more than the operations described may be performed.
  • FIG. 9 is a block diagram of a radio architecture 105 A, 105B in accordance with some embodiments that may be implemented in any one of the example APs 102 and/or the example user devices 120 of FIG. 1.
  • Radio architecture 105 A, 105B may include radio front-end module (FEM) circuitry 904a-b, radio IC circuitry 906a-b and baseband processing circuitry 908a-b.
  • FEM radio front-end module
  • Radio architecture 105 A, 105B as shown includes both Wireless Local Area Network (WLAN) functionality and Bluetooth (BT) functionality although embodiments are not so limited.
  • WLAN Wireless Local Area Network
  • BT Bluetooth
  • the FEM circuitry 904a-b may include a WLAN or Wi-Fi FEM circuitry 904a and a Bluetooth (BT) FEM circuitry 904b.
  • the WLAN FEM circuitry 904a may include a receive signal path comprising circuitry configured to operate on WLAN RF signals received from one or more antennas 901, to amplify the received signals and to provide the amplified versions of the received signals to the WLAN radio IC circuitry 906a for further processing.
  • the BT FEM circuitry 904b may include a receive signal path which may include circuitry configured to operate on BT RF signals received from one or more antennas 901, to amplify the received signals and to provide the amplified versions of the received signals to the BT radio IC circuitry 906b for further processing.
  • FEM circuitry 904a may also include a transmit signal path which may include circuitry configured to amplify WLAN signals provided by the radio IC circuitry 906a for wireless transmission by one or more of the antennas 901.
  • FEM circuitry 904b may also include a transmit signal path which may include circuitry configured to amplify BT signals provided by the radio IC circuitry 906b for wireless transmission by the one or more antennas.
  • FIG. 1 In the embodiment of FIG.
  • FEM 904a and FEM 904b are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of an FEM (not shown) that includes a transmit path and/or a receive path for both WLAN and BT signals, or the use of one or more FEM circuitries where at least some of the FEM circuitries share transmit and/or receive signal paths for both WLAN and BT signals.
  • Radio IC circuitry 906a-b as shown may include WLAN radio IC circuitry 906a and BT radio IC circuitry 906b.
  • the WLAN radio IC circuitry 906a may include a receive signal path which may include circuitry to down-convert WLAN RF signals received from the FEM circuitry 904a and provide baseband signals to WLAN baseband processing circuitry 908a.
  • BT radio IC circuitry 906b may in turn include a receive signal path which may include circuitry to downconvert BT RF signals received from the FEM circuitry 904b and provide baseband signals to BT baseband processing circuitry 908b.
  • WLAN radio IC circuitry 906a may also include a transmit signal path which may include circuitry to up-convert WLAN baseband signals provided by the WLAN baseband processing circuitry 908a and provide WLAN RF output signals to the FEM circuitry 904a for subsequent wireless transmission by the one or more antennas 901.
  • BT radio IC circuitry 906b may also include a transmit signal path which may include circuitry to up-convert BT baseband signals provided by the BT baseband processing circuitry 908b and provide BT RF output signals to the FEM circuitry 904b for subsequent wireless transmission by the one or more antennas 901.
  • radio IC circuitries 906a and 906b are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of a radio IC circuitry (not shown) that includes a transmit signal path and/or a receive signal path for both WLAN and BT signals, or the use of one or more radio IC circuitries where at least some of the radio IC circuitries share transmit and/or receive signal paths for both WLAN and BT signals.
  • Baseband processing circuity 908a-b may include a WLAN baseband processing circuitry 908a and a BT baseband processing circuitry 908b.
  • the WLAN baseband processing circuitry 908a may include a memory, such as, for example, a set of RAM arrays in a Fast Fourier Transform or Inverse Fast Fourier Transform block (not shown) of the WLAN baseband processing circuitry 908a.
  • Each of the WLAN baseband circuitry 908a and the BT baseband circuitry 908b may further include one or more processors and control logic to process the signals received from the corresponding WLAN or BT receive signal path of the radio IC circuitry 906a- b, and to also generate corresponding WLAN or BT baseband signals for the transmit signal path of the radio IC circuitry 906a-b.
  • Each of the baseband processing circuitries 908a and 908b may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with a device for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 906a-b.
  • PHY physical layer
  • MAC medium access control layer
  • WLAN-BT coexistence circuitry 913 may include logic providing an interface between the WLAN baseband circuitry 908a and the BT baseband circuitry 908b to enable use cases requiring WLAN and BT coexistence.
  • a switch 903 may be provided between the WLAN FEM circuitry 904a and the BT FEM circuitry 904b to allow switching between the WLAN and BT radios according to application needs.
  • antennas 901 are depicted as being respectively connected to the WLAN FEM circuitry 904a and the BT FEM circuitry 904b, embodiments include within their scope the sharing of one or more antennas as between the WLAN and BT FEMs, or the provision of more than one antenna connected to each of FEM 904a or 904b.
  • the front-end module circuitry 904a-b, the radio IC circuitry 906a- b, and baseband processing circuitry 908a-b may be provided on a single radio card, such as wireless radio card 902.
  • the one or more antennas 901, the FEM circuitry 904a-b and the radio IC circuitry 906a-b may be provided on a single radio card.
  • the radio IC circuitry 906a-b and the baseband processing circuitry 908a-b may be provided on a single chip or integrated circuit (IC), such as IC 912.
  • the wireless radio card 902 may include a WLAN radio card and may be configured for Wi-Fi communications, although the scope of the embodiments is not limited in this respect.
  • the radio architecture 105 A, 105B may be configured to receive and transmit orthogonal frequency division multiplexed (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals over a multicarrier communication channel.
  • OFDM orthogonal frequency division multiplexed
  • OFDMA orthogonal frequency division multiple access
  • radio architecture 105 A, 105B may be part of a Wi-Fi communication station (STA) such as a wireless access point (AP), a base station or a mobile device including a Wi-Fi device.
  • STA Wi-Fi communication station
  • AP wireless access point
  • radio architecture 105A, 105B may be configured to transmit and receive signals in accordance with specific communication standards and/or protocols, such as any of the Institute of Electrical and Electronics Engineers (IEEE) standards including, 802.1 ln-2009, IEEE 802.11-2012, IEEE 802.11-2016, 802.11n-2009, 802.11ac, 802.11ah, 802.11ad, 802.1 lay and/or 802.1 lax standards and/or proposed specifications for WLANs, although the scope of embodiments is not limited in this respect.
  • Radio architecture 105A, 105B may also be suitable to transmit and/or receive communications in accordance with other techniques and standards.
  • the radio architecture 105A, 105B may be configured for high- efficiency Wi-Fi (HEW) communications in accordance with the IEEE 802.1 lax standard.
  • the radio architecture 105A, 105B may be configured to communicate in accordance with an OFDMA technique, although the scope of the embodiments is not limited in this respect.
  • the radio architecture 105A, 105B may be configured to transmit and receive signals transmitted using one or more other modulation techniques such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and/or frequency hopping code division multiple access (FH-CDMA)), time-division multiplexing (TDM) modulation, and/or frequency-division multiplexing (FDM) modulation, although the scope of the embodiments is not limited in this respect.
  • spread spectrum modulation e.g., direct sequence code division multiple access (DS-CDMA) and/or frequency hopping code division multiple access (FH-CDMA)
  • TDM time-division multiplexing
  • FDM frequency-division multiplexing
  • the BT baseband circuitry 908b may be compliant with a Bluetooth (BT) connectivity standard such as Bluetooth, Bluetooth 8.0 or Bluetooth 6.0, or any other iteration of the Bluetooth Standard.
  • BT Bluetooth
  • the radio architecture 105 A, 105B may include other radio cards, such as a cellular radio card configured for cellular (e.g., 5GPP such as LTE, LTE- Advanced or 7G communications).
  • a cellular radio card configured for cellular (e.g., 5GPP such as LTE, LTE- Advanced or 7G communications).
  • the radio architecture 105A, 105B may be configured for communication over various channel bandwidths including bandwidths having center frequencies of about 900 MHz, 2.4 GHz, 5 GHz, and bandwidths of about 2 MHz, 4 MHz, 5 MHz, 5.5 MHz, 6 MHz, 8 MHz, 10 MHz, 20 MHz, 40 MHz, 80 MHz (with contiguous bandwidths) or 80+80 MHz (160MHz) (with non-contiguous bandwidths).
  • a 920 MHz channel bandwidth may be used. The scope of the embodiments is not limited with respect to the above center frequencies however.
  • FIG. 10 illustrates WLAN FEM circuitry 904a in accordance with some embodiments. Although the example of FIG. 10 is described in conjunction with the WLAN FEM circuitry 904a, the example of FIG. 10 may be described in conjunction with the example BT FEM circuitry 904b (FIG. 9), although other circuitry configurations may also be suitable.
  • the FEM circuitry 904a may include a TX/RX switch 1002 to switch between transmit mode and receive mode operation.
  • the FEM circuitry 904a may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry 904a may include a low-noise amplifier (LNA) 1006 to amplify received RF signals 1003 and provide the amplified received RF signals 1007 as an output (e.g., to the radio IC circuitry 906a- b (FIG. 9)).
  • LNA low-noise amplifier
  • the transmit signal path of the circuitry 904a may include a power amplifier (PA) to amplify input RF signals 1009 (e.g., provided by the radio IC circuitry 906a-b), and one or more filters 1012, such as band-pass filters (BPFs), low-pass filters (LPFs) or other types of filters, to generate RF signals 1015 for subsequent transmission (e.g., by one or more of the antennas 901 (FIG. 9)) via an example duplexer 1014.
  • PA power amplifier
  • BPFs band-pass filters
  • LPFs low-pass filters
  • the FEM circuitry 904a may be configured to operate in either the 2.4 GHz frequency spectrum or the 5 GHz frequency spectrum.
  • the receive signal path of the FEM circuitry 904a may include a receive signal path duplexer 1004 to separate the signals from each spectrum as well as provide a separate LNA 1006 for each spectrum as shown.
  • the transmit signal path of the FEM circuitry 904a may also include a power amplifier 1010 and a filter 1012, such as a BPF, an LPF or another type of filter for each frequency spectrum and a transmit signal path duplexer 1004 to provide the signals of one of the different spectrums onto a single transmit path for subsequent transmission by the one or more of the antennas 901 (FIG. 9).
  • BT communications may utilize the 2.4 GHz signal paths and may utilize the same FEM circuitry 904a as the one used for WEAN communications.
  • FIG. 11 illustrates radio IC circuitry 906a in accordance with some embodiments.
  • the radio IC circuitry 906a is one example of circuitry that may be suitable for use as the WLAN or BT radio IC circuitry 906a/906b (FIG. 9), although other circuitry configurations may also be suitable.
  • FIG. 11 may be described in conjunction with the example BT radio IC circuitry 906b.
  • the radio IC circuitry 906a may include a receive signal path and a transmit signal path.
  • the receive signal path of the radio IC circuitry 906a may include at least mixer circuitry 1102, such as, for example, down-conversion mixer circuitry, amplifier circuitry 1106 and filter circuitry 1108.
  • the transmit signal path of the radio IC circuitry 906a may include at least filter circuitry 1112 and mixer circuitry 1114, such as, for example, up-conversion mixer circuitry.
  • Radio IC circuitry 906a may also include synthesizer circuitry 1104 for synthesizing a frequency 1105 for use by the mixer circuitry 1102 and the mixer circuitry 1114.
  • the mixer circuitry 1102 and/or 1114 may each, according to some embodiments, be configured to provide direct conversion functionality.
  • the latter type of circuitry presents a much simpler architecture as compared with standard super-heterodyne mixer circuitries, and any flicker noise brought about by the same may be alleviated for example through the use of OFDM modulation.
  • FIG. 11 illustrates only a simplified version of a radio IC circuitry, and may include, although not shown, embodiments where each of the depicted circuitries may include more than one component.
  • mixer circuitry 1114 may each include one or more mixers
  • filter circuitries 1108 and/or 1112 may each include one or more filters, such as one or more BPFs and/or LPFs according to application needs.
  • mixer circuitries when mixer circuitries are of the direct-conversion type, they may each include two or more mixers.
  • mixer circuitry 1102 may be configured to down-convert RF signals 1007 received from the FEM circuitry 904a-b (FIG. 9) based on the synthesized frequency 1105 provided by synthesizer circuitry 1104.
  • the amplifier circuitry 1106 may be configured to amplify the down-converted signals and the filter circuitry 1108 may include an LPF configured to remove unwanted signals from the down-converted signals to generate output baseband signals 1107.
  • Output baseband signals 1107 may be provided to the baseband processing circuitry 908a-b (FIG. 9) for further processing.
  • the output baseband signals 1107 may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 1102 may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 1114 may be configured to up-convert input baseband signals 1111 based on the synthesized frequency 1105 provided by the synthesizer circuitry 1104 to generate RF output signals 1009 for the FEM circuitry 904a-b.
  • the baseband signals 1111 may be provided by the baseband processing circuitry 908a-b and may be filtered by filter circuitry 1112.
  • the filter circuitry 1112 may include an LPF or a BPF, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 1102 and the mixer circuitry 1114 may each include two or more mixers and may be arranged for quadrature down-conversion and/or up- conversion respectively with the help of synthesizer 1104.
  • the mixer circuitry 1102 and the mixer circuitry 1114 may each include two or more mixers each configured for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 1102 and the mixer circuitry 1114 may be arranged for direct down-conversion and/or direct up-conversion, respectively.
  • the mixer circuitry 1102 and the mixer circuitry 1114 may be configured for super-heterodyne operation, although this is not a requirement.
  • Mixer circuitry 1102 may comprise, according to one embodiment: quadrature passive mixers (e.g., for the in-phase (I) and quadrature phase (Q) paths).
  • RF input signal 1007 from FIG. 11 may be down-converted to provide I and Q baseband output signals to be sent to the baseband processor.
  • Quadrature passive mixers may be driven by zero and ninety-degree time-varying LO switching signals provided by a quadrature circuitry which may be configured to receive a LO frequency (fLO) from a local oscillator or a synthesizer, such as LO frequency 1105 of synthesizer 1104 (FIG. 11).
  • a LO frequency fLO
  • the LO frequency may be the carrier frequency
  • the LO frequency may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency).
  • the zero and ninety-degree time-varying switching signals may be generated by the synthesizer, although the scope of the embodiments is not limited in this respect.
  • the LO signals may differ in duty cycle (the percentage of one period in which the LO signal is high) and/or offset (the difference between start points of the period). In some embodiments, the LO signals may have an 85% duty cycle and an 80% offset. In some embodiments, each branch of the mixer circuitry (e.g., the in-phase (I) and quadrature phase (Q) path) may operate at an 80% duty cycle, which may result in a significant reduction is power consumption.
  • the in-phase (I) and quadrature phase (Q) path may operate at an 80% duty cycle, which may result in a significant reduction is power consumption.
  • the RF input signal 1007 may comprise a balanced signal, although the scope of the embodiments is not limited in this respect.
  • the I and Q baseband output signals may be provided to low-noise amplifier, such as amplifier circuitry 1106 (FIG. 11) or to filter circuitry 1108 (FIG. 11).
  • the output baseband signals 1107 and the input baseband signals 1111 may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals 1107 and the input baseband signals 1111 may be digital baseband signals. In these alternate embodiments, the radio IC circuitry may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, or for other spectrums not mentioned here, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 1104 may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 1104 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 1104 may include digital synthesizer circuitry. An advantage of using a digital synthesizer circuitry is that, although it may still include some analog components, its footprint may be scaled down much more than the footprint of an analog synthesizer circuitry.
  • frequency input into synthesizer circuity 1104 may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • a divider control input may further be provided by either the baseband processing circuitry 908a-b (FIG. 9) depending on the desired output frequency 1105.
  • a divider control input (e.g., N) may be determined from a look-up table (e.g., within a Wi-Fi card) based on a channel number and a channel center frequency as determined or indicated by the example application processor 910.
  • the application processor 910 may include, or otherwise be connected to, one of the example secure signal converter 101 or the example received signal converter 103 (e.g., depending on which device the example radio architecture is implemented in).
  • synthesizer circuitry 1104 may be configured to generate a carrier frequency as the output frequency 1105, while in other embodiments, the output frequency 1105 may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the output frequency 1105 may be a LO frequency (fLO).
  • fLO LO frequency
  • FIG. 12 illustrates a functional block diagram of baseband processing circuitry 908a in accordance with some embodiments.
  • the baseband processing circuitry 908a is one example of circuitry that may be suitable for use as the baseband processing circuitry 908a (FIG. 9), although other circuitry configurations may also be suitable.
  • the example of FIG. 11 may be used to implement the example BT baseband processing circuitry 908b of FIG. 9.
  • the baseband processing circuitry 908a may include a receive baseband processor (RX BBP) 1202 for processing receive baseband signals 1109 provided by the radio IC circuitry 906a- b (FIG. 9) and a transmit baseband processor (TX BBP) 1204 for generating transmit baseband signals 1111 for the radio IC circuitry 906a-b.
  • the baseband processing circuitry 908a may also include control logic 1206 for coordinating the operations of the baseband processing circuitry 908a.
  • the baseband processing circuitry 908a may include ADC 1210 to convert analog baseband signals 1209 received from the radio IC circuitry 906a-b to digital baseband signals for processing by the RX BBP 1202.
  • the baseband processing circuitry 908a may also include DAC 1212 to convert digital baseband signals from the TX BBP 1204 to analog baseband signals 1211.
  • the transmit baseband processor 1204 may be configured to generate OFDM or OFDMA signals as appropriate for transmission by performing an inverse fast Fourier transform (IFFT).
  • IFFT inverse fast Fourier transform
  • the receive baseband processor 1202 may be configured to process received OFDM signals or OFDMA signals by performing an FFT.
  • the receive baseband processor 1202 may be configured to detect the presence of an OFDM signal or OFDMA signal by performing an autocorrelation, to detect a preamble, such as a short preamble, and by performing a cross-correlation, to detect a long preamble.
  • the preambles may be part of a predetermined frame structure for Wi-Fi communication.
  • the antennas 901 may each comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals.
  • the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result.
  • Antennas 901 may each include a set of phased-array antennas, although embodiments are not so limited.
  • radio architecture 105A, 105B is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • processing elements including digital signal processors (DSPs), and/or other hardware elements.
  • DSPs digital signal processors
  • some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein.
  • the functional elements may refer to one or more processes operating on one or more processing elements.
  • the word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.
  • the terms “computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,” “wireless device” and “user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device.
  • the device may be either mobile or stationary.
  • the term “communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as “communicating,” when only the functionality of one of those devices is being claimed.
  • the term “communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal.
  • a wireless communication unit which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.
  • AP access point
  • An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art.
  • An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art.
  • Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards.
  • Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non- vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN
  • Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multistandard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like.
  • WAP wireless application protocol
  • Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi- tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra- wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3 GPP, long term evolution (LTE), LTE advanced, enhanced data rates for G
  • Example 1 may be an apparatus of a device comprising memory and processing circuitry configured to: identify an Internet connection; present one or more identity providers (IDPs) associated with an OpenRoaming Wi-Fi connection; receive a user selection of an IDP of the one or more IDPs; generate an OpenRoaming profile with the IDP; install the OpenRoaming profile; and establish the OpenRoaming Wi-Fi connection using the OpenRoaming profile.
  • IDPs identity providers
  • Example 2 may include the apparatus of example 1 and/or some other example herein, wherein to establish the OpenRoaming Wi-Fi connection occurs without user input.
  • Example 3 may include the apparatus of example 1 and/or some other example herein, wherein a cellular subscriber identification module (SIM) card is absent from the device.
  • SIM subscriber identification module
  • Example 4 may include the apparatus of example 1 and/or some other example herein, wherein the IDP has an OpenRoaming provisioning portal, and wherein to generate the OpenRoaming profile with the IDP comprises the processing circuitry being further configured to: re-direct the device to the OpenRoaming portal; and receive a username and password or certificate for the device, wherein the OpenRoaming profile is based on the username and password or certificate.
  • Example 5 may include the apparatus of example 1 and/or some other example herein, wherein the IDP does not have an OpenRoaming provisioning portal, and wherein to generate the OpenRoaming profile with the IDP comprises the processing circuitry being further configured to: initiate an oAuth authentication protocol with the IDP; and receive a username and password or certificate for the device, wherein the OpenRoaming profile is based on the username and password or certificate.
  • Example 6 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry is further configured to identify the one or more IDPs based on IDP data provided to an OpenRoaming system by the one or more IDPs.
  • Example 7 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry is further configured to re-direct the device to a web-based portal with oAuth authentication protocol support for the IDP.
  • Example 8 may include the apparatus of example 1 and/or some other example herein, the device further comprising a transceiver configured to transmit and receive wireless signals associated with generating the OpenRoaming profile.
  • Example 9 may include the device of example 8 and/or some other example herein, further comprising one or more antennas coupled to the transceiver to cause to send the wireless signals.
  • Example 10 may include a non- transitory computer-readable medium storing computerexecutable instructions which when executed by one or more processors result in performing operations comprising: identifying an Internet connection of a device; presenting one or more identity providers (IDPs) associated with an OpenRoaming Wi-Fi connection; receiving a user selection of an IDP of the one or more IDPs; generating an OpenRoaming profile with the IDP; installing the OpenRoaming profile; and establishing the OpenRoaming Wi-Fi connection using the OpenRoaming profile.
  • IDPs identity providers
  • Example 11 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein establishing the OpenRoaming Wi-Fi connection occurs without user input.
  • Example 12 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein a cellular subscriber identification module (SIM) card is absent from the device.
  • SIM subscriber identification module
  • Example 13 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the IDP has an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: re-directing the device to the OpenRoaming portal; and receiving a username and password for the device, wherein the OpenRoaming profile is based on the username and password.
  • Example 14 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the IDP does not have an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: initiating an oAuth authentication protocol with the IDP; and receiving a username and password for the device, wherein the OpenRoaming profile is based on the username and password.
  • Example 15 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, the operations further comprising identifying the one or more IDPs based on IDP data provided to an OpenRoaming system by the one or more IDPs.
  • Example 16 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, the operations further comprising re-directing the device to a web-based portal with oAuth authentication protocol support for the IDP.
  • Example 17 may include a method comprising: identifying, by processing circuitry of a device, an Internet connection of a device; presenting, by the processing circuitry, one or more identity providers (IDPs) associated with an OpenRoaming Wi-Fi connection; receiving, by the processing circuitry, a user selection of an IDP of the one or more IDPs; generating, by the processing circuitry, an OpenRoaming profile with the IDP; installing, by the processing circuitry, the OpenRoaming profile; and establishing, by the processing circuitry, the OpenRoaming Wi-Fi connection using the OpenRoaming profile.
  • IDPs identity providers
  • Example 18 may include the method of example 17 and/or some other example herein, wherein the IDP has an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: re-directing the device to the OpenRoaming portal; and receiving a username and password or certificate for the device, wherein the OpenRoaming profile is based on the username and password or certificate.
  • Example 19 may include the method of example 17 and/or some other example herein, wherein the IDP does not have an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: initiating an oAuth authentication protocol with the IDP; and receiving a username and password for the device or certificate, wherein the OpenRoaming profile is based on the username and password or certificate.
  • Example 20 may include the method of example 17 and/or some other example herein, further comprising re-directing the device to a web-based portal with oAuth authentication protocol support for the IDP.
  • Example 21 may include one or more non- transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein
  • Example 22 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
  • Example 23 may include a method, technique, or process as described in or related to any of examples 1-20, or portions or parts thereof.
  • Example 24 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.
  • Example 25 may include a method of communicating in a wireless network as shown and described herein.
  • Example 26 may include a system for providing wireless communication as shown and described herein.
  • Example 27 may include a device for providing wireless communication as shown and described herein.
  • Embodiments according to the disclosure are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well.
  • the dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims.
  • These computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks.
  • These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks.
  • certain implementations may provide for a computer program product, comprising a computer-readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks.
  • the computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks.
  • blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware -based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.
  • conditional language such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Accounting & Taxation (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

This disclosure describes systems, methods, and devices related to out-of-band activation and provisioning of mobile devices for OpenRoaming networks. A device may identify an Internet connection; present one or more identity providers (IDPs) associated with an OpenRoaming Wi-Fi connection; receive a user selection of an IDP of the one or more IDPs; generate an OpenRoaming profile with the IDP; install the OpenRoaming profile; and establish the OpenRoaming Wi-Fi connection using the OpenRoaming profile.

Description

ENHANCED MECHANISM FOR OUT-OF-BAND ACTIVATION AND PROVISIONING OF MOBILE DEVICES FOR OPENROAMING NETWORKS
CROSS-REFERENCE TO RELATED APPLICATIONS
This application claims the benefit of U.S. Provisional Application No. 63/092,366, filed October 15, 2020, and of U.S. Provisional Application No. 63/112,910, filed November 12, 2020, the disclosures of which are incorporated herein by reference as if set forth in full.
TECHNICAL FIELD
This disclosure generally relates to systems and methods for wireless communications and, more particularly, to a mechanism for out-of-band activation and provisioning of mobile devices for OpenRoaming networks.
BACKGROUND
Wireless devices are becoming widely prevalent and are increasingly requesting access to wireless channels. The Institute of Electrical and Electronics Engineers (IEEE) is developing one or more standards that utilize Orthogonal Frequency-Division Multiple Access (OFDMA) in channel allocation.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a network diagram illustrating an example network environment for out-of-band activation and provisioning, in accordance with one or more example embodiments of the present disclosure.
FIG. 2 depicts an illustrative schematic architecture and device association using OpenRoaming, in accordance with one or more example embodiments of the present disclosure.
FIG. 3 depicts an illustrative process for device pre-provisioning using OpenRoaming, in accordance with one or more example embodiments of the present disclosure.
FIG. 4 depicts an illustrative schematic architecture and device association using OpenRoaming with multiple different identity providers (IDPs), in accordance with one or more example embodiments of the present disclosure.
FIG. 5 depicts an illustrative process for device pre-provisioning using OpenRoaming and multiple different IDPs, in accordance with one or more example embodiments of the present disclosure. FIG. 6 illustrates a flow diagram of illustrative process for an out-of-band activation and provisioning system, in accordance with one or more example embodiments of the present disclosure.
FIG. 7 illustrates a functional diagram of an exemplary communication station that may be suitable for use as a user device, in accordance with one or more example embodiments of the present disclosure.
FIG. 8 illustrates a block diagram of an example machine upon which any of one or more techniques (e.g., methods) may be performed, in accordance with one or more example embodiments of the present disclosure.
FIG. 9 is a block diagram of a radio architecture in accordance with some examples.
FIG. 10 illustrates an example front-end module circuitry for use in the radio architecture of FIG. 9, in accordance with one or more example embodiments of the present disclosure.
FIG. 11 illustrates an example radio IC circuitry for use in the radio architecture of FIG. 9, in accordance with one or more example embodiments of the present disclosure.
FIG. 12 illustrates an example baseband processing circuitry for use in the radio architecture of FIG. 9, in accordance with one or more example embodiments of the present disclosure.
DETAILED DESCRIPTION
The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, algorithm, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.
OpenRoaming refers to a global Wi-Fi network of Wi-Fi networks where mobile devices can automatically and securely connect. Wi-Fi access network providers (ANPs) may include retailers, restaurants, enterprises, Internet service providers, and the like. As devices move from one physical location to another, some Wi-Fi networks may become unavailable, while other Wi-Fi networks may become available. Generally, as a device leaves a physical area in which one Wi-Fi network is available and enters another physical area in which another Wi-Fi network is available, the device may be presented with the option to join the other Wi-Fi network. In this manner, Wi-Fi mobility lacks the cellular concept of roaming, in which a device that is outside of a coverage area of a cellular provider automatically may access a network provided by a different cellular provider (e.g., due to agreements in place between the cellular providers). Accordingly, the processes for a mobile device to switch to different Wi-Fi access networks as the device changes locations are more cumbersome than cellular roaming techniques. OpenRoaming is a mechanism for allowing Wi-Fi-enabled devices to join Wi-Fi access networks without the need to re-register and re-enter credentials each time.
Establishing a global Wi-Fi roaming network is challenging due to fragmentation of WiFi networks and a lack of roaming agreements that would need to be in place (e.g., similar to cellular network roaming agreements, but more complicated in part due to the many more WiFi access network providers than cellular network providers). OpenRoaming addresses the challenges of Wi-Fi roaming by bringing together ANPs and identity providers (IDPs) under a public key infrastructure (PKI)-based trust model. An ANP may securely connect with IDPs using the PKI model under OpenRoaming. OpenRoaming creates an automatic plug-and-play architecture through a cloud-based roaming framework using PKI. An IDP goes thru IDP onboarding process with OpenRoaming cloud, and it also registers with OpenRoaming domain name service (DNS) for auto-discovery. At the access network provider, an OpenRoaming connector supports ANP onboarding to the OpenRoaming cloud. A mobile client device (e.g., station device) provisioned with an OpenRoaming profile, discovers an OpenRoaming Wi-Fi network, associates with the AP and provides its OpenRoaming IDP to ANP. In turn, ANP queries the OpenRoaming DNS to find out where to route the authentication. In this manner, the client device automatically may identify and join Wi-Fi networks available at any physical location through use of the OpenRoaming profile.
However, provisioning of mobile devices for Wi-Fi networks has been a long-standing problem. Given the number of Wi-Fi networks all around the world, it has not been possible to provision the devices and configure them for out-of-box Wi-Fi connectivity experience.
The present disclosure defines an out-of-band mechanism for OpenRoaming account activation and provisioning of mobile devices to enable an out-of-box OpenRoaming ready solution. There are captive portals, Passpoint (an OpenRoaming application), and other onboarding solutions. Hotspot 2.0 Online Sign Up has not scaled up over ten years due to deployment complexity and device implementation challenges. Captive portal mechanism is a manual process with tedious use involvements.
Example embodiments of the present disclosure relate to systems, methods, and devices for a mechanism for out-of-band activation and provisioning of mobile devices for OpenRoaming networks. In one or more embodiments, an application on a client device (e.g., station device) without a SIM card (e.g., such as a laptop, tablet, or smartphone without a cellular SIM card) may trigger OpenRoaming pre-provisioning, and an OpenRoaming provisioning portal may generate OpenRoaming profiles based on IDP-provided tokens, and may provision the profile on the client device. When the client device has Internet access, the client device may establish an account using OpenRoaming provisioning (e.g., using a web-based provisioning portal). The client device may receive a list of available IDPs from the web-based provisioning portal, and may select an IDP with which to establish OpenRoaming account. If the user has already established account with the IDP, it can be used for OpenRoaming. If not, user goes through and account establishment with the IDSP (e.g., username, password, and/or certificate). Once the account is established with the IDP, the OpenRoaming profile of the client device may be provisioned for future connection, allowing the client device to automatically join Wi-Fi OpenRoaming networks (e.g., in the background of the client device without requiring user inputs) because the OpenRoaming profile may be used to discover the OpenRoaming networks and dynamically identify the IDP that will perform the authentication. . For example, when the client device identifies an OpenRoaming ANP, the client device may connect to the ANP’s network using the OpenRoaming profile because the ANP identifies the IDP through OpenRoaming DNS, and it forwards the authentication to the IDP (e.g., using Remote Authentication Dial-In User Service - Radius - RADSec). Once the IDP authenticates the user, the client device may be granted access to the Internet.
In one or more embodiments, multiple IDPs could be supported in OpenRoaming provisioning portal.. OpenRoaming provisioning portal provides oAuth support for IDPs interested in joining OpenRoaming and the portal interfaces between the mobile device and IDPs to get authorization token from IDS and provision the OpenRoaming profile on the mobile device for future connections.
In one or more embodiments, an out-of-band activation and provisioning system may enable an end-to-end out-of-box mobile device OpenRoaming readiness capability and user experience by: Pre-configuring the devices for activation, enabling a provisioning Web Server for account activation and establishment, routing the provisioning to participating IDPs, provisioning devices when the system has a network access, and facilitating out-of-box provisioning of devices when the system has network access. The proposed solutions herein may be integrated in mobile devices to enable seamless, simple Wi-Fi connectivity and roaming capability using OpenRoaming. The above descriptions are for purposes of illustration and are not meant to be limiting. Numerous other examples, configurations, processes, algorithms, etc., may exist, some of which are described in greater detail below. Example embodiments will now be described with reference to the accompanying figures.
FIG. 1 is a network diagram illustrating an example network environment of out-of-band activation and provisioning for OpenRoaming, according to some example embodiments of the present disclosure. Wireless network 100 may include one or more user devices 120 and one or more access points(s) (AP) 102, which may communicate in accordance with IEEE 802.11 communication standards. The user device(s) 120 may be mobile devices that are non- stationary (e.g., not having fixed locations) or may be stationary devices.
In some embodiments, the user devices 120 and the AP 102 may include one or more computer systems similar to that of the functional diagram of FIG. 7 and/or the example machine/system of FIG. 8.
One or more illustrative user device(s) 120 and/or AP(s) 102 may be operable by one or more user(s) 110. It should be noted that any addressable unit may be a station (STA). An STA may take on multiple distinct characteristics, each of which shape its function. For example, a single addressable unit might simultaneously be a portable STA, a quality-of-service (QoS) STA, a dependent STA, and a hidden STA. The one or more illustrative user device(s) 120 and the AP(s) 102 may be STAs. The one or more illustrative user device(s) 120 and/or AP(s) 102 may operate as a personal basic service set (PBSS) control point/access point (PCP/AP). The user device(s) 120 (e.g., 124, 126, or 128) and/or AP(s) 102 may include any suitable processor- driven device including, but not limited to, a mobile device or a non-mobile, e.g., a static device. For example, user device(s) 120 and/or AP(s) 102 may include, a user equipment (UE), a station (STA), an access point (AP), a software enabled AP (SoftAP), a personal computer (PC), a wearable wireless device (e.g., bracelet, watch, glasses, ring, etc.), a desktop computer, a mobile computer, a laptop computer, an ultrabookTM computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, an internet of things (loT) device, a sensor device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a mobile phone, a cellular telephone, a PCS device, a PDA device which incorporates a wireless communication device, a mobile or portable GPS device, a DVB device, a relatively small computing device, a non-desktop computer, a “carry small live large” (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an “origami” device or computing device, a device that supports dynamically composable computing (DCC), a context-aware device, a video device, an audio device, an A/V device, a set-top-box (STB), a blu-ray disc (BD) player, a BD recorder, a digital video disc (DVD) player, a high definition (HD) DVD player, a DVD recorder, a HD DVD recorder, a personal video recorder (PVR), a broadcast HD receiver, a video source, an audio source, a video sink, an audio sink, a stereo tuner, a broadcast radio receiver, a flat panel display, a personal media player (PMP), a digital video camera (DVC), a digital audio player, a speaker, an audio receiver, an audio amplifier, a gaming device, a data source, a data sink, a digital still camera (DSC), a media player, a smartphone, a television, a music player, or the like. Other devices, including smart devices such as lamps, climate control, car components, household components, appliances, etc. may also be included in this list.
As used herein, the term “Internet of Things (loT) device” is used to refer to any object (e.g., an appliance, a sensor, etc.) that has an addressable interface (e.g., an Internet protocol (IP) address, a Bluetooth identifier (ID), a near-field communication (NFC) ID, etc.) and can transmit information to one or more other devices over a wired or wireless connection. An loT device may have a passive communication interface, such as a quick response (QR) code, a radiofrequency identification (RFID) tag, an NFC tag, or the like, or an active communication interface, such as a modem, a transceiver, a transmitter-receiver, or the like. An loT device can have a particular set of attributes (e.g., a device state or status, such as whether the loT device is on or off, open or closed, idle or active, available for task execution or busy, and so on, a cooling or heating function, an environmental monitoring or recording function, a light-emitting function, a sound-emitting function, etc.) that can be embedded in and/or controlled/monitored by a central processing unit (CPU), microprocessor, ASIC, or the like, and configured for connection to an loT network such as a local ad-hoc network or the Internet. For example, loT devices may include, but are not limited to, refrigerators, toasters, ovens, microwaves, freezers, dishwashers, dishes, hand tools, clothes washers, clothes dryers, furnaces, air conditioners, thermostats, televisions, light fixtures, vacuum cleaners, sprinklers, electricity meters, gas meters, etc., so long as the devices are equipped with an addressable communications interface for communicating with the loT network. loT devices may also include cell phones, desktop computers, laptop computers, tablet computers, personal digital assistants (PDAs), etc. Accordingly, the loT network may be comprised of a combination of “legacy” Internet- accessible devices (e.g., laptop or desktop computers, cell phones, etc.) in addition to devices that do not typically have Internet-connectivity (e.g., dishwashers, etc.).
The user device(s) 120 and/or AP(s) 102 may also include mesh stations in, for example, a mesh network, in accordance with one or more IEEE 802.11 standards and/or 3 GPP standards.
Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to communicate with each other via one or more communications networks 130 and/or 135 wirelessly or wired. The user device(s) 120 may also communicate peer-to-peer or directly with each other with or without the AP(s) 102. Any of the communications networks 130 and/or 135 may include, but not limited to, any one of a combination of different types of suitable communications networks such as, for example, broadcasting networks, cable networks, public networks (e.g., the Internet), private networks, wireless networks, cellular networks, or any other suitable private and/or public networks. Further, any of the communications networks 130 and/or 135 may have any suitable communication range associated therewith and may include, for example, global networks (e.g., the Internet), metropolitan area networks (MANs), wide area networks (WANs), local area networks (LANs), or personal area networks (PANs). In addition, any of the communications networks 130 and/or 135 may include any type of medium over which network traffic may be carried including, but not limited to, coaxial cable, twisted-pair wire, optical fiber, a hybrid fiber coaxial (HFC) medium, microwave terrestrial transceivers, radio frequency communication mediums, white space communication mediums, ultra-high frequency communication mediums, satellite communication mediums, or any combination thereof.
Any of the user device(s) 120 (e.g., user devices 124, 126, 128) and AP(s) 102 may include one or more communications antennas. The one or more communications antennas may be any suitable type of antennas corresponding to the communications protocols used by the user device(s) 120 (e.g., user devices 124, 126 and 128), and AP(s) 102. Some non-limiting examples of suitable communications antennas include Wi-Fi antennas, Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards compatible antennas, directional antennas, non-directional antennas, dipole antennas, folded dipole antennas, patch antennas, multiple-input multiple-output (MIMO) antennas, omnidirectional antennas, quasi- omnidirectional antennas, or the like. The one or more communications antennas may be communicatively coupled to a radio component to transmit and/or receive signals, such as communications signals to and/or from the user devices 120 and/or AP(s) 102.
Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform directional transmission and/or directional reception in conjunction with wirelessly communicating in a wireless network. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform such directional transmission and/or reception using a set of multiple antenna arrays (e.g., DMG antenna arrays or the like). Each of the multiple antenna arrays may be used for transmission and/or reception in a particular respective direction or range of directions. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional transmission towards one or more defined transmit sectors. Any of the user device(s) 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may be configured to perform any given directional reception from one or more defined receive sectors.
MIMO beamforming in a wireless network may be accomplished using RF beamforming and/or digital beamforming. In some embodiments, in performing a given MIMO transmission, user devices 120 and/or AP(s) 102 may be configured to use all or a subset of its one or more communications antennas to perform MIMO beamforming.
Any of the user devices 120 (e.g., user devices 124, 126, 128), and AP(s) 102 may include any suitable radio and/or transceiver for transmitting and/or receiving radio frequency (RF) signals in the bandwidth and/or channels corresponding to the communications protocols utilized by any of the user device(s) 120 and AP(s) 102 to communicate with each other. The radio components may include hardware and/or software to modulate and/or demodulate communications signals according to pre-established transmission protocols. The radio components may further have hardware and/or software instructions to communicate via one or more Wi-Fi and/or Wi-Fi direct protocols, as standardized by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards. In certain example embodiments, the radio component, in cooperation with the communications antennas, may be configured to communicate via 2.4 GHz channels (e.g. 802.11b, 802.11g, 802.1 In, 802.1 lax), 5 GHz channels (e.g. 802.1 In, 802.1 lac, 802.1 lax), or 60 GHZ channels (e.g. 802. Had, 802. Hay). 800 MHz channels (e.g. 802.11ah). The communications antennas may operate at 28 GHz and 40 GHz. It should be understood that this list of communication channels in accordance with certain 802.11 standards is only a partial list and that other 802.11 standards may be used (e.g., Next Generation Wi-Fi, or other standards). In some embodiments, non-Wi-Fi protocols may be used for communications between devices, such as Bluetooth, dedicated short-range communication (DSRC), Ultra- High Frequency (UHF) (e.g. IEEE 802.1 laf, IEEE 802.22), white band frequency (e.g., white spaces), or other packetized radio communications. The radio component may include any known receiver and baseband suitable for communicating via the communications protocols. The radio component may further include a low noise amplifier (LNA), additional signal amplifiers, an analog-to-digital (A/D) converter, one or more buffers, and digital baseband.
OpenRoaming may be performed according to FIGs. 2-6, using an OpenRoaming provisioning system 150. For example, when the one or more user devices 120 are connected to the Internet, the OpenRoaming provisioning system 150 may provision and automatically connect the one or more user devices 120 to Wi-Fi networks (e.g., a Wi-Fi network provided by the AP 102).
It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.
FIG. 2 depicts an illustrative schematic architecture and device association 200 using OpenRoaming, in accordance with one or more example embodiments of the present disclosure.
Referring to FIG. 2, user devices 202 (e.g., similar to the one or more user devices 120 of FIG. 1) may connect to an OpenRoaming Wi-Fi network provided by an ANP 204. The ANP 204 may exchange ANP onboarding data 206 with an OpenRoaming cloud 208, which may communicate with one or more IDPs 210. The OpenRoaming cloud 208 and the one or more IDPs 210 may exchange IDP onboarding data 212. The one or more IDPs 210 also may provide IDP registration data 213 to a DNS server 214 for future identification. The ANP 204 may query DNS for IDP discoverya 216. As explained further below with respect to FIG. 3, the ANP 204 may authenticate 218 the user devices 202 to the one of the OpenRoaming IDPs 210 by using a provisioned OpenRoaming profile of the user devices 202 and selected IDPs of the one or more IDPs 210 as identified based on the IDP registration data 213. In this manner, the OpenRoaming cloud 208 may connect ANPs to IDPs so to provide OpenRoaming in which the user devices 202 may connect automatically to Wi-Fi networks.
In one or more embodiments, the OpenRoaming provisioning system 150 of FIG. 1 may include at least some of the architecture shown in FIG. 2.
In one or more embodiments, the user devices 202 may be pre-configured with an OpenRoaming activation flag. During a system set up, or when the user devices 202 are connected to the Internet, the user devices 202 may present a user prompt to a user to activate OpenRoaming. When OpenRoaming is activated on the user devices 202, an OpenRoaming web server (e.g., as shown in FIG. 3) may be enabled for OpenRoaming activation and account establishment. The user devices 202 may accept terms and conditions for OpenRoaming, and may allow a user to provide a username, password, and/or certificate, along with any other account details, to generate a user-specific OpenRoaming profile with which the user devices 202 may be provisioned. The user devices 202 may use the provisioned OpenRoaming profile to establish future Wi-Fi connections.
FIG. 3 depicts an illustrative process 300 for device pre-provisioning using OpenRoaming, in accordance with one or more example embodiments of the present disclosure.
Referring to FIG. 3, the process 300 may include a client device 302 (e.g., similar to the user devices 202 of FIG. 2), an ANP 304, the Internet 306, a DNS server 308, an OpenRoaming web server 310, and one or more IDPs 312. A pre-provisioning process 318 for the client device 302 may include the client device 302 establishing Internet access 320 with the Internet 306. When the client device 302 has an Internet connection, the client device 302 may establish an OpenRoaming account by using the Internet 306 to access the OpenRoaming web server 310, which may display an IDP list 322 (e.g., of the one or more IDPs 312, as established based on the IDP registration data 213 of FIG. 2). At step 324, the client device 302 may select one or more of the IDPs presented as available. When the client device 302 receives a user selection of an IDP, the client device 302 may be directed to the selected IDP of the one or more IDPs 312, where the client device 302 and the one of the IDPs 312 may establish an OpenRoaming account 326 (e.g., a username and password, and/or certificate). Based on the established account, an OpenRoaming profile 326 may be generated and installed on the client device 302 for the selected IDP, and provisioned for establishing a future Wi-Fi connection.
Still referring to FIG. 3, once the OpenRoaming profile 326 is installed, the client device 302 may join an OpenRoaming ANP 328 Wi-Fi network, and the ANP 304 may look up, at the DNS server 308, the address 330 of the IDP used in the OpenRoaming account 326. Once the ANP 304 identifies the IDP address 330, the ANP 304 may perform extensible authentication protocol (EAP) authentication with the IDP 312. As a result, the client device 302 may be granted network access to the Internet 306.
In one or more embodiments, the pre -pro visioning process 318 may set an OpenRoaming activation flag on the client device 302. When the client device 302 receives a user confirmation to accept OpenRoaming, a device identifier of the client device 302 may be used to establish the OpenRoaming account 326. For example, the OpenRoaming web server 310 may verify the device identifier, display the terms and conditions of the OpenRoaming, and the user of the client device 302 may accept the terms and conditions. When the user selects the IDP, the OpenRoaming web server 310 may redirect the account activation/establishment to the selected IDP. The client device 302 may provide the username and password, along with contact or other account information, and the IDP may generate the OpenRoaming profile 326 for the user and may install the OpenRoaming profile 326 on the client device 302 (e.g., using operating system- provided application programming interfaces, etc.).
In one or more embodiments, once the client device 302 has been pre-provisioned using the pre -pro visioning process 318, the client device 302 may be ready for OpenRoaming “out-of- the box.” When the client device 302 is moved into an OpenRoaming Wi-Fi network, the WiFi connection may be established using the OpenRoaming account 326 automatically. For example, the client device 302 may identify an OpenRoaming Wi-Fi network, and the client device 302 may perform authentication and association using the OpenRoaming ANP 304, without the need for user interaction, as the ANP 304 may route the authentication to the specified IDP of the OpenRoaming account 326. The IDP may authenticate the user based on the OpenRoaming account 326, allowing the client device 302 to access the Wi-Fi network provided by the ANP 304 without the user needing to select the network and provide credentials. In this manner, when a user purchases a new device (e.g., without a SIM card), the device is ready for OpenRoaming activation and out-of-band provisioning.
FIG. 4 depicts an illustrative schematic architecture and device association 400 using OpenRoaming with multiple different IDPs, in accordance with one or more example embodiments of the present disclosure.
Referring to FIG. 4, the schematic architecture of FIG. 2 may be modified to support multiple IDPs, including IDPs that can and cannot perform OpenRoaming provisioning. Part of the OpenRoaming provisioning may be supported in the user devices 202, and part may be implemented in the OpenRoaming provisioning web portal 402. As shown, a web portal 402 (e.g., having oAuth support) for provisioning may allow for IDPs without provisioning capabilities, but having oAuth authentication, may be supported. The user devices 202 may be re-directed (e.g., by an application) to the web portal 402. For IDPs with provisioning capabilities, the provisioning process may be re-directed (e.g., via the web portal 402) to the IDP to provision the OpenRoaming account 326 of FIG. 3 (e.g., using an application programming interface). For IDPs without provisioning capabilities, the web portal 402 may authenticate 406 (e.g., using oAuth) to the IDPs without provisioning capabilities. For example, the web portal 402 may obtain an authorized oAuth token, and may generate an OpenRoaming profile (the OpenRoaming account 326) using the authorized token, then may provision the OpenRoaming profile on the user devices 202.
In one or more embodiments, the OpenRoaming provisioning system 150 of FIG. 1 may include at least some of the architecture shown in FIG. 4.
In one or more embodiments, the user devices 202 may use a provisioning application to establish an OpenRoaming activation flag during an operating system setup or update. When an operating system is being updated, the application may determine whether an OpenRoaming profile has been established for the user devices 202. If so, the activation may be skipped. When the user devices 202 has an Internet connection, the application may trigger OpenRoaming activation by prompting a user to enable OpenRoaming. When the user accepts OpenRoaming activation, the application may re-direct the user devices 202 to the web portal 402 for the provisioning process.
In one or more embodiments, the provisioning web portal 402 may display the OpenRoaming terms and conditions to the user devices 202, and when accepted by a user, the OpenRoaming cloud 208 may display the OpenRoaming IDP list to the user devices 202. When the user selects an IDP with oAuth-only support, the web portal 402 may initiate the oAuth process with the selected IDP. When the user selects an IDP with portal-based provisioning, the web portal 402 re-directs the user devices 202 to the provisioning portal of the selected IDP, where the user devices 202 may provide credentials (e.g., username and password), and the IDP portal may generate and provision the OpenRoaming profile on the user devices 202. The provisioning process for multiple different IDPs is shown in FIG. 5.
FIG. 5 depicts an illustrative process 500 for device pre-provisioning using OpenRoaming and multiple different IDPs, in accordance with one or more example embodiments of the present disclosure.
Referring to FIG. 5, the process 500 may include a client device 502 (e.g., similar to the user devices 202 of FIG. 2), an ANP 504, the Internet 506, a DNS server 508, an OpenRoaming web server 510, and two or more IDPs 512. A pre-provisioning process 518 for the client device 502 may include the client device 502 establishing Internet access 520 with the Internet 506. When the client device 502 has an Internet connection, the client device 502 may establish an OpenRoaming account by using the Internet 506 to access the OpenRoaming web server 510, which may display an IDP list 522 (e.g., of the two or more IDPs 512, as established based on the IDP registration data 213 of FIG. 2). At step 524, the client device 502 may select one or more of the IDPs presented as available. When the client device 502 receives a user selection of an IDP with a provisioning capability, the client device 502 may be re-directed 525 to the provisioning portal of the selected IDP of the one or more IDPs 512, where the client device 502 and the selected IDP may establish an OpenRoaming account 526 (e.g., a username and password). The OpenRoaming profile 326 may be installed on the client device 502 for the IDP, and provisioned for establishing a future Wi-Fi connection. When the client device 502 receives a user selection of an IDP without a provisioning capability, the selected IDP may provide an authorization token to the web server 510 to be used to authorize the user (e.g., using oAuth) by generating a profile (e.g., the OpenRoaming account 326 of FIG. 3) with the token at step 530. At step 532, the web server 510 may install the OpenRoaming profile on the client device 502 for the IDP (e.g., using an operating system application programming interface for delivery).
Still referring to FIG. 5, once the OpenRoaming profile 326 is established, the client device 502 may join an OpenRoaming ANP 540 Wi-Fi network, and the ANP 504 may look up, at the DNS server 508, the address 550 of the IDP used in the OpenRoaming profile 326. Once the ANP 504 identifies the IDP address 550, the mobile device 502 may perform EAP authentication with the IDP. The IDP 502 then may signal the ANP 504 about the successful authentication of the device 502). As a result, the client device 502 may be granted network access to the Internet 506.
It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.
FIG. 6 illustrates a flow diagram of illustrative process 600 for an out-of-band activation and provisioning system, in accordance with one or more example embodiments of the present disclosure.
At block 602, a device (e.g., the user device(s) 120 and/or the AP 102 of FIG. 1, the user devices 202 of FIG. 2, the OpenRoaming cloud 208 of FIG. 2, the client device 302 of FIG. 3, the web server 310 of FIG. 3, the client device 502 of FIG. 5, and/or the web server 510 of FIG. 5) may determine that a client device (e.g., a client device not having a cellular SIM) may have an Internet connection. For example, the client device may have a provisioning application for OpenRoaming that determines when the client device has an Internet connection.
At block 604, the device may activate an OpenRoaming process based on the detected Internet connection. For example, the client device application may redirect the client device to the device for OpenRoaming device provisioning.
At block 606, the device may present to the client device a list of IDPs available for selection and with which to generate an OpenRoaming profile.
At block 608, the device may receive, from the client device, a user selection of an IDP from the list of IDPs. When the client device receives a user selection of an IDP with a provisioning capability, the client device may be re-directed by the device to the provisioning portal of the selected IDP of the one or more IDPs at block 610 (e.g., an optional step depending on whether the selected IDP has a provisioning capability for OpenRoaming). When the client device receives a user selection of an IDP without a provisioning capability, the selected IDP may provide an authorization token to the device to be used to authorize the user (e.g., using oAuth) by generating a profile (e.g., the OpenRoaming account 326 of FIG. 3) with the token at block 612.
At block 612, the device or the IDP portal may generate the OpenRoaming profile for the client device. When the client device receives a user selection of an IDP with a provisioning capability, the client device and the selected IDP may establish an OpenRoaming account (e.g., a username and password).
At block 614, the device may install the OpenRoaming profile on the client device to be provisioned for establishing a future Wi-Fi connection.
It is understood that the above descriptions are for purposes of illustration and are not meant to be limiting.
FIG. 7 shows a functional diagram of an exemplary communication station 700, in accordance with one or more example embodiments of the present disclosure. In one embodiment, FIG. 7 illustrates a functional block diagram of a communication station that may be suitable for use as an AP 102 (FIG. 1) or a user device 120 (FIG. 1) in accordance with some embodiments. The communication station 700 may also be suitable for use as a handheld device, a mobile device, a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a wearable computer device, a femtocell, a high data rate (HDR) subscriber station, an access point, an access terminal, or other personal communication system (PCS) device.
The communication station 700 may include communications circuitry 702 and a transceiver 710 for transmitting and receiving signals to and from other communication stations using one or more antennas 701. The communications circuitry 702 may include circuitry that can operate the physical layer (PHY) communications and/or medium access control (MAC) communications for controlling access to the wireless medium, and/or any other communications layers for transmitting and receiving signals. The communication station 700 may also include processing circuitry 706 and memory 708 arranged to perform the operations described herein. In some embodiments, the communications circuitry 702 and the processing circuitry 706 may be configured to perform operations detailed in the above figures, diagrams, and flows. In accordance with some embodiments, the communications circuitry 702 may be arranged to contend for a wireless medium and configure frames or packets for communicating over the wireless medium. The communications circuitry 702 may be arranged to transmit and receive signals. The communications circuitry 702 may also include circuitry for modulation/demodulation, upconversion/downconversion, filtering, amplification, etc. In some embodiments, the processing circuitry 706 of the communication station 700 may include one or more processors. In other embodiments, two or more antennas 701 may be coupled to the communications circuitry 702 arranged for sending and receiving signals. The memory 708 may store information for configuring the processing circuitry 706 to perform operations for configuring and transmitting message frames and performing the various operations described herein. The memory 708 may include any type of memory, including non-transitory memory, for storing information in a form readable by a machine (e.g., a computer). For example, the memory 708 may include a computer-readable storage device, read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flashmemory devices and other storage devices and media.
In some embodiments, the communication station 700 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a smartphone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), a wearable computer device, or another device that may receive and/or transmit information wirelessly.
In some embodiments, the communication station 700 may include one or more antennas 701. The antennas 701 may include one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas, or other types of antennas suitable for transmission of RF signals. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated for spatial diversity and the different channel characteristics that may result between each of the antennas and the antennas of a transmitting station.
In some embodiments, the communication station 700 may include one or more of a keyboard, a display, a non-volatile memory port, multiple antennas, a graphics processor, an application processor, speakers, and other mobile device elements. The display may be an LCD screen including a touch screen.
Although the communication station 700 is illustrated as having several separate functional elements, two or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may include one or more microprocessors, DSPs, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio- frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements of the communication station 700 may refer to one or more processes operating on one or more processing elements.
Certain embodiments may be implemented in one or a combination of hardware, firmware, and software. Other embodiments may also be implemented as instructions stored on a computer-readable storage device, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage device may include any non-transitory memory mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage device may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and other storage devices and media. In some embodiments, the communication station 700 may include one or more processors and may be configured with instructions stored on a computer-readable storage device.
FIG. 8 illustrates a block diagram of an example of a machine 800 or system upon which any one or more of the techniques (e.g., methodologies) discussed herein may be performed. In other embodiments, the machine 800 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine 800 may operate in the capacity of a server machine, a client machine, or both in server-client network environments. In an example, the machine 800 may act as a peer machine in peer- to-peer (P2P) (or other distributed) network environments. The machine 800 may be a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile telephone, a wearable computer device, a web appliance, a network router, a switch or bridge, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine, such as a base station. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), or other computer cluster configurations.
Examples, as described herein, may include or may operate on logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations when operating. A module includes hardware. In an example, the hardware may be specifically configured to carry out a specific operation (e.g., hardwired). In another example, the hardware may include configurable execution units (e.g., transistors, circuits, etc.) and a computer readable medium containing instructions where the instructions configure the execution units to carry out a specific operation when in operation. The configuring may occur under the direction of the executions units or a loading mechanism. Accordingly, the execution units are communicatively coupled to the computer-readable medium when the device is operating. In this example, the execution units may be a member of more than one module. For example, under operation, the execution units may be configured by a first set of instructions to implement a first module at one point in time and reconfigured by a second set of instructions to implement a second module at a second point in time.
The machine (e.g., computer system) 800 may include a hardware processor 802 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 804 and a static memory 806, some or all of which may communicate with each other via an interlink (e.g., bus) 808. The machine 800 may further include a power management device 832, a graphics display device 810, an alphanumeric input device 812 (e.g., a keyboard), and a user interface (UI) navigation device 814 (e.g., a mouse). In an example, the graphics display device 810, alphanumeric input device 812, and UI navigation device 814 may be a touch screen display. The machine 800 may additionally include a storage device (i.e., drive unit) 816, a signal generation device 818 (e.g., a speaker), an enhanced OpenRoaming device 819, a network interface device/transceiver 820 coupled to antenna(s) 830, and one or more sensors 828, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensor. The machine 800 may include an output controller 834, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., a printer, a card reader, etc.)). The operations in accordance with one or more example embodiments of the present disclosure may be carried out by a baseband processor. The baseband processor may be configured to generate corresponding baseband signals. The baseband processor may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with the hardware processor 802 for generation and processing of the baseband signals and for controlling operations of the main memory 804, the storage device 816, and/or the enhanced OpenRoaming device 819. The baseband processor may be provided on a single radio card, a single chip, or an integrated circuit (IC).
The storage device 816 may include a machine readable medium 822 on which is stored one or more sets of data structures or instructions 824 (e.g., software) embodying or utilized by any one or more of the techniques or fimctions described herein. The instructions 824 may also reside, completely or at least partially, within the main memory 804, within the static memory 806, or within the hardware processor 802 during execution thereof by the machine 800. In an example, one or any combination of the hardware processor 802, the main memory 804, the static memory 806, or the storage device 816 may constitute machine- readable media.
The enhanced OpenRoaming device 819 may carry out or perform any of the operations and processes (e.g., process 600) described and shown above (e.g., in FIGs. 2-6).
It is understood that the above are only a subset of what the enhanced OpenRoaming device 819 may be configured to perform and that other functions included throughout this disclosure may also be performed by the out-of-band activation and provisioning device 819.
While the machine-readable medium 822 is illustrated as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 824.
Various embodiments may be implemented fully or partially in software and/or firmware. This software and/or firmware may take the form of instructions contained in or on a non- transitory computer-readable storage medium. Those instructions may then be read and executed by one or more processors to enable performance of the operations described herein. The instructions may be in any suitable form, such as but not limited to source code, compiled code, interpreted code, executable code, static code, dynamic code, and the like. Such a computer- readable medium may include any tangible non-transitory medium for storing information in a form readable by one or more computers, such as but not limited to read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; a flash memory, etc.
The term “machine-readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the machine 800 and that cause the machine 800 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting machine-readable medium examples may include solid-state memories and optical and magnetic media. In an example, a massed machine-readable medium includes a machine-readable medium with a plurality of particles having resting mass. Specific examples of massed machine-readable media may include non-volatile memory, such as semiconductor memory devices (e.g., electrically programmable read-only memory (EPROM), or electrically erasable programmable read-only memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD- ROM disks.
The instructions 824 may further be transmitted or received over a communications network ZZ26 using a transmission medium via the network interface device/transceiver ZZ20 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communications networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), plain old telephone (POTS) networks, wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax®), IEEE 802.15.4 family of standards, and peer-to-peer (P2P) networks, among others. In an example, the network interface device/transceiver ZZ20 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 826. In an example, the network interface device/transceiver 820 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multipleinput multiple-output (MIMO), or multiple-input single-output (MISO) techniques. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding, or carrying instructions for execution by the machine 800 and includes digital or analog communications signals or other intangible media to facilitate communication of such software. The operations and processes described and shown above may be carried out or performed in any suitable order as desired in various implementations. Additionally, in certain implementations, at least a portion of the operations may be carried out in parallel. Furthermore, in certain implementations, less than or more than the operations described may be performed.
FIG. 9 is a block diagram of a radio architecture 105 A, 105B in accordance with some embodiments that may be implemented in any one of the example APs 102 and/or the example user devices 120 of FIG. 1. Radio architecture 105 A, 105B may include radio front-end module (FEM) circuitry 904a-b, radio IC circuitry 906a-b and baseband processing circuitry 908a-b. Radio architecture 105 A, 105B as shown includes both Wireless Local Area Network (WLAN) functionality and Bluetooth (BT) functionality although embodiments are not so limited. In this disclosure, “WLAN” and “Wi-Fi” are used interchangeably.
FEM circuitry 904a-b may include a WLAN or Wi-Fi FEM circuitry 904a and a Bluetooth (BT) FEM circuitry 904b. The WLAN FEM circuitry 904a may include a receive signal path comprising circuitry configured to operate on WLAN RF signals received from one or more antennas 901, to amplify the received signals and to provide the amplified versions of the received signals to the WLAN radio IC circuitry 906a for further processing. The BT FEM circuitry 904b may include a receive signal path which may include circuitry configured to operate on BT RF signals received from one or more antennas 901, to amplify the received signals and to provide the amplified versions of the received signals to the BT radio IC circuitry 906b for further processing. FEM circuitry 904a may also include a transmit signal path which may include circuitry configured to amplify WLAN signals provided by the radio IC circuitry 906a for wireless transmission by one or more of the antennas 901. In addition, FEM circuitry 904b may also include a transmit signal path which may include circuitry configured to amplify BT signals provided by the radio IC circuitry 906b for wireless transmission by the one or more antennas. In the embodiment of FIG. 9, although FEM 904a and FEM 904b are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of an FEM (not shown) that includes a transmit path and/or a receive path for both WLAN and BT signals, or the use of one or more FEM circuitries where at least some of the FEM circuitries share transmit and/or receive signal paths for both WLAN and BT signals.
Radio IC circuitry 906a-b as shown may include WLAN radio IC circuitry 906a and BT radio IC circuitry 906b. The WLAN radio IC circuitry 906a may include a receive signal path which may include circuitry to down-convert WLAN RF signals received from the FEM circuitry 904a and provide baseband signals to WLAN baseband processing circuitry 908a. BT radio IC circuitry 906b may in turn include a receive signal path which may include circuitry to downconvert BT RF signals received from the FEM circuitry 904b and provide baseband signals to BT baseband processing circuitry 908b. WLAN radio IC circuitry 906a may also include a transmit signal path which may include circuitry to up-convert WLAN baseband signals provided by the WLAN baseband processing circuitry 908a and provide WLAN RF output signals to the FEM circuitry 904a for subsequent wireless transmission by the one or more antennas 901. BT radio IC circuitry 906b may also include a transmit signal path which may include circuitry to up-convert BT baseband signals provided by the BT baseband processing circuitry 908b and provide BT RF output signals to the FEM circuitry 904b for subsequent wireless transmission by the one or more antennas 901. In the embodiment of FIG. 9, although radio IC circuitries 906a and 906b are shown as being distinct from one another, embodiments are not so limited, and include within their scope the use of a radio IC circuitry (not shown) that includes a transmit signal path and/or a receive signal path for both WLAN and BT signals, or the use of one or more radio IC circuitries where at least some of the radio IC circuitries share transmit and/or receive signal paths for both WLAN and BT signals.
Baseband processing circuity 908a-b may include a WLAN baseband processing circuitry 908a and a BT baseband processing circuitry 908b. The WLAN baseband processing circuitry 908a may include a memory, such as, for example, a set of RAM arrays in a Fast Fourier Transform or Inverse Fast Fourier Transform block (not shown) of the WLAN baseband processing circuitry 908a. Each of the WLAN baseband circuitry 908a and the BT baseband circuitry 908b may further include one or more processors and control logic to process the signals received from the corresponding WLAN or BT receive signal path of the radio IC circuitry 906a- b, and to also generate corresponding WLAN or BT baseband signals for the transmit signal path of the radio IC circuitry 906a-b. Each of the baseband processing circuitries 908a and 908b may further include physical layer (PHY) and medium access control layer (MAC) circuitry, and may further interface with a device for generation and processing of the baseband signals and for controlling operations of the radio IC circuitry 906a-b.
Referring still to FIG. 9, according to the shown embodiment, WLAN-BT coexistence circuitry 913 may include logic providing an interface between the WLAN baseband circuitry 908a and the BT baseband circuitry 908b to enable use cases requiring WLAN and BT coexistence. In addition, a switch 903 may be provided between the WLAN FEM circuitry 904a and the BT FEM circuitry 904b to allow switching between the WLAN and BT radios according to application needs. In addition, although the antennas 901 are depicted as being respectively connected to the WLAN FEM circuitry 904a and the BT FEM circuitry 904b, embodiments include within their scope the sharing of one or more antennas as between the WLAN and BT FEMs, or the provision of more than one antenna connected to each of FEM 904a or 904b.
In some embodiments, the front-end module circuitry 904a-b, the radio IC circuitry 906a- b, and baseband processing circuitry 908a-b may be provided on a single radio card, such as wireless radio card 902. In some other embodiments, the one or more antennas 901, the FEM circuitry 904a-b and the radio IC circuitry 906a-b may be provided on a single radio card. In some other embodiments, the radio IC circuitry 906a-b and the baseband processing circuitry 908a-b may be provided on a single chip or integrated circuit (IC), such as IC 912.
In some embodiments, the wireless radio card 902 may include a WLAN radio card and may be configured for Wi-Fi communications, although the scope of the embodiments is not limited in this respect. In some of these embodiments, the radio architecture 105 A, 105B may be configured to receive and transmit orthogonal frequency division multiplexed (OFDM) or orthogonal frequency division multiple access (OFDMA) communication signals over a multicarrier communication channel. The OFDM or OFDMA signals may comprise a plurality of orthogonal subcarriers.
In some of these multicarrier embodiments, radio architecture 105 A, 105B may be part of a Wi-Fi communication station (STA) such as a wireless access point (AP), a base station or a mobile device including a Wi-Fi device. In some of these embodiments, radio architecture 105A, 105B may be configured to transmit and receive signals in accordance with specific communication standards and/or protocols, such as any of the Institute of Electrical and Electronics Engineers (IEEE) standards including, 802.1 ln-2009, IEEE 802.11-2012, IEEE 802.11-2016, 802.11n-2009, 802.11ac, 802.11ah, 802.11ad, 802.1 lay and/or 802.1 lax standards and/or proposed specifications for WLANs, although the scope of embodiments is not limited in this respect. Radio architecture 105A, 105B may also be suitable to transmit and/or receive communications in accordance with other techniques and standards.
In some embodiments, the radio architecture 105A, 105B may be configured for high- efficiency Wi-Fi (HEW) communications in accordance with the IEEE 802.1 lax standard. In these embodiments, the radio architecture 105A, 105B may be configured to communicate in accordance with an OFDMA technique, although the scope of the embodiments is not limited in this respect.
In some other embodiments, the radio architecture 105A, 105B may be configured to transmit and receive signals transmitted using one or more other modulation techniques such as spread spectrum modulation (e.g., direct sequence code division multiple access (DS-CDMA) and/or frequency hopping code division multiple access (FH-CDMA)), time-division multiplexing (TDM) modulation, and/or frequency-division multiplexing (FDM) modulation, although the scope of the embodiments is not limited in this respect.
In some embodiments, as further shown in FIG. 6, the BT baseband circuitry 908b may be compliant with a Bluetooth (BT) connectivity standard such as Bluetooth, Bluetooth 8.0 or Bluetooth 6.0, or any other iteration of the Bluetooth Standard.
In some embodiments, the radio architecture 105 A, 105B may include other radio cards, such as a cellular radio card configured for cellular (e.g., 5GPP such as LTE, LTE- Advanced or 7G communications).
In some IEEE 802.11 embodiments, the radio architecture 105A, 105B may be configured for communication over various channel bandwidths including bandwidths having center frequencies of about 900 MHz, 2.4 GHz, 5 GHz, and bandwidths of about 2 MHz, 4 MHz, 5 MHz, 5.5 MHz, 6 MHz, 8 MHz, 10 MHz, 20 MHz, 40 MHz, 80 MHz (with contiguous bandwidths) or 80+80 MHz (160MHz) (with non-contiguous bandwidths). In some embodiments, a 920 MHz channel bandwidth may be used. The scope of the embodiments is not limited with respect to the above center frequencies however.
FIG. 10 illustrates WLAN FEM circuitry 904a in accordance with some embodiments. Although the example of FIG. 10 is described in conjunction with the WLAN FEM circuitry 904a, the example of FIG. 10 may be described in conjunction with the example BT FEM circuitry 904b (FIG. 9), although other circuitry configurations may also be suitable.
In some embodiments, the FEM circuitry 904a may include a TX/RX switch 1002 to switch between transmit mode and receive mode operation. The FEM circuitry 904a may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 904a may include a low-noise amplifier (LNA) 1006 to amplify received RF signals 1003 and provide the amplified received RF signals 1007 as an output (e.g., to the radio IC circuitry 906a- b (FIG. 9)). The transmit signal path of the circuitry 904a may include a power amplifier (PA) to amplify input RF signals 1009 (e.g., provided by the radio IC circuitry 906a-b), and one or more filters 1012, such as band-pass filters (BPFs), low-pass filters (LPFs) or other types of filters, to generate RF signals 1015 for subsequent transmission (e.g., by one or more of the antennas 901 (FIG. 9)) via an example duplexer 1014.
In some dual-mode embodiments for Wi-Fi communication, the FEM circuitry 904a may be configured to operate in either the 2.4 GHz frequency spectrum or the 5 GHz frequency spectrum. In these embodiments, the receive signal path of the FEM circuitry 904a may include a receive signal path duplexer 1004 to separate the signals from each spectrum as well as provide a separate LNA 1006 for each spectrum as shown. In these embodiments, the transmit signal path of the FEM circuitry 904a may also include a power amplifier 1010 and a filter 1012, such as a BPF, an LPF or another type of filter for each frequency spectrum and a transmit signal path duplexer 1004 to provide the signals of one of the different spectrums onto a single transmit path for subsequent transmission by the one or more of the antennas 901 (FIG. 9). In some embodiments, BT communications may utilize the 2.4 GHz signal paths and may utilize the same FEM circuitry 904a as the one used for WEAN communications.
FIG. 11 illustrates radio IC circuitry 906a in accordance with some embodiments. The radio IC circuitry 906a is one example of circuitry that may be suitable for use as the WLAN or BT radio IC circuitry 906a/906b (FIG. 9), although other circuitry configurations may also be suitable. Alternatively, the example of FIG. 11 may be described in conjunction with the example BT radio IC circuitry 906b.
In some embodiments, the radio IC circuitry 906a may include a receive signal path and a transmit signal path. The receive signal path of the radio IC circuitry 906a may include at least mixer circuitry 1102, such as, for example, down-conversion mixer circuitry, amplifier circuitry 1106 and filter circuitry 1108. The transmit signal path of the radio IC circuitry 906a may include at least filter circuitry 1112 and mixer circuitry 1114, such as, for example, up-conversion mixer circuitry. Radio IC circuitry 906a may also include synthesizer circuitry 1104 for synthesizing a frequency 1105 for use by the mixer circuitry 1102 and the mixer circuitry 1114. The mixer circuitry 1102 and/or 1114 may each, according to some embodiments, be configured to provide direct conversion functionality. The latter type of circuitry presents a much simpler architecture as compared with standard super-heterodyne mixer circuitries, and any flicker noise brought about by the same may be alleviated for example through the use of OFDM modulation. FIG. 11 illustrates only a simplified version of a radio IC circuitry, and may include, although not shown, embodiments where each of the depicted circuitries may include more than one component. For instance, mixer circuitry 1114 may each include one or more mixers, and filter circuitries 1108 and/or 1112 may each include one or more filters, such as one or more BPFs and/or LPFs according to application needs. For example, when mixer circuitries are of the direct-conversion type, they may each include two or more mixers.
In some embodiments, mixer circuitry 1102 may be configured to down-convert RF signals 1007 received from the FEM circuitry 904a-b (FIG. 9) based on the synthesized frequency 1105 provided by synthesizer circuitry 1104. The amplifier circuitry 1106 may be configured to amplify the down-converted signals and the filter circuitry 1108 may include an LPF configured to remove unwanted signals from the down-converted signals to generate output baseband signals 1107. Output baseband signals 1107 may be provided to the baseband processing circuitry 908a-b (FIG. 9) for further processing. In some embodiments, the output baseband signals 1107 may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1102 may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
In some embodiments, the mixer circuitry 1114 may be configured to up-convert input baseband signals 1111 based on the synthesized frequency 1105 provided by the synthesizer circuitry 1104 to generate RF output signals 1009 for the FEM circuitry 904a-b. The baseband signals 1111 may be provided by the baseband processing circuitry 908a-b and may be filtered by filter circuitry 1112. The filter circuitry 1112 may include an LPF or a BPF, although the scope of the embodiments is not limited in this respect.
In some embodiments, the mixer circuitry 1102 and the mixer circuitry 1114 may each include two or more mixers and may be arranged for quadrature down-conversion and/or up- conversion respectively with the help of synthesizer 1104. In some embodiments, the mixer circuitry 1102 and the mixer circuitry 1114 may each include two or more mixers each configured for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1102 and the mixer circuitry 1114 may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuitry 1102 and the mixer circuitry 1114 may be configured for super-heterodyne operation, although this is not a requirement.
Mixer circuitry 1102 may comprise, according to one embodiment: quadrature passive mixers (e.g., for the in-phase (I) and quadrature phase (Q) paths). In such an embodiment, RF input signal 1007 from FIG. 11 may be down-converted to provide I and Q baseband output signals to be sent to the baseband processor.
Quadrature passive mixers may be driven by zero and ninety-degree time-varying LO switching signals provided by a quadrature circuitry which may be configured to receive a LO frequency (fLO) from a local oscillator or a synthesizer, such as LO frequency 1105 of synthesizer 1104 (FIG. 11). In some embodiments, the LO frequency may be the carrier frequency, while in other embodiments, the LO frequency may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the zero and ninety-degree time-varying switching signals may be generated by the synthesizer, although the scope of the embodiments is not limited in this respect.
In some embodiments, the LO signals may differ in duty cycle (the percentage of one period in which the LO signal is high) and/or offset (the difference between start points of the period). In some embodiments, the LO signals may have an 85% duty cycle and an 80% offset. In some embodiments, each branch of the mixer circuitry (e.g., the in-phase (I) and quadrature phase (Q) path) may operate at an 80% duty cycle, which may result in a significant reduction is power consumption.
The RF input signal 1007 (FIG. 10) may comprise a balanced signal, although the scope of the embodiments is not limited in this respect. The I and Q baseband output signals may be provided to low-noise amplifier, such as amplifier circuitry 1106 (FIG. 11) or to filter circuitry 1108 (FIG. 11).
In some embodiments, the output baseband signals 1107 and the input baseband signals 1111 may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals 1107 and the input baseband signals 1111 may be digital baseband signals. In these alternate embodiments, the radio IC circuitry may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry.
In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, or for other spectrums not mentioned here, although the scope of the embodiments is not limited in this respect.
In some embodiments, the synthesizer circuitry 1104 may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1104 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider. According to some embodiments, the synthesizer circuitry 1104 may include digital synthesizer circuitry. An advantage of using a digital synthesizer circuitry is that, although it may still include some analog components, its footprint may be scaled down much more than the footprint of an analog synthesizer circuitry. In some embodiments, frequency input into synthesizer circuity 1104 may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. A divider control input may further be provided by either the baseband processing circuitry 908a-b (FIG. 9) depending on the desired output frequency 1105. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table (e.g., within a Wi-Fi card) based on a channel number and a channel center frequency as determined or indicated by the example application processor 910. The application processor 910 may include, or otherwise be connected to, one of the example secure signal converter 101 or the example received signal converter 103 (e.g., depending on which device the example radio architecture is implemented in).
In some embodiments, synthesizer circuitry 1104 may be configured to generate a carrier frequency as the output frequency 1105, while in other embodiments, the output frequency 1105 may be a fraction of the carrier frequency (e.g., one-half the carrier frequency, one-third the carrier frequency). In some embodiments, the output frequency 1105 may be a LO frequency (fLO).
FIG. 12 illustrates a functional block diagram of baseband processing circuitry 908a in accordance with some embodiments. The baseband processing circuitry 908a is one example of circuitry that may be suitable for use as the baseband processing circuitry 908a (FIG. 9), although other circuitry configurations may also be suitable. Alternatively, the example of FIG. 11 may be used to implement the example BT baseband processing circuitry 908b of FIG. 9.
The baseband processing circuitry 908a may include a receive baseband processor (RX BBP) 1202 for processing receive baseband signals 1109 provided by the radio IC circuitry 906a- b (FIG. 9) and a transmit baseband processor (TX BBP) 1204 for generating transmit baseband signals 1111 for the radio IC circuitry 906a-b. The baseband processing circuitry 908a may also include control logic 1206 for coordinating the operations of the baseband processing circuitry 908a.
In some embodiments (e.g., when analog baseband signals are exchanged between the baseband processing circuitry 908a-b and the radio IC circuitry 906a-b), the baseband processing circuitry 908a may include ADC 1210 to convert analog baseband signals 1209 received from the radio IC circuitry 906a-b to digital baseband signals for processing by the RX BBP 1202. In these embodiments, the baseband processing circuitry 908a may also include DAC 1212 to convert digital baseband signals from the TX BBP 1204 to analog baseband signals 1211.
In some embodiments that communicate OFDM signals or OFDMA signals, such as through baseband processor 908a, the transmit baseband processor 1204 may be configured to generate OFDM or OFDMA signals as appropriate for transmission by performing an inverse fast Fourier transform (IFFT). The receive baseband processor 1202 may be configured to process received OFDM signals or OFDMA signals by performing an FFT. In some embodiments, the receive baseband processor 1202 may be configured to detect the presence of an OFDM signal or OFDMA signal by performing an autocorrelation, to detect a preamble, such as a short preamble, and by performing a cross-correlation, to detect a long preamble. The preambles may be part of a predetermined frame structure for Wi-Fi communication.
Referring back to FIG. 9, in some embodiments, the antennas 901 (FIG. 9) may each comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input multiple-output (MIMO) embodiments, the antennas may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result. Antennas 901 may each include a set of phased-array antennas, although embodiments are not so limited.
Although the radio architecture 105A, 105B is illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), and/or other hardware elements. For example, some elements may comprise one or more microprocessors, DSPs, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.
The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments. The terms “computing device,” “user device,” “communication station,” “station,” “handheld device,” “mobile device,” “wireless device” and “user equipment” (UE) as used herein refers to a wireless communication device such as a cellular telephone, a smartphone, a tablet, a netbook, a wireless terminal, a laptop computer, a femtocell, a high data rate (HDR) subscriber station, an access point, a printer, a point of sale device, an access terminal, or other personal communication system (PCS) device. The device may be either mobile or stationary.
As used within this document, the term “communicate” is intended to include transmitting, or receiving, or both transmitting and receiving. This may be particularly useful in claims when describing the organization of data that is being transmitted by one device and received by another, but only the functionality of one of those devices is required to infringe the claim. Similarly, the bidirectional exchange of data between two devices (both devices transmit and receive during the exchange) may be described as “communicating,” when only the functionality of one of those devices is being claimed. The term “communicating” as used herein with respect to a wireless communication signal includes transmitting the wireless communication signal and/or receiving the wireless communication signal. For example, a wireless communication unit, which is capable of communicating a wireless communication signal, may include a wireless transmitter to transmit the wireless communication signal to at least one other wireless communication unit, and/or a wireless communication receiver to receive the wireless communication signal from at least one other wireless communication unit.
As used herein, unless otherwise specified, the use of the ordinal adjectives “first,” “second,” “third,” etc., to describe a common object, merely indicates that different instances of like objects are being referred to and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.
The term “access point” (AP) as used herein may be a fixed station. An access point may also be referred to as an access node, a base station, an evolved node B (eNodeB), or some other similar terminology known in the art. An access terminal may also be called a mobile station, user equipment (UE), a wireless communication device, or some other similar terminology known in the art. Embodiments disclosed herein generally pertain to wireless networks. Some embodiments may relate to wireless networks that operate in accordance with one of the IEEE 802.11 standards.
Some embodiments may be used in conjunction with various devices and systems, for example, a personal computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non- vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a wireless video area network (WVAN), a local area network (LAN), a wireless LAN (WLAN), a personal area network (PAN), a wireless PAN (WPAN), and the like.
Some embodiments may be used in conjunction with one way and/or two-way radio communication systems, cellular radio-telephone communication systems, a mobile phone, a cellular telephone, a wireless telephone, a personal communication system (PCS) device, a PDA device which incorporates a wireless communication device, a mobile or portable global positioning system (GPS) device, a device which incorporates a GPS receiver or transceiver or chip, a device which incorporates an RFID element or chip, a multiple input multiple output (MIMO) transceiver or device, a single input multiple output (SIMO) transceiver or device, a multiple input single output (MISO) transceiver or device, a device having one or more internal antennas and/or external antennas, digital video broadcast (DVB) devices or systems, multistandard radio devices or systems, a wired or wireless handheld device, e.g., a smartphone, a wireless application protocol (WAP) device, or the like.
Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems following one or more wireless communication protocols, for example, radio frequency (RF), infrared (IR), frequency-division multiplexing (FDM), orthogonal FDM (OFDM), time-division multiplexing (TDM), time-division multiple access (TDMA), extended TDMA (E-TDMA), general packet radio service (GPRS), extended GPRS, code-division multiple access (CDMA), wideband CDMA (WCDMA), CDMA 2000, single-carrier CDMA, multi-carrier CDMA, multi-carrier modulation (MDM), discrete multi- tone (DMT), Bluetooth®, global positioning system (GPS), Wi-Fi, Wi-Max, ZigBee, ultra- wideband (UWB), global system for mobile communications (GSM), 2G, 2.5G, 3G, 3.5G, 4G, fifth generation (5G) mobile networks, 3 GPP, long term evolution (LTE), LTE advanced, enhanced data rates for GSM Evolution (EDGE), or the like. Other embodiments may be used in various other devices, systems, and/or networks.
The following examples pertain to further embodiments.
Example 1 may be an apparatus of a device comprising memory and processing circuitry configured to: identify an Internet connection; present one or more identity providers (IDPs) associated with an OpenRoaming Wi-Fi connection; receive a user selection of an IDP of the one or more IDPs; generate an OpenRoaming profile with the IDP; install the OpenRoaming profile; and establish the OpenRoaming Wi-Fi connection using the OpenRoaming profile.
Example 2 may include the apparatus of example 1 and/or some other example herein, wherein to establish the OpenRoaming Wi-Fi connection occurs without user input.
Example 3 may include the apparatus of example 1 and/or some other example herein, wherein a cellular subscriber identification module (SIM) card is absent from the device.
Example 4 may include the apparatus of example 1 and/or some other example herein, wherein the IDP has an OpenRoaming provisioning portal, and wherein to generate the OpenRoaming profile with the IDP comprises the processing circuitry being further configured to: re-direct the device to the OpenRoaming portal; and receive a username and password or certificate for the device, wherein the OpenRoaming profile is based on the username and password or certificate.
Example 5 may include the apparatus of example 1 and/or some other example herein, wherein the IDP does not have an OpenRoaming provisioning portal, and wherein to generate the OpenRoaming profile with the IDP comprises the processing circuitry being further configured to: initiate an oAuth authentication protocol with the IDP; and receive a username and password or certificate for the device, wherein the OpenRoaming profile is based on the username and password or certificate.
Example 6 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry is further configured to identify the one or more IDPs based on IDP data provided to an OpenRoaming system by the one or more IDPs.
Example 7 may include the apparatus of example 1 and/or some other example herein, wherein the processing circuitry is further configured to re-direct the device to a web-based portal with oAuth authentication protocol support for the IDP.
Example 8 may include the apparatus of example 1 and/or some other example herein, the device further comprising a transceiver configured to transmit and receive wireless signals associated with generating the OpenRoaming profile.
Example 9 may include the device of example 8 and/or some other example herein, further comprising one or more antennas coupled to the transceiver to cause to send the wireless signals.
Example 10 may include a non- transitory computer-readable medium storing computerexecutable instructions which when executed by one or more processors result in performing operations comprising: identifying an Internet connection of a device; presenting one or more identity providers (IDPs) associated with an OpenRoaming Wi-Fi connection; receiving a user selection of an IDP of the one or more IDPs; generating an OpenRoaming profile with the IDP; installing the OpenRoaming profile; and establishing the OpenRoaming Wi-Fi connection using the OpenRoaming profile.
Example 11 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein establishing the OpenRoaming Wi-Fi connection occurs without user input. Example 12 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein a cellular subscriber identification module (SIM) card is absent from the device.
Example 13 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the IDP has an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: re-directing the device to the OpenRoaming portal; and receiving a username and password for the device, wherein the OpenRoaming profile is based on the username and password.
Example 14 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, wherein the IDP does not have an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: initiating an oAuth authentication protocol with the IDP; and receiving a username and password for the device, wherein the OpenRoaming profile is based on the username and password.
Example 15 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, the operations further comprising identifying the one or more IDPs based on IDP data provided to an OpenRoaming system by the one or more IDPs.
Example 16 may include the non-transitory computer-readable medium of example 10 and/or some other example herein, the operations further comprising re-directing the device to a web-based portal with oAuth authentication protocol support for the IDP.
Example 17 may include a method comprising: identifying, by processing circuitry of a device, an Internet connection of a device; presenting, by the processing circuitry, one or more identity providers (IDPs) associated with an OpenRoaming Wi-Fi connection; receiving, by the processing circuitry, a user selection of an IDP of the one or more IDPs; generating, by the processing circuitry, an OpenRoaming profile with the IDP; installing, by the processing circuitry, the OpenRoaming profile; and establishing, by the processing circuitry, the OpenRoaming Wi-Fi connection using the OpenRoaming profile.
Example 18 may include the method of example 17 and/or some other example herein, wherein the IDP has an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: re-directing the device to the OpenRoaming portal; and receiving a username and password or certificate for the device, wherein the OpenRoaming profile is based on the username and password or certificate.
Example 19 may include the method of example 17 and/or some other example herein, wherein the IDP does not have an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: initiating an oAuth authentication protocol with the IDP; and receiving a username and password for the device or certificate, wherein the OpenRoaming profile is based on the username and password or certificate.
Example 20 may include the method of example 17 and/or some other example herein, further comprising re-directing the device to a web-based portal with oAuth authentication protocol support for the IDP.
Example 21 may include one or more non- transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein
Example 22 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1-20, or any other method or process described herein.
Example 23 may include a method, technique, or process as described in or related to any of examples 1-20, or portions or parts thereof.
Example 24 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1-20, or portions thereof.
Example 25 may include a method of communicating in a wireless network as shown and described herein.
Example 26 may include a system for providing wireless communication as shown and described herein.
Example 27 may include a device for providing wireless communication as shown and described herein.
Embodiments according to the disclosure are in particular disclosed in the attached claims directed to a method, a storage medium, a device and a computer program product, wherein any feature mentioned in one claim category, e.g., method, can be claimed in another claim category, e.g., system, as well. The dependencies or references back in the attached claims are chosen for formal reasons only. However, any subject matter resulting from a deliberate reference back to any previous claims (in particular multiple dependencies) can be claimed as well, so that any combination of claims and the features thereof are disclosed and can be claimed regardless of the dependencies chosen in the attached claims. The subject-matter which can be claimed comprises not only the combinations of features as set out in the attached claims but also any other combination of features in the claims, wherein each feature mentioned in the claims can be combined with any other feature or combination of other features in the claims. Furthermore, any of the embodiments and features described or depicted herein can be claimed in a separate claim and/or in any combination with any embodiment or feature described or depicted herein or with any of the features of the attached claims.
The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.
Certain aspects of the disclosure are described above with reference to block and flow diagrams of systems, methods, apparatuses, and/or computer program products according to various implementations. It will be understood that one or more blocks of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and the flow diagrams, respectively, may be implemented by computer-executable program instructions. Likewise, some blocks of the block diagrams and flow diagrams may not necessarily need to be performed in the order presented, or may not necessarily need to be performed at all, according to some implementations .
These computer-executable program instructions may be loaded onto a special-purpose computer or other particular machine, a processor, or other programmable data processing apparatus to produce a particular machine, such that the instructions that execute on the computer, processor, or other programmable data processing apparatus create means for implementing one or more functions specified in the flow diagram block or blocks. These computer program instructions may also be stored in a computer-readable storage media or memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage media produce an article of manufacture including instruction means that implement one or more functions specified in the flow diagram block or blocks. As an example, certain implementations may provide for a computer program product, comprising a computer-readable storage medium having a computer-readable program code or program instructions implemented therein, said computer-readable program code adapted to be executed to implement one or more functions specified in the flow diagram block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational elements or steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions that execute on the computer or other programmable apparatus provide elements or steps for implementing the functions specified in the flow diagram block or blocks.
Accordingly, blocks of the block diagrams and flow diagrams support combinations of means for performing the specified functions, combinations of elements or steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the block diagrams and flow diagrams, and combinations of blocks in the block diagrams and flow diagrams, may be implemented by special-purpose, hardware -based computer systems that perform the specified functions, elements or steps, or combinations of special-purpose hardware and computer instructions.
Conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain implementations could include, while other implementations do not include, certain features, elements, and/or operations. Thus, such conditional language is not generally intended to imply that features, elements, and/or operations are in any way required for one or more implementations or that one or more implementations necessarily include logic for deciding, with or without user input or prompting, whether these features, elements, and/or operations are included or are to be performed in any particular implementation.
Many modifications and other implementations of the disclosure set forth herein will be apparent having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific implementations disclosed and that modifications and other implementations are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

CLAIMS What is claimed is:
1. An apparatus of a device, the apparatus comprising processing circuitry coupled to storage, the processing circuitry configured to: identify an Internet connection; present one or more identity providers (IDPs) associated with an OpenRoaming WiFi connection; receive a user selection of an IDP of the one or more IDPs; generate an OpenRoaming profile with the IDP; install the OpenRoaming profile; and establish the OpenRoaming Wi-Fi connection using the OpenRoaming profile.
2. The apparatus of claim 1, wherein to establish the OpenRoaming Wi-Fi connection occurs without user input.
3. The apparatus of claim 1, wherein a cellular subscriber identification module (SIM) card is absent from the device.
4. The apparatus of claim 1, wherein the IDP has an OpenRoaming provisioning portal, and wherein to generate the OpenRoaming profile with the IDP comprises the processing circuitry being further configured to: re-direct the device to the OpenRoaming portal; and receive a username and password or certificate for the device, wherein the OpenRoaming profile is based on the username and password or certificate.
5. The apparatus of claim 1, wherein the IDP does not have an OpenRoaming provisioning portal, and wherein to generate the OpenRoaming profile with the IDP comprises the processing circuitry being further configured to: initiate an oAuth authentication protocol with the IDP; and receive a username and password or certificate for the device,
36 wherein the OpenRoaming profile is based on the username and password or certificate.
6. The apparatus of claim 1, wherein the processing circuitry is further configured to identify the one or more IDPs based on IDP data provided to an OpenRoaming system by the one or more IDPs.
7. The apparatus of claim 1, wherein the processing circuitry is further configured to redirect the device to a web-based portal with oAuth authentication protocol support for the IDP.
8. The apparatus of claim 1, the device further comprising a transceiver configured to transmit and receive wireless signals associated with generating the OpenRoaming profile.
9. The apparatus of claim 8, the device further comprising an antenna coupled to the transceiver to cause to send the wireless signals.
10. A non-transitory computer-readable medium storing computer-executable instructions which when executed by one or more processors result in performing operations comprising: identifying an Internet connection of a device; presenting one or more identity providers (IDPs) associated with an OpenRoaming Wi-Fi connection; receiving a user selection of an IDP of the one or more IDPs; generating an OpenRoaming profile with the IDP; installing the OpenRoaming profile; and establishing the OpenRoaming Wi-Fi connection using the OpenRoaming profile.
11. The non-transitory computer-readable medium of claim 10, wherein establishing the OpenRoaming Wi-Fi connection occurs without user input.
12. The non-transitory computer-readable medium of claim 10, wherein a cellular subscriber identification module (SIM) card is absent from the device.
37
13. The non- transitory computer-readable medium of claim 10, wherein the IDP has an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: re-directing the device to the OpenRoaming portal; and receiving a username and password for the device, wherein the OpenRoaming profile is based on the username and password.
14. The non-transitory computer-readable medium of claim 10, wherein the IDP does not have an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: initiating an oAuth authentication protocol with the IDP; and receiving a username and password for the device, wherein the OpenRoaming profile is based on the username and password.
15. The non-transitory computer-readable medium of claim 10, the operations further comprising identifying the one or more IDPs based on IDP data provided to an OpenRoaming system by the one or more IDPs.
16. The non-transitory computer-readable medium of claim 10, the operations further comprising re-directing the device to a web-based portal with oAuth authentication protocol support for the IDP.
17. A method comprising: identifying, by processing circuitry of a first device, an Internet connection of a second device; presenting, by the processing circuitry, one or more identity providers (IDPs) associated with an OpenRoaming Wi-Fi connection for the second device; receiving, by the processing circuitry, a user selection of an IDP of the one or more IDPs; generating, by the processing circuitry, an OpenRoaming profile with the IDP; installing, by the processing circuitry, the OpenRoaming profile on the second device; and establishing, by the processing circuitry, the OpenRoaming Wi-Fi connection using the OpenRoaming profile.
18. The method of claim 17, wherein the IDP has an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: re-directing the second device to the OpenRoaming portal; and receiving a username and password or certificate for the second device, wherein the OpenRoaming profile is based on the username and password or certificate.
19. The method of claim 17, wherein the IDP does not have an OpenRoaming provisioning portal, and wherein generating the OpenRoaming profile with the IDP comprises: initiating an oAuth authentication protocol with the IDP; and receiving a username and password or certificate for the second device, wherein the OpenRoaming profile is based on the username and password or certificate.
20. The method of claim 17, further comprising re-directing the second device to a webbased portal with oAuth authentication protocol support for the IDP.
21. The method of claim 17, wherein establishing the OpenRoaming Wi-Fi connection occurs without user input.
22. The method of claim 17, wherein a cellular subscriber identification module (SIM) card is absent from the second device.
23. The method of claim 17, further comprising identifying the one or more IDPs based on IDP data provided to an OpenRoaming system by the one or more IDPs.
24. The method of claim 17, further comprising authenticating the second device, using an extensible authentication protocol (EAP), to a first IDP of the one or more IDPs.
25. The method of claim 17, wherein presenting the one or more IDPs is based on a domain name server (DNS) registration.
EP21881204.8A 2020-10-15 2021-10-15 ENHANCED MECHANISM FOR OUT-OF-BAND ACTIVATION AND PROVISIONING OF MOBILE DEVICES FOR OPENROAMING NETWORKS Pending EP4229892A4 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US202063092366P 2020-10-15 2020-10-15
US202063112910P 2020-11-12 2020-11-12
PCT/US2021/055252 WO2022082024A1 (en) 2020-10-15 2021-10-15 Enhanced mechanism for out-of-band activation and provisioning of mobile devices for openroaming networks

Publications (2)

Publication Number Publication Date
EP4229892A1 true EP4229892A1 (en) 2023-08-23
EP4229892A4 EP4229892A4 (en) 2024-10-23

Family

ID=81208700

Family Applications (1)

Application Number Title Priority Date Filing Date
EP21881204.8A Pending EP4229892A4 (en) 2020-10-15 2021-10-15 ENHANCED MECHANISM FOR OUT-OF-BAND ACTIVATION AND PROVISIONING OF MOBILE DEVICES FOR OPENROAMING NETWORKS

Country Status (2)

Country Link
EP (1) EP4229892A4 (en)
WO (1) WO2022082024A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12426079B2 (en) 2023-02-23 2025-09-23 Cisco Technology, Inc. Prioritizing network traffic for emergency services

Also Published As

Publication number Publication date
EP4229892A4 (en) 2024-10-23
WO2022082024A1 (en) 2022-04-21

Similar Documents

Publication Publication Date Title
US11696353B2 (en) Single-radio multi-channel medium access
US20190349758A1 (en) Ultrasound-assisted wi-fi and bluetooth authentication
US12356255B2 (en) Link recommendation for basic service set transition management request for a multi-link device
US12418593B2 (en) Mechanism to enable a federated onboarding service in an openroaming framework
US20210392494A1 (en) Multi-link device resetup and transition with station device address authentication
US20210112414A1 (en) Multi-link device security association query
US12574838B2 (en) Establishing communication between AP and STA using modified QoS
US20260122461A1 (en) Enhanced in-band activation and provisioning of devices for openroaming networks
WO2022094297A1 (en) Restricted service periods
US20230130190A1 (en) Enhancement to sensing by proxy
WO2023024771A1 (en) NON-TRIGGER BASED (TB) SENSING MEASUREMENT FLOW FOR 11bf IN THE SUB-7 GHZ
US12549545B2 (en) Onboarding and enrollment of internet of things devices via federated wireless networks and openroaming framework
US11337068B1 (en) Multi-link device and method performed therein
CN115397032A (en) Randomized Medium Access Control (MAC) address for multi-link devices (MLD)
US20230127717A1 (en) Sensing measurement report for sensing by proxy
EP4240064A1 (en) Mechanism to signal peer-to-peer availability and advertisement
US11943754B2 (en) Extreme high throughput resource unit allocation table
US20240306207A1 (en) Optimizing peer-to-peer communication by utilizing channel availability
WO2022082024A1 (en) Enhanced mechanism for out-of-band activation and provisioning of mobile devices for openroaming networks
EP4412267A1 (en) Mechanism for venue based onboarding of mobile devices for openroaming
US12058522B2 (en) Operating channel validation under protected beacon
US20250048109A1 (en) Enhanced compatibility between next-generation access points and legacy clients through wpa3 capability advertising
US20250126649A1 (en) Extended enhanced multi-link single-radio operation
US20260129563A1 (en) Ultra high reliability neighbor access point probing
EP4213584A1 (en) Future proof null data packet announcement (ndpa) indications

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20230110

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Free format text: PREVIOUS MAIN CLASS: H04W0012084000

Ipc: H04W0012300000

A4 Supplementary search report drawn up and despatched

Effective date: 20240923

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 84/12 20090101ALI20240917BHEP

Ipc: H04W 48/18 20090101ALI20240917BHEP

Ipc: H04L 65/40 20220101ALI20240917BHEP

Ipc: H04L 9/40 20220101ALI20240917BHEP

Ipc: H04W 12/069 20210101ALI20240917BHEP

Ipc: H04W 12/084 20210101ALI20240917BHEP

Ipc: H04W 12/30 20210101AFI20240917BHEP