Additionally, or alternatively, the Tx UE 405 may determine the slice identifier based at least in part on a set of quality of service parameters associated with the service type and/or the D2D application. For example, the Tx UE 405 may store a data structure that maps different sets of QoS parameters (e.g., represented by QCI values, shown as 5QI for a 5G network) to corresponding slice identifiers. In some aspects, and as shown, the Tx UE 405 may determine the slice identifier based at least in part on a service type and a set of QoS parameters. For example, a first service type identifier of “PSID 1” and a first set of QoS parameters represented as “5QI 1” may correspond to a first slice identifier of “Slice ID 1,” a second service type identifier of “PSID 2” and a second set of QoS parameters represented as “5QI 2” may correspond to a second slice identifier of “Slice ID 2,” and/or the like. In example 400, the Tx UE 405 may determine that a first D2D and/or V2X application (e.g., D2D/V2X App 1) is associated with a first slice identifier of “Slice ID 1,” and may determine that a second D2D and/or V2X application (e.g., D2D/V2X App 2) is associated with a second slice identifier of “Slice ID 2.”