Automatic frequency coordination for high speed mobility

Abstract

The present disclosure provides systems and methods for managing transmit power and frequency using automatic frequency coordination (AFC). In some implementations, a device sends an AFC request to a network entity. The device receives an AFC response from the network entity, the AFC response including an AFC power level indication for one or more nearest neighbor entities. The device sets a transmit power of the device based at least in part on the AFC power level indication of at least one of the one or more nearest neighbor entities, and the device transmits at the transmit power. In some instances, the device sends a first number of AFC requests during a first instance traveling along a path, and sends a second number of AFC requests less than the first number of AFC requests during one or more consecutive instances following the first instance traveling along the path.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. patent application No. 17 / 945,431, entitled “AUTOMATED FREQUENCY COORDINATION FOR HIGH SPEED MOBILITY,” filed by ANANTHARAMAN et al. on September 15, 2022, which is assigned to the assignee of this application and is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly to using automatic frequency coordination (AFC) for mobile wireless devices.

[0004] Related technical description

[0005] A wireless local area network (WLAN) may be formed by one or more access points (APs) that provide a shared wireless medium for use by multiple client devices, such as wireless stations (STAs). The basic building block of a WLAN that complies with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards is a basic service set (BSS) managed by an AP. Each BSS is identified by a basic service set identifier (BSSID), which is announced by the AP in beacon frames that are periodically broadcast over the wireless medium, so that a STA within the wireless range of the AP can associate with the AP and establish a wireless communication link with the WLAN.

[0006] In some geographic locations, portions of the 6 Gigahertz (GHz) wireless frequency band have been made available for use by wireless communication devices that conform to the IEEE 802.11 family of standards or another suitable set of standards, such as the European Telecommunications Standards Institute (ETSI) family of standards in Europe. Because the 6 GHz band includes licensed microwave communications, public communication systems, and other potentially established systems, wireless communication devices, such as APs for WLANs, use automatic frequency coordination (AFC) to determine transmit power and specific frequencies to use that do not interfere with established devices in the 6 GHz band, thereby enabling such wireless devices to gain unlicensed access to the 6 GHz band. Thus, AFC enables the AP to share the 6 GHz wireless medium with incumbent devices using the 6 GHz band. Summary of the invention

[0007] The systems, methods, and devices of the disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.

[0008] An innovative aspect of the subject matter described in the present disclosure may be implemented in a wireless device. The wireless device may include at least one processor and at least one memory communicatively coupled to the at least one processor. In some specific implementations, the memory stores a processor-readable code, which is configured to cause the device to send an automatic frequency coordination (AFC) request when executed by the at least one processor. The execution of the processor-readable code is configured to cause the device to receive an AFC response, wherein the AFC response includes an AFC power level indication for one or more nearest neighbor entities of the device. The execution of the processor-readable code is further configured to cause the device to set the transmit power of the device based at least in part on the AFC power level indication for at least one of the one or more nearest neighbor entities. The execution of the processor-readable code is also configured to cause the device to transmit at the transmit power.

[0009] In various implementations, execution of the processor readable code is configured to cause the device to send a first number of AFC requests during a first instance of traveling along a path and send a second number of AFC requests less than the first number of AFC requests during one or more consecutive instances following the first instance of traveling along the path, the second number of AFC requests being based at least in part on setting the transmit power to an AFC power level indication for a neighboring entity of the one or more nearest neighboring entities independently of sending another AFC request. In some implementations, execution of the processor readable code is further configured to cause the device to set the number of AFC requests to a minimum value required for performing AFC.

[0010] In various implementations, one or more AFC power level indications for the one or more nearest neighbor entities are stored in a table identifying the one or more nearest neighbor entities, a location of each of the one or more nearest neighbor entities, and the AFC power level indications for the one or more nearest neighbor entities.

[0011] In various implementations, the AFC power level indication is a binary indication of whether standard power (SP) transmit power is allowed.

[0012] In various implementations, the AFC response includes a VendorExtension object to indicate the AFC power level indication to the one or more nearest neighbor entities.

[0013] In various specific implementations, the AFC response includes a frequency indicator of the one or more nearest neighbor entities of the device. Execution of the processor readable code is further configured to cause the device to set a transmit frequency based at least in part on the frequency indicator of the one or more nearest neighbor entities of the device. Transmitting at the transmit power includes transmitting at the transmit frequency.

[0014] Another innovative aspect of the subject matter described in the present disclosure can be implemented as a method for wireless communication by a device. In some specific implementations, the method includes sending an AFC request. The method includes receiving an AFC response, wherein the AFC response includes an AFC power level indication for one or more nearest neighbor entities of the device. The method also includes setting the transmit power of the device based at least in part on the AFC power level indication for at least one of the one or more nearest neighbor entities. The method also includes transmitting at the transmit power.

[0015] In various implementations, the method further includes sending a first number of AFC requests during a first instance of traveling and sending a second number of AFC requests less than the first number of AFC requests during one or more consecutive instances of traveling after the first instance, the second number of AFC requests being based at least in part on setting the transmit power to an AFC power level indication to a neighboring entity of the one or more nearest neighboring entities independently of sending another AFC request. In some implementations, the method further includes setting the number of AFC requests to a minimum value required for performing AFC.

[0016] In various implementations, the AFC power level indications for the one or more nearest neighbor entities are stored in a table identifying the one or more nearest neighbor entities, a location of each of the one or more nearest neighbor entities, and the AFC power level indications for the one or more nearest neighbor entities.

[0017] In various implementations, the AFC power level indication is a binary indication of whether the SP is allowed to transmit power.

[0018] In various implementations, the AFC response includes a VendorExtension object to indicate the AFC power level indication to the one or more nearest neighbor entities.

[0019] In various specific implementations, the AFC response includes a frequency indicator of the one or more nearest neighbor entities of the device. The device sets a transmission frequency based at least in part on the frequency indicator of the one or more nearest neighbor entities of the device. Transmitting at the transmit power includes transmitting at the transmit frequency.

[0020] Another innovative aspect of the subject matter described in the present disclosure may be implemented in a wireless device. The wireless device may include at least one processor and at least one memory communicatively coupled to the at least one processor. In some specific implementations, the memory stores a processor-readable code, which is configured to cause the device to send an AFC request to a network component in a cellular network based at least in part on an AFC event when executed by the at least one processor. The execution of the processor-readable code is configured to cause the device to receive an AFC response from the network component. The execution of the processor-readable code is further configured to cause the device to identify a transmit power to be used by one of an access point (AP) or a station (STA) based on the AFC response. The execution of the processor-readable code is also configured to cause the device to instruct the AP or the STA to use a specific transmit power level to transmit.

[0021] In various implementations, the device is included in the one of the AP or the STA, the AFC request is sent to a network entity, the AFC response is received from the network entity, and the AFC event includes one of the following: the AP or the STA crosses a cellular-based location boundary, the AP is switched between network entities, or an AFC association timer indicates that the AFC request is to be transmitted. In some implementations, execution of the processor-readable code is further configured to cause the device to obtain multiple locations of the AP or the STA associated with multiple AFC events during one or more instances of travel. Execution of the processor-readable code is also configured to cause the device to determine a location pattern of the AP or the STA over time based at least in part on the multiple locations of the AP or the STA associated with the multiple AFC events. Execution of the processor readable code is further configured to cause the device to send, based at least in part on the location pattern, a second number of AFC requests, less than the first number, to the network entity during consecutive instances following the one or more instances of traveling, the first number of AFC requests being sent during one of the one or more instances of traveling along the path, and the second number of AFC requests being based at least in part on setting the transmit power of the AP or the one of the STAs to a transmit power associated with one of the multiple locations of the AP or the one of the STAs and one of the multiple AFC events independently of sending another AFC request.

[0022] In various implementations, the device is included in a cellular network controller to receive one or more AFC requests from the AP and provide one or more AFC responses to the AP, the AFC event comprising receiving an AFC request from the AP, the AFC request to be sent by the device to be sent to an AFC server in the cellular network, and the AFC response to be received by the device to be received from the AFC server. In some implementations, execution of the processor readable code is further configured to cause the device to obtain one or more locations of the AP or the STA during one or more instances of the AP or the STA traveling, the one or more locations being associated with one or more AFC events. Execution of the processor readable code is also configured to cause the device to obtain a corresponding transmit power associated with each of the one or more locations.

[0023] In some implementations, execution of the processor readable code is further configured to cause the device to receive another AFC request from the AP, obtain a first position of the AP or the STA, and send an AFC response to the AP independently of sending the AFC request to the AFC server, the AFC response indicating a current transmit power to be used by the AP or the STA, the current transmit power being based at least in part on the first position of the AP or the STA, the one or more positions of the AP or the STA, and one or more corresponding transmit powers associated with the one or more positions. In some implementations, execution of the processor readable code is further configured to cause the device to send a first number of AFC requests to the AFC server during a first instance of the AP or the STA traveling, the first number of AFC requests being associated with the AP or the STA. Execution of the processor readable code is further configured to cause the device to determine one or more of: a location pattern of the AP or the one of the STAs over time based at least in part on the one or more locations of the AP or the one of the STAs, or an AFC request pattern of the AP over time based at least in part on one or more AFC requests received from the AP. Execution of the processor readable code is further configured to cause the device to send a second number of AFC requests less than the first number of AFC requests to the AFC server during one or more consecutive instances after the first instance of travel by the AP or the one of the STAs, the second number of AFC requests being based at least in part on sending one or more AFC responses to the AP, the one or more AFC responses indicating a transmit power to be used by the AP or the one of the STAs based at least in part on one or more of the location pattern or the AFC request pattern, and the one or more AFC responses sent to the AP being sent independently of sending another AFC request to the AFC server.

[0024] In some specific implementations, execution of the processor readable code is further configured to cause the device to receive a first number of AFC responses associated with the first number of AFC requests, wherein the second number of AFC requests is based on the location pattern, and the location pattern is determined based on a logical model and the first number of AFC requests.

[0025] In various implementations, execution of the processor readable code is further configured to cause the device to send a plurality of AFC requests, wherein the plurality of AFC requests are sent in a random manner.

[0026] In various specific implementations, execution of the processor readable code is further configured to cause the device to send a first number of AFC requests to the AFC server during a first instance of the AP or the STA traveling, wherein each AFC request in the first number of AFC requests is sent based on a first time at a timer. Execution of the processor readable code is further configured to cause the device to send a second number of AFC requests to the AFC server during a second instance of the AP or the STA traveling, wherein each AFC request in the second number of AFC requests is sent based on a second time at the timer, the second time being greater than the first time.

[0027] In various implementations, execution of the processor readable code is further configured to cause the device to send a number of AFC requests, the number of AFC requests being based on a memory size of the device.

[0028] In various implementations, the device will identify a transmit frequency to be used and instruct the one of the AP or the STA to transmit using the transmit frequency.

[0029] Another innovative aspect of the subject matter described in the present disclosure may be implemented in a method for wireless communication by a device. The method includes sending an AFC request to a network component in a cellular network based at least in part on an AFC event. The method also includes receiving an AFC response from the network component. The method also includes identifying a transmit power to be used by one of an AP or a STA based on the AFC response. The method also includes instructing the one of the AP or the STA to transmit using a specific transmit power level.

[0030] In various implementations, the device is included in the one of the AP or the STA, the AFC request is sent to a network entity, the AFC response is received from the network entity, and the AFC event includes one of the following: the AP or the STA crosses a cellular-based location boundary, the AP is switched between network entities, or an AFC association timer indicates that the AFC request is to be transmitted. In some implementations, the method also includes obtaining multiple locations of the AP or the STA associated with multiple AFC events during one or more instances of travel. The method also includes determining a location pattern of the AP or the STA over time based at least in part on the multiple locations of the AP or the STA associated with the multiple AFC events. The method also includes sending, based at least in part on the location pattern, a second number of AFC requests, less than the first number, to the network entity during consecutive instances following the one or more instances of traveling, the second number of AFC requests being based at least in part on setting the transmit power of the AP or the one of the STAs to a transmit power associated with one of the multiple locations of the AP or the one of the STAs and one of the multiple AFC events, independently of sending another AFC request.

[0031] In various implementations, the device is included in a cellular network controller to receive one or more AFC requests from the AP and provide one or more AFC responses to the AP, the AFC event including receiving an AFC request from the AP, the AFC request to be sent by the device to be sent to an AFC server in the cellular network, and the AFC response to be received by the device to be received from the AFC server. In some implementations, the method also includes obtaining one or more locations of the AP or the STA during one or more instances of the AP or the STA traveling, the one or more locations associated with one or more AFC events. The method also includes obtaining a corresponding transmit power associated with each of the one or more locations.

[0032] In some implementations, the method further includes receiving another AFC request from the AP, obtaining a first position of the AP or the STA, and sending an AFC response to the AP independently of sending the AFC request to the AFC server, the AFC response indicating a current transmit power to be used by the AP or the STA, the current transmit power being based at least in part on the first position of the AP or the STA, the one or more positions of the AP or the STA, and one or more corresponding transmit powers associated with the one or more positions. In some implementations, the method further includes sending a first number of AFC requests to the AFC server during a first instance of the AP or the STA traveling, the first number of AFC requests being associated with the AP or the STA. The method further includes determining one or more of the following: a position pattern of the AP or the STA over time based at least in part on the one or more positions of the AP or the STA, or an AFC request pattern of the AP over time based at least in part on one or more AFC requests received from the AP. The method also includes sending a second number of AFC requests, less than the first number of AFC requests, to the AFC server during one or more consecutive instances following the first instance of travel by the AP or the STA, the second number of AFC requests being based at least in part on sending one or more AFC responses to the AP, the one or more AFC responses indicating a transmit power to be used by the AP or the STA based at least in part on one or more of the location pattern or the AFC request pattern, and the one or more AFC responses sent to the AP being sent independently of sending another AFC request to the AFC server.

[0033] In some implementations, the method further includes receiving a first number of AFC responses associated with the first number of AFC requests, wherein the second number of AFC requests is based on the location pattern, and the location pattern is determined based on a logical model and the first number of AFC requests.

[0034] In various implementations, the method further includes sending a plurality of AFC requests, wherein the plurality of AFC requests are sent in a random manner.

[0035] In various specific implementations, the method further includes sending a first number of AFC requests to the AFC server during a first instance of the one of the AP or the STA traveling, wherein each AFC request in the first number of AFC requests is sent based on a first time at a timer. The method further includes sending a second number of AFC requests to the AFC server during a second instance of the one of the AP or the STA traveling along a path, wherein each AFC request in the second number of AFC requests is sent based on a second time at the timer, the second time being greater than the first time.

[0036] In various implementations, the method further includes sending a number of AFC requests, the number of AFC requests being based on a memory size of the device.

[0037] In various implementations, the device identifies a transmit frequency to be used and instructs the one of the AP or the STA to transmit using the specific transmit frequency.

[0038] The details of one or more specific implementations of the subject matter described in the present disclosure are set forth in the accompanying drawings and the following description. Other features, aspects, and advantages will become apparent from the description, drawings, and claims. It should be noted that the relative dimensions in the drawings may not be drawn to scale. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A schematic diagram of an example wireless communication network is shown.

[0040] Figure 2 A schematic diagram of an example cellular network for communicating with a mobile wireless communications device is shown.

[0041] Figure 3 A block diagram of an example wireless communication device is shown.

[0042] Figure 4A A block diagram of an example access point (AP) is shown.

[0043] Figure 4B A block diagram of an example station (STA) is shown.

[0044] Figure 4C A block diagram of example network entities is shown.

[0045] Figure 5 A schematic diagram showing a wireless communication device traveling through an area for which a transmit power of the wireless communication device is to be determined is shown.

[0046] Figure 6 A schematic diagram showing a wireless communication device sending an automatic frequency coordination (AFC) request to a nearest neighbor entity of the wireless communication device is shown.

[0047] Figures 7 to 9 A flow chart illustrating example operations for wireless communications to support AFC requests to nearest neighbor entities of a wireless communication device to control transmit power of the wireless communication device in accordance with some implementations is shown.

[0048] Fig.10 A schematic diagram showing a wireless communication device sending an AFC request based on crossing a defined location area is shown.

[0049] Fig.11 A schematic diagram showing a wireless communication device sending an AFC request based on a handover between network entities is shown.

[0050] Fig.12 A schematic diagram showing a wireless communication device sending AFC requests at regular intervals.

[0051] Fig.13 A sequence diagram depicting example wireless communications supporting cellular network assistance in controlling transmit power of a wireless communication device according to some implementations is shown.

[0052] Figures 14 to 22 A flow chart illustrating example operations for wireless communications supporting AFC requests based on AFC events for controlling transmit power of a wireless communication device in accordance with some implementations is shown.

[0053] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION

[0054] The following description is directed to some specific implementations in order to describe the innovative aspects of the present disclosure. However, those skilled in the art will readily recognize that the teachings herein can be applied in a variety of different ways. The described implementations can be implemented in any device, system, or network capable of sending and receiving radio frequency (RF) signals according to one or more of the following: Long Term Evolution (LTE), 3G, 4G, or 5G (New Radio (NR)) standards issued by the Third Generation Partnership Project (3GPP), the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, the IEEE 802.15 standard, or as defined by the Bluetooth Special Interest Group (SIG). Standards, etc. The described implementations may be implemented in any device, system, or network capable of sending and receiving RF signals according to one or more of the following technologies or techniques: Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), Single Carrier FDMA (SC-FDMA), Single User (SU) Multiple Input Multiple Output (MIMO), and Multi-User (MU) MIMO. The described implementations may also be implemented using other wireless communication protocols or RF signals suitable for use in one or more of a wireless wide area network (WWAN), a wireless personal area network (WPAN), a wireless local area network (WLAN), or an Internet of Things (IOT) network.

[0055] The IEEE 802.11ax amendment to the IEEE 802.11 standard (among other standards) describes the use of an unlicensed portion of the 6 Gigahertz (GHz) wireless band for wireless communications, and various locations around the world have opened up the 6 GHz wireless band for wireless communications. However, various communications devices are licensed in the 6 GHz wireless band, such as specially licensed point-to-point microwave communications. In order not to interfere with previously licensed devices, wireless devices reduce their transmit power for communicating in the 6 GHz wireless band. For example, as defined by the Federal Communications Commission (FCC), an access point (AP) may adjust its transmit power from transmitting at standard power (SP) to low power indoors (LPI), very low power (VLP) for mobile APs, or to other future power levels that may be defined (and to ensure clients of the wireless local area network (WLAN) of the AP).

