WO2018044279A1

WO2018044279A1 - Integration of spectrum access system into a cellular network

Info

Publication number: WO2018044279A1
Application number: PCT/US2016/049510
Authority: WO
Inventors: Srikathyayani Srikanteswara; Ana Lucia Pinheiro; Markus Dominik Mueck; Joey Chou
Original assignee: Intel IP Corporation
Priority date: 2016-08-30
Filing date: 2016-08-30
Publication date: 2018-03-08

Abstract

Technology for integrating the spectrum access system (SAS) into a cellular network is disclosed. The SAS can comprise an internal SAS located in the mobile operator domain, wherein the internal SAS can be configured to interface with an external SAS, an Operation, Administration, and Maintenance (OAM) system, and an Environmental Sensing Capability (ESC). The external SAS can also be configured to interface with an internal SAS, an OAM system via the internal SAS, and an ESC. Generally, a spectrum sharing component in a cellular network can comprise an intra-carrier domain entity configured to interface with an extra-carrier domain entity, an operations and management system, and a sensing data component.

Description

INTEGRATION OF SPECTRUM ACCESS SYSTEM INTO A CELLULAR

NETWORK

BACKGROUND

[0001] Fifth generation (5G) communication systems have a goal of providing a lOOOx to 10,000x capacity increase over 4^th Generation (4G) technology. To accomplish this goal, more efficient usage of the spectrum below 6GHz is necessary. However, below 6GHz, spectrum has been fully allocated to incumbents that often oppose proposals to repurpose this spectrum to other stakeholders. The Federal Communications Commission (FCC) has issued an order related to the operation of the Spectrum Access System (SAS) in the U.S. in frequency band 3.55-3.7 GHz. SAS is a system that authorizes and manages use of shared spectrum in the U.S. This system can be important in the further development of spectrum management and spectrum sharing.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Features and advantages of the disclosure will be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the disclosure; and, wherein:

[0003] FIG 1 illustrates the high-level SAS architecture in accordance with an example.

[0004] FIG 2 illustrates the interaction between the internal SAS, as a separate entity, with the NM and other entities in accordance with an example.

[0005] FIG 3 illustrates the interaction between the internal SAS, as a part of the NM, with other entities in accordance with an example.

[0006] FIG 4 illustrates the interaction between the internal SAS, as a separate entity, with the DM and other entities in accordance with an example.

[0007] FIG 5. Illustrates the interaction between the internal SAS, as part of the DM, with other entities in accordance with an example.

[0008] FIG 6 illustrates the interaction between the SAS stub, as a separate entity, with the NM and other entities in accordance with an example.

[0009] FIG 7. Illustrates the interaction between the SAS stub, as part of the NM, with other entities in accordance with an example.

[0010] FIG 8 illustrates the interaction between the SAS stub, as a separate entity, with the DM and other entities in accordance with an example.

[0011] FIG 9 illustrates the interaction between the SAS stub, as part of the DM, with other entities in accordance with an example.

[0012] FIG 10 depicts a flowchart of a machine readable storage medium having instructions embodied thereon for operating an internal SAS in a mobile operator domain in accordance with an example.

[0013] FIG 11 depicts a flowchart of a machine readable storage medium having instructions embodied thereon for operating an external SAS outside a mobile operator domain in accordance with an example.

[0014] FIG 12 depicts a flowchart of a machine readable storage medium having instructions embodied thereon for operating an SAS stub in a mobile operator domain in accordance with an example.

[0015] FIG. 13 illustrates a diagram of a wireless device (e.g., UE) and a node (e.g., eNodeB) in accordance with an example.

[0016] FIG 14 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example.

[0017] Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended.

DETAILED DESCRIPTION

[0018] Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process actions, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.

EXAMPLE EMBODIMENTS

[0019] An initial overview of technology embodiments is provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter.

[0020] The Spectrum Access System (SAS) can be integrated into the 3 GPP (3^rd

Generation Partnership Project) Network. The SAS can be developed so that the desires of both incumbents and commercial users can be met. The incumbents want an SAS that includes interference protection, privacy, and security of data, while the commercial users want the confidentiality of their network information to be preserved. For example, incumbents can include military services using networks operated mainly close to U.S. coastal areas, while commercial users can include Mobile Network Operators providing 3GPP services. The desires of all of these stakeholders can be considered in integrating the SAS into the 3 GPP network.

[0021] The Spectrum Access System (SAS) relates to a system of sharing spectrum in selected frequency bands. For example, the frequency band 3.55-3.7 GHz is currently occupied by incumbents. The incumbents are the existing users. The incumbents can provide the SAS with information relating to their use of the spectrum. In this case, the incumbents are referred to as "Informing Incumbents." Some incumbents, such as military and government users, often do not provide the SAS with this information. These incumbents are known as Non-Informing Incumbents. The Informing Incumbents and Non-Informing Incumbents are generally known as Incumbents and are the current users of the spectrum. These Incumbents can use the spectrum that they have already been using without limitation, and can be provided with interference protection from the other two tiers of users with lower priority.

[0022] The second tier of users is Priority Access Users (PA Users), who are obligated to vacate a spectrum if the Incumbents want to use it. PA Users can include users who obtain a Priority Access License (PAL) which is defined as authorization to use a selected bandwidth, such as a 10 MHz channel, at a specific band. The authorization may be for a selected area and time period, such as in a single Census Tract for three years. A Census Tract is an area that is defined by the amount of population, not geographical size. Other types of areas may be defined by geographic size.

[0023] In one example, PA Users can include Mobile Network Operators providing 3GPP services. It should be noted that the authorization to use a 10MHz channel in a single Census Tract does not indicate a fixed channel; rather, the PAL spectrum can be dynamically re-allocated to take the desires of Incumbents into account. PA Users can be assigned up to a selected amount of bandwidth, such as 70 MHz in a selected band, such as the 3.55 - 3.65 GHz portion of the band.

[0024] PA Users can have protection from the third tier of users, who can be referred to as Generalized Authorized Access Users (GAA Users) in one example. The GAA Users typically do not pay a fee for use of the bandwidth or license the bandwidth. Rather, they are able to use the bandwidth when it is available. The GAA users typically get no interference protection from the Incumbents and the PA Users. GAA Users can include users that typically operate systems defined for industrial, scientific, and medical (ISM) radio bands, such as LTE Licensed Assisted Access (LAA) or Wi-Fi type systems. The GAA users have the lowest priority. If higher priority users, such as PA users or incumbents use the bandwidth, the bandwidth will not be accessible to the GAA users. The GAA users can be assigned a selected amount of bandwidth, such as at least 80MHz of spectrum in a selected band, such as the 3.55-3.70 GHz band.

[0025] FIG 1 illustrates a high-level SAS architecture 100 composed of an SAS entity 102, which can be connected to: (1) FCC databases 112, (2) an Informing Incumbent 108, (3) an Environmental Sensing Capability (ESC) 104, and (4) any other SASs 110. An

Informing Incumbent 108 can provide the SAS 102 with information regarding its use of the band directly to the SAS 102 or via a database to be accommodated by the SAS. If information regarding band use is provided directly to the SAS 102, then the Informing Incumbent 108 can interface directly with the SAS 102. If the information regarding band use is provided via a database, then the SAS 102 can be configured to interface directly with the database, which can be configured to interface either directly or indirectly with the Informing Incumbent 108. The SAS 102 can also be configured to interface indirectly with the database, which can be configured to interface directly or indirectly with the Informing Incumbent 108.

