2. section (Continued) 6 Call Layer 3 Processing

2.6.4.3.2 Waiting for Mobile Station Answer Substate

Upon entering the Waiting for Mobile Station Answer Substate, the mobile station shall set the substate timer for T_53m seconds.

While in the Waiting for Mobile Station Answer Substate, the mobile station shall perform the following:

• If the substate timer expires, the mobile station shall disable its transmitter and enter the System Determination Substate of the Mobile Station Initialization State with a system lost indication (see 2.6.1.1).

• The mobile station may send a Pilot Strength Measurement Mini Message to report pilot strength order change information, periodic pilot strength information, or threshold based pilot strength information, as specified in the Mobile Assisted Burst Operation Parameters Request Message.

• The mobile station shall perform Forward Traffic Channel supervision as specified in 2.6.4.1.8. If a loss of the Forward Traffic Channel is declared, the mobile station shall enter the System Determination Substate of the Mobile Station Initialization State with a system lost indication (see 2.6.1.1). In addition, if Resource Control is supported, Layer 3 shall send SIG-Release.Indication({CH_LIST}, NULL, NULL, NULL) to Resource Control where CH_LIST includes “FCH”, “DCCH”, or both to indicate the channel(s) that were lost.

• The mobile station shall adjust its transmit power as specified in 2.1.2.3 of TIA/EIA/IS-2000-2.

• The mobile station shall perform Forward Traffic Channel power control as specified in 2.6.4.1.1.

• The mobile station shall perform handoff processing as specified in 2.6.6.

• The mobile station shall process Forward and Reverse Traffic Channel frames in accordance with requirements for the active service subfunction (see 2.6.4.1.2.2).

• The mobile station shall perform registration timer maintenance as specified in 2.6.5.5.4.2.

• If the mobile station is directed by the user to answer the call, the mobile station shall send a Connect Order in assured mode. The mobile station shall enter the Conversation Substate.

• If the mobile station is directed by the user to transmit a message, the mobile station shall send a Data Burst Message.

• If the mobile station is directed by the user to request a new service configuration, the mobile station shall initiate service negotiation or service option negotiation in accordance with the requirements for the active service subfunction (see 2.6.4.1.2.2).

• If the mobile station is directed by the user to forward the incoming call, the mobile station shall send a Flash With Information Message in assured mode with a Feature Indicator information record (see 2.7.4.1) with the FEATURE field set to ‘00000000’.

• If the mobile station is directed by user to forward the incoming call to a number stored in the mobile station, the mobile station shall send a Flash With Information Message in assured mode with a Feature Indicator information record (see 2.7.4.1) with the FEATURE field set to ‘00010000’ and a Called Party Number information record set to the forwarding number.

• If the mobile station is directed by the user to forward the incoming call to network-based voice mail, the mobile station shall send a Flash With Information Message in assured mode with a Feature Indicator information record (see 2.7.4.1) with the FEATURE field set to ‘00010001’.

• If the mobile station is directed by the user to activate answer holding, the mobile station shall send a Flash With Information Message in assured mode requiring confirmation of delivery with a Feature Indicator information record (see 2.7.4.1) with the FEATURE field set to ‘00010010’. After receiving confirmation of delivery of the Flash With Information Message, the mobile station shall send a Connect Order in assured mode. The mobile station shall enter the Conversation Substate.

• The mobile station may send a Service Option Control Message or Service Option Control Order to invoke a service option specific function in accordance with the requirements for the active service subfunction (see 2.6.4.1.2.2).

• If the mobile station is directed by the user to request a private long code transition and has the long code mask (see 2.3.12.3), the mobile station shall send a Long Code Transition Request Order (ORDQ = ‘00000001’) in assured mode.

• If the mobile station is directed by the user to request a public long code transition, the mobile station shall send a Long Code Transition Request Order (ORDQ = ‘00000000’) in assured mode.

• If the mobile station is directed by the user to operate in analog mode, allowing operation in either wide or narrow analog mode, the mobile station shall send the Request Analog Service Order in assured mode.

• If the mobile station is directed by the user to operate in wide analog mode, the mobile station shall send the Request Wide Analog Service Order in assured mode.

• If the mobile station is directed by the user to operate in narrow analog mode, the mobile station shall send the Request Narrow Analog Service Order in assured mode.

• If the mobile station is directed by the user to power down, the mobile station shall enter the Release Substate with a power-down indication (see 2.6.4.5).

• If Layer 3 receives a L2-Condition.Notification primitive from Layer 2 indicating an acknowledgment failure, the mobile station shall disable its transmitter and enter the System Determination Substate of the Mobile Station Initialization State with a system lost indication (see 2.6.1.1).

1. 
   Alert With Information Message: The mobile station shall reset the substate timer for T_53m seconds. If the Alert With Information Message does not contain a Signal information record, the mobile station should use standard alert as defined in 3.7.5.5.
   
