WO2022106713A1 - Distribution de budget d'interférence sur la base d'un groupe - Google Patents

Distribution de budget d'interférence sur la base d'un groupe Download PDF

Info

Publication number
WO2022106713A1
WO2022106713A1 PCT/EP2021/082609 EP2021082609W WO2022106713A1 WO 2022106713 A1 WO2022106713 A1 WO 2022106713A1 EP 2021082609 W EP2021082609 W EP 2021082609W WO 2022106713 A1 WO2022106713 A1 WO 2022106713A1
Authority
WO
WIPO (PCT)
Prior art keywords
base stations
interference
network device
operational parameters
base station
Prior art date
Application number
PCT/EP2021/082609
Other languages
English (en)
Inventor
Navin Hathiramani
Roy Yang
Lan Hu
Original Assignee
Nokia Solutions And Networks Oy
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 Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Publication of WO2022106713A1 publication Critical patent/WO2022106713A1/fr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W16/00Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/14Spectrum sharing arrangements between different networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W16/00Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
    • H04W16/02Resource partitioning among network components, e.g. reuse partitioning
    • H04W16/10Dynamic resource partitioning

Definitions

  • This description relates to wireless communications.
  • a communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.
  • LTE Long Term Evolution
  • APs base stations or access points
  • eNBs enhanced Node AP
  • UE user equipments
  • LTE has included a number of improvements or developments. Aspects of LTE are also continuing to improve.
  • 5G New Radio (NR) development is part of a continued mobile broadband evolution process to meet the requirements of 5G, similar to earlier evolution of 3G & 4G wireless networks.
  • 5G is also targeted at the new emerging use cases in addition to mobile broadband.
  • a goal of 5G is to provide significant improvement in wireless performance, which may include new levels of data rate, latency, reliability, and security.
  • 5G NR may also scale to efficiently connect the massive Internet of Things (loT) and may offer new types of mission-critical services. For example, ultra-reliable and low- latency communications (URLLC) devices may require high reliability and very low latency.
  • URLLC ultra-reliable and low- latency communications
  • a method may include receiving, by a first network device from a second network device, a message including at least one maximum interference margin for a set of base stations within a geographic interference protection area of a protected device, determining, by the first network device, operational parameters including a distribution of the maximum interference for each base station in the set of base stations, transmitting, by the first network device to the second network device, a grant update request message including the operational parameters for each base station in the set of base stations, and receiving, by the first network device from the second network device, a grant update response message including a verification of the operational parameters for each base station in the set of base stations.
  • Implementations can include one or more of the following features, alone, or in any combination with each other.
  • the first network device can be a network access manager and the second network device can be a frequency allocation arbitrator or coordinator device.
  • the operational parameters can be modified without exceeding the at least one maximum interference margin.
  • the set of base stations can be associated with one operator.
  • the geographic interference protection area can include a signal coverage range defined by a plurality of contour lines each separated by a contour interval, each contour line can have an associated maximum allowed aggregate interference margin for the set of base stations, and the determining of the operational parameters can include determining base station interference at each point within the signal coverage range for each of the base stations in the set of base stations such that the maximum allowed aggregate interference margin is not exceeded.
  • the maximum allowed aggregate interference margin associated with each contour line can have a time period for which the maximum allowed aggregate interference margin is valid.
  • the operational parameters for each base station in the set of base stations can include a power setting and a beam pattern modification.
  • the method can further include reading, by the first network device from a memory associated with the first network device, information for a self-interference budget allocation associated with the set of base stations, wherein the information for the self-interference budget allocation includes an operator’s priorities of coverage/capacity for a geographic area including at least a portion of the geographic interference protection area of the protected device.
  • the distribution of the maximum interference for each base station in the set of base stations can be modified within a time period for which the maximum allowed aggregate interference margin is valid.
  • a method may include determining, by a first network device, at least one interference margin for a set of base stations within a geographic interference protection area of a protected device, transmitting, by the first network device to a second network device, a message including the at least one interference margin, a geographical area to be protected, and a set of interfering base stations, receiving, by the first network device from the second network device, a message including operational parameters for each base station in the set of base stations, determining, by the first network device, that the operational parameters cause the set of base stations to operate within the at least one interference margin for the set of base stations, and in response to determining that the operational parameters cause the set of base stations to operate within the at least one interference margin for the set of base stations, transmitting, by the first network device to a second network device, a message indicating the operational parameters have been verified.
  • Implementations can include one or more of the following features, alone, or in any combination with each other.
  • the first network device can be a frequency allocation arbitrator or coordinator device and the second network device can be a network access manager or an interference budget service associated with the first network device.
  • the set of base stations can be associated with one operator.
  • the geographic interference protection area can include a signal coverage range defined by a plurality of contour lines each separated by a contour interval, each contour line can have an associated maximum allowed aggregate interference margin for the set of base stations, and the determining of the operational parameters can include determining base station interference at each point within the signal coverage range for each of the base stations in the set of base stations such that the maximum allowed aggregate interference margin is not exceeded.
  • the maximum allowed aggregate interference margin associated with each contour line can have a time period for which the maximum allowed aggregate interference margin is valid.
  • the operational parameters for each base station in the set of base stations can include a power setting and a beam pattern modification.
  • the method can further include reading, by the second network device from a memory associated with the second network device, information for a self-interference budget allocation associated with the set of base stations, wherein the information for the selfinterference budget allocation includes an operator’s priorities of coverage/capacity for a geographic area including at least a portion of the geographic interference protection area of the protected device.
  • the operational parameters for each base station in the set of base stations can be modified within a time period for which the at least one interference margin is valid.
  • a method may include determining, by the first network device, at least one interference margin for a set of base stations within a geographic interference protection area of a protected device, determining, by the interference budget service, based on the at least one interference margin and information for a self-interference budget allocation associated with the set of base stations, operational parameters including a distribution of a maximum interference for each base station in the set of base stations, determining, by the first network device, that the operational parameters cause the set of base stations to operate within the at least one interference margin for the set of base stations, and in response to determining that the operational parameters cause the set of base stations to operate within the at least one interference margin for the set of base stations, transmitting, by the first network device to a second network device, a message indicating the operational parameters have been verified and can be employed for transmission.
  • Implementations can include one or more of the following features, alone, or in any combination with each other.
  • the first network device can be a frequency allocation arbitrator or coordinator device and the second network device can be a network access manager or a set of base stations.
  • the set of base stations can be associated with one operator.
  • the geographic interference protection area can include a signal coverage range defined by a plurality of contour lines each separated by a contour interval, each contour line can have an associated maximum allowed aggregate interference margin for the set of base stations, and the determining of the operational parameters can include determining base station interference at each point within the signal coverage range for each of the base stations in the set of base stations such that the maximum allowed aggregate interference margin is not exceeded.
  • the maximum allowed aggregate interference margin associated with each contour line can have a time period for which the maximum allowed aggregate interference margin is valid.
  • the operational parameters for each base station in the set of base stations can include a power setting and a beam pattern modification.
  • the method can further include reading, by the interference budget service from a memory associated with the interference budget service, information for a self-interference budget allocation associated with the set of base stations, wherein the information for the selfinterference budget allocation includes an operator’s priorities of coverage/capacity for a geographic area including at least a portion of the geographic interference protection area of the protected device.
  • the distribution of the maximum interference for each base station in the set of base stations can be modified within a time period for which the maximum allowed aggregate interference margin is valid.
  • FIG. 1 is a block diagram of a wireless network according to at least one example embodiment.
  • FIG. 2 is a block diagram illustrating a network architecture according to at least one example embodiment.
  • FIG. 3 is an illustration of a geographic interference protection area of a protected device.
  • FIG. 4 is an illustration of interference range contours of a protected device.
  • FIG. 5 is an illustration of the coverage area of a beam based system or base station.
  • FIG. 6 is a block diagram illustrating a network architecture according to at least one example embodiment.
  • FIG. 7 is a block diagram illustrating a signal flow according to at least one example embodiment.
  • FIG. 8 is a block diagram illustrating a signal flow according to at least one example embodiment.
  • FIG. 9 illustrates a block diagram of a method for determining operating parameters according to at least one example implementation.
  • FIG. 10 illustrates a block diagram of a method for determining operating parameters according to at least one example implementation.
  • FIG. 11 illustrates a block diagram of a method for determining operating parameters according to at least one example implementation.
  • FIG. 12 illustrates a block diagram of a method for determining operating parameters according to at least one example implementation.
  • FIG. 13 illustrates a block diagram of a method for determining operating parameters according to at least one example implementation.
  • FIG. 14 is a block diagram of a wireless station or wireless node (e.g., AP, BS, gNB, RAN node, relay node, UE or user device, network node, network entity, DU, CU-CP, CU-CP, ... or other node) according to an example embodiment.
  • a wireless station or wireless node e.g., AP, BS, gNB, RAN node, relay node, UE or user device, network node, network entity, DU, CU-CP, CU-CP, ... or other node
  • FIG. 1 is a block diagram of a wireless network 130 according to an example embodiment.
  • user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs) may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB), a BS, next generation Node B (gNB), a next generation enhanced Node B (ng-eNB), or a network node.
  • AP access point
  • eNB enhanced Node B
  • gNB next generation Node B
  • ng-eNB next generation enhanced Node B
  • a BS may also include or may be referred to as a RAN (radio access network) node, and may include a portion of a BS or a portion of a RAN node, such as (e.g., such as a centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS).
  • a BS e.g., access point (AP), base station (BS) or (e)Node B (eNB), BS, RAN node
  • AP access point
  • BS base station
  • eNB Node B
  • BS RAN node
  • RAN node may also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head.
  • BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices (or UEs) 131, 132, 133 and 135. Although only four user devices (or UEs) are shown as being connected or attached to BS 134, any number of user devices may be provided.
  • BS 134 is also connected to a core network 150 via a SI interface or NG interface 151. This is merely one simple example of a wireless network, and others may be used.
  • a base station (e.g., such as BS 134) is an example of a radio access network (RAN) node within a wireless network.
  • a BS (or a RAN node) may be or may include (or may alternatively be referred to as), e.g., an access point (AP), a gNB, an eNB, or portion thereof (such as a centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS or split gNB), or other network node.
  • a BS may include: a distributed unit (DU) network entity, such as a gNB-distributed unit (gNB- DU), and a centralized unit (CU) that may control multiple DUs.
  • the centralized unit (CU) may be split or divided into: a control plane entity, such as a gNB-centralized (or central) unit-control plane (gNB-CU-CP), and an user plane entity, such as a gNB-centralized (or central) unit-user plane (gNB-CU-UP).
  • the CU sub-entities may be provided as different logical entities or different software entities (e.g., as separate or distinct software entities, which communicate), which may be running or provided on the same hardware or server, in the cloud, etc., or may be provided on different hardware, systems or servers, e.g., physically separated or running on different systems, hardware or servers.
  • the gNB functionality may be split into a DU and a CU.
  • a distributed unit (DU) may provide or establish wireless communications with one or more UEs.
  • a DUs may provide one or more cells, and may allow UEs to communicate with and/or establish a connection to the DU in order to receive wireless services, such as allowing the UE to send or receive data.
  • a centralized (or central) unit (CU) may provide control functions and/or data-plane functions for one or more connected DUs, e.g., including control functions such as gNB control of transfer of user data, mobility control, radio access network sharing, positioning, session management etc., except those functions allocated exclusively to the DU.
  • a BS node e.g., BS, eNB, gNB, CU/DU, ...
  • RAN radio access network
  • a RAN may include one or more BSs or RAN nodes that implement a radio access technology, e.g., to allow one or more UEs to have access to a network or core network.
  • the RAN may reside between one or more user devices or UEs and a core network.
  • each RAN node e.g., BS, eNB, gNB, CU/DU, ...
  • BS may provide one or more wireless communication services for one or more UEs or user devices, e.g., to allow the UEs to have wireless access to a network, via the RAN node.
  • Each RAN node or BS may perform or provide wireless communication services, e.g., such as allowing UEs or user devices to establish a wireless connection to the RAN node, and sending data to and/or receiving data from one or more of the UEs.
  • a RAN node e.g., BS, eNB, gNB, CU/DU, ...
  • RAN nodes e.g., BS, eNB, gNB, CU/DU, ...
  • a base station may also be DU (Distributed Unit) part of IAB (Integrated Access and Backhaul) node (a.k.a. a relay node). DU facilitates the access link connect! on(s) for an IAB node.
  • IAB Integrated Access and Backhaul
  • a user device may refer to a portable computing device that includes wireless mobile communication devices operating either with or without a subscriber identification module (SIM) (which may be referred to as Universal SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, a vehicle, a sensor, and a multimedia device, as examples, or any other wireless device.
  • SIM subscriber identification module
  • a user device may also be (or may include) a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.
  • a user device may be also MT (Mobile Termination) part of IAB (Integrated Access and Backhaul) node (a.k.a. a relay node). MT facilitates the backhaul connection for an IAB node.
  • IAB Integrated Access and Backhaul
  • core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility/handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • EPC Evolved Packet Core
  • MME mobility management entity
  • gateways may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • 5G which may be referred to as New Radio (NR)
  • NR New Radio
  • 5GC New Radio
  • New Radio (5G) development may support a number of different applications or a number of different data service types, such as for example: machine type communications (MTC), enhanced machine type communication (eMTC), massive MTC (mMTC), Internet of Things (loT), and/or narrowband loT user devices, enhanced mobile broadband (eMBB), and ultrareliable and low-latency communications (URLLC).
  • MTC machine type communications
  • eMTC enhanced machine type communication
  • mMTC massive MTC
  • LoT Internet of Things
  • URLLC ultrareliable and low-latency communications
  • Many of these new 5G (NR) - related applications may require generally higher performance than previous wireless networks.
  • loT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices.
  • many sensor type applications or devices may monitor a physical condition or a status and may send a report to a server or other network device, e.g., when an event occurs.
  • Machine Type Communications MTC, or Machine to Machine communications
  • MTC Machine Type Communications
  • eMBB Enhanced mobile broadband
  • Ultra-reliable and low-latency communications is a new data service type, or new usage scenario, which may be supported for New Radio (5G) systems.
  • 5G New Radio
  • 3 GPP targets in providing connectivity with reliability corresponding to block error rate (BLER) of 10-5 and up to 1 ms U-Plane (user/data plane) latency, by way of illustrative example.
  • BLER block error rate
  • U-Plane user/data plane
  • URLLC user devices/UEs may require a significantly lower block error rate than other types of user devices/UEs as well as low latency (with or without requirement for simultaneous high reliability).
  • a URLLC UE or URLLC application on a UE
  • the various example embodiments may be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE-A, 5G (New Radio (NR)), cmWave, and/or mmWave band networks, loT, MTC, eMTC, mMTC, eMBB, URLLC, etc., or any other wireless network or wireless technology.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • 5G New Radio (NR)
  • cmWave and/or mmWave band networks
  • loT LTC
  • eMTC eMTC
  • mMTC massive machine type
  • eMBB massive machine type
  • URLLC etc.
  • CBRS citizens Broadband Radio Service
  • AS Spectrum Access System
  • IA Incumbent Access
  • PAL Priority Access Licensee
  • GAA General Access
  • PAL users must protect and accept interference from IA users and receive protection against the interferences from the GAA users.
  • GAA users must accept interference.
  • the lower tiered user needs to reduce (e.g., attenuate) transmitted power or even stop transmission to avoid causing interference to the higher tiered users. This process can be referred to as spectrum evacuation.
  • the SAS can determine which lower tiered users are to reduce power or stop transmission based on the SASs estimation of the combined or aggregate interference levels to the higher tiered users.
  • a citizens Broadband Radio Service Device can be a base station that supports the CBRS spectrum authorization framework.
  • one category of IA users can be a fixed satellite station (FSS).
  • FSS can be a protected device.
  • An FSS can have a known geographical location and can be transmitting and receiving signals in a certain frequency band.
  • CBSDs There are two classes of CBSDs.
  • Category A can include a CBSD with a nominal maximum Equivalent Isotopically Radiated Power (EIRP) of 30 dBm/lOMHz.
  • EIRP Equivalent Isotopically Radiated Power
  • Category B can include a CBSD with a maximum EIRP of 47 dBm/lOMHz.
  • CBSD When the CBSD is located in the vicinity of an FSS, in order not to interfere with the FSS operation, CBSD may not be able to transmit at the nominal max power.
  • the SAS server can be responsible for calculating the max EIRP allowed per CBSD in a time window (Coordinated Periodic Activates among SASes sometimes known as a CPAS window) to ensure the combined signals from all CBSDs is below the maximum allowed interference level of the FSS, also known as the interference budget of FSS.
  • a time window Coordinatd Periodic Activates among SASes sometimes known as a CPAS window
  • the max EIRP value from SAS server can be applied by the CBSD to all directions in its coverage area.
  • the coverage area associated with the CBSD can shrink uniformly, resulting degradation of service for users in all directions.
  • the max EIRP allowed is zero, the CBSD shuts down, and all users lose service in that particular frequency band.
  • the shared spectrum is managed by the Spectrum Access System (SAS).
  • SAS Spectrum Access System
  • a Citizen Broadband Radio Service Device (CBSD) can send a Heartbeat Request message to request authorization to transmit.
  • the SAS can grant the usage of the spectrum for a certain period of time defined by transmitExpir eTime in the Heartbeat Response Message.
  • the SAS can estimate the interference levels of each CBSD towards the IA.
  • the SAS can deny the transmission request for the CBSD by setting the transmitExpireTime field to a value that will result in a timeout.
  • the CBSD may stop transmission and evacuate the spectrum (e.g., after the transmitExpireTime expires).
  • the CBSD’s radio transmission may fall into one of the two states.
  • the first state can be transmitting when the transmitExpireTime has not expired.
  • the second state can be ceasing radio transmission after transmitExpireTime has expired.
  • An interference budget (e.g., the amount of permitted interference) for a given protected entity is equally split among all the interfering CBSDs.
  • This scheme does not promote development of high spectral efficiency features for the CBRS band, since the allowed interference is equally split independent of possible efforts of some operators to reduce interference towards the protected devices.
  • the CBSD(s) surrounding/neighbour CBSD(s) interfering with the protected device can equally benefit from this reduction in interference (e.g., by being allowed a higher transmission power without adopting interference reduction features).
  • a protected device e.g., WinnForum two-dimensional (2D) antenna patterns
  • the CBSD may cease transmissions in the channels that the CBSD cannot transmit below the requested EIRP. This can result in coverage outage for the channel where the max EIRP could not be met which may be an inefficient use of the interference budget from a CBRS operator point of view.
  • Example implementations include allocation of an interference budget to a plurality of CBSDs (e.g., an operator’s CBSDs) in a coverage area (e.g., interference area, in the vicinity) of a protected device.
  • Allocating the interference budget to a plurality of CBSDs can enable CBRS operators to fully exploit the gains generated by deploying features which aid in higher spectral efficiency and can enable CBSDs requested to transmit at an EIRP below the min capability to no longer have to cease transmissions because the CBSDs can be assigned a larger amount of the allocated interference budget to maintain a minimum desired level of capacity/coverage.
  • Example implementations can reduce processing demands on the SAS because the SAS may not have to compute all possible combinations for all existing CBSDs in the coverage area of the protected device, i.e., also trying to derive a solution which maximizes spectral efficiency and is fair to all CBSD operator’s accounting for each operators preferences.
  • Example implementations can enable an operator to trade off coverage/capacity requirements between their CBSDs (e.g., coverage can be restricted in certain cells to favour other cells).
  • FIG. 2 is a block diagram illustrating a network architecture according to at least one example embodiment.
  • the network includes a Spectrum Access System (SAS) 205, a domain proxy (DP) 210, base station(s) 215, and base station 220.
  • the SAS 205 can be configured to work as a frequency band arbitrator to coordinate the access and operations between protected devices such as incumbents (e.g., authorized federal users), Priority Access Licensee users (PAL) (e.g., service providers that are licensed from the regional governments) and General Access users (e.g., small offices).
  • the SAS can be configured to ensure protection of protected devices (e.g., incumbents and higher priority users). Rules can establish the criteria for this protection together with the maximum aggregate interference permitted.
  • the DP 210 can be a network access manager device.
  • the DP 210 can be a smart controller for a set of base stations.
  • the DP 210 can be an automated frequency control (AFC) device.
  • the DP 210 can be a logical device.
  • the DP 210 can be a network device configured to engage in network management and aggregate communications with the SAS 205 on behalf of a multiple individual base station nodes and/or networks of base station nodes. In other words, the DP 210 can be a network access manager for a group of base stations.
  • the DP 210 can be configured to provide a plurality of (a group of, a set of, etc.) CBSDs an interface to the SAS 205.
  • the DP 210 can be configured to provide enhancements for the CBSDs the DP 210 manages, such as frequency management.
  • the base station(s) 215 can be one or more (a plurality of, two or more, etc.) base stations managed by the DP 210 and the SAS 205.
  • the base station 220 can be managed by the SAS 205.
  • the DP 210 and the SAS 205 can be configured to perform one or more of the techniques for interference budget distribution described herein.
  • the SAS 205, the DP 210 and the base station(s) 215 can be communicatively coupled.
  • the SAS 205 and the base station 220 can be communicatively coupled
  • FIG. 3 is an illustration of a geographic interference protection area (or range) of a protected device.
  • a protected device 305 can be within a geographic interference protection area 310.
  • base station 315, 320, 325, 330, 335, 340 can be within the geographic interference protection area 310.
  • Base station 325 and 335 can be associated with a first operator (as indicted by the dot shading).
  • Base station 315, 320, 330, and 340 can be associated with a second operator (as indicated by the lined shading). Any base station 315, 320, 325, 330, 335 within the geographic interference protection area 310 may interfere with the protected device 305. Therefore, the geographic interference protection area 310 can be an interference protection range.
  • the protection of protected devices can be based on aggregate interference from all base stations in a given distance from the protected device (e.g., as defined in the FCC part 96 rules).
  • the interference budget e.g., the amount of permitted interference
  • the interference budget for the interfering base stations can be aggregated based on groupings (e.g., by operator) or sets of base stations.
  • the interference budget associated with the geographic interference protection area 310 can be B (e.g., for a channel).
  • the interference budget can be equally split among all the base stations 315, 320, 325, 330, 335, and 340. Therefore, each base station can be allowed 1/6B of interference.
  • the interference allowance can be assigned (e.g., aggregated) to a set of base stations by, for example, operators. Therefore, base station 325 and 335 (associated with the first operator) can be allocated (e.g., assigned) an aggregate amount of interference equal to 1/3B.
  • base station 315, 320, 330, and 340 (associated with the second operator) can be allocated (e.g., assigned) an aggregate amount of interference equal to 2/3B. Then each of the base stations can be individually allocated (e.g., assigned) an amount of interference based on, for example, operator preferences and hardware (e.g., of the base station) capabilities. For example, base station 325 could be allocated 1/4B of interference and base station 335 could be allocated 1/12B of interference based on the first operator’s preferences and the hardware capabilities of base station 325 and 335.
  • the allocated interference limits can be met using a combination of power (e.g., EIRP) and beam/antenna pattern modifications.
  • FIG. 4 is an illustration of a signal coverage range (or area) of a protected device.
  • a protected device 405 can be within a signal coverage range 425.
  • the signal coverage range 425 can be within a geographic interference protection area (e.g., geographic interference protection area 310).
  • the signal coverage range 425 (and/or the geographic interference protection area) can be defined by a plurality of contour lines 445, 450 (the remainder of the contour lines are not labelled for clarity) each separated by a contour interval 455 (the remainder of the contour intervals are not labelled for clarity).
  • Each contour line 445, 450 has an associated maximum allowed aggregate interference margin (e.g., -12, -9, -6, -3, 0, 3, and the like).
  • base station(s) 410, 415, 420 can be in the vicinity (e.g., within the geographic interference protection area) of the protected device 405. Further, base station 410 can have a signal range 430, bases station 415 can have a signal range 435 and base station 420 can have a signal range 440. Base station(s) 410, 415, 420 can be interfering base station of protected device 405 as indicated by signal range 430, 435, 440 being within (or extending to) the signal coverage range 425 of protected device 405.
  • a SAS can be informed that a group of base stations (e.g., base station(s) 410, 415, 420) belong to an operator.
  • the operator can inform the SAS (e.g., messaging causing pre-configuration settings to be stored in a memory of the SAS) of their capability for self-allocating an interference budget. Therefore, when performing computations for interference protection (e.g., for protected device 405), the SAS can use the self-interference budget allocation techniques described herein. Otherwise, the SAS can follow standard procedures for budget allocation.
  • base station(s) 410, 415, 420 can be associated with an operator and can support self-interference budget allocation. Therefore, the SAS can determine an interference budget per operator for the protected device 405 (and other protected devices not shown). For example, the SAS can determine and provide (or communicate) an interference budget per operator for the protected device 405.
  • the interference budget per operator can include a list of interfering base stations which can include base station(s) 410, 415, 420, and contour line 445, 450 information (or data) including an associated maximum allowed aggregate interference margin (e.g., -12, -9, -6, -3, 0, 3) as the max interference level allowed for the base stations in the list of base stations.
  • the interference budget per operator can include a time period during which the interfering contours are valid. This time period can establish the period over which operators may be allowed to modify their strategy in terms of interference budget management. This can allow a list of interfering base stations to dynamically vary their operational parameters within the interference constraints provided based on the contour lines in order to, for example, follow the variations of traffic demands in the geographical area the base station(s) 410, 415, 420 cover (e.g., within signal range 430, 435, 440).
  • the SAS (e.g., SAS 205, 605) can determine the interference budget per operator based on the information for self-interference budget allocation capable base station/DP (e.g., as stored in the memory of the SAS). Then, the DP or other logical entity (e.g., a service or microservice in the SAS) can allocate the allowed interference margin based on an operators pre-configured priorities of coverage and/or capacity for a given area (e.g., the signal coverage range 430 vs 435 and/or geographic interference protection area 530 vs 535).
  • the interference budget requirements can be met using a combination of power (e.g., EIRP) and beam/antenna pattern modifications that also consider operator preferences and hardware (e.g., of the base station) capabilities.
  • the DP or the other logical entity can inform the SAS of the base station operational parameters.
  • the SAS can determine (e.g., verify) whether a criterion is met (e.g., the max interference margins are not exceeded) based on the provided base station operational parameters (e.g., power (e.g., EIRP) values and/or antenna patterns).
  • the SAS can enable (e.g., communicate a confirmation or grant) the base stations to operate using the operational parameters.
  • FIG. 5 is an illustration of a beam coverage area. As shown in FIG.
  • the beam coverage area includes a protected device 505 and a base station 510.
  • the protected device 505 can be protected device can be at least one of a base station, a fixed microwave station, a radio astronomy station and a fixed satellite station (FSS) base station, a military radar, and/or the like and the base station 510 can be a CBSD.
  • the protected device 505 can have a coverage area 515.
  • the base station 510 can have a steering range 520.
  • the steering range 520 can be a full steering range.
  • the base station 510 (and other base stations not shown) can be interfering with the protected device 505.
  • spatial range 525 can be the interfering spatial range that has an angle OB.
  • the base station 510 can have a max EIRP level 1530 at which a signal (e.g., associated with at least one beam) generated by the base station 510 interferes with the protected device 505. Therefore, the base station 510 can be assigned a max power (e.g., EIRP) level 535 at which a signal generated by the base station 510 does not interfere (or interferes within a threshold amount of interference) with the protected device 505.
  • EIRP max power
  • the base station 510 illustrates the base station 510 having reduced or attenuated signal power such that all, or substantially all, of the signals in the steering range 520 are generated at the max power level 535.
  • the base station 510 reduce or attenuate signal power based on base station operational parameters determined by a SAS.
  • FIG. 6 is a block diagram illustrating a network architecture according to at least one example embodiment.
  • the network architecture associated with Operator A includes a domain proxy 620 communicatively coupled to base station(s) 625.
  • the domain proxy 620 is communicatively coupled to a service 610 of a SAS 605.
  • the network architecture associated with Operator B includes a domain proxy 630 communicatively coupled to base station(s) 635.
  • the domain proxy 630 is communicatively coupled to a service 615 of the SAS 605.
  • the service 615 is also communicatively coupled to base station 650.
  • the network architecture associated with Operator C includes a domain proxy 640 communicatively coupled to base station(s) 645.
  • the domain proxy 640 is communicatively coupled to the SAS 605.
  • the SAS 605 is also communicatively coupled to base station 655.
  • Example implementations including use of a SAS service e.g., the architectures of Operator A and Operator B
  • FIGS. 8 signal flow
  • 10 method
  • Example implementations without the use of a SAS service e.g., the architecture of Operator C
  • FIGS. 7 signal flow
  • 9 method
  • the SAS 605 can be configured to determine the interference margin for each of Operator A, Operator B, and Operator C.
  • the SAS 605 can be further configured to determine whether (e.g., verify) a criterion is met (e.g., the max interference margins are not exceeded) based on the base station operational parameters.
  • the domain proxy 640 can determine a distribution of the interference margin for Operator C and to determine operational parameters for base station(s) 645. The distribution of the interference margin can be determined based on Operator C coverage and capacity priorities.
  • the SAS 605 can assign the base station 655 an interference margin based on an even distribution of interference margin amongst all interfering base stations. Therefore, the SAS 605 can subtract the interference margin associated with base station 655 from the interference margin for Operator C and communicate the remainder of the interference margin for Operator C to domain proxy 640.
  • the service 610, 615 can determine a distribution of the interference margin for Operator A and Operator B respectively.
  • the service 610, 615 can be configured to determine operational parameters for base station(s) 625, 635, 650.
  • the distribution of the interference margin can be determined based on Operator A and Operator B coverage and capacity priorities.
  • the service 615 can determine the interference margin and the operational parameters for base station 650. Therefore, the service 615 can subtract the interference margin associated with base station 650 from the interference margin for Operator B and use the remainder of the interference margin for Operator B to determine the interference margin and the operational parameters for base station(s) 635.
  • FIG. 7 is a block diagram illustrating a signal flow (for the aforementioned first implementation) according to at least one example embodiment.
  • a feature capability exchange between the base station/domain proxy (BS/DP) 705 and the SAS 710.
  • the feature capability exchange can include a base station (e.g., base station(s) 625) declaration for support of self-interference margin allocation.
  • the SAS 710 can determine the protected device interference margin.
  • the protected device interference margin can be determined per a plurality of (group of, set of, etc.) base stations based on an even split of interference margin per interfering base station and a number of base stations associated with an Operator.
  • the protected device interference margin can be determined during a time window. For example, during a Coordinated Periodic Activities among SASes (CPAS) window.
  • CPAS Coordinated Periodic Activities among SASes
  • a message can be communicated from the BS/DP 705 to the SAS 710.
  • the message can include a request (e.g., a heartbeat request).
  • the message can be configured to inform the SAS 710 that the BS/DP 705 of the current transmission status of the BSs.
  • a message can be communicated from the SAS 710 to the BS/DP 705.
  • the message can include a response (e.g., a heartbeat response) to communication 725.
  • the message can include operational parameters per base station including max interference margin per set of base station and per protected device.
  • the BS/DP 705 can determine a distribution of interference margin based on operator coverage and capacity priorities.
  • the BS/DP 705 can further determine operational parameters per base station based on the determined distribution of interference margin.
  • a message can be communicated from the BS/DP 705 to the SAS 710.
  • the message can include a request (e.g., a grant update request).
  • the message can the new operational parameters per base station (e.g., as determined in block 735) which can include different power (e.g., EIRP) and/or antenna pattern variations.
  • the SAS 710 can determine (e.g., verify) whether a criterion is met (e.g., the max interference margins are not exceeded) based on the new operational parameters per base station (e.g., power (e.g., EIRP) values and/or antenna patterns).
  • a message can be communicated from the SAS 710 to the BS/DP 705.
  • the message can include a response (e.g., a grant update response) to communication 740.
  • the message can be in response to determining the criterion is met and that the base stations to operate using the operational parameters.
  • the protected device interference margin can be determined per a plurality of (group of, set of, etc.) base stations based on an even split of interference margin per interfering base station (e.g., base station 650) and a number of base stations associated with an Operator (e.g., base stations 635).
  • the protected device interference margin can be determined during a time window. For example, during a Coordinated Periodic Activities among SASes (CPAS) window.
  • CPAS Coordinated Periodic Activities among SASes
  • interference budget information for plurality of BS for a given geographical area is communicated from the SAS 810 to the service 815.
  • the interference budget information can be the interference budget assigned to the plurality of (group of, set of, etc.) base stations associated with an operator.
  • the service 815 determine per base station capability and priority information in terms of power (e.g., ERIP min/max) and hardware (e.g., beamforming) capabilities.
  • the priorities of e.g., coverage may be time variant to enable coverage adaptation to busy hour traffic in different geographical areas. For example, capability and priority information can be read from a memory of the SAS 810.
  • the memory of the SAS 810 can be pre-configured (e.g., when a base station is added to the network) to include capability and priority information associated with each base station in the network.
  • the service 815 can determine a distribution of interference margin based on operator coverage and capacity priorities.
  • the service 815 can further determine operational parameters per base station based on the determined distribution of interference margin.
  • communication e.g., via messaging
  • the operational parameters per base station are communicated from the service 815 to the SAS 810.
  • the SAS 810 can determine (e.g., verify) whether a criterion is met (e.g., the max interference margins are not exceeded) based on the new operational parameters per base station (e.g., power (e.g., EIRP) values and/or antenna patterns).
  • a message can be communicated from the BS/DP 805 to the SAS 810.
  • the message can include a request (e.g., a heartbeat request).
  • the message can be configured to inform the SAS 810 that the BS/DP 805 of the current status of transmission of the BSs.
  • a message can be communicated from the SAS 810 to the BS/DP 805.
  • the message can include a response (e.g., a heartbeat response) to communication 725.
  • the message can include the verified operational parameters per base station including max interference margin per set of base station and per protected device.
  • a message can be communicated from the BS/DP 805 to the SAS 810.
  • the message can include a request (e.g., a grant update request).
  • the message can the established operational parameters per base station (e.g., as configured by the BS/DP 805) which can include different power (e.g., EIRP) and/or antenna pattern variations.
  • a message can be communicated from the SAS 810 to the BS/DP 805.
  • the message can include a response (e.g., a grant update response) to communication 870.
  • the message can be in response to storing (e.g., in a memory of the SAS 810) the established operational parameters.
  • FIGS. 9-12 are flowcharts of methods according to example embodiments.
  • the methods described with regard to FIGS. 9-12 may be performed due to the execution of software code stored in a memory (e.g., a non-transitory computer readable storage medium) associated with an apparatus (e.g., base station(s) 215, 220, 625, 635, 645, 650, 655 and/or SAS 205, 605) and executed by at least one processor associated with the apparatus.
  • the software code can be configured to implement the techniques described herein.
  • alternative embodiments are contemplated such as a system embodied as a special purpose processor.
  • processors and/or special purpose processor may execute the method described below with regard to FIGS. 9-12.
  • FIG. 9 illustrates a block diagram of a method for determining operating parameters according to at least one example implementation.
  • a base station (BS) and/or domain proxy (DP) informs a SAS of the BS/DP’s support to self-allocate an interference budget.
  • a message(s) can be communicated between the BS/DP and the SAS.
  • the message(s) can be configured to perform a feature capability exchange between the BS/DP and the SAS.
  • the feature capability exchange can include a base station declaration for support of self-interference margin allocation.
  • the BS/DP could employ a WINNF defined Group and an associated Group Id to inform the SAS base station(s) are managed by the same operator and hence request to manage their interference budget.
  • the SAS performs computations to ensure that the aggregate interference for all protected entities are below established limits.
  • the SAS can determine the protected device interference margin.
  • the protected device interference margin can be determined per a plurality of (group of, set of, etc.) base stations based on an even split of interference margin per interfering base station and a number of base stations associated with an Operator.
  • the protected device interference margin can be determined during a time window. For example, during a Coordinated Periodic Activities among SASes (CPAS) window.
  • CPAS Coordinated Periodic Activities among SASes
  • An interference budget per operator can include a list of interfering base stations and contour line information (or data) including an associated maximum allowed aggregate interference margin (see FIG. 4) as the max interference level allowed for the base stations in the list of base stations.
  • the interference budget per operator can include a time period during which the interfering contours are valid. This time period can establish the period over which operators may be allowed to modify their strategy in terms of interference budget management. This can allow a list of interfering base stations to dynamically vary their operational parameters within the interference constraints provided based on the contour lines in order to, for example, follow the variations of traffic demands in the geographical area the base station(s) cover (e.g., within a signal range).
  • Each SAS can allocate a power limit (e.g., an EIRP limit) to a base station (e.g., a CBSD) (unless otherwise limited by the base station’s radio capabilities or requested power) such that the mean of the interference contribution of the base station for every qualifying protected point for every protected entity is allowed by the SAS to be at least (1/Np,ch) of the allowable interference protection level for the given base station’s most constraining applicable protected point.
  • a power limit e.g., an EIRP limit
  • a base station e.g., a CBSD
  • the SAS having the information (or data) of which base station(s) belong to which operator the SAS can provide a contour by multiplying the allowed interference per base station (1/Np,ch) by the number of the operators base station(s) interfering at the point of the contour.
  • the DP determines the optimal parameter configuration per base station. For example, the DP can determine a distribution of interference margin based on operator coverage and capacity priorities. The DP can further determine operational parameters per base station based on the determined distribution of interference margin.
  • the DP can be aware (e.g., have stored in memory) of the EIRP and beamforming capabilities of base station(s) (CBSDs) managed by the DP.
  • CBSDs base station(s)
  • preconfigured operator priorities in terms of cell coverage could be considered. For example, sacrifice coverage by reducing EIRP power in a cell near the protected device, in exchange for higher power in multiple cells away from the entity with much higher user payload during the busy hour.
  • the DP can derive the optimal configuration considering each base station(s) (CBSDs) power (EIRP) and beamforming capabilities. This may result in attenuated or muted beams or null steering depending on the operator pre-defined priorities and allocated interference budget.
  • An example of how the DP could establish the operational parameters for a list of CBSDs interfering a protected device, could be based on an algorithm.
  • the algorithm can include using the interference contours to determine the level of interference at every considered point from each base station in the list, assuming max power (EIRP) and the base station preferred antenna pattern.
  • EIRP max power
  • determine in a delta contour the difference between allowed interference and required interference for the scenario estimated for every point in the contour.
  • This minimum delta can be at a value (e.g., 3dB) that can indicate the change in the interference level contributed by this base station would need to be reduced by a min of the value (e.g., 3dB), re-compute the contour considering these changes, and assess if the interference for the point under consideration is below the max established value by the contour. If the interference is not below the max, select the next lowest priority in the base station list and repeat. If the interference is below the max, select the next point in the contour and repeat until all points in the contour have been covered.
  • a value e.g., 3dB
  • some base stations could be on various lists for impacted protected devices and the base station’s interference to more than one (e.g., most, all) protected devices can be considered.
  • the DP can have a mask with power (EIRP) and or antenna pattern limitations per base station. The DP can fine tune based on base station capability, the EIRP value and/or antenna patterns per CBSD in the list.
  • the DP can inform the SAS.
  • a message can be communicated from the DP to the SAS.
  • the message can include the determined operating parameters per base station.
  • the SAS can verify that interference budget allocated to the operator’s base stations is not exceeded with the proposed parameterization and proceed to allow the use of these via, e.g., a Grant Update Response message.
  • the DP may determine that the optimal configuration would entail varying the parameterization of cells, within the interference budget allocated during different periods of the day to accommodate for geographically varying busy hours. In these scenarios the DP could trigger a Grant update message with a new set of operational parameters when deemed required to meet the traffic variation needs, as long as the validity period of the interference contour provided by the SAS has not expired. For example, during events at a stadium the DP may decide to prioritize its interference budget at the base station(s) covering the stadium location only during the duration of the events.
  • the computation to allocate the interference budget provided could reside in the SAS as a service (e.g., microservice) and could be provided as a value-added service from the SAS.
  • the architecture models for the first embodiment and the second embodiment are not mutually exclusive and both can co-exist (see FIG. 6). For example, the second embodiment can be provided to operators whose DP does not support the capability to determine the best method to distribute their interference budget.
  • FIG. 10 illustrates a block diagram of a method for determining operating parameters according to at least one example implementation.
  • a base station (BS) and/or domain proxy (DP) informs a SAS of the BS/DP’s support to self-allocate an interference budget.
  • a message(s) can be communicated between the BS/DP and the SAS.
  • the message(s) can be configured to perform a feature capability exchange between the BS/DP and the SAS.
  • the feature capability exchange can include a base station declaration for support of self-interference margin allocation.
  • the BS/DP could employ a WINNF defined Group and an associated Group Id to inform the SAS base station(s) are managed by the same operator and hence request to manage their interference budget.
  • the SAS performs computations to ensure that the aggregate interference for all protected entities are below established limits.
  • the SAS can determine the protected device interference margin.
  • the protected device interference margin can be determined per a plurality of (group of, set of, etc.) base stations based on an even split of interference margin per interfering base station and a number of base stations associated with an Operator.
  • the protected device interference margin can be determined during a time window. For example, during a Coordinated Periodic Activities among SASes (CPAS) window.
  • CPAS Coordinated Periodic Activities among SASes
  • An interference budget per operator can include a list of interfering base stations and contour line information (or data) including an associated maximum allowed aggregate interference margin (see FIG. 4) as the max interference level allowed for the base stations in the list of base stations.
  • the interference budget per operator can include a time period during which the interfering contours are valid. This time period can establish the period over which operators may be allowed to modify their strategy in terms of interference budget management. This can allow a list of interfering base stations to dynamically vary their operational parameters within the interference constraints provided based on the contour lines in order to, for example, follow the variations of traffic demands in the geographical area the base station(s) cover (e.g., within a signal range).
  • Each SAS can allocate a power limit (e.g., an EIRP limit) to a base station (e.g., a CBSD) (unless otherwise limited by the base station’s radio capabilities or requested power) such that the mean of the interference contribution of the base station for every qualifying protected point for every protected entity is allowed by the SAS to be at least (1/Np,ch) of the allowable interference protection level for the given base station’s most constraining applicable protected point.
  • a power limit e.g., an EIRP limit
  • a base station e.g., a CBSD
  • the SAS having the information (or data) of which base station(s) belong to which operator the SAS can provide a contour by multiplying the allowed interference per base station by the number of the operators base station(s) interfering at the point of the contour.
  • step SI 015 in response to receiving the interference budget details from the SAS, the SAS (e.g., as a service, see FIG. 6) determines the optimal parameter configuration per base station. For example, the SAS can determine a distribution of interference margin based on operator coverage and capacity priorities. The SAS can further determine operational parameters per base station based on the determined distribution of interference margin.
  • the SAS can be aware (e.g., have stored in memory) of the EIRP and beamforming capabilities of base station(s) (CBSDs) managed by an associated DP.
  • CBSDs base station(s)
  • preconfigured operator priorities in terms of cell coverage could be considered. For example, sacrifice coverage by reducing EIRP power in a cell near the protected device, in exchange for higher power in multiple cells away from the entity with much higher user payload during the busy hour.
  • the SAS can derive the optimal configuration considering each base station(s) (CBSDs) power (EIRP) and beamforming capabilities. This may result in attenuated or muted beams or null steering depending on the operator pre-defined priorities and allocated interference budget.
  • step SI 020 in response to determining the optimal operating parameters, the SAS verifies the operational parameters. For example, the SAS can verify that interference budget allocated to the operator’s base stations is not exceeded with the proposed parameterization and proceed to allow the use of these via, e.g., a Grant Update Response.
  • FIG. 11 is a flowchart illustrating operation of a network device.
  • Operation SI 105 includes receiving, by a first network device from a second network device, a message including at least one maximum interference margin for a set of base stations within a geographic interference protection area of a protected device.
  • Operation SI 110 includes determining, by the first network device, operational parameters including a distribution of the maximum interference for each base station in the set of base stations.
  • Operation S 1115 includes transmitting, by the first network device to the second network device, a grant update request message including the operational parameters for each base station in the set of base stations.
  • Operation SI 120 includes receiving, by the first network device from the second network device, a grant update response message including a verification of the operational parameters for each base station in the set of base stations.
  • Example 2 The method of Example 1, wherein the first network device is a network access manager and the second network device is a frequency allocation arbitrator or coordinator device.
  • Example 3 The method of Example 1, wherein the operational parameters are modified without exceeding the at least one maximum interference margin.
  • Example 4 The method of Example 1 to Example 3, wherein the set of base stations is associated with one operator.
  • Example 5 The method of Example 1 to Example 4, wherein the geographic interference protection area includes a signal coverage range defined by a plurality of contour lines each separated by a contour interval, each contour line has an associated maximum allowed aggregate interference margin for the set of base stations, and the determining of the operational parameters includes determining base station interference at each point within the signal coverage range for each of the base stations in the set of base stations such that the maximum allowed aggregate interference margin is not exceeded.
  • Example 6 The method of Example 5, wherein the maximum allowed aggregate interference margin associated with each contour line has a time period for which the maximum allowed aggregate interference margin is valid.
  • Example 7 The method of Example 1 to Example 6, wherein the operational parameters for each base station in the set of base stations include a power setting and a beam pattern modification.
  • Example 8 The method of Example 1 to Example 7, further including reading, by the first network device from a memory associated with the first network device, information for a self-interference budget allocation associated with the set of base stations, wherein the information for the self-interference budget allocation includes an operator’s priorities of coverage/capacity for a geographic area including at least a portion of the geographic interference protection area of the protected device.
  • Example 9 The method of Example 1 to Example 8, wherein the distribution of the maximum interference for each base station in the set of base stations is modified within a time period for which the maximum allowed aggregate interference margin is valid.
  • FIG. 12 is a flowchart illustrating operation of a network device.
  • Operation SI 205 includes determining, by a first network device, at least one interference margin for a set of base stations within a geographic interference protection area of a protected device.
  • Operation SI 210 includes transmitting, by the first network device to a second network device, a message including the at least one interference margin, a geographical area to be protected, and a set of interfering base stations.
  • Operation 1215 includes receiving, by the first network device from the second network device, a message including operational parameters for each base station in the set of base stations.
  • Operation SI 220 includes determining, by the first network device, that the operational parameters cause the set of base stations to operate within the at least one interference margin for the set of base stations.
  • Operation SI 225 includes in response to determining that the operational parameters cause the set of base stations to operate within the at least one interference margin for the set of base stations, transmitting, by the first network device to a second network device, a message indicating the operational parameters have been verified.
  • Example 11 The method of Example 10, wherein the first network device is a frequency allocation arbitrator or coordinator device and the second network device is a network access manager or an interference budget service associated with the first network device.
  • Example 12 The method of Example 10 and Example 11 , wherein the set of base stations is associated with one operator.
  • Example 13 The method of Example 10 to Example 12, wherein the geographic interference protection area includes a signal coverage range defined by a plurality of contour lines each separated by a contour interval, each contour line has an associated maximum allowed aggregate interference margin for the set of base stations, and the determining of the operational parameters includes determining base station interference at each point within the signal coverage range for each of the base stations in the set of base stations such that the maximum allowed aggregate interference margin is not exceeded.
  • Example 14 The method of Example 13, wherein the maximum allowed aggregate interference margin associated with each contour line has a time period for which the maximum allowed aggregate interference margin is valid.
  • Example 15 The method of Example 10 to Example 14, wherein the operational parameters for each base station in the set of base stations include a power setting and a beam pattern modification.
  • Example 16 The method of Example 10 to Example 15 further including reading, by the second network device from a memory associated with the second network device, information for a self-interference budget allocation associated with the set of base stations, wherein the information for the self-interference budget allocation includes an operator’s priorities of coverage/capacity for a geographic area including at least a portion of the geographic interference protection area of the protected device.
  • Example 17 The method of Example 10 to Example 16, wherein the operational parameters for each base station in the set of base stations is modified within a time period for which the at least one interference margin is valid.
  • FIG. 13 is a flowchart illustrating operation of a network device.
  • Operation SI 305 includes determining, by the first network device, at least one interference margin for a set of base stations within a geographic interference protection area of a protected device.
  • Operation SI 310 includes determining, by the interference budget service, based on the at least one interference margin and information for a selfinterference budget allocation associated with the set of base stations, operational parameters including a distribution of a maximum interference for each base station in the set of base stations.
  • Operation S 1315 includes determining, by the first network device, that the operational parameters cause the set of base stations to operate within the at least one interference margin for the set of base stations.
  • Operation SI 320 includes in response to determining that the operational parameters cause the set of base stations to operate within the at least one interference margin for the set of base stations, transmitting, by the first network device to a second network device, a message indicating the operational parameters have been verified and can be employed for transmission.
  • Example 19 The method of Example 18, wherein the first network device is a frequency allocation arbitrator or coordinator device and the second network device is a network access manager or a set of base stations.
  • Example 20 The method of Example 18 and Example 19, wherein the set of base stations is associated with one operator.
  • Example 21 The method of Example 18 to Example 20, wherein the geographic interference protection area includes a signal coverage range defined by a plurality of contour lines each separated by a contour interval, each contour line has an associated maximum allowed aggregate interference margin for the set of base stations, and the determining of the operational parameters includes determining base station interference at each point within the signal coverage range for each of the base stations in the set of base stations such that the maximum allowed aggregate interference margin is not exceeded.
  • Example 22 The method of Example 21, wherein the maximum allowed aggregate interference margin associated with each contour line has a time period for which the maximum allowed aggregate interference margin is valid.
  • Example 23 The method of Example 18 to Example 22, wherein the operational parameters for each base station in the set of base stations include a power setting and a beam pattern modification.
  • Example 24 The method of Example 18 to Example 23, further including reading, by the interference budget service from a memory associated with the interference budget service, information for a self-interference budget allocation associated with the set of base stations, wherein the information for the self-interference budget allocation includes an operator’s priorities of coverage/capacity for a geographic area including at least a portion of the geographic interference protection area of the protected device.
  • Example 25 The method of Example 18 to Example 24, wherein the distribution of the maximum interference for each base station in the set of base stations is modified within a time period for which the maximum allowed aggregate interference margin is valid.
  • Example 26 A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any of Examples 1-25.
  • Example 27 An apparatus comprising means for performing the method of any of Examples 1-25.
  • Example 28 An apparatus comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform the method of any of Examples 1-25.
  • FIG. 14 is a block diagram of a wireless station 1400 or wireless node or network node 1400 according to an example embodiment.
  • the wireless node or wireless station or network node 1400 may include, e.g., one or more of an AP, BS, gNB, RAN node, relay node, UE or user device, network node, network entity, DU, CU-CP, CU-CP, ... or other node) according to an example embodiment.
  • the wireless station 1400 may include, for example, one or more (e.g., two as shown in FIG. 14) RF (radio frequency) or wireless transceivers 1402A, 1402B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals.
  • the wireless station also includes a processor or control unit/entity (controller) 1404 to execute instructions or software and control transmission and receptions of signals, and a memory 1406 to store data and/or instructions.
  • Processor 1404 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein.
  • Processor 1404 which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 1402 (1402A or 1402B).
  • Processor 1404 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 1402, for example).
  • Processor 1404 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above.
  • Processor 1404 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these.
  • processor 1404 and transceiver 1402 together may be considered as a wireless transmitter/receiver system, for example.
  • a controller (or processor) 1408 may execute software and instructions, and may provide overall control for the station 1400, and may provide control for other systems not shown in FIG. 14, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 1400, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
  • a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 1404, or other controller or processor, performing one or more of the functions or tasks described above.
  • RF or wireless transceiver(s) 1402A/1402B may receive signals or data and/or transmit or send signals or data.
  • Processor 1404 (and possibly transceivers 1402A/1402B) may control the RF or wireless transceiver 1402A or 1402B to receive, send, broadcast or transmit signals or data.
  • the example embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other communication systems.
  • Another example of a suitable communications system is the 5G system. It is assumed that network architecture in 5G will be quite similar to that of the LTE -advanced. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input - multiple output
  • NFV network functions virtualization
  • a virtualized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized.
  • radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be non-existent.
  • Example embodiments of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them.
  • Example embodiments may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
  • Embodiments may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium.
  • Embodiments of the various techniques may also include embodiments provided via transitory signals or media, and/or programs and/or software embodiments that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks.
  • embodiments may be provided via machine type communications (MTC), and also via an Internet of Things (IOT).
  • MTC machine type communications
  • IOT Internet of Things
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • carrier include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • example embodiments of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities).
  • CPS may enable the embodiment and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, ...) embedded in physical objects at different locations.
  • ICT devices sensors, actuators, processors microcontrollers, ...) embedded in physical objects at different locations.
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various embodiments of techniques described herein may be provided via one or more of these technologies.
  • a computer program such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment.
  • a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
  • Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data.
  • a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
  • Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks
  • magneto-optical disks e.g., CD-ROM and DVD-ROM disks.
  • the processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
  • embodiments may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
  • a display device e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor
  • a user interface such as a keyboard and a pointing device, e.g., a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
  • Example embodiments may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an embodiment, or any combination of such back-end, middleware, or front-end components.
  • Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
  • LAN local area network
  • WAN wide area network

