Shared frequency band for multiple networks

Abstract

Some wireless devices communicate with multiple networks. For example, a User Equipment (UE) may communicate with cellular networks and wireless local area networks (WLANs). In some cases, licensed and unlicensed use may occur in the same portion of the radio frequency (RF) spectrum or in overlapping portions of the RF spectrum. In some examples of the techniques described herein, the UE may relay information between networks to coordinate spectrum usage in the same frequency band. For example, a cellular network may provide channel sharing information to the UE. Channel sharing information may include requests to another network (e.g., a WLAN) to free up one or more channels in a frequency band, requests to reduce the transmit signal power of one or more channels, or other channel sharing information. The UE may be used to relay channels that share information with another network.

Description

Cross-referencing

[0001] This patent application claims the benefit of U.S. Patent Application No. 18 / 410,867, entitled “SHARED BANDS FORMULTIPLE NETWORKS”, filed January 11, 2024, by LEE et al., which has been assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0002] The following discussion pertains to wireless communications, including shared frequency bands used for multiple networks. Background Technology

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0004] Some wireless devices communicate with multiple networks. For example, user equipment (UE) may communicate with cellular networks and wireless local area networks (WLANs). Portions of the radio frequency (RF) spectrum may be designated for use by one or more wireless networks (e.g., a combination of different types of networks, such as a combination of one or more cellular networks and one or more WLAN networks). A portion of the RF spectrum may be licensed for use by cellular networks, and another portion may be designated for unlicensed use. For example, the higher 6 GHz band (e.g., the 6 GHz band according to the International Mobile Telecommunications (IMT) standard) may be allocated to unlicensed users in certain regions of the world. In some cases, licensed and unlicensed use may occur in the same portion of the RF spectrum or in overlapping portions of the RF spectrum. Some regions (e.g., countries, regions controlled by regulatory bodies, ethnic groups, states, or unions, etc.) may allocate the higher portion of the 6 GHz band as unlicensed spectrum for indoor use while simultaneously licensing the same spectrum for outdoor coverage deployments.

[0005] Rules, procedures, or techniques for accessing networks occupying the same frequency band can improve access and RF spectrum usage. In some examples of the techniques described herein, the UE can relay information between networks to coordinate spectrum usage in the same frequency band. For example, a cellular network (e.g., a 3GPP network) can provide channel sharing information to the UE. This channel sharing information may include: a request (e.g., from a mobile network operator (MNO)) to free up one or more channels in a frequency band for another network (e.g., a WLAN), indicating the time period for freeing up one or more channels; a request to reduce the transmit signal power of one or more channels, indicating the time period for reducing the transmit signal power of one or more channels; or other channel sharing information. The UE can use this to relay channels shared with another network.

[0006] In some aspects, channel sharing information can be encoded into 802.11 Enhanced Broadcast Service (EBCS) uplink frames. For example, an EBCS uplink frame may include a higher-layer protocol (HLP) payload. An EBCS uplink frame may include a certificate associated with the MNO or network (e.g., certificate verification). For example, an EBCS uplink frame may be signed with a private key associated with the certificate. A UE (e.g., a non-access point (AP) station (STA)) may include the certificate in the uplink EBCS frame sent to the AP. The EBCS uplink frame may indicate a destination (e.g., to an authorizing server). An AP (e.g., which typically relays information from STAs or UEs) may relay the HLP to the destination indicated in the frame (e.g., a server) via an associated EBCS agent. The EBCS agent may use the certificate in the uplink frame to verify the signature. For example, an EBCS agent may verify the EBCS uplink frame and may forward the HLP payload to the destination (e.g., an authorizing server).

[0007] In some aspects, the authorization server can verify channel sharing requests from the MNO. In some examples, the authorization server can be provided by a broadband service provider, the MNO, or an enterprise. The authorization server can evaluate channel sharing requests from the MNO based on policies or regulations. In some cases, the authorization server can authorize part or all of the request (e.g., authorize the freeing up of one or more channels). The authorization server can transmit the request to the AP to perform an action corresponding to the evaluation result (e.g., an authorization action). In some examples, the request can be protected based on Transport Layer Security (TLS). The request can be processed (e.g., processed by a broadband operator or WLAN operator) and configured at the AP. In some examples, the broadband service provider associated with the network (e.g., WLAN) can have a Service Level Agreement (SLA) with the MNO for channel sharing operations. Some examples of the techniques described herein can be performed in IMT-related processes.

[0008] A method performed by a UE is described. The method may include: transmitting to a first network a measurement of a signal received from a second network; receiving from the first network information for sharing a frequency band between the first and second networks, wherein the information for sharing the frequency band is based on the measurement of the signal received from the second network; and transmitting to the second network the information for sharing the frequency band between the first and second networks.

[0009] A UE is described. The UE may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to cause the UE to: transmit measurements of signals received from a second network to a first network; receive information from the first network for sharing a frequency band between the first network and the second network, wherein the information for sharing the frequency band is based on measurements of signals received from the second network; and transmit the information for sharing the frequency band between the first network and the second network to the second network.

[0010] Another UE is described. This UE may include: components for transmitting to a first network measurements of signals received from a second network; components for receiving from the first network information for sharing a frequency band between the first and second networks, wherein the information for sharing the frequency band is based on measurements of signals received from the second network; and components for transmitting to the second network information for sharing the frequency band between the first and second networks.

[0011] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to perform the following operations: transmitting to a first network measurements of signals received from a second network; receiving from the first network information for sharing a frequency band between the first and second networks, wherein the information for sharing the frequency band is based on measurements of signals received from the second network; and transmitting to the second network information for sharing the frequency band between the first and second networks.

[0012] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for: receiving from a first network a configuration for the UE to use to measure signals from a second network; and receiving signals from the second network to generate measurements of signals from the second network using the configuration received from the first network.

[0013] The methods described herein, some examples of UEs and non-transitory computer-readable media may also include operations, features, components or instructions for transmitting information for sharing a frequency band, including transmitting information in an EBCS uplink frame.

[0014] The methods described herein, UEs, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for receiving information for sharing a frequency band, including receiving information from a broadcast via an SIB.

[0015] In some examples of the methods, UEs, and nontransitory computer-readable media described herein, the information used for sharing a frequency band includes a certificate associated with a first network, control instructions for freeing up channels in the frequency band, control instructions for reducing transmission power in channels in the frequency band, instructions for time periods for one or more control instructions, instructions for time, an identifier of the first network, or any combination thereof.

[0016] The methods described herein, examples of UEs, and nontransitory computer-readable media may also include operations, features, components, or instructions for performing licensed communication with a first network based on information for sharing a frequency band, or for performing unlicensed communication with a second network based on information for sharing a frequency band.

[0017] The methods described herein, UEs, and some examples of nontransitory computer-readable media may also include operations, features, components, or instructions for: receiving one or more parameters from a second network, the one or more parameters being associated with one or more signaling criteria for adapting a first network to the second network in a frequency band; and sending the one or more parameters to the first network.

[0018] A method performed by a network entity is described. The method may include: obtaining from a UE at a first network a measurement of a signal received at the UE from a second network; and outputting from the first network to the UE information for sharing a frequency band between the first and second networks, wherein the information for sharing the frequency band is based on the measurement of the signal received from the second network.

[0019] A network entity is described. The network entity may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be able to operate individually or jointly to execute code to enable the network entity to: obtain, at a first network, measurements of signals received at the UE from a second network; and output from the first network to the UE information for sharing a frequency band between the first and second networks, wherein the information for sharing the frequency band is based on measurements of signals received from the second network.

[0020] Another network entity is described. This network entity may include: components for obtaining measurements of signals received from a second network at a first network from a UE; and components for outputting information from the first network to the UE for sharing a frequency band between the first and second networks, wherein the information for sharing the frequency band is based on measurements of signals received from the second network.

[0021] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to: obtain, at a first network, measurements of signals received at the UE from a second network; and output from the first network to the UE information for sharing a frequency band between the first and second networks, wherein the information for sharing the frequency band is based on measurements of signals received from the second network.

[0022] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for outputting a configuration from a first network to a UE for the UE to use to measure signals from a second network, wherein the measurement of the signals may be based on the UE's configuration.

[0023] The methods, network entities, and some examples of nontransitory computer-readable media described herein may also include operations, features, components, or instructions for outputting information for sharing a frequency band, including broadcasting information via SIB.

[0024] In some examples of the methods, network entities, and nontransitory computer-readable media described herein, information used for sharing a frequency band includes a certificate associated with a first network, control instructions for freeing up channels in the frequency band, control instructions for reducing transmission power in channels in the frequency band, instructions for time periods for one or more control instructions, instructions for time, an identifier of the first network, or any combination thereof.

[0025] Some examples of the methods, network entities, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining a measurement report from the UE indicating that a channel in a frequency band can be freed up; and interrupting the output of information for sharing the frequency band based on the measurement report.

[0026] Some examples of the methods, network entities, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: obtaining one or more parameters from a UE, which are associated with one or more signaling criteria for adapting a first network to a second network in a frequency band; and communicating via the frequency band based on the one or more parameters.

[0027] A method performed by an AP is described. The method may include: receiving from a UE information for sharing a frequency band between a first network and a second network including the AP; transmitting via the second network the information for sharing the frequency band between the first and second networks; and receiving via the second network a configuration of signaling for the frequency band, the configuration of which is based on the information for sharing the frequency band.

[0028] An access point (AP) is described. The AP may include one or more memories storing processor-executable code and one or more processors coupled to the memories. The one or more processors may be able to operate individually or jointly to execute code to enable the AP to: receive from a UE information for sharing a frequency band between a first network and a second network including the AP; transmit via the second network the information for sharing the frequency band between the first and second networks; and receive via the second network a configuration for signaling for the frequency band, the configuration of which is based on the information for sharing the frequency band.

[0029] Another type of AP is described. This AP may include: components for receiving from a UE information for sharing a frequency band between a first network and a second network including the AP; components for transmitting the information for sharing the frequency band between the first network and the second network via the second network; and components for receiving configuration of signaling for the frequency band via the second network, the configuration of which is based on the information for sharing the frequency band.

[0030] A non-transitory computer-readable medium storing code is described. The code may include instructions executable by one or more processors to: receive from a UE information for sharing a frequency band between a first network and a second network including an AP; transmit via the second network the information for sharing the frequency band between the first and second networks; and receive via the second network configuration of signaling for the frequency band, the configuration of which is based on the information for sharing the frequency band.

[0031] The methods described herein, examples of APs and nontransitory computer-readable media may also include operations, features, components or instructions for avoiding signaling notifications in the channel of a frequency band based on the configuration of signaling for the frequency band.

[0032] The methods described herein, examples of APs and non-transitory computer-readable media may also include operations, features, components or instructions for reducing transmission power used for signaling notification in channels within a frequency band, based on the configuration of signaling for the frequency band.

[0033] The methods described herein, examples of APs and non-transitory computer-readable media may also include operations, features, components or instructions for receiving information for sharing a frequency band, including receiving information in an EBCS uplink frame.

[0034] In some examples of the methods, APs, and nontransitory computer-readable media described herein, information used for sharing a frequency band includes a certificate associated with a first network, control instructions for freeing up channels in the frequency band, control instructions for reducing transmission power in channels in the frequency band, instructions for time periods for one or more control instructions, instructions for time, an identifier of the first network, or any combination thereof.

[0035] In the methods described herein, and in some examples of APs and non-transitory computer-readable media, the configuration of signaling for the frequency band can be formatted according to transport layer security.

[0036] The methods described herein, examples of APs and nontransitory computer-readable media may also include operations, features, components or instructions for: receiving one or more parameters via a second network, the one or more parameters being associated with one or more signaling criteria for adapting a first network to the second network in a frequency band; and sending the one or more parameters to a UE. Attached Figure Description

[0037] Figure 1 An example of a wireless communication system supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown.

[0038] Figure 2An example of a network architecture supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown.

[0039] Figure 3 An example of a wireless communication network supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown.

[0040] Figure 4 An example of a wireless communication system supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown.

[0041] Figure 5 An example of a process flow supporting one or more aspects of this disclosure for sharing a frequency band across multiple networks is shown.

[0042] Figure 6 and Figure 7 A block diagram is shown that supports a device for sharing a frequency band for multiple networks, according to one or more aspects of this disclosure.

[0043] Figure 8 A block diagram is shown that supports a communication manager for a shared frequency band for multiple networks, according to one or more aspects of this disclosure.

[0044] Figure 9 A diagram is shown of a system including devices supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure.

[0045] Figure 10 and Figure 11 A block diagram is shown that supports a device for sharing a frequency band for multiple networks, according to one or more aspects of this disclosure.

[0046] Figure 12 A block diagram is shown that supports a communication manager for a shared frequency band for multiple networks, according to one or more aspects of this disclosure.

[0047] Figure 13 A diagram is shown of a system including devices supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure.

[0048] Figure 14 and Figure 15 A block diagram is shown that supports a device for sharing a frequency band for multiple networks, according to one or more aspects of this disclosure.

[0049] Figure 16 A block diagram is shown that supports a communication manager for a shared frequency band for multiple networks, according to one or more aspects of this disclosure.

[0050] Figure 17A diagram is shown of a system including devices supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure.

[0051] Figures 18 to 23 A flowchart illustrating a method for supporting shared frequency bands for multiple networks according to one or more aspects of this disclosure is shown. Detailed Implementation

