2.1.

1 MO Call
This section describes the procedure of a mobile originated (MO) call, as shown in Figure 2-1. Figure 2-1 MO call procedure

The procedure of a MO call is described as follows: Step 1 The MS sends an Origination message to the BSS through the access channel to request service. Step 2 The BSS acknowledges the receipt of the Origination message with a Base Station Acknowledgment Order message. Step 3 The BSS creates A CM Service Request message, package it and sends it to the MSC. For a circuit switched call, the BSS can request the MSC to allocate a terrestrial circuit. Step 4 The MSC sends an Assignment Request message to the BSS to request the assignment of radio resources. If the BSS recommends a terrestrial circuit in the CM Service Request message and the MSC can support that circuit, the MSC specifies the same circuit in the Assignment Request message. Otherwise, the MSC may assign a different terrestrial circuit.

Step 5 If a traffic channel is available for the call and the MS is not on a traffic channel, the BSS sends a Channel Assignment message or Extended Channel Assignment Message over the paging channel to initiate the setup of a radio traffic channel. Step 6 The MS starts sending a TCH Preamble message through the designated reverse traffic channel. Step 7 Once the BSS acquires the reverse traffic channel, it sends a BS Ack Order message to the MS through the forward traffic channel, requesting the response of the MS. Step 8 The MS acknowledges the receipt of the BS Ack Order message by transmitting an MS Ack Order message through the reverse traffic channel. Step 9 The BSS then sends a Service Connect message/Service Option Response Order message to the MS, specifying the service configuration for the call. Step 10 Upon receiving the Service Connect message or Service Option Response Order message, the MS starts processing traffic in accordance with the specified service configuration, and responds with a Service Connect Completion message. Step 11 After the radio traffic channel and terrestrial circuit are set up and fully interconnected, the BSS sends an Assignment Complete message to the MSC and considers the call in conversation state. Step 12 When the call progress tone is applied to the traffic channel frames, the ringback tone is available on the audio circuit path towards the MS. ----End

2.1.2 MT Call
This section describes the procedure of a mobile terminated (MT) call, as shown in Figure 2-2.

Figure 2-2 MT call procedure

The procedure of a MT call is described as follows: Step 1 The MSC determines that an incoming call terminates to a mobile station within its service area, and sends a Paging Request to the BSS to initiate a MT call setup scenario. Step 2 The BSS issues a General Page message containing the MS address over the paging channel. Step 3 The MS acknowledges the page by transmitting a Page Response message over the access channel. Step 4 The BSS creates a Paging Response, package it and sends it the message to the MSC. The BSS may request the MSC to allocate a preferred terrestrial circuit. Step 5 The BSS sends a Base Station Ack Order message to the MS to acknowledge the receipt of the Page Response message from the MS.

Step 6 The MSC sends an Assignment Request message to the BSS to request assignment of radio resources. This message also includes circuit if one is to be used between the MSC and the BSS. If the BSS requests a preferred terrestrial circuit in the Paging Response message and the MSC can support that circuit, the MSC shall use the same circuit in the Assignment Request message. Otherwise, the MSC may assign a different circuit. Step 7 The BSS sends a Channel Assignment message or Extended Channel Assignment message over the control channel of the radio interface (with the MS address) to initiate the setup of a radio traffic channel, if the MS is not already on a traffic channel. Step 8 The MS starts sending a TCH Preamble message over the designated reverse traffic channel. Step 9 Once the BSS acquires the reverse traffic channel, it sends a BS Ack Order message to the MS through the forward traffic channel. Step 10 The MS sends an MS Ack Order message to acknowledge the receipt of the BSS order. Step 11 The BSS then sends a Service Connect message/Service Option Response Order message to the MS to specify the service configuration for the call. The MS starts processing traffic in accordance with the specified service configuration. Step 12 Upon receipt of the Service Connect message, the MS responds with a Service Connect Completion message. Step 13 After the radio traffic channel and terrestrial circuit are set up, the BSS sends an Assignment Complete message to the MSC. Step 14 The BSS sends an Alert with Info message to instruct the MS to ring. Step 15 The MS acknowledges the receipt of the Alert with Info message by sending an MS Ack Order message. Step 16 When the call is answered at the MS, a Connect Order message containing required acknowledgment is sent to the BSS. Step 17 The BSS acknowledges the receipt of the Connect Order message by sending a BS Ack Order message through the forward traffic channel. Step 18 The BSS sends a Connect message to the MSC, indicating that the call has been answered at the MS. In such case, the call is stable and in the conversation state. ----End

2.1.3 Call Release Initiated by the MS

After initiating the network access, an MS can initiate the release procedure as required by the service (such as when the subscriber hooks on), as shown in Figure 2-3.

Figure 2-3 Call clear initiated by the MS

