As shown in FIG. 6, in some aspects, process 600 may include determining a service type to be used by the UE for one or more device-to-device (D2D) communications on a sidelink interface (block 610). For example, the UE (e.g., using controller/processor 280 and/or the like) may determine a service type to be used by the UE for one or more D2D communications on a sidelink interface, as described above in connection with FIGS. 4-5.
As further shown in FIG. 6, in some aspects, process 600 may include determining a slice identifier based at least in part on the service type, wherein the slice identifier corresponds to a resource allocation to be used for the one or more D2D communications (block 620). For example, the UE (e.g., using controller/processor 280 and/or the like) may determine a slice identifier based at least in part on the service type, as described above in connection with FIGS. 4-5. In some aspects, the slice identifier corresponds to a resource allocation to be used for the one or more D2D communications.
As further shown in FIG. 6, in some aspects, process 600 may include transmitting an indication of the slice identifier (block 630). For example, the UE (e.g., using controller/processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, and/or the like) may transmit an indication of the slice identifier, as described above in connection with FIGS. 4-5.
