Network Working Group H. Deng Internet-Draft China Mobile Intended status: Standards Track February 17, 2008 Expires: August 20, 2008 Problem Statement and Requirement: Protocol between Mobile Access Point and Terminal draft-deng-gmp-ps-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on August 20, 2008. Copyright Notice Copyright (C) The IETF Trust (2008). Deng Expires August 20, 2008 [Page 1] Internet-Draft GMP PS February 2008 Abstract This document discusses the problem and requirement of the communication protocol between mobile access point and terminal. With the evolution of mobile communication, there are various kind of wireless communication technologies such as GSM, GPRS, WCDMA, LTE, WLAN, WiMAX, and TDS-CDMA et al. Each of these wireless communication has independent connection, mobility and configuration management. This document would like converge all these function into a common ground especially in the environment of multiple connections. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Multiple Network Connections . . . . . . . . . . . . . . . . . 4 2.1. Service requirement . . . . . . . . . . . . . . . . . . . 4 2.2. Routing issue for terminal . . . . . . . . . . . . . . . . 4 3. Reference Model . . . . . . . . . . . . . . . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 6. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 10 7.1. Normative References . . . . . . . . . . . . . . . . . . . 10 7.2. Informative References . . . . . . . . . . . . . . . . . . 10 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 Intellectual Property and Copyright Statements . . . . . . . . . . 13 Deng Expires August 20, 2008 [Page 2] Internet-Draft GMP PS February 2008 1. Introduction In the current wireless communication network, there are various kinds of selection around our environment, even in one mobile operator, there are several choices for subscriber to choose. It become obvious that mutiple connections have to be supported by mobile terminals. Current each individual wireless communication has independent connection commands and triggers, as well as mobility management and configuration. for example, 802.11 specifiy "Associate/Deassociate/ Reassociate", GSM specify "Channel Request", WCDMA/LTE/TDS-CDMA specify "RRC setup/release", and Wimax specify "MAC Ranging" et al. Mobile terminal normally use each specific interface to control its connection, mobility management and configurations et al. Terminal software have to study each interface characteristics. This phenomena become more serious after the request of terminal for multiple connections comes. There were some proposals to extend link layer to make a common ground for this operation, but it will cost to revise some chipset or kernel level. This make it hard to realize. But solution such as more high level interface and independent on link layer may meet the requirement. And it will be quite convenient for the mobile opreator to handle if the connection, mobility, and configuration management will be based on a common protocol which don't rely on link layer technology. Deng Expires August 20, 2008 [Page 3] Internet-Draft GMP PS February 2008 2. Multiple Network Connections multiple Network Connection has become obvious requirement for wireless data communications. Operator may think about efficient using radio resource. subscriber may think about different price for different connections. Some connections may be flat rate based, others may be transmitted packet based. Or some connection has better Quality of Service or no traffic filter exist. The multiple network connections for mobile terminal is shown in the figure below: x y v z xi | | | | | +-----+ +-----+ +-----+ +-----+ +-----+ | MAR |......| MAR |......| MAR |......| MAR |......| MAR | +-----+ +-----+ +-----+ +-----+ +-----+ `. : ,' `. : ,' `. : ,' `. : ,' `. : ,' `. : ,' `. : ,' `. : ,' v v v v v v | | | | | | +----------+ Move +----------+ | Terminal | ==========> | Terminal | +----------+ +----------+ When Terminal move around in the wireless environment, it may change multiple connections timely.Let's make a example for above figure, radio x and xi are the same type wireless link like LTE, and radio v is always connected like Wimax, radio y is WLAN and radio z is TDS- CDMA. when terminal make a movement, wireless connections will also changes, the routing and mobility management would better change accordingly. 2.1. Service requirement Different service may act independently when terminal has multiple connections. From the service provider point of view, they don't mandate that the application must handover to the second interface when it just start up. Some of service may keep orginal connection, and others may handover to the second interface. This kind of handover could happen both initiated by network or terminal itself. 2.2. Routing issue for terminal Current most default routing of the operating system will take the last connection after the second interface is up. This is the basic Deng Expires August 20, 2008 [Page 4] Internet-Draft GMP PS February 2008 requirement for terminal to support multiple interface routing. Deng Expires August 20, 2008 [Page 5] Internet-Draft GMP PS February 2008 3. Reference Model Assuming the name of protocol between terminal and access point is GMP (Generic Mobility Protocol) which would work in the various kind of wireless connections such as GSM, GPRS, WCDMA, LTE, WiFi, and TDS- CDMA et al. After the coding of each command for connections, mobility, and configuration, network or terminal could control each connection and mobility management based on a common language like the figure below. +------+------+------+------+------+-------+ | GMP Protocol | +------+------+------+------+------+-------+ | GMP Interface and Payload | +------+------+------+------+------+-------+ | Various Kinds of MAC layer and Protocol | +------+------+------+------+------+-------+ |GSM | GPRS |WCDMA | LTE | WiFi |TDSCDMA| +------+------+------+------+------+-------+ Each wireless technology essentially have independent control command and protocol, but that will not really interfer with configuration and mobility management until GMP based command come. This is specially happen when network or terminal would like to have new interface connectioned or make happen for a mobility event +-----------------+ | +-----------------+ | | | | | | +-------------+ | | | +-------------+ | | | GMP | | GMP | | GMP | | | |Connection | | | | |Connection | | | |Configuration| | | | |Configuration| | | |Mobility |(------|------)|Mobility | | | +-------------+ | | | +-------------+ | | | | | | | | | +-------------+ | | | +-------------+ | | | Driver | | | | | Driver | | | | MAC | | Radio/MAC | | MAC | | | | Phy |(------|------)| Phy | | | +-------------+ | | | +-------------+ | | | | | | | MN | | | AP | +-----------------+ | +-----------------+ Deng Expires August 20, 2008 [Page 6] Internet-Draft GMP PS February 2008 4. Security Considerations The protocol between terminal and wireless access point could be protected by wirless protection mechanism since most of wireless communication is based on P2P connections, in the case of shared link wireless connection, layer 2 or layer 3 based seucrity mechanism should be adopted. Deng Expires August 20, 2008 [Page 7] Internet-Draft GMP PS February 2008 5. IANA Considerations This document makes no requests to IANA. Deng Expires August 20, 2008 [Page 8] Internet-Draft GMP PS February 2008 6. Conclusion This draft discusses problem and requirement for protocol between terminal and mobile access point which would work as a basic command for connection, mobility and configuration. Deng Expires August 20, 2008 [Page 9] Internet-Draft GMP PS February 2008 7. References 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 7.2. Informative References [FLOW-RULES] Larsson, C., "Flow Distribution Rule Language for Multi- Access Nodes", November 2007, . [MIS-PS] Melia, T., "Mobility Services Transport: Problem Statement", November 2007, . [NETLMM-MM-MAG] Laganier, J., "Interface between a Proxy MIPv6 Mobility Access Gateway and a Mobile Node", Februray 2008, . [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003. [RFC3748] Aboba, B., Blunk, L., Vollbrecht, J., Carlson, J., and H. Levkowetz, "Extensible Authentication Protocol (EAP)", RFC 3748, June 2004. [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. [RFC4068] Koodli, R., "Fast Handovers for Mobile IPv6", RFC 4068, July 2005. [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, September 2007. [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless Address Autoconfiguration", RFC 4862, September 2007. [RFC4903] Thaler, D., "Multi-Link Subnet Issues", RFC 4903, June 2007. Deng Expires August 20, 2008 [Page 10] Internet-Draft GMP PS February 2008 [RFC5072] S.Varada, Haskins, D., and E. Allen, "IP Version 6 over PPP", RFC 5072, September 2007. Deng Expires August 20, 2008 [Page 11] Internet-Draft GMP PS February 2008 Author's Address Hui Deng China Mobile 53A,Xibianmennei Ave., Xuanwu District, Beijing 100053 China Email: denghui02@gmail.com Deng Expires August 20, 2008 [Page 12] Internet-Draft GMP PS February 2008 Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Deng Expires August 20, 2008 [Page 13]