[0026] Some band use cannot be provided to the SAS 102 directly from the incumbent users because the use is critical to Department of Defense radar operations and other military, government, or civilian communication systems. Examples of non-informing incumbent communication can include radar systems that are used for radio-location and radio-navigation services including: fleet air defense, missile and gunfire control, bomb scoring, battlefield weapon location, air traffic control, and range detection. These incumbents that are unwilling to provide information regarding band use to the SAS 102 are in areas referred to as "exclusion or protection zones," which are often located near coastal areas. However, non-coastal areas may also be used. For these areas, an

Environmental Sensing Capability (ESC) 104 is used to provide sensing results regarding these incumbents use of the band. These sensing results can be transmitted from the Sensing Network 106 to the ESC 104. The ESC sensing results can be used to determine the decisions on spectrum access for PA users and GAA users.

[0027] The SAS 102 can also be configured to interface with other SASs 110 in order to coordinate interference across a plurality of networks. The SAS 110 can also interact with a licensee's Public Land Mobile Network (PLMN) in order to support the mapping of availability information into appropriate radio transmitter configurations, and receive the respective confirmations from the PLMN.

[0028] The SAS operates to protect incumbents from PA Users and GAA Users, and to protect PA Users from GAA Users. Because the Non-Informing Incumbents do not provide the SAS with information relating to their use of the spectrum, the FCC has proposed a step-by-step approach for SAS operation. First, the SAS can be operated throughout a selected territory, such as the US territory or another desired territory, except within Exclusion/Protection Zones close to coastal areas. These Exclusion/Protection Zones are where the Non-Informing Incumbents operate, and are a geographical area within which Non-Informing Incumbents will not be subject to harmful interference caused by PA Users or GAA Users.

[0029] Second, an Environmental Sensing Capability (ESC) is added which is used to sense the activity of the Non-Informing Incumbents. The sensing results from the ESC determine the spectrum access decisions for PA Users and GAA Users. The ESC sensing results can be obtained from a sensing network. The sensing network can be configured to detect whether the Non-Informing Incumbents are using a selected band. This sensing network is used because the Non-Informing Incumbents are unwilling to share their secure data with the SAS. These sensing results from the sensing network can be transmitted to the ESC to be transmitted to the SAS. The SAS can propagate decisions on spectrum access to network elements to protect the Non-Informing Incumbents from interference from the PA Users and the GAA Users. When the ESC determines that a selected band is being used by the incumbents, the PA Users and GAA Users will be denied access to the selected band.

[0030] The SAS can be integrated into cellular networks in general and the 3 GPP network in particular. An intra-carrier domain entity can be configured to interface with: an extra carrier domain entity that is configured for interference coordination across a plurality of networks; an operations and management system; and a sensing data component. The intra-carrier domain entity can be configured to determine and send a decision on spectrum access through the operations and management system to other network elements based on information received from the sensing data component and the extra-carrier domain entity.

[0031] The cellular network can be a 3GPP network in releases 8, 9, 10, 11, 12, or beyond. Releases 8, 9, 10, 11, 12 have already been frozen, which means that no further additional functions can be added. Releases 13 and 14 are currently in progress and can still have additional functions added. Releases 13 and beyond of the 3GPP networks can be released in the future.

[0032] To integrate the SAS into the 3 GPP network, an internal SAS located in the mobile operator domain can be configured to interface with: an external SAS, an OAM system, and an ESC. The external SAS is configured for SAS interference coordination across a plurality of networks. The OAM system is the mobile network operator's Operation, Administration, and Maintenance system and can instruct the relevant base stations to enable transmission in the allowed portion of the frequency band. The ESC is configured to obtain sensing data. The internal SAS is configured to determine and send a decision on spectrum access through the OAM system to other network elements based on information received from the ESC and the external SAS.

[0033] The functions of the SAS can be divided into an internal SAS, which is located in the mobile operator domain, and an external SAS, which is located outside of the mobile operator domain. The internal SAS can hide information that is collected that is proprietary to the mobile operator, such as information relating to channel, frequency, band, and the like. The collected information can be hidden from competitors because of the internal SAS's location within the mobile operator domain. The external SAS can be a third-party device that is unrelated to the servicer of the mobile operator domain. In such a case, information provided to the external SAS can be information that can be disclosed to the third party. When an internal SAS provides information to the external SAS, specific details can be aggregated into general information to protect the confidentiality of the information.

[0034] The external SAS can be configured to provide interference coordination across a plurality of networks. This function of the external SAS is amplified because of the way in which spectrum is used by users. In one example, the minimum geographic area that is used by users can be referred to as a Census Tract, which are determined by population size, not geographical size. In densely populated areas the size of a Census Tract can be as small as a few blocks, and will share boundaries with various other Census Tracts. This increases the desire for interference coordination because of the increased possibility of interference between the Census Tracts. The interference that arises from neighboring Census Tracts can come from distinct Mobile Network Operators. Because distinct Mobile Network Operators do not typically share information and coordinate their actions, it can be difficult to use established techniques to reduce the interference between neighboring Census Tracts. Interference coordination can also be used to protect the PA Users from the GAA Users. To achieve this interference coordination, both PA Users and GAA Users can interact with the SAS entities, via their networks, to share information.

[0035] For example, there may be multiple SAS bands that should be split across multiple Mobile Network Operators. To split the SAS band, each Mobile Network Operator can provide information to the external SAS requesting use of a band. The external SAS can allocate the frequencies to the Mobile Network Operators in order to minimize interference. As a second possibility, the internal SAS inside the Mobile Network Operation Domain of a Mobile Network Operator can provide the external SAS with a selected channel by informing the extemal SAS that it desires to use a certain frequency. The external SAS can determine if the selected frequency is occupied and communicate this information to the intemal SAS. This process can also be repeated with a mixture of Mobile Network Operators that select use of a certain frequency and other Mobile Network Operators that request use of a non-specific frequency.

[0036] Integration of the SAS into the 3 GPP network can be accomplished by

interactions involving a Network Manager (NM), a Domain Manager (DM), an Element Manager (EM), and a Network Element (NE). A Network Manager provides a package of functions with the responsibility with management of a network. A Network Manager can by supported by the Element Manager but it may also have direct access to the Network Elements. A Domain Manager provides element management functions and domain management functions for a sub-network. An Element Manager provides a package of functions for management of a set of closely-related types of network elements. A Network Element corresponds to a discrete telecommunications entity, such as the Radio Network Controller (RNC) or an evolved Node B (eNB).

[0037] The internal SAS can be configured to interface with an extemal SAS, an OAM system, and an ESC. The internal SAS, as a separate entity, can be configured to interface with the OAM system at the NM level, the DM level, or the EM level. The internal SAS can also be a part of the NM, the DM, or the EM. In this case, the internal SAS can be exposed directly to interface with the external SAS. Whether the internal SAS is a separate entity or a part of the NM, DM, or EM, the internal SAS can be configured to interface with the FCC databases and the Informing Incumbents.

[0038] In some cases, the internal SAS can be an SAS stub that provides fewer functions than the intemal SAS previously described. The SAS stub can be a separate entity configured to interface with the external SAS or the SAS stub can be located within the NM, DM, or EM, in which case the SAS stub can be exposed directly to interface with the extemal SAS.

[0039] When the intemal SAS is an SAS stub, the extemal SAS can be configured to interface with FCC databases, the ESC, and the Informing Incumbents. The extemal SAS is still configured for SAS interference coordination across a plurality of networks, but can also have additional functions such as: interference coordination of the SAS network and across neighboring SAS networks; providing information on the incumbents accessing or using part of or all of the SAS spectrum; and providing additional information for efficient operation of the entire SAS spectrum. The extemal SAS can also have additional functions that the FCC has promulgated including: information gathering and retention; registration, authentication, and authorization of Citizens Broadband Radio Service Devices (CBSDs); frequency assignment and security; and enforcement.

