---
title: "Returns information about the given slice"
method: GET
path: "/slice/{slice_id}"
tags: ["Slice"]
---

# Returns information about the given slice

`GET /slice/{slice_id}`

## Path parameters

- `slice_id` string, uuid, required

## Response `200`

Successful Operation

- Nsi
  - `_id` string, uuid — The uuid that is used for storing the NSI in the database
  - `created_at` number
  - `deployment_time` Time — The Slice Deployment time
    - `NS_Deployment_Time` object
      - `NSi_name` number — Seconds
    - `Placement_Time` number — Seconds
    - `Provisioning_Time` number — Seconds
    - `Radio_Configuration_Time` number — Seconds
    - `Slice_Deployment_Time` number — Seconds
    - `WAN_Deployment_Time` number — Seconds
  - `coverage` string[] — A list with all the locations that are part of the slice
  - `network_DL_throughput` object — The achievable data rate in downlink for the whole network slice (and not per user).
    - `guaranteed` number — kbps
    - `maximum` number — kbps
  - `ue_DL_throughput` object — This attribute describes the guaranteed data rate supported by the network slice per UE in downlink
    - `guaranteed` number — kbps
    - `maximum` number — kbps
  - `network_UL_throughput` object — The achievable data rate in uplink for the whole network slice (and not per user).
    - `guaranteed` number — kbps
    - `maximum` number — kbps
  - `ue_UL_throughput` object — This attribute describes the guaranteed data rate supported by the network slice per UE in uplink
    - `guaranteed` number — kbps
    - `maximum` number — kbps
  - `group_communication_support` 0 | 1 | 2 | 3 — 0: not available 1: Single Cell Point to Multipoint (SCPTM) 2: Broadcast/Multicast 3: Broadcast/Multicast + SC-PTM
  - `mtu` number — 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` number[] — 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` number — This attribute describes the maximum number of concurrent sessions supported by the network slice.
  - `number_of_terminals` number — 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` number[] — Describes if this attribute is provided by the network slice and contains a list of positioning methods provided by the slice.
    - `frequency` number — Seconds
    - `accuracy` number — Meters
  - `radio_spectrum` string[] — Defines the radio spectrum supported by the network slice.
  - `qos` object[] — This attribute defines all the QoS relevant parameters supported by the network slice, based on 3GPP defined standard values (5QIs)
    - `qi` number — Based on the table of defined 5QI by 3GPP
    - `resource_type` 0 | 1 | 2 — 0: GBR (Mission Critical Video user plane) 1: Delay critical GBR (Intelligent Transport Systems) 2: Non-GBR (Voice, AR)
    - `priority_level` number — Associated with 5G QoS characteristics indicates a priority in scheduling resources among QoS Flows.
    - `packet_delay_budget` number — 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` number — 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` number — Jitter is defined as a variation in the delay of received packets [Seconds].
    - `max_packet_loss_rate` number — 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` 1 | 2 | 3 | 4 — 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` number — maximum number of connected and/or accessible devices per unit area (per km2) supported by the network slice [Number/km^2]
  - `probe_list` string[] — A list of probe ids to be included in the slice
  - `status` string — Init, Peovisioning, Activation, Running or Terminating
  - `connections` object[] — A list of 5G service connections. Each connection contains a core and a radio endpoint. The endpoints are selected from the platform fanctions repository of the Slice Manager
    - `core` object — The Core part of the 5G service connection
      - `_id` string, uuid — The uuid of the function that is used in the database
      - `id` string — A unique ID of the function
      - `name` string — The name of the function
      - `gen` 4 | 5 — Type of the network function - 4: 4G, 5: 5G
      - `func` 0 | 1 — 0: Core, 1: Radio
      - `shared` object — Defines if the function can be shared between different slices
        - `availability` boolean, required — true: shared, false: no shared
        - `max_shared` number — Max number of slices - If availability is true and max_shared not defined, it will be assumed unlimited availability
      - `type` 0 | 1 — 0: Virtual, 1: Physical
      - `location` string — Supported location
      - `ns_list` object[] — Conditional - If type == Virtual - A list of the NSs that will be part of the slice
        - `nsd-id` string — The NSD id as defined on the NFVO
        - `ns-name` string — The name of the NS
        - `placement` 0 | 1 — 1: Core, 2: Edge
        - `optional` boolean
      - `pnf_list` object[] — Conditional - If type == Physical - A list of the PNFs that will be part of the slice
        - `pnf-id` string — A Unique ID of the pnf
        - `pnf-name` string — The name of the PNF
        - `description` string
        - `ip` string — The management IP of the PNF
        - `ip_s1` string — Optional - The IP of the S1 Interface
        - `location` string — The location of the PNF
        - `optional` boolean
      - `ems-id` string — Optional - Defines the EMS that is responsible for D1&2 configuration
  - `functions` string[] — A list of all the functions that are used in the slice
  - `conf_comp` object — The items components that have been configured by the ems
  - `ns_list` object[] — A list of the instantiated NSs
    - `nsd-id` string — The NSD id as defined on the NFVO
    - `ns-name` string — The name of the NS
    - `placement` 0 | 1 — 1: Core, 2: Edge
    - `optional` boolean
    - `nsd-info` object — Information about the NS Descriptor
      - `_id` string
      - `id` string
      - `vnfd_list` string[] — The list of VNFDs in the NSD
      - `flavor` object — The NS requirements
        - `memory-mb` integer
        - `vcpu-count` integer
        - `storage-gb` integer
      - `nfvo-id` string, uuid
    - `placement_loc` object — Detailed info regarding the placement of the NS
      - `location` string — The location where the NS is running
      - `vim` string — The VIM ID of the location where the NS is hosted
    - `vims` string[] — The list of VIMs used for the NS
  - `wim_data` object — The data that was sent to WIM
    - `slice_sla` object — Slice parameteres as defiend in NEST
      - `network_DL_throughput` object — The achievable data rate in downlink for the whole network slice (and not per user).
        - `guaranteed` number — kbps
        - `maximum` number — kbps
      - `network_UL_throughput` object — The achievable data rate in uplink for the whole network slice (and not per user).
        - `guaranteed` number — kbps
        - `maximum` number — kbps
      - `mtu` number — Bytes
    - `core_connections` object[] — List of connections that are part of the slice and must be implemented by the WIM
      - `core` object — The core part of the radio connection
        - `ns` object[] — A list of VIMs where the NSs have been instantiated
          - `location` string — The location of the VIM
          - `vim` string — The ID of the VIM
        - `pnf` object[] — A list of the PNFs that are part of the slice
          - `pnf-id` string — A Unique ID of the pnf
          - `pnf-name` string — The name of the PNF
          - `description` string
          - `ip` string — The management IP of the PNF
          - `ip_s1` string — Optional - The IP of the S1 Interface
          - `location` string — The location of the PNF
          - `optional` boolean
      - `radio` object — The core part of the radio connection
        - `ns` object[] — A list of VIMs where the NSs have been instantiated
          - `location` string — The location of the VIM
          - `vim` string — The ID of the VIM
        - `pnf` object[] — A list of the PNFs that are part of the slice
          - `pnf-id` string — A Unique ID of the pnf
          - `pnf-name` string — The name of the PNF
          - `description` string
          - `ip` string — The management IP of the PNF
          - `ip_s1` string — Optional - The IP of the S1 Interface
          - `location` string — The location of the PNF
          - `optional` boolean
    - `extra_ns` object[] — A list of VIMs where the NSs that are not part of the core slice have been instantiated
      - `location` string — The location of the VIM
      - `vim` string — The ID of the VIM

## 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)
