---
id: "supi"
kind: "datatype"
status: "draft"
is_pii: true
categories: ["telecom", "pii"]
langs: ["common"]
quality: 80
url: "http://registry.apicrafter.io/datatype/supi"
---

# Subscription Permanent Identifier (SUPI) of a 5G network (`supi`)

> **Draft.** Draft records have not been reviewed yet and may be incomplete or wrong; do not treat them as authoritative for legal or compliance decisions.

Permanent identifier of a subscriber in a 5G core network (3GPP TS 23.003). The service APIs of the 5G core (3GPP TS 29.571) write it as a string with a type prefix, imsi- followed by an IMSI or nai- followed by a network access identifier; gci- and gli- mark identifiers of wireline access. In radio signalling the SUPI is sent only in concealed form (SUCI).

- Personal data (PII): yes
- Categories: Telecommunications (telecom), Personally identifiable information (pii)
- Countries: global
- Languages: Common to most languages (common)
- Classification: identifier

## Detection

Regular expression (Python `re`):

```
^(?:imsi-\d{5,15}|nai-\S+|gci-\S+|gli-\S+)$
```

## Examples

- `imsi-310150123456789` — SUPI of type IMSI
- `imsi-460001357924680` — SUPI of type IMSI
- `310150123456789` (invalid example) — A bare IMSI without the type prefix

## Translations

- ru: Постоянный идентификатор подписки (SUPI) в сети 5G: Постоянный идентификатор абонента в ядре сети 5G (3GPP TS 23.003). В сервисных API ядра 5G (3GPP TS 29.571) записывается строкой с префиксом типа — imsi- и IMSI или nai- и сетевой идентификатор доступа. По радиоканалу передаётся только в скрытом виде (SUCI).

## Sources

- doc: <https://www.3gpp.org/DynaReport/23003.htm>
- doc: <https://www.3gpp.org/DynaReport/29571.htm>

## Quality

Score 80/100. Missing: mapping (Wikidata, Schema.org, ...), detector coverage.

JSON: <http://registry.apicrafter.io/api/v1/datatypes/supi.json> · Edit: <https://github.com/apicrafter/metacrafter-registry/edit/main/data/datatypes/any/telecom/supi.yaml>