---
title: "Return Info about a specific base slice descriptor"
method: GET
path: "/base_slice_des/{id}"
tags: ["Base Slice Descriptors"]
---

# Return Info about a specific base slice descriptor

`GET /base_slice_des/{id}`

## Path parameters

- `id` string, uuid, required

## Response `200`

Successful Operation

- BaseSliceDes — This is the schema for the core part of the new slice
  - `base_slice_des_id` string, uuid — Id of the slice descriptor which will be used as base for the gst
  - `base_slice_des_ref` string, uuid — Reference to an added slice descriptor which will be used as base for the gst
  - `coverage` string[] — A list with all the locations that are part of the slice
  - `delay_tolerance` boolean — Supported or not supported
  - `deterministic_communication` object — This attribute defines if the network slice supports deterministic communication for periodic user traffic. Periodic traffic refers to the type of traffic with periodic transmissions.
    - `availability` boolean — This parameter describes if the network slice supports deterministic communication.
    - `periodicity` number[] — This parameter provides a list of periodicities supported by the network slice.
  - `network_DL_throughput` object — The achievable data rate in downlink for the whole network slice (and not per user).
    - `guaranteed` number, float — kbps
    - `maximum` number, float — kbps
  - `ue_DL_throughput` object — This attribute describes the guaranteed data rate supported by the network slice per UE in downlink
    - `guaranteed` number, float — kbps
    - `maximum` number, float — kbps
  - `network_UL_throughput` object — The achievable data rate in uplink for the whole network slice (and not per user).
    - `guaranteed` number, float — kbps
    - `maximum` number, float — kbps
  - `ue_UL_throughput` object — This attribute describes the guaranteed data rate supported by the network slice per UE in uplink
    - `guaranteed` number, float — kbps
    - `maximum` number, float — kbps
  - `group_communication_support` integer — 0: not available 1: Single Cell Point to Multipoint (SCPTM) 2: Broadcast/Multicast 3: Broadcast/Multicast + SC-PTM
  - `isolation` 0 | 1 | 2 | 3 — A network slice instance may be fully or partly, isolated from another network slice instance. 0: No Isolation 1: Core Isolation 2: RAN Isolation 3: Both Isolation
  - `mtu` integer — Bytes
  - `mission_critical_support` object — Mission-critical (MC) leads to a priority of the network slice relative to others, for C-plane and U-plane decisions.
    - `availability` boolean
    - `mc_service` integer[] — This attribute specifies whether or not the network slice supports MC push-to-talk, MC data, MC video, Isolated E-UTRAN Operation for Public Safety or MC interworking.
  - `mmtel_support` boolean — This attribute describes whether the network slice supports IP Multimedia Subsystem (IMS) and Multimedia Telephony Service MMTel.
  - `nb_iot` boolean — This parameter describes whether NB-IoT is supported in the network slice.
  - `number_of_connections` integer — This attribute describes the maximum number of concurrent sessions supported by the network slice.
  - `number_of_terminals` integer — This attribute describes the maximum number of concurrent terminals supported by the network slice.
  - `positional_support` object — This attribute describes if the network slice provides geo-localization methods or supporting methods.
    - `availability` integer[] — Describes if this attribute is provided by the network slice and contains a list of positioning methods provided by the slice.
    - `frequency` integer — Seconds
    - `accuracy` integer — Meters
  - `radio_spectrum` string[] — Defines the radio spectrum supported by the network slice.
  - `simultaneous_nsi` integer — 0: Can be used with any network slice 1: Can be used with network slices with same SST value 2: Can be used with any network slice with same SD value 3: Cannot be used with another network slice 4-15: operator defined class
  - `qos` object[] — This attribute defines all the QoS relevant parameters supported by the network slice, based on 3GPP defined standard values (5QIs)
    - `qi` integer — Based on the table of defined 5QI by 3GPP
    - `resource_type` integer — 0: GBR (Mission Critical Video user plane) 1: Delay critical GBR (Intelligent Transport Systems) 2: Non-GBR (Voice, AR)
    - `priority_level` integer — Associated with 5G QoS characteristics indicates a priority in scheduling resources among QoS Flows.
    - `packet_delay_budget` integer — The Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be delayed between the UE and the UPF [Seconds].
    - `packet_error_rate` integer — The Packet Error Rate (PER) defines an upper bound for the rate of packets that are not successfully delivered by the corresponding receiver [percentage].
    - `jitter` integer — Jitter is defined as a variation in the delay of received packets [Seconds].
    - `max_packet_loss_rate` integer — the maximum rate for lost packets of the QoS flow that can be tolerated in the uplink (UL) and downlink (DL) direction [percentage].
  - `nonIP_traffic` boolean
  - `device_velocity` integer — 1: Stationary: 0 km/h 2: Pedestrian: 0 km/h to 10 km/h 3: Vehicular: 10 km/h to 120 km/h 4: High speed vehicular: 120 km/h to 500 km/h
  - `terminal_density` integer — maximum number of connected and/or accessible devices per unit area (per km2) supported by the network slice [Number/km^2]

## Other responses

- `400` — Bad Request
- `404` — Not Found
- `500` — Server Error

---

[API](https://skmtc.net/core-ncsrd/apis/katana.md) · [All operations](https://skmtc.net/core-ncsrd/apis/katana/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/core-ncsrd/katana/versions/7ddfc4202f39/schema)