ITU-T J 367-2008 IPCablecom2 presence specification (Study Group 9)《IPCablecom 2现场规范》.pdf

《ITU-T J 367-2008 IPCablecom2 presence specification (Study Group 9)《IPCablecom 2现场规范》.pdf》由会员分享，可在线阅读，更多相关《ITU-T J 367-2008 IPCablecom2 presence specification (Study Group 9)《IPCablecom 2现场规范》.pdf（35页珍藏版）》请在麦多课文档分享上搜索。

1、 International Telecommunication Union ITU-T J.367TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2008) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom IPCablecom2 presence specification Recommendation ITU-T J.367 Rec. ITU-T J.367

2、(06/2008) i Recommendation ITU-T J.367 IPCablecom2 presence specification Summary Recommendation ITU-T J.367 adds the Presence functionality to the IPCablecom2 architecture. This feature enables the exchange of dynamic information about the state of a logical entity (e.g., person, device) and its av

3、ailability and willingness to communicate or to share. Source Recommendation ITU-T J.367 was approved on 13 June 2008 by ITU-T Study Group 9 (2005-2008) under Recommendation ITU-T A.8 procedure. ii Rec. ITU-T J.367 (06/2008) FOREWORD The International Telecommunication Union (ITU) is the United Nati

4、ons 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, operating and tariff questions and issuing Recommendations

5、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 turn, produce Recommendations on these topics. The approval of

6、 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 In this Recommendation, the expression “Administration“ is

7、 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.g. interoperability or applicability) and compliance with t

8、he 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 suggest that compliance with the Recommendation is required o

9、f any party. INTELLECTUAL PROPERTY RIGHTS ITU 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 evidence, validity or applicability of claimed Intellectual P

10、roperty 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, which may be required to implement this Recommendation. However,

11、 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 2009 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior

12、written permission of ITU. Rec. ITU-T J.367 (06/2008) iii CONTENTS Page 1 Scope 1 2 References. 1 2.1 Normative References 1 2.2 Informative References 2 2.3 Reference Acquisition 3 3 Terms and definitions . 3 4 Abbreviations, acronyms and conventions. 4 4.1 Abbreviations and Acronyms . 4 4.2 Conven

13、tions 5 5 IPCablecom2 Presence background . 6 5.1 Relationship with Existing Presence Solutions 7 5.2 IPCablecom2 Presence Document Organization 8 6 IPCablecom2 Presence Architecture 8 6.1 Presence Functional Components. 11 6.2 Presence Reference Points 14 6.3 Presence Protocols and Data Formats 17

14、6.4 XDM Protocols. 21 6.5 Client Provisioning and Management 22 6.6 Accounting . 22 6.7 Security. 22 6.8 Codec 22 7 IPCablecom2 Presence Requirements 22 7.1 OMA Presence Enabler 23 7.2 OMA XDM Enabler. 23 7.3 Provisioning and Management . 24 Appendix I Informative Call Flow 25 Rec. ITU-T J.367 (06/2

15、008) 1 Recommendation ITU-T J.367 IPCablecom2 presence specification 1 Scope This Recommendation adds the Presence functionality to the IPCablecom2 architecture. This enables the exchange of dynamic information about the state of a logical entity (e.g., person, device) and its availability and willi

16、ngness to communicate or to share. This information can be exploited, for example, by application servers to optimize or customize services. This Recommendation describes the IPCablecom2 Presence architecture that is aligned with the OMA Presence service. This Recommendation also adopts the normativ

17、e requirements from the relevant OMA specifications and identifies the exceptions where applicable (clause 7). It is an important objective of this work that interoperability between IPCablecom 2.0 and 3GPP IMS is provided. IPCablecom 2.0 is based upon 3GPP IMS, but includes additional functionality

18、 necessary to meet the requirements of cable operators. Recognizing developing converged solutions for wireless, wireline, and cable, it is expected that further development of IPCablecom 2.0 will continue to monitor and contribute to IMS developments in 3GPP, with the aim of alignment of 3GPP IMS a

19、nd IPCablecom 2.0. NOTE The structure and content of this Recommendation have been organized for ease of use by those familiar with the original source material; as such, the usual style of ITU-T recommendations has not been applied. 2 References 2.1 Normative References The following ITU-T Recommen

20、dations and other references contain 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 there

21、fore encouraged to investigate the 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

