OMARDPresenceSIMPLEV201223C.docx

OMARDPresenceSIMPLEV201223C.docx

《OMARDPresenceSIMPLEV201223C.docx》由会员分享，可在线阅读，更多相关《OMARDPresenceSIMPLEV201223C.docx（62页珍藏版）》请在冰豆网上搜索。

OMARDPresenceSIMPLEV201223C

PresenceSIMPLERequirements

CandidateVersion2.0–23Dec2008

OpenMobileAlliance

OMA-RD-Presence_SIMPLE-V2_0-20081223-C

UseofthisdocumentissubjecttoallofthetermsandconditionsoftheUseAgreementlocatedathttp:

//www.openmobilealliance.org/UseAgreement.html.

Unlessthisdocumentisclearlydesignatedasanapprovedspecification,thisdocumentisaworkinprocess,isnotanapprovedOpenMobileAlliance™specification,andissubjecttorevisionorremovalwithoutnotice.

Youmayusethisdocumentoranypartofthedocumentforinternaloreducationalpurposesonly,providedyoudonotmodify,editortakeoutofcontexttheinformationinthisdocumentinanymanner.Informationcontainedinthisdocumentmaybeused,atyoursolerisk,foranypurposes.YoumaynotusethisdocumentinanyothermannerwithoutthepriorwrittenpermissionoftheOpenMobileAlliance.TheOpenMobileAllianceauthorizesyoutocopythisdocument,providedthatyouretainallcopyrightandotherproprietarynoticescontainedintheoriginalmaterialsonanycopiesofthematerialsandthatyoucomplystrictlywiththeseterms.Thiscopyrightpermissiondoesnotconstituteanendorsementoftheproductsorservices.TheOpenMobileAllianceassumesnoresponsibilityforerrorsoromissionsinthisdocument.

EachOpenMobileAlliancememberhasagreedtousereasonableendeavorstoinformtheOpenMobileAllianceinatimelymannerofEssentialIPRasitbecomesawarethattheEssentialIPRisrelatedtothepreparedorpublishedspecification.However,themembersdonothaveanobligationtoconductIPRsearches.ThedeclaredEssentialIPRispubliclyavailabletomembersandnon-membersoftheOpenMobileAllianceandmaybefoundonthe“OMAIPRDeclarations”listathttp:

//www.openmobilealliance.org/ipr.html.TheOpenMobileAlliancehasnotconductedanindependentIPRreviewofthisdocumentandtheinformationcontainedherein,andmakesnorepresentationsorwarrantiesregardingthirdpartyIPR,includingwithoutlimitationpatents,copyrightsortradesecretrights.Thisdocumentmaycontaininventionsforwhichyoumustobtainlicensesfromthirdpartiesbeforemaking,usingorsellingtheinventions.DefinedtermsabovearesetforthinthescheduletotheOpenMobileAllianceApplicationForm.

NOREPRESENTATIONSORWARRANTIES（WHETHEREXPRESSORIMPLIED）AREMADEBYTHEOPENMOBILEALLIANCEORANYOPENMOBILEALLIANCEMEMBERORITSAFFILIATESREGARDINGANYOFTHEIPR’SREPRESENTEDONTHE“OMAIPRDECLARATIONS”LIST,INCLUDING,BUTNOTLIMITEDTOTHEACCURACY,COMPLETENESS,VALIDITYORRELEVANCEOFTHEINFORMATIONORWHETHERORNOTSUCHRIGHTSAREESSENTIALORNON-ESSENTIAL.

THEOPENMOBILEALLIANCEISNOTLIABLEFORANDHEREBYDISCLAIMSANYDIRECT,INDIRECT,PUNITIVE,SPECIAL,INCIDENTAL,CONSEQUENTIAL,OREXEMPLARYDAMAGESARISINGOUTOFORINCONNECTIONWITHTHEUSEOFDOCUMENTSANDTHEINFORMATIONCONTAINEDINTHEDOCUMENTS.

©2008OpenMobileAllianceLtd.AllRightsReserved.

