ETSI TS 129 199-14 V7.4.1 (2008-01)

Technical Specification
Universal Mobile Telecommunications System (UMTS);
Open Service Access (OSA);
Parlay X web services;
Part 14: Presence
(3GPP TS 29.199-14 version 7.4.1 Release 7)

�
3GPP TS 29.199-14 version 7.4.1 Release 7 1 ETSI TS 129 199-14 V7.4.1 (2008-01)

Reference
RTS/TSGC-0529199-14v741
Keywords
UMTS
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 enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of 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).
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 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 authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 2 ETSI TS 129 199-14 V7.4.1 (2008-01)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared 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 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 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 Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 3 ETSI TS 129 199-14 V7.4.1 (2008-01)
Contents
Intellectual Property Rights.2
Foreword.2
Foreword.6
Introduction .6
1 Scope.7
2 References.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.9
4 Detailed service description .9
5 Namespaces.11
6 Sequence diagrams.11
6.1 Interface flow overview.11
7 XML Schema data type definition .13
7.1 PresenceAttributeType enumeration.13
7.2 ActivityValue enumeration.13
7.3 PlaceTypeValue enumeration.14
7.4 PrivacyType enumeration.15
7.5 SphereValue enumeration.15
7.6 CommunicationMeansType enumeration.15
7.7 CommunicationMeans structure.16
7.8 CommunicationValue structure.16
7.9 OtherValue structure.16
7.10 PresenceAttribute structure.16
7.10a AttributeTypeAndValue union.17
7.11 SubscriptionRequest structure.17
7.12 PresencePermission structure.17
7.13 CommunicationStatusType enumeration.17
7.14 PrivacyValue structure.18
7.15 MoodValue enumeration.18
7.16 PlaceIsValue structure.19
7.17 PlaceIsAudioValue enumeration.19
7.18 PlaceIsVideoValue enumeration.19
7.19 PlaceIsTextValue enumeration.19
7.20 RelationshipValue enumeration.20
7.21 TimeOffsetValue structure.20
7.22 StatusIconValue structure.20
7.23 Watcher structure.20
7.24 WatcherSubscriptionStatus enumeration.20
8 Web Service interface definition.21
8.1 Interface: PresenceConsumer.21
8.1.1 Operation: subscribePresence.21
8.1.1.1 Input message: subscribePresenceRequest.21
8.1.1.2 Output message: subscribePresenceResponse.22
8.1.1.3 Referenced faults.22
8.1.2 Operation: getUserPresence.23
8.1.2.1 Input message: getUserPresenceRequest .23
8.1.2.2 Output message: getUserPresenceResponse.23
8.1.2.3 Referenced faults.23
8.1.3 Operation: startPresenceNotification.24
ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 4 ETSI TS 129 199-14 V7.4.1 (2008-01)
8.1.3.1 Input message: startPresenceNotificationRequest.24
8.1.3.2 Output message: startPresenceNotificationResponse.24
8.1.3.3 Referenced faults.25
8.1.4 Operation: endPresenceNotification.26
8.1.4.1 Input message: endPresenceNotificationsRequest.26
8.1.4.2 Output message: endPresenceNotificationResponse.26
8.1.4.3 Referenced faults.26
8.2 Interface: PresenceNotification.27
8.2.1 Operation: statusChanged.27
8.2.1.1 Input message: statusChangedRequest.27
8.2.1.2 Output message: statusChangedResponse.27
8.2.1.3 Referenced faults.27
8.2.2 Operation: statusEnd.27
8.2.2.1 Input message: statusEndRequest .27
8.2.2.2 Output message: statusEndResponse.27
8.2.2.3 Referenced faults.27
8.2.3 Operation: notifySubscription.28
8.2.3.1 Input message: notifySubscriptionRequest .28
8.2.3.2 Output message: notifySubscriptionResponse .28
8.2.4 Operation: subscriptionEnded.28
8.2.4.1 Input message: subscriptionEndedRequest .28
8.2.4.2 Output message: subscriptionEndedResponse.28
8.3 Interface: PresenceSupplier.29
8.3.1 Operation: publish.29
8.3.1.1 Input message: publishRequest.29
8.3.1.2 Output message: publishResponse.29
8.3.1.3 Referenced faults.29
8.3.2 Operation: getOpenSubscriptions.30
8.3.2.1 Input message: getOpenSubscriptionsRequest.30
8.3.2.2 Output message: getOpenSubscriptionsResponse.30
8.3.2.3 Referenced faults.30
8.3.3 Operation: updateSubscriptionAuthorization.31
8.3.3.1 Input message: updateSubscriptionAuthorizationRequest .31
8.3.3.2 Output message updateSubscriptionAuthorizationResponse .31
8.3.3.3 Referenced faults.31
8.3.4 Operation: getMyWatchers.33
8.3.4.1 Input message: getMyWatchersRequest .33
8.3.4.2 Output message: getMyWatchersResponse.33
8.3.4.3 Referenced faults.33
8.3.5 Operation: getSubscribedAttributes.34
8.3.5.1 Input message: getSubscribedAttributesRequest .34
8.3.5.2 Output message: getSubscribedAttributesResponse .34
8.3.5.3 Referenced faults.34
8.3.6 Operation: blockSubscription.35
8.3.6.1 Input message: blockSubscriptionRequest.35
8.3.6.2 Output message: blockSubscriptionResponse.35
8.3.6.3 Referenced faults.35
8.4 Interface: PresenceSupplierNotificationManager.36
8.4.1 Operation: StartSubscriptionNotification .36
8.4.1.1 Input message: StartSubscriptionNotificationRequest.36
8.4.1.2 Output message: StartSubscriptionNotificationResponse.36
8.4.1.3 Referenced Faults.36
8.4.2 Operation: EndNotification.38
8.4.2.1 Input message: EndNotificationRequest.38
8.4.2.2 Output message: EndNotificationResponse.38
8.4.2.3 Referenced Faults.38
8.5 Interface: PresenceSupplierNotification.39
8.5.1 Operation: notifyOpenSubscription.39
8.5.1.1 Input message: notifyOpenSubscriptionRequest.39
8.5.1.2 Output message: notifyOpenSubscriptionResponse.39
8.5.1.3 Referenced faults.39
8.5.2 Operation: notifyError.39
ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 5 ETSI TS 129 199-14 V7.4.1 (2008-01)
8.5.2.1 Input message: notifyErrorRequest.39
8.5.2.2 Output message: notifyErrorResponse.39
8.5.2.3 Referenced faults.39
8.5.3 Operation: notifyEnd.40
8.5.3.1 Input message: notifyEndRequest.40
8.5.3.2 Output message: notifyEndResponse.40
8.5.3.3 Referenced faults.40
9 Fault definitions.41
9.1 ServiceException.41
9.1.1 SVC0220: No subscription request.41
9.1.2 SVC0221: Not a watcher .41
10 Service policies .41
Annex A (normative): WSDL of Presence API .42
Annex B (informative): Bibliography.43
Annex C (informative): Description of Parlay X Web Services Part 14: Presence for 3GPP2
cdma2000 networks .44
C.1 General Exceptions.44
C.2 Specific Exceptions.44
C.2.1 Clause 1: Scope .44
C.2.2 Clause 2: References .44
C.2.3 Clause 3: Definitions and abbreviations.44
C.2.4 Clause 4: Detailed service description.44
C.2.5 Clause 5: Namespaces .44
C.2.6 Clause 6: Sequence diagrams .45
C.2.7 Clause 7: XML Schema data type definition.45
C.2.8 Clause 8: Web Service interface definition .45
C.2.9 Clause 9: Fault definitions.45
C.2.10 Clause 10: Service policies.45
C.2.11 Annex A (normative):WSDL of Presence API .45
Annex D (informative): Change history .46
History .47

ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 6 ETSI TS 129 199-14 V7.4.1 (2008-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
3GPP acknowledges the contribution of the Parlay X Web Services specifications from The Parlay Group. The Parlay
Group is pleased to see 3GPP acknowledge and publish the present document, and the Parlay Group looks forward to
working with the 3GPP community to improve future versions of the present document.
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
Introduction
rd
The present document is part 14 of a multi-part deliverable covering the 3 Generation Partnership Project; Technical
Specification Group Core Network and Terminals; Open Service Access (OSA); Parlay X Web Services, as identified
below:
Part 1: "Common"
Part 2: "Third party call"
Part 3: "Call Notification"
Part 4: "Short Messaging"
Part 5: "Multimedia Messaging"
Part 6: "Payment"
Part 7: "Account management"
Part 8: "Terminal Status"
Part 9: "Terminal location"
Part 10: "Call handling"
Part 11: "Audio call"
Part 12: "Multimedia conference"
Part 13: "Address list management"
Part 14: "Presence"
Part 15: "Message Broadcast"
Part 16: "Geocoding"
Part 17: "Application driven Quality of Service (QoS)"
Part 18: "Device Capabilities and Configuration"
Part 19: "Multimedia streaming control"
Part 20: "Multimedia multicast session management"

ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 7 ETSI TS 129 199-14 V7.4.1 (2008-01)
1 Scope
The present document is Part 14 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).
The OSA specifications define an architecture that enables application developers to make use of network functionality
through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are
contained in 3GPP TS 23.198 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].
The present document specifies the Presence Web Service aspects of the interface. All aspects of the Presence Web
Service are defined here, these being:
• Name spaces.
• Sequence diagrams.
• Data definitions.
• Interface specification plus detailed method descriptions.
• Fault definitions.
• Service policies.
• WSDL Description of the interfaces.

