Patent Description:
Existing <NUM> networks use relatively low radio frequencies, such as frequencies in bands below <NUM>. <NUM> networks are able to use an extended range of frequency bands compared to <NUM> networks, such as higher frequency bands in in the range of <NUM>-<NUM>. Radio communications using the higher frequency <NUM> bands can support higher data speeds, but also have disadvantages compared to the lower frequency bands. Specifically, radio signals in the higher frequencies have shorter range and are more easily blocked by physical objects. Accordingly, the ability for a communication device to communicate using higher-frequency <NUM> bands may be sporadic as the device is physically moved.

Conventionally, users of data networks may gain access to the Internet either through directly connecting to LTE, <NUM>, or <NUM> base stations or by connecting to a modem and router which are physically connected to a broadband network via a cable or wire. The router may be connected to a wireless access point which could be incorporated within the router or be a separate piece of hardware. Computing devices may connect to the router using a service set identifier (SSID), which identifies the router, and in some cases the computing devices may need authentication credentials (e.g., username, password, or both) to associate with the router. Patent document <CIT>, document entitled "<NPL>, and patent document <CIT> are representative of the available art.

In particular, <CIT> is concerned with creating a user-specific virtual network and for this purpose provides an "elastic cell" for the mobile user that follows the mobile node while roaming within the network. The access network, to which a mobile node can attach, is arranged to dynamically reconfigure itself, so that the user can maintain uninterrupted connectivity to its personalized virtual network when the user moves. In this regard, a network controller creates and manages a virtualized Wi-Fi network based on a Wi-Fi network of physical Access Points. The virtualized Wi-Fi network follows the mobile node as it moves around within the same network domain.

The application aims at facilitating delivery of broadband Internet service with respect to the available art.

Accordingly, the invention lies in that delivery of broadband Internet service is facilitated by a method and a telecommunications system as detailed in the claims that follow.

Examples in this disclosure describe methods, apparatuses, computer-readable media, and system(s) for providing broadband Internet access via virtual wireless services. The described virtual wireless services deploy virtual routers provisioned to base stations within a telecommunication network. The base stations may be small cell base stations of a <NUM> telecommunications network, and they can include a transceiver for providing high-frequency data connections (e.g., LTE or NR) and a wireless access point having a transceiver allowing for lower-frequency data connections (e.g., Wi-Fi, WiMAX, or IEEE <NUM>. 1X connections). Wi-Fi and WiMAX are trademarks.

Traditionally, customers receive broadband Internet service through the use of customer premise equipment (CPE). CPE can include, for example, modems, routers, wireless access points, or Wi-Fi range extenders. In some implementations, functionality of multiple CPE can be combined in a single hardware device. For example, a modem, router, and wireless access point may be combined in a single unitary piece of CPE. However, for customers to receive broadband Internet service under the traditional model, a customer must obtain CPE either from the service provider or from a third-party.

Signing up for broadband Internet service can be cumbersome and labor-intensive. An example process for registering for broadband Internet service under the traditional model could include a customer calling a service provider to sign-up and register for service and having to schedule an appointment with the service provider for a technician to install a physical line (such as a fiberoptic cable or coaxial cable) connecting a network hub distanced from the customer's home or building to the home or building. Installation my require drilling holes in exterior walls, and installing and connecting physical equipment inside the customer's home or building. The turnaround time from the moment the customer decides to register for broadband Internet service to when the customer can use the service can often be longer than a week. Such turnaround time can be frustrating to customers and in some instances could result in loss of a customer account for a service provider when the service provider is unable to schedule a technician quickly enough. Moreover, the installation process can be expensive for the customer, service provider, or both due to the labor-intensive nature of installation.

Another issue that arises in traditional delivery of Internet broadband service is that each piece of CPE for each customer operates independently, and often times CPE of multiple customers is of similar make and model for a particular service provider. For example, a service provider may contract with a manufacturer of CPE to rent or sell to its customers, and the service provider may use the same model of CPE for all of its customers. When the service provider provides broadband Internet service to multiple customers within the same neighborhood, apartment building, office building, or same geographical region, customers' CPE may be communicating within the same frequency spectrum range and may be competing for bandwidth. Since each CPE operates independently, they cannot coordinate bandwidth to use it more efficiently. This problem can be exacerbated in high-density service areas, such as a large apartment building in a highly populated city.

To address the above identified concerns, and others, the disclosed examples concern delivering broadband Internet service without, or with minimal use of, CPE. The disclosed examples leverage the ubiquitous nature of small cells in telecommunications networks. Traditionally these small cells deliver NR or LTE based data services to mobile devices. The disclosed examples contemplate base stations also having transceivers providing Wi-Fi (e.g., IEEE <NUM>) data services in addition to transceivers providing NR or LTE based data services. By utilizing base stations having Wi-Fi transceivers, a virtual router can be deployed to base stations within the telecommunications network eliminating or reducing the need for CPE.

Using the disclosed examples, a customer may register for virtual wireless services through a registration portal offered by the service provider. For example, the customer may provide their name, phone number, address, and billing information through the registration portal. The customer may also provide a service set identifier (SSID) to the registration portal. Once the registration process is complete, the service provider may instantiate and deploy a virtual router to a base station proximate to the customer's location. The customer may then be able to connect one or more computing devices or other user equipment to the virtual router using the SSID the customer provided during the registration process.

Base stations according to disclosed examples that include wireless access points can address some of the issues of providing broadband Internet access solely via NR or LTE technology. For example, wireless access point transceivers typically operate within a frequency range where signals can more easily penetrate structures than NR or LTE technology. Additionally, Wi-Fi technology is unlicensed and ubiquitous, especially within the home environment. For example, most Internet of things (IoT) devices, home computing devices, and wireless peripherals communicate via Wi-Fi protocols, making it difficult or impossible for these devices to communicate with a base station that only transmits data over NR or LTE frequency bands without CPE. By providing a wireless access point at the base station, customers can leverage the advantages of Wi-Fi access without the disadvantages and frustrations of needing CPE.

