27.03.2014 Views

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan

Moby Dick Consolidated System Integration Plan

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

D0103v1.doc Version 1 6.7.2003<br />

4.3.4.1 General architecture of the software platform<br />

This section presents an overview of the basic hardware/software architecture. The platform is used to<br />

implement the Time Division Duplex (TDD) transmission mode of the UMTS standard. The hardware<br />

architecture is centred on a real-time PC system that gives access to, and allows experimenting with, wide<br />

band radio resources. The platform is scalable and allows configurations from a powerful base station<br />

with smart antennas to simpler mobile terminals with a single antenna. It provides functionality at three<br />

levels: hardware, Digital Signal Processing (DSP) software, and link level software.<br />

• Hardware Components<br />

The hardware portion of the current testbed consists of 3 elements which are under software-control,<br />

namely<br />

• a PCI-bus based data acquisition card (PMC form-factor)<br />

• an analogue/digital interface<br />

• an up/down conversion RF card using TDD multiplexing<br />

The radio portion is capable of generating arbitrary signals of a 5MHZ bandwidth in the 2110-2170 MHz<br />

band using TDD multiplexing. A new radio interface is being produced for the 1900-1920 MHz band<br />

(UMTS TDD).<br />

• Software Components<br />

The software portion of the platform is an extension to the Linux Operating <strong>System</strong> and makes use of a<br />

hard real-time micro-kernel known as RT -Linux for performing layer 1 and layer 2 UMTS/TDD<br />

processing. Networking functionality is provided by the Linux kernel and open-source extensions.<br />

RT-Linux, an extension to the Linux Operating <strong>System</strong>, supports real-time interrupt handlers and realtime<br />

periodic tasks with interrupt latencies and scheduling jitter close to hardware limits.<br />

Real-time tasks in RT-Linux can communicate with Linux processes either via shared memory regions or<br />

a FIFO interface. Thus, real-time applications can make use of all the powerful, non-real-time services of<br />

Linux, including: Networking, Graphics, Windowing systems, Linux device drivers, Standard POSIX<br />

functionality.<br />

The configurations for Radio Gateways (RG), a combination of a base station and an IP router, and<br />

Mobile Terminals (MT) are shown in figure 65 and figure 66.<br />

IP Network (v4 v6)<br />

Multi-CPU Linux Machine<br />

/dev/srnet<br />

/dev/eth0<br />

Kernel<br />

Space<br />

Layer 1H/2/3<br />

RT thread<br />

Radio<br />

Bearers<br />

IP Networking subsystem<br />

Linux Kernel<br />

Server<br />

Functions<br />

PCI<br />

Real-time<br />

µKernel<br />

DAQ<br />

+<br />

RF<br />

Layer1L<br />

RT thread<br />

Real-time Space<br />

User<br />

Space<br />

Figure 65: Radio Gateway Architecture<br />

The RG’s network connection is IP based and is assumed to be connected to an IP network via Ethernet<br />

using the standard Linux /dev/eth0 Ethernet device. The TD-CDMA to IP Network Interconnect is<br />

made via a homemade RTLinux driver /dev/srnet. Its basic functions include<br />

• Strict real-time implementation of 3GPP Layers 1 (PHY) and 2 (MAC/RLC)<br />

• Adapted RRC signalling functionality to accommodate a set of mobile-IP management functions<br />

(information broadcast, attachment, resource requests, paging, etc.)<br />

The entities comprising the Radio Protocol Layers are collectively known as the Access Stratum (AS) in<br />

3GPP terminology, whereas entities in the IP backbone are collectively known as the Non-Access<br />

Stratum (NAS).<br />

D0103v1.doc 87 / 168

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!