1、 ETSI TS 102 334-4 V1.1.2 (2006-11)Technical Specification Network Address Book on fixed network;Part 4: Data synchronizationETSI ETSI TS 102 334-4 V1.1.2 (2006-11) 2 Reference RTS/AT-030049 Keywords addressing, ISDN, MMS, PSTN, synchronization ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Ce
2、dex - 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:/www.etsi.org The present docum
3、ent 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 printing on ETSI printers of the P
4、DF 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:/portal.etsi.org/tb/status/stat
5、us.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 the foregoing restriction exten
6、d to reproduction in all media. European Telecommunications Standards Institute 2006. 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 registered by ETSI for the benefit
7、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 334-4 V1.1.2 (2006-11) 3 Contents Intellectual Property Rights4 Foreword.4 Introduction 5 1 Scope 6 2 References 6 3 Definitions and abbreviations.7 3.1
8、Definitions7 3.2 Abbreviations .7 4 Requirements7 5 Architecture8 6 Format of contact information exchange8 7 OMA DS (previously SyncML).8 7.1 OMA DS version8 7.2 Synchronization session initiation9 7.3 OMA DS options9 7.4 Device Information.9 7.5 Transport 9 8 Terminal requirements .9 9 Server requ
9、irements10 Annex A (informative): Bibliography.11 History 12 ETSI ETSI TS 102 334-4 V1.1.2 (2006-11) 4 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
10、available for ETSI members and non-members, and can be found in ETSI SR 000 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
11、server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, 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 ma
12、y be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI Technical Committee Access and Terminals (AT). The present document is part 4 of a multi-part deliverable covering the Network Address Book on fixed network, as identified bel
13、ow: Part 1: “Overview“; Part 2: “Service description“; Part 3: “vCard 2.1 profile for contact exchange by SMS/EMS for fixed network“; Part 4: “Data synchronization“. NOTE: The parts above refer to the active work items and published standards within ETSI. Many devices and applications handling perso
14、nal contact information are today available to the consumers. Contact information is stored in various devices such as mobile phones, PDAs, or PCs, and also fixed line terminals. Without a mean to homogenize that information among all these devices, a consumer may have difficulties to manage and ret
15、rieve easily his personal contact information. In this context, data synchronization is considered as the appropriate technology to maintain those different information sources in a consistent state and thus allow consumers to manage efficiently their data, wherever they are stored. Service provider
16、s and operators are now offering systems centralizing personal information to allow an easier personal data management. Consumers can already synchronize and manage data between network elements, mobile devices and Personal Computers (PCs). There is a need to make it possible also between network el
17、ements and fixed devices. OMA DS (SyncML) is an open standard for Data Synchronization that is already widely used to synchronize data between mobile handsets, PCs, and network elements. The present document, which is based on XML messages exchanges over any kind of network, can be deployed on fixed
18、 line networks as well as on mobile or IP based networks and on any type of operating system. OMA DS allows to synchronize any kind of data, including contact information or calendars. The present document is being maintained by OMA Data Sync WG of the Open Mobile Alliance, and is supported by an in
19、creasing number of mobile devices. The objective of the present document is to define a profile on OMA DS 1.2 for contact information synchronization dedicated to fixed-line devices that will maintain interoperability between the fixed line, internet and mobile devices. This will enable any consumer
20、 to synchronize seamlessly its contacts between its mobile devices, PDAs, PCs and fixed line terminals. ETSI ETSI TS 102 334-4 V1.1.2 (2006-11) 5 Introduction The purpose of the present document is to define requirements for the use of OMA DS 1.2 (formerly known as SyncML) for contact information sy
21、nchronization between the address book of a fixed-line device (Local Address Book) and a Network Address Book. As such, the present document does not modify the original OMA DS specification. It only specifies - when needed - any option/choice to be taken to adapt it to the fixed line environment. T
22、he OMA DS 1.2 specification packages (OMA Data sync v1.2 and OMA SyncML Common v 1.2) can be found at the following URL: http:/ The reader is strongly advised to read OMA DS 1.2 specification packages along with this Technical Specification. NOTE: SyncML has been renamed as OMA DS since 1.1.2 releas
23、e. SyncML 1.2 does not exist anymore. Nevertheless OMA DS still refers to SyncML messages and packages as the messages/packages exchanged between an OMA DS client and an OMA DS server. Any definition can be found in OMA DS 1.2 specification packages. The present document provides also some informati
24、on concerning the exchange format used for contact information synchronization using OMA DS, and including the underlying transport protocol. ETSI ETSI TS 102 334-4 V1.1.2 (2006-11) 6 1 Scope The present document defines requirements for the use of OMA DS 1.2 for fixed-line devices. The present docu
25、ment defines contact information exchange format to be used for contact synchronization with OMA DS 1.2. 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
26、 publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced documents which are not found to be publicly available in the expected location might be found at h
27、ttp:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 1 OMA-SyncML-DevInf-V1-2-20040601-C: “SyncML Device Information“. 2 OMA-TS-SyncML-HTTPBinding-V1-2-20050509-C: “SyncML HTTP Binding
28、“. 3 OMA-TS-SyncML-RepPro-V1-2-20050509-C: “SyncML Representation Protocol“. 4 OMA-TS-SyncML-SAN-V1-2-20050509-C: “SyncML Server Alerted Notification“. 5 OMA-TS-SyncML-MetaInfo-V1-2-20050509-C: “SyncML Meta Information“. 6 OMA-SyncML-DataSyncProtocol-V1-2-20040601-C: “SyncML Data Sync Protocol“. 7 O
29、MA-SyncML-DataSyncRep-V1-2-20040601-C: “SyncML Representation Protocol, Data Synchronization Usage“. 8 vCard 2.1: “The electronic business card“, Versit consortium, 1996. NOTE: (http:/www.imc.org/pdi/vcard-21.doc). 9 ETSI ES 201 986 (V1.1.2): “Services and Protocols for Advanced Networks (SPAN); Sho
30、rt Message Service (SMS) for PSTN/ISDN; Service description“. 10 ETSI ES 201 912: “Access and Terminals (AT); Short Message Service (SMS) for PSTN/ISDN; Short Message Communication between a fixed network Short Message Terminal Equipment and a Short Message Service Centre“. 11 ETSI ES 202 314-4: “Fi
31、xed network Multimedia Messaging Service (F-MMS); Part 4: PSTN/ISDN; Multimedia Message communication between a fixed network Multimedia Messaging Terminal Equipment and a Multimedia Messaging Service Centre“. 12 IETF RFC 2616: “Hypertext Transfer Protocol - HTTP/1.1“. ETSI ETSI TS 102 334-4 V1.1.2
32、(2006-11) 7 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: client: OMA DS client refers to the protocol role when the application issues SyncML “request“ messages NOTE: For example, in data synchronization, the Syn
33、cML Command in a SyncML Message. data: unit of information exchanged, encoded for transmission over a network global unique identifier: number assigned to an object in a data base. GUID values are never reused NOTE: In practice, numbers do not have a unique GUID forever, they must only be unique as
34、long as they exist in some mapping table. message: a SyncML Message is the primary content of a SyncML Package NOTE: It contains the SyncML Commands as well as the related data and meta information. The SyncML Message is an XML document. meta information: parameters or attributes about the represent
35、ation, state or type or content of an object or property server alerted notification: method by which an OMA DS server notifies an OMA DS client to initiate a SyncML session server alerted sync: Data Synchronization terminology for Server Alerted Notification OMA DS application: application that sup
36、ports the OMA DS protocol NOTE: The application can either be the originator or recipient of the OMA DS protocol commands. The application can act as a OMA DS client or a OMA DS server. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: GUID Global Unique
37、IDentifier HTTP HyperText Transfer Protocol ID IDentifier LAB Local Address Book NAB Network Address BookOBEX Object Exchange Protocol OMA Open Mobile Alliance OMA DS Open Mobile Alliance Date Synchronization URL Uniform Resource Locator vCard versit CardWAP Wireless Application Protocol WSP Wireles
38、s Session Protocol XML Extensible Markup Language 4 Requirements For data synchronization, the following requirements apply: There shall be the capability to initiate the synchronization from the Network Address Book. The device should be able to stop or suspend a synchronization. ETSI ETSI TS 102 3
39、34-4 V1.1.2 (2006-11) 8 The underlying transport (see OMA DS 1.2 definitions) shall be HTTP. Each client shall be addressed with an ID which should be unique (e.g. name, subscriber line number, serial number, etc.). Two way synchronization shall be supported. 5 Architecture Figure 1: Architecture ov
40、erview (informative) A fixed line terminal containing a Local Address Book is considered as the client, and the Network Address Book as the server, using OMA DS terminology. Each part has its own internal personal information data representation, and those could be different. Clause 6 describes the
41、minimal set of information needed to exchange contact data. In order to ensure interoperability the client and the server use SyncML messages (see 3, 7, 1 and 5) for contacts exchange. vCard 2.1 (see 8) format shall be used for contact representation (see clause 7) and the corresponding contact obje
42、cts shall be embedded in SyncML messages as vCard 2.1 instances. Each side shall be able to parse SyncML messages and vCard 2.1 instances in order to obtain its own internal contact representation, and to do the reverse operation (e.g. to generate SyncML messages containing vCard 2.1 instances from
43、the internal contact representation). 6 Format of contact information exchange vCard 2.1 format shall be used as defined in 8. Other formats are for further study. A nickname is often used in fixed phones instead of regular first name and last name. The Formatted Name property (i.e. FN) of vCard 2.1
44、 (see 8) shall be used to cover that specific point. 7 OMA DS (previously SyncML) This part defines the OMA DS 1.2 profile for a fixed-line device. It does not modify the original OMA DS specification. It only specifies - when needed - any option/choice to be taken to adapt it to the fixed line envi
45、ronment. 7.1 OMA DS version OMA DS version 1.2 shall be used. See 1 to 7. ETSI ETSI TS 102 334-4 V1.1.2 (2006-11) 9 7.2 Synchronization session initiation Either NAB or LAB side may initiate a synchronization session. As defined in OMA DS, the client (LAB side) initiates the synchronization in the n
46、ormal case. Nevertheless, OMA DS provides a mechanism, called Server Alerting Notification, making it possible for a server (NAB side) to require a client to start a synchronization session. As specified in 4 and 6, the server sends a notification to the client, which initiates a synchronization ses
47、sion. 7.3 OMA DS options As this Technical Specification defines a profile on OMA DS 1.2 for fixed-line terminals, every OMA DS 1.2 mandatory feature shall be implemented by the terminals. The following optional features defined in OMA DS 1.2 are recommended to be implemented in fixed-line terminals
48、: Server Alerted Sync (emission for servers and reception for clients). Transport for Server Alerted Sync initiation notification should be SMS 9 and 10, according 4 and 6. Suspend and Resume (should be implemented also in the server). 7.4 Device Information OMA DS provides the exchange of device in
49、formation between the client and the server during the initialization phase (see 6). The SyncML syntax used for device information is given in 1. The present document only includes vCards synchronization. Thus, the DevInf element (as defined in SyncML) shall contain all the mandatory vCard information conforming with 8. 7.5 Transport OMA DS is transport-independent. Several transport bindings are defined in OMA DS specifications (HTTP, OBEX, WSP). Within