Landscapes

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

Abstract

La présente invention concerne un procédé qui peut comprendre la réception, par un premier dispositif de réseau à partir d'un second dispositif de réseau, d'un message comprenant au moins une marge d'interférence maximale pour un ensemble de stations de base dans une zone de protection d'interférence géographique d'un dispositif protégé, la détermination, par le premier dispositif de réseau, des paramètres de fonctionnement comprenant une distribution de l'interférence maximale pour chaque station de base dans l'ensemble de stations de base, la transmission, par le premier dispositif de réseau au second dispositif de réseau, d'un message de demande de mise à jour d'autorisation comprenant les paramètres opérationnels pour chaque station de base dans l'ensemble de stations de base, et la réception, par le premier dispositif de réseau en provenance du second dispositif de réseau, d'un message de réponse de mise à jour d'autorisation comprenant une vérification des paramètres de fonctionnement pour chaque station de base dans l'ensemble de stations de base.
PCT/EP2021/082609 2020-11-23 2021-11-23 Distribution de budget d'interférence sur la base d'un groupe WO2022106713A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063198935P 2020-11-23 2020-11-23
US63/198,935 2020-11-23

Publications (1)

Publication Number Publication Date
WO2022106713A1 true WO2022106713A1 (fr) 2022-05-27

Family

