WiGig SD Extension PAL Technical Specification

© 2015 Wi-Fi Alliance. All Rights Reserved. Used with the permission of Wi-Fi Alliance under the terms as stated in this document.

WiGig SD Extension PAL Technical Specification

Version 1.1

WI-FI ALLIANCE PROPRIETARY – SUBJECT TO CHANGE WITHOUT NOTICE

This document may be used with the permission of Wi-Fi Alliance under the terms set forth herein. By your use of the document, you are agreeing to these terms. Unless this document is clearly designated as an approved specification, this

document is a work in process and is not an approved Wi-Fi Alliance specification. This document is subject to revision or removal at any time without notice. Information contained in this document may be used at your sole risk. Wi-Fi Alliance assumes no responsibility for errors or

omissions in this document. This copyright permission does not constitute an endorsement of the products or services. Wi-Fi Alliance trademarks and certification marks may not be used unless specifically allowed by Wi-Fi Alliance.

Wi-Fi Alliance has not conducted an independent intellectual property rights ("IPR") review of this document and the information contained

herein, and makes no representations or warranties regarding IPR, including without limitation patents, copyrights or trade secret rights. This document may contain inventions for which you must obtain licenses from third parties before making, using or selling the inventions.

Wi-Fi Alliance owns the copyright in this document and reserves all rights therein. A user of this document may duplicate and distribute copies of the document in connection with the authorized uses described herein, provided any duplication in whole or in part includes the copyright notice and the disclaimer text set forth herein. Unless prior written permission has been received from Wi-Fi Alliance, any other use of this

document and all other duplication and distribution of this document are prohibited. Unauthorized use, duplication, or distribution is an infringement of Wi-Fi Alliance’s copyright.

NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY WI-FI ALLIANCE AND WI-FI ALLIANCE

IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS DOCUMENT AND ANY INFORMATION

CONTAINED IN THIS DOCUMENT.


of 113

Document History

Version Date Status Comments

1.1 7 January 2015 Final WFA formatted version with WFA cover

page and legal information, removed

Participants page, added Document History

page


of 113

Table of Contents 1 Overview................................................................................................................................................................................11

1.1 Scope ............................................................................................................................................................................11 1.2 Purpose .........................................................................................................................................................................11

2 Normative references ...........................................................................................................................................................12

3 Definitions .............................................................................................................................................................................12

4 Abbreviations and acronyms ...............................................................................................................................................13

5 Usage and Requirements......................................................................................................................................................13

6 Architecture ..........................................................................................................................................................................15

6.1 Device Models ..............................................................................................................................................................15 6.1.1 Device Model for WSD Host............................................................................................................................15 6.1.2 Device Model for WSD Device ........................................................................................................................16

6.2 Layer Management Model ............................................................................................................................................17 7 Functional Description .........................................................................................................................................................18

7.1 Control Plane Functions ...............................................................................................................................................18 7.1.1 Session Management .......................................................................................................................................18

7.1.1.1 Session setup ....................................................................................................................................................... 19 7.1.1.2 Session termination ............................................................................................................................................. 21 7.1.1.3 Check connection ................................................................................................................................................ 22 7.1.1.4 Session management state machine..................................................................................................................... 23

7.1.2 Bus Handle Management .................................................................................................................................25 7.1.2.1 Bus handle management model ........................................................................................................................... 25 7.1.2.2 Get bus handle ..................................................................................................................................................... 26 7.1.2.3 Release bus handle .............................................................................................................................................. 27 7.1.2.4 Suspend bus handle ............................................................................................................................................. 28 7.1.2.5 Resume bus handle .............................................................................................................................................. 29 7.1.2.6 Clear Bus ............................................................................................................................................................. 31 7.1.2.7 Bus handle management state machine ............................................................................................................... 32

7.1.3 Notification ......................................................................................................................................................33 7.1.4 Error Handling in Control Plane ....................................................................................................................34

7.2 Data Plane Functions ....................................................................................................................................................35 7.2.1 Packetization ...................................................................................................................................................36 7.2.2 Data Delivery ..................................................................................................................................................37 7.2.3 General Data Plane Sequence .........................................................................................................................37 7.2.4 Buffer Requirements ........................................................................................................................................39 7.2.5 Data Plane Sequence .......................................................................................................................................42

7.2.5.1 Broadcast command without response (bc) ......................................................................................................... 42 7.2.5.2 Broadcast command with response (bcr)............................................................................................................. 43 7.2.5.3 Addressed command without data transfer (ac) .................................................................................................. 43 7.2.5.4 Addressed command without data transfer with SD response type R1b (ac-r1b) ................................................ 44 7.2.5.5 Addressed data transfer command for out-data (adtc-out-data) ........................................................................... 44 7.2.5.6 Addressed data transfer command for in-data (adtc-in-data) .............................................................................. 45 7.2.5.7 Interrupt (int) ....................................................................................................................................................... 46 7.2.5.8 End of bus busy (ebusy) ...................................................................................................................................... 47

7.2.6 Intermediate Data Acknowledgement for Data Transfer .................................................................................47 7.2.7 Auto Command Flags ......................................................................................................................................48

7.2.7.1 acmd .................................................................................................................................................................... 49 7.2.7.2 stop ...................................................................................................................................................................... 49

7.2.8 Error Handling in Data Plane .........................................................................................................................50 7.2.8.1 Timeout Detection ............................................................................................................................................... 50


of 113

7.2.8.2 Packet Loss Detection ......................................................................................................................................... 51 7.3 WiGig MAC Requirements ..........................................................................................................................................53 7.4 WSD Device Discovery................................................................................................................................................53 7.5 WSD PAL Identification ..............................................................................................................................................54

8 WSD PAL-SAP Services ......................................................................................................................................................55

8.1 WSD PAL-SAP primitives ...........................................................................................................................................55 8.1.1 WSDPAL-DATA.request ..................................................................................................................................55 8.1.2 WSDPAL-DATA.indication .............................................................................................................................56 8.1.3 WSDPAL-DATA.response ...............................................................................................................................57 8.1.4 WSDPAL-DATA.confirmation .........................................................................................................................58 8.1.5 Command Parameter Set .................................................................................................................................59 8.1.6 Response Parameter Set ..................................................................................................................................61 8.1.7 Interrupt Parameter Set ...................................................................................................................................61 8.1.8 Data Set ...........................................................................................................................................................61 8.1.9 Data Acknowledgement Parameter Set ...........................................................................................................62

9 WSD PALME-SAP Services ................................................................................................................................................62

9.1 Session Start .................................................................................................................................................................62 9.1.1 PALME-WSD-SessionStart.request .................................................................................................................62 9.1.2 PALME-WSD-SessionStart.indication .............................................................................................................63 9.1.3 PALME-WSD-SessionStart.response ...............................................................................................................63 9.1.4 PALME-WSD-SessionStart.confirm ................................................................................................................64

9.2 Capability Exchange .....................................................................................................................................................64 9.2.1 PALME-WSD-CapabilityExchange.request ....................................................................................................64 9.2.2 PALME-WSD-CapabilityExchange.indication ................................................................................................65 9.2.3 PALME-WSD-CapabilityExchange.response ..................................................................................................65 9.2.4 PALME-WSD-CapabilityExchange.confirm ....................................................................................................67

9.3 Session Termination .....................................................................................................................................................68 9.3.1 PALME-WSD-SessionTermination.request .....................................................................................................68 9.3.2 PALME-WSD-SessionTermination.indication .................................................................................................68 9.3.3 PALME-WSD-SessionTermination.response ...................................................................................................68 9.3.4 PALME-WSD-SessionTermination.confirm ....................................................................................................69

9.4 Check Connection ........................................................................................................................................................69 9.4.1 PALME-WSD-CheckConnection.request ........................................................................................................69 9.4.2 PALME-WSD-CheckConnection.indication ....................................................................................................70 9.4.3 PALME-WSD-CheckConnection.response ......................................................................................................70 9.4.4 PALME-WSD-CheckConnection.confirm ........................................................................................................71

9.5 Get Bus handle .............................................................................................................................................................71 9.5.1 PALME-WSD-GetBusHandle.request .............................................................................................................71 9.5.2 PALME-WSD-GetBusHandle.indication .........................................................................................................71 9.5.3 PALME-WSD-GetBusHandle.response ...........................................................................................................72 9.5.4 PALME-WSD-GetBusHandle.confirm .............................................................................................................73

9.6 Release Bus handle .......................................................................................................................................................73 9.6.1 PALME-WSD-ReleaseBusHandle.request .......................................................................................................73 9.6.2 PALME-WSD-ReleaseBusHandle.indication ..................................................................................................74 9.6.3 PALME-WSD-ReleaseBusHandle.response ....................................................................................................75 9.6.4 PALME-WSD-ReleaseBusHandle.confirm ......................................................................................................75

9.7 Suspend Bus handle ......................................................................................................................................................76 9.7.1 PALME-WSD-SuspendBusHandle.request ......................................................................................................76 9.7.2 PALME-WSD-SuspendBusHandle.indication .................................................................................................77 9.7.3 PALME-WSD-SuspendBusHandle.response ...................................................................................................77


of 113

9.7.4 PALME-WSD-SuspendBusHandle.confirm .....................................................................................................78 9.8 Resume Bus handle ......................................................................................................................................................79

9.8.1 PALME-WSD-ResumeBusHandle.request .......................................................................................................79 9.8.2 PALME-WSD-ResumeBusHandle.indication ..................................................................................................79 9.8.3 PALME-WSD-ResumeBusHandle.response ....................................................................................................79 9.8.4 PALME-WSD-ResumeBusHandle.confirm ......................................................................................................80

9.9 Clear Bus ......................................................................................................................................................................81 9.9.1 PALME-WSD-ClearBus.request ......................................................................................................................81 9.9.2 PALME-WSD-ClearBus.indication .................................................................................................................82 9.9.3 PALME-WSD-ClearBus.response ...................................................................................................................82 9.9.4 PALME-WSD-ClearBus.confirm .....................................................................................................................83

9.10 Notification .................................................................................................................................................................83 9.10.1 PALME-WSD-Notification.request ................................................................................................................83 9.10.2 PALME-WSD-Notification.indication ...........................................................................................................85

10 Packet Formats ...................................................................................................................................................................87

10.1 WSD PAL Header ......................................................................................................................................................87 10.2 WSD PAL Control Plane Packet Formats ..................................................................................................................90

10.2.1 Session Start Request Packet Format .....................................................................................................90 10.2.2 Session Start Response Packet Format ...................................................................................................90 10.2.3 Capability Exchange Request Packet Format ...............................................................................................91 10.2.4 Capability Exchange Response Packet Format .............................................................................................92 10.2.5 Session Termination Request Packet Format ................................................................................................95 10.2.6 Session Termination Response Packet Format ..............................................................................................95 10.2.7 Check Connection Request Packet Format ...................................................................................................96 10.2.8 Check Connection Response Packet Format .................................................................................................96 10.2.9 Get Bus Handle Request Packet Format .......................................................................................................96 10.2.10 Get Bus Handle Response Packet Format ...................................................................................................97 10.2.11 Release Bus Handle Request Packet Format ...............................................................................................97 10.2.12 Release Bus Handle Response Packet Format ............................................................................................98 10.2.13 Suspend Bus Handle Request Packet Format ..............................................................................................98 10.2.14 Suspend Bus Handle Response Packet Format ...........................................................................................99 10.2.15 Resume Bus Handle Request Packet Format .............................................................................................100 10.2.16 Resume Bus Handle Response Packet Format ..........................................................................................100 10.2.17 Clear Bus Request Packet Format .............................................................................................................101 10.2.18 Clear Bus Response Packet Format ..........................................................................................................102 10.2.19 Notification Request Packet Format ..........................................................................................................102

10.3 WSD PAL Data Plane Packet Formats .....................................................................................................................104 10.3.1 WSD PAL Command Payload Unit .............................................................................................................104 10.3.2 WSD PAL Response Payload Unit ..............................................................................................................106 10.3.3 WSD PAL Data Acknowledgement Payload Unit ........................................................................................107 10.3.4 WSD PAL Data Payload Unit......................................................................................................................107 10.3.5 WSD PAL Interrupt Payload Unit ...............................................................................................................107 10.3.6 WSD PAL Check Status Payload Unit .........................................................................................................108 10.3.7 CMD Packet Format ...................................................................................................................................108 10.3.8 RES Packet Format .....................................................................................................................................108 10.3.9 DATA Packet Format ..................................................................................................................................109 10.3.10 CMD+DATA Packet Format .....................................................................................................................109 10.3.11 RES+DATA Packet Format .......................................................................................................................109 10.3.12 DATA-ACK Packet Format .......................................................................................................................110 10.3.13 RES+DATA-ACK Packet Format ..............................................................................................................110


of 113

10.3.14 INT Packet Format ....................................................................................................................................110 10.3.15 CHECK-STATUS Request Packet Format ................................................................................................111 10.3.16 CHECK-STATUS Response Packet Format ..............................................................................................111

11 CONSTANT DEFINITIONS .........................................................................................................................................112

Annex A – Valid Combinations of Various Types (Normative) ........................................................................................113


of 113

List of Figures

Figure 1: First example of Wireless SD Bus usage scenario ....................................................................................................14 Figure 2: Second example of Wireless SD Bus usage scenario ...............................................................................................15 Figure 3: Third example of Wireless SD Bus usage scenario ...................................................................................................15 Figure 4: Device model for WSD Host .....................................................................................................................................16 Figure 5: Device model for WSD Device .................................................................................................................................17 Figure 6: WSD layer management model .................................................................................................................................18 Figure 7: Overview of WSD PAL session management ...........................................................................................................19 Figure 8: WSD PAL session setup function..............................................................................................................................19 Figure 9: WSD PAL session start function ...............................................................................................................................20 Figure 10: WSD PAL capability exchange function .................................................................................................................21 Figure 11: WSD PAL session termination function ..................................................................................................................22 Figure 12: WSD PAL check connection function .....................................................................................................................23 Figure 13: WSD PAL session management state machine .......................................................................................................24 Figure 14: WSD PAL bus handle management model .............................................................................................................26 Figure 15: WSD PAL get bus handle function .........................................................................................................................26 Figure 16: WSD PAL release bus handle function ...................................................................................................................28 Figure 17: WSD PAL suspend bus handle function .................................................................................................................29 Figure 18: WSD PAL resume bus handle function ...................................................................................................................30 Figure 19: WSD PAL clear bus function ..................................................................................................................................31 Figure 20: WSD PAL bus handle management state machine Bus ..........................................................................................32 Figure 21: WSD PAL notification function ..............................................................................................................................34 Figure 22: Control plane error handling procedure at the WSD Host .......................................................................................35 Figure 23: Concept of WSD PAL data plane packet transitions ...............................................................................................36 Figure 24: An example of general data plane sequences ..........................................................................................................38 Figure 25: An example of check status sequence .....................................................................................................................38 Figure 26: receiving buffer space seen by the sending PAL .....................................................................................................40 Figure 27: An example of data buffer management ..................................................................................................................42 Figure 28: Sequence diagram of transaction type “bc” .............................................................................................................42 Figure 29: Sequence diagram of transaction type “bcr” ............................................................................................................43 Figure 30: Sequence diagram of transaction type “ac” .............................................................................................................43 Figure 31: Sequence diagram of transaction type “ac-r1b” ......................................................................................................44 Figure 32: Sequence diagram of transaction type “adtc-out-data” ............................................................................................45 Figure 33: Sequence diagram of transaction type “adtc-in-data” ..............................................................................................46 Figure 34: Sequence diagram of transaction type “int” ............................................................................................................47 Figure 35: Sequence diagram of transaction type “ebusy” .......................................................................................................47 Figure 36: An example sequence diagram of intermediate response [out-data transfer] ..........................................................48 Figure 37: An example sequence diagram of intermediate response [in-data transfer] ............................................................48 Figure 38: Sequence diagram of auto command flag: acmd .....................................................................................................49 Figure 39: Sequence diagram of auto command flag: stop .......................................................................................................49 Figure 40: Data plane timeout detection procedure at the WSD Host ......................................................................................51 Figure 41: The first example of PSN error detection ................................................................................................................52 Figure 42: The second example of PSN error detection ...........................................................................................................52 Figure 43: WSD packet encapsulation with LLC and SNAP headers ......................................................................................54 Figure 44: WSD PAL-SAP primitives ......................................................................................................................................55 Figure 45: Bitmap structure of Auto Command Flags ..............................................................................................................60 Figure 46: WSD PAL packet format .........................................................................................................................................87 Figure 47: WSD PAL packet header format .............................................................................................................................87 Figure 48: Session start request packet format..........................................................................................................................90


of 113

Figure 49: Session start response packet format .......................................................................................................................91 Figure 50: Capability exchange request packet format .............................................................................................................91 Figure 51: Capability exchange response packet format ...........................................................................................................92 Figure 52: Format of SDDevCapabilitySet subfield .................................................................................................................93 Figure 53: Format of DevInfo-xy field .....................................................................................................................................93 Figure 54: Session termination request packet format ..............................................................................................................95 Figure 55: Session termination response packet format ............................................................................................................95 Figure 56: Check connection request packet format .................................................................................................................96 Figure 57: Check connection response packet format...............................................................................................................96 Figure 58: Get bus handle request packet format ......................................................................................................................97 Figure 59: Get bus handle response packet format ...................................................................................................................97 Figure 60: Release bus handle request packet format ...............................................................................................................97 Figure 61: Release bus handle response packet format .............................................................................................................98 Figure 62: Suspend bus handle request packet format ..............................................................................................................99 Figure 63: Suspend bus handle response packet format..........................................................................................................100 Figure 64: Resume bus handle request packet format .............................................................................................................100 Figure 65: Resume bus handle response packet format ..........................................................................................................101 Figure 66: Clear bus request packet format ............................................................................................................................101 Figure 67: Clear bus response packet format ..........................................................................................................................102 Figure 68: Notification request packet format ........................................................................................................................102 Figure 69: WSD PAL Command Payload Unit format ...........................................................................................................104 Figure 70: Bitmap structure of Auto Command Flags field ....................................................................................................105 Figure 71: WSD PAL Response Payload Unit format ............................................................................................................106 Figure 72: WSD PAL Data Acknowledgement Payload Unit format .....................................................................................107 Figure 73: WSD PAL Data Payload Unit format ....................................................................................................................107 Figure 74: WSD PAL Interrupt Payload Unit format .............................................................................................................107 Figure 75: WSD PAL Check Status Payload Unit format ......................................................................................................108 Figure 76: CMD packet format ...............................................................................................................................................108 Figure 77: RES packet format .................................................................................................................................................109 Figure 78: DATA packet format .............................................................................................................................................109 Figure 79: CMD+DATA packet format ..................................................................................................................................109 Figure 80: RES +DATA packet format ..................................................................................................................................110 Figure 81: DATA-ACK packet format ...................................................................................................................................110 Figure 82: RES+DATA-ACK packet format ..........................................................................................................................110 Figure 83: INT packet format .................................................................................................................................................111 Figure 84: CHECK-STATUS request packet format ..............................................................................................................111 Figure 85: CHECK-STATUS response packet format ...........................................................................................................111


of 113

List of Tables

