Did you know that you can navigate the posts by swiping left and right?

Flex grid for entanglement : one switch instead of a tree of filters

04 Apr 2026 . category: networking . Comments
#networking #fiber #quantum

classical network operators have a word for deciding who gets how much capacity: provisioning. you pick the split, you push a config, the box does it, and nobody drives to the site with a screwdriver.

quantum networks have exactly the same need and, for a long time, none of the tooling. the entangled photons got divided up at install time by the physical layout of a tree of optical filters. want a different split? go into the rack.

this paper is the one that fixed that. Lingaraju et al., “Adaptive bandwidth management for entanglement distribution in quantum networks,” Optica 8(3), 329 (2021). four users, one entangled photon source, one wavelength selective switch, and two-party rates that start out a factor of 4200 apart and end up within a factor of two. it is four pages long and most of it is a networking paper wearing a quantum hat.

below: what the paper did, what the following five years did with it, and what i think is still missing.

the setup, for people who don’t do quantum

one source, many users

the architecture here is called entanglement distribution by a central provider. one box in the middle makes entangled photon pairs, and every user gets a fiber to that box. no user needs a source, a laser, or a crystal. they need a fiber and a detector.

the source in this paper is spontaneous parametric down-conversion: a pump photon goes into a nonlinear crystal and occasionally splits into two lower-energy photons. the pair comes out entangled in polarization, and, importantly, over a wide band of wavelengths at once. that band is the resource being divided.

wavelength is the address

this is the part that makes the whole scheme work, and it is not obvious.

the split obeys energy conservation. the two daughter photons always add up to the pump:

    ω_signal  +  ω_idler  =  ω_pump

so if you hand Alice a slice of spectrum 100 GHz above the center of the band, her photons’ partners are all sitting 100 GHz below the center. give that lower slice to Bob and Alice and Bob now share entanglement. give it to Carol instead and Alice and Bob share nothing at all, even though both are connected to the same box by the same kind of fiber.

you do not route entanglement by choosing a destination. you route it by handing two people the two halves of the same energy budget. the switch in the middle is not deciding where photons go so much as deciding which pairs of people are energy-matched. that is why this is a spectrum allocation problem rather than a switching problem, and why the entire vocabulary of flexible-grid WDM turns out to apply.

what you actually measure

each user has a polarization analyzer and a single photon detector. a detector clicking on its own tells you almost nothing, because dark counts and stray light click too. what matters is a coincidence: Alice clicks and Bob clicks inside the same short window, so those two probably came from the same pair.

the coincidence rate on a link is the closest thing this network has to bandwidth. it is what the paper uses as its service metric, and, as we will get to, that choice is one of the paper’s own stated weaknesses.

the problem with a tree of filters

the state of the art before this paper was passive. Wengerowsky et al. (Nature 564, 225, 2018) built a fully and simultaneously connected four-user network out of nothing but DWDM filters, which is a lovely result: no active components, no power, nothing to configure. Joshi et al. (Sci. Adv. 6, eaba0959, 2020) took it to eight users by having pairs of users share a slice through a 50:50 splitter, at the cost of a hard 3 dB.

the trouble is what happens to the filter tree as N grows.

full connectivity needs 2N² − 3N filters. worse than the count is the path length. a photon headed for the lucky channel passes through two filters. the photon headed for the worst channel gets bounced off, at minimum, N² − N filter ports before it is finally transmitted. at the paper’s assumed 0.25 dB per reflection and 0.6 dB per transmission, that is 3.6 dB at four users and 60.6 dB at sixteen.

the filter count and the worst case are both bad. the spread between channels is worse. one link on your network is fine and another is 56 dB down. you cannot engineer a service around that, because every link needs its own integration time, its own noise budget, and its own expectations.

worst-case channel loss as the network growsthe paper's own comparison, Fig. 1 inset. 0.25 dB per DWDM reflection, 0.6 dB for the final transmission, 4.5 dB for the switch.DWDM filter tree, worst channelwavelength selective switch, every channel
filters needed
tree, worst channel
switch, any channel4.5 dB
photons that survive the worst path

the crossover sits between four and five users. below that the passive tree really is better, which the authors say plainly. above it, the tree stops being a design and starts being a liability.