The procedure of a call release initiated by the MS is described as follows: Step 1 The MS initiates call release by sending a Release Order message through the reverse traffic channel. Step 2 The BSS then sends a Clear Request message to the MSC to initiate a call release transaction. Step 3 The MSC sends a Clear Command message to instruct the BSS to release the corresponding dedicated resource (such as a terrestrial circuit). Step 4 The BSS sends a Release Order message to the MS and releases the radio resource. Step 5 In response to the Clear Command message the BSS releases the terrestrial circuit. The BSS then responds the MS with a Clear Complete message. Upon the receipt of the Clear Complete message, the MSC releases the underlying transport connection (SCCP connection). ----End

2.1.4 Call Release Initiated by the BSS

A BSS can send a clear request to the MSC to trigger the call release procedure when:

The MS is not active. The radio connection between the MS and the BSS fails. Calls fail owing to the BSS equipment failure or other reasons.

Figure 2-4 shows the procedure of a call release initiated by the BSS.

Figure 2-4 Call clear initiated by BSS

The procedure of a call release initiated by the BSS is described as follows: Step 1 In the case of radio channel failure between the MS and the BSS, or if the MS is not active, the BSS sends a Clear Request message to the MSC. Step 2 The MSC sends a Clear Command message to instruct the BSS to release the associated dedicated resource (such as a terrestrial circuit). Step 3 The BSS then sends back a Clear Complete message. The MSC releases the underlying transport connection. ----End

2.1.5 Call Release Initiated by the MSC

Figure 2-5 shows the procedure of a call release initiated by the MSC. Figure 2-5 Call release initiated by the MSC

The procedure of a call release initiated by the MSC is described as follows: Step 1 The MSC sends a Clear Command message, instructing the BSS to release the corresponding dedicated resources. The MSC also initiates the Um interface call release procedure. Step 2 The BSS sends a Release Order message over the forward channel to initiate the call release operation. Step 3 After receiving the Release Order message, the MS sends a Release Order message over the reverse channel as the response.

Step 4 The BSS sends a Clear Complete message to the MSC, which releases the lower layer transport connection (SCCP connection) after receiving the message. ----End

2.2 Registration Procedure

In the CDMA2000 system, MS registration realizes the following functions:

The location and status information of the MS are reported so that the BTS can efficiently page the MS when setting up a MO call. The slotted mode MS supporting CDMA2000 can provides slot cycle index so that the BSC knows which slot is monitored by the MS. The MS type and protocol version is reported to the BSS so that the BSS knows the capability of the MS to support channels.

The registration types of an MS are as follows:

Power-on registration Power-off registration Periodic registration Distance-based registration Zone-based registration Parameter update registration Implicit registration

Figure 2-6 shows an MS registration procedure. Figure 2-6 MS registration procedure

The MS registration procedure is described as follows: Step 1 The MS initiates a registration by sending a Registration message to the BSS. Step 2 On receipt of the Registration message, the BSS creates a Location Updating Request message, places it in a Complete Layer 3 Information message, and sends it to the MSC. Step 3 The MSC sends a Location Updating Accept message to the BSS to indicate that the Location Updating Request has been processed.

Step 4 The BSS transmits a Registration Accepted Order message to the MS to indicate a successful location registration. ----End

2.3 Handoff Procedures

Handoff is the process of air interface link transfer between the MS and the BTS. That is, the current BTS and air interface channel are transferred to another BTS and air interface channel or different air interface channel of the current BTS. There are four types of handoff according to the methods to realize handoff:

Soft handoff: A handoff in which the MS starts communications with a new BTS without interrupting communications with the old BTS. Softer handoff: A handoff that occurs between different sectors in the same BTS without interrupting communication link. Hard handoff: A handoff in which the MS disconnects with the old BTS (carrier) and then start communication with a new BTS (carrier). During hard handoff, the communication link is disconnected temporarily. Handoff in system access state: A handoff that occurs during the process that the MS enters the traffic channel from the access state. This type of handoff is to guide the MS to use the access channel and paging channel with optimal pilot strength.

2.3.1 Intra-BSC Soft Handoff

Figure 2-7 shows the intra-BSC soft handoff procedure. Figure 2-7 Intra-BSC soft handoff procedure

The intra-BSC soft handoff procedure is described as follows:

Step 1 The MS sends a Pilot Strength Measurement Message to the BSS, reporting that the pilot strength in the target cell exceeds the threshold. Step 2 If the target cell is in the area of this BSC, the BSC decides to initiate an intra-BSC soft handoff. The BSC assigns resources, connects the MS, and sends a Null Forward Traffic Channel Frames message to the MS in the target cell. Step 3 The BSS sends to the MS an Extended Handoff Direction message to add the new cell to the active set. Step 4 The MS sends to the BSS an MS ACK Order message in the source cell as a response to the Extended Handoff Direction message. Step 5 The MS sends to the BSS a Reverse Traffic Channel Frames message or Traffic Channel Preamble message from the target cell. Step 6 The MS indicates successful results of processing the Extended Handoff Direction message by sending a Handoff Completion message. Step 7 The BSS sends a BS ACK Order message to the MS. Step 8 The BSS sends to the MSC a Handoff Performed message to notify the MSC that one soft handoff has been successfully performed. ----End