Table 1: List of auto command flags.........................................................................................................................................48 Table 2: Optional WiGig MAC features required by WSD ......................................................................................................53 Table 3: List of the ID values of the WiGig sub categories for the Secondary Device Type ...................................................53 Table 4: The primitive parameters of WSDPAL-DATA.request ..............................................................................................56 Table 5: Valid value of the ValidParamSetType ......................................................................................................................56 Table 6: The primitive parameters of WSDPAL-DATA.indication .........................................................................................57 Table 7: The primitive parameters of WSDPAL-DATA.response ...........................................................................................58 Table 8: Valid value of the ValidParamSetType ......................................................................................................................58 Table 9: The primitive parameters of WSDPAL-DATA.confirmation .....................................................................................59 Table 10: Valid value of ValidParamSetType ..........................................................................................................................59 Table 11: The elements of Command Parameter Set ................................................................................................................59 Table 12: Valid value of Transaction Type ...............................................................................................................................60 Table 13: Valid value of SD Response Type ............................................................................................................................60 Table 14: Description of Auto Command Flags .......................................................................................................................60 Table 15: The elements of Response Parameter Set .................................................................................................................61 Table 16: The elements of Interrupt Parameter Set ...................................................................................................................61 Table 17: Valid value of Event Type ........................................................................................................................................61 Table 18: The elements of Data Set ..........................................................................................................................................61 Table 19: The elements of Data Acknowledge Parameter Set ..................................................................................................62 Table 20: The primitive parameters of PALME-WSD-SessionStart.request ............................................................................62 Table 21: The primitive parameters of PALME-WSD-SessionStart.indication .......................................................................63 Table 22: The primitive parameters of PALME-WSD-SessionStart.response .........................................................................63 Table 23: The primitive parameters of PALME-WSD-SessionStart.confirm ...........................................................................64 Table 24: The primitive parameters of PALME-WSD-CapabilityExchange.request ...............................................................64 Table 25: The elements of SDHostCapabilitySet .....................................................................................................................65 Table 26: The primitive parameters of PALME-WSD-CapabilityExchange.indication ...........................................................65 Table 27: The primitive parameters of PALME-WSD-CapabilityExchange.response .............................................................66 Table 28: The elements of SDDevCapabilitySet ......................................................................................................................66 Table 29: The primitive parameters of PALME-WSD-CapabilityExchange.confirm ..............................................................67 Table 30: The primitive parameters of PALME-WSD-SessionTermination.request ................................................................68 Table 31: The primitive parameters of PALME-WSD-SessionTermination.indication ...........................................................68 Table 32: The primitive parameters of PALME-WSD-SessionTermination.response .............................................................69 Table 33: The primitive parameters of PALME-WSD-SessionTermination.confirm ...............................................................69 Table 34: The primitive parameters of PALME-WSD-CheckConnection.request ...................................................................70 Table 35: The primitive parameters of PALME-WSD-CheckConnection.indication ...............................................................70 Table 36: The primitive parameters of PALME-WSD-CheckConnection.response .................................................................70 Table 37: The primitive parameters of PALME-WSD-CheckConnection.confirm ..................................................................71 Table 38: The primitive parameters of PALME-WSD-GetBusHandle.request ........................................................................71 Table 39: The primitive parameters of PALME-WSD-GetBusHandle.indication ....................................................................72 Table 40: The primitive parameters of PALME-WSD-GetBusHandle.response ......................................................................72 Table 41: The primitive parameters of PALME-WSD-GetBusHandle.confirm .......................................................................73 Table 42: The primitive parameters of PALME-WSD-ReleaseBusHandle.request .................................................................73 Table 43: The primitive parameters of PALME-WSD-ReleaseBusHandle.indication .............................................................74 Table 44: The primitive parameters of PALME-WSD-ReleaseBusHandle.response ...............................................................75 Table 45: The primitive parameters of PALME-WSD-ReleaseBusHandle.confirm ................................................................75 Table 46: The primitive parameters of PALME-WSD-SuspendBusHandle.request ................................................................76 Table 47: The primitive parameters of PALME-WSD-SuspendBusHandle.indication ............................................................77 Table 48: The primitive parameters of PALME-WSD-SuspendBusHandle.response ..............................................................78 Table 49: The primitive parameters of PALME-WSD-SuspendBusHandle.confirm ...............................................................78


of 113

Table 50: The primitive parameters of PALME-WSD-ResumeBusHandle.request .................................................................79 Table 51: The primitive parameters of PALME-WSD-ResumeBusHandle.indication .............................................................79 Table 52: The primitive parameters of PALME-WSD-ResumeBusHandle.response ...............................................................80 Table 53: The primitive parameters of PALME-WSD-ResumeBusHandle.confirm ................................................................81 Table 54: The primitive parameters of PALME-WSD-ClearBus.request .................................................................................81 Table 55: The primitive parameters of PALME-WSD-ClearBus.indication ............................................................................82 Table 56: The primitive parameters of PALME-WSD-ClearBus.response ..............................................................................82 Table 57: The primitive parameters of PALME-WSD-ClearBus.confirm ................................................................................83 Table 58: The primitive parameters of PALME-WSD-Notification.request ............................................................................84 Table 59: EventMessage and EventParameter ..........................................................................................................................84 Table 60: The primitive parameters of PALME-WSD-Notification.indication ........................................................................86 Table 61: Valid value of the PV field .......................................................................................................................................87 Table 62: Valid value of the PType field ..................................................................................................................................87 Table 63: Valid value of the PDT field for control plane packet (PType = 0) ..........................................................................88 Table 64: Valid value of the PDT field for data plane packet (PType = 1) ...............................................................................89 Table 65: Valid value of the BusID field ..................................................................................................................................89 Table 66: Valid value of the DevID field ..................................................................................................................................89 Table 67: Valid value of the PSN field .....................................................................................................................................90 Table 68: Valid value of the PLen field ....................................................................................................................................90 Table 69: Valid value for the ResultCode field .........................................................................................................................91 Table 70: Valid value for the ReceivingBufferSize field ..........................................................................................................92 Table 71: Valid value for the ReceivingBufferSize field ..........................................................................................................92 Table 72: Valid value of the Bc field ........................................................................................................................................92 Table 73: Valid value of the Bcr field .......................................................................................................................................93 Table 74: Valid value for the ResultCode field .........................................................................................................................93 Table 75: Valid value for the BIType-x field ............................................................................................................................94 Table 76: Valid value for the DevAccessibilityInfo-x field ......................................................................................................94 Table 77: Valid value for the DT-xy field ................................................................................................................................94 Table 78: Valid value for the WPSL-xy field ...........................................................................................................................94 Table 79: Valid value for the ResultCode field .........................................................................................................................95 Table 80: Valid value for the ResultCode field .........................................................................................................................97 Table 81: Valid value for the ModificationFlag field ...............................................................................................................98 Table 82: Valid value for the ResultCode field .........................................................................................................................98 Table 83: Valid value for the ModificationFlag field ...............................................................................................................99 Table 84: Valid value for the LockFlag field ............................................................................................................................99 Table 85: Valid value for the ResultCode field .......................................................................................................................100 Table 86: Valid value for the ModificationFlag field .............................................................................................................101 Table 87: Valid value for the ResultCode field .......................................................................................................................101 Table 88: Valid value for the ResultCode field .......................................................................................................................102 Table 89: Valid value for the NotificationType field ..............................................................................................................103 Table 90: Valid value for the EventMessage field when NotificationType = 0b00 ................................................................103 Table 91: Valid value for the EventMessage field when NotificationType = 0b01 ................................................................104 Table 92: Valid value of the Transaction Type field...............................................................................................................104 Table 93: Valid value of the SD Response Type field ............................................................................................................105 Table 94: Mnemonic of the Auto Command Flags field.........................................................................................................105 Table 95: Valid value of the SD Response Type field ............................................................................................................106 Table 96: Valid value of the Event Type field ........................................................................................................................107 Table 97: WSD constants ........................................................................................................................................................112 Table 98: Valid combinations of various types .......................................................................................................................113


of 113

1 Overview

1.1 Scope The scope of this document standard is to define a WiGig SD Extension (WSD) Protocol Adaptation

Layer (PAL) for adapting SD Bus protocols [SD 3.01& SDIO 3.00] to the MAC layer. The WSD PAL

defined in this document standard includes an interface between the WSD PAL and the SME as well as

over-the-air data plane and control plane functions that are required for support of wired SD/SDIO

operation over a WiGig link. Note that the WSD PAL defined in this document standard is also targeted

to be able to operate over the IEEE 802.11 MAC layer [IEEE 802.11] as well.

1.2 Purpose The purpose of this document is to enable efficient transfer of SD/SDIO command, response, data and

special signaling (e.g., Interrupt) over a WiGig link.


of 113

2 Normative references The following referenced documents are indispensable for the application of this standard. For dated

references, only the edition cited applies. For undated references, the latest edition of the referenced

document (including any amendments or corrigenda) applies.

[IEEE 802] IEEE Std 802®-2001, March 2002

[IEEE 802.2] ANSI/IEEE Std 802.2, May 1998

[IEEE 802.11] IEEE Std 802.11™-2012, March 2012

[ISO 11578] ISO/IEC 11578: 1996 Information Technology -- Open Systems

Interconnection -- Remote Procedure Call (RPC), 1996

[RFC 4122] RFC 4122 A Universally Unique Identifier (UUID) URN Namespace, July

2005

[SD 3.01] SD Specification Part 1 Physical Layer Simplified Specification, Version 3.01,

May 2010

[SDIO 3.00] SD Specification Part E1 SDIO Simplified Specification, Version 3.00,

February 2011

[WGA MAC & PHY] WiGig MAC and PHY specification, Version 1.2, March 2013

[WGA MRD] WiGig Marketing Requirements Document, Version 1.0, June 2010

[WFA P2P] Wi-Fi Peer-to-Peer (P2P) Technical Specification, Version 1.2

3 Definitions For the purposes of this standard, the following terms and definitions apply. See normative references

for terms that are not defined in this clause.

Combo Card An SD Card comprising of a memory portion and an SDIO function

portion, which have the same functionalities as an SD Memory Card and an

SDIO Card, respectively.

SD Device An SD Memory Device or an SDIO Device.

SD Memory Device An SD Memory Card, or an embedded SD (eSD), or the memory portion of

a Combo Card.

WSD Device A user equipment implemented with WiGig MAC/PHY and capable of

exercising the device portion of WSD PAL.

WSD Host A user equipment implemented with WiGig MAC/PHY and capable of

exercising the host portion of WSD PAL.

SDIO Device An SDIO Card, or an embedded SDIO Device, or the SDIO function

portion of a Combo Card.

WiGig Combo Card A Combo Card in which SDIO function portion implements WiGig

MAC/PHY and the device functionality of WSD PAL.


of 113

4 Abbreviations and acronyms IEEE Institute of Electrical and Electronics Engineers

LLC Logical Link Control

MAC Medium Access Control (Layer)

MLME MAC Layer Management Entity

P2P Peer-to-Peer

PAL Protocol Adaptation Layer

PALME Protocol Adaptation Layer Management Entity

PDT Packet Payload Type

PDU Protocol Data Unit

PHY Physical (Layer)

PLME PHY Layer Management Entity

PSN Packet Sequence Number

SAP Service Access Point

SDIO SD Input/Output

SNAP Service Access Point

SME Station Management Entity

VPST Valid Parameter Set Type

WFA Wi-Fi Alliance

WiGig Wireless Gigabit

WGA Wireless Gigabit Alliance

WSD WiGig SD extension

5 Usage and Requirements In the process of developing the WSD PAL specification, two use cases defined in the WiGig

Marketing

Requirements Document [WGA MRD] are considered: “Peer to Peer Sync” and “Wireless IO”. In the

Peer to Peer Sync use case, a user equipment (i.e. camera, computer, mobile phone, etc.) uses SD Bus

protocols for SD Memory Device to transfer contents from/to a remote SD Memory Device in a peer

user equipment via a WiGig link. In the Wireless IO use case, a user equipment uses SD Bus protocols

for SDIO Device to control a remote SDIO Device in a peer user equipment via a WiGig link.

Based on the above two use cases, a usage scenario called by Wireless SD Bus is supported by the WSD

PAL specification. In this usage scenario, an SD Device is connected to a user equipment equipped with


of 113

WiGig MAC/PHY and attached to an SD Bus, which communicates directly with a peer user equipment

also equipped with WiGig MAC/PHY.

In a first example of Wireless SD Bus usage scenario as shown in Figure 1, a user equipment (e.g.,

computer) is equipped with host functionality of WSD PAL and acts as WSD Host. A peer user

equipment (e.g., mobile phone) is equipped with device functionality of WSD PAL and acts as

WSD Device.

The WSD Device can be equipped with multiple SD Buses to connect more than one SD Device to be

accessed remotely by the WSD Host via a WiGig link during a WSD PAL session.

The WSD Host can autonomously initiate a session start procedure to request establishment of a WSD

PAL session with the WSD Device. Alternatively, the WSD Device can request the WSD Host to

initiate the session start procedure.

During setup of a WSD PAL session, the WSD Host shall obtain the system information of the

WSD Device, e.g., number of accessible SD Devices, Device ID and device type for each of

accessible SD Devices, etc.

WSD Device

WSD Host (including SD Bus)

Figure 1: First example of Wireless SD Bus usage scenario

In a second example of Wireless SD Bus usage scenario as shown in Figure 2, either user equipment

(e.g., computer or mobile phone), can be equipped with both host and device functionalities of WSD

PAL, and can request to play a role of either WSD Host or WSD Device in a WSD PAL session.


of 113

Figure 2: Second example of Wireless SD Bus usage scenario

In a third example of Wireless SD Bus usage scenario as shown in Figure 3, a user equipment (e.g.,

computer) is equipped with host functionality of WSD PAL and acts as WSD Host. A peer user

equipment (e.g., mobile phone) is equipped with an SD Bus, and a WiGig Combo Card is connected to

the SD Bus of the peer user equipment.

The WSD Host can autonomously initiate a session start procedure to request establishment of a WSD

PAL session with the WiGig Combo Card. Alternatively, the WiGig Combo Card can request the WSD

Host to initiate the session start procedure. After establishing a WSD PAL session with the WiGig

Combo Card and obtaining bus handle of the SD Bus to which the WiGig Combo Card is attached, the

WSD Host is able to access memory portion of the WiGig Combo Card remotely.

WSD Host (includingUser equipment SD Bus)

Figure 3: Third example of Wireless SD Bus usage scenario

6 Architecture

6.1 Device Models The WSD PAL specification defines two entities, namely WSD Host and WSD Device. The device

models for these two entities are presented in this section.

6.1.1 Device Model for WSD Host

The device model for WSD Host is illustrated in Figure 4, which is comprised of the following building

blocks:


of 113

SD Logical

Host Controller

WSD Host PAL

WiGig MAC/PHY

Figure 4: Device model for WSD Host

• SD Device Driver

The SD Device drivers (i.e., SD Memory driver or SDIO driver) are software entities in control

of SD Devices and/or device interfaces. The SD Device drivers are out of scope of the WSD

PAL specification.

• SD Logical Host Controller

The SD logical host controller includes the functionalities of SD host controller, which can be

implemented in software and/or hardware. The SD logical host controller is out of scope of the

WSD PAL specification.

• WSD Host PAL

The WSD Host PAL entity is an intermediate functional block between the WiGig MAC/PHY

and the SD logical host controller. The WSD Host PAL is defined in the WSD PAL

specification.

• WiGig MAC/PHY

WiGig MAC/PHY includes the WiGig MAC and PHY functions [WGA MAC & PHY] and is

out of scope of the WSD PAL specification.

6.1.2 Device Model for WSD Device

The device model for WSD Device is illustrated in Figure 5, which is derived from the Wireless SD Bus

usage scenario described in Section 5 and is comprised of the following building blocks:

SD Interconnection

WSD Device PAL

SD Memory

Driver

SDIO

Driver

SD Memory

Device

SDIO

Device


of 113

WiGig MAC/PHY

Figure 5: Device model for WSD Device

• SD Interconnection

The SD interconnection includes downstream interface for each SD Bus to connect SD Device,

which also implements the functionality of SD host controller. The SD interconnection manages

arbitration between remote access initiated by the WSD Host and local access inside the WSD

Device to the same SD Bus. The SD interconnection is out of scope of the WSD PAL

specification.

• WSD Device PAL

The WSD Device PAL entity is an intermediate functional block between the WiGig MAC/PHY

and the SD interconnection. The WSD Device PAL is defined in the WSD PAL specification.

• WiGig MAC/PHY

WiGig MAC/PHY includes the WiGig MAC and PHY functions [WGA MAC & PHY] and is

out of scope of the WSD PAL specification.

6.2 Layer Management Model The WiGig layer management model is based on the IEEE 802.11 model specified in [IEEE 802.11] and

extends it by including a PAL Management Entity (PALME) which interacts with SME in the same

manner as MLME.

As shown in Figure 6, the WSD layer management model comprises of a WSD PAL layer and a WSD

PAL layer management entity (WSD PALME). The WSD PAL-SAP specifies the data services

provided by the WSD PAL layer to the higher layer. The WSD PALME-SAP specifies a management

interface through which the management functions are provided by the WSD PALME to the SME. Both

the WSD PAL-SAP and the WSD PALME-SAP are defined in primitives, which are further described

later. The HL-SAP is out of scope of this specification.


of 113

Figure 6: WSD layer management model

7 Functional Description

7.1 Control Plane Functions Control plane functions of the WSD PAL are categorized into session management, bus handle

management and notification functions. The session management functions are required for establishing,

maintaining and terminating a WSD PAL session, including session start, capability exchange, session

termination and check connection functions. The bus handle management functions are used by the

WSD Host to manage the handle of each available SD Bus inside the WSD Device, including get bus

handle, release bus handle, suspend bus handle, resume bus handle and clear bus functions. The

notification function allows the WSD Device to initiate asynchronous communication with the WSD

Host.

7.1.1 Session Management

This section describes how to manage a WSD PAL session between peer user equipment with WSD

PAL capability.

Figure 7 illustrates an overview of WSD PAL session management, which comprise of session setup and

session termination. During the period between session setup and session termination, the WSD Host


of 113

can perform data plane functions and bus handle management functions through the established WSD

PAL session.

Figure 7: Overview of WSD PAL session management

As shown in Figure 7, there may have a network initialization procedure prior to the setup of the WSD

PAL session, which may comprise of the following three steps:

1) The WiGig PHY and MAC link is started up between peer user equipment following the

mechanism specified in [WGA PHY & MAC].

2) Layer 2 device discovery is completed [WFA P2P] as a consequence of that the SME of either

user equipment becomes aware of presence of the peer user equipment in the network, and

initiates internal device procedures to load the WSD PAL.

3) The SME of the initiating user equipment, which intends to initiate a session setup request for

establishing a WSD PAL session, requests its MAC to initiate layer 2 security mechanisms,

including link level encryption, if not already in place.

7.1.1.1 Session setup

Figure 8 illustrates the WSD PAL session setup function, which is used to establish a WSD PAL

session. The WSD PAL session setup function comprises of the following two steps:

• The SME of the WSD Host initiates the session start procedure (see Section 7.1.1.1.1).

• The SME of the WSD Host initiates the capability exchange procedure (see Section 7.1.1.1.2).

Figure 8: WSD PAL session setup function

WSD PAL WSD PALME SME MLME MAC

Session Start

Capability Exchange

Session

Setup


of 113

7.1.1.1.1 Session start

Figure 9 illustrates the session start function, which is initiated by the WSD Host to establish a WSD

PAL session with the WSD Device and clear/initialize internal states of the WSD Device related to the

WSD PAL session, except states of SD Buses inside the WSD Device. As mentioned above, the WSD

Host can autonomously initiate the session start procedure based on the user or application demand.

Alternatively, the WSD Device can also request the WSD Host to initiate the session start procedure via

notification function.

Figure 9 illustrates the entities in the WSD Host and can be easily extended to include the counterpart

exchanges in the WSD Device.

As shown in Figure 9, the SME of the WSD Host instructs its WSD PALME by the PALME-WSD-

SessionStart.req primitive to send a session start request to the WSD Device. After receiving the session

start request, the SME of the WSD Device instructs its WSD PALME by the PALME-WSD-

SessionStart.res primitive to reply a session start response to the WSD Host, which indicates the result of

the requested session start (i.e., success, failure or executed).

The result would indicate “executed” if the WSD Device is in the state that the session start procedure

has already been executed.

(a) Session start without notification

(b) Session start with notification

Figure 9: WSD PAL session start function


of 113

7.1.1.1.2 Capability exchange

Figure 10 illustrates the capability exchange function, which is initiated by the WSD Host to exchange

their respective capability information related to the WSD PAL session between the WSD Host and the

WSD Device. The WSD Host can autonomously initiate the capability exchange procedure.

Alternatively, the WSD Device can also request the WSD Host to initiate the capability exchange

procedure via notification function.



As shown in Figure 10, the SME of the WSD Host instructs its WSD PALME by the PALME-

WSDCapabilityExchange.req primitive to send a capability exchange request to the WSD Device, which

includes the capability information of WSD Host related to the WSD PAL session, e.g., the buffer size

which is the total memory available for buffering PAL packets received from the WSD Device. After

receiving the capability exchange request, the SME of the WSD Device instructs its WSD PALME by

the PALME-WSD-CapabilityExchange.res primitive to reply a capability exchange response to the

WSD Host, which indicates the result of requested capability exchange (i.e., success or failure) as well

as the capability information of the WSD Device related to the WSD PAL session. The capability

information of the WSD Device comprises of the information about each of available SD Buses and

accessible SD Devices, e.g., Bus ID, Device ID, bus interface type and device type, etc.

(a) Capability exchange without notification

(b) Capability exchange with notification

Figure 10: WSD PAL capability exchange function

7.1.1.2 Session termination

Figure 11 illustrates the session termination function, which is used by the WSD Host to explicitly

disconnect the WSD PAL session in response to the user or application demand. The WSD Host can


of 113

autonomously initiate the session termination procedure. Alternatively, the WSD Device can also

request the WSD Host to initiate the session termination procedure via notification function.




WSDSessionTermination.req primitive to send a session termination request to the WSD Device. After

receiving the session termination request, the SME of the WSD Device instructs its WSD PALME by

the PALME-WSD-SessionTermination.res primitive to reply a session termination response to the WSD

Host, which indicates the result of the requested session termination (i.e., success, failure or executed).

The result would indicate “executed” if the WSD Device is in the state that the session termination

procedure has already been executed.

If the requested session termination is successful, the WSD PAL session is disconnected and all of

internal states of both WSD Host and WSD Device related to the WSD PAL session, including internal

states related to the bus handle management, are cleared.

(a) Session termination without notification

(b) Session termination with notification

Figure 11: WSD PAL session termination function

7.1.1.3 Check connection

Figure 12 illustrates the check connection function, which is used by the WSD Host to explicitly check

