1、 ETSI TR 102 397-14-1 V1.1.1 (2005-08)Technical Report Open Service Access (OSA);Mapping of Parlay X Web Services to Parlay/OSA APIs;Part 14: Presence Mapping;Sub-part 1: Mapping to Presence and Availability ManagementETSI ETSI TR 102 397-14-1 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01021-14-01-OSA
2、Keywords API, OSA, service 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 7803/88 Important notice Individual copies of
3、 the present document can be downloaded from: http:/www.etsi.org The present document 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).
4、 In case of dispute, the reference shall be the printing on ETSI printers of the PDF 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
5、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 following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as a
6、uthorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2005. The Parlay Group 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its
7、 Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit 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 TR 102 397-14-1 V1.1.1 (2005-08) 3 Contents Intellectua
8、l Property Rights4 Foreword.4 1 Scope 5 2 References 5 3 Definitions and abbreviations.5 3.1 Definitions5 3.2 Abbreviations .6 4 Mapping Description6 5 Sequence Diagrams 7 5.1 Presence Supplier and Consumer .7 6 Detailed Mapping Information.8 6.1. Data Mappings .8 6.2 Operations 8 6.2.1 subscribePre
9、sence .8 6.2.2 getUserPresence8 6.2.3 startPresenceNotification 8 6.2.4 endPresenceNotification .9 6.2.5 statusChanged .9 6.2.6 statusEnd.9 6.2.7 notifySubscription.9 6.2.8 subscriptionEnded.9 6.2.9 publish 9 6.2.10 getOpenSubscriptions .9 6.2.11 updateSubscriptionAuthorization .9 6.2.12 getMyWatche
10、rs.9 6.2.13 getSubscribedAttributes9 6.2.14 blockSubscription .9 6.2.15 Unmapped Elements.10 6.3 Exceptions 10 7 Additional Notes 10 History 11 ETSI ETSI TR 102 397-14-1 V1.1.1 (2005-08) 4 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been decl
11、ared 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 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which
12、 is available from the ETSI Secretariat. Latest updates are available on the ETSI Web 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
13、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 Report (TR) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advance
14、d Networking (TISPAN). The present document is part 14, sub-part 1, of a multi-part deliverable covering Open Service Access (OSA); Mapping of Parlay X Web Services to Parlay/OSA APIs, as identified below: Part 1: “Common Mapping“; Part 2: “Third Party Call Mapping“; Part 3: “Call Notification Mappi
15、ng“; Part 4: “Short Messaging Mapping“; Part 5: “Multimedia Messaging Mapping“; Part 6: “Payment Mapping“; Part 7: “Account Management Mapping“; Part 8: “Terminal Status Mapping“; Part 9: “Terminal Location Mapping“; Part 10: “Call Handling Mapping“; Part 11: “Audio Call Mapping“; Part 12: “Multimed
16、ia Conference Mapping“; Part 14: “Presence Mapping“; Sub-part 1: “Mapping to Presence and Availability Management“ Sub-part 2: “Mapping to SIP/IMS Networks“. NOTE: Part 13 has not been provided as there is currently no defined mapping between ES 202 391-13 1 and the Parlay/OSA APIs. If a mapping is
17、developed, it will become part 13 of this series. The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. ETSI ETSI TR 102 397-14-1 V1.1.1 (2005-08) 5 1 Scope The Parlay X Web Services provide powerful yet simple, highly abstracted, imaginati
18、ve, telecommunications functions that application developers and the IT community can both quickly comprehend and use to generate new, innovative applications. The Open Service Access (OSA) specifications define an architecture that enables application developers to make use of network functionality
19、 through an open standardized interface, i.e. the Parlay/OSA APIs. The present document specifies the mapping of the Parlay X Presence Web Service to the Presence and Availability Management (PAM) Service Capability Feature (SCF). 2 References For the purposes of this Technical (TR), the following r
20、eferences apply: 2 ETSI TR 121 905: “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Vocabulary for 3GPP Specifications (3GPP TR 21.905)“. 3 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/
21、TR/2001/REC-xmlschema-2-20010502/. 4 ETSI TR 102 397-1: “Open Service Access (OSA); Parlay X Web Services Part 1: Common Mapping“. 5 ETSI ES 202 915-14: “Open Service Access (OSA); Application Programming Interface (API); Part 14: Presence and Availability Management SCF (Parlay 4)“. 6 ETSI ES 202 3
22、91-13: “Open Service Access (OSA); Parlay X Web Services; Part 13: Address List Management“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 102 397-1 4 and the following apply: applications: for Instant Messaging, Push
23、to Talk, or call control and other purposes may become clients of the Presence Web Service NOTE: We assume that these applications belong to a watcher and authenticate to the services in the name of the watcher. identity: representation of a user in the real world NOTE: See ES 202 915-14 5, clause 4
24、.4.1. presence attributes: contain information about a presentity NOTE: An attribute has a name and a value and can be supplied by any device, application or network module that can be associated to the presentitys identity. A watcher can obtain attributes only after he has successfully subscribed t
25、o them. Examples for attributes are activity, location type, communication means, etc. ETSI ETSI TR 102 397-14-1 V1.1.1 (2005-08) 6 presence information: set of attributes that characterize the presentity such as current activity, environment, communication means and contact addresses NOTE: Only the
26、 system and the presentity have direct access to this information, which may be collected and aggregated from several devices associated to the presentity. subscription: relationship between a watcher and present data NOTE: Before a watcher can access the presence data, he has to suscribe to it. One
27、 possibility the API provides is an end-to-end subscription concept, in which only identities that have accepted a subscription to their presence can be addressed. Subscriptions can be also automatically handled by server policies edited by the presentity or other authorized users. The service/proto
28、col to manage those policies is out of the scope of the present document. NOTE: This definition is not related to the term “subscription“ in ETSI TR 121 905 2. watcher and presentity: We use these names to denote the role of the client connected to the presence services. NOTE: As in ES 202 915-14 5
29、the watcher and the presentity have to be associated to identities registered to the system, i.e. users, groups of users or organizations. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 102 397-1 4 and the following apply: ACL Access Control List IMS IP Mul
30、timedia Subsystem PAM Presence and Availability Management PIDF Presence Information Data Format RPID Rich Presence Information Data SCF Service Capability Feature SIMPLE SIP for Instant Messaging and Presence Leveraging Extensions SIP Session Initiation Protocol XML eXtensible Markup Language4 Mapp
31、ing Description The Presence capability can be implemented with Parlay/OSA PAM. It is applicable to ETSI OSA 2.x/3.x, Parlay/OSA 4.x/5.x and 3GPP Releases 5/6. ETSI ETSI TR 102 397-14-1 V1.1.1 (2005-08) 7 5 Sequence Diagrams 5.1 Presence Supplier and Consumer Presence Web Service : IpAppPAMEventHand
32、lerWatcher Application : PresenceConsumerNotificationsPresence Web Service : PresenceConsumerPAM Server : IpPAMAvailabilityPAM Server : IpPAMEventHandlerPAM Server : IpPAMAgentPresencePresence Web Service : PresenceSupplierPresentity Application :after a while the user logs onthe watcher can access
33、presence data by polling.if there is a policy for this subscription request, no interaction with the presentity is necessary. or through notificationsuser status changes (for whatever reason)subscribePresencegetUserPresencestartPresenceNotificationnotifySubscriptiongetOpenSubscriptionsget user answe
34、rupdateSubscriptionAuthorisationpublishgetMyWatchersgetSubscribedAttributesblockSubscriptionpublishgetAvailabilityregisterForEventsetAgentPresence(internal event)endPresenceNotificationderegisterFromEventdetermine availability from agent / identity presenceagent presence or identity presencesetAgent
35、PresenceIf the PAM application cannot obtain ACLs from the PAM server, it can test whether it can currently obtain availability (meaning that access is allowed)getPreference(internal: create open subscription)eventNotify(internal)getAvailabilitystatusChangeddetermine availability from agent / identi
36、ty presenceNo corresponding PAM methods. The web service can however monitor the watchers via PAM events (PAM_CE_ WATCHERS_CHANGED) and return the list upon request.setPreferenceeventNotifyendSubscriptionNotificationthe web service has to listen for the watchers changed event so it will be notified
37、if a watcher is deleted.setPreference(does not exist)notifySubscriptiongetAvailabilityNo corresponding PAM method. The web service can however monitor the watchers via PAM events (PAM_CE_ WATCHERS_CHANGED) and forward the event when the watcher application is added.Figure 1 ETSI ETSI TR 102 397-14-1
38、 V1.1.1 (2005-08) 8 6 Detailed Mapping Information 6.1. Data Mappings In PIDF (and therefore in RPID, and in Parlay X) the presence data of a presentity consists of the identifier of the presentity plus a set of tuples describing her presence state. A tuple having a contact address can be mapped to
39、a PAM agent belonging to the presentity. The following table maps the RPID structure to PAM attributes. If the SIMPLE server does not support RPID, only the basic type from PIDF can be mapped to the lower layer. Rich Presence can still be used within the Parlay X layer. RPID PAM Presentity (URL) Uni
40、que identifier of the identity Tuple Set of attributes belonging either to the identity or to one of her agents Contact address of tuple (optional) Identifier of agent belonging to the identity. If not set, the tuple describes identity attributes Status element of tuple The actual presence attribute
41、s of the agent or identity. RPID: class of tuple Agent or identity type Status: basic Boolean attribute called status RPID: other status elements Attributes with corresponding names and types Not supported Other attributes (arbitrary name and type) RPID: tuple type No mapping RPID: relationship No m
42、apping Not currently supported; still under discussion Capabilities of agents, capability attributes Notes on presentities Identity attribute Notes on tuples Identity/agent attribute Presence vs. Availability. The mapping to the PAM server has to take into account that Parlay X Presence does not sup
43、port the distinction between availability and presence. The Parlay X Web Service offers PAM availability information to its applications and stores PAM presence information at the PAM server. Identities and Agents. Pams notion of agents and identities is not clearly supported by the RPID model. Depe
44、nding on the data at hand, the Parlay X service and the SIMPLE server will use either the IpPAMIdentityPresence or the IpPAMAgentPresence interfaces of the PAM server. The computation of availability information is up to the PAM server. Parlay X Subscription Data. Parlay X subscription data describe
45、s who is allowed to access which attributes of a presentity. This corresponds to the access control lists protecting PAM availability information. The Parlay X subscription state “pending“ cannot be mapped to ACLs. 6.2 Operations 6.2.1 subscribePresence If the watcher is already on the ACL of the pr
46、esentity (this can be checked with the method getPreference() on the IpPAMAvailability interface), the web service can answer the request immediately. If not, this method does not map directly to PAM, as the ACL has no “pending“ state. A solution is a new presentity identity attribute listing all pe
47、nding subscriptions. 6.2.2 getUserPresence This operation maps to the Parlay/OSA PAM method getAvailability on the IpPAMAvailability interface. 6.2.3 startPresenceNotification This operation maps to the Parlay/OSA PAM method registerForEvent on the IpPAMEventHandler interface. ETSI ETSI TR 102 397-1
48、4-1 V1.1.1 (2005-08) 9 6.2.4 endPresenceNotification This operation maps to the Parlay/OSA PAM method deregisterForEvent on the IpPAMEventHandler interface. 6.2.5 statusChanged The Parlay/OSA PAM method eventNotify on the IpAppPAMEventHandler interface maps to this operation. 6.2.6 statusEnd The Par
49、lay/OSA PAM method eventNotify on the IpAppPAMEventHandler interface maps to this operation. 6.2.7 notifySubscription As subscriptions do not map well to PAM, no PAM method maps directly to this operation. The web service would have to constantly monitor the ACLs of all presentities the watcher wants to subscribe to (using getPreference(). In this way, if the watcher is added to an ACL, the web service can invoke notifySubscription. 6.2.8 subscriptionEnded The same applies in case of subscriptionEnded: If the watcher is removed from an ACL, the web
