# Telecommunications — original Anime.js scenes Two editable, conceptual educational models; neither is an operational simulation. Geometry is original SVG with no external assets. [Overall gallery](../dist/animejs-gallery-0.6.0/index.html) · [Industry gallery](../dist/animejs-gallery-0.6.0/telecom/index.html) [Source module](../assets/animejs/industries/telecom.js) · [Catalog JSON](../assets/animejs/catalogs/telecom.json) · [Shared lifecycle and seeking](choreography.md) | ID | Question / individual preview | | --- | --- | | `telecom-congestion-reroute` | [Packet network: congestion and rerouting](../dist/animejs-gallery-0.6.0/examples/telecom-congestion-reroute.html) | | `telecom-cell-handover` | [Cell handover: preserving a session](../dist/animejs-gallery-0.6.0/examples/telecom-cell-handover.html) | ## Packet network: congestion and rerouting **Audience / use:** Explain topology resilience, queue pressure and alternate-path selection to a non-protocol-specific networking audience. **Narrative:** Forward → Queue → Detect → Reroute → Deliver → complete readable state. **Model assumptions:** Packets, queue slots and timings are illustrative. Alternate capacity and route availability are assumed; convergence, loss and retransmission are omitted. **Recipe-specific control:** `queuePackets` sets the visible illustrative queued packets, clamped to 1–4 (default 4). **Avoid:** Not a routing-protocol implementation, QoS SLA, traffic simulator or evidence that rerouting always preserves ordering. **Anime.js techniques:** one paused finite v4 timeline, explicit attribute from/to tweens, normalized SVG path drawing (`pathLength=1` and dash offset), progressive evidence opacity, and phase indicators. Physical movement uses coordinates or a dedicated group. No callbacks, listeners, random data or autoplay. **Editable configuration:** `duration` is the total illustrative timeline length in milliseconds, default `6000`; the renderer clamps it to at least `3000`. Every animation scales with this duration. Catalog beats are nominal defaults at 0, 1000, 2000, 3000, 4000 and 6000 ms; regenerate/retest seek targets after duration changes. Geometry and labels are intentionally authored in source, not exposed as unused config knobs. **Readable final state:** all static explanatory labels remain present. Faint abandoned paths, baseline outlines or closed-valve handles preserve the earlier context; they are not hidden text. A timeline owner must settle for reduced motion and revert on unmount as described in the shared lifecycle guide. ## Cell handover: preserving a session **Audience / use:** Use to explain the distinction between radio access and persistent session identity during mobility. **Narrative:** Serve A → Measure → Prepare B → Switch → Release A → complete readable state. **Model assumptions:** Coverage ellipses, travel distance and times are illustrative. Target admission and a shared session anchor are assumed; technology-specific procedures are intentionally omitted. **Recipe-specific control:** `travelPx` controls handset travel through the overlap, clamped to 220–320 SVG units (default 286); radio endpoints follow. **Avoid:** Not a 3GPP message flow, radio-planning calculation, coverage map or promise of zero interruption. **Anime.js techniques:** one paused finite v4 timeline, explicit attribute from/to tweens, normalized SVG path drawing (`pathLength=1` and dash offset), progressive evidence opacity, and phase indicators. Physical movement uses coordinates or a dedicated group. No callbacks, listeners, random data or autoplay. **Editable configuration:** `duration` is the total illustrative timeline length in milliseconds, default `6000`; the renderer clamps it to at least `3000`. Every animation scales with this duration. Catalog beats are nominal defaults at 0, 1000, 2000, 3000, 4000 and 6000 ms; regenerate/retest seek targets after duration changes. Geometry and labels are intentionally authored in source, not exposed as unused config knobs. **Readable final state:** all static explanatory labels remain present. Faint abandoned paths, baseline outlines or closed-valve handles preserve the earlier context; they are not hidden text. A timeline owner must settle for reduced motion and revert on unmount as described in the shared lifecycle guide.