lice types. Tenants who may provide services of the same service type can still use differen- tiated NSIs via customization of the network slice template with the same network slice types. Template design is separated from the NSI operation: in the design phase, the network slice template is generated based on the network capability of each technical domain and a tenant's particular requirements. In the operation phase, an NSI is instantiated based on the network slice template, which includes the deployment and configuration of related network functions and related resources in different technical domains. The network slice design is separated from the operation to enable repeated use of a network slice template. NSIs require multidimensional management: an NSI usually includes multiple technical domains such as RAN domain, CN domain, and TN domain. An NSI may also include multiple administrative domains that belong to different operators. To guarantee NSI's 12 Service-Oriented RAN Support of Network Slicing fast deployment, it is essential to use efficient multidimensional management via coordination and cooperation across such different domains. NSIs ensure SLA compliance: tenants will sign SLA with operators, which may include requirement agreements related to security/confidentiality, visibility/manageability, spe- cific service characteristics (service type, air interface standard, and customized func- tions), and the corresponding performance indicators (latency, throughput, packet loss rate, call drop rate, and reliability/availability). Terminals may be involved in the selection of NSIs: terminals can access one or multi- ple NSIs. Terminals could assist NSI selection based on, for instance, network slice type, while the network performs the final selection decision. Simple terminals, such as sen- sors, are usually in a static and one-to-one relationship with NSIs, because the costs and power consumption requirements limit the terminal capability. Therefore, the network solely performs NSI selection. 12.