WO2020230092A1 - Procédé de regroupement en grappes et nœud permettant d'attribuer une configuration de tdd dans une bande de cbrs - Google Patents

Procédé de regroupement en grappes et nœud permettant d'attribuer une configuration de tdd dans une bande de cbrs Download PDF

Info

Publication number
WO2020230092A1
WO2020230092A1 PCT/IB2020/054595 IB2020054595W WO2020230092A1 WO 2020230092 A1 WO2020230092 A1 WO 2020230092A1 IB 2020054595 W IB2020054595 W IB 2020054595W WO 2020230092 A1 WO2020230092 A1 WO 2020230092A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
nodes
configuration
interference
clusters
Prior art date
Application number
PCT/IB2020/054595
Other languages
English (en)
Inventor
Gary Boudreau
Kumar Balachandran
Virgil CIMPU
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2020230092A1 publication Critical patent/WO2020230092A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/121—Wireless traffic scheduling for groups of terminals or users
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames

Definitions

  • the present description generally relates to wireless communication systems and specifically to methods and apparatus for coexistence management in shared spectrum scenarios.
  • Licensed Shared Access LSA
  • ASA Authorized shared access
  • This disclosure is concerned with the third (last) approach, which proposes a shared spectrum approach.
  • a typical use of this scenario is to enable use of a band that is available for licensed users in some markets, but is being restricted in others because of incumbents, such as radar or satellite systems.
  • Incumbent systems can be protected around the area of deployment, while authorization for mobile infrastructure can be granted in such a way that aggregate interference from mobile systems towards the incumbent is limited to an acceptable level of noise rise or performance degradation.
  • LSA the mobile operator is licensed to operate in permitted or authorized areas and is the reasonable regulatory approach to ASA.
  • the Federal Communications Commission has defined the citizens Broadband Radio Service (CBRS) in the 3550-3700 MHz band.
  • CBRS Citizens Broadband Radio Service
  • FSS Fixed Satellite System
  • the two remaining tiers respectively allow the issue of Priority Access Licenses (PAL) and General Authorized Access (GAA) in the band for wireless broadband use.
  • PAL Priority Access Licenses
  • GAA General Authorized Access
  • PAL users benefit from the priority to spectrum based on the acquired licensed area and bandwidth.
  • GAA users are allowed access to any spectrum not utilized by higher tiers based on authorized access.
  • Radio devices are registered as citizens Broadband Radio Service Devices (CBSD) based on their location and their operating parameters. A single eligible radio device may request access to PAL and GAA spectrum.
  • CBSD citizens Broadband Radio Service Devices
  • the CBRS Alliance was chartered as an industry trade organization seeking to promote and improve the operation of LTE in the band.
  • the Alliance is specifying changes to network architecture to allow both the traditional operator deployed operation and private network operation including neutral hosts and has provided a platform to establish the impetus for contributions in Third Generation Partnership Project (3 GPP) for defining frequency bands for LTE-Time Division Duplex (TDD) and LTE-enhanced Licensed Assisted Access (eLAA) operation in the band.
  • 3 GPP Third Generation Partnership Project
  • the CBRS Alliance has also taken on the task to define guidelines and standards for coexistence solutions using the LTE-TDD technologies. These solutions are based on a logical component known as the Coexistence Manager (CxM). This will allow LTE-TDD networks to cooperate within a Coexistence Group (CxG), known as the CBRS Alliance CxG, by means of semi-static allocation of different frequency channels.
  • CxM Coexistence Manager
  • 3 GPP has defined the band B48 for the LTE TDD devices operating in CBRS band and it is working towards introducing band N48 for 5G New Radio (NR) devices.
  • NR 5G New Radio
  • the CBRS Alliance also advocates for the use of LTE and NR technology in the CBRS 3.5GHz band, as well as to specify methods of improving LTE performance in a shared spectrum deployment.
  • the CBRS alliance has published a technical specification entitled“CBRS Alliance, CBRS Coexistence Technical Specification, CBRSA-TS-2001, V2.0.0, 6 January 2019” (see htps://wmv.cbrsdliance.Org/wp-content/upioads/2019/Q3/CBRSA-TS-2QQl-V2.0.0 Pubiished- March-1 l-2019.pdf) for co-existence of network and devices using LTE technology and is in the process of expanding the technical specification to include NR devices.
  • the CxM will be in charge of assigning channels to a group of CBSDs that declare themselves as compatible with one another for the purposes of interference mitigation.
  • the group is generally referred to as a CxG and may e.g. be composed of LTE CBSDs belonging to the CxG called“CBRS ALLIANCE CXG” that has passed compliance with certification by the CBRS Alliance.
  • the CxM manages these CBSDs in a way that minimizes inter-CBSD interference as well as protects the incumbents and the higher tier users.
  • the CBRS Alliance is also defining additional rules for the CxG CBRS ALLIANCE CXG, as follows:
  • All TDD deployments in the band shall be cell phase synchronized and shall have frame timing derived from a common time reference.
  • TDD Config 2 There are two TDD configurations that are mandated: TDD Config 2 and TDD Config 1
  • TDD configurations can be used when the deployment is isolated or when all the operators in the area agree to use a particular configuration. Otherwise, the CxM will default to one of the mandated configurations.
  • Connected sets offer a method to determine where the CBRS spectrum can be re-used and where it requires to be divided between different network deployments to ensure coexistence.
  • Connected sets are built by evaluating if the CBSDs will interfere with each other, for example, two CBSDs or two networks of CBSDs that have overlapping coverage may be deemed to be connected.
  • Independent connected sets may each access the entire CBRS spectrum, but within a connected set, the spectrum must be divided between different deployments.
  • - Individual CBSDs specify the desired TDD configuration (uplink-downlink configuration and SSF configuration) and the TDD fallback configuration as attributes in the grouping parameter associated with the CBRS Alliance CxG.
  • Any 3GPP uplink-downlink configuration and SSF configuration defined in 3GPP may be used, provided all the LTE-TDD CBSDs in the LTE-TDD Connected Set use the same desired TDD configuration.
  • the CxM designates the use of one mandatory fallback TDD configuration from those listed in Table 1, which also requires the use of SSF Configuration 7.
  • the TDD configuration shall be chosen by the majority vote among the fallback TDD configurations requested by CBSDs within the constructed baseline Connected Set, where ties are resolved by a pseudorandom draw.
  • TabSs 1 Mandatory E-UTRA TDD UL/DL Configurations for the C'BRSA CxG.
  • the current rules require the CxM to coordinate a change in the TDD configuration when the number of CBSDs requesting a different fallback TDD configuration has increased and that number becomes the majority of CBSDs within the connected set.
  • the embodiments introduce a clustering method that will allow a CBRS Coexistence Manager (CxM) to perform a more flexible LTE TDD configuration assignment within a Connected Set.
  • CxM CBRS Coexistence Manager
  • the method can also be applied to NR TDD configuration assignment.
  • some embodiments include a method performed by a controlling node.
  • the controlling node can be a coexistence manager (CxM).
  • the method may comprise: determining one or more first clusters of nodes based on a first configuration; determining one or more second clusters of nodes based on a second configuration; determining one or more third clusters of nodes that do not belong to any of the determined first and second clusters; and assigning the first configuration to the first clusters, assigning the second configuration to the second clusters and assigning a third configuration to the third clusters based on a rule.
  • some embodiments include a controlling node configured, or operable, to perform one or more functionalities (e.g. actions, operations, steps, etc.) as described herein. For example, it can perform the above method.
  • the controlling node may comprise one or more communication interfaces configured to communicate with one or more network nodes, and processing circuitry operatively connected to the communication interface, the processing circuitry being configured to perform one or more functionalities as described herein.
  • the processing circuitry may comprise at least one processor and at least one memory storing instructions which, upon being executed by the processor, configure the at least one processor to perform one or more functionalities as described herein.
  • the controlling node may comprise one or more functional modules configured to perform one or more functionalities as described herein.
  • some embodiments include a non-transitory computer- readable medium storing a computer program product comprising instructions which, upon being executed by processing circuitry (e.g., at least one processor) of the controlling node, configure the processing circuitry to perform one or more functionalities as described herein.
  • processing circuitry e.g., at least one processor
  • Figure la and Figure lb illustrate an architecture for shared spectrum and co-existence management.
  • Figure 2 illustrates a flow chart of a method for determining configuration assignment, according to an embodiment.
  • Figure 3a and Figure 3b illustrate an example of a connected set for a first configuration and a second configuration, according to an embodiment.
  • Figure 4a and Figure 4b illustrate an example of determining different clusters in a connected set in which the method of Figure 2 is applied, according to an embodiment.
  • Figure 5 illustrates an example of configuration assignment, according to an embodiment.
  • Figure 6 illustrates an example of configuration assignment according to an existing method.
  • Figure 7a and Figure 7b illustrate an example of a connected set for a first configuration and a second configuration.
  • Figure 8a, Figure 8b and Figure 8c illustrate an example of determining different clusters in a connected set in which the method of Figure 2 is applied.
  • Figure 9a illustrates an example of configuration assignment, according to an embodiment.
  • Figure 9b illustrates an example of configuration assignment according to an existing method.
  • Figure 10 illustrates an example of an interference matrix, according to an embodiment.
  • Figure 11 illustrates an example of a network deployment with different operators.
  • Figure 12 illustrates an example of an interference matrix for the example of Figure 11.
  • Figure 13 illustrates an exemplary flow chart of a method for assigning TDD configuration.
  • Figure 14 illustrates an exemplary flow chart of a method for assigning TDD configuration.
  • Figure 15 illustrates an exemplary flow chart of a method for assigning TDD configuration.
  • Figures 16 and 17 are a schematic illustration of a controlling node, according to an embodiment.
  • some embodiments can be partially or completely embodied in the form of computer readable carrier or carrier wave containing an appropriate set of computer instructions that would cause a processor to carry out the techniques described herein.
  • the shared spectrum and co-existence management architecture is depicted in Figure la, as proposed by the FCC for the 3.5 GHz band.
  • the Spectrum Access System (SAS) is a central entity or system for coordinating, authorizing and managing use of the CBRS spectrum, protecting higher tier operations from interference, and maximizing frequency capacity for all CBRS operators.
  • the SAS may be referred to as a controlling node.
  • the SAS administrators will be permitted to charge CBRS operators fees for registration and frequency coordination services.
  • the SAS is also connected to FCC databases, an Environmental Sensing Capability (ESC) system for incumbent detection, an informing incumbent system, a plurality of CBSDs, a domain proxy (DP) and a second SAS, such as SAS2.
  • the Domain Proxy can be connected to a plurality of CBSDs.
  • the SAS2 can be also connected to another ESC.
  • the FCC requires that transmission equipment with specific, standardized capabilities be employed by CBRS operators for use in the 3.5 GHz band. This equipment is called CBSD.
  • CBSDs are fixed base stations/access points, such as an LTE Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs).
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • Node Bs also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs
  • CBDSs Category A (a lower power CBSD) and Category B (a higher power CBSD).
  • the CBSDs can only operate under the authority and management of a centralized SAS.
  • CBRS end user devices are controlled by an authorized CBSD.
  • End User Devices have the capability to receive and decode information from a CBSD.
  • the users access a communication network through one or more CBSDs and, when granted permission from the SAS, use resources within the shared band.
  • the ESC can monitor for incumbent radar activity in coastal areas and near inland military bases.
  • the ESC can employ spectrum sensing technologies in conjunction with the SAS, in order to allow CBRS users to operate near coastlines on frequencies not being used by the federal radar systems.
  • incumbent activity is detected, the ESC communicates that information to SAS1.
  • the SAS or SASs will reconfigure local devices to avoid interfering with the detected incumbent radars.
  • the FCC databases include information related to commercial users and corresponding licenses (e.g., site-based licensing information).
  • SAS and SAS2 are capable of directly interfacing with the FCC databases to access information used for SAS operations.
  • the Domain Proxy is a managing intermediary.
  • a Domain Proxy’s functions are to, for example:
  • Figure la shows an architecture, as supported by the specification for CBRS from the perspective of regulatory compliance. More specifically, Figure la shows the Wireless Innovation Forum (WinnForum) architecture that has been used by the FCC as baseline for certification of both CBSDs and SASes.
  • Figure lb shows an architecture supported by the specification for CBRS from the perspective of regulatory compliance and coordination of GAA users within a Coexistence Group . More specifically, Figure lb shows a notional representation of how the CBRS Alliance Coexistence group policy agreements may be carried out, using the illustrated architecture.
  • Figure lb is similar to Figure la with the exception that the DP is absent, so that a plurality of CBSDs is connected to the SAS directly. Furthermore, a CxM is also connected to the SAS.
  • the CxM can be regionally assigned to a particular SAS for centralized control of the CxG on a local basis or may be distributed with periodic reconciliation of state.
  • the interface between the CxM and the SAS is not specified yet but mechanisms to communicate information to the CxM have been defined via the SAS-CBSD interface.
  • the CxM could be integrated in the SAS as there is no specified direct interface to the CBSD and information transfer is via containers in SAS-CBSD messages.
  • the CxM is charged with analyzing and mitigating interference among members of the Co-existence group operating on GAA spectrum, for example.
  • a co-existence group can be defined as a group of nodes (e.g. CBSDs) that may have interference with each other, but the CBSDs of the group can coordinate their own interference within the group according to a common interference management policy.
  • nodes e.g. CBSDs
  • CBSDs of the group can coordinate their own interference within the group according to a common interference management policy.
  • a Common Channel Group can be defined as a group of CBSDs, that are part of the same Interference Coordination Group (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.
  • a Connected set can be defined as a set of CBSDs belonging to a connected component of a graph created at the SAS or CxM.
  • a CxM can be defined as a logical entity responsible for managing coexistence between GAA users within a CxG in coordination with SAS, according to the common interference management policy. More specifically, the CxM is associated with a SAS and represents an analytical engine that coordinates operations of CBSDs belonging to a CxG, for example.
  • the CBRS Alliance coexistence technical specification states that the Coexistence Manager shall build a connected set of CBSDs and shall use the connected set as an input to the TDD Configuration assignment. Two (2) CBSDs are deemed to be connected by an edge in the connected set, if there is a coverage overlap between the 2 CBSDs.
  • Individual CBSDs can specify the desired TDD configuration (uplink-downlink configuration and SSF configuration) and the TDD fallback configuration as attributes in the grouping parameter associated with CBRSA CxG. Only two fallback TDD configurations are allowed by the specification, TDD Configl and TDD Config 2 (as described in Table 1). The introduction of other TDD configurations is not precluded. Then, the present disclosure would be also applicable to these configurations.
  • the present disclosure proposes a new clustering method to increase flexibility of TDD configuration determination for CBSDs/nodes in a Connected Set.
  • the method comprises identifying clusters of nodes in the connected set that only have connections to nodes for which CBSDs have requested the same TDD configuration.
  • Method 200 comprises:
  • Step 210 Determining one or more first clusters of nodes/CBSDs based on a first (e.g. desired) configuration
  • Step 220 Determining one or more second clusters of nodes/CBSDs based on a second (e.g. fallback) configuration
  • Step 230 Determining one or more third (e.g. leftover/remaining) clusters of nodes, that do not belong to any of the determined first and second clusters.
  • Step 240 Assigning the first configuration to the first clusters, assigning the second configuration to the second clusters and assigning a third configuration to the third clusters based on a rule.
  • the CxM can identify/determine one or more (first) clusters of nodes in the graph that have a first desired configuration, such as TDD Config x and only have connections to nodes of the graph that also have the same first configuration (i.e. TDD Config x). For those first clusters of nodes, the desired first configuration, TDD Config x, can be granted.
  • a first desired configuration such as TDD Config x
  • TDD Config x For those first clusters of nodes, the desired first configuration, TDD Config x, can be granted.
  • the CxM can further identify/determine one or more second clusters of nodes that have a specified second configuration, such as a fallback configuration TDD Config y and only have connections to nodes of the graph that also have the same second configuration (e.g. fallback TDD Config ).
  • the CxM can further identify/determine one or more leftover or third clusters, which are not part of the first clusters or second clusters.
  • the CxM can determine a third configuration based on the majority of the CBSDs requesting the same fallback configuration. The determination of the 3 rd configuration can be based on other rules as well.
  • the first configuration may comprise one or more desired configurations requested by the nodes in the first clusters. And the one or more first clusters of nodes may have only connections with nodes that have the first configuration.
  • the second configuration may comprise one or more fallback configurations requested by the nodes in the second clusters.
  • the one or more second clusters of nodes may have only connections with nodes that have the second configuration.
  • the first, second and third configurations are TDD configurations.
  • the“link nodes” i.e. the nodes that connect the different clusters, which are identified as the first (or desired) clusters, the second (or fallback) clusters and the third (or leftover) clusters with nodes belonging to other clusters.
  • the controlling node may identify the link nodes, which connect different clusters together and manage interference between the link nodes and adjacent nodes.
  • the controlling node may build a connected set of nodes for the first configuration and a connected set of nodes for the second configuration.
  • TDD Config 1 TDD Config 1
  • the fallback configuration is also TDD Config l;
  • TDD Config 2 TDD Config 2
  • fallback configuration TDD Config 2
  • TDD Config 0 TDD Config 1
  • Figures 3a and 3b illustrate the TDD Connected Sets that are built by the CxM for this example.
  • the connected set for the first configuration e.g. desired TDD configuration
  • the connected set for the second configuration e.g. fallback TDD configuration
  • the CxM identifies/determines the clusters having the first/desired configurations.
  • Figure 4a illustrates the result of step 210, i.e. three clusters have been identified/determined as the first clusters: Ci, C2 and C3, each of the first clusters is based on a first configuration.
  • Ci is based on TDD Config 1
  • C2 is based on TDD Config 2
  • C3 is based on TDD Config 0.
  • step 220 the CxM does not identify/determine any clusters for the fallback configuration.
  • Appling 230 in this example the CxM identifies/determines the leftover clusters C4, as shown in Figure 4b.
  • FIG. 5 illustrates the final TDD Configuration assignment done by the CxM, in this example.
  • the CxM assigns TDD Config 1 to Ci, TDD Config 2 to C2 and TDD Config 0 to C3.
  • the majority of nodes has requested TDD Config 1 as the fallback configuration (i.e. two nodes have requested TDD Config 1 against one node requesting TDD Config 2).
  • the CxM assigns TDD Config 1 to C4.
  • Figure 5 shows some specific nodes. The nodes in light grey shade have some interference.
  • the interference is at a low level because the light grey shaded nodes are using the same TDD configuration as their neighbor nodes.
  • the dark grey shaded nodes are neighbor nodes using different TDD configuration. As such, their level of interference is higher.
  • the dark grey shaded nodes, that are also link nodes need interference management within the network of each operator. More specifically, the interference between some of the link nodes (e.g. dark grey shaded nodes) can be managed by the CxM.
  • the interfering nodes (using different TDD configurations) belong to the same network (of the same operator). Different techniques can be used to manage this interference, including using collaborative schedulers, radio planning, addition of physical barriers or orienting of coverage. There may also be some scheduling features that can mitigate interference by allowing two networks to reduce the probability of use of the spectrum simultaneously, etc. These techniques are beyond the scope of this disclosure.
  • Figure 5 also highlights that several nodes will be allowed to operate using their desired (or first) TDD configuration. These nodes are marked without shading.
  • Figure 6 describes the TDD configuration assignment done by the CxM according to the rules captured in Release 2 of the CBR Alliance Coexistence Technical Specification.
  • Figure 6 shows that all the nodes in the connected set are required to use a same configuration, e.g. TDD Config 1. This is in contrast with Figure 5, which shows that most of the nodes can use their own desired configuration, such as TDD Config 1, TDD Config 2 or TDD Config 0.
  • TDD Config 2 TDD Config 2
  • fallback configuration TDD Config 2
  • TDD Config 1 TDD Config 1
  • TDD Config 2 TDD Config 2
  • TDD Config 0 TDD Config 1
  • Figures 7a and 7b illustrate the TDD Connected Set that is built by the CxM. More specifically, Figure 7a illustrates the connected set for the desired TDD configuration. Figure 7b illustrates the connected set for the fallback TDD configuration.
  • the CxM identifies/determines the desired clusters as depicted in Figure 8a. As shown in Figure 8a, the CxM identifies/ determines 2 clusters, Ci and C2, with Ci being based on TDD Config 2 and with C2 being based on TDD Config 0, for example.
  • the CxM identifies/ determines the fallback clusters, as depicted in Figure 8b.
  • Figure 8b shows C3 as the fallback cluster, with C3 being based on TDD Config _2, for example.
  • the CxM identifies/ determines the leftover clusters, as depicted in Figure 8c.
  • C4 is identified as the leftover cluster.
  • the final TDD configuration assignment done by the CxM is illustrated in Figure 9a.
  • the CxM assigns TDD Config 2 to Ci, and TDD Config 0 to C2.
  • the CxM asisgns TDD Config 2 to C 3.
  • the majority of the nodes in C4 has requested TDD Config 2 as their fallback configuration (e.g. 2 nodes have requested TDD Config 2 against one node requesting TDD Config 1).
  • TDD Config 2 is chosen to the be the configuration for C4. Therefore, the CxM assigns TDD Config 2 to C4.
  • other rules to decide what configuration to choose for C4 can be considered.
  • the interference term ijk may be insignificant (i.e. well below the noise floor of the channel in the network) if CBSD j and CBSD k are not physically adjacent to each other in the network, or equivalently in the connected set graph.
  • a threshold T1 is defined for interference between adjacent or non-adjacent CBSDs below which ijk is set to be zero, the only remaining non-zero elements will represent interference between adjacent CBSDs or non-adjacent CBSDs (these will possibly be CBSDs within one additional degree of separation) that cause significant interference between the given pair of CBSDs.
  • a typical value of the threshold T1 may be in the range of the noise floor receive sensitivity of the CBRS band (e.g.
  • the network is comprised of three different operators A, B and C with 11 different CBSDs in the network, numbered 1 through 11.
  • the interference levels above the threshold T1 between any two different CBSDs is illustrated by a solid line
  • interference below the threshold T1 between any two CBSDs is illustrated by a dashed line.
  • These interference relationships can be represented by the interference matrix provided in Figure 12.
  • interference relationships with a level above the threshold Tl are indicated with a solid bold type (i.e. hi), whereas interference relationships with a level below the threshold Tl are indicated by a greyed out type (i.e 114).
  • operator A comprises CBSDs 1 - 4
  • operator B comprises CBSDs 5 - 8
  • operator C comprise CBSDs 9 to 11.
  • the interference from CBSDs in a given network corresponds to entries in rows 1-4 for operator A, rows 5-8 for operator B and rows 9 - 11 for operator C respectively.
  • interference received by CBSDs in a given network translates to entries in columns 1-4 for operator A, columns 5-8 for operator B and columns 9 - 11 for operator C respectively.
  • This partitioning of the rows and columns in the matrix between operators provides both a visualization and a representation of interference between the different operators as illustrated in Figure 12.
  • the entries across rows 1 - 4 illustrate that in terms of interference to operator B, only CBSDs 5 and 7 (i.e. 145 and 137) are impacted with interference above the threshold Tl, and for operator C only CBSD 9 (i.e. 149) is impacted. Furthermore, it can be seen that for rows 1 and 2 none of the CBSDs in columns 5 - 8 for operator B or columns 9 -11 for operator C are above the threshold Tl . As such, CBSDs 1 and 2 could use any TDD configuration without impacting any CBSDs of operator B or C, e.g. CBSDs 1 and 2 could use a different TDD configuration from the TDD configuration for CBSDs of operators B and C and not impact any of the CBSDs of operators B and C.
  • interference values above Tl in the section of the matrix spanned by rows 1-4 and columns 1-4 represent interference between CBSDs within the network of operator A.
  • no TDD coordination between operators is required to manage these interference impacts, but they can be managed within the network of operator A itself - i.e. if any non-zero values of ijk represents interference between CBSDs in the same operator network, the interference between these CBSDs can be managed within the network, by choosing the same TDD configurations for example or employing other interference mitigation strategies, if different TDD configurations are chosen.
  • TDD configuration assignment with the interference matrix /of Figure 12
  • operator A could assign TDD configuration 0 to CBSDs 1 and 2, and assign TDD configuration 1 to CBSDs 3 and 4, and manage the interference between CBSDs 1/2 and 3/4 internal to its own network.
  • Another alternative for operator A would be to assign TDD configuration 0 to all of CBSDS 1, 2, 3, and 4.
  • the generalized clustering method involves partitioning the interference matrix /into the intersection of rows corresponding to CBSD numbers or labels j of a first operator and columns corresponding to the CBSDs numbers or labels k of a second operator, the intersection of rows and columns are referred to as an intersection set. If for any row j of the intersection set, there are no interference terms ijk that exceed the threshold Tl, then CBSD j may employ a TDD configuration independent of that employed by CBSD k of the second operator.
  • the corresponding CBSD j from the first operator and CBSD k from the second operator must either employ the same TDD configurations or employ a mutually agreed upon interference mitigation strategy.
  • method 300 as detailed in Figure 13 comprises:
  • Step 310 Generating an interference matrix /for all“N” CBSDs in the network with each entry ijk corresponding to the interference to CBSD k from CBSD j .
  • Step 320 Partitioning the interference matrix / into intersecting sets among different operators in the network such that a row j of the intersection set corresponds to a CBSD j of a first operator and a column k of the intersection set corresponds to a CBSD k of a second operator.
  • Step 330 for any row j of the intersection set, determining if the interference terms ijk exceeds the threshold TL
  • Step 340 if it is determined that the terms ijk do not exceed the threshold Tl (i.e. the terms ijk are inferior to the threshold Tl), employing/assigning a TDD configuration for CBSD j that is independent of the TDD configuration employed by CBSD k of the second operator.
  • Step 350 if it is determined that the terms ijk exceed the threshold Tl, either assigning the same TDD configuration for CBSD j from operator 1 and CBSD k from operator 2 or employing a mutually agreed upon interference mitigation strategy.
  • the entries ijk of the interference matrix I can be changed from an interference level to a measure of the SINR in dB as seen at the CBSD k in the presence of transmissions from CBSD j . This may be more appropriate particularly for indoor deployments.
  • appropriate thresholds T1 and T2 may be for example on the order of 15-20 dB for T1 and 0-5 dB for T2.
  • link adaptation can be applied to the entries ijk of the interference matrix I that exceed the threshold Tl .
  • Link adaptation will be applied to CBSDs j and k corresponding to element ijk exceeding the threshold Tl, in order to increase the robustness of the communication at both CBSD j and CBSD k to interference (i.e. choose link adaptation with a lower code rate and/or lower modulation order).
  • a second more robust link adaptation setting may be chosen.
  • machine learning can be first applied to the transmission levels of each CBSD in the network to minimize the number of interference entries exceeding the threshold Tl while maintaining a target SINR for communication by a CBSD with the EUDs it is serving.
  • Method 600 comprises:
  • Step 610 Determining based on an interference matrix, a plurality of sets of nodes from different operators.
  • Step 620 for a first node in a first set, determining whether an interference value between the first node of a first operator and a second node of a second operator is inferior to a threshold value.
  • Step 630 in response to determining that the interference value between the first node and the second node is inferior to the threshold value, assigning a first time division duplex (TDD) configuration to the first node and assigning a second TDD configuration to the second node.
  • TDD time division duplex
  • the first TDD configuration may different from the second TDD configuration.
  • the controlling node in response to determining that the interference value between the first node and the second node exceeds the threshold value, may assign a same TDD configuration to the first node and the second node. [0140] In some examples, in response to determining that the interference between the first node and the second node exceeds the threshold value, the controlling node may apply an interference mitigation strategy on the first node and second node.
  • the controlling node may compare an interference value with the threshold value for each node of the first set.
  • the controlling node may compare an interference value with a second threshold value for each node of the interference matrix.
  • the interference matrix can be generated by calculating interference between all nodes of the different operators in a network.
  • the controlling node may partition the interference matrix into intersecting sets among different operators such that a row j of the intersection set corresponds to a node j of a first operator and a column k of the intersection set corresponds to a node k of a second operator.
  • the entries of the interference matrix may comprise an interference level or a signal to interference plus noise ratio (SINR).
  • SINR signal to interference plus noise ratio
  • the controlling node may apply link adaptation to the first node and the second node, for increasing robustness of communications at the first and second nodes.
  • the interference matrix can be generated based on transmissions between all the nodes of the different operators, the transmissions being associated with machine learning for minimizing interference between the nodes.
  • the plurality of sets of nodes can show interference between nodes of different operators.
  • the assigned TDD configuration can be used by the first and second nodes for transmissions of data.
  • Method 700 can be implemented in a controlling node, such as a CxM.
  • Method 700 comprises:
  • Step 710 generating an interference matrix between all nodes of a plurality of operators in a network.
  • Step 720 partitioning the interference matrix into a plurality of intersecting sets corresponding to interference between different operators.
  • Step 730 for a first node in a first intersecting set, determining whether an interference value between the first node from a first operator and a second node from a second operator is inferior to a threshold value.
  • Step 740 in response to determining that the interference value between the first node and the second node is inferior to the threshold value, assigning a first TDD configuration to the first node and assigning a second TDD configuration to the second node.
  • FIG 16 is a block diagram of an exemplary controlling node 1000, such as CxM, that may be used to determine a configuration assignment based on the method described hereinabove.
  • the controlling node 1000 includes a processing circuitry 1010, and a network interface 1020.
  • the circuitry 1010 may include one or more (node) processors 1030, and memory 1040.
  • the one or more processors 1030 executes the method 200 and all embodiments as described above.
  • the memory 1040 stores the instructions for execution by the one or more processors 1030, and the network interface 1020 communicates signals to the other elements, such as the SAS.
  • the one or more processors 1030 may include any suitable combination of hardware and software implemented in one or more modules to execute instructions and manipulate data to perform some or all of the described functions of the CxM, such as those described above.
  • the one or more processors 1030 may include, for example, one or more computers, one or more central processing units (CPUs), one or more microprocessors, one or more applications, one or more application specific integrated circuits (ASICs), one or more field programmable gate arrays (FPGAs) and/or other logic.
  • the one or more processors 1030 may comprise one or more of the modules discussed below with respect to Figure 16.
  • the memory 1040 is generally operable to store instructions, such as a computer program, software, an application including one or more of logic, rules, algorithms, code, tables, etc. and/or other instructions capable of being executed by one or more processors 1030.
  • Examples of memory 1040 include computer memory (for example, Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (for example, a hard disk), removable storage media (for example, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or or any other volatile or non-volatile, non-transitory computer-readable and/or computer-executable memory devices that store information.
  • the network interface 1020 is communicatively coupled to the one or more processors 1030 and may refer to any suitable device operable to receive input for the controlling node 1000, send output from the controlling node 1000, perform suitable processing of the input or output or both, communicate to other devices, or any combination of the preceding.
  • the network interface 1020 may include appropriate hardware (e.g., port, modem, network interface card, etc.) and software, including protocol conversion and data processing capabilities, to communicate through a network.
  • controlling node 1000 may include additional components beyond those shown in Figure 16 that may be responsible for providing certain aspects of a CxM functionality, including any of the functionality described above and/or any additional functionality (including any functionality necessary to support the solutions described above).
  • Processors, interfaces, and memory similar to those described with respect to Figure 10 may be included in other network nodes.
  • Other network nodes may optionally include or not include a wireless interface.
  • Functionalities described could reside within the same node or could be distributed across a plurality of nodes and network nodes.
  • FIG 17 illustrates an example of a controlling node 1100 in accordance with another embodiment.
  • the controlling node 1100 could be a CxM.
  • the controlling node 1100 may include some modules 1110, such as a determining module, an assigning module, a generating module and a partitioning module.
  • the determining module is configured to perform at least steps 210, 220 and 230 of Figure 2 and steps 610, 620 of Figure 14 and step 730 of Figure 15.
  • the assigning module is configured to perform at least steps 240 of Figure 2 and step 630 of Figure 14 and step 740 of Figure 15.
  • the generating module is configured to perform at least step 710 of Figure 15.
  • the partitioning module is configured to perform at least steps 720 of Figure 15.
  • the determining module and the assigning module may be implemented using one or more processors, such as described with respect to Figure 10.
  • the modules may be integrated or separated in any manner suitable for performing the described functionality.
  • a “virtualized” network node or controlling node e.g., a virtualized base station or a virtualized radio access node or a SAS
  • a virtualized network node or controlling node is an implementation of the network node or controlling node in which at least a portion of the functionality of the network node/controlling node is implemented as a virtual component (e.g., via a virtual machine(s) or container(s) executing on a physical processing node(s) in a network(s)).
  • any steps or features described herein are merely illustrative of certain embodiments. It is not required that all embodiments incorporate all the steps or features disclosed nor that the steps be performed in the exact order depicted or described herein. Furthermore, some embodiments may include steps or features not illustrated or described herein, including steps inherent to one or more of the steps disclosed herein.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé exécuté dans un nœud de commande et permettant d'attribuer des configurations de spectres. Le procédé comprend les étapes consistant à : déterminer une ou plusieurs premières grappes de nœuds sur la base d'une première configuration ; déterminer une ou plusieurs deuxièmes grappes de nœuds sur la base d'une deuxième configuration ; déterminer une ou plusieurs troisièmes grappes de nœuds qui ne font partie ni des premières ni des deuxièmes grappes déterminées ; puis attribuer la première configuration aux premières grappes, attribuer la deuxième configuration aux deuxièmes grappes et attribuer une troisième configuration aux troisièmes grappes sur la base d'une règle.
PCT/IB2020/054595 2019-05-15 2020-05-14 Procédé de regroupement en grappes et nœud permettant d'attribuer une configuration de tdd dans une bande de cbrs WO2020230092A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201962848134P 2019-05-15 2019-05-15
US62/848,134 2019-05-15
US201962857541P 2019-06-05 2019-06-05
US62/857,541 2019-06-05

Publications (1)

Publication Number Publication Date
WO2020230092A1 true WO2020230092A1 (fr) 2020-11-19

Family

ID=70861521

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2020/054595 WO2020230092A1 (fr) 2019-05-15 2020-05-14 Procédé de regroupement en grappes et nœud permettant d'attribuer une configuration de tdd dans une bande de cbrs

Country Status (1)

Country Link
WO (1) WO2020230092A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220240098A1 (en) * 2021-01-26 2022-07-28 Celona, Inc. Time Division Duplex Configuration Selection for Citizen Band Radio Service Operation with TDD Configuration Mismatch

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016037660A1 (fr) * 2014-09-12 2016-03-17 Huawei Technologies Co.,Ltd Procédé et appareil permettant de déterminer des grappes de nœuds d'accès
US20180227151A1 (en) * 2016-07-07 2018-08-09 Qualcomm Incorporated Methods and apparatus for managing interference across operators

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016037660A1 (fr) * 2014-09-12 2016-03-17 Huawei Technologies Co.,Ltd Procédé et appareil permettant de déterminer des grappes de nœuds d'accès
US20180227151A1 (en) * 2016-07-07 2018-08-09 Qualcomm Incorporated Methods and apparatus for managing interference across operators

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220240098A1 (en) * 2021-01-26 2022-07-28 Celona, Inc. Time Division Duplex Configuration Selection for Citizen Band Radio Service Operation with TDD Configuration Mismatch

Similar Documents

Publication Publication Date Title
EP3539313B1 (fr) Procédé et noeud de commande servant à commander des ressources dans un canal partagé
JP6796724B2 (ja) 累積干渉の割り当て
US11800367B2 (en) Managing resources in CBRS networks
TWI747870B (zh) 通訊控制裝置、通訊控制方法、非暫時性電腦可讀媒體及無線通訊裝置
US11617087B2 (en) Method and apparatus for handling interference connection types in citizens broadband radio service devices band
US20210168804A1 (en) Method and node for determining channel assignment using an objective function
JP6442763B2 (ja) 共同電力制御及びチャネル割り当てを用いた空白帯域におけるスペクトル共有
KR20200003099A (ko) 업링크 캐리어 어그리게이션을 위한 사용자 장비 승인 절차
US20220400385A1 (en) Multi-spectrum and multi-network communication system
Tonnemacher et al. Opportunistic channel access using reinforcement learning in tiered CBRS networks
US12052580B2 (en) Access point centric connectivity map service
WO2019206073A1 (fr) Dispositif électronique, procédé de communication sans fil et support d'informations lisible par ordinateur
US12003972B2 (en) Method and a node for allocating spectrum efficiently in clusters of nodes
US11991530B2 (en) Electronic device and method for wireless communication and computer readable storage medium
WO2020230092A1 (fr) Procédé de regroupement en grappes et nœud permettant d'attribuer une configuration de tdd dans une bande de cbrs
CN111683374A (zh) 用于无线通信的电子设备和方法、计算机可读存储介质
Avdic et al. LSA-Advanced and C-RAN: A (5G) Romance of Many Dimensions
Dashti et al. Cognative Radio and its Impacts on Spectrum Management

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20728824

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20728824

Country of ref document: EP

Kind code of ref document: A1