UsedwiththepermissionoftheOpenMobileAllianceLtd.underthetermssetforthabove.

Contents

1.Scope（Informative）5

2.References6

2.1NormativeReferences6

2.2InformativeReferences6

3.TerminologyandConventions7

3.1Conventions7

3.2Definitions7

3.3Abbreviations8

4.Introduction（Informative）10

4.1OMAPresenceMandate10

4.2ServiceOverview10

4.3PresenceInformation,SourcesandWatchers10

4.4PresenceInformationProcessing11

4.5CommunicatingPreferencestoEnd-usersusingPresenceInformation12

5.UseCases（Informative）13

5.1Provisioning13

5.1.1SettingUpMyPresenceService13

5.2BasicPresenceUsage13

5.2.1SharingPresenceInformationA13

5.2.2SharingPresenceInformationB13

5.2.3FindingOtherPresenceUsers13

5.2.4UpdatingPresenceInformation13

5.2.5Presence-enabledAddress-book13

5.2.6ValidityPeriod13

5.2.7One-timeEventSubscriptionandNotification13

5.2.8RegulatingPublicationsofPresenceInformation13

5.2.9NotificationFiltering15

5.3NetworkPresence16

5.3.1UpdatethePresenceStatuswhentheMobileisOutofCoverage16

5.4Application-SpecificUseCases16

5.4.1EventBuddy16

5.5SecurityandPrivacy16

5.5.1PresencePrivacy17

5.5.2UsingthePresenceServiceforAdvertisingCapabilities17

5.5.3ReactiveAuthorization17

5.5.4ProactiveAuthorization:

17

5.5.5ProactiveAuthorization–CommonGroup,StrictlySecure17

5.5.6ProactiveAuthorization–CommonGroup17

5.5.7AuthorizationCategory17

6.Requirements（Normative）18

6.1High-LevelFunctionalRequirements18

6.1.1General18

6.1.2UserExperience19

6.1.3Features19

6.1.4PresenceInformation25

6.1.5XMLDocumentManagementforthePresenceService29

6.1.6NetworkInterfaces30

6.1.7Security30

6.1.8PresenceSourcesandWatchers31

6.1.9CollectingAccountingInformation31

6.1.10Operational&QualityofExperience32

6.1.11Interoperability33

AppendixA.ChangeHistory（Informative）34

A.1ApprovedVersionHistory34

A.2Draft/CandidateVersion2.0History34

Figures

Figure1.Presencespecificationlayers10

Figure2.PresenceServicecomponents.11

Figure3.ProcessingofPresenceInformation12

Tables

Table1:

GeneralRequirements19

Table2:

UserExperienceRequirements19

Table3:

FeaturesRequirements19

Table4:

FeaturesRequirements–PublishItems21

Table5:

FeaturesRequirements–SubscribeItems23

Table6:

FeaturesRequirements–NotifyItems23

Table7:

FeaturesRequirements–PreferencesItems24

Table8:

FeaturesRequirements–DelegationItems25

Table9:

PresenceInformationRequirements–ContentItems25

Table10:

PresenceInformationRequirements–FormatItems28

Table11:

PresenceInformationRequirements–EnablerSpecificItems29

Table12:

XMLDocumentManagementforthePresenceServiceRequirements–SharedListsItems29

Table13:

XMLDocumentManagementforthePresenceServiceRequirements–PresenceAuthorizationPoliciesItems29

Table14:

XMLDocumentManagementforthePresenceServiceRequirements–PresenceListsItems30

Table15:

NetworkInterfacesRequirements30

Table16:

SecurityRequirements31

Table17:

PresenceSourcesandWatchersRequirements31

Table18:

CollectingaccountinginformationRequirements31

Table19:

CollectingaccountinginformationRequirements–ChargingofPresentityItems32

Table20:

CollectingaccountinginformationRequirements–ChargingofWatcherItems32

Table21:

Operational&QualityofExperienceRequirements32

Table22:

InteroperabilitybetweenPresenceServiceProviders&ServiceEntitiesRequirements33

1.Scope（Informative）

