O C U S T Flexible Protocol Stack Framework : Design, Validation and Performance Tim Farnham 1 , Thorsten Schöler 2 SDR Forum Technical Conference November 2003 1 Toshiba Research Europe Ltd 2 Siemens AG Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 1
O C U Contents S T • Introduction • Terminal architecture • Flexible protocol stack framework – Design – Validation – Performance • Conclusions Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 2
O C U Terminal architecture S T ISO OSI level Implementation domain Layer 7: Application Reconfigurable protocol Reconfigurable protocol Layer 6: Presentation stack architecture stack architecture Layer 5: Session Object-oriented software Layer 4: Transport Highly-optimised software (system / kernel) Layer 3: Network Layer 2: Data Link Layer Digital signal processing hardware Layer 1: Physical Custom hardware Reconfigurable hardware Reconfigurable hardware Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 3
O C U Network Centric Support for Reconfiguration S T Application Ad Hoc Networks Reconfiguration Functions (CMM, RSMM etc.) Flexible protocol stack Reconfiguration Functions Cellular Networks Middleware (MIMM, MNSM etc.) Service Discovery Transport Transport Transport #1 #2 #n Reconfiguration Functions Middleware (MIMM, MNSM etc.) Network Network Network #1 #2 #n Network Mode Selection Middleware Link Link Network PHY Baseband Software Download RF Physical Link Execution environment Hardware Physical Hardware Abstraction Layer Hardware Hardware Reconfigurable Terminal CMM: Configuration Management Module RSMM: Resource System Management Module MIMM: Mode Identification and Mode Monitoring MNSM: Mode Negotiation and Switching Module Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 4
O C Requirements and Solution Features for U S T Flexible Protocol Stacks • Platform Independence – Multiple CPU / execution environment and language support • High reliability / availability – Fallback states, etc. – Validation of Stack Configuration and Implementation • Secure operation – Mechanisms to prevent unauthorised interception, manipulation • Multi-vendor sourcing – Manufacturer, operator, service provider and third party – Open interfaces • Dynamic optimisation – Depending on resource availability, execution environment and service requirements – Mechanisms for active protocol stack reconfiguration • Customisation and enhancement – Mechanisms to allow incremental upgrading Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 5
O C U Contents S T • Introduction • Terminal architecture • Flexible protocol stack framework – Design – Validation – Performance • Conclusions Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 6
O C U State of the art in modular protocol stacks S T Customisable protocol stacks Composable protocol stacks protocol stacks Customisable protocol stacks Composable (design time) (run time) (design time) (run time) Layer α Terminal A Terminal B 1 1 Framework Terminal A specific SW Generic Protocol Stack Terminal B specific SW Layer β Library 1 1 Terminal A Protocol Stack Terminal B Protocol Stack Layer γ X-Kernel – Composable (at compile time) framework with configurable virtual protocol layers OPtIMA – Java based, composable and (run-time) customisable framework with configurable active programming interfaces DIMMA – C++ based, customisable framework which is derived from X-kernel framework Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 7
O C U Protocol stack computation models S T Process per protocol Process per message Process per protocol Process per message Thread for layer α Static code layer α Message 1 Message 2 Thread Thread Static code for for layer β message 1 message 2 Thread for layer β Static code layer γ Thread for layer γ queue Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 8
O C U Proposed Flexible Protocol Stack Framework S T Middleware QoS Manager INET MNSM = Open Interfaces getBestMode CMM IRL measurePerformance MIMM GPI attach/bind/connect getInformation SDM CM GSAP addMode DGSAP DGSAP DGSAP resourceAllocation RSMM GSAP Note : MIMM = Mode Identification and Monitoring Module (or Mode Identification and Monitoring), MNSM = Mode Negotiation and Switching Module (or Mode Switching Module), SDM = Software Download Module, RSMM = Resource System Management Module (or Resource Management System), GPI = Generic Protocol Interface, GSAP = Generic Service Access Point, CM-GSAP = Connection Management GSAP, Authors: Tim Farnham, Date: 30/09/2003 CMM = Configuration Management Module, INET = Internet TCP/IP Stack, IRL = Intelligent Routing Layer. Thorsten Schöler Page: 9
O C U Framework Key Features S T • Generic Protocol Interface (GPI) – Language and platform independent – Radio access technology independent • Generic Service Access Points (GSAPs) – Dynamically bound and rebound – Secure interaction between layer instances – Extensible message data format – Execution environment neutral • Intelligent Routing Layer (IRL) – Supporting dynamic mode selection Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 10
O C U S Generic Protocol Stack Example T - - - Association / Association / Association / Compression / Compression / Compression / Connection setup Connection setup Connection setup registration registration registration decompression decompression decompression Key : Key : Key : = GPI = GPI = Generic Packet Classification / Packet Classification / Packet Classification / Protocol Interface Scheduling Scheduling Scheduling = GSAP = GSAP = Generic Service Access Point = Generic = Generic component component = Generic Packet fragmentation / Packet fragmentation / Packet fragmentation / component reassembly reassembly reassembly Encryption / decryption Encryption / decryption Encryption / decryption Medium Access Control (MAC) / Medium Access Control (MAC) / Alternative Mode Alternative Mode Alternative Mode Performance Performance Performance Medium Access Control (MAC) CRC Generation / CRC Generation / / Link Adaptation Link Adaptation Link Adaptation Detection / Monitoring Detection / Monitoring Detection / Monitoring measurement measurement measurement Scrambling / whitening Scrambling / whitening Radio PHY Radio PHY Radio PHY Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 11
O C U Reconfiguration Management Interactions S T • Open interfaces Management interactions Intelligent allow reconfiguration Routing Best Modes Layer of protocol stack to Performance (IRL) exploit the capabilities of the Generic Protocol Interface attach/bind/connect platform execution Capabilities Connection Management environments and Mode GSAP attributes customisation and DGSAP DGSAP Allocate Resource enhancement options Generic Service DGSAP Access Point within protocol (GSAP) software. Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 12
O C U Contents S T • Introduction • Terminal architecture • Flexible protocol stack framework – Design – Validation – Performance • Conclusions Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 13
O C U Protocol stack validation process S T • Network-based validation – Off-line validation HW Network simulation • Virtual prototyping simulation – HW, SW, Network simulation Simulated – Simulation of actual stack implementation user – Assertions for validation of software Configuration server correctness • Terminal-based validation Syntax check – On-line validation Layers: Layers: DummyLid l6, Dummy l5, CRC l4, Fragment l3, DummyLid l6, Dummy l5, CRC l4, Fragment l3, Semantics • Check of protocol stack configuration Dummy l2, DummyBase l1 Dummy l2, DummyBase l1 Channels: Channels: l6<->l5, l4<->l3, l3<->l2, l2<->l1 l6<->l5, l4<->l3, l3<->l2, l2<->l1 Param: Param: l6: default l6: default check l5: default l5: default l4: crc_size=16 l4: crc_size=16 l3: max_frag_size=1024 l3: max_frag_size=1024 – Syntax and semantics l2: default l2: default l1: mirror=true l1: mirror=true Mobile terminal – Run-time validation Layer 1 SW probes • In protected execution environment Layer 2 • Software probes in protocol stack Layer 3 software Framework Mobile execution environment – Assertion-based Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 14
O C U Contents S T • Introduction • Terminal architecture • Flexible protocol stack framework – Design – Validation – Performance • Conclusions Authors: Tim Farnham, Date: 30/09/2003 Thorsten Schöler Page: 15
Recommend
More recommend
