Windows Logo Program

səhifə	23/37
tarix	18.07.2016
ölçüsü	1.03 Mb.

1 ... 19 20 21 22 23 24 25 26 ... 37

B5.6 Smart Card Readers

All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.
All general input requirements in B5.1 are included by reference.

B5.6.1 Smart Card - Windows Compatibility

B5.6.1.1 Windows XP/Windows 2000 and Windows 98/Me: “Smart Card Devices” in the Windows DDK

B5.6.1.2 Windows compatibility and implementation notes (general)

http://www.microsoft.com/hwdev/smartcard/

Note: Smart Card base software components must be installed before the driver on Windows 98/Me; the base components are automatically installed on Windows 2000.

B5.6.2 Smart Card - Industry Standards

B5.6.2.1 ISO/IEC DIS 7816 Identification Cards—Integrated circuit(s) cards with contacts

[SMRT-0153; SDG3:196]

Part 1: Physical characteristics - http://www.iso.ch/cate/d29257.html.

Part 2: Dimensions and location of the contacts - http://www.iso.ch/cate/d26536.html.
Part 3: Electronic signals and transmission protocols - http://www.iso.ch/cate/d14735.html.

B5.6.2.2 Interoperability Specification for ICCs and Personal Computer Systems

http://www.pcscworkgroup.com/

B5.6.2.3 ISO/IEC 7811

[SMRT-0153]

Part 1: Embossing

Part 3: Location of embossed characters on ID-1 cards
ISO/IEC 7813:1995 Identification Cards—Financial transaction cards
ISO/IEC 10373:1993 Identification cards—Test methods

B5.6.3 Smart Card - Quality

B5.6.3.1 SEE B5.6.4.6

B5.6.3.2 Pass WHQL tests

See B1.3.

Windows XP: See “Smart Card Readers ” in HCT documentation.

B5.6.4 Smart Card - Windows Experience

Design Guideline References:
PC 2001 System Design Guide, Chapter 7, "Input Devices" ;
SMRT-0162; SDG3:196
Smart Card for Windows web site at http://www.microsoft.com/smartcard/

B5.6.4.1 Driver does not cause system to stop running if required resources are not available

B5.6.4.2 Driver supports multiple instances of the same device on system without problems

B5.6.4.3 Windows XP/Windows 2000: Device works properly after system resumes from S3 or hibernation state

Note: Hibernation tests on Windows 98/Me are disabled.

B5.6.4.4 Reader supports required capabilities

[SMRT-0154-0159]

Direct and Inverse-convention smart cards. [SMRT-0155]
258 byte packets in T=0 and 259 byte packets in T=1. [SMRT-0156]
Smart card insertion/removal monitor. [SMRT-0157]
PTS not required.

Reader must support negotiable and specific modes according to ISO/IEC 7816-3 (1997-12-15) Sections 6 and 7. [SMRT-0158]

3.5795 MHz minimum clock frequency. [SMRT-0159]
9600 bps minimum data rate.
Reset command [SMRT-0154]

B5.6.4.5 Input device implementing a PIN data-entry keyboard complies with ISO 13491-1

[SMRT-0162]

B5.6.4.6 Hot-plugging for PC Card does not cause system to stop running or other problems; USB reader is functional upon hot-plugging

[SYS-0030; SDG3:47]

B5.6.5 Smart Card - FAQs

B5.6.5.1 Current smart card FAQs

See http://www.microsoft.com/winlogo/hardware/input/.

B5.6.5.2 PTS and Power Down citations [Correction]

The correct citation for PTS support is ISO 7816-3 (1997-12-15) Section 7. The correct citation for Power Down command is ISO 7816-3 (1997-12-15) Section 5.4. Power Down command for ISO 7816-3 is optional, but Reset command is mandatory.
FAQ Date: October 7, 1998

B5.6.R Smart Card - Future Requirements

Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/input/.

B6.0 Modems

B6.1 General Modem

All general requirements in B1.0 are included by reference.
All bus-specific requirements in B2.0 are included by reference.

B6.1.1 General Modem - Windows Compatibility

B6.1.1.1 Windows Modem Development Kit: “Modem Devices” in the Windows DDK

[MOD-0366; SDG3:92]

B6.1.1.2 Windows compatibility and implementation notes (general)

http://www.microsoft.com/hwdev/modem/

B6.1.1.3 Unimodem Diagnostics Command Reference Specification

http://www.microsoft.com/hwdev/respec/commspec.htm

B6.1.1.4 Standard Modem Command Sets and Standard Modem INFs

http://www.microsoft.com/hwdev/modem/comndset.htm

B6.1.1.5 Guidelines for WDM-based Software Modems