[0052] Some wireless devices communicate with multiple networks. For example, user equipment (UE) may communicate with cellular networks and wireless local area networks (WLANs). Different portions of the radio frequency (RF) spectrum may be designated for use by one or more wireless networks (e.g., a combination of different types of networks, such as one or more cellular networks and one or more WLAN networks). A portion of the RF spectrum may be licensed for use by cellular networks, and another portion may be designated for unlicensed use. For example, the higher 6 GHz band (e.g., the 6 GHz band according to the International Mobile Telecommunications (IMT) standard) may be allocated to unlicensed users in certain regions of the world. In some cases, licensed and unlicensed use may occur in the same portion of the RF spectrum or in overlapping portions of the RF spectrum. Some regions (e.g., countries, regions controlled by regulatory bodies, ethnic groups, states, or unions) may allocate the higher portion of the 6 GHz band as unlicensed spectrum for indoor use while simultaneously licensing the same spectrum for outdoor coverage deployments. Therefore, licensed and unlicensed use in the same band may face coexistence problems because one or more signals in the band can interfere with or attenuate one or more other signals in the same band. Some networks may not communicate directly due to different signaling structures.

[0053] Rules, procedures, or techniques for accessing networks occupying the same frequency band can improve access and RF spectrum usage. In some examples of the techniques described herein, the UE can relay information between networks to coordinate spectrum usage in the same frequency band. For example, a cellular network (e.g., a 3GPP network) can provide channel sharing information to the UE. This channel sharing information may include: a request (e.g., from a mobile network operator (MNO)) to another network (e.g., a WLAN) for freeing up one or more channels in a frequency band (e.g., channel switching), the request indicating the time period for freeing up one or more channels; a request to reduce the transmit signal power of one or more channels, the request indicating the time period for reducing the transmit signal power of one or more channels; or other channel sharing information. The UE can use this to relay channels shared with another network.

[0054] In some aspects, channel sharing information can be encoded as 802.11 Enhanced Broadcast Service (EBCS) uplink frames. For example, an EBCS uplink frame may include a Higher Layer Protocol (HLP) payload. An EBCS uplink frame may include a certificate associated with the MNO or network (e.g., a certificate verification). For example, an EBCS uplink frame may be signed with a private key associated with the certificate. A UE (e.g., a non-access point (AP) station (STA)) may include the certificate in the uplink EBCS frame sent to the AP. The EBCS uplink frame may indicate a destination (e.g., to a server or other device). An AP (e.g., which typically relays information from a STA or UE) may relay the HLP to the destination indicated in the frame (e.g., a server) via an associated EBCS agent. The EBCS agent can use the certificate in the uplink frame to verify the signature. For example, an EBCS agent may verify the EBCS uplink frame and forward the HLP payload to the destination. In some examples, the destination may be an authorization server or another device. An authorization server can be a computing device (including one or more processors or one or more memories with instructions) configured to determine whether one or more requests or actions are authorized. In some approaches, the authorization server may instruct whether an action is authorized or control a device (e.g., an access point) to perform an authorization action.

[0055] In some aspects, the authorization server can verify channel sharing requests from the MNO. In some examples, the authorization server may be provided by the broadband service provider or by the MNO. The authorization server may evaluate channel sharing requests from the MNO based on policies or regulations. In some cases, the authorization server may authorize part or all of the request (e.g., authorize the freeing up of one or more channels). The authorization server may transmit the request to the AP to perform an action corresponding to the evaluation result (e.g., an authorization action). In some examples, the request may be protected based on Transport Layer Security (TLS). The request may be processed (e.g., processed by the broadband operator or WLAN operator) and configured at the AP. In some examples, the broadband service provider associated with the network (e.g., WLAN) may have a Service Level Agreement (SLA) with the MNO for channel sharing operations. Some examples of the techniques described herein can be performed in IMT-related processes.

[0056] The aspects of this disclosure are first described in the context of a wireless communication system. The aspects of this disclosure are also illustrated by process flows and described with reference to those process flows. Further aspects of this disclosure are illustrated by apparatus diagrams, system diagrams, and flowcharts relating to a shared frequency band for multiple networks, and described with reference to these diagrams.

[0057] Figure 1An example of a wireless communication system 100 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0058] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, etc. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area where network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0059] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0060] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0061] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0062] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, evolved node B (eNodeB, eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolved node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0063] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, 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, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0064] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) functions and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0065] In a wireless communication system (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0066] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), where the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and may communicate with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0067] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 can provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) can provide a Uu interface for parent IAB node 104 to send signaling notifications to child IAB node 104 or UE 115.

[0068] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0069] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support shared frequency bands for multiple networks as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0070] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0071] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0072] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0073] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0074] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0075] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0076] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0077] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0078] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0079] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0080] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0081] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region (e.g., control resource set (CORESET)) of the physical control channel can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0082] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., using a carrier) to communicate with network entity 105 and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the range of such cells may be from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be a building, a subset of buildings, or external space between or overlapping coverage areas 110, etc., or may include buildings, subsets of buildings, or external space between or overlapping coverage areas, etc.

[0083] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells may be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and may operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a closed subscriber group (CSG), or UE 115 associated with a user in a home or office). Network entity 105 may support one or more cells and may also use one or more component carriers to support communication via one or more cells.

[0084] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0085] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0086] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0087] Some UE 115s (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115s may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0088] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0089] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0090] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0091] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signaling, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0092] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0093] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the area from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) band or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0094] The wireless communication system 100 can also operate using the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0095] Wireless communication system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating with licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0096] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly (such as an antenna tower). In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0097] Network entity 105 or UE 115 may use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique may be referred to as spatial multiplexing. The multiple signals may be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0098] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0099] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 along different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0100] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with the receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 along different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0101] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) along one or more directions, UE 115 may use similar techniques to transmit signals multiple times along different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals along a single direction (e.g., to transmit data to a receiving device).

[0102] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of the antenna array; or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0103] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer can perform packet segmentation and reassembly for transmission via logical channels. The MAC layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can also implement error detection, error correction, or both to support retransmission and improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer can map transport channels to physical channels.

[0104] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0105] Some wireless devices communicate with multiple networks. For example, UE 115 may communicate with a first network (e.g., cellular network, network entity 105, donor base station 140, CU 160, DU 165, RU 170, RIC 175, SMO 180, or core network 130, etc.) and a second network (e.g., reference network 130). Figure 3 The described wireless communication network 300, reference Figure 3 The UE 115 may be referred to as a STA relative to one or more networks (e.g., WLAN). For example, the UE 115 may be as described in the reference... Figure 3The STA 304 is described. A portion of the RF spectrum may be designated for use by a wireless network. A portion of the RF spectrum may be licensed for use by a cellular network, and another portion may be designated for unlicensed use. For example, a higher 6 GHz band (e.g., the 6 GHz band according to IMT standards) may be allocated to unlicensed users in certain regions of the world. In some cases, licensed and unlicensed use may occur in the same portion of the RF spectrum or in overlapping portions of the RF spectrum. Some regions (e.g., countries, regions controlled by regulatory bodies, ethnic groups, states, or unions, etc.) may allocate a higher portion of the 6 GHz band as unlicensed spectrum for indoor use while licensing the same spectrum for outdoor coverage deployment. Therefore, licensed and unlicensed use in the same band may face coexistence problems because one or more signals in the band can interfere with or attenuate one or more other signals in the same band. Some networks may not communicate directly due to different signaling structures.

[0106] Rules, procedures, or techniques for accessing networks occupying the same frequency band can improve access and RF spectrum usage. In some examples of the techniques described herein, UE 115 can relay information between networks (e.g., between a cellular network and a WLAN) to coordinate spectrum usage in the same frequency band. For example, a cellular network (e.g., a 3GPP network, network entity 105, donor base station 140, CU 160, DU 165, RU 170, RIC 175, SMO 180, the channel management function (CMF) entity of the cellular network, or core network 130, etc.) can provide channel sharing information to UE 115. This channel sharing information may include: requests to another network (e.g., wireless communication network 300 or WLAN, etc.) to free up one or more channels in a frequency band; requests to reduce the transmit signal power of one or more channels (e.g., from an MNO); indications of time periods for freeing up channels or reducing the transmit signal power of channels; or other channel sharing information. UE 115 can be used to relay channels shared with another network.

[0107] In some aspects, channel sharing information can be encoded as an 802.11 EBCS uplink frame. For example, an EBCS uplink frame may include an HLP payload. An EBCS uplink frame may include a certificate associated with the MNO or network (e.g., a certificate verification). For example, an EBCS uplink frame may be signed with the private key associated with the certificate. UE 115 (e.g., a non-AP STA) may include the certificate in the data sent to the AP (e.g., for reference purposes). Figure 3The uplink EBCS frame described in AP 302 describes a destination (e.g., to an authorizing server). The AP (e.g., which typically relays information from STAs or UEs) may relay the HLP to the destination (e.g., a server) indicated in the frame via an associated EBCS agent. The EBCS agent may use a certificate in the uplink frame to verify the signature. For example, the EBCS agent may verify the EBCS uplink frame and may forward the HLP payload to the destination (e.g., an authorizing server).

[0108] In some aspects, the authorization server can verify channel sharing requests from the MNO. In some examples, the authorization server may be provided by the broadband service provider or by the MNO. The authorization server may evaluate channel sharing requests from the MNO based on policies or regulations. In some cases, the authorization server may authorize part or all of the request (e.g., authorize the freeing up of one or more channels). The authorization server may transmit the request to the AP to perform an action corresponding to the evaluation result (e.g., an authorization action). In some examples, the request may be protected based on TLS. The request may be processed (e.g., processed by the broadband operator or WLAN operator) and configured at the AP. In some examples, the broadband service provider associated with the network (e.g., WLAN) may have an SLA with the MNO for channel sharing operations. Some examples of the techniques described herein can be performed in IMT-related processes.

[0109] Figure 2 An example of a network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown. Network architecture 200 may exemplify examples of one or more aspects for implementing wireless communication system 100. Network architecture 200 may include one or more CUs 160-a that can communicate directly with core network 130-a via backhaul communication link 120-a, or indirectly with core network 130-a via one or more decomposed network entities 105 (e.g., near-RT RIC 175-b via an E2 link, or a non-RT RIC 175-a associated with SMO 180-a (e.g., an SMO framework), or both). CUs 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). DUs 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with UE 115-a via one or more communication links 125-a. In some implementations, UE 115-a may be served simultaneously by multiple RU 170-a.

[0110] Each network entity in network entity 105 of network architecture 200 (e.g., CU 160-a, DU 165-a, RU170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, Open Cloud (O-Cloud) 205, Open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via wired or wireless transmission media. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to the interfaces of network entity 105 may be configured to communicate with one or more network entities in other network entities 105 via transmission media. For example, network entity 105 may include a wired interface configured to receive signals or transmit signals to one or more network entities in other network entities 105 using a wired transmission medium. Additionally or alternatively, network entity 105 may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals using a wireless transmission medium or to transmit signals to one or more other network entities in network entity 105, or both.

[0111] In some examples, the CU 160-a can host one or more higher-level control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function can be implemented using an interface configured to communicate signaling using other control functions hosted by the CU 160-a. The CU 160-a can be configured to handle user plane functions (e.g., CU-UP), control plane functions (e.g., CU-CP), or combinations thereof. In some examples, the CU 160-a can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 160-a can be implemented to communicate with the DU 165-a for network control and signaling purposes, as needed.

[0112] DU 165-a may correspond to a logic unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RU 170-a. In some examples, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the functional breakdown, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to communicate signals using other layers hosted by DU 165-a or with control functions hosted by CU 160-a.

[0113] In some examples, lower-layer functionality may be implemented by one or more RU 170-a units. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both) based at least in part on functional decomposition (such as lower-layer functional decomposition). In such architectures, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UE 115-a units. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a unit. In some examples, such configurations enable the implementation of DU 165-a and CU160-a units in cloud-based RAN architectures such as vRAN architectures.

[0114] The SMO 180-a can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) to perform network entity lifecycle management (e.g., instantiating virtualized network entities 105) via a cloud computing platform interface (e.g., the O2 interface). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a can (e.g., via the O1 interface) communicate with components configured according to the 4G RAN. Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RU 170-a via the O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0115] The non-RT RIC 175-a can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) or machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 175-b. The non-RT RIC 175-a can be coupled to or communicate with the near-RT RIC 175-b (e.g., via an A1 interface). The near-RT RIC 175-b can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources using data collection and actions on an interface (e.g., via an E2 interface) that connects one or more CU 160-a, one or more DU 165-a, or both, and an O-eNB 210 to the near-RT RIC 175-b.

[0116] In some examples, to generate AI / ML models to be deployed in a near-RT RIC 175-b, a non-RT RIC 175-a may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 175-b and can be received from non-network data sources or network functions at the SMO 180-a or non-RT RIC 175-a. In some examples, the non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, the non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions via the SMO 180-a (e.g., via O1 reconfiguration) or via RAN management policies (e.g., A1 policies).