2. 
   Analog Handoff Direction Message: If the analog mode directed by the base station is supported by the mobile station, the mobile station shall process the message as specified in 2.6.6.2.9 and enter the Waiting For Answer Task (see 2.6.4.3.2 for handoff to a wide analog channel and 2.6.5.3.2A of TIA/EIA/IS-91-A for handoff to an 800 MHz narrow analog channel). If the mobile station is directed to an unsupported operation mode or band class, the mobile station shall respond with a Mobile Station Reject Order with ORDQ equal to ‘00000110’ (message requires a capability that is not supported by the mobile station).
   
3. 
   Audit Order
   
4. 
   Authentication Challenge Message: The mobile station shall process the message and respond as specified in 2.3.12.1.4 within T_32m seconds, regardless of the value of AUTH_s.
   
5. 
   Base Station Challenge Confirmation Order: The mobile station shall process the message and respond with an SSD Update Confirmation Order or SSD Update Rejection Order as specified in 2.3.12.1.5 within T_32m seconds.
   
6. 
   Candidate Frequency Search Control Message: The mobile station shall process the message as specified in 2.6.6.2.5.1.
   
7. 
   Candidate Frequency Search Request Message: The mobile station shall process the message as specified in 2.6.6.2.5.1.
   
8. 
   Data Burst Message
   
9. 
   Extended Handoff Direction Message: If the band class is not specified in the message or the specified band is supported by the mobile station, the mobile station shall process the message as specified in 2.6.6.2.5.1.
   
10. 
    Extended Neighbor List Update Message: The mobile station shall process the message as specified in 2.6.6.2.6.3.
    
11. 
    Extended Release Message: The mobile station shall process the message as specified in 2.6.4.1.9.
    
12. 
    Extended Release Mini Message: The mobile station shall process the message as specified in 2.6.4.1.11.
    
13. 
    Extended Supplemental Channel Assignment Message: The mobile station shall process the message as specified in 2.6.6.2.5.1.
    
14. 
    Forward Supplemental Channel Assignment Mini Message: The mobile station shall process the message as specified in 2.6.6.2.5.1.
    
15. 
    General Handoff Direction Message: If the band class is not specified in the message or the specified band is supported by the mobile station, the mobile station shall process the message as specified in 2.6.6.2.5.1. If the message contains a service configuration record, the mobile station shall process the message in accordance with the requirements for the active service subfunction (see 2.6.4.1.2.2).
    
16. 
    In-Traffic System Parameters Message: The mobile station shall process the message as specified in 2.6.4.1.4.
    
17. 
    Local Control Order
    
18. 
    Lock Until Power-Cycled Order: The mobile station shall disable its transmitter and record the reason for the Lock Until Power-Cycled Order in the mobile station’s semi-permanent memory (LCKRSN_P_s-p equals the least-significant four bits of ORDQ_r). The mobile station should notify the user of the locked condition. The mobile station shall enter the System Determination Substate of the Mobile Station Initialization State with a lock indication (see 2.6.1.1), and shall not enter the System Access State again until after the next mobile station power-up or until it has received an Unlock Order. This requirement shall take precedence over any other mobile station requirement specifying entry to the System Access State.
    
19. 
    Long Code Transition Request Order: The mobile station shall process the message as specified in 2.6.4.1.6.
    
20. 
    Maintenance Order: The mobile station shall reset the substate timer for T_53m seconds.
    
21. 
    Maintenance Required Order: The mobile station shall record the reason for the Maintenance Required Order in the mobile station’s semi-permanent memory (MAINTRSN_s p equals the least-significant four bits of ORDQ_r). The mobile station shall remain in the unlocked condition. The mobile station should notify the user of the maintenance required condition.
    
22. 
    Message Encryption Mode Order: The mobile station shall process the message as specified in 2.3.12.2.
    
23. 
    Mobile Assisted Burst Operation Parameters Message: The mobile station shall process the message as specified in 2.6.6.2.5.1.
    
24. 
    Mobile Station Registered Message: The mobile station shall process the message as specified in 2.6.5.5.4.3.
    
25. 
    Neighbor List Update Message: The mobile station shall process the message as specified in 2.6.6.2.6.3.
    
26. 
    Outer Loop Report Request Order: The mobile station shall send the Outer Loop Report Message in assured mode to the base station.
    
27. 
    Parameter Update Order: The mobile station shall increment COUNT_s-p (see 2.3.12.1.3). The mobile station shall send a Parameter Update Confirmation Order within T_56m seconds. The mobile station shall set the ORDQ field of the Parameter Update Confirmation Order to the same value as the ORDQ field of the Parameter Update Order.
    
28. 
    Periodic Pilot Measurement Request Order: The mobile station shall process the order as specified in 2.6.6.2.5.1.
    
29. 
    Pilot Measurement Request Order: The mobile station shall process the order as specified in 2.6.6.2.5.1.
    
30. 
    Power Control Message: The mobile station shall process the message as specified in 2.6.4.1.1.3.
    
31. 
    Power Control Parameters Message: The mobile station shall process the message as specified in 2.6.4.1.1.2.
    
32. 
    Power Up Function Message: The mobile station shall process the message as specified in 2.6.4.1.7.1.
    
33. 
    Power Up Function Completion Message: The mobile station shall process the message as specified in 2.6.4.1.7.3.
    
34. 
    Release Order: The mobile station shall enter the Release Substate with a base station release indication (see 2.6.4.5).
    