[0040] A machine readable storage medium having instructions embodied thereon can be used for operating an internal SAS in a mobile operator domain. The instructions when executed can perform any of the following: receiving interference coordination information from an extemal SAS; receiving sensing data from an Environmental Sensing Capability (ESC); determining and sending a decision on spectrum access through an Operation, Administration, and Maintenance (OAM) system to other network elements based on the sensing data received from the ESC and the interference coordination information received from the extemal SAS. This list is not intended to be limiting. Additional functions can also be performed based on the network design.

[0041] A machine readable storage medium having instructions embodied thereon can be used for operating an extemal SAS outside a mobile operator domain. The instructions when executed can perform any of the following: determining interference coordination information; receiving sensing data from an Environmental Sensing Capability (ESC); determining and sending a decision on spectrum access through an Operation,

Administration, and Maintenance (OAM) system via the internal SAS to other network elements based on the interference coordination information and the sensing data received from the ESC. This list is not intended to be limiting. Additional functions can also be performed based on the network design.

[0042] A machine readable storage medium having instructions embodied thereon can be used for operating an SAS stub in a mobile operator domain. The instructions when executed can perform any of the following: report sensing information to an extemal

SAS; determine network changes based on reports of interference from the external SAS; send a command to the NM, DM, or EM to instruct an eNB to start operating or stop operating in a band when instructed by the external SAS; send a command to UEs via the NM, DM, EM, and/or the eNB for the UEs to start operating or stop operating in a band when instructed by the external SAS; obtain a list of channels from the external SAS; manage frequency and power allocations to UEs based on available channels from the external SAS; and aggregate information from the cellular network and send the aggregated information to the external SAS. This list is not intended to be limiting. Additional functions can also be performed based on the network design.

[0043] The spectrum sharing technology can also include a spectrum sharing component operating in a cellular network. This spectrum sharing component can be comprised of an intra-carrier domain entity which is configured to interface with an extra-carrier domain entity, an operations and management system, and a sensing data component. The extra- carrier domain entity is located outside of the carrier domain and is configured for interference coordination across a plurality of networks. The intra-carrier domain entity is located inside the carrier domain and is configured to propagate a decision on spectrum access through the operations and management system to other network elements depending on the information received from the sensing data component and the extra- carrier domain entity.

[0044] The intra-carrier domain entity can be a separate entity that is configured to interface with an NM, a DM, or an EM. Alternatively, the intra-carrier domain entity can be included as a part of the NM, DM, or EM and have an interface that is directly exposed to interface with the extra-carrier domain entity, the operations and management system, and the sensing data component. The intra-carrier domain entity can also be configured to interface with governmental databases and Informing Incumbents.

[0045] The intra-carrier domain entity can also be an intra-carrier domain stub that provides a reduced functionality in comparison to the intra-carrier domain entity. This intra-carrier domain stub can be configured to interface with the extra-carrier domain entity. The extra-carrier domain entity can perform the functions that were previously performed by the intra-carrier domain entity but no longer performed by the intra-carrier domain stub. The extra-carrier domain entity can be configured to interface with governmental databases, the sensing data component, the Informing Incumbents, and the intra-carrier domain stub.

[0046] FIG. 2 illustrates an embodiment 200 showing the interaction between the internal SAS 202 and the Network Manager (NM) 214. An NM 214 provides a package of functions with the responsibility for the management of a network. In this example, the internal SAS 202 can be implemented as a separate entity within the mobile network operator's domain. There are multiple benefits to implementing the internal SAS 202 as a separate entity, such as: (1) the internal SAS 202, which can be certified by a government or civilian entity such as the FCC, can be extracted as a separate entity for certification, (2) independent vendors and SAS providers can provide SAS solutions without the having to engineer the NM 214, and (3) the internal SAS can be extended to perform the functions supporting other spectrum sharing rules from other countries.

[0047] It can be important to be able to extend the internal SAS to be able to perform the functions supporting other spectrum sharing rules from other countries. In Europe, the Licensed Shared Access (LSA) System has been developed to include functionality to enable a coordination of resource usage between incumbents and LSA licensees. As a separate entity, the internal SAS can be extended to perform the functions of an LSA Controller (LC). Furthermore, the internal SAS can also be extended to work with the standards to be formulated by other countries for spectrum sharing.

[0048] According to this example, the internal SAS 202 can be located inside the mobile network operator domain as a separate entity. The internal SAS 202 can interface with (1) an external SAS 210, (2) an ESC 204, (3) an Informing Incumbent 208, (4) the FCC databases 212, and/or (5) the Network Manager 214. The external SAS 210, the ESC 204, the Sensing Network 206, the Informing Incumbent 208, and the FCC databases 212 can all be located outside of the mobile network operator domain. The Network Manager 214 can be located within the mobile network operator domain. The Network Manager can interface with one or more Domain Managers 216, which can each interface with one or more Network Elements 218.

[0049] In one example, the internal SAS 202 can have the following functions:

interference coordination of the SAS network and across neighboring SAS networks; providing information on the incumbents accessing or using part of or all of the SAS spectrum; and providing additional information for efficient operation of the entire SAS spectrum. The internal SAS 202 can also have additional functions that the FCC has promulgated including: information gathering and retention; registration, authentication, and authorization of Citizens Broadband Radio Service Devices (CBSDs); frequency assignment and security; and enforcement.

[0050] FIG. 3 illustrates an embodiment 300 showing the interaction between the internal SAS 302, as part of the NM 314, and other entities including the external SAS 310, the ESC 304, the FCC databases 312, and the Informing Incumbents 308. In this case, the internal SAS 302 can also be certified by a government or civilian agency, such as the FCC. As part of the NM 314, the interface of the internal SAS 302 can still be exposed directly, allowing it to interface with the external SAS 310, the ESC 304, the FCC databases 312, and the Informing Incumbents 308. One advantage of including the internal SAS 302 as part of the NM 314 is that interfaces may not have to be developed from the internal SAS 302 to other network entities within the operator's domain. The only interfaces that may have to be standardized are the interfaces that are external to the operator's domain. The external SAS 310, the ESC 304, the Sensing Network 306, which is configured to interface with the ESC 304, the Informing Incumbent 308, and the FCC databases 312 can all be located outside of the mobile operator domain. The Network Manager 314 can be configured to interface with one or more Domain Managers 316, which can each be configured to interface with one or more Network Elements 318.

[0051] FIG. 4 illustrates an embodiment 400 showing the interaction between the internal SAS 402, as a separate entity, and the Domain Manager (DM) 416. The DM 416 can provide element management functions and domain management functions for a subnetwork. In this example, the internal SAS 402 is implemented as a separate entity within the mobile network operator's domain. The Domain Manager can be configured to interface with the Network Elements 418.

[0052] The internal SAS 402 can be configured to interface with various entities including the external SAS 410, the ESC 404, the FCC databases 412, the Informing Incumbents 408, and the Domain Manager 416. The ESC 404 can further be configured to interface with a sensing network 406 that provides information about incumbents in exclusion or protection zones.

[0053] FIG. 5 illustrates an embodiment 500 showing the interaction between the internal SAS 502, as part of the Domain Manager 516, and various other entities including the external SAS 510, the ESC 504, the FCC databases 512, and the Informing Incumbents 508. The internal SAS 502 is configured to interface with the external SAS 510, the ESC 504, the FCC databases 512, and the Informing Incumbents 508. One advantage of locating the internal SAS 502 in the DM 516 is that interfaces do not have to be developed from the internal SAS 502 to the other network entities within the operator's domain. The only interfaces that would have to be standardized are the interfaces that are external to the operator's domain. The internal SAS 502, even though located in the DM 516, still has an exposed interface allowing it to interface directly with the various entities outside of the operator's domain. The ESC 504 is further configured to interface with a Sensing Network 506 that can provide information about incumbents in exclusion or protection zones. The Domain Manager 516, which include the internal SAS 502, is further configured to interface with one or more Network Elements 518.

