DISH Proprietary & Confidential - Not to be shared without NDA

Requirement Id
General Requirements
ORC-GR-1
ORC-GR-0
ORC-GR-1
ORC-GR-0
ORC-GR-1
ORC-GR-0
ORC-GR-1
ORC-GR-0
ORC-GR-1

ORC-GR-0

ORC-GR-1

ORC-GR-0
ORC-GR-1
ORC-GR-0
ORC-GR-1
ORC-GR-0
Northbound interfaces
ORC-NB-1
ORC-NB-0
ORC-NB-1
ORC-NB-0
ORC-NB-1

ORC-NB-0

ORC-NB-1

ORC-NB-0

ORC-NB-1
ORC-NB-0
ORC-NB-1

ORC-NB-0
SouthBound Interfaces
ORC-SB-1
 ORC-SB-0

ORC-SB-1

ORC-SB-0
ORC-SB-1
Functional Requirements
ORC-FN-1

ORC-FN-0

ORC-FN-1
ORC-FN-0
ORC-FN-1
ORC-FN-0
ORC-FN-1

ORC-FN-0

ORC-FN-1

ORC-FN-0
ORC-FN-1
ORC-FN-0
ORC-FN-1
ORC-FN-0
ORC-FN-1
ORC-FN-0

ORC-FN-1

ORC-FN-0

ORC-FN-1

ORC-FN-0

ORC-FN-1

ORC-FN-0

ORC-FN-1

ORC-FN-0
 ORC-FN-1

ORC-FN-0

ORC-FN-1

ORC-FN-0

ORC-FN-1

ORC-FN-0
ORC-FN-1
ORC-FN-0
ORC-FN-1
ORC-FN-0
ORC-FN-1
Storage Requirements
ORC-ST-1
ORC-ST-0
ORC-ST-1
Life Cycle Management
ORC-LC-1
ORC-LC-0
ORC-LC-1
ORC-LC-0
etary & Confidential - Not to be shared without NDA
Requirement
ements
The orchestrator shall meet the requirements of the NFVO as specified by ETSI GS NFV-IFA 010 V3.1.1 or later!
Solution shall support/realize zero-touch provisioning.
Solution shall automatically execute work flow and triggers for operations and network configuration.
Solution shall enable automated self-healing.
Solution shall enable auto-scaling.
The orchestrator shall be fully automated and programable through service templates and other metadata.
The rrchesrator shall managed resources to achieve SLA for specific network services (NS) and tenants.
The orchestrator shall be able to report on level of service and KPIS per network service and per tenant.
All interfaces to the orchestrator shall be based on widely used open APIs and open standards such as those of 3GPP and
IETF.
The orchestrator shall manage the lifecycle of Network Services (NSs) and Virtual Network Functions (VNFs) across multiple
NFVI-PoPs from multiple 3rd parties.
Implementation of new service definitions and versions shall be possible without downtime and without disruption to running
processes.
The orchestrator shall perform all functions required of NFVO for management of 3GPP 5G and IMS networks per 3GPP
28.500.
The orchestrator shall perform all functions required for management of virtualized RAN per O-RAN specification.
The orchestrator shall provide 5 9s availability.
The orchestrator shall be built with a cloud native, micro-service based architecture.
The orchestrator shall support VNF and IM that are cloud native and container over bare metal based.
erfaces
All orchestrator UIs shall provide single pane of glass (SPOG) interface for e2e network.
The orchestrator shall allow the service definition template to specify that the components are to be created, reused and/or
configured to provide the service.
The orchestrator must provide a graphical tool for designing service definition templates.
The orchestrator shall have a dashboard that provides a summary and health status of registered service templates.
The orchestrator shall allow Services and VNFs to be created, initiated, monitored and updated through a web-based user
interface.
The orchestrator shall allow Services and VNFs to be be created, initiated, monitored and updated through a REST-based
API.
The orchestrator must provide means to search for current and historical orders based on external order reference, progress
stage, initiating user or system, service definition, and other relevant attributes.
The orchestrator must provide means to search for current and historical orders based on external order reference, progress
stage, initiating user or system, service definition, and other relevant attributes.
The service inventory must provide a notification API suitable for ongoing streaming of status changes (service, VNF and
resouces) to systems who subscribe.
The repository shall provide reporting capability to summarize identified data integrity discrepancies.
The orchestrator shall provide all interfaces for interworking with and reporting to 3GPP network management system as
described in 3GPP 28.500
Please provide details on capacity of the proposed orchestrator solution. Is there a limitation in number of transactions per
seconds? In number of cell sites? In number of end users?
erfaces
The orchestrator must be able to request WAN transport services as required by the service definition.
 The request for WAN transport services must be able to specify transport characteristics including bandwidth, latency,