The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and the Parlay
Consortium.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.127: "Service Requirement for the Open Services Access (OSA); Stage 1".
[3] 3GPP TS 23.198: "Open Service Access (OSA); Stage 2".
[4] 3GPP TS 22.101: "Service aspects; Service principles".
[5] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/.
[6] 3GPP TS 29.199-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common".
[7] Void.
[8] 3GPP TS 29.198-14: "Open Service Access (OSA) Application Programming Interface (API);
Part 14: Presence and Availability Management (PAM)".
[9] RFC 3856: "A Presence Event Package for the Session Initiation Protocol (SIP)".
http://www.ietf.org/rfc/rfc3856.txt
[10] Void.
[11] Void.
ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 8 ETSI TS 129 199-14 V7.4.1 (2008-01)
[12] 3GPP TS 23.141: "Presence service; Architecture and functional description; Stage 2".
[13] 3GPP TS 29.199-13: "Open Service Access (OSA); Parlay X Web Services; Part 13: Address list
management".
[11] IETF RFC 3265: "Session Initiation Protocol (SIP)-Specific Event Notification".
[15] Void.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in 3GPP TS 29.199-1 [6] and the following
apply:
applications: for Instant Messaging, Push to Talk, or call control and other purposes may become clients of the
presence Web Service
We assume that these applications belong to a watcher and authenticate to the services in the name of the watcher.
identity: represents a user in the real world
NOTE: See OSA/Parlay PAM identities [8], section 4.4.1.
presence attributes: contain information about a presentity
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 presentity's identity. A watcher can obtains attributes only after he has successfully subscribed to them.
Examples for attributes are activity, location type, communication means, etc.
presence information: consists of a set of attributes that characterize the presentity such as current activity,
environment, communication means and contact addresses
Only the system and the presentity have direct access to this information, which may be collected and aggregated from
several devices associated to the presentity.
subscription: before a watcher can access presence data, he has to subscribe to it
One 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/protocol to manage those policies is out of the scope of
the present document.
NOTE: This definition is not related to the term "subscription" in 3GPP TR 21.905 [1].
watcher and presentity: We use these names to denote the role of the client connected to the presence services
Like in OSA/Parlay PAM [8] the watcher and the presentity have to be associated to identities registered to the system,
i.e. users, groups of users or organizations.
ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 9 ETSI TS 129 199-14 V7.4.1 (2008-01)
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TS 29.199-1 [6] and the following apply:
ACL Access Control List
DMS Data Manipulation Server
GM Group Management
IETF Internet Engineering Task Force
IMS IP Multimedia Subsystem
ISC IP multimedia subsystem Service Control interface
MMS Multimedia Message Service
PAM Presence and Availability Management
RLS Resource List Server
SCF Service Capability Feature
SIMPLE SIP for Instant Messaging and Presence Leveraging Extensions
SIP Session Initiation Protocol
SMS Short Message Service
URI Uniform Resource Identifier
WS Web Service
WSDL Web Services Definition Language
XCAP XML Configuration Access Protocol
XML eXtensible Markup Language
XMPP eXtensible Messaging and Presence Protocol
XSD XML Schema Definition
4 Detailed service description
The presence service allows for presence information to be obtained about one or more users and to register presence
for the same. It is assumed that the typical client of these interfaces is either a supplier or a consumer of the presence
information. An Instant Messaging application is a canonical example of such a client of this interface.
Figure 4.1 shows the architecture of the presence Web Service and the underlying services. The OSA/Parlay PAM SCF
is the straightforward option and implements the presence server with extended identity, device capability, and presence
agent management. OSA/Parlay PAM allows aggregation of presence information from internet, mobile and enterprise
users, etc. using a presence transport network of SIP or XMPP servers. The Presence Web Service can however
communicate directly for example with IMS presence network elements (presence and resource list servers) using the
ISC (SIP/SIMPLE) protocol interface.
ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 10 ETSI TS 129 199-14 V7.4.1 (2008-01)