[0054] FIG. 6 illustrates an embodiment 600 showing the interaction between the SAS stub 602, as a separate entity from the Network Manager 614, and various other entities, including the external SAS 610. The Network Manager is further configured to interface with one or more Domain Managers 616, which are each configured to interface with one or more Network Elements 618. In this example, the functions of the SAS are split between the external SAS 610 and the SAS stub 602.

[0055] The external SAS 610 can have the following functions: interference coordination of the SAS network and across neighboring SAS networks; providing information on the incumbents accessing or using part of or all of the SAS spectrum; and providing additional information for efficient operation of the entire SAS spectrum. The external SAS 610 can also have additional functions that the FCC has promulgated including: information gathering and retention; registration, authentication, and authorization of

Citizens Broadband Radio Service Devices (CBSDs); frequency assignment and security; and enforcement. The external SAS 610 can be configured to interface with the ESC 604, the FCC databases 612, and the Informing Incumbents 608. All of these entities are located outside of the mobile operator domain. The ESC 604 is further configured to interface with a Sensing Network 606 that provides information about incumbents in exclusion or protection zones. [0056] The SAS stub 602 can perform at least six functions. First, it can report sensing information to the external SAS 610. Second, it can make decisions on network changes if the external SAS 610 reports interference to incumbent or higher tiers in a given area. For example, the power levels or frequencies can be modified. Third, the SAS stub 602 can filter details of the operator's network and provide this aggregated information to the external SAS 610. The details are filtered and the information can be aggregated to protect the confidentiality of proprietary details within the operator's network. Fourth, the SAS stub 602 can stop devices from operating in a band if instructed by the external SAS 610. This instruction can be transmitted from the external SAS 610 to the eNB to stop the eNB from operating in a band, or the instruction can be transmitted from the external SAS 610 to the UE via the eNB to stop the UE from operating in a band. Fifth, the SAS stub 602 can obtain a list of channels that can be used from the external SAS 610. Sixth, the SAS stub 602 can manage frequency and power allocations to its devices, such as UEs.

[0057] FIG. 7 illustrates another embodiment 700 showing the interactions between the SAS stub 702, as part of the Network Manager 714, with the external SAS 710. The Network Manager 714 is further configured to interface with one or more Domain Managers 716, which can each be configured to interface with one or more Network Elements 718. The external SAS 710 can be configured to interface with the ESC 704, the FCC databases 712, and the Informing Incumbents 708. The ESC 704 is further configured to interface with a Sensing Network 706 that provides information about incumbents in exclusion or protection zones. The advantage of locating the SAS stub 702 in the Network Manager 714 is that interfaces do not have to be developed from the SAS stub 702 to the other network entities within the operator's domain. The SAS stub 702, although located in the NM 714, can still have an exposed interface that allows it to directly interface with the external SAS 710.

[0058] FIG. 8 illustrates another embodiment 800 showing the interactions between the SAS stub 802, as a separate entity from the DM 816, with the DM 816 and the external SAS 810. The external SAS 810 can be configured to interface with the ESC 804, the FCC databases 812, and the Informing Incumbents 808. The ESC 804 is further configured to interface with a Sensing Network 806 that provides information about incumbents in exclusion or protection zones. The Domain Manager 816 is further configured to interface with one or more Network Elements 818.

[0059] FIG. 9 illustrates another embodiment 900 showing the interactions between the SAS stub 902, as part of the Domain Manager 916, with the external SAS 910. The external SAS 910 can be configured to interface with the ESC 904, the FCC databases 912, and the Informing Incumbents 908. The advantage of locating the SAS stub 902 within the DM 916 is that interfaces do not have to be developed from the SAS stub 902 to the other network entities within the operator's domain. However, the SAS stub 902 can still have an exposed interface that allows it to interface directly with the external SAS 910. The ESC 904 is further configured to interface with a Sensing Network 906 that provides information about incumbents in exclusion or protection zones. The Domain Manager 916 is further configured to interface with one or more Network Elements 918.

[0060] It should be noted that the embodiments and/or exemplary scenarios described herein may involve devices (including PA user devices for SAS, GAA user devices for SAS, LSA Licensee user devices for LSA, incumbent users for any systems, other mobile devices, and/or other devices) operating and/or arranged to operate according to 3 GPP (Third Generation Partnership Project) specifications, such as Long Term Evolution (LTE) and Long Term Evolution- Advanced (LTE-A) and LTE-Advanced Pro. However, it is understood that such embodiments and/or exemplary scenarios may be similarly applied to other mobile communication technologies and standards, such as any Cellular Wide Area radio communication technology, which may include e.g. a 5th Generation (5G) communication system, a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio

communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology (e.g. UMTS (Universal Mobile Telecommunications System), FOMA (Freedom of Multimedia Access), 3 GPP LTE (Long Term Evolution), 3GPP LTE Advanced (Long Term Evolution Advanced)), 3 GPP LTE-Advanced Pro, CDMA2000 (Code division multiple access 2000), CDPD (Cellular Digital Packet Data), Mobitex, 3G (Third Generation), CSD (Circuit Switched Data), HSCSD (High-Speed Circuit-Switched Data), UMTS (3G) (Universal Mobile Telecommunications System (Third Generation)), W-CDMA (UMTS) (Wideband Code Division Multiple Access (Universal Mobile Telecommunications System)), HSPA (High Speed Packet Access), HSDPA (High-Speed Downlink Packet Access), HSUPA (High-Speed Uplink Packet Access), HSPA+ (High Speed Packet Access Plus), UMTS-TDD (Universal Mobile Telecommunications System - Time-Division Duplex), TD-CDMA (Time Division - Code Division Multiple Access), TD-CDMA (Time Division - Synchronous Code Division Multiple Access), 3 GPP Rel. 8 (Pre-4G) (3rd Generation Partnership Project Release 8 (Pre-4th Generation)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation

Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3 GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation

Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3 GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3 GPP Rel. 17 (3rd Generation Partnership Project Release 17), 3GPP LTE Extra, LTE Licensed- Assisted Access (LAA), UTRA (UMTS Terrestrial Radio Access), E-UTRA (Evolved UMTS Terrestrial Radio Access), LTE Advanced (4G) (Long Term Evolution Advanced (4th Generation)), ETSI OneM2M, IoT (Internet of things), cdmaOne (2G), CDMA2000 (3G) (Code division multiple access 2000 (Third generation)), EV-DO (Evolution-Data Optimized or Evolution-Data Only), AMPS (1G) (Advanced Mobile Phone System (1st Generation)), TACS/ETACS (Total Access Communication System/Extended Total Access Communication System), D-AMPS (2G) (Digital AMPS (2nd Generation)), PTT (Push-to-talk), MTS (Mobile Telephone System), IMTS (Improved Mobile Telephone System), AMTS (Advanced Mobile Telephone System), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, or Mobile telephony system D), Autotel/PALM (Public

Automated Land Mobile), ARP (Finnish for Autoradiopuhelin or "car radio phone"), NMT (Nordic Mobile Telephony), Hicap (High capacity version of NTT (Nippon Telegraph and Telephone)), CDPD (Cellular Digital Packet Data), Mobitex, DataTAC, iDEN (Integrated Digital Enhanced Network), PDC (Personal Digital Cellular), CSD (Circuit Switched Data), PHS (Personal Handy-phone System), WiDEN (Wideband Integrated Digital Enhanced Network), iBurst, Unlicensed Mobile Access (UMA, also referred to as also referred to as 3GPP Generic Access Network, or GAN standard)), WiFi systems based on IEEE 802.11a/b/c/g/n/ac/ax, Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-90 GHz and above such as WiGig, IEEE 802. Had, IEEE 802. Hay and/or others) and/or others. The embodiments and/or examples provided herein are thus understood as being applicable to various other mobile communication technologies.