its PAL connectivity with the WSD Device.


WSDPAL[SessionTermination.req]

WSDPAL[SessionTermination.res]

PALME ‐ WSD ‐ SessionTermination.req

PALME ‐ WSD ‐ SessionTermination.conf


of 113

The WSD Host can autonomously initiate the check connection procedure. Alternatively, the WSD

Device can also request the WSD Host to initiate the check connection procedure via notification

function. Once the WSD Host receives the notification with check connection request from WSD

Device, it shall initiate the check connection procedure immediately.




WSDCheckConnection.req primitive to send a check connection request to the WSD Device. After

receiving the check connection request, the SME of the WSD Device instructs its WSD PALME by the

PALMEWSD-CheckConnection.res primitive to reply a check connection response to the WSD Host.

(a) Check connection without notification

(b) Check connection with notification

Figure 12: WSD PAL check connection function

7.1.1.4 Session management state machine

Peer user equipment involved in a WSD PAL session comply with the same session management state

machine, as shown in Figure 13. The session management state machine comprises of three states:


WSDPAL[CheckConnection.req]

WSDPAL[CheckConnection.res]

PALME ‐ WSD ‐ CheckConnection.req

PALME ‐ WSD ‐ CheckConnection.con f


of 113

Figure 13: WSD PAL session management state machine

No L2 Connection:

This state is entered on any of the following events:

• This is the default power-on-reset state.

• From any state when L2 connection is lost.

While in this state, peer user equipment wait for the L2 layer to establish a valid connection between

them.

This state exits when a valid (secure) L2 connection has been established between peer user equipment.

L2 Connected:


• From the No L2 Connection state after a valid (secure) L2 connection has been established

between peer user equipment.

• From the Session Established state after a session termination request sent by the WSD Host is

positively acknowledged by the WSD Device.

• From the Session Established state after PAL Connection Lost is detected.

While in this state, the WSD Host can autonomously initiate the session setup procedure, and the WSD

Device can send a session start request via the notification function for the purpose of requesting the

WSD Host to initiate the session setup procedure.

This state exits when the session setup procedure is successfully completed.

Session Established:


• From the L2 Connected state after successful completion of the session setup procedure which

includes the session start and capability exchange procedures.

While in this state, the WSD Host can perform data plane functions and bus handle management

functions through the established WSD PAL session.

While in this state, the WSD Host can autonomously initiate the session termination procedure based on

user or application demand. Alternatively, the WSD Device can request the WSD Host via notification

function to initiate the session termination procedure.

Power on Reset or L2 Connection lost

No L2 Connection

L2 Connected Session Established

L2 Connection Established

Notification SessionStart ( )

Session Setup

Session Termination PAL Connection Lost

Notification

Capability Exchange

Check Connection


of 113

While in this state, the WSD Host can autonomously initiate the check connection procedure.

Alternatively, the WSD Device can request the WSD Host via notification function to initiate the check

connection procedure.

While in this state, if any new SD Device is inserted into the WSD Device, it shall request the WSD

Host via notification function to initiate the capability exchange procedure.

While in this state, if any SD Device is removed from the WSD Device, it shall request the WSD Host

via notification function to obsolete the capability information related to the removed SD Device.

This state exits when a session termination request sent by the WSD Host is positively acknowledged by

the WSD Device.

This state exits when PAL Connection Lost is detected.

7.1.2 Bus Handle Management

The bus handle management functions comprise of get bus handle, release bus handle, suspend bus

handle, resume bus handle and clear bus, each of which can be initiated by the WSD Host on per-bus

basis through WSD PAL session.

7.1.2.1 Bus handle management model

Figure 14 illustrates the bus handle management model. As shown in Figure 14, both Bus ID and Device

ID can be used for uniquely identifying a particular SD Device attached to a specific SD Bus inside the

WSD Device.

Bus ID for each available SD Bus inside the WSD Device is assigned by the WSD Device and shall be

informed to the WSD Host as a result of the first Capability Exchange procedure. Bus ID shall not be

modified or removed until the Session Established state exits.

Device ID for each accessible SD Device inside the WSD Device is also assigned by the WSD Device

and shall be informed or updated to the WSD Host as a result of the Capability Exchange procedure.

Device ID shall be obsoleted when the corresponding SD Device is removed from the WSD Device

while in Session Established state.

Note that an SD Bus can be accessed by a single Host at a time. So while an SD Bus inside the WSD

Device is remotely accessed by the WSD Host, the WSD Device cannot access the same SD Bus locally.

The WSD Device manages arbitration between remote access initiated by the WSD Host and local

access inside the WSD Device to the same SD Bus using bus handle management.

When any of the bus handle management procedures targeted to the specific SD Bus is successfully

completed, all the SD Devices attached to that SD Bus, which have been exposed during capability

exchange procedure, shall be in “tran” state for SD Memory Device and shall be in “command” state for

SDIO Device, respectively.


of 113

Figure 14: WSD PAL bus handle management model

7.1.2.2 Get bus handle

Figure 15 illustrates the get bus handle function, which is initiated by the WSD Host to get the handle

for an SD Bus. The WSD Host can autonomously initiate the get bus handle procedure. Alternatively,

the WSD Device can also request the WSD Host to initiate the get bus handle procedure via notification

function.



(a) Get bus handle without notification

(b) Get bus handle with notification

Figure 15: WSD PAL get bus handle function


WSDGetBusHandle.req primitive to send a get bus handle request to the WSD Device. After receiving

Host CPU

Host Controller

Mem WiGig

Mem

UHS ‐ II

SD Bus

1

2

1 2 1

WSD Device

n

n Device ID

for the

SD Device

Bus ID

for the

SD Bus


of 113

the get bus handle request, the SME of the WSD Device instructs its WSD PALME by the PALME-

WSDGetBusHandle.res primitive to reply a get bus handle response to the WSD Host, which indicates

the result of the requested get bus handle (i.e., success, failure, busy or executed).

The result would indicate “success” if the target SD Bus is available, and then the WSD Host obtains the

access right of the target SD Bus to be used by data plane functions from the WSD Device. In this case,

the WSD Device activates the target SD Bus to be accessible from the WSD Host before sending the get

bus handle response to the WSD Host.

The result would indicate “busy” if the target SD Bus has been already used by the WSD Device locally

or by any other WSD Host. In this case, the WSD Device shall request the WSD Host to initiate get bus

handle procedure via notification function when the target SD Bus becomes available.

The result would indicate “executed” if the WSD Device is in the state that the get bus handle procedure

for the target SD Bus has already been executed.

The result would indicate “failure” if the target SD Bus is not available for any other reasons.

7.1.2.3 Release bus handle

Figure 16 illustrates the release bus handle function, which is initiated by the WSD Host to release the

bus handle for an SD Bus. The WSD Host can autonomously initiate the release bus handle procedure.

Alternatively, the WSD Device can also request the WSD Host to initiate the release bus handle

procedure via notification function. When the WSD Host receives the notification with release bus

handle request, it can still access the target SD Bus but should release the bus handle of the target SD

Bus as soon as possible.



(a) Release bus handle without notification


of 113

(b) Release bus handle with notification

Figure 16: WSD PAL release bus handle function


WSDReleaseBusHandle.req primitive to send a release bus handle request to the WSD Device, which

indicates whether the content of each SD Device under the target SD Bus has been changed before the

bus handle for target SD Bus transits to the Inactive State. After receiving the release bus handle request,

the SME of the WSD Device instructs its WSD PALME by the PALME-WSD-ReleaseBusHandle.res

primitive to reply a release bus handle response to the WSD Host, which indicates the result of the

requested release bus handle (i.e., success, failure or executed).

The result would indicate “executed” if the WSD Device is in the state that the release bus handle

procedure for the target SD Bus has already been executed.

If the result indicates “success”, then the WSD Host releases the access right of the target SD Bus which

is obtained by using the get bus handle function from the WSD Device.

If the requested release bus handle is successful, all of internal states of both WSD Host and WSD

Device related to the target SD Bus shall be cleared.

7.1.2.4 Suspend bus handle

Figure 17 illustrates the suspend bus handle function, which is initiated by the WSD Host to suspend the

handle of an SD Bus inside the WSD Device. The WSD Host can autonomously initiate the suspend bus

handle procedure. Alternatively, the WSD Device can request the WSD Host to initiate the suspend bus

handle procedure via notification function when it intends to access the same SD Bus locally. When the

WSD Host receive the notification with suspend bus handle request, it can still access the target SD Bus

but should suspend the bus handle of target SD Bus as soon as possible.




of 113

(a) Suspend bus handle without notification

(b) Suspend bus handle with notification

Figure 17: WSD PAL suspend bus handle function


WSDSuspendBusHandle.req primitive to send a suspend bus handle request to the WSD Device. The

suspend bus handle request not only indicates whether the content of each SD Device under the target

SD Bus has been changed before the bus handle for target SD Bus transits to the Inactive State, but also

indicates whether the target SD Bus can be accessed while the bus handle for the target SD Bus is in the

Inactive state. After receiving the suspend bus handle request, the SME of the WSD Device instructs its

WSD PALME by the PALME-WSD-SuspendBusHandle.res primitive to reply a suspend bus handle

response to the WSD Host, which indicates the result of the requested suspend bus handle (i.e., success,

failure or executed).

The result would indicate “executed” if the WSD Device is in the state that the suspend bus handle


If the result indicates “success”, then the WSD Host temporarily releases the access right of the target

SD Bus which is obtained by using the get bus handle function from the WSD Device.

7.1.2.5 Resume bus handle

Figure 18 illustrates the resume bus handle function, which is initiated by the WSD Host to resume the

handle of an SD Bus inside the WSD Device. The WSD Host can autonomously initiate the resume bus

handle procedure. Alternatively, the WSD Device can also request the WSD Host to initiate the resume

bus handle procedure via notification function.


WSDPAL[SuspendBusHandle.req]

WSDPAL[SuspendBusHandle.res]

PALME ‐ WSD ‐ SuspendBusHandle.req

PALME ‐ WSD ‐ SuspendBusHandle.conf


of 113



(a) Resume bus handle without notification

(b) Resume bus handle with notification

Figure 18: WSD PAL resume bus handle function

As shown in Figure 18, the SME of WSD Host instructs its WSD PALME by the PALME-

WSDResumeBusHandle.req primitive to send a resume bus handle request to the WSD Device. After

receiving the resume bus handle request, the SME of WSD Device instructs its WSD PALME by the

PALME-WSD-ResumeBusHandle.res primitive to reply a resume bus handle response to the WSD

Host, which indicates whether the content of each SD Memory Device under the target SD Bus has been

changed before the bus handle for target SD Bus transits to the Active State as well as the result of the

requested resume bus handle (i.e., success, failure, busy or executed).

The result would indicate “success” if the target SD Bus is available. In this case, the WSD Host gets

back the access right of the target SD Bus which is temporarily released by using the suspend bus handle

function.

The result would indicate “busy” if the target SD Bus has been already used by WSD Device locally or

by any other WSD Host. In this case, the WSD Device shall request WSD Host to initiate resume bus

handle procedure via notification function when the target SD Bus becomes available.

The result would indicate “executed” if the WSD Device is in the state that the resume bus handle


The result would indicate “failure” if the target SD Bus is not available for any other reasons.


of 113

If the received resume bus handle response shows that the result of the requested resume bus handle is

successful and the content of SD Memory Device has been changed, the WSD Host shall update file

system cache of the SD Memory Device.

7.1.2.6 Clear Bus

Figure 19 illustrates the clear bus function, which is initiated by the WSD Host to cancel the current data

plane transaction related to the target SD Bus inside the WSD Device and clear the relevant buffer and

internal state parameters of data plane. The WSD Host can autonomously initiate the clear bus

procedure. Alternatively, the WSD Device can request the WSD Host to initiate the clear bus procedure

via notification function. The clear bus function shall be activated when any data plane error is detected

by either WSD Host or WSD Device, as specified in Section 7.2.8.



(a) Clear bus without notification

(b) Clear bus with notification

Figure 19: WSD PAL clear bus function

As shown in Figure 19, the SME of WSD Host instructs its WSD PALME by the PALME-

WSDClearBus.req primitive to send a clear bus request to the WSD Device. After receiving the clear

bus request, the WSD device shall stop and cancel SD command sequence between SD Local Host

Controller and the target SD Device. The SME of the WSD Device also instructs its WSD PALME by

the PALME-WSD-ClearBus.res primitive to reply a clear bus response to the WSD Host, which

indicates the result of the requested clear bus (i.e., success or failure).


of 113

7.1.2.7 Bus handle management state machine

A bus handle management state machine shall be maintained for each of the available SD Bus inside the

WSD Device. The bus handle management state machine for an SD Bus is illustrated in Figure 20,

which comprises of three states:

Figure 20: WSD PAL bus handle management state machine Bus

Handle Not Assigned:


• This is the default state after the session setup procedure is successfully completed.

• After the release bus handle procedure is successfully completed from the Bus Handle Assigned

state.

• After the session termination procedure is successfully completed so that the WSD PAL session

transits from the Session Established state to the L2 Connected state.

• After PAL Connection Lost is detected so that the WSD PAL session transits from the Session

Established state to the L2 Connected state.

While in this state, the WSD Host can autonomously initiate the get bus handle procedure to obtain the

access right of a target SD Bus from the WSD Device. The WSD Device can also request the WSD Host

to initiate the get bus handle procedure via notification function.

While in this state, the target SD Bus may be accessed by the WSD Device locally, or in power saving

state.

This state exits when the get bus handle request sent by the WSD Host is positively acknowledged by

the WSD Device.

Bus Handle Active:


• From the Bus Handle Not Assigned state after the get bus handle procedure is successfully

completed.

Bus Handle Not Assigned

Bus Handle Active

Bus Handle Inactive

Get Bus Handle

Release Bus Handle

Suspend Bus Handle

Resume Bus Handle

Bus Handle Assigned

Clear Bus


of 113

• From the Bus Handle Inactive state after the resume bus handle procedure is successfully

completed.

While in this state, the WSD Host can autonomously initiate the release bus handle procedure to give up

the access right of the target SD Bus. Alternatively, the WSD Device can request the WSD Host via

notification function to initiate the release bus handle procedure.

While in this state, the WSD Host can autonomously initiate the suspend bus handle procedure to

temporarily release the access right of the target SD Bus. Alternatively, the WSD Device can request the

WSD Host via notification function to initiate the suspend bus handle procedure.

While in this state, if any a data plane transaction related to the target SD Bus is terminated abnormally,

the WSD Host shall autonomously initiate the clear bus procedure to request the WSD Device to clear

the buffer and the internal state parameters of data plane for all data plane transactions related to the

target SD Bus. Alternatively, the WSD Device can request the WSD Host via notification function to

initiate the clear bus procedure.

While in this state, the WSD Host can access the SD Device in the WSD Device through WSD PAL data

plane service.

This state exits when either the suspend bus handle request or the release bus handle request sent by the

WSD Host is positively acknowledged by the WSD Device.

Bus Handle Inactive:


• From the Bus Handle Active state after the suspend bus handle procedure is successfully

completed.

While in this state, the WSD Host can autonomously initiate the resume bus handle procedure to get

back the access right of the target SD Bus. Alternatively, the WSD Device can request the WSD Host

via notification function to initiate the resume bus handle procedure.

While in this state, the WSD Host can autonomously initiate the release bus handle procedure to give up

the access right of the target SD Bus. Alternatively, the WSD Device can request the WSD Host via

notification function to initiate the release bus handle procedure.

While in this state, the WSD Host cannot send any WSD PAL data plane packet to the SD Device in the

WSD Device. The WSD Device also cannot send any WSD PAL data plane packet to the WSD Host

except interrupt packet.

While in this state, the target SD Bus may be accessed by WSD Device locally, or in power saving

mode. However, if the “LockFlag” in the suspend bus handle request is set, the target SD Bus shall not

be accessed by the WSD Device locally or by any other WSD Host.

This state exits when either the resume bus handle request or the release bus handle request sent by the

WSD Host is positively acknowledged by the WSD Device.

7.1.3 Notification

Figure 21 illustrates the notification function, which is the only function initiated by the WSD Device to

provide in-band communication of asynchronous events (e.g., session start request, suspend bus handle

request, resume bus handle request, capability exchange request) from the WSD Device to the WSD


of 113

Host. The WSD Device can initiate the notification function when it is in the state of L2 Connected or

Session Established.

Figure 21 illustrates the entities in the WSD Device and can be easily extended to include the

counterpart exchanges in the WSD Host.

Figure 21: WSD PAL notification function

As shown in Figure 21, the SME of WSD Device instructs its WSD PALME by the PALME-WSD-

Notification.req primitive to send a notification request to the WSD Host. Other than the other control

plane functions, the WSD Host needs not to send a notification response to the WSD Device. Instead the

WSD Device can determine whether the notification request is successfully admitted to a transmit queue

via the MAC-SAP primitive.

7.1.4 Error Handling in Control Plane

This specification only specifies the control plane error handling procedure at the WSD Host.

The WSD Host PAL manages a control plane timer for the period of CNTRL_PLANE_TIMEOUT.

When the WSD Host PAL initiates any control plane request, the control plane timer shall be started. It

shall be stopped when the WSD Host PAL receives the corresponding control plane response. If the

WSD Host PAL cannot receive the corresponding control plane response before the control plane timer

expired, the WSD Host shall initiate the error handling procedure.

The error handling procedure at the WSD Host is shown in Figure 22, which comprises of the following

steps:

1) The variant Count is initialized to be zero;

2) The WSD Host sends any control plane request to the WSD Device and restarts the control plane

timer;

3) If the WSD Host PAL receives the corresponding control plane response before the control plane

timer expires, it shall determine that PAL connection is still alive, and stop the timer and the

procedure. Otherwise, stop the timer and go to step 4;

4) The WSD Host PAL shall indicate “timeout” to the SME in the result code of PALME-

WSDAction.confirm primitive;

5) The variant Count is incremented by one;

6) If variant Count is equal to CNTRL_PLANE_RETRYNUM, the WSD Host PAL shall determine

that it falls into PAL Connection Lost, and stop the procedure. Otherwise, go back to step 2.


of 113

Figure 22: Control plane error handling procedure at the WSD Host

7.2 Data Plane Functions Data plane functions of the WSD PAL are enabled during Bus Handle Active state of WSD PAL bus

handle management state machine. SD commands, SD responses, SD data, interrupt, data

acknowledgement and check status are transferred using the data plane functions. Busses that are

attached to WSD Device are either SD Bus or UHS-II Bus. WSD PAL data plane function carries only

essential information for both SD Bus and UHS-II Bus in neutral way to execute SD commands and data

transfers. WSD PAL data plane defines its native packet format. SD Interconnection in the WSD Device

encapsulates/interprets native SD packets according to the corresponding attached SD Bus. Native

packet format for SD Bus is “Command Format Token”, and for UHS-II Bus is “UHS-II Packet”.

Figure 23 depicts a concept of WSD PAL data plane packet transitions.

For SD Devices attached to SD Bus, SD Interconnection in the WSD Device forms native SD Bus

Command Format Token from WSD PAL data plane packet for outgoing SD commands and SD data.

SD Interconnection in the WSD Device interprets SD Bus Command Format Token and forms WSD

PAL data plane packet for incoming SD responses and SD data.


of 113

For SD Devices attached to UHS-II Bus, SD Interconnection in the WSD Device forms native UHS-II

Packet format from WSD PAL data plane packet for outgoing SD commands and SD data. SD

Interconnection in the WSD Device interprets UHS-II Packet format and forms WSD PAL data plane

packet for incoming SD responses and SD data.

Figure 23: Concept of WSD PAL data plane packet transitions

7.2.1 Packetization

A WSD PAL packet consists of a WSD PAL header and its payload. The WSD PAL header related to

data plane has various fields listed as follows:

• WSD PAL packet length: entire size of the WSD PAL packet in byte

• Bus ID: identifier of target SD Bus, acquired by the control plane capability exchange procedure

• Device ID: identifier of target SD Device, acquired by the control plane capability exchange

procedure

• Packet Sequence Number: a sequence number incremented by one for each packet per SD Bus

with same direction

• Payload Data Type: type of WSD PAL packet payload format. For data plane, this field takes

either “CMD”, “CMD+DATA”, “RES”, “RES+DATA”, “DATA”, “RES+DATA-ACK”,

“DATA-ACK”, “INT” or “CHECK-STATUS”.

• etc …

WSD PAL payload may contain SD command, SD response, SD data, interrupt, data acknowledgement

and check status. As abovementioned in the description of Payload Data Type field, WSD PAL payload

takes either of 9 combinations:

• SD command (“CMD”)

• SD command and SD data (“CMD+DATA”)

• SD response (“RES”)

• SD response and SD data (“RES+DATA”)

• SD data (“DATA”)

• SD response and data acknowledgement (“RES+DATA-ACK”)

• Data acknowledgement (“DATA-ACK”)

• Interrupt (“INT”)

• Check status (“CHECK-STATUS”) SD commands are categorized into 4 types:

• Broadcast command without response (“bc”)

