100.4 CDMA Events
|
Event Name |
Symbol |
Description/Extra Information |
Refined |
|
Answer End |
|
An Answer activity completed. Extra information: Service status. Serving Radio Technology |
✔ |
|
Answer Start |
|
An Answer activity started. Extra information: Serving Radio Technology |
✔ |
|
Answer Error |
|
An Answer activity failed. Extra information: Error Cause Serving Radio Technology |
✔ |
|
Call events (Blocked Call; Call*; Dropped Call): Some of these events are also generated for VoIP. Most of these events have pieces of extra information namely "Call Domain", which is either "Circuit Switched" or "Packet Switched", and "Serving Radio Technology" which holds the radio technology responsible for generating the event. These are not repeated for the individual events below. |
|||
|
|
Triggered by one of the following: Unexpected change to idle or init state before "Call Established" CM Call Event (MR) message with "Block or Drop" event received Generalized Searcher General Status (MR) message received with Searcher State = " CM State Response (MR) message with CM System Mode "No Service" event received. |
✔ |
|
|
|
MO call: Origination (ACH) message sent with a voice Service Option. MT call: Page Response (ACH) message received with a voice Service Option. Extra information: Initial RRC State |
✔ |
|
|
Call Attempt Retry |
|
A call attempt (see "Call Attempt") was repeated. Extra information: Initial RRC State |
✔ |
|
|
Triggered by Order (RTCH) or Order (FTCH) message with order code " |
✔ |
|
|
|
MO call: Triggered by Service Connect Completion (RTCH) message, and thus generated immediately after "Call Setup". MT call: Order (RTCH) message with order code " |
✔ |
|
|
Call Failure MO |
|
A mobile-originated call was either blocked or dropped. |
|
|
Call Failure MT |
|
A mobile-terminated call was either blocked or dropped. |
|
|
|
Triggered by Protocol Report containing dialed number. |
|
|
|
|
Triggered by Service Connect Completion (RTCH) message. Extra information: Call direction (MO/MT) Call setup time (measured from "Call Attempt", i.e. the first call attempt) User setup time (measured from "Call Initiation", thus more accurately reflecting the user-perceived setup time; obtained only for MO calls in scripts) |
✔ |
|
|
CSFB events: Some of these events have a piece of extra information "Call Domain", which however always takes the value "Circuit Switched". |
|||
|
CSFB Blocked Call |
|
A CS fallback call was blocked. This can happen in several ways: The Extended Service Request timed out without any response from network, or the network responded with Service Reject. In this case the CS fallback procedure never reaches the RAT change stage. RAT change to EV-DO or 1x failed, as indicated by the event "EUTRAN RRC Connection Release Redirected Failure". After successful RAT change to EV-DO or 1x, the CS call setup failed (CS "Blocked Call" event generated). Extra information: Serving Radio Technology |
✔ |
|
|
A CS fallback call attempt was made. Triggered by the Layer 3 message NAS Extended Service Request. Extra information: Serving Radio Technology Initial RRC State |
✔ |
|
|
CSFB Call Established |
|
Same triggers as for "CSFB Call Setup", and generated immediately after that event. |
✔ |
|
|
Triggered by one of the following: Fast Forward Power Control (MR) Fast Forward Power Control Statistics (MR) Reverse Power Control Statistics (MR) message with Service Option (1), (3), (17), (38) or (68), each of which specifies a type of voice service. Status Snapshot Response (MR) with CDMA Mode = " Extra information: Call direction (MO/MT) Call setup time (measured from "CSFB Call Attempt", i.e. the first call attempt) User setup time (measured from "Call Initiation", thus more accurately reflecting the user-perceived setup time. Obtained only for MO calls in scripts. If no "Call Initiation" event was generated, the user setup time cannot be computed.) Serving Radio Technology |
✔ |
|
|
Dedicated Mode |
|
The device is in traffic state. |
|
|
Dial End |
|
A Dial activity completed. Extra information: Service status. |
✔ |
|
Dial Start |
|
A Dial activity started. Extra information: Phone number dialed. |
✔ |
|
|
Triggered by one of the following: Unexpected change to idle or init state after "Call Established" CM Call Event (MR) message with "Block or Drop" event received Generalized Searcher General Status (MR) message received with Searcher State = " CM State Response (MR) message with CM System Mode "No Service" event received. |
✔ |
|
|
EV-DO 1x Tune-away |
|
The device suspended the EV-DO service to look for 1x paging. Triggered by EV-DO Tuneaway Information Report. |
|
|
EV-DO Access Failure |
|
An EV-DO access attempt failed. Triggered by EV-DO Access Attempt Report. |
|
|
EV-DO Access Success |
|
An EV-DO access attempt completed successfully. Triggered by EV-DO Access Attempt Report. Extra information: Sector sending ACAck message. |
|
|
EV-DO Connection Failure |
|
An EV-DO connection attempt failed. Triggered by EV-DO Connection Attempt Report. |
|
|
EV-DO Connection Success |
|
An EV-DO connection attempt completed successfully. Triggered by EV-DO Connection Attempt Report. |
|
|
EV-DO Dynamic Rate |
|
The device switched back from fixed rate to dynamic rate during an EV-DO session. Triggered by occurrence of fixed rate end time (see EV-DO Fixed Rate). |
|
|
EV-DO Fixed Rate |
|
The device entered fixed rate mode for a period of time during an EV-DO session. Triggered by receipt of Fixed Mode Enable Message (containing a given end time). |
|
|
|
The EV-DO active set was reduced to a single pilot. Extra information: EV-DO Rev. A: PN offset of each active pilot. EV-DO Rev. B: RF channel(s) and PN offset of each active pilot (to one pilot PN may correspond multiple RF channels: |
|
|
|
EV-DO Handoff 2 Actives |
|
Handoff in EV-DO traffic mode, two pilots in active set. Extra information: See "EV-DO Handoff 1 Active". |
|
|
EV-DO Handoff 3 Actives |
|
Handoff in EV-DO traffic mode, three pilots in active set. Extra information: See "EV-DO Handoff 1 Active". |
|
|
EV-DO Handoff 4 Actives |
|
Handoff in EV-DO traffic mode, four pilots in active set. Extra information: See "EV-DO Handoff 1 Active". |
|
|
EV-DO Handoff 5 Actives |
|
Handoff in EV-DO traffic mode, five pilots in active set. Extra information: See "EV-DO Handoff 1 Active". |
|
|
EV-DO Handoff 6 Actives |
|
Handoff in EV-DO traffic mode, six pilots in active set. Extra information: See "EV-DO Handoff 1 Active". |
|
|
EV-DO Island |
|
There is only a single active EV-DO pilot and no candidates. Triggered by EV-DO Pilot Sets Ver2 Report. |
|
|
EV-DO Session Failure |
|
An EV-DO session attempt failed. Triggered by EV-DO Session Attempt Ver2 Report. |
|
|
EV-DO Session Success |
|
An EV-DO session attempt completed successfully. Triggered by EV-DO Session Attempt Ver2 Report. |
|
|
|
Handoff in traffic state to another frequency, a different band, a different pilot set, or another frame offset, or a combination of these. Triggered by Active Set Change. Extra information: If band changed: RF mode (EV-DO or 1x); new band; new RF channel; new top pilot PN. If only channel changed: RF mode; new RF channel. |
✔ |
|
|
|
Idle handoff 1x to 1x or EV-DO to EV-DO. Triggered by Active Set Change. Extra information: If band changed: RF mode (EV-DO or 1x); new band; new RF channel; new top pilot PN. If only channel changed: RF mode; new RF channel. |
|
|
|
|
System change from 1x or EV-DO to Analog in idle mode. Triggered by System Determination Last Main Action Report. |
|
|
|
|
System change from Analog or EV-DO to 1x in idle mode. Triggered by System Determination Last Main Action Report. Extra information: New RF channel. |
|
|
|
|
System change from 1x to EV-DO in idle mode. Triggered by System Determination Last Main Action Report. Extra information: New RF channel. |
|
|
|
Idle Mode |
|
The device is in init state or entered idle mode. |
|
|
|
Generated in the course of narrowband interference scanning: see UM section "Narrowband Interference Scanning". Triggered when an in-band RF channel has a strength exceeding the average in-band RSSI by an amount at least equal to Interference Offset. The latter margin is set in the General window: see UM section "Setup of Narrowband Interference Scan". The event is generated only once for a given interferer in the course of a scan. Furthermore, if interference is detected on several contiguous RF channels, only one event is reported for all of these channels. |
|
|
|
No Service Mode |
|
The mobile is searching for serving network, or is in sleep mode. |
✔ |
|
Packet Mode |
|
The device entered data traffic mode. |
|
|
Soft Handoff 2-Way |
|
Soft handoff in 1x traffic mode, two pilots in active set. |
|
|
Soft Handoff 3-Way |
|
Soft handoff in 1x traffic mode, three pilots in active set. |
|
|
Soft Handoff 4-Way |
|
Soft handoff in 1x traffic mode, four pilots in active set. |
|
|
Soft Handoff 5-Way |
|
Soft handoff in 1x traffic mode, five pilots in active set. |
|
|
Soft Handoff 6-Way |
|
Soft handoff in 1x traffic mode, six pilots in active set. |
|
|
Soft Handoff Complete |
|
Active set in 1x reduced to a single pilot. |
✔ |
|
|
System change from 1x to Analog during traffic. Triggered by System Determination Last Main Action Report. |
|
|
|
|
System change from Analog or EV-DO to 1x during traffic. Triggered by System Determination Last Main Action Report. Extra information: New RF channel. |
|
|
|
|
System change from 1x to EV-DO during traffic. Triggered by System Determination Last Main Action Report. Extra information: New RF channel. |
|
|
