ETSI TS 102 483-2008 Smart cards UICC-Terminal interface Internet Protocol connectivity between UICC and terminal《智能卡 UICC终端接口 UICC和终端V7 2 0之间的网络协议互联性 V7 2 0 第7版》.pdf

《ETSI TS 102 483-2008 Smart cards UICC-Terminal interface Internet Protocol connectivity between UICC and terminal《智能卡 UICC终端接口 UICC和终端V7 2 0之间的网络协议互联性 V7 2 0 第7版》.pdf》由会员分享，可在线阅读，更多相关《ETSI TS 102 483-2008 Smart cards UICC-Terminal interface Internet Protocol connectivity between UICC and terminal《智能卡 UICC终端接口 UICC和终端V7 2 0之间的网络协议互联性 V7 2 0 第7版》.pdf（21页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 102 483 V7.2.0 (2008-09)Technical Specification Smart cards;UICC-Terminal interface;Internet Protocol connectivity between UICC and terminal(Release 7)ETSI ETSI TS 102 483 V7.2.0 (2008-09) 2 Release 7 Reference RTS/SCP-T0311V72 Keywords smart card, internet, protocol ETSI 650 Route des Luci

2、oles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http

3、:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the pr

4、inting on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http

5、:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and

6、 the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2008. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mar

7、k of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 483 V7.2.0 (2008-09) 3 Release 7 Content Intellectual Property Rights4 Foreword.4 Introduction 4 1 Scope 5 2 References 5 2.1 Normative references .5 2.2 Informative references7 3 Definition

8、s and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .8 4 Terminal-UICC IP configuration .8 4.1 Local client on UICC .9 4.2 Local server on UICC.9 4.3 Remote client UICC .9 4.4 Remote server on UICC .10 5 Protocol Stack 11 6 UICC and Terminal components requirements12 6.1 UICC IP layer.12 6.1.1

9、IPv4 / IPv6 interworking.12 6.1.2 Address allocation 12 6.1.2.1 Local Connection 13 6.1.2.2 Remote Connection.13 6.1.2.2.1 IPv4 address allocation13 6.1.2.2.2 IPv6 address allocation13 6.2 Local naming13 6.2.1 Predefined names13 6.2.2 Names provided by the UICC.14 6.3 Summary of terminal and UICC co

10、nfiguration 15 6.3.1 UICC Configuration .15 6.3.1.1 IP v415 6.3.1.2 IP v615 6.3.2 Terminal Configuration 15 6.3.2.1 IP v415 6.3.2.2 IP v615 6.4 Terminal IP Components15 6.4.1 Connection setting 15 6.4.2 Routing, Network Address Translation and port forwarding16 Annex A (informative): Connection of a

11、 local equipment to the terminal and UICC .17 Annex B (informative): Definition of the connection activation parameters for common network technologies 18 Annex C (informative): Bibliography.19 Annex D (informative): Change history .20 History 21 ETSI ETSI TS 102 483 V7.2.0 (2008-09) 4 Release 7 Int

12、ellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Ri

