idnits 2.17.00 (12 Aug 2021) /tmp/idnits2342/draft-zhang-mif-connection-manager-arena-00.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 issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 58 instances of too long lines in the document, the longest one being 5 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (February 27, 2009) is 4831 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: 'I-D.hui-ip-multiple-connections-ps' is defined on line 268, but no explicit reference was found in the text == Unused Reference: 'I-D.blanchet-mif-problem-statement' is defined on line 273, but no explicit reference was found in the text == Outdated reference: A later version (-02) exists of draft-hui-ip-multiple-connections-ps-01 == Outdated reference: A later version (-01) exists of draft-blanchet-mif-problem-statement-00 Summary: 3 errors (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force Y. Zhang 2 Internet Draft Leadcoretech 3 Intended status: Informational T. Sun 4 Expires: August 2009 China Mobile 5 H. Chen 6 February 27, 2009 8 Multi-interface Network Connection Manager in Arena Platform 9 draft-zhang-mif-connection-manager-arena-00.txt 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html 31 This Internet-Draft will expire on August 27, 2009. 33 Copyright Notice 35 Copyright (c) 2009 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents 40 (http://trustee.ietf.org/license-info) in effect on the date of 41 publication of this document. Please review these documents 42 carefully, as they describe your rights and restrictions with respect 43 to this document. 45 Abstract 46 This document presents a "Connection Manager" model implemented in 47 the platform Arena, a mobile OS based on Linux. The introduction of 48 Connection Manager brings two major benefits in Arena. First, it 49 logically decouples the underlining connection approach with the 50 connection management. Second, it plays a central role which executes 51 the policy of OS, especially for multiple interfaces. 52 Table of Contents 54 1. Introduction................................................2 55 2. Scenario....................................................2 56 3. Solution....................................................5 57 3.1. Work Flow..............................................5 58 3.2. Interface Reuse.........................................6 59 3.3. Link route consideration................................6 60 4. Conclusions.................................................7 61 5. References..................................................7 63 1. Introduction 65 In current practices, most of applications maintain network by 66 themselves. They directly connect to the network with given parameters 67 leading to the coupling of operation and network management in logic 68 level. Moreover, such type of mechanism does not meet variant 69 requirements in multiple interfaces situations. 71 This document presents a Network Connect Manager solution which 72 abstracts the network connect function to a class which can be used by 73 the functions to get connection management services. The access 74 approaches, parameter settings, management policies and connection 75 management solicitation processes are handled based on OS predefined or 76 application customized interface settings and are separate with the 77 Network Connect Manager. In this way, the connection link related 78 operations are separated with network management logically. This also 79 makes it possible to address multiple interface cases. 81 This document will illustrate the scenarios where connection manger 82 applies, the link management model and the procedure to use connection 83 mananger. 84 2. Scenario 86 There are three modes of interface selection as depicted in Figure 1. 88 These modes are summarized as follows. 90 UE +-------------------------+ 91 | +-----------------------+ | Default Wifi Internet | 92 | |Default Wifi Internet | |Connect Process | 93 | User Select |SSID:**** |======>|Disconnect Process | 94 |--------------->|Password:**** | |Link Status Query Process| 95 | |...... | |Parameter Setting Process| 96 | +-----------------------+ |Parameter Query Process | 97 | |...... | 98 | +-------------------------+ 99 | +-----------------------+ +-------------------------+ 100 | |Default GPRS Internet | | Default GPRS Internet | 101 |System automatic |Access Point Name:**** | |Connect Process | 102 |---------------->|User Name:**** | |Disconnect Process | 103 | select |Password:**** |=====>|Link Status Query Process| 104 | |Quality Of Service:****| |Parameter Setting Process| 105 | |...... | |Parameter Query Process | 106 | +-----------------------+ |...... | 107 | : +-------------------------+ 108 | : 109 | +------------------------+ +-------------------------+ 110 | |Customize GPRS WAP | | Customize GPRS WAP | 111 | |Default GPRS Internet | |Connect Process | 112 |User Customize |User Name:**** | |Disconnect Process | 113 |--------------->|Password:**** |=====>|Link Status Query Process| 114 | |Uplink Rate:**** | |Parameter Setting Process| 115 | |Downlink Rate:**** | |Parameter Query Process | 116 | |...... | |...... | 117 | +------------------------+ +-------------------------+ 118 Figure 1 There modes of interface selection 120 Interface Selection by an Application. If an application selects a 121 system default interface, it calls those default link management 122 service interfaces offered by the Network Connection Manager. 124 System Automatic Selection. If an application attempts to get 125 connected without specific requirements, the system will evaluate 126 various factors such as bandwidth, cost, stability, then select an 127 interface automatically for the application. 129 Creating New Interface based on Requirements. When all default 130 interfaces can't meet the requirement of an application, the 131 application can customize a new connect interface and configure 132 the connection parameters, define the detailed processes such as 133 connect, disconnect, status query, parameter settings and query. 134 Then the interface is registered to the Connection Manager. In 135 this way, a new interface is created and can be used as other 136 interfaces in Connection Manager. 138 Figure 2 illustrates the mechanism of Connection Manager model. All the 139 interfaces must register with the Connection Manager and link manage 140 operations carry out via the multiple network connect interfaces. 142 Interfaces 143 +--------+ +-------+ || 144 +-----+ Select |Default | Register | | || 145 |App 1|-------->|GPRS |--------->| |--Connect-->|| 146 +-----+ |MMS | | | Disconnect ||G 147 +--------+ |Network| ||P 148 +-----+ Selec +--------+ | | ||R 149 |App 2|-------->|Default | Register | | ||S 150 +-----+ |GPRS |--------->| |--Connect-->|| 151 |Internet| | | Disconnect || 152 +--------+ | | || 153 : : |Connect| || 154 : : | | || 155 +---------+ | | || 156 +-------+Select |Customize| Register| | || 157 |App n-1|------>|GPRS |-------->| |--Connect-->||C 158 +-------+ |Internet | |Manager| Disconnect ||S 159 +---------+ | | ||D 160 | | || 161 | | || 162 +---------+ | | ||W 163 +-----+ Select |Customize| Register| | ||i 164 |App n|-------->|Wifi |-------->| |--Connect-->||f 165 +-----+ |Internet | | | Disconnect ||i 166 +---------+ +-------+ ||: 168 Figure 2 Network Connection Manager Model 170 3. Connection Manager 172 3.1. Work Flow 174 Figure 3 demonstrates the working flow of the Network Connection 175 Manager. In the figure an application select a default interface 176 named "Default GPRS Internet" to connect with the network. 178 Application Socket Interface Connection Manager 179 | | | | 180 | Select Default | | | 181 (1) |------GPRS Interface-----|----------->| | 182 | | | | 183 (2) | | |----Interface Register--->| 184 | | | | 185 (3) |-------------- Connect Request(Default GPRS Internet)----------->| 186 | | | | 187 (4) | | |<---Call Connect Process--| 188 | | | | 189 (5) |<------------------------|------------|------Connect Response----| 190 | | | | 191 (6) |-------Create Socket---->| | | 192 | | | | 193 (7) |-------Bind Socket------>| | | 194 | | | | 195 | Normal Socket | | | 196 (8) |<-----Communication----->| | | 197 | | | | 198 (9) |-----Close Socket------->| | | 199 | | | | 200 | | | | 201 (10)|------------ Disconnect|Request(Default GPRS Internet)---------->| 202 | | | | 203 (11)| | |<-Call Disconnect Process-| 204 | | | | 205 (12)|<------------------------|------------|--Disconnect Response-----| 206 | | | | 207 | | | | 209 Figure 3 Network Connection Manager Work Flow 211 The steps are listed as below: 213 1) An application selects a default interface named "Default GPRS 214 Internet" to connect with network; 216 2) The Default GPRS Internet interface registers with the 217 Connection Manager; 219 3) An application requests the Connection Manager to connect with 220 network via Default Network Interface connect interface; 222 4) When the Connection Manager receives the request of connection, 223 the Connection Manager will select one interface according to 224 the parameter required. The implementation of the interface on 225 connection is called to establish link for network access. 227 5) The Connection Manager informs the success of connection to the 228 application and saves the information about this link such as 229 PDP context, IP address, DNS etc.; 231 6) From step (6) to step (9), the application creates a socket and 232 binds it with the IP address of the active link. The 233 communication is established via the socket. The socket will be 234 closed at the end of the communication. 236 7) The disconnect procedures from step(10) to (12) are similar as, 237 previous procedures for connection establishment. 239 Note: In the case of interface customization, a new interface 240 should be created through configuring parameters and implement 241 network management at step (1). 243 3.2. Interface Reuse 245 The Connection Manager has the ability to make connections work 246 simultaneously. Multiple applications can share a connect interface 247 at the same time. In such situations, operations such as link 248 establish and disconnect will be shared. 250 3.3. Link route consideration 252 Under the circumstance that multiple interfaces are connected 253 simultaneously, applications should bind socket with IP address of 254 the corresponding interface to make sure that each socket created by 255 every application exactly communicate via its respective link and 256 route. 258 4. Conclusions 260 The Connection Manager model in Arena platform improves the 261 efficiency for application developers and makes it convenient to 262 manage connections over variant network resources. Further work will 263 be conducted on link resource management, task scheduling and policy 264 control. 266 5. Informative References 268 [I-D.hui-ip-multiple-connections-ps] Hui, M. and H. Deng, "Problem 269 Statement and Requirement of Simple IP Multi-homing of the 270 Host", draft-hui-ip-multiple-connections-ps-01 (work in 271 progress), November 2008. 273 [I-D.blanchet-mif-problem-statement] Blanchet, M., "Multiple 274 Interfaces Problem Statement", draft-blanchet-mif-problem- 275 statement-00 (work in progress), December 2008. 277 Authors' Addresses 279 Yan Zhang 280 Leadcoretech Ltd. 281 333,qinjiang Ave., 282 Xuhui District, 283 Shanghai 200233 284 China 285 Email: zhangyan4@leadcoretech.com 287 Tao Sun 288 China Moible 289 53A,Xibianmennei Ave., 290 Xuanwu District, 291 Beijing 100053 292 China 293 Email: suntao@chinamobile.com 295 Hua Chen 296 Leadcoretech Ltd. 297 333,qinjiang Ave., 298 Xuhui District, 299 Shanghai 200233 300 China 301 Email: chenhua@leadcoretech.com