2.3.2 Inter-BSC Soft Handoff

Figure 2-8 shows the inter-BSC soft handoff procedure.

Figure 2-8 Inter-BSC soft handoff

The inter-BSC soft handoff procedure is described as follows: Step 1 The MS sends Pilot Strength Measurement Message to the BSS, reporting that the pilot strength in the target cell exceeds the threshold. Step 2 If the target cell is not in the area of this BSC, the source BSS decides that one or more cells in the target BSS need to support the call, and then sends an A7Handoff Request message to the target BSS. Step 3 The target BSS initiates an A3 connection by sending an A3-Connect message to the specified address. Step 4 The source BSS replies with an A3-Connect Ack message to complete the A3 connection and to acknowledge the addition of cells to an existing A3 connection. Step 5 The source BSS starts to send forward frames to the target BSS. Step 6 The target BSS starts to transmit the forward frames as soon as synchronization has occurred. Step 7 The target BSS starts to send reverse idle frames as soon as the first forward frame is received from the source BSS. The reverse frames contain the timing adjustment information necessary to achieve synchronization. Step 8 The target BSS sends an A7-Handoff Request Ack message to the source BSS to indicate the success of the cell addition.

Step 9 If the source BSS has chosen to be notified of the start of transmission and receipt at the target BSS, when the target BSS have synchronized the A3 traffic sub-channel, the target BSS replies with an A3-Traffic Channel Status message. Step 10 The source BSS sends an Extended Handoff Direction message to the MS to add the new cell to the active set. Step 11 The MS acknowledges receipt of the Extended Handoff Direction message with an MS Ack Order. Step 12 The MS indicates successful results of processing the Extended Handoff Direction message by sending a Handoff Completion message. Step 13 The source BSS acknowledges receipt of the Handoff Completion message by sending a BS Ack Order message. Step 14 The source BSS may send a Handoff Performed message to the MSC. The Handoff Performed message may be sent any time after the Handoff Completion message is received by the BSS. ----End

2.3.3 Softer Handoff

Softer handoff refers to a soft handoff takes place between different sectors of the same BTS. Compared with soft handoffs, the softer handoff saves resources on the Abis interface. In addition, the softer handoff adopts coherent combination for signals of different legs to get higher signal gain than the selective combination used in soft handoff. Figure 2-9 shows the procedure of a softer handoff. Figure 2-9 Procedure of a softer handoff

The procedure of a softer handoff is described as follows: Step 1 The MS sends a Pilot Strength Measurement Message to the BSC, reporting that the pilot strength in the target cell exceeds the threshold. Step 2 If the target cell and source cell are in the same BTS area, the BSC initiates a softer handoff. The BSC requests to add a softer handoff branch and assigns resources by sending an Abis-BTS Setup message to the BTS. Step 3 If the resources can be assigned, the BTS responds with an Abis Connect message. Step 4 BSC acknowledges the Abis Connect message with an Abis Connect Ack message. Step 5 The BTS sends an Abis-BTS Setup Ack message as a response. Step 6 BSC can request BTS to send an Abis Traffic Channel Status message. Step 7 BSC sends an Extended Handoff Direction message to the MS. Step 8 The MS acknowledges having received the Extended Handoff Direction message. Step 9 The MS sends a Handoff Completion message. Step 10 The BSC responds the MS with a BS Ack Order message upon the receipt of the Handoff Completion message. ----End

2.3.4 Intra-BSC Hard Handoff

During an intra-BSC hard handoff, the source BTS and target BTS belong to the same BSC. Figure 2-10 shows the procedure of an intra-BSC hard handoff. Figure 2-10 Intra-BSC hard handoff

The procedure of an intra-BSC hard handoff is described as follows: Step 1 The MS sends a Pilot Strength Measurement Message to the BSC, reporting that the pilot strength in the target cell exceeds the threshold. Step 2 If the target cell in the area of this BSC, and the BSC decides to initiate an intra-BSC hard handoff, the BSC assigns resources, connects to the MS, and sends null forward traffic channel frames to the MS in the target cell. Step 3 The BSS sends to the MS a Handoff Direction message on the air interface of the source cell. Step 4 The MS sends to the BSS an MS ACK Order message in the source cell as a response to the Handoff Direction message. Step 5 The MS sends to the BSS a Reverse Traffic Channel Frames message or Traffic Channel Preamble message from the target cell. Step 6 The MS sends to the BSS a Handoff Completion message from the target cell. Step 7 The BSS sends to the MS a BS ACK Order message from the target cell, and the MS is handed off to the new cell. Step 8 The BSS sends to the MSC a Handoff Performed message to notify the MSC that one hard handoff has been successfully executed. ----End

