-->

The Miracast over Infrastructure protocol provides theability to transmit a multimedia data stream over a local wireless networkinstead of Wi-Fi Direct (WFD).The process of such transmission is called 'projection'.

Microsoft Comfort Mouse 3000 for Business Black 3 Buttons 1 x Wheel USB Wired BlueTrack. Hand Orientation: Both Hands Maximum dpi: 1000 dpi Operating System Supported: Microsoft Windows 7, Windows Vista, and Windows XP (excluding Windows XP 64-bit) Macintosh Mac OS X v10.4.x-10.6.x. Microsoft Comfort Mouse 3000 for Business Black 3 Buttons 1 x Wheel USB Wired BlueTrack. Hand Orientation: Both Hands Maximum dpi: 1000 dpi Operating System Supported: Microsoft Windows 7, Windows Vista, and Windows XP (excluding Windows XP 64-bit) Macintosh Mac OS X v10.4.x-10.6.x.

A Miracast over Infrastructure session involves thefollowing principals.

Mouse

Microsoft Basic Optical Mouse - 800 dpi - Black - Wired - P58-00061. Hand Orientation: Both Hands Maximum dpi: 800 dpi Operating System Supported: Win 10 64 bit / Win 10 32 bit / Win 8.1 32 bit / Win 8.1 64 bit / Win 8 32 bit / Win 8 64 bit / Win 7 32 bit / Win 7 64 bit / Win RT 8.1 / Win RT 8 Mac OS 10.10 / Mac OS 10.9 / Mac OS 10.8 / Mac OS 10.7 Android 5.0, Nexus 9 / Android 4.4.4, Nexus 5. Explore computer accessories and peripherals from Microsoft. Get the most out of your PC or Surface with keyboard, mice, webcams, headsets, adapters and more.

Miracast Source: A device that sends audio and videostreams to the Miracast Sink. This device is sometimes called a'sender'. Optionally, this device can also receive input signals fromthe Miracast Sink.

Miracast Sink: A device that receives audio and videostreams from the Miracast Source. This device is sometimes called a'receiver'. Optionally, this device can also send input signals backto the Miracast Source.

The following diagram illustrates the logical flow ofestablishing a Miracast over Infrastructure session, including successful andunsuccessful outcomes. For further details, see Protocol Details (section 3).

Figure 1: A Miracast over Infrastructure session

A Miracast over Infrastructure session consists of threephases: device discovery, host name resolution, and projection.

The device discovery phase starts with a Miracast Sourcetrying to find devices capable of performing the role of Miracast Sink. EachSink advertises its capabilities by transmitting Beacon and ProbeResponse frames that might include WSC IE Vendor Extensionattributes (section 2.2.8).

A Sink is selected from those discovered; for example, byasking a user to pick one. If the Vendor Extension attribute from the selectedSink does not indicate support for Miracast over Infrastructure, the Sourcefalls back to using standard Miracast [WF-WSC2.0.2].

If the Vendor Extension attribute contains one or more IPAddress attributes (section 2.2.8.5), theSource optionally skips the host name resolution phase and proceeds to theprojection phase.

In the host name resolution phase, name resolution isperformed on the name in a Host Name attribute (section 2.2.8.2)in the Vendor Extension attribute. If name resolution is unsuccessful, theSource again falls back to using standard Miracast.

In the projection phase, the Source attempts a connection tothe Sink for sending Miracast over Infrastructure messages (section 2.2).Finally, the Sink establishes a connection with the Source for streamingmultimedia data. If that connection cannot be established, the entire processfails.

-->Microsoft

The Miracast over Infrastructure Connection EstablishmentProtocol specifies a connection negotiation sequence used to connect, indicatereadiness to connect, and disconnect from a Miracast over Infrastructureendpoint. This protocol also specifies the Miracast over InfrastructureInformation Element (IE), which helps identify Miracast receivers (sinks) thatcan support a Miracast session over an infrastructure link (as opposed to aWi-Fi Direct link).