[0061] Turning to FIG 10, an example provides functionality 1000 of an internal Spectrum Access System (SAS) in a mobile operator domain in a cellular network, as shown in the flowchart in FIG 10. The functionality 1000 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included in one or more computer readable mediums or one or more non- transitory machine readable storage mediums.

[0062] The first operation 1010 in the flowchart is receiving interference coordination information from an external SAS. The second operation is receiving sensing data from an Environmental Sensing Capability (ESC). The third operation is determining and sending a decision on spectrum access through an Operation, Administration, and Maintenance (OAM) system to other network elements based on the sensing data received from the ESC and the interference coordination information received from the external SAS.

[0063] In addition to the operations from FIG. 10, there are also additional operations that can be on a machine readable storage medium having instructions embodied thereon for operating an internal SAS in a mobile operator domain in a cellular network. An additional operation for the internal SAS is providing information on spectrum availability from an Informing Incumbent to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM). This information on spectrum availability can include information about whether the

Informing Incumbent is in a given geographical area, time, or frequency band. This information on spectrum availability, can be provided to the OAM via an internal SAS that is configured to interface with an NM, an EM, or a DM. The information can further propagate to other network elements.

[0064] There is an additional operation that can be on a machine readable storage medium having instructions embodied thereon for operating an internal SAS in a mobile operator domain in a cellular network. The operation is determining and sending a decision on Priority Access User (PA User) or Generalized Authorized Access User (GAA User) spectrum allocation to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM). After a request is sent from the OAM to the intemal SAS, the internal SAS can determine the optimal possible channel and send back a corresponding decision to the OAM system. This decision can be provided to the OAM via an internal SAS that is configured to interface with an NM, an EM, or a DM. The information can further propagate to other network elements.

[0065] One more operation that can be on a machine readable storage medium having instructions embodied thereon for operating an internal SAS in a mobile operator domain in a cellular network is: determining and sending information about a specific channel allocation for a Priority Access User (PA User) or a Generalized Authorized Access User (GAA User) to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM). The OAM can request a specific channel for PA Users or GAA Users, and the internal SAS can provide information indicating whether the request is possible, not possible, or possible under certain conditions. If an incumbent would like use of the channel, then typically the request cannot be possible. The information can be provided to the OAM via an internal SAS that is configured to interface with an NM, an EM, or a DM. The information can further propagate to other network elements.

[0066] Another operation can be on a machine readable storage medium having instructions embodied thereon for operating an intemal SAS in a mobile operator domain in a cellular network. This operation is receiving certification information from a governmental entity. The governmental entity, for example, can be the Federal

Communications Commission (FCC) in the U.S. In Europe and other countries, the governmental entity can be any entity that regulates communications.

[0067] The next flowchart, as shown in FIG 11, provides functionality 1100 of an external Spectrum Access System (SAS) outside a mobile operator domain in a cellular network. The functionality 1100 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included in one or more computer readable mediums or one or more non-transitory machine readable storage mediums. The first operation 1110 is determining interference coordination information. The second operation 1120 is receiving sensing data from an Environmental Sensing Capability (ESC). The third operation 1130 is determining and sending a decision on spectrum access through an Operation, Administration, and Maintenance (OAM) system via the internal SAS to other network elements based on the interference coordination information and the sensing data received from the ESC.

[0068] In addition to the operations from FIG 11, there are also additional operations that can be on a machine readable storage medium having instructions embodied thereon for operating an external SAS outside a mobile operator domain in a cellular network. One additional operation is providing information on spectrum availability from an Informing Incumbent to the OAM system via the intemal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM). This information on spectrum availability can include information about whether the Informing Incumbent is in a given geographical area, time, or frequency band. This information on spectrum availability, can be provided to the OAM via an internal SAS that is configured to interface with an NM, an EM, or a DM. The information can further propagate to other network elements.

[0069] There is an additional operation that can be on a machine readable storage medium having instructions embodied thereon for operating an external SAS outside a mobile operator domain in a cellular network. The operation is determining and sending a decision on Priority Access User (PA User) or Generalized Authorized Access User

(GAA User) spectrum allocation to the OAM system via the intemal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM). After a request is sent from the OAM to the external SAS, the external SAS can determine the optimal possible channel and send back a corresponding decision to the OAM system. This decision can be provided to the OAM via an internal SAS that is configured to interface with an NM, an EM, or a DM. The information can further propagate to other network elements.

[0070] One more operation that can be on a machine readable storage medium having instructions embodied thereon for operating an external SAS outside a mobile operator domain in a cellular network is: determining and sending information about a specific channel allocation for a Priority Access User (PA User) or a Generalized Authorized Access User (GAA User) to the OAM system via the internal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM). The OAM can request a specific channel for PA Users or GAA Users, and the external SAS can provide information indicating whether the request is possible, not possible, or possible under certain conditions. If an incumbent would like use of the channel, then typically the request cannot be possible. The information can be provided to the OAM via an internal SAS that is configured to interface with an NM, an EM, or a DM. The information can further propagate to other network elements.

[0071] Another operation can be on a machine readable storage medium having instructions embodied thereon for operating an external SAS outside a mobile operator domain in a cellular network. This operation is receiving certification information from a governmental entity. The governmental entity, for example, can be the Federal

[0072] Turning now to FIG 12, an example provides functionality 1200 of a Spectrum Access System (SAS) stub in a mobile operator domain in a cellular network, as shown in the flow chart in FIG 12. The functionality 1200 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included in one or more computer readable mediums or one or more non-transitory machine readable storage mediums.

[0073] The SAS stub does not provide the full functionality of an internal SAS. Rather, the functionality consists primarily of the following operations described below. The purpose of providing this reduced functionality is to reduce the amount of functions that a mobile network operator needs to provide in implementing the Spectrum Access System. Because of the reduced functionality, some of the functions provided by the SAS stub may be different from the corresponding functions in the internal SAS.

[0074] The first operation 1210 in the flowchart is the reporting of sensing information to an external SAS. This sensing information related to use of the band outside of the Mobile Network Operator's Domain can be aggregated by the external SAS and communicated to the SAS stub. Use of the band within the Mobile Network Operator's Domain can be aggregated by the SAS stub, filtered, and communicated to the external SAS. The external SAS can communicate the usage of the band related to the Mobile Network Operator to other external SASs.

[0075] The next operation 1220 is determining network changes based on reports of interference from the external SAS. The external SAS operates to mitigate interference across a plurality of networks. The external SAS can also have the functionality of generating and providing reports of interference. Upon receiving this report from the external SAS, the SAS stub can determine network changes, such as changes in power levels or frequencies, so that the interference is mitigated. The interference can include interference from a lower tier to a higher tier, such as: interference from a GAA User to a PA User; interference from a GAA User to an Incumbent; or interference from a PA User to an Incumbent. The interference can also include interference between neighboring Census Tracts. For example, in a densely populated city such as New York City neighboring blocks can constitute differing Census Tracts, which can lead to additional sources of interference.

[0076] The third operation 1230 is sending a command to an eNB to start or stop operating in a selected band when instructed by the external SAS. This can reduce interference that originates between Census Tracts and interference that originates between users.