WSD Host

WSD Host PAL

WSD Device

WSD Device PAL

WSD PAL session

Re q uest

Res p onse

WSD PAL data

SD Interconnection

SD Host Controller

SD Host Controller

UHS ‐ II Bus UHS ‐ II Packet

CMD RES

CMD

RES

SD Bus Command Format Token


of 113

• Broadcast command with response (“bcr”)

• Addressed (point-to-point) command without data transfer (“ac”)

• Addressed (point-to-point) data transfer command (“adtc”)

And, SD responses are categorized into 7 types, R1, R1b, R2, R4, R5, R6 and R7. WSD PAL supports

all of SD commands and SD responses listed above. WSD PAL packet format is specified in Section 10.

7.2.2 Data Delivery

The WSD PAL packets are handled through the MAC-SAP to the MAC layer for transmission, only

when in the Bus Handle Active state of the WSD PAL bus handle management state machine. These

packets shall follow the requirements in [WGA MAC & PHY]. Each WSD PAL packet transferred

through the MAC-SAP is intended for a single peer PAL entity. WSD PAL requires in-order and reliable

delivery of packets by the MAC layer.

7.2.3 General Data Plane Sequence

To initiate a WSD PAL data plane transaction, the WSD Host PAL sends SD command to the WSD

Device PAL as a request. The WSD Device PAL issues the SD command to the SD Device and receives

corresponding SD response from the SD Device. Then the WSD Device PAL returns SD response as a

response to the WSD Host PAL.

In case of out-data transfer, the WSD Host PAL sends SD data as request(s) to the WSD Device PAL

and the WSD Device PAL sends response(s) to the WSD Host PAL. In case of in-data transfer, the

WSD Device PAL sends SD data as request(s) to the WSD Host PAL and the WSD Host PAL sends

response(s) to the WSD Device PAL.

When SD data is transferred, it is typical that SD data may be divided and encapsulated into several

WSD PAL packets.

WSD PAL uses Packet Sequence Number (PSN) to identify a series of packets transmitted with data

plane transactions. PSN is a number that is assigned to each WSD PAL packet transmitted with the same

direction for the same SD Bus. Just after a get bus handle procedure or a clear bus procedure is

successfully completed, the PSN value shall be initialized to zero (0). The PSN value shall be

incremented by one for each new packet excluding WSD native packets (i.e., DATA-ACK,

CHECKSTATUS and INT). The PSN value shall be reset to 0x000 after reaching 0x7FF. The PSN field

in the header of WSD native packets is invalid and is always set to 0. An example of general data plane

sequences showing the use of PSN is illustrated in Figure 24.

The WSD Host PAL shall maintain a data plane timer for the period of CHECK_STATUS_PERIOD to

detect any transmission error related to data plane between the WSD Host PAL and the WSD Device

PAL. The data plane timer shall be activated when the WSD Host PAL initiates a first data plane

transaction with the WSD Device PAL. The data plane timer shall be reset and restarted when the WSD

Host PAL dispatches or receives any data plane packet. Once the data plane timer expires, the WSD

Host PAL shall send a check status request to the WSD Device PAL.

The check status request contains a NextPSN field, which specifies the next incremented value of PSN

at the WSD Host PAL. The WSD Device PAL can determine whether there was a packet loss according

to the NextPSN field of the received check status request.


of 113

Once the WSD Device PAL receives the check status request, it shall immediately return a check status

response. The check status response packet also contains the NextPSN field, which specifies the next

incremented value of PSN at the WSD Device PAL. The WSD Host PAL can determine whether there

was a packet loss according to the NextPSN field of the received check status response.

Figure 24: An example of general data plane sequences

Figure 25: An example of check status sequence


of 113

Both check status request and check status response further include the Remaining Size field, which

specifies the size of remaining SD data that needs to be acknowledged by the receiving PAL in adtc-type

transactions.

Note that the check status sequence exchanges the internal state of the WSD Host PAL and the WSD

Device PAL and is dedicated to communication between the WSD Host PAL and the WSD Device PAL

so that higher layer and SD interconnection are not involved. An example of check status sequence is

illustrated in Figure 25.

The error detection and handling in data plane is further detailed in Section 7.2.8.

Note that the WSD Host PAL shall not manage more than one data plane transactions for an SD Bus at

the same time. In other words, the WSD Host PAL cannot initiate a new data plane transaction for the

same SD Bus until the current data plane transaction is completed.

7.2.4 Buffer Requirements

The WSD Host PAL and the WSD Device PAL shall provide enough memory for PAL operations to

meet the performance requirements. The required buffer size is implementation specific.

Both WSD Host PAL and WSD Device PAL shall reserve data buffer to hold received SD data which is

contained in WSD packet with the PDT field in its header of either “CMD+DATA”, “RES+DATA” or

“DATA”. The size of receiving data buffer (i.e., Receiving Buffer Size) that is available for receiving

SD data shall be exposed to the peer PAL at the capability exchange as specified in Section 7.1.1.1.2.

The Receiving Buffer Size is determined by taking only SD data into account. The WSD Host PAL and

the WSD Device PAL shall manage availability of the receiving data buffer at the peer PAL for SD data

transfer during the data plane transaction.

The type of SD commands involving SD data transfer is “adtc”. A WSD PAL transaction that is

accompanied with SD data payload is called adtc-type transaction. In this WSD PAL specification there

are two types of adtc-type transaction as defined in Section 8.1.5 and 10.3.1.

In an adtc-type transaction, the WSD Host PAL can transport an SD command with its Total Data

Length exceeding the receiving data buffer size of the peer PAL. The sending PAL (i.e., either WSD

Host PAL or WSD Device PAL which sends the WSD PAL packet including SD data) shall track the

availability of the receiving data buffer in the receiving PAL so that the receiving data buffer in the

receiving PAL would not overflow.

The sending PAL manages those two variables, i.e., CurrentPos and RemainingSize. The variable

CurrentPos is a total size (in byte) of SD data included in WSD PAL packets which have been sent by

the sending PAL to the receiving PAL. The variable CurrentPos is set to zero at the beginning of the

adtc-type transaction. When the sending PAL initiates a request including SD data, the size (in byte) of

the SD data is added to the variable CurrentPos. The variable RemainingSize is remaining size (in byte)

of SD data that needs to be acknowledged by the receiving PAL. At the beginning of the adtc-type

transaction, the variable RemainingSize shall be set to be the same as the Total Data Length which is

included in the WSD PAL packet. When the sending PAL receives a response including DATA-ACK

through MAC-SAP, then the variable RemainingSize shall be set to the value indicated by the

Remaining Size field of DATA-ACK.

For the sending PAL, the receiving data buffer space (PendingBufSpace) in use and available space (in

byte) of data buffer (AvailableBuffSpace) at the receiving PAL can be calculated as follows:


of 113

PendingBufSpace = CurrentPos – (Total Data Length – RemainingSize)

AvailableBufSpace = Receiving Buffer Size – PendingBufSpace

The sending PAL is allowed to send the WSD PAL packet(s) including SD data up to the size of

AvailableBufSpace. The size of SD data carried in a single WSD PAL packet shall be fixed to 7680

octets as long as the size of remaining SD data to be transferred exceeds 7680 octets. When the sending

PAL gets indication from the local MAC that the packets have been successfully admitted into the

transmit queue, it can clear those packets from its sending buffer.

Figure 26 depicts the relationship between those variables.

Figure 26: receiving buffer space seen by the sending PAL

The receiving PAL shall track the space availability of its own receiving data buffer and shall respond to

the sending PAL for the progress of the SD data transfer using DATA-ACK.

The receiving PAL shall manage a variable, i.e., RemainingSize. The variable RemainingSize is

remaining size (in byte) of SD data that needs to be processed at the receiving PAL. At the beginning of

the adtc-type transaction, the variable RemainingSize shall be set to be the same as the Total Data

Length which is transferred along with adtc type of SD command in the WSD PAL packet. When the

receiving PAL gets the response from the higher layer through WSD PAL-SAP indicating the SD data

which has been processed by the higher layer, then the receiving PAL clears the processed SD data from

the receiving data buffer and the variable RemainingSize is subtracted by the Processed Data Size as

specified in Section 8.1.9. Then the receiving PAL sets the Remaining Size field of DATA-ACK

according to the current value of the variable RemainingSize and sends the DATA-ACK to the sending

PAL.

Figure 27 depicts an example of sending SD data from WSD Host PAL to WSD Device PAL.

1) When the WSD Host PAL initiates an adtc-out-data transaction by sending CMD+DATA[0], it

sets RemainingSize to Total Data Length. The WSD Host PAL clears DATA[0] from sending

buffer and sets CurrentPos to the size of DATA[0] after DATA[0] is successfully admitted to a

transmit queue. On the other hand, the WSD Device PAL initializes its RemainingSize to Total

Data Length of the receiving packet.

2) If the Receiving Buffer Size of the WSD Device PAL equals to the size of DATA[0:7], the

WSD Host PAL determines that the receiving buffer of the WSD Device PAL becomes full

(i.e., AvailableBufSize becomes zero) just after it sends DATA[7] without receiving

DATAACK from the WSD Device PAL. Since then, the WSD Host PAL waits for a DATA-

ACK sent by the WSD Device PAL.

3) DATA[0:3] are cleared from receiving data buffer in response to the confirmation from the

higher layer of WSD Device. RemainingSize is subtracted by the size of DATA[0:3] and

CurrentPos

RemainingSize

AvailableBufSpace PendingBufSpace

Receivin g Buffer Size

Total Data Length


of 113

transmitted with the DATA-ACK to the WSD Host PAL. The WSD Host PAL reflects the

RemainingSize of the received DATA-ACK to its own RemainingSize and determines that the

receiving buffer of the WSD Device PAL become available for transmission again.

4) After sending the last data (i.e., DATA[9]), the WSD Host PAL waits for the last DATA-ACK

which RemainingSize is zero.

5) The WSD Host PAL completes the adtc-out-data transaction when it receives the last

DATAACK.

* (X) denotes the size of DATA[0:X].


of 113

Figure 27: An example of data buffer management

7.2.5 Data Plane Sequence

WSD PAL supports 8 types of data-plane transactions as follows:

• Broadcast command without response (“bc”)

• Broadcast command with response (“bcr”)

• Addressed command without data transfer (“ac”)

• Addressed command without data transfer with SD response type R1b (“ac-r1b”)

• Addressed data transfer command for out-data (“adtc-out-data”)

• Addressed data transfer command for in-data (“adtc-in-data”)

• Interrupt (“int”)

• End of bus busy (”ebusy”).

The WSD PAL data plane sequences are categorized according to transaction types. Sequence for each

type of transaction type is specified in the following subsections. Basically, WSD PAL shall keep

transmission order of SD Bus/UHS-II Bus protocol for both WSD Host and WSD Device, respectively.

7.2.5.1 Broadcast command without response (bc)

In terms of transaction type “bc”, the WSD Host PAL sends an SD command and its argument as a

request. The SD command is distributed to the target SD Device. The WSD Device PAL shall return a

response, right after SD command is executed by the Local SD Host Controller, since SD response is not

expected from the SD Device. The response shall indicate whether the SD command is successfully

executed or not.

Figure 28: Sequence diagram of transaction type “bc”

From the perspective of WSD Device PAL, this type of transaction completes when the packet carrying

the response is successfully admitted to a MAC transmit queue. From the perspective of WSD Host

PAL, this type of transaction completes when the packet carrying the response is successfully received.

The transaction type “bc” is optionally supported by the WSD Device PAL. If the WSD Device PAL

does not support this transaction type “bc”, the WSD Host PAL shall not initiate this type of transaction.


of 113

7.2.5.2 Broadcast command with response (bcr)

In terms of transaction type “bcr”, the WSD Host PAL sends an SD command and its argument as a

request. The SD command is distributed to the target SD Device. WSD Device PAL returns a response

including SD response from the SD Device.




The transaction type “bcr” is optionally supported by the WSD Device PAL. If the WSD Device PAL

does not support the transaction type “bcr”, the WSD Host PAL shall not initiate this type of transaction.

Figure 29: Sequence diagram of transaction type “bcr”

7.2.5.3 Addressed command without data transfer (ac)

In terms of transaction type “ac”, the WSD Host PAL sends an SD command and its argument as a

request. The SD command is distributed to the target SD Device. The WSD Device PAL returns a

response including SD response from the SD Device.




Figure 30: Sequence diagram of transaction type “ac”


of 113

7.2.5.4 Addressed command without data transfer with SD response type R1b (ac-r1b)

In terms of transaction type “ac-r1b”, the WSD Host PAL sends an SD command and its argument as a

request. The SD command is distributed to a target SD Device, which responds with a SD response. The

SD Interconnection shall signal end of bus busy (EBUSY) to WSD Device PAL, after the busy signal on

the SD Device is terminated. The WSD Device PAL returns a response including SD response from the

SD Device.

In this transaction type, the WSD Device PAL may receive the next request with a new SD command

during bus busy. In this case, the WSD Device PAL shall wait for EBUSY SAP request before issuing

the new SD command to the target SD Device.




Figure 31: Sequence diagram of transaction type “ac-r1b”

7.2.5.5 Addressed data transfer command for out-data (adtc-out-data)

In terms of transaction type “adtc-out-data”, the WSD Host PAL sends an SD command and its

argument as well as an SD data as a request. The SD data may be divided and carried in several requests

with appropriate packet sequence numbers. The SD command is sent to the target SD Device, which

responds with an SD response. Then the SD data is transferred to SD Device. The SD Interconnection

shall signal end of bus busy (EBUSY) to WSD Device PAL, after the busy signal on the SD Device is

terminated. The WSD Device PAL returns responses including SD response from the SD Device and/or

data acknowledgement. The first response from the WSD Device PAL shall include both SD response

and data acknowledgement. And the subsequent responses shall include data acknowledgement only.


of 113

Figure 32: Sequence diagram of transaction type “adtc-out-data”




From the perspective of WSD Device PAL, this type of transaction completes when the last packet

carrying the data acknowledgement is successfully admitted to a MAC transmit queue. From the

perspective of WSD Host PAL, this type of transaction completes when the last packet carrying the data

acknowledgement is successfully received.

7.2.5.6 Addressed data transfer command for in-data (adtc-in-data)

In terms of transaction type “adtc-in-data”, the WSD Host PAL sends an SD command and its argument

as a request. The SD command is sent to the target SD Device, which responds with an SD response,

followed by SD data. The SD Interconnection shall signal end of bus busy (EBUSY) to WSD Device

PAL, after the busy signal on the SD Device is terminated. The SD data may be divided and carried in

several requests with appropriate packet sequence numbers. The WSD Device PAL shall send a first

request to carry both SD data and SD response. And the following requests shall carry SD data only. The

WSD Host PAL shall return a response carrying data acknowledgement, after the incoming SD data is

successfully processed.


of 113

Figure 33: Sequence diagram of transaction type “adtc-in-data”




From the perspective of WSD Host PAL, this type of transaction completes when the last packet

carrying the data acknowledgement is successfully admitted to a MAC transmit queue. From the

perspective of WSD Device PAL, this type of transaction completes when the last packet carrying the

data acknowledgement is successfully received.

7.2.5.7 Interrupt (int)

The transaction type “int” is defined for support of various data plane interrupts including SDIO

interrupts and other data plane asynchronous event notifications (e.g. errors) from the WSD Device to

the WSD Host. In terms of this transaction type, the WSD Device PAL sends an interrupt as a request.

Then the WSD Host PAL receives the interrupt as an indication. The WSD Host needs not to send a

response to the WSD Device.


the interrupt is successfully admitted to a MAC transmit queue. From the perspective of WSD Host

PAL, this type of transaction completes when the packet carrying the interrupt is successfully received.


of 113

Figure 34: Sequence diagram of transaction type “int”

7.2.5.8 End of bus busy (ebusy)

The transaction type “ebusy” is defined for notifying bus busy ends by SD Interconnection to the WSD

Device PAL in the WSD Device. In terms of this transaction type, the WSD Device PAL shall not send

any WSD packet corresponding to this transaction type. This transaction type is used by WSD Device

PAL only as a trigger to issue a pending SD command received during bus busy.

This type of transaction completes when the EBUSY SAP request is successfully asserted in WSD

Device PAL.

Host PAL Host MAC Device MAC

SD Device

Figure 35: Sequence diagram of transaction type “ebusy”

7.2.6 Intermediate Data Acknowledgement for Data Transfer

The length of SD data may be larger than the amount of receiving data buffer in the receiving PAL The

receiving PAL shall respond by sending DATA-ACK which indicating the SD data have been

processed. The DATA-ACK has a parameter that indicating the size of SD data that has been processed

properly. The receiving PAL does not have to respond to every received packet.

Figure 36 illustrates an example sequence diagram of intermediate response for the case of out-data

transfer. In this case, the WSD Host PAL is the sending PAL and the WSD Device PAL is the receiving

PAL. Figure 37 illustrates an example sequence diagram of intermediate response for the case of in-data

transfer. In this case, the WSD Device PAL is the sending PAL and the WSD Host PAL is the receiving

PAL.

Device PAL SD Interconnection

Local SD Host Controller

SAP request ( VPST : EBUSY)

end of bus busy


of 113

Figure 36: An example sequence diagram of intermediate response [out-data transfer]

Figure 37: An example sequence diagram of intermediate response [in-data transfer]

7.2.7 Auto Command Flags

The Auto Command Flags field is placed in the command field of WSD PAL packet payload.

Frequently used SD commands are preset with one bit flag to execute before or after the intended SD

command described in the command field of WSD PAL packet payload. WSD Host shall omit to send

independent request with SD command, if it is replaced by this Auto Command Flag. WSD Device shall

execute the assigned SD command as described in the following subsection if a flag is set.

Table 1: List of auto command flags

Mnemonic SD command Brief Description

acmd CMD55 Execute CMD55 before the desired application command.


of 113

stop CMD12 Execute CMD12 stop transmission command explicitly after data transfer

has done.

7.2.7.1 acmd

If the “acmd” flag is set, the WSD Device shall execute CMD55 (APP_CMD) before executing a desired

application command. WSD Device can execute the desired SD command, if the CMD55 is successfully

executed. WSD Device PAL shall return SD response of the desired SD command as a response to the

WSD Host PAL, if the SD command is executed successfully. If an error happens when executing

CMD55, the WSD Device PAL shall return the SD response of the CMD 55 to the WSD Host PAL and

shall not execute the desired SD command.

Figure 38: Sequence diagram of auto command flag: acmd

7.2.7.2 stop

If the “stop” field is set, the WSD Device shall execute CMD12 (STOP_TRANSMISSION) to the target

SD Device, after sending/or receiving intended SD data to/from SD Device, to stop transfer of the data

explicitly. WSD Device PAL shall return SD response of the desired SD command as a response to the

WSD Host PAL.

Figure 39: Sequence diagram of auto command flag: stop


of 113

7.2.8 Error Handling in Data Plane

The purpose of this section is to specify the error handling in data plane related only to transmission

errors over-the-air. The data plane error handling related to other transmission errors are beyond the

scope of this specification.

The WSD Host PAL can detect two different types of data plane errors at its own, i.e., timeout and

packet loss. When the WSD Host PAL detects any type of data plane errors, it shall inform the higher

layer of that error by using the WSDPAL-DATA.indication primitive with the parameter

ValidParamSetType indicating “INT”.

Unlike the WSD Host PAL, the WSD Device PAL can detect only a single type of data plane errors at

its own, i.e., packet loss. When the WSD Device PAL detects loss of any a data plane packet, it shall

send an INT packet with error indication to the WSD Host.

In any of the above cases, the WSD Host shall send a clear bus request to the WSD Device to terminate

the current data plane transaction related to the target SD Bus.

7.2.8.1 Timeout Detection

The WSD Host PAL manages a data plane timer for the period of CHECK_STATUS_PERIOD.

When the WSD Host PAL initiates a first data plane transaction, the data plane timer shall be started. It

shall be reset and restarted once the WSD Host PAL sends or receives any data plane packet which

belongs to any data plane transaction.

When the data plane timer is expired, the WSD Host shall initiate the timeout detection procedure. The

timeout detection procedure at the WSD Host is shown in Figure 40, which comprises of the following

steps:

1) The variant Count is initialized to be zero;

2) The WSD Host sends a check status request to the WSD Device, and restarts the data plane

timer;

3.1) If the WSD Host PAL does not receive the desired data plane packet required to proceed the

data plane transaction or the check status response corresponding to the previous check status

request before the data plane timer expires, go to step 4. Otherwise, if the received packet is

the desired data plane packet, the WSD Host PAL shall determine that data plane is not

timeout and stop the procedure. And if the received packet is the check status response, go to

step 3-2;

3.2) If the WSD Host PAL receives the desired data plane packet before the restarted data plane

timer expires, it shall determine that data plane is not timeout and stop the procedure.

Otherwise, go to step 3-3;

3.3) If Bus Busy field of the received check status response equals to 0b0, go to step 4. Otherwise,

go to step 5;

4) The variant Count is incremented by one;

