您的当前位置：首页 OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C

来源：小侦探旅游网

Home Subscription Agent (HSA) Specification

Candidate Version 1.0 – 17 Sep 2009

Open Mobile Alliance

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 2 (15)

Use of this document is subject to all of the terms and conditions of the Use Agreement located at http://www.openmobilealliance.org/UseAgreement.html.

Unless this document is clearly designated as an approved specification, this document is a work in process, is not an approved Open Mobile Alliance™ specification, and is subject to revision or removal without notice.

You may use this document or any part of the document for internal or educational purposes only, provided you do not

modify, edit or take out of context the information in this document in any manner. Information contained in this document may be used, at your sole risk, for any purposes. You may not use this document in any other manner without the prior

written permission of the Open Mobile Alliance. The Open Mobile Alliance authorizes you to copy this document, provided that you retain all copyright and other proprietary notices contained in the original materials on any copies of the materials and that you comply strictly with these terms. This copyright permission does not constitute an endorsement of the products or services. The Open Mobile Alliance assumes no responsibility for errors or omissions in this document.

Each Open Mobile Alliance member has agreed to use reasonable endeavors to inform the Open Mobile Alliance in a timely manner of Essential IPR as it becomes aware that the Essential IPR is related to the prepared or published specification. However, the members do not have an obligation to conduct IPR searches. The declared Essential IPR is publicly available to members and non-members of the Open Mobile Alliance and may be found on the “OMA IPR Declarations” list at http://www.openmobilealliance.org/ipr.html. The Open Mobile Alliance has not conducted an independent IPR review of this document and the information contained herein, and makes no representations or warranties regarding third party IPR, including without limitation patents, copyrights or trade secret rights. This document may contain inventions for which you must obtain licenses from third parties before making, using or selling the inventions. Defined terms above are set forth in the schedule to the Open Mobile Alliance Application Form.

NO REPRESENTATIONS OR WARRANTIES (WHETHER EXPRESS OR IMPLIED) ARE MADE BY THE OPEN MOBILE ALLIANCE OR ANY OPEN MOBILE ALLIANCE MEMBER OR ITS AFFILIATES REGARDING ANY OF THE IPR‟S REPRESENTED ON THE “OMA IPR DECLARATIONS” LIST, INCLUDING, BUT NOT LIMITED TO THE ACCURACY, COMPLETENESS, VALIDITY OR RELEVANCE OF THE INFORMATION OR WHETHER OR NOT SUCH RIGHTS ARE ESSENTIAL OR NON-ESSENTIAL.

THE OPEN MOBILE ALLIANCE IS NOT LIABLE FOR AND HEREBY DISCLAIMS ANY DIRECT, INDIRECT, PUNITIVE, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR EXEMPLARY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF DOCUMENTS AND THE INFORMATION CONTAINED IN THE DOCUMENTS. © 2009 Open Mobile Alliance Ltd. All Rights Reserved.

Used with the permission of the Open Mobile Alliance Ltd. under the terms set forth above.

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 3 (15)

Contents