the switch

a wavelength selective switch is a stock ROADM part. light comes in one fiber, a grating spreads it across a liquid crystal spatial light modulator, and each column of pixels steers its little bit of spectrum to whichever output fiber you tell it to. it is how carriers add and drop wavelengths without touching hardware, and it is the reason “flexible grid” exists as a concept: the channels do not have to be a fixed 50 GHz or 100 GHz wide any more, they can be whatever width the job needs.

the paper uses a Finisar WaveShaper 4000S/X: one input, four outputs, C and L band, about 20 GHz of spectral resolution and 4 GHz of addressability. three properties matter here.

loss does not grow with N. roughly 4.5 dB, on every connection, whether the device is feeding two users or twenty. this is the headline claim, and it is the one the flat green line in the chart above is making.

it reconfigures electronically. a new allocation is a new profile loaded over USB, not a new patch layout.

slice widths are free above the resolution floor. you can give one link 12 GHz and another 200 GHz in the same configuration.

that is the whole idea: replace a hard-wired passive tree with one active component whose cost is fixed and whose configuration is software.

the testbed

the source is a 10 mm type-II PPLN ridge waveguide pumped by about 24 mW of continuous wave light at 780 nm, tuned for degenerate down-conversion so the pair spectrum is centered in the C band. the biphoton is 2.5 nm wide, about 310 GHz. temporal walk-off between the two polarizations is undone with a 90 degree splice of polarization-maintaining fiber.

that 310 GHz gets carved into 24 slices of 24 GHz each, plus a stopband in the middle. 24 GHz is chosen because it is a multiple of the switch’s 4 GHz addressability while comfortably clearing its 20 GHz resolution. an energy-matched pair of slices is one channel, so there are 12 channels.

then the interesting bit. the four users do not get equivalent equipment:

UserDetectorEfficiencySingles rate as a 1:4 splitter
AliceSNSPD, free running~0.852.6 × 105 s−1
BobSNSPD, free running~0.853.3 × 105 s−1
CarolInGaAs APD, gated 20 MHz at 10% duty~0.25.5 × 103 s−1
DaveInGaAs APD, gated 20 MHz at 10% duty~0.13.3 × 103 s−1

two good detectors, two bad ones, and a factor of about 80 in singles rate between the best and worst user before you have allocated anything. this is not sloppiness, it is the experiment. a real network will have heterogeneous nodes, and the question is whether the provider can do anything about it from the middle.

before allocating, they check the entanglement is actually there. polarization correlations in two mutually unbiased bases, run through Bayesian mean estimation rather than a linear inversion, with no accidental subtraction. channels 1 through 11 come out above 95% fidelity to the target Bell state. channel 12, way out in the wing of the spectrum where there is barely any flux, is worse.

three ways to divide the same spectrum

now the actual result. six two-party links exist on a four-user network: AB, AC, AD, BC, BD, CD. the paper allocates the same 310 GHz three different ways.

allocate the biphoton spectrum yourselfpick a link, then click channels to give them to it. clicking a channel that already belongs to the selected link releases it.
the paper's three allocations
assigning to
the biphoton spectrum, 24 slices of 24 GHz, energy-matched about the center
each linkresulting two-party coincidence rate, relative, log scalersquo;s coincidence rate, relative to the best link on the network
links carrying entanglement
imbalance, best over worst
verdict

(a) fixed 48 GHz grid, allocated alphabetically. pair up adjacent slices, hand them out in order: AB gets the two brightest, CD gets the two faintest. AB is two good detectors on the brightest part of the spectrum, CD is two bad detectors on the dimmest. the measured ratio between them is about 4200.

this configuration is not stupid, though. it is a different policy. read the other way round, it is a premium tier: AB gets the best service the network can give. flexible allocation is as useful for deliberately favoring a link as it is for leveling them.

(b) same fixed grid, allocated to balance. keep the 48 GHz channels, but send the brightest ones to the weakest links. that alone takes the imbalance from 4200 to about 26.

that is the cheap win and it deserves emphasis. two orders of magnitude came from not allocating alphabetically. no new hardware, no finer grid, just a sensible ordering.

(c) full flex, 24 GHz slices, no grid at all. now every slice is allocated independently. five links land within a factor of two of each other.