2.3.5 Inter-BSC Hard Handoff

An inter-BSC may happen in one of the following situations:

The source BTS and target BTS belong to different BSCs. The source BTS and target BTS belong to the same BSC. The source BSS and target BSS are not connected with the same MSC.

Figure 2-11 shows the procedure of an inter-BSC hard handoff.

Figure 2-11 Inter-BSC hard handoff

The procedure of an inter-BSC hard handoff is described as follows: Step 1 The MS sends a Pilot Strength Measurement Message to the BSC, reporting that the pilot strength in the target cell exceeds the threshold. Step 2 The source BSS sends a Handoff Required message with the cell list to the MSC, requesting to perform a hard handoff to the target cell. Step 3 Since the Handoff required indicates that the handoff is a hard handoff, the MSC sends to the target BSS a Handoff Request message. Step 4 After receiving the Handoff Request message from the MSC, the target BSS assigns related radio resources and connects the target, and sends to the MS null forward traffic channel frames. Step 5 The target BSS sends to the MSC a Handoff Request Ack message and waits for the MS accessing the assigned radio channel. Step 6 The MSC prepares to perform a handoff from the source BSS to the target BSS, and sends a Handoff Command message to the source BSS. Step 7 The source BSS sends to the MS a Handoff Direction message on Um interface. If the MS is allowed to return to the source BSS, the source BSS turns on the timer.

Step 8 The MS sends an MS Ack Order to the source BSS as a response to the Handoff Direction message. Step 9 The source BSS sends to the MSC a Handoff Commenced message to notify the MSC that the MS has been ordered to hand off to the target BSS channel. Step 10 The MS sends a Reverse Traffic Channel Frames message or Traffic Channel Preamble message to the target BSS. Step 11 The MS sends a Handoff Completion message to the target BSS. Step 12 The target BSS sends a BS Ack Order message. Step 13 The target BSS sends to the MSC a Handoff Complete message to notify the MSC that the MS has completed the hard handoff. Step 14 The MSC sends a Clear Command message to the source BSS to release all the resources. Step 15 The source BSS sends a Clear Complete message to notify the MSC that the resources are cleared. ----End

2.3.6 Handoff in System Access State

Types of the handoff in access state are as follows:

Access entry handoff: Before sending an Origination message or Paging Response, the MS performs a pilot search and hands off to the adjacent BSS with better pilot strength. In the new BSS, the MS then sends an Origination message or Paging Response. Access probe handoff: After sending an Origination message or Paging Response but before receiving a BS Ack Order from the BSS, the MS hands off to the adjacent BSS. There the MS resends the Origination message or Paging Response for new probe. Access handoff: After sending an Origination message or Paging Response and receiving a BS Ack Order from the BSS, the MS hands off to the adjacent BSS, waiting for a Channel Assignment message. Channel assignment into soft handoff (SHO): The BSS includes multiple PNs in an Extended Channel Assignment message (ECAM). At the request of the BSS, the MS sets up branches on the active set formed by these PNs. That is, the call enters the SHO state when it is set up.

During the access of the MS, one or more of the above handoffs might occur; there might be no handoff at all. The handoff in the same state might occur repeatedly. In the access state, all handoffs are cooperative rather than independent. They jointly guide the MS to use the paging channel and access channel with optimal pilot strength. The following are handoffs in mobile origination and mobile termination access states.

Handoff in MO Call Access State

In this example, when a MO call enters the traffic channel from access state, the MS performs access probe handoffs twice to BSS1 and BSS2. The MS repeats access probe until it receives a BS Ack Order; then it performs an access handoff. The access handoff might occur repeatedly. That is, the MS tries different handoffs in the access state to search the paging channel and access channel with optimal pilot strength. Figure 2-12 shows the procedure of a handoff in MO call access state. Figure 2-12 Handoff in MO call access state

The procedure of a handoff in MO call access state is described as follows: Step 1 The MS sends Origination message 1 over the access channel of the source BSS. If the BSS fails to receive the message and does not send BS Ack Order, the MS performs a probe handoff.

Figure 2-12 adds a number after the name of the same message, indicating it is sent several times to different targets. For example, Origination message 1 refers to the message sent at the first time.