22、-alone document, the status of a Recommendation. OMA TS-PRS OMA-TS-Presence_SIMPLE-V1_0_1-20061128-A, Presence SIMPLE Specification, November 2006, Open Mobile Alliance. OMA TS-PRSXDM OMA-TS-Presence_SIMPLE_XDM-V1_0_1-20061128-A, Presence XDM Specification, November 2006, Open Mobile Alliance. OMA T

23、S-RLSXDM OMA-TS-Presence_SIMPLE_RLS_XDM-V1_0_1-20061128-A, Resource List Server (RLS) XDM Specification, November 2006, Open Mobile Alliance. OMA TS-SHDXDM OMA-TS-XDM_Shared-V1_0_1-20061128-A, Shared XDM Specification, November 2006, Open Mobile Alliance. OMA TS-XDM OMA-TS-XDM_Core-V1_0_1-20061128-A

24、, XML Document Management (XDM) Specification, November 2006, Open Mobile Alliance. 2 Rec. ITU-T J.367 (06/2008) 2.2 Informative References The following informative references are used in this Recommendation. ACCT Recommendation ITU-T J.363, IPCablecom2 data collection to support accounting. ARCH-F

25、RM-TR Recommendation ITU-T J.360, IPCablecom2 architecture framework. CODEC-MEDIA Recommendation ITU-T J.361, IPCablecom2 codec and media. ID PARTNOT IETF draft, draft-ietf-simple-partial-notify-10, Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information, July 20

26、07. IETF RFC 5025 IETF RFC 5025, Presence Authorization Rules, December 2007. IETF RFC 4825 IETF RFC 4825, The Extensible Markup Language (XML) Configuration Access Protocol (XCAP), May 2007. OMA AD-PRS OMA-AD-Presence_SIMPLE-V1_0-20061128-A, Presence SIMPLE Architecture Document, November 2006, Ope

27、n Mobile Alliance. OMA AD-XDM OMA-AD-XDM-V1_0-20060612-A, XML Document Management Architecture, June 2006, Open Mobile Alliance. OMA RD-PRS OMA-RD-Presence_SIMPLE-V1_0-20060725-A, Presence SIMPLE Requirements, July 2006, Open Mobile Alliance. OMA RD-XDM OMA-RD-XDM-V1_0-20060612-A, XML Document Manag

28、ement Requirements, June 2006, Open Mobile Alliance. OMA PRES-MO OMA-TS-Presence_SIMPLE_MO-V1_0_1-20061128-A, OMA Management Object for SIMPLE Presence, November 2006, Open Mobile Alliance. OMA XDM-MO OMA-TS-XDM_MO-V1_0_1-20061128-A, OMA Management Object for XML Document Management, November 2006,

29、Open Mobile Alliance. PKT 33.203 Recommendation ITU-T J.366.7 (2006), IPCablecom2 IP Multimedia Subsystem (IMS): Access security for IP-Based services. PKT 33.210 Recommendation ITU-T J.366.8, IPCablecom2 IP Multimedia Subsystem (IMS): Network domain security specification. IETF RFC 2617 IETF RFC 26

30、17, HTTP Authentication: Basic and Digest Access Authentication, June 1999. IETF RFC 3265 IETF RFC 3265, Session Initiation Protocol (SIP)-Specific Event Notification, June 2002. IETF RFC 3856 IETF RFC 3856, A Presence Event Package for the Session Initiation Protocol (SIP), August 2004. IETF RFC 38

31、57 IETF RFC 3857, A Watcher Information Event Template-Package for the Session Initiation Protocol (SIP), August 2004. IETF RFC 3863 IETF RFC 3863, Presence Information Data Format (PIDF), August 2004. IETF RFC 3903 IETF RFC 3903, Session Initiation Protocol (SIP) Extension for Event State Publicati

32、on, October 2004. IETF RFC 4119 IETF RFC 4119, A Presence-based GEOPRIV Location Object Format, December 2005. IETF RFC 4480 IETF RFC 4480, RPID: Rich Presence Extensions to the Presence Information Data Format (PIDF), July 2006. Rec. ITU-T J.367 (06/2008) 3 IETF RFC 4483 IETF RFC 4483, A Mechanism

33、for Content Indirection in Session Initiation Protocol (SIP) Messages, May 2006. IETF RFC 4660 IETF RFC 4660, Functional Description of Event Notification Filtering, September 2006. IETF RFC 4662 IETF RFC 4662, A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists, Augu

