As shown by reference number 415, the Tx UE 405 may determine a service type to be used by the Tx UE 405 for one or more D2D communications on a sidelink interface, such as a PC5 interface and/or the like. For example, as shown, the Tx UE 405 may determine the service type based at least in part on information received from a D2D application executing on the Tx UE 405. In some aspects, a D2D application may provide information identifying a service type of the application, one or more quality of service (QoS) parameters associated with the application and/or the service type, one or more transmission characteristics associated with the application and/or the service type, and/or the like. In some aspects, if the Tx UE 405 is executing multiple D2D applications (e.g., V2X applications and/or the like), the Tx UE 405 may receive and/or determine such information for each of the D2D applications.

A service type may indicate a type of D2D service (e.g., a V2X service and/or the like) associated with the D2D application, such as a location-based service, an intersection assist service, a platooning service (e.g., where one or more trailing vehicles or trailing UEs follow a lead vehicle or lead UE), a cooperative adaptive cruise control (CACC) service, a sensor sharing service (e.g., where sensor information measured by one UE is shared with one or more other UEs), and/or the like.

A quality of service parameter may include, for example, a packet loss rate requirement, a packet error rate requirement, a bit rate requirement, a throughput requirement, a latency requirement, a reliability requirement, an availability requirement, a jitter requirement, and/or the like. In some aspects, a set of quality of service parameters may be indicated by a QoS class identifier (QCI), 5G QoS identifier (5QI) value, and/or the like.