[0117] Figure 3 Examples of wireless communication networks 300 supporting shared frequency bands for multiple networks are shown according to one or more aspects of this disclosure. According to some aspects, the wireless communication network 300 may be an example of a WLAN (such as a Wi-Fi network). For example, the wireless communication network 300 may be a network implementing at least one of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 wireless communication protocol standard families (such as those defined by the IEEE 802.11-2020 specification or its revisions, including but not limited to 802.11ay, 802.11ax, 802.11az, 802.11ba, 802.11bc, 802.11bd, 802.11be, 802.11bf, and 802.11bn). In some other specific examples, the wireless communication network 300 may be an example of a cellular radio access network (RAN), such as a 5G or 6G RAN implementing one or more cellular protocols (such as those specified in one or more 3GPP standards). In some other examples, the wireless communication network 300 may include a WLAN that operates in an interoperable or converged manner with one or more cellular RANs to provide greater or enhanced network coverage to wireless communication devices within the wireless communication network 300, or to enable such devices to connect to the core of the cellular network, such as to access network management capabilities and functionality provided by the cellular network core.

[0118] The wireless communication network 300 may include numerous wireless communication devices, including at least one wireless access point (AP) 302 and any number of wireless stations (STAs) 304. In some specific implementations, as used herein, the term "wireless device" may refer to either STA 304 or AP 302. Although Figure 3Only one AP 302 is shown, but the wireless communication network 300 may include multiple APs 302. AP 302 can be or represent various different types of network entities, including but not limited to home networking APs, enterprise APs, single-band APs, dual-band synchronous (DBS) APs, tri-band synchronous (TBS) APs, standalone APs, non-standalone APs, software-enabled APs (software APs), and multi-link APs (also known as AP multi-link devices (MLDs)), as well as cellular (such as 3GPP, 4G LTE, 5G, or 6G) base stations or other cellular network nodes (such as Node B, evolved Node B (eNB), gNB, Transmit Receive Point (TRP)) or another type of equipment or apparatus included in the radio access network (RAN), including open RAN (O-RAN) network entities such as central units (CUs), distributed units (DUs), or radio units (RUs).

[0119] Each STA 304 may also be referred to as a mobile station (MS), mobile device, mobile phone, wireless phone, access terminal (AT), user equipment (UE), subscriber station (SS), or subscriber unit, etc. STA 304 can represent a variety of devices such as mobile phones, other handheld or wearable communication devices, netbooks, laptops, tablets, laptops, Chromebooks, augmented reality (AR), virtual reality (VR), mixed reality (MR), or extended reality (XR) wireless headsets or other peripherals, wireless earbuds, other wearable devices, display devices (e.g., televisions, computer monitors, or video game consoles), video game controllers, navigation systems, music or other audio or stereo devices, remote control devices, printers, kitchen appliances (including smart refrigerators) or other household appliances, remote keys (e.g., for passive keyless entry and start (PKES) systems), Internet of Things (IoT) devices, vehicles, etc.

[0120] A single AP 302 and its associated set of STA 304s may be referred to as a Basic Service Set (BSS), which is managed by the corresponding AP 302. Figure 3Additionally, an example coverage area 308 of AP 302 is shown, which may represent the Basic Service Area (BSA) of wireless communication network 300. The BSA can be identified by STA 304 and other devices via a Service Set Identifier (SSID) and a Basic Service Set Identifier (BSSID), which may be the Media Access Control (MAC) address of AP 302. AP 302 may periodically broadcast a beacon frame (“beacon”) including the BSSID to enable any STA 304 within the wireless range of AP 302 to “associate” or reassociate with AP 302 to establish or maintain a corresponding communication link 306 (also referred to hereinafter as a “Wi-Fi link”) with AP 302. For example, the beacon may include an identifier or indication of the primary channel used by the corresponding AP 302, and a Timing Synchronization Function (TSF) for establishing or maintaining timing synchronization with AP 302. AP 302 can provide access to external networks to each STA 304 in the wireless communication network 300 via the corresponding communication link 306.

[0121] To establish a communication link 306 with AP 302, each STA 304 can be configured to perform passive or active scanning operations (“scanning”) on frequency channels in one or more frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, or 60 GHz bands). To perform a passive scan, STA 304 listens for beacons transmitted by the corresponding AP 302 at periodic time intervals (referred to as the Target Beacon Transmission Time (TBTT)). To perform an active scan, STA 304 generates probe requests and transmits these requests sequentially on each channel to be scanned, and listens for probe responses from AP 302. Each STA 304 can identify, determine, detect, or select an AP 302 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 306 with the selected AP 302. The selected AP 302 assigns an association identifier (AID) to STA 304 at the end of the association operation, and AP 302 uses the association identifier (AID) to track STA 304.

[0122] As wireless networks become increasingly prevalent, STA 304 may have the opportunity to choose from one of many BSSs within its range or from multiple APs 302 that together form an Extended Service Set (ESS) (comprising multiple connected BSSs). For example, wireless communication network 300 may be connected to a wired or wireless distribution system capable of connecting multiple APs 302 in such an ESS. Therefore, STA 304 may be covered by more than one AP 302 and may be associated with different APs 302 at different times for different transmissions. Additionally, after associating with an AP 302, STA 304 may periodically scan its surroundings to find a more suitable AP 302 to associate with. For example, STA 304 moving relative to its associated AP 302 may perform a "roaming" scan to find another AP 302 with more desirable network characteristics, such as a larger Received Signal Strength Indicator (RSSI) or reduced traffic load.

[0123] In some implementations, STA 304 may form a network without AP 302 or other equipment besides STA 304 itself. An example of such a network is an ad hoc network (or wireless ad hoc network). Ad hoc networks may also be referred to as mesh networks or peer-to-peer (P2P) networks. In some implementations, ad hoc networks may be implemented within a larger network, such as wireless communication network 300. In such examples, while STA 304 may be able to communicate with each other via AP 302 using communication link 306, STA 304 may also communicate directly with each other via direct wireless communication link 310. Additionally, two STA 304 may communicate via direct communication link 310, regardless of whether the two STA 304 are associated with and served by the same AP 302. In such ad hoc systems, one or more STAs among STA 304 may assume the role played by AP 302 in the BSS. Such STA 304 may be referred to as group owner (GO) and may coordinate transmissions within the ad hoc network. Examples of direct wireless communication links 310 include Wi-Fi direct connections, connections established by using Wi-Fi Tunneling Direct Link Establishment (TDLS) links, and other P2P group connections.

[0124] In some networks, AP 302 or STA 304, or both, may support applications associated with high throughput or low latency requirements, or provide lossless audio to one or more other devices. For example, AP 302 or STA 304 may support applications and use cases associated with ultra-low latency (ULL), such as ULL gaming, or streaming lossless audio and video to one or more personal audio devices (such as peripherals) or AR / VR / MR / XR headsets. In scenarios where a user uses two or more peripherals, AP 302 or STA 304 may support extended personal audio networks enabling communication with these two or more peripherals. Additionally, AP 302 and STA 304 may support additional ULL applications with ULL and high throughput requirements, such as cloud-based applications (such as VR cloud gaming).

[0125] As indicated above, in some implementations, AP 302 and STA 304 may operate and communicate according to one or more of the IEEE 802.11 wireless communication protocol family (via the corresponding communication link 306). These standards define WLAN radio and baseband protocols for the physical (PHY) and MAC layers. AP 302 and STA 304 transmit and receive wireless communications to and from each other in the form of PHY Protocol Data Units (PPDUs) (also referred to below as "Wi-Fi communication" or "wireless packets").

[0126] Each PPDU is a composite structure comprising a PHY preamble and a payload in the form of a PHY 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 instances where the PPDU is transmitted using a bound channel or a wideband channel, the preamble field may be copied and transmitted in each of the multiple component channels. The PHY preamble may include both a legacy portion (or "legacy preamble") and a non-legacy portion (or "non-legacy preamble"). The legacy preamble can be used for other purposes such as packet detection, automatic gain control, and channel estimation. The legacy preamble is also typically used to maintain compatibility with legacy equipment. The format, decoding, and information provided in the non-legacy portion of the preamble are associated with the specific IEEE 802.11 wireless communication protocol to be used to transmit the payload.

[0127] AP 302 and STA 304 in the WLAN wireless communication network 300 can transmit PPDUs using unlicensed spectrum, which can be a portion of the spectrum including frequency bands traditionally used by Wi-Fi technologies, such as the 2.4 GHz band, 5 GHz band, 6 GHz band, 45 GHz band, and 60 GHz band. Some specific implementations of AP 302 and STA 304 described herein can also communicate in other frequency bands that can support licensed or unlicensed communication. For example, AP 302 or STA 304, or both, may also be able to communicate using licensed operating frequency bands, where multiple operators may have corresponding licenses to operate in the same or overlapping frequency ranges. Such licensed operating bands may be mapped to or associated with the following frequency ranges: FR1 (410 MHz - 7.125 GHz), FR2 (24.25 GHz - 52.6 GHz), FR3 (7.125 GHz - 24.25 GHz), FR4a or FR4-1 (52.6 GHz - 71 GHz), FR4 (52.6 GHz - 114.25 GHz), and FR5 (114.25 GHz - 300 GHz).

[0128] Each of these frequency bands can include multiple subbands and frequency channels (also referred to as subchannels). For example, PPDUs conforming to revisions of the IEEE 802.11n, 802.11ac, 802.11ax, 802.11bc, 802.11be, and 802.11bn standards can be transmitted using one or more of the 2.4 GHz, 5 GHz, or 6 GHz frequency bands, each of which is divided into multiple 20 MHz channels. Therefore, these PPDUs are transmitted using physical channels with a minimum bandwidth of 20 MHz, but larger channels can be formed through channel bonding. For example, PPDUs can be transmitted using physical channels with bandwidths of 40 MHz, 80 MHz, 160 MHz, 240 MHz, 320 MHz, 480 MHz, or 640 MHz by bonding multiple 20 MHz channels together.

[0129] Figure 4 An example of a wireless communication system 400 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown. The wireless communication system 400 may include a first network 440 and a second network 445. In some examples, one or more of the wireless communication systems 400 may implement aspects of wireless communication system 100, network architecture 200, or wireless communication network 300. In some aspects, the first network 440 may be an example of wireless communication system 100, or the second network 445 may be an example of wireless communication network 300.

[0130] The first network 440 may include network entity 470-a. Network entity 470-a may provide communication services within cell area 410. In some examples, the first network 440 may be a cellular network (e.g., a 3GPP network). The first network 440 may include UE 475-a, or may provide communication services to UE 475-a. For example, network entity 470-a may communicate with UE 475-a via first communication resource 425 (e.g., send signals to or receive signals from the UE). The first communication resource 425 may include one or more resources for signaling (e.g., time, frequency, or spatial resources). Examples of the first communication resource 425 may include a broadcast channel, control channel, shared channel, data channel, uplink channel, downlink channel, random access channel, another channel, or any combination thereof. The first communication resource 425 between UE 475-a and network entity 470-a may be related to... Figure 1 An example of the described communication link 125. In some examples, network entity 470-a may output (e.g., transmit) one or more signals or information described herein via physical layer signaling or higher layer signaling (e.g., RRC signaling or system information signaling, etc.). References Figure 1 or Figure 2 Network entity 470-a can be an example of network entity 105, RU 170-a, DU 165-a, CU 160-a, CMF entity, or a combination thereof. In some examples, the functionality of network entity 470-a can be split or combined among entities (e.g., RU, DU, CU, or CMF entities).

[0131] The second network 445 may include AP 485-a. AP 485-a may provide communication services within coverage area 405. In some examples, the second network 445 may include UE 475-a, or may provide communication services to UE 475-a. For example, AP 485-a may communicate with UE 475-a via second communication resource 455 (e.g., send signals to or receive signals from the UE). Second communication resource 455 may include one or more resources for signaling (e.g., time, frequency, or spatial resources). Examples of second communication resource 425 may include broadcast channels, control channels, shared channels, data channels, uplink channels, downlink channels, random access channels, another channel, or any combination thereof. The second communication resource 455 between UE 475-a and AP 485-a may be related to... Figure 3 The described communication link 306 is an example. AP 485-a can be used as a reference. Figure 3 An example of the described AP302. For example, the second network 445 could be a WLAN (e.g., a Wi-Fi network).

[0132] UE 475-a can be a reference Figure 1 The described UE 115, reference Figure 2 The UE 115-a described, or referenced Figure 3 Examples of STA 304 or combinations thereof described. In some cases, UE 475-a may be located in cell area 410 and coverage area 405. In some examples, cell area 410 may be located in coverage area 405, cell area 410 may partially overlap with coverage area 405, or cell area 410 may be located in coverage area 405.

[0133] A second network 445 (e.g., AP 485-a) may send signal 415 to UE 475-a. In some respects, signal 415 may be a beacon (e.g., a Wi-Fi beacon transmitted from AP 485-a), a broadcast signal, a synchronization signal, other signals, or any combination thereof.

[0134] UE 475-a can receive signal 415. In some respects, UE 475-a can detect one or more measurements based on signal 415. For example, UE 475-a can perform one or more measurements based on signal 415 (e.g., signal strength measurement, Received Signal Strength Indicator (RSSI), Signal-to-Noise Ratio (SNR), etc.).

[0135] UE 475-a may send a measurement 420 of a signal 415 received from the second network 445 to the first network 440 (e.g., network entity 470-a). For example, UE 475-a may report measurement 420 (e.g., a measurement of a Wi-Fi beacon from AP 485-a) to the first network 440. Measurement 420 may be included in a measurement report, or it may be a measurement report itself.