34、st 2006. TS 22.141 3GPP TS 22.141 V6.5.0, Presence Service; Stage 1 (Release 6), December 2005. TS 23.141 3GPP TS 23.141 V6.9.0, Presence Service; architecture and functional description (Release 6), December 2005. TS 24.141 3GPP TS 24.141 V6.7.0, Presence service using the IP Multimedia (IM) Core N

35、etwork (CN) subsystem; Stage 3 (Release 6), September 2006. TS 26.141 3GPP TS 26.141 V6.3.0, IP Multimedia System (IMS) Messaging and Presence; Media formats and codecs (Release 6), March 2006. TS 33.141 3GPP TS 33.141 V6.2.0, Presence service; Security (Release 6), September 2005. TS 33.220 3GPP TS

36、 33.220 V6.13.0, Generic Authentication Architecture (GAA); Generic bootstrapping architecture (Release 6), June 2007. TS 33.222 3GPP TS 33.222 V6.6.0, Generic Authentication Architecture (GAA); Access to network application functions using Hypertext Transfer Protocol over Transport Layer Security (

37、HTTPS), March 2006. 2.3 Reference Acquisition Internet Engineering Task Force (IETF), Internet: http:/www.ietf.org/. NOTE Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. The list of current Internet-Draf

38、ts can be accessed at http:/www.ietf.org/ietf/1id-abstracts.txt. 3rd Generation Partnership Project (3GPP), ETSI Mobile Competence Centre, 650 route des Lucioles, 06921 Sophia-Antipolis Cedex, France, Internet: http:/www.3gpp.org/. Open Mobile Alliance (OMA), OMA Office, 4275 Executive Square, Suite

39、 240, La Jolla, CA 92037, Fax +1-858-623-0743, Internet: http:/ 3 Terms and definitions This Recommendation uses the following terms defined elsewhere: 3.1 application usage: Detailed information on the interaction of an application with the XCAP server IETF RFC 4825. 3.2 enabler: A term used by OMA

40、 to mean “a technology intended for use in the development, deployment or operation of a service“. Examples of OMA Enablers are Device Management, Push-to-Talk over Cellular (PoC), Presence SIMPLE, and XML Document Management (XDM). 3.3 fetcher: A form of Watcher that has asked the Presence Service

41、for the Presence Information of one or more Presentities, but is not requesting a Notification from the Presence Service of (future) changes in a Presentitys Presence Information OMA RD-PRS. 3.4 notification: A message sent from the Presence Service to a Subscriber when there is a change in the Pres

42、ence Information of some Presentity of interest, as recorded in one or more Subscriptions OMA RD-PRS. 4 Rec. ITU-T J.367 (06/2008) 3.5 presence information: Dynamic set of information pertaining to a Presentity that may include Presence Information Elements such as the status, reachability, willingn

43、ess, and capabilities of that Presentity OMA RD-PRS. 3.6 presence information element: A basic unit of Presence Information OMA RD-PRS. 3.7 presence list: A list of presentities that can have their individual states subscribed to with a single subscription request (e.g., a subscription list). 3.8 pr

44、esence server: A logical entity that receives Presence Information from a multitude of Presence Sources pertaining to the Presentities it serves and makes this information available to Watchers according to the rules associated with those Presentities OMA RD-PRS. 3.9 presence service: The capability

45、 to support management of Presence Information between Watchers and Presentities, in order to enable applications and services to make use of Presence Information OMA RD-PRS. 3.10 presence source: A logical entity that provides Presence Information pertaining to exactly one or more Presentities to t

46、he Presence Server. 3GPP Presence User Agents, Presence Network Agents, and Presence External Agents are examples of Presence Sources OMA RD-PRS. 3.11 presentity: A logical entity that has Presence Information associated with it. This Presence Information may be composed of a multitude of Presence S

47、ources. A Presentity is most commonly a reference for a person, although it may represent a role such as “help desk“ or a resource such as “conference room #27“. Presentities are generally referenced by distinguished names, such as ““ or by phone numbers like “+19724735455“. In SIMPLE, presentities

48、are generally referenced using a sip:, pres: or tel: URL OMA RD-PRS. 3.12 subscriber: A form of watcher that has asked the Presence service to notify it immediately of changes in the Presence Information of one or more presentities OMA RD-PRS. 3.13 subscription: The information kept by the presence

49、service about a subscribers request to be notified of changes in the Presence Information of one or more presentities OMA RD-PRS. 3.14 watcher: Any uniquely identifiable entity that requests Presence Information about a presentity, or watcher information about a watcher, from the Presence service. Special types of watchers are fetchers and subscribers OMA RD-PRS. 3.15 watcher Information: Information about watchers th