In some aspects, the Tx UE 405 may transmit the indication of the slice identifier, and/or the related information described above (e.g., to an Rx UE 410), in a non-access stratum (NAS) message over a sidelink interface (e.g., a PC5 interface), in an RRC message to another UE (e.g., Rx UE 410), in a header of a D2D communication (e.g., a media access control (MAC) header, a radio link control (RLC) header, a packet data convergence protocol (PDCP) header, and/or the like), and/or the like. Additionally, or alternatively, the Tx UE 405 may transmit the indication of the slice identifier (e.g., to a base station 110) in an RRC message to the base station 110.

As shown in FIG. 4, in some aspects, the Tx UE 405 may indicate multiple slice identifiers in a slice occupancy announcement, such as if the Tx UE 405 is using multiple slices or expecting to use multiple slices within a threshold time period. In some aspects, if the Tx UE 405 is using only a single slice (e.g., associated with a single service type), then the Tx UE 405 may indicate a single slice identifier.

As shown by reference number 435, the Rx UE 410 may determine a service type to be used by the Rx UE 410 for one or more D2D communications on a sidelink interface, one or more QoS parameters associated with a D2D 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 a similar manner as described above in connection with the Tx UE 405. The Rx UE 410 may use this information to schedule D2D communications associated with D2D applications executing on the Rx UE 410 and/or to adjust resource usage for such D2D communications, as described below.