5) If variant Count is equal to CHECK_STATUS_RETRYNUM, the WSD Host PAL shall

determine that data plane is timeout, and stop the procedure. Otherwise, go back to step 2.

Note that the variant Count is managed per data plane transaction but the data plane timer is shared

among all data plane transactions.


of 113

Figure 40: Data plane timeout detection procedure at the WSD Host

7.2.8.2 Packet Loss Detection

Packet loss detection can be achieved by detecting PSN error only for the packet with valid PSN field.

Either WSD Host PAL or WSD Device PAL shall detect PSN error when

• There exists a missing PSN among headers of successively received data plane packets for the

same direction corresponding to the same SD Bus. An example sequence in this case is shown in

Figure 41; or

• The NextPSN field of received check status packet indicates a value which is different from the

latest PSN plus one for the same direction corresponding to the same SD Bus. An example

sequence in this case is shown in Figure 42.


of 113

Figure 41: The first example of PSN error detection

Figure 42: The second example of PSN error detection


of 113

7.3 WiGig MAC Requirements Mandatory and optional WiGig MAC and PHY features are defined in Annex B of the WiGig MAC and

PHY standard [WGA MAC & PHY]. In addition to the mandatory MAC and PHY features, WSD

requires a set of optional features, listed in Table 2. The PICS table in [WGA MAC & PHY], together

with mandatory features in Table 2, defines the WiGig MAC features required to support the WSD

protocol.

Table 2: Optional WiGig MAC features required by WSD

PICS item Optional feature WSD expectation (M=Mandatory)

DMG MAC features

DMG-M4.4 Transmission of A-MPDU M

DMG-M7.3.2 CBAP allocation M

7.4 WSD Device Discovery For discovery of WSD enabled devices over a wireless link, WFA P2P device discovery mechanism is

required at MAC layer. Specifically, WFA P2P specification [WFA P2P] defines P2P Information

Element as specified in Section 4.1.1 and it carries one or more P2P attribute fields. How P2P IE is

carried in MAC management frames are also specified in Section 4.1.1. One of the P2P attributes is P2P

Device Info which is specified in Section 4.1.15 in WFA P2P specification [WFA P2P]; it carries a

Primary Device Type field whose format is defined in Annex B in WFA P2P specification [WFA P2P]

and optionally Secondary Device Type List field whose format is specified in Section 4.1.15 of WFA

P2P specification [WFA P2P].

For discovery of WSD capability, Secondary Device Type list shall be used in WFA P2P device

discovery mechanism, i.e., the P2P Device Info field shall carry at least one Secondary Device Type as

opposed to the optionally use of the Secondary Device Type List field in WFA P2P specification [WFA

P2P]. More specifically, for every device that is WSD enabled, the Secondary Device Type list shall use

Wireless Gigabit Alliance OUI value of D4 5C 70; its category ID shall be set to that of the Primary

Device Field, and the subcategory ID identifying the WSD capability shall be set according to Table 3.

Note that Table 3 contains the complete list of services/protocols/PALs that are identified via this

mechanism.

Table 3: List of the ID values of the WiGig sub categories for the Secondary Device Type

Category ID Value Sub Category ID Value

The same as that of

the Primary Device Type

The same as that of

Primary Device Type

IP capable device 1

WDE-Source 2

WDE-Sink 3

WSE-Host 4

WSE-Device 5

WBE-Host 6

WBE-Device 7

WSD-Host 8

WSD-Device 9


of 113

7.5 WSD PAL Identification Both WSD Host and WSD Device shall support protocol identification through the Subnetwork Access

Protocol (SNAP) defined in the IEEE 802 standard [IEEE 802], which makes use of the IEEE 802.2

Logical Link Control (LLC) protocol [IEEE 802.2].

Figure 43 shows the LLC and SNAP headers to be used for WSD PAL. Both WSD Host PAL and WSD

Device PAL shall use the registered EtherType 0xXXXX. While the LLC control field is most

commonly set to the LLC Protocol Data Unit (PDU) type UI (Unnumbered Information), other

information-carrying LLC PDU types may also be used with SNAP.

Octets: 1 1 1 3 2

Figure 43: WSD packet encapsulation with LLC and SNAP headers


of 113

8 WSD PAL-SAP Services

The WSD PAL provides data service to a higher layer protocol or interface through WSD PAL-SAP, i.e.

it accepts/delivers SD transactions (e.g., SD commands, SD responses, SD data, interrupt and data

acknowledge) from/to the higher layer protocol or interface.

8.1 WSD PAL-SAP primitives The WSD PAL-SAP utilizes four primitives as depicted in Figure 44 and specified in the following

subsections.

Figure 44: WSD PAL-SAP primitives

8.1.1 WSDPAL-DATA.request

When ValidParamSetType value is either CMD or CMD+DATA, the WSDPAL-DATA.request

primitive is sent from the higher layer of the WSD Host to request transmission of SD command and/or

data.

When ValidParamSetType value is either RES+DATA, INT or EBUSY, the WSDPAL-DATA.request

primitive is sent from the higher layer of the WSD Device to request transmission of either SD response

and data or SD interrupt.

When ValidParamSetType value is DATA, the WSDPAL-DATA.request primitive is sent from the

higher layer of either the WSD Host or the WSD Device to request transmission of SD data.

The primitive parameters are as follows:

WSDPAL-DATA.request(

BusID,

DevID,


of 113

ValidParamSetType,

CommandParamSet,

ResponseParamSet,

InterruptParamSet,

DataSet

)

Table 4: The primitive parameters of WSDPAL-DATA.request

Name Type Valid Range Description

BusID Integer 1 - 7 Specify the Bus ID

DevID Integer 1 - 15 Specify the Device ID

ValidParamSetType Constant 0 - 15 Specify valid part of following Parameter Set

(See Table 5)

CommandParamSet A set of SD Command

parameter information

As defined in

Section 8.1.5

This field is valid only if ValidParamSetType is

CMD or CMD+DATA (See Section 8.1.5).

ResponseParamSet A set of SD Response


As defined in

Section 8.1.6


RES+DATA (See Section 8.1.6).

InterruptParamSet A set of Interrupt

parameter information As defined in

Section 8.1.7 This field is valid only if ValidParamSetType is

INT or EBUSY (See Section 8.1.7).

DataSet A set of SD Data

information

As defined in

Section 8.1.8.


CMD+DATA, RES+DATA or DATA (See Section 8.1.8).

Table 5: Valid value of the ValidParamSetType

Valid value Description

0 CMD

1 Reserved

2 DATA

3 CMD+DATA

4 RES+DATA

5-7 Reserved

8 INT

9-10 Reserved

11 EBUSY

12-15 Reserved

8.1.2 WSDPAL-DATA.indication

When ValidParamSetType value is either CMD or CMD+DATA, the WSDPAL-DATA.indication

primitive is sent from the WSD Device PAL to the higher layer to signal the arrival of the SD command

and/or data.


of 113

When ValidParamSetType value is either RES+DATA or INT, the WSDPAL-DATA.indication

primitive is sent from the WSD Host PAL to the higher layer to signal the arrival of either the SD

response and data or SD interrupt.

When ValidParamSetType value is DATA, the WSDPAL-DATA.indication primitive is sent from either

the WSD Host PAL or the WSD Device PAL to the higher layer to signal the arrival of the SD data.


WSDPAL-DATA.indication(

BusID,

DevID,

ValidParamSetType,

CommandParamSet,

ResponseParamSet,

InterruptParamSet,

DataSet

)

Table 6: The primitive parameters of WSDPAL-DATA.indication


BusID Integer 1-7 Specify the Bus ID


ValidParamSetT

ype Constant 0 - 15 Specify valid part of following Parameter Set

(See Table 5)

CommandParam Set

A set of SD Command


Section 8.1.5 This field is valid only if ValidParamSetType is

CMD or CMD+DATA (See Section 8.1.5).

ResponseParam

Set

A set of SD Response


As defined in

Section 8.1.6


RES+DATA (See Section 8.1.6).

InterruptParamS

et

A set of Interrupt


As defined in

Section 8.1.7


INT (See Section 8.1.7).

DataSet A set of SD Data

information As defined in

Section 8.1.8 This field is valid only if ValidParamSetType is CMD+DATA, RES+DATA or DATA (See

Section 8.1.8).

8.1.3 WSDPAL-DATA.response

When ValidParamSetType value is either RES or RES+DATA-ACK, the WSDPAL-DATA.response

primitive is sent from the higher layer of the WSD Device to respond SD response and/or DATA-ACK.

When ValidParamSetType value is DATA-ACK, the WSDPAL-DATA.response primitive is sent from

the higher layer of either the WSD Host or the WSD Device to respond DATA-ACK.


WSDPAL-DATA.response(

BusID,

DevID,

ValidParamSetType,


of 113

ResponseParamSet,

DataAckParamSet

)

Table 7: The primitive parameters of WSDPAL-DATA.response




ValidParamSetType Constant 0 - 15 Specify valid part of following Parameter

Set (See Table 8)



As defined in

Section 8.1.6

This field is valid only if

ValidParamSetType is RES or

RES+DATAACK (See Section 8.1.6).

DataAckParamSet A set of Data

Acknowledgement

information

As defined in

Section 8.1.9


ValidParamSetType is DATA-ACK or

RES+DATA-ACK (See Section 8.1.9).

Table 8: Valid value of the ValidParamSetType


0 Reserved

1 RES

2-4 Reserved

5 RES+DATA-ACK

6-8 Reserved

9 DATA-ACK

10-15 Reserved

8.1.4 WSDPAL-DATA.confirmation

When ValidParamSetType value is either RES or RES+DATA-ACK, the WSDPAL-

DATA.confirmation primitive is sent from the WSD Host PAL to the higher layer to signal the arrival of

the SD response and/or DATA-ACK for the WSDPAL-DATA.request primitive.

When ValidParamSetType value is DATA-ACK, the WSDPAL-DATA.confirmation primitive is sent

from either the WSD Host PAL or the WSD Device PAL to the higher layer to signal the arrival of the

DATA-ACK for the WSDPAL-DATA.request primitive.


WSDPAL-DATA.confirmation(

BusID,

DevID,

ValidParamSetType,

ResponseParamSet,

DataAckParamSet


of 113

)

Table 9: The primitive parameters of WSDPAL-DATA.confirmation




ValidParamSetType Constant 0 - 15 Specify valid part of following Parameter

Set (See Table 10)



Section 8.1.6 This field is valid only if ValidParamSetType is RES or

RES+DATAACK (See Section 8.1.6).

DataAckParamSet A set of Data

Acknowledgement

information

As defined in

Section 8.1.9


ValidParamSetType is DATA-ACK or

RES+DATA-ACK (See Section 8.1.9).

Table 10: Valid value of ValidParamSetType


0 Reserved

1 RES

2-4 Reserved

5 RES+DATA-ACK

6-8 Reserved

9 DATA-ACK

10-15 Reserved

8.1.5 Command Parameter Set

When ValidParamSetType is either CMD or CMD+DATA, this Command Parameter Set is valid. The

elements of Command Parameter Set are specified in Table 11.

Table 11: The elements of Command Parameter Set


Transaction Type Constant 0 - 15 Specify the type of the transaction sequence using SD

command (See Table 12).

SD Command Index Integer 0 – 63 Specify the index number of the SD command.

SD Command

Argument

4 octets N/A Specify 32-bit SD command argument in a binary form

SD Response Type Constant 0 - 15 Specify expected SD response type to be returned from

the peer PAL (see Table 13).

Auto Command Flags 1 octet As defined in Figure 45 and

Table 14

Specify a trigger of the Auto Command function

described in Section 7.2.7. This one octet forms a bitmap

as specified as Figure 45. If a bit in the bitmap is set, the

associated auto command is triggered as specified in

Table 14.


of 113

Total Data Length Integer 1 - 4294967295

This field is valid only when the SD command Type is

“adtc”. This field indicates the total data length in byte

transferred during this command sequence.

Table 12: Valid value of Transaction Type


0 Broadcast command without response (“bc”) (See Section 7.2.5.1).

1 Broadcast command with response (“bcr”) (See Section 7.2.5.2).

2 Addressed command without data transfer (“ac”) (See Section 7.2.5.3) or

Addressed command without data transfer with SD response type R1b (“ac-r1b”) (See Section

7.2.5.4).

3 Addressed data transfer command for out-data (“adtc-out-data”) (See Section 7.2.5.5).

4 Addressed data transfer command for in-data (“adtc-in-data”) (See Section 7.2.5.6).

5-15 Reserved

Table 13: Valid value of SD Response Type


0 R1b

1 R1

2 R2

3 R3

4 R4

5 R5

6 R6

7 R7

8-14 Reserved

15 No SD response is

expected

Bit: 0 1 2 3 4 5 6 7

Mnemonic acmd Reserved stop Reserved

Figure 45: Bitmap structure of Auto Command Flags

Table 14: Description of Auto Command Flags

Mnemonic Description

acmd When this bit is set, execute CMD55 before the desired application command. (See Section

7.2.7.1).


of 113

stop When this bit is set, execute CMD12 stop transmission command explicitly after data transfer has

done (See Section 7.2.7.2).

8.1.6 Response Parameter Set

When ValidParamSetType is either RES or RES+DATA, this Response Parameter Set is valid. The

elements of Response Parameter Set are specified in Table 15.

Table 15: The elements of Response Parameter Set


SD Response

Type Constant 0 - 15 Specify expected SD response type to be returned from the peer

PAL (see Table 13).

SD Response

Data 16 octets N/A Specify a binary string of SD response data without CRC field

except for SD response type R2. In case of R2, this field

specifies a binary string of whole SD response data including

CRC field. The size of SD response data depends on the SD

response type.

8.1.7 Interrupt Parameter Set

When ValidParamSetType is INT or EBUSY, this Interrupt Parameter Set is valid. The elements of

Interrupt Parameter Set are specified in Table 16.

Table 16: The elements of Interrupt Parameter Set


Event Type Constant 0 -15 Specify the type of the interrupt (See Table 17).

Table 17: Valid value of Event Type


0 SDIO interrupt

1 End of bus

busy

2 SD Bus error

3-7 Reserved

8 PSN error

10 Timeout

11-15 Reserved

The SD Bus error is set when the WSD Device PAL detects any error related to the target SD Bus inside

the WSD Device.

8.1.8 Data Set

When ValidParamSetType is either DATA, CMD+DATA or RES+DATA, this Data Set is valid. The

elements of Data Set are specified in Table 18.

Table 18: The elements of Data Set


of 113


Data Length Integer 1 – 4294967295 Specify data length in byte

Data Binary String N/A Specify SD data to be sent or received

8.1.9 Data Acknowledgement Parameter Set

When ValidParamSetType is either DATA-ACK or RES+DATA-ACK, this Data Acknowledgement Set

is valid. The elements of Data Acknowledgement Parameter Set are specified in Table 19.

Table 19: The elements of Data Acknowledge Parameter Set


Processed

Data Size

Integer 1 – the size of

receiving buffer of the

peer PAL

Specify the size (in byte) of SD data that have been dispatched

from the receiving buffer from the previous DATA-ACK

response in that transaction.

9 WSD PALME-SAP Services

The services provided by the WSD PALME to the SME are specified in this section. These services are

described in an abstract way and do not imply any particular implementation or exposed interface. The

SME uses the services provided by the WSD PALME through the WSD PALME-SAP. The WSD

PALME-SAP primitives are of the following general form:

• ACTION.request which is sent from SME to WSD PALME

• ACTION.indication which is sent from WSD PALME to SME and triggered by receipt of a

request from peer UE.

• ACTION.response which is sent from SME to WSD PALME in response to an

ACTION.indication primitive.

• ACTION.confirm which is sent from WSD PALME to SME and triggered internally or by

receipt of a response from peer UE.

9.1 Session Start

9.1.1 PALME-WSD-SessionStart.request

This primitive is generated by the SME of the WSD Host to establish a WSD PAL session with the

WSD Device and clear/initialize internal states of WSD Device related to the WSD PAL session, except

states of SD Bus. The primitive parameters are as follows:

PALME-WSD-SessionStart.request(

PeerSTAAddress,

TID,

VendorSpecificInfo

)

Table 20: The primitive parameters of PALME-WSD-SessionStart.request


of 113

Name Type Valid range Description

PeerSTAAddress MACAddress Any valid individual MAC

address

Specify the address of the peer WSD

Device

TID Integer 0-15 Specify the Traffic Identifier for the

WSD PAL packets.

VendorSpecificInfo TBD TBD Describe vendor specific information

9.1.2 PALME-WSD-SessionStart.indication

This primitive is generated by the WSD PALME of WSD Device as a result of receipt of a

PALMEWSD-SessionStart.request. The primitive parameters are as follows:

PALME-WSD-SessionStart.indication(

PeerSTAAddress,

TID,

VendorSpecificInfo

)

Table 21: The primitive parameters of PALME-WSD-SessionStart.indication


PeerSTAAddress MACAddress Any valid individual

MAC address Specify the address of the WSD Host

initiating the session start request

TID Integer 0-15 Specify the Traffic Identifier for the WSD

PAL packets.


9.1.3 PALME-WSD-SessionStart.response

This primitive is generated by the SME of WSD Device in response to a PALME-

WSDSessionStart.indication. The primitive parameters are as follows:

PALME-WSD-SessionStart.response(

PeerSTAAddress,

ResultCode,

VendorSpecificInfo

)

Table 22: The primitive parameters of PALME-WSD-SessionStart.response



MAC address

Specify the address of the WSD Host

initiating the session start request.


of 113

ResultCode Constant 0: Success 1: Failure

2: Executed

3: Reserved

Indicate the result of the corresponding request. “Executed” means that the WSD Device is in

the state that the session start procedure has

already been executed.

VendorSpecificInfo TBD TBD Describe vendor specific information.

9.1.4 PALME-WSD-SessionStart.confirm

This primitive is generated by the WSD PALME of WSD Host as a result of receipt of PALME-

WSDSessionStart.response. The primitive parameters are as follows:

PALME-WSD-SessionStart.confirm(

PeerSTAAddress,

ResultCode,

VendorSpecificInfo

)

Table 23: The primitive parameters of PALME-WSD-SessionStart.confirm



MAC address


Device

ResultCode Constant 0: Success

1: Failure

Indicate the result of the corresponding

request.

2: Executed

3: Reserved 4: Timeout

“Timeout” is defined in Section 7.1.4.

“Executed” means that the WSD Device

is in the state that the session start



9.2 Capability Exchange

9.2.1 PALME-WSD-CapabilityExchange.request

This primitive is generated by the SME of the WSD Host to request exchange of their respective

capability information related to the WSD PAL session between WSD Host and WSD Device. The

primitive parameters are as follows:

PALME-WSD-CapabilityExchange.request(

PeerSTAAddress,

SDHostCapabilitySet,

VendorSpecificInfo

)

Table 24: The primitive parameters of PALME-WSD-CapabilityExchange.request



of 113


MAC address Specify the address of the peer WSD Device

SDHostCapabilitySet Set of WSD Host’s

capability information

N/A Specify the capability

information of WSD Host

VendorSpecificInfo TBD TBD Describe vendor specific

information

SDHostCapabilitySet consists of the following elements:

Table 25: The elements of SDHostCapabilitySet


Receiving

buffer size Integer 61440 – 8388608

Specify the size of buffer memory available for receiving SD data

contained in WSD PAL packets in byte

9.2.2 PALME-WSD-CapabilityExchange.indication


PALMEWSD-CapabilityExchange.request. The primitive parameters are as follows:

PALME-WSD-CapabilityExchange.indication(

PeerSTAAddress,

SDHostCapabilitySet,

VendorSpecificInfo

)

Table 26: The primitive parameters of PALME-WSD-CapabilityExchange.indication


PeerSTAAddress MACAddress Any valid

individual MAC

address

Specify the address of the WSD

Host initiating the capability

exchange request

SDHostCapabilitySet Set of WSD Host’s


N/A Specify the capability

information of WSD Host


information

9.2.3 PALME-WSD-CapabilityExchange.response


WSDCapabilityExchange.indication. The primitive parameters are as follows:

PALME-WSD-CapabilityExchange.response(

PeerSTAAddress,

SDDevCapabilitySet

ResultCode,

VendorSpecificInfo

)


of 113

Table 27: The primitive parameters of PALME-WSD-CapabilityExchange.response



individual MAC

address


initiating the capability exchange

request

SDDevCapabilitySet

Set of WSD Device’s


N/A Specify the capability information of

the peer WSD Device

ResultCode

Constant

0: Success

1: Failure 2-3: reserved


request


SDDevCapabilitySet consists of the following elements:

Table 28: The elements of SDDevCapabilitySet


Receiving buffer

size Integer 61440 - 8388608

Specify the size of buffer memory available

for receiving SD data contained in WSD

PAL packets in byte.

Support of

broadcast

command without

response (bc)

Constant 0: bc is not supported 1: bc is supported

Specify whether the broadcast command

without response (bc) is supported by WSD

Device.

Support of

broadcast

command with

response (bcr)

Constant 0: bcr is not supported

1: bcr is supported

Specify whether the broadcast command

