ETSI TS 102 483-2007 Smart cards UICC-Terminal interface Internet Protocol connectivity between UICC and terminal《智能卡 UICC-终端接口 UICC和终端间的互联网协议连通性(版本7 0 0 第7次发布)》.pdf

1、 ETSI TS 102 483 V7.1.0 (2007-11)Technical Specification Smart cards;UICC-Terminal interface;Internet Protocol connectivity between UICC and terminal(Release 7)ETSI ETSI TS 102 483 V7.1.0 (2007-11) 2 Release 7 Reference RTS/SCP-T0311r1 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 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being regi

7、stered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 483 V7.1.0 (2007-11) 3 Release 7 Content Intellectual Property Rights4 Foreword.4 Introduction 4 1 Scope 5 2 References 5

8、2.1 Normative references .5 2.2 Informative references6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7 4 Terminal-UICC IP configuration .8 4.1 Local client on UICC .8 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 UIC

9、C and Terminal components requirements12 6.1 UICC IP layer.12 6.1.1 IPv4 / IPv6 interworking.12 6.1.2 Address allocation 12 6.1.2.1 Local Connection 12 6.1.2.2 Remote Connection.12 6.1.2.2.1 IPv4 address allocation13 6.1.2.2.2 IPv6 address allocation13 6.2 Local naming13 6.2.1 Static resolution 13 6

10、.3 Summary of terminal and UICC configuration 13 6.3.1 UICC Configuration .13 6.3.1.1 IP v413 6.3.1.2 IP v613 6.3.2 Terminal Configuration 14 6.3.2.1 IP v414 6.3.2.2 IP v614 6.4 Terminal IP Components14 6.4.1 Connection setting 14 6.4.2 Routing, Network Address Translation and port forwarding14 Anne

11、x A (informative): Connection of a local equipment to the terminal and UICC15 Annex B (informative): Definition of the connection activation parameters for common network technologies .16 Annex C (informative): Bibliography.17 Annex D (informative): Change history .18 History 19 ETSI ETSI TS 102 483

12、 V7.1.0 (2007-11) 4 Release 7 Intellectual 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 0

13、00 314: “Intellectual Property Rights (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 Pol

14、icy, no investigation, including 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 Tec

15、hnical Specification (TS) has been 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

16、be republished by ETSI with an identifying 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 un

17、der change control. y the second 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 P

18、rotocol connection may be established 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 In

19、ternet Protocol and therefore telecommunication 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 standardi

20、zation efforts: Applicative protocols 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 fo

21、rcing specific developments. Facilitate 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

22、use this connection capability. ETSI ETSI TS 102 483 V7.1.0 (2007-11) 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

23、 packets. The way the Internet Protocol 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

24、 of the Internet Protocol connection 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 22. 2 References References are either specific (identified by date of publication and/or edition nu

25、mber or version number) or non-specific. For a specific reference, subsequent revisions do not apply. In the case of a reference to an 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 referenc

26、e may be made only to a complete 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

27、case of a reference to an TC SCP 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

28、/Reference. For online referenced 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

29、 the expected life of the document. 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 publicati

30、on 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 references, the latest edition of the referenced docume

31、nt (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. ETSI ETSI TS 102 483 V7.1.0 (2007-11) 6 Release 7 3 I

32、ETF 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. 5 IETF RFC 2449: “POP3 Extension Mechanism“. NOTE: Available from http:/www.ietf.org/rfc/

33、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/rfc/rfc2460.txt. 8 IETF RFC 2463: “Internet Co

34、ntrol 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:/www.ietf.org/rfc/rfc3022.txt. 10 IETF RFC 3314

35、: “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)“. 12 IETF RFC 2461: “Neighbor Discovery for IP V

36、ersion 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 from http:/www.ietf.org/rfc/rfc4294.txt. 15 IET

37、F RFC 4291: “IP Version 6 Addressing Architecture“. NOTE: Available from http:/www.ietf.org/rfc/rfc4291.txt. 2.2 Informative references 16 IETF RFC 2060: “Internet Message Access Protocol“, version 4rev1. NOTE: Available from http:/www.ietf.org/rfc/rfc2060.txt. 17 IETF RFC 2246: “The TLS Protocol“,

38、version 1.0. NOTE: Available from http:/www.ietf.org/rfc/rfc2246.txt. 18 IETF RFC 2616: “Hypertext Transfer Protocol - HTTP/1.1“. NOTE: Available from http:/www.ietf.org/rfc/rfc2616.txt. ETSI ETSI TS 102 483 V7.1.0 (2007-11) 7 Release 7 19 IETF RFC 959: “File Transfer Protocol (FTP)“. NOTE: Availabl

39、e from http:/www.ietf.org/rfc/rfc959.txt. 20 IETF RFC 821: “Simple Mail Transfer Protocol“. NOTE: Available from http:/www.ietf.org/rfc/rfc821.txt. 21 IETF RFC 1034: “Domain Names - concepts and facilities“. NOTE: Available from http:/www.ietf.org/rfc/rfc1034.txt. 22 OMA-TS-Smartcard-Web-Server-V1-0

40、. NOTE: Available from http:/www.openmobilealliance.org. 23 IETF RFC 768: “User Datagram Protocol“. NOTE: Available from http:/www.ietf.org/rfc/rfc768.txt. 24 ETSI TS 102 223: “Smart Cards; Card Application Toolkit (CAT)“. 25 ETSI TS 131 111: “Digital cellular telecommunications system (Phase 2+); U

41、niversal 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: application: computer prog

42、ram 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. file: directory or an org

43、anized set of bytes or records in the UICC 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: APDU Application Protocol Data Unit ARP Address Resolution ProtocolDHCP Dynamic Host Configuration Protocol FTP File Transfer Protocol HTTP HyperText Transport Pr

44、otocol ICC Integrated Circuit Card ICMP Internet Control Message Protocol IMAP Internet Message Access Protocol IEC International Electrotechnical Commission IP Internet Protocol ISO International Organization for Standardization NAT Network Address TranslationPOP Post Office Protocol RARP Reverse A

45、ddress Resolution Protocol RFU Reserved for Future Use RST ReSeTSE Security Environment HTTPS Secure HyperText Transport Protocol ETSI ETSI TS 102 483 V7.1.0 (2007-11) 8 Release 7 SMTP Simple Mail Transfer Protocol SSL Secure Sockets Layer TCP Transmission Control Protocol TLS Transport Layer Securi

46、ty 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 section is an introduction to the various configurations and uses of the IP UICC. A UICC sup

47、porting 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 configur

48、ations: 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 thro

49、ugh the terminal. Depending on the final applications, the actual configuration may be a combination of these basic configurations. In the present document, the wording TCP/IP or UDP/IP protocol includes any application protocol such as HTTP, FTP, POP, SMTP that may be enabled by TCP or UDP, i.e. the configuration targeted is not restricted to having a web server and web client on the card. 4.1 Local client on UICC In this configuration the UICC is a client for TCP/IP servers loc