인문학
사회과학
자연과학
공학
의약학
농수해양학
예술체육학
복합학
지원사업
학술연구/단체지원/교육 등 연구자 활동을 지속하도록 DBpia가 지원하고 있어요.
커뮤니티
연구자들이 자신의 연구와 전문성을 널리 알리고, 새로운 협력의 기회를 만들 수 있는 네트워킹 공간이에요.
논문 기본 정보
- 자료유형
- 학위논문
- 저자정보
- 지도교수
- Sungwon Lee
- 발행연도
- 2020
- 저작권
- 경희대학교 논문은 저작권에 의해 보호받습니다.
이용수3
초록· 키워드
상세정보 수정요청해당 페이지 내 제목·저자·목차·페이지정보가 잘못된 경우 알려주세요!
4차 산업혁명과 더불어 UAV(Unmanned Aerial Vehicle)은 지난 10년간 매우 빠르게 성장하였다. 이러한 성장과 함께 다양한 분야에서 UAV를 활용한 연구들이 진행되고 있다. UAV는 한 기의 기체만 운용하는 경우보다 여러 기의 기체를 활용할 경우 더 경제적이고 효과적이다. 일반적으로 UAV는 데이터를 수집하고 그 정보를 Control Center로 전송하고 Control Center로 부터 제어 명령을 받아 행동한다. 이때 UAV와 Control Center 간의 통신은 주로 RF, Bluetooth, Wi-Fi, Cellular 등의 module을 이용하여 이루어진다. 하지만 여러 대의 UAV가 Control Center와 직접적으로 통신하게 되는 경우 통신 기술들의 한계점과 노드가 증가할 경우 생기는 문제점 등이 발생하게 된다. 이러한 점들을 해결하기 위한 연구들이 진행되었다. 여러 연구들에서 UAV들의 ad-hoc network를 구성하여 Wi-Fi,Bluetooth의 통신 범위의 제약이나 cellular의 고비용 문제를 해결하였다. 하지만 기존의 연구들은 ad-hoc network의 고정된 topology를 구성하였다. 이러한 연구들은 UAV의 빠른 이동성과 잦은 대형변경으로 인한 네트워크 토폴로지의 변경 문제점을 해결하지 못하였다. 이는 UAV의 대형 변경을 고려하지 않아 구성된 토폴로지의 대형으로만 이동해야 하는 한계점이 존재하였다.
본 논문에서는 이를 해결하기 위해 UAV Swarm의 동적인 토폴로지 구성 프로토콜에 대해 제안한다. 본 논문의 주요 내용은 다음과 같다. 먼저 기존의 UAV 통신에 대한 연구와 한계점에 대해 알아본 후 이를 해결하기 위한 프로토콜을 제시한다. 본 논문에서 제안하는 것은 여러 대의 UAV를 이용하여 미션을 수행하려 할 때 해당 UAV들이 어떻게 Ad-hoc Network를 구성하는 지에 대한 프로토콜이다. 또한 Network를 구성한 후 비행 대형의 변경으로 인해 Network Topology가 변경되었을 때 변화한 네트워크 토폴로지가 어떤 과정을 통해 재구성되는지에 대해 설명한다. 마지막으로 상황을 설정하고 제안한 프로토콜을 적용하여 그에 대한 실험을 진행한다. 이후 그에 대한 결과를 분석하고 향후 필요한 연구에 대해 기술한다.
본 논문에서는 이를 해결하기 위해 UAV Swarm의 동적인 토폴로지 구성 프로토콜에 대해 제안한다. 본 논문의 주요 내용은 다음과 같다. 먼저 기존의 UAV 통신에 대한 연구와 한계점에 대해 알아본 후 이를 해결하기 위한 프로토콜을 제시한다. 본 논문에서 제안하는 것은 여러 대의 UAV를 이용하여 미션을 수행하려 할 때 해당 UAV들이 어떻게 Ad-hoc Network를 구성하는 지에 대한 프로토콜이다. 또한 Network를 구성한 후 비행 대형의 변경으로 인해 Network Topology가 변경되었을 때 변화한 네트워크 토폴로지가 어떤 과정을 통해 재구성되는지에 대해 설명한다. 마지막으로 상황을 설정하고 제안한 프로토콜을 적용하여 그에 대한 실험을 진행한다. 이후 그에 대한 결과를 분석하고 향후 필요한 연구에 대해 기술한다.
목차
- Abstract ····································································································1. Introduction ························································································· 12. Related Works ······················································································ 32.1 UAV Wireless Communications ························································· 32.2 UAV Swarm Research ···································································· 52.3 Mobile Ad Hoc Network ································································· 53. Proposal ······························································································ 73.1 Dynamic Topology Reconstruction Protocol ········································· 73.1.1 Goal of DTRP ········································································· 83.1.2 Architecture and Components of DTRP ··········································· 73.2 Topology Reconstruction using DTRP ················································· 83.2.1 The Entire Process ··································································· 83.2.2 Base Topology Reconstruction Process ··········································· 83.2.3 Power On Registration ······························································ 103.2.4 Periodic Check Operation ·························································· 103.2.5 Control Commands Offer & Operation ··········································· 113.3 Message Format for a DTRP ···························································· 123.3.1 Init Message ·········································································· 123.3.2 Link Message ········································································ 123.3.3 ACK ·················································································· 123.3.4 Link Check Message ································································ 133.3.5 Error Message ······································································· 133.3.6 Control Offer & Operation Message ·············································· 134. Result ······························································································· 144.1 Simulation Environment ································································· 144.2 Testbed Scenario ·········································································· 164.2.1 Base Case ············································································· 164.2.2 Test Case 1 ··········································································· 184.2.3 Test Case 2 ··········································································· 194.2.4 Total Number of Messages per Case ·············································· 214.3 Comparison between Central Control System and Proposed System ·············· 225. Conclusion ························································································· 236. References ··························································································· 24