with response (bcr) is supported by WSD

Device.

For i = 1: Number

of

Available SD

Buses{

BusID Integer 1-7 Specify the Bus ID for the i-th available SD

Bus.

Bus interface type Constant

0 = SD Bus

1 = UHS-II Bus 2-7: reserved

Specify the interface type for the i-th

available SD Bus.


of 113

Device

accessibility

information

Bitmap

(15 bits)

Bit x = 0: SD Device with

Device ID = x+1 is not

accessible Bit x = 1: SD Device with

Device ID = x+1 is accessible

Not only indicate the accessibility of SD

Devices under the i-th available SD Bus, but

also indicate the Device ID for each of

accessible SD Devices.

Device type Constant

0 = SD Memory

1 = SDIO

2 = COMBO

3: reserved

Specify the type for each of accessible SD

Devices under the i-th available SD Bus.

Write protect

switch level Constant

0 = write protection on

1 = write protection off

Specify the write protection information for

each of accessible SD Devices under the i-th

available SD Bus.

RCA information Integer 0 - 65535

Specify the information of Relative Card

Address register for each of accessible SD

Devices under the i-th available SD Bus [SD

3.01 & SDIO 3.0].

CSD information Bitmap

(128 bits) [SD 3.01 & SDIO 3.0]

Specify the information of Card Specific Data register for each of accessible SD

Devices under the i-th available SD Bus [SD

3.01 & SDIO 3.0]. Note that CSD[7:0] including CRC7 and end

bit is not in use for this specification.

}

9.2.4 PALME-WSD-CapabilityExchange.confirm


WSDCapabilityExchange.response. The primitive parameters are as follows:

PALME-WSD-CapabilityExchange.confirm(

PeerSTAAddress,

SDDevCapabilitySet,

ResultCode,

VendorSpecificInfo

)

Table 29: The primitive parameters of PALME-WSD-CapabilityExchange.confirm





of 113

SDDevCapabilitySet

Set of WSD Device’s

capability information N/A Specify the capability information

of the WSD Device

ResultCode

Constant 0: Success 1: Failure

2-3: Reserved

4: Timeout

Indicate the result of the corresponding request. “Timeout” is defined in Section

7.1.4.


information

9.3 Session Termination

9.3.1 PALME-WSD-SessionTermination.request

This primitive is generated by the SME of the WSD Host to request explicit disconnection of WSD PAL

session in response to the user or application demand. The primitive parameters are as follows:

PALME-WSD-SessionTermination.request(

PeerSTAAddress,

VendorSpecificInfo

)

Table 30: The primitive parameters of PALME-WSD-SessionTermination.request



address Specify the address of the peer WSD Device


information

9.3.2 PALME-WSD-SessionTermination.indication


PALMEWSD-SessionTermination.request. The primitive parameters are as follows:

PALME-WSD-SessionTermination.indication(

PeerSTAAddress,

VendorSpecificInfo

)

Table 31: The primitive parameters of PALME-WSD-SessionTermination.indication



MAC address Specify the address of the WSD Host initiating

the session termination request


9.3.3 PALME-WSD-SessionTermination.response


WSDSessionTermination.indication. The primitive parameters are as follows:

PALME-WSD-SessionTermination.response(

PeerSTAAddress,

ResultCode,


of 113

VendorSpecificInfo

)

Table 32: The primitive parameters of PALME-WSD-SessionTermination.response


PeerSTAAddress MACAdd

ress

Any valid individual

MAC address


initiating the session termination request


2: Executed

3: Reserved


request. “Executed” means that the WSD Device is in

the state that the session termination procedure



9.3.4 PALME-WSD-SessionTermination.confirm


WSDSessionTermination.response. The primitive parameters are as follows:

PALME-WSD-SessionTermination.confirm(

PeerSTAAddress,

ResultCode,

VendorSpecificInfo

)

Table 33: The primitive parameters of PALME-WSD-SessionTermination.confirm



MAC address

Specify the address of the peer WSD Device


2: Executed

3: Reserved

4: Timeout


request.

“Timeout” is defined in Section 7.1.4.

“Executed” means that the WSD Device is in

the state that the session termination



9.4 Check Connection

9.4.1 PALME-WSD-CheckConnection.request

This primitive is generated by the SME of the WSD Host to check the existence of PAL connections

between the WSD Host and the WSD Device. The primitive parameters are as follows:

PALME-WSD-CheckConnection.request(


of 113

PeerSTAAddress,

VendorSpecificInfo

)

Table 34: The primitive parameters of PALME-WSD-CheckConnection.request



MAC address


Device


9.4.2 PALME-WSD-CheckConnection.indication

This primitive is generated by the WSD PALME of the peer WSD Device as a result of receipt of a

PALME-WSD-CheckConnection.request. The primitive parameters are as follows:

PALME-WSD-CheckConnection.indication(

PeerSTAAddress,

VendorSpecificInfo

)

Table 35: The primitive parameters of PALME-WSD-CheckConnection.indication



MAC address


initiating the check connection request


9.4.3 PALME-WSD-CheckConnection.response

This primitive is generated by the SME of the peer WSD Device in response to a PALME-

WSDCheckConnection.indication. The primitive parameters are as follows:

PALME-WSD-CheckConnection.response(

PeerSTAAddress,

VendorSpecificInfo

)

Table 36: The primitive parameters of PALME-WSD-CheckConnection.response



MAC address


initiating the check connection request



of 113

9.4.4 PALME-WSD-CheckConnection.confirm

This primitive is generated by the WSD PALME of the WSD Host as a result of receipt of

PALMEWSD-CheckConnection.response. The primitive parameters are as follows:

PALME-WSD-CheckConnection.confirm(

PeerSTAAddress,

ResultCode,

VendorSpecificInfo

)

Table 37: The primitive parameters of PALME-WSD-CheckConnection.confirm



MAC address


Device


1-3: Reserved

4: Timeout


request. “Timeout” is defined in Section 7.1.4.


9.5 Get Bus handle

9.5.1 PALME-WSD-GetBusHandle.request

This primitive is generated by the SME of the WSD Host to request getting the access right of the target

SD Bus inside the WSD Device. The primitive parameters are as follows:

PALME-WSD-GetBusHandle.request(

PeerSTAAddress,

BusID,

VendorSpecificInfo

)

Table 38: The primitive parameters of PALME-WSD-GetBusHandle.request



MAC address


BusID Integer 1-7 Specify the Bus ID of the target SD Bus

inside the peer WSD Device


9.5.2 PALME-WSD-GetBusHandle.indication


PALMEWSD-GetBusHandle.request. The primitive parameters are as follows:

PALME-WSD-GetBusHandle.indication(

PeerSTAAddress,


of 113

BusID,

VendorSpecificInfo

)

Table 39: The primitive parameters of PALME-WSD-GetBusHandle.indication



MAC address


initiating the get bus handle request


inside the WSD Device


9.5.3 PALME-WSD-GetBusHandle.response


WSDGetBusHandle.indication. The primitive parameters are as follows:

PALME-WSD-GetBusHandle.response(

PeerSTAAddress,

BusID,

ResultCode,

VendorSpecificInfo

)

Table 40: The primitive parameters of PALME-WSD-GetBusHandle.response



MAC address


initiating the get bus handle request




1: Failure

2: Executed 3: Busy


request. “Busy” means the target SD Bus has been

used by the WSD Device locally or by any

other WSD Host. “Executed” means the WSD Device is in

the state that the get bus handle procedure




of 113

9.5.4 PALME-WSD-GetBusHandle.confirm


WSDGetBusHandle.response. The primitive parameters are as follows:

PALME-WSD-GetBusHandle.confirm(

PeerSTAAddress,

BusID,

ResultCode,

VendorSpecificInfo

)

Table 41: The primitive parameters of PALME-WSD-GetBusHandle.confirm


PeerSTAAddress MACAddr

ess

Any valid

individual MAC

address


BusID Integer 1-7 Specify the Bus ID of the target SD Bus inside

the peer WSD Device


2: Executed

3: Busy

4: Timeout

Indicate the result of the corresponding request. “Busy” means the target SD Bus has been used

by the WSD Device locally or by any other WSD Host. “Timeout” is defined in Section 7.1.4.

“Executed” means the WSD Device is in the

state that the get bus handle procedure has



9.6 Release Bus handle

9.6.1 PALME-WSD-ReleaseBusHandle.request

This primitive is generated by the SME of the WSD Host to request releasing the access right of the

target SD Bus inside the WSD Device. The primitive parameters are as follows:

PALME-WSD-ReleaseBusHandle.request(

PeerSTAAddress,

BusID,

ModificationFlag,

VendorSpecificInfo

)

Table 42: The primitive parameters of PALME-WSD-ReleaseBusHandle.request



of 113


address

Specify the address of the peer

WSD Device

BusID Integer 1-7 Specify the Bus ID of the target

SD Bus inside the peer WSD Device

ModificationFlag Bitmap (15

bits)

Bit x =0: The content of SD

Memory Device with Device

ID = x+1 has not changed

Bit x= 1: The content of SD Memory Device with Device

ID = x+1 has changed

Specify whether the content of

each of SD Memory Devices

under target SD Bus has changed

while the bus handle for target SD

Bus is in Active State.


information

9.6.2 PALME-WSD-ReleaseBusHandle.indication


PALMEWSD-ReleaseBusHandle.request. The primitive parameters are as follows:

PALME-WSD-ReleaseBusHandle.indication(

PeerSTAAddress,

BusID,

ModificationFlag,

VendorSpecificInfo

)

Table 43: The primitive parameters of PALME-WSD-ReleaseBusHandle.indication



address


Host initiating the release bus

handle request


SD Bus inside the WSD Device

ModificationFlag Bitmap (15 bits)


Memory Device with Device ID = x+1 has not changed

Bit x= 1: The content of SD









information


of 113

9.6.3 PALME-WSD-ReleaseBusHandle.response


WSDReleaseBusHandle.indication. The primitive parameters are as follows:

PALME-WSD-ReleaseBusHandle.response(

PeerSTAAddress,

BusID,

ResultCode,

VendorSpecificInfo

)

Table 44: The primitive parameters of PALME-WSD-ReleaseBusHandle.response



individual MAC

Specify the address of the WSD Host initiating

the release bus handle request

address


the WSD Device


1: Failure

2: Executed 3: Reserved

Indicate the result of the corresponding request.

“Executed” means the WSD Device is in the state

that the release bus handle procedure has already

been executed.


9.6.4 PALME-WSD-ReleaseBusHandle.confirm


WSDReleaseBusHandle.indication. The primitive parameters are as follows:

PALME-WSD-ReleaseBusHandle.confirm(

PeerSTAAddress,

BusID,

ResultCode,

VendorSpecificInfo

)

Table 45: The primitive parameters of PALME-WSD-ReleaseBusHandle.confirm



MAC address



of 113



ResultCode Constant 0: Success 1: Failure 2: Executed





state that the release bus handle procedure



9.7 Suspend Bus handle

9.7.1 PALME-WSD-SuspendBusHandle.request

This primitive is generated by the SME of the WSD Host to request releasing temporarily the access

right of the target SD Bus inside the WSD Device. The primitive parameters are as follows:

PALME-WSD-SuspendBusHandle.request(

PeerSTAAddress,

BusID,

ModificationFlag,

LockFlag,

VendorSpecificInfo

)

Table 46: The primitive parameters of PALME-WSD-SuspendBusHandle.request



address

Specify the address of the peer

WSD Device

BusID Integer 1-7 Specify the Bus ID of the target SD

Bus inside the peer WSD Device


bits)




Bit x= 1: The content of SD Memory Device with Device







LockFlag

Constant

0: The bus handle is not

locked 1: The bus handle is locked

Specify whether target SD Bus can

be accessed while the bus handle

for target SD Bus is in Inactive

State.


of 113


information

9.7.2 PALME-WSD-SuspendBusHandle.indication


PALMEWSD-SuspendBusHandle.request. The primitive parameters are as follows:

PALME-WSD-SuspendBusHandle.indication(

PeerSTAAddress,

BusID,

ModificationFlag,

LockFlag,

VendorSpecificInfo

)

Table 47: The primitive parameters of PALME-WSD-SuspendBusHandle.indication



address

Specify the address of the

WSD Host initiating the

suspend bus handle request


SD Bus inside the WSD Device

ModificationFlag Bitmap (15 bits) Bit x =0: The content of SD

Memory Device with Device ID

= x+1 has not changed Bit x= 1: The content of SD

Memory Device with Device ID

= x+1 has changed



under target SD Bus has

changed while the bus handle

for target SD Bus is in Active

State.

LockFlag

Constant

0: The bus handle is not locked

1: The bus handle is locked

Specify whether target SD Bus

can be accessed while the bus

handle for target SD Bus is in

Inactive State.


information

9.7.3 PALME-WSD-SuspendBusHandle.response


WSDSuspendBusHandle.indication. The primitive parameters are as follows:

PALME-WSD-SuspendBusHandle.response(

PeerSTAAddress,

BusID,

ResultCode,


of 113

VendorSpecificInfo

)

Table 48: The primitive parameters of PALME-WSD-SuspendBusHandle.response



MAC address Specify the address of the WSD Host initiating

the suspend bus handle request


the WSD Device


1: Failure

2: Executed 3: Reserved


request. “Executed” means the WSD Device is

in the state that the suspend bus handle



9.7.4 PALME-WSD-SuspendBusHandle.confirm

This primitive is generated by the WSD PALME of the WSD Host initiating the Ping request as a result

of receipt of PALME-WSD-CheckConnection.response. The primitive parameters are as follows:

PALME-WSD-SuspendBusHandle.confirm(

PeerSTAAddress,

BusID,

ResultCode,

VendorSpecificInfo

)

Table 49: The primitive parameters of PALME-WSD-SuspendBusHandle.confirm







1: Failure 2: Executed





state that the suspend bus handle procedure




of 113

9.8 Resume Bus handle

9.8.1 PALME-WSD-ResumeBusHandle.request

This primitive is generated by the SME of the WSD Host to request getting back the access right of the

target SD Bus inside the WSD Device which is temporarily released by using the suspend bus handle

function. The primitive parameters are as follows:

PALME-WSD-ResumeBusHandle.request(

PeerSTAAddress,

BusID,

VendorSpecificInfo

)

Table 50: The primitive parameters of PALME-WSD-ResumeBusHandle.request



MAC address





9.8.2 PALME-WSD-ResumeBusHandle.indication


PALMEWSD-ResumeBusHandle.request. The primitive parameters are as follows:

PALME-WSD-ResumeBusHandle.indication(

PeerSTAAddress,

BusID,

VendorSpecificInfo

)

Table 51: The primitive parameters of PALME-WSD-ResumeBusHandle.indication



MAC address


initiating the resume bus handle request




9.8.3 PALME-WSD-ResumeBusHandle.response


WSDResumeBusHandle.indication. The primitive parameters are as follows:


of 113

PALME-WSD-ResumeBusHandle.response(

PeerSTAAddress,

BusID,

ModificationFlag,

ResultCode,

VendorSpecificInfo

)

Table 52: The primitive parameters of PALME-WSD-ResumeBusHandle.response



address


Host initiating the resume bus

handle request

BusID Integer 1-7 Specify the Bus ID of the target SD Bus inside the WSD Device

ModificationFlag Bitmap (15 bits) Bit x =0: The content of SD Memory Device with Device


Bit x= 1: The content of SD







Bus is in Inactive State.


1: Failure 2: Executed

3: Busy

Indicate the result of the

corresponding request. “Busy” means the target SD Bus

has been used by the WSD Device

locally or by any other WSD Host. “Executed” means the WSD

Device is in the state that the

resume bus handle procedure has



information

9.8.4 PALME-WSD-ResumeBusHandle.confirm


WSDResumeBusHandle.response. The primitive parameters are as follows:

PALME-WSD-ResumeBusHandle.confirm(

PeerSTAAddress,

BusID,

ModifcationFlag,

ResultCode,


of 113

VendorSpecificInfo

)

Table 53: The primitive parameters of PALME-WSD-ResumeBusHandle.confirm



address Specify the address of the peer WSD Device

BusID Integer 1-7 Specify the Bus ID of the target SD

Bus inside the peer WSD Device


bits)

Bit x =0: The content of SD Memory Device with Device ID = x+1 has not

changed Bit x= 1: The content of SD Memory Device with

Device ID = x+1 has

changed


each of SD Memory Devices under

target SD Bus has changed while

the bus handle for target SD Bus is

in Inactive State.


2: Executed

3: Busy

4: Timeout

Indicate the result of the corresponding request. “Busy” means the target SD Bus has

been used by the WSD Device

locally or by any other WSD Host.

“Timeout” is defined in Section

7.1.4. “Executed” means the WSD Device

is in the state that the resume bus

handle procedure has already been

executed.


information

9.9 Clear Bus

9.9.1 PALME-WSD-ClearBus.request

This primitive is generated by the SME of the WSD Host to request the WSD Device to clear the buffer

and internal state parameters of data plane for all data plane transactions related to the target SD Bus.


PALME-WSD-ClearBus.request(

PeerSTAAddress,

BusID,

VendorSpecificInfo

)

Table 54: The primitive parameters of PALME-WSD-ClearBus.request


of 113



MAC address





9.9.2 PALME-WSD-ClearBus.indication


PALMEWSD-ClearBus.request. The primitive parameters are as follows:

PALME-WSD-ClearBus.indication(

PeerSTAAddress,

BusID,

VendorSpecificInfo

)

Table 55: The primitive parameters of PALME-WSD-ClearBus.indication



MAC address


initiating the clear bus request




9.9.3 PALME-WSD-ClearBus.response


WSDClearBus.indication. The primitive parameters are as follows:

PALME-WSD-ClearBus.response(

PeerSTAAddress,

BusID,

ResultCode,

VendorSpecificInfo

)

Table 56: The primitive parameters of PALME-WSD-ClearBus.response



MAC address


initiating the clear bus request


of 113




2-3: Reserved


request


9.9.4 PALME-WSD-ClearBus.confirm


WSDClearBus.response. The primitive parameters are as follows:

PALME-WSD-ClearBus.confirm(

PeerSTAAddress,

BusID,

ResultCode,

VendorSpecificInfo

)

Table 57: The primitive parameters of PALME-WSD-ClearBus.confirm



MAC address





2-3: Reserved

4: Timeout

Indicate the result of the corresponding request


9.10 Notification

9.10.1 PALME-WSD-Notification.request

This primitive is generated by the SME of the WSD Device to request informing the WSD Host of the

occurrence of any asynchronous event. The primitive parameters are as follows:

PALME-WSD-Notification.request(

PeerSTAAddress,

NotificationType,

EventMessage,

EventParameter,

VendorSpecificInfo


of 113

)

Table 58: The primitive parameters of PALME-WSD-Notification.request



MAC address


Host

NotificationType Constant 0: Control indication

1: Update indication 2-3: Reserved

Specify the type of notification

EventMessage Constant See details in Table 59 Specify the event message

EventParameter See details in Table

59

See details in Table 59 Specify the parameters of the

asynchronous event or event message


Table 59: EventMessage and EventParameter

NotificationType EventMessage EventParameter Type Valid

range Description

0: Control

indication

0: Session start

request N/A N/A N/A Session start request

triggered by WSD Device.

1: Capability

exchange

request N/A N/A N/A

Capability exchange request

triggered by WSD Device

when SDDevCapabilitySet

has been changed.

2: Session

termination

request N/A N/A N/A

Session termination request


3: Check

connection

request N/A N/A N/A

Check connection request


4-7: Reserved

8: Get Bus

handle request

Bus ID of target

SD Bus Integer 1-7

Get bus handle request


when the target SD Bus

becomes available after the

get bus handle request


of 113

initiated by WSD Host fails

because of busy state of the

target SD Bus.

9: Release bus

handle request Bus ID of target SD Bus Integer 1-7

Release bus handle request


10: Suspend

bus handle

request

Bus ID of target

SD Bus Integer 1-7

Suspend bus handle request


11: Resume bus

handle request

Bus ID of target

SD Bus Integer 1-7

Resume bus handle request


when the target SD Bus

becomes available, after the

resume bus handle request

initiated by WSD Host fails

because of busy state of the

target SD Bus.

12: Clear bus

request

Bus ID of target

SD Bus Integer 1-7

Clear bus request triggered

by the WSD Device when

any a data plane transaction

related to the target SD Bus

is terminated abnormally.

13-15:

Reserved

1: Update

indication

0: Capability

update

indication

Bus ID of target

SD Bus and

Device ID of target

SD Device

{Integer, Integer}

{1-7, 1-15}

Capability update request


for removal of SD Device

information.

1-15: Reserved

2-3: reserved

9.10.2 PALME-WSD-Notification.indication

This primitive is generated by the WSD PALME of WSD Host as a result of receipt of a PALME-

WSDNotification.request. The primitive parameters are as follows:

PALME-WSD-Notification.indication(

PeerSTAAddress,

NotificationType,

EventMessage,

EventParameter,

VendorSpecificInfo


of 113

)

Table 60: The primitive parameters of PALME-WSD-Notification.indication