there are two details in here that are easy to skim past. the first is that balancing required using the wings of the spectrum, not just the flat bit in the middle, which earlier work had stuck to. the second is that interleaving matters: links with comparable detection efficiency get channels alternated with each other, so they see the same mean flux rather than one getting a bright block and the other a dim one.

the part they don’t hide

link CD got dropped.

carol and dave have the two worst detectors, and their link pays both penalties at once. the paper works out that even in the most favorable allocation, giving CD the seven highest-flux channels, it still could not reach the rates of the other links. so they stopped trying and equalized across the five remaining links instead.

that is the honest boundary of the whole technique. a switch in the middle redistributes entanglement, it does not create any. if the total pair flux times the product of two users’ efficiencies is below what you need, no allocation saves you. flex grid gives you a budget to spend, and that is all.

the second caveat they flag is subtler. the fidelity numbers were measured channel by channel between Alice and Bob. the paper says outright that this does not guarantee the fidelity of arbitrary groupings of those channels, because crosstalk, multipair emission and frequency-dependent birefringence all show up when you combine slices. any allocation you actually intend to run has to be tested where it will run. that sentence is doing a lot of quiet work, and five years later it is still the reason nobody can just solve the allocation on paper and walk away.

how far this scales

the scaling argument at the end is the part that made this paper matter.

a commercial WSS available at the time had 20 output ports, 4.8 THz of bandwidth and 6.25 GHz of resolution. carve that into 12.5 GHz slices and you get enough channels for all N(N−1) connections of a fully connected 20-user network, through one device, at one fixed loss.

the nested DWDM equivalent would need 740 filters, and its worst channel would be roughly 96 dB down, which is not a link, it is a wall.

and the better argument is the one after that: you do not actually need all 380 channels standing by. the provider allocates the subgraph that is in demand right now and spends the leftover bandwidth boosting the links that are busy. a passive tree has to pre-build every connection it might ever need. the switch builds only the ones you asked for.

what happened after 2021

the paper ends with a list of its own limitations, which turns out to be an unusually accurate roadmap. it wanted a metric better than coincidence rate, it wanted clock synchronization between separated nodes, and it wanted a source with flat flux across the whole band. all three got done, mostly by the same people.

it went outside, the same year

Alshowkan et al., “Reconfigurable Quantum Local Area Network Over Deployed Fiber,” PRX Quantum 2, 040304 (2021) took the idea off the optical table and onto deployed fiber between three buildings on the Oak Ridge campus, GPS synchronized, with eight reconfigurable channels.

it also swapped the metric. instead of coincidence rate, links are rated by log-negativity, in entangled bits per second, which is a real information-theoretic quantity rather than a proxy for one. and they ran remote state preparation across it, the first time that protocol had been done on deployed fiber.

then it got a proper clock

Alshowkan et al., “Advanced architectures for high-performance quantum networking,” JOCN 14, 493 (2022) replaced GPS with White Rabbit switches between the three nodes, and added a QKD channel to secure the classical control traffic that runs the instruments. measured fidelities of 0.938 to 0.971 and entanglement rates of 19.6 to 145 ebits/s on the allocated channels.

if you read the coexistence post, that is the same White Rabbit, doing the same job, and the wavelength-choice argument in that post applies directly to this architecture.

the source got much wider

Alshowkan et al., “Broadband polarization-entangled source for C+L-band flex-grid quantum networks,” Opt. Lett. 47, 6480 (2022) covers 1530 to 1625 nm, 7.5 THz in one box, characterized as 150 pairs of 25 GHz channels with an average fidelity of 0.98 and more than 181 kebits/s of distillable entanglement.

put next to the 310 GHz and 12 channels of the original paper, that is a factor of 24 in bandwidth and 12 in channel count, and it is exactly the “uniform flux across the entire C band” the 2021 paper asked for.

allocation turned into a solver

this is where it stopped being a photonics problem.

2022. Optimal resource allocation for flexible-grid entanglement distribution networks put upper bounds on achievable fidelity and ebit rate, derived a condition on detector quality and link efficiency for whether a link is viable at all, and ran a genetic algorithm to find allocations, checked against the deployed network.