Step 2 The MS performs the access probe handoff to BSS1 while sending Origination message 2, and requires response from the BSS. Step 3 After receiving Origination message, the target BSS1 sends a BS Ack Order to the MS, but the MS fails to receive the response. Step 4 Because BSS1 is not the source BSS, it sends an Origination message to the source BSS. If BSS1 and the source BSS belong to the same BSC module, the sending is unnecessary. Step 5 The source BSS creates a CM Service Request message and sends it to the MSC after encapsulation. Step 6 Not receiving a BS Ack Order message, the MS performs access probe handoff to BSS2 and sends Origination message 3 over the access channel. Step 7 After receiving the Origination message, the target BSS2 sends a BS Ack Order message to the MS. the MS stops sending Origination messages when receiving the response, and the access probe handoff ends. If the MS cannot enter the traffic channel at specified time, it will resend an Origination message to start access handoff. Step 8 Because BSS2 is not the source BSS, it sends an Origination message to the source BSS. If BSS2 and the source BSS belong to the same BSC module, the sending is unnecessary. Step 9 The MSC requests the source BSS to assign resources by sending an Assignment Request message. This step might occur any time after step 5. Step 10 After all probed BSSs (including the source BSS) assign traffic channels for the MS, they send Extended Channel Assignment message and the idle forward traffic channel frame over the paging channel at the same time. Therefore, it is more possible for the MS to receive the message. The MS only accepts one Extended Channel Assignment message. (Suppose it is from the target BSS2). Step 11 The MS sends a TCH preamble over the specified reverse traffic channel; then it can start sending the traffic frame. Step 12 After capturing the reverse traffic channel, any BSS (suppose it is the target BSS1) will send the captured channel to the source BSS. If the BSS capturing the channel and the source BSS are in the same module, the sending is unnecessary. Step 13 The source BSS sends a BS Ack Order message to the MS and requests response. Step 14 The MS sends an MS Ack Order message over the reverse traffic channel and transfers idle frame, responding to the BS Ack Order message from BSS. Step 15 The source BSS sends a Service Connect message to the MS to specify the service configuration.

Step 16 After receiving the Service Connect message, the MS starts processing service according the specified service configuration and sends a Service Connect Completion message as response. Step 17 When the radio traffic channel and terrestrial circuit are all connected successfully, BSS sends an Assignment Complete message to the MSC. ----End

Handoff in MT Call Access State

In this example, when a MT call enters the traffic channel from access state, the MS performs two access probe handoffs to target BSS1 and target BSS2. The MS repeats access probe until it receives a BS Ack Order; then it performs the access handoff. Figure 2-13 shows the procedure of a handoff in MT call access state.

Figure 2-13 Handoff in MT call access state

The procedure of a handoff in MT call access state is described as follows: Step 1 When the paged the MS is in the service area of the MSC, the MSC sends a Paging Request message to all BSSs to start the call setup process of paging the MS. Step 2 The source BSS sends a General Page message with the MS identity over the paging channel. Step 3 After identifying the Paging Request with the MS identity over the paging channel, the MS sends Page Response message 1 to the source BSS. However, the source BSS fails to receive the message, so it does not respond. Therefore, the MS performs the access probe handoff.

Figure 2-13 adds a number after the name of the same message, indicating it is sent several times to different targets. For example, Origination message 1 refers to the message sent at the first time.

Step 4 The MS performs the access probe handoff to the target BSS1. Meanwhile, it sends Page Response message 2 over the access channel. Step 5 After receiving the Page Response message, the target BSS1 sends a BS Ack Order message to the MS. The MS fails to receive the response. Step 6 Because BSS1 is not the source BSS, it sends a Page Response message to the source BSS. If BSS1 and the source BSS belong to the same BSC module, the sending is unnecessary. Step 7 The source BSS creates a CM Service Request message and sends it to the MSC after encapsulation. Step 8 Because the MS does not receive the response, it performs access probe handoff to BSS2 and sends Page Response message 3 over the access channel. Step 9 After receiving the Page Response message, the target BSS2 sends a BS Ack Order to the MS. the MS stops sending Page Response messages when receiving the response, and the access probe handoff ends. If the MS cannot enter the traffic channel at specified time, it will restart the access probe handoff. Step 10 Because BSS2 is not the source BSS, it sends a Page Response message to the source BSS. If BSS2 and the source BSS belong to the same BSC module, the sending is unnecessary. Step 11 The MSC sends an Assignment Request message to the source BSS to request resources assignment. This step might occur any time after step 7. Step 12 All probed BSSs assign traffic channels for the MS. The BSSs then send an Extended Channel Assignment message and the idle forward traffic channel frame over the paging channel. Because the message is sent by many BSSs at the same time, it is more likely to be received by the MS. However, the MS only accepts one Extended Channel Assignment message. Suppose that the MS receives this message from the target BSS2. Step 13 The MS sends a TCH preamble over the specified reverse traffic channel; then it can start sending the traffic frame. Step 14 After capturing the reverse traffic channel, any BSS (suppose it is the target BSS1) will send the captured channel to the source BSS. If the BSS capturing the channel and the source BSS are in the same BSC module, the sending is unnecessary. Step 15 The source BSS sends a BS Ack Order message over the forward traffic channel to the MS and requires response. Step 16 The MS sends an MS Ack Order message over the reverse traffic channel and transfers idle frame, responding to the BS Ack Order message from BSS.