[0136] In some methods, a first network 440 (e.g., network entity 470-a) may output a configuration for UE 475-a to use for measuring signal 415 from a second network 445 (e.g., before receiving or measuring signal 415). For example, UE 475-a may receive (e.g., via RRC signaling) the configuration for UE 475-a to use for measuring signal 415 received from the second network 445. The measurement of signal 415 may be based on the configuration of UE 475-a. For example, UE 475-a may receive signal 415 from the second network 445 to generate a measurement of signal 415 from the second network 445 using the configuration received from the first network 440. In some examples, the configuration may indicate instructions for UE 475-a to measure signal 415, the frequency range in which the measurement is performed, or other information for configuring UE 475-a to measure signal 415. For example, the configuration may be a Wi-Fi measurement configuration.

[0137] In some examples, network 440 may include one or more nodes or entities for configuring UE 475-a to measure signal 415. For example, a CMF entity may configure UE 475-a to measure Wi-Fi signals, where CMF is a 3GPP system network function. In some examples, an Operations, Administration and Maintenance (OAM) node may act as a CMF. OAM may configure a Radio Access Network (RAN) node. The RAN node may configure UE 475-a to perform measurements via RRC signaling. UE 475-a may measure signal 415 (e.g., one or more Wi-Fi signals) and report the measurement 420 to the CMF entity or the RAN node.

[0138] Network entity 470-a can obtain, at the first network 440, a measurement 420 of signal 415 received at the second network 445 from UE 475-a. Network entity 470-a (e.g., a RAN node or CMF entity, etc.) can determine information 430 for sharing a frequency band based on the measurement 420 of signal 415 received from the second network 445. The frequency band can be a frequency band in which the first network 440 and the second network 445 can signal notification (e.g., a partially or completely overlapping frequency band). For example, the frequency band may include a 6 GHz band or another frequency band. While some examples of the technique are described herein with reference to the 6 GHz band, some examples of this technique can also be applied to other frequency bands in which multiple networks can signal notification.

[0139] In some methods, determining information 430 may include determining whether measurement 420 indicates that the second network 445 is communicating (e.g., transmitting or receiving) in one or more channels of a frequency band (e.g., in one or more channels of a frequency band utilized by the first network 440). The first network 440 (e.g., network entity 470-a) may determine one or more channels to request the second network 445 to vacate or reduce transmission power. For example, if network entity 470-a determines that the second network 445 is signaling in one or more channels currently utilized (or expected to be utilized by network entity 470-a), network entity 470-a may generate information 430 corresponding to one or more channels. In some examples, information 430 may indicate Wi-Fi channel configuration.

[0140] In some methods, determining information 430 may include determining a time period for freeing up one or more channels or for reducing transmission power in one or more channels. For example, network entity 470-a may have scheduled communication in one or more channels (e.g., conflicting channels), and the time period may indicate a target time period for completing the scheduled communication or a time period before resuming a request to free up or reduce transmission power.

[0141] In some methods, determining information 430 may include generating a certificate or signing a certificate. For example, network entity 470-a may generate a certificate associated with the first network 440, or may sign a certificate associated with the first network 440.

[0142] In some examples, the information 430 for sharing a frequency band may include: a certificate associated with the first network 440, control instructions for freeing up a channel in the frequency band (e.g., switching channels), control instructions for reducing transmission power in a channel of the frequency band, instructions for a time period for one or more control instructions, instructions for time, an identifier of the first network 440, a destination address (e.g., the destination address of an authorization server, such as an Internet Protocol (IP) address), or any combination thereof. The identifier of the first network 440 may indicate the identity of network entity 470-a (e.g., a request MNO associated with the first network 440). For example, the identifier of the first network 440 may be a RAN node identifier (e.g., a New Radio Cell Global Identity (NCGI)). In some methods, the identifier of the first network 440 may be used to combat relay attacks.

[0143] In some respects, a certificate can be a verification certificate based on public-key cryptography. For example, a first network 440 (e.g., an entity of the first network) can provide an identity indicative of the first network 440 or a certificate (e.g., an MNO) associated with the first network 440. In some examples, the first network 440 (e.g., a RAN node) can generate channel sharing information 430 and can sign the channel sharing information 430. For example, the first network 440 (e.g., network entity 470-a of the first network 440) can use the private key associated with the first network 440 to sign the certificate.

[0144] In some aspects, information 430 may include control instructions for freeing up channels in the frequency band. For example, the control instructions for freeing up channels may request or instruct the second network 445 to avoid using one or more channels in the frequency band (e.g., transmitting within its frequency range). The instructions may identify a channel or indicate a request or command to free up a channel. A channel may be a channel corresponding to the second network 445, a channel corresponding to the first network 440, one or more channels of the second network 445 overlapping with channels of the first network 440, one or more channels of the first network 440 overlapping with channels of the second network 445, or any combination thereof. One or more channels may include one or more sub-bands within the frequency band.

[0145] In some aspects, information 430 may include control indications for reducing the transmission power in channels of a frequency band. For example, the control indications for reducing the transmission power in a channel may request or command the second network 445 to reduce the transmission power in one or more channels of a frequency band. The indications may identify the channel or indicate the amount of transmission power reduction for the channel.

[0146] In some examples, the information 430 for sharing a frequency band may include an indication of a time period for one or more control indications. The indication of the time period may be associated with one or more control indications. For example, information 430 may include: an indication of one or more time periods for freeing up one or more channels, or an indication of one or more time periods for reducing transmission power in one or more channels, or any combination thereof. The time period may indicate the period during which one or more control indications are effective.

[0147] In some examples, the information 430 used for sharing the frequency band may include a time indication. The time indication may indicate Coordinated Universal Time (UTC), a timestamp in a beacon frame, or another time. In some methods, the time indication can be used to counter replay attacks.

[0148] Network entity 470-a may output (e.g., transmit) information 430 from first network 440 to UE 475-a for sharing a frequency band between first network 440 and second network 445. For example, a RAN node or CMF entity may transmit the determined information 430 to UE 475-a. In some methods, network entity 470-a may broadcast information 430 via one or more System Information Blocks (SIBs). For example, network entity 470-a (e.g., a RAN node) may broadcast information 430 (e.g., signature information for sharing a frequency band) via an SIB.

[0149] UE 475-a may receive information 430 from a first network 440 for sharing a frequency band between the first network 440 and a second network 445. The information 430 for sharing the frequency band may be based on a measurement 420 of a signal 415 received from the second network 445, as described herein. In some examples, UE 475-a may receive the information 430 for sharing the frequency band from a broadcast via an SIB.

[0150] UE 475-a can send information 435 to the second network 445 for sharing a frequency band between the first network 440 and the second network 445. For example, UE 475-a can forward the information 435 for sharing the frequency band to AP 485-a (e.g., Wi-Fi AP).

