1、 ETSI TS 102 483 V7.3.0 (2009-01)Technical Specification Smart cards;UICC-Terminal interface;Internet Protocol connectivity between UICC and terminal(Release 7)ETSI ETSI TS 102 483 V7.3.0 (2009-01)2Release 7 Reference RTS/SCP-T0311v730 Keywords smart card, internet, protocol ETSI 650 Route des Lucio
2、les 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 pri
4、nting 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 2009. 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 Mark
7、 of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association.
8、 ETSI ETSI TS 102 483 V7.3.0 (2009-01)3Release 7 Content Intellectual Property Rights 4g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 7g33 Definitions and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 8g34 Terminal-UICC
9、 IP configuration . 8g34.1 Local client on UICC . 9g34.2 Local server on UICC . 9g34.3 Remote client UICC . 9g34.4 Remote server on UICC . 10g35 Protocol Stack 11g36 UICC and Terminal components requirements 12g36.1 UICC IP layer . 12g36.1.1 IPv4 / IPv6 interworking . 12g36.1.2 Address allocation 12
10、g36.1.2.1 Local Connection 13g36.1.2.2 Remote Connection . 13g36.1.2.2.1 IPv4 address allocation 13g36.1.2.2.2 IPv6 address allocation 14g36.2 Local naming 14g36.2.1 Predefined names 14g36.2.2 Names provided by the UICC . 14g36.3 Summary of terminal and UICC configuration 15g36.3.1 UICC Configuratio
11、n . 15g36.3.1.1 IP v4 15g36.3.1.2 IP v6 15g36.3.2 Terminal Configuration 15g36.3.2.1 IP v4 15g36.3.2.2 IP v6 15g36.4 Terminal IP Components 16g36.4.1 Connection setting 16g36.4.2 Routing, Network Address Translation and port forwarding 16g3Annex A (informative): Connection of a local equipment to th
12、e terminal and UICC 17g3Annex B (informative): Definition of the connection activation parameters for common network technologies . 18g3Annex C (informative): Bibliography . 19g3Annex D (informative): Change history . 20g3History 21g3ETSI ETSI TS 102 483 V7.3.0 (2009-01)4Release 7 Intellectual Prope
13、rty 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 Rights (IPRs); Es
14、sential, 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 IPR searches, h
15、as 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 been produced by E
16、TSI 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 identifying chang
17、e 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 digit is increm
18、ented 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 established between a
19、UICC and a terminal connected through a UICC-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 telecommunication
20、 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 protocols relying o
21、n 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. Facilitate connect
22、ivity 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. ETSI ETSI TS 10
23、2 483 V7.3.0 (2009-01)5Release 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 Protocol packets (
24、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 connection between the
25、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-specific. For a s
26、pecific 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 document or a pa
27、rt 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 document, a non
28、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. NOTE: While any hyperlinks included i
29、n this clause were valid at the time of publication ETSI cannot guarantee their long 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 refere
30、nces, the latest edition of the referenced document (including any amendments) applies. 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 IE
31、TF RFC 792: “Internet Control Message Protocol“. 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. ETSI ETSI TS 102 483 V7.3.0 (2009-01)6Release 7 5 IETF RFC 2449: “POP3 Extension Mechanism
32、“. NOTE: Available from http:/www.ietf.org/rfc/rfc2449.txt. 6 IETF RFC 1122: “Requirements 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
33、/rfc/rfc2460.txt. 8 IETF RFC 2463: “Internet Control Message Protocol (ICMPv6)for 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:
34、/www.ietf.org/rfc/rfc3022.txt. 10 IETF RFC 3314: “Recommendations for IPv6 in Third 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)“.
35、 12 IETF RFC 2461: “Neighbor Discovery for IP Version 6 (IPv6)“. NOTE: Available 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
36、from http:/www.ietf.org/rfc/rfc4294.txt. 15 IETF RFC 4291: “IP Version 6 Addressing 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
37、1035: “Domain names - Implementation and Specification“. NOTE: Available from http:/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 19 IETF RFC 2131: “Dynamic Host Configuration Protocol“
38、. NOTE: Available from http:/www.ietf.org/rfc/rfc2131.txt. 20 ETSI TS 102 600: “Smart Cards; UICC-Terminal Interface; Characteristics of the USB interface“. ETSI ETSI TS 102 483 V7.3.0 (2009-01)7Release 7 2.2 Informative references The following referenced documents are not essential to the use of t
39、he 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 http:/www.i
40、etf.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 Protocol (FTP)“
41、. 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-TS-Smartc
42、ard-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 telecommunicatio
43、ns 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 apply: app
44、lication: 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 executable code. fi
45、le: directory or an organized set of bytes or records in the UICC ETSI ETSI TS 102 483 V7.3.0 (2009-01)8Release 7 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ARP Address Resolution Protocol ASCII American Standard Code for Information Interchange DH
46、CP Dynamic Host Configuration Protocol FTP File Transfer Protocol HTTP HyperText Transport Protocol ICMP Internet Control Message Protocol IMAP Internet Message Access Protocol IP Internet Protocol NAT Network Address Translation POP Post Office Protocol HTTPS Secure HyperText Transport Protocol SMT
47、P Simple Mail Transfer Protocol TCP Transmission Control ProtocolTLS Transport Layer Security UDP User Datagram Protocol URI Universal Resource Identifier USIM Universal Subscriber Identity Module 4 Terminal-UICC IP configuration This clause is an introduction to the various configurations and uses
48、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 th
49、e following basic configurations: A TCP/IP or UDP/IP client of a server located on the terminal. A TCP/IP or UDP/IP server for a client located on the terminal. A TCP/IP or UDP/IP client of a server located in a network reachable through the terminal. A TCP/IP or UDP/IP server for a client located in a network reachable through the terminal. Depending on the final applications, the actual configuration may be a combination of these basic configurations. In the pre