In addition, the disclosed examples describe provisioning virtual wireless services via a common connection point, either the base station itself or via a computer network supporting the base station from the backend. This allows the service provider to manage devices within frequency bands to avoid issues that may arise from crowded bandwidth because it has insight into what devices are connected to particular base stations at a given time. As a result, a telecommunications network employing the disclosed examples may alleviate issues concerning frequency spectrum use that could occur when multiple pieces of CPE are communicating with a single base station on the same, or close, frequencies.

Disclosed examples also allow for a geographically disperse virtual local area network (LAN) with minimal set-up for the customer. For example, a customer may have one or more computing devices or user equipment connected to a base station close to their home. Those devices may be connected to the base station via a virtual router deployed at the base station with the customer's supplied SSID. The customer may also have mobile computing devices that are not at their home. For example, the customer may have a laptop mobile device on their person while they are traveling or while they are at work. With the disclosed examples, all of the customer's devices, whether they be at home or away from home, can communicate with each other as if they were on the same physical LAN. This can allow, for example, a customer to print a document on their home computer-connected to virtual wireless services via a base station close to home-from a mobile device that is far away from their home and connected to a different base station than the customer's home computing devices.

Certain implementations and examples of the disclosure will now be described more fully below with reference to the accompanying figures, in which various aspects are shown. However, the various aspects may be implemented in many different forms and should not be construed as limited to the implementations set forth herein. It will be appreciated that the disclosure encompasses variations of the described examples.

<FIG> illustrates a schematic diagram of an example telecommunications network environment <NUM> providing virtual wireless services consistent with disclosed examples. Network environment <NUM> can include a base station <NUM> that has a cellular transceiver <NUM> and a wireless access point <NUM>. Base station <NUM> can be in communication with a virtual router service <NUM> consistent with disclosed examples. Base station <NUM> can also be in communication with user equipment <NUM> ("UE").

According to some examples, base station <NUM> may communicate voice traffic and/or data traffic with one or more UEs <NUM> using RF signals. In some examples, cellular transceiver <NUM> of base station <NUM> may communicate with UE <NUM> using one or more appropriate cellular wireless communication protocols or standards. For example, cellular transceiver <NUM> may communicate with UE <NUM> using one or more standards, including but not limited to GSM, Time Division Multiple Access (TDMA), Universal Mobile Telecommunications System (UMTS), Evolution-Data Optimized (EVDO), Long Term Evolution (LTE), Fifth Generation (<NUM>), Generic Access Network (GAN), Unlicensed Mobile Access (UMA), Code Division Multiple Access (CDMA) protocols (including IS-<NUM>, IS-<NUM>, and IS-<NUM> protocols), Advanced LTE or LTE+, Orthogonal Frequency Division Multiple Access (OFDM), General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Advanced Mobile Phone System (AMPS).

In some examples, wireless access point <NUM> of base station <NUM> can be configured to communicate with UE using Wi-Fi protocols (including IEEE <NUM> protocols), WiMAX protocols (including IEEE <NUM>. 16e-<NUM> and IEEE <NUM> protocols), High Speed Packet Access (HSPA) (including High Speed Downlink Packet Access (HSDPA) and High Speed Uplink Packet Access (HSUPA)), Ultra Mobile Broadband (UMB), and/or the like. Consistent with disclosed examples, UE <NUM> can communicate with wireless access point <NUM> to receive virtual wireless services via a virtual router, as disclosed herein.

According to some examples, base station <NUM> may support packet-switched or circuit-switched connections and may include a number of network components. Such components may include a home location register (HLR) or HSS for storing user and device information, as well as IMS components, such as the P-CSCF and S-CSCF. The components may also include an application server(s), such as a telephony application server (TAS) or rich communication service (RCS) server. Further, base station <NUM> may connect to networks having an account information server (AIS), which may provide network identities, contact addresses, credentials, and other information to the UEs <NUM>.