Step 17 The source BSS sends a Service Connect message to the MS to specify the service configuration. Step 18 After receiving the Service Connect message, the MS starts processing service according the specified service configuration and sends a Service Connect Completion message as response. Step 19 When the radio traffic channel and terrestrial circuit are all connected successfully, the source BSS sends an Assignment Complete message to the MSC. ----End

2.4 SMS Procedures

The SMS procedure refers to the procedures of the services between the MS and BSS when the MS originates or terminates the short message transmission. The length of the short message determines whether the short message is transmitted on the control channel or the traffic channel.

2.4.1 MO Short Message Transmission over the Access Channel

The small-size short message can be transmitted from an idle MS over the access channel. Figure 2-14 shows the procedure of a MO short message sending over the access channel. Figure 2-14 Procedure of an MO short message sending over the access channel

The procedure of a MO short message sending over the access channel is described as follows: Step 1 The MS sends point-to-point short messages to the network through an Access Channel SMS Deliver message (Data Burst message) over the access channel. Step 2 If the MS has requested a Layer 2 Ack message, BSS acknowledges the short message received over the access channel by sending a Layer 2 Ack message over the paging channel. Step 3 BSS sends to the MSC an Application Data Deliver Service (ADDS) Transfer message, containing the SMS message received from the MS in the ADDS User Part element.

----End

2.4.2 MT Short Message Transmission over the Paging Channel

The small-size short message can be transmitted from an MSC to an idle MS over the paging channel. The procedures of the MT small-size short message sending over the paging channel include:

Sending the Point-To-Point Short Message to an MS Sending the Broadcast Short Message to an MS

Sending the Point-To-Point Short Message to an MS

Figure 2-15 shows the procedure for sending a point-to-point short message to an MS over a paging channel. Figure 2-15 Procedure for sending a point-to-point short message to an MS over a paging channel

The procedure for sending a point-to-point short message to an MS over the paging channel is described as follows: Step 1 The MSC determines that a point-to-point short message is to be sent to an idle MS. The MSC sends an ADDS Page message to the BSS. The ADDS Page contains the short message in its ADDS User Part information element. If the MSC requires an acknowledgment, it includes the Tag information element in the ADDS Page. Step 2 The BSS sends a Data Burst message to the MS over the paging channel. Before sending the short message, the BSS may perform vendor-specific procedures such as paging the MS. Step 3 If a Layer 2 Ack has been requested, the MS acknowledges the receipt of the message with a Layer 2 Ack. Step 4 If the MSC requested an acknowledgment by including the Tag information element in the ADDS Page, the BSS replies with an ADDS Page Ack including the Tag information element set identical to the value sent by the MSC. ----End

Sending the Broadcast Short Message to an MS

Figure 2-16 shows the procedure for sending a broadcast short message to an MS over a paging channel. Figure 2-16 Procedure for sending a broadcast short message to the MS over a paging channel

The procedure for sending a broadcast short message to an MS over a paging channel is described as follows: Step 1 The MSC sends an ADDS Page to the BSS. The ADDS Page message contains the SMS broadcast message in its ADDS User Part information element. If the MSC requires an acknowledgment from the BSS, the ADDS Page message contains the tag element. Step 2 If the MSC requests an acknowledgment from the BSS by including the Tag element in the ADDS Page message, the BSS replies with an ADDS Page Ack including the Tag element the same as the Tag element in the ADDS Page message received from the MSC. Step 3 The BSS sends a Data Burst Message (Paging Channel SMS Broadcast Deliver) to the appropriate MSs over the paging channel. ----End

2.4.3 MO Short Message Transmission over the Traffic Channel

When the short message is too big to be sent over the access channel, the MS sends an Origination message to the BSS (with the service option of the short message) to set up the traffic channel on Um interface. If a traffic channel has already been set up for the MS, the MS sends the short message directly on this channel. Figure 2-17 shows the procedure of the MO short message sending over the traffic channel.

Figure 2-17 Procedure of the MO short message sending over the traffic channel

The procedure of the MO short message sending over the traffic channel is described as follows: Step 1 The BSS receives a Traffic Channel SMS Deliver message from the traffic channel. The burst type of this message of is SMS. Step 2 The BSS sends a Layer 2 Ack to the MS over the traffic channel. Step 3 The BSS sends an ADDS Deliver message to MSC. The ADDS User Part element contains the short message which was received from the MS. ----End

2.4.4 MT Short Message Transmission over the Traffic Channel

When the short message is too big to be sent over the paging channel, the MSC pages the MS and sets up a traffic channel at the Um interface before sending the message. If a traffic channel has already been set up for the MS, the MSC sends the short message directly on this channel. Figure 2-18 shows the procedure for sending a short message to an MS over the traffic channel. Figure 2-18 Procedure for sending a short message to an MS over the traffic channel