35. 
    Resource Allocation Message: The mobile station shall process the message as specified in 2.6.4.1.10.
    
36. 
    Resource Allocation Mini Message: The mobile station shall process the message as specified in 2.6.4.1.10.
    
37. 
    Retrieve Parameters Message: The mobile station shall send, within T_56m seconds, a Parameters Response Message.
    
38. 
    Reverse Supplemental Channel Assignment Mini Message: The mobile station shall process the message as specified in 2.6.6.2.5.1.
    
39. 
    Service Connect Message: The mobile station shall process the message in accordance with the requirements for the active service subfunction (see 2.6.4.1.2.2).
    
40. 
    Service Option Control Message: The mobile station shall process the message in accordance with the requirements for the active service subfunction (see 2.6.4.1.2.2).
    
41. 
    Service Option Control Order: The mobile station shall process the message in accordance with the requirements for the active service subfunction (see 2.6.4.1.2.2).
    
42. 
    Service Option Request Order: The mobile station shall process the message in accordance with the requirements for the active service subfunction (see 2.6.4.1.2.2).
    
43. 
    Service Option Response Order: The mobile station shall process the message in accordance with the requirements for the active service subfunction (see 2.6.4.1.2.2).
    
44. 
    Service Request Message: The mobile station shall process the message in accordance with the requirements for the active service subfunction (see 2.6.4.1.2.2).
    
45. 
    Service Response Message: The mobile station shall process the message in accordance with the requirements for the active service subfunction (see 2.6.4.1.2.2).
    
46. 
    Set Parameters Message: If the mobile station can set all of the parameters specified by the PARAMETER_ID fields in the message, the mobile station shall set them; otherwise, the mobile station shall send, within T_56m seconds, a Mobile Station Reject Order.
    
47. 
    SSD Update Message: The mobile station shall process the message and respond with a Base Station Challenge Order as specified in 2.3.12.1.5 within T_32m seconds.
    
48. 
    Status Request Message: The mobile station shall send, within T_56m seconds, a Status Response Message. If the message does not specify any qualification information (QUAL_INFO_TYPE_r is equal to ‘00000000’), the mobile station shall include the requested information records in the Status Response Message. If the message specifies a band class (QUAL_INFO_TYPE_r is equal to ‘00000001’), the mobile station shall only include the requested information records for the specified band class (BAND_CLASS_r) in the Status Response Message. If the message specifies a band class and an operating mode (QUAL_INFO_TYPE_r is equal to ‘00000010’), the mobile station shall only include the requested information records for the specified band class (BAND_CLASS_r) and operating mode (OP_MODE_r) in the Status Response Message. If the message specifies a band class or a band class and an operating mode which is not supported by the mobile station, the mobile station shall send a Mobile Station Reject Order with ORDQ set to ‘00000110’ (message requires a capability that is not supported by the mobile station). If the response to this message exceeds the allowable length, the mobile station shall send a Mobile Station Reject Order with ORDQ set to ‘00001000’ (response message would exceed the allowable length). If the message specifies an information record which is not supported by the mobile station for the specified band class and operating mode, the mobile station shall send a Mobile Station Reject Order with ORDQ set to ‘00001001’ (information record is not supported for the specified band class and operating mode).
    
49. 
    Status Request Order: If CDMABAND_s is equal to ‘00000’, the mobile station shall send, within T_56m seconds, a Status Message. The mobile station shall respond with information corresponding to the current band class and operating mode.
    
50. 
    Supplemental Channel Assignment Message: The mobile station shall process the message as specified in 2.6.6.2.5.1.
    
51. 
    TMSI Assignment Message: The mobile station shall store the TMSI zone and code as follows:
    

• 
  The mobile station shall store the length of the TMSI zone field by setting ASSIGNING_TMSI_ZONE_LEN_s-p to TMSI_ZONE_LEN_r,
  
• 
  The mobile station shall store the assigning TMSI zone number by setting the ASSIGNING_TMSI_ZONE_LEN_s-p least significant octets of ASSIGNING_TMSI_ZONE_s-p to TMSI_ZONE_r, and
  
• 
  The mobile station shall store the TMSI code by setting TMSI_CODE_s-p to TMSI_CODE_r.
  

52. 
    Universal Handoff Direction Message: The mobile station shall process the message as specified in 2.6.6.2.5.1. If the message contains a service configuration record, the mobile station shall process the message in accordance with the requirements for the active service subfunction (see 2.6.4.1.2.2)
    

• If the bits of TMSI_CODE_s-p are not all equal to ‘1’ and if System Time (in 80 ms units) exceeds TMSI_EXP_TIME_s-p  2¹², the mobile station shall set all the bits of TMSI_CODE_s-p to ‘1’ within T_66m seconds.

• If the full-TMSI timer expires or has expired, the mobile station shall set all the bits of TMSI_CODE_s p to ‘1’. The mobile station shall update the registration variables as described in 2.6.5.5.2.5.

• If Resource Control is supported, Layer 3 may receive a primitive from Resource Control. Layer 3 shall process the primitives received from Resource Control as specified in 2.6.4.1.12.