availability, diversity.
The orchestrator must be able to query the WAN transport service provider regarding network capabilities and design the
overall service accordingly (e.g. place VNFs so that they are reachable within the required service latency).
The orchestrator shall collect all information necessary for interworking with and reporting to 3GPP network management
system as described in 3GPP 28.500.
The orchestrator shall be able to associate HW resources with specific geographical locations.
uirements
The orchestrator shall support a DevOps approach to service and VNF definition.
The orchestrator shall be capable of on-boarding network services and VNFs, i.e. register a Network Service/VNF in the
catalogue and ensure that all the templates describing the NS/VNF are on-boarded and validated in terms of integrity and
authenticity.
The orchestrator must maintain a catalog of service definitions.
The orchestrator must publish, in catalog form, the available service definitions and their required input parameters.
The orchestrator shall allow service definitions to include input parameters that are populated when the service is instantiated,
to allow a single service definition to support varying customer requirements and product offers.
The orchestrator must allow the service definition to specify validity rules for input parameters.
The orchestrator must be able to fulfil requests for enterprise services including network connectivity, network functions and
applications.
The orchestrator must be able to fulfil engineering requests for network capability (such as 5G service to a particular area).

The orchestrator must be able to fulfil requests for network slices (NSI) as defined by 3GPP TS28.530 including requesting the
required network slice subnets (NSSI).
The orchestrator shall be able to manage end-to-end service lifecycle management in centralized and distributed data center
scenarios, such as a network slice with distributed and centralised components.
The orchestrator must be able to fulfil requests to terminate a service.
The execution process should operate asynchronously.
The execution process should restart automatically in case of downtime.
The execution process includes a testing and validation step to ensure that all operations completed succesfully and that
Network Service is working properly.
Custom process steps, including manual steps, should be able to be included in the execution process.
If any step fails, southbound domains and the orchestrator inventory should be rolled back to the state prior to the request
starting to be executed.
Orchestrator must generate any required configuration to enable virtual network functions to start operating. (Day 0
configuration.)
Orchestrator must generate any required configuration for physical and virtual components to provide a service. (Day 1
configuration.)
The orchestrator must support policy-driven closed-loop operations using this capability, such as service healing, capacity
management, diagnosis and rectification.
Orchestrator must manage an inventory of service instances including the components that make up each service instance.

Each service instances must include a reference to the service definition, version and input parameters of the service request
that created it.
Instantiation, changes and deletion of services must be auditable to the originating request, user and external order reference.

The orchestrator must determine appropriate placement of VNFs and Network Services across multiple NFV infrastructure
domains to meet service performance criteria.
The orchestrator shall be able to partition the NFVI resources into “resource zones” to isolate and protect NFV applications
from each other.
 The orchestrator shall monitor KPIs of network services, VNFs and NFVI and shall be able to report this information to external
functions (for example, OSS/BSS).
The orchestrator shall collect/analyze resource usage, events and alarms from VNFs and NFVI and shall be able to report this
information to external functions (for example, OSS/BSS).
The orchestrator shall be able to detect Hardware/Software failures and determine the impacted applications/NSs/VNFs.

The orchestrator shall be able to automatically restore a NS/VNF in the case where a hardware or a software failure is
detected.
The orchestrator shall collect the information and provide a topology view of network service (NS) instances, VNF instances,
and NFVI resources across all NFVI-PoPs, including network connectivity endpoints and geographical locations.

The orchestrator shall provide an operational view of the status of NS instances, VNF instances, and NFVI resources.
The orchestrator shall validate that a received message is from an authenticated and authorized consumer (VIM, NFVM, or
OSS).
The orchestrator shall verify the integrity of any received message.
The orchestrator shall support the capability to add/remove/update VNF(s)/VL(s)/VNFFG(s)/PNF(s)/Nested NS(s)/Service
Access Point(s) (SAPs) to an existing NS in order to perform NS update.
The orchestrator shall support the capability to add existing VNF instance(s) to an existing NS.
The catalogs and repositories must allow for version control of their content (e.g. through github interface).
ements
The Vendor shall ensure that the Repository will enable the establishment of processes to detail real-time topology and shall
be capable of interrogating all inventory for a period of 30 days.
It shall be possible to remotely backup and restore the Repository along with all configuration data.
The repository shall deliver encryption of all data.
gement
The orchestrator can be updated with no downtime.
New Interfaces can be added easily through the use of plugins.
The orchestrator shall support automated discovery of new resources, infrastructure and Infrastructure manager instances.

An automated process shall be available for deployment of orchestrator.

Vendor Response Vendor Comment