[FS_ULBC] On target platforms for ULBC
This contribution addresses a gap in TR 26.940 regarding target platforms for Ultra Low Bit rate Codec (ULBC) deployment. While the TR currently discusses NPU as a possible platform in clause 6.2.1.5.1, it lacks coverage of other non-NPU platforms. The document aims to complete this missing information, particularly focusing on DSP-enabled devices.
The contribution identifies an inconsistency in TR 26.940:
The source references previous contributions (S4aA250267 and S4-251747) that discussed the need for DSP deployment and provided clarification on DSP-enabled UE devices.
The contribution adopts the definition from S4-251747 for DSP-enabled UE devices:
The proposal adds a new paragraph to clause 6.2.1.5.1 that:
Acknowledges vendor flexibility: Vendors may choose any computing unit to implement ULBC based on business needs or product constraints
Highlights DSP advantages:
Potentially wider range of product support
Establishes DSP deployment requirement: ULBC should be deployable on DSP-enabled UE devices, including:
Devices with multiple computing units including DSP
Provides deployment rationale: Even when CPU or NPU are available, DSP may be preferred for power-sensitive applications (wearables, mobile phones)
Defines DSP computational power: Audio processing DSPs typically range from several hundred to over a thousand MIPS
The proposal maintains the existing text about:
- NPU prevalence in modern smartphones
- NPU being 5-20x more power efficient than CPUs for AI tasks
- The note that ULBC may need to run on non-NPU platforms in certain configurations
This contribution ensures that TR 26.940 provides comprehensive guidance on target platforms for ULBC deployment, balancing the AI-optimized NPU approach with the power-efficient DSP approach, thereby supporting a wider range of device implementations and use cases.