System Architecture Design

More documents

Recommendations

Info

pSHIELDSystem Architecture DesignPU3.1.2.2.2 New CLA3.1.2.2.2.1 Cross-Layer Interaction ModelThe cross-layer architectures proposed in the literature do not address all the design goals ofinteroperability, rapid prototyping, maintainability, portability and efficiency. Starting from thisconsideration, the goal of this work is to provide a generic framework for building and organizing a crosslayerinteractions model (CLIM) which could serve as a unified and simple way to implement cross-layeroptimizations (see Figure 5). When using CLIM, the concept of NF (Network Feature) should also beintroduced. A NF is either a functional service that can be provided to the end-user (e.g. QoS), or anetwork component whose operations/configurations are supposed to be critical in terms of performance,efficiency or services, at the system level or for the user satisfaction. Basically, cross-layer interactionsmay be local to or distant within a network node.In many cases only two elementary NF are involved in the adaptation and interaction (one source NF, onetarget NF). In some other cases multiple (local or distant) entities could participate. Local communicationsbetween protocols of non-neighbour layers are done through a local interface that must be defined.Figure 5 - Proposed Cross-Layer Interaction ModelThe cross-layer architecture and interaction module CLIM has two main components: 1) QoS andResource Management and 2) Mobility Management. The QoS and Resource Management componentincludes:• SIP and MAC cross-layer interactions used to support the interworking between WiMAX andDVB-RCS and multimedia QoS-aware application• Transport layer and MAC cross-layer interaction (i.e. the interaction between TCP PEP(Performance Enhancing Proxy) and DAMA (Demand Assignment Multiple Access) in the MAC)PUD2.3.2Issue 5 Page 22 of 122
pSHIELDSystem Architecture DesignPUdesigned to optimize the way in which the available resources is used taking into account QoSmapping at the MAC layer and enabling data to be sent to the lower layers at the speed at whichthe MAC layer queues are emptied (flow-control)• IP and MAC scheduling interaction implemented in a way that can fully take advantage of QoScapabilities offered by the satellite system• MAC and Physical layer interaction between DRA and DAMA as information in the frameconstitutionThe Mobility Management component utilizes a slightly modified model (CLIM-m) based on the moregeneric CLIM architecture together with ideas from [17], [18]. The mobility management modules include:• algorithms for handover prediction and decision algorithms for fast handover with handoverpreparation, handover coordination and optimization algorithms for best performance, and• information to decide the appropriate time to initiate and execute the handover procedures.The proposed cross-layer platform for mobility management specifies a Cross-layer Manager consisting ofa Link Information Manager and a Handover Manager connected to Layer Agents (LA). The HandoverManager communicates with multiple protocol layers via the LAs which capture specified parameters ineach layer when the respective values are changing beyond a certain threshold. These data are reportedto the Handover Manager to collect sufficient information for the Handover Decision Unit.3.1.2.3 ChallengesThere are additionally several open questions, some of which cannot be addressed from a performanceviewpoint alone and require a consideration of architectural concerns too. For example:• What should be the role of the physical layer in wireless networks?• Is the conventional view of the network—that of a collection of point-to-point links—appropriate forwireless networks?• How do the different cross-layer design proposals co-exist with one another?• Will a given cross-layer design idea possibly stifle innovation in the future?• What are the cross-layer designs that will have the most significant impact on networkperformance, and hence should be most closely focused on?• Has a given design proposal been made with a thorough knowledge of the effect of theinteractions between the parameters at different layers on network performance?• Under what network and environmental conditions can a particular cross-layer design proposal beinvoked?• Can the mechanisms/interfaces used to share information between the layers be standardized?• How do we make sure that the new architectures allow innovative usage of the wireless mediumthat we are likely to see in the future?We will investigate at some of these issues in greater detail.3.1.2.4 Description of LayersPUD2.3.2Issue 5 Page 23 of 122
Page 1 and 2: Project no: 100204pSHIELDpilot embe
Page 3 and 4: Contents1 Executive Summary .......
Page 5 and 6: FiguresFigure 1 - A generic embedde
Page 7 and 8: Figure 45 - pSHIELD Security Agent
Page 9 and 10: MGFMIPSMLNeLNFMRFPNMPNMPSNoLNVMOLOS
Page 11 and 12: Issue 5Page xi
Page 13 and 14: pSHIELDSystem Architecture DesignPU
Page 19 and 20: pSHIELDSystem Architecture Design3.
Page 21: pSHIELDSystem Architecture DesignPU
Page 31 and 32: pSHIELDSystem Architecture Design
Page 39 and 40: pSHIELDSystem Architecture Design
Page 47 and 48: pSHIELDSystem Architecture Designen
Page 73 and 74:
pSHIELDSystem Architecture DesignPU
Page 75:
Page 80 and 81:
Page 82:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
show all

System Architecture Design

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?