13、ghts (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including

14、IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has bee

15、n produced by ETSI Technical Committee Smart Card Platform (SCP). The contents of the present document are subject to continuing work within TC SCP and may change following formal TC SCP approval. If TC SCP modifies the contents of the present document, it will then be republished by ETSI with an id

16、entifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 0 early working draft; 1 presented to TC SCP for information; 2 presented to TC SCP for approval; 3 or greater indicates TC SCP approved document under change control. y the second

17、digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document defines how an Internet Protocol connection may be establi

18、shed between a UICC and a terminal connected through aUICC-Terminal Interface able to carry Internet Protocol packets, and how the UICC resources defined in ETSI TS 102 221 11 may be accessed over this connection. Most telecommunication infrastructures rely on the Internet Protocol and therefore tel

19、ecommunication terminals commonly implement the IP layers as standardized by the IETF RFC 791 1 and by the new version in IETF RFC 2460 7. Connecting the UICC and the terminal at this level is expected to bring the following advantages: Leverage on existing standardization efforts: Applicative proto

20、cols relying on IP, e.g. running over TCP or UDP, have already been standardized for a wide variety of applications and may be used by UICC applications. Minimize UICC-specific developments on the terminals; reuse what is already available on terminals rather than forcing specific developments. Faci

21、litate connectivity of the UICC with standard network elements such as remote servers etc. The present document focuses on the establishment and configuration of a generic IP connection between the UICC and terminal, without addressing specific applications that may use this connection capability. E

22、TSI ETSI TS 102 483 V7.2.0 (2008-09) 5 Release 7 1 Scope The present document specifies the establishment and configuration of an Internet Protocol connection between a UICC and a terminal interfaced through a protocol that supports the transport of Internet Protocol packets. The way the Internet Pr

23、otocol packets (or similar packets such as ARP) are transported over the UICC-Terminal interface is part of the UICC-Terminal interface specification and not within the scope of the present document. The present document focuses on the configuration and establishment of the Internet Protocol connect

24、ion between the UICC and the terminal. The Internet Protocol connectivity defined in the present document may be used by applications such as the Smartcard Web Server i.7. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-s

25、pecific. For a specific reference, subsequent revisions do not apply. In the case of a reference to a TC SCP document, a non specific reference implicitly refers to the latest version of that document in the same Release as the present document. Non-specific reference may be made only to a complete

26、document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references, the latest version applies. In the case of a reference to an TC SCP

27、document, a non specific reference implicitly refers to the latest version of that document in the same Release as the present document. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. For online referenced

28、 documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the documen

29、t. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their lo

30、ng term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) app

31、lies. 1 IETF RFC 791: “Internet Protocol“. NOTE: Available from http:/www.ietf.org/rfc/rfc791.txt. 2 IETF RFC 826: “An Ethernet Address Resolution Protocol“. NOTE: Available from http:/www.ietf.org/rfc/rfc826.txt. 3 IETF RFC 792: “Internet Control Message Protocol“. ETSI ETSI TS 102 483 V7.2.0 (2008

32、-09) 6 Release 7 NOTE: Available from http:/www.ietf.org/rfc/rfc792.txt. 4 IETF RFC 793: “Transmission Control Protocol“. NOTE: Available from http:/www.ietf.org/rfc/rfc793.txt. 5 IETF RFC 2449: “POP3 Extension Mechanism“. NOTE: Available from http:/www.ietf.org/rfc/rfc2449.txt. 6 IETF RFC 1122: “Re

33、quirements for Internet Hosts - Communication Layers“. NOTE: Available from http:/www.ietf.org/rfc/rfc1122.txt. 7 IETF RFC 2460: “Internet Protocol, Version 6 (IPv6)Specification“. NOTE: Available from http:/www.ietf.org/rfc/rfc2460.txt. 8 IETF RFC 2463: “Internet Control Message Protocol (ICMPv6)fo

34、r the Internet Protocol Version 6 (IPv6) Specification“. NOTE: Available from http:/www.ietf.org/rfc/rfc2463.txt. 9 IETF RFC 3022: “Traditional IP Network Address Translator (Traditional NAT)“. NOTE: Available from http:/www.ietf.org/rfc/rfc3022.txt. 10 IETF RFC 3314: “Recommendations for IPv6 in Th

35、ird Generation Partnership Project (3GPP) Standards“. NOTE: Available from http:/www.ietf.org/rfc/rfc3314.txt. 11 ETSI TS 102 221: “Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 7)“. 12 IETF RFC 2461: “Neighbor Discovery for IP Version 6 (IPv6)“. NOTE: Available

36、 from http:/www.ietf.org/rfc/rfc2461.txt. 13 IETF RFC 2462:“IPv6 Stateless Address Autoconfiguration“. NOTE: Available from http:/www.ietf.org/rfc/rfc2462.txt. 14 IETF RFC 4294: “IPv6 Node Requirements“. NOTE: Available from http:/www.ietf.org/rfc/rfc4294.txt. 15 IETF RFC 4291: “IP Version 6 Address

