Editing Media Transfer Protocol (section)

==Overview==
MTP is a high level [[file transfer]] protocol, as opposed to a general storage protocol like [[USB mass storage]]. That means that the MTP client (computer) does not see an array of [[block device|byte blocks]] that makes up a [[data structure]] that makes up a [[file system]], but instead speaks in terms of files and folders to the MTP device. This lets the MTP device take part in the high level operations (such as updating its metadata indexes) while keeping the integrity of its file system in its own hands. In particular, dropped transfers (such as by unplugging the USB cable too soon) do not corrupt the device file system.<ref name="elinux">{{cite web|url=http://elinux.org/images/8/85/Media_Transfer_Protocol.pdf|title=Fear and Loathing in the Media Transfer Protocol|at=PTP/MTP basics|website=eLinux|access-date=February 7, 2021|archive-date=February 7, 2021|archive-url=https://web.archive.org/web/20210207213707/https://elinux.org/images/8/85/Media_Transfer_Protocol.pdf|url-status=live}}</ref> The non-generality of MTP has consequences for how a computer [[operating system]] can present the MTP device, both to other programs and to the user.

According to its specification, the main purpose of MTP is to facilitate communication between media devices with transient connection.<ref name="spec1.1"/>
A secondary purpose being to enable command and control of the connected device.<ref name="spec1.1"/> A battery-powered mobile device can report its battery charge level through MTP.<ref name="elinux"/>

The protocol was originally implemented for use across USB but extended for use across [[TCP/IP]] and [[Bluetooth]]. [[Windows Vista]] supports MTP over TCP/IP. [[Windows 7]] and Windows Vista with the Platform Update for Windows Vista also support MTP over Bluetooth.<ref>{{cite web|url=https://blogs.msdn.microsoft.com/wpdblog/2009/08/29/mtp-over-various-transports/|title=MTP Over Various Transports|date=August 29, 2009 |access-date=June 1, 2016|archive-date=May 1, 2019|archive-url=https://web.archive.org/web/20190501155338/https://blogs.msdn.microsoft.com/wpdblog/2009/08/29/mtp-over-various-transports/|url-status=live}}</ref> The host connecting to an MTP device is called an ''MTP Initiator'', whereas the device itself is an ''MTP Responder''.<ref name="Implementation">{{cite web|url=https://download.microsoft.com/download/f/1/3/f13df1a5-6ce4-4907-86a0-6ce5c3560639/MTP_Enhanced.exe|url-status=live|title=MTP Specification|archive-url=https://web.archive.org/web/20110604235827/http://download.microsoft.com/download/f/1/3/f13df1a5-6ce4-4907-86a0-6ce5c3560639/MTP_Enhanced.exe|archive-date=June 4, 2011}}</ref>

MTP allows ''MTP Initiators'' to identify the specific capabilities of device(s) with respect to file formats and functionality. In particular, MTP Initiators may have to provide passwords and other information to unlock files, or otherwise enable [[digital rights management]]. Nothing specific of this nature is in the core standard, but the features are available via vendor extensions. MTPZ, the Zune Extension to MTP, specifically denies access to files until authentication has been processed, which is only possible using Windows Media Player 10 or higher.