臺灣博碩士論文加值系統

在過去的幾年中，多媒體服務和其他資料密集服務的流量一直在快速成長，同時全世界的手機使用數量也不斷增加。這些現象讓近期在行動通訊網路上的研究也都以改善頻譜的使用效率與網路傳輸量為主要目標。而裝置間通訊(Device-to-device Communication; D2D Communication)被認為是一種很有前景的解決方案，其可達到提高無線資源使用效率、降低能量消耗、減輕基地台負擔並提供資料分流等優點。在長期演進技術(Long Term Evolution; LTE)網路中，D2D communication使用LTE的無線資源，並透過使用者設備(User Equipment; UE)上的LTE介面來發送和接收D2D communication。由於目前每個UE只配備了一個LTE介面，所以當有人播電話給正在進行的D2D communication的UE時會發生一個嚴重的問題，因為目前UE的LTE介面被D2D communication占用，所以UE無法及時接收來自核心網路(Core Network)傳來的來電通知。為了要解決此問題，我們提出了一個D2D連線管理機制，並利用UE的其他介面和D2D連線來傳遞來電通知。除此之外，我們更進一步採取上述的連線管理機制的概念，在網頁即時通訊(Web Real-Time Communicaiton; WebRTC)的環境實作出一個可以支援D2D功能的連線機制。

In the past few years multimedia and other data intensive traffic have been growing rapidly, as well as the number of mobile phones in usage through the world. Recent advances have been motivated towards improving spectral efficiency and throughput in cellular network. Device-to-device (D2D) communication is considered to be a promising solution to increase resource utilization, lower power consumption, ease base station load and provide data offloading. In the Long Term Evolution (LTE) network, the D2D communication technology reuses the radio resource and shares the LTE interface for the transmission and reception for D2D communications. However, because each UE is equipped with only one LTE interface, a serious problem may arise when someone is calling the user equipment (UE) in an ongoing D2D connection. Because the LTE interface is now being occupied by the D2D connection, the call notification from the core network cannot be timely received by the UE. To resolve this issue, we propose a connection management mechanism to route the call notification by utilizing other interfaces of
UE and the D2D connection. We further take advantage of the idea of the proposed mechanism and implement the connection functions in the Web Real-Time Communication (WebRTC) environment to support D2D features.

摘要 i
Abstract ii
誌謝 iii
Contents iv
List of Tables vi
List of Figures vii
1 Introduction 1
2 Related Work 3
2.1 Device-to-Device Communication . . . . . . . . . . . . . . . . . . . . . . . . 3
2.2 Session Initiation Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2.3 Web Real-Time Communication . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 Connection Management Mechanism for D2D Communication 8
3.1 Archirecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.2 IMS Registration Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3 D2D Resource Acquisition/Free Procedures . . . . . . . . . . . . . . . . . . . 10
3.4 D2D Registration/De-registration Procedures . . . . . . . . . . . . . . . . . . 12
3.5 Call Termination through D2D Connection . . . . . . . . . . . . . . . . . . . 13
4 Design and Implementation of D2D Connection Functions in WebRTC Environ-
ment 16
iv4.1 Archirecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.2 WebRTC Connection Establishment . . . . . . . . . . . . . . . . . . . . . . . 17
4.3 WebRTC Connection Switching between Direct and Indirect Link . . . . . . . 21
4.4 Interrupt Call Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
4.5 Mobility Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
5 Conclusions 28
Bibliography 30
A Implementation Source Codes 32

[1] P. Janis, C.-H. Yu, K. Doppler, C. Ribeiro, C. Witjing, K. Hugl, O. Tirkkonen, and
V. Koivunen, ”Device-to-Device Communication Underlaying Cellular Communications
Systems,” Int. J. Communications, Network and System Sciences, vol. 2, no. 3, pp. 169-
178, Mar. 2009.
[2] K. Doppler, M. P. Rinne, P. Janis, C. Ribeiro, and K. Hugl, ”Device-to-Device communica-
tions; functional prospects for LTE-Advanced networks,” IEEE International Conference
on Communications Workshops, pp. 1-6, June 2009.
[3] L. Lei, Z. Zhong, C. Lin, and X. Shen, ”Operator controlled device-to-device communi-
cations in LTE-advanced networks,” IEEE Wireless Communications, vol. 19, no. 3, pp
96-104, June 2012.
[4] X. Lin, J. G. Andrews, A. Ghosh, and R. Ratasuk, ”An Overview on 3GPP Device-to-
Device Proximity Services,” IEEE Communications Magazine, 2013.
[5] 3GPP, 3rd Generation Partnership Project; Technical Specification Group Services and
System Aspects; Feasibility study for Proximity Services (ProSe) (Release 12), Technical
Report 3GPP TR 22.803 V12.2.0, 2013.
[6] 3GPP, 3rd Generation Partnership Project; Technical Specification Group Services and
System Aspects; Study on architecture enhancements to support Proximity-based Services
(ProSe) (Release 12), Technical Report 3GPP TR 23.703 V1.0.0, 2013.
[7] P. Janis, V. Koivunen, C. Ribeiro, J. Korhonen, K. Doppler, and K. Hugl, ”Interference-
Aware Resource Allocation for Device-to-Device Radio Underlaying Cellular Networks,”
Vehicular Technology Conference, pp1-5, Apr. 2009.
[8] S. Vasudevan, K. Sivanesan, S. Kanugovi, and J. Zou, ”Enabling Data Offload and Proxim-
ity Services using Device to Device communication over licensed cellular spectrum with
infrastructure control,” Vehicular Technology Conference, pp 1-7, Sept. 2013.
[9] B. Raghothaman, E. Deng, R. Pragada, G. Sternberg, T. Deng, and K. Vanganuru, ”Ar-
chitecture and protocols for LTE-based device to device communication,” International
Conference on Computing, Networking and Communications (ICNC), pp 895-899, Jan.
2013.
[10] Y.-B. Lin, A.-C. Pang, Wireless and Mobile All-IP Networks. John Wiley &; Sons, Inc.,
2005.
[11] J. Rosenberg, H. Schulzrinne, G. Camarillo, A. Johnston, J. Peterson, R. Sparks, M. Han-
dley, and E. Schooler. SIP: Session Initiation Protocol, RFC 3261, IETF, June 2002.
[12] S. Loreto, and S. P. Romano, ”Real-Time Communication in the Web: Issue, Achieve-
ments, and Ongoing Standardization Efforts,” IEEE Internet Computing, vol. 16, no.5, pp
68-73, 2012.
[13] E. Bertin, S. Cubaud, N. Crespi, and V. Beltran, ”WebRTC, the day after: What’s next for
conversational services?,” International Conference on Intelligence in Next Generation
Networks (ICIN), pp 46-52, Oct. 2013
[14] WebRTC Demo Application - AppRTC. https://apprtc.appspot.com/.
[15] rfc5766-turn-server. https://code.google.com/p/rfc5766-turn-server/.
[16] Node.js. http://nodejs.org/.