6.7 User Status

29.1983GPPOpen Service Architecture (OSA) Application Programming Interface (API) - Part 1Release 1999TS

The User Status (US) SCF provides the IpUserStatus interface. Most methods are asynchronous, in that they do not lock a thread into waiting whilst a transaction performs. In this way, the client machine can handle many more calls, than one that uses synchronous message calls. To handle responses and reports, the developer must implement IpAppUserStatus interface to provide the callback mechanism.

Figure 6-17: User Status class diagram.

6.7.1 User Status SCF interface

The user status interface represents the interface to the user status service capability feature.

<<Interface>>

IpUserStatus

statusReportReq(appStatus : in IpAppUserStatusRef, users : in TpAddressSet, assignmentId : out TpSessionIDRef) : TpResult

triggeredStatusReportingStartReq (appStatus : in IpAppUserStatusRef, users : in TpAddressSet, assignmentId : out TpSessionIDRef) : TpResult

triggeredStatusReportingStop (stopRequest : in TpMobilityStopAssignmentData) : TpResult

6.7.2 User Status application interface

The user-status application interface is implemented by the client application developer and is used to handle user status reports.

<<Interface>>

IpAppUserStatus

statusReportRes(assignmentId : in TpSessionID, status : in TpUserStatusSet) : TpResult

statusReportErr(assignmentId : in TpSessionID, cause : in TpMobilityError, diagnostic : in TpMobilityDiagnostic)

triggeredStatusReport(assignmentId : in TpSessionID, status : in TpUserStatus) : TpResult

triggeredStatusReportErr(assignmentId : in TpSessionID, cause : in TpMobilityError, diagnostic : in TpMobilityDiagnostic)