[0077] The fourth operation 1240 is sending a command to one or more User Equipment (UEs) via an eNB for the UE to start or stop operating in a selected band when instructed by the external SAS. Such a command can be sent to the UE in response to sensing results from an ESC indicating that Informing Incumbents want use of the band.

Alternatively, the command can be sent to the UE if the Informing Incumbents inform the external SAS of their desire to use the band. The command can also be used when PA Users want to use the band over the GAA Users.

[0078] In addition to the operations from FIG. 12, there are also additional operations that can be on a machine readable storage medium having instructions embodied thereon for operating an SAS stub in a mobile operator. The instructions, when executed, can obtain a list of channels from the external SAS. The list of channels can be a list of available channels or a list of unavailable channels. A list of available channels can allow the SAS stub to propagate a decision on spectrum access through the OAM system to other network elements. The instructions, when executed, can also manage frequency and power allocations to UEs based on the available channels.

[0079] The instructions, when executed, can also aggregate information from the cellular network and send the aggregated information to the external SAS. One of the purposes of aggregating the information is to preserve the confidentiality of the specific information that is being aggregated. This allows the external SAS to perform its function of interference mitigation across a plurality of networks without relying on confidential information from the Mobile Network Operator.

[0080] FIG. 13 provides an example illustration of a user equipment (UE) device 1300 and a node 1320. The UE device 1300 can include a wireless device, a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of wireless device. The UE device 1300 can include one or more antennas configured to communicate with the node 1320 or transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (R H), a remote radio equipment (R E), a relay station (RS), a radio equipment (RE), a remote radio unit (RRU), a central processing module (CPM), or other type of wireless wide area network (WWAN) access point. The node 1320 can include one or more processors 1322 and memory 1324. The UE device 1300 can be configured to communicate using at least one wireless communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The UE device 1300 can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The UE device 1300 can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN.

[0081] In some embodiments, the UE device 1300 may include application circuitry

1302, baseband circuitry 1304, Radio Frequency (RF) circuitry 1306, front-end module (FEM) circuitry 1308 and one or more antennas 1310, coupled together at least as shown.

[0082] The application circuitry 1302 may include one or more application processors. For example, the application circuitry 1302 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with and/or may include a storage medium, and may be configured to execute instructions stored in the storage medium to enable various applications and/or operating systems to run on the system.

[0083] The baseband circuitry 1304 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1304 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 1306 and to generate baseband signals for a transmit signal path of the RF circuitry 1306. Baseband processing circuity 1304 may interface with the application circuitry 1302 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1306. For example, in some embodiments, the baseband circuitry 1304 may include a second generation (2G) baseband processor 1304a, third generation (3G) baseband processor 1304b, fourth generation (4G) baseband processor 1304c, and/or other baseband processor(s) 1304d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6Q etc.). The baseband circuitry 1304 (e.g., one or more of baseband processors 1304a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1306. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 1304 may include Fast-Fourier Transform (FFT), precoding, and/or constellation

mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 1304 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.

Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0084] In some embodiments, the baseband circuitry 1304 may include elements of a protocol stack such as, for example, elements of an evolved universal terrestrial radio access network (EUTRAN) protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or radio resource control (RRC) elements. A central processing unit (CPU) 1304e of the baseband circuitry 1304 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 1304f. The audio DSP(s) 1304f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 1304 and the application circuitry 1302 may be implemented together such as, for example, on a system on a chip (SOC).

[0085] In some embodiments, the baseband circuitry 1304 may provide for

communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 1304 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 1304 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0086] The RF circuitry 1306 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 1306 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1306 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1308 and provide baseband signals to the baseband circuitry 1304. RF circuitry 1306 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1304 and provide RF output signals to the FEM circuitry 1308 for transmission.

[0087] In some embodiments, the RF circuitry 1306 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 1306 may include mixer circuitry 1306a, amplifier circuitry 1306b and filter circuitry 1306c. The transmit signal path of the RF circuitry 1306 may include filter circuitry 1306c and mixer circuitry 1306a. RF circuitry 1306 may also include synthesizer circuitry 1306d for synthesizing a frequency for use by the mixer circuitry 1306a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1306a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1308 based on the synthesized frequency provided by synthesizer circuitry 1306d. The amplifier circuitry 1306b may be configured to amplify the down-converted signals and the filter circuitry 1306c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 1304 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a necessity. In some embodiments, mixer circuitry 1306a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0088] In some embodiments, the mixer circuitry 1306a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1306d to generate RF output signals for the FEM circuitry 1308. The baseband signals may be provided by the baseband circuitry 1304 and may be filtered by filter circuitry 1306c. The filter circuitry 1306c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[0089] In some embodiments, the mixer circuitry 1306a of the receive signal path and the mixer circuitry 1306a of the transmit signal path may include two or more mixers and may be arranged for quadrature down-conversion and/or up-conversion respectively. In some embodiments, the mixer circuitry 1306a of the receive signal path and the mixer circuitry 1306a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1306a of the receive signal path and the mixer circuitry 1306a may be arranged for direct down-conversion and/or direct up-conversion, respectively. In some embodiments, the mixer circuitry 1306a of the receive signal path and the mixer circuitry 1306a of the transmit signal path may be configured for super-heterodyne operation.

[0090] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these altemate embodiments, the RF circuitry 1306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1304 may include a digital baseband interface to communicate with the RF circuitry 1306.

[0091] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[0092] In some embodiments, the synthesizer circuitry 1306d may be a fractional -N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1306d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0093] The synthesizer circuitry 1306d may be configured to synthesize an output frequency for use by the mixer circuitry 1306a of the RF circuitry 1306 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1306d may be a fractional N/N+l synthesizer.

[0094] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a necessity. Divider control input may be provided by either the baseband circuitry 1304 or the applications processor 1302 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 1302.

[0095] Synthesizer circuitry 1306d of the RF circuitry 1306 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0096] In some embodiments, synthesizer circuitry 1306d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 1306 may include an IQ/polar converter.

[0097] FEM circuitry 1308 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1310, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1306 for further processing. FEM circuitry 1308 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1306 for transmission by one or more of the one or more antennas 1310.

[0098] In some embodiments, the FEM circuitry 1308 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1306). The transmit signal path of the FEM circuitry 1308 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1306), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1310.

[0099] FIG. 12 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile

communication device, a tablet, a handset, or other type of wireless device. The wireless device can include one or more antennas configured to communicate with a node, macro node, low power node (LPN), or, transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point. The wireless device can be configured to communicate using at least one wireless communication standard such as, but not limited to, 3 GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network

(WLAN), a wireless personal area network (WPAN), and/or a WWAN. The wireless device can also comprise a wireless modem. The wireless modem can comprise, for example, a wireless radio transceiver and baseband circuitry (e.g., a baseband processor). The wireless modem can, in one example, modulate signals that the wireless device transmits via the one or more antennas and demodulate signals that the wireless device receives via the one or more antennas.

[00100] FIG. 12 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device. The display screen can be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display. The display screen can be configured as a touch screen. The touch screen can use capacitive, resistive, or another type of touch screen technology. An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities. A non-volatile memory port can also be used to provide data input/output options to a user. The non-volatile memory port can also be used to expand the memory capabilities of the wireless device. A keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard can also be provided using the touch screen.

Examples

[00101] The following examples pertain to specific technology embodiments and point out specific features, elements, or actions that can be used or otherwise combined in achieving such embodiments.

[00102] Example 1 includes at least one machine readable storage medium having instructions embodied thereon for operating an internal Spectrum Access System (SAS) in a cellular network, the instructions when executed perform the following: receiving, at the internal SAS, interference coordination information from an external SAS; receiving, at the internal SAS, sensing data from an Environmental Sensing Capability (ESC);