MAC address Specify the address of the WSD

Device

NotificationType Constant 0: Control indication

1: Update indication 2-3: Reserved

Specify the type of notification

EventMessage Constant See details in Table 59 Specify the event message

EventParameter See details in Table

59

See details in Table 59 Specify the parameters of the

asynchronous event or event message



of 113

10 Packet Formats

The WSD PAL packet comprises of a set of fields that occur in a fixed order in all packets. Each frame

consists of the following basic components:

• A header

• A variable length payload, which contains information specific to the packet type

As shown in Figure 46, the WSD PAL header field has a fixed size of 8 octets. The WSD PAL payload

field is of variable size. The maximum WSD PAL payload size is 7704 octets.

Octets: 8 1 - 7704

WSD PAL header WSD PAL payload

Figure 46: WSD PAL packet format

10.1 WSD PAL Header Each WSD PAL packet contains a 64 bits packet header. This header is for PAL to PAL interpretation

only. Each WSD PAL header shall contain the fields as described in Figure 47.

LSB 0 63 MSB

P

V PType Reser

ved PD T

BusI

D Reserve

d DevI

D Reserved PSN Reser

ved PLen Reser

ved Bits 2 1 1 4 3 1 4 4 11 1 13 19

Figure 47: WSD PAL packet header format

The PV field is 2 bits in length and specifies WSD PAL protocol version. Table 61 defines the valid

value of the PV field. If a packet is received that has the PV field set to a different value than what is

supported by the WSD PAL, the packet shall be ignored by the WSD PAL layer.

Table 61: Valid value of the PV field


0b00 Current version

0b01-0b11 Reserved

The PType field is 1 bit in length and specifies the type of WSD PAL packet. Table 62 defines the valid

value of the PType field.

Table 62: Valid value of the PType field


0b0 Packet for control plane

0b1 Packet for data plane

The PDT field is 4 bit in length and specifies the Payload Data Type of WSD PAL packet. Table 63

defines the valid value of the PDT field for control plane packet (PType = 0).


of 113

Table 63: Valid value of the PDT field for control plane packet (PType = 0)


0b0000 Session Start

0b0001 Capability Exchange

0b0010 Session Termination

0b0011 Check Connection

0b0100 Notification

0b0101-0b0111 Reserved

0b1000 Get Bus Handle

0b1001 Release Bus Handle

0b1010 Suspend Bus Handle

0b1011 Resume Bus Handle

0b1100 Clear Bus


As shown in Table 63, the control plane packets with PDT = {0b0000, …., 0b0011}, PDT = 0b0100 and

PDT = {0b1000, …, 0b1100} are for session management, notification and bus handle management

purposes, respectively.

From the viewpoint of WSD Host, an incoming session management or bus handle management packet

always carries a response message, and an incoming notification packet always carries a request

message. From the viewpoint of WSD Device, an incoming session management or bus handle

management packet always carries a request message.

For session management or bus handle management packets, a single PDT value indicates two different

packet formats which are corresponding to the request and response messages of a single session

management or bus handle management function, respectively. For notification packets, a single PDT

value indicates a single packet format which is corresponding to notification request message.

During setup of a WSD PAL session, a user equipment may receive session start request packet and

session start response packet from peer user equipment. In this case, it cannot determine whether an

incoming session start packet carries request message or response message. Therefore, a mechanism is

especially required for session start packet to identify whether the packet carries request message or

response message.

Table 64 defines the valid value of the PDT field for data plane packet (PType = 1).


of 113

Table 64: Valid value of the PDT field for data plane packet (PType = 1)


0b0000 CMD

0b0001 RES

0b0010 DATA

0b0011 CMD+DATA

0b0100 RES+DATA

0b0101 RES+DATA-ACK


0b1000 INT

0b1001 DATA-ACK

0b1010 CHECK-STATUS


WSD PAL native packets include any control plane packet and any INT/DATA-ACK/CHECKSTATUS

packet for data plane.

The BusID filed is 3 bits in length and specifies the Bus ID of target SD Bus. The field is not valid for

session management packets and session management related notification packets. Table 65 defines the

valid value of the BusID field.

Table 65: Valid value of the BusID field


0b001-0b111 The Bus ID of target SD Bus is the field value in decimal

The DevID filed is 4 bits in length and specifies the Device ID of target SD Device. The field is not

valid for control plane packets except capability update request packets. Table 66 defines the valid value

of the DevID field.

Table 66: Valid value of the DevID field


0b0001-0b1111 The Device ID of target SD Device is the field value in decimal


of 113

The PSN field is 11 bits in length and specifies the Packet Sequence Number of WSD PAL packet,

which increments by one for each packet for same direction corresponding to the same SD Bus. This

field shall be set to 0x000 for any WSD PAL native packet. Table 67 defines the valid value of the PSN

field.

Table 67: Valid value of the PSN field


0x000-0x7FF Packet Sequence Number of WSD PAL packet is the field value in decimal

The PLen filed is 13 bits in length and specifies the entire size of WSD PAL packet in bytes. Table 68

defines the valid value of the PLen field.

Table 68: Valid value of the PLen field


0x0009- 0x1E2F The entire size of WSD PAL packet is the field value in decimal

10.2 WSD PAL Control Plane Packet Formats In this section, the WSD PAL packet formats for control plane are described.

10.2.1 Session Start Request Packet Format

The session start request packet is a control plane packet related to session management, which is

initiated by WSD Host PAL to request establishment of a WSD PAL session with WSD Device PAL.

Figure 48 depicts the session start request packet format. The session start request packet starts with

WSD PAL header and is followed by SessionStartIndicator field. The PDT field in the WSD PAL

header shall be “Session Start” for the session start request packet. The size of this packet format is fixed

and its length is 12 octets.

LSB 0 95 MSB

WSD PAL header SessionStartIndicator TID Reserved

Bits 64 1 4 27

Figure 48: Session start request packet format

The SessionStartIndicator field is 1 bit in length and specifies whether the packet is for session start

request or for session start response. For session start request packet, this field is always “0”.

The TID field is 4 bits in length and specifies the Traffic Identifier for WSD PAL packets.

10.2.2 Session Start Response Packet Format

The session start response packet is a control plane packet related to session management, which is

initiated by WSD Device PAL to return result of a session start request to the WSD Host PAL.

Figure 49 depicts the session start response packet format. The session start response packet starts with

WSD PAL header and is followed by SessionStartIndicator field and ResultCode field. The PDT field in


of 113

the WSD PAL header shall be “Session Start” for the session start response packet. The size of this

packet format is fixed and its length is 12 octets.

LSB 0 95 MSB

WSD PAL header SessionStartIndicator ResultCode Reserved

Bits 64 1 2 29

Figure 49: Session start response packet format

The SessionStartIndicator field is 1 bit in length and specifies whether the packet is for session start

request or for session start response. For session start response packet, this field is always “1”.

The ResultCode field is 2 bits in length and specifies the result of session start request. Table 69 defines

the valid value of the ResultCode field.

Table 69: Valid value for the ResultCode field


0b00 Success

0b01 Failure

0b10 Executed

0b11 Reserved

10.2.3 Capability Exchange Request Packet Format

The capability exchange request packet is a control plane packet related to session management, which

is initiated by WSD Host PAL to request WSD Device PAL to exchange their respective capability

information.

Figure 50 defines the capability exchange request packet format. The capability exchange request packet

starts with WSD PAL header and is followed by ReceivingBufferSize field. The PDT field in the WSD

PAL header shall be “Capability Exchange” for the capability exchange request packet. The size of this


LSB 0 95 MSB

WSD PAL header ReceivingBufferSize Reserved

Bits 64 23 9

Figure 50: Capability exchange request packet format

The ReceivingBufferSize field is 23 bits in length and specifies the size of memory available for

buffering PAL packets received from the WSD Device in bytes. This field shall not be changed after

successful completion of the session setup procedure which includes the session start and capability

exchange procedures. Table 70 defines the valid value of the ReceivingBufferSize field.


of 113

Table 70: Valid value for the ReceivingBufferSize field


0x00F000-0x800000 The size of receiving buffer is the field value in decimal

10.2.4 Capability Exchange Response Packet Format

The capability exchange response packet is a control plane packet related to session management, which

is initiated by WSD Device PAL to return result of a capability exchange request to the WSD Host PAL.

Figure 51 defines the capability exchange response packet format. The capability exchange response

packet starts with WSD PAL header and is followed by ReceivingBufferSize field, Bc field, Bcr field,

OC field, ResultCode field, UUID field and SDDevCapabilitySet field. The PDT field in the WSD PAL

header shall be “Capability Exchange” for the capability exchange response packet. The size of this

packet format is variable and its minimum length is 28 octets and maximum length is 2156 octets.

LSB 0 MSB

WSD PAL

header ReceivingBufferSize Bc Bcr OC ResultCode Reserved UUID SDDevCapabilitySet

Bits 64 23 1 1 3 2 2 128 0 ~ 17024

Figure 51: Capability exchange response packet format

The ReceivingBufferSize field is 23 bits in length and specifies the size of memory available for

buffering PAL packets received from the WSD Host in bytes. This field shall not be changed after

successful completion of the session setup procedure which includes the session start and capability

exchange procedures. Table 71 defines the valid value of the ReceivingBufferSize field.

Table 71: Valid value for the ReceivingBufferSize field


0x00F000-0x800000 The size of receiving buffer is the field value in decimal

The Bc field is 1 bit in length and specifies whether broadcast command without response (bc) is

supported by WSD Device. This field shall not be changed after successful completion of the session

setup procedure which includes the session start and capability exchange procedures. Table 72 defines

the valid value of the Bc field.

Table 72: Valid value of the Bc field


0b0 Bc is not supported

0b1 Bc is supported

The Bcr field is 1 bit in length and specifies whether broadcast command with response (bcr) is

supported by WSD Device. This field shall not be changed after successful completion of the session

setup procedure which includes the session start and capability exchange procedures. Table 73 defines

the valid value of the Bcr field.


of 113

Table 73: Valid value of the Bcr field


0b0 Bcr is not supported

0b1 Bcr is supported

The ResultCode field is 2 bits in length and specifies the result of capability exchange request. Table 74

defines the valid value of the ResultCode field.



0b00 Success

0b01 Failure

0b10-0b11 Reserved

The UUID field is 128 bits in length, which allows vendor specific optimization [ISO 11578] or [RFC

4122].

The SDDevCapabilitySet field is variable in length and specifies the capability information of WSD

Device. The SDDevCapabilitySet field comprises of N consecutive subfields, where N equals to the

number of available SD Buses inside the WSD Device. Figure 52 defines the format of the

SDDevCapabilitySet subfield, which corresponds to the x-th available SD Bus inside the WSD Device.

The DevInfo-xy field as shown in Figure 52, which corresponds to the y-th SD Device under the x-th

available SD Bus is further depicted in Figure 53.

LSB 0 830 MSB

BusIDx Rvd

BITypex Rvd

DevAccessibilityInfox Rvd

DevInfox1 DevInfox2 DevInfox3 DevInfox4 DevInfox5 Bits 3 1 3 9 15 1 160 160 160 160 160

831 2431 MSB

DevInfox

6 DevInfox

7 DevInfox

8 DevInfox

9 DevInfox

A DevInfox

B DevInfox

C DevInfox

D DevInfox

E DevInfox

F Bits 160 160 160 160 160 160 160 160 160 160

Figure 52: Format of SDDevCapabilitySet subfield

LSB 0 159 MSB

DT-xy Rvd WPSL-xy Rvd RCA-xy CSD-xy

Bits 2 2 1 11 16 128

Figure 53: Format of DevInfo-xy field


of 113

The BusID-x is 3 bits in length and specifies the Bus ID for the x-th available SD Bus inside the WSD

Device.

The BIType-x field is 3 bits in length and specifies interface type for the x-th available SD Bus inside

WSD Device. Table 75 defines the valid value for the BIType-x field.

Table 75: Valid value for the BIType-x field


0b000 SD Bus

0b001 UHS-II Bus


The DevAccessibilityInfo-x field is a 15-bit bitmap, which not only indicates the accessibility of SD

Devices under the x-th available SD Bus inside WSD Device, but also indicates the Device ID for each

SD Device. Table 76 defines the valid value of the DevAccessibilityInfo-x field.

Table 76: Valid value for the DevAccessibilityInfo-x field


Bit y = 0 The SD Device with Device ID = y+1 is not accessible

Bit y = 1 The SD Device with Device ID = y+1 is accessible

The DT-xy field is 2 bits in length and specifies the type for the SD Device with Device ID = y under the

x-th available SD Bus inside WSD Device. This field is not applicable if the SD Device with Device ID

= y under the x-th available SD Bus is inaccessible. Table 77 defines the valid value for the DT-xy field.

Table 77: Valid value for the DT-xy field


0b00 SD Memory

0b01 SDIO

0b10 COMBO

0b11 Reserved

The WPSL-xy field is 1-bit in length, which indicates the write protection switch level for the SD

Device with Device ID = y under the x-th available SD Bus inside the WSD Device. Table 78 defines

the valid value of the WPSL-xy field.

Table 78: Valid value for the WPSL-xy field



of 113

0b0 Write protect for the SD Device with Device ID = y is on

0b1 Write protect for the SD Device with Device ID = y is off

The RCA-xy field is 16-bit in length, which specifies the information on RCA register of the SD Device

with Device ID = y under the x-th available SD Bus inside the WSD Device [SD 3.01 & SDIO 3.00].

The CSD-xy field is 128-bit in length, which specifies the information on CSD register of the SD Device

with Device ID = y under the x-th available SD Bus inside the WSD Device [SD 3.01 & SDIO 3.00].

Note that CSD[7:0] including CRC7 and end bit is not in use for this specification.

10.2.5 Session Termination Request Packet Format

The session termination request packet is a control plane packet related to session management, which is

initiated by WSD Host to request termination of a WSD PAL session with WSD Device PAL.

Figure 54 defines the session termination request packet format. The PDT field in the WSD PAL header

shall be “Session Termination” for the session termination request packet. The size of this packet format

is fixed and its length is 12 octets.

LSB 0 95 MSB

WSD PAL header Reserved

Octets 8 4

Figure 54: Session termination request packet format

10.2.6 Session Termination Response Packet Format

The session termination response packet is a control plane packet related to session management, which

is initiated by WSD Device PAL to return result of a session termination request to WSD Host PAL.

Figure 55 defines the session termination response packet format. The session termination response

packet starts with WSD PAL header and is followed by ResultCode field. The PDT field in the WSD

PAL header shall be “Session Termination” for the session termination response packet. The size of this


LSB 0 95 MSB

WSD PAL header ResultCode Reserved

Bits 64 2 30

Figure 55: Session termination response packet format

The ResultCode field is 2 bits in length and specifies the result of session termination request. Table 79




0b00 Success


of 113

0b01 Failure

0b10 Executed

0b11 Reserved

10.2.7 Check Connection Request Packet Format

The check connection request packet is a control plane packet related to session management, which is

initiated by WSD Host PAL to request checking the existence of PAL connection between WSD Host

PAL and WSD Device PAL.

Figure 56 defines the check connection request packet format. The PDT field in the WSD PAL header

shall be “Check Connection” for the check connection request packet. The size of this packet format is

fixed and its length is 12 octets.

LSB 0 95 MSB


Octets 8 4

Figure 56: Check connection request packet format

10.2.8 Check Connection Response Packet Format

The check connection response packet is a control plane packet related to session management, which is

initiated by WSD Device PAL to return result of a check connection request to WSD Host PAL.

Figure 57 defines the check connection response packet format. The PDT field in the WSD PAL header

shall be “Check Connection” for the check connection response packet. The size of this packet format is

fixed and its length is 12 octets.

LSB 0 95 MSB


Octets 8 4

Figure 57: Check connection response packet format

10.2.9 Get Bus Handle Request Packet Format

The get bus handle request packet is a control plane packet related to bus handle management, which is

initiated by WSD Host PAL to request obtaining access right of target SD Bus from WSD Device PAL.

Figure 58 defines the get bus handle request packet format. The PDT field in the WSD PAL header shall

be “Get Bus Handle” for the get bus handle request packet. The size of this packet format is fixed and its

length is 12 octets. Note that Bus ID of target SD Bus is carried in the WSD PAL header.

LSB 0 95 MSB



of 113

Octets 8 4

Figure 58: Get bus handle request packet format

10.2.10 Get Bus Handle Response Packet Format

The get bus handle response packet is a control plane packet related to bus handle management, which is

initiated by WSD Device to return result of the get bus handle request to WSD Host PAL.

Figure 59 defines the get bus handle response packet format. The get bus handle response packet starts

with WSD PAL header and is followed by ResultCode field. The PDT field in the WSD PAL header

shall be “Get Bus Handle” for the get bus handle response packet. The size of this packet format is fixed

and its length is 12 octets. Note that Bus ID of the target SD Bus is carried in the WSD PAL header.

LSB 0 95 MSB


Bits 64 2 30

Figure 59: Get bus handle response packet format

The ResultCode field is 2 bits in length and specifies the result of get bus handle request. Table 80




0b00 Success

0b01 Failure

0b10 Executed

0b11 Busy

10.2.11 Release Bus Handle Request Packet Format

The release bus handle request packet is a control plane packet related to bus handle management, which

is initiated by WSD Host PAL to request releasing access right of target SD Bus to WSD Device PAL.

Figure 60 defines the release bus handle request packet format. The release bus handle request packet

starts with WSD PAL header and is followed by ModificationFlag field. The PDT field in the WSD

PAL header shall be “Release Bus Handle” for the release bus handle request packet. The size of this

packet format is fixed and its length is 12 octets. Note that Bus ID of the target SD Bus is carried in the

WSD PAL header.

LSB 0 95 MSB

WSD PAL header ModificationFlag Reserved

Bits 64 15 17

Figure 60: Release bus handle request packet format


of 113

The ModificationFlag field is a 15-bit bitmap, which specifies whether the content of each of SD

Devices under the target SD Bus has changed before the bus handle for target SD Bus transits to the

Inactive State. Table 81 defines the valid value of the ModificationFlag field.

Table 81: Valid value for the ModificationFlag field


Bit x =0b0 The content of SD Memory Device with Device ID = x+1 has not changed

Bit x= 0b1 The content of SD Memory Device with Device ID = x+1 has changed

10.2.12 Release Bus Handle Response Packet Format

The release bus handle response packet is a control plane packet related to bus handle management,

which is initiated by WSD Device PAL to return result of the release bus handle request to WSD Host

PAL.

Figure 61 defines the release bus handle response packet format. The release bus handle response packet

starts with WSD PAL header and is followed by ResultCode field. The PDT field in the WSD PAL

header shall be “Release Bus Handle” for the release bus handle response packet. The size of this packet

format is fixed and its length is 12 octets. Note that Bus ID of the target SD Bus is carried in the WSD

PAL header.

LSB 0 95 MSB


Bits 64 2 30

Figure 61: Release bus handle response packet format

The ResultCode field is 2 bits in length and specifies the result of release bus handle request. Table 82




0b00 Success

0b01 Failure

0b10 Executed

0b11 Reserved

10.2.13 Suspend Bus Handle Request Packet Format

The suspend bus handle request packet is a control plane packet related to bus handle management,

which is initiated by WSD Host PAL to request releasing temporarily access right of target SD Bus to

WSD Device PAL.


of 113

Figure 62 defines the suspend bus handle request packet format. The suspend bus handle request packet

starts with WSD PAL header and is followed by ModificationFlag field and LockFlag field. The PDT

field in the WSD PAL header shall be “Suspend Bus Handle” for the suspend bus handle request packet.

The size of this packet format is fixed and its length is 12 octets. Note that Bus ID of the target SD Bus

is carried in the WSD PAL header.

LSB 0 95 MSB

WSD PAL header ModificationFlag LockFlag Reserved

Bits 64 15 1 16

Figure 62: Suspend bus handle request packet format


Memory Devices under the target SD Bus has changed before the bus handle for target SD Bus transits

to the Inactive State. Table 83 defines the valid value of the ModificationFlag field.


Valid

value

Description



The LockFlag field is 1 bit in length and specifies whether target SD Bus can be accessed while the bus

handle for target SD Bus is in Inactive State. Table 84 defines the valid value of the LockFlag field.

Table 84: Valid value for the LockFlag field


0b0 The bus handle is not locked

0b1 The bus handle is locked

10.2.14 Suspend Bus Handle Response Packet Format

The suspend bus handle response packet is a control plane packet related to bus handle management,

which is initiated by WSD Device PAL to return result of the suspend bus handle request to WSD Host

PAL.

Figure 63 defines the suspend bus handle response packet format. The suspend bus handle response

packet starts with WSD PAL header and is followed by ResultCode field. The PDT field in the WSD

PAL header shall be “Suspend Bus Handle” for the suspend bus handle response packet. The size of this


WSD PAL header.


of 113

LSB 0 95 MSB


Bits 64 2 30

Figure 63: Suspend bus handle response packet format

The ResultCode field is 2 bits in length and specifies the result of suspend bus handle request. Table 85




0b00 Success

