Printer FriendlyEmail Article Link

UTS command required by PLTS

Answer

 

When you are testing A-GPS test with TASKIT/PLTS software, if you want automatic testing including User Plane testing, UTS command is needed to send the proper command to the handset to do proper operation.

Class CDMASys
 

Name
User Plane Requirement
When Used
Property
PRL
Mandatory
·         Querying mobile
·         Verifying mobile
 
PreferredServiceOption
Optional
·         Any Control Plane test where MS originates the voice call (Call Type = Mobile Originated)
 
Sleep
Mandatory
·         All tests
 
OTAMask
Mandatory
·         All MS-Based tests (Positioning Method = MS-Based)
 
State
Optional
·         User Interaction sub-test where Automation Command is CDMA State
Method
EnableCDMASysEvent
Mandatory
·         All MS-Based tests (Positioning Method = MS-Based)

 
Class Handset
 

Type
Name
User Plane Requirement
When Used
Event
LocationEvent
Mandatory
·         All MS-Based tests (Positioning Method = MS-Based)
Property
AvailableKeys
Optional
·         User Interaction sub-test where Automation Command is Key Sequence
·         All other tests where MS-Resident Application Initiation Method is Key Sequence
 
ManufacturerName
Optional
·         Querying mobile
 
ModelName
Optional
·         Querying mobile
 
HardwareVersion
Optional
·         Querying mobile
 
SoftwareVersion
Optional
·         Querying mobile
Method
Connect
Mandatory
·         All tests
 
Ping
Mandatory
·         All tests
 
GetESN
Optional
·         Querying mobile
·         Verifying mobile
 
GetMEID
Optional
·         Querying mobile
·         Verifying mobile
 
DepressKey
Optional
·         User Interaction sub-test where Automation Command is Key Sequence
·         All tests where MS-Resident Application Initiation Method is Key Sequence
 
ReleaseKey
Optional
·         User Interaction sub-test where Automation Command is Key Sequence
·         All other tests where MS-Resident Application Initiation Method is Key Sequence
 
OriginateCall
Optional
·         All Control Plane tests where mobile originates calls (Call Type = Mobile Originated)
 
EndCall
Optional
·         Emergency Call Test where call is released or dropped by mobile (Call Released By or Call Dropped By = Mobile)
 
AnswerCall
Optional
·         All Control Plane tests where Call Type is Mobile Terminated
 
Reset
Mandatory
·         Any tests where Reset Mobile is Between Tests or Between Calls.
 
EnableHandsetEvent
Mandatory
·         All MS-Based tests (Positioning Method = MS-Based)

 
Class GPS
 

Type
Name
User Plane Requirement
When Used
Event
GPSSearchEvent
Mandatory
·         Any MS-Based tests where Location Response Time Start = Start GPS Search or Location Response Time Stop = End GPS Search
Method
EnableGPSEvent
Mandatory
·         Any MS-Based tests where Location Response Time Start = Start GPS Search or Location Response Time Stop = End GPS Search
 
GPSControl
Mandatory
·         Any tests where MS-Resident Application Initiation Method = MS API Request
·         Any tests where Cold Start = Between Tests or Between Calls

Class PersistentMemory
Note that ALL the following UTS items are required for User Plane testing in Mobile IP service type. 
 

Type
Name
When Used
 
·         BeginNVTransaction
·         EndNVTransaction
·         NVItemNames
·         NVItemFieldName
·         NVItemFieldType
·         NVItemFieldMaximumStringLengh
·         NVItemFieldMinimumStringLength
·         NVItemFieldString
·         NVItemFieldMaximumValue
·         NVItemFieldMinimumValue
·         NVItemFieldValue
·         NVItemFieldMaximumDate
·         NVItemFieldMinimumDate
·         NVItemFieldDate
·         NVItemFieldLabel
·         NVItemFieldTime
·         NVItemFieldIPAddress
 
·         Querying current NAM
·         Any User Plane tests with mobile parameter IP Service Type = Mobile IP Only or Mobile IP Preferred and MN-NAI = Auto


Product : PLTS,PLTS