tech-invite   World Map     

IETF     RFCs     Groups     SIP     ABNFs    |    3GPP     Specs     Gloss.     Arch.     IMS     UICC    |    Misc.    |    search     info

ETSI (SCP TEST)
TS 102 694-1

 

 

 

 

Top

 

Up

 

Prev

 

Next

 

 

 

Smart Cards –
Test specification for the Single Wire Protocol (SWP) interface –
Part 1:  Terminal features

(P) V10.2.0    2015-03    94 p.
(P) V9.5.0    2013-12    96 p.
(P) V8.2.0    2012-03    88 p.
(P) V7.4.0    2011-07    9 p.


The present document defines test cases for the terminal relating to Single Wire Protocol (SWP). SWP is the communication interface between the UICC and a contactless frontend (CLF) as specified in TS 102 613.

The aim of the present document is to ensure interoperability between the terminal and the UICC independently of the respective manufacturer, card issuer or operator.

The present document covers the minimum characteristics which are considered necessary for the terminal in order to provide compliance to TS 102 613.

The present document specifies the test cases for:
  • the physical layer of the interface CLF - UICC;
  • the electrical interface of the CLF;
  • the initial communication establishment CLF - UICC;
  • the data link layer.


1   Scope   p. 10
2   References
3   Definitions, symbols and abbreviations
4   Test environment   p. 14
5   Test cases
5.1   Principle of the Single Wire Protocol
5.2   System architecture
5.3   Physical characteristics
5.3.1   Temperature range for card operations
5.3.2   Contacts
5.3.2.1   Provision of contacts      Up
5.3.2.2   Contact activation and deactivation   p. 27
5.3.2.3   Interface activation
5.3.2.3.1   Conformance requirements
5.3.2.3.2   Test case 1: SWP initial activation in full power mode - normal procedure   p. 30
5.3.2.3.3   Test case 2: SWP Initial activation - no resume   p. 31
5.3.2.3.4   Test case 3: SWP initial activation in full power mode - corrupted ACT_SYNC frame (repeat the last frame)
5.3.2.3.5   Test case 4: SWP initial activation in full power mode - no ACT_SYNC frame (repeat the last frame)
5.3.2.3.6   Test case 5: SWP initial activation failed in full power mode - corrupted ACT_SYNC frame (multiple)   p. 32
5.3.2.3.7   Test case 6: SWP initial activation failed in full power mode - no ACT_SYNC frame (multiple)
5.3.2.3.8   Test case 7: SWP Initial activation in full power mode - corrupted ACT_READY frame (repeat last frame)   p. 33
5.3.2.3.9   Void
5.3.2.3.9a   Test case 8a: SWP Initial activation in full power mode - no ACT_READY frame (repeat last frame)   p. 34
5.3.2.3.10   Test case 9: SWP initial activation failed in full power mode - corrupted ACT_READY frame (multiple)
5.3.2.3.11   Test case 10: SWP initial activation failed in full power mode - no ACT_READY frame (multiple)   p. 35
5.3.2.3.12   Test case 11: SWP initial activation in low power mode   p. 36
5.3.2.3.13   Test case 12:SWP initial activation in low power mode - corrupted ACT_SYNC frame (repeat the last frame)
5.3.2.3.14   Test case 13: SWP initial activation in low power mode - no ACT_SYNC frame (repeat the last frame)   p. 37
5.3.2.3.15   Test case 14: SWP initial activation failed in low power mode - corrupted ACT_SYNC frame (multiple)
5.3.2.3.16   Test case 15: SWP initial activation failed in low power mode - no ACT_SYNC frame (multiple)   p. 38
5.3.2.3.17   Test case 16: SWP subsequent activation in full power mode
5.3.2.3.18   Void
5.3.2.3.19   Test case 18: SWP initial activation in full power mode - send ACT frames in wrong order, ACT_READY frame after activation (repeat the last frame)   p. 39
5.3.2.4   Behavior of a UICC in a terminal not supporting SWP      Up
5.3.2.5   Behavior of terminal connected to a UICC not supporting SWP   p. 40
5.3.2.6   Inactive contacts
5.4   Electrical characteristics
5.5   Physical transmission layer   p. 46      Up
5.5.1   S1 Bit coding and sampling time
5.5.2   S2 switching management      Up
5.5.3   SWP interface states management   p. 49
5.5.4   Power mode states/transitions and Power saving mode      Up
5.6   Data link layer   p. 53
5.7   SHDLC LLC definition   p. 59
5.7.1   SHDLC overview
5.7.2   Endpoints
5.7.3   SHDLC frames types      Up
5.7.4   Control Field
5.7.5   Changing sliding window size and endpoint capabilities      Up
5.7.6   SHDLC context
5.7.7   SHDLC sequence of frames
5.7.7.1   Conformance requirements
5.7.7.2   Nomenclature
5.7.7.3   Link establishment with default sliding window size   p. 63
5.7.7.4   Link establishment with custom sliding window size   p. 66      Up
5.7.7.5   Data flow
5.7.7.6   Reject (go N back)   p. 68
5.7.7.7   Last Frame Loss      Up
5.7.7.8   Receive and not ready   p. 70
5.7.7.9   Selective reject   p. 71
5.7.8   Implementation      Up
5.8   CLT LLC definition
5.9   Timing and performance
A   Void
B   Core specification version information   p. 91      Up
C   Change history   p. 92

Top