0b01 Failure

0b10 Executed

0b11 Reserved

10.2.15 Resume Bus Handle Request Packet Format

The resume bus handle request packet is a control plane packet related to bus handle management, which

is initiated by WSD Host PAL to request getting back access right of target SD Bus from WSD Device

PAL.

Figure 64 defines the resume bus handle request packet format. The PDT field in the WSD PAL header

shall be “Resume Bus Handle” for the resume bus handle request packet. The size of this packet format

is fixed and its length is 12 octets. Note that Bus ID of target SD Bus is carried in the WSD PAL header.

LSB 0 95 MSB


Octets 8 4

Figure 64: Resume bus handle request packet format

10.2.16 Resume Bus Handle Response Packet Format

The resume bus handle response packet is a control plane packet related to bus handle management,

which is initiated by WSD Device PAL to return result of the resume bus handle request to WSD Host

PAL.

Figure 65 defines the resume bus handle response packet format. The Payload Data Type in the WSD

PAL header shall be “Resume Bus Handle” for the resume bus handle response packet. The size of this


WSD PAL header.


of 113

LSB 0 95 MSB

WSD PAL header ModificationFlag Reserved ResultCode Reserved

Bits 64 15 1 2 14

Figure 65: Resume bus handle response packet format


Memory Devices under target SD Bus has changed before the bus handle for target SD Bus transits to

the Active State. Table 86 defines the valid value of the ModificationFlag field.





The ResultCode field is 2 bits in length and specifies the result of resume bus handle request. Table 87




0b00 Success

0b01 Failure

0b10 Executed

0b11 Busy

10.2.17 Clear Bus Request Packet Format

The clear bus request packet is a control plane packet related to bus handle management, which is

initiated by the WSD Host to request the WSD Device to clear the buffer and internal state parameters of

data plane for all data plane transactions related to target SD Bus.

Figure 66 defines the clear bus request packet format. The PDT field in the WSD PAL header shall be

“Clear Bus” for the clear bus request packet. The size of this packet format is fixed and its length is 12

octets. Note that Bus ID of target SD Bus is carried in the WSD PAL header.

LSB 0 95 MSB


Octets 8 4

Figure 66: Clear bus request packet format


of 113

10.2.18 Clear Bus Response Packet Format

The clear bus response packet is a control plane packet related to bus handle management, which is

initiated by the WSD Device to return result of the clear bus request to the WSD Host.

Figure 67 defines the clear bus response packet format. The PDT field in the WSD PAL header shall be

“Clear Bus” for the clear bus response packet. The size of this packet format is fixed and its length is 12

octets. Note that Bus ID of the target SD Bus is carried in the WSD PAL header.

LSB 0 95 MSB


Bits 64 2 30

Figure 67: Clear bus response packet format

The ResultCode field is 2 bits in length and specifies the result of clear bus request. Table 88 defines the

valid value of the ResultCode field.



0b00 Success

0b01 Failure

0b10-0b11 Reserved

10.2.19 Notification Request Packet Format

The notification request packet is a control plane packet related to notification, which is initiated by

WSD Device PAL to inform WSD Host of the occurrence of any asynchronous event.

Figure 68 defines the notification request packet format. The notification request packet starts with WSD

PAL header and is followed by NotificationType field and EventMessage field. The PDT field in the

WSD PAL header shall be “Notification” for the notification request packet. The size of this packet

format is fixed and its length is 12 octets.

LSB 0 95 MSB

WSD PAL header NotificationType EventMessage Reserved

Bits 64 2 4 26

Figure 68: Notification request packet format

The NotificationType field is 2 bits in length and specifies the type of notification. Table 89 defines the

valid value of the NotificationType field.


of 113

Table 89: Valid value for the NotificationType field


0b00 Control indication

0b01 Update indication

0b10-0b11 Reserved

The EventMessage field is 4 bits in length and specifies the event message. Table 90 defines the valid

value of the EventMessage field when NotificationType = 0b00.

Table 90: Valid value for the EventMessage field when NotificationType = 0b00


0b0000 Session start request

0b0001 Capability exchange request indication

0b0010 Session termination request

0b0011 Check connection request


0b1000 Get Bus handle request

0b1001 Release bus handle request

0b1010 Suspend bus handle request

0b1011 Resume bus handle request

0b1100 Clear bus request


As shown in Table 90, control indication packets with EventMessage = {0b0000, …, 0b0011} and

EventMessage = {0b1000, …, 0b1100} are for session management purpose and for bus handle

management purpose, respectively.

Note that the EventParameter of control indication packets for bus handle management purpose, i.e., Bus

ID of target SD Bus, is signaled in the WSD PAL header.

Table 91 defines the valid value of the EventMessage field when NotificationType = 0b01.


of 113

Table 91: Valid value for the EventMessage field when NotificationType = 0b01


0b0000 Capability update indication


Note that the EventParameter of update indication packets with EventMessage = 0b0000, i.e., both

Device ID of target SD Device and Bus ID of target SD Bus, is signaled in the WSD PAL header

10.3 WSD PAL Data Plane Packet Formats In this section, the WSD PAL packet formats for data plane are described.

WSD PAL packet for data plane consists of a WSD PAL header and a set of payload units that occur in

a fixed order in all packets WSD PAL packet for data plane shall have Packet Type (PType) value in the

WSD PAL header being always equal to 1 (Data Plane Packet). WSD PAL packet for data plane shall be

either of the types specified by the Payload Data Type as specified in Table 64 of Section 10.1.

A definition of payload units and payload format is described in the following subsections.

10.3.1 WSD PAL Command Payload Unit

The WSD PAL Command Payload Unit conveys SD command and consists of the following fields:

Transaction Type, SD Response Type, SD Command Index, Auto Command Flags, SD Command

Argument and Total Data Length. The format of the WSD PAL Command Payload Unit is illustrated in

Figure 69.

LSB 0 95 MSB

Transaction

Type

SD

Response

Type

SD

Command

Index Reserved

Auto

Command

Flags

SD

Command

Argument

Total Data

Length

Bits 4 4 6 10 8 32 32

Figure 69: WSD PAL Command Payload Unit format

The Transaction field is 4 bits in length and identifies the type of the transaction with the SD command.

Table 92 defines the valid value of this field.

Table 92: Valid value of the Transaction Type field


0b0000 Broadcast command without response (“bc”)

0b0001 Broadcast command with response (“bcr”)


of 113

0b0010 Addressed command without data transfer (“ac”) or addressed command without data

transfer with SD response type R1b (“ac-r1b”)

0b0011 Addressed data transfer command for out-data (“adtc-out-data”).

0b0100 Addressed data transfer command for in-data (“adtc-in-data”).


The SD Response Type field is 4 bits in length and identifies the expected type of SD response

associated with the SD command to be requested. Table 93 defines the valid type of this field.

Table 93: Valid value of the SD Response Type field


0b0000 R1b

0b0001 R1

0b0010 R2

0b0011 R3

0b0100 R4

0b0101 R5

0b0110 R6

0b0111 R7


0b1111 No SD response is expected

The SD Command Index field is 6 bits in length and specifies the index number of the SD command as

specified in [SD 3.01 & SDIO 3.00] and other associated application commands specified by SD

Association.

The Auto Command Flags field is 8 bits in length and forms bitmap structure which each bit is assigned

to the auto command flag as depicted in Figure 70. WSD Host is responsible for valid combination of

the desired command that is specified with the SD Command Index field and the auto command(s). The

WSD Device shall execute corresponding SD command when the associated bit is set as described in

Table 94.

Bit: 0 1 2 3 4 5 6 7

Mnemonic acmd Reserved stop Reserved

Figure 70: Bitmap structure of Auto Command Flags field

Table 94: Mnemonic of the Auto Command Flags field

Mnemonic Description

acmd When this bit is set, execute CMD55 before the desired

application command.

stop When this bit is set, execute CMD12 stop transmission command

explicitly after data transfer has done.


of 113

The SD Command Argument field is 32 bits in length and contains binary data of the argument of SD

command that is specified at the SD Command Index field. The binary format of the SD command

argument is specified in the [SD 3.01 & SDIO 3.00].

The Total Data Length field is 32 bits in length and only valid when the SD command type is “adtc”.

This field specifies the total length in byte of SD data that is transferred in that specific transaction

sequence.

10.3.2 WSD PAL Response Payload Unit

The WSD PAL Response Payload Unit conveys SD response and consists of the following fields: SD

Response Type and SD Response Data. The format of the WSD PAL Response Payload Unit is

illustrated in Figure 71.

LSB 0 191 MSB

SD Response

Type Reserved SD Response Data Reserved

Bits: 4 28 128 32

Figure 71: WSD PAL Response Payload Unit format

The SD Response Type field is 4 bits in length and specifies the type of SD response encapsulated in the

SD Response Data field. Table 95 defines the valid type of this field.

Table 95: Valid value of the SD Response Type field


0b0000 R1b

0b0001 R1

0b0010 R2

0b0011 R3

0b0100 R4

0b0101 R5

0b0110 R6

0b0111 R7


0b1111 No SD response is expected

The SD Response Data field is 128 bits in length and contains binary data of the SD response data that is

specified at the SD Response Type field. The binary format of the SD response data is specified in [SD

3.01 & SDIO 3.00]. When the size of SD response data is shorter than 128 bits, the SD response data

shall be occupied from the least significant byte of the field. For SD response type R1, R1b, R3, R5, R6,

R7, the first 6 byte from the least significant byte of the field is valid and occupied by SD response token

without last octet which contains CRC field. For SD response type R2, the entire field is valid and

occupied by SD response token including last octet which contains CRC field.


of 113

10.3.3 WSD PAL Data Acknowledgement Payload Unit

The WSD PAL Data Acknowledgement Payload Unit conveys data acknowledgement of SD data and

consists of the Remaining Size field. The format of the WSD PAL Data Acknowledgement Payload Unit

is illustrated in Figure 72.

LSB 0 31 32 63 MSB

Reserved Remaining Size

Bits: 32 32

Figure 72: WSD PAL Data Acknowledgement Payload Unit format

The Remaining Size field is 32 bits in length and specifies a size of the remaining data in bytes to be

received and processed in adtc-type transaction.

10.3.4 WSD PAL Data Payload Unit

The WSD PAL Data Payload Unit is to convey SD data and consists of the SD Data field. The format of

the WSD PAL Data Payload Unit is illustrated in Figure 73.

LSB 0 MSB

SD Data

Octets: 1 ~ 7680

Figure 73: WSD PAL Data Payload Unit format

The SD Data field is a variable length field that contains raw SD data. The minimum field size is 1 octet

and the maximum field size is 7680 octets. If the SD data targets at the SD Memory Device, the size of

SD Data field shall be 512 octets for single block read/write operation, and shall be multiple of 512

octets for multiple block read/write operation. If the size of SD data to be transferred exceeds 7680

octets, SD data shall be segmented and transmitted in multiple WSD PAL packets. The size of SD Data

field in each WSD PAL packet, except the last WSD PAL packet, shall be 7680 octet.

10.3.5 WSD PAL Interrupt Payload Unit

The WSD PAL Interrupt Payload Unit is to convey an interrupt message and consists of the following

fields: Event Type. The format of the WSD PAL Interrupt Payload Unit is illustrated in Figure 74.

LSB 0 31 MSB

Event Type Reserved

Bits: 4 28

Figure 74: WSD PAL Interrupt Payload Unit format

The Event Type field is 4 bits in length and specifies the cause of an event. Table 96 defines the valid

type of this field.

Table 96: Valid value of the Event Type field

Valid value Type description


of 113

0b0000 SDIO interrupt

0b0001 Reserved

0b0010 SD Bus error


0b1000 PSN error


10.3.6 WSD PAL Check Status Payload Unit

The WSD PAL Check Status Payload Unit conveys a request or responses of check status and consists

of NextPSN field, Bus Busy field and Remaining Size field. The format of the WSD PAL Check Status

Payload Unit is illustrated in Figure 75.

LSB 0 7 8 18 19 23 24 25 30 31 63 MSB

Reserved NextPSN Reserved Bus

Busy Reserved Remaining

Size

Bits: 8 11 5 1 7 32

Figure 75: WSD PAL Check Status Payload Unit format

The NextPSN field is 11 bits in length and specifies the next incremented value of PSN at its own PAL.

The Bus Busy field is 1 bit in length and specifies whether the target SD Bus is busy or not, 0b0

indicates that the target SD Bus is not busy and 0b1 indicates that the target SD Bus is busy. The Bus

Busy field is not valid for the CHECK-STATUS request packet format.

The Remaining Size field is 32 bits in length and specifies a size of the remaining data in bytes to be

received and processed in adtc-type transaction. The Remaining Size field is only valid when the

transaction is adtc-type transaction.

10.3.7 CMD Packet Format

The CMD packet format consists of a WSD PAL header and a set of payload units that occur in a fixed

order in all packets. Figure 76 depicts the CMD packet format. The CMD packet starts with WSD PAL

header and is followed by WSD PAL Command Payload Unit. The PDT field in the WSD PAL header

shall be “CMD” for the CMD packet format. The size of this packet format is fixed and its length is 20

octets.

LSB 0 159 MSB

WSD PAL header WSD PAL Command Payload Unit

Octets: 8 12

Figure 76: CMD packet format

10.3.8 RES Packet Format

The RES packet format consists of a WSD PAL header and a set of payload units that occur in a fixed

order in all packets. Figure 77 depicts the RES packet format. The RES packet starts with WSD PAL


of 113

header and is followed by WSD PAL Response Payload Unit. The PDT field in the WSD PAL header

shall be “RES” for the RES packet format. The size of this packet format is fixed and its length is 32

octets.

LSB 0 255 MSB

WSD PAL header WSD PAL Response Payload Unit

Octets: 8 24

Figure 77: RES packet format

10.3.9 DATA Packet Format

The DATA packet format consists of a WSD PAL header and a set of payload units that occur in a fixed

order in all packets. Figure 78 depicts the DATA packet format. The DATA packet starts with WSD

PAL header and is followed by WSD PAL Data Payload Unit. The PDT field in the WSD PAL header

shall be “DATA” for the DATA packet format. The size of this packet format is variable and its

minimum length is 9 octets and maximum length is 7688 octets.

LSB 0 63 64 MSB

WSD PAL header WSD PAL Data Payload Unit

Octets: 8 1 ~ 7680

Figure 78: DATA packet format

10.3.10 CMD+DATA Packet Format

The CMD+DATA packet format consists of a WSD PAL header and a set of payload units that occur in

a fixed order in all packets. Figure 79 depicts the CMD+DATA packet format. The CMD+DATA packet

starts with WSD PAL header and is followed by WSD PAL Command Payload Unit and WSD PAL

Data Payload Unit. The PDT field in the WSD PAL header shall be “CMD+DATA” for the

CMD+DATA packet format. The size of this packet format is variable and its minimum length is 21

octets and maximum length is 7700 octets.

LSB 0 159 160 MSB

WSD PAL header

WSD PAL Command Payload

Unit WSD PAL Data Payload Unit

Octets: 8 12 1 ~ 7680

Figure 79: CMD+DATA packet format

10.3.11 RES+DATA Packet Format

The RES+DATA packet format consists of a WSD PAL header and a set of payload units that occur in a

fixed order in all packets. Figure 80 depicts the RES +DATA packet format. The RES+DATA packet

starts with WSD PAL header and is followed by WSD PAL Response Payload Unit and WSD PAL Data

Payload Unit. The PDT field in the WSD PAL header shall be “RES+DATA” for the RES+DATA


of 113

packet format. The size of this packet format is variable and its minimum length is 33 octets and

maximum length is 7712 octets.

LSB 0 255 256 MSB

WSD PAL header WSD PAL Response Payload Unit WSD PAL Data Payload Unit

Octets: 8 24 1 ~ 7680

Figure 80: RES +DATA packet format

10.3.12 DATA-ACK Packet Format

The DATA-ACK packet format consists of a WSD PAL header and a set of payload units that occur in a

fixed order in all packets. Figure 81 depicts the DATA-ACK packet format. The DATA-ACK packet

starts with WSD PAL header and is followed by WSD PAL Data Acknowledgement Payload Unit. The

PDT field in the WSD PAL header shall be “DATA-ACK” for the DATA-ACK packet format. The PSN

field in the WSD PAL header shall be always 0. The size of this packet format is fixed and its length is

16 octets.

LSB 0 127 MSB

WSD PAL header WSD PAL Data Acknowledgement

Payload Unit

Octets: 8 8

Figure 81: DATA-ACK packet format

10.3.13 RES+DATA-ACK Packet Format

The RES+DATA-ACK packet format consists of a WSD PAL header and a set of payload units that

occur in a fixed order in all packets. Figure 82 depicts the RES+DATA-ACK packet format. The

RES+DATA-ACK packet starts with WSD PAL header and is followed by WSD PAL Response

Payload Unit and WSD PAL Data Acknowledgement Payload Unit. The PDT field in the WSD PAL

header shall be “RES+DATA-ACK” for the RES+DATA-ACK packet format. The size of this packet

format is fixed and its length is 40 octets.

LSB 0 319 MSB

WSD PAL header

WSD PAL Response Payload

Unit

WSD PAL Data Acknowledgement

Payload Unit

Octets: 8 24 8

Figure 82: RES+DATA-ACK packet format

10.3.14 INT Packet Format

The INT packet format consists of a WSD PAL header and a set of payload units that occur in a fixed

order in all packets. Figure 83 depicts the INT packet format. The INT packet starts with WSD PAL

header and is followed by WSD PAL Interrupt Payload Unit. The PDT field in the WSD PAL header


of 113

shall be “INT” for the INT packet format. The PSN field in the WSD PAL header shall be always 0. The

size of this packet format is fixed and its length is 12 octets.

LSB 0 63 64 MSB

WSD PAL header WSD PAL Interrupt Payload Unit

Octets: 8 4

Figure 83: INT packet format

10.3.15 CHECK-STATUS Request Packet Format

The CHECK-STATUS request packet format consists of a WSD PAL header and a set of payload units

that occur in a fixed order in all packets. Figure 84 depicts the CHECK-STATUS request packet format.

The CHECK-STATUS request packet starts with WSD PAL header and is followed by WSD PAL

Check Status Payload Unit. The PDT field in the WSD PAL header shall be “CHECK-STATUS” for the

CHECK-STATUS request packet format. The PSN field in the WSD PAL header shall be always 0. The

Bus Busy field is not valid for the CHECK-STATUS request packet format. The Remaining Size field is

only valid when the transaction type is “adtc-in-data”, and it may contain arbitrary value for any other

transaction type. The size of this packet format is fixed and its length is 16 octets.

LSB 0 127 MSB

WSD PAL header WSD PAL Check Status Payload Unit

Octets: 8 8

Figure 84: CHECK-STATUS request packet format

10.3.16 CHECK-STATUS Response Packet Format

The CHECK-STATUS response packet format consists of a WSD PAL header and a set of payload units

that occur in a fixed order in all packets. Figure 85 depicts the CHECK-STATUS response packet

format. The CHECK-STATUS response packet starts with WSD PAL header and is followed by WSD

PAL Check Status Payload Unit. The PDT field in the WSD PAL header shall be “CHECK-STATUS”

for the CHECK-STATUS response packet format. The PSN field in the WSD PAL header shall be

always 0. The Remaining Size field is only valid when the transaction type is “adtc-out-data”, and it may

contain arbitrary value for any other transaction type. The size of this packet format is fixed and its

length is 16 octets.

LSB 0 127 MSB

WSD PAL header WSD PAL Check Status Payload Unit

Octets: 8 8

Figure 85: CHECK-STATUS response packet format


of 113

11 CONSTANT DEFINITIONS

Definitions of constants used in this specification are summarized in Table 97.

Table 97: WSD constants

Name Value

CNTRL_PLANE_TIMEOUT 1000 msec

CNTRL_PLANE_RETRYNUM Implementation specific

CHECK_STATUS_PERIOD 100 msec

CHECK_STATUS_RETRYNUM Implementation specific


of 113

Annex A – Valid Combinations of Various Types (Normative)

Table 98 shows valid combinations of ValidParamSetType in the WSD PAL-SAP primitives, the PDT

field for data plane packet in WSD packet header, value of the Transaction Type field in the WSD PAL

Command Payload Unit. WSD PAL shall generate WSD data plane packet based on the combinations as

shown in Table 98.

Table 98: Valid combinations of various types

Value of ValidParamSetType

in the WSD PAL-SAP

primitives

Valid value of the PDT field for

data plane packet in WSD

packet header

Valid value of the Transaction

Type field in the WSD PAL Command Payload Unit

CMD CMD bc, bcr, ac, ac-r1b, adtc-in-data

RES RES

DATA DATA

CMD+DATA CMD+DATA, DATA adtc-out-data

RES+DATA RES+DATA, DATA

DATA-ACK DATA-ACK, CHECK-STATUS

RES+DATA-ACK RES+DATA-ACK

INT INT

EBUSY

Reserved

WiGig SD Extension PAL Technical Specification

Documents

Transcript of WiGig SD Extension PAL Technical Specification