SCOPE ................................................................................................................................................................................ 4 2. REFERENCES .................................................................................................................................................................. 5 2.1 NORMATIVE REFERENCES .......................................................................................................................................... 5 2.2 INFORMATIVE REFERENCES ....................................................................................................................................... 5 3. TERMINOLOGY AND CONVENTIONS ...................................................................................................................... 6 3.1 CONVENTIONS ............................................................................................................................................................. 6 3.2 DEFINITIONS ................................................................................................................................................................ 6 3.3 ABBREVIATIONS .......................................................................................................................................................... 7 4. INTRODUCTION ............................................................................................................................................................. 8 4.1 VERSION 1.0 ................................................................................................................................................................ 8 5. FUNCTIONAL DESCRIPTION OF THE HOME SUBSCRIPTION AGENT ........................................................... 9 5.1 SUBSCRIPTION SERVICE AUTHORIZATION ................................................................................................................. 9 5.2 LIMITING THE NUMBER OF SUBSCRIPTIONS .............................................................................................................. 9 5.3 HANDLING OF EVENT NOTIFICATION SUPPRESSION ................................................................................................. 9 5.3.1 Handling of event notification suppression conditions ........................................................................................ 9 5.3.2 Direct Event Notification Suppression............................................................................................................... 10 APPENDIX A. CHANGE HISTORY (INFORMATIVE) .............................................................................................. 11 A.1 APPROVED VERSION HISTORY ................................................................................................................................. 11 A.2 DRAFT/CANDIDATE VERSION 1.0 HISTORY ............................................................................................................. 11 APPENDIX B. STATIC CONFORMANCE REQUIREMENTS (NORMATIVE) ..................................................... 12 B.1 HOME SUBSCRIPTION AGENT ................................................................................................................................... 12 APPENDIX C. COMMON CONTENT TYPES (NORMATIVE) ................................................................................. 13 C.1 PRESENCE-BASED EVENT NOTIFICATION SUPPRESSION FILTER ............................................................................ 13 C.1.1 MIME Type ....................................................................................................................................................... 13 C.1.2 XML Schema ..................................................................................................................................................... 13 C.1.3 Structure and Data Semantics ............................................................................................................................ 13 C.1.4 Evaluation .......................................................................................................................................................... 14 C.1.5 Examples (Informative) .................................................................................................................................. 14

Figures

No table of figures entries found.

Tables

No table of figures entries found.

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 4 (15)

1. Scope

This document provides the specification for the Home Subscription Agent (HSA) in the OMA Presence SIMPLE 2.0 Enabler.

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 5 (15)

2. References

2.1

OMA [PRS_AD] [PRS_Spec] IETF

[IETF-EventThrottle]

Normative References

“Presence SIMPLE Architecture”, Version 2.0, Open Mobile Alliance, OMA-AD-Presence_ SIMPLE-V2_0, URL: http://www.openmobilealliance.org/

“Presence SIMPLE Specification”, Version 2.0, Open Mobile Alliance, OMA-TS-Presence_SIMPLE-V2_0, URL: http://www.openmobilealliance.org/

IETF draft-niemi-sipping-event-throttle-07 “Session Initiation Protocol (SIP) Event Notification Extension for

Notification Throttling”, A. Niemi et al., Oct 22, 2008, URL: http://www.ietf.org/internet-drafts/draft-niemi-sipping-event-throttle-07.txt Note: IETF Draft work in progress

[IETF-SubNotEtag]

IETF draft-ietf-sip-subnot-etags-03 “An Extension to Session Initiation Protocol (SIP) Events for Conditional Event Notification”, A. Niemi, Jul 14, 2008, URL: http://www.ietf.org/internet-drafts/draft-ietf-sip-subnot-etags-03.txt Note: IETF Draft work in progress

[RFC3265] [RFC4661]

IETF RFC 3265 “Session Initiation Protocol (SIP)-Specific Event Notification”, A. B. Roach, Jun 2002, URL: http://www.ietf.org/rfc/rfc3265.txt

IETF RFC 4661 “An Extensible Markup Language (XML) Based Format for Event Notification Filtering”, H. Khartabil et al., Sep 2006, URL: http://www.ietf.org/rfc/rfc4661.txt

IETF RFC 4662 “A Session Initiation Protocol (SIP) Event Notification Extension for Resource Lists”, A. B. Roach et al., Aug 2006, URL: http://www.ietf.org/rfc/rfc4662.txt

IETF RFC 5367 “Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)”, G. Camarillo et al., Oct 2008,

URL: http://www.ietf.org/rfc/rfc5367.txt

3GPP TS 23.141 “Presence Service; Architecture and functional description”, URL: http://www.3gpp.org/ftp/Specs/archive/23_series/23.141/

3GPP2 X.S0027-001 “Presence Service; Architecture and functional description”, URL: http://www.3gpp2.org/Public_html/specs/index.cfm

[RFC4662]

[RFC5367]

3GPP/3GPP2 [3GPP-TS_23.141] [3GPP2-X.S0027-001]

2.2

Void.