ThisdocumentcontainsusecasesandrequirementsfortheOMAPresenceSIMPLE2.0enabler,takingintoconsiderationthedemandsofend-users,serviceproviders,andsystemimplementers.

2.References

NormativeReferences

OMA

[Privacy]

“OMAPrivacyRequirementsforMobileServices”,Version1.0,OpenMobileAlliance,OMA-RD_Privacy-V1_0,URL:

http:

//www.openmobilealliance.org/

[PRS_RD-V1_1]

“PresenceSIMPLERequirements”,Version1.1,OpenMobileAlliance,OMA-RD-Presence_SIMPLE-V1_1,URL:

http:

//www.openmobilealliance.org/

[PDE_RD]

“PresenceSIMPLEDataExtensionsRequirements”,Version1.0,OpenMobileAlliance,OMA-RD-Presence_Data_Ext-V1_0,URL:

http:

//www.openmobilealliance.org/

[XDM_RD]

“XMLDocumentManagementRequirements”,Version2.0,OpenMobileAlliance,OMA-RD-XDM-V2_0,URL:

http:

//www.openmobilealliance.org/

IETF

[RFC2119]

IETFRFC2119“KeywordsforuseinRFCstoIndicateRequirementLevels”,S.Bradner,Mar1997,URL:

http:

//www.ietf.org/rfc/rfc2119.txt

[RFC2778]

IETFRFC2778“AModelforPresenceandInstantMessaging”,M.Dayetal.,Feb2000,URL:

http:

//www.ietf.org/rfc/rfc2778.txt

[RFC3261]

IETFRFC3261“SessionInitiatonProtocol（SIP）”,J.Rosenbergetal.,Jun2002,URL:

http:

//www.ietf.org/rfc/rfc3261.txt

3GPP/3GPP2

[3GPP-TS_22.141]

3GPPTS22.141“PresenceService;Stage1”,URL:

http:

//www.3gpp.org/ftp/Specs/archive/22_series/22.141/

[3GPP-TS_23.141]

3GPPTS23.141“PresenceService;Architectureandfunctionaldescription”,URL:

http:

//www.3gpp.org/ftp/Specs/archive/23_series/23.141/

[3GPP2-S.R0062]

3GPP2S.R0062“PresenceforWirelessSystems;Stage1Requirements”,URL:

http:

//www.3gpp2.org/Public_html/specs/index.cfm

InformativeReferences

3GPP/3GPP2

[3GPP-TS_22.250]

3GPPTS22.250“IPMultimediaSubsystem（IMS）groupmanagement”,URL:

http:

//www.3gpp.org/ftp/Specs/archive/22_series/22.250/

3.TerminologyandConventions

Conventions

Thekeywords“MUST”,“MUSTNOT”,“REQUIRED”,“SHALL”,“SHALLNOT”,“SHOULD”,“SHOULDNOT”,“RECOMMENDED”,“MAY”,and“OPTIONAL”inthisdocumentaretobeinterpretedasdescribedin[RFC2119].

Allsectionsandappendixes,except“Scope”and“Introduction”,arenormative,unlesstheyareexplicitlyindicatedtobeinformative.

Definitions

CommunicationMeans

Indicatesamethodwherebycommunicationcantakeplace.InstantmessageserviceisoneexampleofaCommunicationMeans.（Source:

[RFC2778]）

DelegatedSubscription

TheSubscriptionmadeonbehalfofaDelegatingWatcher.

DelegatingWatcher

AWatcherthatauthorizesanotherWatchertosubscribeonhisbehalf.

Fetcher

AformofWatcherthathasaskedthePresenceServiceforthePresenceInformationofoneormorePresentities,butisnotrequestingaNotificationfromthePresenceServiceof（future）changesinaPresentity’sPresenceInformation.（Source:

[3GPP-TS_22.141]）

NOTE:

Thisdefinitiondiffersslightlyfromthe[RFC2778]definition,butisidenticalto[3GPP2-S.R0062].

Notification

AmessagesentfromthePresenceServicetoaSubscribed-watcherwhenthereisachangeinthePresenceInformation