1 / 44

System Integration

Yves LaCerte Rockwell Collins ylacerte@rockwellcollins.com (952) 826-0080. Cognitive Radio. System Integration. System Integration. What is System Integration?. Integration is Hard. Cognitive Radio.

chandler-sanders
Download Presentation

System Integration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Yves LaCerte Rockwell Collins ylacerte@rockwellcollins.com (952) 826-0080 Cognitive Radio System Integration

  2. System Integration Yves LaCerte

  3. What is System Integration? Yves LaCerte

  4. Integration is Hard Yves LaCerte

  5. Cognitive Radio Scientific American, February, 2006 http://www.sciam.com/article.cfm?id=000C7B72-2374-13F6-A37483414B7F0000 “A Public Safety Cognitive Radio Node” http://www.sdrforum.org/SDR08/3.3-2.pdf “A Policy Proposal to Enable Cognitive Radio for Public Safety and Industry in the Land Mobile Radio Bands”, http://www.netcityengineering.com/PID354224.pdf Yves LaCerte

  6. Scenarios • Urban agencies need to communicate with each other • New York City police and fire departments during 9/11 were not successful • Federal, state and local level responders need to communicate • Katrina response was less than successful Yves LaCerte

  7. The Problem • “Spectrum“ is regulated (e.g. FCC) • Assigned/licensed to users • On a long term basis • For large regions like whole countries Yves LaCerte

  8. A Solution • Cognitive Radio • Senses and is aware of its environment • Dynamically adapts to utilize changing radio resources • Maintains connectivity with its peers • Does not interfere with licensed users and other CRs Yves LaCerte

  9. Yves LaCerte

  10. Timeline Yves LaCerte

  11. Basic Non-Cognitive Radio Architecture: CR Architecture • Cognitive Radio architecture: Yves LaCerte

  12. Integration Challenge I Yves LaCerte

  13. Orient Establish Priority Infer on Context Hierarchy Normal Plan Generate Alternatives (Program Generation) Evaluate Alternatives Pre-process Immediate Urgent Parse Register to Current Time Learn Observe New States Receive a Message Decide Read Buttons Save Global States Prior States Alternate Resources Outside World Act Initiate Process(es) (Isochronism Is Key) Send a Message Set Display The Cognition Cycle Machine Learning Mitola, “Cognitive Radio for Flexible Mobile Multimedia Communications”, IEEE Mobile Multimedia Conference, 1999, pp3-10 Yves LaCerte

  14. Advantages Yves LaCerte

  15. Disadvantages Yves LaCerte

  16. Integration Challenge II • Unlike traditional interferers, cognitive radios adapt their operation in response to their perceived interference environment. When numerous cognitive radios are collocated, this interference environment may be constantly changing as the cognitive radios adapt to the other cognitive radios adaptations. Because of this recursive process, serious concerns are introduced: • Under what conditions will the recursions settle down to a steady state? • What is that steady-state? • Will the resources be hoarded by a single radio/link or will they be equitably shared among the radios? • Will the cognitive radios actually make use of available spectrum without impinging on other radios’ spectrum rights? • How much bandwidth will be consumed with signaling overhead and how much bandwidth will actually be used for data transfer? Yves LaCerte

  17. Yves LaCerte

  18. A Typical Integration Example Collect Hardware Components Human Systems Integration Integrate Hardware Platform Test System Interfaces User Acceptance Test Configurations Integrate Software on Target Hardware Stress Factory Acceptance Collect Software Components Resolve Issues Yves LaCerte

  19. Human Systems Integration Yves LaCerte

  20. Integration Trends Yves LaCerte

  21. Integration Trends Yves LaCerte

  22. Integration Trends Yves LaCerte

  23. Integration Trends Mechanical Fluidic BiPolar Parasitics Optical Thermal CMOS Digital Integration Inductance Behaviors Analog Materials MEMS Design Flow VLSI Design Flow Yves LaCerte

  24. Integration Trends Yves LaCerte

  25. Integration Trends Yves LaCerte

  26. Enterprise Integration Yves LaCerte

  27. Enterprise Integration Yves LaCerte

  28. Enterprise Integration Yves LaCerte

  29. Integrating Two Systems Yves LaCerte

  30. Yves LaCerte

  31. Integration is Hard • High degree of uncertainty • Design for integrability • Integration strategies • Emergent properties Yves LaCerte

  32. Uncertainties • System components are not available on time • Duration of integration is longer than planned • Cost of testing facilities is higher than planned Yves LaCerte

  33. Integration Planning Requirements Specification User Acceptance Test Plan User Acceptance Test System Specification Factory Acceptance Test Plan Factory Acceptance Test System Design System Integration Test Plan System Integration Test Detailed Design Sub-system Integration Test Plan Sub-system Integration Test Component Implementation Component Test Yves LaCerte

  34. Design for Integrability • Integration tends to be more successful with low coupling between components • Partitioning decisions are made early, often without integration in mind • Hardware software co-design • Merged integration approach Yves LaCerte

  35. Integration Strategies • Strategies • Big bang or Incremental • Horizontal or Vertical • Order of integration impacts efficiency • First come first integrated? • Foundational components with long lead time? Yves LaCerte

  36. Integration Strategy • Incremental integration • Scheduling and staging strategy • Components are developed at different times or rates, and integrated as they are completed • The alternative to incremental development is to develop the entire system with a "big bang" integration Yves LaCerte

  37. Integration Strategy Sub-system 2 Sub-system 1 Sub-system 2 Sub-system n Component 1 Component 2 Component m Yves LaCerte

  38. Integration Strategy Sub-system 2 Sub-system 1 Sub-system 2 Sub-system n Component 1 Component 1 Component 1 Component 2 Component m Yves LaCerte

  39. Emergent Properties • A new component is introduced and problems are found • Is it due to the relationship between the new component and the existing system? • Or does the new component cause the existing system to be used in a different way? • Did problems with the system exist BEFORE the component was added? Yves LaCerte

  40. We know quite a lot about integrating components (over which we may have little or no control) to form systems. Unplanned, unexpected, emergent behavior here… We know something about integrating individual systems (over which we may have little or no control) into systems of systems. System “B” We know very little about integrating an interoperable network of systems…the key distinction being that the network is unbounded (or very loosely bounded) and has no single controlling authority. “SYSTEM D” System “A” System “C” The State of Our Knowledge Yves LaCerte

  41. Unbounded Systems Yves LaCerte

  42. Interoperability Yves LaCerte

  43. Interoperability Challenges Yves LaCerte

  44. Game theory • Does the algorithm have a steady state? • What are those steady states? • Is the steady state(s) desirable? • What restrictions need to be placed on the decision update algorithm to ensure convergence? • Is the steady state(s) stable? Yves LaCerte

More Related