37、ing Architecture“. NOTE: Available from http:/www.ietf.org/rfc/rfc4291.txt. 16 IETF RFC 2136: “Dynamic Updates in the Domain Name System (DNS UPDATE)“. NOTE: Available from http:/www.ietf.org/rfc/rfc2136.txt 17 IETF RFC 1035: “Domain names - Implementation and Specification“. NOTE: Available from ht

38、tp:/www.ietf.org/rfc/rfc1035.txt 18 IETF RFC 3490: “Internationalizing Domain Names in Applications (IDNA)“. NOTE: Available from http:/www.ietf.org/rfc/rfc3490.txt ETSI ETSI TS 102 483 V7.2.0 (2008-09) 7 Release 7 2.2 Informative references The following referenced documents are not essential to th

39、e use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. i.1 IETF RFC 2060: “Internet Message Access Protocol“, version 4rev1. NOTE: Available from h

40、ttp:/www.ietf.org/rfc/rfc2060.txt. i.2 IETF RFC 2246: “The TLS Protocol“, version 1.0. NOTE: Available from http:/www.ietf.org/rfc/rfc2246.txt. i.3 IETF RFC 2616: “Hypertext Transfer Protocol - HTTP/1.1“. NOTE: Available from http:/www.ietf.org/rfc/rfc2616.txt. i.4 IETF RFC 959: “File Transfer Proto

41、col (FTP)“. NOTE: Available from http:/www.ietf.org/rfc/rfc959.txt. i.5 IETF RFC 821: “Simple Mail Transfer Protocol“. NOTE: Available from http:/www.ietf.org/rfc/rfc821.txt. i.6 IETF RFC 1034: “Domain Names - concepts and facilities“. NOTE: Available from http:/www.ietf.org/rfc/rfc1034.txt. i.7 OMA

42、-TS-Smartcard-Web-Server-V1-0. NOTE: Available from http:/www.openmobilealliance.org. i.8 IETF RFC 768: “User Datagram Protocol“. NOTE: Available from http:/www.ietf.org/rfc/rfc768.txt. i.9 ETSI TS 102 223: “Smart Cards; Card Application Toolkit (CAT)“. i.10 ETSI TS 131 111: “Digital cellular teleco

43、mmunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Universal Subscriber Identity Module (USIM) Application Toolkit (USAT); (3GPP TS 31.111)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions

44、apply: application: computer program that defines and implements a useful functionality on a smart card or in a terminal NOTE: The term may apply to the functionality itself, to the representation of the functionality in a programming language, or to the realization of the functionality as executabl

45、e code. file: directory or an organized set of bytes or records in the UICC ETSI ETSI TS 102 483 V7.2.0 (2008-09) 8 Release 7 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: APDU Application Protocol Data Unit ARP Address Resolution ProtocolASCII Americ

46、an Standard Code for Information Interchange DHCP Dynamic Host Configuration Protocol FTP File Transfer Protocol HTTP HyperText Transport Protocol ICC Integrated Circuit Card ICMP Internet Control Message Protocol IMAP Internet Message Access Protocol IEC International Electrotechnical Commission IP

47、 Internet Protocol ISO International Organization for Standardization NAT Network Address TranslationPOP Post Office Protocol RARP Reverse Address Resolution Protocol RFU Reserved for Future Use RST ReSeTSE Security Environment HTTPS Secure HyperText Transport Protocol SMTP Simple Mail Transfer Prot

48、ocol SSL Secure Sockets Layer TCP Transmission Control Protocol TLS Transport Layer Security TPDU Transfer Protocol Data Unit UDP User Datagram Protocol URI Universal Resource Identifier URL Universal Resource Locator USIM Universal Subscriber Identity Module 4 Terminal-UICC IP configuration This se

49、ction is an introduction to the various configurations and uses of the IP UICC. A UICC supporting IP will be deployed with at least a local address. This address relates to a private network established between the UICC and the terminal, independently from other networks to which the terminal may be connected. The UICC shall be able to act as a combination of the following basic configurations: A TCP/IP or UDP/IP client of a server located on the terminal. A TCP/IP or UDP/IP