Protocols And Network Aspects of SDR

1
Protocols And Network Aspects of SDR

• Multimedia Lab.
• Lee Young Seok

yslee38_at_mlab.hanyang.ac.kr
2
Contents

• 12.1 Protocol Stacks SAPs vs. Reconfigurability
• 12.2 Approaches to Protocol Stack Reconfiguration
• 12.3 Reconfiguration Management and Control
• 12.4 Network Support for Software Radios
• 12.5 Conclusions

3
Cf) Software/Firmware categories in commercial
Wireless Terminal
4
Cf) Requirements of SDR Vision of 4G

• Fully converged services
• Ubiquitous mobile access
• Diverse user devices
• Autonomous networks
• Software dependency Intelligent mobile agents

5
12.1 Protocol Stacks SAPs vs. Reconfigurability

• 12.1.1 Service Provision via Service Access
  Points
• 12.1.2 Protocol Configuration and Reconfiguration
• 12.1.3 Interfaces vs SAPs

6
12.1.1 Service Provision via Service Access Points
MT Mobile Terminal BTS
Base Transceiver Station LAPDm A modified
version of the LAPD(Link Access Protocol for the
ISDN D-channel) RR Request Responses
7
12.1.2 Protocol Configuration and Reconfiguration

• Configuration
• - Adaptive and composable approaches offer their
  services to applications via additional
  adaptation layers.
• Reconfiguration
• - The reconfigurable approach is based on
  programming interfaces without such additional
  adaptation layers.

8
12.1.3 Interfaces vs SAPs
9
12.2 Approaches to Protocol Stack Reconfiguration

• 12.2.1 Protocols and Protocol Stacks
• 12.2.2 Modular Approaches
• 12.2.2.1 Adaptive Protocols
• 12.2.2.2 Composable Protocols
• The principle of basic protocol functions being
  combined in a generic protocol stack
• 12.2.2.3 Reconfigurable Protocol Stacks
• 12.2.3 Active Networks
• 12.2.3.1 P1520 Architectures

10
12.2.1 Protocols and Protocol Stack

• Protocols are the actual implementations of
  agreements, and the sending and the receiving
  nodes
• Protocol stack is a list of protocols used by a
  certain system, one protocol per layer
• Protocol stack model not only reduced the
  complexity of protocol implementations but it
  also introduced different levels of abstraction

11
12.2.2.1 Adaptive Protocols
GSM
Adaptive Terminal
UMTS
DECT
decomposition
Protocol Stack Generic Stack
Specific Extension
12
Cf ) The layered structure of the mobile
communication systems GSM and DECT/UMTS
13
Cf ) Interaction of components for an SDR
protocol stack
14
12.2.2.2 Composable Protocols DaCaPo Project
(Dynamic Configuration of Protocols)
Application Adaptation layer
A
SAP for user and application programming interface
configuration during boot/run time sequence
C
Composable layer
Library of protocol functions
SAP for End-to-End connectivity
T
Host-network Interface layer

• CoRA(Configuration and Resource Allocation)
• Connection management
• Runtime environment
• Monitor the other components and control the
  resource

• Layer A Application layer
• Layer C Communication support layer
• Layer T the transport infrastructure layer

15
Cf) DaCaPo with a simple example Protocols
graph for video
16
12.2.2.3 Reconfigurable Stacks
Application
(B1)
(A1)
API-(active interface) object
(A2)
(B2)
Basic Signaling Application-object
(A3)
PPI-I-(active interface) object
(A4)
(B3)
Network Control Layer-object
(A5)
(B4)

• Active Protocol Interface Objects

APIs Application Programming Interfaces PPIs
Protocol Programming Interfaces
17
Cf) OPtIMA Framework(The Open Protocol Interface
Model and Architecture)
APIs Application Programming Interfaces PPIs
Protocol Programming Interfaces
18
12.2.2.3 Reconfigurable Stacks (cont.)
Pro-layer (Net-Control)
T H R E A D
H-3
data
PPI
Pro-layer (Link-Control)
H-2
H-3
data
PPI
Pro-layer (Driver-Control)
H-1
H-2
H-3
data

• Message passing within OPtIMA framework

OPtIMA The Open Protocol Interface Model and
Architecture
19
12.2.3 Active Network(APIs for Networks)

• Object-oriented software engineering(modularity,
  reusability, scalability and reliability)
• Distributed Computing(location-transparent remote
  access, dynamic binding)
• Separation of the signaling business from the
  transport business
• Legacy interoperability will always be kept in
  the forefront

LIJ Leaf-Initiated Join
20
12.2.3.1 IEEE P1520 Architectire(reference Model)
UI, Application
Management of real time streams
Access to generic network services
Distributed object interfaces
Enables to direct access
Connection control and management
21
Cf) Mapping of the P1520 architecture to IP
routers/switches
22
12.3 Reconfiguration Management and Control

• 12.3.1 The Scope of Reconfiguration Management
• 12.3.2 Requirements of a Management Architecture
• 12.3.2.1 Soft Terminals and the Issue of
  Standards Compliance