The procedure for sending a short message to an MS over the traffic channel is described as follows:

Step 1 If the MS has already occupied the traffic channel when the MSC sends a short message to the MS. The MSC sends an ADDS Deliver message to the BSS. Step 2 The BSS transmits a Data Burst Message (Traffic Channel SMS Deliver message) to send a short message over the forward traffic channel. If the BSS does not receive an acknowledgment after transmitting the Data Burst Message, it shall retransmit the message. The number of times that the BSS retransmits the Data Burst Message cannot exceed the maximum number. Step 3 After the MS receives the short message over the traffic channel, it acknowledges the receiving by sending a Layer 2 Ack message over the traffic channel. Step 4 If the ADDS Deliver message sent by the MSC includes the tag element, the BSS replies with an ADDS Deliver Ack message to the MSC after it receives a Layer 2 Ack message from the MS. In the ADDS Deliver Ack message, the BSS includes the Tag element that is the same as the tag element included in the ADDS Deliver message. ----End

2.5 Data Service Procedures

In the CDMA2000 1X data service procedure, the wireless data service can be in one of the following three states:

Active state: There is air traffic channel between the MS and the BTS. Data can be transferred at both sides. The connection of the Um interface, A8 interface, and A10 interface is retained. Dormant state: There is no air traffic channel between the MS and BTS, but there is PPP link between them. The connection of Um interface and A8 is released, and that of A10 interface is retained. Null state: The air traffic channel or PPP link does not exist between the MS and the BTS. The connection of A1 interface, A8 interface, and A10 interface is released.

2.5.1 Mobile Originated Call

This section describes the MO data service procedure, as shown in Figure 2-19.

Figure 2-19 MO data service

The procedure of the MO data service is described as follows: Step 1 The MS sends an Origination message to the BTS over the access channel. Step 2 After receiving the Origination Message, the BSS sends to the MS a BS ACK Order. Step 3 The BSS creates a CM Service Request message and sends it to the MSC. Step 4 The MSC sends to the BSS an Assignment Request message for radio resources assignment. Step 5 The BSS sends an A9-Setup-A8 message to the PCF, requesting the setup of an A8 connection. Step 6 The PCF sends an A11 Registration Request message to the PDSN, requesting the setup of an A10 connection.

Step 7 The PDSN accepts the request for setting up an A10 connection and sends an A11 Registration Reply message back to the PCF. Step 8 The PCF sends an A9-Connect-A8 message back to the BSS, and thus the A8 and A10 connections are successfully set up. Step 9 The BTS sends an extended channel assignment message (ECAM) over the paging channel. Step 10 The MS sends a TCH Preamble message over the assigned reverse traffic channel. Step 11 After receiving the TCH Preamble message, the BTS sends a BS ACK Order over the forward traffic channel. Step 12 After receiving the BS Ack Order message, the MS sends an MS ACK Order and transmits null traffic frames over the reverse traffic channel. Step 13 The BSS sends to the MS a Service Connect Message or Service Option Response Order message to assign service configurations for the call. Step 14 After receiving the Service Connect message, the MS starts to process service according to the assigned service configurations and responds with a Service Connect Complete Message. Step 15 Upon completion of the radio traffic channel and terrestrial circuit setup as well as through connection, the BTS sends to the MSC an Assignment Complete Message. Step 16 The MS negotiates with the PDSN to set up a PPP connection. In the mobile IP mode, the mobile IP connection also needs to be set up. The PPP message and mobile IP message are sent over the traffic channel. Step 17 After PPP connection is successfully set up, the data service enters the connected state. ----End

2.5.2 SCH Setup

The supplemental channel (SCH) setup procedures include:

SCH setup procedure initiated by the MS SCH setup procedure initiated by the BSC

The only difference is that the latter is triggered by the radio link protocol (RLP) based on the data traffic rather than by the Supplemental Channel Request message (SCRM) message. This section describes the SCH setup procedure initiated by the MS, as shown in Figure 2-20.

Figure 2-20 SCH setup procedure initiated by the MS

The procedure of the SCH setup initiated by the MS is described as follows: Step 1 Under the setup of the packet data service call, the MS may report a Supplemental Channel Request message, requesting the setup of an SCH channel. Step 2 The BSC sends an Abis-BTS Setup message to the BTS, requesting the BTS to set up cells. Step 3 The BTS sends an Abis Connect message to the BSC after setting up the channel. Step 4 The BSC responds to the BTS with an Abis Connect Ack message. Step 5 After setting up all the channels, BTS sends an Abis-BTS Setup Ack message to the BSC. To this step, the circuit is successfully set up. Step 6 The BSC sends an Abis-Burst Request message to the BTS to activate the BTS. Step 7 The BTS sends an Abis-Burst Response message back to the BSC. Step 8 The BSC sends an Abis-Burst Commit message to the BTS. When the BTS receives this message, the SCH is activated and data can be transmitted over the SCH. Step 9 The BSC sends an Extended Supplemental Channel Assignment message to assign SCH channel for the MS so that the packet data service can achieve highspeed transmission over the SCH channel.