watcher
client
presentity
watcher
client
application
Parlay-X API
Group
Parlay-X Presence Web Service
Management WS
OSA/Parlay API
Policy
Network protocols
PAM Parlay SCF
rules
(e.g. SIP)
Network elements
(e.g. SIP)
Figure 4.1: The PAM Web Service Environment

Relationship to Similar or Supplanted Specifications:
The most important relations are to:
• Parlay-X Terminal Status and Terminal Location: Both services deal with information that could be considered
part of the user's presence information. Communication abilities can be derived from terminal status information,
and the user's placetype can be derived from his location.
• OSA/Parlay PAM: The OSA/Parlay Presence and Availability specification can be considered the big brother of
this specification. While ParlayX Presence stays behind OSA PAM in terms of flexibility and power - especially
concerning attributes and management interfaces - it also extends PAM by introducing end-to-end authorization.
This specification aims to be mappable to OSA PAM.
• SIP SIMPLE [9]: This specification aims to be mappable to the SIP/SIMPLE architecture.
• XMPP (Jabber): Many principles of this specification (see Bibliography) have been adopted, especially the end-
to-end authorization.
• IETF Rich Presence (see Bibliography). The set of attributes the present document specifies is closely aligned
with the IETF's Rich Presence ideas.
• Group Management [13]: Presence of groups is supported by this specification, however their creation and
manipulation has to be done using the GM PX Web Service. In the 3GPP presence context, contact lists and
group manipulation is done with the XCAP protocol (see Bibliography).
ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 11 ETSI TS 129 199-14 V7.4.1 (2008-01)
5 Namespaces
The PresenceConsumer interface uses the namespace:
http://www.csapi.org/wsdl/parlayx/presence/consumer/v3_2
The PresenceNotification interfaces use the namespace:
http://www.csapi.org/wsdl/parlayx/presence/notification/v3_2
The PresenceSupplier interfaces use the namespace:
http://www.csapi.org/wsdl/parlayx/presence/supplier/v3_2
The PresenceSupplierNotificationManager interfaces use the namespace:
http://www.csapi.org/wsdl/parlayx/presence_supplier/notification_manager/v3_0
The PresenceSupplierNotification interfaces use the namespace:
http://www.csapi.org/wsdl/parlayx/presence_supplier/notification/v3_0
The data types are defined in the namespace:
http://www.csapi.org/schema/parlayx/presence/v3_2
The 'xsd' namespace is used in the present document to refer to the XML Schema data types defined in
XML Schema [5]. The use of the name 'xsd' is not semantically significant.