2024. Routing and Spectrum Allocation in Broadband Quantum Entanglement Distribution settled the complexity question: the routing half admits an optimal polynomial-time algorithm, and max-min fair spectrum allocation is NP-hard. so you are in approximation territory, and the paper offers two polynomial-time approximations that behave well. it also makes a point worth remembering, which is that maximizing the minimum rate can be a bad objective if you also care about the median.

2026. Goisman et al., “Efficient routing and spectrum allocation in arbitrary flex-grid entanglement networks” is the current state of it: a three-stage pipeline, Yen’s k-shortest-paths run twice to get low-loss candidate routes between users and sources, then APOPT to pick channel allocations that maximize rate under a fidelity constraint, then a CP-SAT solver to assign actual frequency bins without two sources colliding on the same one. tested on a ring and on a Manhattan incumbent local exchange carrier topology, and it beats the genetic algorithm on speed, accuracy and scale.

that last one is worth sitting with. the problem has fully converged onto routing and spectrum assignment, the same RSA problem elastic optical networks have been chewing on since about 2010, with a fidelity constraint bolted on and multiple sources instead of one transmitter. twenty years of classical work just became applicable.

the network grew a control plane

Alshowkan et al., “Resilient Entanglement Distribution in a Multihop Quantum Network,” JLT 43, 9016 (2025) runs six nodes across three buildings in a mesh, with quantum, data and control planes, and reroutes entanglement around a failed link. that is protection switching, on a quantum network, which is roughly the least glamorous and most necessary thing on this list.

the switch started shrinking

the WaveShaper in the original paper is a rack instrument. in 2024 the group demonstrated a foundry-fabricated photonic integrated circuit doing flex-grid entanglement distribution on a CMOS process. if that path works, the middle box goes from an instrument to a die.

other people went other ways

not everything descends from this paper.

a group at Nanjing put the source on a silicon chip, a nanowire generating polarization-entangled pairs by four-wave mixing across the whole 4.5 THz C band, and ran it over 30 km of deployed metro fiber between two campuses with 22 channel pairs available.

a group at USTC built a state-multiplexing source that pumps a microring with two lasers at once, so one wavelength correlates with three others. four users on six wavelength channels instead of twelve, which attacks the spectrum problem from the source end rather than the switch end.

and a group at Heriot-Watt skipped wavelength entirely, connecting eight users through the natural mode mixing inside 30 cm of multimode fiber used as a programmable 8x8 circuit, with entanglement swapping between distant pairs above 77% fidelity and two weeks of stability without recalibration. different degree of freedom, same provisioning idea.

what i’d build next

here is what i think is still missing. some of these are small and some are not.

1. put the Raman term in the objective function. every RSA solver above optimizes against loss and fidelity. but on a real deployed fiber the noise floor in a given quantum channel depends on which classical channels are lit on the same glass and how hard they are being driven, because spontaneous Raman scattering in silica dumps noise across tens of THz. that cost is wavelength-dependent, distance-dependent and traffic-dependent, and as far as i can tell nobody has written a spectrum assignment problem where the cost of a frequency bin is a function of the classical traffic matrix. the same group publishes on both, and has a whole review of hybrid classical-quantum networks to draw the noise model from. this is sitting right there.

2. close the loop. allocation today is open-loop: solve it, program the switch, then measure and hope. the missing input just arrived, though. in situ process tomography of a polarization-stabilized channel gives you a live quantum map per channel, including noise the classical polarization tracker cannot see. feed that back into the allocator and you have a controller with a time constant instead of an optimization you run at commissioning.

3. somebody publish the reconfiguration time. i cannot find it stated anywhere. the switch itself changes profile quickly, but after the spectrum moves, the polarization compensation at each user has to re-settle, and that part could be much slower. the total is the service-change latency of a flex-grid quantum network, and it decides whether “on demand” means seconds or means minutes. it is an afternoon’s measurement and it is the number an operator would ask for first.

4. flatten the source instead of scheduling around it. a good chunk of the allocation difficulty is the sinc-squared envelope. the outermost channel carries about four percent of the flux of the innermost one, so the solver spends its effort compensating for a shape the source imposed for no useful reason. chirped or apodized poling can flatten a joint spectrum considerably. every GHz of flatness is a constraint the allocator no longer has to satisfy, and unlike solver improvements it helps every allocation at once.