ID=78821405

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2021/082609 WO2022106713A1 (fr) 2020-11-23 2021-11-23 Distribution de budget d'interférence sur la base d'un groupe

Country Status (1)

Country Link
WO (1) WO2022106713A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016195751A1 (fr) * 2015-05-29 2016-12-08 Intel Corporation Nœud b évolué, contrôleur de système d'accès au spectre (sas), et procédé de communication dans un spectre partagé
EP3422756A1 (fr) * 2017-06-30 2019-01-02 INTEL Corporation Coordination d 'interférences dans un système d' accès partagé sous licence d 'un système de communication mobile
US20190215698A1 (en) * 2016-05-11 2019-07-11 Telefonaktiebolaget Lm Ericsson (Publ) Validation of pal protection areas

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016195751A1 (fr) * 2015-05-29 2016-12-08 Intel Corporation Nœud b évolué, contrôleur de système d'accès au spectre (sas), et procédé de communication dans un spectre partagé
US20190215698A1 (en) * 2016-05-11 2019-07-11 Telefonaktiebolaget Lm Ericsson (Publ) Validation of pal protection areas
EP3422756A1 (fr) * 2017-06-30 2019-01-02 INTEL Corporation Coordination d 'interférences dans un système d' accès partagé sous licence d 'un système de communication mobile