[MOD-0383]
http://www.microsoft.com/hwdev/modem/softmodem.htm

See also FAQs B6.1.5.6, B6.1.5.7, B6.1.5.8.

B6.1.2 General Modem - Industry Standards

B6.1.2.1 No requirement

Note: The current version of "National ISDN Basic Rate Interface Terminal Equipment Generic Guidelines" provides a collection of industry specifications and standards for Integrated Services Digital Network (ISDN); see http://www.telcordia.com/index.html.

B6.1.2.2 Bellcore Technical References

http://www.telcordia.com/index.html

B6.1.2.3 Communications Device Class Power Management Reference Specification, V. 2.0

[MOD-0381, 0382]
http://www.microsoft.com/hwdev/specs/PMref/PMcom.htm

B6.1.2.4 EIA Standard #ANSI/EIA-516-88

Joint EIA/CVCC Recommended Practice for Teletext: North American Basic Teletext Specification (NABTS) - http://www.tiaonline.org/.

B6.1.2.5 ETSI (European Telecommunication Standards Institute)

http://www.etsi.org/

B6.1.2.6 ITU (International Telecommunication Union) communications standards

http://www.itu.int/publications/index.html

B6.1.2.7 USB Class Definitions for Communications Devices

[MOD-0380; SDG3:70]
http://www.usb.org/developers/docs.html

Version 1.1 for External Devices.

B6.1.2.8 PHS Internal Access Forum Specification (PIAFS)

http://mitf.arib.or.jp/e/menu.html

B6.1.2.9 SII NS-2482-30

http://www.sii.co.jp/js/nshp/product/index-e.html (English); http://www.sii.co.jp/js/nshp/product/NS2482/ns2482_30.html (Japanese).

B6.1.3 General Modem - Quality

WHQL Test Specification References:
Chapter 20: Modem Test Specification

B6.1.3.1 Pass WHQL tests

See B1.3.

Windows XP: See “Modem” in HCT documentation.

B6.1.4 General Modem - Windows Experience

Design Guideline References:
PC 2001 System Design Guide, Chapter 13, "Modems"
Hardware Design Guide 3.0 for Windows 2000 Server, Chapter 4

B6.1.4.1 Wake on Ring (if implemented) meets OnNow requirements

[MOD-0381, 0382; SDG3:103]

See FAQ B6.1.5.9.

B6.1.4.2 Analog modem supports standard capabilities

[MOD-036x; SDG3:10x]

V.250 Extended AT Command Set (formerly V.25 ter). [MOD-0368; SDG3:101; see also FAQ B6.1.5.3]
modem supports country selection +GCI. [MOD-0368]
If implemented, wireless/cellular modem supports appropriate control commands. [MOD-0368, MOD-0376, MOD-0386-0388; SDG3:100]
V.90 connectivity, V.42 Link Access Protocol, Modem (LAPM), V.42 bis, and V. 80 Synchronous Access data protocols. [MOD-0369; SDG3:104]
Connection to two distinct V.90 host modems (such as 3Com and Conexant) at 40 Kbps or better.
Modem call control supports media detection using V.251. [MOD-0370]
If implemented, modem supports caller ID reporting. [MOD-0376; see also FAQ B6.1.5.10]
If implemented, voice modem supports ITU V.253. Voice modem optionally supports speakerphone. [MOD-0374; SDG3:110; see also FAQ B6.1.5.4]
Fax—14.4 Kbps (V.17) with Class 1 (TIA-578-A) command set. [MOD-0371; SDG3:106]

B6.1.4.3 Controller-based modem supports additional capabilities

9.6 Kbps connectivity to analog modem.
Connection to reference modem; see test documentation for list.
Error control and blind dial.
AT commands:
ATA - accept ringing
ATD - dial
ATE - echo setting
ATH - hangup
ATI - get modem information
S0 - S0 register (0 value is to disable to accept ringing)
ATV - response code style
ATZ - reset
- - Initialize
- - Hard/Soft flow control

B6.1.4.4 PIAFS modem supports additional capabilities

32 Kbps (PIAFS 1.0) connectivity to PIAFS modem.
Connection to DC-6S in PIAFS 1.0 and to SII NS-2482-30 (dial-up).
Modem generates appropriate error messages for delayed and blacklisted numbers (where applicable). [MOD-0372; SDG3:108]

B6.1.4.5 ISDN modem

See B7.4.

B6.1.4.6 DELETED

B6.1.4.7 Global System for mobile communications or digital cellular phone support, if implemented, includes required command and protocol support

[MOD-0387]

B6.1.4.8 Analog V.90 modem tested in conjunction with digital V.90 modems commonly deployed by ISPs

