---
id: fb-10014-connection-priority
title: FB-10014 Connection Priority
doc_type: handoff
status: in-dev
last_updated: 2026-06-15
sources:
  - { type: jira, ref: "FB-10014", url: "https://tvunetworks.atlassian.net/browse/FB-10014" }
  - { type: slack, ref: "Connection Priority logic thread 2026-06-15" }
figma:
  file: rJJjWWs51n2iFOlCIC7aYG
  nodes:
    - { id: "7070:2", label: "Connection Priority page (PRD / BEFORE / modal)", url: "https://www.figma.com/design/rJJjWWs51n2iFOlCIC7aYG/Config-T---Local-UI---v7.7---8.0--20240220?node-id=7070-2" }
---

# Handoff — FB-10014 Connection Priority

## Current State

Figma page: `< FB-10014 > Connection Priority 20260612`

Page node: `7070:2`

Existing sections:

| Node | Section | Notes |
|---|---|---|
| `7070:3` | `FB-10014 · PRD` | PRD card exists and captures source/background/requirements/acceptance/open item |
| `7099:314` | `FB-10014 · BEFORE — Config-T Network (V3 baseline)` | Contains baseline Network frame, but also currently contains the modified Network draft and modal |

Existing drafted components:

| Node | Name | Notes |
|---|---|---|
| `7111:343` | `btn · Connection Priority` | Button added in Network header |
| `7102:314` | `Connection Priority (modal)` | Modal drafted with Internal Cellular, Ethernet, WiFi, USB 1-4 rows |

Local spec added:

- `docs/specs/2026-06-15-fb-10014-connection-priority-design-record.md`

Latest Slack logic incorporated from 2026-06-15:

- Add a general TPC feature control: `Connection Priority`.
- If authorized, local GUI allows users to set priorities by themselves.
- If not authorized, support still configures data weight in TPC, same as today.
- This is downward compatible.
- Davion confirmed that when this feature is added, the device should use the RPS Link priority logic.
- TPC nickname may be clearer/longer, e.g. `Self-serviced Connection Priority`; actual feature name is usually kept shorter.

## Requirement Summary

Add Connection Priority configuration in Config-T Home -> Network for V3 / TM930.

Main behavior:

- Local GUI is gated by TPC `Connection Priority` authorization.
- Initial values come from the current local/RPS Link-style priority state when authorized.
- User can set each visible connection type to `1`, `2`, or `3`.
- `1` means highest priority.
- Same value means equal load balancing.
- Changes apply dynamically, no reboot.
- Config persists after reboot.
- If not authorized, the legacy TPC data weight path remains available for support.

## Figma Work Remaining

1. Create independent section:

```text
FB-10014 · AFTER — Config-T Network (V3 / TM930)
```

2. Keep baseline-only content in:

```text
FB-10014 · BEFORE — Config-T Network (V3 baseline)
```

3. Move or clone the modified Network page with the `Connection Priority` button into AFTER.

4. Move or clone modal `7102:314` into AFTER, positioned near the modified Network page.

5. Add UX/dev handoff card in AFTER with:

- Entry: Network module header button
- Modal row order: Internal Cellular, Ethernet, WiFi, USB 1, USB 2, USB 3, USB 4
- Priority options: `1`, `2`, `3`
- Semantics: `1 = highest`; equal values share traffic
- Feature gate: authorized = local GUI self-service; unauthorized = support configures TPC data weight
- Logic: authorized path uses RPS Link-style priority logic
- Apply: immediate, no reboot
- Persistence: retained after reboot

6. Add visible review labels:

- BEFORE
- AFTER
- Modal / interaction
- Feature gate note: TPC `Connection Priority`
- Compatibility note: unauthorized devices keep current TPC Data priority / data weight behavior

## Suggested AFTER Layout

Place content in one AFTER section:

```text
[Modified Network page]   [Connection Priority modal]
[UX/dev handoff card]     [Open item card]
```

Keep the AFTER section separate from PRD and BEFORE. This follows the project rule recorded in `docs/FIGMA_LINKS.md`: PRD, BEFORE, and AFTER should be separate sections for review and navigation.

## Open Questions To Confirm

| Question | Why it matters |
|---|---|
| Exact feature control name and nickname | Slack direction is `Connection Priority`; nickname may be `Self-serviced Connection Priority` |
| Is Internal Cellular one grouped row or three modem rows? | PRD says 3 modems participate, Figma modal uses one grouped row |
| What is the exact readable-slot API shape? | Determines whether absent USB rows are omitted or disabled |
| What feedback pattern should apply failure use? | Should match existing Config-T error feedback |

## Next Recommended Step

Finish Figma structure first: create AFTER section, move the modified Network frame and modal there, then add the UX/dev handoff card from the local design record with the new TPC feature-gate logic.