Similar Documents

Publication Publication Date Title
US10701751B2 (en) Signaling for multiple radio access technology dual connectivity in wireless network
EP3711383B1 (fr) Réduction de puissance maximale pour une partie de bande passante de liaison montante pour des réseaux sans fil
US11190951B2 (en) Method and apparatus for dimensioning base stations and determining spectrum availability in a spectrum controlled network
US10743262B2 (en) Beam management for interference mitigation for wireless networks
CN111226351B (zh) 一种广播波束域调整方法及装置
US11516679B2 (en) Communication control device, communication control method, and computer program
US20170289917A1 (en) Dynamic time division duplex interference mitigation in a wireless network
JPWO2019130922A1 (ja) 通信制御装置、通信制御方法およびコンピュータプログラム
US20230403591A1 (en) Group based beam reporting
KR20180129423A (ko) 무선 통신 시스템에서 간섭을 관리하기 위한 장치 및 방법
WO2022101073A1 (fr) Réduction des effets d'un recul de puissance
US11224044B1 (en) Partial spectrum evacuation in citizens broadband radio service (CBRS) networks
US20220263615A1 (en) Synchronization signaling block compatible interference coordination patterns to reduce interference in wireless networks
US11696145B2 (en) Registered and unregistered operation for shared band wireless nodes within wireless networks
WO2022106713A1 (fr) Distribution de budget d'interférence sur la base d'un groupe
US10250349B2 (en) Coordinated interference cancellation in wireless network
US11924769B2 (en) Exploitation of transmitter (TX) power for each band dual up-link (UL) carrier aggregation (CA)
WO2019096386A1 (fr) Réduction d'interférence de liaison montante pour réseaux sans fil
US20220394771A1 (en) Spectrum extension for initial access
US12009905B2 (en) Dynamic cellular network interference management
Ponomarenko-Timofeev Uplink Transmission Control Methods in LSA-Enabled Cellular Networks
EP4381794A1 (fr) Mise à jour de configuration de mesure pendant une reconfiguration conditionnelle destinée à une pscell pour réseaux sans fil
CN117997500A (zh) 报告低或零最大灵敏度劣化的区域

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: 21819407

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: 21819407

Country of ref document: EP

Kind code of ref document: A1