[MOD-0377, 0378, 0379]

Telecommunications Industry Association (TIA) TSB-38 provides detailed test procedures and criteria.

Operation on impairment combination 2C4 as specified in ITU-T Recommendation V.56 bis.
Modem must be able to repeatedly connect, with an overall call completion success ratio of 97 percent with a minimum of 50 iterations, and without the modem stalling in an unresponsive, inoperable state.
Modem pair must be able to sustain the connection for at least 30 minutes, at no less than 90 percent of the initial connection rate, with no more than 1 retrain, using the same TSB-3800 line I01d-loop 3 specified for use under B6.1.4.
E-mail: Microsoft Outlook® Express over Microsoft Hotmail®.
Web browsing: Internet Explorer.
Video teleconferencing using H.323: Microsoft NetMeeting®.

B6.1.4.9 Telephony applications meet communication and performance requirements

[MOD-0389, MOD-0390]

Note: If a future ITU recommendation equivalent to TIA-3800 for the testing of pulse-coded modulation (PCM) modem operation is developed, passing such tests could become a requirement in future versions the Windows Logo Program.

B6.1.4.10 Windows Whistler Advanced Server: Data modem supports digital connection to support host-side V.90 operation

[SDG3:105]

B6.1.5 General Modem - FAQs

B6.1.5.1 Current Modem FAQs

See http://www.microsoft.com/winlogo/hardware/modem/.

B6.1.5.2 DELETED

Modems are not required on any system.
FAQ Date: January 31, 2001

B6.1.5.3 Unimodem required commands [Clarification]

[MOD-0368; SDG3:101]

Windows Unimodem does not use the following commands directly; therefore, these are not in the sample INF and are not required: +ICF, +MA, +EB, +ESR, +ETBM. These commands are only required if the function is controllable in the modem by way of AT commands; in that case, the standard V.250 commands defined here must be included.

FAQ Date: October 7, 1998

B6.1.5.4 Voice recording and playback capabilities [Logo Program correction]

[MOD-0374; SDG3:110]

The capability for voice recording and playback (+VTX, +VRX) is not required.

FAQ Date: July 8, 1999

B6.1.5.5 DELETED

B6.1.5.6 WDM support for driver-based modems [Logo Program clarification]

[MOD-0383]

WDM support for driver-based modems is required for Windows Me and Windows XP/Windows 2000. For information about the Ccport.sys QFE for Windows 98, see http://www.microsoft.com/hwdev/devdes/modem_up.htm.

FAQ Date: July 28, 1999; revisions August 26, 1999, March 3, 2000

B6.1.5.7 Total execution time for DPCs queued by a WDM modem [Clarifications]

At any instant in time, the total execution time required for all delayed procedure calls (DPCs) that have been queued by a WDM driver-based modem, but have not dequeued and started executing, should not exceed 500 milliseconds.

A WDM driver-based modem should not continuously disable thread preemption for more than 4.4 milliseconds. This guideline accommodates 400 microseconds of interrupts being disabled together with two back-to-back episodes of 2.0 milliseconds of extended processing at DISPATCH_LEVEL, as up to four 500-microsecond DPCs execute sequentially.

FAQ Date: October 7, 1998

B6.1.5.8 WDM modem latency tolerances [Clarifications]

A driver-based modem should be able to tolerate:

A period of 4 milliseconds with interrupts disabled.
A continuous period of 8 milliseconds during which a queued DPC is held off from execution, possibly by other DPCs.
A 16-millisecond period when thread scheduling is continuously disabled.

See http://www.microsoft.com/hwdev/devdes/modem_up.htm.
FAQ Date: October 7, 1998

B6.1.5.9 Modem supports wake-up events [Clarification]

[MOD-0381, 0382; SDG3:102]

PCI modems must support power states D0 and D3. PCI devices are required to support the D3 state on a PCI 2.2-enabled system with auxiliary power. On all other power-managed buses (such as USB), support for either D2 or D3 state is acceptable. Modem drivers must accept power management IRPs.

FAQ Date: October 7, 1998; June 14, 2000

B6.1.5.10 Analog modem correctly reports caller ID [Clarification]

For hardware-based modems, see ITU-T V253 section 9.2.3.1 for details about correctly implementing caller ID reporting.

Note: Software-based modems are not required to capture caller ID while the system is either in ACPI S3 sleep state or resuming from S3 state.
FAQ Date: May 08, 2001

B6.1.R General Modem - Future Requirements

Announcement of additional future requirements will be published at http://www.microsoft.com/winlogo/hardware/modem/.

1 ... 19 20 21 22 23 24 25 26 ... 37