determining, at the internal SAS, a decision on spectrum access based on sensing data received from the ESC and interference coordination information received from the external SAS; and sending, at the internal SAS, the decision on spectrum access through an Operation, Administration, and Maintenance (OAM) system to other network elements in the mobile operator domain.

[00103] Example 2 includes the at least one machine readable storage medium of example 1, further comprising instructions that when executed perform the following: providing, at the internal SAS, information on spectrum availability from an Informing Incumbent to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00104] Example 3 includes the at least one machine readable storage medium of example 1, further comprising instructions that when executed perform the following: determining, at the internal SAS, a decision on Priority Access User (PA User) or Generalized

Authorized Access User (GAA User) spectrum allocation; and sending the decision to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00105] Example 4 includes the at least one machine readable storage medium of example 1, further comprising instructions that when executed perform the following: determining, at the internal SAS, information about a specific channel allocation for a Priority Access User (PA User) or a Generalized Authorized Access User (GAA User); and sending, at the internal SAS, the information to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00106] Example 5 includes the internal SAS of examples 1, 2, 3, or 4, wherein the cellular network is a Third Generation Partnership Project (3GPP) network.

[00107] Example 6 includes at least one machine readable storage medium having instructions embodied thereon for operating an external Spectrum Access System (SAS) in a cellular network, the instructions when executed perform the following: determining, at the external SAS, interference coordination information across a plurality of networks; receiving, at the external SAS, sensing data from an Environmental Sensing Capability (ESC); determining, at the external SAS, a decision on spectrum access based on the interference coordination information from the external SAS and the sensing data received from the ESC; and sending, at the external SAS, the decision on spectrum access through an Operation, Administration, and Maintenance (OAM) system via an internal SAS to other network elements in the mobile operator domain.

[00108] Example 7 includes the at least one machine readable storage medium of example 6, further comprising instructions that when executed perform the following: providing, at the external SAS, information on spectrum availability from an Informing Incumbent to the OAM system via an internal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00109] Example 8 includes the at least one machine readable storage medium of example 6, further comprising instructions that when executed perform the following: determining, at the external SAS, a decision on Priority Access User (PA User) or Generalized

Authorized Access User (GAA User) spectrum allocation; and sending, at the external SAS, the decision to the OAM system via an internal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00110] Example 9 includes the at least one machine readable storage medium of example 6, further comprising instructions that when executed perform the following: determining, at the external SAS, information about a specific channel allocation for a Priority Access User (PA User) or a Generalized Authorized Access User (GAA User); and sending, at the external SAS, the information to the OAM system via the internal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00111] Example 10 includes the external SAS of examples 6, 7, 8, or 9, wherein the cellular network is a 3GPP network.

[00112] Example 11 includes at least one machine readable storage medium having instructions embodied thereon for operating a Spectrum Access System (SAS) stub in a mobile operator domain in a cellular network, the instructions when executed perform the following: reporting sensing information to an external SAS; determining network changes based on reports of interference from the external SAS; sending a command to an Evolved Node B (eNB) to start operating or stop from operating in a selected band when instructed by the external SAS; and sending a command to one or more user equipments (UEs) via the eNB for the UEs to start operating or stop operating in the selected band when instructed by the external SAS.

[00113] Example 12 includes the at least one machine readable storage medium of example 11, further comprising instructions that when executed perform the following: obtaining a list of channels from the external SAS.

[00114] Example 13 includes the at least one machine readable storage medium of example 11, further comprising instructions that when executed perform the following: managing frequency and power allocations to UEs based on available channels from the external SAS.

[00115] Example 14 includes the at least one machine readable storage medium of examples 11, 12, or 13, further comprising instructions that when executed perform the following: aggregating information from the cellular network and sending the aggregated information to the external SAS.

[00116] Example 15 includes the SAS stub of examples 11, 12, 13, or 14, wherein the cellular network is a Third Generation Partnership Project (3 GPP) network.

[00117] Example 16 includes a spectrum sharing component operating in a cellular network comprising: an intra-carrier domain entity, wherein the intra-carrier domain entity is configured to interface with: an extra-carrier domain entity, wherein the extra- carrier domain entity is configured for interference coordination across a plurality of networks; and an operations and management system; and wherein the intra-carrier domain entity, is configured to determine and send a decision on spectrum access through the operations and management system to other network elements based on information received from the sensing data component and the extra-carrier domain entity.

[00118] Example 17 includes the spectrum sharing component of example 16, wherein the intra-carrier domain entity is further configured to interface with a sensing data component. [00119] Example 18 includes the spectrum sharing component of example 17 wherein: the intra-carrier domain entity is an internal Spectrum Access System (SAS); the extra-carrier domain entity is an external SAS; the operations and management system is an Operation, Administration, and Maintenance (OAM) system; and the sensing data component is an Environmental Sensing Capability (ESC).

[00120] Example 19 further includes the spectrum sharing component of example 18 wherein the internal SAS is further configured to interface with the OAM system at one of: a Network Manager (NM) level; an Element Manager (EM); or a Domain Manager (DM) level; and wherein the internal SAS is further configured to interface with one or more of: an Informing Incumbent; or a Federal Communications Commission (FCC) database.

[00121] Example 20 further includes the spectrum sharing component of example 18, wherein the internal SAS is located in one of: a Network Manager (NM); an Element Manager (EM); or a Domain Manager (DM); and wherein the internal SAS is further configured to interface with one or more of: an Informing Incumbent; or a Federal Communications Commission (FCC) database.

[00122] Example 21 includes an internal Spectrum Access System (SAS) in a cellular network, the internal SAS comprising: means for receiving, at the internal SAS, interference coordination information from an external SAS; means for receiving, at the internal SAS, sensing data from an Environmental Sensing Capability (ESC); means for determining, at the internal SAS, a decision on spectrum access based on sensing data received from the ESC and interference coordination information received from the external SAS; and means for sending, at the internal SAS, the decision on spectrum access through an Operation, Administration, and Maintenance (OAM) system to other network elements in the mobile operator domain.

[00123] Example 22 includes the internal SAS of example 21, further comprising: means for providing, at the internal SAS, information on spectrum availability from an

Informing Incumbent to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00124] Example 23 includes the internal SAS of example 21, further comprising: means for determining, at the internal SAS, a decision on Priority Access User (PA User) or Generalized Authorized Access User (GAA User) spectrum allocation; and means for sending the decision to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00125] Example 24 includes the internal SAS of example 21, further comprising: means for determining, at the internal SAS, information about a specific channel allocation for a Priority Access User (PA User) or a Generalized Authorized Access User (GAA User); and means for sending, at the internal SAS, the information to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00126] Example 25 includes the internal SAS of examples 21, 22, 23, or 24, wherein the cellular network is a Third Generation Partnership Project (3 GPP) network

[00127] Example 26 includes an external Spectrum Access System (SAS) in a cellular network, the external SAS comprising: means for determining, at the external SAS, interference coordination information across a plurality of networks; means for receiving, at the external SAS, sensing data from an Environmental Sensing Capability (ESC); means for determining, at the external SAS, a decision on spectrum access based on the interference coordination information from the external SAS and the sensing data received from the ESC; and means for sending, at the external SAS, the decision on spectrum access through an Operation, Administration, and Maintenance (OAM) system via an internal SAS to other network elements in the mobile operator domain.

[00128] Example 27 includes the external SAS of example 26, further comprising: means for providing, at the external SAS, information on spectrum availability from an

