12 Contact Manager
21.1113GPPRelease 17TSUSIM and IC card requirements
12.1 General
The Contact Manager provides an interface for the management of contact information including rich content without any structural limitations.
There shall be a mechanism for the ME to detect that the UICC containing the Contact Manager has changed. This mechanism may be used by the ME to ask the user whether synchronization of data between the ME and the UICC Contact Manager should occur.
This clause defines the functional requirements of the Contact Manager. An ME and a 3GPP application supporting the Contact Manager shall comply with all these requirements.
12.2 Security requirements
The Contact Manager may contain personal information. It shall be possible to restrict the access to this information to authorized users or entities (e.g. by binding the access to the verification of the USIM PIN).
12.4.3 Interworking with the 3G Phone Book
In case both the ME and the 3GPP application support both the 3G Phone Book (i.e. as defined in clause 10.2 of the present document) and the Contact Manager the Contact Manager shall be used. There shall be a mechanism for the 3GPP application to indicate the support of the Contact Manager.
12.4.4 Content description
12.4.4.1 Number of contacts
The Contact Manager specification shall not unreasonably restrict the number of contacts.
12.4.4.2 Contact structure
The Contact Manager shall consist of contacts, which are made up of various fields (e.g. phone number, name, photo). A filtering mechanism according to OMA DS Field Filtering shall be supported.
It shall be possible to have several instances of a field in a contact when appropriate (e.g. a contact may have two fax numbers).
An extensible coding scheme shall be defined which allows to describe a contact including all its fields. An existing scheme (e.g. "vcard") shall be used, if appropriate.
A minimum set of field types recognised by the 3GPP application and the ME shall be defined (e.g. name, phone number, URL, Email address, address, sound, pictures, notes).
It shall be possible to store and associate multimedia information (stored on the 3GPP application) with a contact (e.g. photo, logo, video, ring tone, voice tag).
It shall be possible to associate an icon or a label to each contact field type (e.g. associate an icon representing a phone to the number field. "Home address" could be configured as the label of the "mailing address" field type).
It shall be possible to configure the structure and the display order of the contact fields (e.g. first name then Instant Messaging address then number, etc) depending on ME capabilities.
12.4.4.3 Group management
It shall be possible to define new groups (e.g. My Tennis Club).
It shall be possible to pre-define groups (e.g. Friend, Work, Family and VIP).
It shall be possible to store and associate multimedia information (stored on the 3GPP application) with a group (e.g. photo, logo, video, ring tone, icon).
It shall be possible to bind contacts to one or several groups.
12.4.4.4 User Action Management
It shall be possible to configure a list of possible actions that could be proposed to the user when the contact is selected (e.g. Launch Browser, Send SMS, Send MMS, Instant messaging, Make a voice over IP call, Make a video call, Make a conference call, Game player, Send Email).
12.4.5 Interface capabilities description
An external and an internal interface to the Contact Manager shall be defined.
The external interface between the Contact Manager and a UICC external entity, i.e. the ME, shall rely on a transport protocol layer that is independent of the physical interface (i.e. the ISO interface and the new high-speed interface). This is to allow the definition of one solution that can use either the existing ISO interface or the new high-speed interface. The external interface definition shall also ease interfacing the PC applications with the Contact Manager.
Both the ME and the UICC shall be capable of initiating contact information synchronization based on a configurable policy.The internal interface allows other UICC resident applications to access the Contact Manager e.g. through a dedicated API. This enables the creation of additional services utilizing the Contact Manager data and properties. There shall be a mechanism for the user to allow or prevent remote access to the Contact Manager.
The external and internal interface shall provide means to:
– identify Contact Manager capabilities
– perform the following operations on a contact or a group: create, retrieve, modify, delete, search
In addition the internal interface shall provide mechanisms to:
– register/deregister an UICC resident application to the Contact Manager.
– allow a resident UICC application to access Contact Manager data and properties based on user permission.
– allow the Contact Manager to notify events to registered UICC application and to pass event related information when applicable. Events notifying the applications shall include:
– contact information is modified locally
– contact information is modified remotely
– change of contact manager configuration
12.4.6 Efficient browsing and searching
The Contact Manager interfaces should allow efficient searching and browsing of the contacts (i.e. the user experience browsing the Contact Manager should be acceptable).
12.4.7 Associated services
12.4.7.1 Memory management
It shall be possible to determine the number of stored contacts and the amount of the available and used Contact Manager memory.
Annex A (informative):
Change history
The table below indicates all change requests that have been incorporated into the present document since it was initially approved by 3GPP TSG T and subsequently 3GPP TSG CT.
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Cat |
Subject/Comment |
New |
|
1999-06 |
TP-03 |
TP-99085 |
Draft specification first approved at TSG-T #3 |
3.0.0 |
|||
|
1999-12 |
TP-06 |
TP-99255 |
001 |
D |
References to new specifications and editorial changes |
3.0.1 |
|
|
2000-04 |
TP-07 |
TP-000017 |
002 |
F |
Location of the UIA (3GPP integrity algorithm) aligned with 33.102 |
3.1.0 |
|
|
2000-07 |
TP-08 |
TP-000097 |
003 |
F |
Clarification of USIM application selection |
3.2.0 |
|
|
TP-000097 |
004 |
F |
Alignment with 33.102: removal of Enhanced User Identity Confidentiality (EUIC) from R99 |
||||
|
2000-10 |
TP-09 |
TP-000150 |
005 |
F |
Partial AID selection requirements |
3.3.0 |
|
|
2001-03 |
TP-11 |
– |
– |
Issued as version 4.0.0 in order to create a complete set of specifications for release 4. The contents of version 4.0.0 are identical to the contents of version 3.3.0 |
4.0.0 |
||
|
2002-06 |
TP-16 |
– |
– |
Issued as version 5.0.0 in order to create a complete set of specifications for release 5. The contents of version 5.0.0 are identical to the contents of version 4.0.0 |
5.0.0 |
||
|
2002-09 |
TP-17 |
TP-020208 |
009 |
A |
Clarification on the use of the USIM and the SIM |
5.1.0 |
|
|
2004-03 |
TP-23 |
TP-040023 |
010 |
C |
Update with respect to the third form factor and removal of an unused reference |
6.0.0 |
|
|
2004-06 |
TP-24 |
TP-040100 |
011 |
D |
Release 6 alignment |
6.1.0 |
|
|
2005-06 |
CT-28 |
CP-050136 |
015 |
A |
ISO/IEC 7816-Series Revision |
6.2.0 |
|
|
2006-05 |
CT-32 |
CP-060349 |
0017 |
1 |
F |
Review of TS 21.111, USIM and IC Card Requirements |
6.3.0 |
|
2006-09 |
CT-33 |
action item |
– |
– |
MCC to raise spec to Rel-7 |
7.0.0 |
|
|
2007-03 |
CT-35 |
CP-070070 |
0019 |
2 |
B |
Requirements for the Enhanced USIM phonebook |
8.0.0 |
|
2007-10 |
Editorial correction to cover page |
8.0.1 |
|||||
|
2007-12 |
CT-38 |
CP-070839 |
0020 |
2 |
B |
Completion of the requirements for the Enhanced USIM phonebook Renaming of the feature to Contact Manager. Contact Manager moved to a dedicated clause |
8.1.0 |
|
2008-05 |
CT-40 |
CP-080384 |
0023 |
2 |
F |
Update and correct references and pointers to references |
8.2.0 |
|
2009-12 |
CT-46 |
CP-091042 |
0025 |
2 |
F |
References update |
8.3.0 |
|
2009-12 |
CT-46 |
– |
– |
– |
– |
Upgrade of the specification to Rel-9 |
9.0.0 |
|
2011-03 |
SP-51 |
– |
– |
– |
– |
Upgrade of the specification to Rel-10 |
10.0.0 |
|
2012-09 |
SP-57 |
– |
– |
– |
– |
Upgrade of the specification to Rel-11 |
11.0.0 |
|
2012-10 |
– |
– |
– |
– |
Remove hidden text |
11.0.1 |
|
|
2014-10 |
SP-65 |
– |
– |
– |
– |
Upgrade of the specification to Rel-12 |
12.0.0 |
|
2015-12 |
Upgrade to Rel-13 |
13.0.0 |
|||||
|
2016-12 |
CT-74 |
CP-160789 |
0027 |
1 |
B |
Usage of non-removable UICC |
14.0.0 |
|
2017-09 |
CT-77 |
CP-172064 |
0028 |
2 |
C |
Support for two voltage classes |
14.1.0 |
|
2018-03 |
CT-79 |
CP-180130 |
0029 |
1 |
B |
Mandating only single voltage class support for MEs supporting NG-RAN. |
15.0.0 |
|
2018-06 |
CT-80 |
CP-181158 |
0030 |
– |
F |
Correction on implementation of CR0029 |
15.1.0 |
|
2018-07 |
Correction to logo, version and date on cover page |
15.1.1 |
|||||
|
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2020-12 |
CT#903 |
CP-203085 |
A |
Allowing single voltage class for MEs supporting Category 1bis |
16.1.0 |
||
|
2021-09 |
CT#93e |
CP-212091 |
0034 |
2 |
C |
Clarification of supply voltage support for NG-RAN ME |
17.0.0 |