 (802.11 and MIMO). In the personal area, the decision would be whether to support Bluetooth EDR and/or NFC. In the audio system domain, the choice for voice would be which of the higher-rate voice codecs to support, the choice for audio would be which audio codec to support, other choices would be functional such as voice or speech recognition support, advanced noise cancellation, extended audio capture or advanced search and playback capabilities. In the positioning domain, the choice is essentially rate, resolution and accuracy both in micro- and macropositioning. An improvement in any one of these metrics will imply additional processor loading. In the imaging domain, the decision would be whether to support newer coding schemes such as JPEG2000 (imaging) or H264/MPEG Part 10 AVC/SVC or, in general, any of the emerging wavelet-based progressive rendering schemes. In the data domain, decisions revolve around the amount of local and remote storage dedicated to personal and corporate data management systems and related data set management capabilities. 21.13 Testing the Model on Specific Applications To be valid, we now need to show that the model has relevance when applied to specific appli- cations. For example, a gaming application may be a composite of radio layer functionality, audio functionality, micro- and macropositioning functionality, imaging functionality and Making Telecoms Work personal profiling (personal data set management). A camera phone application will already have wide-area radio access, may have enhanced audio, should probably have integrated positioning, will certainly have imaging and should have data functionality. 21.13.1 The Concept of a 'Dominant Domain' This leads us towards defining future handsets in terms of their 'dominant domain'. The 'dominant domain' of an audio phone is the audio system domain with potentially all other domains adding complementary domain value. The dominant domain of a location device is the positioning domain with potentially all other domains adding domai