opologies dynamically and flexibly for different slices based on the requested slice types of the connected UEs; (ii) dynamic and flexible air interface adaptation and scheduling should be supported by the NG-RAN based on the service-oriented network topolo- gies, for example, the NG-RAN should provide different multi-layer air connections or communication modes to different UEs supporting multiple slices based on the service-oriented network topologies to maximize the network performance. Mission-driven resource utilization, sharing, and aggregation, e.g. by specifying the following: 12 Service-Oriented RAN Support of Network Slicing - Mechanisms to support multi-layer connection hierarchy to UE with service sub- scriptions to multiple providers: it aims to achieve the goal that the RAN may provide slice-specific multi-layer connection to one UE supporting multiple network slices simultaneously, for example, the multi-layer connection may include side-link V2X communication, UE-to-UE communication, and broadcast/multicast mode communication supported by different slices, respectively. Mechanisms to allow UE to have multiple data paths for various services based on SLA requirements: it aims to achieve the goal that the NG-RAN can enable UE to have var- ious data paths for various services toward RAN subsystems related to different slices, for example, semi-static radio resources and data paths for services with different SLA requirements can be allocated to the UE. The support of dual connectivity across RAN parts of different network slices: it aims to achieve the goal that Master Node (MN) and Secondary Node (SN) PHY can be flexibly configured and released for the UE supporting multiple branded subsystems related to multiple slices, for example, dual connection can be configured to the UE if both the subsystem supported by MN and the subsystem supported by SN are supported by the UE, and the UE falls back to single connection when only one of the subsystems supported by MN and SN is supported by the UE. 12.4.1 