According to some examples, base station <NUM> can be a small cell connected to a <NUM> core network comprising any of an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Policy Control Function (PCF), an Application Function (AF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Unified Data Management (UDM), a Network Exposure Function (NEF), a Network Repository Function (NRF), a User Plane Function (UPF), a data network (DN), and the like. Base station <NUM> can include a femtocell, picocell, or microcell providing radio access to UEs <NUM> via cellular transceiver <NUM>.

In addition to, or instead of the configuration described above, base station <NUM> may be connected to a <NUM> core network comprising a Mobility Management Entity (MME), a Serving Gateway (SGW), a Packet Data Network (PDN) Gateway (PGW), a Home Subscriber Server (HSS), an Access Network Discovery and Selection Function (ANDSF), an evolved Packet Data Gateway (ePDG), a Data Network (DN), and the like.

In some cases, base station <NUM> can communicate using licensed spectrum or unlicensed spectrum. For example, base station <NUM> may communicate via wireless access point <NUM> using unlicensed RF bands, such as Wi-Fi, Bluetooth, etc., each of which may have different characteristics that may affect communication with UEs <NUM>. Similarly, base station <NUM> may communicate via cellular transceiver <NUM> using licensed RF bands, such as RF signals according to 3rd Generation Partnership Project (3GPP) protocols, Universal Mobile Telecommunications System (UMTS) protocols, Long Term Evolution (LTE) protocols, Fifth Generation (<NUM>) protocols, etc., which may affect communication with UEs <NUM> differently from each other and from communication with UEs <NUM> using unlicensed spectra. For example, each licensed or unlicensed communication protocol may have different ranges of effectiveness or may have differing abilities to penetrate walls or other materials.

UE <NUM> can include internet-of-things ("IoT") devices <NUM> (e.g., appliances, security cameras, video doorbells, televisions), laptop <NUM>, printer <NUM>, mobile devices <NUM>, computer workstations <NUM>, or servers <NUM>, or other network capable computing devices as just some examples. As shown in <FIG>, user equipment <NUM> can be located within a residence <NUM>, a business <NUM>, or located outside of a building or dwelling. UE <NUM> can include any appropriate device, e.g., a stationary device or a portable electronic device, for communicating over a wireless communication network. As such, UE <NUM> can range in terms of capabilities and features. The UE <NUM> may also comprise a SIM-less device (i.e., a UE that does not contain a functional subscriber identity module ("SIM")), a roaming UE (i.e., a UE operating outside of their home access network), and/or mobile software applications.

In some examples, UE <NUM> can include mobile devices <NUM> that may have a numeric keypad, a capability to display only a few lines of text at a time and be configured to interoperate with Global System for Mobile Communications (GSM) networks. Mobile devices <NUM> may also, or alternatively, have a touch-sensitive screen, a stylus, an embedded Global Positioning System (GPS) receiver, and a relatively high-resolution display, and be configured to interoperate with multiple types of networks.

Virtual router service <NUM> can be a service providing virtual router functions to UE <NUM> via base station <NUM>. The functions provided by virtual router service <NUM> can include those functions that are typical and expected of network routers, as known in the art. For example, these functions can include, among other things, managing authorization and association of one or more UE <NUM> with a LAN, routing data packets between UE <NUM> within the LAN, routing data packets to computing devices outside of the LAN, managing router tables, and providing security features for UE <NUM> connecting to the virtual router. In some examples, virtual router service <NUM> can be a remote service provided by one or more computing systems networked with base station <NUM>, such as a SaaS offered through a cloud computing cluster or server. Although depicted differently in <FIG>, virtual router service <NUM> can also be local to base station <NUM> in some examples.

Base station <NUM> can be in communication with service provider computer system <NUM>. Service provider computer system <NUM> can include one or more processors <NUM> and memory <NUM> storing computer executable instructions that when executed by the one or more processors <NUM> cause the processors to perform operations providing a registration portal <NUM>, a provisioner <NUM>, and lookup services <NUM>. Consistent with disclosed examples, registration portal <NUM>, provisioner <NUM> and lookup services <NUM> can be components enabling provisioning and registration of virtual wireless services to UEs <NUM> within network environment <NUM>.

Registration portal <NUM> can be a web portal providing webpages allowing a customer using UE <NUM> to sign-up or register for virtual wireless services with the service provider. For example, registration portal <NUM> can provide a webpage allowing a customer to enter their name, address, phone number, cellular service account number, email address, and payment information, among other information, to create an account for virtual wireless services. Registration portal <NUM> can also include a webpage or other user interface element allowing a customer to create a service set identifier (SSID) and password for a virtual router associated with the customer. Registration portal <NUM> can also provide other webpages or user interface elements providing the terms and conditions of using the virtual wireless services, help functionality, or other information that may be useful to the customer when registering for, or using, virtual wireless services. For example, registration portal <NUM> can provide webpages allowing a customer to update or change their contact information or change service.

Provisioner <NUM> may perform operations to manage the provision of virtual routers by virtual router service <NUM>. For example, provisioner <NUM> may receive a request to create a new virtual router based on a customer registering for virtual wireless services, or may perform operations to determine whether a customer or an SSID is registered for virtual wireless services. In some examples, provisioner <NUM> may interact with lookup services <NUM> to perform these operations. For example, lookup services <NUM> could include, or interface with, a database including customer information, account status information, and SSID information.

In some examples, base station <NUM> may interface with one or more Wi-Fi repeaters <NUM>. Wi-Fi repeaters <NUM> may act to repeat a Wi-Fi signal within a building, or outside of the building, to extend the range of base station <NUM> or to provide increased signal strength of the Wi-Fi signal being transmitted by wireless access point <NUM>.

<FIG> illustrates a block diagram <NUM> of an example base station <NUM> and virtual router service <NUM> consistent with disclosed examples. As described above, base station <NUM> may be configured to support communications in accordance with multiple air interface standards and can include cellular transceiver <NUM> for longer range wireless air interface standards (e.g., LTE, <NUM>) and wireless access point <NUM> for supporting shorter range wireless air interface standards such as Wi-Fi or WiMAX. In some examples, base station <NUM> can also be configured to perform handover communications between different air interface standards between other base stations.

Base station <NUM> can include a small cell as is known in the art. For example, base station <NUM> can include components that facilitate transmission of data in accordance with the wireless air interface standards it supports, including, but not limited to, antennas, filters, radios, base station control components, network interface components and power supplies. One skilled in the relevant art will appreciate that all such components that could be implemented in a small cell are not illustrated in <FIG> for purposes of brevity and not limitation. Base station <NUM> can be configured into include both cellular transceiver <NUM> and wireless access point <NUM> into a form factor desired for a small cell, such as a femtocell form factor, picocell form factor, or microcell form factor, as just some examples.

In other examples, base station <NUM> may be configured to support other technologies, or more or less radios may be present in base station. For example, base station <NUM> can include additional transceivers <NUM> in addition to cellular transceiver <NUM> and wireless access point <NUM> for receiving signals in accordance with an interface standard. Additional transceivers <NUM> can be configured to receive signals in a manner redundant to either the cellular transceiver <NUM> or wireless access point <NUM> or in a manner additional to the first and second radio components. Each of cellular transceiver <NUM>, wireless access point <NUM>, and additional transceivers <NUM> include transceiver components and/or modulators that perform functions of transmitting and receiving radio. In addition, in some implementations additional transceivers <NUM> can include wired communication components, such as an Ethernet port, for communicating with computing devices such as computer terminals of service technicians.

Base station <NUM> can also include a communication controller <NUM>. Communication controller <NUM> can include control software that provides operation and maintenance support for the communication technologies supported by base station <NUM>. Communication controller <NUM> can include the same or variations of similar controllers included in other infrastructure equipment, such as macro cells, for example. Communication controller <NUM> can also be connected to backhaul interface <NUM> in base station <NUM>. In various examples, base station <NUM> leverages a Small Form factor Pluggable (SFP) module as backhaul interface <NUM>. This allows flexibility to backhaul traffic with fiber, Pico Ethernet, or a large variety of wireless backhaul products. In some examples, backhaul interface <NUM> incorporates Integrated Access Backhaul (IAB). In IAB, wireless spectrum is used for the backhaul connection of base stations instead of fiber or other wired means of backhaul. IAB can be beneficial in areas where wired connections or fiber is impractical or scarce. In some implementations, additional transceivers <NUM> can include a transceiver dedicated to IAB.

According to some examples, backhaul interface <NUM> of base station <NUM> can be connected to and in communication with virtual router service <NUM>. Virtual router service <NUM> can include one or more processors <NUM> and memory <NUM> storing computer executable instructions that when executed by the one or more processors <NUM> perform operations and functions to provide virtual routers <NUM>.

Virtual routers <NUM> are software or virtual implementations replicating in software the functionality of hardware-based Layer <NUM> Internet Protocol routing that is typically performed by a dedicated hardware device. The functionality performed by virtual routers <NUM> can include providing virtual private network (VPN) functionality, traffic engineering, route reflectors, firewalls, and standard typical packet routing expected under Layer <NUM> Internet Protocol. Virtual router service <NUM> may execute multiple virtual routers <NUM> at a time and may in some cases coordinate resources or share resources between the virtual routers <NUM>.

In some implementations, virtual router service <NUM> may facilitate communication between one or more virtual routers <NUM> in situations where a customer has requested virtual wireless services at multiple base stations <NUM> using the SSID. In such implementations, virtual router service <NUM> may provision a first virtual router <NUM> using an SSID associated with a first base station <NUM> and a second virtual router <NUM> associated with a second base station <NUM> using the same SSID. Virtual router service <NUM> may then facilitate network communication between the two virtual routers sharing the SSID to form a virtual LAN spanning two different geographic locations (e.g., a first geographic location for the first base station and a second geographic location for the second base station).

<FIG> illustrates a block diagram of another example base station <NUM> consistent with disclosed examples. In the example base station <NUM> of <FIG>, memory <NUM> of base station <NUM> stores one or more virtual routers <NUM>. Virtual routers <NUM> executing at base station <NUM> operate and function similarly to virtual routers <NUM> executing at or within virtual router service <NUM>, with the primary difference being the location of execution of virtual routers <NUM>. For some implementations, it may be advantageous to have virtual routers <NUM> execute at the base station <NUM> as opposed to virtual router service <NUM>. For example, when fiber-optic backhaul is limited or bandwidth for backhaul is limited, deploying virtual router <NUM> at base station <NUM> may reduce traffic and therefore improve performance of the virtual network service.

<FIG> illustrates a data flow sequence diagram <NUM> showing an example sequence and flow of data between components of telecommunications network environment <NUM> consistent with disclosed examples. Data flow sequence diagram <NUM> relates to a use case or scenario where a customer registers for virtual wireless services and then uses the virtual wireless services at the base station through which the customer has registered for the service. In data flow sequence diagram <NUM>, the flow of data is represented in a sequence with numerals indicating an example sequence of data flow. However, in some implementations the sequence of data flow may be performed in a different order than shown by the numerals in <FIG>. Such differences in data flow may be based on specific implementations, and do not depart from the scope of the present disclosure as defined by the appended claims.

User equipment <NUM>, operated by a customer, may send HTML request <NUM> to registration portal <NUM> to gain access to a webpage allowing the customer to register for virtual wireless services. In response to HTML request <NUM>, registration portal <NUM> may transmit to user equipment <NUM> registration page <NUM>. Registration page <NUM> may include one or more user interface elements that allow a customer to register for virtual wireless services. The user interface elements can include, for example, text fields allowing a customer to enter their name address phone number and email address, drop-down boxes allowing customers to select a particular service level, or other user interface elements typical of service registration for wireless services or account creation.

Once a customer completes the information on registration page <NUM>, user equipment <NUM> may transmit back to registration portal <NUM> registration data <NUM> and payment data <NUM>. Registration data <NUM> can include a home address or business address of the customer, e.g., the address where the customer is most likely to use the virtual wireless services. The payment data <NUM> can include credit card information for example to allow for periodic and regular payment of the virtual wireless services.

Once registration portal <NUM> receives registration data <NUM> and payment data <NUM> it may verify both. If verification is successful, registration portal <NUM> may communicate a new virtual router request <NUM> to provisioner <NUM>. New virtual router request <NUM> can include the service address for the virtual wireless services. Provisioner <NUM> can then determine, based at least in part on the service address, the appropriate base station <NUM> to which a new virtual router will be provisioned to provide virtual wireless services.

Once provisioner <NUM> determines the appropriate base station <NUM> for provisioning a virtual router, provisioner <NUM> may send provision message <NUM> to the virtual router service <NUM> associated with the appropriate base station <NUM>. As noted above, in some implementations, the associated virtual router service <NUM> may be executed by processors associated with the base station <NUM> or the associated virtual router service <NUM> may executed by processors associated with a server or cloud-based computing system separate from the base station <NUM> and in communication with base station <NUM>.

Provision message <NUM> can include authentication credentials <NUM> and SSID information <NUM>. Authentication credentials <NUM> can include a username and password associated with the customer who has registered for virtual wireless services. In some implementations, authentication credentials <NUM> can also include additional codes, images, or other authentication information selected by the customer to increase security related to the virtual wireless services for which the customer has registered. SSID information <NUM> can include the name of the virtual wireless network supplied by the customer in registration data <NUM>. SSID information <NUM> may also include information related to the virtual router associated with the virtual wireless network for which the customer is registered. For example, SSID information <NUM> can include information about security levels associated with the virtual wireless network, whether the SSID is to be broadcast by base station <NUM>, and/or whether the SSID is to be encrypted.

Once virtual router service <NUM> receives provision message <NUM>, it may provision virtual router <NUM>. Once virtual router <NUM> has been instantiated and provisioned and enters a state whereby it can receive connection requests, virtual router service <NUM> may send an SSID available message <NUM> to base station <NUM> to inform base station <NUM> that virtual router <NUM> is available and ready.

Base station <NUM> may then send SSID broadcast message <NUM> via its wireless access point <NUM>. SSID broadcast message <NUM> can be a message broadcast to computing devices within the range of wireless access point <NUM> of base station <NUM> letting such computing devices know that a SSID with the customer's selected SSID is available for connection. In some implementations, a customer may request that its SSID not be broadcast, and in such implementations, base station <NUM> would not broadcast SSID broadcast message <NUM>. As such, user equipment <NUM> may request connection to the customer's SSID independent of base station <NUM> sending SSID broadcast message <NUM>. User equipment <NUM> may also begin the authentication and association process responsive to receiving SSID broadcast message <NUM>, or responsive to an input on user equipment <NUM> requesting connection to the SSID.

User equipment <NUM> may then begin the standard authentication and association process consistent with Wi-Fi or WiMAX standards. For example, under <NUM>, user equipment <NUM> may be in one of three connection states: (<NUM>) not authenticated or associated; (<NUM>) authenticated but not yet associated; and (<NUM>) authenticated and associated. When user equipment <NUM> is in the third state-authenticated and associated-user equipment <NUM> can begin to use virtual router <NUM> for communications as it would any traditional hardware router.

The authentication and association process begins with user equipment <NUM> sending authentication request <NUM>. Authentication request <NUM> can include a low-level <NUM>. 1X authentication frame and can include WEP encryption. In some examples, authentication request <NUM> can also include WPA2 or <NUM>. 1X authentication information to authenticate user equipment <NUM> and provide access to virtual router <NUM>. Note that in some examples, and while not shown in <FIG>, authentication request <NUM> may occur in two steps one via a authentication for WEP encryption or as part of the <NUM> standard authentication process, and a second step where user equipment <NUM> sends WPA2 or <NUM>. 1X authentication information. In such examples, the timing of part of authorization request for <NUM> (and subsequent authentication response <NUM>) can occur after the association step. For example, in some implementations, a first part of authentication request <NUM> related to WEP authentication can occur before association, and a second part of authentication request <NUM> related to authentication under WPA2 can occur after association.

Once base station <NUM> receives authentication request <NUM>, it can send authentication response <NUM> informing user equipment <NUM> that authentication was successful or unsuccessful. If authentication was successful, user equipment <NUM> may send association request <NUM> requesting association with the SSID of virtual router <NUM>. In some of implementations, association request <NUM> can include information regarding types of encryption and other capabilities related to the <NUM>. 1X standard. Once base station <NUM> receives association request <NUM>, base station <NUM> will verify that its wireless access point <NUM> is compatible with user equipment <NUM>, and may send association response <NUM> informing user equipment <NUM> that association was successful or unsuccessful.

<FIG> illustrates a data flow sequence diagram <NUM> showing an example sequence and flow of data between components of telecommunications network environment <NUM> of <FIG> consistent with disclosed examples. Data flow sequence diagram <NUM> relates to a use case or scenario where a customer accesses a portal landing page to request provisioning of a virtual router at a location different than where the customer typically uses virtual wireless services. For example, when a customer uses virtual wireless services while traveling, user equipment <NUM> would not be connected to the base station proximate to the customer's home or business. Instead, the customer's user equipment would connect to the base station in closest proximity to user equipment <NUM> that was capable of providing virtual wireless services. Such a base station may provide the ability for user equipment to connect to the base station and provide a portal landing page whereby the customer can request that a virtual router be provisioned at that base station.

In data flow sequence diagram <NUM>, the flow of data is represented in a sequence with numerals indicating a typical sequence of data flow. However, in some implementations the sequence of data flow may be performed in a different order than shown by the numerals in <FIG>. Such differences in data flow may be based on specific implementations, and do not depart from the scope of the present disclosure as defined by the appended claims. Moreover, much of the data flow
shown in data flow sequence diagram <NUM> is consistent with or duplicative of data flow shown in data flow sequence diagram <NUM>. Such data flow will be noted in the description that follows, but will not be repeated in detail for the sake of brevity.

In some examples, wireless access point <NUM> may make available a universal or generic SSID known to subscribers of virtual wireless services. For example, a service provider providing virtual wireless services may let it be known to its customers that base stations of the service provider where virtual wireless services are available may have wireless access points that broadcast an SSID of "Service Provider Portal Network. " A customer of the service provider can look for wireless networks named "Service Provider Portal Network" when away from their home base stations and connect to the "Service Provider Portal Network" wireless network to reach a portal landing page to request that a virtual router with the customer's specific SSID be provisioned to the base station.

In such examples, base station <NUM> may broadcast a portal SSID broadcast message <NUM> that includes the SSID of the wireless network providing the portal of the service provider. User equipment <NUM> may connect to the service provider portal using the SSID. Once connected, base station <NUM> may transmit portal landing page <NUM> to user equipment <NUM>. Portal landing page <NUM> can include a webpage that provides one or more user interface elements allowing a customer operating user equipment <NUM> to enter the customer's identification information (e.g., name, email address, user ID, password, virtual network SSID) and send the request (e.g., a button or hyperlink). User equipment <NUM> may send user provision request <NUM> to base station <NUM>. User provision request <NUM> can include the information entered in the portal landing page <NUM> and can contain information, such as the customer's SSID or that may be necessary for service provider computer system <NUM> to provision a virtual router having the customer's SSID at base station <NUM>.

After base station <NUM> receives user provision request <NUM>, it may create provision request <NUM> and send it to virtual router service <NUM>. Provision request <NUM> can include customer information such as username and password or other identifiable information related to the customer and the customer's virtual wireless services account. Provision request <NUM> can also include the customer's SSID and an identifier associated with base station <NUM>. Provision request <NUM> serves as a request to provision virtual router <NUM> having the customer's SSID at base station <NUM>. As noted above, virtual router service <NUM> may execute on one or more processors of base station <NUM>, and in such implementations, provision request <NUM> may be a request internal to base station <NUM>.

Upon receiving provision request <NUM>, virtual router service <NUM> may issue a service provision request <NUM> to provisioner <NUM> of service provider computer system <NUM>. The purpose of service provision request <NUM> is to check with provisioner <NUM> and determine whether the SSID of user SSID message <NUM> is one for which a customer has registered for virtual wireless services and that the customer is current with payment or other obligations for receiving virtual wireless services from the service provider. Provisioner <NUM> may send lookup request <NUM> to lookup services <NUM> to determine whether virtual wireless services are available for the SSID provided in service provision request <NUM>. Lookup services <NUM> can then send lookup response <NUM> to provisioner <NUM> informing provisioner <NUM> as to the status of virtual wireless services for that SSID.

When lookup response <NUM> indicates that virtual wireless services are available for the SSID, provisioner <NUM> sends provision message <NUM> to virtual router service <NUM>. Once virtual router service receives provision message <NUM> it may instantiate and provision virtual router <NUM> with the SSID initially provided by user equipment <NUM> in user SSID message <NUM>. From that point, user equipment <NUM> may authenticate and associate with the wireless access point <NUM> as described above with respect to <FIG>.

<FIG> illustrates a data flow sequence diagram <NUM> showing an example sequence and flow of data between components of the telecommunications network environment <NUM> of <FIG> consistent with disclosed examples. Data flow sequence diagram <NUM> relates to a use case or scenario where a customer attempts to connect to a virtual wireless network provided by a virtual router at a point in time when the customer has already registered for, or used, virtual wireless network services in the past. The example provided in <FIG> is one where base station <NUM> can receive requests for specific SSIDs and provision virtual routers accordingly.

In data flow sequence diagram <NUM>, the flow of data is represented in a sequence with numerals indicating a typical sequence of data flow. However, in some implementations the sequence of data flow may be performed in a different order than shown by the numerals in <FIG>. Such differences in data flow may be based on specific implementations, and do not depart from the scope of the present disclosure as defined by the appended claims. Moreover, much of the data flow shown in data flow sequence diagram <NUM> is consistent with and duplicative of data flow shown in data flow sequence diagram <NUM> and data flow sequence diagram <NUM>. Such data flow will be noted in the description that follows but will not be repeated detail for the sick of brevity.

When attempting connection to a virtual router, user equipment <NUM> may send user SSID message <NUM> to wireless access point <NUM> of base station <NUM>. User SSID message <NUM> can include an SSID for a virtual router to which user equipment <NUM> wishes to establish a connection. User equipment <NUM> may send user SSID message <NUM> to base station <NUM> responsive to SSID broadcast message <NUM> (described above with respect to <FIG>). In some implementations, user equipment <NUM> may send user SSID message <NUM> when it wishes to connect to a virtual router <NUM> identified by the SSID. For example, user equipment <NUM> may send user SSID message <NUM> after it is been powered up, after it has lost a network connection, or responsive to a user performing a set of user input actions requesting connection to the SSID.

Once base station <NUM> receives user SSID message <NUM>, it may perform an internal lookup request in the form of base station SSID lookup request <NUM> to determine whether a virtual router <NUM> matching the SSID contained within user SSID message <NUM> has already been provisioned at base station <NUM>. If base station <NUM> already has access to a provisioned virtual router <NUM> matching the SSID of user SSID message <NUM>, user equipment <NUM> and base station <NUM> may perform the authentication and association process described above with respect to <FIG>. If, however, base station <NUM> does not have access to a provisioned virtual router <NUM> matching the SSID of user SSID message <NUM>, base station <NUM> may send provision request <NUM> to virtual router service <NUM> requesting that virtual router service <NUM> provision a virtual router having an SSID matching the SSID of user SSID message <NUM>. As noted above, virtual router service <NUM> may execute on a processor of base station <NUM>, and in such implementations, provision request <NUM> may be a request internal to base station <NUM>.

Once virtual router service <NUM> receives provision request <NUM>, the sequence of data flow may be similar to that described above with respect to <FIG>. For example, virtual router service <NUM> may send a service provision request <NUM> to provisioner <NUM> of service provider computer system <NUM>, provisioner <NUM> may use lookup services <NUM> to determine whether virtual wireless services are available for the SSID of user SSID message <NUM>, and provisioner <NUM> may then send provision message <NUM> back to virtual router service <NUM>. Virtual router service <NUM> may then instantiate and provision virtual router <NUM> consistent with disclosed examples, and user equipment <NUM> and base station <NUM> may perform the authentication and association process.

<FIG> illustrates a flowchart for an example virtual router provision process <NUM> for provisioning a virtual router and provide virtual wireless services consistent with disclosed examples. Virtual router provision process <NUM> can be performed by various components of network environment <NUM>. For example, aspects of virtual router provision process <NUM> can be performed by base station <NUM>, virtual router service <NUM>, and/or service provider computer system <NUM>. Although the following discussion may describe aspects of virtual router provision process <NUM> as being performed by certain components, other components described in the present disclosure may perform these aspects without departing from the scope of the present disclosure as defined by the appended claims.

At block <NUM>, base station <NUM> may wait for incoming connection requests associated with virtual wireless services. At block <NUM>, base station <NUM> may receive a request from a client device, such as user equipment <NUM>, to connect to a virtual router providing virtual wireless services. The request base station receives at block <NUM> can include an SSID. The SSID may be one associated with virtual wireless services for which a customer operating the client device has registered.

Once the request is received by the base station <NUM>, base station <NUM> will determine if a virtual router matching the SSID of the request has already been provisioned and is available through base station <NUM>. If a virtual router matching the SSID has already been provisioned (block <NUM>:YES), then processing moves to block <NUM>, described below. If, however, there is no virtual router matching the SSID of the request provisioned and available through base station <NUM> (block <NUM>:NO), processing moves to block <NUM>.

At block <NUM>, base station <NUM> determines if the SSID of the request received in block <NUM> is associated with a customer that has registered for virtual wireless services and is up to date with payment or other requirements for receiving the services. Base station <NUM> may perform this operation by contacting service provider computer system <NUM>. As noted above, in some examples, base station <NUM> may not handle the operations and functionality for provisioning virtual routers. It may instead make a request for provisioning to virtual router service <NUM>. In such examples, virtual router service <NUM> may make a request to service provider computer system <NUM> at block <NUM> to determine whether the SSID is associated with an active registration for virtual Wi-Fi network services.

If the received SSID is not associated with an active registration for virtual wireless services (block <NUM>:NO), base station <NUM> refuses the connection request at block <NUM>. In some examples, base station <NUM> may provide a registration portal webpage at block <NUM>. The portal registration webpage can be similar to registration page <NUM> described above with respect to <FIG>. For example, it may provide user interface elements allowing a customer to provide the information needed to register for virtual wireless services. If, however, the received SSID is associated with an active registration for virtual wireless services (block <NUM>: YES), processing moves to block <NUM>.

At block <NUM>, a virtual router <NUM> is provisioned at base station <NUM> and made accessible through the wireless access point <NUM> of the base station <NUM>. Provisioning of a virtual router can be accomplished through a combination of the service provider computer system <NUM>, the virtual router service <NUM>, and/or the base station <NUM> consistent with disclosed examples. Once the virtual router <NUM> is provisioned, processing then moves to block <NUM>.

At block <NUM> to block <NUM>, process <NUM> performs authentication and association as described above with respect to authentication request <NUM>, authentication response <NUM>, association request <NUM>, and association response <NUM> described above with respect to <FIG>.

In some examples, the operations of process <NUM> may be performed out of the order presented, with additional elements, and/or without some elements. Some of the operations of process <NUM> may further take place substantially concurrently and, therefore, may conclude in an order different from the order of operations shown above.

<FIG> illustrates a flowchart for an example multiple virtual router provision process <NUM> for provisioning a virtual wireless network via virtual router provisioned at multiple base stations consistent with disclosed examples. Multiple virtual router provision process <NUM> can be performed by various components of network environment <NUM>. For example, aspects of multiple virtual router provision process <NUM> can be performed by multiple base stations <NUM>, virtual router service <NUM>, and/or service provider computer system <NUM>. Although the following discussion may describe aspects of virtual router provision process <NUM> as being performed by certain components, other components described in the present disclosure may perform these aspects without departing from the scope of the present disclosure as defined by the appended claims.

At block <NUM>, a first base station may receive a request from user equipment to connect to virtual wireless services. The request can include a SSID that may be associated with an account of a customer that has registered for virtual wireless services from a service provider that controls or operates the first base station.

At block <NUM>, the first base station may determine whether the SSID included in the request received at block <NUM> is registered for virtual wireless services. For example, the first base station may follow a process similar to that described above with respect to <FIG> blocks <NUM> through <NUM> when determining whether the SSID is one registered for virtual wireless services. Once the first base station makes this determination, it will cause provisioning of a first virtual router connectable through its wireless access point. Provisioning of the first virtual router may follow a process similar to that described above with respect to <FIG>, in various examples.

At block <NUM>, after the first base station provisions the first virtual router, the first base station may associate a first client device with the virtual router. The first client device may be the user equipment that sent the request received at block <NUM>, or it may be some other piece of user equipment wishing to use virtual wireless services. Although the above description describes connection of one piece of user equipment, or a first client device, to a first base station, the first virtual router provisioned in association with the first base station can accept connections from multiple pieces of user equipment.

At block <NUM>, a second base station within the telecommunications network of the service provider may receive a second request for virtual wireless services. The request may include the same SSID received by the first base station at block <NUM> above. The second base station may be located in a different location within the telecommunications network, and the request the second base station receives at block <NUM> may have originated from a different piece of user equipment than what sent the request at block <NUM>.

At block <NUM>, the second base station may determine whether the SSID included in the second request received at block <NUM> is registered for virtual wireless services. This determination process is similar to the process followed by the first base station at block <NUM>. For example, the second base station may follow a process similar to that described above with respect to <FIG>, blocks <NUM> through <NUM> when determining whether the SSID is one registered for virtual wireless services. Once the second base station makes this determination, it will cause provisioning of a second virtual router connectable through its wireless access point at <NUM>. Again, the process followed by the second base station at block <NUM> will be similar to the process followed by the first base station at block <NUM>, e.g., provisioning of the second virtual router may follow a process similar to that described above with respect to <FIG>, in various examples.

In some examples, the first virtual router and the second virtual router execute and operate within the same instance of virtual router service <NUM>. While not stated above, in alternative examples, the first virtual router and the second virtual router may be the same instance of a virtual router whereby both the first and second base stations offer connections to the virtual router via their respective connections to virtual router service <NUM>.

At block <NUM>, after the second base station provisions the second virtual router, the second base station may associate a second client device with the second virtual router. The second client device may be the user equipment that sent the request received at block <NUM>, or it may be some other piece of user equipment wishing to use virtual wireless services. Although the above description describes the connection of one piece of user equipment, or a second client device, to a second base station, the second virtual router provisioned in association with the first base station can accept connections from multiple pieces of user equipment.

The first virtual router and the second virtual router described above with respect to process <NUM> use the same SSID, refer to the same customer account, and can create a virtual local area network allowing multiple pieces of user equipment that are geographically separated and connected to separate base stations to communicate as if they were on the same LAN. This may allow, for example, a customer connected to a base station while traveling on business to print a document at the customer's home, provided that both the customer's laptop for business and the printer are connected to virtual wireless services using the same SSID.

Many of the examples described above describe computing devices, computing systems or structures having aspects of computing systems. For example, disclosed examples describe base station <NUM> having one or more processors <NUM> and memory <NUM>, virtual router service <NUM> which could be a server having or more processors <NUM> and memory <NUM> or a collection cloud computing components each having a one or more processors <NUM> and memory <NUM>, and service provider computer system <NUM> also having one or more processors <NUM> and memory <NUM>. In addition, while not described in detail, user equipment <NUM> can also include one or more processors and memory depending on the example of user equipment <NUM>.

As used in the present disclosure, processors <NUM>, <NUM>, <NUM> can include one or more of a central processing unit (CPU), a graphics processing unit (GPU), both CPU and GPU, a microprocessor, a digital signal processor or other processing units or components known in the art. Alternatively, or in addition, the functionally described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that may be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip system(s) (SOCs), complex programmable logic devices (CPLDs), etc. Additionally, each of the processors <NUM>, <NUM>, <NUM> may possess its own local memory, which also may store program modules, program data, and/or one or more operating system(s). One or more processor(s) <NUM>, <NUM>, <NUM> may include one or more cores, depending on the example.

Also used in the present disclosure, memory <NUM>, <NUM>, <NUM> can include computer-readable media that can be volatile and/or nonvolatile memory. It can also include removable and/or non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules, or other data. Memory <NUM>, <NUM>, <NUM> can include, but is not limited to, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, RAID storage system(s), or any other medium which can be used to store the desired information and which can be accessed by a computing device.

Memory <NUM>, <NUM>, <NUM> may be implemented as computer-readable storage media (CRSM), which may be any available physical media accessible by processors <NUM>, <NUM>, <NUM> to execute instructions stored on the memory <NUM>, <NUM>, <NUM>. In one implementation, CRSM may include RAM and Flash memory. In other implementations, CRSM may include, but is not limited to, ROM, EEPROM, or any other tangible medium which can be used to store the desired information, which can be accessed by the processors <NUM>, <NUM>, <NUM>. Memory <NUM>, <NUM>, <NUM> may have an operating system (OS) and/or a variety of suitable applications stored thereon. The OS, when executed by the processors <NUM>, <NUM>, <NUM> may enable management of hardware and/or software resources.

Several functional blocks having instruction, data stores, and so forth may be stored within the memory <NUM>, <NUM>, <NUM> and configured to execute on processors <NUM>, <NUM>, <NUM>. For example, memory <NUM>, <NUM>, <NUM> may have stored thereon a registration portal <NUM>, a provisioner <NUM>, lookup services <NUM>, and SSID manager <NUM>, the communication controller <NUM>, and one or more virtual routers <NUM>, consistent with the examples of the present disclosure. Each of these components may include instructions that when executed by processors <NUM>, <NUM>, <NUM> may enable various functions pertaining to the operations of the disclosed examples.

The disclosure is described above with reference to block and flow diagrams of system(s), methods, apparatuses, and/or computer program products according to examples of the disclosure. 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 flow diagrams, respectively, can 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 examples of the disclosure.

Computer-executable program instructions may be loaded onto a general purpose computer, a special-purpose computer, 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 for implementing one or more functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction that implement one or more functions specified in the flow diagram block or blocks. As an example, embodiments of the disclosure may provide for a computer program product, comprising a computer usable medium having a computer readable program code or program instructions embodied 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.

It will be appreciated that each of the memories and data storage devices described herein can store data and information for subsequent retrieval. The memories and datastores can be in communication with each other and/or other datastores, such as a centralized datastore, or other types of data storage devices. When needed, data or information stored in a memory or datastore may be transmitted to a centralized datastore capable of receiving data, information, or data records from more than one datastore or other data storage devices. In other examples, the datastores shown can be integrated or distributed into any number of datastores or other data storage devices.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as illustrative forms of implementing the claims.

Many modifications and other examples 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 examples disclosed and that modifications and other examples are intended to be included within, but is limited only by 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.

Claim 1:
A method for provisioning a virtual router providing virtual wireless services, at a base station (<NUM>) comprising a small cell transceiver (<NUM>) associated with a cellular network and
a wireless access point (<NUM>), the wireless access point being configured to exchange short-range communications, the method comprising:
receiving (<NUM>; <NUM>), by the base station (<NUM>) via the wireless access point (<NUM>) of the base station (<NUM>), a first request to connect to a virtual router from a first client device (<NUM>), the first request including a service set identifier, SSID;
determining (<NUM>; <NUM>), by the base station (<NUM>), that the SSID is registered by a user of the client device for virtual wireless services;
determining that authentication credentials utilized to provision the virtual wireless services are associated with the SSID;
receiving, by a virtual router service element (<NUM>) associated with the base station (<NUM>), via the cellular network, a provision message including the SSID and the authentication credentials (<NUM>) based at least in part on the SSID being registered, and on the authentication credentials being associated with the SSID;
provisioning (<NUM>; <NUM>), by the virtual router service element (<NUM>), based on the received provision message, a virtual router (<NUM>) to be accessible through the wireless access point, the virtual router being identifiable using the SSID;
receiving (<NUM>; <NUM>), by the base station (<NUM>), from the first client device, a first authentication request to connect to the virtual router (<NUM>), the first authentication request including the SSID;
authenticating (<NUM>; <NUM>), by the base station (<NUM>), the first client device based at least in part on whether the first authentication request includes information matching the authentication credentials;
receiving (<NUM>; <NUM>), by the base station (<NUM>), a first association request from the first client device, the first association request including the SSID; and
associating (<NUM>; <NUM>; <NUM>), by the base station (<NUM>), the first client device with the virtual router (<NUM>).