6 Sequence diagrams
6.1 Interface flow overview
The sequence diagram shows the interactions in case both watcher application and presentity are Web Service clients.
Compared to the SIP interactions, the subscription notification is separated from the delivery of presence information
itself. Based on the subscription result, the watcher can select the polling or notification mode for presence events.
Changes in the authorization of presence attributes are propagated to the watchers via notifySubscription() message, the
blocking of a subscription by the presentity are propagated via an endSubscriptionNotification message.
The sequence diagram does not show the internal communication within the presence server. It is assumed that the
Presence Consumer and Supplier interfaces are implemented by the same instance. If an implementers of the API find
other solutions preferable, he has to take care of the internal communication himself.
ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 12 ETSI TS 129 199-14 V7.4.1 (2008-01)
Watcher Application : Presence Web Service : Presence Web Service :
Presentity Application
PresenceConsumerNotifications PresenceConsumer PresenceSupplier
:
subscribePresence
check subscription policies
after a while the
user logs on
notifySubscription
getOpenSubscriptions
if there is a policy for this get user answer
subscription request, no
interaction with the
presentity is necessary.
updateSubscriptionAuthorisation
notifySubscription
publish
the watcher can access
presence data by polling.
getUserPresence
determine presence
... or through notifications
user status changes (for
whatever reason)
startPresenceNotification
publish
statusChanged
endPresenceNotification
subscription timeout
subscriptionEnded
getMyWatchers
a subscription can either
time out; or the presentity
can cancel it
getSubscribedAttributes
blockSubscription
subscriptionEnded
Figure : Message interaction overview
ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 13 ETSI TS 129 199-14 V7.4.1 (2008-01)
7 XML Schema data type definition
Presence attributes are inspired by the IETF's Rich Presence ideas (see Bibliography).
7.1 PresenceAttributeType enumeration
The different types of attributes. For each entry in this enumeration there is a separate value type.
Enumeration Description
Activity The presentity's activity (available, busy, lunch, etc.)
PlaceType At what kind of place the presentity is (home, office, etc.)
Privacy The amount of privacy the user wants (public, quiet, etc.)
Sphere The user's current environment (work, home)
Communication The user's means of communication (phone, mail, etc.)
Mood The user"s mood (angry, confused, happy, etc.)
PlaceIs Describes the properties of the place the user is currently at.
TimeOffset Describes the number of minutes of offset from UTC that the user is currently at.
StatusIcon Depicts the current status of the user.
Other A name - value pair for arbitrary presence information