This page and associated content may beupdated frequently. We recommend you subscribe to the RSSfeed to receive update notifications.

Download

Published Version

Date

Protocol Revision

Revision Class

Downloads

5/30/2019

3.0

None

PDFDOCXDiff

Previous Versions

Date

Protocol Revision

Revision Class

Downloads

9/12/2018

3.0

Major

PDFDOCXDiff

3/16/2018

2.0

Major

PDFDOCXErrataDiff

6/1/2017

1.1

Minor

PDFDOCXDiff

3/16/2017

1.0

New

PDFDOCX

Preview Versions

From time to time, Microsoft maypublish a preview, or pre-release, version of an Open Specifications technicaldocument for community review and feedback. To submit feedback for a previewversion of a technical document, please follow any instructions specified forthat document. If no instructions are indicated for the document, pleaseprovide feedback by using the Open Specification Forums.

Microsoft Mice & Touchpads Driver Download

The preview period for a technical document varies.Additionally, not every technical document will be published for preview.

A preview version of this document may beavailable on the WindowsProtocols - Preview Documents page. After the preview period, themost current version of the document is available on this page.

Development Resources

Findresources for creating interoperable solutions for Microsoft software,services, hardware, and non-Microsoft products:

Plugfestsand Events, Test Tools,DevelopmentSupport, and Open SpecificationsDev Center.

Microsoft Mice Wireless

Intellectual Property Rights Notice for Open Specifications Documentation

  • Technical Documentation. Microsoft publishes OpenSpecifications documentation (“this documentation”) for protocols, fileformats, data portability, computer languages, and standards support.Additionally, overview documents cover inter-protocol relationships andinteractions.

  • Copyrights. This documentation is covered by Microsoftcopyrights. Regardless of any other terms that are contained in the terms ofuse for the Microsoft website that hosts this documentation, you can makecopies of it in order to develop implementations of the technologies that aredescribed in this documentation and can distribute portions of it in yourimplementations that use these technologies or in your documentation asnecessary to properly document the implementation. You can also distribute inyour implementation, with or without modification, any schemas, IDLs, or codesamples that are included in the documentation. This permission also applies toany documents that are referenced in the Open Specifications documentation.

  • No Trade Secrets. Microsoft does not claim any tradesecret rights in this documentation.

  • Patents. Microsoft has patents that might cover yourimplementations of the technologies described in the Open Specificationsdocumentation. Neither this notice nor Microsoft's delivery of thisdocumentation grants any licenses under those patents or any other Microsoftpatents. However, a given Open Specifications document might be covered by theMicrosoft Open Specifications Promiseor the Microsoft CommunityPromise. If you would prefer a written license, or if thetechnologies described in this documentation are not covered by the OpenSpecifications Promise or Community Promise, as applicable, patent licenses areavailable by contacting [email protected].

  • License Programs. To see all of the protocols in scopeunder a specific license program and the associated patents, visit the Patent Map.

  • Trademarks. The names of companies and products containedin this documentation might be covered by trademarks or similar intellectualproperty rights. This notice does not grant any licenses under those rights.For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.

  • Fictitious Names. The example companies, organizations,products, domain names, email addresses, logos, people, places, and events thatare depicted in this documentation are fictitious. No association with any realcompany, organization, product, domain name, email address, logo, person,place, or event is intended or should be inferred.

Reservation of Rights. All otherrights are reserved, and this notice does not grant any rights other than asspecifically described above, whether by implication, estoppel, or otherwise.

Tools.The Open Specifications documentation does not require the use of Microsoftprogramming tools or programming environments in order for you to develop animplementation. If you have access to Microsoft programming tools andenvironments, you are free to take advantage of them. Certain OpenSpecifications documents are intended for use in conjunction with publiclyavailable standards specifications and network programming art and, as such,assume that the reader either is familiar with the aforementioned material orhas immediate access to it.

Microsoft Ps/2 Mouse Driver Touchpad Download

Support.For questions and support, please contact [email protected].

Coments are closed
Scroll to top