[0151] In some examples, UE 475-a may transmit information 435 in an EBCS uplink frame. For example, UE 475-a may encode information 435 for sharing a frequency band into an 802.11 EBCS uplink frame. UE 475-a (e.g., reading an SIB message) may forward the EBCS uplink frame to AP 485-a. The EBCS uplink frame may include an HLP payload. In some aspects, the EBCS uplink frame may include a certificate (e.g., an MNO certificate). For example, the EBCS uplink frame may be signed with a private key associated with the certificate (e.g., a certificate associated with the first network 440 or an MNO). In some methods, the certificate may be used to enable information 435 to be sent to AP 485-a without establishing a connection with AP 485-a. For example, UE 475-a can broadcast information 435 without associating with AP 485-a (e.g., without explicitly joining the second network 445 or requesting resources for communicating with AP 485-a). In some examples, EBCS uplink frames can be sent to the authorization server ( Figure 4 (Not shown in the image) indicates the destination (e.g., the destination address).

[0152] The second network 445 (e.g., AP 485-a) may receive information 435 from UE 475-a for sharing a frequency band between the first network 440 and the second network 445. In some examples, AP 485-a may receive information 435 for sharing a frequency band in an EBCS uplink frame.

[0153] AP 485-a can transmit information 435 for sharing a frequency band between the first network 440 and the second network 445 via a second network 445. In some examples, AP 485-a can send information 435 to a proxy device or a destination device (e.g., an authorization server). The proxy device can be a computing device (including one or more processors or one or more memories with instructions) configured to authenticate or authenticate the sender of the information. For example, AP 485-a can transmit information via an associated EBCS proxy ( Figure 4 (Not shown in the image) to relay or forward the HLP payload to the destination device (e.g., a server) indicated in the EBCS frame. In some methods, the AP 485-a and the destination device may communicate (e.g., send or receive information) via a secure link. For example, information 435 may be communicated via a secure link between the AP 485-a and the destination device. In some examples, an SLA for band-sharing operation may exist between the operator of the AP 485-a and the operator of the destination device (e.g., an authorization server).

[0154] A proxy device (e.g., an EBCS proxy) can verify information 435, EBCS uplink frames, or a combination thereof. In some methods, certificate verification and EBCS frame verification can be separate or distinct. For example, the proxy device can verify the certificate indicated in information 435 (e.g., the certificate included in the EBCS frame can be verified first). In some methods, the certificate can be verified based on a root certificate authority (CA) certificate or a supplied (e.g., a previously supplied) MNO certificate. The proxy device (e.g., an EBCS proxy) can use the certificate included in the EBCS uplink frame to verify the EBCS frame (e.g., after verifying information 435). In some examples, the proxy device can use the certificate associated with the first network 440 and included in the EBCS frame to verify the signature information. If the signature information is successfully verified using the public key, operation can continue.

[0155] The proxy device may transmit information 435 to the destination device (e.g., a server). For example, the proxy device may forward the HLP payload to the authorization server. The authorization server may evaluate (e.g., verify) the information 435 from the first network 440 (e.g., a channel sharing request from an MNO associated with the first network 440). In some examples, the authorization server may be operated by a broadband service provider, an MNO, or a combination thereof. The broadband service provider associated with the second network may enter into an SLA with the MNO associated with the first network 440 for band-sharing operations. For example, the SLA may indicate (e.g., control) whether or how the first network 440 and the second network 445 can share a band (e.g., manage one or more channels of the band).

[0156] In some examples, the authorization server may evaluate information 435. For example, the authorization server may determine whether to permit one or more control instructions based on one or more rules (e.g., one or more rules based on SLAs, policies, applicable laws, or applicable regulations). For example, the authorization server may determine whether to grant or deny one or more control instructions based on one or more rules (e.g., based on whether band sharing is permitted based on one or more policies, one or more laws, one or more regulations, one or more SLAs, or any combination thereof).

[0157] In some cases, the authorization server may determine the configuration of signaling for a frequency band. The signaling configuration may indicate the configuration for AP 485-a to use for signaling notification within the frequency band. The signaling configuration may be determined based on information 435 (e.g., one or more control indications) or one or more rules. For example, the signaling configuration may request or instruct (e.g., command) AP485-a to free up one or more channels in the frequency band for a period of time or to reduce the transmission power in one or more channels in the frequency band for a period of time, based on one or more rules and one or more control indications. In some examples, the signaling configuration may be used to configure AP 485-a to provide signaling notification to the extent permitted by one or more rules. In some cases, the authorization server may determine the configuration of signaling for one or more control indications (e.g., requests for all or part of them) in the authorization control indications. For example, the signaling configuration may indicate one or more authorization control indications within one or more associated time periods (or portions of one or more associated time periods) indicated by information 435. In some cases, if one or more control instructions are prohibited by one or more rules (e.g., prohibited by policies, SLAs, laws, regulations, or any combination thereof), the authorization server may reject one or more control instructions.

[0158] The authorization server can transmit signaling configurations to one or more APs (e.g., to AP 485-a, or to one or more downstream APs). For example, the signaling configurations can be used to concurrently configure AP 485-a or multiple APs. AP 485-a can receive signaling configurations for a frequency band via a second network 445 (e.g., from the authorization server). The signaling configurations can be based on information 435 for sharing a frequency band as described herein. In some aspects, the signaling configurations for a frequency band can be formatted according to TLS (e.g., protected based on TLS). In some examples, one or more of the functions or operations described with reference to the proxy device or destination device can be performed by AP 485-a (e.g., alternatively performed by it).

[0159] AP 485-a can perform one or more actions (e.g., authorization actions) based on signaling configuration, or can apply signaling configuration. For example, AP 485-a can avoid signaling notification in a channel of a frequency band based on signaling configuration for that band. For example, AP 485-a can free up one or more channels for a period of time based on an assessment performed by an authorization server, according to signaling configuration. In some examples, AP 485-a can reduce the transmission power used for signaling notification in a channel of a frequency band based on signaling configuration for that band. For example, AP 485-a can reduce the transmission power used for signaling notification in one or more channels for a period of time based on an assessment performed by an authorization server, according to signaling configuration. In some methods, the signaling configuration can indicate the amount of transmission power reduction to be performed, and AP 485-a can apply that amount of transmission power reduction. In some examples, the signaling configuration can be applied based on a time period (e.g., a time period requested by an MNO or indicated by a policy). For example, even though the MNO may have requested to free up the channel for two hours, the authorization server may accept one hour based on its policy.

[0160] In some examples, the authorization server or AP 485-a may determine one or more parameters. Alternatively or additionally, one or more parameters may be generated based on signaling configuration. For example, one or more rules (e.g., policies, SLAs, laws, regulations, or any combination thereof) may cause the authorization server of AP 485-a to reject one or more control instructions in a control instruction or generate one or more parameters. These one or more parameters may be associated with one or more signaling criteria for adapting the first network 440 (e.g., network entity 470-a) to the second network 445 in a frequency band. For example, these one or more signaling criteria may indicate that the first network (e.g., network entity 470-a) may include, or may be based on, one or more rules that indicate that the first network 440 is adaptable to the second network 445. In some cases, the parameters may indicate a request, instruction, or command for the first network (e.g., network entity 470-a) to free up one or more channels or reduce the transmit power in one or more channels.

[0161] In some methods, the authorization server may use information 435 for sharing the frequency band (e.g., EBCS uplink frames) to generate an interference map. The interference map may represent one or more channels in which collisions may occur (e.g., one or more channels in the frequency band targeted by communication between the first network 440 and the second network 445). In some examples, the interference map may have associated expiration periods (e.g., seconds, minutes, hours, days, or months). One or more parameters may be updated based on one or more rules (e.g., policies, laws, regulations, or SLAs). In some examples, one or more rules may be applied to generate signaling configurations or parameters based on estimates of traffic (e.g., traffic estimated based on artificial intelligence, machine learning, or another technology).

[0162] In some examples, AP 485-a may receive one or more parameters via a second network 445. These parameters may be associated with one or more signaling criteria used by the first network 440 to adapt to the second network 445 in a frequency band, as described herein. AP 485-a may send one or more parameters to UE 475-a. UE 475-a may receive one or more parameters from the second network 445. UE 475-a may send one or more parameters to the first network 440 (e.g., network entity 470-a).

[0163] A first network 440 (e.g., network entity 470-a) may obtain one or more parameters from UE 475-a. In some cases, the first network (e.g., network entity 470-a) may communicate via a frequency band based on one or more parameters. For example, based on one or more parameters, network entity 470-a may free up one or more channels in the frequency band, or may reduce the transmission power in one or more channels of the frequency band. In some cases, the first network 440 (e.g., network entity 470-a) may reject one or more parameters based on one or more conditions (e.g., policies, SLAs, laws, regulations, etc.).

[0164] In some examples, UE 475-a may perform licensed communication with the first network 440 based on information used for sharing the frequency band, or it may perform unlicensed communication with the second network 445 based on the same information. For example, UE 475-a may communicate with network entity 470-a via one or more channels vacated (or signaled by AP 485-a at reduced power). Additionally or alternatively, UE 475-a may communicate with network entity 470-a via one or more channels vacated (or signaled by AP 485-a at reduced power).

[0165] In some aspects, the first network (e.g., network entity 470-a) may obtain measurement reports from UE 475-a indicating that a channel in a frequency band has been freed up. UE 475-a may periodically or intermittently send one or more signal measurements to the first network 440 (e.g., network entity 470-a), wherein such signal measurements are associated with the second network 445 (e.g., AP 485-a). For example, after measurement 420 of signal 415, UE 475-a may send one or more measurement reports. These measurement reports may indicate whether the second network 445 has freed up one or more channels, or whether it has reduced the transmission power in one or more channels (e.g., relative to an earlier signal measurement).

[0166] A first network 440 (e.g., network entity 470-a) may interrupt the output of information 430 for sharing a frequency band, at least in part, based on measurement reports. For example, network entity 470-a may send (e.g., broadcast) information 430 for sharing a frequency band intermittently or periodically. Network entity 470-a may interrupt the output of information 430 if a measurement report indicates that a second network 445 (e.g., AP 485-a) has freed up or reduced the transmit power of one or more channels (e.g., according to information 430). For example, if one or more APs (e.g., AP 485-a) have applied a band-sharing request (e.g., by freeing up a channel or performing a transmit power reduction), the RAN node may stop broadcasting an SIB including information 430, where the application of the band-sharing request may be identified based on one or more UE 475-a measurement reports. In some methods, one or more measurements from the second network 445 (e.g., a Wi-Fi network or AP 485-a) may be optional.

[0167] In some examples, network entity 470-a can be configured to periodically send EBCS uplink frames. For example, network entity 470-a can send one or more messages to UE 475-a to configure UE 475-a to periodically send EBCS frames.

[0168] Figure 5 An example of a process flow 500 supporting a shared frequency band for multiple networks according to one or more aspects of this disclosure is shown. Process flow 500 may include UE 475-b, which may be an example of one or more of UE 115, UE 115-a, STA 304, or UE 475-a, as described herein. Process flow 500 also includes CMF entity 470-b, which may be an example of one or more of CU 160, DU 165, RU 170, network entity 105, CU 160-a, DU 165-a, RU 170-a, RAN node, or network entity 470-a, as described herein. CMF entity 470-b may be included in a first network (e.g., a cellular network). Process flow 500 additionally includes AP 485-b, which may be an example of one or more of AP 302 or AP 485-a, as described herein. Process flow 500 may also include agent device 590 and authorization server 595, which may be as described in the reference. Figure 4 Examples of the described agent device and authorization server. AP 485-b, agent device 590, or authorization server 595 may be included in the second network.

[0169] In the following description of process flow 500, signaling or communication between UE 475-b, CMF entity 470-b, AP 485-b, agent device 590, or authorizing server 595 may be sent in a different order than the example order shown, or operations performed by UE 475-b, CMF entity 470-b, AP 485-b, agent device 590, or authorizing server 595 may be performed in a different order or at different times. Some operations in process flow 500 may also be omitted, or additional operations may be added to process flow 500. Furthermore, although some operations or signaling are shown to occur at different times for discussion purposes, these operations may actually occur simultaneously or in some examples within overlapping time periods. In some examples, one or more operations described with reference to different elements may be performed by one element, or one or more operations described with reference to one element may be split into operations performed by multiple elements.

[0170] At 505, CMF entity 470-b can output (e.g., transmit) a configuration for UE 475-b to use for measuring signals from AP 485-b. For example, see reference... Figure 4 The output configuration is as described.

[0171] At position 510, AP 485-a can transmit (or UE 475-b can receive) a signal. For example, UE 475-b can do so as described in the reference. Figure 4 Receive signals as described. The signals can be beacon signals, pilot signals, or data signals, etc.

[0172] At 515, UE 475-b can perform measurements of signals from AP 485-b. For example, UE 475-b can measure (e.g., detect, calculate, or perform operations) one or more characteristics of the signal (e.g., RSSI, SNR), as referenced. Figure 4 As described.

[0173] At position 520, UE 475-b can transmit signal measurements to the CMF entity. For example, UE 475-b can do so as referenced. Figure 4 Send measurements as described.

[0174] At point 525, CMF entity 470-b can determine the information used for sharing the frequency band between the first and second networks. The information for determining the frequency band sharing can be found in the reference... Figure 4 Perform as described.

[0175] At position 530, CMF entity 470-b can output (or UE 475-b can receive) information for sharing the frequency band. For example, CMF entity 470-b can output information for sharing the frequency band, as shown in reference... Figure 4 As described.

[0176] At position 535, UE 475-b can transmit (or AP 485-b can receive) information for sharing the frequency band. For example, UE 475-b can do so as described in reference [reference missing]. Figure 4 Send information as described (e.g., in an EBCS uplink frame).

[0177] At position 540, AP 485-b can send (or proxy device 590 can receive) information for sharing the frequency band. For example, proxy device 590 can do so as described in the reference. Figure 4 Receive information as described.

[0178] At 545, proxy device 590 can verify information or frames. For example, proxy device 590 can verify information used for sharing frequency bands or frames, as referenced. Figure 4 As described. For example, agent device 590 can verify information, EBCS uplink frames, or a combination thereof. In some methods, agent device 590 can perform verification via a certificate included in the verification information (e.g., via public-key cryptography).

[0179] At point 550, agent device 590 can send (or authorized server 595 can receive) information for sharing the frequency band. For example, agent device 590 can do so as described in the reference. Figure 4 Send information as described (e.g., via a second network).

[0180] At point 555, the licensing server 595 can evaluate information used for sharing the frequency band. For example, the licensing server 595 can refer to... Figure 4 The information is evaluated as described. In some aspects, the authorizing server 595 may evaluate the information based on one or more rules (e.g., policies, SLAs, laws, or regulations). For example, the authorizing server 595 may evaluate one or more control instructions in the information based on an SLA between the authorizing server 595 and CMF entity 470-b or an SLA between the authorizing server 595 and AP 485-b. The authorizing server 595 may perform the evaluation to generate a configuration for signaling for AP 485-b or one or more parameters for the first network (e.g., CMF entity 470-b).

[0181] At position 560, the authorization server 595 can send (or AP 485-b can receive) signaling configuration. For example, AP485-b can be configured as follows: Figure 4The AP 485-b is configured to receive signaling as described. In some cases, the AP 485-b may apply signaling configurations. For example, the AP 485-b may free up one or more channels, or may reduce the transmit power of one or more channels as indicated by the signaling configuration. In some methods, the AP 485-b may free up one or more channels for a period of time, or may reduce the transmit power of one or more channels for a period of time indicated by the signaling configuration.

[0182] At point 565, the authorization server 595 can send (or AP 485-b can receive) one or more parameters (e.g., operational parameters of the first network or CMF entity 470-b). For example, AP 485-b can refer to... Figure 4 It receives one or more parameters as described.

[0183] At 570, AP 485-b can send (or UE 475-b can receive) one or more parameters. For example, UE 475-b can, as referenced... Figure 4 It receives one or more parameters as described.

[0184] At 575, UE 475-b can send (or CMF entity 470-b can receive) one or more parameters. For example, CMF entity 470-b can, as referenced... Figure 4 It receives one or more parameters as described. In some aspects, CMF entity 470-b may evaluate one or more parameters based on one or more rules (e.g., policies, SLAs, laws, or regulations). For example, CMF entity 470-b may evaluate one or more parameters based on an SLA between the authorization server 595 and CMF entity 470-b. CMF entity 470-b may perform the evaluation to generate a configuration message for UE 475-b. In some examples, CMF entity 470-b may apply one or more parameters partially or completely. For example, CMF entity 470-b may control the first network to free up one or more channels or reduce the transmit power on one or more channels.

[0185] At 580, CMF entity 470-b may output (e.g., send) a configuration message to UE 475-b to apply one or more parameters. For example, the configuration message may command UE 475-b to vacate a channel, reduce transmit power on a channel, or switch channels (e.g., allocate communication resources on an unvacated channel). In some cases, CMF entity 470-b may reject one or more parameters. For example, the first network may continue operating without applying one or more parameters.

[0186] Figure 6A block diagram 600 illustrates a device 605 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure. Device 605 may be an example of various aspects of UE 115 as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605, or one or more components of device 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described technologies. Each of these components may communicate with each other (e.g., via one or more buses).

[0187] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with shared frequency bands for multiple networks). The information may be passed to other components of device 605. Receiver 610 may utilize a single antenna or a collection of antennas.

[0188] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with shared frequency bands for multiple networks). In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a collection of multiple antennas.

[0189] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of a shared frequency band for multiple networks as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0190] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of the following: a processor, digital signal processor (DSP), central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, microcontroller, discrete gate or transistor logic component, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0191] Additionally or alternatively, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0192] In some examples, the communication manager 620 may be configured to use a receiver 610, a transmitter 615, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated with the receiver 610, the transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0193] For example, the communication manager 620 can be configured or operable to support components for transmitting measurements of signals received from the second network to the first network. The communication manager 620 can be configured or operable to support components for receiving information from the first network for sharing a frequency band between the first and second networks, wherein the information for sharing the frequency band is based on measurements of signals received from the second network. The communication manager 620 can be configured or operable to support components for transmitting information for sharing a frequency band between the first and second networks to the second network.

[0194] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., controlling receiver 610, transmitter 615, communication manager 620 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption or utilizing communication resources more efficiently.

[0195] Figure 7 A block diagram 700 illustrates a device 705 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure. Device 705 may be an example of aspects of device 605 or UE 115 as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705, or one or more components of device 705 (e.g., receiver 710, transmitter 715, and communication manager 720), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0196] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with shared frequency bands for multiple networks). The information may be passed to other components of device 705. Receiver 710 may utilize a single antenna or a collection of multiple antennas.

[0197] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with shared frequency bands for multiple networks). In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a collection of multiple antennas.

[0198] Device 705 or its various components may be examples of parts used to perform various aspects of sharing a frequency band for multiple networks as described herein. For example, communication manager 720 may include signal measurement component 725, frequency band sharing component 730, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use receiver 710, transmitter 715, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0199] Signal measurement component 725 is capable of, configured to, or operable to support components for measuring signals received from a second network and transmitting them to a first network. Band sharing component 730 is capable of, configured to, or operable to support components for receiving information from a first network for sharing a band between the first and second networks, wherein the information for sharing the band is based on measurements of signals received from the second network. Band sharing component 730 is capable of, configured to, or operable to support components for transmitting information to a second network for sharing a band between the first and second networks.

[0200] Figure 8 A block diagram 800 is shown of a communication manager 820 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure. The communication manager 820 may be an example of a communication manager 620, a communication manager 720, or aspects thereof as described herein. The communication manager 820 or its various components may be examples of parts for performing the various aspects of a shared frequency band for multiple networks as described herein. For example, the communication manager 820 may include a signal measurement component 825, a frequency band sharing component 830, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0201] Signal measurement component 825 is capable of, configured to, or operable to support components for transmitting measurements of signals received from a second network to a first network. Band sharing component 830 is capable of, configured to, or operable to support components for receiving information from a first network for sharing a band between the first and second networks, wherein the information for sharing the band is based on measurements of signals received from the second network. In some examples, band sharing component 830 is capable of, configured to, or operable to support components for transmitting information for sharing a band between the first and second networks to a second network.

