CDMA2000 Family

A1 Signaling

http://www.3gpp2.org/Public_html/specs/A.S0014-0_v1.0.pdf

The Base Station Application Part (BSAP) is the application layer signaling protocol that provides messaging to accomplish the functions of the A1 Interface component of the MSC - BS Interface. BSAP is split into two sub-application parts; the BS Management Application Part (BSMAP), and the Direct Transfer Application Part (DTAP).
The BS Management Application Part (BSMAP) supports all Radio Resource Management and Facility Management procedures between the MSC and the BS, or to a cell(s) within the BS. BSMAP messages are not passed to the MS, but are used only to perform functions at the MSC or the BS. A BSMAP message (Complete Layer 3 Information) is also used together with a DTAP message to establish a connection for a MS between the BS and the MSC, in response to the first layer 3 air interface message sent by the MS to the BS for each MS system request. The description of the layer 3 protocol for the BSMAP information exchange is contained within this specification.

The Direct Transfer Application Part (DTAP) messages are used to transfer call processing and mobility management messages between the MSC and BS. DTAP messages carry information that is primarily used by the MS. The BS maps the DTAP messages going to and coming from the MSC from/into the appropriate air interface signaling protocol.
The A1 header structure is as follows:

BSMAP Header

DTAP Header

Message Discriminator
The message discriminator; this has a value of 0 in BSMAP messages and 1 in DTAP messages.

Message Type
The Message type can be either BSMAP messages or DTAP messages.

BSMAP Messages
The following BSMAP message types are available:

DTAP Messages
The following DTAP message types are available:

Protocol Discriminator
The protocol discriminator can have the following values:
Call processing and call related supplementary services
5 Mobility Management
6 Radio Resource Management
9 Facility Management
11 Other Signaling Procedures
15 Reserved for Test Procedures

Length Indicator
The length of the message

DLCI
The data link connection identifier

Reserved Octet
The Octet is reserved

Enlarge	More Details

Interested in more details about testing this protocol?

A3 Signaling

http://www.3gpp2.org/Public html/specs/A.S0015-0 v1.0.pdf.

The A3 interface is composed of signaling and user traffic subchannels. It provides the ability to establish and remove A3 traffic connections. The A3 interface also provides support for operational procedures, such as turning on/off voice privacy or changing the service configuration of a call.
The A3 Signaling header structure is as follows:

Message Type II
This contains the Message Type II message. The message types are followed by a set of information elements with the format shown above. The following message types are available:

Interested in more details about testing this protocol?

A7 Signaling

http://www.3gpp2.org/Public html/specs/A.S0015-0 v1.0.pdf

The A7 interface provides direct BS to BS signaling for the support of an efficient soft handoff procedure. Only a call release procedure interrupts any Handoff procedure.
Multiple concurrent A7 Handoff Add procedures are prohibited for the same physical Channel on the same call.
The A7 Signaling message header appears as follows:

Message Type II
The message type distinguishes between the types of messages. The message types are followed by a set of information elements with the format shown above.
The following message types are available:

Interested in more details about testing this protocol?

A9 Signaling

http://www.3gpp2.org/Public html/specs/A.S0016-0 v1.0.pdf

The A9 interface carries signaling information between the BS and the PCF. The A8/A9 interfaces support mobility between BSCs under the same PCF.
The A9 Signaling header appears as follows:

Message Type
The type of message. The message types are followed by a set of information elements with the format shown above.
The following message types are available
MessageType – Determines traffic distribution by different message types.

Interested in more details about testing this protocol?

A11 Signaling

http://www.3gpp2.org/Public_html/specs/A.S0017-0_v1.0.pdf.

The A11 interface carries signaling information between the PCF and the PDSN for packet data services and provides a signaling connection between a PCF and PDSN pair (A11). A11 signaling messages are also used for passing accounting related and other information from the PCF to the PDSN. The A10/A11 interfaces support mobility between PCFs under the same PDSN.
The format of the A11 Signaling messages header is as follows:

A11 Message Type
The A11 message type field defines the message type. The following message types are available:

The message type is followed by information elements in the form of a TLV or in the form of a value.

Enlarge	More Details

Interested in more details about testing this protocol?

A13 Signaling

http://www.3gpp2.org/Public_html/specs/A.S0007-A_v1.0.pdf.

The A13 protocol is responsible for information exchange between the source and target AN. The protocol is divided up into information from the target to source direction, and information from the source to the target direction. Signaling over the A13 interface requires a reliable transport protocol and appropriate addressing and routing mechanisms to deliver messages from the target to source destination.
The A13 header appears as follows:

A13 Message Type
The Message type value distinguishes between four types of A13 session information messages.
The following message types are available:

The message types are followed by a set of information elements with the format shown above.

Information Element Identifier
The information element identifier

IE Length
The length of the information element.

Interested in more details about testing this protocol?

A14 Signaling

http://www.3gpp2.org/Public html/specs/A.S0007-A v1.0.pdf

The A14 interface between the AN and the SC/MM function of the PCF is used for performing HRPD Session and HRPD mobility related operations.
The A14 interface supports the following procedures:

• UATI assignment procedure.
• General updating procedure.
• Terminal authentication.
• Session release.
• Session information updating procedure.
• Paging procedure.

The A14 header appears as follows:

The message types are followed by a set of information elements with the format shown above.

Message Types
The type of message. The following message types are available:

Interested in more details about testing this protocol?

A15 Signaling

(belongs to TCP/IP)
http://www.3gpp2.org/Public_html/specs/A.S0007-A_v1.0.pdf

The A15 interface is used for sending paging request messages from the AN that manages the registered sector to the ANs that send paging messages over the air. This interface is used for inter AN paging.
The header for the A15 protocol appears as follows:

Message Type
Distinguishes between the various message types. The following message types are available:

The message types are followed by a set of information elements with the format shown above.

Interested in more details about testing this protocol?

1 2

CDMA2000 Family Protocol Information
A1 | A3 | A7 | A8 | A9 | A10 | A11 | A12 | A13 | A14 | A15 | CDMA2000 Reference Page