• 12.3.3 Management Architecture Implications

23
12.3.1 The Scope of Reconfiguration Management
24
12.3.1 The Scope of Reconfiguration
Management(cont.)
Software DownloadServer
Base Station
Terminal
Backbone Network
BackboneNetwork GateWay
Communication end-point
Reconfiguration Manager Terminal
Reconfiguration Manager Base Station
Network Reconfiguration Monitor
Software Server
internal
internal
external
external
external
external
Middleware based reconfiguration platform
25
12.3.2 Requirements of a Management Architecture

• Independent of level within the terminal protocol
  stack, reconfigurability may be
• - Using parameterized radio (and protocol)
  modules
• - Exchange of (a) single component(s) within a
  module
• - Exchange of complete radio modules or protocol
  layers
• The three categories to be considered with an
  internal reconfiguration procedure are
• - Class 0 Partial reconfiguration of any layer
  (or part thereof)
• within an existing standard
  implementation
• - Class 1 Complete reconfiguration of any given
  layer
• - Class 2 Full reconfiguration of a complete
  stack

26
12.3.2 Requirements of a Management Architecture
27
12.3.2.1 Soft Terminals and the Issue of
Standards Compliance

• Each Radio and protocol stack module within an
  SDR terminal may be configured
• - Independently
• - Reconfiguration
• Whether partial (i.e. affecting only one module
  (e.g. the antenna)) or complete (i.e. affecting
  all modules), may cause the terminal to adapt to
  a different access scheme
• Two different requirements may arise
• - A mechanism that allows type approval
  testing/compliance to standards and yet still
  supports the use of open platforms (and thus the
  software provision from any third party), or, for
  a more progressive approach
• - Negotiation mechanisms between the network
  nodes (terminals) which freely allow
  reconfiguration of the network node (terminal)
  within the scope of standardized interfaces, but
  without the need for any formal test approval
  mechanisms (in the traditional sense).

28
12.4 Network Support for Software Radios

• 12.4.1 The Network Access and Connectivity
  Chennel (NACCH)
• 12.4.2 The Bootstrap Channel
• 12.4.3 A Global or Universal Control Channel
  (UCCH)
• 12.4.4 The Interconnected Seamless Network
• 12.4.4.1 Access Networks
• 12.4.4.2 The Backbone

29
12.4.1 The Network Access and Connectivity Channel

• Mobility management
• (Location Management)
• Authentication and registration facilities
• Call paging
• Call establishment signaling
• An Interface to define traffic channels

30
12.4.2 The Bootstrap Channel

• Definition a specific channel onto which the
  terminal camps to download some software to
  access a new service

Coverage area of the pilot channel (signal)
Bootstrap channel areas
31
Cf) Software Layering

• Layer A software modules concern with the
  Communication physical layer processing
• Layer B protocol stack and modification for the
  bearer services
• Layer C any change regarding the end-user
  applications(browser, UI)

32
Cf) Software download Sharing Responsibilities
33
12.4.3 A Global or Universal Control Channel
MM
SWD
MAP/INAP
MAP/INAP
MM
SWD
MM
SWD
IIOP
IIOP
IIOP
TCAP
TCAP
TCP
TCP
TCP
SCCP
SCCP
IP
IP
IP
MTP3
MTP3
Layer 2
Layer 2
Layer 2
Layer 2
Layer 2
Layer 2
MTP2
MTP2
Physical Layer
Physical Layer
Physical Layer
Physical Layer
Physical Layer
Physical Layer
Physical Layer
Physical Layer
URS (User Registry and SW-store)
USST (UCCH signalling and SW transceiver)
USM (UCCH signlling manager)
USC (UCCH switching center)
MT (Mobile Terminal)
34
12.4.4.1 Access Networks
GPRS
UTRAN
PLMN
Node B
RNC
BG
RNC
Node B
SGSN
GGSN
INTERNET
PCU
GSM
SMSC
EIR
HLR
AUC
BSC
PSTN
BTS
MSC
GMSC
VLR
BSC Base Station Controller MSC Mobile
Switching Center GMSC Gateway Mobile Services
Switching Center EIR Equipment Identity
Register SMSC Standard Modular System
Card H/VLR Home/Visitor Location Register PSTN
Public Switched Telephone Network
RNC Radio network Controller BG Border
Gateway SGSN Serving GPRS Support Node GGSN
Gateway GPRS Support Node PCU Protocol Control
Unit BTS Base Transceiver Station PLMN Public
Land Mobile Network
35
12.4.4.2 The Backbone
36
Conclusions

• The Implications of Software reconfigurability,
  demonstration a logical extension from the
  handset to understand the implications for
  network infrastructure
• Limitations of todays protocol stack approaches,
  using service access points, technical approaches
  which dynamically reconfigurable protocols,
  mechanisms
• Need for a new reconfiguration management plane
• The full potential of SDR for allowing full,
  seamless cross network roaming The Interconnected
  Seamless Network
• A goal may yet prove common global air interface
  standard