[0202] In some examples, the signal measurement component 825 is capable of, configured to, or operable to support components for receiving from a first network a configuration for the UE to use to measure signals from a second network. In some examples, the signal measurement component 825 is capable of, configured to, or operable to support components for receiving signals from a second network to generate measurements of signals from the second network using configuration received from the first network.

[0203] In some examples, sending information for sharing a frequency band includes sending information in an uplink frame of the Enhanced Broadcast Service (EBCS).

[0204] In some examples, receiving information for sharing the frequency band includes receiving information from the broadcast via the SIB.

[0205] In some examples, the information used for sharing the frequency band includes a certificate associated with the first network, control instructions for freeing up channels in the frequency band, control instructions for reducing the transmission power in channels in the frequency band, instructions for time periods for one or more control instructions, instructions for time, an identifier of the first network, or any combination thereof.

[0206] In some examples, the band sharing component 830 is capable of, configured to, or operable to support components for performing licensed communication with a first network based on information used for sharing the band, or for performing unlicensed communication with a second network based on information used for sharing the band.

[0207] In some examples, the band sharing component 830 is capable of, configured to, or operable to support components for receiving one or more parameters from a second network, the one or more parameters being associated with one or more signaling criteria for the first network to adapt to the second network in a frequency band. In some examples, the band sharing component 830 is capable of, configured to, or operable to support components for transmitting one or more parameters to the first network.

[0208] Figure 9A diagram of a system 900 including a device 905 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or UE 115 as described herein, or may include components thereof. Device 905 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, an input / output (I / O) controller 910, a transceiver 915, an antenna 925, at least one memory 930, code 935, and at least one processor 940. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 945).

[0209] I / O controller 910 manages the input and output signals of device 905. I / O controller 910 can also manage peripheral devices not integrated into device 905. In some cases, I / O controller 910 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 910 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or another known operating system. Additionally or alternatively, the I / O controller 910 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 910 may be implemented as part of one or more processors, such as at least one processor 940. In some cases, a user may interact with the device 905 via the I / O controller 910 or via hardware components controlled by the I / O controller 910.

[0210] In some cases, device 905 may include a single antenna 925. However, in other cases, device 905 may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 915 may communicate bidirectionally via one or more antennas 925, a wired or wireless link as described herein. For example, transceiver 915 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 915 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 925 for transmission; and demodulating packets received from one or more antennas 925. Transceiver 915, or transceiver 915 and one or more antennas 925, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

[0211] At least one memory 930 may include random access memory (RAM) and read-only memory (ROM). At least one memory 930 may store computer-readable, computer-executable code 935, including instructions that, when executed by at least one processor 940, cause device 905 to perform the various functions described herein. Code 935 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 935 may not be directly executable by at least one processor 940, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 930 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0212] At least one processor 940 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 940 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 940. At least one processor 940 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 930) to cause device 905 to perform various functions (e.g., supporting various functions or tasks for a shared frequency band of multiple networks). For example, device 905 or components of device 905 may include at least one processor 940 and at least one memory 930 coupled to or coupled to at least one processor 940, the at least one processor 940 and at least one memory 930 being configured to perform the various functions described herein. In some examples, at least one processor 940 may include multiple processors, and at least one memory 930 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 940 may be a component of a processing system, which may refer to a system of machines, circuits (including, for example, one or both of processor circuitry (which may include at least one processor 940) and memory circuitry (which may include at least one memory 930)) or components that receive or obtain input and process that input to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 940 or a processing system including at least one processor 940 may be configured, capable of being configured, or operable to cause device 905 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 930 or otherwise.

[0213] For example, the communication manager 920 can be configured or operable to support components for transmitting measurements of signals received from the second network to the first network. The communication manager 920 can be configured or operable to support components for receiving information from the first network for sharing a frequency band between the first and second networks, wherein the information for sharing the frequency band is based on measurements of signals received from the second network. The communication manager 920 can be configured or operable to support components for transmitting information for sharing a frequency band between the first and second networks to the second network.

[0214] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support technologies for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, or increasing processing power.

[0215] In some examples, the communication manager 920 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using a transceiver 915, one or more antennas 925, or any combination thereof, or otherwise cooperating with them. Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by at least one processor 940, at least one memory 930, code 935, or any combination thereof. For example, code 935 may include instructions that can be executed by at least one processor 940 to cause device 905 to perform various aspects of a shared frequency band for multiple networks as described herein, or at least one processor 940 and at least one memory 930 may be otherwise configured to perform or support such operations individually or jointly.

[0216] Figure 10 A block diagram 1000 of a device 1005 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown. Device 1005 may be an example of aspects of network entity 105 as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005, or one or more components of device 1005 (e.g., receiver 1010, transmitter 1015, and communication manager 1020), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0217] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0218] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0219] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of a shared frequency band for multiple networks as described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0220] In some examples, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0221] Additionally or alternatively, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0222] In some examples, the communication manager 1020 may be configured to use the receiver 1010, the transmitter 1015, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or integrate with the receiver 1010, the transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0223] For example, the communication manager 1020 can be configured or operable to support components for obtaining measurements of signals received from the second network at the UE at the first network. The communication manager 1020 can be configured or operable to support components for outputting information from the first network to the UE for sharing a frequency band between the first and second networks, wherein the information for sharing the frequency band is based on measurements of signals received from the second network.

[0224] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 (e.g., controlling receiver 1010, transmitter 1015, communication manager 1020 or a combination thereof or at least one processor otherwise coupled to them) can support techniques for reducing processing, reducing power consumption or utilizing communication resources more efficiently.

[0225] Figure 11 A block diagram 1100 of a device 1105 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown. Device 1105 may be an example of aspects of device 1005 or network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105, or one or more components of device 1105 (e.g., receiver 1110, transmitter 1115, and communication manager 1120), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0226] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0227] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0228] Device 1105 or its various components may be examples of parts used to perform various aspects of sharing a frequency band for multiple networks as described herein. For example, communication manager 1120 may include signal measurement manager 1125, frequency band sharing manager 1130, or any combination thereof. Communication manager 1120 may be examples of aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use receiver 1110, transmitter 1115, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in combination with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0229] Signal measurement manager 1125 is capable of, configured to, or operable to support components for measuring signals received from the UE at the first network and from the second network at the UE. Band sharing manager 1130 is capable of, configured to, or operable to support components for outputting information from the first network to the UE for sharing a band between the first and second networks, wherein the information for sharing the band is based on measurements of signals received from the second network.

[0230] Figure 12A block diagram 1200 is shown of a communication manager 1220 supporting a shared frequency band for multiple networks according to one or more aspects of this disclosure. The communication manager 1220 may be an example of a communication manager 1020, a communication manager 1120, or aspects thereof as described herein. The communication manager 1220 or its various components may be examples of components for performing the various aspects of a shared frequency band for multiple networks as described herein. For example, the communication manager 1220 may include a signal measurement manager 1225, a frequency band sharing manager 1230, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0231] Signal measurement manager 1225 is capable of, configured to, or operable to support components for measuring signals received from the UE at the first network and from the second network at the UE. Band sharing manager 1230 is capable of, configured to, or operable to support components for outputting information from the first network to the UE for sharing a band between the first and second networks, wherein the information for sharing the band is based on measurements of signals received from the second network.

[0232] In some examples, the signal measurement manager 1225 is capable of, configured to, or operable to support components for outputting configurations from a first network to a UE for the UE to use in measuring signals from a second network, wherein the signal measurement is based on the UE's configuration.

[0233] In some examples, the output information used for sharing the frequency band includes broadcasting information via the SIB.

[0234] In some examples, the information used for sharing the frequency band includes a certificate associated with the first network, control instructions for freeing up channels in the frequency band, control instructions for reducing the transmission power in channels in the frequency band, instructions for time periods for one or more control instructions, instructions for time, an identifier of the first network, or any combination thereof.

[0235] In some examples, the signal measurement manager 1225 is capable of, configured to, or operable to support components for obtaining measurement reports from the UE indicating that a channel in a frequency band has been freed up. In some examples, the band sharing manager 1230 is capable of, configured to, or operable to support components for interrupting the output of information for sharing the frequency band based on measurement reports.

[0236] In some examples, the band sharing manager 1230 is capable of, configured to, or operable to support components for obtaining one or more parameters from the UE, which are associated with one or more signaling criteria for adapting a first network to a second network in a band. In some examples, the band sharing manager 1230 is capable of, configured to, or operable to support components for communicating via a band based on one or more parameters.

[0237] Figure 13 A diagram of a system 1300 including a device 1305 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of device 1005, device 1105, or network entity 105 as described herein, or may include components thereof. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, which may include communication using one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1305 may include components supporting output and enabling communication, such as a communication manager 1320, a transceiver 1310, an antenna 1315, at least one memory 1325, code 1330, and at least one processor 1335. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., bus 1340).

[0238] Transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1310 may include a wired transceiver and be capable of bidirectional communication with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1310 may include a wireless transceiver and be capable of bidirectional communication with another wireless transceiver. In some examples, device 1305 may include one or more antennas 1315 that may be capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., by one or more antennas 1315, by a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1310 may include one or more processors or one or more memory components, or be configured to couple to such processors or memory components, which are operable to perform or support operations based on received or acquired information or signals, or generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1310, or transceiver 1310 and one or more antennas 1315, or transceiver 1310 and one or more antennas 1315, and one or more processors or one or more memory components (e.g., at least one processor 1335, at least one memory 1325, or both) may be included in a chip or chip assembly mounted in device 1305. In some examples, transceiver 1310 may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0239] At least one memory 1325 may include RAM, ROM, or any combination thereof. At least one memory 1325 may store computer-readable, computer-executable code 1330 including instructions that, when executed by one or more processors of at least one processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by a processor of at least one processor 1335, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, at least one memory 1325 may also include a BIOS, among other things, that controls basic hardware or software operations, such as interaction with peripheral components or devices. In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein (e.g., as part of a processing system).

[0240] At least one processor 1335 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, at least one processor 1335 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into one or more processors in at least one processor 1335. At least one processor 1335 may be configured to execute computer-readable instructions stored in memory (e.g., one or more memories in at least one memory 1325) to cause device 1305 to perform various functions (e.g., supporting various functions or tasks for a shared frequency band of multiple networks). For example, device 1305 or components of device 1305 may include at least one processor 1335 and at least one memory 1325 coupled to one or more processors in at least one processor 1335, the at least one processor 1335 and the at least one memory 1325 being configured to perform the various functions described herein. At least one processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as an operating system, virtual machine, or container instance) that can (e.g., by executing code 1330) host functions for performing the functions of device 1305. At least one processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305 (such as within one or more memories of at least one memory 1325). In some examples, at least one processor 1335 may include multiple processors, and at least one memory 1325 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 1335 may be a component of a processing system, which can refer to a system that receives or receives input and processes that input to produce, generate, or obtain a set of outputs (such as a series of) machines, circuits (including, for example, one or both of processor circuitry (which may include at least one processor 1335) and memory circuitry (which may include at least one memory 1325)). The processing system may be configured to perform one or more of the functions described herein. For example, at least one processor 1335 or a processing system including at least one processor 1335 may be configured, configured to, or operable to cause the device 1305 to perform one or more of the functions described herein.Furthermore, as described herein, “configured to,” “capable of being configured to,” and “capable of operating to” are used interchangeably and can be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 1325 or otherwise.

[0241] In some examples, bus 1340 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1305, or communication performed between different components of device 1305 that are co-addressable or may be located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, at least one memory 1325, code 1330 and at least one processor 1335 may be located in one component of different components or partitioned between different components).

[0242] In some examples, the communication manager 1320 may manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1320 may manage the delivery of data communications by client devices, such as one or more UEs 115. In some examples, the communication manager 1320 may manage communication with other network entities 105 and may include a controller or scheduler for cooperating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1320 may support an X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0243] For example, the communication manager 1320 can be configured or operable to support components for obtaining measurements of signals received from the second network at the UE at the first network. The communication manager 1320 can be configured or operable to support components for outputting information from the first network to the UE for sharing a frequency band between the first and second networks, wherein the information for sharing the frequency band is based on measurements of signals received from the second network.

[0244] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 can support technologies for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, or increasing processing power.

[0245] In some examples, the communication manager 1320 may be configured to use or otherwise coordinate with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, one or more processors in at least one processor 1335, one or more memories in at least one memory 1325, code 1330, or any combination thereof (e.g., by a processing system including at least a portion of at least one processor 1335, at least one memory 1325, code 1330, or any combination thereof). For example, code 1330 may include instructions that can be executed by one or more processors in at least one processor 1335 to cause the device 1305 to perform various aspects of a shared frequency band for multiple networks as described herein, or at least one processor 1335 and at least one memory 1325 may be otherwise configured to perform or support such operations individually or jointly.

[0246] Figure 14 A block diagram 1400 is shown of a device 1405 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure. Device 1405 may be an example of various aspects of an AP as described herein. Device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. Device 1405, or one or more components of device 1405 (e.g., receiver 1410, transmitter 1415, and communication manager 1420), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0247] Receiver 1410 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with a shared frequency band for multiple networks). The information may be passed to other components of device 1405. Receiver 1410 may utilize a single antenna or a collection of antennas.