7.2 ActivityValue enumeration
This enumeration shows the user's current activity. If the activity is unknown, the attribute value will be
ActivityNone, meaning the attribute was not set. If the user is doing something not in this list, the value will be set
to ActivityOther.
Enumeration Description
ActivityNone Not set.
Appointment The user has an appointment.
Available The user is available for communication.
Busy The user is busy and is only available for urgent matters.
DoNotDisturb The user is very busy and does not wish to be disturbed.
OnThePhone The user is on the phone.
Steering The user is driving a car / train / airplane, etc.
Meeting The user is in a meeting.
Away No idea what the user is doing, but he is away.
Meal The user is eating.
Breakfast The user is having breakfast.
Lunch The user is having lunch.
Dinner The user is having dinner.
PermanentAbsence The user is away and will not return for an extended period.
Vacation The user is on vacation.
Holiday A scheduled national or local holiday.
Performance The user is in a theatre / concert.
InTransit The user is in the transit area of an (air)port.
Travel The user is travelling.
Sleeping The user is sleeping.
LookingForWork The user is looking for (paid) work.
Playing The user is occupying him- or herself in amusement, sport, or other recreation.
Presentation The user is giving a presentation, lecture, or participating in a formal round-table discussion.
Shopping The user is visiting stores in search of goods or services.
Spectator The user is observing an event, such as a sports event.
TV The user is watching television.
Working The user is engaged in, typically paid, labor, as part of a profession or job.
Worship The user is participating in religious rites.
ActivityOther The user is doing something not in this list.

ETSI
3GPP TS 29.199-14 version 7.4.1 Release 7 14 ETSI TS 129 199-14 V7.4.1 (2008-01)
7.3 PlaceTypeValue enumeration
This enumeration shows the type of the user's current location. If the place type is unknown, the attribute value will be
PlaceNone, meaning the attribute was not set. If the user in a place not in this list, the value will be set to
PlaceOther.
Enumeration Description
PlaceNone Not set.
Arena The user is at an enclosed area used for sports events.
Home The user is at home.
Office The user is in an office.
PublicTransport The user is on public transport.
Street Walking on the street.
Outdoors Generally outdoors.
PublicPlace The user is in a public place.
Hotel The user is in a hotel.
Theatre The user is in a theatre or concert.
Restaurant The user is in a restaurant, coffee shop or, other public dining establishment.
School The user is at school.
Industrial The user is in an industrial building.
Quiet The user is in a quiet area.
Noisy The user is in a noisy area.
Aircraft The user is on an aircraft.
Watercraft The user is on a vessel for travel on water such as a boat or ship.
Automobile The user is in a car.
Bus The user is in a bus.
BusStation The user is in a bus- station.
TrainStation The user is in a train-station.
ShoppingArea The user is in a shopping mall or shopping area.
Airport The user is in an airport.
Train The user is in a train.
Bank The user is in a bank.
Bar The user is in a bar.
Bicycle The user is on a bicycle.
Café The user is in a café; usually a small and informal establishment that serves various refreshments
(such as coffee); coffee shop.
Classroom The user is in an academic classroom or lecture hall.
Club The user is in a dance club, nightclub, or discotheque.
Construction The user is at a contstruction site.
ConventionCenter The user is in a convention center or exhibition hall.
Government The user is in a government building, such as those used by the legislative, executive, or judicial
branches of governments, including court houses, police stations, and military inst
...