Informative References

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 6 (15)

3. Terminology and Conventions

3.1

Conventions

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119]. All sections and appendixes, except “Scope” and “Introduction”, are normative, unless they are explicitly indicated to be informative.

3.2

Notifier

Definitions

Use definition from [PRS_AD]. Use definition from [PRS_AD]. Use definition from [PRS_AD]. Use definition from [PRS_AD].

A service that makes use of the SIP event notification mechanism as defined in [RFC3265].

Presence Information Presence Information Element Subscriber

Subscription Service

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 7 (15)

3.3

AD HSA IETF IMS IP MIME MMD OMA PRS RD RFC SIMPLE SIP UE XML

Abbreviations

Architecture Document Home Subscription Agent Internet Engineering Task Force IP Multimedia Subsystem Internet Protocol

Multipurpose Internet Mail Extensions Multimedia Domain Open Mobile Alliance Presence SIMPLE Requirement Document Request For Comments

SIP for Instant Messaging and Presence Leveraging Extensions Session Initiation Protocol User Equipment

eXtensible Markup Language

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 8 (15)

4. Introduction

This document provides the specification for the Home Subscription Agent (HSA) in the OMA Presence SIMPLE 2.0 Enabler.

4.1 Version 1.0

The OMA Presence SIMPLE 2.0 enabler separates the functions for entity that controls the Subscriber‟s service use in the Subscriber‟s home domain into a specification of its own to simplify reuse by other enablers. The functions included in this specification are:

  

Subscription service authorization; Limiting the number of subscriptions; and Regulation of event notifications.

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 9 (15)

5. Functional Description of the Home Subscription Agent

The HSA is an entity that controls the Subscriber‟s access to the Subscription Service and optimizes the notification traffic based on the Subscriber‟s preferences or local policy.

5.1 Subscription Service Authorization

Upon receiving the SUBSCRIBE request from a Subscriber, the HSA:

1) SHALL, if a local policy for Subscription Service authorization exists, check whether the Subscriber is authorized to

use the Subscription Service per the local policy and generate a 403 (Forbidden) response to the Subscriber if authorization fails; 2) SHALL, if limiting the number of subscriptions is supported, perform the procedures of section 5.2; 3) SHALL, if event notification suppression is supported, perform the procedures of section 5.3; and

4) SHALL, if event notification suppression is not supported, forward the received SUBSCRIBE request to the SIP/IP

Core.

When the SIP/IP Core corresponds with 3GPP IMS or 3GPP2 MMD networks, the above functionalities of the HSA MAY be implemented in the P-CSCF and/or S-CSCF as defined in [3GPP-TS_23.141] and [3GPP2-X.S0027-001] respectively. NOTE: The method how the SUBSCRIBE request is routed to the HSA depends on the underlying SIP/IP Core and is out of scope of this specification.

5.2 Limiting the Number of Subscriptions

The HSA MAY have a local policy to limit the maximum number of simultaneous subscriptions for a Subscriber. If the HSA determines to reject an initial subscription due to the current number of active subscriptions initiated by the Subscriber being equal to or greater than the maximum, the HSA SHALL send a 480 (Maximum number of subscriptions exceeded) response. The response MAY include the Retry-After header field (e.g. based on the expiry of active subscriptions initiated by the Subscriber) in order to suggest to the Subscriber not to retry the subscription prior to the Retry-After time.

5.3



Handling of Event Notification Suppression

SHALL support the handling of event notification suppression conditions. These conditions MAY be based on a local policy, or supplied by the event notification suppression filters set by the Subscriber as described in Appendix C.1, or the combination of local policy and the event notification suppression filters; and SHALL support direct event notification suppression to suppress notifications at the Notifier.

The HSA MAY support event notification suppression. If supported, the HSA:



5.3.1 Handling of event notification suppression conditions

Upon successful authorization of the SUBSCRIBE request from a Subscriber, the HSA:

1) SHALL check whether the body contains a valid „application/vnd.oma.suppnot+xml‟ content as described in