[0248] Transmitter 1415 may provide components for transmitting signals generated by other components of device 1405. Transmitter 1415 may utilize a single antenna or a collection of multiple antennas.

[0249] The communication manager 1420, receiver 1410, transmitter 1415, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of a shared frequency band for multiple networks as described herein. For example, the communication manager 1420, receiver 1410, transmitter 1415, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0250] In some examples, the communication manager 1420, receiver 1410, transmitter 1415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., instructions stored in at least one memory are executed individually or collectively by one or more processors).

[0251] Additionally or alternatively, the communication manager 1420, receiver 1410, transmitter 1415, or various combinations or components thereof may be implemented in code (e.g., as communication management software or firmware) executed by at least one processor. If implemented in code executed by at least one processor, the functionality of the communication manager 1420, receiver 1410, transmitter 1415, or various combinations or components thereof may be performed by a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0252] In some examples, the communication manager 1420 may be configured to use a receiver 1410, a transmitter 1415, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1420 may receive information from the receiver 1410, transmit information to the transmitter 1415, or integrate with the receiver 1410, the transmitter 1415, or both to acquire information, output information, or perform various other operations as described herein.

[0253] For example, the communication manager 1420 can be configured or operable to support components for receiving information from the UE for sharing a frequency band between a first network and a second network including an AP. The communication manager 1420 can be configured or operable to support components for transmitting information for sharing a frequency band between the first and second networks via the second network. The communication manager 1420 can be configured or operable to support components for configuring signaling for receiving signaling for a frequency band via the second network, the configuration of which is based on the information for sharing the frequency band.

[0254] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 (e.g., controlling receiver 1410, transmitter 1415, communication manager 1420, or a combination thereof, or at least one processor otherwise coupled to them) can support techniques for reducing processing, lowering power consumption, or utilizing communication resources more efficiently.

[0255] Figure 15 A block diagram 1500 is shown of a device 1505 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure. Device 1505 may be an example of aspects of device 1405 or AP 302 as described herein. Device 1505 may include a receiver 1510, a transmitter 1515, and a communication manager 1520. Device 1505, or one or more components of device 1505 (e.g., receiver 1510, transmitter 1515, and communication manager 1520), may include at least one processor that may be coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0256] Receiver 1510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels associated with a shared frequency band for multiple networks). The information may be passed to other components of device 1505. Receiver 1510 may utilize a single antenna or a collection of antennas.

[0257] Transmitter 1515 may provide components for transmitting signals generated by other components of device 1505. Transmitter 1515 may utilize a single antenna or a collection of multiple antennas.

[0258] Device 1505 or its various components may be examples of parts used to perform various aspects of a shared frequency band for multiple networks as described herein. For example, communication manager 1520 may include information controller 1525 or any combination thereof. Communication manager 1520 may be examples of aspects of communication manager 1420 as described herein. In some examples, communication manager 1520 or its various components may be configured to use receiver 1510, transmitter 1515, or both, or otherwise cooperate with them to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 1520 may receive information from receiver 1510, transmit information to transmitter 1515, or be integrated in combination with receiver 1510, transmitter 1515, or both to acquire information, output information, or perform various other operations as described herein.

[0259] The information controller 1525 is capable of, configured to, or operable to support components for receiving information from the UE for sharing a frequency band between a first network and a second network including an AP. The information controller 1525 is capable of, configured to, or operable to support components for transmitting information for sharing a frequency band between the first and second networks via the second network. The information controller 1525 is capable of, configured to, or operable to support components for configuring signaling for a frequency band via the second network, the configuration of which is based on the information for sharing the frequency band.

[0260] Figure 16 A block diagram 1600 is shown of a communication manager 1620 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure. The communication manager 1620 may be an example of a communication manager 1420, a communication manager 1520, or aspects thereof as described herein. The communication manager 1620 or its various components may be examples of parts for performing the various aspects of a shared frequency band for multiple networks as described herein. For example, the communication manager 1620 may include an information controller 1625, a frequency band sharing controller 1630, or any combination thereof. Each of these components, or its components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses).

[0261] Information controller 1625 is capable of, configured to, or operable to support components for receiving information from the UE for sharing a frequency band between a first network and a second network including an AP. In some examples, information controller 1625 is capable of, configured to, or operable to support components for transmitting information for sharing a frequency band between the first and second networks via the second network. In some examples, information controller 1625 is capable of, configured to, or operable to support components for configuring signaling for a frequency band to be received via the second network, the configuration of which is based on the information for sharing the frequency band.

[0262] In some examples, the band sharing controller 1630 is capable of, configured to, or operable to support components for avoiding signaling notifications in the band's channels based on signaling configuration for the band.

[0263] In some examples, the band sharing controller 1630 is capable of, configured to, or operable to support components for reducing the transmit power used for signaling notification in the channel of the band, based on the configuration for signaling for the band.

[0264] In some examples, receiving information for sharing a frequency band includes receiving information in an uplink frame of the Enhanced Broadcast Service (EBCS).

[0265] In some examples, the information used for sharing the frequency band includes a certificate associated with the first network, control instructions for freeing up channels in the frequency band, control instructions for reducing the transmission power in channels in the frequency band, instructions for time periods for one or more control instructions, instructions for time, an identifier of the first network, or any combination thereof.

[0266] In some examples, the signaling configuration for the frequency band is formatted according to transport layer security.

[0267] In some examples, the information controller 1625 is capable of, configured to, or operable to support components for receiving one or more parameters via a second network, the one or more parameters being associated with one or more signaling criteria for the first network to adapt to the second network in a frequency band. In some examples, the information controller 1625 is capable of, configured to, or operable to support components for transmitting one or more parameters to a UE.

[0268] Figure 17A diagram of a system 1700 including a device 1705 supporting a shared frequency band for multiple networks, according to one or more aspects of this disclosure, is shown. Device 1705 may be an example of device 1405, device 1505, or an AP as described herein, or a component including such devices. Device 1705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1720, a network communication manager 1710, a transceiver 1715, an antenna 1725, at least one memory 1730, code 1735, at least one processor 1740, and an inter-AP communication manager 1745. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1750).

[0269] The network communication manager 1710 can manage (e.g., via one or more wired backhaul links) communication with the core network. For example, the network communication manager 1710 can manage the delivery of data communications by client devices (such as one or more UEs 115 (e.g., STAs)).

[0270] In some cases, device 1705 may include a single antenna 1725. However, in other cases, device 1705 may have more than one antenna 1725, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1715 may communicate bidirectionally via one or more antennas 1725 as described herein, a wired or wireless link. For example, transceiver 1715 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1715 may also include a modem for modulating packets, providing modulated packets to one or more antennas 1725 for transmission, and demodulating packets received from one or more antennas 1725. Transceiver 1715, or transceiver 1715 and one or more antennas 1725, may be an example of transmitter 1415, transmitter 1515, receiver 1410, receiver 1510, or any combination thereof or components thereof as described herein.

[0271] Memory 1730 may include RAM and ROM. Memory 1730 may store computer-readable, computer-executable code 1735 including instructions that, when executed by processor 1740, cause device 1705 to perform the various functions described herein. In some cases, in addition to this, memory 1730 may also contain a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0272] Processor 1740 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1740 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1740. Processor 1740 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1730) to cause device 1705 to perform various functions (e.g., supporting various functions or tasks for a shared frequency band of multiple networks). For example, device 1705 or components of device 1705 may include processor 1740 and memory 1730 coupled to processor 1740, wherein processor 1740 and memory 1730 are configured to perform the various functions described herein.

[0273] Inter-AP communication manager 1745 manages communication with other APs 302 and may include a controller or scheduler for coordinating communication between other APs 302 and UE 115. For example, inter-AP communication manager 1745 may coordinate the scheduling of transmissions to APs 302 for various interference mitigation techniques, such as beamforming or joint transmission. In some examples, inter-AP communication manager 1745 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between APs 302.

[0274] For example, the communication manager 1720 can be configured or operable to support components for receiving information from the UE for sharing a frequency band between a first network and a second network including an AP. The communication manager 1720 can be configured or operable to support components for transmitting information for sharing a frequency band between the first and second networks via the second network. The communication manager 1720 can be configured or operable to support components for configuring signaling for a frequency band to be received via the second network, the configuration of which is based on the information for sharing the frequency band.

[0275] By including or configuring a communication manager 1720 according to an example as described herein, device 1705 can support technologies for improving communication reliability, reducing latency, reducing power consumption, utilizing communication resources more efficiently, improving coordination between devices, extending battery life, or increasing processing power.

[0276] Figure 18 A flowchart illustrating a method 1800 for supporting shared frequency bands for multiple networks, according to one or more aspects of this disclosure, is shown. Operation of method 1800 may be implemented by a UE or its components as described herein. For example, operation of method 1800 may be performed by, as referenced... Figures 1 to 9The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0277] At 1805, the method may include: transmitting to a first network a measurement of a signal received from a second network. The operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1805 may be derived from references... Figure 8 The described signal measurement component 825 is used to perform this.

[0278] At 1810, the method may include: receiving from a first network information for sharing a frequency band between the first network and a second network, wherein the information for sharing the frequency band is based on measurements of signals received from the second network. Operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1810 may be provided by reference to [reference needed]. Figure 8 The described band-sharing component 830 is used to perform this.

[0279] At 1815, the method may include: sending information to a second network for sharing a frequency band between the first network and the second network. The operation of block 1815 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1815 may be derived from references... Figure 8 The described band-sharing component 830 is used to perform this.

[0280] Figure 19 A flowchart illustrating a method 1900 for supporting shared frequency bands for multiple networks, according to one or more aspects of this disclosure, is shown. Operation of method 1900 can be implemented by a UE or its components as described herein. For example, operation of method 1900 can be achieved by, as referenced... Figures 1 to 9 The UE 115 described herein is used to perform this function. In some examples, the UE can execute a set of instructions to control the functional elements of the UE to perform the described function. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the described function.

[0281] At 1905, the method may include: receiving from a first network a configuration for the UE to use to measure signals from a second network. Operation of block 1905 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1905 may be provided by reference to... Figure 8 The described signal measurement component 825 is used to perform this.

[0282] At 1910, the method may include: receiving a signal from a second network to generate a measurement of the signal from the second network using a configuration received from the first network. The operation of block 1910 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1910 may be provided by reference to [reference needed]. Figure 8 The described signal measurement component 825 is used to perform this.

[0283] At 1915, the method may include: transmitting to a first network a measurement of a signal received from a second network. The operation of block 1915 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1915 may be provided by reference to [reference needed]. Figure 8 The described signal measurement component 825 is used to perform this.

[0284] At 1920, the method may include: receiving from a first network information for sharing a frequency band between the first network and a second network, wherein the information for sharing the frequency band is based on measurements of signals received from the second network. The operation of block 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1920 may be provided by reference to [reference needed]. Figure 8 The described band-sharing component 830 is used to perform this.

[0285] At 1925, the method may include: sending information to a second network for sharing a frequency band between the first and second networks. The operation of block 1925 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1925 may be provided by reference to [reference needed]. Figure 8 The described band-sharing component 830 is used to perform this.

[0286] Figure 20 A flowchart illustrating a method 2000 for supporting shared frequency bands for multiple networks, according to one or more aspects of this disclosure, is shown. Operation of method 2000 may be implemented by a network entity or its components as described herein. For example, operation of method 2000 may be performed by, as referenced... Figures 1 to 5 as well as Figures 10 to 13 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0287] At block 2005, the method may include: obtaining from the UE at a first network a measurement of a signal received at the UE from a second network. Operation of block 2005 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2005 may be provided by reference to [reference needed]. Figure 12 The described signal measurement manager 1225 is used to perform this.

[0288] At block 2010, the method may include: outputting information from a first network to the UE for sharing a frequency band between the first network and a second network, wherein the information for sharing the frequency band is based on measurements of signals received from the second network. Operation of block 2010 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2010 may be provided by reference to [reference needed]. Figure 12 The described band sharing manager 1230 is used to execute this.

[0289] Figure 21 A flowchart illustrating a method 2100 for supporting shared frequency bands for multiple networks, according to one or more aspects of this disclosure, is shown. Operation of method 2100 may be implemented by a network entity or its components as described herein. For example, operation of method 2100 may be performed by, as referenced... Figures 1 to 5 as well as Figures 10 to 13 The network entity described is used to perform this function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0290] At 2105, the method may include: outputting a configuration from a first network to a UE for the UE to use in measuring signals from a second network. Operation of block 2105 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2105 may be provided by reference to... Figure 12 The described signal measurement manager 1225 is used to perform this.

[0291] At 2110, the method may include: obtaining from the UE at a first network a measurement of a signal received from the UE at a second network, wherein the signal measurement is based on the UE's configuration. Operation of block 2110 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2110 may be provided by reference to... Figure 12 The described signal measurement manager 1225 is used to perform this.

[0292] At 2115, the method may include: outputting information from a first network to the UE for sharing a frequency band between the first network and a second network, wherein the information for sharing the frequency band is based on measurements of signals received from the second network. Operation of block 2115 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2115 may be derived from references... Figure 12 The described band sharing manager 1230 is used to execute this.