5. admission control, not silent dropping. link CD was dropped. on a real network that is an outage, and “the max-min solver decided” is not an incident report. classical networks have committed and peak rates, admission control, and a refusal with a reason. a quantum network layer should be able to tell Carol and Dave at request time that their link is infeasible with the detectors they own, and offer them a lower service class or a longer integration time rather than nothing. the hardware knows. the protocol does not ask.

6. reconcile the grid with memory bandwidth. the moment repeaters enter the picture, slices have to match the acceptance bandwidth of a quantum memory, which is typically hundreds of MHz to a few GHz. spectrally multiplexed repeater work is already asking for mode spacings in that range. a WSS bottoms out around 6.25 GHz. so either sources get cavity-enhanced down to memory linewidths, or a second, finer filtering stage appears after the switch, and either way the flexible grid gets a lot less flexible. this is where the current architecture and the repeater architecture collide, and nobody has reconciled them yet.

7. treat the slice width as a clock decision too. this one seems under-stated in the literature.

a narrower slice is a longer photon. that is just the transform limit. and from the coexistence post, the indistinguishability of two photons meeting at a beamsplitter for entanglement swapping depends only on the ratio of clock jitter to photon duration:

    I  =  1 / sqrt( 1 + δt² / 2σ² )

so the width you choose for bandwidth reasons also sets how good your clock has to be. the 24 GHz slices in this paper give roughly 18 ps photons, against which White Rabbit’s ~2 ps of jitter is nothing. the full 310 GHz biphoton, undivided, is a 1.4 ps photon, and the same White Rabbit link is nowhere near good enough for a swap.

one knob, three consequencesslice width sets how many users you can serve, how much flux each gets, and how good your clock has to be. transform-limited Gaussian approximation.
real values
indistinguishability vs slice width
what the same knob costs you
photon duration
indistinguishability
channels in 7.5 THz
verdict

which means the grid granularity, the user count, the per-link rate and the synchronization budget are all one decision, and right now they get made by different people in different papers. an allocator that knew the clock quality of each node could pick slice widths that keep every link swappable, instead of optimizing rate and finding out later that nothing on the network can interfere.

the short version

  • entanglement from a central source is addressed by wavelength, because the two photons of a pair always add up to the pump. handing two users energy-matched slices is what connects them.
  • the passive DWDM tree that did this before scales at 2N² − 3N filters, and its worst channel is 60 dB down at 16 users. the spread between channels hurts more than the average does.
  • one wavelength selective switch replaces the tree at a fixed 4.5 dB regardless of user count, and can be reprogrammed.
  • the crossover is around four or five users. below that, the passive tree wins, and the paper says so.
  • most of the win came from not allocating alphabetically. same fixed grid, sensible ordering: 4200x imbalance down to 26x. going to full flex bought the last factor of 13.
  • balancing required using the low-flux wings of the spectrum, which earlier work avoided.
  • link CD was dropped because two bad detectors cannot be rescued by any allocation. a switch redistributes entanglement, it does not make any.
  • per-channel fidelity does not predict the fidelity of a group of channels. allocations have to be tested in place.
  • one 20-port switch at 12.5 GHz slices covers a fully connected 20-user network. the DWDM equivalent is 740 filters.
  • since 2021: deployed over three buildings, White Rabbit clocked, sources widened to 7.5 THz, metric moved to ebits/s, allocation formalized as NP-hard RSA and solved with Yen plus APOPT plus CP-SAT on a Manhattan carrier topology, and the switch is being put on a chip.
  • what is missing: Raman noise in the objective, closed-loop reallocation, a published reconfiguration time, flatter sources, honest admission control, and a grid that a quantum memory can actually accept.

what strikes me about this line of work is how quickly the interesting problems stopped being physical. the 2021 paper is an optics experiment. the 2026 paper is a constraint solver run on a map of Manhattan. the entangled photons in the middle did not change much. what changed is that somebody decided to treat them as a resource with a scheduler, and once you do that, the questions become the ones network engineers have been arguing about for decades: fairness, admission, protection, and who gets the good wavelength.