Appendix C.1 or whether there is any other event notification suppression conditions set by the local policy. In case of invalid content and no local policy the HSA SHALL forward the SUBSCRIBE request targeted to the Notifier; 2) SHALL, in case of a valid „application/vnd.oma.suppnot+xml‟ content or event notification suppression conditions

by local policy, terminate the SUBSCRIBE request, install the subscription and send a 202 (Accepted) response to the Subscriber as described in [RFC3265]. The HSA SHALL also extract the event notification suppression filters from the „application/vnd.oma.suppnot+xml‟ content; 3) SHALL generate a back-end subscription request targeted to the Notifier according to the subscriber procedures

described in [RFC3265], [RFC4662] or [RFC5367], depending on the incoming subscription. The HSA SHALL

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 10 (15)

preserve all headers and payloads except the „application/vnd.oma.suppnot+xml‟ content from the received SUBSCRIBE request into the back-end SUBSCRIBE request;

4) SHALL generate a presence subscription request to the Subscriber‟s Presence Information according to the

procedures described in section [PRS_Spec] “Subscription to Presence Information”; and 5) SHALL, upon receiving a response for the back-end subscription from the Notifier, send a NOTIFY request to the

Subscriber containing a Subscription-State header with the value of „active‟. During the Subscriber‟s subscription lifetime, the HSA:

1) SHALL evaluate the presence-based event notification suppression filters against the Subscriber‟s Presence

Information; and 2) SHALL, if a match is found, request the Notifier to suppress the notifications according to the procedures described

in section 5.3.2.

5.3.2 Direct Event Notification Suppression

Direct event notification suppression is a mechanism that enables the HSA to request the Notifier to suppress event notifications while keeping the corresponding event subscription state active.

Direct event notification suppression can be requested using one of the following options:

If the HSA supports conditional event notification procedures as described in [IETF-SubNotEtag], the HSA SHALL issue a SUBSCRIBE request to refresh the subscription and include a wildcarded Suppress-If-Match header field using the special \"*\" entity-tag value as described in [IETF-SubNotEtag] “Generating SUBSCRIBE Requests”; or  If the HSA supports event notification throttling procedures as described in [IETF-EventThrottle], the HSA SHALL

issue a SUBSCRIBE request to refresh the subscription and include a throttle parameter set to the remaining subscription expiration value as described in [IETF-EventThrottle] “Selecting the Throttle Interval”.

If the HSA supports both of the above options, the HSA SHALL indicate the presence notification suppression request using the conditional event notification procedure.



Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 11 (15)

Appendix A. Change History

A.1 Approved Version History

Reference n/a n/a (Informative)

Description No prior version Date A.2 Draft/Candidate Version 1.0 History

Document Identifier Draft Versions OMA-TS-Presence_SIMPLE_HSA-V1_0 Date 04 Aug 2009 Sections All Description First version as agreed in OMA-PAG-2009-0129R01-INP_PRS2_new_HSA_TS. Application of 2009 template. CR incorporated: OMA-PAG-2009-0235 Status changed to Candidate by TP TP ref # OMA-TP-2009-0438-INP_PRS_V2_0_ERP_for_Notification 14 Aug 2009 Candidate Version OMA-TS-Presence_SIMPLE_HSA-V1_0 17 Sep 2009 4 N/A  2009 Open Mobile Alliance Ltd. All Rights Reserved.

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 12 (15)

Appendix B. Static Conformance Requirements

The notation used in this appendix is specified in [SCRRULES]. The SCR‟s defined in the following table include SCR for the HSA.

(Normative)

The following tags are used in the Function column to identify the release of the Presence SIMPLE enabler that the requirement was introduced:



PRSv2.0 – Requirement was introduced in Presence SIMPLE 2.0.

B.1 Home Subscription Agent