[0293] Figure 22A flowchart illustrating a method 2200 for supporting shared frequency bands for multiple networks, according to one or more aspects of this disclosure, is shown. Operation of method 2200 may be implemented by an AP or its components as described herein. For example, operation of method 2200 may be implemented by, as referenced... Figures 1 to 5 and Figures 14 to 17 The described AP performs this function. In some examples, the AP can execute a set of instructions to control the functional elements of the wireless AP to perform the described function. Additionally or alternatively, the wireless AP may use dedicated hardware to perform aspects of the described function.

[0294] At 2205, the method may include: receiving from the UE information for sharing a frequency band between a first network and a second network including an AP. Operation of block 2205 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2205 may be provided by reference to... Figure 16 The described information controller 1625 performs this action.

[0295] At 2210, the method may include: transmitting information via a second network for sharing a frequency band between the first network and the second network. The operation of block 2210 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2210 may be derived from references... Figure 16 The described information controller 1625 performs this action.

[0296] At 2215, the method may include: receiving configuration of signaling for a frequency band via a second network, the configuration of which is based on information for sharing the frequency band. Operation of block 2215 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2215 may be provided by reference to [reference needed]. Figure 16 The described information controller 1625 performs this action.

[0297] Figure 23 A flowchart illustrating method 2300 for supporting shared frequency bands for multiple networks, according to one or more aspects of this disclosure, is shown. Operation of method 2300 may be implemented by an AP or its components as described herein. For example, operation of method 2300 may be implemented by, as referenced... Figures 1 to 5 and Figures 14 to 17 The described AP performs this function. In some examples, the AP can execute a set of instructions to control the functional elements of the wireless AP to perform the described function. Additionally or alternatively, the wireless AP may use dedicated hardware to perform aspects of the described function.

[0298] At 2305, the method may include: receiving from the UE information for sharing a frequency band between a first network and a second network including an AP. Operation of block 2305 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2305 may be provided by reference to... Figure 16 The described information controller 1625 performs this action.

[0299] At 2310, the method may include: transmitting information via a second network for sharing a frequency band between the first network and the second network. The operation of block 2310 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2310 may be derived from references... Figure 16 The described information controller 1625 performs this action.

[0300] At 2315, the method may include: receiving configuration of signaling for a frequency band via a second network, the configuration of which is based on information for sharing the frequency band. Operation of block 2315 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2315 may be provided by reference to [reference needed]. Figure 16 The described information controller 1625 performs this action.

[0301] At 2320, the method may include: avoiding signaling notification in the channel of the frequency band based on the configuration of signaling for the frequency band. The operation of block 2320 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2320 may be provided by reference to... Figure 16 The described band-sharing controller 1630 is used to perform this.

[0302] The following provides an overview of the various aspects of this disclosure.

[0303] Aspect 1: A method for wireless communication by a UE, the method comprising: transmitting to a first network a measurement of a signal received from a second network; receiving from the first network information for sharing a frequency band between the first network and the second network, wherein the information for sharing the frequency band is at least partially based on the measurement of the signal received from the second network; and transmitting to the second network the information for sharing the frequency band between the first network and the second network.

[0304] Aspect 2: According to the method of aspect 1, the method further includes: receiving from the first network a configuration for the UE to use to measure the signal from the second network; and receiving the signal from the second network to generate the measurement of the signal from the second network using the configuration received from the first network.

[0305] Aspect 3: The method according to any one of Aspects 1 to 2, wherein sending the information for sharing the frequency band comprises: sending the information in an EBCS uplink frame.

[0306] Aspect 4: The method according to any one of Aspects 1 to 3, wherein receiving the information for sharing the frequency band comprises: receiving the information from a broadcast via SIB.

[0307] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the information for sharing the frequency band includes a certificate associated with the first network, a control indication for freeing up a channel in the frequency band, a control indication for reducing the transmission power in a channel of the frequency band, an indication for a time period for one or more control indications, an indication for time, an identifier of the first network, or any combination thereof.

[0308] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: performing licensed communication with the first network based at least in part on the information for sharing the frequency band, or performing unlicensed communication with the second network based at least in part on the information for sharing the frequency band.

[0309] Aspect 7: The method according to any one of Aspects 1 to 6, the method further comprising: receiving one or more parameters from the second network, the one or more parameters being associated with one or more signaling criteria for the first network to adapt to the second network in the frequency band; and transmitting the one or more parameters to the first network.

[0310] Aspect 8: A method for wireless communication by a network entity, the method comprising: obtaining from a UE at a first network a measurement of a signal received from a second network at the UE; and outputting from the first network to the UE information for sharing a frequency band between the first network and the second network, wherein the information for sharing the frequency band is based at least in part on the measurement of the signal received from the second network.

[0311] Aspect 9: The method according to aspect 8, the method further comprising: outputting from the first network to the UE a configuration for the UE to use to measure the signal from the second network, wherein the measurement of the signal is based at least in part on the configuration of the UE.

[0312] Aspect 10: The method according to any one of Aspects 8 to 9, wherein outputting the information for sharing the frequency band comprises: broadcasting the information via SIB.

[0313] Aspect 11: The method according to any one of Aspects 8 to 10, wherein the information for sharing the frequency band includes a certificate associated with the first network, a control indication for freeing up a channel in the frequency band, a control indication for reducing the transmission power in a channel of the frequency band, an indication for a time period for one or more control indications, an indication for time, an identifier of the first network, or any combination thereof.

[0314] Aspect 12: The method according to any one of Aspects 8 to 11, the method further comprising: obtaining from the UE a measurement report indicating that a channel in the frequency band has been freed up; and interrupting the output of the information for sharing the frequency band based at least in part on the measurement report.

[0315] Aspect 13: The method according to any one of Aspects 8 to 12, the method further comprising: obtaining one or more parameters from the UE, the one or more parameters being associated with one or more signaling criteria for the first network to adapt to the second network in the frequency band; and communicating via the frequency band based at least in part on the one or more parameters.

[0316] Aspect 14: A method for wireless communication by an AP, the method comprising: receiving from a UE information for sharing a frequency band between a first network and a second network including the AP; transmitting via the second network the information for sharing the frequency band between the first network and the second network; and receiving via the second network the configuration of signaling for the frequency band, the configuration of the signaling being at least partially based on the information for sharing the frequency band.

[0317] Aspect 15: The method according to aspect 14, the method further comprising: avoiding signaling notification in the channel of the frequency band based at least in part on the configuration of the signaling for the frequency band.

[0318] Aspect 16: The method according to any one of Aspects 14 to 15, the method further comprising: reducing the transmission power for signaling notification in the channel of the frequency band, at least in part based on the configuration of the signaling for the frequency band.

[0319] Aspect 17: The method according to any one of Aspects 14 to 16, wherein receiving the information for sharing the frequency band comprises: receiving the information in an EBCS uplink frame.

[0320] Aspect 18: The method according to any one of Aspects 14 to 17, wherein the information for sharing the frequency band includes a certificate associated with the first network, a control indication for freeing up a channel in the frequency band, a control indication for reducing the transmission power in a channel of the frequency band, an indication for a time period for one or more control indications, an indication for time, an identifier of the first network, or any combination thereof.

[0321] Aspect 19: The method according to any one of Aspects 14 to 18, wherein the configuration of the signaling for the frequency band is formatted according to transport layer security.

[0322] Aspect 20: The method according to any one of aspects 14 to 19, the method further comprising: receiving one or more parameters via the second network, the one or more parameters being associated with one or more signaling criteria for the first network to adapt to the second network in the frequency band; and transmitting the one or more parameters to the UE.

[0323] Aspect 21: A UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to enable the UE to perform a method according to any one of aspects 1 to 7.

[0324] Aspect 22: A UE comprising at least one component for performing the method according to any one of aspects 1 to 7.

[0325] Aspect 23: A non-transitory computer-readable medium storing code, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 1 to 7.

[0326] Aspect 24: A network entity comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the network entity to perform a method according to any one of Aspects 8 to 13.

[0327] Aspect 25: A network entity comprising at least one component for performing the method according to any one of aspects 8 to 13.

[0328] Aspect 26: A non-transitory computer-readable medium storing code, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 8 to 13.

[0329] Aspect 27: An AP comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the UE to perform a method according to any one of Aspects 14 to 20.

[0330] Aspect 28: An AP comprising at least one component for performing the method according to any one of aspects 14 to 20.

[0331] Aspect 29: A non-transitory computer-readable medium storing code, said code comprising instructions executable by one or more processors to perform the method according to any one of aspects 14 to 20.

[0332] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0333] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks outside of LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0334] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0335] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0336] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including various portions distributed such that the functions are implemented in different physical locations.

[0337] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0338] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on". Moreover, as used herein, the phrase "set" should be understood to include the possibility of a set having one member. That is, the phrase "set" should be interpreted in the same manner as "one or more of". As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of the one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0339] The term "determine" encompasses a wide range of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and so on. Moreover, "determine" can include parsing, obtaining, selecting, choosing, creating, and other similar actions.

[0340] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0341] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all implementable or within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0342] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A user equipment (UE), the user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the UE: Measurement of signals received from the second network sent to the first network; Information for sharing a frequency band between the first network and the second network is received from the first network, wherein the information for sharing the frequency band is based at least in part on the measurement of the signal received from the second network; as well as The information for sharing the frequency band between the first network and the second network is sent to the second network.

2. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive configuration from the first network for the UE to use to measure the signal from the second network; and The signal is received from the second network to generate the measurement of the signal from the second network using the configuration received from the first network.

3. The UE according to claim 1, wherein, In order to send the information for sharing the frequency band, the one or more processors can operate individually or jointly to execute the code to cause the UE to send the information in an Enhanced Broadcast Service (EBCS) uplink frame.

4. The UE according to claim 1, wherein, In order to receive the information for sharing the frequency band, the one or more processors are also capable of operating individually or jointly to execute the code so that the UE receives the information from broadcast via a System Information Block (SIB).

5. The UE of claim 1, wherein the information for sharing the frequency band includes a certificate associated with the first network, a control indication for freeing up a channel in the frequency band, a control indication for reducing the transmission power in a channel of the frequency band, an indication for a time period for one or more control indications, an indication for time, an identifier of the first network, or any combination thereof.

6. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Licensed communication with the first network is performed at least in part based on the information used for sharing the frequency band, or unlicensed communication with the second network is performed at least in part based on the information used for sharing the frequency band.

7. The UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the UE to: Receive one or more parameters from the second network, the one or more parameters being associated with one or more signaling criteria for the first network to adapt to the second network in the frequency band; and Send one or more parameters to the first network.

8. A network entity, the network entity comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, coupled to one or more memories and capable of operating individually or jointly to execute the code to enable the network entity: Measurements of signals received from the second network at the user equipment (UE) are obtained at the first network; as well as Information for sharing a frequency band between the first network and the second network is output from the first network to the UE, wherein the information for sharing the frequency band is based at least in part on the measurement of the signal received from the second network.

9. The network entity of claim 8, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: The first network outputs a configuration to the UE for the UE to use to measure the signal from the second network, wherein the measurement of the signal is based at least in part on the UE's configuration.

10. The network entity according to claim 8, wherein, In order to output the information for sharing the frequency band, the one or more processors can operate individually or jointly to execute the code so that the UE broadcasts the information via a System Information Block (SIB).

11. The network entity of claim 8, wherein the information for sharing the frequency band includes a certificate associated with the first network, a control indication for freeing up a channel in the frequency band, a control indication for reducing the transmission power in a channel of the frequency band, an indication for a time period for one or more control indications, an indication for time, an identifier of the first network, or any combination thereof.

12. The network entity of claim 8, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: Obtain from the UE a measurement report indicating that a channel in the frequency band has been freed up; and The output of the information used to share the frequency band is interrupted, at least in part, based on the measurement report.

13. The network entity of claim 8, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the network entity to: One or more parameters are obtained from the UE, the one or more parameters being associated with one or more signaling criteria for the first network to adapt to the second network in the frequency band; and Communication is conducted via the frequency band, at least in part based on one or more of the parameters.

14. An access point (AP), the access point (AP) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, said one or more processors coupled to said one or more memories and capable of operating individually or jointly to execute said code to enable said AP: Receive information from the user equipment (UE) for sharing a frequency band between the first network and a second network including the AP; The information for sharing the frequency band between the first network and the second network is transmitted via the second network; as well as The configuration for receiving signaling for the frequency band via the second network, the configuration of which is at least in part based on the information for sharing the frequency band.

15. The AP of claim 14, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the AP to: Signaling notifications in the channel of the frequency band are avoided, at least in part, based on the configuration of the signaling for the frequency band.

16. The AP of claim 14, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the AP to: The transmission power for signaling notification in the channel of the frequency band is reduced, at least in part, based on the configuration of the signaling for the frequency band.

17. The AP according to claim 14, wherein, In order to receive the information for sharing the frequency band, the one or more processors can operate individually or jointly to execute the code so that the UE receives the information in an Enhanced Broadcast Service (EBCS) uplink frame.

18. The AP of claim 14, wherein the information for sharing the frequency band includes a certificate associated with the first network, a control indication for freeing up a channel in the frequency band, a control indication for reducing the transmission power in a channel in the frequency band, an indication for a time period for one or more control indications, an indication for time, an identifier of the first network, or any combination thereof.

19. The AP of claim 14, wherein the configuration of the signaling for the frequency band is formatted according to transport layer security.

20. The AP of claim 14, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the AP to: Receive one or more parameters via the second network, the one or more parameters being associated with one or more signaling criteria for the first network to adapt to the second network in the frequency band; and Send one or more parameters to the UE.

Images