Wireless Backbone and Structured Wireless
Through automatic frequency coordination and position awareness technology, unlicensed devices on the 6GHz band are dynamically managed, solving spectrum congestion and interference issues, ensuring band availability and safe operation of devices.
Patent Information
- Application Number
- CN202080057580.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-09-06
- Filing Date
- 2020-06-29
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2040-06-29
AI Technical Summary
Unauthorized use of the 6GHz band leads to spectrum congestion, and the prior art is difficult to effectively manage and coordinate the operation of unlicensed equipment, resulting in interference to other user services.
Through automatic frequency coordination (AFC) systems and position perception technology, combined with GPS, cellular triangulation and Wi-Fi signal analysis, the position of the device is determined and the frequency and power is dynamically adjusted to ensure that the device operates without interfering with other users. .
It effectively solves the spectrum congestion problem, ensures the availability of the 6GHz band and reduces interference from other user services, and achieves safe and reliable operation of the equipment.
Smart Images

Figure CN114271023B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application is a non-provisional application, which claims the benefit of U.S. Provisional Application Serial No. 62 / 868,583, filed on June 28, 2019, entitled “6 GHz Wireless”, which is incorporated herein by reference in its entirety. In addition, this application is a non-provisional application, which claims the benefit of U.S. Provisional Application Serial No. 62 / 896,608, filed on September 6, 2019, entitled “6 GHz Wireless”, which is incorporated herein by reference in its entirety. Technical Field
[0003] The present disclosure relates to wireless backbone and structured wireless. Background Art
[0004] As the number of wireless devices and services available to subscribers grows, the use of unlicensed spectrum continues to grow. The rise in bandwidth usage, coupled with the lack of new mid-band unlicensed spectrum allocations, has created severe congestion issues in the available mid-band unlicensed spectrum.
[0005] The 6 GHz band is located in the main area of the mid-band spectrum. Various regulations have been implemented to protect established microwave systems from interference. Regulations also enable the free deployment and operation of microwave systems.
[0006] Regulations have been approved to allow unlicensed devices to use the 6 GHz band. The regulations include restrictions that will require unlicensed devices to operate only in locations and frequencies that will not cause interference to other users of the 6 GHz band. The FCC has considered different treatments for four sub-bands of the 6 GHz band, including:
[0007] U-NII 5: 5925-6425MHz
[0008] U-NII 6: 6425-6525MHz
[0009] U-NII 7: 6525-6825MHz
[0010] U-NII 8: 6875-7125MHz
[0011] Different regulations have been proposed for each sub-band. Exemplary usage restrictions that may be imposed on a sub-band include:
[0012] For U-NII 5 and U-NII 7 sub-bands:
[0013] i. Unlicensed devices may only be allowed to transmit under the control of the Automatic Frequency Coordination (AFC) system.
[0014] ii. The AFC system can identify frequencies where unlicensed devices can operate without causing harmful interference to fixed point-to-point microwave receivers.
[0015] iii. Unlicensed devices may operate at standard power (eg, 4W, 1W, etc.).
[0016] For all 6GHz sub-bands:
[0017] i. Unlicensed devices may be limited to indoor use and may need to operate at lower power (eg, 1 W, 250 mW, 24 mW, etc.) without coordination of the AFC system.
[0018] ii. Frequencies in the U-NII 6 and U-NII 8 sub-bands are used for mobile services, such as broadcast auxiliary services and cable television relay services, and fixed satellite services. The nomadic nature of mobile services makes the use of AFC systems impractical.
[0019] iii. The combination of lower power and indoor operation can protect other registered services already operating on these frequencies from harmful interference. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Figure 1 An example network operable to facilitate device management based on determining proximity to one or more exclusion zones is shown.
[0021] Figure 2 is a flow chart illustrating an example process for directing a STA to a particular channel based on potential operating performance at a 6 GHz channel.
[0022] Figure 3 is a flow chart illustrating an example process of scanning for satisfactory 6 GHz channels.
[0023] Figure 4 is a flow chart illustrating an example process of establishing timing allocations between an AP and a STA.
[0024] Figure 5 is a flow chart illustrating an example process of establishing a timing allocation between an AP and a STA, wherein the STA determines whether the AP provides timing allocations from a certain source at a certain service level.
[0025] Figure 6 is a block diagram illustrating an example system for transmitting and receiving signals over a 6 GHz backbone.
[0026] Figure 7is a block diagram illustrating an example network architecture that facilitates use of the 6 GHz wireless frequency band.
[0027] Figure 8 An example use of millimeter wave (mmWave) to 6 GHz bridging is shown.
[0028] Fig. 9 is a block diagram illustrating an example home network using 6 GHz and 6 GHz adapters to bring broadband to a premises.
[0029] Fig.10 is a block diagram illustrating an example home network supported by a 6 GHz backbone.
[0030] Fig.11 An example schematic diagram of a mmWave to 6 GHz adapter is shown.
[0031] Fig.12 Wider connections for higher bandwidth connections and narrower connections for lower bandwidth connections are shown.
[0032] Fig.13 is a block diagram of a hardware configuration operable to facilitate and utilize 6 GHz backbone and / or 6 GHz wireless communications.
[0033] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION
[0034] The methods, systems, and computer-readable media described herein may be operable to provide a 6 GHz backhaul within a venue. The adapter may facilitate conversion of communications between one or more local area networks and one or more wide area networks. The 6 GHz backhaul may be used by one or more access points to support a variety of wireless services with unique or different operating and bandwidth requirements. The 6 GHz backhaul may be used to transfer communications between the adapter and a network interface device and / or between the adapter and one or more access points.
[0035] Automatic Frequency Coordination (AFC)
[0036] Figure 1 An example network 100 is shown that is operable to facilitate device management based on determining proximity to one or more exclusion zones.
[0037] In an embodiment, the operation of a device (e.g., an access device such as an access point (AP) 105 and / or one or more stations 110 associated with the AP 105) may depend on communication with the AFC system 115. The AP 105 as described herein may include an RLAN (radio local area network) device, a WLAN (wireless local area network), and any other device configured to facilitate wireless communication with other devices. The AFC system 115 may include a database containing pre-calculated exclusion zone data for one or more microwave paths. It should be understood that spectrum availability can be calculated upon request. The exclusion zone data may be updated at the database periodically (e.g., hourly, daily, etc.) or in response to the addition or deletion of data associated with the microwave path. Communication between the device and the AFC system 115 may be performed via a wired or wireless link that is not in the 6 GHz band. The AFC system 115 and its database may be connected to a packet-based wide area network (e.g., a wide area network (WAN) 120), including but not limited to the Internet. Each of the one or more devices (e.g., the AP 105) may be registered in the database. Initial registration and querying may be performed outside of the 6 GHz band. In an embodiment, each device (e.g., AP 105) may also register devices associated with the device (e.g., STA (station) 110, client, etc.). Each device may query the database with location information (e.g., location information associated with the current location of the device), identification of the device type, identification information (e.g., a unique identifier), and / or other information associated with the device. Based on the queries received from each respective one of the devices, the database may determine the proximity of the respective device to one or more exclusion zones.
[0038] The device (e.g., AP 105) can automatically determine the geographic location where the device is currently located and / or the location where the device has been installed. For example, GPS, cellular triangulation, or other systems can be used to determine the location of the device. The device can alternatively or additionally use the location information to authenticate through a local user interface or remotely through a deployment or status interface.
[0039] In an embodiment, the device may include an internal GPS by which the device may determine its current location. The internal GPS may be utilized by devices installed in outdoor locations.
[0040] In an embodiment, the device may communicate with a separate GPS receiver to determine the current location of the device. For example, the GPS receiver may be mounted at an outdoor location, while the device may be mounted at an indoor location. Given the location of the GPS receiver, the device may determine its own location using one or more Wi-Fi location determination features to map back from the location of the GPS receiver. For example, the device may measure the signal strength and / or directional components associated with one or more wireless signals received at the device, and the measurements may be used to identify the location of the device relative to the GPS receiver.
[0041] STA (station) 110 (e.g., wireless extender, etc.) can determine its location by wirelessly communicating with a device (e.g., AP 105). STA 110 can determine its location relative to the device. For example, the wireless extender can use one or more Wi-Fi location determination features (e.g., signal strength, directional components associated with one or more received signals, etc.) to map its location relative to the device.
[0042] It should be understood that cellular triangulation may be used instead of GPS. Other satellite-based position determination services may also be used instead of GPS, such as Galileo.
[0043] A device (e.g., AP 105) may be manually configured with device location information. In an embodiment, once the device has been installed, a technician (e.g., a licensed technician or installer) may configure the device with the location information. For example, the device may be configured with a trusted certificate, blockchain, or other information for authenticating the manually provided location of the device.
[0044] The location information may be provided to a device (eg, AP 105) by a provisioning server or configuration server. In an embodiment, the provisioning server may have information about the address of the customer deploying the device and may provide the address information to the device.
[0045] In an embodiment, a device (e.g., AP 105) or an upstream device (e.g., a controller of AFC system 115) may be configured to detect movement of the device. The device or upstream device may be configured to determine the current location of the device in response to a triggering event. The triggering event may include, but is not limited to, the following events: a restart of the device, detection of the loss or addition of a STA (from which the device receives communications), and others. In an embodiment, a co-located device (e.g., an AP (access point)) may determine that another co-located device has moved based on a change in position indicated by one or more Wi-Fi location determination features.
[0046] Outdoor GPS-APs can use interlocks to prevent them from moving and continue to operate. This interlock allows the AP to reinitialize its GPS position and contact the AFC when the AP thinks it has moved. If the device has used the location provided by the technician, a physical interlock can be used. For example, if the AP is powered off and has been powered on again, you can try to determine whether the AP has moved by querying other location-specific attributes or at least attributes that indicate the location. For example, if the AP is integrated with a cable modem, the cable modem can notify the AP whether it has moved to a new HFC (hybrid fiber coaxial) feed (new power level, new CMTS (cable modem terminal system) communication information, different cable groups, etc.). Other location indications can be: DHCP server changes, DHCP gateway changes, new clients / old clients lost, new overlapping Wi-Fi basic service sets (OBSS). In an embodiment, a 6GHz AP can be co-located with a 5GHz AP and / or a 2.4GHz AP. If these co-located APs report the presence of new neighboring APs, one or more new clients, or other new wireless devices, the 6GHz AP can refuse to transmit until its location is updated by a trusted source.
[0047] In an embodiment, the AFC system 115 may utilize location information from multiple sources to verify or otherwise improve the confidence level of the determined location of a device (e.g., AP 105). For example, the AFC system 115 may associate the location information of the device with GPS data with a physical address associated with the customer (e.g., an address recovered from billing data or subscriber information stored at a subscriber information server 125, such as a service provider server or other server storing subscriber or account information).
[0048] Position determination by RF scanning in the 6 GHz band
[0049] The device that needs to perform location determination, typically AP 105, initializes and starts scanning available frequency bands. The AP can access 2.4GHz, 5GHz, and 6GHz radios. The AP can scan Wi-Fi signals in the 2.4, 5, and 6GHz bands. The SSID that can be obtained from the received Wi-Fi transmission can help estimate the location of the AP. The signals of other 6GHz APs can be detected by 6GHz scanning or from analysis of information about the 6GHz SSID included in the 5GHz or 2.4GHz signals. For example, one or more signals received by AP105 through a 2.4GHz or 5GHz radio may indicate the presence of a 6GHz SSID or a 6GHz SSID provided by one or more other APs. The goal of the 802.11 standard for the 6GHz band is to limit the number of beacon transmissions and similar activities to reduce the percentage of flight time delivered to background or maintenance activities. APs with 6GHz capabilities can announce this capability in their 2.4 and / or 5GHz transmissions.
[0050] The AP 105 may also scan the 6 GHz band to determine if there are non-Wi-Fi signals. Signals of fixed wireless or other non-Wi-Fi communications may be detected and their directions may be recorded. With energy detection, the AP does not have to be able to demodulate or decode fixed wireless or other non-Wi-Fi communication signals to detect their presence. In an embodiment, further processing beyond energy detection is performed on the received signal spectrum. Characteristics of at least well-known signals such as fixed microwave signals may be applied to the received signal spectrum and energy signatures of possible interest that are marked for further processing. For example, fixed microwave signals are typically 30 MHz wide and appear in pairs. These signals also need to be registered with the FCC. In an embodiment, the signal spectrum detected by the AP may be processed locally or sent to the controller 130 or a cloud server for further processing.
[0051] If the AP 105 processes the spectrum locally, it can detect a certain combination of fixed microwave signals. With this information, the AP can query a database containing 6GHz registered signal sites. Fixed wireless allocated frequencies can be recorded in a database that also includes location information. When combined with Wi-Fi signal information, the location of the AP can be determined with greater certainty or less uncertainty. Even if GPS or similar location determination equipment is not available, the AP can make a location estimate based on these information sources. If the AP sends the collected signal spectrum to the controller 130 or cloud server, these entities can similarly consult a database of known 6GHz entities for location estimation. These entities can also query a database of known 2.4GHz and 5GHz signal sources. The estimate can be returned to the AP for use when it communicates with the AFC system. Alternatively, the controller 130 or cloud server can forward the location estimate with information identifying the AP to the AFC. If the AP identifies a Wi-Fi signal within the 6GHz scan, this information can also be used to help determine the location.
[0052] As previously described, additional sources of location information may include client devices, such as smartphones associated with the AP's 2.4GHz or 5GHz radio, as well as GPS receivers, etc. Many smartphones have built-in GPS receivers and can provide an estimate of their current location by combining their GPS signals (if any) with other signals in the Wi-Fi band and other indications known in the art. The client device may have an application (app) installed that facilitates communication with the AP and indicates to the AP whether the client device shares its current location estimate. In an embodiment, the user of the client device may be presented with the option of sharing or not sharing its location with the AP associated with it. The AP can request a location estimate from the client device by communicating with the application. Alternatively, the controller can communicate with the application of the client device on behalf of the AP to obtain the client's location estimate.
[0053] The AP can use an algorithm itself to predict its most likely location based on the various inputs it receives, or it can contact another device or server, provide information and receive an estimated location with an estimated position error. The AP or location server can use standard techniques of positioning and triangulation to predict the location of the AP from the collected data.
[0054] The AFC database (at the AFC system 115) may utilize a buffer to compensate for potential inaccuracies in the location information transmitted regarding the query. The AFC database may identify one or more frequencies that may be used for the corresponding device (e.g., the AP 105), wherein the available frequencies are based on determining whether the corresponding device is located within the exclusion zone. In addition, the database may identify one or more operating requirements, such as a transmit power level, based on determining whether the corresponding device is located within the exclusion zone. The database may send a list of available frequencies to the corresponding device, and the corresponding device may begin operating with the available frequencies identified from the list according to any operating requirements.
[0055] In an embodiment, a device registered in the AFC database may send a heartbeat message to the database to ensure that the exclusion zone data is up to date and to confirm that the device is active. The device may be deregistered from the AFC database when it is determined that the device has moved beyond a threshold distance (e.g., 50m, 100m, etc.), when a heartbeat message is not received for longer than a certain duration (e.g., 24 hours, etc.), or in response to another triggering event.
[0056] If an AP provides high reliability service, the AP may register with more than one AFC and keep a record of at least two different AFC responses to provide channel availability and power levels. If the responses are different, the AP may choose to use the response of one AFC instead of the response of another AFC, or it may choose to comply with the merger of the two responses.
[0057] Monitoring sites already in place for CBRS can be enhanced to also collect signatures of radio traffic in various bands outside the CBRS band. It is true that radios are very specific to a specific frequency range, but this limitation is less accurate as software defined radios (SDRs) with flexible front ends improve in performance and cost effectiveness. Some of the problems associated with SDRs are mitigated if the SDR is used only for reception. A common problem is that filtering for out-of-band emissions from an SDR transmitter is difficult or expensive. This problem is minimized if the SDR is operated only as a receiver.
[0058] 6 GHz devices may also include 2.4 GHz and / or 5 GHz radios. This allows, for example, an AP to provide minimal beacon transmissions in only its 6 GHz assigned channel, since its 5 GHz beacon may include information about any 6 GHz interfaces. For example, an AP may advertise a 6 GHz SSID via a beacon provided by the AP's 2.4 or 5 GHz radios.
[0059] If a 6 GHz device such as an AP or mesh station does not include an LTE radio, one or more of its clients or associated devices may be, for example, a cell phone. In this case, the AP may query its clients about networks visible via the radio, for example, even if the AP does not request an actual location determination from these devices.
[0060] The AFC database may alternatively receive information received by a device seeking to register, such as 5 GHz and 6 GHz signals. The received information about the 5 GHz and 6 GHz signals may include the SSID from the Wi-Fi AP, and the frequencies at which energy above a threshold was detected in the 5 GHz and 6 GHz bands. The received information about the 5 GHz and 6 GHz signals may include the signal strength and angular direction associated with the received signal.
[0061] The database can associate the received energy signature with known 6 GHz fixed microwave deployments to determine the likely location of the device. Known 6 GHz microwave deployments may register their frequency usage and location. Detection of a certain pattern of 6 GHz signals can be matched with known deployments to allow the AFC database to estimate where the device must be to receive that pattern of 6 GHz signals. For example, it is known that fixed microwave links in the 6 GHz band are 30 MHz wide and exist in pairs. The database will not only consider the detected 6 GHz signals when allocating frequencies to a requesting device that reports receiving at least one 30 MHz signal in its 6 GHz scan. Detection of a 30 MHz wide signal necessarily means that if the device begins transmitting on the frequency allocated to the pairing signal, the matching pairing signal may also be affected.
[0062] Similarly, the database may correlate received SSIDs with known SSID locations to determine the likely location of the device. The database may combine various estimates to form an estimate with greater confidence. If estimates formed based on different information sources do not indicate the same location within a certain amount of uncertainty, the database may select which estimates to rely on for registration decisions, or the database may reject the registration request entirely. Relative signal strength and direction may be combined with the location estimate to determine whether the information provided is credible.
[0063] The database can also use relative signal strength and direction to determine the transmit power level allowed for a device and the frequency blocks allowed. For example, a device reporting very low signal levels for received 5GHz and 6GHz signals may be inside a building such that other signals can only reach the device weakly. In this case, the database can allow the device to safely use a higher transmit power because its transmissions will also be severely attenuated before reaching any 6GHz fixed microwave operations.
[0064] Location Awareness
[0065] The device or an associated upstream device may be configured to determine that the device has moved by comparing the current location of the device with the baseline location of the device (e.g., location information automatically determined or manually input during installation or initial setup of the device). Additional description of comparing the current location of the device with the baseline location of the device to determine that the device has moved can be found in U.S. Application No. 15 / 131,693, filed on April 18, 2016, entitled "Detecting Device Movement through Electronic Fingerprint Analysis". The disclosure provided by U.S. Application No. 15 / 131,693 is incorporated herein. The device may respond to determining that the current location of the device is different from the baseline location of the device by initiating an action to ensure compliance with regulatory requirements. The device may be configured to initiate an action to ensure compliance with regulatory requirements only when the difference between the current location of the device and the baseline location of the device exceeds a certain threshold. The action to ensure compliance with regulatory requirements may include, but is not limited to, the following: stopping the operation of AFC adjustment; reducing the transmit power; changing the channel to a channel that does not require the operation of AFC adjustment; powering off the device; and others.
[0066] In an embodiment, a database of AP SSIDs linked to locations may be accessed. Such a database may be provided as a service where a device can survey the APs it can hear and query the database where the device is most likely physically located based on reports of what it can hear.
[0067] AFC can use the wider network in the network to provide similar services. AFC can use data from its own sensors to collect information about the location. The location of the AFC's own sensors may be well-known, allowing information from sensors with well-known locations and well-known antenna patterns to be credible. AFC can receive information from devices, Wi-Fi APs (SSID and RSSI) and / or LTE or 5G base stations or microcells that already have a trusted receiving location for 6GHz signals. 900MHz signals of Wi-Fi HaLow, Lora, SigFox or other such signals can also be obtained in certain areas and from certain devices or sensors. When the device is credible, AFC can use this information to enhance its mapping capabilities. It can also double-check the location information from a new device seeking authorization by requesting information about other signals detected by it from an untrusted device. If the other information matches the location information provided by the new device within a certain error level, AFC will have additional confidence that the location it reports is correct. On the other hand, if the location information from the device is inconsistent with the wireless environment information provided by the device, AFC may not choose to trust the device or provide it with a high-power channel authorization.
[0068] Alternatively, the device may determine its location using available services, instead of having the ability to determine its location by accessing GPS or by using cellular location services. When the device reports its location to the AFC, it may provide an error margin for that determination based on the coefficients returned by the location service.
[0069] Database Management
[0070] A controller or database may be used to store exclusion zone data associated with areas where unlicensed frequency band use may impact microwave pathways. The controller or database may include or may be part of an AFC system. Updates to the exclusion zone data may be pushed to the controller or database, or may be pulled by the controller or database from one or more exclusion zone data sources. The exclusion zone data may include one or more geolocators (e.g., GPS coordinates, etc.) that constitute the boundaries of the exclusion zone or are otherwise located within the boundaries of the exclusion zone. An exclusion zone may be an area designated as an area where unlicensed frequency band use may impact microwave pathways.
[0071] In an embodiment, periodically or in response to certain triggers, the controller or database may identify one or more devices operating at a location that falls within the area that is the subject of updates to the exclusion zone data. For example, when an update to the exclusion zone data is received, the controller or database may check the location information associated with one or more devices to determine whether the location information of any of the one or more devices indicates that the device is located within the area affected by the update. As another example, the controller or database may periodically (e.g., hourly, daily, weekly, etc.) determine whether the location information of any of the one or more devices indicates that the device is located in an area affected by updates to the exclusion zone data during a certain duration covered by the period. In response to determining that the device is located in the area affected by the update to the exclusion zone data, the controller or database may output updated frequency information (e.g., AFC operation requirements) to the device.
[0072] In embodiments, the controller or database may include channel scanning functionality or secure and authenticated access to external channel scanning functionality.
[0073] In an embodiment, the controller or database may maintain a schedule of frequency band usage by one or more microwave systems. The controller or database may clear or terminate channel usage at one or more devices based on the schedule.
[0074] In an embodiment, the controller or database may generate a frequency band usage schedule for one or more microwave systems. The controller or database may monitor channel usage of one or more microwave systems and may record the time / day during which the microwave systems are active. Based on the monitored channel usage, the controller or database may generate a schedule for daily / weekly / yearly usage. The controller or database may clear or terminate channel usage at one or more devices based on the schedule.
[0075] In an embodiment, a controller or database may direct one or more devices (e.g., one or more devices within an MDU (multiple dwelling units), campus, etc.) to use certain frequencies based on frequencies used by other devices. The controller may also direct other devices to change their power levels or use directional null formation to avoid causing interference. For example, a controller or database may allocate 6 GHz channels among a group of APs within a certain proximity of each other, where the allocation is performed on a non-interference basis.
[0076] In an embodiment, a device (e.g., an AP) may receive a communication indicating that a microwave path associated with the device has become active or inactive based on the current location of the device. For example, a beacon positioned proximate to a microwave system may determine the current state of the microwave system. When the state of the microwave system changes (e.g., when the corresponding microwave path becomes active / inactive), the beacon may output a notification indicating the state change to one or more devices located within an exclusion zone associated with the microwave path. For example, the notification may include a clear or terminate request notifying one or more devices that one or more frequencies have become available or unavailable. In addition, the notification may notify one or more devices that an operational requirement may be temporarily ignored or that an operational requirement should be complied with based on the identified state change.
[0077] In an embodiment, the AP may scan channels to determine whether the 6 GHz band is available. For example, an AP operating at low power may perform a scan of the 6 GHz band as a background operation. If a signal is detected on the 6 GHz band, the AP may avoid using the 6 GHz band, or may instead maintain low power until the 6 GHz band is clear.
[0078] Operational deployment
[0079] In an embodiment, an AP may have a 6 GHz radio and another radio (e.g., a 2.4 GHz or 5 GHz radio). If a 6 GHz AP has a legacy band (2.4 GHz or 5 GHz) and a 6 GHz STA also has legacy capabilities, the AP may advertise its 6 GHz capabilities on the legacy band. In an embodiment, a device may be configured with a 2+5+6 solution. In an embodiment, a device may be configured with 2+5+5 / 6, where one of the radio chains may switch between 5 GHz and 6 GHz.
[0080] If the unit is a backend solution and / or controlled by a home network controller, the home network controller can direct the STA / extender to a specific 5 or 6 GHz channel based on the STA's 5 GHz RSSI. The controller can consider the performance of similar stations already attached at 6 GHz to determine if the STA should be directed to a higher frequency band. If the higher channel has a very wide channel and there is little or no interference, the controller can choose to move the STA.
[0081] Figure 22 is a flowchart showing an example process 200 of directing a STA to a specific channel based on potential operating performance in a 6 GHz channel. In order for the controller to make the right decision, it needs to access the AP's AFC channel / power allocation. The AP can handle the request process independently and keep the controller informed of any allocation or rejection in a timely manner. When the controller decides which frequency band to allocate to the station, the controller can consider the STA's current RSSI and RSSI history, as well as the channel allocation and power level limits of the AP it controls. At 205, the controller can determine the STA's 5 GHz RSSI. At 210, the controller can determine the breadth and interference level of the 6 GHz channel. At 215, the controller can determine whether the 6 GHz channel can provide the STA with better performance than the currently used 5 GHz channel. If it is determined that the 6 GHz channel cannot provide better performance for the STA, then at 220 the controller can direct the STA to the 5 GHz channel. If it is determined that the 6 GHz channel does provide better performance for the STA, then at 225 the controller can direct the STA to the 6 GHz channel.
[0082] Figure 3 is a flow chart showing an example process 300 of scanning for a satisfactory 6 GHz channel. If the unit is not relevant, the STA can turn on and activate its 5 GHz radio at 305 and perform a normal scan. If no 6 GHz announcement is found at 310, the STA can remain in the 5 GHz band at 315. If it is found at 310 that the AP also announces 6 GHz capabilities, the STA can consider which 6 GHz channel / band is included in the AP's information. For example, at 320, the STA can determine the operating requirements associated with the 6 GHz band. Since the current regulatory proposal in the United States indicates that the power level can be set by the channel, the STA can consider this. If it is determined at 325 that the operating requirements of the 6 GHz band are satisfactory to the STA, the STA can activate the 6 GHz radio at 330. If at 325, the STA determines that the operating requirements of the 6 GHz band are not satisfactory, the STA can continue to scan at 335. For example, if the channel is a low power channel, the STA can preferentially continue to search until it finds an AFC / high power channel.
[0083] In an embodiment, multiple APs may coordinate to maximize the efficiency of frequency band usage among the multiple APs. For example, the APs may coordinate the use of a large frequency band based on different regulatory requirements associated with each of the frequency bands.
[0084] Since power constraints may be lower (at least for a while), dispersing STAs across multiple APs may help use wide bandwidth to boost data rates. A deployment constrained by low power levels (e.g., 250mW) may require more APs to cover the same area compared to a standard 5GHz AP (1W).
[0085] The set of centrally coordinated APs may be sent in a separate AFC request, and the central coordinator may choose how to allocate STAs based on the responses. In an embodiment, the controller may instruct the AP to resend its request if the result is not acceptable.
[0086] If the AFC withdraws a previously allowed channel from an active AP, the STA may be instructed to go from standard power to low power, or to clear the band.
[0087] In an embodiment, the AFC may withdraw the channel allocation at any time. If the AP receives a withdrawal notification from the AFC, the AP may notify all STAs that they must at least drop to low power. If the operating parameters do not allow the STA to change its power level and remain on the channel, the AP may instruct the STA to switch to a non-6 GHz band until the AP can obtain a new allocation from the AFC.
[0088] Timing distribution / low latency service / QoS
[0089] PTP (IEEE-1588) allows distributed timing over Ethernet. CableLabs' DTP (DOCSIS Timing Protocol) extends this technology over DOCSIS.
[0090] The motivation for 6GHz Wi-Fi adoption is that the new unlicensed band may be virtually free of interference for some time, especially if all four bands are open. If only Band 6 is open, that advantage will be short-lived.
[0091] The present disclosure is applicable to cable modem GWs that also have Wi-Fi including 6GHz (but not required). The CM supports DTP as it does the CMTS. The CMTS / CM can provide several different timing sources. Since different mobile providers are advancing their networks from 4G to 5G at different rates, there may be different timing feeds available for different small cell / pico cell uses. The timing feeds may also have different qualities (4G vs. 5G 1ms).
[0092] The AP may announce that it supports timing allocation, or provide timing allocation later in a capability exchange. This notification may appear through a field in the beacon or in a capability exchange after the STA is associated. The notification may include multiple possible timing sources available to the CM / AP. The notification may also indicate the accuracy or quality of each potential timing source. The STA decides whether the AP can provide the timing feed it needs. The STA may request a timing feed. If the STA wishes to receive a timing allocation, the STA notifies the AP that it wishes to receive a timing allocation. The notification may indicate which timing source the STA is interested in and / or the accuracy or quality level it may need to receive. The AP may evaluate whether it can provide the service that the STA has requested. The AP may need to communicate with the CM and / or CMTS to ensure that the requested service and QoS level can be provided. The AP / CM transmits the request back to the CMTS. If the CM / AP must support multiple timing feeds, the CM may choose which timing feed to use for its internal system, or it may not use any specific feed directly. If the AP can provide the service it requests to the STA, the AP selects OFDM / OFDMA downstream and upstream channels to transmit timing messages. For example, the timing message may be transmitted over the selected 6GHz channel. Note that a channel can actually be one or more resource units (RUs), as known in 11ax with limited bandwidth, but dedicated for this purpose. The AP and STA start communicating over this RU according to a schedule established by the AP to accommodate the QoS requirements of the service level requested by the STA. The AP can select a limited set of MCS settings for the channel to ensure predictability and good performance.
[0093] Figure 4 4 is a flow chart illustrating an example process 400 for establishing a timing allocation between an AP and a STA. At 405, the AP may output an announcement that it supports the timing allocation. At 44, the AP may receive a request from the STA to receive a timing feed, wherein the request is output from the STA in response to the STA identifying the announcement. At 415, a channel may be selected for transmitting a timing message. For example, the timing message may be transmitted via the selected 6 GHz channel. At 420, a schedule for transmitting the timing message may be formulated based on the service level indicated by the request received from the STA. At 425, communication may be initiated between the AP and the STA via the selected channel according to the formulated schedule.
[0094] Figure 5is a flow chart showing an example process 500 of establishing a timing allocation between an AP and a STA, wherein the STA determines whether the AP provides a timing allocation from a certain source at a certain service level. At 505, the STA may receive an announcement message from the AP carrying information associated with the timing allocation provided by the AP. At 510, the STA may identify the source and / or service level provided by the AP. At 515, the STA may determine whether the required timing service is provided by the AP. If the required timing service is not provided by the AP, then at 520 the STA may evaluate other methods for receiving the timing allocation. If the required timing service is provided by the AP, then at 525 the STA may output a request to receive a timing feed from a specified source at a specified service level. At 530, communication may be initiated between the AP and the STA to receive the requested timing feed.
[0095] 6GHz Backbone
[0096] In an embodiment, the 6 GHz band may be used as a backbone by a set of access points or extenders to support a wireless network provided to one or more STAs or clients. One or more channel blocks within one or more sub-bands of the 6 GHz band may be allocated to each of the set of APs or extenders of the wireless network.
[0097] Figure 6 6 GHz backbone 605. In an embodiment, two logical interfaces may be provided by a single 6 GHz radio 610 (e.g., a LAN SSID and a WAN SSID). Traffic between the WAN and LAN SSIDs may pass through a router 615 for typical WAN ingress functions (e.g., a firewall). In an embodiment, VLAN tags may be used to differentiate and separate WAN and LAN traffic. One or more extenders 620 may be associated to a LAN SSID and may obtain an IP address from a gateway (e.g., the router 615 may be integrated within a gateway device). For example, one or more extenders 620 may communicate via a LAN interface 625. The extender 620 may be a Wi-Fi client. The WAN device 630 may discover and associate with a gateway. The WAN device 630 may be a Wi-Fi client. Upon association, a link event occurs on the gateway. The gateway obtains an IP address from the WAN network. The WAN device 630 has a fixed, well-known IP address for management.
[0098] In an embodiment, each corresponding channel block of one or more channels in the 6 GHz band may be allocated to a room or space within a venue. For example, a room configured with a virtual reality headset may have its indoor extender (e.g., extender 620) configured with a 160 MHz channel block, while another room with only cell phone and laptop users may be configured with only an 80 MHz channel block. The power level may be optimized for each channel based on one or more factors associated with the location and / or barriers between each room or space and the 6 GHz AP or extender. Separate channel block allocations may be used for communications between an indoor extender and an AP (e.g., a gateway).
[0099] In an embodiment, signals may be received at and transmitted from a subscriber's premises by a network interface device (NID). A 6 GHz backbone may be used to pass signals between the NID and an AP located within the premises (e.g., the AP may be centrally located within the premises). The 6 GHz backbone may be provided by the NID itself, or by a separate device attached to the NID, mounted to a wall near the NID, or otherwise located near the NID. For example, home network wiring may be eliminated by adding a 6 GHz radio to the NID and using one or more 6 GHz network extenders to provide Wi-Fi coverage throughout the home.
[0100] The network can be configured to use a standard power backbone line, thereby providing higher throughput in channels of a certain size compared to the throughput available for a low power backbone. For example, a NID-AP backbone that can also allow extenders to join can use standard power 320MHz channel blocks to pass information between the NID and the AP and extenders. Within each room, the extender can use low power transmissions through 160MHz or 320MHz channel blocks. Even though these channels can be as large as or larger than the backbone link, the lower power will result in lower throughput within the room. This is still advantageous because it allows indoor extenders to be less likely to interfere with each other while still providing a large amount of bandwidth for indoor devices to provide wireless services.
[0101] Each indoor extender may also choose to use the 2.4 GHz or 5 GHz transmission band as well as the 6 GHz transmission band. If the extender has client devices that require lower frequency bands, the extender may have additional Wi-Fi radios, such as 2.4 GHz or 5 GHz radios, to support these legacy devices. Traffic to and from the indoor extender will still be transmitted over the 6 GHz backbone. In an embodiment, one or more extenders 620 may communicate via Ethernet port 645 through LAN interface 640, via 2.4 GHz radio 655 through LAN interface 650, and / or via 5 GHz radio 665 through LAN interface 660.
[0102] In an embodiment, one or more network extenders 620 may be configured to communicate with WAN devices 630 via the 6 GHz backbone 605. For example, communications may be received and forwarded from and to one or more extenders 620 via the LAN interface 625, and communications may be received and forwarded from and to WAN devices 630 via the WAN interface 635.
[0103] Figure 7 is a block diagram illustrating an example network architecture that facilitates the use of the 6 GHz wireless band. In an embodiment, an adapter may be located in a venue, where the adapter converts WAN communications into Wi-Fi signals, which are then transmitted to one or more devices via the 6 GHz wireless band. In an embodiment, one or more WAN adapters (e.g., 5G mmWave to 6 GHz adapter 705, LTE to 6 GHz adapter 710, PON to 6 GHz adapter 715, and / or HFC to 6 GHz adapter 720) may facilitate signal conversion to support communications between a 6 GHz WAN and one or more various communication networks (e.g., 5 GHz / LTE 725, PON 730, HFC 735). The PON to 6 GHz adapter 715 may be connected to an ONT 740. Each WAN adapter may include a 6 GHz radio to send and receive 6 GHz wireless signals to and from a gateway device (e.g., a tri-band gateway 745). The tri-band gateway 745 may include a 2.4 GHz radio, a 5 GHz radio, and / or a 6 GHz radio, and the gateway may facilitate communications between a 6 GHz WAN and one or more WLANs (e.g., a 5 GHz WLAN and / or a 6 GHz WLAN). The gateway may communicate with one or more extenders (e.g., a 6 GHz extender 750 and / or a 5 GHz extender 755), a client device 760, and / or a mobile device 765 via one or more WLANs.
[0104] Figure 8 An example use of mmWave to 6 GHz bridging is shown. In an embodiment, the adapter 805 may be mounted at a location 810 (e.g., the adapter 805 may be mounted at a window 815 of an exterior wall 820 of the location 810), and the adapter 805 may be used as a mmWave to 6 GHz converter. The adapter 805 may include a 5G UE to 6 GHz Wi-Fi solution, thereby providing a 6 GHz WLAN within the location 810. A 4x4 6 GHz solution may be used to connect to a gateway 825. The adapter 805 may provide a 6 GHz backhaul, and the gateway 825 may have tri-band capabilities, thereby facilitating communication between the gateway 825 and the adapter 805.
[0105] In an embodiment, the adapter 805 may include a removable interface module (e.g., Fig.11 The removable interface module 1130 facilitates the conversion of mmWave communications to 6 GHz communications and vice versa. The removable interface module can be installed at the gateway device 825 or the adapter 805, and the removable interface module can be moved between the gateway device 825 and the adapter 805 based on the quality of the connection with the RCU 830 providing mmWave communications.
[0106] In an embodiment, a user or installer may verify the performance of the 6 GHz backhaul when the removable interface module is installed at the gateway 825 and / or when the removable interface module is installed at the adapter 805. Based on the performance metrics, the user or installer may install the removable interface module at a device or location with better or more desired performance metrics.
[0107] In an embodiment, the gateway 825 may be configured with a plurality of operation modes, wherein the gateway 825 operates in a first mode when it is detected that the removable interface module is installed at the gateway 825, and the gateway operates in a second mode when it is detected that the removable interface module is not installed at the gateway 825. For example, when operating in the first mode, the gateway 825 may disable a 6 GHz module used by the gateway 825 for communicating via a 6 GHz backhaul provided by the adapter 805. When operating in the second mode, the gateway 825 may enable a 6 GHz module used for communicating via a 6 GHz backhaul provided by the adapter 805.
[0108] Fig. 9 905. 6 GHz and 6 GHz adapter 910 are used to introduce broadband to the example home network of the place 905. In an embodiment, the adapter 910 can be connected to the ONT 915 via a wired connection (e.g., 2.5GigE). The adapter 910 may include a 6 GHz radio, through which a 6 GHz wireless backhaul can be provided. The adapter 910 can be installed in the place 905 in close proximity to the ONT 915. The gateway 920 with a 6 GHz radio can utilize the 6 GHz wireless backhaul provided by the adapter 910. With the wireless backhaul, the gateway 920 can be placed in an optimal location within the place 905 to provide a wider coverage area within the place 905. For example, the gateway 920 can be placed at a central location within the place.
[0109] In an embodiment, the gateway may provide a WLAN accessible by one or more extenders 925 and / or one or more client devices 930. The gateway 920 may provide one or more services to one or more MoCA clients 935 via a wired connection to the MoCA clients 935.
[0110] In an embodiment, a rooftop AP 940 may be installed at a rooftop of a location 905. The rooftop AP 940 may be installed in a location that has access to power but not to a data interface. The rooftop AP 940 may communicate via a 6 GHz backhaul provided by the adapter 910 and may provide wireless services to one or more client devices 930. The rooftop AP 940 may communicate wirelessly with a gateway 920.
[0111] Fig.10 10 is a block diagram illustrating an example home network supported by a 6 GHz backbone. In an embodiment, a 6 GHz wireless backhaul may be provided by an adapter 1005 that is located outside of a premises 1010 and connected to an ONT 1015 via a wired connection. The 6 GHz wireless backhaul may be used by a gateway 1020 located within the premises 1010, and the gateway 1020 may provide wireless services to one or more extenders 1025 and / or one or more client devices 1030 via one or more wireless interfaces / radios.
[0112] Fig.11 An example schematic diagram of a millimeter wave to 6 GHz adapter is shown. In an embodiment, the adapter can convert signals received through the sub6 interface 1105 and / or the millimeter wave interface 1110 to signals transmitted through the 6 GHz interface 1115 and / or the Ethernet interface 1120. The adapter can provide 6 GHz wireless service and / or Ethernet communications to the subscriber premises. In an embodiment, the sub6 and / or millimeter wave RF interface and modem 1125 can be installed at the adapter as a removable interface module 1130, and the removable interface module 1130 can be moved from the adapter to a gateway located at a different location at the subscriber premises.
[0113] The adapter may include a SoC (System on Chip) 1135 , a DDR 1140 , a flash memory 1145 , an LED 1150 , and / or a button 1155 .
[0114] In an embodiment, the 6 GHz interface module may include multiple antennas and may support multiple-input-multiple-output (MIMO) services (eg, 2x2, 4x4, etc.).
[0115] 6GHz Structured Wi-Fi in the Home or SMB
[0116] Wi-Fi services are deployed primarily in homes and small and medium businesses (SMBs) on an ad hoc basis. Even though more sophisticated mesh schemes have been used to extend coverage, the channels and frequency bands used have been limited to the relatively crowded 2.4 GHz and 5 GHz bands. The power levels in these bands are such that even in isolated single-family homes (SFRs), the leakage from one home to another is large enough that few homes are free of impacting signals from other nearby homes. For multi-dwelling units (MDUs) and SMB units, the situation is even worse, as most businesses have multiple overlapping signals from other Wi-Fi APs and their clients.
[0117] The 6 GHz band may provide improved conditions using an approach referred to herein as structured Wi-Fi. The 6 GHz band may provide hundreds of GHz of open channels, with the possible limitation that the power levels allowed may be very low (250 mW to 100 mW). Structured APs may provide 6 GHz as well as 2.4 GHz and 5 GHz service. APs may provide more complex switching and routing for packets than is currently common.
[0118] Backbone APs can be connected to at least one other backbone AP using a wide 6GHz channel. Backbone APs can be used as a grid to minimize the number of wireless hops a packet must go through to reach a WAN connection. Opposite the grid of backbone APs are local APs and their clients. Fig.12 is a block diagram illustrating an example network including multiple backbone APs.
[0119] Fig.12 Wider connections for higher bandwidth connections and narrower connections for lower bandwidth connections are shown. For example, the connection between WAN 1205 and backbone AP 1210, the connection between backbone AP 1210, and the connection between backbone AP 1210 and extender 1215 can be a higher bandwidth connection than the connection between local AP 1220 and / or extender 1215 and client device 1225.
[0120] The system uses wider channels, such as 400MHz channels, for backbone connections, and narrower channels, such as 160MHz channels, for connections to clients 1225. Clients can be associated with a local AP or an extender AP, but the backbone connection is a separate channel from the client connections. The channels used for client connections may be at a lower power and use a narrower channel bandwidth. Lower power signals have a harder time penetrating walls, so a client connection to a local AP can still provide a high-speed connection within the room without causing congestion or interfering with other non-Wi-Fi communications.
[0121] In an embodiment, an AP may detect the use of one or more 6 GHz channels by one or more neighboring APs. For example, in an MDU, an AP may be configured to exchange information with a neighboring AP, wherein the information identifies the channels being used by the AP and / or uses metrics associated with the AP's use of the identified channels. Based on the exchanged information, the AP may determine that the use of a 6 GHz channel is optimal. For example, the AP may select a 6 GHz channel that is identified by a neighboring AP as having the lowest level of use.
[0122] In an embodiment, the AP may change 6 GHz channels until a channel not used by a neighboring AP is found.
[0123] In an embodiment, information exchanged between neighboring APs may trigger reallocation of channels used by each AP. For example, each of the neighboring APs may be assigned to a unique channel.
[0124] Physical Instantiation
[0125] Combined backbone AP / local AP (e.g. Fig.12 The integrated backbone AP 1210 and local AP 1220 shown in FIG. 1 may be in a standard black rectangular box, but it is advantageous to place these APs at the ceiling level. For example, the combined backbone AP and local AP may be integrated in Fig. 9 The fewer obstructions high in the room, the fewer moving obstacles that can cause frequent changes in signal levels. One possible instantiation is in a ceiling fan. These fans typically have considerable weight compared to simple light fixtures, making it easier to add AP circuitry. The fan is also typically located in the center of the room, making coverage within the room easier. The ceiling AP may have a 6GHz backbone radio that may support wider channels and / or higher power levels than the second radio in the ceiling AP. The second radio may be another 6GHz radio operating at a lower power level and on a different channel than the backbone AP. The second radio may be a standard single-band or dual-band 2.4GHz or 5GHz Wi-Fi radio. The second radio may be a 6GHz Wi-Fi radio or a LiFi radio. Either of the latter two options is also advantageous for keeping the signal within the room and minimizing interference to adjacent rooms.
[0126] In an embodiment, a ceiling-mounted AP may be installed at a location that is powered but does not have a wired data connection. For example, a ceiling-mounted AP may be installed at a ceiling fan or other ceiling-mounted fixture that has access to power. The ceiling-mounted AP may be connected to a wireless backhaul (e.g., a 6 GHz wireless backhaul) to provide wireless services to one or more client devices via one or more interfaces (e.g., 2.4 GHz, 5 GHz, 6 GHz interfaces, etc.).
[0127] Timing distribution / low latency service / QoS
[0128] PTP (IEEE-1588) allows distributed timing over Ethernet. CableLabs' DTP extends this technology over DOCSIS.
[0129] The motivation for 6GHz Wi-Fi adoption is that the new unlicensed band may be virtually free of interference for some time, especially if all four bands are open. If only Band 6 is open, that advantage will be short-lived.
[0130] The present disclosure is applicable to cable modem GWs that also have Wi-Fi including 6GHz (but not required). The CM supports DTP as it does the CMTS. The CMTS / CM can provide several different timing sources. Since different mobile providers are advancing their networks from 4G to 5G at different rates, there may be different timing feeds available for different small cell / pico cell uses. The timing feeds may also have different qualities (4G vs. 5G 1ms).
[0131] The AP may announce that it supports timing allocation, or provide timing allocation later in a capability exchange. This notification may appear through a field in the beacon or in a capability exchange after the STA is associated. The notification may include multiple possible timing sources available to the CM / AP. The notification may also indicate the accuracy or quality of each potential timing source. The STA decides whether the AP can provide the timing feed it needs. The STA may request a timing feed. If the STA wishes to receive a timing allocation, the STA notifies the AP that it wishes to receive a timing allocation. The notification may indicate which timing source the STA is interested in and / or the accuracy or quality level it may need to receive. The AP may evaluate whether it can provide the service that the STA has requested. The AP may need to communicate with the CM and / or CMTS to ensure that the requested service and QoS level can be provided. The AP / CM transmits the request back to the CMTS. If the CM / AP must support multiple timing feeds, the CM may choose which timing feed to use for its internal system, or it may not use any specific feed directly. If the AP can provide the service it requests to the STA, the AP selects OFDM / OFDMA downstream and upstream channels to transmit timing messages. For example, the timing message may be transmitted over the selected 6GHz channel. Note that a channel can actually be one or more resource units (RUs), as known in 11ax with limited bandwidth, but dedicated for this purpose. The AP and STA start communicating over this RU according to a schedule established by the AP to accommodate the QoS requirements of the service level requested by the STA. The AP can select a limited set of MCS settings for the channel to ensure predictability and good performance.
[0132] Fig.13 1300 is a block diagram of a hardware configuration 1300 that is operable to facilitate and utilize a 6 GHz backbone and / or 6 GHz wireless communications. The hardware configuration 1300 may include a processor 1310, a memory 1320, a storage device 1330, and an input / output device 1340. Each of the components 1310, 1320, 1330, and 1340 may be interconnected, for example, using a system bus 1350. The processor 1310 is capable of processing instructions for execution within the hardware configuration 1300. In one embodiment, the processor 1310 may be a single-threaded processor. In another embodiment, the processor 1310 may be a multi-threaded processor. The processor 1310 is capable of processing instructions stored in the memory 1320 or on the storage device 1330.
[0133] The memory 1320 can store information within the hardware configuration 1300. In one implementation, the memory 1320 can be a computer-readable medium. In one implementation, the memory 1320 can be a volatile memory unit. In another implementation, the memory 1320 can be a non-volatile memory unit.
[0134] In some embodiments, storage device 1330 can provide mass storage for hardware configuration 1300. In one embodiment, storage device 1330 can be a computer readable medium. In various embodiments, storage device 1330 can include, for example, a hard disk device, an optical disk device, a flash memory, or some other large-capacity storage device. In other embodiments, storage device 1330 can be a device external to hardware configuration 1300.
[0135] The input / output device 1340 provides input / output operations for the hardware configuration 1300. In one embodiment, the input / output device 1340 may include one or more of the following: a network interface device (e.g., an Ethernet card), a serial communication device (e.g., an RS-232 port), one or more universal serial bus (USB) interfaces (e.g., USB 2.0 ports), one or more wireless interface devices (e.g., an 802.11 card), and / or one or more interfaces for outputting video and / or data services to a client device (e.g., a TV, STB, computer, mobile device, tablet computer, etc.) or a display device associated with the client device. In another embodiment, the input / output device may include a driver device configured to send communications to and receive communications from one or more networks.
[0136] The subject matter of the present disclosure and its components can be implemented by instructions, which, when executed, cause one or more processing devices to perform the above-mentioned processes and functions. For example, such instructions may include interpretation instructions, such as script instructions, such as JavaScript or ECMAScript instructions, or executable code, or other instructions stored in a computer-readable medium.
[0137] Implementation of the subject matter and functional operations described in this specification may be provided in digital electronic circuitry or in computer software, firmware or hardware, including the structures disclosed in this specification and their structural equivalents, or a combination of one or more of them. Embodiments of the subject matter described in this specification may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a tangible program carrier, for execution by a data processing apparatus or to control the operation of a data processing apparatus.
[0138] A computer program (also referred to as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language file), in a single file dedicated to a related program, or in multiple coordinated files (e.g., files that store one or more modules, subroutines, or code portions). A computer program can be deployed to execute on one computer or on multiple computers located in one location or distributed between multiple locations and interconnected by a communication network.
[0139] The processes and logic flows described in this specification are performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output, thereby binding the processes to a specific machine (e.g., a machine programmed to perform the processes described herein). The processes and logic flows may also be performed by special purpose logic circuitry, and the apparatus may also be implemented as special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application specific integrated circuit).
[0140] Computer-readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media, and storage devices, including, for example, semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices); magnetic disks (e.g., internal hard disks or removable disks); magneto-optical disks; and CD ROM and DVD ROM disks. The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.
[0141] Although this specification contains many specific implementation details, these should not be interpreted as limitations on the scope of any invention or the content that can be claimed, but should be interpreted as descriptions of features that can be directed to specific embodiments of specific inventions. Certain features described in the context of independent embodiments in this specification may also be implemented in combination in a single embodiment. Conversely, the individual features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination. In addition, although the above may describe features as working in certain combinations, even initially claimed as such, in some cases, one or more features from the claimed combination may be removed from the combination, and the claimed combination may involve sub-combinations or changes in sub-combinations.
[0142] Similarly, although operations are shown in a particular order in the accompanying drawings, this situation should not be understood as requiring such operations to be performed in a sequential order or at the particular times shown, or requiring all operations shown to be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of the various system components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can be integrated together in a single software product or packaged into multiple software products.
[0143] Specific embodiments of the subject matter described in this specification have been described. Other embodiments are also within the scope of the appended claims. For example, unless otherwise explicitly stated, the actions set forth in the claims can be performed in a different order and still achieve the desired results. As an example, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or sequential order to achieve the desired results. In some embodiments, multitasking and parallel processing may be advantageous.
Claims
1. A method comprising: receiving, at a wide area network (WAN) adapter located at a premises, one or more WAN communications from one or more networks, wherein the WAN adapter includes at least a 6 GHz radio for providing a 6 GHz wireless backhaul to communicate with a tri-band capable gateway device located at the premises; converting the one or more WAN communications into one or more 6 GHz Wireless Fidelity (Wi-Fi) signals for delivery to a 6 GHz gateway device radio of the gateway device over a 6 GHz wireless frequency band provided by a 6 GHz radio of the WAN adapter; outputting the one or more Wi-Fi signals to the gateway device via a 6 GHz wireless frequency band of the 6 GHz radio; as well as Communicates with the access point via the 6 GHz wireless backhaul.
2. The method of claim 1, wherein the one or more WAN communications are received at the WAN adapter from one or more WAN adapters, wherein the one or more WAN adapters are different from the WAN adapter. 3 . The method of claim 2 , wherein the WAN adapter communicates with the one or more WAN adapters via a wired connection between the WAN adapter and the one or more WAN adapters.
4. The method of claim 1, wherein the WAN adapter further comprises at least a 2.4 GHz radio and a 5 GHz radio. 5 . The method of claim 1 , wherein the WAN adapter receives one or more additional 6 GHz Wi-Fi signals from the gateway device.
6. The method of claim 1, wherein the WAN adapter provides at least a 6 GHz wireless LAN and a 5 GHz wireless LAN.
7. The method of claim 1, wherein the WAN adapter operates as a millimeter wave to 6 GHz converter.
8. The method of claim 7, wherein the WAN adapter comprises a removable interface module that facilitates conversion of mmWave communications to one or more 6 GHz communications.
9. A wide area network (WAN) adapter for receiving one or more WAN communications, the WAN adapter comprising: a radio, wherein the radio receives one or more WAN communications from one or more networks, and wherein the radio includes at least a 6 GHz radio for providing a 6 GHz wireless backhaul to communicate with a tri-band capable gateway device located at a premises; an interface, wherein the interface converts the one or more WAN communications into one or more Wireless Fidelity (Wi-Fi) signals for delivery to a 6 GHz gateway device radio of the gateway device over a 6 GHz wireless band provided by a 6 GHz radio of the WAN adapter; a memory storing one or more computer-readable instructions; as well as a processor configured to execute the one or more computer-readable instructions to: outputting the one or more Wi-Fi signals to the gateway device via a 6 GHz wireless band of the 6 GHz radio; and Communicates with the access point via the 6 GHz wireless backhaul.
10. The WAN adapter of claim 9, wherein the one or more WAN communications are received at the WAN adapter from one or more WAN adapters, wherein the one or more WAN adapters are different than the WAN adapter.
11. The WAN adapter of claim 10, wherein the processor is further configured to execute the one or more computer-readable instructions to: Communicating with the one or more WAN adapters via a wired connection between the WAN adapter and the one or more WAN adapters.
12. The WAN adapter of claim 9, wherein the radio further comprises at least a 2.4 GHz radio and a 5 GHz radio.
13. The WAN adapter of claim 9, wherein the processor is further configured to execute the one or more computer readable instructions to: Provide at least 6 GHz wireless LAN and 5 GHz wireless LAN.
14. One or more non-transitory computer-readable media having instructions operable to cause one or more processors to perform operations comprising: receiving, at a wide area network (WAN) adapter, one or more WAN communications from one or more networks, wherein the WAN adapter includes at least a 6 GHz radio for providing a 6 GHz wireless backhaul to communicate with a tri-band capable gateway device located at the premises; converting the one or more WAN communications into one or more 6 GHz Wireless Fidelity (Wi-Fi) signals for delivery to a 6 GHz gateway device radio of the gateway device over a 6 GHz wireless frequency band provided by a 6 GHz radio of the WAN adapter; outputting the one or more Wi-Fi signals to the gateway device via a 6 GHz wireless frequency band of the 6 GHz radio; as well as Communicates with the access point via the 6 GHz wireless backhaul.
15. The one or more non-transitory computer-readable media of claim 14, wherein the one or more communications are received at the WAN adapter from one or more WAN adapters, wherein the one or more WAN adapters are different than the WAN adapter.
16. The one or more non-transitory computer-readable media of claim 15, wherein the WAN adapter communicates with the one or more WAN adapters via a wired connection between the WAN adapter and the one or more WAN adapters.
17. The one or more non-transitory computer-readable media of claim 14, wherein the WAN adapter further comprises at least a 2.4 GHz radio and a 5 GHz radio.
18. The one or more non-transitory computer-readable media of claim 14, wherein the WAN adapter provides at least a 6 GHz wireless local area network and a 5 GHz wireless local area network.
19. The one or more non-transitory computer-readable media of claim 14, wherein the WAN adapter operates as a millimeter wave to 6 GHz converter.
20. The one or more non-transitory computer-readable media of claim 19, wherein the WAN adapter comprises a removable interface module that facilitates conversion of mmWave communications to one or more 6 GHz communications.