Item PRS-HSA-S-001-O PRS-HSA-S-002-O PRS-HSA-S-003-O PRS-HSA-S-004-O PRS-HSA-S-005-O Function Subscription Service authorization (PRSv2.0) Limiting number of subscriptions (PRSv2.0) Handling of event notification suppression (PRSv2.0) Handling of event notification suppression conditions (PRSv2.0) Direct event notification suppression (PRSv2.0) Reference 5.1 5.2 5.3 5.3.15.3 5.3.2 Requirement PRS-HSA-S-003-O PRS-HSA-S-003-O  2009 Open Mobile Alliance Ltd. All Rights Reserved.

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 13 (15)

Appendix C. Common Content Types

The common content types for this specification are described in this Appendix.

(Normative)

C.1 Presence-based Event Notification Suppression Filter

The presence-based event notification suppression filter specifies the conditions when the Subscriber wishes not to receive event notifications based on its Presence Information. A condition is evaluated by comparing the values of the condition with the Subscriber‟s Presence Information. If they match, the condition evaluates to true.

C.1.1 MIME Type

The MIME type for the presence-based event notification suppression filter SHALL be “application/vnd.oma.suppnot+xml”. Editor‟s Note: The MIME type shall be OMNA registered. C.1.2 C.1.3

XML Schema

Structure and Data Semantics

The presence-based event notification suppression filter SHALL conform to the XML schema described in [XSD_suppNot].

The presence-based event notification suppression filter SHALL conform to the structure and semantics as described in this subclause.

The root element :

a) MAY include any other attributes for the purposes of extensibility;

b) MAY include a element that contains the namespace bindings according to [RFC4661] “The Element”; c) SHALL include zero or more elements that contain the conditions for event notification

suppression. The element:

a) SHALL include one or more elements, each of which SHALL contain the binding between the prefix

and the namespace in a “prefix” attribute and a “namespace” attribute, respectively. This is used to express the XPATH formed Presence Information Elements or Presence Information Element attributes under elements. The element:

a) SHALL include a “id” attribute that contains the unique identification for the filter; b) MAY include any other attribute for the purposes of extensibility;

c) MAY include one or more elements that contain the Presence Information Elements or Presence

Information Element attributes that decide the suppression of the notifications; d) MAY include any other elements from other namespaces for the purposes of extensibility. The element:

a) MAY include any other attribute for the purposes of extensibility;

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 14 (15)

b) MAY include one or more elements, each of which contains the XPATH expression according

to [RFC4661] “Syntax for Referencing XML Items and Making Logical Expressions”, that identifies the Presence Information Elements or Presence Information Element attributes to be matched; c) MAY include any other elements from other namespaces for the purposes of extensibility. The element:

a) MAY include a “type” attribute that contains the expression type of the Presence Information Elements or Presence

Information Element attributes in a element. The default value is “xpath” in case of the absence of this attribute; b) MAY include any other attribute for the purposes of extensibility.

C.1.4 Evaluation

The evaluation of the presence-based event notification suppression filter is achieved as following:  The empty element SHALL remove any existing filters set in the HSA;

 The evaluation of each element under the root element SHALL be logically ORed;  The evaluation of each child element under a element SHALL be logically ANDed;  The evaluation of each child element under a element SHALL be logically ANDed;  The evaluation of a element SHALL be TRUE if the corresponding expression in the content results in identification of one or more elements in the Watcher‟s Presence Information;  The evaluation of an empty element SHALL be FALSE.

C.1.5 Examples (Informative)

The following is an example of the presence-based event notification suppression filter.

//pdm:tuple[*/op:service-id=\"org.openmobilealliance:PoC-session\" and pdm:deviceID=\"urn:uuid:d27459b7-8213-4395-aa77-ed859a3e5b3a\"]/op:session-participation[op:basic=\"open\"] //pdm:person/rpid:activities/rpid:away  2009 Open Mobile Alliance Ltd. All Rights Reserved.

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

OMA-TS-Presence_SIMPLE_HSA-V1_0-20090917-C Page 15 (15)

//pdm:device[pdm:deviceID=\"urn:uuid:d27459b7-8213-4395-aa77-ed859a3e5b3a\" and op:network-availability/op:network/pde:visited]

Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.

[OMA-Template-Spec-20090101-I]

因篇幅问题不能全部显示，请点此查看更多更全内容

查看全文