# Dynamic device mapping

> Mediated Wiki article. Canonical URL: https://mediated.wiki/source/Dynamic_device_mapping
> Markdown URL: https://mediated.wiki/source/Dynamic_device_mapping.md
> Source: https://en.wikipedia.org/wiki/Dynamic_device_mapping
> Source revision: 1240160909
> License: Creative Commons Attribution-ShareAlike 4.0 International (https://creativecommons.org/licenses/by-sa/4.0/)

**Dynamic device mapping** is a technology for [USB](/source/USB) [KVM switches](/source/KVM_switch) which is sometimes implemented as an alternative to standard [USB](/source/USB) [keyboard](/source/Keyboard_(computing)) and [mouse](/source/Mouse_(computing)) emulation.

## Design

With DDM (Dynamic Device Mapping) Technology, the communication between shared [peripherals](/source/Peripherals) and all connected systems are maintained 100% of the time, even as a user switches between the KVM ports. This makes generic device emulation unnecessary as the DDM allows each connected computer system to believe all connected [I/O](/source/I/O) devices are remaining connected even as the [KVM switch](/source/KVM_switch) might move to another port.

## KVM device emulation

Many USB [KVM devices](/source/KVM_Switch) provide [peripheral emulation](/source/Hardware_emulation), sending signals to the computers that are not currently selected to simulate a keyboard, mouse and monitor being connected. The emulation is used to avoid problems with machines which may reboot in unattended operation. [Peripheral emulation](/source/Hardware_emulation) services embedded in the hardware also provides continuous support where computers require constant communication with the [peripherals](/source/Peripheral). In addition, some types of computer systems do not treat [USB](/source/USB) devices as [hot-pluggable](/source/Hot-swappable), which means the keyboard and mouse will not be re-detected when switching back to a particular KVM port. For these types of systems, it is necessary to implement device emulation.

Standard device emulation has its limitations. When emulating a [USB](/source/USB) keyboard, mouse, and monitor it is impossible for most KVM's to simulate various types of I/O devices specifically. As a result, [KVM switches](/source/KVM_switch) will sometimes offer inconsistent performance and even sometimes unsolved compatibility issues with the shared keyboard, mouse, and other devices. The intent of Dynamic Device Mapping is to resolve the issues that standard device mapping sometimes faces.

## Applications for USB DDM

- sharing touchscreen monitor among connected systems
- integrated multi-vendor [self-service kiosk systems](/source/Self-service_kiosk)
- secured user login by sharing USB [smart card](/source/Smart_card) or [biometrics](/source/Biometrics) reader (e.g. fingerprint scanner)

## See also

- [KVM switch](/source/KVM_switch)
- [Display data channel](/source/Display_data_channel)
- [Display Control Channel](/source/Display_Control_Channel)
- Reverse DDM

## References

- [USB and USB Device Details](https://web.archive.org/web/20110713051905/http://www.iogear.com/support/faq/id/10184)

- [U.S. Patent Information](http://appft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&p=1&u=%2Fnetahtml%2FPTO%2Fsearch-bool.html&r=3&f=G&l=50&co1=AND&d=PG01&s1=june-on&OS=june-on&RS=june-on)

---
Adapted from the Wikipedia article [Dynamic device mapping](https://en.wikipedia.org/wiki/Dynamic_device_mapping) by Wikipedia contributors ([contributor history](https://en.wikipedia.org/wiki/Dynamic_device_mapping?action=history)). Available under [Creative Commons Attribution-ShareAlike 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/). Changes may have been made.