Method and apparatus for handling interference connection types in citizens broadband radio service devices band
11617087 · 2023-03-28
Assignee
Inventors
Cpc classification
H04W72/0453
ELECTRICITY
H04W16/14
ELECTRICITY
International classification
H04W16/14
ELECTRICITY
H04W28/16
ELECTRICITY
Abstract
A method and network node for classification of interference connections between Citizens Broadband Radio Service Devices, CBSDs, in a wireless communication network are provided. According to one aspect, a method includes calculating an interference level, the calculation being based on whether two interfering CBSDs are operating in one of the alternate channels, adjacent channels and the same channel. The method also includes comparing the calculated interference level to a threshold to determine a classification of an interference connection.
Claims
1. A network node in a wireless communication network, the network node comprising: processing circuitry configured to: classify a measured interference between Citizen Broadband Service Devices, CBSDs, having a coverage overlap, to a first classification of a plurality of classifications, the first classification indicating whether at least one of different radio access technologies, RATs, and overlapping uplink, UL, and downlink, DL, cycles is allowed, the classification of the measured interference to the first classification being based at least in part on: whether the interference between the CBSDs is associated with one of alternative channels and adjacent channels; measurements of the interference between the CBSDs; and perform at least one action based on the classification of the measured interference to the first classification, the at least one action including performing channel assignments; and the interference between the two interfering CBSDs does not allow the CBSDs to operate in a Citizen's Broadband Radio Service, CBRS, band without incurring interference above a predefined threshold if the CBSDs are part of different coexistence groups or the CBSDs use different radio access technologies, RATs.
2. The network node of claim 1, wherein the interference between the two interfering CBSDs does not allow the CBSDs to operate in the Citizen's Broadband Radio Service, CBRS, band without incurring interference about a predefined threshold if the CBSDs have overlapping downlink and uplink cycles, regardless of the existence of a guard band between channels assigned to the CBSDs.
3. The network node of claim 1, wherein the interference between the two interfering CBSDs does not allow the CBSDs to operate in adjacent channels without incurring interference about a predefined threshold if the CBSDs use different RATs or overlapping downlink and uplink cycles.
4. The network node of claim 3, wherein the interference between the two interfering CBSDs is associated with a guard band greater than a predefined bandwidth.
5. The network node of claim 1, wherein the interference between the two interfering CBSDs does allow CBSDs to operate in different channels without incurring interference above a predefined threshold if CBSDs use different RATs or overlapping downlink and uplink cycle.
6. The network node of claim 5, wherein the different channels between the CBSDs are orthogonal to each other.
7. The network node of claim 1, wherein the interference threshold is one of static, dynamic and based on a probability distribution of received interference levels at the CBSDs.
8. The network node of claim 1, wherein the at least one action includes applying at least one network policy to reduce interference associated with the CBSDs.
9. The network node of claim 1, wherein the network node is a spectrum access system, SAS.
10. The network node of claim 1, wherein the network node is a Coexistence Manager, CxM.
11. A method for a network node for classification of interference between Citizens Broadband Radio Service Devices, CBSDs, in a wireless communication network, the method comprising: classifying a measured interference between Citizen Broadband Service Devices, CBSDs, having a coverage overlap, to a first classification of a plurality of classifications, the first classification indicating whether at least one of different radio access technologies, RATs, and overlapping, UL, and downlink, DL, cycles is allowed, the classification of the measured interference to the first classification being based at least in part on: whether the measured interference between the CBSDs is associated with one of alternative channels and adjacent channels; measurements of the interference between the CBSDs; and performing at least one action based on the classification of the measured interference to the first classification, the at least one action including performing channel; and the interference between the two interfering CBSDs does not allow the CBSDs to operate in a Citizen's Broadband Radio Service, CBRS, band without incurring interference above a predefined threshold if the CBSDs are part of different coexistence groups or the CBSDs use different radio access technologies, RATs.
12. The method of claim 11, wherein the interference between the two interfering CBSDs does not allow the CBSDs to operate in a Citizen's Broadband Radio Service, CBRS, band without incurring interference above a predefined threshold if the CBSDs have overlapping downlink and uplink cycles, regardless of the existence of a guard band between channels assigned to the CBSDs.
13. The method of claim 11, wherein the interference between the two interfering CBSDs does not allow the CBSDs to operate in adjacent channels without incurring interference above a predefined threshold if the CBSDs use different RATs or overlapping downlink and uplink cycles.
14. The method of claim 13, wherein the interference between the two interfering CBSDs is associated with a guard band greater than a predefined bandwidth.
15. The method of claim 11, wherein the interference between the two interfering CBSDs does allow CBSDs to operate in different channels without incurring interference above a predefined threshold if CBSDs use different RATs or overlapping downlink and uplink cycles.
16. The method of claim 15, wherein the different channels between the CBSDs are orthogonal to each other.
17. The method of claim 11, wherein the interference threshold is one of static, dynamic and based on a probability distribution of received interference levels at the CBSDs.
18. The method of claim 11, wherein the at least one action includes applying at least one network policy to reduce interference associated with the CBSDs.
19. The method of claim 11, wherein the network node is a spectrum access system, SAS.
20. The method of claim 11, wherein the network node is a Coexistence Manager, CxM.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
(1) A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
DETAILED DESCRIPTION
(16) Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to the classification of interference connections between Citizens Broadband Radio Service Devices, CBSDs 2, and performing at least one action based on the classification of interference connections. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
(17) The term “wireless device”, also referred to as “used herein may refer to any type of wireless device communicating with a network node and/or with another wireless device in a cellular or mobile communication system. Examples of a wireless device are user equipment (UE), end user device (EUD), target device, device to device (D2D) wireless device, machine type wireless device or wireless device capable of machine to machine (M2M) communication, a sensor equipped with UE, PDA, iPAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, computer premises equipment (CPE), etc.
(18) The term “network node” used herein may refer to a radio network node or another network node, e.g., a core network node, MSC, MME, O&M, OSS, SON, positioning node (e.g. E-SMLC), MDT node, etc.
(19) The term “network node” or “radio network node” used herein can be any kind of network node comprised in a radio network which may further comprise any of base station (BS), Spectrum Access System (SAS), Citizens Broadband Radio Service Device (CBSD), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell/multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), etc. The network node may also comprise test equipment. The term “radio node” used herein may be used to also denote a wireless device such as a wireless device or a radio network node.
(20) Note further, that functions described herein as being performed by a wireless device or a network node may be distributed over a plurality of wireless devices and/or network nodes. In other words, it is contemplated that the functions of the network node and wireless device described herein are not limited to performance by a single physical device and, in fact, can be distributed among several physical devices.
(21) Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to classifying an interference connection of multiple CBSDs 2 and performing at least one action based on the classification of the interference connection where the at least one action may help mitigate at least some of the interference between the CBSDs. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein.
(22) As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements.
(23) The CBRS Alliance coexistence task group is proposing that the Coexistence Manager build a connected set of CBSDs 2, and should use the connected set as an input to the channel assignment algorithm. Two CBSDs 2 are deemed to be connected by an edge in the connected set if there is a coverage overlap between the two CBSDs 2. The threshold for defining the CBSD 2 coverage has not been fixed yet, but it has been proposed to use a value of −80 dBm/10 MHz.
(24) Some embodiments provide a classification of the connections between the CBSDs 2 depending on the interference conditions. A goal is to identify the interference conditions that will impact channel assignments to the two connected CBSDs 2.
(25) In one example, one coexistence group, dedicated to the CBRS Alliance, may be managed by one or more Coexistence Managers (CxMs). CBSDs that are members of the same ICG may independently manage the interference, and hence they do not require a CxM to handle the interference for them. CBSDs that are members of the same CCG are requesting the CxM to assign them to the same channel.
(26) It may be assumed that the CBSDs 2 belonging to the same ICG will use the same TDD configuration in order to avoid downlink/uplink (DL/UL) interference. Members of different ICGs can request for different TDD configurations, but this may result in potential interference scenarios as described later.
(27)
(28) Processing circuitry 22 may include and/or be connected to and/or be configured for accessing (e.g., writing to and/or reading from) memory 24, which may include any kind of volatile and/or non-volatile memory, e.g., cache and/or buffer memory and/or RAM (Random Access Memory) and/or ROM (Read-Only Memory) and/or optical memory and/or EPROM (Erasable Programmable Read-Only Memory). Such memory 24 may be configured to store code executable by control circuitry and/or other data, e.g., data pertaining to communication, e.g., configuration and/or address data of nodes, etc. Processing circuitry 22 may be configured to control any of the methods described herein and/or to cause such methods to be performed, e.g., by processor 26. Corresponding instructions may be stored in the memory 24, which may be readable and/or readably connected to the processing circuitry 22. In other words, processing circuitry 22 may include a controller, which may comprise a microprocessor and/or microcontroller and/or FPGA (Field-Programmable Gate Array) device and/or ASIC (Application Specific Integrated Circuit) device. It may be considered that processing circuitry 22 includes or may be connected or connectable to memory, which may be configured to be accessible for reading and/or writing by the controller and/or processing circuitry 22.
(29) The memory 24 is configured to store interference levels 30 calculated by an interference level calculator 28. The interference level calculations are based on whether two interfering CBSDs 2 are operating in one of alternate channels, adjacent channels and the same channel. A comparator 30 is configured to compare the calculated interference level to a threshold to determine a classification of an interference connection. The transceiver 32 communicates with one or more network entities such as CBSDs 2 and other wireless devices 10.
(30)
(31)
(32) In some embodiments, the at least one action includes making/performing channel assignments based on the classification of interference connections. According to one embodiment of this aspect, the at least one action includes performing channel assignments based on the classification of interference connections. According to one embodiment of this aspect, the interference connection between the two interfering CBSDs 2 does not allow the CBSDs 2 to operate in a Citizen's Broadband Radio Service, CBRS, band without incurring interference above a predefined threshold if the CBSDs 2 are part of different coexistence groups or the CBSDs 2 use different radio access technologies, RATs.
(33) According to one embodiment of this aspect, the interference connection between the two interfering CBSDs 2 does not allow the CBSDs 2 to operate in the Citizen's Broadband Radio Service, CBRS, band without incurring interference about a predefined threshold if the CBSDs 2 have overlapping downlink and uplink cycles, regardless of the existence of a guard band between channels assigned to the CBSDs 2. According to one embodiment of this aspect, the interference connection between the two interfering CBSDs 2 does not allow the CBSDs 2 to operate in adjacent channels without incurring interference about a predefined threshold if the CBSDs 2 use different RATs or overlapping downlink and uplink cycles.
(34) According to one embodiment of this aspect, the interference connection between the two interfering CBSDs 2 is associated with a guard band greater than a predefined bandwidth. According to one embodiment of this aspect, the interference connection between the two interfering CBSDs 2 does allow CBSDs 2 to operate in different channels without incurring interference above a predefined threshold if CBSDs 2 use different RATs or overlapping downlink and uplink cycle. According to one embodiment of this aspect, the different channels between the CBSDs 2 are orthogonal to each other.
(35) According to one embodiment of this aspect, the interference threshold is one of static, dynamic and based on a probability distribution of received interference levels at the CBSDs 2. According to one embodiment of this aspect, the at least one action includes applying at least one network policy to reduce interference associated with the CBSDs 2. According to one embodiment of this aspect, the network node is a spectrum access system, SAS. According to one embodiment of this aspect, the network node 14 is a Coexistence Manager, CxM.
(36) Some embodiments produce a classification of interference connections between CBSDs 2 and specifies how these connections need to be handled by SAS 6 and CxM. CBRS band offers a unique opportunity for the central entities like SAS 6 and CxM, that have access to CBSD 2 information, to calculate interference types between CBSDs 2 and apply different policies to manage interference.
(37) Having generally described arrangements for classification of an interference connection and performing at least one action based on a classification of an interference connection between CDSDs 2, details for these arrangements, functions and processes are provided as follows, and which may be implemented by the network node 14.
Embodiment 1: Co-Existence Connected Set Classifications with Static Thresholds
(38) The SAS 6's, i.e., network node 14's, ability to break a connected set into multiple independent CxG connected sets can be impacted by the type of interference connections between the CBSDs 2. For this purpose, this method defines the following classification of the CBSD connections in the SAS 6, i.e., network node 14, connected set: Type 1 Connection: Connected CBSDs 2 cannot use different technologies or overlapping UL/DL cycles regardless of the guard band between the channels assigned to the two CBSDs 2; Type 2 Connection: Connected CBSDs 2 cannot use different technologies or overlapping UL/DL cycles if the assigned channels are adjacent; and Type 3 Connection: Connected CBDSs could potentially use different technologies or overlapping UL/DL in different channels.
(39) To explain the classification of the CBSD connections, the scenario is described in
(40) An assumption is made that the CBSDs 2 use 10 MHz channels. The formula for the interference level is:
I.sub.1->2=P.sub.1+G.sub.1->2−PL.sub.1->2
(41) Where: P.sub.1 is the conducted power that the CBSD 2a is transmitting in the channel ch.sub.2 used by CBSD 2b; a) For alternate channels: P.sub.1=−25 dBm/MHz=−15 dBm/10 MHz, for example; b) For adjacent channels: P.sub.1=−13 dBm/MHz=−3 dBm/10 MHz, for example; G.sub.1->2 includes both aggressor transmit (Tx) gain and victim receive (Rx) gain a) G.sub.1->2 is usually between −20 dBi to 30 dBi, for example; PL.sub.1->2 is the path loss between CBSD 2a and CBSD 2b.
As used in one or more examples, subscript “1” is associated with CBSD 2a and subscript “2” is associated with CBSD 2b. “G” denotes gain, I denotes interference, P denotes power while PL denotes path loss. Path loss may be determined using theoretical propagation models that are known in the art. In one or more embodiments, the propagation model may use additional data such as actual/measured data associated with interference distribution to increase the accuracy of estimated path loss. For example, SAS 6, i.e., network node 14, has access to measurements to build a cumulative distribution function (CDF) of probability for determining path loss.
(42) Consider that the two channels assigned to the CBSDs 2 are alternate channels (i.e. channels with at least a guard band of f.sub.guard frequency gap between them). Without loss of generality, it may be assumed that, for this example, f.sub.guard=10 MHz, then P.sub.1 will be given by the FCC emission mask requirements P.sub.1=−25 dBm/MHz=−15 dBm/10 MHz. If the channels are adjacent channels, then P.sub.1 will be given by the FCC emission mask requirements P.sub.1=−13 dBm/MHz=−3 dBm/10 MHz. If the CBSDs 2 are operating in the same channel (co-channel), then instead of P.sub.1, the max effective isotropic radiated power (EIRP) power level for CatA or CatB devices may be used.
(43) Interference Connection Type 1: Connected CBSDs 2 cannot use different technologies or overlapping UL/DL cycles regardless of the guard band between the channels assigned to the two CBSDs 2.
(44) For alternate channels, P.sub.1=−15 dBm/10 MHz, and considering the cases where the interference threshold is exceeded=>
(45) I.sub.1->2=P.sub.1+G.sub.1->2−PL.sub.1->2>T.sub.interference_max=>
(46) PL.sub.1->2<−15−T.sub.interference_max+G.sub.1->2
(47) Assuming T.sub.interference_max=−80 dBm/10 MHz=> PL.sub.1_>2<65+G.sub.1->2
(48) So, if the path loss between the two CBSDs 2 meet the above formula, the two CBSDs 2 are considered to have an Interference connection of Type 1. This is equivalent to: Assume G.sub.1->2=6 dBi=>PL.sub.1->2<71 dB=>D.sub.1->2<23m (free space propagation) Assume G.sub.1->2=0 dBi=>PL.sub.1->2<65 dB=>D.sub.1->2<11m (free space propagation) Assume G.sub.1->2=18 dBi=>PL.sub.1->2<83 dB=>D.sub.1->2<94m (free space propagation)
(49) Note that the output power of the aggressor in channel ch.sub.1 does not impact the equation, so reducing the output power of an aggressor, i.e., CBSD 2a, does not solve this problem. In practice, reducing the power of the aggressor may have a positive effect, but it might not be enough to solve the interference problem.
(50) Interference Connection Type 2: Connected CBSDs 2 cannot use different technologies or overlapping UL/DL cycles if the assigned channels are adjacent.
(51) For adjacent channels, P.sub.1=−3 dBm/10 MHz=>
(52) PL.sub.1->2<−3−T.sub.interference_max+G.sub.1->2 PL.sub.1->2<77+G.sub.1->2
(53) This is equivalent to: Assume G.sub.1->2=6 dBi=>PL.sub.1->2<83 dB=> <=D.sub.1->2<94m(free space propagation); Assume G.sub.1->2=0 dBi=>PL.sub.1->2<77 dB=>D.sub.1->2<47 m(free space propagation); and Assume G.sub.1->2=18 dBi=>PL.sub.1->2<95 dB=>D.sub.1->2<375m(free space propagation).
(54) Interference Connection Type 3: Connected CBDSs 2 can potentially use different technologies or overlapping UL/DL in different channels. In this case, the interference threshold is met, resulting in the following formula:
PL.sub.1->2>=77+G.sub.1->2
(55) However, this case requires more considerations regarding the impact on the wireless device 10 DL signal interference, as described later.
(56) A potential Interference Connection Type 4 can also be considered, where the connected CBDSs 2 can use different technologies or overlapping UL/DL in the same channel, but in this case, the two CBSDs 2 are no longer connected and hence the type 4 connection may not appear in practice.
(57) The different types of interference connections may have to be handled differently by the SAS 6, i.e., network node 14, and CxM, i.e. network node 14:
(58) Type 1 Difficult case where the main coexistence tools (e.g., reducing output power and adding guard band between channels) cannot solve the interference problem; This type of connection may require manual intervention if the CBSDs 2 are part of different CxGs, like for example: Coordinating deployments between operators: Increasing isolation between CBSDs 2; Coordinating technologies; Business arrangements; and If CBSDs 2 are part of the same CxG, the type 1 connection may require the use of same UL/DL configuration.
(59) Type 2 may require a guard band of 10 MHz if CBSDs 2 are part of different CxGs; may require a guard band of 10 MHz if CBSDs 2 want to use different UL/DL configuration; and SAS 6, i.e., network node 14, via processing circuitry 22, can use this information when dividing the spectrum between CxGs, and CxM, i.e. network node 14, can use this info when dividing the spectrum between TDD and listen before talk (LBT) or between different subgroups using different LTE TDD configurations.
(60) Type 3 For these connection types, a further analysis may be required before deciding how to handle them where one example is illustrated in
(61) For type 3 connections, the CxM, i.e. network node 14, can use the coloring algorithm, as specified in the CBRS Alliance Technical Report to orthogonalize channels between CBSDs 2. In fact, the coloring algorithm can also be used for type 1 and type 2 interference connections as long as the CBSDs 2 are using the same LTE TDD UL/DL configuration.
(62) Therefore, SAS 6 or CxM, i.e., network node 14, via processing circuitry 22, may classify the interference connection between CBDSs 2 to be one of the above types (i.e., Type 1, Type 2, etc.), and may perform at least one action such as channel assignment and/or dividing up the spectrum based on the classification of the interference connection. In one or more embodiments, by classifying interference of a vast amount of scenarios into one of these specific interference types, the disclosure advantageously allows the mitigation tools to be selected and implemented in a low complexity manner. For example, in various different scenarios classified as interference type 1, the same mitigation tool(s) can be implemented, thereby reducing complexity in interference management.
(63)
(64) Wireless device (WD) 10a is the aggressor, using channel ch1, in UL mode. Wireless device 10b is the victim, using channel ch.sub.2, in DL mode. The acceptable Interference threshold is T.sub.interference_max (for example −80 dBm/10 MHz) I.sub.WD10a->WD10b=P.sub.WD10a−ACIR.sub.WD10a->WD10b−PL.sub.WD10a->WD10b I.sub.WD10a->WD10b<=T.sub.interference_max P.sub.WD10a is the conducted power emitted by wireless device 10a in channel ch.sub.1: Max 23 dBm/10 MHz ACIR.sub.WD10a->WD10b˜=28 dB
(65) For example, If PL.sub.WD10a->2<65 dB (equivalent to D.sub.WD10a->WD10b<11m), the DL could be impacted. However, SAS 6, i.e., network node 14, has no information about the wireless device 10 position and the effective wireless device 10 transmit power, hence it may not be able to evaluate wireless device 10 interference impacts. Therefore, the type 2 and type 3 interference connection types cannot be detected by SAS 6, i.e., network node 14, or CxM, i.e. network node 14, and they are left to be handled by the network operators.
Embodiment #2: Variable Threshold Co-Existence Connected Set Classifications
(66) In Embodiment #1, the connection set thresholds defined for the different connection set types were static. In this embodiment, the connection set thresholds for connections can be also, semi-static or dynamic fixed values defined by the SAS 6, i.e. network node 14, or CxM, i.e. network node 14. Semi-static connection set thresholds can be modified on a daily basis or less over an interval consistent with a grant period for a CBSD 2, whereas dynamic connection set thresholds can be modified within a grant period of a CBSD 2.
Embodiment #3: Soft-Value Threshold Co-Existence Connected Set Classifications
(67) In Embodiments #1 and #2, the connection set thresholds defined for the different connection set types could static, semi-static or dynamic, but were based on fixed threshold values. In this embodiment, the connection set thresholds defined by the SAS 6, i.e. network node 14, or CxM, i.e. network node 14, can be probabilistic soft values. Due to the random nature of the propagation channel such as log-normal shadowing, fast fading, additive white Gaussian noise and other random channel impairments, the measured interference between CBSDs 2 as well as between CBSDs 2 and protection points may be by definition a random variable. Based on this randomness the connection set threshold T.sub.interference_max can be associated with a probability of occurrence P.sub.interference_max. The pair (T.sub.interference_max, P.sub.interference_max) can be set by the SAS 6, i.e. network node 14, CxM, i.e. network node 14, or domain proxy in a static, semi-static or dynamic manner based on a probability of achieving a desired quality of service metric between CBSDs 2 such as signal to interference plus noise ratio (SINR), SLNR (signal loss to noise ratio) or other probabilistic measures.
Some Other Embodiments
Embodiment 1A
(68) A method in a network node 14 for classification of interference connections between Citizens Broadband Radio Service Devices, CBSDs 2, in a wireless communication network, the method comprising:
(69) calculating an interference level, the calculation being based on whether two interfering CBSDs 2 are operating in one of alternate channels, adjacent channels and the same channel; and
(70) comparing the calculated interference level to a threshold to determine a classification of an interference connection.
Embodiment 2A
(71) The method of Embodiment 1A, further comprising making channel assignments based on the classification of interference connections.
Embodiment 3A
(72) The method of any of Embodiments 1A and 2A, wherein an interference connection between the two interfering CBSDs 2 is one of:
(73) a type 1 connection wherein the CBSDs 2 may not use different radio access technologies, RATs, and overlapping downlink and uplink cycles regardless of an existence of a guard band between channels assigned to the CBSDs 2;
(74) a type 2 connection wherein the CBSDs 2 may not use different RATs and overlapping downlink and uplink cycles when the channels assigned to the CBSDs 2 are adjacent; and
(75) a type 3 connection wherein the CBSDs may use different RATs and overlapping downlink and uplink cycles in different channels.
Embodiment 4A
(76) The method of any of Embodiments 1A-3A, wherein the threshold is static.
Embodiment 5A
(77) The method of any of Embodiments 1A-3A, wherein the threshold is dynamic.
Embodiment 6A
(78) The method of any of Embodiments 1A-3A, wherein the threshold is determined probabilistically.
Embodiment 7A
(79) The method of any of Embodiments 1A-6A, wherein the network node 14 is a spectrum access system, SAS 6.
Embodiment 8A
(80) The method of any of Embodiments 1A-6A, wherein the network node 14 is a Coexistence Manager, CxM.
Embodiment 9A
(81) A network node 14 for classification of interference connections between Citizens Broadband Radio Service Devices, CBSDs 2, in a wireless communication network, the network node 14 comprising:
(82) processing circuitry 22 configured to:
(83) calculate an interference level, the calculation being based on whether two interfering CBSDs 2 are operating in one of alternate channels, adjacent channels and the same channel; and
(84) compare the calculated interference level to a threshold to determine a classification of an interference connection.
Embodiment 10A
(85) The network node 14 of Embodiment 9A, further comprising making channel assignments based on the classification of interference connections.
Embodiment 11A
(86) The network node 14 of any of Embodiments 9A and 10A, wherein an interference connection between the two interfering CBSDs 2 is one of:
(87) a type 1 connection wherein the CBSDs 2 may not use different radio access technologies, RATs, and overlapping downlink and uplink cycles regardless of an existence of a guard band between channels assigned to the CBSDs 2;
(88) a type 2 connection wherein the CBSDs 2 may not use different RATs and overlapping downlink and uplink cycles when the channels assigned to the CBSDs 2 are adjacent; and
(89) a type 3 connection wherein the CBSDs 2 may use different RATs and overlapping downlink and uplink cycles in different channels.
Embodiment 12A
(90) The network node 14 of any of Embodiments 9A-11A, wherein the threshold is static.
Embodiment 13A
(91) The network node 14 of any of Embodiments 9A-11A, wherein the threshold is dynamic.
Embodiment 14A
(92) The network node 14 of any of Embodiments 9A-11A, wherein the threshold is determined probabilistically.
Embodiment 15A
(93) The network node 14 of any of Embodiments 9A-14A, wherein the network node is a spectrum access system, SAS 6.
Embodiment 16A
(94) The network node 14 of any of Embodiments 9A-14A, wherein the network node 14 is a Coexistence Manager, CxM.
Embodiment 17A
(95) A network node 14 for classification of interference connections between Citizens Broadband Radio Service Devices, CBSDs 2, in a wireless communication network, the network node 14 comprising:
(96) an interference level calculation module 29 configured to calculate an interference level, the calculation being based on whether two interfering CBSDs 2 are operating in one of the alternate channels, adjacent channels and the same channel; and
(97) a comparator module 31 configured to compare the calculated interference level to a threshold to determine a classification of an interference connection.
(98) TABLE-US-00001 Abbreviation Explanation ASA Authorized Shared Access CBRS Citizen's Broadband Radio Service CBSD Citizens Broadband Radio Service Device CCG Common Channel Group: A group of CBSDs, that are part of the same ICG, requiring a common primary channel assignment. The common primary channel assignment will be fulfilled by the CxM only for the CBSDs that have overlapping coverage. Connected Set Set of CBSDs belonging to a connected component of a graph created at the SAS or CxM CxG Coexistence Group: A group of CBSDs that coordinate their own interference within the group according to a common interference management policy CxM Coexistence Manager: A logical entity responsible for managing coexistence between GAA users within a CxG in coordination with SAS, according to the common interference management policy ESC Environmental Sensing Capability EUD End User Device GAA General Authorized Access ICG Interference coordination group LSA Licensed Shared Access PAL Priority Access License PE Protected Entity PL Path Loss PPA PAL Protection Area RAT Radio Access Technology SAS: Spectrum Access System
(99) As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, and/or computer program product. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that can be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.
(100) Some embodiments are described herein with reference to flowchart illustrations and/or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
(101) These computer program instructions may also be stored in a computer readable memory or storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
(102) The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
(103) It is to be understood that the functions/acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
(104) Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the “C” programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
(105) Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments can be combined in any way and/or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.
(106) It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings.
(107) It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.