Revision Summary Date Revision History Revision Class Comments 3/30/2012 1.0 New Released new document. 7/12/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 2.0 Significantly changed the technical content. 11/14/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 2.0 None No changes to the meaning, language, or formatting of the technical content.
UUID for ITpmVirtualSmartCardManager UUID for ITpmVirtualSmartCardManager2 [C706] UUID for ITpmVirtualSmartCardManagerStatusCallback [C706] UUID for ITpmVirtualSmartCardManager3 [C706]
Return Values: The server MUST return 0 if it successfully locates and destroys the indicated VSC, and a nonzero value otherwise. Exceptions Thrown: No exceptions are thrown beyond those thrown by the underlying RPC protocol . The server MUST validate the parameters before executing the requested operation and fail requests with invalid parameters. In response to the request, the server MUST locate the VSC using the provided instance identifier from the underlying smart card implementation compliant with , remove its registration with the implementation, and clear all data structures associated with the VSC. If pStatusCallback is present, the server SHOULD notify the client of the progress and errors of the undergoing operation, as specified in section . The status callback happens synchronously with the requested operation. If the status callback returns an error code, the server SHOULD try to abort the requested operation and roll back all changes related to the operation. If the operation is aborted, the server MUST return a non-zero error code to the client, with the severity bit in the error code set to 1. If the operation cannot be aborted, the server MUST ignore the error from the status callback interface and complete the requested operation. Timer Events None. Local Events None. ITpmVirtualSmartCardManagerStatusCallback Server Details Abstract Data Model This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model as long as their external behavior is consistent with that described in this document. TPMVSC management requests: The set of that are currently in progress from this host to remote ITpmVirtualSmartCardManager interfaces. This state is shared with the ITpmVirtualSmartCardManager client implementation. Timers None. Initialization The server is initialized by the ITpmVirtualSmartCardManager interface client as part of the process of making a request on that interface. The server MUST register itself with the DCOM infrastructure and bind to a dynamic endpoint obtained from the RPC runtime.
Index A Abstract data model server ( 15, 18, 20, 23) 15 20 18 8 C 8 34 10 10 13 26 26 16 23 20 D Data model - abstract server ( 15, 18, 20, 23) 15 20 18 Data 10 17 E Enumerations 10 13 11 12 Events local server 18 22 20 local - server ( 18, 20, 22, 25) timer server 18 22 20 - server ( 18, 20, 22, 25) Examples 26 26 F 8 29 G 5 I 29 28 28 6 Initialization server ( 15, 18, 20, 23) 15 20 18 Interfaces server 20 Interfaces - server 20 22 5 ITpmVirtualSmartCardManager2 interface 20 20 20 22 L Local events server ( 18, 20, 22, 25) 18 22 20 M Message processing server ( 15, 19, 20, 23) 15 20 19 Messages 10 10 Methods 16 23 20 17 19 19 N 5 O 6
P 28 14 8 8 33 Protocol Details 15 R 5 6 5 7 19 19 S Security 28 28 Sequencing 15 20 19 server ( 15, 19, 20, 23) Server abstract data model ( 15, 18, 20, 23) 16 23 20 17 initialization ( 15, 18, 20, 23) ITpmVirtualSmartCardManager 15 16 17 15 18 15 15 18 15 ITpmVirtualSmartCardManager2 20 20 20 20 22 20 20 22 20 20 22 ITpmVirtualSmartCardManagerStatusCallback 18 18 20 19 19 19 19 20 18 local events ( 18, 20, 22, 25) message processing ( 15, 19, 20, 23) overview ( 20, 22) 19 19 sequencing ( 15, 19, 20, 23) timer events ( 18, 20, 22, 25) timers ( 15, 18, 20, 23) 13 8 Structures 13 14 T Timer events server ( 18, 20, 22, 25) 18 22 20 Timers server ( 15, 18, 20, 23) 15 20 18 11 12 34 10 V 8 8