1. Jul 12, 2010
07/12/10
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: Inclusion of UWB Secure Service Information Element
Date Submitted: September 2018
Source: Yi Yang, Jong-Hoon Jang, Moon-Seok Kang, Jonghyo Lee, Aditya V. Padaki, Boon Loong Ng (Samsung), Rias Al-kadi (NXP)
Company: Samsung
Abstract:[]
Purpose: []
Notice: This document has been prepared to assist the IEEE P It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P
Slide 1
Slide 1
Page 1

2. Note: Notation/nomenclature based on
Overview
Need for application specific payload IE
Envisioned architecture
Proposed Frame Format
Conclusions
Note: Notation/nomenclature based on
ppdu-text-contribution.docx
and
enhanced-impulse-radio.pptx

3. Need for App Specific Payload IE
Most controllers have already established connections from other services (e.g. NFC) to Secure Element (SE)
To ensure seamless deployment of UWB, UWB SE should be able to directly interface with existing SE within host
Existing Host System
Secure Element
UWB Controller
NFC Controller
Frame format should be readable by the existing eSE systems

4. Application specific information
Not all applications need secure element access
Example Case NFC
Figure source: ETSI TS V ( ) Smart Cards; UICC - Contactless Front-end (CLF) Interface; Host Controller Interface (HCI).

5. Proposal UWB controller to have interface to SE
During UWB transaction, APDU can directly forward to the SE under routing table control in UWB
As Figure shows:
There is one direct interface connect the UWB and SE in phone.
In a given UWB session, post secure ranging, reader or POS should trigger the transaction through UWB.
When UWB controller receives UWB Secure Service Information Element (USS IE) MAC payload during the given UWB session, UWB controller should decide whether to forward it to AP or SE based on the routing table setting by user.
Since not all apps need SE, frame format should indicate the kind of application for routing

6. Envisioned Architecture
Not all applications require SE: routing table to decide which applications are routed to SE
Those which require will be directly routed to host SE
Signaling format for the same required

7. UWB Secure Service IE
We propose the addition of USS IE to the list (already existing) of MAC Payload IEs
The frame structure is as proposed below

8. Conclusions
The UWB eSE should be able to interface with existing SE systems
This requires inclusion of a new frame payload IE to route to the SE based on Application
Frame format for UWB Secure Service IE proposed