idnits 2.17.1 draft-liu-mwrmn-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (November 15, 2020) is 1248 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? 'RFC2119' on line 102 looks like a reference Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Y. Liu 3 Internet-Draft Xidian University 4 Expires: May 19, 2021 November 15, 2020 6 The Cooperative Communication Method of the Converged Multi-media 7 Wireless Resource Management Network 8 draft-liu-mwrmn-03 10 Abstract 12 This paper describes a cooperative communication method of 13 theconverged multi-media wireless resource management network.It can 14 maximize the utilization of heterogeneous network resources and 15 optimize the access to wireless resources of the network in the form 16 of Mesh, which solves the problem of collaborative wireless resource 17 management in multi-media converged networks. Through the overall 18 consideration of multi-media converged networks including wired 19 network, wireless network, broadband network, and narrowband network, 20 joint access control and resource scheduling for network devices with 21 different characteristics in heterogeneous networks are realized. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on May 19, 2021. 40 Copyright Notice 42 Copyright (c) 2020 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 1. Introduction 57 The rapid development of wireless network technology has not only 58 significantly improved network coverage, network capacity, 59 transmission rate, and service quality, but also presents the 60 development trend of diversification of access modes, higher speed of 61 data transmission, universal mobility and full IP integration. Being 62 different from wired communication, wireless transmission media are 63 uncertain and susceptible to unpredictable interferences such as 64 noise, multipath fading, and shadow effect. Moreover, the inherent 65 mobility of wireless transmission media also does harm to channel 66 prediction and channel estimation. It brings considerable problem, 67 which increases the bit error rate of the channel. In order to 68 ensure the availability of wireless communication, the conservative 69 design is often performed according to the requirements of the lowest 70 channel performance, rather than adaptively adjusting to adapt to the 71 communication channel. It makes the protocol stack unable to 72 effectively and reasonably utilize limited power resources and 73 spectrum resources. 75 However, existing wireless communication methods ignore the 76 correlation between the overall requirements of network design and 77 the functions of each layer. Each layer of the protocol stack is 78 designed and operated independently, and between layers and layers 79 only exist interfaces which are static and independent of the 80 limitation and application of each network layers. This rigorous 81 layering design method lacks flexibility, compatibility, and does not 82 fit well into the characteristics of today's networks. In the 83 practical network communication process, the information between 84 layers is difficult to share, which also adds a large number of 85 uncontrollable link overheads, information redundancy, and 86 communication overhead between peer layers. 88 The cooperative communication method of the converged multi-media 89 wireless resource management network described in the proposal can 90 easily solve these problems. It can change the link type and 91 facilitate cross-layer design, which not only realizes device 92 independence, but also achieves the effect communication between 93 high-level applications and underlying channels. 95 2. Conventions used in this document 97 2.1. Requirements Language 99 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 100 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 101 document are to be interpreted as described in RFC 2119 [RFC2119]. 103 2.2. Protocol Stack 105 The protocol stack, is a specific software implementation of the 106 computer network protocol suite. A protocol in a protocol suite is 107 usually designed for one purpose only, which makes the design easier. 108 Each protocol module can usually be treated as a layer in the 109 protocol stack, because it typically communicates with two other 110 protocol modules. The lowest level protocol always describes the 111 physical interaction with the hardware. The user applications only 112 handle the top-level protocols. 114 2.3. Wireless Pipe 116 Wireless Pipe - phytype = "atheros", refers to wireless mesh_Pipe 117 based on wlan_mwds; 119 2.4. Ethernet Pipe 121 Ethernet Pipe - phytype = "ethernet", refers to the two-layered wired 122 mesh_Pipe in the same broadcast domain; 124 2.5. Ip Tunnel Pipe 126 Ip_tunnel Pipe - phytype = "ip_tunnel" is used to establish a three- 127 layered mesh network across the LAN. It can be divided into two 128 modes: active one and non-active one according to different working 129 modes. 131 2.6. Ip Pipe 133 Ip Pipe - phytype = "ip", which refers to the ability to extend other 134 types of links based on the change of the three-layered wired 135 mesh_Pipe in the same broadcast domain. 137 3. Joint Access Control and Resource Scheduling 138 3.1. Unified Interface 140 The cooperative communication method of the converged multi-media 141 wireless resource management network can provide a unified standard 142 Ethernet interface to users by adapting to protocol specifications of 143 different media, so that coordination between network layer protocols 144 can improve the overall performance and efficiency of the wireless 145 network. 147 In practical applications, the protocol stack is usually divided into 148 three main parts: media, transmission, and application. A particular 149 operating system or platform often has two well-defined software 150 interfaces: one between the media layer and the transport layer and 151 the other between the transport layer and the application layer. 153 3.2. Different Assessment Standards 155 Different transmission quality assessment methods are adopted for 156 different media, which requires effective implementation of network 157 cross-layer radio resource management mechanism which assists in the 158 design of cross-layer optimal relay node selection algorithm in 159 cooperative relay network, and supports multi-hop self-organizing 160 network cross-layer routing. 162 4. Maximization of the Heterogeneous Network Resources Utilization Rate 164 4.1. Flexible Networking 166 The IP Pipe and IP Tunnel are designed to be ones that can change the 167 link type, which makes the network mode flexible. 169 4.2. Design Structure 171 Design structure: mesh - Pipe - link; 173 4.3. Service Interfaces 175 Pipe provides a standard Ethernet interface to Mesh. After being 176 configured in the configuration file G8000.xml, then the Ethernet 177 port can be treated as a Mesh Pipe. The type of the Box is 178 Relay/Mobile/Gateway (dual Ethernet port). While the Ethernet port 179 is used as the Mesh Pipe, it cannot be used as another role at the 180 same time, such as access users, etc. For example, the device is 181 connected to the Mesh Pipe through a standard Ethernet interface, and 182 the Mesh Pipe provides standard adaptation interface to the external 183 network. 185 4.4. Link Adaptation 187 The message format encapsulation and the transmission of 188 corresponding control instructions are chosen according to different 189 link transmission standards. 191 5. Classified Design of Mesh Pipe 193 Mesh Pipe's classified design technique is mainly showed in the power 194 control and adaptive modulation and demodulation control according to 195 the QoS requirements of MAC protocol, routing protocol, TCP protocol 196 and application layer services. 198 In the separate unit of a converged multi-media system, all Mesh Pip- 199 es will provide a unified Ethernet interface. 201 5.1. Design of Different Link Type 203 Two-layer and three-layer Pipe are designed according to different 204 link types. Set two-layer Pipes for Ethernet and link types "ethos". 205 Set three-layer Pipe for IP Tunnel. 207 --------------------------------------- | wired Pipe | fiber,covered 208 wire | --------------------------------------- |wireless 209 Pipe|scatter,radio,satellite| --------------------------------------- 211 5.2. Wired and Wireless Design 213 Designing wired and wireless Pipe is to set wired Pipe for fiber and 214 covered wire devices, and to set wireless Pipe for scatter, radio and 215 satellite devices, which achieves the wireless communication between 216 heterogeneous multi-media. 218 5.3. Broadband and Narrowband Design 220 Setting broadband Pipe and narrowband Pipe according to the practical 221 transmission rate of the device.A broadband Pipe is set for the fiber 222 devices, and a narrowband Pipe is set for the scattering and the 223 radio devices. 225 The structure can achieve multi-media convergence through the 226 application of Mesh Pipe, and provide a unified network interface for 227 business units, so the business units has the ability to cross media, 228 and the business units only need standard Ethernet port access. For 229 example, communication unit can be linked up to the converged multi- 230 media wireless communication system not only through the Mac layer 231 but also through the IP_tunnel Pipe using IP. Regardless of the 232 access, a unified standard Ethernet interface will be provided by the 233 converged multi-media wireless communication system. 235 ------------------------------- | broadband Pipe| fiber | 236 ------------------------------- |narrowband Pipe|scatter,radio| 237 ------------------------------- 239 6. Security Considerations 241 It is necessary to use the "network ID" to distinguish different ad 242 hoc networks. Only the ad hoc network node devices (hereinafter 243 referred to as nodes) configured with the same "network ID" can 244 discover each other. 246 Nodes in the same ad hoc network use a unified pre-configured static 247 key to encrypt the transmitted data. When the keys are different, 248 nodes cannot transfer data. Even if the eavesdropper acquires the 249 key seed by some means, he cannot get the final key. 251 And broadcast data packets and Mesh protocol packets are not 252 encrypted. 254 7. IANA Considerations 256 This document does not include an IANA request. 258 8. Acknowledgements 260 We would like to thank Shanghai zhige network communication 261 technology co., LTD for providing technical scheme verification 262 support. 264 Author's Address 266 Yi Liu 267 Xidian University 268 2 South Taibai Road 269 Xi'an, Shaanxi 710071 270 P.R.China 272 Email: yliu@xidian.edu.cn