29.198-063GPPOpen Service Access (OSA) Application Programming Interface (API)Part 6: Mobility Service Capability Feature (SCF)Release 9TS

10.1 Mobility Properties

10.1.1 Emergency Application Subtypes

Emergency (see definition of ‘LCS Client Type’ in 3GPP TS 23.271) Application Subtypes;

This property contains a list of application subtypes that are permitted to use the service. The possible subtypes are (see definition of ‘LCS Client Internal ID’ in 3GPP TS 23.271):

– “Broadcast service”
– “O&M HPLMN service”
– “O&M VPLMN service”
– “Anonymous location”
– “Target MS subscribed service”

10.1.2 Value Added Application Subtypes

Value Added (see definition of ‘LCS Client Type’ in 3GPP TS 23.271) Application Subtypes.

This property contains a list of application subtypes that are permitted to use the service. The possible subtypes are (see definition of ‘LCS Client Internal ID’ in 3GPP TS 23.271):

– “Broadcast service”
– “O&M HPLMN service”
– “O&M VPLMN service”
– “Anonymous location”
– “Target MS subscribed service”

10.1.3 PLMN Operator Application Subtypes

PLMN Operator (see definition of ‘LCS Client Type’ in 3GPP TS 23.271.) Application Subtypes.

This property contains a list of application subtypes that are permitted to use the service. The possible subtypes are (see definition of ‘LCS Client Internal ID’ in 3GPP TS 23.271):

– “Broadcast service”
– “O&M HPLMN service”
– “O&M VPLMN service”
– “Anonymous location”
– “Target MS subscribed service”

10.1.4 Lawful Intercept Application Subtypes

Lawful Intercept (See definition of ‘LCS Client Type’ in 3GPP TS 23.271.) Application Subtypes.

This property contains a list of application subtypes that are permitted to use the service. The possible subtypes are (see definition of ‘LCS Client Internal ID’ in 3GPP TS 23.271):

– “Broadcast service”
– “O&M HPLMN service”
– “O&M VPLMN service”
– “Anonymous location”
– “Target MS subscribed service”

10.1.5 Altitude Obtainable

Indicates whether it is possible to obtain a user’s altitude.

10.1.6 Location Methods

List of supported location methods. Possible values (other values are permitted):

• “Time of Arrival”
• “Timing Advance”
• “GPS”
• “User Data Lookup”
• “Any Time Interrogation”

10.1.7 Priorities

List of supported priorities for location requests. Possible values (no other values are permitted):

• “Normal”
• “High”

10.1.8 Max Interactive Requests

The maximum number of parallel outstanding location or status requests allowed per application. It shall be possible to convert the value to a 32-bit integer.

10.1.9 Max Triggered Users

The maximum number of users allowed per application for which triggered location reporting can be requested. It shall be possible to convert the value to a 32-bit integer.

10.1.10 Max Periodic Users

The maximum number of users allowed per application for which periodic location reporting can be requested. It shall be possible to convert the value to a 32-bit integer.

10.1.11 Min Periodic Interval Duration

The minimal time in seconds allowed between two periodic reports. It shall be possible to convert the value to a 32-bit integer. Note however that the reportingInterval parameter, which is used in methods pertaining to periodic location reporting, is of common data type TpDuration, i.e. a signed 32-bit integer representing a time interval in milliseconds.

10.1.12 Initial Report

Indicates whether a triggered service should generate an initial triggered report immediately after a triggered start request.

• Triggered Status – If this property is set to “True”, the initial status of the end user is reported immediately after the triggeredStatusReportingStartReq.
• Triggered Location – If this property is set to “True”, the initial location of the end user is reported immediately after the triggeredLocationReportingStartReq, if the trigger criteria is met i.e. if the end user is within the location area and the Criterion is P_UL_ENTERING_AREA or the end user is outside the location area and the Criterion is P_UL_LEAVING_AREA.

10.1.13 Max Life Time

Specifies the maximum life time in milliseconds of a triggered or periodic reporting. It is of common data type TpDuration, i.e. a signed 32-bit integer representing a time interval in milliseconds. A value of zero means infinite life time.

• The periodic or triggered reporting will stop when a stop method associated with the triggering is received by the SCS or when the life time has expired.

10.2 User Location Service Properties

A specific User Location service shall set the following properties:

• General Properties applicable to all SCFs (in Framework)
• Permitted application types
• Permitted application subtypes
• Priorities (see definition of ‘LCSClientType’ in 3GPP TS 23.271.)
• Altitude obtainable
• Location methods
• Max interactive requests
• Max triggered users
• Max periodic users
• Min periodic interval duration
• Initial Report
• Max Life Time

EXAMPLE: The example below describes the capabilities of two fictive User Location services:

10.3 User Location Camel Service Properties

A specific User Location Camel service shall set the following properties:

• General Properties applicable to all SCFs (in Framework)
• Max interactive requests
• Max triggered users
• Max periodic users
• Min periodic interval duration
• Initial Report
• Max Life Time

10.4 User Location Emergency Service Properties

A specific User Location Emergency service shall set the following properties:

• General Properties applicable to all SCFs (in Framework).
• Permitted application types.
• Permitted application subtypes.
• Altitude obtainable.
• Location methods.
• Priorities.

NOTE: See definition of ‘LCS Client Type’ in TS 123 271.

• Max interactive requests.

10.5 User Status Service Properties

A specific User Location service shall set the following properties:

• General Properties applicable to all SCFs (in Framework)
• Max interactive requests
• Max triggered users
• Initial Report
• Max Life Time