In some aspects, the first technique described above can generally be used to indicate, within a single DCI message, a codepoint associated with an individual CG and/or SPS configuration in order to jointly activate and/or release all CG and/or SPS configurations that are grouped with the individual CG and/or SPS configuration within an individual configuration set based on having a common service type. Thus, in the first technique, one configuration set (which may have one or multiple members) can be activated and/or released within a single DCI message. Accordingly, in some aspects, efficiency may be increased by using a single DCI message to jointly activate and/or release multiple configuration sets, each of which may include one or multiple members. For example, as mentioned above, configurations that have a particular service type may be grouped together within the configuration sets. Additionally, or alternatively, configurations with a common service type may be distributed among different configuration sets, with members of the respective configuration sets sharing one or more parameters (e.g., a configuration set may include a first CG configuration for URLLC and a second CG configuration for eMBB based on the first and second CG configurations having a common periodicity, modulation coding scheme (MCS), time offset, and/or the like).