1、 I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T F.746.2 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (02/2014) SERIES F: NON-TELEPHONE TELECOMMUNICATION SERVICES Audiovisual services Service description for user data exchange between functional components in network e
2、ntities and terminals Recommendation ITU-T F.746.2 ITU-T F-SERIES RECOMMENDATIONS NON-TELEPHONE TELECOMMUNICATION SERVICES TELEGRAPH SERVICE Operating methods for the international public telegram service F.1F.19 The gentex network F.20F.29 Message switching F.30F.39 The international telemessage se
3、rvice F.40F.58 The international telex service F.59F.89 Statistics and publications on international telegraph services F.90F.99 Scheduled and leased communication services F.100F.104 Phototelegraph service F.105F.109 MOBILE SERVICE Mobile services and multidestination satellite services F.110F.159
4、TELEMATIC SERVICES Public facsimile service F.160F.199 Teletex service F.200F.299 Videotex service F.300F.349 General provisions for telematic services F.350F.399 MESSAGE HANDLING SERVICES F.400F.499 DIRECTORY SERVICES F.500F.549 DOCUMENT COMMUNICATION Document communication F.550F.579 Programming c
5、ommunication interfaces F.580F.599 DATA TRANSMISSION SERVICES F.600F.699 AUDIOVISUAL SERVICES F.700F.799 ISDN SERVICES F.800F.849 UNIVERSAL PERSONAL TELECOMMUNICATION F.850F.899 HUMAN FACTORS F.900F.999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T F.746.2 (02/20
6、14) i Recommendation ITU-T F.746.2 Service description for user data exchange between functional components in network entities and terminals Summary Recommendation ITU-T F.746.2 describes user data exchange scenarios and a basic approach of exchanging user data between terminals or between terminal
7、s and network entities by using data packages encapsulating formatted user data. The functionality of the components which implement the data exchange and general guidance of generating and parsing such data package are given as well. This Recommendation also describes the preferred extensible marku
8、p language (XML) representations used when encapsulating corresponding user data, including, but not limited to, contacts, messages and other user data categories. History Edition Recommendation Approval Study Group Unique ID* 1.0 ITU-T F.746.2 2014-02-13 16 11.1002/1000/12050 Keywords Data exchangi
9、ng agent (DXA), user data exchange, XML. _ * To access the Recommendation, type the URL http:/handle.itu.int/ in the address field of your web browser, followed by the Recommendations unique ID. For example, http:/handle.itu.int/11.1002/1000/11830-en. ii Rec. ITU-T F.746.2 (02/2014) FOREWORD The Int
10、ernational Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical,
11、operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in tur
12、n, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE
13、 In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e
14、.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not
15、suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTSITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the e
16、vidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, whic
17、h may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2014 All rights reserved. No part of this publication ma
18、y be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T F.746.2 (02/2014) iii Table of Contents Page 1 Scope . 1 2 References . 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation . 2 4 Abbreviations and acronyms 2 5 Conv
19、entions 3 6 General 3 7 Scenarios of user data exchange . 3 7.1 User data grouping . 3 7.2 Scenario description . 4 8 User data exchange method 4 8.1 General procedure 4 8.2 Data package 5 9 Functionality of data exchange functional components . 6 9.1 Basic functionality 6 9.2 Security consideration
20、 6 10 Preferred XML user data syntax . 7 10.1 General . 7 10.2 Contacts data syntax . 7 10.3 Calendar data syntax . 7 10.4 Messaging data syntax 7 10.5 Other . 10 Rec. ITU-T F.746.2 (02/2014) 1 Recommendation ITU-T F.746.2 Service description for user data exchange between functional components in n
21、etwork entities and terminals 1 Scope The general purpose of this Recommendation is to describe user data exchange scenarios and a basic approach to exchange user data between terminals or between terminals and network entities by using data packages encapsulating formatted user data. The functional
22、ity of the components which implement the data exchange and general guidance of generating and parsing such data packages are given as well. This Recommendation also describes the preferred extensible markup language (XML) representations used when encapsulating corresponding user data, including, b
23、ut not limited, to contacts, messages and other user data categories. This Recommendation applies to terminals and network entities which choose to implement user data exchanging functions as described in this Recommendation. 2 References The following ITU-T Recommendations and other references cont
24、ain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate th
25、e possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a
26、Recommendation. ETSI TS 123 140 ETSI TS 123 140 V6.16.0 (2009), Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Multimedia Messaging Service (MMS); Functional description; Stage 2 (3GPP TS 23.140 version 6.16.0 Release 6). ETSI TS 126 140 ETS
27、I TS 126 140 V7.1.0 (2007), Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Multimedia Messaging Service (MMS); Media formats and codes (3GPP TS 26.140 version 7.1.0 Release 7). ETSI TS 127 005 ETSI TS 127 005 V3.2.0 (2002), Digital cellular
28、telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS);Use of Data Terminal Equipment Data Circuit terminating Equipment (DTE DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS) (3GPP TS 27.005 version 3.2.0 Release 1999). IETF RFC 5545 IE
29、TF RFC 5545 (2009), Internet Calendaring and Scheduling Core Object Specification (iCalendar). IETF RFC 6321 IETF RFC 6321 (2011), xCal: The XML Format for iCalendar. IETF RFC 6350 IETF RFC 6350 (2011), vCard Format Specification. IETF RFC 6351 IETF RFC 6351 (2011), xCard: vCard XML Representation.
30、W3C XML W3C XML 1.0 (2008), Extensible Markup Language (XML) 1.0 (Fifth Edition). W3C XMLEnc W3C XML Encryption (2002), XML Encryption Syntax and Processing. 2 Rec. ITU-T F.746.2 (02/2014) W3C XSD W3C XML Schema Part 1 (2004), XML Schema Part 1: Structures Second Edition. 3 Definitions 3.1 Terms def
31、ined elsewhere None. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 data exchanging agent: Logic in terminals or entities where the main function is to put data into or extract data from the data package described in this Recommendation. Furthermore,
32、it monitors the data exchange process and takes actions when specific user data is encountered after the data exchange process. A typical form of the functional component is an extensible markup language (XML) parser combined with application-dependent logic. 3.2.2 depository: A depository is a loca
33、tion where the user data could be stored or kept so that it could be accessed later. It can take various forms such as internal or external memory of terminals, network storage servers and other storage devices. 3.2.3 user data: “User data“ is the data that is created or stored in terminals or netwo
34、rk entities by the users, and is related to the private information, historical operations performed by the user, personal tendencies or favourite user settings. It is independent of whether this data is transported by terminal or network entities, and has no correlation with the counterpart of “Con
35、trol data“. 4 Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: DRM Digital Rights Management DXA Data exchanging Agent FTP File Transfer Protocol HTTP Hypertext Transfer Protocol IM Instant Message MMS Multimedia Message Service RAM Random Access Memory R
36、OM Read Only Memory SD Secure Digital SIM Subscriber Identity Module SMS Short Message Service URL Uniform Resource Locator USB Universal Serial Bus USIM User Services Identity Module W3C World Wide Web Consortium XML Extensible Markup Language Rec. ITU-T F.746.2 (02/2014) 3 5 Conventions None. 6 Ge
37、neral Under many circumstances there is a need to exchange user data between terminals or network entities and another data depository. For example, a user may want to replace a terminal with a new terminal without losing personal data, such as contacts and received messages, stored in the original
38、one. The data exchange process might be initiated by the user manually or by a network application automatically, and multiple categories of data might be involved in an exchange process. However, the terminals or entities acting as the source and destination in the exchange process may use differen
39、t operating systems or different internal data expressions for the same kind of data. Without a consistent approach, accurate exchange of the user data is difficult to realize. To facilitate the exchange process and make it as simple as possible for the users, this Recommendation describes an exchan
40、ge approach by using a data package as a container to encapsulate user data and specifies the recommended data syntax for parsing or generating the data package. 7 Scenarios of user data exchange 7.1 User data grouping The user data includes the users personal data, device configuration parameters a
41、nd personalized application data, and can be stored in terminals or other entities, no matter the device type. User data may take various forms such as binary, text or multimedia files depending on the corresponding data category. It could be stored in different locations such as internal memory (RA
42、M, ROM, etc.) and external memory (SIM/USIM, SD card, hard disk, etc.). 7.1.1 Private user data Private user data is created by the user for a special purpose or generated by the users operations and contains important information about the user. Examples of private user data include: Contact inform
43、ation (including phonebook) Messages (including SMS, MMS, IM and e-mail) Calendar information Favourite uniform resource locator (URL) lists and bookmarks Call and browsing history 7.1.2 Device configuration data Device configuration data is the data that a terminal allows users to access and modify
44、, so as to personalize what the terminal displays and the way it behaves. Examples of device configuration data include: Terminal theme, fonts, wallpaper and screensaver Language settings Date/Time and location settings Energy saving settings Accessibility settings 4 Rec. ITU-T F.746.2 (02/2014) 7.1
45、.3 Personalized application data Personalized application data is the data that applications allow users to access and modify, so as to personalize the way an application operates or behaves, including: Service dependent settings or parameters Application settings or application files 7.2 Scenario d
46、escription A basic user data exchange scenario is that a terminal or an entity wants to receive discrete sets of user data from another terminal or to send data to another terminal. For example, a mobile phone desires to retrieve all the contacts and calendar data stored in another terminal. Another
47、 example would be that an entity in the network needs to receive a status report or needs to retrieve the browsing history of the streaming media player on the terminal to use for later statistical purposes. In those cases, typically user data is of small size and may be stored in different formats
48、in the two terminals because of different operating platforms or different data management applications. To exchange data, normally the data providing party will generate a data package which contains multiple categories of data, and the other party receives the data package and performs data analys
49、is, followed by certain operations according to the original purpose of this data acquisition process. 8 User data exchange method 8.1 General procedure For a typical user data exchange scenario, the data exchange process can be summarized into several steps: Export, transfer and analyse. Export: Export selected user data from party A as an accessible data package. Transfer: Party A transfers the selected package to party B by any approach. This step does not need to be in real tim