[0056] Automatic frequency coordination (AFC) has been introduced to enable wireless communication devices to transmit with SPs in the 6 GHz wireless band when there are no incumbent devices near the AP. For AFC, an AFC server stores the geographic location and transmit power limits of the incumbent devices. For a wireless communication device (such as an AP) in a new geographic location, the wireless communication device transmits an AFC request, which indicates the location of the wireless communication device (such as the latitude and longitude of the location) and requests the AFC server for the permitted power level for the location based on the information stored on the AFC server. For mobile wireless communication devices (such as APs on buses, trains, and other mobile devices), the wireless communication device repeatedly sends AFC requests (such as via a cellular network) to identify the allowed transmit power for the current location. As the number of mobile wireless communication devices increases, the number of AFC requests and responses increases, which may saturate, for example, the cellular network used to send AFC requests and responses and the AFC server that processes and provides AFC requests and responses. Therefore, it is necessary to reduce the number of AFC requests and responses required to identify and set the transmit power of the wireless communication device when it is on the 6 GHz wireless band.

[0057] The implementations described herein provide various frameworks for still identifying the required transmit power to be used in the 6 GHz wireless band using a reduced number of AFC requests and responses. Specifically, in some implementations, a device may send an AFC request to a network entity (such as a base station of a cellular network). The device may then receive an AFC response, wherein the AFC response includes an AFC power level indication for one or more nearest neighbor entities of the device. The device may then set the transmit power of the device based at least in part on the AFC power level indication for at least one of the one or more nearest neighbor entities, and transmit at the transmit power. By sending an AFC response to a nearest neighbor by a network entity, setting the transmit power based on the neighbor's AFC power level, and / or limiting the sending of an AFC request to a specific AFC event, various aspects of the present disclosure may reduce the number of AFC requests that are traditionally required to transmit to an AFC server to identify the transmit power of an AP.

[0058] In various embodiments, the device sends a first number of AFC requests during a first instance of traveling along a path and sends a second number of AFC requests less than the first number of AFC requests during one or more consecutive instances after the first instance of traveling along the path, wherein the second number of AFC requests is based at least in part on setting the transmit power to one or more AFC power level indications stored by the device independently of sending another AFC request. In some other embodiments, the device may send an AFC request based at least in part on an AFC event, wherein a network component in a cellular network receives the AFC request. The device may then receive an AFC response, identify a transmit power to be used by a wireless local area network (WLAN) device based on the AFC response, and instruct the WLAN device to use a specific transmit power level and frequency. In various embodiments, the AFC event includes one of the following: the WLAN device crosses a cellular-based location boundary, an AP of the WLAN switches between network entities, or an AFC association timer indicates that an AFC request will be transmitted. In various embodiments, the AFC response may also indicate a frequency to be used. In some embodiments, the frequency indication may be based on the nearest neighboring entity of the device. The device can identify the frequency to use based on the AFC response and instruct the WLAN device (which can be itself or another device) to use the frequency for transmission. In these ways, the mobile AP and stations wirelessly coupled to the mobile AP can use AFC to set transmit power as needed (and determine which frequencies can be allowed for transmission) while reducing the number of AFC requests and responses required.

[0059] Certain implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages. Aspects of the present disclosure may reduce the number of AFC requests traditionally required to identify the transmit power of an AP by initially sending an AFC request for a nearest neighbor or limiting the sending of an AFC request to a specific AFC event. By reducing the number of AFC requests, fewer resources of the wireless network (such as bandwidth of a cellular network and components of a core network) are required to send the AFC requests. Additionally, by reducing the number of AFC requests, the AFC server requires fewer resources and less time to process the AFC requests.

[0060] Figure 1 A block diagram of an example wireless communication network 100 is shown. According to some aspects, the wireless communication network 100 may be an example of a wireless local area network (WLAN) such as a Wi-Fi network (and will be referred to as WLAN 100 hereinafter). For example, the WLAN 100 may be a network that implements at least one of the IEEE 802.11 family of standards such as those defined by the IEEE 802.11-2016 specification or an amendment thereof, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be. The WLAN 100 may include numerous wireless communication devices such as an access point (AP) 102 and a plurality of stations (STAs) 104. Although only one AP 102 is shown, the WLAN 100 may also include a plurality of APs 102.

[0061] Each of the STAs 104 may also be referred to as a mobile station (MS), a mobile device, a mobile handset, a wireless handset, an access terminal (AT), a user equipment (UE), a subscriber station (SS), or a subscriber unit, etc. The STAs 104 may represent a variety of devices, such as mobile phones, personal digital assistants (PDAs), other handheld devices, netbooks, notebook computers, tablet computers, laptop computers, display devices (e.g., TVs, computer monitors, navigation systems, etc.), music or other audio or stereo equipment, remote control devices (“remote controls”), printers, kitchen or other home appliances, key fobs (e.g., for passive keyless entry and start (PKES) systems), etc.

[0062] A single AP 102 and the associated set of STAs 104 may be referred to as a basic service set (BSS), which is managed by the corresponding AP 102 . Figure 1Additionally shown is an example coverage area 106 of the AP 102, which may represent a basic service area (BSA) of the WLAN 100. The BSS may be identified to users by a service set identifier (SSID) and may also be identified to other devices by a basic service set identifier (BSSID), which may be a medium access control (MAC) address of the AP 102. The AP 102 periodically broadcasts a beacon frame (“beacon”) including the BSSID to enable any STA 104 within the wireless range of the AP 102 to “associate” or re-associate with the AP 102 to establish or maintain a corresponding communication link 108 (also referred to as a “Wi-Fi link” hereinafter) with the AP 102. For example, the beacon may include an identification of a primary channel used by the corresponding AP 102 and a timing synchronization function for establishing or maintaining timing synchronization with the AP 102. The AP 102 may provide the various STAs 104 in the WLAN with access to external networks via respective communication links 108 .

[0063] To establish a communication link 108 with the AP 102, each of the STAs 104 is configured to perform passive or active scanning operations ("scans") on frequency channels in one or more frequency bands (eg, the 2.4 GHz, 5.0 GHz, 6.0 GHz, or 60 GHz bands). To perform passive scanning, the STA 104 listens for beacons transmitted by the corresponding AP 102 at periodic time intervals, referred to as target beacon transmission time (TBTT), measured in time units (TUs), where one TU may be equal to 1024 microseconds (μs). To perform active scanning, the STA 104 generates probe requests and transmits them sequentially on each channel to be scanned, and listens for probe responses from the AP 102. Each STA 104 may be configured to identify or select an AP 102 to associate with based on the scanning information obtained through passive or active scanning, and perform authentication and association operations to establish a communication link 108 with the selected AP 102. The AP 102 assigns an association identifier (AID) to the STA 104 at the end of the association operation, and the AP 102 uses the association identifier (AID) to track the STA 104.

[0064] As wireless networks become more and more common, STA 104 may have the opportunity to select one of many BSSs within the range of the STA or to select among multiple APs 102 that together form an extended service set (ESS) (including multiple connected BSSs). Extended network stations associated with WLAN 100 can be connected to a wired or wireless distribution system that allows multiple APs 102 to be connected in such an ESS. Therefore, STA 104 can be covered by more than one AP 102 and can be associated with different APs 102 at different times for different transmissions. Additionally, after associating with AP 102, STA 104 can also be configured to periodically scan the surrounding environment of the STA to find a more appropriate AP 102 to associate with it. For example, a STA 104 that is moving relative to the STA's associated AP 102 can perform a "roaming" scan to find another AP 102 with more suitable network characteristics (such as a larger received signal strength indicator (RSSI) or a reduced traffic load).

[0065] In some cases, STA 104 may form a network without AP 102 or other equipment other than STA 104 itself. An example of such a network is a self-organizing (ad hoc) network (or wireless self-organizing network). A self-organizing network may alternatively be referred to as a mesh network or a peer-to-peer (P2P) network. In some cases, a self-organizing network may be implemented within a larger wireless network (such as WLAN 100). In such a specific implementation, although STA 104 may be able to communicate with each other through AP 102 using communication link 108, STA 104 may also communicate directly with each other via direct communication link 110. Additionally, two STA 104 may communicate via direct communication link 110, regardless of whether the two STA 104 are associated with the same AP 102 and served by the same AP. In such a self-organizing system, one or more STA 104 may assume the role played by AP 102 in the BSS. Such STA 104 may be referred to as a group owner (GO) and may coordinate the transmission within the self-organizing network. Examples of direct communication link 110 include a Wi-Fi direct connection, a connection established by using a Wi-Fi Tunneled Direct Link Setup (TDLS) link, and other P2P group connections.

[0066] The AP 102 and the STA 104 may operate and communicate in accordance with the IEEE 802.11 family of standards (such as those defined by the IEEE 802.11-2016 specification or amendments thereof, including, but not limited to, 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be) (via respective communication links 108). These standards define WLAN radio and baseband protocols for the PHY and medium access control (MAC) layers. The AP 102 and the STA 104 send and receive wireless communications (hereinafter also referred to as "Wi-Fi communications") to and from each other in the form of physical layer convergence protocol (PLCP) protocol data units (PPDUs). The AP 102 and STA 104 in the WLAN 100 may send PPDUs on an unlicensed spectrum, which may be a portion of a spectrum that includes frequency bands traditionally used by Wi-Fi technology, such as the 2.4 GHz band, the 5.0 GHz band, the 60 GHz band, the 3.6 GHz band, and the 900 MHz band. Specific implementations of the AP 102 and STA 104 described herein may also communicate in other frequency bands, such as the 6.0 GHz band, that may support both licensed and unlicensed communications. The AP 102 and STA 104 may also be configured to communicate on other frequency bands, such as shared licensed frequency bands, where multiple operators may have licenses to operate in one or more of the same or overlapping frequency bands.

[0067] Each of the frequency bands may include multiple sub-bands or frequency channels. For example, PPDUs that comply with the IEEE 802.11n, 802.11ac, and 802.11ax standard amendments may be sent on 2.4 GHz and 5.0 GHz frequency bands, where each frequency band is divided into multiple 20 MHz channels. Therefore, these PPDUs are sent on a physical channel with a minimum bandwidth of 20 MHz, but larger channels may be formed through channel bonding. For example, a PPDU may be sent on a physical channel with a bandwidth of 40 MHz, 80 MHz, 160 MHz, or 320 MHz by bonding multiple 20 MHz channels together.

[0068] Each PPDU is a composite structure including a PHY preamble and a payload in the form of a PLCP service data unit (PSDU). The information provided in the preamble can be used by the receiving device to decode subsequent data in the PSDU. In an instance where the PPDU is sent on a bound channel, the preamble field can be copied and sent in each component channel of a plurality of component channels. The PHY preamble may include both a legacy part (or "legacy preamble") and a non-legacy part (or "non-legacy preamble"). Legacy preambles can be used for other purposes such as packet detection, automatic gain control, and channel estimation. Legacy preambles can also be used to maintain compatibility with legacy devices. The format, decoding, and information provided therein of the non-legacy part of the preamble are based on the specific IEEE 802.11 protocol to be used to send the payload.

[0069] Figure 2 A block diagram of an example cellular network 200 for communicating with a mobile wireless communication device 202 is shown. According to some aspects, the cellular network 200 may be a network that implements at least one standard of the 3rd Generation Partnership Project (3GPP) family of standards, such as those defined for 3G, 4G, Long Term Evolution (LTE), or 5G-New Radio (NR). The cellular network 200 may include a number of network entities 206 for communicating between one or more client devices (also referred to as user equipment (UE)), such as the mobile wireless communication device 202, and the cellular network 200 via communication links 208. Although only one wireless communication device 202 is shown, the cellular network may communicate with multiple wireless communication devices 202.

[0070] In some implementations, the wireless communication device 202 is Figure 1 1. Thus, the wireless communication device 202 can be associated with a BSS or ESS, and one or more STAs can be wirelessly coupled to the AP 102. In some implementations, the wireless communication device 202 is an example of a STA that is wirelessly coupled to an AP that communicates with a network entity 206. The wireless communication device 202 is depicted as being mobile by being included in a high-speed train 204. In some other implementations, the wireless communication device 202 can be included in a car, bus, boat, or other vehicle such that the location of the wireless communication device 202 can change over time. Although in Figure 2 One wireless communication device 202 and three network entities 206 are depicted as UEs in the example of FIG. 4 , but any number of UEs may be communicatively coupled to the cellular network 200 , which may include any number of network entities 206 .

[0071] The cellular network 200 is depicted as including network entities 206, a radio network controller 210, a core network 214, a network management server 220, one or more application servers 222, and (optionally) a location register 218. One or more of the network entities 206 may be referred to herein as a transmit-receive point (TRP) 206. The network entities 206 may include macrocell network entities (high-power cellular network entities) and / or small cell network entities (low-power cellular network entities). In some implementations, the macrocell network entity may include an evolved Node B (eNB) (where the cellular network 200 corresponds to an LTE network) or a next-generation Node B (gNB) (where the cellular network 200 corresponds to a 5G network) or a combination of both, and the small cell network entity may include a femtocell, a picocell, a microcell, etc.

[0072] In some examples, network entity 206 (e.g., a base station) may be implemented in a converged (e.g., monolithic, stand-alone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 206 (e.g., a single RAN node, such as a base station).

[0073] In some examples, the network entity 206 can be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture) that can be configured to utilize a protocol stack that is physically or logically distributed between two or more network entities 206, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, the network entity 206 may include one or more of the following: a central unit (CU), a distributed unit (DU), a radio unit (RU), a RAN intelligent controller (RIC) (e.g., a near real-time RIC (near RT) The RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remote radio unit (RRU), or a transmit receive point (TRP). One or more components of the network entity 206 in the decomposed RAN architecture may be co-located, or one or more components of the network entity 206 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 206 of the decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0074] The network entities 206 may collectively form a radio access network (RAN) and interface with a core network 214 (e.g., an evolved packet core (EPC) or a next generation core (NGC)) via backhaul links 212 and 216 and a radio network controller 210. In various implementations, the core network 214 is further coupled to a network management server (NMS) 220 and one or more application servers 222 via a backhaul link 224. In some implementations, the core network 214 may also be coupled to a location register 218 via the backhaul link 224. Among other functions, the network entity 206 may perform functions related to one or more of the following: delivering user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of warning messages. In some specific implementations, one or more network entities 206 may also be configured for RF sensing. The network entities 206 may communicate with each other directly or indirectly via backhaul links (e.g., via EPC / NGC), which may be wired or wireless or a combination of both. Similarly, the backhaul links 212, 216, and 224 may be wired or wireless or a combination of both.

[0075] If the cellular network 200 includes a location register 218, the location register 218 may be used to store the location of the wireless communication device 202 or other UE coupled to the cellular network 200. For example, the wireless communication device 202 may periodically send its location to the network entity 206 (which may be provided to the location register 218 via the core network 214), and the location of the wireless communication device may be stored in one of the location registers 218. In this way, one or more components of the cellular network 200 may be used to track the location of the UE over time. In some implementations, the location register 218 is used for one or more cellular network components to assist in the AFC operations described herein. The location register 218 may also be used for other location services such as those based on a location management function (LMF).

[0076] The NMS 220 is used to manage the network associated with the wireless communication device 202. For example, the AP on the high-speed train 204 can be used for the managed wireless network in the high-speed train 204. In various specific implementations, the NMS 220 performs authorization, authentication, and accounting (AAA) for the managed network. For example, the NMS 220 can be used to enforce policies, audit usage, manage billing, or provide other services associated with the managed network.

[0077] One or more application servers 222 may be used to provide one or more Internet applications or other applications to a UE coupled to a cellular network (such as an AP in communication with the network entity 206) or to other devices communicatively coupled to the application server (such as one or more STAs communicatively coupled to the AP in communication with the network entity 206). For example, a streaming service may include an application server 222 for streaming media to one or more devices in the high-speed train 204. In various specific implementations, the application server 222 includes an AFC server 226, which may include one or more servers configured to provide AFC services to one or more devices (such as the wireless communication device 202) for a defined area. The AFC server 226 stores the locations of devices communicating in the 6 GHz wireless band in a defined area (such as a licensed microwave tower) and location areas associated with these devices (such as the location of the device or the area in which the device will communicate). The location areas may be stored according to geographic tags such as latitude and longitude. For example, an AFC server 226 serving devices traveling along one or more track lines including a high-speed train 204 may store the geographic locations of microwave towers or other permitted, preconfigured, or known devices present in the area around the one or more track lines. The AFC server 226 also stores the transmit power of other devices allowed by the permitted, preconfigured, or known devices for each permitted, preconfigured, or known device. For example, the AFC server 226 may store an indication of whether the device allows SP or LPI (or may only allow VLP) for an AP transmitting at a frequency of 6 GHz. In some other examples, the AFC server 226 may store an indication of the actual transmit power allowed, or another suitable indication that allows the AP to set the transmit power of the AP to the allowed power setting when it is near a permitted device. In the case where the AFC server 226 stores the location area of ​​existing devices and the transmit power level allowed by the existing devices, the AFC server 226 is able to process an AFC request indicating the location of the wireless communication device 202 so as to identify the transmit power allowed at the indicated location and provide an AFC response indicating the allowed transmit power. In some implementations, the AFC server 226 also stores an indication of frequencies allowed by one or more of the existing devices. For example, for an existing device occupying a particular 20 MHz channel in the 6 GHz wireless band, the AFC server 226 may store an indication for the existing device that the particular 20 MHz channel will not be used at a location corresponding to the existing device, or the AFC server 226 may store an indication of all 20 MHz channels allowed for use (excluding the particular 20 MHz channel).

[0078] Although the location register 218, NMS 220, and one or more application servers 222 are depicted as being external to the core network 214, in some implementations, one or more of the location register 218, NMS 220, or one or more application servers 222 are included in the core network 214. Alternatively, although the location register 218, NMS 220, and one or more application servers 222 are described as being included in the cellular network 200, the location register 218, NMS 220, or one or more application servers 222 may be outside the cellular network 200. Any of the components depicted as being included in the cellular network 200, such as the RNC 210, one or more components of the core network 214, the location register 218, NMS 220, or one or more application servers 222 (such as the AFC server 226), may be referred to herein as a network component or a cellular network component. In addition, Figure 2 Any of the components depicted in the figure (such as wireless communication device 202, network entity 206, RNC 210, one or more components of core network 214, location register 218, NMS 220, or one or more application servers 222 (such as AFC server 226)) may be referred to as a device in this article. In addition, a wireless communication device may refer to the device itself or at least a part of the device (such as the one referred to below). Figure 3 described).

