1、 ETSI TS 1Universal Mobile TelCharacteristfor 3GP(3GPP TS 31.2TECHNICAL SPECIFICATION131 220 V13.0.0 (2016elecommunications System (LTE; istics of the Contact Manager GPP UICC applications .220 version 13.0.0 Release 1316-02) (UMTS); er 13) ETSI ETSI TS 131 220 V13.0.0 (2016-02)13GPP TS 31.220 versi
2、on 13.0.0 Release 13Reference RTS/TSGC-0631220vd00 Keywords LTE,UMTS ETSI 650 Route des Lucioles 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 780
3、3/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prio
4、r written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat. Users of the present d
5、ocument 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:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the f
6、ollowing services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI. The content of the P
7、DF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI
8、 registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI 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. ETSI ETSI TS 131 220 V13.0.0 (2016-02)23GPP TS 31.22
9、0 version 13.0.0 Release 13Intellectual 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
10、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 (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investiga
11、tion, 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 Technical Specificat
12、ion (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
13、The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as
14、 described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 131 220 V13.0.0 (2016-02)33GPP TS 31.220 version 13.0.0 Release 13Contents Intellectual Pr
15、operty Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Symbols 7g33.3 Abbreviations . 7g34 Contact Manager External interface characteristics . 7g34.1 Reference model . 7g
16、34.2 External interface definition . 8g34.2.1 General 8g34.2.2 Contact Manager Server capabilities 8g34.2.3 Contact Manager External client capabilities . 8g34.2.4 Contact Manager Server and External Client capabilities 8g34.3 Access rules 9g34.4 Server configuration . 9g34.5 External Client configu
17、ration . 10g34.5.1 Framework 10g34.5.2 Basic configuration . 10g34.5.3 User Actions configuration . 10g34.6 Contacts grouping. 10g34.7 3GPP specific contacts elements 11g34.8 Synchronization with an external device 11g3Annex A (normative): Contact Manager Provisioning DTD 12g3A.1 Document Type Defin
18、ition . 12g3A.2 DTD Description 12g3Annex B (normative): User Actions DTD 13g3B.1 Document Type Definition . 13g3B.2 DTD Description 13g3Annex C (normative): Groups definition DTD 15g3C.1 Document Type Definition . 15g3C.2 DTD Description 15g3Annex D (normative): vCard properties requirements and ex
19、tensions 16g3D.1 vCard properties requirements . 16g3D.2 vCard 3GPP extensions 16g3Annex E (informative): Mapping of OMA DS functionalities and the Contact Manager . 17g3Annex F (informative): Contact Manager XML files examples 19g3ETSI ETSI TS 131 220 V13.0.0 (2016-02)43GPP TS 31.220 version 13.0.0
20、 Release 13F.1 Provisioning XML file example . 19g3F.2 User Actions XML file example 19g3F.3 Groups Definition XML file. 20g3Annex G (informative): Change history . 21g3History 22g3ETSI ETSI TS 131 220 V13.0.0 (2016-02)53GPP TS 31.220 version 13.0.0 Release 13Foreword This Technical Specification ha
21、s been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an iden
22、tifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. Y the second digit is incremented for all chang
23、es 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 the external interface characteristics of the Contact Manager for 3GPP UICC applicat
24、ions (e.g. USIM 3 and ISIM 4). The Contact Manager provides an interface for the management of contact information including rich content without any structural limitations. The Contact Manager Server application resides on the UICC, an IC card specified in TS 31.101 2. TS 31.101 2 specifies the app
25、lication independent properties of the UICC/terminal interface such as the physical characteristics. The external interface between the Contact Manager Server application on the UICC and the Contact Manager Client application on the ME enables the synchronization of the contact information, contacts
26、 grouping, configuration of contact structure, configuration of the triggering mechanism, and configuration of user actions which may be performed using contact information. ETSI ETSI TS 131 220 V13.0.0 (2016-02)63GPP TS 31.220 version 13.0.0 Release 131 Scope The present document defines the Contac
27、t Manager for 3GPP UICC applications based on OMA DS 7. The present document specifies the external interface between the Contact Manager Server in the UICC and the Contact Manager External Client in the ME; Any internal technical realization of either the Contact Manager Server or clients is only s
28、pecified where these are reflected over the interfaces. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc
29、.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in th
30、e same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 31.101: “UICC-Terminal Interface, Physical and Logical Characteristics“. 3 3GPP TS 31.102: “Characteristics of the Universal Subscriber Identity Module (USIM) application“. 4 3GPP TS 31.103: “Ch
31、aracteristics of the IP Multimedia Services Identity Module (ISIM) application“. 5 3GPP TS 31.111: “USIM Application Toolkit (USAT)“. 6 OMA SCWS: “OMA TS Smartcard Web Server v1_0-20070209-C“, www.openmobilealliance.org 7 OMA DS: “OMA TS DS Protocol V1.2“, www.openmobilealliance.org 8 OMA vObject Pr
32、ofile: “OMA TS vObject OMA Profile V1.0“, www.openmobilealliance.org 9 ETSI TS TS 102 483 V8.1.0: “UICC-Terminal interface; Internet Protocol connectivity between UICC and Terminal“ 10 OMA DS Folder: “Folder data object specification v1.2“, www.openmobilealliance.org 11 OMA DS File: “File data objec
33、t specification v1.2“, www.openmobilealliance.org 12 OMA SAN: “SyncML Server Alerted Notification v1.2“, http:/www.openmobilealliance.org 13 IETF RFC 3629: “UTF-8, a transformation format of ISO 10646“. 14 Void ETSI ETSI TS 131 220 V13.0.0 (2016-02)73GPP TS 31.220 version 13.0.0 Release 133 Definiti
34、ons, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. Contact Manager Exter
35、nal Client: The Contact Manager client application that resides on the ME. This client application acts as an OMA DS client. Contact Manager Server: An application residing on the UICC that provides services to the External clients. It acts as an OMA DS server for the Contact Manager External Client
36、. Contact Manager External Interface: the interface between the Contact Manager Server residing on the UICC and the Contact Manager External Client. 3.2 Symbols For the purposes of the present document, the following symbols apply: | Concatenation 3.3 Abbreviations For the purposes of the present do
37、cument, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. DS Data Synchronization DTD Document Type Definition OMA Open Mobile Alliance PIN Personal Id
38、entification Number SCWS Smart Card Web Server URL Universal Resource Location XML eXtensible Markup Language 4 Contact Manager External interface characteristics 4.1 Reference model The following figure shows the architecture of the interface between the Contact Manager Server and the Contact Manag
39、er External Client. ETSI ETSI TS 131 220 V13.0.0 (2016-02)83GPP TS 31.220 version 13.0.0 Release 13SCWS Contact Manager Server BIP (TCP server mode) HTTP TS 102 221 based interface Application layer TCP/IP High-Speed Interface Contact Manager External Client BIP (TCP server mode) HTTP TS 102 221 bas
40、ed interface TCP/IP High-Speed Interface UICC ME Figure 1: External interface reference model 4.2 External interface definition 4.2.1 General This clause defines the Contact Manager External Interface. In case both the ME and the 3GPP UICC application support both the 3G Phone Book (i.e. as defined
41、in TS 31.102 3) and the Contact Manager, the Contact Manager should be used. 4.2.2 Contact Manager Server capabilities The Contact Manager Server shall implement the mandatory OMA DS server functionalities defined in OMA DS 7. The Contact Manager Server shall also support the following functionaliti
42、es: - The Contact Manager Server shall support at least two External clients. - The Contact Manager Server shall use the same contact database account if more than one client is used. 4.2.3 Contact Manager External client capabilities The Contact Manager External client shall implement the mandatory
43、 OMA DS client functionalities defined in OMA DS 7. The Contact Manager client shall also support the following functionalities: - The Contact Manager External client shall support an automatic triggering mechanism based on a policy. A default policy may be based either on time or on number of updat
44、ed contacts. The default policy parameters shall be stored in “Provisioning.xml“. If the default policy parameters are present in “Provisioning.xml“ they shall be used unless otherwise configured by the user. Otherwise, the triggering mechanism shall be based on ME local policy. The synchronization
45、initiated by this mechanism shall be totally transparent for the end-user (i.e. without any display, popup or progress bar). 4.2.4 Contact Manager Server and External Client capabilities Both the Contact Manager Server and the Contact Manager External Client shall support the following functionaliti
46、es: - The Contact Manager Server and External client shall support the Field Level Filtering functionality as defined in OMA DS 7. - The Contact Manager Server and External Client shall support and use the Device Memory Management mechanism defined in OMA DS 7. The Contact Manager Server and Externa
47、l Client shall indicate their dynamic memory capabilities using and elements as described in OMA DS 7. The Contact ETSI ETSI TS 131 220 V13.0.0 (2016-02)93GPP TS 31.220 version 13.0.0 Release 13Manager Server and External Client shall indicate their permanent memory capabilities using , and elements
48、 as described in OMA DS 7. - The Contact Manager Server and External Client shall comply with the vCard2.1 Minimum Interoperability Profile guidelines specified in OMA vObject Profile 8. The vCard profile shall also comply with the implementation requirements in Annex D. - The Contact Manager Server
49、 and External Client should comply with vCard 3.0. If vCard 3.0 is supported, the Contact Manager Server and External Client shall comply with the vCard2.1 Minimum Interoperability Profile guidelines specified in OMA vObject Profile 8. The vCard profile shall also comply with the implementation requirements in Annex D. - The Contact Manager Server and External Client shall specify the and elements in their Device Information for the vCard Properties. The receiving device shall not send more than the speci