There is no specific procedure to release the SCH. When the BSC dynamically allocates the SCH, it sets the rate and duration of the SCH. When the duration ends, the SCH is released.

----End

2.5.3 Dormant State

The process that the data service enters the dormant state is initiated by the MS or the BSS. The two processes are similar. When the MS decides to enter the dormant state, it sends a Release Order to the BSS, requesting the BSS to release the traffic channel. The subsequent processing is the same with the processing in the procedure initiated by the BSS. This section describes the procedure intiated by the BSS that the data service enters the dormant state, as shown in Figure 2-21. Figure 2-21 Procedure intiated by the BSS that the data service enters the dormant state

The procedure intiated by the BSS that the data service enters the dormant state is described as follows: Step 1 When the packet data service enters a connected state, the BSS maintains a dormant timer for packet data. The dormant timer is reset when there are RLP data frames to be received or transmitted. Step 2 If the dormant timer expires, the BSS sends a Clear Request message to the MSC to release the connection. Step 3 The MSC sends a Clear Command message to the BSS to notify it to release relevant resources. Step 4 The BSS initiates the traffic channel release procedure. Step 5 The BSS sends an A9-Release-A8 message to the PCF, with the cause value of Packet Call Going Dormant, to notify it to release relevant resources. Note that A10/A11 connections are not released. Step 6 The PCF sends an A9-Release-A8 Complete message back.

Step 7 After relevant resources are released, the BSS sends a Clear Complete message back to the MSC. Step 8 The MS enters the dormant state. ----End

2.5.4 Call Activation Initiated by the MS

When the MS is in dormant state, if the MS has data to transmit, the MS reactivates the data connection. This procedure is similar to the call origination procedure, except that A10/A11 connections, PPP connection and mobile IP connection (if mobile IP is in use) do not need to be re-established.

2.5.5 Call Activation Initiated from the Network

This section describes the procedure of call activation initiated from the network, as illustrated in Figure 2-22.

Figure 2-22 Call activation initiated by network side

The procedure of the call activation initiated by the network side is described as follows: Step 1 The MS is in the dormant state. The PPP connection exists. Step 2 The PDSN sends packet data traffic to the PCF on the A10 connection. Step 3 Finding the packet data call is in a dormant state, the PCF sends an A9-BS Service Request message to the BSS, requesting the packet data service. Step 4 The BSS sends a BS Service Request message to the MSC to re-connect the call. Step 5 The MSC sends a BS Service Response message back to acknowledge the call setup request.

Step 6 The BSS responds to the PCF with an A9-BS Service Response message. Step 7 The MSC sends a Paging Request message to set up the MS-terminated packet service call. Step 8 The BSS sends a General Page message over the paging channel. Step 9 The MS acknowledges with a Page Response message over the access channel. Step 10 The BSS puts the Page Response message into a Complete Layer 3 Information and sends it to the MSC. Step 11 The BSS sends back a BS Ack Order message to the MS to acknowledge the receipt of Page Response message. Step 12 The MSC sends an Assignment Request message to the BSS, requesting the allocation of radio resources and A8 connection. Step 13 The BSS and the MS execute the radio resources setup procedure. Step 14 The BSS sends an A9-Setup-A8 message to PCF for setting up A8 connection. Step 15 The PCF responds to the BSS with an A9-Connect-A8 message. The A8 connection is set up. Step 16 After the radio link and A8 connection are set up successfully, the BSS sends an Assignment Complete message to the MSC and the data service enters the active state. Step 17 The MS enters the active state. ----End

2.5.6 Call Release Initiated by the MS

Figure 2-23 shows the call release initiated by the MS.

Figure 2-23 Call clear initiated by MS

The procedure of a call release initiated by the MS is described as follows: Step 1 The MS sends a Release Order message to the BSS over the control channel. Step 2 The BSS sends a Clear Request message to the MSC. Step 3 While releasing the network side resources, the MSC sends Clear Command message to the BSS. Step 4 The BSS sends a Release Order message to the MS. Step 5 The BSS sends an A9-Release-A8 message to the PCF, requesting the release of the A8 connection. Step 6 The PCF sends an A11-Registration-Request message to the PDSN, requesting the release of the A10 connection. Step 7 The PDSN sends an A11-Registration-Reply message to PCF. The A10 connection release is complete. Step 8 The BSS sends an A9-Release-A8 Complete message to the PCF. The A8 connection release is complete. Step 9 The BSS sends a Clear Complete message to the MSC. ----End