[0079] Each of the network entities 206 may provide communication coverage for a corresponding geographic coverage area. In one aspect, one or more cells may be supported by the network entity in each coverage area. A "cell" is a logical communication entity used to communicate with a network entity or UE (e.g., via a certain frequency resource referred to as a carrier frequency, component carrier, carrier, frequency band, etc.), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) for distinguishing cells operating via the same or different carrier frequencies. In some cases, different cells may be configured according to different protocol types (e.g., machine type communication (MTC), narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that can provide access to different types of UEs. In some cases, the term "cell" may also refer to a geographic coverage area (e.g., a sector) of a network entity, as long as a carrier frequency can be detected and used for communication within a portion of the geographic coverage area.

[0080] Although adjacent macrocell network entity geographic coverage areas may partially overlap (e.g., in a handover zone), some areas of the geographic coverage area may substantially overlap with a larger geographic coverage area. For example, a small cell network entity may have a coverage area that substantially overlaps with the coverage area of ​​one or more macrocell network entities. A network that includes both small cell network entities and macrocell network entities may be referred to as a heterogeneous network. A heterogeneous network may also include a home eNB (HeNB) that may provide services to a restricted group referred to as a closed subscriber group (CSG).

[0081] The communication link between the network entity and the UE may include UL (also referred to as a reverse link) transmission from the UE to the network entity and / or DL ​​(also referred to as a forward link) transmission from the network entity to the UE. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may pass through one or more carrier frequencies. The allocation of carriers may be asymmetric for DL ​​and UL (e.g., more or fewer carriers may be allocated to DL than to UL). UL and DL transmissions as described herein may be performed on a user plane (UP) or a control plane (CP).

[0082] Figure 3 1 shows a block diagram of an example wireless communication device 300. In some implementations, the wireless communication device 300 may be a wireless communication device for a STA (such as the one described above with reference to FIG. Figure 1 In some implementations, the wireless communication device 300 may be an example of a device in an AP (such as one of the STAs 104 described above). Figure 1 In some implementations, the wireless communication device 300 may be an example of a device in a network entity (such as the AP 102 described above). Figure 2 The wireless communication device 300 is an example of a device in the network entity 206 described herein. The wireless communication device 300 is capable of sending (or outputting for sending) and receiving wireless communications (e.g., in the form of wireless packets). For example, the wireless communication device 300 may be configured to send and receive packets in the form of physical layer convergence protocol (PLCP) protocol data units (PPDUs) and medium access control (MAC) protocol data units (MPDUs) that comply with the IEEE 802.11 standard (such as the standards defined by the IEEE 802.11-2016 specification or its amendments, including but not limited to 802.11ah, 802.11ad, 802.11ay, 802.11ax, 802.11az, 802.11ba, and 802.11be). Additionally or alternatively, the wireless communication device 300 may be configured to send and receive packets that comply with one or more of the 3GPP standards (such as for 3G, 4G, or 5G) or other cellular or WWAN technologies.

[0083] The wireless communication device 300 may be a chip, system on chip (SoC), chipset, package or device including one or more modems 302 (e.g., Wi-Fi (IEEE802.11 compliant) modems), or may include the chip, system on chip (SoC), chipset, package or device. In some implementations, one or more modems 302 (collectively referred to as "modems 302") additionally include a WWAN modem (e.g., a 3GPP 4G LTE or 5G compatible modem). In some implementations, the wireless communication device 300 also includes one or more radio components 304 (collectively referred to as "radio components 404"). In some implementations, the wireless communication device 300 also includes one or more processors, processing blocks or processing elements (collectively referred to as "processors 306") and one or more memory blocks or elements (collectively referred to as "memory 308").

[0084] The modem 302 may include an intelligent hardware block or device, such as an application specific integrated circuit (ASIC) or the like. The modem 302 is configured to implement the PHY layer. For example, the modem 302 is configured to modulate packets and output the modulated packets to the radio component 304 for transmission over a wireless medium. Similarly, the modem 302 is configured to obtain the modulated packets received by the radio component 304 and demodulate the packets to provide demodulated packets. In addition to the modulator and demodulator, the modem 302 may also include a digital signal processing (DSP) circuit, an automatic gain control (AGC), a decoder, a decoder, a multiplexer, and a demultiplexer. For example, when in a transmit mode, the data obtained from the processor 306 is provided to a decoder, which encodes the data to provide coded bits. The coded bits are then mapped to points in the modulation constellation (using the selected MCS) to provide modulated symbols. The modulated symbols can then be mapped to a number N SS spatial streams or the number N STS The modulated symbols in the corresponding spatial stream or space-time stream may then be multiplexed, transformed via an inverse fast Fourier transform (IFFT) block, and then provided to the DSP circuit for Tx windowing and filtering. The digital signal may then be provided to a digital-to-analog converter (DAC). The resulting analog signal may then be provided to an upconverter and provided to the radio component 304. In a specific implementation involving beamforming, the modulated symbols in the corresponding spatial stream are pre-decoded via a steering matrix before being provided to the IFFT block.

[0085] When in receive mode, a digital signal received from the radio component 304 is provided to a DSP circuit configured to acquire the received signal, for example, by detecting the presence of a signal and estimating initial timing and frequency offset. The DSP circuit is further configured to digitally condition the digital signal, for example, using channel (narrowband) filtering, analog impairment conditioning (such as correcting I / Q imbalance), and applying digital gain to obtain a narrowband signal. The output of the DSP circuit may then be fed to an AGC configured to use information extracted from the digital signal (e.g., in one or more received training fields) to determine an appropriate gain. The output of the DSP circuit is also coupled to a demodulator configured to extract the modulated symbols from the signal and, for example, calculate a log-likelihood ratio (LLR) for each bit position of each subcarrier in each spatial stream. The demodulator is coupled to a decoder, which may be configured to process the LLRs to provide decoded bits. The decoded bits from all spatial streams are then fed to a demultiplexer for demultiplexing. The demultiplexed bits may then be descrambled and provided to the MAC layer (processor 306) for processing, evaluation, or interpretation.

[0086] The radio 304 includes at least one radio frequency (RF) transmitter (or "transmitter chain") and at least one RF receiver (or "receiver chain"), which may be combined into one or more transceivers. For example, the RF transmitter and receiver may include various DSP circuits, including at least one power amplifier (PA) and at least one low noise amplifier (LNA), respectively. The RF transmitter and receiver may in turn be coupled to one or more antennas. For example, in some implementations, the wireless communication device 300 may include or be coupled to multiple transmit antennas (each with a corresponding transmit chain) and multiple receive antennas (each with a corresponding receive chain). The symbols output from the modem 302 are provided to the radio 304, which then transmits the symbols via the coupled antennas. Similarly, the symbols received via the antennas are obtained by the radio 304, which then provides the symbols to the modem 302.

[0087] The processor 306 may include an intelligent hardware block or device designed to perform the functions described herein, such as a processing core, a processing block, a central processing unit (CPU), a microprocessor, a microcontroller, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD) (such as a field programmable gate array (FPGA)), discrete gate or transistor logic, discrete hardware components, or any combination thereof. The processor 306 processes information received through the radio component 304 and the modem 302, and processes information to be output by the modem 302 and the radio component 304 to be sent through the wireless medium. For example, the processor 306 may implement a control plane and a MAC layer, which is configured to perform various operations related to the generation and transmission of MPDUs, frames, or packets. The MAC layer is configured to perform or facilitate the coding and decoding of frames, spatial multiplexing, space-time block coding (STBC), beamforming, and OFDMA resource allocation, and other operations or techniques. In some specific implementations, the processor 306 may control the modem 302 to cause the modem to perform the various operations described above.

[0088] The memory 308 may include a tangible storage medium, such as a random access memory (RAM) or a read-only memory (ROM) or a combination thereof. The memory 308 may also store non-transitory processor-executable or computer-executable software (SW) code containing instructions that, when executed by the processor 306, cause the processor to perform various operations described herein for wireless communication, including generation, transmission, reception, and interpretation of MPDUs, frames, or packets. For example, various functions of the components disclosed herein or various blocks or steps of the methods, operations, processes, or algorithms disclosed herein may be implemented as one or more modules of one or more computer programs.

[0089] Figure 4A 4 shows a block diagram of an example AP 402. For example, AP 402 may be a reference Figure 1 The AP 102 is described as an example implementation. The AP 402 includes a wireless communication device (WCD) 410. For example, the wireless communication device 410 may be a reference Figure 3An example implementation of the wireless communication device 300 described. The AP 402 also includes a plurality of antennas 420 coupled to the wireless communication device 410 to send and receive wireless communications. In some implementations, the AP 402 additionally includes an application processor 430 coupled to the wireless communication device 410 and a memory 440 coupled to the application processor 430. The AP 402 also includes at least one external network interface 450 that enables the AP 402 to communicate with a core network or a backhaul network to gain access to an external network including the Internet. For example, the external network interface 450 may include one or both of a wired (e.g., Ethernet) network interface and a wireless network interface (such as a WWAN interface). In some implementations, the external network interface 450 is configured to communicate within a cellular network, and the wireless communication device 410 (in combination with the antenna 420) is configured to communicate within a WLAN. In some other implementations, the wireless communication device 410 (in combination with the antenna 420) is configured to communicate within both a cellular network and a WLAN. The AP 402 may also include one or more sensors 405. For example, the AP 402 may include one or more of a global positioning system (GPS) receiver or other suitable global navigation satellite system (GNSS) receiver, an accelerometer, a magnetometer, or other suitable sensors for determining the location of the AP 402. Multiple of the above components may communicate directly or indirectly with other of the components via at least one bus. The AP 402 also includes a housing that encloses the wireless communication device 410, the application processor 430, the memory 440, and at least a portion of the antenna 420 and the external network interface 450. In some implementations, the housing encloses at least a portion of the sensor 405.

[0090] Figure 4B 404. For example, STA 404 may be a reference Figure 1 The example implementation of STA 104 is described. STA 404 includes a wireless communication device 415. For example, the wireless communication device 415 may be a reference Figure 3An example implementation of the wireless communication device 300 described. STA 404 also includes one or more antennas 425 coupled to the wireless communication device 415 to send and receive wireless communications. STA 404 additionally includes an application processor 435 coupled to the wireless communication device 415 and a memory 445 coupled to the application processor 435. In some implementations, STA 404 also includes a user interface (UI) 455 (such as a touch screen or keyboard) and a display 465, which can be integrated with UI 455 to form a touch screen display. In some implementations, STA 404 can also include one or more sensors 475, such as one or more inertial sensors, accelerometers, temperature sensors, pressure sensors, or altitude sensors. For example, STA 404 can include a GPS receiver or other suitable GNSS receiver. Multiple components of the above components can communicate directly or indirectly with other components of the components through at least one bus. STA 404 also includes a housing that contains the wireless communication device 415, the application processor 435, the memory 445, and at least a portion of the antenna 425, the UI 455, and the display 465.

[0091] Figure 4C A block diagram of an example network entity 406 is shown. For example, the network entity 406 may be a reference Figure 2 The network entity 406 includes a wireless communication device (WCD) 416. For example, the wireless communication device 416 may be a wireless communication device (WCD) 416. Figure 3An example implementation of the wireless communication device 300 described. The network entity 406 also includes a plurality of antennas 426 coupled to the wireless communication device 416 to send and receive wireless communications. In some implementations, the network entity 406 additionally includes an application processor 436 coupled to the wireless communication device 416 and a memory 446 coupled to the application processor 436. The network entity 406 also includes at least one network interface 456 that enables the network entity 406 to communicate with a core network (such as via an RCN). For example, the network interface 456 may include one or both of a wired (e.g., Ethernet or fiber) network interface. In some implementations, the network interface 456 is configured to communicate with the core network via the RCN, and the wireless communication device 416 (in combination with the antenna 426) is configured to communicate with a UE that is communicatively coupled to the network entity 406. In some other implementations, the wireless communication device 416 (in combination with the antenna 426) is configured to communicate with both the core network and the UE. Multiple of the above components may communicate directly or indirectly with other of the components via at least one bus. The network entity 406 also includes a housing that houses the wireless communication device 416 , the application processor 436 , the memory 446 , and at least portions of the antenna 426 and the network interface 456 .

[0092] Figure 5 Schematic diagram 500 is shown of a wireless communication device 502 traveling through an area 508 for which a transmit power of the wireless communication device 502 is to be determined. In some implementations, the wireless communication device 502 can be an example of the wireless communication device 300. The wireless communication device 502 can be, or can be included in, an AP 402 or a STA 404. The wireless communication device 502 is referred to herein simply as the device 502.

[0093] Device 502 (such as an AP serving a STA of a WLAN or a STA being served by an AP of a WLAN) is depicted as being included in a high-speed train 504, which may be an example implementation of the high-speed train 202. For example, device 502 may be an AP installed in the high-speed train 504 to provide Internet access to passengers. In another example, device 502 may be a STA implemented as a soft AP (SAP) to serve other devices of one or more passengers. In another example, device 502 is a STA served by an AP installed in the high-speed train 504 or by a SAP in the high-speed train 504. The high-speed train 504 travels along a path 506 including one or more tracks. If device 502 is in a vehicle other than the high-speed train 504 (such as a car, bus, etc.), path 506 may include one or more roads or suitable paths for the vehicle to travel. Note that device 502 may travel in any suitable manner that may not be predefined by the path (such as traveling by a drone, by an off-road vehicle, or by other vehicles that do not use a predefined path). Thus, a path of a device may refer to any suitable trajectory of the device, which may be known before the device travels the path or may be known only after the device travels the path.

[0094] Path 506 is depicted as winding through coverage area 508, which includes multiple network entities 510 with coverage areas 512. Unshaded coverage areas indicate those coverage areas that do not include or are otherwise associated with communication devices or paths that require device 502 to transmit at a transmit power lower than the SP. Thus, device 502 is allowed to transmit at the SP while traveling through those areas. Associated (such as associated with network entity 510') shaded coverage areas indicate those coverage areas that include or are otherwise associated with communication devices or paths that require device 502 to transmit at a transmit power lower than the SP. For example, the first shaded coverage area through which path 506 enters may include a microwave tower that requires all devices near the tower to transmit at the LPI.

[0095] Typically, when the high-speed train 504 travels along the path 506, the device 502 sends an AFC request to identify what transmit power is available for 6 GHz communications. For example, the AP or STA may identify that it has moved 500 meters (such as via a GPS receiver or based on a location indicated by a STA communicating with the AP) or a maximum amount of time has passed, and sends an AFC request to a network entity of the cellular network (such as by the AP for the STA) so that the AFC server generates an AFC response that is communicated back to the AP or STA to indicate the allowed transmit power for the AP's or STA's location. Therefore, each time the device 502 travels along the path 506, the device 502 sends multiple AFC requests.

[0096] Because licensed devices and other known devices for 6 GHz communications (such as devices communicating in unlicensed portions of the spectrum) (and their corresponding coverage areas affected by such communications) may have static, defined locations, if the devices frequently travel along the same path, AFC requests may be repeatedly sent for the same location and, therefore, result in the same AFC response from the AFC server. As multiple devices sending AFC requests travel in the same area, the increased number of AFC requests may put a strain on the processing resources of a cellular network (such as a network entity) or an AFC server. Therefore, various specific implementations described herein are about learning the movement patterns of devices in order to reduce the number of AFC requests required to set the required transmit power of the device for 6 GHz communications. Figures 6 to 9 The invention relates to using AFC requests to identify required transmit powers for multiple nearest neighbors at different locations. The identified locations and required transmit powers of the nearest neighbors received over time can be used to track the movement of the device so that the transmit power can be set without sending an AFC request from an AFC server for a location previously queried by the device. Figures 10 to 22 It is about initially limiting the sending of AFC requests to AFC events (such as crossings between defined location areas, handovers between network entities, or expiration of a timer counting a predefined time between AFC requests). AFC responses received over time can be used to identify previously travelled locations and the required transmit power to be used for such locations without requiring the transmission of additional AFC requests.

[0097] Notice, Figure 5 Depicting the required transmit power divided according to the coverage area of ​​the network entity is merely for the purpose of clearly explaining various aspects of the present disclosure. For example, the coverage area of ​​the network entity may include multiple permitted or known devices or location areas associated with such devices, such that multiple portions of the coverage area may be associated with one or more transmit power requirements that are lower than the SP, and other portions of the coverage area may be associated with allowable SPs. In another example, multiple coverage areas may be associated with location areas of permitted or known devices that require lower transmit power than the SP.

[0098] Figure 6 Schematic diagram 600 shows a wireless communication device 602 sending an AFC request for a nearest neighbor entity of the wireless communication device 602. The wireless communication device 602 may be Figure 56, and may be referred to simply as device 602. As depicted, device 602 is included in a high-speed train 604 (which may be an example implementation of high-speed train 504) traveling along a path 606 (which may be the same as path 506). At a location 608 along path 606, device 602 sends an AFC request. Return to Reference Figure 2 In some implementations, the device 202 sends an AFC request, which is received by the serving network entity 206. For example, an AP served by the network entity 206 can send the AFC request to the network entity 206. In another example, a STA communicatively coupled to an AP served by the network entity 206 can send an AFC request to the AP, which sends the AFC request to the network entity 206. The AFC request received by the network entity 206 is forwarded to the AFC server 226. The AFC server 226 processes the AFC request and generates an AFC response, which is sent to the device 202 (such as to the AP or to the STA through the AP) over the cellular network 200 and by the serving network entity 206.

[0099] In various implementations, each AFC request is associated with multiple entities at different locations for which an indication of the allowed transmit power for that location is requested. Figure 6 , each location 608 is associated with eight entities 610 that are adjacent to the location 608. As used herein, the nearest neighbor entity 610 may refer to one or more of the following: a nearest neighbor device on the 6 GHz wireless band (such as may be based on an indication issued by an AFC server), a location defined by the device 602, a serving cell, or another suitable object having a location different from the current location 608 of the device 602. If the nearest neighbor entity is a defined location, the location of the nearest neighbor entity is the defined location itself. If the nearest neighbor entity is a known device that is closest to the device 602 as determined by the AFC server 226, the location of the nearest neighbor entity is the location of the known device.

[0100] In some implementations, in order to be able to request transmit power indications associated with multiple entities (such as for multiple locations defined for device 602), the AFC request is modified to allow multiple entities to be indicated. For example, a typical AFC request includes a payload indicating the location of device 602 (such as the latitude and longitude of device 602). The AFC request may be modified so that the payload may indicate multiple locations (such as a string of latitude and longitude coordinates). In another example, device 602 may provide an AFC request indicating the location of device 602, and the AFC server 226 (or another network component) may translate the location of device 602 in the AFC request into multiple nearest neighboring locations to the indicated location. In another example, the AFC server 226 may identify the nearest neighboring device to the indicated location (such as within a defined distance from the indicated location). In some other implementations, device 602 may increase the number of AFC requests transmitted, wherein each entity 610 is associated with a separate AFC request, so that each AFC request includes a different location. To clearly explain aspects of the present disclosure, the following examples are about an AFC request indicating a plurality of locations neighboring a current location of an AP.

[0101] The number of nearest neighbor entities to be indicated by the AFC request may be defined at one or more of the device sending the AFC request, the AFC server, or one or more network components. For the examples provided herein, for any suitable integer K greater than or equal to one, the defined number of nearest neighbor entities is K nearest neighbor entities (KNN). K may be defined in any suitable manner, such as predefined by a manufacturer or based on a standard, defined based on vendor requirements, user defined or adjusted, and the like.

[0102] If the AFC request is modified to include the KNN or otherwise indicate the KNN to the device, the AFC server processing the AFC request is configured to be able to identify the KNN from the request and generate an AFC response including an AFC power level indication for each of the KNNs. If the AFC request includes the location of the device, the AFC server processing the AFC request is configured to be able to identify the KNN based on the indicated location and generate an AFC response including an AFC power level indication for each of the KNNs. The AFC power level indication is any suitable indicator of the transmit power allowed at the location corresponding to the associated nearest neighbor entity. In some specific implementations, the AFC power level indication is a binary indication (such as a bit in the AFC response) as to whether the SP transmit power is allowed. For example, a bit set to low or false may indicate that the SP is not allowed and the transmit power of the device nearby must be less than or equal to the LPI, and a bit set to high or true may indicate that the SP is allowed so that the transmit power of the device can be as high as the SP transmit power. In some other implementations, the AFC power level indication is a multi-bit indication indicating one of a plurality of different AFC power levels (such as a two-bit indicator indicating one of SP, LPI, or VLP). In some further implementations, the AFC power level indication indicates an actual maximum transmit power value.

[0103] In some implementations, the AFC response also includes a frequency indication of one or more frequencies that can be used. For example, the AFC response may include a frequency indication for each of the KNNs to indicate one or more frequencies that can be used for 6 GHz communications at a location associated with each of the KNNs. The frequency indication can be any suitable indication. For example, the frequency indication can be a multi-bit indication of which 20 MHz channels of the 6 GHz spectrum are allowed or not allowed. In some implementations, the frequency indication may indicate whether a different spectrum is to be used (such as whether to use 6 GHz or a specific spectrum greater than 6 GHz).

[0104] In some implementations, the AFC response includes a VendorExtension object to indicate an AFC power level indication for KNN. For example, if K is eight, the VendorExtension object may include eight binary indicators, such as the binary indicators described above. In some implementations, the VendorExtension object also indicates the frequency of KNN (which may include one or more channels or other suitable frequency divisions). The VendorExtension object may be in any suitable format as defined at the AFC server and receiving device. For example, the VendorExtension object may be standard or proprietary and configured to meet the needs of the vendor. The format of the VendorExtension object may vary based on a specific vendor (the object is modified to meet each specific need of the vendor's specific needs). In some implementations, the VendorExtension object includes an extensionID field indicating one or more of the field types of the payload extended by the vendor or a specific vendor. For example, the extensionID field may be in the preamble of the VendorExtension object. Thus, a device receiving an AFC response may process the preamble (including the extensionID field) and identify the vendor or the format of the VendorExtension object based on the indication of the vendor in the extensionID field. Based on the known format of the VendorExtension object for the vendor, the receiving device is able to successfully parse the remainder of the VendorExtension object. In some implementations, the VendorExtension object also includes a parameter field that contains a payload as defined by the known format of the specific VendorExtension object. If the extensionID field indicates a field type for the payload, the parameter field has the indicated field type, and processing the parameter field may be based on the specific field type. For example, the field type may define the number of bits in the parameter field, and with respect to how the AFC power level indication is included in the parameter field, based on the known format of the bits for the specific field type (or based on the specific vendor), the receiving device is able to parse the parameter field to obtain the AFC power level indication. For example, the parameter field may include eight binary indicators of AFC power levels of KNN (where K equals eight) arranged in a specific format based on the field type of the parameter field or one or more of the specific vendors of the VendorExtension object (or other suitable indicators). Processing the VendorExtension object includes processing the parameter field to obtain one or more AFC power level indications included in the parameter field.If the parameter field also includes a frequency indicator, the receiving device can parse the parameter field to obtain the frequency indicator. In this way, processing the VendorExtension object can also include processing the parameter field to obtain one or more frequency indicators included in the parameter field. Any JavaScript Object Notation (JSON) primitive or structure data type can be used to define the various parts of the VendorExtension object (such as the parameter field).

[0105] After a receiving device (such as an AP or STA) processes the AFC response to identify the transmit power allowed for one or more nearest neighbor entities (such as obtaining one or more AFC power level indications included in the parameter field of the VendorExtension object of the AFC response), the receiving device may store the one or more AFC power level indications for the transmit power allowed for the one or more nearest neighbor entities (such as in a memory of the wireless communication device 300, in a memory 440 of the AP 402, or in another suitable storage device of the device receiving the AFC response). If the receiving device also identifies the frequencies allowed for the one or more nearest neighbor entities (such as obtaining one or more frequency indicators included in the parameter field of the VendorExtension object of the AFC response), the receiving device may store the one or more frequency indicators. In some specific implementations, the one or more AFC power level indications (and optionally, the one or more frequency indicators) are stored in a table. The table may identify the one or more nearest neighbor entities, the location of each of the one or more nearest neighbor entities, and the AFC power level indications for the one or more nearest neighbor entities. If the entity is a location (such as may be indicated by latitude and longitude), the table may store a label for distinguishing the location from other locations (such as "location 1", "location 2", "location 3", etc. in a simplified example), a location associated with the label (such as latitude and longitude), and the transmit power allowed at the location (such as whether SP is allowed at the location). The table may be stored in any suitable manner. In some implementations, the table may be included in a relational database that can present information as a data set in a tabular form and can manipulate the data set using relational operators. Structured Query Language (SQL) may be used to query and maintain the database.

[0106] Table 1 below is a simplified example of a table storing ten AFC power level indications for ten different locations:

[0107]

[0108]

[0109] Table 1

[0110] In the example of Table 1, each row is associated with a different entity, which is a location. For each entity, the AFC power level indication is a binary indicator as to whether the SP is allowed to transmit power, and the location is indicated in latitude and longitude coordinates. Although not depicted in Table 1, the table may also include a frequency indicator, which may be an additional column of Table 1. For example, the additional column may indicate one or more specific 20 MHz channels allowed for each of the locations.

[0111] The table including the AFC power level indication may be updated and maintained in any suitable manner. In some implementations, each time an AFC power level indication associated with a new location is received, the AFC power level indication and the location may be stored in the table. In some implementations, obsolete entries (such as those that have existed in the table for a defined amount of time) may be removed from the table. Additionally or alternatively, entries may be removed from the table based on the amount of memory allocated for the table. For example, when the table runs out of allocated space, the oldest entry in the table may be removed. Alternatively, the least visited entry in the table may be removed. Although some examples are provided, the table may be maintained in any suitable manner based on any suitable parameters (such as defined by a vendor or manufacturer).

[0112] As new entries in the table are added over time, the device can use the table to identify the transmit power without using a new AFC request. For example, when to send an AFC request can be based on a countdown of time by a timer in the device. Once the timer reaches zero, the device can obtain its current location and compare its current location with the location stored in the table. If the current location is equal to one of the current locations, the AFC power level indication stored for the location in the table can be used to set the transmit power for the device. The current location equal to the stored location can refer to the current location within the tolerance of the stored location (such as within 100 meters or another suitable distance between the locations). When using the stored AFC power level indication, the device can prevent the AFC request from being sent. The timer can be reset and counted down again until the time when a new AFC request can be transmitted. Note that any suitable time can be used. For example, the timer can be set to a random value so that the time between AFC requests is random. If the device travels along the same route (such as in a high-speed train that travels repeatedly between two locations), the table stores the location and AFC power level indication along those routes, so that the possibility of matching the current location of the device with one of the stored locations in the table increases. In some implementations, if the table also includes a frequency indicator, the table can also be used to identify the frequency, and the device can set its transmission frequency.

[0113] A minimum number of AFC requests may be required (such as by government requirements, standards requirements, or vendor requirements). In some implementations, the device tracks one or more of the number of AFC requests sent within a certain period of time, the time interval between AFC requests, or the time since the last AFC request was sent. In this way, the device may send AFC requests to ensure that the required minimum number of AFC requests is sent even if the current location matches a stored location in the table.

[0114] As a supplement or alternative to the example in which the device identifies the transmit power to be used based on the matching position in the table, the device may learn mobility zones that may include devices associated with different transmit power requirements (such as different parts of the path of a high-speed train) based on the table entries. In this way, the device can learn specific zones associated with different power levels based on the entries in the table. For example, the device may cluster the entries in the table based on the location and similar AFC power level indications to generate geo-fences, thereby defining different zones. If the specific zones associated with different power levels are known, the device can switch the transmit power faster. For example, the device may track that it is entering the first zone requiring the use of LPI, and switch to the LPI transmit power without first requiring the transmission of the AFC request and the processing of the AFC response. Note that any suitable means for generating a mobility zone may be used, such as a clustering algorithm or a machine learning model trained to generate a mobility zone. The mobility zone may be updated based on any new entry of the table for a new AFC response received by the device.

[0115] In some other specific implementations of identifying the transmit power without using another AFC request, the device may be configured to predict the AFC power level indication for the location of the device based on the information in the table without sending the AFC request. For example, the location and AFC power level indication from the past AFC response can be used to train a machine learning model (or another suitable model), and the machine learning model is stored in the table to predict the AFC power level indication for the current location of the device. The machine learning model can be based on, for example, a decision tree, a random forest, a logistic regression, a nearest neighbor, a classification tree, a control flow graph, a support vector machine, a naive Bayes, a Bayesian network, a value set, a hidden Markov model, or one or more of a neural network configured to predict an AFC power level indication (or another suitable indication of the transmit power to be used). For example, a logistic regression model can be trained using the location and AFC power level indication in the table. Then, the trained logistic regression model can be used to predict the AFC power level indication for the current location of the device. After adding multiple new entries to the table, the logistic regression model can be updated or retrained based on the new entries in the table. In another example, the logistic regression model may be a statistical model for predicting the transmit power based on the position in the table and the AFC power level indication. As used herein, a logistic regression model may refer to a machine learning model or a statistical model.

[0116] If the table includes a frequency indicator, any of the above examples of identifying the transmit power can also be used to identify the transmit frequency. For example, the transmit frequency can be based on a frequency indicator for a stored location in the table that matches the current location of the device. In another example, the transmit frequency can be based on a machine learning model, a statistical model, or another suitable model trained to predict the transmit frequency.

[0117] Any of the device components for identifying the AFC power level indication or the transmit power of the device without sending another AFC request may be implemented in the device in hardware, software, or a combination of both. If the device also identifies the frequency to be used, any of the device components for identifying the transmit frequency without sending another AFC request may be implemented in the device in hardware, software, or a combination of both. For example, a clustering model for generating mobility zones, a machine learning model for predicting AFC power level indications, or logic for matching a current location with a stored location in a table may be embodied in software stored in the memory 440 of the AP 402, the memory 308 of the wireless communication device 300, or another suitable device storage device and executed by the application processor 430 of the AP 402, the processor 306 of the wireless communication device 300, or another suitable device processor.

[0118] In the above example, the device sends a first number of AFC requests during a first instance of travel (e.g., travel along a path of a train or car or along another suitable track). The device then sends a second number of AFC requests that are less than the first number of AFC requests during one or more consecutive instances after the first instance of travel (e.g., travel along the same path as the first instance or travel near the location of the path of the first instance). As described above, the second number of AFC requests is based at least in part on setting the transmit power to one of the one or more AFC power level indications stored by the device independently of sending another AFC request. For example, a first number of AFC requests may be sent when traveling the path for the first time, and a second, smaller number of AFC requests may be sent when traveling the path (or a similarly located path) for the second, eighth, or later time. In this way, the number of AFC requests and responses decreases over time. As used herein, multiple instances of devices traveling along a path may refer to devices traveling along the same path (e.g., in a train or car following the same path), or may refer to devices traveling along one or more paths with similar locations (e.g., traveling along a street parallel to the original path in a city, traveling off-road near a road on the original path, traveling along a road adjacent to a train track on the original path, etc.).

[0119] To prevent errors caused by the sparsity of the data, the device may be configured to send AFC requests and process the associated AFC responses for an initial amount of time until the table includes a sufficient number of entries. For example, if a high-speed train travels between two locations five times a day, an AP or STA in the high-speed train may be configured to send AFC requests for 48 hours without reference to whether its current location matches the stored location in the table. In this way, the high-speed train traverses the same path ten times (the AP or STA sends AFC requests, receives AFC responses, and fills entries into the table including AFC power levels) before the AP or STA attempts to reduce the number of AFC requests sent during the train's crossing between locations. The initial amount of time can be any suitable amount of time, which can be defined by the manufacturer, supplier, adjusted by the user, and the like.

[0120] Figure 7 A flowchart illustrating example operations 700 for wireless communication for supporting an AFC request for a nearest neighbor entity of a wireless communication device to control the transmit power of the wireless communication device according to some implementations is shown. Operations 700 may be performed by any suitable device (such as the one described above with reference to FIG. Figure 3 In some examples, operations 700 may be performed by a device operating as or within an AP, such as a wireless communication device 300. Figure 1 AP 102 Figure 3The wireless communication device 300 or Figure 4A In some other examples, operation 700 may be performed by, for example, Figure 4B The STA 404 may be executed by another suitable device, which may be a SAP (the SAP may also be referred to as an AP) or may be served by an AP.

[0121] At 702, the device sends an AFC request. For example, the AP may send an AFC request to a network entity serving the AP. In another example, the STA may send an AFC request to the AP, and the AP may send an AFC request to the network entity. In some specific implementations, the AFC request includes the current location of the device and one or more locations adjacent to the current location (such as KNN for any suitable integer K). In this way, the AFC server that receives the AFC request through the network entity identifies the transmission power allowed for each location in the indicated location. The device may determine K adjacent locations based on a circle, an ellipse, a polygon, or another defined shape surrounding the current location or otherwise associated with the current location. For example, the current location may be the center of a circle of a defined size, and the adjacent entity is defined as a specific location on the perimeter of the circle (such as defined as an offset from the current location in latitude and longitude). In some other specific implementations, the AFC request may be a typical AFC request including the current location of the device. The AFC server processing the request may be configured to generate K neighboring locations based on the current location (such as similar to that described above), and generate K AFC power level indications for the K neighboring locations (as well as the AFC power level indication for the current location of the device). For the above specific implementation, the AFC response may be the same by including the K AFC power level indications for the K neighboring locations. For example, the legacy portion of the AFC response may include the AFC power level indication for the current location of the device, and the VendorExtension object of the AFC response may include the K AFC power level indications for the K neighboring locations.

[0122] At 704, the device receives an AFC response, which includes an AFC power level indication for one or more nearest neighbor entities of the device. For example, the AFC response travels to the device (such as traveling to the AP or traveling to the STA through the core network, RNC, and the service network entity of the cellular network). As described above, in some specific implementations, the AFC response includes a VendorExtension object to include an AFC power level indication for one or more nearest neighbor entities (such as one or more defined locations adjacent to the current location of the device). Also as described above, in some specific implementations, one or more AFC power level indications may be stored in a table identifying one or more nearest neighbor entities, the location of each nearest neighbor entity in one or more nearest neighbor entities, and the AFC power level indication for one or more nearest neighbor entities. Also as described above, in some specific implementations, the AFC power level indication is a binary indication of whether the SP is allowed to transmit power. Alternatively, the AFC power level indication may indicate a transmit power of three or more different transmit powers, or a specific transmit power value.

[0123] At 706, the device sets the transmit power of the device based at least in part on the AFC power level indication of at least one of the one or more nearest neighbor entities. For example, over time, the device obtains the AFC power level indication and the associated position in the AFC response, and stores the AFC power level indication and the position in the table. As the density of the AFC power level indication across the position increases, the device may generate a mobility zone to indicate the zone (such as whether SP is allowed) that allows a specific maximum transmit power. In this way, when the device crosses into the zone, the device may set its transmit power to the maximum transmit power associated with the zone. For example, when traveling in and out of different mobility zones, the device may alternate between SP and LPI. In another example, the device may determine that its current position matches the position stored in the table (the position is associated with the previously sent AFC request), and the device may set its transmit power to the maximum transmit power indicated by the AFC power level indication for the matching position stored in the table. At 708, the device transmits at the transmit power. For example, an AP in a high-speed train may set the transmit power of the AP to the LPI based on a previously received AFC power level indication stored in a table at the AP, and the AP may transmit to one or more STAs of the BSS of the AP in the 6 GHz band using the set transmit power. When using the previously received AFC power level indication to set the transmit power, the device may reduce the number of AFC requests sent over time.

[0124] In some implementations, the AFC response may also include a frequency indicator for indicating one or more permissible frequencies. For example, the frequency indicator may indicate one or more channels to be used, or the frequency indicator may indicate a specific frequency band to be used. The device may also store the frequency indicator in a table. Over time, the device obtains the frequency indicator and the associated position in the AFC response, and stores the frequency indicator and the position in the table. For example, the table may include an additional column for storing frequency indicators associated with the position. As the density of frequency indicators across the position increases, the computable mobility zone may also indicate the frequency to be used for transmission. In another example, the device may match the stored position with the current position and use the frequency indicated in the table for the stored position.

[0125] Figure 8 A flow chart illustrating example operations 800 for wireless communication supporting AFC requests for nearest neighbor entities of a wireless communication device to control transmit power of the wireless communication device according to some implementations is shown. Operation 800 may be in addition to operation 700. Operation 800 indicates that the number of AFC requests sent decreases over time.

[0126] For example, at 802, the device sends a first number of AFC requests during a first instance of traveling along a path. At 804, the device sends a second number of AFC requests less than the first number of AFC requests during one or more consecutive instances after the first instance of traveling along the path. The second number of AFC requests is based at least in part on an AFC power level indication of a neighboring entity in one or more nearest neighboring entities that is set to transmit power independently of sending another AFC request. For example, if the current position matches the stored position in the table, the device sets the transmit power to the power level indicated by the associated AFC power level indication stored in the table. In another example, if the current position indicates that the device is moving into or out of a mobility zone associated with a specific transmit power, the device sets the transmit power to as specified. In both examples, the transmit power is set without requiring another AFC request. In this way, the number of AFC requests decreases over time.

[0127] Fig. 9A flowchart illustrating an example operation 900 of wireless communication for supporting an AFC request for a nearest neighbor entity of a wireless communication device to control the transmit power of the wireless communication device according to some specific implementations is shown. Operation 900 may be in addition to operations 700 and 800. Operation 900 indicates that a minimum number of AFC requests may be required to be sent. For example, at 902, the device sets the number of AFC requests to the minimum value required for performing AFC. In some specific implementations, the number of AFC requests sent may decrease over time (such as described herein) until the number of AFC requests reaches the required minimum number. A government agency, a standard, a supplier, or another suitable entity may indicate the required minimum number of AFC requests to be sent within a certain period of time in order to perform AFC. The minimum number can ensure that the device (such as before launching a new device for communication in the 6 GHz wireless band) does not use stale or erroneous data to cause interference or other problems. In this way, although the number of AFC requests can be reduced, in order to perform AFC, AFC requests cannot be completely eliminated. Note that if there is any conflict between the AFC power level indication in the new AFC response and the AFC power level indication stored in the table, the table may be updated with the received AFC power level indication.

[0128] In the example implementations above with respect to nearest neighbor entities, the reduction in the number of AFC requests is based on the implementation of a modified AFC response that includes an AFC power level indication for one or more neighboring locations of the device's current location. Based on the use of such AFC responses, over time, the device is able to reduce the number of AFC requests sent. In some other implementations, the reduction in the number of AFC requests may be associated with basing the sending of AFC requests on being triggered by the occurrence of specific AFC events, which are associated with when the AFC requests will be sent. The reduction in the number of AFC requests may be further associated with learning the location patterns of the device over time in order to identify when to switch the transmit power (and optionally, the transmit frequency).

[0129] In some implementations, the AFC event includes a device crossing a cellular-based location boundary. A cellular-based location boundary is a boundary of a location area defined within the coverage area of ​​a cellular network. For example, a network entity transmits on one or more frequencies, and a cell may refer to a geographical area covered by the frequencies transmitted by the network entity. Therefore, a network entity may be associated with one or more cells. In some implementations, a cellular-based location area is a geographical area of ​​a cell, wherein the geographical boundaries of a cell are based on the location boundaries of the cell. A device (which may be a UE (such as an AP) or a network entity) may monitor communications between the UE and the network entity to identify when the UE crosses between cells (such as based on changes in the frequency used for communication), and an AFC request may be sent based on the UE crossing between cells.

[0130] Fig.10 Schematic diagram 1000 shows a wireless communication device 1002 sending an AFC request based on crossing a defined location area. The wireless communication device 1002 may be Figure 5 1002 is an example implementation of a wireless communication device 502 in , and may be referred to as device 1002 for short. As depicted, device 1002 is included in a high-speed train 1004 (which may be an example implementation of high-speed train 504) traveling along a path 1006 (which may be the same as path 506). At locations 1026-1042 along path 1006, device 1002 sends an AFC request. Device 1002 sends an AFC request to a network entity (such as network entity 1008, 1014, or 1020). For example, if device 1002 is an AP, the AP sends an AFC request to the network entity currently serving the AP. If device 1002 is a STA, the STA sends an AFC request to the AP, and the AP sends an AFC request to the network entity currently serving the AP. The AFC request received by the network entity is forwarded to an AFC server. The AFC server processes the AFC request and generates an AFC response, which is sent to device 1002 by the serving network entity through a cellular network.

[0131] As depicted, each network entity is associated with two location areas. For example, network entity 1008 is associated with location area 1010 and location area 1012, network entity 1014 is associated with location area 1016 and location area 1018, and network entity 1020 is associated with location area 1022 and location area 1022. Although two location areas are depicted for each network entity for clarity, each network entity may be associated with any number of location areas, such as one or three or more location areas. In addition, although the location areas are depicted as concentric circles around the network entities, the location areas may be any suitable shape. For example, the concentric circles may indicate that communications from the network entity for a particular frequency are omnidirectional, and the smaller concentric circles may indicate that a higher frequency is being used, which may cover a smaller geographic area than the lower frequency associated with the larger concentric circles. In some other examples, the location areas may be ellipses or elongated areas based on, for example, the directivity of one or more antennas at the network entity.

[0132] The locations 1026-1042 along the path 1006 where the AFC requests are sent are locations associated with cellular-based location boundaries. For example, the location 1026 is associated with the device 1002 entering the location area 1012, the location 1028 is associated with the device 1002 entering the location area 1010, and the location 1030 is associated with the device 1002 leaving the location area 1010. Once the device 1002 enters the location area 1012, the network entity 1008 can communicate with the device 1002 on the frequency associated with the location area 1012. Thus, the crossing into the location area 1012 can be identified based on the frequency of communication between the network entity 1008 and the device 1002. Once the device 1002 enters the location area 1010, the network entity 1008 can switch from communicating with the device 1002 on the frequency associated with the location area 1012 to the frequency associated with the location area 1010. Thus, crossing into location area 1010 may be identified based on a switch in communication frequencies between network entity 1008 and device 1002. Once device 1002 leaves location area 1010, network entity 1008 may switch from communicating with device 1002 on frequencies associated with location area 1010 back to frequencies associated with location area 1012. Thus, leaving location area 1010 may be identified based on a switch in communication frequencies between network entity 1008 and device 1002.

[0133] The location 1032 may be associated with a switch between a network entity 1008 serving the device 1002 and a network entity 1014 serving the device 1002. As used herein, a network entity serving a device refers to a network entity serving an AP, and the device may be the AP itself or a STA communicatively coupled to the AP (such as as part of a BSS of the AP). The frequency used to communicate with the device 1002 may change, so that the device 1002 may be considered to have entered a location area 1018 associated with the current serving network entity 1014, or to have left a location area 1012 associated with the previous serving network entity 1008. Similar to what is described above with reference to locations 1028, 1030, and 1032, location 1034 may be associated with device 1002 entering location area 1016, location 1036 may be associated with device 1002 leaving location area 1016, location 1038 may be associated with device 1002 entering location area 1024 or leaving location area 1018 (such as based on a switch between network entities 1014 and 1020), location 1040 may be associated with device 1002 entering location area 1022, and location 1042 may be associated with device 1002 leaving location area 1022.

[0134] Each AFC request sent at location 1026-1042 may be a typical AFC request indicating the location of device 1002, and each AFC response may be a typical AFC response including an AFC power level indication for the location of device 1002. Information from the AFC responses may be stored in a table (such as similar to example Table 1 above), and the information stored in the table (such as the stored locations and AFC power level indications, and optionally, frequency indicators) may be used to learn location patterns of device 1002 (which may include when or where to switch transmit power for transmissions in the 6 GHz wireless band, and optionally, frequencies to be used in the 6 GHz wireless band). For example, a machine learning model (or another suitable model) may be trained using locations and AFC power level indications from past AFC responses and stored in a table to learn location patterns of device 1002. The machine learning model may be based on, for example, one or more of a decision tree, a random forest, a logistic regression, a nearest neighbor, a classification tree, a control flow graph, a support vector machine, a naive Bayes, a Bayesian network, a value set, a hidden Markov model, or a neural network. For example, the locations and AFC power level indications in the table may be used to train a logistic regression model to learn the location patterns of the devices 1002. In another example, the logistic regression model may be a statistical model for indicating location patterns of the devices.

[0135] In addition or alternatively to an AFC event that includes a device (such as an AP) crossing a cellular-based location boundary, in some specific implementations, the AFC event includes a handover of the device between network entities. In some examples, in order to determine when to send an AFC request, communications between the device and the network entity may be observed (such as when a serving base station identification code (BSIC) changes). In some other examples, the device may be able to indicate its location, where the coverage area of ​​the network entity is known. The location of a device (such as an AP or STA) that crosses between coverage areas may be observed to determine when to send an AFC request. Based on the handover from the current network entity to the new network entity for serving the device being identified based on the communications between the device and the network entity, an AFC request may be generated and sent for the current location of the device.

[0136] Fig.11 Schematic diagram 1100 shows a wireless communication device 1102 sending an AFC request based on a handoff between network entities. The wireless communication device 1102 may be Figure 5 1102 is an example implementation of a wireless communication device 502 in , and may be referred to as device 1102 for short. For example, as described above, device 1102 may be an AP, or device 1102 may be a STA communicatively coupled to an AP. As depicted, device 1102 is included in a high-speed train 1104 (which may be an example implementation of high-speed train 504) traveling along a path 1106 (which may be the same as path 506). At locations 1126-1130 along path 1106, device 1102 sends an AFC request. Device 1102 sends an AFC request to a network entity (such as network entity 1108, 1114, or 1120) currently serving device 1102, such as an AP that sends an AFC request to the network entity or a STA that sends an AFC request to the AP, which sends the AFC request to the network entity. The AFC request received by the network entity is forwarded to an AFC server. The AFC server processes the AFC request and generates an AFC response, which is sent to the device 1102 through the cellular network and by the serving network entity.

[0137] As depicted, network entity 1108 has coverage area 1112, network entity 1114 has coverage area 1118, and network entity 1120 has coverage area 1124. Location 1126 along path 1106 is associated with device 1102 (such as based on information from Fig.111102 begins being served by network entity 1108 (not depicted in the handover of a previously serving network entity). Location 1128 along path 1106 is associated with a handover of device 1102 from network entity 1108 to network entity 1114, and location 1130 along path 1106 is associated with a handover of device 1102 from network entity 1114 to network entity 1120. The AFC requests sent at locations 1126-1130 may be typical AFC requests that include the current location of device 1102, and the AFC responses may be typical AFC responses that include an AFC power level indication for the location of device 1102. Similar to the above reference to FIG. Fig.10 As described, information from the AFC responses may be stored in a table (such as similar to example Table 1 above), and the information stored in the table (such as stored location and AFC power level indications, and optionally, frequency indicators) may be used to learn the location pattern of device 1102 (which location pattern may include when or where to switch transmit power for transmissions in the 6 GHz wireless band, and optionally, frequencies to be used in the 6 GHz wireless band).

[0138] As a supplement or alternative to an AFC event including a device crossing a cellular-based location boundary or including a handover of a device between network entities, in some specific implementations, the AFC event includes an AFC association timer indicating that an AFC request will be transmitted. For example, AP 402 may include a timer to count the amount of time until the next AFC request is generated. In another example, STA 404 may include a timer to count the amount of time until the next AFC request is generated. The timer may be set to count any suitable amount of time. For example, the timer may be set to a random amount of time defined by a maximum amount of time and a minimum amount of time. In another example, the timer may be set to a predefined amount of time that is the same for each instance. In yet another example, the timer may be set to a predefined amount of time plus or minus a random difference, so that the actual amount of time counted by the timer may be different. When the timer counts down to zero, the AFC request may be sent, and the timer may be reset to the amount of time to be counted before the next AFC request is sent. The advantage of using a timer is that if the cell-based location area is unknown or particularly large, or if the coverage area of ​​the network entity is particularly large so that an AFC request is not sent for an unexpected amount of time, using a timer to indicate when to send an AFC request allows the AFC request to still be sent.

[0139] Fig.12 Schematic diagram 1200 shows a wireless communication device 1202 sending AFC requests at regular intervals. The wireless communication device 1202 may be Figure 51202 . An example implementation of a wireless communication device 502 in , and may be referred to as device 1202 for short. For example, as described above, device 1202 may be an AP or may be a STA communicatively coupled to an AP. As depicted, device 1202 is included in a high-speed train 1204 (which may be an example implementation of high-speed train 504) traveling along a path 1206 (which may be the same as path 506). At locations 1226-1242 along path 1206, device 1202 sends an AFC request. Device 1202 sends an AFC request to a network entity currently serving the network entity of device 1202. The AFC request received by the network entity is forwarded to an AFC server. The AFC server processes the AFC request and generates an AFC response, which is sent to device 1202 by the serving network entity through a cellular network.

[0140] Positions 1226-1242 along path 1206 are associated with timers indicating that an AFC request is to be sent. In this example, the timer can be configured to count x number of minutes of any suitable integer x, which can be manufacturer-defined, vendor-defined, or user-defined or adjustable. In some implementations, the amount of time to count is based on a required minimum number of AFC requests to be sent within a certain time period or a required maximum amount of time between AFC requests (which can be defined by a standard, by a regulatory organization, or by a vendor).

[0141] Although in Fig.12 1202, the AFC requests sent at the locations 1226-1242 may be typical AFC requests including the current location of the device 1202, and the AFC responses may be typical AFC responses including an AFC power level indication for the location of the device 1202. Similar to the above reference 1202, the AFC requests sent at the locations 1226-1242 may be typical AFC requests including the current location of the device 1202, and the AFC responses may be typical AFC responses including an AFC power level indication for the location of the device 1202. Similar to the above reference 1202, the AFC requests sent at the locations 1226-1242 may be regular intervals between locations 1226-1242, but in some embodiments, the intervals between locations may be irregular. For example, if the same time is counted by the timer, the distance between the locations may change based on the high-speed train 1204 stopping or adjusting its speed based on track or weather conditions. In addition or alternatively, the timer may count different amounts of time. Fig.10 As described, information from the AFC responses may be stored in a table (such as similar to example Table 1 above), and the information stored in the table (such as stored location and AFC power level indications, and optionally, frequency indicators) may be used to learn the location pattern of device 1202 (which location pattern may include when or where to switch transmit power for transmissions in the 6 GHz wireless band, and optionally, frequencies to be used in the 6 GHz wireless band).

[0142] exist Figures 10 to 12In the figure, a traveling device (such as an AP in a high-speed train) is depicted as determining when to send an AFC request and sending the AFC request. The device also learns the location pattern of the device based on information stored in a table from received AFC responses. In some other specific implementations, the network entity may assist in sending an AFC request to an AFC server, determine the location pattern of the device, or otherwise be able to generate an AFC response to an AFC request from a device without sending an AFC request to an AFC server. For example, the network entity may identify when to send an AFC request to an AFC server of a device, generate an AFC request based on a tracking location of the device or a timer associated with the device, and send the AFC request to the AFC server. In the case where the network entity handles the sending of the AFC request to the AFC server, the device may not require modifications to the AFC. Therefore, the device may not send an AFC request, or may send an AFC request without any restrictions on location areas, switching, or timers. In this way, the number of AFC requests provided to the AFC server (which may be limited to the number of AFC requests that can be processed) may be reduced by the network entity to prevent the AFC server from being saturated as the number of devices sending AFC requests increases. In cellular network assisted AFC operation (such as the above reference Figures 10 to 12 In a specific implementation of the AFC operation performed by the device described above, the network entity may be configured to track the location of the device and the AFC power level indication included in the AFC response to the location of the device so that the AFC response can be generated without forwarding the AFC request from the device to the AFC server. For example, the network entity may store a table including the location of the device and the AFC power level indication from previously received AFC responses to the device, and the network entity may use a machine learning model (or another suitable model) to learn the location pattern of the device based on the information in the table. As described above, if the device manages the AFC operation, the AFC event may include one or more of the following: the device crosses a location boundary, the device switches between network entities, or the AFC association timer indicates that the AFC request is to be transmitted. In some specific implementations where the network entity assists in managing the AFC operation, the AFC event may include receiving an AFC request from the device (such as from an AP).

[0143] Fig.13 A sequence diagram depicting an example wireless communication 1300 that supports cellular network assistance in controlling transmit power of a wireless communication device according to some implementations is shown. The wireless communication 1300 may be performed between an AP 1310, a cellular network controller 1320, and an AFC server 1330. The AP 1310 may be Figure 4A An example implementation of AP402 (which may be Figure 2In some implementations, the AFC request may originate from a STA that is communicatively coupled to the AP 1310 (such as a STA that is part of the BSS of the AP), and the AP 1310 may forward the AFC request and response between the STA and the cellular network controller 1320. The AFC server 1330 may be Figure 2 The cellular network controller 1320 may be a cellular network (such as Figure 2 218 and any suitable component of the cellular network 200). For example, a location server that includes a location register 218 and implements LMF may be configured to assist in reducing the number of AFC requests forwarded to the AFC server 226. In another example, the network entity 206 may be configured to assist in reducing the number of AFC requests forwarded to the AFC server 226 for devices served by the network entity 206. In another example, a component of the core network separate from the location server may be configured to use the location register to track the locations of one or more devices and AFC power level indications received in an AFC response from the AFC server for one or more of those locations. In the following example, the cellular network controller 1320 is described as a location server that includes a location register to store a table that includes the locations of the APs 1310 and the AFC power level indications associated with one or more of those locations. Although not described in detail herein, the cellular network controller 1320 may be any suitable component of the cellular network 200 that includes a location register and implements LMF. Fig.13 , but the communication between AP 1310 and cellular network controller 1320 may be through one or more of a network entity, RNC, or one or more components of a core network. The communication between cellular network controller 1320 and AFC server 1330 may be through one or more core network components, one or more application servers, or one or more other components for communicatively coupling cellular network controller 1320 and AFC server 1330.

[0144] exist Fig.13In the example of , the AP 1310 sends one or more AFC requests to the cellular network controller 1320. In some implementations, the AFC request from the AP 1310 is based on the typical time that the AFC request is to be sent by the device for AFC (such as based on a standard or vendor). The cellular network controller 1320 can manage whether the AFC request will be forwarded to the AFC server 1330 to receive an AFC response. For the first depicted AFC request sent by the AP 1310 to the cellular network controller 1320, the cellular network controller 1320 identifies that an AFC response is required from the AFC server 1330 (the AFC response indicates the transmit power that can be used by the AP 1310 or the STA). For example, the cellular network controller 1320 can determine that the received AFC request is associated with an AFC event (and is configured to forward such AFC request). In another example, the cellular network controller 1320 may determine that the current location of the AP 1310 (or STA) indicated in the AFC request or otherwise known by the cellular network controller 1320 does not match any stored location in the table linking the AFC power level indication to the stored location. In another example, the table may not include enough entries to determine the location area associated with different cells. In another example, the table may not include enough entries to determine the location pattern of the AP 1310 (or STA). As described above, in some examples, determining the location area or determining the location pattern can be based on a machine learning model (or another suitable model) trained using the location and AFC power level indication from past AFC responses and stored in the table. After the location area or location pattern is known, the cellular network controller 1320 can predict the AFC power level indication and (optionally) the frequency indicator for the current location of the device.

[0145] The cellular network controller 1320 forwards the first AFC request received from the AP 1310 to the AFC server 1330. The AFC server 1330 processes the AFC request, generates an AFC response, and sends the AFC response to the cellular network controller 1320. The cellular network controller 1320 stores the AFC data in the AFC response. For example, the cellular network controller 1320 may store the location and associated AFC power level indication included in the AFC response in a table (such as a table similar to Table 1 above). Return to Reference Figure 2 , the location of the AP 1310 (or STA) may be stored in the location register 218, which may also store the associated AFC power level indication. In some implementations, the cellular network controller 1320 may also store the frequency indicator included in the AFC response. In the following examples, the device is described as being an AP 1310, but the device may be a STA that is communicatively coupled to the AP 1310 for performing the operations described in the following examples.

[0146] In some implementations, AP 1310 sends AP location updates to cellular network controller 1320. For example, AP 1310 may use a GPS receiver to identify the current location of the AP (such as in latitude and longitude) and periodically indicate the location of the AP to cellular network controller 1320. In another example, a location server implementing LMF may determine the location of AP 1310 using signal measurements of DL signals received at AP 1310 or UL signals received at a network entity. In this example, the AP location update may include signal measurements provided by AP 1310 or signals from AP 1310 to generate signal measurements at the network entity. In the event that cellular network controller 1320 receives periodic AP location updates, cellular network controller 1320 tracks the location of AP 1310. Return to reference Figure 2 , the location update of AP 1310 may be stored in location register 218.

[0147] Since the cellular network controller 1320 tracks the location of the AP 1310, the cellular network controller 1320 may be able to independently generate an AFC request including the location of the AP 1310. In some implementations, the cellular network controller 1320 sends the independently generated AFC request to the AFC server 1330, receives an AFC response from the AFC server 1330, and stores the AFC data included in the AFC response (such as an AFC power level indication associated with the location included in the AFC request sent to the AFC server). If the cellular network controller 1320 is able to independently generate the AFC request, the cellular network controller 1320 may send the AFC request at any suitable time. For example, the cellular network controller 1320 may identify when an AFC event occurs for the AP 1310 and send an AFC request for the AP 1310 based on the AFC event. In some implementations, the AFC event may include receiving an AFC request from the AP 1310. In some other specific implementations, the AFC event may include AP 1310 crossing a location boundary, AP 1310 switching between network entities, or an AFC associated timer indicating that an AFC request will be transmitted. In another example, if the data in the table for AP 1310 is sparse, the cellular network controller 1320 may use a timer to indicate when to periodically generate and send AFC requests based on the last known AP location in order to receive more AFC data for the table. In addition or alternatively, the cellular network controller 1320 may generate and send AFC requests for one or more devices based on the current load of the AFC server 1330. For example, the cellular network controller 1320 may manage forwarding AFC requests for all devices that are communicatively coupled to the cellular network. Based on the AFC request being forwarded, the cellular network controller 1320 is able to identify when the AFC server is processing fewer AFC requests and therefore has bandwidth for handling more AFC requests. Thus, the cellular network controller 1320 may generate and send AFC requests for devices whose current locations may require additional AFC power level indications, such as devices for any location area whose location pattern has not yet been determined, whose current location deviates from the location pattern, whose location area has not yet been determined, or whose current location is not included in the determined location area.

[0148] As described above, after the location area or location pattern is known, the cellular network controller 1320 can predict the AFC power level indication for the current location of the device. Therefore, the cellular network controller 1320 can receive an AFC request from the AP 1310, identify that an AFC response is not required, generate an AFC response without sending an AFC request to the AFC server 1330, and send the generated AFC response to the AP 1310. For example, the AFC request indicates the current location of the AP 1310. The cellular network controller 1320 identifies that the current location is in the determined location area associated with a specific transmit power, and the cellular network controller 1320 generates an AFC response and sends the AFC response to the AP 1310, the AFC response including an AFC power level indication indicating the transmit power associated with the location area.

[0149] In some implementations, the determined location areas and associated transmit power levels may be stored at a network entity serving the AP 1310. For example, the cellular network controller 1320 may mark each combination of a location area and a cell ID on the cellular network with an allowable transmit power based on an AFC response received from an AFC server. For example, each combination may be linked to one of the transmit power requirements including a required LPI, an allowed SP, a required VLP, or the transmit power may be flexible. In some implementations, one or more combinations may be associated with an unknown allowable transmit power (such as based on sparse AFC data for a location associated with the combination). The cellular network controller 1320 may mark different combinations over time as the allowable transmit power for these combinations is determined. The links between different combinations and the allowable transmit power are stored in a table. Each network entity of the cellular network may store a copy of the table, and the network entity may reference the table to generate an AFC response to an AFC request without forwarding the AFC request to the AFC server. In some implementations, the table may be updated or completed over time for different combinations as new AFC responses are received from the AFC server.If the AFC response includes a frequency indicator, the table may also include frequency indicators, such as for different combinations of location area and cell ID.

[0150] One benefit of network-assisted AFC is that the location and AFC power level indications and (optionally) frequency indicators associated with multiple devices can be used to identify the transmit power and (optionally) transmit frequency to be used by one device. In other words, the data used to identify the transmit power and frequency is not limited to the AFC data of that particular device. Therefore, while some of the examples above describe using the AFC data of one device to determine a mobility zone or other area, AFC data aggregated for multiple devices can be used to generate such zones or areas.

[0151] As described above in various specific implementations of sending an AFC request based on an AFC event, setting the transmit power and (optionally) transmit frequency of the device without requiring the AFC server to process the AFC request and send an AFC response can be based on the device tracking the AFC power level indication and (optionally) frequency indicator for different locations, or the network assisting in tracking the AFC power level indication and frequency indicator for different locations. For example, the AP or STA may determine its location mode, mobility zone, location area, etc. to identify the transmit power and transmit frequency to be used for its current location. In another example, the network component may determine the location mode, mobility zone, location area, etc. of the AP or STA to identify the transmit power and transmit frequency to be used by the AP or STA for the current location of the AP or STA. Figures 14 to 22 A flow chart illustrating example operations for wireless communications supporting AFC requests based on AFC events for controlling transmit power of a wireless communication device is shown.

[0152] Fig.14 A flowchart illustrating example operations 1400 for wireless communication for supporting AFC requests based on AFC events for controlling transmit power of a wireless communication device according to some implementations is shown. Operations 700 may be performed by any suitable device (such as the one described above with reference to Figure 3 In some examples, operations 700 may be performed by a device operating as or within an AP, such as a wireless communication device 300. Figure 1 AP 102 Figure 3 The wireless communication device 300 or Figure 4A In some other examples, operation 700 may be performed by, for example, Figure 4B The operation 1400 may be performed by another suitable device of the STA 404, which may be a SAP (the SAP may also be referred to as an AP) or may be served by an AP. In some other examples, the operation 1400 may be performed by a network controller, such as a Figure 4C 406, a location server, a core network component, or another suitable component of the cellular network.

[0153] For example, at 1402, the device sends an AFC request to a network component in a cellular network based at least in part on an AFC event. In some implementations, the AFC event includes one of the following: an AP (or STA) crosses a cellular-based location boundary, an AP switches between network entities, or an AFC association timer indicates that an AFC request will be transmitted. At 1404, the device receives an AFC response from a network component. For example, an AP may receive an AFC response from a network component from a network entity, which may be a network component or may be an intermediate device between a network component and an AP. If the STA sends an AFC request, the AP may forward the AFC response to the STA. At 1406, the device identifies a transmit power to be used by one of the AP or STA based on the AFC response. For example, an AFC power level indication included in the AFC response may indicate the maximum transmit power allowed for the current location of the AP or STA. At 1408, the device instructs one of the AP or STA to transmit using a specific transmit power level. In some implementations, the device also identifies a frequency to be used by the AP or STA based on the AFC response. For example, the AFC response may include a frequency indicator to indicate one or more channels in the 6 GHz spectrum to be used by the AP to transmit to the network entity. Thus, the device may also instruct the AP (or STA) to use a specific 6 GHz frequency for transmission.

[0154] If the device performing operation 1400 is included in an AP or a STA, an AFC request is transmitted to a network entity, and an AFC response is received from the network entity.

[0155] Fig.15 A flowchart illustrating example operations 1500 for wireless communication supporting AFC requests based on AFC events for controlling transmit power of a wireless communication device according to some implementations is shown. Operation 1500 may be complementary to operation 1400, and the device performing operations 1400 and 1500 may be an AP or a STA. Operation 1500 is about an AP or a STA determining a location pattern of the AP or the STA based on multiple AFC requests and AFC responses associated with multiple AFC events.

[0156] At 1502, the AP or STA obtains multiple locations of the AP or STA, wherein the AP or STA is associated with multiple AFC events during one or more instances of traveling. For example, if the AFC event includes a handover of the AP between network entities, the AP or STA sends an AFC request to the network entity whenever the handover occurs. The AFC request is provided to the AFC server, and the AFC server sends a response including an AFC power level indication for the location of the AP or STA. The AP or STA receives the AFC response, obtains the AFC power level indication from the AFC response, and stores the AFC power level indication and the associated AP or STA location in a table. When additional AFC events occur, the AP or STA sends additional AFC requests, receives additional AFC responses, and obtains the AFC power level indication from the AFC response. In some specific implementations, the AP or STA may obtain multiple locations indicating the location of the AP or STA from a sensor (such as a GPS receiver), wherein these locations are used to generate one or more AFC requests. In some other specific implementations, the AP or STA may obtain multiple locations from multiple received AFC responses. As time passes and the number of AFC events increases, the number of acquired AP or STA positions increases (such as the number of table entries increases).

[0157] At 1504, the AP or STA determines a position pattern of the AP or STA over time based at least in part on a plurality of positions of the AP or STA associated with a plurality of AFC events. As described above, in some implementations, any suitable machine learning model (or another suitable model) may be trained to determine a position pattern of the AP or STA based on the obtained AP or STA positions.

[0158] At 1506, the AP or STA sends a second number of AFC requests less than the first number to the network entity during consecutive instances following one or more instances of traveling, based at least in part on the location pattern. For example, the AP or STA may travel along the same path or a similar path during the consecutive instances of traveling as during the one or more instances of traveling, wherein the AP or STA sends a smaller number of AFC requests during the consecutive instances of traveling than during the previous instance of traveling. If the STA sends an AFC request, the AFC request may be sent to the AP that forwards the AP request to the network entity. The AP or STA sends a first number of AFC requests during one of the one or more instances of traveling (e.g., along the same or similar path). Thus, the AP or STA receives a first number of AFC responses during the instance of traveling, and obtains an AFC power level indication for the AP or STA location associated with the first number of AFC responses. The second number of AFC requests is based at least in part on setting the transmit power of the AP or STA to a transmit power associated with one of the multiple locations of the AP or STA and one of the multiple AFC events independently of sending another AFC request. For example, an AP or STA may use its location pattern and its current location to identify that the AP or STA is entering a mobility zone or location area that is associated with a transmit power that is different from the current transmit power of the AP or STA. The AP or STA may store a table indicating the mobility zones or location areas that the AP or STA may enter or leave, and the table may include the transmit power allowed for each of the zones or areas. The table may also indicate the frequency to be used for transmission in each of the zones or areas (e.g., the channel to be used for transmission in the 6 GHz wireless band). The AP or STA may use the table to identify its location as being in a particular zone or area, and to identify the transmit power and (optionally) transmit frequency to be used when in that zone or area. Return to reference Fig.14 If the device is an AP or a STA, instructing the AP or STA to use a specific transmit power level may include the AP or STA setting its transmit power to a transmit power level indicated in the table for a specific zone or region.

[0159] Return to reference Fig.14, if the device performing operation 1400 is included in a cellular network controller (such as a location server, a network entity, or another suitable core network component), the cellular network controller may receive one or more AFC requests from the AP and provide one or more AFC responses to the AP. In some specific implementations, the AFC event includes receiving an AFC request from the AP. The cellular network controller may send an AFC request to the AFC server, and the cellular network controller may receive an AFC response from the AFC server. If the cellular network controller sends an AFC request to the AFC server based on an AFC event in which the AP sends an AFC request to the cellular network controller, the cellular network controller may provide the AP with an AFC response received from the AFC server. As described above, the cellular network controller may obtain an AFC power level indication and other AFC data (such as a frequency indicator) to be stored at the cellular network controller in order to identify a location mode, mobility zone, location area, or other information that can be used to identify a transmit power and (optionally) a transmit frequency to be used by the AP or STA without requiring another AFC request to be sent to the AFC server.

[0160] Fig.16 A flowchart illustrating example operations 1600 for wireless communication supporting AFC requests based on AFC events for controlling transmit power of a wireless communication device according to some implementations is shown. Operation 1600 may be complementary to operation 1400, and the device performing operations 1400 and 1600 may be a cellular network controller. Operation 1600 is about the cellular network controller obtaining the locations of APs or STAs and the corresponding transmit powers associated with these locations.

[0161] At 1602, the cellular network controller obtains one or more locations of the AP or STA during one or more instances of the AP or STA traveling, the one or more locations being associated with one or more AFC events. For example, if the AFC event includes receiving an AFC request from an AP and the AP sends one or more AFC requests, the cellular network controller may send one or more AFC requests to an AFC server, receive one or more AFC responses from the AFC server, and obtain one or more locations of the AP or STA from the one or more AFC responses. In another example, the cellular network controller may obtain one or more locations of the AP or STA from one or more AFC requests from the AP indicating the current location of the AP or STA. In another example, the cellular network controller may obtain one or more locations of the AP or STA from one or more AP or STA location updates received for the AP (such as described above with reference to FIG. 1 ). Fig.13 described).

[0162] At 1604, the cellular network controller obtains a corresponding transmit power associated with each of the one or more locations. For example, the cellular network controller may obtain an AFC power level indication included in one or more AFC responses to one or more AFC requests sent by the cellular network controller to the AFC server. Based on the AFC power level indication corresponding to the AP or STA location, the cellular network controller may determine a transmit power to be used by the AP or STA for the AP or STA location. For example, if the AFC power level indication is a binary indicator as to whether SP is allowed at the corresponding location, the cellular network controller may identify whether the transmit power for the AP or STA at the corresponding AP or STA location is SP or LPI based on the binary indicator. Although Fig.16 Not depicted in FIG, but the cellular network controller may store the obtained transmit power and the obtained AP or STA position in a table or another suitable memory, such as described above. The cellular network controller may also send one or more AFC responses to the AP.

[0163] As more AP or STA locations and corresponding transmit powers are obtained by the cellular network controller, the cellular network controller may have stored enough AFC data to be able to generate an AFC response that instructs the AP or STA about the transmit power to be used without sending an AFC request to the AFC server. For example, the cellular network controller may match the AP or STA location from an AFC request received from the AP or STA with the stored location in the table, and the cellular network controller may be able to generate an AFC response to the AFC request based on the transmit power indicated in the table as corresponding to the location. In another example, the cellular network controller may determine that the AP or STA location from the AFC request is in a zone or region associated with a transmit power level, and the cellular network controller may generate an AFC response to the AFC request based on the transmit power level associated with the zone or region.

[0164] In some implementations, the AFC response may also include a frequency indicator. Thus, the cellular network controller may also obtain and store a frequency indicator corresponding to the AP or STA location. The cellular network controller may be able to generate an AFC response to include a frequency indicator based on one or more frequency indicators stored in a similar manner as described above with reference to the transmit power indicated in the table. The frequency indicator may indicate a transmit frequency to be used for transmission (e.g., a transmit frequency in the 6 GHz wireless band to be used by the AP to transmit to the network entity).

[0165] Fig.17A flowchart illustrating an example operation 1700 for wireless communication supporting an AFC request based on an AFC event for controlling the transmit power of a wireless communication device according to some implementations is shown. Operation 1700 may be complementary to operation 1400 and operation 1600, and the device performing operations 1400, 1600, and 1700 may be a cellular network controller. Operation 1700 is about the cellular network controller sending an AFC response to an AP without sending an AFC request to an AFC server.

[0166] At 1702, the cellular network controller receives another AFC request from the AP. At 1704, the cellular network controller obtains a first location of the AP or STA. For example, the AFC request may indicate a first location of the AP or STA, which may be resolved by the cellular network controller. In another example, the cellular network controller may track the location of the AP or STA (such as based on periodic AP or STA location updates from the AP or a network entity), and the cellular network controller may identify the first location of the AP or STA as the last tracked location of the AP or STA.

[0167] At 1706, the cellular network controller sends an AFC response to the AP independently of sending an AFC request to the AFC server. The AFC response indicates the current transmit power to be used by the AP, and the current transmit power is based at least in part on the first position of the AP or STA, one or more previously obtained positions of the AP or STA, and one or more corresponding transmit powers associated with the one or more previously obtained positions. For example, as described above, the cellular network controller may store indications of one or more positions of the AP or STA and indications of one or more corresponding transmit powers (obtainable from one or more AFC responses) in a table. The cellular network controller may then receive an AFC request indicating the first position of the AP or STA. The cellular network controller may compare the first position with the stored positions in the table. If a match is identified, the cellular network controller may generate and send an AFC response including an AFC power level indication indicating the corresponding transmit power associated with the matching position stored in the table. In another example, a table including combinations of location areas and cell IDs on a cellular network and permissible transmit power levels marked for each combination may be stored at the cellular network controller. The cellular network controller may identify that the first location belongs to one of the combinations, and may generate an AFC response and send the AFC response to the AP, wherein the AFC response includes an AFC power level indication indicating an allowable transmit power associated with the combination in the table. In some implementations, the table may be stored at a network entity that receives an AFC request including the first location from the AP, and the network entity sends the AFC response to the AP based on the table without forwarding the AFC request from the AP to the AFC server. In another example, a machine learning model (or another suitable model) trained using one or more AP or STA locations and one or more corresponding transmit powers may generate a transmit power to be indicated to the AP based on the first location of the AP or STA. In some implementations, the cellular network controller (such as a network entity) also includes a frequency indicator in the AFC response to indicate one or more transmit frequencies to be used (e.g., one or more channels in the 6 GHz wireless band to be used by the AP to transmit to the network entity).

[0168] In some embodiments, the cellular network controller may determine one or more of a location pattern of an AP or STA or an AFC request pattern from an AP, and the cellular network controller may use one or more patterns to identify a transmit power and (optionally) a transmit frequency to be indicated to the AP in response to the AFC request from the AP.

[0169] Fig.18A flowchart illustrating an example operation 1800 for wireless communication supporting AFC requests based on AFC events for controlling transmit power of a wireless communication device according to some implementations is shown. Operation 1800 may be complementary to operations 1400, 1600, and 1700, and the device performing operations 1400, 1600, 1700, and 1800 may be a cellular network controller. Operation 1800 is about the cellular network controller determining a location pattern or an AFC request pattern of an AP or a STA so as to be able to identify a transmit power to be indicated in an AFC response without sending an AFC request to an AFC server, and thus reducing the number of AFC requests transmitted to the AFC server.

[0170] At 1802, the cellular network controller sends a first number of AFC requests to an AFC server during a first instance of AP or STA travel, the first number of AFC requests being associated with the AP or STA. At 1804, the cellular network controller determines one or more of the following: a location pattern of the AP or STA over time based at least in part on one or more locations of the AP or STA, or an AFC request pattern of the AP over time based at least in part on one or more AFC requests received from the AP. For example, the AFC request pattern may indicate a specific time or a specific location at which the AP sends the AFC request. At 1806, the cellular network controller sends a second number of AFC requests less than the first number of AFC requests to the AFC server during one or more consecutive instances after the first instance of AP or STA travel. In some examples, the one or more consecutive instances of travel may be along the same path as the first instance of travel, or may be along a path similarly positioned to the first instance of travel. The second number of AFC requests is based at least in part on sending one or more AFC responses to the AP, the one or more AFC responses indicating a transmit power to be used by the AP or STA based at least in part on one or more of the location pattern or the AFC request pattern. The one or more AFC responses sent to the AP are sent independently of sending another AFC request to the AFC server. Thus, the AP sends one or more AFC requests to the cellular network controller, and the cellular network controller is able to generate an AFC response for each AFC request in the one or more AFC requests based on previously received AFC data for generating one or more of the location pattern or the AFC request pattern without sending any of the one or more AFC requests to the AFC server. For example, after generating the location pattern and the AFC request pattern, the cellular network controller may use the AFC request pattern and the location pattern to identify a specific location that may be associated with future AFC requests, or a hole in the coverage area where the mobility zone of the location area may exist and may be associated with future AFC requests. In some specific implementations, the cellular network controller may send an AFC request for the identified location to the AFC server to receive an AFC power level indication in the AFC response associated with these locations. In this way, if a future AFC request from the AP includes one of the identified locations, the cellular network controller is able to determine the corresponding transmit power to be indicated in the AFC response without sending another AFC request to the AFC server.

[0171] like Fig.18As depicted in , independent of sending the AFC requests to the AFC server, a second number of AFC requests to the AFC server may be less than the first number of AFC requests by at least the number of one or more AFC responses generated by the cellular network controller. For example, during a first instance of an AP or STA traveling along a path, the cellular network controller may receive a first number of AFC requests from the AP and send the first number of AFC requests to the AFC server to obtain AFC data for determining a location pattern (or AFC request pattern) of the AP. During a later instance of the AP or STA traveling along the path (or a similarly located path), the cellular network controller may receive the same number of AFC requests from the AP as during the first instance, but the cellular network may only send a subset of the number of AFC requests received from the AP during the later instance. The reduction in the number of AFC requests sent to the AFC server is due to the cellular network controller being able to generate AFC responses based on previously received AFC data.

[0172] In some implementations, the location pattern can be determined by a logistic regression model (which can also be referred to as a logistic model), where the first number of AFC requests and the received AFC data for the first number of AFC requests are used as inputs to the logistic regression model.

[0173] Fig.19A flowchart illustrating an example operation 1900 for wireless communication for supporting AFC requests based on AFC events for controlling the transmit power of a wireless communication device according to some specific implementations is shown. Operation 1900 may be a supplement to operations 1400, 1600, 1700, and 1800, and the device performing operations 1400, 1600, 1700, 1800, and 1900 may be a cellular network controller. Operation 1900 is about using a logical model to generate a location pattern. At 1902, the cellular network controller receives a first number of AFC responses associated with a first number of AFC requests from an AFC server. The second number of AFC requests is based on the location pattern. For example, as described above, the second number of AFC requests (which are received during a later instance of an AP or STA (e.g., along a path located the same or similar to the first instance of travel)) is less than the first number of AFC requests (which are received during the first instance of the AP or STA traveling along the path). The difference between the first number and the second number is based on the AFC requests received by the cellular network controller, and the cellular network controller is capable of generating AFC responses for these AFC requests without sending AFC requests to the AFC server. For example, as described above, the cellular network controller is capable of identifying the transmit power corresponding to the location indicated in the AFC request based on the location pattern of the AP or STA, which may have been used to previously request an AFC response for the same location or otherwise allow the cellular network controller to identify the corresponding transmit power. In some specific implementations, the location pattern is determined based on the logical model and the first number of AFC requests. For example, the location of the AP or STA in the first number of AFC requests and the AFC power level indication in the first number of AFC responses can be used to train the logical model to generate an output of the transmit power corresponding to the input location. In this way, the AP or STA location indicated in the AFC request from the AP is input into the trained logical model, and the trained logical model outputs the transmit power corresponding to the input AP or STA location. For example, the transmit power indicated by the trained logical model may include whether SP is allowed. In another example, the transmit power that can be indicated includes SP, LPI, VLP, or any other appropriately defined power level. The cellular network controller may generate and send an AFC response with an AFC power level indication indicating the corresponding transmit power indicated by the logic model. If the AFC response will also include a frequency indicator, the cellular network controller may also generate and send an AFC response with a frequency indicator indicating a frequency to be used (e.g., a portion of the 6 GHz spectrum to be used by the AP to transmit to the network entity). In some implementations, the logic model may be trained to have a separate output indicating a frequency to be used (such as a specific wireless channel in the 6 GHz wireless band).In some other implementations, a separate model may be trained to output the frequencies to be used.

[0174] To prevent AFC requests from being sent at the same time or at the same location while traversing the same path, in some implementations, the AFC requests sent to the AFC server may be sent in a random manner.

[0175] Fig. 20 A flowchart illustrating an example operation 2000 for wireless communication for supporting AFC requests based on AFC events for controlling the transmit power of a wireless communication device according to some specific implementations is shown. Operation 2000 may be a supplement to operation 1400, and the device performing operations 1400 and 2000 may be an AP, a STA, a cellular network controller, or another suitable device. At 2002, the device sends multiple AFC requests, which are sent in a random manner. If the device is an AP, the AP may send multiple AFC requests to a network entity in a random manner. If the device is a STA, the STA may send multiple AFC requests to the AP in a random manner, wherein the AFC requests are provided to the network entity by the AP. If the device is a cellular network controller, the cellular network controller may send multiple AFC requests to the AFC server in a random manner. For example, a timer may be used to count the amount of time until the next AFC request is to be sent. As described above, in some specific implementations, the time set for the timer may be a random value or may include randomness so that the timer does not always count the same amount of time.

[0176] As devices become increasingly able to identify a transmit power and (optionally) a transmit frequency to use without sending an AFC request to an AFC server, the device may reduce the number of AFC requests sent to the AFC server. If when to send an AFC request is based on an AFC association timer that indicates when to send the AFC request (such as by counting down to zero), some implementations of reducing the number of AFC requests sent to the AFC server may include increasing the amount of time to be counted by the AFC association timer.

[0177] Fig.21A flowchart illustrating an example operation 2100 for wireless communication for supporting AFC requests based on AFC events for controlling the transmit power of a wireless communication device according to some specific implementations is shown. Operation 2100 may be a supplement to operation 1400, and the device performing operations 1400 and 2100 may be an AP, a STA, a cellular network controller, or another suitable device. At 2102, the device sends a first number of AFC requests to an AFC server during a first instance of AP or STA travel. In some examples, the first instance of travel may be along a first path. Each AFC request in the first number of AFC requests is sent based on the expiration of a first time at a timer. Note that the first time may be a static amount of time, or may vary to ensure that the AFC request is sent in a random manner.

[0178] At 2104, the device sends a second number of AFC requests to the AFC server during a second instance of the AP or STA's travel. In some examples, the second instance of the travel may be along the first path or along a second path similarly positioned to the first path (e.g., along a road defining a train track associated with the first path, a second path repeatedly crossing the first path, or a second path having various points close to the point geographic location of the first path). Each AFC request in the second number of AFC requests sent expires based on a second time at the timer, and the second time is greater than the first time. In this way, the spacing between the AFC requests may be increased as a whole based on the difference between the second time and the first time. Similar to the first time, the second time may be static, or may be variable to ensure that the AFC request is sent in a random manner. If the first time and the second time are variable, the first time may be within a bounded range lower than the bounded range defined for the second time. In this way, the second time may remain greater than the first time, even if the first time and the second time are variable.

[0179] Any storage of a device is limited in size. For example, a certain amount of memory may be allocated to store a table including AP or STA locations, AFC power level indications, and (optionally) frequency indicators. Therefore, the table (or other memory for storing such AFC data) may be limited to a maximum number of entries. In some implementations, a device may limit the number of AFC requests sent based on the memory size of the device. For example, if the table can only store ten additional locations and corresponding AFC power level indications, the device may only send ten more AFC requests.

[0180] Fig. 22A flowchart illustrating an example operation 2200 for wireless communication for supporting AFC requests based on AFC events for controlling the transmit power of a wireless communication device according to some specific implementations is shown. Operation 2200 may be a supplement to operation 1400, and the device performing operations 1400 and 2200 may be an AP, a STA, a cellular network controller, or another suitable device. At 2202, the device sends a certain number of AFC requests, the number of which is based on the memory size of the device. In some specific implementations, the number of AFC requests may also be based on the required minimum number or frequency of AFC requests to be sent. The device may replace older entries in a table or device memory with AFC data from a new AFC response (such as in a first-in, first-out (FIFO) order). Alternatively, the device may not store the newly received AFC data in a table or device memory.

[0181] Various specific implementations for reducing the number of AFC requests sent to an AFC server or other parts of a cellular network are described above. As described above, any suitable device may be used to perform the operations described above. For example, an AP, a STA, or a cellular network component may perform one or more of these operations. The cellular network component may include any suitable component of a cellular network. Although these examples may describe communicating with a network entity (such as sending an AFC request to a network entity or receiving an AFC request from a network entity), the network entity used in the above examples may refer to one or more network entities of a cellular network. In addition, although the cellular network component is described as a component of a cellular network, the cellular network component may include a combination of components. For example, a cellular network component that assists AFC may include one or more network entities, an RNC, and a location server of a cellular network. Various machine learning models, logical models, and other models are described above with reference to reducing the number of AFC requests to an AFC server. One or more models may be implemented in hardware, software, or a combination of both in a device that performs an AFC operation. For example, an AP or STA may store in a memory a machine learning model that can be implemented in any suitable processor-readable code and trained hyperparameters of the machine learning model. The code including the machine learning model with the trained hyperparameters may be executed by any suitable processor of the AP or STA to cause the AP or STA to perform the operation of the trained machine learning model. In addition, although the above examples are described with reference to setting the transmit power and (optionally) transmit frequency for transmission in the 6 GHz wireless band, the various operations described above may be applied to determine the transmit power or transmit frequency for other wireless bands. For example, if the AFC is extended to other frequency bands, the operations described above may be extended to those other frequency bands to determine the transmit power and one or more wireless channels to be used for transmission. There may also be other variations of the above examples that do not remove these examples from the scope of the present disclosure.

[0182] Specific implementation examples are described in the following numbered clauses:

[0183] Clause 1. A device comprising:

[0184] at least one processor; and

[0185] at least one memory, the at least one memory being communicatively coupled to the at least one processor and storing processor-readable code, the processor-readable code being executed by the at least one processor

[0186] The device is configured to enable:

[0187] Sending Automatic Frequency Coordination (AFC) requests;

[0188] receiving an AFC response, wherein the AFC response includes an AFC power level indication for one or more nearest neighbor entities of the device;

[0189] setting a transmit power of the device based at least in part on the AFC power level indication for at least one of the one or more nearest neighbor entities; and

[0190] Transmitting at the said transmit power.

[0191] Clause 2. The apparatus of clause 1, wherein execution of the processor readable code is further configured to cause the apparatus to:

[0192] sending a first number of AFC requests during a first instance of travel; and

[0193] and sending a second number of AFC requests, less than the first number of AFC requests, during one or more consecutive instances following the first instance of traveling, wherein the second number of AFC requests is based at least in part on setting the transmit power to an AFC power level indication to a neighboring entity of the one or more nearest neighboring entities independently of sending another AFC request.

[0194] Clause 3. The apparatus of clause 2, wherein execution of the processor readable code is further configured to cause the apparatus to set the second number of AFC requests to a minimum value required for performing AFC.

[0195] Clause 4. An apparatus according to any one or more of clauses 1 to 3, wherein the AFC power level indication for the one or more nearest neighbor entities is stored in a table identifying the one or more nearest neighbor entities, the location of each of the one or more nearest neighbor entities, and the AFC power level indication for the one or more nearest neighbor entities.

[0196] Clause 5. The apparatus of any one or more of clauses 1 to 4, wherein the AFC power level indication is a binary indication of whether standard power (SP) transmit power is allowed.

[0197] Clause 6. An apparatus as described in any one or more of Clauses 1 to 5, wherein the AFC response includes a VendorExtension object to indicate the AFC power level indication for the one or more nearest neighbor entities.

[0198] Clause 7. A device according to any one or more of clauses 1 to 6, wherein the AFC response includes a frequency indicator of the one or more nearest neighboring entities of the device, wherein execution of the processor readable code is further configured to cause the device to set a transmission frequency based at least in part on the frequency indicators of the one or more nearest neighboring entities of the device, and wherein transmission at the transmission power includes transmission at the transmission frequency.

[0199] Clause 8. A method for wireless communication by a device, comprising:

[0200] Sending Automatic Frequency Coordination (AFC) requests;

[0201] receiving an AFC response, wherein the AFC response includes an AFC power level indication for one or more nearest neighbor entities of the device;

[0202] setting a transmit power of the device based at least in part on the AFC power level indication for at least one of the one or more nearest neighbor entities; and

[0203] Transmitting at the said transmit power.

[0204] Clause 9. The method according to clause 8, further comprising:

[0205] sending a first number of AFC requests during a first instance of travel; and

[0206] and sending a second number of AFC requests, less than the first number of AFC requests, during one or more consecutive instances following the first instance of traveling, wherein the second number of AFC requests is based at least in part on setting the transmit power to an AFC power level indication to a neighboring entity of the one or more nearest neighboring entities independently of sending another AFC request.

[0207] Clause 10. The method of clause 9, further comprising setting the number of AFC requests to a minimum value required to perform AFC.

[0208] Clause 11. A method according to any one or more of clauses 8 to 10, wherein one or more AFC power level indications for the one or more nearest neighbor entities are stored in a table identifying the one or more nearest neighbor entities, the location of each of the one or more nearest neighbor entities, and the AFC power level indications for the one or more nearest neighbor entities.

[0209] Clause 12. The method of any one or more of clauses 8 to 11, wherein the AFC power level indication is a binary indication of whether standard power (SP) transmit power is allowed.

[0210] Clause 13. The method of any one or more of clauses 8 to 12, wherein the AFC response includes a VendorExtension object to indicate the AFC power level indication to the one or more nearest neighbor entities.

[0211] Clause 14. A method according to any one or more of clauses 8 to 13, wherein the AFC response includes a frequency indicator of the one or more nearest neighboring entities of the device, wherein the device sets a transmission frequency based at least in part on the frequency indicators of the one or more nearest neighboring entities of the device, and transmission at the transmission power includes transmission at the transmission frequency.

[0212] Clause 15. An apparatus comprising:

[0213] at least one processor; and

[0214] at least one memory, the at least one memory being communicatively coupled to the at least one processor and storing processor-readable code, the processor-readable code being executed by the at least one processor

[0215] The device is configured to enable:

[0216] sending an automatic frequency coordination (AFC) request to a network component in a cellular network based at least in part on an AFC event;

[0217] receiving an AFC response from the network component;

[0218] identifying a transmit power to be used by one of an access point (AP) or a station (STA) based on the AFC response; and

[0219] The one of the AP or the STA is instructed to transmit using a specific transmit power level.

[0220] Clause 16. The apparatus of clause 15, wherein:

[0221] The device is included in the one of the AP or the STA;

[0222] The AFC request is sent to a network entity;

[0223] The AFC response is received from the network entity; and

[0224] The AFC event includes one of the following:

[0225] The one of the AP or the STA crosses a cellular-based location boundary;

[0226] Switching of the AP between network entities; or

[0227] The AFC association timer indicates that an AFC request is to be transmitted.

[0228] Clause 17. The apparatus of clause 16, wherein execution of the processor readable code is further configured to cause the apparatus to:

[0229] obtaining a plurality of positions of the one of the AP or the STA associated with a plurality of AFC events during one or more instances of traveling;

[0230] determining a pattern of positions of the one of the AP or the STA over time based at least in part on the plurality of positions of the one of the AP or the STA associated with the plurality of AFC events; and

[0231] Based at least in part on the location pattern, a second number of AFC requests, less than the first number, is sent to the network entity during consecutive instances following the one or more instances of traveling, wherein the first number of AFC requests is sent during one of the one or more instances of traveling, and the second number of AFC requests is based at least in part on setting the transmit power of the AP or the one of the STAs to a transmit power associated with one of the multiple locations of the AP or the one of the STAs and one of the multiple AFC events independently of sending another AFC request.

[0232] Clause 18. Apparatus according to any one or more of clauses 15 to 17, wherein:

[0233] The device is included in a cellular network controller to receive one or more AFC requests from the AP and provide one or more AFC responses to the AP;

[0234] The AFC event includes receiving an AFC request from the AP;

[0235] The AFC request to be sent by the device will be sent to an AFC server in the cellular network; and

[0236] The AFC response to be received by the device will be received from the AFC server.

[0237] Clause 19. The apparatus of clause 18, wherein execution of the processor readable code is further configured to cause the apparatus to:

[0238] obtaining one or more positions of the one of the AP or the STA during one or more instances of travel of the one of the AP or the STA, wherein the one or more positions are associated with one or more AFC events; and

[0239] A corresponding transmit power associated with each of the one or more locations is obtained.

[0240] Clause 20. The apparatus of clause 19, wherein execution of the processor readable code is further configured to cause the apparatus to:

[0241] receiving another AFC request from the AP;

[0242] obtaining a first position of the one of the AP or the STA; and

[0243] and sending an AFC response to the AP independently of sending an AFC request to the AFC server, wherein the AFC response indicates a current transmit power to be used by the AP or the one of the STAs, wherein the current transmit power is based at least in part on the first position of the AP or the one of the STAs, the one or more positions of the AP or the one of the STAs, and one or more corresponding transmit powers associated with the one or more positions.

[0244] Clause 21. The apparatus of clause 20, wherein execution of the processor readable code is further configured to cause the apparatus to:

[0245] sending a first number of AFC requests to the AFC server during a first instance of travel by the one of the AP or the STA, wherein the first number of AFC requests is associated with the one of the AP or the STA;

[0246] Identify one or more of the following:

[0247] a pattern of positions of the one of the AP or the STA over time based at least in part on the one or more positions of the one of the AP or the STA; or

[0248] a pattern of AFC requests over time by the AP based at least in part on one or more AFC requests received from the AP; and

[0249] sending, to the AFC server, a second number of AFC requests less than the first number of AFC requests during one or more consecutive instances following the first instance of travel by the one of the AP or the STA, wherein:

[0250] the second number of AFC requests being based at least in part on sending one or more AFC responses to the AP, the one or more AFC responses indicating a transmit power to be used by the one of the AP or the STA based at least in part on one or more of the location pattern or the AFC request pattern; and

[0251] The one or more AFC responses sent to the AP are sent independently of sending another AFC request to the AFC server.

[0252] Clause 22. The apparatus of clause 21, wherein execution of the processor readable code is further configured to cause the apparatus to:

[0253] receiving a first number of AFC responses associated with the first number of AFC requests, wherein:

[0254] The second number of AFC requests is based on the location pattern; and

[0255] The location pattern is determined based on a logical model and the first number of AFC requests.

[0256] Clause 23. The device of clause 15, wherein execution of the processor readable code is further configured to cause the device to send a plurality of AFC requests, wherein the plurality of AFC requests are sent in a random manner.

[0257] Clause 24. The apparatus of any one or more of clauses 15 to 23, wherein execution of the processor readable code is further configured to cause the apparatus to:

[0258] sending a first number of AFC requests to the AFC server during a first instance of travel by the one of the AP or the STA, wherein sending each of the first number of AFC requests expires based on a first time at a timer; and

[0259] A second number of AFC requests are sent to the AFC server during a second instance of travel by the one of the AP or the STA, wherein sending each of the second number of AFC requests is based on expiration of a second time at the timer, wherein the second time is greater than the first time.

[0260] Clause 25. The device of any one or more of clauses 15 to 24, wherein execution of the processor readable code is further configured to cause the device to send a number of AFC requests, wherein the number of AFC requests is based on a memory size of the device.

[0261] Clause 26. The device of any one or more of clauses 15 to 25, wherein the device is to identify a transmit frequency to be used and instruct the one of the AP or the STA to transmit using the transmit frequency.

[0262] Clause 27. A method for wireless communication by a device, comprising:

[0263] sending an automatic frequency coordination (AFC) request to a network component in a cellular network based at least in part on an AFC event;

[0264] receiving an AFC response from the network component;

[0265] identifying a transmit power to be used by one of an access point (AP) or a station (STA) based on the AFC response; and

[0266] The one of the AP or the STA is instructed to transmit using a specific transmit power level.

[0267] Clause 28. The method according to clause 27, wherein:

[0268] The device is included in the one of the AP or the STA;

[0269] The AFC request is sent to a network entity;

[0270] The AFC response is received from the network entity; and

[0271] The AFC event includes one of the following:

[0272] The one of the AP or the STA crosses a cellular-based location boundary;

[0273] Switching of the AP between network entities; or

[0274] The AFC association timer indicates that an AFC request is to be transmitted.

[0275] Clause 29. The method according to clause 28, further comprising:

[0276] obtaining a plurality of positions of the one of the AP or the STA associated with a plurality of AFC events during one or more instances of traveling;

[0277] determining a pattern of positions of the one of the AP or the STA over time based at least in part on the plurality of positions of the one of the AP or the STA associated with the plurality of AFC events; and

[0278] Based at least in part on the location pattern, a second number of AFC requests, less than the first number, is sent to the network entity during consecutive instances following the one or more instances of traveling, wherein the first number of AFC requests is sent during one of the one or more instances of traveling, and the second number of AFC requests is based at least in part on setting the transmit power of the AP or the one of the STAs to a transmit power associated with one of the multiple locations of the AP or the one of the STAs and one of the multiple AFC events independently of sending another AFC request.

[0279] Clause 30. A method according to any one or more of clauses 27 to 29, wherein:

[0280] The device is included in a cellular network controller to receive one or more AFC requests from the AP and provide one or more AFC responses to the AP;

[0281] The AFC event includes receiving an AFC request from the AP;

[0282] The AFC request to be sent by the device will be sent to an AFC server in the cellular network; and

[0283] The AFC response to be received by the device will be received from the AFC server.

[0284] Clause 31. The method according to clause 30, further comprising:

[0285] obtaining one or more positions of the one of the AP or the STA during one or more instances of travel of the one of the AP or the STA, wherein the one or more positions are associated with one or more AFC events; and

[0286] A corresponding transmit power associated with each of the one or more locations is obtained.

[0287] Clause 32. The method according to clause 31, further comprising:

[0288] receiving another AFC request from the AP;

[0289] obtaining a first position of the one of the AP or the STA; and

[0290] and sending an AFC response to the AP independently of sending an AFC request to the AFC server, wherein the AFC response indicates a current transmit power to be used by the AP or the one of the STAs, wherein the current transmit power is based at least in part on the first position of the AP or the one of the STAs, the one or more positions of the AP or the one of the STAs, and one or more corresponding transmit powers associated with the one or more positions.

[0291] Clause 33. The method according to clause 32, further comprising:

[0292] sending a first number of AFC requests to the AFC server during a first instance of travel by the one of the AP or the STA, wherein the first number of AFC requests is associated with the one of the AP or the STA;

[0293] Identify one or more of the following:

[0294] a pattern of positions of the one of the AP or the STA over time based at least in part on the one or more positions of the one of the AP or the STA; or

[0295] a pattern of AFC requests over time by the AP based at least in part on one or more AFC requests received from the AP; and

[0296] sending, to the AFC server, a second number of AFC requests less than the first number of AFC requests during one or more consecutive instances following the first instance of travel by the one of the AP or the STA, wherein:

[0297] the second number of AFC requests being based at least in part on sending one or more AFC responses to the AP, the one or more AFC responses indicating a transmit power to be used by the one of the AP or the STA based at least in part on one or more of the location pattern or the AFC request pattern; and

[0298] The one or more AFC responses sent to the AP are sent independently of sending another AFC request to the AFC server.

[0299] Clause 34. The method of clause 33, further comprising receiving a first number of AFC responses associated with the first number of AFC requests, wherein:

[0300] The second number of AFC requests is based on the location pattern; and

[0301] The location pattern is determined based on a logical model and the first number of AFC requests.

[0302] Clause 35. The method of any one or more of clauses 27 to 34, further comprising sending a plurality of AFC requests, wherein the plurality of AFC requests are sent in a random manner.

[0303] Clause 36. The method according to any one or more of clauses 27 to 35, further comprising:

[0304] sending a first number of AFC requests to the AFC server during a first instance of travel by the one of the AP or the STA, wherein sending each of the first number of AFC requests expires based on a first time at a timer; and

[0305] A second number of AFC requests are sent to the AFC server during a second instance of travel by the one of the AP or the STA, wherein sending each of the second number of AFC requests is based on expiration of a second time at the timer, wherein the second time is greater than the first time.

[0306] Clause 37. The method according to any one or more of clauses 27 to 36, further comprising:

[0307] A number of AFC requests are sent, wherein the number of AFC requests is based on a memory size of the device.

[0308] Clause 38. The method of any one or more of clauses 27 to 37, wherein the device identifies a transmit frequency to be used and instructs the one of the AP or the STA to transmit using the particular transmit frequency.

[0309] As used herein, a phrase referring to "at least one of" or "one or more of" a list of items refers to any combination of those items, including single members. For example, "at least one of a, b, or c" is intended to cover the following possibilities: only a, only b, only c, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a, b, and c. As used herein, "based on" is intended to be interpreted in an inclusive sense unless explicitly indicated otherwise. For example, "based on" can be used interchangeably with "based at least in part on," unless explicitly indicated otherwise. Specifically, unless the phrase in the context refers to "based only on 'one'" or an equivalent, whether it is "based on 'one'" or "based at least in part on 'one'" can be based on "one" alone or on a combination of "one" and one or more other factors, conditions, or information.

[0310] The various illustrative components, logic, logic blocks, modules, circuits, operations, and algorithmic processes described in conjunction with the specific implementations disclosed herein may be implemented as electronic hardware, firmware, software, or a combination of hardware, firmware, or software, including the structures disclosed in this specification and their structural equivalents. This interchangeability of hardware, firmware, and software has been generally described in terms of their functionality and exemplified in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the overall system.

[0311] Various modifications to the specific implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other specific implementations without departing from the spirit or scope of the disclosure. Therefore, the claims are not intended to be limited to the specific implementations shown herein, but are to be consistent with the broadest scope consistent with the disclosure, the principles and novel features disclosed herein.

[0312] Additionally, various features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations individually or in any suitable subcombination. Thus, although features may be described above as functioning in a particular combination, and even initially claimed as such, one or more features from a claimed combination may in some cases be deleted from the combination, and a claimed combination may be directed to a subcombination or variations of a subcombination.

[0313] Similarly, although operations are depicted in a specific order in the figure, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all illustrated operations to achieve the desired result. In addition, the accompanying drawings may schematically depict one or more example processes in the form of a flow chart or a flow diagram. However, other operations not depicted may be incorporated into the example processes schematically illustrated. For example, one or more additional operations may be performed before, after, simultaneously or between any operations in the illustrated operations. In some environments, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the specific implementation described above should not be understood as requiring such separation in all specific implementations, but it should be understood as described program components and systems can usually be integrated together in a single software product, or be packaged in multiple software products.

Claims

1. A device comprising: at least one processor; and at least one memory communicatively coupled to the at least one processor and storing processor-readable code that, when executed by the at least one processor, is configured to cause the apparatus to: Sending Automatic Frequency Coordination (AFC) requests; receiving an AFC response, wherein the AFC response includes an AFC power level indication for one or more nearest neighbor entities of the device; setting a transmit power of the device based at least in part on the AFC power level indication for at least one of the one or more nearest neighbor entities; as well as Transmitting at the said transmit power.

2. The device of claim 1 , wherein execution of the processor readable code is further configured to cause the device to: sending a first number of AFC requests during a first instance of travel; and and sending a second number of AFC requests, less than the first number of AFC requests, during one or more consecutive instances following the first instance of traveling, wherein the second number of AFC requests is based at least in part on setting the transmit power to an AFC power level indication to a neighboring entity of the one or more nearest neighboring entities independently of sending another AFC request.

3. The apparatus of claim 2, wherein execution of the processor readable code is further configured to cause the apparatus to set the second number of AFC requests to a minimum value required for performing AFC.

4. The apparatus of claim 1 , wherein the AFC power level indications for the one or more nearest neighbor entities are stored in a table identifying the one or more nearest neighbor entities, a location of each of the one or more nearest neighbor entities, and the AFC power level indications for the one or more nearest neighbor entities. 5 . The apparatus of claim 1 , wherein the AFC power level indication is a binary indication as to whether standard power (SP) transmit power is allowed. 6 . The apparatus of claim 1 , wherein the AFC response comprises a VendorExtension object to indicate the AFC power level indication to the one or more nearest neighbor entities.

7. The device of claim 1 , wherein the AFC response comprises frequency indicators of the one or more nearest neighbor entities of the device, wherein execution of the processor readable code is further configured to cause the device to set a transmit frequency based at least in part on the frequency indicators of the one or more nearest neighbor entities of the device, and wherein transmitting at the transmit power comprises transmitting at the transmit frequency.

8. A method for wireless communication by a device, comprising: Sending Automatic Frequency Coordination (AFC) requests; receiving an AFC response, wherein the AFC response includes an AFC power level indication for one or more nearest neighbor entities of the device; setting a transmit power of the device based at least in part on the AFC power level indication for at least one of the one or more nearest neighbor entities; as well as Transmitting at the said transmit power.

9. The method according to claim 8, further comprising: sending a first number of AFC requests during a first instance of travel; as well as and sending a second number of AFC requests, less than the first number of AFC requests, during one or more consecutive instances following the first instance of traveling, wherein the second number of AFC requests is based at least in part on setting the transmit power to an AFC power level indication to a neighboring entity of the one or more nearest neighboring entities independently of sending another AFC request.

10. A device comprising: at least one processor; and at least one memory communicatively coupled to the at least one processor and storing processor-readable code that, when executed by the at least one processor, is configured to cause the apparatus to: sending an automatic frequency coordination (AFC) request to a network component in a cellular network based at least in part on an AFC event; receiving an AFC response from the network component; identifying a transmit power to be used by one of an access point (AP) or a station (STA) based on the AFC response; as well as The one of the AP or the STA is instructed to transmit using a specific transmit power level.

11. The apparatus of claim 10, wherein: The device is included in the one of the AP or the STA; The AFC request is sent to a network entity; The AFC response is received from the network entity; and The AFC event includes one of the following: The one of the AP or the STA crosses a cellular-based location boundary; Switching of the AP between network entities; or The AFC association timer indicates that an AFC request is to be transmitted.

12. The device of claim 11, wherein execution of the processor readable code is further configured to cause the device to: obtaining a plurality of positions of the one of the AP or the STA associated with a plurality of AFC events during one or more instances of traveling; determining a location pattern of the one of the AP or the STA over time based at least in part on the plurality of locations of the one of the AP or the STA associated with the plurality of AFC events; as well as Based at least in part on the location pattern, a second number of AFC requests, less than the first number, is sent to the network entity during consecutive instances following the one or more instances of traveling, wherein the first number of AFC requests is sent during one of the one or more instances of traveling, and the second number of AFC requests is based at least in part on setting the transmit power of the AP or the one of the STAs to a transmit power associated with one of the multiple locations of the AP or the one of the STAs and one of the multiple AFC events independently of sending another AFC request.

13. The apparatus of claim 10, wherein: The device is included in a cellular network controller to receive one or more AFC requests from the AP and provide one or more AFC responses to the AP; The AFC event includes receiving an AFC request from the AP; The AFC request to be sent by the device will be sent to an AFC server in the cellular network; and The AFC response to be received by the device will be received from the AFC server.

14. The apparatus of claim 13, wherein execution of the processor readable code is further configured to cause the apparatus to: obtaining one or more locations of the one of the AP or the STA during one or more instances of travel of the one of the AP or the STA, wherein the one or more locations are associated with one or more AFC events; and A corresponding transmit power associated with each of the one or more locations is obtained.

15. The device of claim 14, wherein execution of the processor readable code is further configured to cause the device to: receiving another AFC request from the AP; obtaining a first position of the one of the AP or the STA; and and sending an AFC response to the AP independently of sending an AFC request to the AFC server, wherein the AFC response indicates a current transmit power to be used by the AP or the one of the STAs, wherein the current transmit power is based at least in part on the first position of the AP or the one of the STAs, the one or more positions of the AP or the one of the STAs, and one or more corresponding transmit powers associated with the one or more positions.

16. The device of claim 15, wherein execution of the processor readable code is further configured to cause the device to: sending a first number of AFC requests to the AFC server during a first instance of travel by the one of the AP or the STA, wherein the first number of AFC requests is associated with the one of the AP or the STA; Identify one or more of the following: a pattern of positions of the one of the AP or the STA over time based at least in part on the one or more positions of the one of the AP or the STA; or a pattern of AFC requests over time by the AP based at least in part on one or more AFC requests received from the AP; as well as sending, to the AFC server, a second number of AFC requests less than the first number of AFC requests during one or more consecutive instances following the first instance of travel by the one of the AP or the STA, wherein: the second number of AFC requests being based at least in part on sending one or more AFC responses to the AP, the one or more AFC responses indicating a transmit power to be used by the one of the AP or the STA based at least in part on one or more of the location pattern or the AFC request pattern; and The one or more AFC responses sent to the AP are sent independently of sending another AFC request to the AFC server.

17. The device of claim 16, wherein execution of the processor readable code is further configured to cause the device to: receiving a first number of AFC responses associated with the first number of AFC requests, wherein: The second number of AFC requests is based on the location pattern; and The location pattern is determined based on a logical model and the first number of AFC requests.

18. The device of claim 10, wherein execution of the processor readable code is further configured to cause the device to send a plurality of AFC requests, wherein the plurality of AFC requests are sent in a random manner.

19. The device of claim 10, wherein execution of the processor readable code is further configured to cause the device to: sending a first number of AFC requests to the AFC server during a first instance of travel by the one of the AP or the STA, wherein sending each of the first number of AFC requests expires based on a first time at a timer; and A second number of AFC requests are sent to the AFC server during a second instance of travel by the one of the AP or the STA, wherein sending each of the second number of AFC requests is based on expiration of a second time at the timer, wherein the second time is greater than the first time.

20. The device of claim 10, wherein execution of the processor readable code is further configured to cause the device to send a number of AFC requests, wherein the number of AFC requests is based on a memory size of the device.

21. The device of claim 10, wherein the device is to identify a transmission frequency to be used and instruct the one of the AP or the STA to transmit using the transmission frequency.

22. A method for wireless communication by a device, comprising: sending an automatic frequency coordination (AFC) request to a network component in a cellular network based at least in part on an AFC event; receiving an AFC response from the network component; identifying a transmit power to be used by one of an access point (AP) or a station (STA) based on the AFC response; as well as The one of the AP or the STA is instructed to transmit using a specific transmit power level.

23. The method of claim 22, wherein: The device is included in the one of the AP or the STA; The AFC request is sent to a network entity; The AFC response is received from the network entity; and The AFC event includes one of the following: The one of the AP or the STA crosses a cellular-based location boundary; Switching of the AP between network entities; or The AFC association timer indicates that an AFC request is to be transmitted.

24. The method according to claim 23, further comprising: obtaining a plurality of positions of the one of the AP or the STA associated with a plurality of AFC events during one or more instances of traveling; determining a location pattern of the one of the AP or the STA over time based at least in part on the plurality of locations of the one of the AP or the STA associated with the plurality of AFC events; as well as Based at least in part on the location pattern, a second number of AFC requests, less than the first number, is sent to the network entity during consecutive instances following the one or more instances of traveling, wherein the first number of AFC requests is sent during one of the one or more instances of traveling, and the second number of AFC requests is based at least in part on setting the transmit power of the AP or the one of the STAs to a transmit power associated with one of the multiple locations of the AP or the one of the STAs and one of the multiple AFC events independently of sending another AFC request.

25. The method of claim 22, wherein: The device is included in a cellular network controller to receive one or more AFC requests from the AP and provide one or more AFC responses to the AP; The AFC event includes receiving an AFC request from the AP; The AFC request to be sent by the device will be sent to an AFC server in the cellular network; and The AFC response to be received by the device will be received from the AFC server.

26. The method according to claim 25, further comprising: obtaining one or more positions of the one of the AP or the STA during one or more instances of travel of the one of the AP or the STA, wherein the one or more positions are associated with one or more AFC events; as well as A corresponding transmit power associated with each of the one or more locations is obtained.

27. The method according to claim 26, further comprising: receiving another AFC request from the AP; Obtaining a first position of the one of the AP or the STA; as well as and sending an AFC response to the AP independently of sending an AFC request to the AFC server, wherein the AFC response indicates a current transmit power to be used by the AP or the one of the STAs, wherein the current transmit power is based at least in part on the first position of the AP or the one of the STAs, the one or more positions of the AP or the one of the STAs, and one or more corresponding transmit powers associated with the one or more positions.

28. The method according to claim 27, further comprising: sending a first number of AFC requests to the AFC server during a first instance of travel by the one of the AP or the STA, wherein the first number of AFC requests is associated with the one of the AP or the STA; Identify one or more of the following: a pattern of positions of the one of the AP or the STA over time based at least in part on the one or more positions of the one of the AP or the STA; or a pattern of AFC requests over time by the AP based at least in part on one or more AFC requests received from the AP; as well as sending, to the AFC server, a second number of AFC requests less than the first number of AFC requests during one or more consecutive instances following the first instance of travel by the one of the AP or the STA, wherein: the second number of AFC requests being based at least in part on sending one or more AFC responses to the AP, the one or more AFC responses indicating a transmit power to be used by the one of the AP or the STA based at least in part on one or more of the location pattern or the AFC request pattern; and The one or more AFC responses sent to the AP are sent independently of sending another AFC request to the AFC server.

29. The method of claim 28, further comprising receiving a first number of AFC responses associated with the first number of AFC requests, wherein: The second number of AFC requests is based on the location pattern; and The location pattern is determined based on a logical model and the first number of AFC requests.

30. The method of claim 22, further comprising: sending a first number of AFC requests to the AFC server during a first instance of travel by the one of the AP or the STA, wherein sending each of the first number of AFC requests expires based on a first time at a timer; as well as A second number of AFC requests are sent to the AFC server during a second instance of travel by the one of the AP or the STA, wherein sending each of the second number of AFC requests is based on expiration of a second time at the timer, wherein the second time is greater than the first time.

Images