Resource slicing on a sidelink interface
摘要
說(shuō)明書
In example 400, the Tx UE 405 may determine that a first resource allocation (e.g., RA 1) is associated with a first slice identifier of “Slice ID 1,” and may determine that a second resource allocation (e.g., RA 2) is associated with a second slice identifier of “Slice ID 2.” In this case, the Tx UE 405 may transmit or receive (e.g., monitor for) D2D communications associated with the first D2D and/or V2X application (D2D/V2X App 1) on resources selected from the first resource allocation, and may transmit or receive D2D communications associated with the second D2D and/or V2X application (D2D/V2X App 2) on resources selected from the second resource allocation. In this way, D2D and/or V2X applications having different requirements can use different resource allocations, which may be configured according to one or more requirements of a corresponding D2D and/or V2X application to improve performance.