Informing Incumbent to the OAM system via an internal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00129] Example 28 includes the external SAS of example 26, further comprising: means for determining, at the external SAS, a decision on Priority Access User (PA User) or Generalized Authorized Access User (GAA User) spectrum allocation; and means for sending, at the external SAS, the decision to the OAM system via an internal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00130] Example 29 includes the external SAS of example 26, further comprising: means for determining, at the external SAS, information about a specific channel allocation for a Priority Access User (PA User) or a Generalized Authorized Access User (GAA User); and means for sending, at the external SAS, the information to the OAM system via the internal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

[00131] Example 30 includes the external SAS of examples 26, 27, 28, or 29, wherein the cellular network is a 3GPP network.

[00132] Example 31 includes a Spectrum Access System (SAS) stub in a mobile operator domain in a cellular network, the SAS stub comprising: means for reporting sensing information to an external SAS; means for determining network changes based on reports of interference from the external SAS; means for sending a command to an Evolved Node B (eNB) to start operating or stop from operating in a selected band when instructed by the external SAS; and means for sending a command to one or more user equipments (UEs) via the eNB for the UEs to start operating or stop operating in the selected band when instructed by the external SAS.

[00133] Example 32 includes the SAS stub of example 31, further comprising: means for obtaining a list of channels from the external SAS.

[00134] Example 33 includes the SAS stub of example 31, further comprising: means for managing frequency and power allocations to UEs based on available channels from the external SAS.

[00135] Example 34 includes the SAS stub of examples 31, 32, or 33, further comprising: means for aggregating information from the cellular network and sending the aggregated information to the external SAS.

[00136] Example 35 includes the SAS stub of examples 31, 32, 33, or 34, wherein the cellular network is a Third Generation Partnership Project (3 GPP) network.

[00137] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. A non-transitory computer readable storage medium can be a computer readable storage medium that does not include signal. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable

programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). In one example, selected components of the transceiver module can be located in a cloud radio access network (C-RAN). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

[00138] As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

[00139] It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[00140] Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

[00141] Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.

[00142] Reference throughout this specification to "an example" or "exemplary" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, appearances of the phrases "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

[00143] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present technology may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as defacto equivalents of one another, but are to be considered as separate and autonomous representations of the present technology.

[00144] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology.

[00145] While the forgoing examples are illustrative of the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the technology be limited, except as by the claims set forth below.

Claims

What is claimed is:

1. At least one machine readable storage medium having instructions embodied thereon for operating an internal Spectrum Access System (SAS) in a cellular network, the instructions when executed perform the following:

receiving, at the internal SAS, interference coordination information from an external SAS;

receiving, at the internal SAS, sensing data from an Environmental Sensing Capability (ESC);

determining, at the internal SAS, a decision on spectrum access based on sensing data received from the ESC and interference coordination information received from the external SAS; and

sending, at the internal SAS, the decision on spectrum access through an Operation, Administration, and Maintenance (OAM) system to other network elements in the mobile operator domain.

The at least one machine readable storage medium of claim 1, further comprising instructions that when executed perform the following:

Providing, at the internal SAS, information on spectrum availability from an Informing Incumbent to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

determining, at the internal SAS, a decision on Priority Access User (PA

User) or Generalized Authorized Access User (GAA User) spectrum allocation; and

sending the decision to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

4. The at least one machine readable storage medium of claim 1, further comprising instructions that when executed perform the following: determining, at the internal SAS, information about a specific channel allocation for a Priority Access User (PA User) or a Generalized Authorized Access User (GAA User); and

sending, at the internal SAS, the information to the OAM system at the level of a Network Manager (NM), an Element Manager (EM), or a Domain

Manager (DM).

The internal SAS of claims 1, 2, 3, or 4, wherein the cellular network is a Third Generation Partnership Project (3GPP) network.

6. At least one machine readable storage medium having instructions embodied thereon for operating an external Spectrum Access System (SAS) in a cellular network, the instructions when executed perform the following:

determining, at the external SAS, interference coordination information across a plurality of networks;

receiving, at the external SAS, sensing data from an Environmental Sensing Capability (ESC);

determining, at the external SAS, a decision on spectrum access based on the interference coordination information from the external SAS and the sensing data received from the ESC; and

sending, at the external SAS, the decision on spectrum access through an Operation, Administration, and Maintenance (OAM) system via an internal SAS to other network elements in the mobile operator domain. 7. The at least one machine readable storage medium of claim 6, further comprising instructions that when executed perform the following:

providing, at the external SAS, information on spectrum availability from an Informing Incumbent to the OAM system via an internal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

8. The at least one machine readable storage medium of claim 6, further comprising instructions that when executed perform the following:

determining, at the external SAS, a decision on Priority Access User (PA User) or Generalized Authorized Access User (GAA User) spectrum allocation; and

sending, at the external SAS, the decision to the OAM system via an internal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM). 9. The at least one machine readable storage medium of claim 6, further comprising instructions that when executed perform the following:

determining, at the external SAS, information about a specific channel allocation for a Priority Access User (PA User) or a Generalized Authorized Access User (GAA User); and

sending, at the external SAS, the information to the OAM system via the internal SAS at the level of a Network Manager (NM), an Element Manager (EM), or a Domain Manager (DM).

10. The external SAS of claims 6, 7, 8, or 9, wherein the cellular network is a 3GPP network.

11. At least one machine readable storage medium having instructions embodied thereon for operating a Spectrum Access System (SAS) stub in a mobile operator domain in a cellular network, the instructions when executed perform the following:

reporting sensing information to an external SAS;

determining network changes based on reports of interference from the external SAS;

sending a command to an Evolved Node B (eNB) to start operating or stop from operating in a selected band when instructed by the external SAS; and sending a command to one or more user equipments (UEs) via the eNB for the UEs to start operating or stop operating in the selected band when instructed by the external SAS.

12. The at least one machine readable storage medium of claim 11, further comprising instructions that when executed perform the following:

obtaining a list of channels from the external SAS.

13. The at least one machine readable storage medium of claim 11, further comprising instructions that when executed perform the following:

managing frequency and power allocations to UEs based on available channels from the external SAS.

14. The at least one machine readable storage medium of claim 11, 12, or 13, further comprising instructions that when executed perform the following:

aggregating information from the cellular network and sending the aggregated information to the external SAS.

15. The SAS stub of claims 11, 12, 13, or 14, wherein the cellular network is a Third Generation Partnership Project (3GPP) network.

16. A spectrum sharing component operating in a cellular network comprising:

an intra-carrier domain entity, wherein the intra-carrier domain entity is configured to interface with:

an extra-carrier domain entity, wherein the extra-carrier domain entity is configured for interference coordination across a plurality of networks; and

an operations and management system; and

wherein the intra-carrier domain entity, is configured to determine and send a decision on spectrum access through the operations and management system to other network elements based on information received from the sensing data component and the extra-carrier domain entity.

17. The spectrum sharing component of claim 16, wherein the intra-carrier domain entity is further configured to interface with a sensing data component.

18. The spectrum sharing component of claim 17 wherein:

the intra-carrier domain entity is an intemal Spectrum Access System (SAS);

the extra-carrier domain entity is an external SAS;

the operations and management system is an Operation, Administration, and Maintenance (OAM) system; and

the sensing data component is an Environmental Sensing Capability (ESC).

19. The spectrum sharing component of claim 18 wherein the intemal SAS is further configured to interface with the OAM system at one of:

a Network Manager (NM) level;

an Element Manager (EM); or

a Domain Manager (DM) level; and

wherein the intemal SAS is further configured to interface with one or more of:

an Informing Incumbent; or

a Federal Communications Commission (FCC) database.

20. The spectrum sharing component of claim 18, wherein the internal SAS is located in one of:

a Network Manager (NM);

an Element Manager (EM); or

a Domain Manager (DM); and

wherein the intemal SAS is further configured to interface with one or more of:

an Informing Incumbent; or

a Federal Communications Commission (FCC) database.